comparison oases_optimiser.xml @ 0:53e887dda799 default tip

Migrated tool version 1.0.0 from old tool shed archive to new tool shed repository
author konradpaszkiewicz
date Tue, 07 Jun 2011 17:41:37 -0400
parents
children
comparison
equal deleted inserted replaced
-1:000000000000 0:53e887dda799
1 <tool id="oasesoptimiser" name="oasesoptimiser" version="1.0.0">
2 <description>Auto optimise a denovo RNA-seq Oases/Velvet assembly</description>
3 <command interpreter="python">
4 oases_optimiser.py '$start_hash_length' '$end_hash_length'
5 '#for $i in $inputs
6 ${i.file_format}
7 ${i.read_type}
8 ${i.input}
9 #end for
10 '
11 '$contigs'
12 '$LastGraph'
13 '$velvet_asm'
14 '$unused_reads_fasta'
15 '$stats'
16 '$othervelvetgoptions'
17 '$otheroasesoptions'
18 '$transcripts'
19 '$splicingevents'
20 '$contigordering'
21 '$contigs.extra_files_path'
22 </command>
23
24 <inputs>
25 <param label="Start Hash Length" name="start_hash_length" type="select" help="k-mer length in base pairs of the words being hashed. Shorter hash lengths (i.e. less than 31) may cause out-of-memory problems.">
26
27 <option value="23">23</option>
28 <option value="25">25</option>
29 <option value="27">27</option>
30 <option value="29">29</option>
31 <option value="31" selected="yes">31</option>
32 <option value="33">33</option>
33 <option value="35">35</option>
34 <option value="37">37</option>
35 <option value="39">39</option>
36 <option value="41">41</option>
37
38 </param>
39 <param label="End Hash Length" name="end_hash_length" type="select" help="k-mer length in base pairs of the words being hashed.">
40 <option value="43">43</option>
41 <option value="45">45</option>
42 <option value="47">47</option>
43 <option value="49">49</option>
44 <option value="51">51</option>
45 <option value="53">53</option>
46 <option value="55">55</option>
47 <option value="57">57</option>
48 <option value="59">59</option>
49 <option value="61">61</option>
50 <option value="63">63</option>
51 <option value="65">65</option>
52 <option value="67">67</option>
53 <option value="69" selected="yes">69</option>
54
55 </param>
56
57
58 <param label="Advanced velvetg options" name="othervelvetgoptions" title="Advanced velvetg options" help="Other Velvetg options - see below for details" type="text" size="30">
59
60 </param>
61
62
63 <param label="Advanced Oases options" default="-ins_length 50 -ins_length_sd 100" name="otheroasesoptions" title="Advanced oases options" help="Other oases options - see below for details" type="text" size="30">
64
65 </param>
66
67 <param name="strand_specific" type="boolean" checked="false" truevalue="-strand_specific" falsevalue="" label="Use strand specific transcriptome sequencing" help="If you are using a strand specific transcriptome sequencing protocol, you may wish to use this option for better results."/>
68 <repeat name="inputs" title="Input Files">
69 <param label="file format" name="file_format" type="select">
70 <option value="-fasta" selected="yes">fasta</option>
71 <option value="-fastq">fastq</option>
72 <option value="-eland">eland</option>
73 <option value="-gerald">gerald</option>
74 </param>
75 <param label="read type" name="read_type" type="select">
76 <option value="-short" selected="yes">short reads</option>
77 <option value="-shortPaired">shortPaired reads</option>
78 <option value="-short2">short2 reads</option>
79 <option value="-shortPaired2">shortPaired2 reads</option>
80 <option value="-long">long reads (reads >200bp e.g. 454 reads)</option>
81 <option value="-longPaired">longPaired reads</option>
82 </param>
83
84
85 <param name="input" type="data" format="fasta,fastq,eland,gerald" label="Dataset"/>
86 </repeat>
87 </inputs>
88
89 <outputs>
90
91 <data format="fasta" name="transcripts" label="${tool.name} on ${on_string}: Denovo assembled transcripts"/>
92 <data format="tabular" name="splicingevents" label="${tool.name} on ${on_string}: Splicing events in assembled transcripts"/>
93 <data format="tabular" name="contigordering" label="${tool.name} on ${on_string}: Contig ordering in assembled transcripts"/>
94 <data format="fasta" name="contigs" label="${tool.name} on ${on_string}: Denovo assembled contigs"/>
95
96 <data format="fasta" name="unused_reads_fasta" label="${tool.name} on ${on_string}: Unused Reads">
97 <!-- <filter>unused_reads['generate_unused'] == "yes"</filter>-->
98 </data>
99 <data format="tabular" name="stats" label="${tool.name} on ${on_string}: Stats"/>
100 <data format="afg" name="velvet_asm" label="${tool.name} on ${on_string}: AMOS.afg">
101 <!-- <filter>generate_amos['afg'] == "yes"</filter> -->
102 </data>
103
104 <data format="txt" name="LastGraph" label="${tool.name} on ${on_string}: LastGraph">
105 <!-- <filter>last_graph['generate_graph'] == "yes"</filter> -->
106 </data>
107
108
109 </outputs>
110 <requirements>
111 <requirement type="package">velvet</requirement>
112 <requirement type="package">oases</requirement>
113
114 </requirements>
115
116 <help>
117 **Oases Optimiser Overview**
118
119 Oases_ is a de novo transcriptome assembler specially designed to work with short reads. It is an extension of Velvet developed by Daniel Zerbino and Ewan Birney at the European Bioinformatics Institute (EMBL-EBI), near Cambridge, in the United Kingdom.
120
121 Provide all the information about insert lengths and their standard deviation as
122 possible (identical to Velvet). In the advanced oases options you should set the -ins_length flag when using paired-end reads (e.g. -ins_length 200 -ins_length_sd 100). If you do not do this, then paired-end information will not be used by Oases!
123
124 ----------------------------------------------------------------------------------
125
126 Oases produces a number of output files, which correspond to the different algorithms
127 being run succesively on the data. In the above example, you would find:
128
129 transcripts.fa
130 A FASTA file containing the transcripts imputed directly from trivial
131 clusters of contigs (loci with less than two transcripts and Confidence Values = 1)
132 and the highly expressed transcripts imputed by dynamic
133 programming (loci with more than 2 transcripts and Confidence Values less than 1).
134
135 splicing_events.txt
136 A hybrid file which describes the contigs contained in each locus in FASTA
137 format, interlaced with one line descriptions of splicing events using the
138 AStalavista nomenclature*.
139
140 Read the Oases `documentation`__ for details on using the Oases Assembler.
141
142 .. _Velvet: http://www.ebi.ac.uk/~zerbino/oases/
143
144 .. __: http://www.ebi.ac.uk/~zerbino/oases/Manual.txt
145
146 ------
147
148 **Other outputs (as per Velvet)**
149
150
151 **Contigs**
152
153 The *contigs.fa* file.
154 This fasta file contains the sequences of the contigs longer than 2k, where k is the word-length used in velveth. If you have specified a min contig lgth threshold, then the contigs shorter than that value are omitted.
155 Note that the length and coverage information provided in the header of each contig should therefore be understood in k-mers and in k-mer coverage (cf. 5.1) respectively.
156 The N's in the sequence correspond to gaps between scaffolded contigs. The number of N's corresponds to the estimated length of the gap. For reasons of compatibility with the archives, any gap shorter than 10bp is represented by a sequence of 10 N's.
157
158 **Stats**
159
160 The *stats.txt* file.
161 This file is a simple tabbed-delimited description of the nodes. The column names are pretty much self-explanatory. Note however that node lengths are given in k-mers. To obtain the length in nucleotides of each node you simply need to add k - 1, where k is the word-length used in velveth.
162 The in and out columns correspond to the number of arcs on the 5' and 3' ends of the contig respectively.
163 The coverages in columns short1 cov, short1 Ocov, short2 cov, and short2 Ocov are provided in k-mer coverage (5.1).
164 Also, the difference between # cov and # Ocov is the way these values are computed. In the first count, slightly divergent sequences are added to the coverage tally. However, in the second, stricter count, only the sequences which map perfectly onto the consensus sequence are taken into account.
165
166 **LastGraph**
167
168 The *LastGraph* file.
169 This file describes in its entirety the graph produced by Velvet.
170
171 **AMOS.afg**
172 The *velvet_asm.afg* file.
173 This file is mainly designed to be read by the open-source AMOS genome assembly package. Nonetheless, a number of programs are available to transform this kind of file into other assembly file formats (namely ACE, TIGR, Arachne and Celera). See http://amos.sourceforge.net/ for more information.
174 The file describes all the contigs contained in the contigs.fa file (cf 4.2.1).
175
176 **Advanced options**
177 -ins_length integer : expected distance between two paired-end reads in the first short-read dataset (default: no read pairing)
178 -ins_length2 integer : expected distance between two paired-end reads in the second short-read dataset (default: no read pairing)
179 -ins_length_long integer : expected distance between two long paired-end reads (default: no read pairing)
180 -ins_length*_sd integer : est. standard deviation of respective dataset (default: 10% of corresponding length)
181 -scaffolding yes|no : scaffolding of contigs used paired end information (default: on)
182 -max_branch_length integer : maximum length in base pair of bubble (default: 100)
183 -max_divergence floating-point : maximum divergence rate between two branches in a bubble (default: 0.2)
184 -max_gap_count integer : maximum number of gaps allowed in the alignment of the two branches of a bubble (default: 3)
185 -min_pair_count integer : minimum number of paired end connections to justify the scaffolding of two long contigs (default: 10)
186 -max_coverage floating point : removal of high coverage nodes AFTER tour bus (default: no removal)
187 -long_mult_cutoff int : minimum number of long reads required to merge contigs (default: 2)
188 -min_trans_length
189 simple threshold on output transcript length
190 -cov_cutoff
191 minimum number of times a k-mer has to be observed to be used in the
192 assembly (just like in Velvet) [default=3]
193 -min_pair_cov
194 minimum number of times two contigs must be connected by reads or read pairs to be clustered together [default=4]
195 -paired_cutoff
196 minimum ratio between the numbers of observed and expected connecting
197 read pairs between two contigs [default=0.1]
198
199
200
201 **Hash Length**
202
203 The hash length, also known as k-mer length, corresponds to the length, in base pairs, of the words being hashed.
204
205 The hash length is the length of the k-mers being entered in the hash table. Firstly, you must observe three technical constraints::
206
207 # it must be an odd number, to avoid palindromes. If you put in an even number, Velvet will just decrement it and proceed.
208 # it must be below or equal to MAXKMERHASH length (cf. 2.3.3, by default 31bp), because it is stored on 64 bits
209 # it must be strictly inferior to read length, otherwise you simply will not observe any overlaps between reads, for obvious reasons.
210
211 Now you still have quite a lot of possibilities. As is often the case, it's a trade- off between specificity and sensitivity. Longer kmers bring you more specificity (i.e. less spurious overlaps) but lowers coverage (cf. below). . . so there's a sweet spot to be found with time and experience.
212 We like to think in terms of "k-mer coverage", i.e. how many times has a k-mer been seen among the reads. The relation between k-mer coverage Ck and standard (nucleotide-wise) coverage C is Ck = C # (L - k + 1)/L where k is your hash length, and L you read length.
213 Experience shows that this kmer coverage should be above 10 to start getting decent results. If Ck is above 20, you might be "wasting" coverage. Experience also shows that empirical tests with different values for k are not that costly to run! VelvetOptimiser automates these tests for you.
214
215
216 **Velvetg options**
217
218
219
220 **Input Files**
221
222 Velvet works mainly with fasta and fastq formats. For paired-end reads, the assumption is that each read is next to its mate
223 read. In other words, if the reads are indexed from 0, then reads 0 and 1 are paired, 2 and 3, 4 and 5, etc.
224
225 Supported file formats are::
226
227 fasta
228 fastq
229 eland
230 gerald
231
232 Read categories are::
233
234 short (default)
235 shortPaired
236 short2 (same as short, but for a separate insert-size library - i.e. if you have two libraries of different lengths)
237 shortPaired2 (see above)
238 long (for Sanger, 454 or even reference sequences)
239 longPaired
240
241 </help>
242 </tool>