Mercurial > repos > mikel-egana-aranguren > oppl

comparison oppl_query.xml @ 19:cc270db37d33 draft

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Directories re-arranged
author Mikel Egana Aranguren <mikel-egana-aranguren@toolshed.g2.bx.psu.edu>
date Sat, 06 Oct 2012 21:50:39 +0200
parents
children
comparison
equal deleted inserted replaced
18:d3616fac4ca5 19:cc270db37d33
1 <tool id="oppl_query" name="Perform an OPPL query against an ontology" version="1.0.1">
2 <description>It performs a query, expressed in OPPL Syntax, against an OWL ontology</description>
3
4 <!-- Galaxy is not happy with OPPL throwing info into stderr, and I have redirected stderr to /dev/null, which is a bad solution since OPPL galaxy does not inform properly when it fails -->
5 <!-- More info on the stderr issue: http://wiki.g2.bx.psu.edu/Future/Job%20Failure%20When%20stderr -->
6 <!-- Testing with wrapper.sh but no success so far -->
7
8 <!-- DEFAULT SETTINGS -->
9
10 <!-- For big ontologies I use -Xmx3000M -Xms250M -DentityExpansionLimit=1000000000 If that's too much for your machine simply delete or modify at will, but since Galaxy is usually used in a server setting it makes sense to use a big chunk of memory -->
11
12 <command>
13 java -Xmx3000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_query.jar $ontology $reasoner $answer_format $query > $output 2>/dev/null
14 </command>
15
16 <!-- FACT++ -->
17
18 <!-- If you are planning to use FaCT++ you have to uncomment bellow (And comment the default settings above) and replace the -Djava.library.path with the appropiate JNI library path for your platform:FaCT++-linux-v1.5.2/64bit, FaCT++-linux-v1.5.2/32bit, FaCT++-OSX-v1.5.2/64bit, ...... -->
19 <!-- Using this setting doesn't upset the rest of the reasoners so you may as well leave it on if you plan to switch between FaCT++, Pellet and HermiT -->
20
21 <!--<command>
22 java -Djava.library.path=${__tool_data_path__}/shared/jars/FaCT++-linux-v1.5.2/64bit -Xmx3000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_query.jar $ontology $reasoner $answer_format $query > $output 2>/dev/null
23 </command>-->
24
25
26 <inputs>
27 <param name="ontology" type="data" label="Input ontology file"/>
28 <param name="query" type="data" format="text" label="OPPL query file" />
29 <param name="reasoner" type="select" label="Choose reasoner">
30 <option value="Pellet" selected="true">Pellet</option>
31 <option value="HermiT">HermiT</option>
32 <option value="FaCTPlusPlus">FaCT++</option>
33 <option value="Elk">Elk (Not all axioms supported)</option>
34 </param>
35 <param name="answer_format" type="select" label="Choose how to render the retrieved entities">
36 <option value="URI" selected="true">URI</option>
37 <option value="URIfragment">URI fragment</option>
38 <option value="URIfragment2OBO">OBO type URI fragment (e.g. GO_0000022 to GO:0000022)</option>
39 </param>
40 </inputs>
41 <outputs>
42 <data type="data" format="text" name="output" />
43 </outputs>
44 <!--<tests>
45 <test>
46 <param name="input" value="test.owl"/>
47 <param name="query" value="?p:OBJECTPROPERTY SELECT Transitive ?p "/>
48 <param name="reasoner" value="Pellet"/>
49 <param name="answer_format" value="URIfragment"/>
50 <output name="out_file" file="query_result"/>
51 </test>
52 </tests>-->
53 <help>
54
55 **About OPPL-Query-Galaxy**
56
57 OPPL-Query-Galaxy can be used to execute an OPPL query against an OWL ontology. The result is a two column table with the entities that have been bound by the variables.
58
59 **Usage**
60
61 An ontology is needed as input: load it with Get Data >> Upload File from your computer or redirect the output of another galaxy tool. OPPL-Query-Galaxy uses the OWL API, and therefore it can load any ontology format that such API is able to load: OBO flat file, OWL (RDF/XML, OWL/XML, Functional, Manchester), turtle, and KRSS. In case the loaded ontology includes OWL imports, OPPL-Query-Galaxy will try to resolve them.
62
63 An OPPL query must be provided in a file: an OPPL query is an OPPL script without the actions part, e.g. ?whole:CLASS, ?part:CLASS SELECT ?part SubClassOf part_of some ?whole WHERE ?part != Nothing.
64
65 The reasoner can be Pellet, HermiT, FaCT++ or Elk.
66
67 The returned entities can be rendered using their URI, their URI fragment, or OBO type URI fragment (e.g. GO_0000022 to GO:0000022).
68
69 **Contact**
70
71 Please send any request or comment to mikel.egana.aranguren@gmail.com.
72
73 </help>
74
75 </tool>