I am helping a colleague run sarek on some WGS sam...
# sarek
t
I am helping a colleague run sarek on some WGS samples, and the
GETPILEUPSUMMARIES
process (part of Mutect2) blows through a terabyte(!!) of RAM (we set the allocation in the config to the maximum out cluster has to offer) and still runs out of memory -- clearly this is insane and something is going terribly wrong. Does anyone have a suggestion on what to do? Not sure there is a fix, but even a work-around would be helpful. Thank you!
screams 3