... | @@ -26,7 +26,6 @@ Each workflow is stored with the following structure: |
... | @@ -26,7 +26,6 @@ Each workflow is stored with the following structure: |
|
| └── Snakefile
|
|
| └── Snakefile
|
|
├── config
|
|
├── config
|
|
│ └── config.yaml
|
|
│ └── config.yaml
|
|
│
|
|
|
|
└── results
|
|
└── results
|
|
└── workflow
|
|
└── workflow
|
|
├── module1
|
|
├── module1
|
... | @@ -34,7 +33,6 @@ Each workflow is stored with the following structure: |
... | @@ -34,7 +33,6 @@ Each workflow is stored with the following structure: |
|
```
|
|
```
|
|
The workflow code goes into a subfolder `workflow`, while the configuration is stored in a subfolder `config`. Inside of the `workflow` subfolder, the central `Snakefile` marks the entrypoint of the workflow. Results are written into subfolder `results. Inside of the `results` subfolder, results are stored following the same structure than inside `workflow` subfolder.
|
|
The workflow code goes into a subfolder `workflow`, while the configuration is stored in a subfolder `config`. Inside of the `workflow` subfolder, the central `Snakefile` marks the entrypoint of the workflow. Results are written into subfolder `results. Inside of the `results` subfolder, results are stored following the same structure than inside `workflow` subfolder.
|
|
|
|
|
|
|
|
|
|
# Environment
|
|
# Environment
|
|
|
|
|
|
Softwares and dependencies can be run directly on the local system or using environments such as containers or using a package management system.
|
|
Softwares and dependencies can be run directly on the local system or using environments such as containers or using a package management system.
|
... | | ... | |