Add economic cost overrides and dotted sweeps - #119
Merged
Conversation
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This makes BREOS's economic assumptions directly configurable and sweepable without requiring a throwaway cost preset for every price or CAPEX value. It delivers Phase 0 of the economic-scenario roadmap while keeping the existing flat-pricing model and preset results unchanged.
Summary
[costs]override table with explicit precedence: user override → named preset →CostParamsdefaultCostParamsmapping so App presets and lower-level config construction cannot drift"costs.electricity_cost"andcosts.storage_cost_per_kwhCompatibility
Existing configurations need no changes. With no
[costs]table, named presets and dataclass defaults resolve exactly as before; the residential Portugal preset is pinned character-for-character in a regression test. Sweep CSV columns retain the existingparam_...convention, including dotted names such asparam_costs.electricity_cost.This is intentionally only the override seam. Escalator decomposition, scenario orchestration, switching values, currency, and time-of-use valuation remain in their roadmap phases.
Validation
-Wpassed