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

Use `TimeSliceSelection` for demand maps

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
backend

Research direction

Start by reviewing the closed attempt in #1329 and locating the current demand-map code and TimeSliceSelection usage. Done means demand maps store demands at the TimeSliceSelection level without the seasonal split-and-recombine workaround, while preserving existing demand-map behavior.

Written by the indexing model from the issue text.

Description

Rather than storing demands at the TimeSliceID level, which requires some hacky steps to split up demands for seasonally balanced commodities then add then together again, we should store demands at the TimeSliceSelection level

I had a go at this in #1329, and pretty much got it all working, but closed that as it's now got a lot of merge conflicts, so easier to start again

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.