-
Notifications
You must be signed in to change notification settings - Fork 1
Dependencies and Install
-
Install
Nextflow(>=24.04.2).There are several options for install if you do not already have it on your system:
-
Install into conda environment, which will require a version of Anaconda to be installed on your system.
mamba create -n nextflow -c bioconda nextflow=25.04.2 -
If you prefer a to use
curlorwgetfor install see the Nextflow Documentaiton
-
-
Install
DockerorSingularity >=3.8.7for full pipeline reproducibility. While Docker and Singularity are the most commonly used, Phylophoenix can also be used with Podman and Charliecloud -
(optional) If you installed nextflow via a conda environment activate the nextflow environment with:
conda activate nextflow -
Run PHoeNIx on a test sample loaded with the package with a single command:
nextflow run cdcgov/phylophoenix -r v1.0.0 -profile <singularity/docker/custom>,test --input $PATH_TO_SAMPLESHEET
Note that this command clones (downloads) the repo to ~/.nextflow/assets/cdcgov/phoenix. See PHoeNIx Wiki for how to clone and have the software downloaded to a different location.
> * The pipeline comes with config profiles called `docker` and `singularity` which instruct the pipeline to use the named tool for software management. For example, `-profile test,docker`.
> * Please check [nf-core/configs](https://github.com/nf-core/configs#documentation) to see if a custom config file to run nf-core pipelines already exists for your Institute. If so, you can simply use `-profile <institute>` in your command. This will enable either `docker` or `singularity` and set the appropriate execution settings for your local compute environment.
-
Start running your own analysis with a samplesheet!
nextflow run cdcgov/phylophoenix -r v1.0.0 -profile <singularity/docker/custom> --input <path_to_samplesheet.csv> --metadata <metadata.tsv>
1. Install Nextflow (>=24.04.2).
There are several options for install if you do not already have it on your system:
-
Use
curlorwgetfor install see the Nextflow Documentation -
A good way to install Nextflow is with conda or mamba. Mamba is much faster so we would recommend that. This will require installation of Anaconda first. A short tutorial on Anaconda and its set up can be found here.
If you need mamba installed and you already have anaconda on your system run:
conda install -c conda-forge mambaTo install Nextflow run:
mamba create -n nextflow -c conda-forge -c bioconda nextflow=24.04.2Then you can activate the environment with:
conda activate nextflow- You will run PhyloPHoeNIx from inside this environment!
Configuration will be needed so that Nextflow knows how to fetch the required software. This is usually done in the form of a config profile. You can chain multiple config profiles in a comma-separated string.
- The pipeline comes with config profiles called
dockerandsingularitywhich instruct the pipeline to use the named tool for software management. For example,-profile test,docker. - Please check nf-core/configs to see if a custom config file to run nf-core pipelines already exists for your Institute. If so, you can simply use
-profile <institute>in your command. This will enable eitherdockerorsingularityand set the appropriate execution settings for your local compute environment. - If you are using
singularityand are persistently observing issues downloading Singularity images directly due to timeout or network issues, you can use the--singularity_pull_docker_containerparameter to pull and convert the Docker image instead. Alternatively, you can use thenf-core downloadcommand to download images first, before running the pipeline. Setting theNXF_SINGULARITY_CACHEDIRorsingularity.cacheDirNextflow options enables you to store and re-use the images from a central location for future pipeline runs.- To add
NXF_SINGULARITY_CACHEDIRto your bash profile run the following:- Open your
~/.bash_profileby runningnano ~/.bash_profileor some other text editor that isn't nano. - Inside the
~/.bash_profileadd the following lines
export NXF_SINGULARITY_CACHEDIR=/$PATH/Singularity_Containers export PATH
- Here $PATH is the full path to where you want to store the folder. You can name
Singularity_Containersfolder whatever you want. You will need to restart your terminal or runsource ~/.bash_profileto allow nextflow to see the new path.
- Open your
- To add
Install Docker or Singularity
To run PhyloPHoeNIx there are two options the difference being where you want it installed:
-
Install the latest version via cloning PhyloPHoeNIx github repo into a folder of your choosing:
cd $PATH_TO_INSTALL git clone https://github.com/CDCgov/phylophoenix
If you want to run a particular version then you can download that using the
-bargument like this:git clone -b v1.0.0 https://github.com/CDCgov/phylophoenixThen you can run it (make sure you activate your conda environment first, if that is how nextflow is installed!):
nextflow run $PATH_TO_INSTALL/phylophoenix/main.nf -profile <singularity/docker/custom> --input <path_to_samplesheet.csv> -
Alternatively, PhyloPHoeNIx run directly (will download to
~/.nextflow/assests/cdcgov/phylophoenix):nextflow run cdcgov/phylophoenix -r v1.0.0 -profile <singularity/docker/custom> --input <path_to_samplesheet.csv>Running PhyloPHoeNIx this way means it will just pull the version specified with
-ron github to run and it will be installed into~/.nextflow/assets/cdcgov/phylophoenix.
To test that the pipeline was installed and configured correctly run the following by running either:
nextflow run phylophoenix/main.nf -profile test,<singularity/docker/custom> --input <path_to_samplesheet.csv>or
nextflow run cdcgov/phylophoenix -r v1.0.0 -profile test,<singularity/docker/custom> --input <path_to_samplesheet.csv>This command will run the pipeline on preloaded data. If all goes well you should see some output that looks like this:
DISCLAIMER: The methods used for phylogenetic determination and the data summarized are for public health surveillance or investigational purposes only and must NOT be communicated to the patient, their care provider, or placed in the patient’s medical record. These results should NOT be used for diagnosis, treatment, or assessment of individual patient health or management.