Invalid intersection of trainlines #1

Closed
opened 2021-03-04 21:36:58 +01:00 by markus · 4 comments

I don't think it's the following, but I've seen some weird behavior in regard to this...

Let there be the following scenario.

Trainline A and Trainline B visually cross at point A. Now, exactly (aka rounded to) this point, we intersect Trainline A with an access layer. -> New point created here.

Problem: For some reason, I have now seen a path going directly from Trainline A to Trainline B to the access layer...

I don't think it's the following, but I've seen some weird behavior in regard to this... Let there be the following scenario. Trainline A and Trainline B visually cross at point A. Now, exactly (aka rounded to) this point, we intersect Trainline A with an access layer. -> New point created here. Problem: For some reason, I have now seen a path going directly from Trainline A to Trainline B to the access layer...
Poster
Owner

RN, it can be seen with CFE and E1 from 264,116 to 813,2998.

RN, it can be seen with CFE and E1 from 264,116 to 813,2998.
Poster
Owner

Hmm might there actually be an invalid "upgrade" of a trainline to an access path due to a bugged intersect/split?

Hmm might there actually be an invalid "upgrade" of a trainline to an access path due to a bugged intersect/split?
Poster
Owner

Nope, I just literally forgot to exclude intersecting trainlines with each other...

See: https://git.notsyncing.net:8080/markus/lifo-dijkstraserv/src/master/src/dijkstragraph.c#L317

Nope, I just literally forgot to exclude intersecting trainlines with each other... See: https://git.notsyncing.net:8080/markus/lifo-dijkstraserv/src/master/src/dijkstragraph.c#L317
Poster
Owner

Fixed in 50c39a52bb.

Fixed in 50c39a52bbbafb38ea6cf3505ca05816af628c20.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: markus/lifo-dijkstraserv#1
There is no content yet.