-
Notifications
You must be signed in to change notification settings - Fork 13
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
transcript numbers don't match between OUT.transcript_model_grouped_tpm.tsv and OUT.transcript_models.gtf #195
Comments
Dear @dudududu12138
Best |
Sorry for the late reply. Below are the Moreover, I noticed that in my result, |
By the way, I checked myself. I extracted an example of a transcript that is reported in the |
Yes, this is really odd. |
Here is what I found so far. Output GTF and supporting reads are likely correct. However, expression estimation algorithm is independent from transcript discovery and for some reason assigns 0 to some of the transcripts. I will now check why expression estimation algorithm assigns 0 to these transcripts despite the fact they are supported by reads. Best |
Yes, I also found this reason.
Thanks, looking forward to your checking results! |
This is the log file. |
|
I think I found the problem. IsoQuant outputs a few novel isoforms that are very similar to the reference ones, and that's where read-to-isoform assignment goes wrong and the novel isoform gets 0 counts because all assignments are ambiguous. So, these similar isoforms should not be there in the first place. I'll make a bug-fix release soon. |
Will be fixed in 3.5.0. |
Should be fixed in https://github.com/ablab/IsoQuant/releases/tag/v3.5.0 |
Hi, I recently used isoquant(version 3.4.1) to detect isoforms from multiple samples. But the results are a little odd. Below are my quaetions:
OUT.transcript_models.gtf
while 166857 inOUT.transcript_model_tpm.tsv
.Thank you very much!
The text was updated successfully, but these errors were encountered: