Maybe we can all coordinate?
# mag
j
Maybe we can all coordinate?
a
Absolutely, coordination sounds like a good idea. Have you and your colleague started with this, @Hesham Almessady?
j
They already have added
flye
to a fork of the pipeline, but on a quite out of date version of mag.
We had a talk during the Thursday dev hours (which is open btw, if you're availble - 1400 1600 CEST each week) about how we would go about this - including upidating some of the long-read preprocessing tools as well as adding the assemblers
a
I'll try to attend this Thursday. I'm guessing that this fork will be hard to merge with nf-core, since it's forked on an out of date version? My collegues and I could make a new fork, with the intention to merge with nf-core once we are done.
j
Yes exactly, we discussed with Hesham and his colleague that we would have to change a lot of things in the general structure (move a lot of thigns to subworkflows etc). to get this work properly, so were going to start from scratch. If you are all working together towards the same goal, I think it makes most sense to coordinate, and not work on forks but directly on the mag repo (on a specific fork). We should discuss how to distribute coordinate, tasks etc. Do you have a rough outline of what you want you planned to add more specifically? Then we can either talk on Thursday (@Hesham Almessady do you think you and @Zhi-Luo Deng can also make it again?)
@Zhi-Luo Deng I just invited to the nf-core GH organisation too :)
👍 1
a
Great! I, and possibly one of my collegues, will attend on Thursday. We will have a chat between us what we want to add more specifically. But in essence we are interested in a long-read-only track, with the possibity of using flye as an assembler.
👍 1
z
Then we can either talk on Thursday (@Hesham Almessady do you think you and @Zhi-Luo Deng can also make it again?)
Thank you for inviting me to the channel. I will have another meeting this week sorry🤦