-
Notifications
You must be signed in to change notification settings - Fork 14
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
DSL2 migration #14
Comments
A possible migration planIntroductionI've time-boxed a day for figuring out how I'd do it. Here is a plan with a few commands that might be helpful to someone if a migration is attempted. Inspect overall structureThe logic is duplicated across a few files and it's not obvious how to put them together. This searches for the comments and notes down the lines they are at, so the files can be split into logical chunks:
Split into modulesHere's how to pick a section from each file corresponding to filtering and trimming, based on line numbers above:
Edit each moduleRemove DSL1 bitsRemove all the
Clean upGo through the new file manually. Remove commented out code, and any if()s - leave just the process definitions. Try to recreate each flow through the codeSince the I found it helpful to have two files open next to each other - the common one, and the original ones that had the flow - and search for process names because they didn't change.
Test each moduleSince nothing really changes in the individual processes, any breakages should be quite obvious when testing modules one at a time. Put everything togetherThe new |
I've set up a preliminary project to start some organization on this. I'd like to start on something in the next few months, on a branch of course, as we have several workflows with similar steps. We should also think about some of the newer considerations with the nf-core DSL2 base and configs, in particular process-specific configs that allow some custom arguments. |
We're seeing some fragmentation on workflows due to switches in technologies (PacBio, Shoreline, Loop, etc) that a migration to DSL2 would help tremendously. This is a simple tracker to plot a course forward and note tickets that would benefit from this.
The text was updated successfully, but these errors were encountered: