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

cicuit breaker position seems to be not deterministic #100

Closed
nesnoj opened this issue Dec 15, 2016 · 2 comments
Closed

cicuit breaker position seems to be not deterministic #100

nesnoj opened this issue Dec 15, 2016 · 2 comments
Assignees
Labels
Milestone

Comments

@nesnoj
Copy link
Member

nesnoj commented Dec 15, 2016

position changes with different runs - WTF

Related to #40, #97, #98

@nesnoj nesnoj added the bug label Dec 15, 2016
@nesnoj nesnoj added this to the pre-Release Dingo v0.1 milestone Dec 15, 2016
@nesnoj nesnoj self-assigned this Dec 15, 2016
@nesnoj
Copy link
Member Author

nesnoj commented Dec 15, 2016

With mv routing only, the circuit breakers do not seem to change positions. After connection of satellites they seem to be shifted though. So next step is to check mv_connect.connect_node() what happens with the circuit breakers.
Proposal: The circuit breakers have to be relocated after connection of satellites (and stations?) -> a more general method (currently done during routing only) is required to determine the optimal position that can be called within routing and later on as well.

@nesnoj
Copy link
Member Author

nesnoj commented Dec 19, 2016

Done in f5745a6.
The circuit breaker positions are now recalculated with final grid (after routing, satellites + stations).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant