Hi,
when a tool outputs an unsorted bam file, the indexing fails (quietly) and its metadata variable "bam_index" points to an inexistent file. This causes a nasty bug when trying to import the dataset into a data library and actually makes the library unusable unless you delete the broken entry from the - in my case Postgresql - database by hand. Are you working on it?
Thanks, Florian
Hi Florian,
I am fairly certain that this exact issue is still open, and so have opened a bitbucket ticket to track progress: http://bitbucket.org/galaxy/galaxy-central/issue/718/unsorted-bam-files-and-...
If this has been corrected already, one of us will send an update tomorrow.
Thanks!
Jen Galaxy team
On 9/3/11 4:41 PM, Florian Wagner wrote:
Hi,
when a tool outputs an unsorted bam file, the indexing fails (quietly) and its metadata variable "bam_index" points to an inexistent file. This causes a nasty bug when trying to import the dataset into a data library and actually makes the library unusable unless you delete the broken entry from the - in my case Postgresql - database by hand. Are you working on it?
Thanks, Florian ___________________________________________________________ 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:
galaxy-dev@lists.galaxyproject.org