|
1
|
1 <?xml version="1.0"?>
|
|
|
2
|
|
|
3 <tool name="MGEScan" id="mgescan" version="0.0.2">
|
|
|
4 <description>
|
|
|
5 MGEScan
|
|
|
6 </description>
|
|
|
7 <command interpreter="bash">
|
|
|
8 mgescan.sh $input '$input.name' 3 $output $program $clade $qvalue_en $qvalue_rt $ltr_gff3 $nonltr_gff3 $both_gff3 $mpi_yn.nmpi
|
|
|
9 <!-- mgescan.sh $input $input.name $hmmver $output $program $clade $qvalue_en $qvalue_rt $ltr_gff3 $nonltr_gff3 -->
|
|
|
10 </command>
|
|
|
11 <inputs>
|
|
|
12 <param format="fasta,tabular,data" name="input" type="data" label="Input FASTA file(s)"/>
|
|
|
13 <!--param name="hmmver" type="select" label="Hmmsearch version">
|
|
|
14 <option selected="selected" value="3">3</option>
|
|
|
15 <option value="2">2</option>
|
|
|
16 </param-->
|
|
|
17 <param name="program" type="select" label="MGEScan">
|
|
|
18 <option selected="selected" value="B">Both</option>
|
|
|
19 <option value="L">LTR</option>
|
|
|
20 <option value="N">nonLTR</option>
|
|
|
21 </param>
|
|
|
22 <conditional name="mpi_yn">
|
|
|
23 <param name="mpi_select" type="select" label="Enable MPI">
|
|
|
24 <option value="no_mpi">No</option>
|
|
|
25 <option value="yes_mpi">Yes</option>
|
|
|
26 </param>
|
|
|
27 <when value="yes_mpi">
|
|
|
28 <param name="nmpi" format="txt" type="text" value="1" label="Number of MPI Processes"/>
|
|
|
29 </when>
|
|
|
30 <when value="no_mpi">
|
|
|
31 <param name="nmpi" type="hidden" value="0"/>
|
|
|
32 </when>
|
|
|
33 </conditional>
|
|
|
34 </inputs>
|
|
|
35 <outputs>
|
|
|
36 <data format="ltr.out" name="output" label="LTR Results (ltr.out)">
|
|
|
37 <filter>program != "N"</filter>
|
|
|
38 </data>
|
|
|
39 <data format="fasta" name="clade" label="clade file (FASTA)">
|
|
|
40 <filter>program != "L"</filter>
|
|
|
41 </data>
|
|
|
42 <data format="qfile" name="qvalue_en" label="qvalue_en">
|
|
|
43 <filter>program != "L"</filter>
|
|
|
44 </data>
|
|
|
45 <data format="qfile" name="qvalue_rt" label="qvalue_rt">
|
|
|
46 <filter>program != "L"</filter>
|
|
|
47 </data>
|
|
|
48 <data format="gff3" name="ltr_gff3" label="GFF3 for LTR">
|
|
|
49 <filter>program != "N"</filter>
|
|
|
50 </data>
|
|
|
51 <data format="gff3" name="nonltr_gff3" label="GFF3 for nonLTR">
|
|
|
52 <filter>program != "L"</filter>
|
|
|
53 </data>
|
|
|
54 <data format="gff3" name="both_gff3" label="GFF3 for LTR and nonLTR">
|
|
|
55 <filter>program == "B"</filter>
|
|
|
56 </data>
|
|
|
57
|
|
|
58 </outputs>
|
|
|
59 <help>
|
|
|
60 How to Run MGEScan
|
|
|
61 ===================
|
|
|
62
|
|
|
63 * Select an input genome data from the select box, and choose a program. Both LTR and nonLTR of MGEScan is default.
|
|
|
64 * Click 'Execute' button.
|
|
|
65 * MPI will be enabled depending on your system support.
|
|
|
66
|
|
|
67 If you like to have more options to run LTR or nonLTR program, use separated tools on the left panel.
|
|
|
68
|
|
|
69 For example, in LTR > MGEScan-LTR, preprocessing by repeatmasker and setting other variables are available e.g. distance(bp) between LTRs.
|
|
|
70
|
|
|
71 Output
|
|
|
72 ============
|
|
|
73
|
|
|
74 A. MGEScan_LTR:
|
|
|
75
|
|
|
76 Upon completion, MGEScan-LTR generates a file "ltr.out". This output file has information
|
|
|
77 about clusters and coordinates of LTR retrotransposons identified. Each cluster of LTR
|
|
|
78 retrotransposons starts with the head line of "[cluster_number]---------", followed by
|
|
|
79 the information of LTR retrotransposons in the cluster. The columns for LTR
|
|
|
80 retrotransposons are as follows.
|
|
|
81
|
|
|
82 1. LTR_id: unique id of LTRs identified. It consist of two components, sequence file name and id in the file. For example, chr1_2 is the second LTR retrotransposon in the chr1 file.
|
|
|
83 2. start position of 5’ LTR.
|
|
|
84 3. end position of 5’ LTR.
|
|
|
85 4. start position of 3’ LTR.
|
|
|
86 5. end position of 3’ LTR.
|
|
|
87 6. strand: + or -.
|
|
|
88 7. length of 5’ LTR.
|
|
|
89 8. length of 3’ LTR.
|
|
|
90 9. length of the LTR retrotransposon.
|
|
|
91 10. TSD on the left side of the LTR retotransposons.
|
|
|
92 11. TSD on the right side of the LTR retrotransposons.
|
|
|
93 12. di(tri)nucleotide on the left side of 5’LTR
|
|
|
94 13. di(tri)nucleotide on the right side of 5’LTR
|
|
|
95 14. di(tri)nucleotide on the left side of 3’LTR
|
|
|
96 15. di(tri)nucleotide on the right side of 3’LTR
|
|
|
97
|
|
|
98 B. MGEScan_nonLTR:
|
|
|
99 Upon completion, MGEScan-nonLTR generates the directory, "info" in the data directory you
|
|
|
100 specified. In this "info" directory, two sub-directories ("full" and "validation") are
|
|
|
101 generated.
|
|
|
102
|
|
|
103 * The "full" directory is for storing sequences of elements. Each subdirectory in "full"
|
|
|
104 is the name of clade. In each directory of clade, the DNA sequences of nonLTRs identified
|
|
|
105 are listed. Each sequence is in fasta format. The header contains the position
|
|
|
106 information of TEs identified: [genome_file_name]_[start position in the sequence]
|
|
|
107
|
|
|
108 For example, >chr1_333 means that this element start at 333bp in the "chr1" file.
|
|
|
109
|
|
|
110 * The "validation" directory is for storing Q values.
|
|
|
111 In the files "en" and "rt", the first column corresponds to the element name and the last column Q value.
|
|
|
112
|
|
|
113 License
|
|
|
114 ============
|
|
|
115 Copyright 2015.
|
|
|
116 You may redistribute this software under the terms of the GNU General Public License.
|
|
|
117
|
|
|
118 </help>
|
|
|
119 </tool>
|
