I have been running genomeCoverageBed from my command line for months now. it works fine. I have about 17GB of available RAM and plenty of hard drive space. All of a sudden, it started to throw the std bad alloc error. Any ideas what that could be about?
-
-
Try a memory check and file system check. These "all of a sudden" errors can point to file corruption issues.
Has the program (or compter system) been updated recently? -
Run "top" command at the same time in another window. If memory usage of running process approaches near 100%, that's your problem.Comment
-
Tumors contain complex mixtures of cell populations that evolve in response to treatment and host-specific factors. Tissue biopsies provide only static snapshots of a tumor’s state. But what if we could follow that evolution over time using a minimally invasive technique?
Liquid biopsies can detect tumor-derived material circulating in the bloodstream, providing a way to study treatment response, detect emerging resistance, and discover new biomarkers. Circulating...10-14-2026, 09:55 AM -
Researchers using sequencing and genomics tools often have to make trade-offs. They can choose between speed or scale, short reads or long-range information, or targeted panels or a view of the whole transcriptome. New technologies that have been released this year are built to address those tough choices.
We asked six companies the same four questions to learn about their latest products. The new technologies bring a lot to the table, including rethinking sequencing...
Comment