mykle hoban
01/24/2025, 9:16 PMparams list in nextflow.config and assign them to ext.args in modules.config. In other (non nf-core) contexts, I've allowed the user to pass --<toolname>-<arbitrary param>, parsed the params map for entries starting with 'toolname', and passed the remainder to the tool as-is. This seems to work pretty well, although with nextflow's parameter case translation, it requires some extra string manipulation. Is there an accepted way of doing something like this for nf-core modules, or do we just manually handle all possibilities in modules.config?Leon Hafner
01/25/2025, 10:43 AM$task.ext.args variable."Igor Trujnara
01/25/2025, 3:55 PMnextflow.config , and implement custom handling for it. If it's something less relevant and rarely used (e.g. context settings for grep), then the user always has the ability to set them through an additional config file supplied to Nextflow with -cmykle hoban
01/25/2025, 9:21 PM