Being lazy by not checking, but as we're here - ho...
# wg-meta-pipelinesp
Phil Ewels
03/21/2025, 9:08 AMBeing lazy by not checking, but as we're here - how does it work with config inheritance? Does it do anything clever to pass on config from the main Nextflow job to all of the children?
m
Mahesh Binzer-Panchal
03/21/2025, 9:41 AMThe configs are written separately for each child workflow and then passed as a regular file
Mahesh Binzer-Panchal
03/21/2025, 9:43 AMI haven't tried separating configs and using
includeConfigMahesh Binzer-Panchal
03/21/2025, 9:50 AMThe idea is to mainly use
profiles👍🏻 1
p
Phil Ewels
03/21/2025, 10:05 AMIt'd be cool if the head nextflow job could dump the resolved config, then pass that on to the child jobs as a config file 🤔 😅
m
Mahesh Binzer-Panchal
03/21/2025, 10:06 AMI'm not sure I understand what you mean. The parent workflow likely has very little configuration since unless it has processes itself to distribute
p
Phil Ewels
03/21/2025, 10:08 AMI was thinking of AWS batch configs etc.
m
Mahesh Binzer-Panchal
03/21/2025, 10:08 AMI don't know what they look like
p
Phil Ewels
03/21/2025, 10:09 AMPhil Ewels
03/21/2025, 10:09 AMBut specifics aren't important, I just meant whatever config is needed to submit jobs really
m
Mahesh Binzer-Panchal
03/21/2025, 10:10 AMSo you can definitely pass the same config to multiple workflows as well:
https://github.com/mahesh-panchal/nf-cascade/blob/4b83584254fc88fbeb37ebfa421f1ef190da194a/params.yml#L8
p
Phil Ewels
03/21/2025, 10:12 AMyeah I guess that's the solution - write a config file, then pass it to the head run and the child runs
2 Views