You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reconsider how operation and maintenance are passed to ProFAST
There is some question about whether we should use the 'maintenance' option in pf.set_params or use pf.add_fixed_cost to include the operation and maintenance costs in ProFAST inside the CustomFinancialModel. I think this question is more about how the user wants to include O&M in the model. We may want to support multiple approaches and implement them as projects need them.
Proposed solution
We chose to just use the 'maintenance' option in pf.set_params for now
Alternatives considered
We could use the pf.add_fixed_cost method instead.
Reconsider how operation and maintenance are passed to ProFAST
There is some question about whether we should use the 'maintenance' option in
pf.set_params
or usepf.add_fixed_cost
to include the operation and maintenance costs in ProFAST inside theCustomFinancialModel
. I think this question is more about how the user wants to include O&M in the model. We may want to support multiple approaches and implement them as projects need them.Proposed solution
We chose to just use the 'maintenance' option in
pf.set_params
for nowAlternatives considered
We could use the
pf.add_fixed_cost
method instead.Additional context
See discussion in PR #355
The text was updated successfully, but these errors were encountered: