-
Notifications
You must be signed in to change notification settings - Fork 4
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
Issue 348 #419
Issue 348 #419
Conversation
|
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.
Cool! For some subworkflows, I've implemented subworkflow tests (#129). You can see that the CALL_SVS
test is now failing, and you need to update the tests to reflect you now have 6 inputs instead of 5. Let me know if you need any help 😊
The new linter in nf-core tools 3.0.0 complains about the schema's draft. Just seems to be the protocol (http vs https). Should I push the fix in this PR or do we go about this another way? |
I'll work on merging the 3.0.0 template PR later today. In the meantime, if the change required for it to work is only to change http to https, then you can fix that in this PR :) |
I tried doing that but it continued to produce more errors. 😵💫 So I'll put this on hold and merge your changes into my branch when you're done |
I rebased my branch onto dev without conflicts. So everything should be fine now 🤞 |
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.
Nice, looks really good! One thing you could change if you want, but I'll approve as it stands.
input[2] = SAMTOOLS_FAIDX.out.fai | ||
input[3] = "sniffles" | ||
input[4] = [[],[]] | ||
input[5] = [ |
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 think this is okay (and I've done similarly), but I'm not sure the coordinates in this file will overlap with any variants we call in this test (?).
If you wanted to, you could check the variants output in this test without any bed file, and then choose an appropriate region overlapping a variant.
You can "create" a custom bed file like this:
https://github.com/nf-core/modules/blob/d7462e71f9129083ce10c3fe953ed401781e0ebd/modules/nf-core/modkit/pileup/tests/main.nf.test#L110-L112
Also the |
Closes #348. The input BED file is now passed through to CALL_SVS, which passes it to BEDTOOLS_MERGE for region-based filtering of SVs during merging.
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).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).