NatLabRockies / NatLabRockies/SAM
CSP dispatch optimization for merchant plant
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 486
- Forks
- 219
- Avg merge
- 10h 10m
- Merged PRs (30d)
- 2
Description
Describe the bug
Running a CSP model with dispatch optimization with the merchant plant financial model causes exec fail(tcsmolten_salt): mp_energy_market_revenue input has 1 rows but there are 8760 number of timesteps error.
To Reproduce
- Create a Power Tower / Merchant Plant case.
- On the System Control page, check Enable dispatch optimization.
- On Revenue page, note default energy market revenue options.
- Click Simulate.
Expected behavior
CSP dispatch optimization should work with Merchant Plant financial model.
Operating System and Version
- OS: Windows
- Version: SAM 2025.4.16 r1
Additional context
It appears that our translation between the merchant plant configuration and dispatch optimization does not support the “fixed cleared capacity option” because the cmod pulls price data from “mp_energy_market_revenue” not “mp_energy_market_revenue_single”. Therefore, it is expecting two columns of data [clear capacity, price].
A potential workaround is to use the “Time series cleared capacity and price” option, but this method produces errors when the power generation is below the cleared capacity, which is cumberson. So, without knowing the generation profile a priori, this becomes cumbersome.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with a Power Tower / Merchant Plant case using dispatch optimization, then inspect the System Control and Revenue page configuration and the cmod translation between the merchant plant options and dispatch inputs. Done means the simulation runs successfully with the fixed cleared capacity option without the 1-row versus 8760-timestep error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100