|
23
|
1 <tool id="variant_calling" name="Variant Calling" version="0.1.7.3">
|
|
0
|
2 <description>From a reference and aligned reads generate a BCF file with position-specific variant likelihoods and coverage information</description>
|
|
2
|
3 <macros>
|
|
|
4 <import>toolshed_macros.xml</import>
|
|
|
5 </macros>
|
|
23
|
6 <expand macro="requirements" />
|
|
21
|
7 <version_command>python3 -m MiModD version -q</version_command>
|
|
0
|
8 <command>
|
|
21
|
9 python3 -m MiModD varcall
|
|
0
|
10
|
|
|
11 "$ref_genome"
|
|
|
12 #for $l in $list_input
|
|
|
13 "${l.inputfile}"
|
|
|
14 #end for
|
|
|
15 --ofile "$output_vcf"
|
|
|
16 --depth "$depth"
|
|
|
17 $group_by_id
|
|
|
18 $no_md5_check
|
|
|
19 --verbose
|
|
|
20 --quiet
|
|
|
21 </command>
|
|
|
22
|
|
|
23 <inputs>
|
|
23
|
24 <param format="fasta" label="reference genome" name="ref_genome" type="data" />
|
|
|
25 <repeat default="1" min="1" name="list_input" title="Aligned reads input source">
|
|
|
26 <param format="bam" label="input file" name="inputfile" type="data" />
|
|
0
|
27 </repeat>
|
|
23
|
28 <param checked="false" falsevalue="" help="If selected, this option ensures that only the read group id (but not the sample name) is considered in grouping reads in the input file(s). If turned off, read groups with identical sample names are automatically pooled and analyzed together even if they come from different NGS runs." label="group reads based on read group id only" name="group_by_id" truevalue="-i" type="boolean" />
|
|
|
29 <param checked="false" falsevalue="" help="leave turned on to avoid accidental variant calling against a wrong reference genome version (see the tool help below)." label="turn off md5 sum verification" name="no_md5_check" truevalue="-x" type="boolean" />
|
|
|
30 <param help="to avoid excessive use of memory" label="maximum per-BAM depth (default: 250)" name="depth" type="integer" value="250" />
|
|
0
|
31 </inputs>
|
|
|
32
|
|
|
33 <outputs>
|
|
23
|
34 <data format="bcf" label="Variant Calls from MiModd Variant Calling on ${on_string}" name="output_vcf" />
|
|
0
|
35 </outputs>
|
|
|
36
|
|
|
37 <help>
|
|
|
38 .. class:: infomark
|
|
|
39
|
|
|
40 **What it does**
|
|
|
41
|
|
|
42 The tool transforms the read-centered information of its aligned reads input files into position-centered information.
|
|
|
43
|
|
|
44 **It produces a BCF file that serves as the basis for all further variant analyses with MiModD**.
|
|
|
45
|
|
|
46 **Notes:**
|
|
|
47
|
|
|
48 By default, the tool will check whether the input BAM file(s) provide(s) MD5 checksums for the reference genome sequences used during read alignment (the *SNAP Read Alignment* tool stores these in the BAM file header). If it finds MD5 sums for all sequences, it will compare them to the actual checksums of the sequences in the specified reference genome and
|
|
|
49 check that every sequence mentioned in any BAM input file has a counterpart with matching MD5 sum in the reference genome and abort with an error message if that is not the case. If it finds sequences with matching checksum, but different names in the reference genome, it will use the name from the reference genome file in its output.
|
|
|
50
|
|
|
51 This behavior has two benefits:
|
|
|
52
|
|
|
53 1) It protects from accidental variant calling against a wrong reference genome (i.e., a different one than that used during the alignment step), which would result in wrong calls. This is the primary reason why we recommend to leave the check activated
|
|
|
54
|
|
|
55 2) It provides an opportunity to change sequence names between aligned reads files and variant call files by providing a reference genome file with altered sequence names (but identical sequence data).
|
|
|
56
|
|
|
57 Since there may be rare cases where you *really* want to align against a reference genome with different checksums (e.g., you may have edited the reference sequence based on the alignment results), the check can be turned off, but only do this if you know exactly why.
|
|
|
58
|
|
|
59 -----------
|
|
|
60
|
|
|
61 Internally, the tool uses samtools mpileup combined with bcftools to do all per-nucleotide calculations.
|
|
|
62
|
|
|
63 It exposes just a single configuration parameter of these tools - the *maximum per-BAM depth*. Through this parameter, the maximum number of reads considered for variant calling at any site can be controlled. Its default value of 250 is taken from *samtools mpileup* and usually suitable. Consider, however, that this gives the maximum read number per input file, so if you have a large number of samples in one input file, it could become necessary to increase the value to get sufficient reads considered per sample.
|
|
|
64
|
|
|
65 </help>
|
|
23
|
66 </tool> |
