-
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
Error with GATK4_GENOMICSDBIMPORT during joint calling: Badly formed genome unclippedLoc: Query interval "[]" is not valid for this input #1035
Comments
What is the status on this, @amizeranschi ? When I try to run your script
|
Thanks a lot @asp8200 for looking into this. I tested again now (since the script is configured to run with |
Hey! So with the test profile i cannot reproduce the
I manipulated the fastq_pair.csv to this:
My local copy is on revision: a5122a0 |
also can't reproduce with Of to issue number 2 |
Yes, I'll try to see if I can reproduce the error. |
Finally reproduced the save_mapped error |
fixed the |
I can confirm that |
Fixed, if you'd like to test it |
The
The intervals went missing, i.e. The pipeline was given this cmd:
|
on which commit were you? |
I am getting this now
|
Jun-02 15:30:43.369 [main] INFO nextflow.cli.CmdRun - Launching |
issue was only fixed a few commits later 04a563c |
Ok. I'll relaunch the test. |
for the other issue apparently we could consider adding: https://gatk.broadinstitute.org/hc/en-us/community/posts/4445826530331-Values-for-QD-annotation-not-detected-for-ANY-training-variant-in-the-input-callset-VariantAnnotator-may-be-used-to-add-these-annotations- |
see #1061 |
I now also get "Bad input: Values for QD annotation not detected for ANY training variant in the input callset". And I agree that it is more of a data issue. |
Hey @FriederikeHanssen and @asp8200 Thank you very much for addressing this issue. As it turns out, the yeast VCF file with known variants from Ensembl doesn't contain any indels, so it isn't suitable for VQSR. This is the reason for the I've tested the same code during the week-end on Bos Taurus data and things went pretty much alright, including VQSR. This is the command I ran:
And below are the last lines of the output. There was an error right at the end (after MultiQC), but the pipeline appears to have finished successfully in spite of it. One thing that puzzles me, however, is why Ensembl VEP ended up being skipped, even though I had it enabled in my command above. Is this by design, for joint calling runs?
|
Great news, thanks for testing. Can you send the log? |
Sure, here's the full log. I couldn't find any errors or warnings inside related to Ensembl VEP, so no clue what happened to it. |
For the record, VEP getting skipped was a completely separate issue (unrelated to joint calling). I've opened a new bug report here: #1084. |
Description of the bug
Hello,
I'm getting the error from the title while running joint calling with GATK. I'm attaching the full log below.
I am running
nf-core/sarek -r cbdaaa0
. I can provide my script if needed, for reproducibility.Command used and terminal output
No response
Relevant files
nextflow-error.log.txt
System information
No response
The text was updated successfully, but these errors were encountered: