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

Reassess the use of candidates for price calculations

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

Research direction

Start by reading related issue #1166, then trace the current price-calculation path for commodities with no existing producers and inspect how following-year candidates enter it. Done means deciding whether that dependency is correct and defining the required behavior for current-year pricing before any implementation.

Written by the indexing model from the issue text.

Description

question

When a commodity is not produced by any existing assets, but might be needed in the following year, we look at candidates for the following year to calculate prices. This approach is described in the related issue #1166

While this seems to work to give us the prices we need, it seems a bit odd to use candidates from the following year to calculate prices for the current year. Why would the parameters for technologies in 2035 have any bearing on prices in 2030?

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.