I wanted to consult the hive-mind of <#C043UU89KKQ...
# team-maintainers
p
I wanted to consult the hive-mind of #C043UU89KKQ on this one: https://nfcore.slack.com/archives/CE6SDBX2A/p1747404809839359 Using
params.outdir
for
storeDir
seems like a bad idea..? It looks like it's been there for ages in the template (added by @hpatel back in Feb 2024). Why do we need it? Can it be done a different way?
e
I'm gonna cut this out in nf-utils FYI before we argue in circles
p
Copy + paste so the same code kind of cut out? Or reimplement in a different way kind of cut out?
I was also wondering if the
topic
stuff would affect it. But I guess not, as it's still just
ch_versions
e
reimplement in a different kind of way because I couldn't get it to work in that funky kinda of way
👍🏻 1
m
Interesting
We do use this in Sarek extensively
maxime 2
Outside of just the ch_versions
s
Sarek is using it
Sarek is using it
m
We should probably use a native process for this.
👍🏻 1
I think Ben wanted to replace
collectFile
with using native processes in his reduction of channel operators
➕ 2
j
So what’s the conclusion here — nf-core pipelines will be updated to use something other than
collectFile
so that multiqc isn’t receiving inputs from the
outdir
?
e
Hopefully, probably after the summer
👍 1