-
Notifications
You must be signed in to change notification settings - Fork 33
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
Step-up transformer tap changer support: additional tests #868
Step-up transformer tap changer support: additional tests #868
Conversation
Signed-off-by: Santiago Figueroa Manrique <[email protected]>
Could you update the naming etc as per agreement? https://power-grid-model.readthedocs.io/en/stable/contribution/CONTRIBUTING.html#pull-request-process |
Thanks for the reminder, I had forgotten. Fixed accordingly. |
Signed-off-by: Santiago Figueroa Manrique <[email protected]>
AKI's use case was this way: source -- (HV)transformer(MV) -- (MV)transformer(higher MV with tap and control side) -- load Can you also create a case? Such that source are at other place than control and tap_side? |
tests/data/power_flow/step-up-transformer/max-voltage-tap/input.json
Outdated
Show resolved
Hide resolved
Signed-off-by: Santiago Figueroa Manrique <[email protected]>
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.
- The
step-up-transformer-single
should not live undertests/data/power_flow/
directly, instead, the content should be arranged like all other cases intests/data/power_flow/automatic_tap_regulator
and havestep-up-transformer-single
prefixing all cases - Could you explain to me how is the validation case in the input json files constructed? You put the control side at the other side, but you still have high voltage at from side
Signed-off-by: Santiago Figueroa Manrique <[email protected]>
Okay, addressed. In addition, given your other question, I have renamed those test with the prefix
To my understanding, previously it was forbidden to have the control side on the HV side, however, with the change of logic, it can now be positioned at the LV side. Hence, the current validation cases try to reflect this. On the contrary, this validation case doesn't reflect the specific edge case that AKI ran into, pointed out by you and @nitbharambe as well. For this reason, I am working in an additional validation case, which will include not only the control side at the HV (relative) side, but also away from the source. These set of tests are to be prefixed Until I add the missing validation test, I am putting back this PR into draft. |
Signed-off-by: Santiago Figueroa Manrique <[email protected]>
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.
Great work!
Quality Gate passedIssues Measures |
Changes have been addressed.
84dcd7f
into
feature/step-up-transformer-tap-changer-support
Add missing tests and refactor inappropriate ones for (#826):