-
Notifications
You must be signed in to change notification settings - Fork 52
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
negative added_reads #141
Comments
It is possible in a strange situation with some adjustments I made to the script. I'll try to describe it here: Assume you have species A with strains 1 and 2 and related species B with strain 3, but for some reason, reads from strains 1 and 2 classify as species B (meaning they might be more related to strain 3 and probably should be in the same species with strain 3), then when Bracken reorganizes reads, it will take away reads from species A and give them to species B. This is a bit of a strange situation that does happen, but not all the time. |
Hi! I and a collaborator are a bit confused about this - we thought that Bracken just moves reads from higher levels down, and reads from lower levels up. We didn't think there was any horizontal movement of reads? |
@meenachakra you are correct, Bracken just moves reads down or up in the hierarchy, it does not move them sideways. Jen is referring to an unusual case where the actual data might include a species that has some sequence matching a different species (or genus). However we just discovered a bug, which Jen is fixing right now (already partly fixed), that causes Bracken to "zero out" some species when there are multiple near-identical strains belonging to that species. The updated files will be posted soon (and two updates are already posted). |
Update: the bug is fixed and Bracken no longer has the problem where it can "zero out" species in a custom taxonomy. Users should update their Bracken version to the latest github release. |
Thank you so much! |
@salzberg |
Hi, I am curious to know whether it is possible the 'added_reads' in Bracken output can be a negative number.
name taxonomy_id taxonomy_lvl kraken_assigned_reads added_reads new_est_reads fraction_total_reads
Phocaeicola vulgatus 821 S 82772 -19082 63690 0.03416
Schaalia odontolytica 1660 S 89493 -89493 0 0.00000
Thanks,
The text was updated successfully, but these errors were encountered: