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

Commit c8889ee

Browse files
authored
Update nextflow-overview.md
1 parent 721ae6e commit c8889ee

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/orchestration/nextflow/nextflow-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -383,7 +383,7 @@ aws batch submit-job \
383383
"--skip_qc"
384384
```
385385

386-
For the nf-core 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.
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

0 commit comments

Comments
 (0)