Closed Electrocyte closed 1 year ago
Hi @Electrocyte and thanks for the detailed bug report! The 0
taxid is not a valid NCBI taxid (see output from https://www.ncbi.nlm.nih.gov/taxonomy/?term=0) but just a way that Centrifuge has to represent unclassified reads in its output. So, you can't exclude those using Recentrifuge's -x
argument, but you actually don't want to exclude them: Recentrifuge uses that information to calculate the ratio of classified vs unclassified reads and offer that statistics in the results. Hope this helps.
Bug report
Bug summary
Nodes/names file are missing an unclassified taxID (0) that is present in the troubleshooting file. I am not sure if this is normal behaviour. A simple fix for this is to edit the "-x 0" out of the command line call. After doing this, I had no issues with running recentrifuge for centrifuge.
Running Recentrifuge
Command line
Data
Actual outcome
Expected outcome
Versions