Mercurial > repos > iuc > bedops_sortbed

comparison sort-bed.xml @ 0:e0ca90448989 draft

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
planemo upload for repository https://bedops.readthedocs.io/ commit e64b305e1ef7a6aa06a654f29701d7b43337c0ca
author iuc
date Tue, 08 Aug 2023 10:28:02 +0000
parents
children 4de6dea7d80f
comparison
equal deleted inserted replaced
-1:000000000000 0:e0ca90448989
1 <tool id="bedops-sort-bed" name="bedops sort-bed" version="@TOOL_VERSION@" profile="22.01">
2 <macros>
3 <token name="@TOOL_VERSION@">2.4.41</token>
4 </macros>
5 <requirements>
6 <requirement type="package" version="@TOOL_VERSION@">bedops</requirement>
7 </requirements>
8 <command><![CDATA[
9 sort-bed
10 --max-mem "\${GALAXY_MEMORY_MB:-1024}M"
11 --tmpdir "\${_GALAXY_JOB_TMP_DIR:-.}"
12 $unique
13 $duplicates
14 #for file in $inputs:
15 '$file'
16 #end for
17 > '$output'
18 ]]></command>
19 <inputs>
20 <param name="inputs" type="data" format="bed" multiple="true"/>
21 <param argument="--unique" type="boolean" truevalue="--unique" falsevalue="" label="Output only unique elements?"/>
22 <param argument="--duplicates" type="boolean" truevalue="--duplicates" falsevalue="" label="Output only duplicate elements?"/>
23 </inputs>
24 <outputs>
25 <data name="output" format_source="inputs" label="$tool.name: sorted output"/>
26 </outputs>
27 <tests>
28 <test>
29 <param name="inputs" value="unsorted.bed" ftype="bed"/>
30 <output name="output" value="sorted_simpled.bed"/>
31 </test>
32 <test>
33 <param name="inputs" value="unsorted.bed" ftype="bed"/>
34 <param name="unique" value="true"/>
35 <output name="output" value="sorted_unique.bed"/>
36 </test>
37 <test>
38 <param name="inputs" value="unsorted.bed" ftype="bed"/>
39 <param name="duplicates" value="true"/>
40 <output name="output" value="sorted_duplicates.bed"/>
41 </test>
42 </tests>
43 <help><![CDATA[
44 What this tool does
45 ===================
46
47 The sort-bed utility sorts BED files of any size, even larger than system memory. BED files that are in lexicographic-chromosome order allow BEDOPS utilities to work efficiently with data from any species without software modifications. Further, sorted files can be traversed very quickly.
48
49 Sorted BED order is defined first by lexicographic chromosome order, then ascending integer start coordinate order, and finally by ascending integer end coordinate order. To make the sort order unambiguous, a lexicographical sort is applied on fourth and subsequent columns, where present in the input BED dataset.
50
51
52 Input
53 =====
54
55 The sort-bed utility requires one or more three-column BED file(s). Support for common headers (such as UCSC BED track headers) is included, although headers will be stripped from the output.
56
57
58 Output
59 ======
60
61 Sort order is defined by a lexicographical sort on chromosome name, a numerical sort on start coordinates, a numerical sort on stop coordinates where there are start matches, and finally a lexicographical sort on the remainder of the BED element (if additional columns are present). Additional options may be specified to print only unique or duplicate elements.
62 ]]></help>
63 <citations>
64 <citation type="doi">https://doi.org/10.1093/bioinformatics/bts277</citation>
65 </citations>
66 </tool>