Mercurial > repos > iuc > jbrowse
diff jbrowse.xml @ 61:21585b031a4d draft
"planemo upload for repository https://github.com/galaxyproject/tools-iuc/tree/master/tools/jbrowse commit 369a727966d697c56633b27ad2757db40fef0dc3"
| author | iuc |
|---|---|
| date | Fri, 30 Aug 2019 03:36:04 -0400 |
| parents | e29039f307c4 |
| children | 46cf483e76d6 |
line wrap: on
line diff
--- a/jbrowse.xml Tue Jul 16 05:07:42 2019 -0400 +++ b/jbrowse.xml Fri Aug 30 03:36:04 2019 -0400 @@ -401,7 +401,7 @@ <repeat name="data_tracks" title="Annotation Track"> <conditional name="data_format" label="Track Options"> <param type="select" label="Track Type" name="data_format_select"> - <option value="gene_calls">GFF/GFF3/BED/GBK Features</option> + <option value="gene_calls">GFF/GFF3/BED Features</option> <option value="pileup">BAM Pileups</option> <option value="blast">Blast XML</option> <option value="wiggle">BigWig XY</option> @@ -1167,14 +1167,14 @@ There are a few different types of tracks supported, each with their own set of options: -GFF3/BED/GBK -~~~~~~~~~~~~ +GFF3/BED +~~~~~~~~ These are your standard feature tracks. They usually highlight genes, mRNAs and other features of interest along a genomic region. The underlying tool and this help documentation focus primarily on GFF3 data, and have not been tested extensively with other formats. Automatic -min/max detection will likely fail under BED and GBK datasets. +min/max detection will fail under BED datasets. The data may be of a subclass we call **match/match part** data. This consists of top level ``match`` features, with a child ``match_part``
