Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Create debug files for prices per iteration

Open
#791 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
data

Research direction

No file, test, or entry point is named. Start by tracing where prices and reduced costs are produced for each iteration, then clarify the debug-file format and location with maintainers. Done means those per-iteration values are written to files and can be compared across iterations.

Written by the indexing model from the issue text.

Description

question

@tsmbland Yup. If this is ready to go, feel free to merge it.

Done. I've realised we don't actually have a way to see how the prices/reduced costs are changing from iteration to iteration, so it would be good to output these as debug files. I'll open up another issue for this.

Originally posted by @tsmbland in https://github.com/EnergySystemsModellingLab/MUSE_2.0/issues/757#issuecomment-3233720017

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.