Debugging travel search is very time consuming, so it would be nice to have an option to print every event that happens to one trip - also when it is dominated and dropped.
Design
Request:
// Print events for the given list of stops indexes
debugStops="14585, 42038, 61157, 11116"
// Print all events for the given trip only. The debugging will start to print events for the
// first stop marked with an '*'
debugTrip="45185, 62028, *16157, 16426, 39886, 82455"
// Debug events
debugEvents="ARRIVAL, "
We already half way support the debugging stop events, but it does explicit print when a trip i dropped - dominated by an other trip.
To debug a set of stops now the code must be changed, not passed in as part of the request. I would like it to be part of the request, and that the result returned.
Today only ADDING an arrival and PATH found is printed as an event, but often the problem is that e stop is dominated and is dropped from the set, it would be nice i it is possible to add this to the printed events.
Debugging travel search is very time consuming, so it would be nice to have an option to print every event that happens to one trip - also when it is dominated and dropped.
Design
We already half way support the debugging stop events, but it does explicit print when a trip i dropped - dominated by an other trip.
To debug a set of stops now the code must be changed, not passed in as part of the request. I would like it to be part of the request, and that the result returned.
Today only ADDING an arrival and PATH found is printed as an event, but often the problem is that e stop is dominated and is dropped from the set, it would be nice i it is possible to add this to the printed events.