-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Htseq_count can fail with RNA STAR input #84
Comments
@davebx is updating to htseq-count 0.9.1, which hopefully fixes it (or at least it's worth testing once it's updated). |
Test history: https://usegalaxy.org/u/jen/h/test-history-rnastar (includes updated star 2.5.2b-0 + htseq 0.9.1) I don't think this exact test will capture the specific error above -- and we don't have an example of the inputs that trigger this (why there was no original test history, end-user deleted before I could get it back in Jan) -- but we can watch for it being reported again. I close this out once the general-usage tests finish overnight. |
I can't get HTseq to work (no features overlap - even when using HISAT2 input). Featurecounts works with the same inputs. I am using tutorial data that should work with both. Second test history: https://usegalaxy.org/u/jen/h/test-history-cufflinks-hisat2 I'll need to troubleshoot this more. |
Trying again with the newer version of HISAT2, STAR, and complete reruns with different params. In progress, same test history as in the prior comment. |
Still a problem. Looks like the tool was updated in the MTS (bug fix) but didn't have a revision change. Could we update it to the most current MTS version and see if this problem goes away, too? |
Retesting with different data - think works in some data, might be a corner-case tool bug |
Tracking ticket Once the problem is resolved and Main updated (as needed) we can close this out.
Workaround Use HISAT2 instead of RNA STAR.
Example error
Potentially the root issue: https://www.biostars.org/p/147487/
Comments from @natefoo:
The text was updated successfully, but these errors were encountered: