-
Notifications
You must be signed in to change notification settings - Fork 38
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
Refactoring + other issues with cadd and samtools merge #538
Conversation
|
The test profile works perfectly for this |
Hi! I am trying out running this patch PR on the dataset I have been running before (i.e. GIAB on our server). I run into errors, trying to see whether they are on my part or in the code.
In a quick look it indeed looks like there is a mismatch for the Sentieon workflow. Here is what is asked for from the "parent" processes using the Sentieon SNV calling subprocess.
Here are the emitted arguments. Maybe a typo for raredisease/subworkflows/local/variant_calling/call_snv_sentieon.nf Lines 124 to 129 in d0b512b
Need to run for a meeting now, will continue testing (and checking the case error) later today |
indeed looks like a typo. Thanks for testing and reporting |
Quick update. I am running into more downstream issues, but I think these are on my side. I will continue working through the GIAB run and raise any issues I find, but will probably complete when you are done with this PR. I would like to run the test data, but we have an offline-only server, and it is not feasible to pull all containers to my local computer. |
adding explicit temps
saveAs: { filename -> filename.equals('versions.yml') ? null : | ||
filename.contains('_renam.vcf.gz.tbi') ? "${meta.id}_repeat_expansion.vcf.gz.tbi" : | ||
filename }, | ||
saveAs: { filename -> filename.equals('versions.yml') ? null : filename }, | ||
] | ||
} |
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.
@jemten I am thinking if it might be better to add a parameter to generate reviewer compatible output files, like we are doing for cram files at the moment... Then we can publish the compressed files by default, and we can choose to publish the uncompressed files based on whether that parameter is set to true or not.
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.
Good suggestion!
I've tested the most recent version of this PR and I do get an error. I made a separate issue because I also get the error in pipeline version 2.0.x #542 . The error is this:
|
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.
LGTM!
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile test_one_sample,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).