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: .github/PULL_REQUEST_TEMPLATE.md
+1-2
Original file line number
Diff line number
Diff line change
@@ -15,8 +15,7 @@ Learn more about contributing: [CONTRIBUTING.md](https://github.com/nf-core/isos
15
15
16
16
-[ ] This comment contains a description of changes (with reason).
17
17
-[ ] If you've fixed a bug or added code that should be tested, add tests!
18
-
-[ ] If you've added a new tool - have you followed the pipeline conventions in the [contribution docs](https://github.com/nf-core/isoseq/tree/master/.github/CONTRIBUTING.md)
19
-
-[ ] If necessary, also make a PR on the nf-core/isoseq _branch_ on the [nf-core/test-datasets](https://github.com/nf-core/test-datasets) repository.
18
+
-[ ] If you've added a new tool - have you followed the pipeline conventions in the [contribution docs](https://github.com/nf-core/isoseq/tree/master/.github/CONTRIBUTING.md)- [] If necessary, also make a PR on the nf-core/isoseq _branch_ on the [nf-core/test-datasets](https://github.com/nf-core/test-datasets) repository.
20
19
-[ ] Make sure your code lints (`nf-core lint`).
21
20
-[ ] Ensure the test suite passes (`nextflow run . -profile test,docker --outdir <OUTDIR>`).
22
21
-[ ] Usage Documentation in `docs/usage.md` is updated.
[](https://github.com/nf-core/isoseq/actions?query=workflow%3A%22nf-core+CI%22)
[](https://doi.org/10.5281/zenodo.XXXXXXX)
3
+
[](https://nf-co.re/isoseq/results)[](https://doi.org/10.5281/zenodo.XXXXXXX)
[](https://docs.conda.io/en/latest/)
10
-
[](https://www.docker.com/)
11
-
[](https://sylabs.io/docs/)
6
+
[](https://docs.conda.io/en/latest/)
7
+
[](https://www.docker.com/)
8
+
[](https://sylabs.io/docs/)
12
9
[](https://tower.nf/launch?pipeline=https://github.com/nf-core/isoseq)
13
10
14
-
[](https://nfcore.slack.com/channels/isoseq)
15
-
[](https://twitter.com/nf_core)
16
-
[](https://www.youtube.com/c/nf-core)
11
+
[](https://nfcore.slack.com/channels/isoseq)[](https://twitter.com/nf_core)[](https://www.youtube.com/c/nf-core)
17
12
18
13
## Introduction
19
14
@@ -54,7 +49,7 @@ On release, automated continuous integration tests run the pipeline on a full-si
54
49
55
50
3. Download the pipeline and test it on a minimal dataset with a single command:
56
51
57
-
```console
52
+
```bash
58
53
nextflow run nf-core/isoseq -profile test,YOURPROFILE --outdir <OUTDIR>
59
54
```
60
55
@@ -67,7 +62,7 @@ On release, automated continuous integration tests run the pipeline on a full-si
67
62
68
63
4. Start running your own analysis!
69
64
70
-
```console
65
+
```bash
71
66
nextflow run nf-core/isoseq --input samplesheet.csv --outdir <OUTDIR> --genome <GENOME NAME (e.g. GRCh37)> --primers <PRIMER FASTA> -profile <docker/singularity/podman/shifter/charliecloud/conda/institute>
Copy file name to clipboardExpand all lines: docs/usage.md
+7-7
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ This pipeline has been designed to analyse several samples or sequencing runs at
12
12
13
13
You will need to create a samplesheet with information about the samples you would like to analyze before running the pipeline. Use `--input` parameter to specify its location.
14
14
15
-
```console
15
+
```bash
16
16
--input '[path to samplesheet file]'
17
17
```
18
18
@@ -66,24 +66,24 @@ The reference genome annotation in `GTF` format is required if `uLTRA` aligner i
66
66
Two aligners are available. The `uLTRA` aligner helps to detect small exons with the help of reference genome. However if no annotation is available for your genome you can use minimap2.
67
67
68
68
```console
69
-
--fasta '[ultra,minimap2]'
69
+
--aligner '[ultra,minimap2]'
70
70
```
71
71
72
72
## Running the pipeline
73
73
74
74
The typical command for running the pipeline is as follows:
This will launch the pipeline with the `singularity` configuration profile. See below for more information about profiles.
81
81
82
82
Note that the pipeline will create the following files in your working directory:
83
83
84
-
```console
84
+
```bash
85
85
work # Directory containing the nextflow working files
86
-
<OUTIDR> # Finished results in specified location (defined with --outdir, default = 'results')
86
+
<OUTDIR># Finished results in specified location (defined with --outdir)
87
87
.nextflow_log # Log file from Nextflow
88
88
# Other nextflow hidden files, eg. history of pipeline runs and old logs.
89
89
```
@@ -92,7 +92,7 @@ work # Directory containing the nextflow working files
92
92
93
93
When you run the above command, Nextflow automatically pulls the pipeline code from GitHub and stores it as a cached version. When running the pipeline after this, it will always use the cached version if available - even if the pipeline has been updated since. To make sure that you're running the latest version of the pipeline, make sure that you regularly update the cached version of the pipeline:
94
94
95
-
```console
95
+
```bash
96
96
nextflow pull nf-core/isoseq
97
97
```
98
98
@@ -268,6 +268,6 @@ Some HPC setups also allow you to run nextflow within a cluster job submitted yo
268
268
In some cases, the Nextflow Java virtual machines can start to request a large amount of memory.
269
269
We recommend adding the following line to your environment to limit this (typically in `~/.bashrc` or `~./bash_profile`):
0 commit comments