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

Investment fails when only remaining options fail to dispatch

Open
  • Is something wrong?
#1,347 8 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #1363 by @alexdewar — closed without merging

Assessment

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

Research direction

Start by tracing the investment selection and appraisal flow described in the issue, focusing on how unmet demand and zero-activity options are handled. Compare the four proposed treatments for dud options and determine which policy should be adopted; done means unprofitable assets can be selected instead of terminating the simulation when remaining options fail to dispatch.

Written by the indexing model from the issue text.

Description

question

When selecting the best assets for a commodity, it is possible to end up with a situation where demand is not met by already-selected assets and we are unable to calculate metrics for any of the remaining options because they fail to dispatch (appraisal produces activity of zero in every time slice). This is bad. While profitable assets should clearly be preferred to unprofitable ones, unprofitable ones should be selected in preference to terminating the simulation.

The question is what to do with these dud options.

A few ideas have been floated:

  1. Keep bumping the price of the CoI until assets start dispatching
  2. Just pick assets arbitrarily until demand is met in partial dispatch
  3. Calculate the price increase that would be required for each asset to dispatch and use that
  4. Calculate what the metric would for each asset assuming full utilisation
Dominant language
Rust
Stars
8
Forks
5
Avg merge
1d 3h
Merged PRs (30d)
17

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.