-
Notifications
You must be signed in to change notification settings - Fork 46
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
core: fix and reintroduce pathfinding heuristic #8145
Conversation
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## dev #8145 +/- ##
============================================
+ Coverage 28.12% 28.16% +0.03%
- Complexity 2112 2120 +8
============================================
Files 1296 1299 +3
Lines 158648 158758 +110
Branches 3164 3176 +12
============================================
+ Hits 44620 44714 +94
- Misses 112126 112141 +15
- Partials 1902 1903 +1
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.
LGTM. For other optional reviewers, I suggest comparing this commit with 1122145, where the remaining distance classes were previously removed.
core/src/main/kotlin/fr/sncf/osrd/api/pathfinding/PathfindingBlocksEndpoint.kt
Outdated
Show resolved
Hide resolved
core/src/main/kotlin/fr/sncf/osrd/api/pathfinding/RemainingDistanceEstimator.kt
Outdated
Show resolved
Hide resolved
c31b1e3
to
977dcbc
Compare
977dcbc
to
e092e40
Compare
core/src/main/kotlin/fr/sncf/osrd/api/pathfinding/PathfindingBlocksEndpoint.kt
Outdated
Show resolved
Hide resolved
It was too slow to be worth using, and needed to be adapted to return times instead of distances
e092e40
to
a9ec24c
Compare
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
Fix #7200
Change summary:
When running the benchmark, average process time per train goes from 40s to 25s. (note: this includes more than just the pathfinding). No extra error.
While tested I compared the old and new distance methods. The new one is less accurate, but it's not off by more than 0.1%.