-
Notifications
You must be signed in to change notification settings - Fork 3
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
Refactor: Replace connected nodes with edges #42
base: main
Are you sure you want to change the base?
Refactor: Replace connected nodes with edges #42
Conversation
Add get_opposite_node to calculate given a one of the top nodes the other one. Add get_next_geo_node to calculate the neighbor geo node given one of the top nodes
Replace setting operations of connected_on_... with new connected_edge_on_... property.
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.
Great job, I found one little mixup
Co-authored-by: Lietze <[email protected]>
fixes Bug: Wrong calculation of "Anschluss" if connected edges are long and not straight simulate-digital-rail#41
7a6def0
to
51f8a77
Compare
@antonykamp Whats the status of this PR? |
I forward this to @Lietze and @SaturnHafen 😇 |
As far as I am concerned this (and all the other PRs across the org) are ready for review. I will mark them as ready :) Edit: I don't have permissions to mark this pr as ready |
Also: The |
This PR replaces
connected_nodes
and its dependencies withconnected_edges
in theNode
class and introducesconnected_nodes
as property again.Additionally, it adds two functions to the
Edge
class to get the opposite node given one top node and the neighbor geo node given a top node.fixes #40