NatLabRockies / NatLabRockies/H2Integrate

Connect dispatch prices to finance models

Open
#337 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

dispatch enhancement finance
Dominant language
Python
Stars
26
Forks
44
Avg merge
3d 22h
Merged PRs (30d)
16

Description

Connect dispatch prices to finance models

This issue is a bit preemptive, but the topic came up in relation to PR #310 (https://github.com/NREL/H2Integrate/pull/310#pullrequestreview-3390037634) and I think @kbrunik or @elenya-grant is working on another PR for providing price profiles for dispatching in H2Integrate.

Price profiles would be a great addition to H2Integrate, but will need to connect to both the dispatch components and the financial models. Because our performance simulations are done on timesteps as part of a year (currently hourly) and our finance models are done on an annual basis, the dispatch and finance models need slightly different price information (hourly vs annually).

Proposed solution

I would like to propose that we have the user provide the hourly price profile (with the option to provide a single value as a constant hourly price). I think the finance model, or maybe a separate in-between component, should aggregate the hourly price profile to a single value for the year to be used in the finance model, where in the finance model the single value can be discounted by inflation to adjust for future years. The user should be able to specify the aggregation method to go from hourly to annual price; I think default should be the mean, but others, such as max, root mean square, or even a custom value directly input by the user could be useful.

Alternatives considered

Additional context

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.

Research direction

Start by reviewing PR #310 and tracing how dispatch components and finance models currently receive price information. Done should cover hourly or constant price profiles, an explicit hourly-to-annual aggregation choice with a default, and the finance model's treatment of future-year inflation; the issue names no files or tests.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.