|
3 | 3 |
|
4 | 4 | ```{toctree} |
5 | 5 | :hidden: |
6 | | -
|
7 | | -about/purpose |
8 | | -about/using_workflows |
9 | | -about/adding_workflows |
10 | | -about/contributions |
11 | 6 | ``` |
12 | 7 |
|
13 | 8 | Here you can find the most important information about the **Snakemake workflow catalog**. |
14 | 9 |
|
15 | | -*Estimated reading time: 5 minutes*. |
16 | | - |
17 | | -::: |
18 | | -## Use a workflow from the catalog |
19 | | -::: |
20 | | - |
21 | | -1. Clone the repository or download the specific workflow directory. |
22 | | - |
23 | | -```bash |
24 | | -git clone https://github.com/<user>/<workflow> |
| 10 | +```{include} about/purpose.md |
25 | 11 | ``` |
26 | 12 |
|
27 | | -2. Review the documentation provided with the workflow to understand its requirements and usage. |
28 | | - |
29 | | -3. Configure the workflow by editing the `config.yml` files as needed. |
30 | | - |
31 | | -4. Create an environment with access to Snakemake. It is recommended to use `mamba`. |
32 | | - |
33 | | -```bash |
34 | | -mamba create -n <env-name> -c <channels> snakemake |
35 | | -mamba activate <env-name> |
| 13 | +```{include} about/using_workflows.md |
36 | 14 | ``` |
37 | 15 |
|
38 | | -5. Execute the workflow using Snakemake. |
39 | | - |
40 | | -```bash |
41 | | -cd <workflow-dir> |
42 | | -snakemake --cores 2 |
| 16 | +```{include} about/adding_workflows.md |
43 | 17 | ``` |
44 | 18 |
|
45 | | -:::tip Dry-run |
46 | | - |
47 | | -Use the `--dry-run` option first to check if all inputs are found. |
48 | | - |
49 | | -::: |
50 | | - |
51 | | -For more detailed instructions, please refer to the individual documentation for each [workflow](workflows/top_wf_by_stars.mdx). |
52 | | - |
53 | | -::: |
54 | | -## Add a workflow to the catalog |
55 | | -::: |
56 | | - |
57 | | -Workflows are **automatically added** to the Workflow Catalog. This is done by regularly searching Github repositories for matching workflow structures. The catalog includes workflows based on the following criteria. |
58 | | - |
59 | | -The catalog currently discriminates between two types of workflows based on their documentation: |
60 | | - |
61 | | -**Generic workflows** |
62 | | - |
63 | | -- all snakemake workflows in public Github repositories |
64 | | -- repositories need to have a `README.md` file containing the words "snakemake" and "workflow" |
65 | | -- also need to have a workflow definition named either `Snakefile` or `workflow/Snakefile`, and contain rules in `*.smk` format. |
66 | | - |
67 | | -**Standardized Usage workflows** |
68 | | - |
69 | | -- workflows that additionally adhere to standards of the workflow catalog |
70 | | -- main workflow definition must be named `workflow/Snakefile` |
71 | | -- provide configuration instructions under `config/README.md` |
72 | | -- contain a `.snakemake-workflow-catalog.yml` file with instructions on deployment options |
| 19 | +```{include} about/contributions.md |
| 20 | +``` |
0 commit comments