-
Notifications
You must be signed in to change notification settings - Fork 25
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
[Feature] Automatic Tap Changer C API #597
Conversation
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
power_grid_model_c/power_grid_model_c/include/power_grid_model_c/basics.h
Outdated
Show resolved
Hide resolved
…_c/basics.h Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com> Signed-off-by: Martijn Govers <martygovers@hotmail.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <martijn.govers@alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
4b69697
to
2f3df3b
Compare
…imilar) Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
power_grid_model_c/power_grid_model/include/power_grid_model/common/exception.hpp
Show resolved
Hide resolved
@mgovers I have reviewed and approved the PR. I am not sure if this should now be merged before |
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
…Model/power-grid-model into feature/auto-tap-c-api Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
This reverts commit 7b16edb. Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
i don't think it matters. with the current implementation in this PR, you do get the optimal state - just not the optimal tap positions. I would consider it a After this PR is merged, the validation tests can already be created and even run - provided we do not check for the tap positions. We can also start the Python API creation. Since we do not give any guarantees for experimental features, I think having If |
Quality Gate passedIssues Measures |
OptimizerType optimizer_type{OptimizerType::no_optimization}; | ||
OptimizerStrategy optimizer_strategy{OptimizerStrategy::any}; | ||
|
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.
Oh, I was under the impression this was intentionally left out of this PR?
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.
no that was #599 , which blocked work on the C API (this PR)
PGM_TapChangingStrategy
enumPGM_set_tap_changing_strategy
option setter