Hi everyone, How should we organise ourselves for the different modules topic migration ? This project will probably have a lot of newcommer so we will have to track things properly to avoid duplicated work. We currently have https://github.com/nf-core/modules/issues/9978 to track the first hundred module.

Full list of modules pending migration:

amcn6d.jpg

Hi @Anabella Trigila, Could you create the next batch of issues (maybe 2) ?

Yes, already did that

Modules migration PART 2: https://github.com/nf-core/modules/issues/10439

PART 3 here: https://github.com/nf-core/modules/issues/10558

Thanks a lot! We already did quite a lot of work !! We should just pay attention to only work on one issue at a time and properly link the PR to the issue and update the status of the latter to ease the daily wrap up. Could everyone check the issue they are assigned to and update the status ?

nice work!

amdgxa.jpg

Hi all, Quick question I was hoping someone would be able to provide some advice on. I am currently working on migrating canu (PR #10584) and have run into a bit of trouble with the final CI step in the PR. Local testing with docker results in both tests passing but the CI appears to have a different container build, but maybe this is just a issue with conda since docker and singularity both pass. Contig lengths also vary slightly depending on build resulting in another point of failure for the conda test... Basically my questions is, is this something I should be concerned with or is this expected behavior from the conda tests? Thanks for your help, currently a newbie at this 😓

I am doing FASTQE

No idea if it's on a list or no

Update of checkv https://github.com/nf-core/modules/pull/10580

Hi, I just finished my module yesterday in my PR was merged some minutes ago, so I was thinking about updating some of these modules. Is there any priority for this??

I've updated the project board and put every assigned

Todo

issue to

In progress

. Every closed issues are now

Done

. This will allow an easier count for the wrap up. We are currently at 91 issues closed What a fantastic amount of job done ! We also have 126 issues in progress, 16 ready to review and 20 to do. We now need to convert all the work in progress into merged PR 😉 !

Hi, I just finished my first sub-issue, and it is ready for review. I have also assigned 3 more to myself, and hopefully I should finish them before the end of the hackathon. I am new to nextflow and hackathons. This really means a lot to me. I hope to increase my speed with the 3 that I have assiged to finish soon Thank you

Hi! I am new to nextflow and working on the centrifuge module. I have a question. I added centrifuge, centrifuge-build and centrifuge-kreport to myself. For centrifuge-build and centrifuge-kreport, in the main.nf

tuple val("${task.process}"), val('<tool1>'), eval('tool1 --version'), emit: versions_tool1, topic: versions

will the val be val('centrifuge-build')/val('centrifuge-kreport') and emitversions centrifuge build/emitversions_centrifuge-kreport or val('centrifuge') and emit:versions_centrifuge ?

fixing the eval echo X.Y.Z to val XYZ: https://github.com/nf-core/modules/pull/10801

Can I have a review on my PRs ? https://github.com/nf-core/modules/pulls/assigned/LouisLeNezet

I was asked to make some changes on my PR which I have made Changes Removed legacy

versions.yml

output Added topic-channel version tuple to

output:

block Updated

<http://main.nf|main.nf>

to use

VERSION

variable with

eval("echo ${VERSION}")

Updated tests and snapshots using

nf-core modules test bioawk --update --once

• Ran

nf-core modules lint bioawk --fix

to update schema I would love to have a re-review before I can go on to pick up another one before the end of the day being the third day.

krona: https://github.com/nf-core/modules/pull/10813

We need a bit more documentation on how the version should be written when template are used or anything else than a bash script. For the moment it is mentionned that:

Update the

path "versions.yml", emit: versions

line to the following:

main.nf

Copy code

path "versions.yml", emit: versions, topic: versions

But

nf-core modules lint

will then complained. What are the current guidelines ?

I think this PR has a null because the author couldn't update the module (she does not have GPU), what could we do here? https://github.com/nf-core/modules/pull/10745

Can I have a second round of review ? https://github.com/nf-core/modules/pulls/assigned/LouisLeNezet

Also, we currently have no more issue unassigned 🎉 We have 151 issues closed, 10 ready for review and 102 in progress.

Hi I'm gonna work with the gecco_run one. Could you please add a card to the hackthon project?