-
Notifications
You must be signed in to change notification settings - Fork 417
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
Update modules once again #459
Conversation
|
@drpatelh at first I was a big annoyed because I just had finally finished my refactoring of everything with the newest modules syntax a week ago, and I had to do it again with the newer newest syntax. I'm particularly proud of the rework of our local bwamem and bwamem2 modules that are now stripped of every sarek logic, and the rework it allowed for the mapping subworkflow. |
// MAPPING | ||
process { | ||
|
||
withName: "BWA.*MEM" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😍
// Only name sort if Spark for Markduplicates + duplicate marking is not skipped | ||
if (('markduplicates' in params.use_gatk_spark) && (!params.skip_markduplicates)) { | ||
process { | ||
withName: "BWA.*_MEM" { ext.args2 = 'sort -n' } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This then overwrites the above config ext.args2
for BWAMEM?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm hoping that we can also remove the part
thingy from the bwa*mem processes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will think about how to do this. I am sure there is a way
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where are you using it? I don't see it in the process anymore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yes, that's what I wanted to figure it out.
I'll let someone else try that, I'm going to the NGI retreat today, so won't be able to work much
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep that is what I thought of, to also pull that in the modules config. I am glad I wasn't completely off here. I'll give it a try probably tomorrow afternoon
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
plus by then maybe the yet new modules syntax is there and I can catch two birds with one stone 😆
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FriederikeHanssen will you be adding the split_fastq logic in the bwamem modules in #462 or will you be doing that in a separate PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll see that I can add it in :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my side this looks all great. Taking the 'parameter logic' out of the subworkflow is pretty nice, makes the workflow look a lot simpler and less crowded. I can also now better see how we can make it work with UMI based subworkflow + mapping.
PR checklist
scrape_software_versions.py
nf-core lint .
).nextflow run . -profile test,docker
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).