-
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
bad_alloc #309
Comments
I have also encountered such a problem!Have you solved this problem? Does this mean there is not enough memory? |
Honestly we gave up on GLNexus. We ended up taking the per-sample VCFs produced by DeepVariant (VCF, not gVCF), and merged them directly. |
@bbimber We also encountered a GLNexus memory error. How did you directly merge VCFs? Thanks a lot! |
@finkbine: we gave up on GLnexus - it doesnt appear to have much active support. We have been taking the VCF (not gVCF) outputs from DeepVariant and merging them directly. |
@bbimber Dear bbimber, |
we've used either bcftools or DISCVseq MergeVariantsAndGenotypes (which is a port from GATK). I dont know how it would handle the wild type genotype issue, but I would be a little concerned about assuming they're wild-type as opposed to no-call/filtered. |
Hello -
I am trying to run GLNExus to combine gVCFs produced by DeepVariant. The input is 16 single-sample gVCFs, aligned to the rhesus macaque genome. I split the job to run one contig at a time, and I find that chromosome 1 consistently gives a std::bad_alloc error. Below is the command and output. Can you suggest any debugging steps I could try?
In the command, contig.bed is a one-line bed file specifying chromosome 1.
The output is the following:
When I run this same pattern for any of the other contigs the tool runs fine. Any help would be appreciated.
The text was updated successfully, but these errors were encountered: