If you intend to modify and further extend this workflow or want to work under version control, fork this repository as outlined in [Advanced](#advanced). The latter way is recommended.
In any case, if you use this workflow in a paper, don't forget to give credits to the authors by citing the URL of this repository and, if available, its DOI (see above).
#### Step 2: Create minimal environment
Some rules will use this environment.
conda env create -f ./envs/MetaSnk.yaml
#### Step 2: Configure workflow
Configure the workflow according to your needs via editing the file `config.yaml`.
##### Basic configuration
- Make a copy of the config.yaml:
```
cp ./config.yaml path/to/my_config.yaml
```
#### Step 3: Execute workflow
Activate the environment via
conda activate MetaSnk
Test your configuration by performing a dry-run via
snakemake --use-conda -n
snakemake --use-singularity -n
Execute the workflow locally via
snakemake --use-conda --cores $N
snakemake --use-singularity --cores $N
using `$N` cores or run it in a cluster environment via
using `$N` cores or run it in a cluster environment controlled by SGE (Sun Grid Engine) via
--directory : specifies the working directory and it is where snakemake will store its files for tracking the status of the workflow before/during/after execution.
After preQC is completed we can generate a html report:
--directory : specifies the working directory and it is where snakemake will store its files for tracking the status of the workflow before/during/after execution.
After rawQC is completed we can generate a html report: