-
Notifications
You must be signed in to change notification settings - Fork 39
Multi-year sell-price in ProFAST NPV #799
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
elenya-grant
wants to merge
5
commits into
NatLabRockies:develop
Choose a base branch
from
elenya-grant:npv/multi_year_sell_price
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+206
−5
Draft
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
3c03c3b
made it so profast npv can take in multi-year sell price costs
elenya-grant c6c922f
Merge remote-tracking branch 'h2i_upstream/develop' into npv/multi_ye…
elenya-grant 62ae478
updated error handling for misisng sell price value
elenya-grant cf985dc
added subtest for inflation test
elenya-grant 1b57833
Merge remote-tracking branch 'h2i_upstream/develop' into npv/multi_ye…
elenya-grant File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both test fixtures use inflation_rate: 0.0. Can you add a case with nonzero inflation to confirm the per-year array isn't getting escalated a second time by ProFAST's own calculation? If users are meant to supply already-nominal per-year prices, we may need to force infation_rate = 0 when an array is passed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, could we clarify in the docs whether
commodity_sell_priceshould be real or nominal dollars? Per our discussion with @jaredthomas68, we need to set nominal prices with inflation_rate = 0 (since ProFAST would otherwise apply its own escalation on top). Worth spelling that out explicitly.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I played around with ProFAST using a 2% inflation rate and have some info in case its useful:
pf.cash_flow(price=0.07)andpf.cash_flow(price=[0.7]*30)result in the same NPVI think ProFAST does escalate the sell price, it basically does this:
Aka - the commodity sell price should provided
plant_config["finance_parameters"]["cost_adjustment_parameters"]["target_dollar_year"](the commodity_sell_price does not go through AdjustedCapexOpexComp)I would be happy to update the docs! @jaredthomas68 - can you confirm that the commodity_sell_price should be input in real dollars?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can yall (@vijay092 and @jaredthomas68) tell me whether this is True or false:
Can y'all look at the test
h2integrate/finances/test/test_profast_npv.py::test_profast_npv_with_inflationand let me know what y'all think?