-
Notifications
You must be signed in to change notification settings - Fork 44
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
editoast: infra/{id}/pathfinding starts in both directions #5904
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## dev #5904 +/- ##
============================================
+ Coverage 25.74% 25.80% +0.06%
Complexity 2117 2117
============================================
Files 926 926
Lines 122479 122526 +47
Branches 2665 2665
============================================
+ Hits 31534 31620 +86
+ Misses 89372 89333 -39
Partials 1573 1573
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
We have a 400 error.
{
"status": 400,
"type": "editoast:JsonError",
"context": {
"cause": "Json deserialize error: unknown field `direction`, expected `track` or `position` at line 1 column 84"
},
"message": "Json deserialize error: unknown field `direction`, expected `track` or `position` at line 1 column 84"
}
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.
Lgtm for the front part :)
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.
Actually front looks good but got the same error as @flomonster when trying to search for routes
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.
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.
I still have a problem, some valid existing routes can't be recomputed.
I've checked that this isn't due to the geographical max distance.
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.
Lgtm
…the initial direction
editoast computes k-shortest path. When we are along a simple line, the next shortest path can be significant longer than the initial solution. This commit limits any subsequent path to be at most twice as long as the best solution. From an implementation point of view, we need to track the total length at each step. This is a bit cumbersome, but we can’t access with the pathfinding crate to cost data.
Closes #5543