Skip to content
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

Conversation

figueroa1395
Copy link
Contributor

@figueroa1395 figueroa1395 commented Jan 8, 2025

Add missing tests and refactor inappropriate ones for (#826):

  • Add validation test case for transformer control side on the HV side. This test is marked as failing.
  • Add validation test case for a step up transformer. This test is marked as failing.
  • Add new test grid, as a unit test, for transformer ranking that works with the new logic.

Signed-off-by: Santiago Figueroa Manrique <[email protected]>
@figueroa1395 figueroa1395 added the feature New feature or request label Jan 8, 2025
@figueroa1395 figueroa1395 self-assigned this Jan 8, 2025
@figueroa1395 figueroa1395 marked this pull request as draft January 8, 2025 14:15
@Jerry-Jinfeng-Guo
Copy link
Contributor

@figueroa1395 figueroa1395 changed the title Validation tests for step up transformer Step-up transformer tap changer support: additional tests Jan 8, 2025
@figueroa1395
Copy link
Contributor Author

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]>
@figueroa1395 figueroa1395 marked this pull request as ready for review January 9, 2025 14:24
@nitbharambe
Copy link
Member

nitbharambe commented Jan 10, 2025

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?

Signed-off-by: Santiago Figueroa Manrique <[email protected]>
Copy link
Contributor

@Jerry-Jinfeng-Guo Jerry-Jinfeng-Guo left a 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 under tests/data/power_flow/ directly, instead, the content should be arranged like all other cases in tests/data/power_flow/automatic_tap_regulator and have step-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

tests/cpp_unit_tests/test_tap_position_optimizer.cpp Outdated Show resolved Hide resolved
tests/cpp_unit_tests/test_tap_position_optimizer.cpp Outdated Show resolved Hide resolved
Signed-off-by: Santiago Figueroa Manrique <[email protected]>
@figueroa1395
Copy link
Contributor Author

  • The step-up-transformer-single should not live under tests/data/power_flow/ directly, instead, the content should be arranged like all other cases in tests/data/power_flow/automatic_tap_regulator and have step-up-transformer-single prefixing all cases

Okay, addressed. In addition, given your other question, I have renamed those test with the prefix trafo-control-side-HV. The prefix step-up-transformer will be used in the remaining test (work in progress).

  • 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

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 step-up-transformer.

Until I add the missing validation test, I am putting back this PR into draft.

@figueroa1395 figueroa1395 marked this pull request as draft January 13, 2025 14:22
@figueroa1395 figueroa1395 marked this pull request as ready for review January 21, 2025 10:24
Copy link
Member

@nitbharambe nitbharambe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work!

@figueroa1395 figueroa1395 dismissed Jerry-Jinfeng-Guo’s stale review January 21, 2025 11:05

Changes have been addressed.

@figueroa1395 figueroa1395 merged commit 84dcd7f into feature/step-up-transformer-tap-changer-support Jan 21, 2025
28 checks passed
@figueroa1395 figueroa1395 deleted the step-up-trafo-validation branch January 21, 2025 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants