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:


Reply via email to