-
Notifications
You must be signed in to change notification settings - Fork 5
feat: add scenario column to custom_costs.csv #361
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
base: master
Are you sure you want to change the base?
Conversation
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.
Looks good tks @daniel-rdt , let's upstream this once we have a final version
| "discount rate": 0.07 | ||
| "standing losses": 0 | ||
| custom_cost_fn: data/custom_costs.csv | ||
| custom_cost_scn: default |
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 think I would prefer this
| custom_cost_scn: default | |
| custom_cost_scenario: all |
| custom_costs_fn : str, optional | ||
| Custom cost modifications file path (default None). | ||
| custom_cost_scn : str, optional | ||
| Custom cost scenario to select in custom cost modification file (default ""). |
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.
| Custom cost scenario to select in custom cost modification file (default ""). | |
| Custom cost scenario to select in custom cost modification file (default "all"). |
Closes #315.
Changes proposed in this Pull Request
This PR proposes to add a scenario column to the
custom_costs.csvfile which can now also be used to handle scenario management via the newcosts:custom_cost_scnconfig parameter. The default behaviour remains unchanged, however, one now needs to specify an empty string for the case that thecustom_costs.csvfile should be ignored.As for other attributes in
custom_costs.csv, specifying "all" leads to the entry being applied independent of the scenario.Tasks
Workflow
costs:custom_cost_scnwhich is added also as a param to theprocess_cost_datarulecustom_costs.csvare applied for the given scenario and for "all". If empty string ("") is given, no custom_costs are applied.Open issues
Notes
Checklist
config/config.default.yaml.doc/configtables/*.csv.config/test/*.yaml.doc/release_notes.rstis added.