Tc issue 80 #105
Tc issue 80 #105
Conversation
… directories to seperate scheduled implementation from frequency implementation. This is a WIP.
… into tc_issue_80
|
Problem with historical average as it is failing to calculate duration. This is likely to do with new cache implementations. It is reverting to the "last vehicle" method of generating a prediction. |
- it requires to have only 1 direction (0) - if direction is not defined in vehicleDetail information, it will assume 0
|
Reloading cache from database on startup, for freq based services, not working. |
Change of LOOP_ENDING_MAX_DISTANCE constant to 200 m
The size of the div container is a little bit bigger to show the whole tooltip.
|
The prediction accuracy module is not working for frequency based services. This seems to relate to the original GTFS I used for Bullrunner not having a direction for a trip. |
|
Values in bold below should be the same. 14:53:55.813 Kalman has last vehicle info for : Indices [blockId=5, tripId=5, tripIndex=0, stopPathIndex=13, segmentIndex=0] : TravelTimeDetails [departure=Departure [vehicleId=1121, time=10-01-2018 08:41:17.356 EST, route=C, rteName=C, directionId=null, stop=116, gtfsStopSeq=13, stopIdx=12, freqStartTime=Mon Oct 01 10:19:59 EDT 2018, stopOrder=-1, avlTime=08:41:46.000 EST, trip=5, tripIdx=0, block=5, srv=Mo, cfg=0, pathLnth=413.23m], arrival=Arrival [vehicleId=1121, time=10-01-2018 08:41:57.081 EST, route=C, rteName=C, directionId=null, stop=426, gtfsStopSeq=14, stopIdx=13, freqStartTime=Mon Oct 01 10:19:59 EDT 2018, stopOrder=-1, avlTime=08:42:09.000 EST, trip=5, tripIdx=0, block=5, srv=Mo, cfg=0, pathLnth=282.94m], getTravelTime()=39725, sanityCheck()=true] 14:53:55.813 Kalman has 3 historical values for : Indices [blockId=5, tripId=5, tripIndex=0, stopPathIndex=13, segmentIndex=0] 14:53:55.813 Generating Kalman prediction for : Indices [blockId=5, tripId=5, tripIndex=0, stopPathIndex=13, segmentIndex=0] 14:53:55.813 Kalman is using historical value : TravelTimeDetails [ 14:53:55.813 Kalman is using historical value : TravelTimeDetails [ 14:53:55.813 Kalman is using historical value : TravelTimeDetails [ |
…ey should be generated.
…ed as they should be generated." This reverts commit 6373d58.
Tc issue 117
#80
This is a first draft of Kalman (for travel times) and RLS(for dwell times) for frequency based services.