-
Notifications
You must be signed in to change notification settings - Fork 46
Documentation: automatic tap changer behavior #1170
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
base: main
Are you sure you want to change the base?
Changes from 6 commits
68ac0a1
8d81fa4
7ee77ca
e12f056
e60a06a
0a54a46
df18aab
fab9422
5c258f7
772a50d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -952,6 +952,33 @@ along the exploitation direction. | |
| | linear search | Start with an initial guess and do a local search with step size 1 for each iteration step. | | ||
| | binary search | Start with a large search region and reduce the search region by half for every iteration step. | | ||
|
|
||
| ##### Regulatable voltage range outside `u_band` | ||
|
|
||
| In the case of an unrealistically set volatage and `u_band`, the viable voltage range regulatable can fall outside | ||
| this target band. | ||
| This will lead the regulator returning the tap that results in the closest voltage level to the target band. | ||
|
||
|
|
||
| ##### Error type `MaxIterationReached` | ||
|
|
||
| When the regulator can not find a suitable voltage after iterations, error `MaxIterationReached` will be thrown. | ||
Jerry-Jinfeng-Guo marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| We define the maximum iterations per transformer to be twice the amount of total taps possible. | ||
| This failure happens in the following type of scenario: | ||
|
|
||
| - The per tap voltage step size in the regulatable voltage range is (significantly) larger than the `u_band` set by the | ||
| input data. This will likely cause the regulator to go back and forth between two tap positions and eventually | ||
| reach a pre-defined limit. | ||
|
|
||
| This error is a result of the two types search method used; `linear` and `binary`: | ||
|
|
||
| - Linear search method, used for `any_valid_tap` strategy, will try to go one tap up or down per iteration. | ||
| If there is no valid tap position available, linear search method will keep trying until the maximum iteration | ||
| for this transformer is reached. | ||
| - Binary search method, used for the other three strategies, will iteratively narrow down search space by half and will | ||
| run into a state where the searchable space is no longer viable. This is equivalent to the maximum iteration | ||
| reached scenario for the linear search method. | ||
|
|
||
| In conclusion, when there is no suitable tap, error `MaxIterationReached` will be thrown. | ||
|
|
||
| ## Batch Calculations | ||
|
|
||
| Usually, a single power-flow or state estimation calculation would not be enough to get insights in the grid. | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.