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/3_pipelines.md
+108Lines changed: 108 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,79 @@
3
3
By default, we run [nf-core](https://nf-co.re) pipelines. To run a pipeline, read
4
4
the official [documentation with an example](https://nf-co.re/configs/ku_sund_danhead).
5
5
6
+
## Basic workflow for running an nf-core pipeline
7
+
8
+
You will need at least 3 things to run a pipeline:
9
+
10
+
- A slurm (sbatch) script that will run the pipeline on one the computing nodes
11
+
- A parameter file which contains the options specific for your experiment
12
+
- A samplesheet, typically specific for the pipeline in question. Sometimes (such as is the case with the PRIME-seq pipeline), you will need a few more csv files
13
+
14
+
### The samplesheet
15
+
16
+
You will need to follow the instructions specific to the experiment you have done and pipeline you wish to run.
17
+
18
+
An example of an RNA-seq samplesheet is taken from the [nf-core website](https://nf-co.re/rnaseq/3.14.0/):
As good practice, place the full path of the FASTQ files, e.g.: /maps/projects/dan1/data/Brickman/assays/RNA_ABC_19700101/raw/SAMPLE_S1_L001_R1_001.fastq.gz
27
+
28
+
It might be easier to make this sheet in Excel and then export it as a csv file.
29
+
30
+
Save or copy this file as samplesheet.csv in your assay folder.
31
+
32
+
### Parameters
33
+
34
+
A params.yml file contains the options you can customise for your run or experiment.
If you see the following error in your nextflow.log or in tower:
105
+
106
+
```
107
+
Failed to pull singularity image
108
+
```
109
+
110
+
Then you need to force download the images you need to run the pipeline. Singularity images are specific to __both__ the computing server and the version of the pipeline.
111
+
112
+
Create an interactive session in the server you would like to send your pipeline to.
0 commit comments