Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split the modules out into separate files #1

Open
andersgs opened this issue Jul 2, 2021 · 1 comment
Open

Split the modules out into separate files #1

andersgs opened this issue Jul 2, 2021 · 1 comment

Comments

@andersgs
Copy link

andersgs commented Jul 2, 2021

It would be useful to have the modules in separate files, you can then build a catalogue of modules (perhaps in its own repo) that you can use across workflows and pipelines.

@dfornika
Copy link
Member

Good suggestion. If we followed this approach, we might also be able to take advantage of the library of modules from nf-core project.

We've taken this approach to some extent in other pipelines, such as our BCCDC-PHL/routine-sequence-qc pipeline. But in order to make the modules truly re-usable we'd need to think carefully about how to isolate them from the specific details of how they're used in the context of any given pipeline. I've been meaning to look more closely at the standards used in the nf-core/modules project to achieve that isolation.

We might also look at MDU-PHL/kovid-trees-nf for ideas on how to better isolate our modules within a single pipeline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants