Mercurial > repos > yhoogstrate > fuma
comparison fuma.xml @ 1:54ce44828e1b draft
planemo upload for repository https://bitbucket.org/EMCbioinf/galaxy-tool-shed-tools/raw/master/fuma commit a88597518f3715c0b22283f6f31757205efcb8d0-dirty
author | yhoogstrate |
---|---|
date | Mon, 01 Jun 2015 06:45:40 -0400 |
parents | a4cfaa0e3e5d |
children | 86526900cb8f |
comparison
equal
deleted
inserted
replaced
0:a4cfaa0e3e5d | 1:54ce44828e1b |
---|---|
163 To annotate genes upon the breakpoints you must provide a BED file that contains gene annotations for the user genome build. Make sure **your BED file contains one gene per line**. You should use BED files that contain one exon per line only if you want restrict your analysis to fusion genes detected within exons. | 163 To annotate genes upon the breakpoints you must provide a BED file that contains gene annotations for the user genome build. Make sure **your BED file contains one gene per line**. You should use BED files that contain one exon per line only if you want restrict your analysis to fusion genes detected within exons. |
164 | 164 |
165 UCSC genome browser provides a very simple way of obtaining BED files with one gene per line by selecting their *RefSeq Genes*-track and *knownGene*-table and putting the export format to BED. Galaxy should have a built-in UCSC table browser. | 165 UCSC genome browser provides a very simple way of obtaining BED files with one gene per line by selecting their *RefSeq Genes*-track and *knownGene*-table and putting the export format to BED. Galaxy should have a built-in UCSC table browser. |
166 | 166 |
167 </help> | 167 </help> |
168 | |
169 <citations> | |
170 </citations> | |
168 </tool> | 171 </tool> |