comparison jbrowse2.xml @ 17:4c201a3d4755 draft

planemo upload for repository https://github.com/usegalaxy-eu/temporary-tools/tree/master/jbrowse2 commit a37bfdfc108501b11c7b2aa15efb1bd16f0c4b66
author fubar
date Sun, 28 Jan 2024 06:48:52 +0000
parents 1fe91657bfd6
children 2e6c48910819
comparison
equal deleted inserted replaced
16:1fe91657bfd6 17:4c201a3d4755
1 <tool id="jbrowse2" name="jbrowse2" version="@TOOL_VERSION@+@WRAPPER_VERSION@_1" profile="22.05"> 1 <tool id="jbrowse2" name="jbrowse2" version="@TOOL_VERSION@+@WRAPPER_VERSION@.1" profile="22.05">
2 <description>genome browser</description> 2 <description>genome browser</description>
3 <macros> 3 <macros>
4 <import>macros.xml</import> 4 <import>macros.xml</import>
5 </macros> 5 </macros>
6 <expand macro="edamInc"/> 6 <expand macro="edamInc"/>
779 The JBrowse-in-Galaxy (JiG) tool was written to help build complex 779 The JBrowse-in-Galaxy (JiG) tool was written to help build complex
780 JBrowse installations straight from Galaxy. It allows you to build up a JBrowse instance without worrying 780 JBrowse installations straight from Galaxy. It allows you to build up a JBrowse instance without worrying
781 about how to run the command line tools to format your data, and which 781 about how to run the command line tools to format your data, and which
782 options need to be supplied and where. 782 options need to be supplied and where.
783 783
784 The JBrowse-in-Galaxy tool is maintained by `the Galaxy IUC 784 The JBrowse-in-Galaxy tool has been rejected by `a Galaxy IUC
785 <https://github.com/galaxyproject/tools-iuc/issues>`__, who you can help you 785 <https://github.com/galaxyproject/tools-iuc/issues>`__, reviewer.
786 with missing features or bugs in the tool. 786 It is maintained by https://github.com/fubar2 who you can help you
787 with missing features or bugs in the tool. For the record, he remains unconvinced by the reviewer's logic,
788 and disturbed by the distinctly coercive approach to introducing new code,
789 compared to the more usual method of providing a working PR.
787 790
788 Options 791 Options
789 ------- 792 -------
790 793
791 The first option you encounter is the **Reference sequence(s)** to use. This option 794 **Reference or Assembly**
792 now accepts multiple fasta files, allowing you to build JBrowse2 795
793 instances that contain data for multiple genomes or chrosomomes 796 Choose either a built-in or select one from your history.
794 (generally known as "landmark features" in gff3 terminology.) 797
795 798 Track coordinates and contig names *must* match this reference precisely
796 **Track Groups** represent a set of tracks in a single category. These 799 or they will not display.
797 can be used to let your users understand relationships between large 800
798 groups of tracks. 801 **Track Groups** represent a set of tracks in a single category.
799 802
800 Annotation Tracks 803 Annotation Tracks
801 ----------------- 804 -----------------
802 805
803 There are a few different types of tracks supported, each with their own
804 set of options:
805
806 GFF3/BED 806 GFF3/BED
807 ~~~~~~~~ 807 ~~~~~~~~
808 808
809 These are standard feature tracks. They usually highlight genes, 809 Standard feature tracks. They usually highlight genes, mRNAs and other features of interest along a genomic region.
810 mRNAs and other features of interest along a genomic region.
811 810
812 When these contain tens of millions of features, such as repeat regions from a VGP assembly, displaying one at a time leads 811 When these contain tens of millions of features, such as repeat regions from a VGP assembly, displaying one at a time leads
813 to extremely slow loading times when a large region is in view, unless the "LinearPileupDisplay" display option is 812 to extremely slow loading times when a large region is in view, unless the "LinearPileupDisplay" display option is
814 selected for that track in the styling options section. The default is LinearBasicDisplay, which shows all details and works 813 selected for that track in the styling options section. The default is LinearBasicDisplay, which shows all details and works
815 well for relatively sparse bed files. 814 well for relatively sparse bed files. A better option is to make a bigwig track using a set of windows based on the
815 lengths of each assembly or reference contig.
816 816
817 BAM Pileups 817 BAM Pileups
818 ~~~~~~~~~~~ 818 ~~~~~~~~~~~
819 819
820 We support BAM files and can automatically generate SNP tracks based on 820 We support BAM files and can automatically generate SNP tracks based on