Mercurial > repos > devteam > t2ps
annotate t2ps_wrapper.xml @ 2:d89ca6d3c4cd draft default tip
planemo upload commit 33927a87ba2eee9bf0ecdd376a66241b17b3d734
| author | devteam |
|---|---|
| date | Tue, 13 Oct 2015 12:57:37 -0400 |
| parents | 9ef9311900c9 |
| children |
| rev | line source |
|---|---|
| 0 | 1 <tool id="Draw_phylogram" name="Draw phylogeny" version="1.0.0"> |
| 2 <description></description> | |
| 3 <requirements> | |
| 4 <requirement type="package" version="1.0.0">taxonomy</requirement> | |
| 5 </requirements> | |
| 6 <command interpreter="python">t2ps_wrapper.py $input $out_file1 $max_tree_level $font_size $max_leaves 1</command> | |
| 7 <inputs> | |
| 8 <param format="taxonomy" name="input" type="data" label="Draw phylogram for"></param> | |
| 9 <param name="max_tree_level" label="show ranks from root to" type="select" help="Choosing to show entire tree may produce very large PDF file disabling your viewer"> | |
| 10 <option value="8">Class</option> | |
| 11 <option value="0">Show entire tree</option> | |
| 12 <option value="1">Superkingdom</option> | |
| 13 <option value="2">Kingdom</option> | |
| 14 <option value="3">Subkingdom</option> | |
| 15 <option value="4">Superphylum</option> | |
| 16 <option value="5">Phylum</option> | |
| 17 <option value="6">Subphylum</option> | |
| 18 <option value="7">Superclass</option> | |
| 19 <option value="9">Subclass</option> | |
| 20 <option value="10">Superorder</option> | |
| 21 <option value="11">Order</option> | |
| 22 <option value="12">Suborder</option> | |
| 23 <option value="13">Superfamily</option> | |
| 24 <option value="14">Family</option> | |
| 25 <option value="15">Subfamily</option> | |
| 26 <option value="16">Tribe</option> | |
| 27 <option value="17">Subtribe</option> | |
| 28 <option value="18">Genus</option> | |
| 29 <option value="19">Subgenus</option> | |
| 30 <option value="20">Species</option> | |
| 31 <option value="21">Subspecies</option> | |
| 32 </param> | |
| 33 <param name="font_size" type="select" label="select font size"> | |
| 34 <option value="8">Normal</option> | |
| 35 <option value="4">Tiny</option> | |
| 36 <option value="12">Large</option> | |
| 37 </param> | |
|
2
d89ca6d3c4cd
planemo upload commit 33927a87ba2eee9bf0ecdd376a66241b17b3d734
devteam
parents:
1
diff
changeset
|
38 <param name="max_leaves" type="text" value="0" label="maximum number of leaves" help="set to 0 to show all"/> |
| 0 | 39 </inputs> |
| 40 <outputs> | |
| 41 <data format="pdf" name="out_file1" /> | |
| 42 </outputs> | |
| 43 <requirements> | |
| 44 <requirement type="binary">tree2PS-fast</requirement> | |
| 45 </requirements> | |
| 46 <help> | |
| 47 | |
| 48 **What it does** | |
| 49 | |
| 50 Given taxonomy representation (produced by *Fetch taxonomic representation* tool) this utility produces a graphical representations of phylogenetic tree in PDF format. | |
| 51 | |
| 52 -------- | |
| 53 | |
| 54 **Example 1: Fake data** | |
| 55 | |
| 56 Suppose you have the following dataset:: | |
| 57 | |
| 58 Species_1 1 root superkingdom1 kingdom1 subkingdom1 superphylum1 phylum1 subphylum1 superclass1 class1 subclass1 superorder1 order1 suborder1 superfamily1 family1 subfamily1 tribe1 subtribe1 genus1 subgenus1 species1 subspecies1 | |
| 59 Species_2 2 root superkingdom1 kingdom1 subkingdom1 superphylum1 phylum1 subphylum1 superclass1 class1 subclass1 superorder1 order1 suborder1 superfamily1 family1 subfamily1 tribe1 subtribe1 genus2 subgenus2 species2 subspecies2 | |
| 60 Species_3 3 root superkingdom1 kingdom1 subkingdom1 superphylum1 phylum3 subphylum3 superclass3 class3 subclass3 superorder3 order3 suborder3 superfamily3 family3 subfamily3 tribe3 subtribe3 genus3 subgenus3 species3 subspecies3 | |
| 61 Species_4 4 root superkingdom1 kingdom1 subkingdom1 superphylum1 phylum4 subphylum4 superclass4 class4 subclass4 superorder4 order4 suborder4 superfamily4 family4 subfamily4 tribe4 subtribe4 genus4 subgenus4 species4 subspecies4 | |
| 62 | |
| 63 Drawing the tree with default parameters (without changing anything in the interface) will produce this tree: | |
| 64 | |
| 1 | 65 .. image:: t2ps_ideal.png |
| 0 | 66 :width: 500 |
| 67 | |
| 68 (for explanation of colors and numbers on the tree scroll to the bottom of this help section) | |
| 69 | |
| 70 Here *Class* rank represent terminal nodes (leaves) of the tree because it is the default setting of the "*show ranks from root to*" drop-down. Changing the drop-down to "*Subspecies*" will produce this: | |
| 71 | |
| 1 | 72 .. image:: t2ps_ideal_ssp.png |
| 0 | 73 :width: 1000 |
| 74 | |
| 75 -------- | |
| 76 | |
| 77 **Example 2: Fake data with missing nodes** | |
| 78 | |
| 79 Real taxonomic datasets almost always contain empty nodes. These are represented with "**n**" as shown below:: | |
| 80 | |
| 81 Species_1 1 root superkingdom1 kingdom1 subkingdom1 superphylum1 phylum1 subphylum1 superclass1 class1 subclass1 superorder1 order1 suborder1 superfamily1 family1 subfamily1 tribe1 subtribe1 genus1 subgenus1 species1 subspecies1 | |
| 82 Species_2 2 root superkingdom1 kingdom1 subkingdom1 superphylum1 phylum1 subphylum1 superclass1 class1 subclass1 superorder1 order1 suborder1 superfamily1 family1 subfamily1 tribe1 subtribe1 genus2 n species2 subspecies2 | |
| 83 Species_3 3 root superkingdom1 kingdom1 subkingdom1 superphylum1 n subphylum3 superclass3 class3 subclass3 superorder3 order3 suborder3 superfamily3 family3 subfamily3 tribe3 subtribe3 genus3 subgenus3 species3 subspecies3 | |
| 84 Species_4 4 root superkingdom1 kingdom1 subkingdom1 superphylum1 phylum4 subphylum4 superclass4 class4 subclass4 superorder4 order4 suborder4 superfamily4 family4 subfamily4 tribe4 subtribe4 genus4 subgenus4 species4 subspecies4 | |
| 85 | |
| 86 (here *phylum* for Species_3 and *subgenus* for Species_2 are unassigned) | |
| 87 | |
| 88 A full tree for this dataset will look like this: | |
| 89 | |
| 1 | 90 .. image:: t2ps_missing_nodes.png |
| 0 | 91 :width: 1000 |
| 92 | |
| 93 Missing nodes are simply omitted from the tree (there are no gray boxes corresponding to "n") but the branch length is maintained so that taxa belonging to the same taxonomic rank are always aligned with each other | |
| 94 | |
| 95 -------- | |
| 96 | |
| 97 **Autoscaling the tree** | |
| 98 | |
| 99 You can use the "*maximum number of leaves*" to restrict the tree to a specified number of leaves (external nodes). Using the following setting on the above dataset (note *show ranks from root to* set to *show entire tree* and *maximum number of leaves* is set *3*): | |
| 100 | |
| 1 | 101 .. image:: t2ps_autoscale.png |
| 0 | 102 |
| 103 will produce this tree: | |
| 104 | |
| 1 | 105 .. image:: t2ps_autoscale_tree.png |
| 0 | 106 :width: 1000 |
| 107 | |
| 108 Here the tree is automatically trimmed at a taxonomic rank that will only have 3 outer nodes. This is very useful for initial evaluation of very large trees where you want to only see, say, 1,000 outer nodes at once. | |
| 109 | |
| 110 ------- | |
| 111 | |
| 112 **Explanation of phylogenetic tree markup** | |
| 113 | |
| 114 Branches of the tree are colored according to the heatmap below. The "bluer" the branch the lesser the number of leaves it leads to and vice versa. | |
| 115 | |
| 1 | 116 .. image:: t2ps_heatmap.png |
| 0 | 117 |
| 118 Each node is labeled with taxonomic name and the number of tree leaves belonging to this taxonomic group: | |
| 119 | |
| 1 | 120 .. image:: t2ps_node_label.png |
| 0 | 121 |
| 122 | |
| 123 | |
| 124 | |
| 125 | |
| 126 </help> | |
| 127 </tool> | |
| 128 | |
| 129 |