You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/usage/bulk_tutorial.md
+21-9Lines changed: 21 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,15 +6,17 @@ This tutorial provides a step by step introduction on how to run nf-core/airrflo
6
6
7
7
You can run this tutorial using the Github Codespaces platform. Codespaces already has Nextflow and Singularity pre-installed, and it can automatically be used for every nf-core repository. To create a Codespace instance for nf-core/airrflow, first click on the button labelled `Code` at the top of [nf-core/airrflow repository](https://github.com/nf-core/airrflow).
8
8
9
-
In the dropdown menu, go to the `Codespaces` tab. You can create a basic "2-core" Codespace by clicking the `+` icon. However, as more CPUs and memories are needed for nf-core/airrflow task, you need to press the `...` sign and choose`+ New with options...`.
9
+
In the dropdown menu, go to the `Codespaces` tab. Click the `...` sign, then select`+ New with options...`.
10
10
11
11

12
12
13
-
Afterwards, you will be directed to another page to choose the setting of your platform. Select `4-core` for `machine type`, which will give you 4 CPUs, 16GB RAM and 32GB space.
13
+
After that, you’ll be directed to the configuration page. Select "4-core" for `machine type`, which will give you 4 CPUs, 16GB RAM and 32GB space.
14
14
15
15

16
16
17
-
If you want to know more about Codespaces, check [the Codespaces overview](https://docs.github.com/en/codespaces/about-codespaces/what-are-codespaces) or the Codespaces part in [the Devcontainers overview](https://nf-co.re/docs/tutorials/devcontainer/overview).
17
+
If you want to know more about Codespaces, check [the Codespaces overview](https://docs.github.com/en/codespaces/about-codespaces/what-are-codespaces) or the Codespaces section in nf-core documentation [the Devcontainers overview](https://nf-co.re/docs/tutorials/devcontainer/overview).
18
+
19
+
When running this tutorial on your local machine, you'll first have to set up Nextflow and a container engine (Docker or Singularity).
18
20
19
21
> [!NOTE]
20
22
> If you want to run this tutorial on your local machine, please refer to [this page](https://nf-co.re/docs/usage/installation) on how to set up Nextflow and a container engine needed to run this pipeline. At the moment, nf-core/airrflow does NOT support using conda virtual environments for dependency management, only containers are supported. Make sure to [test your setup](https://nf-co.re/docs/usage/introduction#how-to-run-a-pipeline) before running the workflow on actual data. To install Docker, follow the [instructions](https://docs.docker.com/engine/install/). After installation Docker on Linux, don't forget to check the [post-installation steps](https://docs.docker.com/engine/install/linux-postinstall/).
@@ -26,7 +28,14 @@ Once you have set up Nextflow and container (Docker or Singularity) for your loc
26
28
```bash
27
29
nextflow run nf-core/airrflow -r 4.3.1 -profile test,docker --outdir test_results
28
30
```
29
-
Change the `docker` profile to `singularity` if you use Codespace since The docker profile currently does not work in Codespaces.
31
+
Change the `docker` profile to `singularity` if you use Codespaces since Docker currently cannot be used in Codespaces. You can first set up a Singularity cache directory which will allow the reuse of Singularity container across all runs:
> The '-r' flag in the command specifies which nf-core/airrflow release to run. We recommend always [checking](https://nf-co.re/airrflow/releases_stats/) and using the latest release.
37
46
47
+
> [!NOTE]
48
+
> Because Codespaces provides limited CPU and RAM resources, the test run may take 20-25 minutes. The process will be faster on systems with greater CPU and RAM capacity.
49
+
38
50
If the tests run through correctly, you should see this output in your command line:
> Before setting memory and cpus in the configuration file, we recommend verifying the available memory and cpus on your system. Otherwise, exceeding the system's capacity may result in an error indicating that you requested more cpus than available or run out of memory.
78
+
> Before setting memory and CPUs in the configuration file, we recommend verifying the available memory and CPUs on your system. Otherwise, exceeding the system's capacity may result in an error indicating that you requested more CPUs than available or run out of memory.
67
79
68
80
> [!NOTE]
69
81
> When running nf-core/airrflow with your own data, provide the full path to your input files under the filename column.
70
82
71
-
We prepared the [samplesheet](https://github.com/nf-core/airrflow/tree/dev/docs/usage/bulk_tutorial/bulk_sample_code/metadata_pcr_umi_airr_300.tsv) and the [configuration file](https://github.com/nf-core/airrflow/tree/dev/docs/usage/bulk_tutorial/bulk_sample_code/resource.config) for this tutorial. If you run the pipeline locally, download both files to the directory where you intend to run nf-core/airrflow.
83
+
We prepared the [samplesheet](https://github.com/nf-core/airrflow/tree/dev/docs/usage/bulk_tutorial/bulk_sample_code/metadata_pcr_umi_airr_300.tsv) and the [configuration file](bulk_tutorial/bulk_sample_code/resource.config) for this tutorial. If you run the pipeline locally, download both files to the directory where you intend to run nf-core/airrflow.
Copy file name to clipboardExpand all lines: docs/usage/single_cell_tutorial.md
+25-25Lines changed: 25 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,51 +6,55 @@ This tutorial provides a step by step introduction on how to run nf-core/airrflo
6
6
7
7
You can run this tutorial using the Github Codespaces platform. Codespaces already has Nextflow and Singularity pre-installed, and it can automatically be used for every nf-core repository. To create a Codespace instance for nf-core/airrflow, first click on the button labelled `Code` at the top of [nf-core/airrflow repository](https://github.com/nf-core/airrflow).
8
8
9
-
In the dropdown menu, go to the `Codespaces` tab. After clicking on the `...` sign, and the`+ New with options...` button.
9
+
In the dropdown menu, go to the `Codespaces` tab. Click the `...` sign, then select`+ New with options...`.
10
10
11
11

12
12
13
-
Choose the setting of your platform. Select "4-core" for `machine type`, which will give you 4 CPUs, 16GB RAM and 32GB space.
13
+
After that, you’ll be directed to the configuration page. Select "4-core" for `machine type`, which will give you 4 CPUs, 16GB RAM and 32GB space.
14
14
15
15

16
16
17
-
If you want to know more about Codespaces, check [the Codespaces overview](https://docs.github.com/en/codespaces/about-codespaces/what-are-codespaces) or the Codespaces section in [the Devcontainers overview](https://nf-co.re/docs/tutorials/devcontainer/overview) nf-core documentation.
17
+
If you want to know more about Codespaces, check [the Codespaces overview](https://docs.github.com/en/codespaces/about-codespaces/what-are-codespaces) or the Codespaces section in nf-core documentation [the Devcontainers overview](https://nf-co.re/docs/tutorials/devcontainer/overview).
18
18
19
-
The Codespaces environment already comes with Singularity and Nextflow pre-installed. When running this tutorial on your local machine, you'll first have to set up Nextflow and a container engine (Docker or Singularity).
19
+
When running this tutorial on your local machine, you'll first have to set up Nextflow and a container engine (Docker or Singularity).
20
20
21
21
> [!NOTE]
22
22
> If you want to run this tutorial on your local machine, please refer to [this page](https://nf-co.re/docs/usage/installation) on how to set up Nextflow and a container engine needed to run this pipeline. At the moment, nf-core/airrflow does NOT support using conda virtual environments for dependency management, only containers are supported. To install Docker, follow the [instructions](https://docs.docker.com/engine/install/). After installation Docker on Linux, don't forget to check the [post-installation steps](https://docs.docker.com/engine/install/linux-postinstall/).
23
23
24
24
## Testing the pipeline with built-in tests
25
25
26
-
Once you have set up Nextflow and container (Docker or Singularity) for your local machine or Codespace environment, test nf-core/airrflow with the built-in test data.
26
+
Once you have set up Nextflow and container (Docker or Singularity) for your local machine or Codespaces environment, test nf-core/airrflow with the built-in test data.
27
27
28
28
```bash
29
-
nextflow run nf-core/airrflow -r 4.3.1 -profile test_assembled_hs,docker --outdir test_results
29
+
nextflow run nf-core/airrflow -r 4.3.1 -profile test,docker --outdir test_results
30
30
```
31
-
Change the `docker` profile to `singularity` if you use Codespaces since Docker currently cannot be used in Codespaces.
32
-
33
-
We can first set up a Singularity cache directory. This will allow us to reuse the containers across all runs:
31
+
Change the `docker` profile to `singularity` if you use Codespaces since Docker currently cannot be used in Codespaces. You can first set up a Singularity cache directory which will allow the reuse of Singularity container across all runs:
nextflow run nf-core/airrflow -r 4.3.1 -profile test_assembled_hs,singularity --outdir test_results
41
+
nextflow run nf-core/airrflow -r 4.3.1 -profile test,singularity --outdir test_results
41
42
```
42
43
43
44
> [!NOTE]
44
45
> The '-r' flag in the command specifies which nf-core/airrflow release to run. We recommend always [checking](https://nf-co.re/airrflow/releases_stats/) and using the latest release.
45
46
47
+
> [!NOTE]
48
+
> Because Codespaces provides limited CPU and RAM resources, the test run may take 20-25 minutes. The process will be faster on systems with greater CPU and RAM capacity.
49
+
46
50
If the tests run through correctly, you should see this output in your command line:
@@ -80,21 +84,18 @@ The samplesheet collects experimental details that are important for the data an
80
84
81
85
Details on the required columns of a samplesheet are available [here](https://nf-co.re/airrflow/usage#assembled-input-samplesheet-bulk-or-single-cell-sequencing).
82
86
83
-
The resource configuration file sets the compute infrastructure maximum available number of CPUs, RAM memory and running time. This will ensure that no pipeline process requests more resources than available in the compute infrastructure where the pipeline is running. The resource config should be provided with the `-c` option. In this example we set the maximum RAM memory to 16GB, we restrict the pipeline to use 4 CPUs and to run for a maximum of 24 hours.
87
+
The resource configuration file sets the compute infrastructure maximum available number of CPUs, RAM memory and running time. This will ensure that no pipeline process requests more resources than available in the compute infrastructure where the pipeline is running. The resource config should be provided with the `-c` option. In this example we set the maximum RAM memory to 15GB, we restrict the pipeline to use 4 CPUs and to run for a maximum of 24 hours.
We prepared the [samplesheet](https://github.com/nf-core/airrflow/blob/dev/docs/usage/single_cell_tutorial/sample_data_code/assembled_samplesheet.tsv) and the [configuration file](https://github.com/nf-core/airrflow/blob/dev/docs/usage/single_cell_tutorial/sample_data_code/resource.config) for this tutorial. Download both files to the directory where you intend to run nf-core/airrflow.
95
+
We prepared the [samplesheet](https://github.com/nf-core/airrflow/blob/dev/docs/usage/single_cell_tutorial/sample_data_code/assembled_samplesheet.tsv) and the [configuration file](single_cell_tutorial/sample_data_code/resource.config) for this tutorial. Download both files to the directory where you intend to run nf-core/airrflow.
95
96
96
97
> [!TIP]
97
-
> Before setting memory and cpus in the configuration file, we recommend verifying the available memory and cpus on your system. Otherwise, exceeding the system's capacity may result in an error indicating that you requested more cpus than available or run out of memory. You can also remove the "time" parameter from the configuration file to allow for unlimited runtime for large-size dataset.
98
+
> Before setting memory and CPUs in the configuration file, we recommend verifying the available memory and CPUs on your system. Otherwise, exceeding the system's capacity may result in an error indicating that you requested more CPUs than available or run out of memory. You can also remove the "time" parameter from the configuration file to allow for unlimited runtime for large-size dataset.
98
99
99
100
> [!NOTE]
100
101
> When running nf-core/airrflow with your own data, provide the full path to your input files under the filename column.
@@ -113,7 +114,7 @@ nextflow run nf-core/airrflow -r 4.3.1 \
113
114
-resume
114
115
```
115
116
116
-
Of course you can wrap all your code in a [bash file](https://github.com/nf-core/airrflow/blob/dev/docs/usage/single_cell_tutorial/sample_data_code/airrflow_sc_from_assembled.sh). With the bash file, it's easy to run the pipeline with a single-line command.
117
+
Of course you can wrap all your code in a [bash file](single_cell_tutorial/sample_data_code/airrflow_sc_from_assembled.sh). With the bash file, it's easy to run the pipeline with a single-line command.
117
118
118
119
```bash
119
120
bash airrflow_sc_from_assembled.sh
@@ -177,7 +178,7 @@ To run nf-core/airrflow on single cell TCR or BCR sequencing data from fastq fil
177
178
We prepared the [samplesheet](https://github.com/nf-core/airrflow/blob/dev/docs/usage/single_cell_tutorial/sample_data_code/10x_sc_raw.tsv) and the [configuration file](https://github.com/nf-core/airrflow/blob/dev/docs/usage/single_cell_tutorial/sample_data_code/resource.config) for this tutorial. Download these two files to the directory where you intend to run nf-core/airrflow.
178
179
179
180
> [!TIP]
180
-
> Before setting memory and cpus in the configuration file, we recommend verifying the available memory and cpus on your system. Otherwise, exceeding the system's capacity may result in an error indicating that you requested more cpus than available or run out of memory.
181
+
> Before setting memory and CPUs in the configuration file, we recommend verifying the available memory and CPUs on your system. Otherwise, exceeding the system's capacity may result in an error indicating that you requested more CPUs than available or run out of memory.
181
182
182
183
Pre-built 10x genomics V(D)J references can be accessed at the [10x Genomics website](https://www.10xgenomics.com/support/software/cell-ranger/downloads). Both human and mouse V(D)J references are available. Download the reference that corresponds to the species of your dataset.
183
184
@@ -200,7 +201,7 @@ nextflow run nf-core/airrflow -r 4.3.1 \
200
201
201
202
In this tutorial, since the samples are TCRs, which do not have somatic hypermutation, clones are defined strictly by identical junction regions. For this reason, we set the `--clonal_threshold` parameter to 0. For more details on important considerations when performing clonal analysis check [FAQ](./FAQ.md).
202
203
203
-
Of course you can wrap all your code in a bash file. We prepared one for you and it's available [here](https://github.com/nf-core/airrflow/blob/dev/docs/usage/single_cell_tutorial/sample_data_code/airrflow_sc_from_fastq.sh).
204
+
Of course you can wrap all your code in a bash file. We prepared one for you and it's available [here](single_cell_tutorial/sample_data_code/airrflow_sc_from_fastq.sh).
204
205
With the bash file, it's easy to run the pipeline with a single-line command.
> Due to the limited RAM and storage space, the single cell raw reads example in this tutorial cannot be run on Codespace.
212
-
```bash
213
213
214
214
After launching the pipeline the following will be printed to the console output, followed by some the default parameters used by the pipeline and execution log of airrflow processes:
0 commit comments