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

Investment issues (umbrella)

Open
#1,382 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Domain
backend

Research direction

Start by reading sub-issues #1358, #1383, #1384, #1209, and #1313, along with the referenced issues and any linked pull requests. This is an umbrella for unresolved capacity, divisible-asset, shadow-price, and multi-output design questions; no single file, test, or completion criterion is identified here.

Written by the indexing model from the issue text.

Description

umbrella

Main issues:

  • #1358 (see also #1199 and #1357)We don't have an agreed upon approach for capacity/tranche size selection. Unclear whether capacities should be defined upfront or dynamic (there are software design implications here, and I'd advise against mixing approaches to keep things relatively simple). Unclear how this should interact with divisible assets. Unclear what the user interface should be.
  • #1383 (see also #1319) We're appraising capacities in each tranche as if they're entirely separate assets, rather than part of a whole. Ignoring what's been selected so far can lead to inefficient use of availability constraints, potentially leading to higher capacity than we need
  • #1384 Zero shadow prices can lead to negative activity coefficients which can prevent assets which would probably be feasible from dispatching (see also #992)
  • General indecision about divisible assets (which, to remind, mostly exist for the purposes of allowing partial decommissioning). Should we have a "parent" asset made up of lots of discrete units with the pre-defined capacities, something that allows for more continuous capacities (#1269), or scrap this completely and just have a collection of independent smaller assets. What should the user interface be?
  • #1209 Related, to the above and point 1, the current approach of splitting assets into small units for re-appraisal can lead to many appraisal rounds which can be inefficient. Should we allow appraising multiple units simultaneously?
  • #1313 No good solution yet for processes with multiple output commodities (also related to zero shadow prices)

See sub issues below, but also look at any linked pull requests/issues for full context.

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.