|
0
|
1 <tool id="bedtools_intersectbed_bam" name="Intersect BAM alignments with intervals in another files" version="0.1.0">
|
|
|
2 <description>
|
|
|
3 </description>
|
|
|
4
|
|
|
5 <requirements>
|
|
|
6 <requirement type="binary">intersectBed</requirement>
|
|
|
7 </requirements>
|
|
|
8
|
|
|
9 <command>
|
|
|
10 intersectBed
|
|
|
11 -abam '$inputA'
|
|
|
12 -b '$inputB'
|
|
|
13 $split
|
|
|
14 $strand
|
|
|
15 #if str($fraction):
|
|
|
16 -f $fraction
|
|
|
17 #end if
|
|
|
18 $reciprocal
|
|
|
19 $invert
|
|
|
20 > '$output'
|
|
|
21 </command>
|
|
|
22
|
|
|
23 <inputs>
|
|
|
24 <param format="bam" name="inputA" type="data" label="Which alignments in this BAM file">
|
|
|
25 <validator type="unspecified_build" />
|
|
|
26 </param>
|
|
|
27 <param format="bed" name="inputB" type="data" label="overlap intervals in this BED file?">
|
|
|
28 <validator type="unspecified_build" />
|
|
|
29 </param>
|
|
|
30 <param name="split" type="boolean" checked="true" truevalue="-split" falsevalue="" label="Treat split/spliced BAM or BED12 entries as distinct BED intervals when computing coverage." help="If set, the coverage will be calculated based the spliced intervals only. For BAM files, this inspects the CIGAR N operation to infer the blocks for computing coverage. For BED12 files, this inspects the BlockCount, BlockStarts, and BlockEnds fields (i.e., columns 10,11,12). If this option is not set, coverage will be calculated based on the interval's START/END coordinates, and would include introns in the case of RNAseq data." />
|
|
|
31
|
|
|
32 <param name="strand" type="select" label="Calculate coverage based on">
|
|
|
33 <option value="">Overlaps on either strand</option>
|
|
|
34 <option value="-s">Only overlaps occurring on the **same** strand.</option>
|
|
|
35 <option value="-S">Only overlaps occurring on the **opposite** strand.</option>
|
|
|
36 </param>
|
|
|
37
|
|
|
38 <param name="fraction" type="text" optional="true" label="Minimum overlap required as a fraction of the BAM alignment" help="Alignments are only retained if the overlap with the an interval in the BED file comprises at least this fraction of the BAM alignment's length. For example, to require that the overlap affects 50% of the BAM alignment, use 0.50"/>
|
|
|
39
|
|
|
40 <param name="reciprocal" type="boolean" checked="false" truevalue="-r" falsevalue="" label="Require reciprocal overlap." help="If set, the overlap between the BAM alignment and the BED interval must affect the above fraction of both the alignment and the BED interval." />
|
|
|
41
|
|
|
42 <param name="invert" type="boolean" checked="false" truevalue="-v" falsevalue="" label="Report only those alignments that **do not** overlap the BED file."/>
|
|
|
43
|
|
|
44 </inputs>
|
|
|
45
|
|
|
46 <outputs>
|
|
|
47 <data format="bam" name="output" metadata_source="inputA" label="Intersection of ${inputA.name} and ${inputB.name}"/>
|
|
|
48 </outputs>
|
|
|
49
|
|
|
50 <help>
|
|
|
51
|
|
|
52 **What it does**
|
|
|
53
|
|
|
54 This tool creates a new BAM alignment file based on alignments that overlap (or optionally, those that do not overlap) intervals in another BED file. Example usage would be to cull a BAM file from an exome capture experiment to include on the "on-target" alignments.
|
|
|
55
|
|
|
56 .. class:: infomark
|
|
|
57
|
|
|
58 Note that each BAM alignment is treated individually. Therefore, if one end of a paired-end alignment overlaps an interval in the BED file, yet the other end does not, the output file will only include the overlapping end.
|
|
|
59
|
|
|
60 .. class:: infomark
|
|
|
61
|
|
|
62 Note that a BAM alignment will be sent to the output file **once** even if it overlaps more than one interval in the BED file.
|
|
|
63
|
|
|
64 .. class:: warningmark
|
|
|
65
|
|
|
66 This tool requires that `bedtools`__ has been installed on your system.
|
|
|
67
|
|
|
68 ------
|
|
|
69
|
|
|
70 This tool is part of the `bedtools package`__ from the `Quinlan laboratory`__. If you use this tool, please cite `Quinlan AR, and Hall I.M. BEDTools: A flexible framework for comparing genomic features. Bioinformatics, 2010, 26, 6.`__
|
|
|
71
|
|
|
72 .. __: http://code.google.com/p/bedtools/
|
|
|
73 .. __: http://code.google.com/p/bedtools/
|
|
|
74 .. __: http://cphg.virginia.edu/quinlan/
|
|
|
75 .. __: http://bioinformatics.oxfordjournals.org/content/26/6/841.short
|
|
|
76
|
|
|
77 </help>
|
|
|
78 </tool>
|
