|
23
|
1 <tool id="blast2go" name="Blast2GO" version="0.0.9">
|
|
|
2 <description>Maps BLAST results to GO annotation terms</description>
|
|
|
3 <requirements>
|
|
|
4 <requirement type="package" version="2.5">b2g4pipe</requirement>
|
|
|
5 </requirements>
|
|
|
6 <command interpreter="python">
|
|
|
7 blast2go.py "${xml}" "${prop.fields.path}" "${tab}"
|
|
|
8 </command>
|
|
|
9 <stdio>
|
|
|
10 <!-- Wrapper ensures anything other than zero is an error -->
|
|
|
11 <exit_code range="1:" />
|
|
|
12 <exit_code range=":-1" />
|
|
|
13 </stdio>
|
|
|
14 <inputs>
|
|
|
15 <param name="xml" type="data" format="blastxml" label="BLAST XML results" description="You must have run BLAST against a protein database such as the NCBI non-redundant (NR) database. Use BLASTX for nucleotide queries, BLASTP for protein queries." />
|
|
|
16 <param name="prop" type="select" label="Blast2GO settings" description="One or more configurations can be setup, such as using the Blast2GO team's server in Spain, or a local database.">
|
|
|
17 <options from_file="blast2go.loc">
|
|
|
18 <column name="value" index="0"/>
|
|
|
19 <column name="name" index="1"/>
|
|
|
20 <column name="path" index="2"/>
|
|
|
21 </options>
|
|
|
22 </param>
|
|
|
23 </inputs>
|
|
|
24 <outputs>
|
|
|
25 <data name="tab" format="tabular" label="Blast2GO ${prop.fields.name}" />
|
|
|
26 </outputs>
|
|
|
27 <tests>
|
|
|
28 <test>
|
|
|
29 <param name="xml" value="blastp_sample.xml" ftype="blastxml"/>
|
|
|
30 <param name="prop" value="Spain_2011_June"/>
|
|
|
31 <output name="tab" file="blastp_sample.blast2go.tabular" ftype="tabular"/>
|
|
|
32 </test>
|
|
|
33 </tests>
|
|
|
34 <help>
|
|
|
35 .. class:: warningmark
|
|
|
36
|
|
|
37 **Note**. Blast2GO may take a substantial amount of time, especially if
|
|
|
38 running against the public server in Spain. For large input datasets it
|
|
|
39 is advisable to allow overnight processing, or consider subdividing.
|
|
|
40
|
|
|
41 -----
|
|
|
42
|
|
|
43 **What it does**
|
|
|
44
|
|
|
45 This runs b2g4Pipe v2.5, which is the command line (no GUI) version of
|
|
|
46 Blast2GO designed for use in pipelines.
|
|
|
47
|
|
|
48 It takes as input BLAST XML results against a protein database, typically
|
|
|
49 the NCBI non-redundant (NR) database. This tool will accept concatenated
|
|
|
50 BLAST XML files (although they are technically invalid XML), which is very
|
|
|
51 useful if you have sub-divided your protein FASTA files and run BLAST on
|
|
|
52 them in batches.
|
|
|
53
|
|
|
54 The BLAST matches are used to assign Gene Ontology (GO) annotation terms
|
|
|
55 to each query sequence.
|
|
|
56
|
|
|
57 The output from this tool is a tabular file containing three columns, with
|
|
|
58 the order taken from query order in the original BLAST XML file:
|
|
|
59
|
|
|
60 ====== ====================
|
|
|
61 Column Description
|
|
|
62 ------ --------------------
|
|
|
63 1 ID of query sequence
|
|
|
64 2 GO term
|
|
|
65 3 GO description
|
|
|
66 ====== ====================
|
|
|
67
|
|
|
68 Note that if no GO terms are assigned to a sequence (e.g. if it had no
|
|
|
69 BLAST matches), then it will not be present in the output file.
|
|
|
70
|
|
|
71 This tabular file is called an "Annotation File" in the Blast2GO GUI.
|
|
|
72 If you download the tabular file, and rename it to use the extension
|
|
|
73 ".annot", then it can be opened with the Blast2GO GUI via the "File",
|
|
|
74 "Load Annotation (.annot)" menu (keyboard shortcut ALT+L). You can
|
|
|
75 then run some of the interactive analyses offered in the GUI tool.
|
|
|
76
|
|
|
77
|
|
|
78 **Advanced Settings**
|
|
|
79
|
|
|
80 Blast2GO has a properties setting file which includes which database
|
|
|
81 server to connect to (e.g. the public server in Valencia, Spain, or a
|
|
|
82 local server), as well as more advanced options such as thresholds and
|
|
|
83 evidence code weights. To change these settings, your Galaxy administrator
|
|
|
84 must create a new properties file, and add it to the drop down menu above.
|
|
|
85
|
|
|
86
|
|
|
87 **References**
|
|
|
88
|
|
|
89 If you use this Galaxy tool in work leading to a scientific publication please
|
|
|
90 cite the following papers:
|
|
|
91
|
|
|
92 Peter Cock, Bjoern Gruening, Konrad Paszkiewicz and Leighton Pritchard (2013).
|
|
|
93 Galaxy tools and workflows for sequence analysis with applications
|
|
|
94 in molecular plant pathology. PeerJ 1:e167
|
|
|
95 http://dx.doi.org/10.7717/peerj.167
|
|
|
96
|
|
|
97 S. Götz et al. (2008).
|
|
|
98 High-throughput functional annotation and data mining with the Blast2GO suite.
|
|
|
99 Nucleic Acids Res. 36(10):3420–3435.
|
|
|
100 http://dx.doi.org/10.1093/nar/gkn176
|
|
|
101
|
|
|
102 A. Conesa and S. Götz (2008).
|
|
|
103 Blast2GO: A Comprehensive Suite for Functional Analysis in Plant Genomics.
|
|
|
104 International Journal of Plant Genomics. 619832.
|
|
|
105 http://dx.doi.org/10.1155/2008/619832
|
|
|
106
|
|
|
107 A. Conesa et al. (2005).
|
|
|
108 Blast2GO: A universal tool for annotation, visualization and analysis in functional genomics research.
|
|
|
109 Bioinformatics 21:3674-3676.
|
|
|
110 http://dx.doi.org/10.1093/bioinformatics/bti610
|
|
|
111
|
|
|
112 See also http://www.blast2go.com/
|
|
|
113
|
|
|
114 This wrapper is available to install into other Galaxy Instances via the Galaxy
|
|
|
115 Tool Shed at http://toolshed.g2.bx.psu.edu/view/peterjc/blast2go
|
|
|
116
|
|
|
117 </help>
|
|
|
118 <citations>
|
|
|
119 <citation type="doi">10.7717/peerj.167</citation>
|
|
|
120 <citation type="doi">10.1093/nar/gkn176</citation>
|
|
|
121 <citation type="doi">10.1155/2008/619832</citation>
|
|
|
122 <citation type="doi">10.1093/bioinformatics/bti610</citation>
|
|
|
123 </citations>
|
|
|
124 </tool>
|
