[galaxy-dev] Trackster error: not able to find the chrom len file
Dear all, I updated to the latest Galaxy stable code, and updated the datatypes_conf.xml. Trackster displays an error after opening a saved view: *** Error: The requested genome file (/home/galaxy/galaxy-dist/tool-data/shared/ucsc/chrom/dm3.len) could not be opened. Exiting! sort: write failed: standard output: Broken pipe sort: write error Couldn't open /home/galaxy/galaxy-dist/tool-data/shared/ucsc/chrom/dm3.len , No such file or directory *** In my universe_wsgi.ini I point to the correct directory where I keep my chrom len files. # Directory where chrom len files are kept, currently mainly used by trackster len_file_path = /mnt/referencedata/trackster Thanks for any advice, Cheers, Joachim -- Joachim Jacob Contact details: http://www.bits.vib.be/index.php/about/80-team ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Re: [galaxy-dev] Trackster error: not able to find the chrom len file
Trackster displays an error after opening a saved view: *** Error: The requested genome file (/home/galaxy/galaxy-dist/tool-data/shared/ucsc/chrom/dm3.len) could not be opened. Exiting! sort: write failed: standard output: Broken pipe sort: write error Couldn't open /home/galaxy/galaxy-dist/tool-data/shared/ucsc/chrom/dm3.len , No such file or directory *** In my universe_wsgi.ini I point to the correct directory where I keep my chrom len files. # Directory where chrom len files are kept, currently mainly used by trackster len_file_path = /mnt/referencedata/trackster This is a bug: Galaxy wasn't using this setting in converters. I've fixed this in -stable changeset 7105c53: https://bitbucket.org/galaxy/galaxy-central/commits/7105c53139d4b8649e6a3714bc117118989712a2 Further, I had to remove the 'chr' in the chrom len files to make it work. This is a problem between the UCSC chromosome naming convention (e.g., 'chr1') and the Ensembl naming convention (e.g. '1'). In most cases Galaxy handles this transparently, but the new converters do not. This is something that definitely needs to be implemented. Here's a card so that you can follow the feature's progress: https://trello.com/c/lai0uU9g Best, J.___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
