EnergySystemsModellingLab / EnergySystemsModellingLab/MUSE2

Use `TimeSliceSelection` for demand maps

Open
#1,409 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
8
Forks
5
Avg merge
1d 2m
Merged PRs (30d)
37

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

Contributor guide

Open the contributing guide

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.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.