-
Notifications
You must be signed in to change notification settings - Fork 494
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
Less multimapping reads, more uniquely mapped reads #215
Comments
Can STARindex have something to do with this:
Is the correct value for |
Hi @P4sm overall, STAR finds more alignable reads: 85.08%+14.02%+0.31%=99.41% vs TopHat2's 98.5%. Cheers |
Hi, Three examples: TopHat 2:
STAR:
TopHat 2:
STAR:
TopHat 2:
STAR
I hope this helps. |
And here are the reads in FASTQ format, in case you need that.
|
Hi @P4sm it looks like in all cases STAR behaves as expected, and these reads are truly multimappers.
STAR also finds three spliced alignments with no mismatches, and assigns them a score of 47 (large gaps are penalized). I guess TopHat completely misses these spliced alignments. If you do not like long gaps, there are ways to penalize them more.
To summarize, in 1 case the differences between STAR and TopHat can be tweaked out. In the other two cases, TopHat simply misses the perfectly good multimapping alignments. Cheers |
Thanks for your thorough analysis, and I agree with you. |
Hi,
I have an example of alignment summary here:
But I get more uniquely aligned reads with Tophat2:
Reads: Input : 10206806 Mapped : 10058745 (98.5% of input) of these: 347302 ( 3.5%) have multiple alignments (2093 have >20) 98.5% overall read mapping rate.
My STAR parameters are pretty much default. Do you know how I could acquire more uniquely aligned reads with STAR?
The text was updated successfully, but these errors were encountered: