comparison OPPL/oppl_query.xml @ 15:622cde484f4c draft

Add new tool to perform OPPL queries
author Mikel Egana Aranguren <mikel-egana-aranguren@toolshed.g2.bx.psu.edu>
date Thu, 12 Jul 2012 17:12:00 +0200
parents
children c9e01f86b07c
comparison
equal deleted inserted replaced
14:68c4ae500a13 15:622cde484f4c
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 -Xmx7000M -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 -Xmx7000M -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 -Xmx7000M -Xms250M -DentityExpansionLimit=1000000000 -jar ${__tool_data_path__}/shared/jars/oppl_query.jar $ontology $reasoner $answer_format "$query" > $output 2>/dev/null
23 </commadn>-->
24
25
26 <inputs>
27 <param name="ontology" type="data" label="Input ontology file"/>
28 <param name="query" type="text" size="100" value="" label="OPPL Query" />
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 </param>
34 <param name="answer_format" type="select" label="Choose how to render the retrieved entities">
35 <option value="URI" selected="true">URI</option>
36 <option value="URIfragment">URI fragment</option>
37 <option value="URIfragment2OBO">OBO type URI fragment (e.g. GO_0000022 to GO:0000022)</option>
38 </param>
39 </inputs>
40 <outputs>
41 <data type="data" format="text" name="output" />
42 </outputs>
43 <tests>
44 <test>
45 <param name="input" value="test.owl"/>
46 <param name="query" value="?p:OBJECTPROPERTY SELECT Transitive ?p "/>
47 <param name="reasoner" value="Pellet"/>
48 <param name="answer_format" value="URIfragment"/>
49 <output name="out_file" file="query_result"/>
50 </test>
51 </tests>
52 <help>
53
54 **About OPPL-Query-Galaxy**
55
56 OPPL-Query-Galaxy can be used to execute an OPPL query against an OWL ontology (?whole:CLASS, ?part:CLASS SELECT ?part SubClassOf part_of some ?whole WHERE ?part != Nothing). The result is a two column table with the entities that have been bound by the variables.
57
58 **Formats**
59
60 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. The output is a list of terms.
61
62 **Contact**
63
64 Please send any request or comment to mikel.egana.aranguren@gmail.com.
65
66 </help>
67
68 </tool>