NatLabRockies / NatLabRockies/H2Integrate

Feature request: allow user to specify when the plant becomes operational (installation time)

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

Nobody has claimed this yet.

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

Description

Allow user to specify when the plant becomes operational (installation time)

As discussed in https://github.com/NREL/H2Integrate/pull/310#discussion_r2470579053, it will likely be important for a user to be able to specify when a plant transitions between installation and operation, specified in ProFAST as installation time. The financing costs, revenue, and operational costs are all impacted by the installation time. In #310, the installation time is hardcoded as a single year for the numpy financial model implementation. We should expose this to the user, preferably in a way that will allow the user to specify less than a year, probably in hours.

Proposed solution

If user specifies part of a year, then we can pro-rate the costs and revenues for the partial year.

Alternatives considered

A partial solution would be to allow the user to specify years of installation as an integer, which would be simpler computationally while still providing some flexibility.

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

The issue points to the numpy financial model implementation and the discussion in PR #310; start there and review how installation time is currently hardcoded to one year. Done means exposing a user-configurable installation duration, including sub-year values, with costs and revenues prorated for partial years.

Written by the indexing model from the issue text.

Assessment

Tech stack
numpy, python
Domain
backend, fintech-quant
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.