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

Zero shadow price for over-supplied commodities

Open
#992 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
backend

Research direction

Start by reproducing the zero shadow prices in the two_outputs model for DIESEL in winter 2020 and GASPRD in summer 2020, then review the related discussion in PR #806 and issue #986. Trace how over-supplied outputs and multi-output assets produce prices, and define done as preventing incorrect zero prices or infinite-loop behavior with regression coverage for the reported cases.

Written by the indexing model from the issue text.

Description

I've noticed in the two_outputs model that a couple of commodities have a price of zero for some timeslices (actually -0.0, to be precise):

  • DIESEL has a price of zero in winter 2020
  • GASPRD has a price of zero in summer 2020

Both of these are produced by assets with more than one output commodity, and in both cases the price of zero coincides with the commodity being over-supplied across these seasons, which is necessary for the asset to meet demand of the other commodity it outputs.

In this model it seems to only happen in the base year (perhaps a sign of poor calibration), but I see no reason why it couldn't happen in later years where MUSE is choosing the investment decisions.

I see this was predicted as a potential issue here, but don't think this has been followed up on.
@ahawkes Do you have any ideas how we might address this?

I've also come across zero prices while working on #986, where hydrogen appears free, which is at least one reason you can end up in an infinite loop. That might be unrelated though

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.