Event System Design Specification#389
Closed
lukelowry wants to merge 1 commit into
Closed
Conversation
lukelowry
force-pushed
the
lukel/event-system-design
branch
from
19220d7 to
523932c
Compare
Collaborator
Author
|
I think this would be very valuable to have right now so we can express different kinds of disturbances, but I don't think there has been enough collective thought or discussion yet on how perturbations/events will work. Given the pace of GK, closing |
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
1 participant
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.
Description
A draft of the event system draft with three supported events (fault on bus and branch, and branch opening).
Proposed changes
EVENTS.mddetailing how to invokeapplyand typed ActionsREADME.mdforPDSimdetailing solver file formatActionssection forBusandBranch, which details the supported actions for each respective component.@pelesh Thinking through this is helping inform some downstream concerns with other models and behavior. If you have a different design direction you want to consider, I am all ears; this is just what is intuitive to me personally.
Further comments
This will allow us to remove
BusFault, simplifying case creation and reducing bloat in case files. My external tool that translates cases from PowerWorld can then support what PW callscontingencies, which is on a par with thescheduleI proposed here (allowing me to further streamline verification)