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
Whilst I find the way published files are organised helpful for debugging as they replicate the pipeline structure, having to replicate the whole directive for each process over and over seems quite odd.
Usage scenario
Avoid having to replicate publishDir directive configuration for each process.
Suggest implementation
I came across with this post: #3107 (comment) .
It would be nice to code the publishDir directive in the process block in nextflow.config, e.g.:
process {
// General publishDir setting
publishDir = [
path: { "${params.output_path}/${task.process.replaceAll(":", "/")}" },
mode: "copy",
overwrite: true
]
}
and then the actual process code to be:
process fastq2bam {
publishDir pattern: '*.bam' // the rest inherited from the config above
// as code above
}
p.s. specifying the patter is redundant in this case as it is the only output file, however it can be helpful in general.
The text was updated successfully, but these errors were encountered:
New feature
In the current pipeline I am working on, processes use the following publishDir directive:
Whilst I find the way published files are organised helpful for debugging as they replicate the pipeline structure, having to replicate the whole directive for each process over and over seems quite odd.
Usage scenario
Avoid having to replicate publishDir directive configuration for each process.
Suggest implementation
I came across with this post: #3107 (comment) .
It would be nice to code the publishDir directive in the process block in nextflow.config, e.g.:
and then the actual process code to be:
p.s. specifying the patter is redundant in this case as it is the only output file, however it can be helpful in general.
The text was updated successfully, but these errors were encountered: