You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The request is to have nextflow clean out the directories for a given process, so that on resumption this process and anything dependent on it will be redone. Ideally this would by default be done for all nextflow runs that were instigated in the current directory. A possibility now is to do this:
I have scripted this in the simplest way possible to do this for all runs that were executed in a study, but ideally nextflow would be in control of this. The reason this is very useful to me is:
Software changes often and sometimes we need to run the latest software; this is especially true for downstream analysis. If we have already done the heavy lifting (upstream) of aligning reads it would be nice to re-use the upstream stages.
I have had cases where a few samples failed and required newer software. Consistency requires that all samples are then run with this updated software.
The text was updated successfully, but these errors were encountered:
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.
The request is to have nextflow clean out the directories for a given process, so that on resumption this process and anything dependent on it will be redone. Ideally this would by default be done for all nextflow runs that were instigated in the current directory. A possibility now is to do this:
nextflow log <run name> -F 'process =~ /foo.*/' | xargs rm -rf
I have scripted this in the simplest way possible to do this for all runs that were executed in a study, but ideally nextflow would be in control of this. The reason this is very useful to me is:
The text was updated successfully, but these errors were encountered: