reg controller winding field#184
Merged
Merged
Conversation
|
There was a problem hiding this comment.
Pull request overview
Adds a new data-model field to RegulatorController so consumers (e.g., OpenDSS export) can target which transformer winding a regulator controller acts on, avoiding incorrect implicit defaults during conversion.
Changes:
- Introduces a
tapped_windingfield onRegulatorControllerwith validation constraints and a description.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Change Summary
Add a field to Regulator controllers to specify which winding is to be acted upon. If not specified, when converted to opendss, a default of 1 will take effect, which is often wrong.
Related issue number
Checklist