If you reset a pipeline, and there some modules not yet reached, and you have added or removed any modules, then those old folders don't get replaced by corresponding modules in the new life of the pipeline, they hang around as duplicates.
These duplicates confuse the user and they can also confuse BioLockJ if the pipeline needs to be restarted again, because an older module will say "fail" while a newer module with a higher number says "complete".
When I pipeline is restarted, there is no real reason to hold onto module folders that just have an empty "biolockjFailed" file. It would be smoother to just remove them during the reset phase of a restart process.
If you reset a pipeline, and there some modules not yet reached, and you have added or removed any modules, then those old folders don't get replaced by corresponding modules in the new life of the pipeline, they hang around as duplicates.
These duplicates confuse the user and they can also confuse BioLockJ if the pipeline needs to be restarted again, because an older module will say "fail" while a newer module with a higher number says "complete".
When I pipeline is restarted, there is no real reason to hold onto module folders that just have an empty "biolockjFailed" file. It would be smoother to just remove them during the reset phase of a restart process.