Mercurial > repos > bgruening > infernal

comparison cmsearch.xml @ 0:652f9d550531 draft

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Uploaded
author bgruening
date Tue, 22 Apr 2014 13:56:22 -0400
parents
children 55bb96edfc07
comparison
equal deleted inserted replaced
-1:000000000000 0:652f9d550531
1 <tool id="infernal_cmsearch" name="Search covariance model(s)" version="1.1.0.2">
2 <description>against a sequence database (cmsearch)</description>
3 <parallelism method="multi" split_inputs="seqdb" split_mode="to_size" split_size="100" shared_inputs="" merge_outputs="outfile,multiple_alignment_output"></parallelism>
4 <requirements>
5 <requirement type="package">infernal</requirement>
6 <requirement type="package" version="1.1">infernal</requirement>
7 <requirement type="package" version="8.21">gnu_coreutils</requirement>
8 </requirements>
9 <command>
10 ## a temp file is needed, because the standard tabular output from infernal is not usefull in Galaxy
11 ## it will be converted to a tab delimited file and piped to Galaxy
12 temp_tabular_output=\$(mktemp);
13
14 cmsearch
15 ## Infernal Options
16 --cpu "\${GALAXY_SLOTS:-12}"
17 -o /dev/null
18 --tformat $seqdb.ext ##target format: fasta, embl, genbank, ddbj, stockholm, pfam, a2m, afa, clustal, and phylip
19 $bottomonly
20 $toponly
21 $cyk
22 $notrunc
23 $max
24 $nohmm
25 $mid
26 ##$bitscore_thresholds
27 --tblout \$temp_tabular_output
28 $g
29 #if $A:
30 $A $multiple_alignment_output
31 #end if
32
33 #if str($inclusion_thresholds_opts.inclusion_thresholds_selector) == "--incE":
34 --incE $inclusion_thresholds_opts.incE
35 #elif str($inclusion_thresholds_opts.inclusion_thresholds_selector) == "--incT":
36 --incT $inclusion_thresholds_opts.incT
37 #end if
38
39 #if str($reporting_thresholds_opts.reporting_thresholds_selector) == "-E":
40 -E $reporting_thresholds_opts.E
41 #elif str($reporting_thresholds_opts.reporting_thresholds_selector) == "-T":
42 -T $reporting_thresholds_opts.T
43 #end if
44
45 ## CM file from the history or stored as database on disc
46
47 #if str($cm_opts.cm_opts_selector) == "db":
48 $cm_opts.database.fields.path
49 #else:
50 $cm_opts.cmfile
51 #end if
52
53 ## sequence file
54 $seqdb
55 2>&#38;1
56 ;
57
58 ## 1. replace all lines starting # (comment lines)
59 ## 2. replace the first 18 spaces with tabs, 18th field is a free text field (can contain spaces)
60 sed -e 's/#.*$//' -e '/^$/d' -e 's/ /\t/g' -e 's/\t/ /18g' \$temp_tabular_output > $outfile
61
62 </command>
63 <inputs>
64
65 <param name="seqdb" type="data" format="fasta" label="Sequence database"/>
66
67 <conditional name="cm_opts">
68 <param name="cm_opts_selector" type="select" label="Subject covariance models">
69 <option value="db" selected="True">Locally installed covariance models</option>
70 <option value="histdb">Covariance model from your history</option>
71 </param>
72 <when value="db">
73 <param name="database" type="select" label="Covariance models">
74 <options from_file="infernal.loc">
75 <column name="value" index="0"/>
76 <column name="name" index="1"/>
77 <column name="path" index="2"/>
78 </options>
79 </param>
80 </when>
81 <when value="histdb">
82 <param name="cmfile" type="data" format="cm" label="Covariance models file from the history."/>
83 </when>
84 </conditional>
85
86 <param name="g" truevalue="-g" falsevalue="" checked="False" type="boolean"
87 label="Turn on the glocal alignment algorithm" help="... global with respect to the query model and local with respect to the target database."/>
88
89 <param name="bottomonly" truevalue="--bottomonly" falsevalue="" checked="False" type="boolean"
90 label="Only search the bottom (Crick) strand of target sequences" help="in the sequence database"/>
91 <param name="toponly" truevalue="--toponly" falsevalue="" checked="False" type="boolean"
92 label="Only search the top (Watson) strand of target sequences" help="in the sequence database"/>
93
94 <param name="cyk" truevalue="--cyk" falsevalue="" checked="False" type="boolean"
95 label="Use the CYK algorithm, not Inside, to determine the final score of all hits" help=""/>
96 <param name="--acyk" truevalue="--cyk" falsevalue="" checked="False" type="boolean"
97 label="Use the CYK algorithm to align hits" help="By default, the Durbin/Holmes optimal accuracy algorithm is used, which finds the alignment that maximizes the expected accuracy of all aligned residues."/>
98
99 <param name="notrunc" truevalue="--notrunc" falsevalue="" checked="False" type="boolean"
100 label="Turn off truncated hit detection" help=""/>
101
102 <!-- accelleration pipeline -->
103
104 <param name="max" truevalue="--max" falsevalue="" checked="False" type="boolean"
105 label="Turn off all filters, and run non-banded Inside on every full-length target sequence" help="This
106 increases sensitivity somewhat, at an extremely large cost in speed."/>
107
108 <param name="nohmm" truevalue="--nohmm" falsevalue="" checked="False" type="boolean"
109 label="Turn off all HMM filter stages " help=""/>
110
111 <param name="mid" truevalue="--mid" falsevalue="" checked="False" type="boolean"
112 label="Turn off the HMM SSV and Viterbi filter stages" help=""/>
113
114
115 <!-- Options for model-specific score thresholding -->
116 <!--
117 <param name="bitscore_thresholds" type="select" label="Bit score thresholds" help="Curated CM databases may define specific bit score thresholds for each CM, superseding any thresholding based on statistical significance alone.">
118 <option value="" selected="true">None</option>
119 <option value=" - -cut_ga">GA (gathering) bit scores</option>
120 <option value=" - -cut_nc">NC (noise cutoff) bit score</option>
121 <option value=" - -cut_tc">TC (trusted cutoff) bit score</option>
122 </param>
123 -->
124 <!-- Options for inclusion thresholds -->
125
126
127 <conditional name="inclusion_thresholds_opts">
128 <param name="inclusion_thresholds_selector" type="select" label="Inclusion thresholds"
129 help="Inclusion thresholds are stricter than reporting thresholds. Inclusion thresholds control which hits are considered to be reliable enough to be included in an output alignment or in a possible subsequent search round, or marked as significant (”!”) as opposed to questionable (”?”) in hit output.">
130 <option value="" selected="true">default</option>
131 <option value="--incE">Use E-value</option>
132 <option value="--incT">Use bit score</option>
133 </param>
134 <when value=""/>
135 <when value="--incE">
136 <param name="incE" type="float" value="0.01" size="5" label="Use E-value" help="of &lt;= X as the hit inclusion threshold.">
137 <sanitizer>
138 <valid initial="string.printable">
139 <remove value="&apos;"/>
140 </valid>
141 </sanitizer>
142 </param>
143 </when>
144 <when value="--incT">
145 <param name="incT" type="integer" size="5" value="0" label="Use bit score" help="of >= X as the hit inclusion threshold.">
146 <sanitizer>
147 <valid initial="string.printable">
148 <remove value="&apos;"/>
149 </valid>
150 </sanitizer>
151 </param>
152 </when>
153 </conditional>
154
155 <!-- Options controlling reporting thresholds -->
156
157 <conditional name="reporting_thresholds_opts">
158 <param name="reporting_thresholds_selector" type="select" label="reporting thresholds"
159 help="Reporting thresholds control which hits are reported in output files">
160 <option value="" selected="true">default</option>
161 <option value="-E">Use E-value</option>
162 <option value="-T">Use bit score</option>
163 </param>
164 <when value=""/>
165 <when value="-E">
166 <param name="E" type="float" value="10.0" size="5" label="Use E-value" help="of &lt;= X as the hit reporting threshold. The default is 10.0, meaning that on average, about 10 false positives will be reported per query, so you can see the top of the noise and decide for yourself if it’s really noise.">
167 <sanitizer>
168 <valid initial="string.printable">
169 <remove value="&apos;"/>
170 </valid>
171 </sanitizer>
172 </param>
173 </when>
174 <when value="-T">
175 <param name="T" type="integer" size="5" value="0" label="Use bit score" help="of >= X as the hit reporting threshold.">
176 <sanitizer>
177 <valid initial="string.printable">
178 <remove value="&apos;"/>
179 </valid>
180 </sanitizer>
181 </param>
182 </when>
183 </conditional>
184
185 <param name="A" truevalue="-A" falsevalue="" checked="False" type="boolean"
186 label="Save a multiple alignment of all significant hits" help="... those satisfying inclusion thresholds"/>
187
188 </inputs>
189 <outputs>
190
191 <data format="tabular" name="outfile" label="cmsearch on ${on_string}"/>
192 <data format="tabular" name="multiple_alignment_output" label="cmsearch on ${on_string} (multi alignment)">
193 <filter>A is True</filter>
194 </data>
195
196 </outputs>
197 <help>
198
199
200 **What it does**
201
202 Infernal is used to search sequence databases for homologs of structural RNA sequences, and to make
203 sequence- and structure-based RNA sequence alignments. Infernal needs a profile from a structurally
204 annotated multiple sequence alignment of an RNA family with a position-specific scoring system for substitutions,
205 insertions, and deletions. Positions in the profile that are basepaired in the consensus secondary
206 structure of the alignment are modeled as dependent on one another, allowing Infernal’s scoring system to
207 consider the secondary structure, in addition to the primary sequence, of the family being modeled. Infernal
208 profiles are probabilistic models called “covariance models”, a specialized type of stochastic context-free
209 grammar (SCFG) (Lari and Young, 1990).
210
211 Compared to other alignment and database search tools based only on sequence comparison, Infernal
212 aims to be significantly more accurate and more able to detect remote homologs because it models sequence
213 and structure.
214
215
216 Output format
217 -------------
218
219 (1) target name: The name of the target sequence or profile.
220 (2) accession: The accession of the target sequence or profile, or ’-’ if none.
221 (3) query name: The name of the query sequence or profile.
222 (4) accession: The accession of the query sequence or profile, or ’-’ if none.
223 (5) mdl (model): Which type of model was used to compute the final score. Either ’cm’ or ’hmm’. A CM is used to compute the final hit scores unless the model has zero basepairs or the --hmmonly option is used, in which case a HMM will be used.
224 (6) mdl from (model coord): The start of the alignment of this hit with respect to the profile (CM or HMM), numbered 1..N for a profile of N consensus positions.
225 (7) mdl to (model coord): The end of the alignment of this hit with respect to the profile (CM or HMM), numbered 1..N for a profile of N consensus positions.
226 (8) seq from (ali coord): The start of the alignment of this hit with respect to the sequence, numbered 1..L for a sequence of L residues.
227 (9) seq to (ali coord): The end of the alignment of this hit with respect to the sequence, numbered 1..L for a sequence of L residues.
228 (10) strand: The strand on which the hit occurs on the sequence. ’+’ if the hit is on the top (Watson) strand, ’-’ if the hit is on the bottom (Crick) strand. If on the top strand, the “seq from” value will be less than or equal to the “seq to” value, else it will be greater than or equal to it.
229 (11) trunc: Indicates if this is predicted to be a truncated CM hit or not. This will be “no” if it is a CM hit that is not predicted to be truncated by the end of the sequence, “5’ ” or “3’ ” if the hit is predicted to have one or more 5’ or 3’ residues missing due to a artificial truncation of the sequence, or “5’&amp;3”’ if the hit is predicted to have one or more 5’ residues missing and one or more 3’ residues missing. If the hit is an HMM hit, this will always be ’-’.
230 (12) pass: Indicates what “pass” of the pipeline the hit was detected on. This is probably only useful for testing and debugging. Non-truncated hits are found on the first pass, truncated hits are found on successive passes.
231 (13) gc: Fraction of G and C nucleotides in the hit.
232 (14) bias: The biased-composition correction: the bit score difference contributed by the null3 model for CM hits, or the null2 model for HMM hits. High bias scores may be a red flag for a false positive. It is difficult to correct for all possible ways in which a nonrandom but nonhomologous biological sequences can appear to be similar, such as short-period tandem repeats, so there are cases where the bias correction is not strong enough (creating false positives).
233 (15) score: The score (in bits) for this target/query comparison. It includes the biased-composition cor-rection (the “null3” model for CM hits, or the “null2” model for HMM hits).
234 (16) E-value: The expectation value (statistical significance) of the target. This is a per query E-value; i.e. calculated as the expected number of false positives achieving this comparison’s score for a single query against the search space Z. For cmsearch Z is defined as the total number of nucleotides in the target dataset multiplied by 2 because both strands are searched. For cmscan Z is the total number of nucleotides in the query sequence multiplied by 2 because both strands are searched and multiplied by the number of models in the target database. If you search with multiple queries and if you want to control the overall false positive rate of that search rather than the false positive rate per query, you will want to multiply this per-query E-value by how many queries you’re doing.
235 (17) inc: Indicates whether or not this hit achieves the inclusion threshold: ’!’ if it does, ’?’ if it does not (and rather only achieves the reporting threshold). By default, the inclusion threshold is an E-value of 0.01 and the reporting threshold is an E-value of 10.0, but these can be changed with command line options as described in the manual pages.
236 (18) description of target: The remainder of the line is the target’s description line, as free text.
237
238
239 For further questions please refere to the Infernal Userguide_.
240
241 .. _Userguide: http://selab.janelia.org/software/infernal/Userguide.pdf
242
243
244 How do I cite Infernal?
245 -----------------------
246
247 The recommended citation for using Infernal 1.1 is E. P. Nawrocki and S. R. Eddy, Infernal 1.1: 100-fold faster RNA homology searches , Bioinformatics 29:2933-2935 (2013).
248
249 **Galaxy Wrapper Author**::
250
251 * Bjoern Gruening, University of Freiburg
252
253 </help>
254 </tool>