-
Notifications
You must be signed in to change notification settings - Fork 2
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
[IIDM v1.2] Add regulation for shunt compensators #38
Projects
Comments
sebalaig
added a commit
that referenced
this issue
May 5, 2020
Signed-off-by: Sébastien LAIGRE <slaigre@silicom.fr>
5 tasks
sebalaig
added a commit
that referenced
this issue
May 5, 2020
Signed-off-by: Sébastien LAIGRE <slaigre@silicom.fr>
mathbagu
changed the title
[IIDM v1.1] Add regulation for shunt compensators
[IIDM v1.2] Add regulation for shunt compensators
May 12, 2020
sebalaig
added a commit
that referenced
this issue
Jun 19, 2020
Signed-off-by: Sébastien LAIGRE <slaigre@silicom.fr>
5 tasks
sebalaig
added a commit
that referenced
this issue
Jun 25, 2020
Signed-off-by: Sébastien LAIGRE <slaigre@silicom.fr>
Fixed in PR #93 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Feature
Add regulation in shunt (IIDM/XIIDM) powsybl-core#958
Allow to write IIDM-XML files in previous versions powsybl-core#1129
Fix bug: check target deadband when setting regulation status to prevent inconsistent data powsybl-core#1204
What is the current behavior?
tapChanger.targetDeadband
is not mandatory when the tap changer is regulatingtapChanger.targetDeadband
should be mandatory when the tap changer is regulating (same behaviour for shunt compensators)What is the motivation / use case for changing the behavior?
Have both Java and C++ API as close as possible
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)
(if a question doesn't apply, you can delete it)
The text was updated successfully, but these errors were encountered: