Organize input params

[alxsmith]

Organized input parameters into groups, define functions to read from yaml

NOTE - i merged in other feature branches so it looks like a lot of changes but you should only focus on data/sample.yaml and params.py for this PR

We can have pre-packaged yamls with defined starting inputs. those are called by passing a run_name which is the file name for the yaml. it will auto populate the input classes and then join them into a single InputParams class nested by group

Still not sure exactly how we want to handle our timeseries values. I updated the type tags to DFs from Seiries but i think the NPA one will make more sense once we start defining that class

[karpdave]

Dupe with TimeSeriesParams: gas_bau_lpp_costs_per_year

[karpdave]

In spreadsheet, the thing called inflation_rate is only used for the conversion to 2025 dollars, so I think this collapses into the NPV thing you are describing

…

On Mon, Aug 25, 2025, 3:55 PM Alex Smith ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In src/npa_howtopay/params.py <#9 (comment)> : > inflation_rate: float cost_inflation_rate: float + npa_lifetime: float + npa_install_costs: float + discount_rate: float i was thinking we have inflation rate but also need discount rate for any NPV calculations. But that may have been confusion on my part — Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN7F3GYY6JD44CW6WF6YVOD3PNS35AVCNFSM6AAAAACEYKZWWOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTCNJSHAZTCOJZG4> . You are receiving this because you commented.Message ID: ***@***.***>