Error while trying to run HUMAnN to annonate reads:
ERROR: The MetaPhlAn taxonomic profile provided was not generated with the database version v3 or vJun23 . Please update your version of MetaPhlAn to at least v3.0 or if you are using MetaPhlAn v4 please use the database vJun23.
HUMAnN calls for the current version of MetaPhlAn which is v4 but the only cached database for classifying community members is from 2022. Can this be updated to at least vJun23 as the error calls for? Thanks!
Is the job failing (red) or is this just a warning in the logs?
I see “June” databases for the tools at the EU server but might be looking at the wrong thing.
Do you want to share your example? The tool versions and databases, exactly, will be needed for me to make a request. You are welcome to generate a shared history link and post that back, and I’ll review. How to share is in the banner topic.
Thanks, I misunderstood the error. Apparently, the error meant it can’t generate the taxonomy on HUMAnN using the database available to be cached. And on the tutorial you shared, that is provided as an output of MetaPhlan. But that is also a problem I’m having, MetaPhlan doesn’t run well with classifying my metagenome reads (it only classifies one species), even though I have classified them without a problem using Kraken2..
Since MetaPhlan wasn’t classifying your reads well anyway (the newest version, when used directly?) you could try using the Kraken2 output instead in HUMAnN with this converter tool.
Krakentools: Convert kraken report file to MetaPhlAn-style
To be clear: it looks to me like the updated indexes are included in MetaPhlAn at UseGalaxy.eu (last updated March 2025). This result can be passed through to HUMAnN. The current usability problems are:
those same indexes could be added to the HUMAnN tool as well (what you originally asked about) but the other two items are delaying the consolidation. These databases are large enough to prevent an easy fix (replicate them with multiple names) and multiple labels leads to reproducibility issues we want to avoid. The available path for now is to run MetaPhlAn directly instead a the server that hosts the current index, and to pass the result to HUMAnN for the additional classification layers.
So, there are a few technical issues remaining to be resolved to make this all nicer (for scientists and admins!), but the scientific path with the most current data should be fine. Adding all the tools to a simple workflow would produce about the same total “processing time” per sample. If you need to move data between servers, this can all be done via URL (no download step).
Apologies for the complicated usage! But, does this help? We can follow up more.