I defined requested the genome-prep files to become write-protected, to prohibit accidential re-evaluation of this long-running step. This also makes it safer to use shared genome folders.
However, what is quite annoying for quick dry-run-testing using a --forced run, is that the pipeline will always fail with a ProtectedOutputException since we are using snakemakes --forceall, -F, which forces the execution of the selected (or the first) rule and all rules it is dependent on regardless of already created output.
I would like to keep the write-protection, but have the feeling that for the dev environment this feature has to be disabled.
I defined requested the genome-prep files to become write-protected, to prohibit accidential re-evaluation of this long-running step. This also makes it safer to use shared genome folders. However, what is quite annoying for quick dry-run-testing using a
--forced run, is that the pipeline will always fail with a ProtectedOutputException since we are using snakemakes--forceall, -F, which forces the execution of the selected (or the first) rule and all rules it is dependent on regardless of already created output.I would like to keep the write-protection, but have the feeling that for the dev environment this feature has to be disabled.