Dear <#C02FC6VFQG1> people, what do I need to do t...
# metatdenovo
m
Dear #C02FC6VFQG1 people, what do I need to do to put mag in #C02FC6VFQG1, cf https://github.com/nf-core/fetchngs/issues/376
Evangelos (now on vacation, so do not ping) want a #C024915L4KB release (cf https://nfcore.slack.com/archives/C043UU89KKQ/p1786351418319259?thread_ts=1786349565.618369&amp;cid=C043UU89KKQ) And I figured it was a fun side quest to do to get back on track
d
I'm not sure I understand. Metatdenovo does de novo assembly, like the mag pipeline, but does not reconstruct MAGs. It is primarily meant for metatranscriptomes. Are you thinking of how to chain, i.e. output param settings etc?
m
NO idea, I guess I will wait for Evangelos to come back from vacation
d
Now I saw your post in #CE9MS66BS, so this was maybe a typo. Particularly after this week's bytesize, I think the downstream pipeline should provide the glue for chaining rather than the upstream. And if nf-meta can do this for us, there's no need for pipelines to chase each others interfaces.
e
There is definitely no need, and it can be done by users manually by hand, or by in-house python parsers...but, for pipelines that are easy to produce downstream pipeline samplesheets, I would say go ahead and create those. But again, completely optional (especially for pipelines that are a pain to chain)
But now that I remember...fetchngs has the
--nf_core_pipeline
parameter (downstream) built in its logic, so it would be nice to create all downstream samplesheets 😄
feel free to have a look and let me know if this makes sense: https://github.com/nf-core/fetchngs/pull/387
👀 1
d
I will, next week. On vacation
❤️ 1
e
Enjoy!!!
✅ 1
d
Thanks, I needed that! Will look right away.