Closed colton-nevs closed 1 year ago
Unless traci.simulation.findIntermodalRoute() has changed, the time does not matter. The departure time is selected after the trip has been generated because you know when you need to be at your destination, and you will decide when to leave to be there on time. I need to know the expected travel time before I know when the trip should start..
I don't understand why the time would not matter if using PT timetables, unless there were an option to optimize for travel distance instead of time in traci.simulation.findIntermodalRoute()
When SAGA was implemented, traci.simulation.findIntermodalRoute() returned PT routes independently from the sim time or timetable. If now the implementation has changed, you are right. I don't know if/when I'll have time to validate this and change it if needed, but you are free to work on it and patch it! PRs are always welcome.
Great! Much fewer errors now. Thank you
For public transit routes, I get the following error
CRITICAL: _generate_intermodal_trip_traci from "['0']" to "['4']" with "public" generated 10 errors, trip generation aborted..
During the callstack
And the resulting route (line #109)
does not pass
sumoutils.is_valid_route()
becausestage.line==''
forall stages in the route, i.e. because it is a walking route. I believe this is because no depart time is provided, and the current simulation time is 0.0. This is midnight, when basically no PT routes are running, so its not surprising the cheapest route returned by this call totraci.simulation.findIntermodalRoute()
returns a walking route and the trip generation fails.I'm curious why in
activitygen._generate_intermodal_trip_traci()
, the depart time is selected after finding the_person_stages
?