MAGNETO
==============================================

MAGNETO is an automated snakemake workflow dedicated to MAG (Metagenome-Assembled Genomes) reconstruction from metagenomic data. 

It includes a fully-automated coassembly step informed by optimal clustering of metagenomic distances, and implements complementary genome binning strategies, for improving MAG recovery.

# Key Features

 - **Quality Control (QC)**: Automatically assesses the quality and the contamination of input reads, ensuring that low-quality data are filtered out to improve downstream analyses.

 - **Assembly**: MAGNETO uses high-performance assembler to construct contigs from metagenomic reads.

 - **Gene Collection**: Extracts and compiles gene sequences from contigs, providing a comprehensive gene catalog directly after assembly.

 - **Binning**: Groups contigs into probable genomes using composition signatures and abundance profiles.

 - **Genomes collection**: Provides taxonomic and functional annotation of reconstructed MAGs.

 - **Metatranscriptomic mapping**: Mapping of transcriptomic reads on genes collection and/or MAGs obtained with previous analysis.

# Documentation

**Full description in the [wiki pages](https://gitlab.univ-nantes.fr/bird_pipeline_registry/magneto/-/wikis/home)**

# Installation
## Install from bioconda
Make sure you download the latest recipe version (currently `magneto-1.5.1-pyhdfd78af_0`).
```bash
conda install -c bioconda magneto
```

## Install from source
### Dependencies

A working installation of **conda** and **git** is mandatory to build magneto. If you have **mamba** already install on your system, the creation of the main environment will be faster.


- python 3.8+
- snakemake 7.32.4
- mamba 1.5.8
- conda 4.10.3
- click 8.01

Other dependencies (such as python libraries for analysis, or to compute programs) are installed through the setup.py and conda management.\
The default conda libraries management for snakemake is mamba, since a couple of month now. Even if it is possible to use conda instead of mamba for conda libraries management, the design of Magneto set mamba mandatory, as `--conda-frontend conda` does not propagate to the subworkflows.\
Except if you use your own databases or already have downloaded them, MAGNETO will also require an internet connection.

### Main conda environment installation
Start by creating a conda environment containing snakemake, mamba and the python module click:
```bash
conda create -n magneto snakemake-minimal=7.32.4 click=8.01 mamba=1.5.8 -c bioconda -c conda-forge
```

> Note  
> - If you have **mamba** or **micromamba** already installed, you can create the environment with it instead of conda.

Then, activate your environment:
```
conda activate magneto
```

### Installation of magneto module in the conda environment
Installation is performed using `pip`:
```
git clone https://gitlab.univ-nantes.fr/bird_pipeline_registry/magneto.git
python3 -m pip install magneto/
```

**Magneto** is now installed in the "magneto" conda environment. Activate your environment whenever you need to run the pipeline !! 

# Initialization of working directory

    magneto init --wd <working_directory (default = ".")>

This will set configuration files into `<working_directory>/config/` :

 - `config.yaml`, in which all parameters for the programs in the workflow may be set;
 - SGE/Slurm profiles, to run the workflow on clusters. Two versions are currently available, for SGE and Slurm, you can find them here : `<working_directory>/config/[sge or slurm]/config.yaml` (Certain details may need to be modified to reflect the specific characteristics of the cluster like queue or partition names.)
 - `cluster_[sge or slurm].yaml`, these files are used to specify the resources allocated for the workflow. It is completely modular and the resources can be adapted for each snakemake rule.

# Input data

Magneto supports both single-end and paired-end reads in fasta/fasta.gz/fastq/fastq.gz format. You will need to provide a file at yaml format listing your reads files, following the general patterns below :

For a sample file containing paired-end reads files :

If you have one run by sample :
```
<sample1>:
  <sample1>:
  - </path/to/sample1_1.fastq.gz>
  - </path/to/sample1_2.fastq.gz>
<sample2>:
  <...>
```

If you have multiple runs by sample :

```
<sample1>:
  <run1>:
  - </path/to/run1_1.fastq.gz>
  - </path/to/run1_2.fastq.gz>
  <run2>:
  - </path/to/run2_1.fastq.gz>
  - </path/to/run2_2.fastq.gz>
<sample2>:
  <...>
```

For a sample file containing single-ended reads files :

```
<sample1>:
  <run1>:
  - </path/to/run1.fastq.gz>
  <run2>:
  - </path/to/run2.fastq.gz>
<sample2>:
  <...>
```

Set the path of your sample file in the samples field of the config file (`<working_directory>/config/config.yaml`). You can find a template for sample files in `<working_directory>/config/samples.yaml`, which can be used for test. [(see section below)](#Test).

# Usage
The general command line is as following :
```
magneto run <submodule_name> <skip-qc> --strategies <strategies> --profile <profile> --rerun-incomplete <other snakemake args>
```  
With the submodules names :

 - `qc` performs reads trimmering, using fastp/fastqScreen;

 - `motus` performs taxonomic profiling of reads;

 - `assembly` performs the assembly of metagenomic reads to contigs, using Megahit;

 - `genes` performs functional and taxonomic annotation on contigs, to obtain the gene collection

 - `binning` performs binning of contigs to putative genomes, using metabat2;

 - `genomes` performs bins quality check and dereplication, using checkM and dRep;

 - `all` allows to run the complete workflow at once.

 - `metaT` can be run once you have genes collection and MAGs, it will map your associated metatranscriptomic reads on genes and MAGs.

`--skip-qc` allows to bypass the reads trimming step.

`--strategies` choose the strategy(ies) you are interested in (`SASB` (default), `SACB`, `CASB`, `CACB`). More informations on the different strategies [here](https://gitlab.univ-nantes.fr/bird_pipeline_registry/magneto/-/wikis/Modules/binning#binning-strategies).

A command line example is represented below:
```
magneto run all --strategies SASB,SACB --profile config/slurm/ --rerun-incomplete
```
The use of `--profile` allows to use Snakemake pre-configuration to run Magneto on clusters.
Use either the SGE of Slurm profile, depending on your system. By default, Snakemake will use the config.yaml file located in the specified folder (in this example, config/slurm).

More details [here](https://snakemake.readthedocs.io/en/stable/executing/cli.html#profiles).

# Test

To test the workflow you can use a test dataset found in zenodo : https://zenodo.org/records/17143360 

It consists of three samples from the HMP project. You are free to use one in SASB or several in SASB or CASB. 

A samples.yaml file is also included, which should be placed in the config directory of your working directory created with Magneto (a similar one already exists normally). 
All you have to do is modify it by uncommenting it according to the samples you want to use, and changing the path to the location of your data.


# Databases management

MAGNETO used dedicated databases to run fastp, checkm2, GTDB-tk... It downloads them automatically and stored them by default in `<working_directory>/Database`.
If you have already run MAGNETO in another working directory, you can reuse the databases you have already downloaded by changing the `database` path in the `config/config.yaml` file in your current working directory.

# Output

Output of the different steps will be stored in `<working_directory>` folder with following organization:

```
intermediate_results
|
|__reads
|   |
|   |__PE (for paired-end reads)
|   |__SE (for single-end reads)
|__assembly
|   |
|   |__single_assembly
|   |   |
|   |   |__megahit
|   |      |
|   |      |__<sample1>
|   |      |__<sample2>
|   |      |__ ...
|   |      |__<sampleN>
|   |__co_assembly
|      |
|      |__megahit
|      |  |
|      |  |__<cluster1>
|      |  |__<cluster2>
|      |  |__...
|      |  |__<clusterN>
|      |__simka (distance matrix computed between samples)
|      |__clusters (repartition of the samples in clusters inferred from matrix distances)
|__binning
|  |
|  |__single_binning
|  |  |
|  |  |__<bins>
|  |
|  |__co_binning
|  |  |
|  |  |__<bins>
|
motus_profiling
|
|__profiling
|
|__mOTU_table.tsv
|
genes_collection
|
|__annotations
|
|__mapping
|
|__tables
|
genomes_collection
|
|__annotations
|
|__data
|
|__dereplicated_at_0.95
|
|__dereplicated_at_0.99
|
|__mapping
|
|__tables
|
metaT
|
|__genes_collection
|
|__genomes_collection
|
|__tables
```

The final output of the workflow will be stored in `<working_directory>/genomes_collection` subfolder.
Graphics reports (notably from fastQscreen and multiQC) will be stored in `<working_directory>/reports`.

# Steps implemented

**Pre-processing:**
* [x]  QC (fastp and fastqscreen)
* [x]  merging (bbmerge)

**mOTU**
* [x]  motus profiling (motus)

**Assembly**
* [x]  single-assembly (megahit)
* [x]  metagenomic distance between samples (simka)
* [x]  co-assembly (megahit - [clustering : CAH  + silhouette])
* [x]  QC assembly and filtering (metacovest.py)
* [x]  missamblies detection (DeepMased for single assembly only at this time.)
* [x]  assembly taxonomic annotation (CAT)

**Genomes collection**
* [x]  single-binning from single-assembly
* [x]  single-binning from co-assembly
* [x]  co-binning from single-assembly
* [x]  co-binning from co-assembly
* [x]  filter out contigs not consistent with bin's assignment (from CATBAT results, homemade script) #require an update
* [x] improve collection with external genomes db.
* [x] checkM (by batch)
* [x] dRep (by batch, for every taxonomic level in theory - 0.95: species, 0.99: species)
* [x] dRep95 followed by dRep99 on 95 clusters
* [x] GTDB-TK
* [x] functional annotation (eggNOG-mapper)
* [x] genomes_length table
* [x] genomes\_reads_counts table
* [x] genomes\_bp_covered table
* [x] genomes\_abundance table
* [x] genomes\_function table
* [x] genomes\_taxo table

**Genes collection**
* [x] CDS prediction using prodigal per sample
* [x] concatenate all CDS
* [x] CDS clustering using linclust
* [x] read back mapping against genes collection
* [x] eggNOG_mapper
* [x] taxonomy using MMSEQ protocol (uniprot db as reference)

**Reports:**
* [x]  multiqc report (pre-processing)
* [x]  assembly report  #homemade


<img src="imgs/magneto_workflow.png" alt="MAGNETO workflow" width="50%"/>

# Citing the pipeline 
Churcheward B, Millet M, Bihouée A, Fertin G, Chaffron S.<br>
MAGNETO: An Automated Workflow for Genome-Resolved Metagenomics.<br>
mSystems. 2022 Jun 15:e0043222. doi: [10.1128/msystems.00432-22](https://doi.org/10.1128/msystems.00432-22)
