-
Notifications
You must be signed in to change notification settings - Fork 582
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
Kaiju module works only at phylum level #1217
Comments
Aha, good spot - thank you! This was a very last-minute addition to the v1.9 release by @noirot. Any thoughts @noirot? Do you think you could add a fix for this please? We can add this test data to MultiQC_TestData once we have a fix (not before though, as it will cause all MultiQC tests to start failing). Thanks, Phil |
Oh weird ! Yes I'll have a look. |
@jkibilds - should now be fixed in v1.10dev. Let us know if you find any problems, thanks for reporting! Phil |
Now it works with reports from all taxonomic levels, thanks! |
Description of bug:
When I run MultiQC on table reports from Kaiju, the Kaiju module breaks if the input files have taxonomic classification at any other level than phylum.
MultiQC Error log:
File that triggers the error:
Li-2020-14538-3.kaiju.genus.txt
(I had to rename the file from .tsv to .txt because GitHub allows only certain extensions)
MultiQC run details:
multiqc -o genus/mqcout genus/
Additional context
I prepared Kaiju reports for the same sample at all taxonomic levels (except superkingdom) using
kaiju2table
and ran MultiQC on each report file separately. It produced a report and no error messages only with phylum-level input. The same is true if I use input files from https://github.com/ewels/MultiQC_TestData/tree/master/data/modules/kaiju - only the three example files at phylum level work.The text was updated successfully, but these errors were encountered: