Hello, I am a galaxy user at Hunter College in New York. Recently we have encountered mismatching files throughout various tools under the same history. We are running our RNAseq analysis on the Dockerized containers. I need the BAM files (accepted hits) which produced by Tophats for the MulticovBed to get the read count. Those BAM files should be the binary 'accepted hit' files but instead they are showing random output from other tools(see the image below). This not only happened to BAM files but for most of the tools and most of the datasets. For example, the output for Groomer is not actually from Groomer but rather from the Tophat 'deletion' or an output from Cufflinks. We are not sure if you are familiar with this issue whether it's a container or a Galaxy known issue. It would be great if you could point me to a right direction on how to resolve this issue. [image: Inline image 1] Sincerely, Changsu
Changsu, It sounds very much like multiple distinct galaxy instances are running against the same database, is that the case here? What happens in those situations is that each galaxy instance associates a dataset ID with a specific file, and the contents of the file might be tool output from a different galaxy instance. - Dave Bouvier http://galaxyproject.org http://usegalaxy.org On 07/06/2017 04:25 PM, Changsu Dong wrote:
Hello,
I am a galaxy user at Hunter College in New York. Recently we have encountered mismatching files throughout various tools under the same history. We are running our RNAseq analysis on the Dockerized containers. I need the BAM files (accepted hits) which produced by Tophats for the MulticovBed to get the read count. Those BAM files should be the binary 'accepted hit' files but instead they are showing random output from other tools(see the image below). This not only happened to BAM files but for most of the tools and most of the datasets. For example, the output for Groomer is not actually from Groomer but rather from the Tophat 'deletion' or an output from Cufflinks.
We are not sure if you are familiar with this issue whether it's a container or a Galaxy known issue. It would be great if you could point me to a right direction on how to resolve this issue.
Inline image 1
Sincerely, Changsu
___________________________________________________________ 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: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/
participants (2)
-
Changsu Dong
-
Dave Bouvier