Files
galaxy/tools/data_source/encode_import_multi-species_sequence_analysis.xml
T
Daniel Blankenberg 11a2c767c3 Rewrite of dynamic options for select lists. There are no more 'special cases' and new filters are much easier to incorporate, as neeeded.
MAF tool interfaces now support the use of index species and all species existing in cached alignment sets.
Until main is updated and the old maf_location files can be overwritten, these symbolic links are required:
maf_index.loc -> /depot/data2/galaxy/maf_index_new.loc
maf_pairwise.loc -> /depot/data2/galaxy/maf_pairwise_new.loc
2008-05-29 17:38:46 +00:00

68 lines
3.2 KiB
XML

<tool id="encode_import_multi-species_sequence_analysis1" name="Multi-species Sequence Analysis">
<command interpreter="python">encode_import.py $hg17,$hg16 $output ${GALAXY_DATA_INDEX_DIR}</command>
<inputs>
<display>
<p><div class="toolFormTitle">hg17 (most recent datasets in bold)</div>$hg17</p>
<p><div class="toolFormTitle">hg16 (most recent datasets in bold)</div>$hg16</p>
</display>
<param name="hg17" type="select" display="checkboxes" multiple="true">
<options from_file="encode_datasets.loc">
<column name="name" index="2"/>
<column name="value" index="3"/>
<column name="dbkey" index="1"/>
<column name="encode_group" index="0"/>
<column name="uid" index="3"/>
<filter type="static_value" name="encode_group" value="MSA" column="0"/>
<filter type="static_value" name="dbkey" value="hg17" column="1"/>
</options>
</param>
<param name="hg16" type="select" display="checkboxes" multiple="true">
<options from_file="encode_datasets.loc">
<column name="name" index="2"/>
<column name="value" index="3"/>
<column name="dbkey" index="1"/>
<column name="encode_group" index="0"/>
<column name="uid" index="3"/>
<filter type="static_value" name="encode_group" value="MSA" column="0"/>
<filter type="static_value" name="dbkey" value="hg16" column="1"/>
</options>
</param>
</inputs>
<outputs>
<data format="bed" name="output"/>
</outputs>
<code file="encode_import_code.py"/>
<help>
.. class:: warningmark
The data in this section is intended as a supplement for this manuscript_. Use the **Get Data->UCSC Main** tool for current ENCODE data.
.. _manuscript: http://www.genome.org/cgi/content/full/17/6/960
For detailed information about data deposition and partitioning, click here_.
.. _here: http://genome.imim.es/gencode/wiki/index.php/Collecting_Feature_Sets_from_All_Analysis_Groups
*[gencode_partitioned]* means that the dataset was partitioned according to the protocol below:
A partition scheme has been defined that is similar to what has previously been done with TARs/TRANSFRAGs such that any feature can be classified as falling into one of the following 6 categories:
1. **Coding** -- coding exons defined from the GENCODE experimentally verified coding set (coding in any transcript)
2. **5UTR** -- 5' UTR exons defined from the GENCODE experimentally verified coding set (5' UTR in some transcript but never coding in any other)
3. **3UTR** -- 3' UTR exons defined from the GENCODE experimentally verified coding set (3' UTR in some transcript but never coding in any other)
4. **Intronic Proximal** -- intronic and no more than 5kb away from an exon.
5. **Intergenic Proximal** -- between genes and no more than 5kb away from an exon.
6. **Intronic Distal** -- intronic and greater than 5kb away from an exon.
7. **Intergenic Distal** -- between genes and greater than 5kb away from an exon.
-----
.. class:: infomark
**Note:** Features overlapping more than one partition will take the identity of the lower-numbered partition.
</help>
</tool>