Postprocessing RAM use

Open
#377 0 comments 0 reactions 1 assignee View on GitHub

@asparke2 is already working on this.

Since Aug 8, 2025.

Assessment

This issue has not been assessed yet.

Description

bug postprocessing

Recent changes to postprocessing have caused simple comparisons of 10k runs to bluescreen a computer when running postprocessing, likely because of running out of memory. Unsure which new processes steps are causing this.

The fix is to profile the postprocessing scripts and include extra save/read steps to lower RAM use.

Dominant language
Ruby
Stars
54
Forks
28
Avg merge
3d 23h
Merged PRs (30d)
5

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NatLabRockies/ComStock

All issues in NatLabRockies/ComStock

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.