You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for maintaining this great tool. Could you clarify the following for me:
I have ran kallisto count using the same input .fastq.gz files, but with different indexes (generated using kb ref). The indices differ in the .gtf files used: in the first version, the .gtf file was the standard GENCODEV47 .gtf file, in the second .gtf additional lncRNA entries were added.
Upon running with the standard index, I get mapping percentages of about 60 %. Upon running with the custom .gtf, the mapping percentages dropped to about 15 %. I first figured that this is probably due to the fast that reads multimap to genes and there antisense lncRNA in the latter case, and get thereby discarded. While Smart-seq3 UMI-reads are stranded, the internal reads are not. So I reran with flag --mm, but mapping percentages remained the same. Is this expected, or should the percentage mapped increase if --mm is supplied?
The mm flag has nothing to do with read mapping (it is only used at the UMI counting step).
As for why you are seeing a lower mapping rate with lncRNAs are added in, it’s hard to say. Usually you should get higher mapping (unless perhaps the GTF was modified incorrectly therefore messing up the mapping?)
Describe the issue
Dear,
Thank you for maintaining this great tool. Could you clarify the following for me:
I have ran kallisto count using the same input .fastq.gz files, but with different indexes (generated using kb ref). The indices differ in the .gtf files used: in the first version, the .gtf file was the standard GENCODEV47 .gtf file, in the second .gtf additional lncRNA entries were added.
Upon running with the standard index, I get mapping percentages of about 60 %. Upon running with the custom .gtf, the mapping percentages dropped to about 15 %. I first figured that this is probably due to the fast that reads multimap to genes and there antisense lncRNA in the latter case, and get thereby discarded. While Smart-seq3 UMI-reads are stranded, the internal reads are not. So I reran with flag --mm, but mapping percentages remained the same. Is this expected, or should the percentage mapped increase if --mm is supplied?
Thanks in advance!
What is the exact command that was run?
Command output (with
--verbose
flag)The text was updated successfully, but these errors were encountered: