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
I implemented a few modules in this pipeline that use a native NF Groovy process like here. It made sense to exploit the functionality on offer in Groovy to perform these sorts of tasks rather than wrapping them in an external script.
However, this results in these warnings being generated which are harmless but can be confusing to users who assume that there is an issue with the pipeline/infrastructure. The warning is generated because Nextflow will run these native / Groovy processes on the head node via the master NF job rather than a compute job.
WARN: Process 'NFCORE_RNASEQ:RNASEQ:MULTIQC_TSV_FAIL_MAPPED' cannot be executed by 'awsbatch' executor -- Using 'local' executor instead
WARN: Process 'NFCORE_RNASEQ:RNASEQ:MULTIQC_TSV_STRAND_CHECK' cannot be executed by 'awsbatch' executor -- Using 'local' executor instead
I implemented a few modules in this pipeline that use a native NF Groovy process like here. It made sense to exploit the functionality on offer in Groovy to perform these sorts of tasks rather than wrapping them in an external script.
However, this results in these warnings being generated which are harmless but can be confusing to users who assume that there is an issue with the pipeline/infrastructure. The warning is generated because Nextflow will run these native / Groovy processes on the head node via the master NF job rather than a compute job.
Ping @pditommaso 🏖️
The text was updated successfully, but these errors were encountered: