Update Configuration Options on Website

[trevorb1]

Type of documentation issue

Missing Information

Issue Description

Taking a quick look, there are quite a few missing configuration options from the website with recent updates. Below is a shortlist:

• [x] run: validation
• [x] scenario: planning_horizon and foresight options should maybe be listed in a table for consistency?
• [ ] electricity: gaslimit_enable (this is listed as only sector studies, so I wonder if it should be moved to the sector section?)
• [x] electricity: retirement (oh. This is actually there, just under the wrong section!)
• [ ] electricity: SAFE_reservemargin (maybe link to opts wildcard section)
• [x] electricity: operational_reserve: activate
• [x] electricity: operational_reserve: epsilon_load
• [x] electricity: operational_reserve: epsilon_vres, contingency
• [x] electricity: operational_reserve: contingency
• [x] electricity: demand: EFS_case
• [x] electricity: demand: EFS_speed
• [ ] electricity: demand: eulp
• [x] electricity: autarky: enable
• [x] electricity: autarky: by_country
• [x] renewable: hydro (not missing, just that it is nested under solar)
• [x] renewable: offwind (not missing, just nested under onwind)
• [x] lines: dynamic_line_rating (not missing, just missformatted with #NAME? in the table)
• [x] load - info here is nested under electricity in the config file. (We may want to explore explaining the scaling_factor better as well. Not clear if this is energy scaling or electricity scaling. Depending on the answer, we may want to look at collapsing the electricity: demand options and this together?)
• [ ] costs: ng_fuel_year (I think we should just be removing this and pull directly from snapshots. Then if we are outside of the 2019-2023 timeframe, we use EIA data to stay consistent with weather years. I am skeptical of the benefits of higher res ng prices if they are not matched to weather. But maybe this is a discussion for a different thread!)
• [x] costs: emission_prices: enable
• [x] costs: emission_prices: co2_monthly_prices
• [x] focus_weights (This is currently in a note, but should probably be in a table?)
• [x] countries (can probably remove)
• [x] conventional: dynamic_fuel_prices (make note that EIA API key must be provided and provide link to website to get the key)

For the following, I wonder if we should just move them to parameters in the workflow since they are configuration files, rather than configuration options? I guess the argument for keeping as is in case you want to have multiple different files.

• electricity: regional_Co2_limits: config/policy_constraints/regional_Co2_limits.csv
• electricity: agg_p_nom_limits: config/policy_constraints/agg_p_nom_minmax.csv
• electricity: portfolio_standards: config/policy_constraints/portfolio_standards.csv
• electricity: SAFE_regional_reservemargins: config/policy_constraints/SAFE_regional_prm.csv

Also, I wonder if we should look at trying to reduce the enable keywords in here? Like, we either provide a value, else if we provide false it is automatically disabled? Just a thought, not married to this idea! :)

Link to existing documentation

No response

Suggested Update

No response

Additional Info

No response

[ktehranchi]

Sounds good, yes we definitely need to add to this documentation. I can add some detail for the non-sector items. But go for it if you have time before the tutorial, would be appreciated.

RE: 'enable' keywords. those are holdovers from using the pypsa-eur's prepare_network file. They are used for determining the Opts in sector studies I believe. I included them in there so we can continue using the Eur script but at this point we could probably depart from Eur.... and remove the subworkflow all together if we wanted to since this is the only rule directly using Eur.

[ktehranchi]

Questions for Trevor:

• [ ] electricity: retirement (oh. This is actually there, just under the wrong section!) I didn't see why this is the wrong section??

• [ ] load - info here is nested under electricity in the config file. (We may want to explore explaining the scaling_factor better as well. Not clear if this is energy scaling or electricity scaling. Depending on the answer, we may want to look at collapsing the electricity: demand options and this together?) I don'y think the 'load' configuration is used anywhere actually, i thought this was something you had implemented. So I removed this.

• [ ] conventional: dynamic_fuel_prices (make note that EIA API key must be provided and provide link to website to get the key) I made an update to the install instructions that you need to get the API key for dynamic fuel pricing to work

Item's Remaining:

• [ ] electricity: gaslimit_enable (this is listed as only sector studies, so I wonder if it should be moved to the sector section?)

• [ ] electricity: SAFE_reservemargin (maybe link to opts wildcard section)

• [ ] electricity: operational_reserve: activate

• [ ] electricity: operational_reserve: epsilon_load

• [ ] electricity: operational_reserve: epsilon_vres, contingency

• [ ] electricity: operational_reserve: contingency

• [ ] electricity: demand: EFS_case

• [ ] electricity: demand: EFS_speed

• [ ] electricity: demand: eulp

• [ ] electricity: autarky: enable

• [ ] electricity: autarky: by_country

• [ ] costs: ng_fuel_year (I think we should just be removing this and pull directly from snapshots. Then if we are outside of the 2019-2023 timeframe, we use EIA data to stay consistent with weather years. I am skeptical of the benefits of higher res ng prices if they are not matched to weather. But maybe this is a discussion for a different thread!)

• [ ] costs: emission_prices: enable

• [ ] costs: emission_prices: co2_monthly_prices