`debug_appraisal_results_time_slices.csv` can be very large

Open
#1,554 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
performance

Research direction

Start by locating where debug_appraisal_results_time_slices.csv is generated and how it relates to the other debug files. Measure its size for representative simulations and determine whether shrinking it, removing it, or adding a selective disable option best fits the existing debug workflow. Done means the chosen behavior is documented and verified without unexpectedly disabling other debug outputs.

Written by the indexing model from the issue text.

Description

Just seen 250 MB for a fairly normal simulation that runs in 25 seconds. For larger simulations this could be astronomical. Think about whether we can shrink this file, or whether we really need it, or can selectively turn it off whilst keeping other debug files.

Dominant language
Rust
Stars
8
Forks
5
Avg merge
11h 31m
Merged PRs (30d)
33

Contributor guide

Open the 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 EnergySystemsModellingLab/MUSE2

All issues in EnergySystemsModellingLab/MUSE2

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.