Mercurial > repos > wolma > mimodd
annotate deletion_predictor.xml @ 17:b658c34ee3fd draft
Uploaded
| author | wolma |
|---|---|
| date | Tue, 26 Apr 2016 07:03:26 -0400 |
| parents | 93db2f9bca12 |
| children | c46406466625 |
| rev | line source |
|---|---|
|
9
93db2f9bca12
upgrade to v0.1.7.2
Wolfgang Maier wolfgang.maier@biologie.uni-freiburg.de
parents:
8
diff
changeset
|
1 <tool id="deletion_prediction" name="Deletion Prediction for paired-end data" version="0.1.7.2"> |
| 0 | 2 <description>Predicts deletions in one or more aligned read samples based on coverage of the reference genome and on insert sizes</description> |
| 2 | 3 <macros> |
| 4 <import>toolshed_macros.xml</import> | |
| 5 </macros> | |
| 6 <expand macro="requirements"/> | |
| 0 | 7 <version_command>mimodd version -q</version_command> |
| 8 <command> | |
| 9 mimodd delcall | |
| 10 #for $l in $list_input | |
| 11 "${l.bamfile}" | |
| 12 #end for | |
| 13 "$covfile" -o "$outputfile" | |
| 14 --max-cov "$max_cov" --min-size "$min_size" $include_uncovered $group_by_id --verbose | |
| 15 </command> | |
| 16 | |
| 17 <inputs> | |
| 18 <repeat name="list_input" title="Aligned reads input source" default="1" min="1"> | |
| 19 <param name="bamfile" type="data" format="bam" label="input BAM file" /> | |
| 20 </repeat> | |
| 21 <param name="covfile" type="data" format="bcf" label="BCF variant call file to extract coverage from" help="Use the Variant Calling tool to generate this file."/> | |
| 4 | 22 <param name="group_by_id" type="boolean" label="group reads based on read group id only" truevalue="-i" falsevalue="" checked="false" help="If selected, reads from different read groups will be treated strictly separate. If turned off, read groups with identical sample names are used together for identifying uncovered regions, but are still treated separately for the prediction of deletions." /> |
| 23 <param name="include_uncovered" type="boolean" label="include low-coverage regions" truevalue="-u" falsevalue="" checked="false" help="If selected, regions that fulfill the coverage criteria below, but are not statistically significant deletions, will be included in the output." /> | |
| 0 | 24 <param name="max_cov" type="integer" value="0" label="maximal coverage allowed inside a low-coverage region (default: 0)" help="The maximal coverage at a site allowed to consider it as part of a low-coverage region" /> |
| 25 <param name="min_size" type="integer" value="100" label="minimal deletion size (default: 100)" help="A low-coverage region must consist of at least this number of consecutive bases below the maximal coverage to consider it in further analyses."/> | |
| 26 </inputs> | |
| 27 | |
| 28 <outputs> | |
| 29 <data name="outputfile" format="gff" /> | |
| 30 </outputs> | |
| 31 | |
| 32 <help> | |
| 33 .. class:: infomark | |
| 34 | |
| 35 **What it does** | |
| 36 | |
| 37 The tool predicts deletions from paired-end data in a two-step process: | |
| 38 | |
| 39 1) It finds regions of low-coverage, i.e., candidate regions for deletions, by scanning a BCF file produced by the *Variant Calling* tool. | |
| 40 | |
| 41 The *maximal coverage allowed inside a low-coverage region* and the *minimal deletion size* parameters are used at this step to define what is considered a low-coverage region. | |
| 42 | |
| 43 .. class:: warningmark | |
| 44 | |
| 45 The tool treats genome positions missing from the BCF input as zero coverage, so it is safe to use ONLY with BCF files produced by the *Variant Calling* tool or through other commands that keep the information for all sites. | |
| 46 | |
| 47 2) It assesses every low-coverage region statistically for evidence of it being a real deletion. **This step requires paired-end data** since it relies on shifts in the distribution of read pair insert sizes around real deletions. | |
| 48 | |
| 49 By default, the tool only reports Deletions, i.e., the subset of low-coverage regions that pass the statistical test. | |
| 50 If *include low-coverage regions* is selected, regions that failed the test will also be reported. | |
| 51 | |
| 52 With *group reads based on read group id only* selected, as it is by default, grouping of reads into samples is done strictly based on their read group IDs. | |
| 53 With the option deselected, grouping is done based on sample names in the first step of the analysis, i.e. the reads of all samples with a shared sample name are used to identify low-coverage regions. | |
| 54 In the second step, however, reads will be regrouped by their read group IDs again, i.e. the statistical assessment for real deletions is always done on a per read group basis. | |
| 55 | |
| 56 **TIP:** | |
| 57 Deselecting *group reads based on read group id only* can be useful, for example, if you have both paired-end and single-end sequencing data for the same sample. | |
| 58 | |
| 59 In this case, the two sets of reads will usually share a common sample name, but differ in their read groups. | |
| 60 With grouping based on sample names, the single-end data can be used together with the paired-end data to identify low-coverage regions, thus increasing overall coverage and reliability of this step. | |
| 61 Still, the assessment of deletions will use only the paired-end data (auto-detecting that the single-end reads do not provide insert size information). | |
| 62 | |
| 63 </help> | |
| 64 | |
| 65 </tool> |