Closed chenzler closed 4 years ago
Hi @chenzler,
Hm-- I'm not sure what is happening here, I can't see anything super useful from the error messages, it is weird it works outside of bcbio but fails in the same spot in bcbio. I'm wondering if this is maybe a memory issue, when you are running it outside of bcbio are you still passing it the same amount of memory? If we can figure out something that we can reproduce we can try to dig into what is causing the problem. You can try giving GATK more memory by setting:
gatk:
jvm_opts: ["-Xms500m", "-Xmx3500m"]
under the resources
section in your bcbio_system.yaml
file, which should give GATK more memory to work with.
Well, this is interesting. I tried giving GATK more memory, and it caught on a different region (on chr1). I had previously tried changing the general default memory settings to give the whole process more memory; I assumed that would also give more memory to GATK, but do I need to allocate specifically to GATK as well? In all my previous runs, I tweaked the general default memory settings in the sample.yaml file, and no matter what I did it failed on the same region of chr7. But changing the allocation for GATK specifically changed that, which seems to suggest that memory is causing the problem at some level. I'll try giving even more memory specifically to GATK and see what happens... Thanks!
closing for now, let us know if you still have issues!
Hi,
I've been running bcbio on a sample with matched tumor/normal (using the variant2 analysis pipeline), and I keep getting the following error on one specific region of the genome. Mutect2 runs for that region, and it looks like it's successful, but then it throws an error. If I run the individual problematic command (as listed in the error report), it runs to completion cleanly. Any ideas what's causing the problem?
Here's the output & error, starting with the end of the Mutect2 run for that region: