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

Refactor how process maps are represented and used

Open
#880 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
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
backend

Research direction

Start by tracing how CSV entries are loaded into Process and how data is transformed when constructing an Asset; review RangeMap usage in #874. Done means Process stores deduplicated entries, milestone-year entries are available upfront, and non-milestone years are checked lazily for commission-year handling.

Written by the indexing model from the issue text.

Description

umbrella

This will allow new features (e.g. #845), but is also necessary to fix some bugs (e.g. #846).

I think ultimately we should store the individual entries in the CSV files in the Process struct, deduplicating by using RangeMaps (see #874). We will need to transform this data into something usable when we construct an Asset. We should ensure entries are provided for every milestone year upfront, but for other years we should do the check lazily to allow for assets whose commission year is on a non-milestone year (#859).

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.