Skip to content
This repository was archived by the owner on Aug 9, 2023. It is now read-only.

Commit 7519e3f

Browse files
authored
Merge pull request #116 from jennomics/master
updating rnaseq demo workflow
2 parents 3a07d25 + c8889ee commit 7519e3f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/orchestration/nextflow/nextflow-overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -370,22 +370,22 @@ aws batch submit-job \
370370
After submitting a workflow, you can monitor the progress of tasks via the AWS Batch console.
371371
For the "Hello World" workflow above you will see five jobs run in Batch - one for the head node, and one for each `Channel` text as it goes through the `hello` process.
372372

373-
For a more complex example, you can try the following, which will run the [RNASeq workflow](https://nf-co.re/rnaseq) developed by the [NF-Core project](https://nf-co.re/) against data in the [1000 Genomes AWS Public Dataset](https://registry.opendata.aws/1000-genomes/):
373+
For a more complex example, you can try the following, which will run a demo [RNASeq workflow](https://github.com/nextflow-io/rnaseq-nf) against data in the [1000 Genomes AWS Public Dataset](https://registry.opendata.aws/1000-genomes/):
374374

375375
```bash
376376
aws batch submit-job \
377377
--job-name nf-core-rnaseq \
378378
--job-queue <queue-name> \
379379
--job-definition nextflow-<nextflow-stack-namespace> \
380-
--container-overrides command=nf-core/rnaseq,\
380+
--container-overrides command=rnaseq-nf,\
381381
"--reads","'s3://1000genomes/phase3/data/HG00243/sequence_read/SRR*_{1,2}.filt.fastq.gz'",\
382382
"--genome","GRCh37",\
383383
"--skip_qc"
384384
```
385385

386-
For the nf-core example "rnaseq" workflow you will see 11 jobs run in Batch over the course of a couple hours - the head node will last the whole duration of the pipeline while the others will stop once their step is complete. You can look at the CloudWatch logs for the head node job to monitor workflow progress. Note the additional single quotes wrapping the 1000genomes path.
386+
For the example "rnaseq" workflow you will see 5 jobs run in Batch over the course of a couple hours - the head node will last the whole duration of the pipeline while the others will stop once their step is complete. You can look at the CloudWatch logs for the head node job to monitor workflow progress. Note the additional single quotes wrapping the 1000genomes path.
387387

388388
In both of the examples above, submitting workflows is an asynchronous task allowing you to quickly move on to other tasks. Importantly, AWS Batch handled scaling up all the compute needed to run workflow jobs, and when the workflow was complete, AWS Batch scaled all compute resources back down.
389389

390390
## Cost optimizing workflows
391-
[Optimizing](../cost-effective-workflows/cost-effective-workflows.md) the allocation of resources to your workflows can help you to reduce costs
391+
[Optimizing](../cost-effective-workflows/cost-effective-workflows.md) the allocation of resources to your workflows can help you to reduce costs

0 commit comments

Comments
 (0)