Currently, in the second module, bismark_genome_preparation is run here as a required step upon first execution of the module (or whenever new annotation files are used). While this is not terribly problematic, it is a waste of time for many use cases, especially when MethylDackel is the preferred default tool to use for methylation extraction. Ideally, bismark_genome_preparation should only be run when new annotation is used AND the --use_bismark option is specified, very similarly to how lambda-pseudoalignment-related workflow steps are run conditionally based on specification of the --with_lambda option. This may require creation of a new process.
bismark_genome_preparation is only required for alignment with bismark, which isn't even performed by this pipeline. I've removed its usage entirely in this commit, making this issue obsolete.
Currently, in the second module,
bismark_genome_preparation
is run here as a required step upon first execution of the module (or whenever new annotation files are used). While this is not terribly problematic, it is a waste of time for many use cases, especially whenMethylDackel
is the preferred default tool to use for methylation extraction. Ideally,bismark_genome_preparation
should only be run when new annotation is used AND the--use_bismark
option is specified, very similarly to how lambda-pseudoalignment-related workflow steps are run conditionally based on specification of the--with_lambda
option. This may require creation of a new process.