-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fix bug injection setpoint shunt compensator can be applied #1005
Fix bug injection setpoint shunt compensator can be applied #1005
Conversation
@@ -163,6 +163,17 @@ void applyOnShuntCompensator() { | |||
assertEquals(2., network.getShuntCompensator("SC1").getSectionCount(), 1e-3); | |||
} | |||
|
|||
@Test | |||
void canBeAppliedOnShuntCompensator() { |
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.
good catch. please add a test with setpoint = 2 (canBeApplied = true) and setpoint = 1 (canBeApplied = true)
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.
done
please fill PR description |
It change the behavior but it is a bug fix, so is it a breaking change? |
90f5b02
to
bd3ca0e
Compare
Signed-off-by: Pauline Jean-Marie <[email protected]>
…be inferior to the max Signed-off-by: Pauline Jean-Marie <[email protected]>
bd3ca0e
to
c11472a
Compare
no, not a breaking change |
Signed-off-by: belthlemar <[email protected]>
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
No
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
Injection set point on shunt compensator cannot be applied (called by network action apply) if the setpoint is equal or below the max section count of the shunt compensator.
What is the new behavior (if this is a feature change)?
Injection set point on shunt compensator cannot be applied (called by network action apply) if the setpoint is strictly above the max section count of the shunt compensator.
Does this PR introduce a breaking change or deprecate an API?