-
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
Add mpileup subworkflow for paired, germline and tumoronly varcalling #570
Conversation
hm ok still tests failing :/ |
GHA issue is gone for the moment, but controlfreec still fails |
subworkflows/nf-core/variantcalling/controlfreec/somatic/main.nf
Outdated
Show resolved
Hide resolved
looking good. |
hm I don't think it would be too bad? it is just the exact same subworkflow import into germline_variantcalling?! all the reference files are already there. Now what would be more difficult to only have MPILEUP_NORMAL run once when somatic is called and |
… a separate subworkflow
@nf-core-bot fix linting |
Co-authored-by: FriederikeHanssen <Friederike.hanssen@qbic.uni-tuebingen.de>
Co-authored-by: FriederikeHanssen <Friederike.hanssen@qbic.uni-tuebingen.de>
Co-authored-by: FriederikeHanssen <Friederike.hanssen@qbic.uni-tuebingen.de>
For the tests for controlfreec to pass, you will need to adapt some file paths to include the .gz thing now. The tool apparently uses the whole filename as prefix. Not sure we can prevent that (unless updating the controlfreec module and
Speaking of tests, mpileup tests for running it alone are missing as far as I see. Could you add them? |
Yep, I noticed that as well. I am currently looking into that; I would like to try and change the prefix in controlfreec so that it does not contain the .gz part. What do you mean with running mpileup alone? Independently of controlfreec? Do I have to create a file in sarek/tests/ for that? |
Now I am even more confused. In controlfreec, the prefix seems to actually be correct, i.e. something like sample4_vs_sample3. Where is the .gz coming from? |
so controlfreec generates a ton of output files with "fixed" endings by the tool. You can only determine the prefix common between all output files |
Yes you need to edit: then edit the |
… added tests for mpileup and fixed some paths
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 work, @WackerO ! From my side only two things missing:
- Update the changelog
- Update the subway map. (I can help you there, if you like)
…ling, fixed space in germline_varcalling, updated subway map (text was slightly changed by inkscape automatically), updated Changelog
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.
Sorry I actually saw one or two more things:
The versions for all the subworkflows must be propagated up to the germline/tumor only subworkflow by adding:
ch_versions = ch_versions.mix(RUN_MPILEUP_TUMOR.out.versions)
etc
The line in the changelog should be in order of PR number
This PR extracts mpileup code for paired, germline and tumoronly variant calling into a separate subworkflow.
Also, as this is related: in this PR, samtools was changed to bgzip mpileup output addressing the space problem described in this issue. The changes are accounted for.
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).