Before opening a new issue here, please check the appropriate help channel on the bioBakery Support Forum (https://forum.biobakery.org) and consider opening or commenting on a thread there.
HUMAnN 3.0 is the next generation of HUMAnN (HMP Unified Metabolic Analysis Network).
If you use HUMAnN 3.0 in your work, please cite the HUMAnN 3.0 paper:
Francesco Beghini1 ,Lauren J McIver2 ,Aitor Blanco-Mìguez1 ,Leonard Dubois1 ,Francesco Asnicar1 ,Sagun Maharjan2,3 ,Ana Mailyan2,3 ,Andrew Maltez Thomas1 ,Paolo Manghi1 ,Mireia Valles-Colomer1 ,George Weingart2,3 ,Yancong Zhang2,3 ,Moreno Zolfo1 ,Curtis Huttenhower2,3 ,Eric A Franzosa2,3 ,Nicola Segata1,4
1 Department CIBIO, University of Trento, Italy
2 Harvard T. H. Chan School of Public Health, Boston, MA, USA
3 The Broad Institute of MIT and Harvard, Cambridge, MA, USA
4 IEO, European Institute of Oncology IRCCS, Milan, Italy
And feel free to link to HUMAnN 3.0 in your Methods:
http://huttenhower.sph.harvard.edu/humann
For additional information, read the HUMAnN Tutorial
HUMAnN is a pipeline for efficiently and accurately profiling the presence/absence and abundance of microbial pathways in a community from metagenomic or metatranscriptomic sequencing data (typically millions of short DNA/RNA reads). This process, referred to as functional profiling, aims to describe the metabolic potential of a microbial community and its members. More generally, functional profiling answers the question "What are the microbes in my community-of-interest doing (or capable of doing)?"
Community functional profiles stratified by known and unclassified organisms
Considerably expanded databases of genomes, genes, and pathways
A simple user interface (single command driven flow)
Accelerated mapping of reads to reference databases (including run-time generated databases tailored to the input)

There are four different types of files that can be provided as input to HUMAnN 3.0 . By default HUMAnN 3.0 will determine the type of the file. As shown in the figure below, the type of input file will determine where HUMAnN 3.0 will start the workflow. Files of type 2, 3, and 4 will begin the workflow after the alignment steps.

File Types:
There are multiple bypass options that will allow you to adjust the standard workflow.

Bypass options:
HUMAnN 3.0 includes a "--resume" option which will allow you to bypass alignment steps which have already been completed. For example, if you originally ran with a bypass option you can run just the step you bypassed with "--resume". This will only run the alignment step you bypassed and then recompute the gene families and pathways.

When using the "--resume" option, the following steps will be bypassed if they have already been completed:
Please install the required software in a location in your $PATH or provide the location with an optional argument to HUMAnN 3.0.
For example, the location of the Bowtie2 install ($BOWTIE2_DIR) can be provided with "--bowtie2 $BOWTIE2_DIR".
Some of the required dependencies are installed automatically when installing HUMAnN 3.0 with pip. If these dependencies do not appear to be installed after installing HUMAnN 3.0 with pip, it might be that your environment is setup to use wheels instead of installing from source. HUMAnN 3.0 must be installed from source for it to also be able to install dependencies. To force pip to install HUMAnN 3.0 from source add one of the following options to your install command, "--no-use-wheel" or "--no-binary :all:".
If you always run with input files of type 2, 3, and 4 (for information on input file types, see section Workflow by input file type), MetaPhlAn2, Bowtie2, and Diamond are not required. Also if you always run with one or more bypass options (for information on bypass options, see section Workflow by bypass mode), the software required for the steps you bypass does not need to be installed.
If always running with files of type 2, 3, and 4 (for information on file types, see section Workflow by input file type), less disk space is required.
You can download the latest HUMAnN 3.0 release or the development version. The source contains example files. If installing with pip, it is optional to first download the HUMAnN 3.0 source.
Option 1: Latest Release (Recommended)
Option 2: Development Version
Create a clone of the repository:
$ git clone https://github.com/biobakery/humann
Note: Creating a clone of the repository requires Github to be installed.
$ pip install humann$ claude mcp add humann \
-- python -m otcore.mcp_server <graph>