A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

image.png

No context (just see the changes made to a certain module used in almost all nf-core pipelines :winking_cowboy:)

Part of the blame also goes to <@U03SLE7RBAS>!

I'm glad I got the best hair in this meme

I'd argue that the propagation of the alternate hack Maxime was proposing in lieue of this was more distressing

the initial hack had low impact, but it was a hack

Screenshot 2026-03-04 at 11.54.37.png

(sorry for the reference, but don't know a better template than this)

```Three Channels for the Bioinformaticians under the sky,
Seven for the SysAdmins in their halls of code,
Nine for Mortal Researchers doomed to retry,
One Tuple for the Master Process on its head node,
In the Work Directory where the symlinks lie.

One Tuple to rule them all, One Tuple to map them,
One Tuple to pipe them all and in the DAG trap them
In the Work Directory where the symlinks lie.```

We should just have make all modules use metas from the start, I think we've hacked away all the exceptions at this point

Hackathon project? :rolling_on_the_floor_laughing:

“Break all existing pipeline logic by changing module inputs”

please add the updates here <https://github.com/nf-core/tools/pull/4077>

<@U039DEJ1RJS> what do you think of this implementation?

Looks good to me as basic implementation, advanced users will have to make their own version of the logic to suit their needs

We're arguing with Matthias about the params

You mean me or <@UQZG2UCF3>? Gets confusing :smile:

I was talking to you, so I meant <@UQZG2UCF3>