Include waiting time at beginning and end in TransitGeneralizedCostFilter - #4188
Conversation
| * <li>To set an absolute value(3000) use: {@code 3000 + 0x} | ||
| * </ul> | ||
| * The default is {@code 3600 + 2x} - 1 hours plus 2 times the lowest cost. | ||
| * The default is {@code 900 + 1.5x} - 15 minutes plus 1.5 times the lowest cost. |
There was a problem hiding this comment.
Why are we changing default value now?
There was a problem hiding this comment.
The introduction of the intervalRelaxFactor make the function work different than before, so it make sence to change the defaults as well.
|
I tested this today and can confirm that it solves the problem I described at #4167 (comment) |
13ad1af to
f94ed77
Compare
Codecov Report
@@ Coverage Diff @@
## dev-2.x #4188 +/- ##
=============================================
+ Coverage 57.06% 57.14% +0.07%
- Complexity 10747 10784 +37
=============================================
Files 1430 1430
Lines 58032 58116 +84
Branches 6720 6729 +9
=============================================
+ Hits 33117 33211 +94
+ Misses 22906 22895 -11
- Partials 2009 2010 +1
Continue to review full report at Codecov.
|
Co-authored-by: Thomas Gran <t2gran@gmail.com>
85c93d5 to
ea306cc
Compare
Co-authored-by: Thomas Gran <t2gran@gmail.com>



Summary
This PR improves filtering done in TransitGeneralizedCostFilter, in order to be able to have a tighter value for the filtering function, meaning that we get less worse results close in time, but more results far away from the best itinerary.
Issue
Fixes #4167
Unit tests
Updated the test with no cost for wait time, and some cost for wait time.