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
We couldn't find a way of making it spawn exactly 4 jobs with the each in place. But with a val instead, it becomes standard and the flatMap version works.
The solution isn't valid if there are more inputs in ch_inputs though because of how each works (and I hadn't realised it worked that way either so thanks for pointing it out).
Have you checked the docs?
Description of the bug
The BUSCO module uses a
each
on thelineage
input parameter, and we've got some trouble making it work in a pipeline with @alxndrdiazThe main problem is that it doesn't work on dynamic lists. See a minimal example below
This creates a single
BUSCO
job that takes the list itself aslineage
rather than unrolling it:If I do a
flatMap
instead ofmap
:ch_inputs
is like this:but Nextflow makes 4*4=16 jobs !
We couldn't find a way of making it spawn exactly 4 jobs with the
each
in place. But with aval
instead, it becomes standard and theflatMap
version works.Command used and terminal output
No response
Relevant files
lineages.txt:
System information
Nextflow 22.04.0
The text was updated successfully, but these errors were encountered: