Add functionality for timedependent forced outage #1172
Conversation
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
…d_outage and time-to-repair - added "on_conflict = replace" to prevent eroneous timeseries
Contributor
|
@mihlema This would be great and it's nice that you're complimenting the existing forced outage functionality. It would be great if we could fix the conflicts and merge |
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.
In order to account for time-dependent outage rates (e.g., influenced by weather, see for example: Murphy - A time-dependent model of generator failures and recoveries captures correlated events and quantifies temperature dependence, it'd be nice to be able to support MTTF and MTTR as timeseries parameters. The adaptation for this script supports this, with the caveat that timeseries currently only supports Float values. The script will treat Floats as number of Days for respective parameters.
Other than minor update to write_parameter function (was outdated) and added the keyword "on_conflict"=replace. The latter one seemed reasonable as I was testing and noticed that I created "more and more" outages, as the script would append the timeseries, leading to erroneous timeseries for forced outages. I left it as an optional keyword, In case e.g. do want to append an existing timeseries (e.g., originally created for year x, and now appended for year y, as long as they don't overlap)
Fixes # (no issue addressed)
Checklist before merging