... | ... | @@ -149,26 +149,23 @@ We use [snakemake](https://snakemake.readthedocs.io/en/stable/), a workflow mana |
|
|
|
|
|
## Environment
|
|
|
|
|
|
|
|
|
Softwares and dependencies can be run directly using environments such as containers or package management system.
|
|
|
|
|
|
### Containers
|
|
|
|
|
|
[](https://singularity-hub.org/collections/2878)
|
|
|
|
|
|
We provide ready to run versions of container built with [Singularity containers](https://www.sylabs.io/). All required softwares to run the workflow have been installed within this container.
|
|
|
|
|
|
We provide ready to run versions of [Singularity containers](https://www.sylabs.io/). All softwares you need to run the workflow have been installed into a container.
|
|
|
User can either download the ready-to-use built container OR build this container instead to download it using the [Singularity.obitools](Singularity.obitools) recipe.
|
|
|
|
|
|
To download this container :
|
|
|
```
|
|
|
singularity pull --name obitools.simg shub://Grelot/bioinfo_singularity_recipes:obitools
|
|
|
```
|
|
|
You will get a file named `obitools.simg`. Snakemake will need it to run softwares it contains.
|
|
|
In both case, it gives an `obitools.simg` file. Absolute path to access to the container file fills the field `singularity:` into [config.yaml](config/)
|
|
|
|
|
|
|
|
|
|
|
|
### Conda
|
|
|
|
|
|
|
|
|
## Wildcards
|
|
|
|
|
|
|
... | ... | |