-
Notifications
You must be signed in to change notification settings - Fork 43
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
Does krakenuniq ever suppress (countable) kmers from reads? #146
Comments
hi @pfeiferd, |
Thank you so much! I was away, but I will look into it this week and tell what's going on... |
Dear Steven, I can reproduce the beviour as described above (which is supposedly a bug according to your answer). We / I can provide you with the necessary files via a personal FTP server (the fastq file is about 121MB). We used a standard krakenuniq database ("kuniq_standard_plus_eupath_minus_kdb"). You could get the following files:
Let me know what you think. The FTP-Server credentials would have to be transferred via email / Skype or so. Daniel |
I'm afraid I don't have time to debug this myself. I will ask a person in my lab about it, but it might take some time. It is possible that your reads are long enough that they got truncated by one program - although that isn't supposed to happen anyway, there's no read length limit. So I can't really guess, but we've never seen this behavior. If you send me email (rather than github) at salzberg@jhu.edu, I will see if someone can take a look. |
Just sent a respective email... Thanks so much for looking into this. |
Dear pioneers for much improved pathogen detection,
we have an example from nanopore (resulting in long reads > 1500 bps) where the kraken1-part of krakenuniq counts over 12000 kmers (k = 31) for a species (taxid 47466). Our own analysis revealed that these reads probably belong to just 26 unique kmers. Thus, the counted kmers are most likely "trash" in a sense that they don't indicate the presence of a corresponding pathogen. BUT: "47466" does not even occur in the corresponding krakenuniq report!
We assume there is a kind of unbuilt filter in krakenuniq to suppress such findings - or is it maybe a bug? Could you briefly explain under which conditions you keep or conversely filter out counted kmers (if so) in krakenuniq reports?
(We could potentially hand over the corresponding fastq file if you suspected a bug.)
Thanks and best regards,
Daniel
The text was updated successfully, but these errors were encountered: