If I am currently refactoring a pipeline, should I...
# pipeline-maintainers
n
If I am currently refactoring a pipeline, should I use the opportunity to switch to topics?
n
This should be fully supported now, so go ahead 😉
👍 1
m
yeah, it's a no brainer given how easy it is
party this 1
n
Looking forward to that no-brainer 😉
🎉 1
Just to clarify, because it actually seems suspiciously easy: every output with
topic: 'something'
can be collected via
channel.topic('something')
, essentially the same as
mix()
ing all of those outputs?
m
That's it
that's really how it started
n
Ok, thats nice. But, it seems that not all nf-core modules have the
topic: 'versions'
next to the versions output?
m
unfortunately not yet
n
So I would still do this with
mix()
for the subworkflows and collect those into a topic channel?
Can I assign workflow outputs to topic channels?
n
Hi the migration will be a gradual process. For now topics are not required yet in nf-core (but they will be next year). So for now we will have modules using the old system and modules using the topics system.You don't have to change anything to your pipeline except when you add a module with the topic. In that case you should simply remove the
versions
mix of that specific module. The template will handle the rest
n
Ok, I think then it will probably make more sense to do this in a couple of months
n
No need for that, you will automatically do this when doing module updates since more and more modules will be migrated
n
What I meant was more that right now there is not much to do since none of the modules I use seem to use topics
n
Ah yes in that case you can wait a bit 🙂
Or update them yourself 😉
m
You can even use the nf-core-utils plugins that we will soon put in the template
n
I am kind of getting the impression that I missed a bunch of developments
What do the nf-core-utils plugins do?
maxime 1
m
Just removing things from template to put it in plugin
s
Sarek is using it
n
I see. To be honest, I think what I am currently doing will be / is confusing enough without adding in a bunch of moving things around
n
Yeah lots of changes are incoming because of the syntax changes in Nextflow, I hope we will finally be stable on that front once we got through that
n
Yeah, but I think combining those changes with what you already noted as a confusing PR is probably not a great idea
n
Yeah I agree, let's not add topics in that PR 😁
👍 1