You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem description
While using the algorithm of the state estimation our developement team noticed something unusual in the behaviour of the function.
Two behaviours occured with our input:
State estimation function went into an infinite loop in this function epsilon value is never converging to the wanted result.
When the epsilon value converges the return are some values that are not accurate and descriptive of the grid (like Nan and infinite values)
To Reproduce
Build an example like this one but instead of the Voltage magnitude and phase input provide in input Voltae magnitude(MeasType.V_mag), active and reactive power.
Expected behavior
Return a state of all the input grid with relevant values trough the Result class included in the pyvolt.result module, where all nodes and branches informations after estimation are contained.
Additional context
The issue has already been discussed with Jan Dinkelbach, member of the community, who gave to the team support and noticed that this behaviour is not normal and could be fixed.
The text was updated successfully, but these errors were encountered:
Problem description
While using the algorithm of the state estimation our developement team noticed something unusual in the behaviour of the function.
Two behaviours occured with our input:
To Reproduce
Build an example like this one but instead of the Voltage magnitude and phase input provide in input Voltae magnitude(MeasType.V_mag), active and reactive power.
Expected behavior
Return a state of all the input grid with relevant values trough the Result class included in the pyvolt.result module, where all nodes and branches informations after estimation are contained.
Additional context
The issue has already been discussed with Jan Dinkelbach, member of the community, who gave to the team support and noticed that this behaviour is not normal and could be fixed.
The text was updated successfully, but these errors were encountered: