When using the -resume option, it would be helpful to see which processes are going to be run and which will be reused from the cache.
Additionally it would be useful to indicate which hashes have changed requiring a cached process to be run. I know this can be done manually with the -dump-hashes option but this is not very user friendly.
jemunro
All 9 comments
Yes, it could have sense to have a kind of dry-run showing the which cached tasks would be used.
pditommaso
on 28 Aug 2018
+1! Would be super useful!
fmorency
on 7 Jan 2019
Just thoughts.
Dry-run or plan should be used to produce the full graph structure or just a part of DAG in text or UI mode. It should use fail-fast behavior while constructing AST. The parts of AST can be validated by json schema validator as a workaround.
nextflow plan -target=process.1A_prepare_genome_samtools
nextflow plan -target=module.'rnaseq.nf'.fastqc
blacky0x0
on 20 Feb 2019
was this ever implemented?
stevekm
on 14 Jan 2020
Is dry-run or plan feature available in the latest nexflow version?
kopardev
on 21 Feb 2020
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![stale[bot] picture](https://avatars3.githubusercontent.com/in/1724?v=4&s=40)
stale[bot]
on 27 Apr 2020
Would still love this
jimhavrilla
on 25 Jun 2020
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stale[bot]
on 23 Nov 2020
Nextflow now supports the ability to simulate the execution using command stubs. See #1774.
More here https://www.nextflow.io/docs/edge/process.html#stub
pditommaso
on 23 Nov 2020
Related issues
wflynny
路
6Comments
MaxUlysse
路
3Comments
olgabot
路
7Comments
ewels
路
3Comments
jaquol
路
7Comments
Most helpful comment
Yes, it could have sense to have a kind of dry-run showing the which cached tasks would be used.