Mercurial > repos > cpt > cpt_gbk_renumber
comparison cpt_renumber_gbk/renumber.xml @ 0:8cac332dbc77 draft default tip
Uploaded
| author | cpt |
|---|---|
| date | Fri, 17 Jun 2022 13:13:47 +0000 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| -1:000000000000 | 0:8cac332dbc77 |
|---|---|
| 1 <?xml version="1.0"?> | |
| 2 <tool id="edu.tamu.cpt.genbank.RelabelTags" name="Renumber GenBank Genes" version="0.4" profile="16.04"> | |
| 3 <description>relabels/renumbers GenBank tags according to rules</description> | |
| 4 <macros> | |
| 5 <import>macros.xml</import> | |
| 6 <import>cpt-macros.xml</import> | |
| 7 </macros> | |
| 8 <expand macro="requirements"/> | |
| 9 <command detect_errors="aggressive"><![CDATA[ | |
| 10 python $__tool_directory__/renumber.py | |
| 11 $file | |
| 12 --tag_to_update "${tag_to_update}" | |
| 13 --string_prefix "${string_prefix}" | |
| 14 --leading_zeros "${leading_zeros}" | |
| 15 $forceMatch | |
| 16 --change_table $change_table | |
| 17 | |
| 18 > $output | |
| 19 | |
| 20 ]]></command> | |
| 21 <inputs> | |
| 22 <param label="GenBank file" name="file" type="data" format="genbank" /> | |
| 23 <param help="Which tag is used to store gene numbers" label="Tag to update" | |
| 24 name="tag_to_update" type="text" value="locus_tag"/> | |
| 25 <param help="A string to use as a prefix for the numbering. Will be used as XXXXXXNNN where XXXXXX is the string and NNN is a numerical identifier. Using "display_id" has special meaning, it will use the genome's name/accession number" | |
| 26 label="String prefix" name="string_prefix" type="text" value="display_id"/> | |
| 27 <param label="Number of leading zeros/padding" name="leading_zeros" | |
| 28 type="integer" value="3"/> | |
| 29 <param name="forceMatch" label="Force Updated Tags to initially match in addition to location checks. " help="If tag is not present, only location and type checks will be used to infer renumber" type="boolean" truevalue="--forceTagMatch" falsevalue="" checked="True" /> | |
| 30 </inputs> | |
| 31 <outputs> | |
| 32 <data format="genbank" name="output"> | |
| 33 </data> | |
| 34 <data format="tabular" name="change_table"> | |
| 35 </data> | |
| 36 </outputs> | |
| 37 <tests> | |
| 38 <test> | |
| 39 <param name="file" value="MS105.genbank" /> | |
| 40 <param name="leading_zeros" value="10" /> | |
| 41 <param name="forceMatch" value="" /> | |
| 42 <param name="string_prefix" value="MS105_" /> | |
| 43 <output name="genbank" value="renumbered.gbk" /> | |
| 44 <output name="change_table" value="renumbered.tsv" /> | |
| 45 </test> | |
| 46 </tests> | |
| 47 <help> | |
| 48 Gene Renumbering Tool | |
| 49 ===================== | |
| 50 | |
| 51 Renumber genes in a genome. | |
| 52 | |
| 53 Subfeatures, such as CDS or intron, will attempt to be grouped with their associated gene, based on location. CDSs and RBSs must share either a start or an end boundary with their parent gene, and also fall entirely within the boundary of said gene. All other features only need to fall within the boundary of a gene. | |
| 54 | |
| 55 If the tag check is enabled, then whatever qualifier is selected for updating (such as locus_tag), the subfeatures must also have the same value as any canidate parent gene had for that qualifier. This is useful for subfeatures such as introns, which may be inside more than one gene and could potentially get renumbered to the wrong parent in a location-only check. However, if your dataset does not already have a consistent naming convention, other valid heirarchies could get dropped. The log file will list what features got dropped based on tag checks, so be sure to use that to verify all data made it through. | |
| 56 </help> | |
| 57 <expand macro="citations-2020" /> | |
| 58 </tool> |