# HG changeset patch # User iuc # Date 1444771234 14400 # Node ID 5efc48568d8dcdde1462087f1d9af8cffd78b254 # Parent a2d4c30ba2f9c07ba9e55e44d085c2f9082d566e planemo upload for repository https://github.com/galaxyproject/tools-iuc/tree/master/tools/bedtools commit e5a5ad091c621348dc6ce2df861475ebc54a380e diff -r a2d4c30ba2f9 -r 5efc48568d8d annotateBed.xml --- a/annotateBed.xml Sun Jun 21 22:49:46 2015 -0400 +++ b/annotateBed.xml Tue Oct 13 17:20:34 2015 -0400 @@ -1,4 +1,4 @@ - + annotate coverage of features from multiple files macros.xml @@ -7,6 +7,7 @@ macros.xml - + + samtools + "${output}" ]]> - - - + + + + label="Use alignment's edit-distance for BED score" help="(-ed)" /> @@ -56,16 +65,16 @@ .. class:: infomark -The "Report spliced BAM alignment..." option breaks BAM alignments with the "N" (splice) operator into distinct BED entries. For example, using this option on a CIGAR such as 50M1000N50M would, by default, produce a single BED record that spans 1100bp. However, using this option, it would create two separate BED records that are each 50bp in size and are separated by 1000bp (the size of the N operation). This is important for RNA-seq and structural variation experiments. +The "Report spliced BAM alignment..." option breaks BAM alignments with the "N" (splice) operator into distinct BED entries. +For example, using this option on a CIGAR such as 50M1000N50M would, by default, produce a single BED record that spans 1100bp. +However, using this option, it would create two separate BED records that are each 50bp in size and are separated by 1000bp (the size of the N operation). +This is important for RNA-seq and structural variation experiments. .. class:: warningmark -If using a custom BAM alignment TAG as the BED score, note that this must be a numeric tag (e.g., type "i" as in NM:i:0). +If using a custom BAM alignment TAG as the BED score, note that this must be a numeric tag (e.g., type "i" as in NM:i:0). -.. class:: warningmark - -If creating a BEDPE output (see output formatting options), the BAM file should be sorted by query name. @REFERENCES@ ]]> diff -r a2d4c30ba2f9 -r 5efc48568d8d bamToFastq.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/bamToFastq.xml Tue Oct 13 17:20:34 2015 -0400 @@ -0,0 +1,39 @@ + + + + macros.xml + + + + + bedtools bamtofastq + $tags + -i '$input' + -fq '$output' + #if $fq2: + -fq2 '$output2' + #end if + + + + + + + + + + fq2 is True + + + + +**What it does** + +bedtools bamtofastq is a conversion utility for extracting FASTQ records from sequence alignments in BAM format. + +@REFERENCES@ + + + + diff -r a2d4c30ba2f9 -r 5efc48568d8d flankBed.xml --- a/flankBed.xml Sun Jun 21 22:49:46 2015 -0400 +++ b/flankBed.xml Tue Oct 13 17:20:34 2015 -0400 @@ -27,10 +27,10 @@ + help="E.g. if used on a 1000bp feature, -l 0.50, will add 500 bp “upstream”. (-pct)" /> + help="For example. if used, -l 500 for a negative-stranded feature, it will add 500 bp to the end coordinate. (-s)" /> diff -r a2d4c30ba2f9 -r 5efc48568d8d intersectBed.xml --- a/intersectBed.xml Sun Jun 21 22:49:46 2015 -0400 +++ b/intersectBed.xml Tue Oct 13 17:20:34 2015 -0400 @@ -28,6 +28,7 @@ $once $header $modes + $count > "${output}" ]]> diff -r a2d4c30ba2f9 -r 5efc48568d8d test-data/annotateBed_result.bed --- a/test-data/annotateBed_result.bed Sun Jun 21 22:49:46 2015 -0400 +++ b/test-data/annotateBed_result.bed Tue Oct 13 17:20:34 2015 -0400 @@ -1,3 +1,4 @@ +# annotateBed2.bed annotateBed3.bed annotateBed4.bed chr1 100 200 nasty 1 - 0.500000 1.000000 0.300000 chr2 500 1000 ugly 2 + 0.000000 0.600000 1.000000 chr3 1000 5000 big 3 - 1.000000 0.250000 0.000000 diff -r a2d4c30ba2f9 -r 5efc48568d8d tool_dependencies.xml --- a/tool_dependencies.xml Sun Jun 21 22:49:46 2015 -0400 +++ b/tool_dependencies.xml Tue Oct 13 17:20:34 2015 -0400 @@ -1,6 +1,9 @@ - - + + + + +