Re: [sumo-user] Unexpected behavior with containerStops

[Jakob Erdmann <namdre.sumo@xxxxxxxxx>]

Yes. This is expected behavior (though I admit it could be improved). The route only gets expanded to the full path after the next call to simulationStep. Adding the stop in the next  step should work.

regards,

Jakob

Am Mo., 26. Aug. 2019 um 16:34 Uhr schrieb Paolo Bolzoni <paolo.bolzoni.brown@xxxxxxxxx>:

Dear list,

See this code. Assume the variable "path" contains a sequence of edges
starting from 4539789#1 and arriving to 4469078#5. The commented line
instead contains only the extremes.

    traci.route.add('t1', path)
#    traci.route.add('t1', ['4539789#1', '4469078#5'])
    traci.vehicle.add('v1', 't1', typeID='garbagetruck')
    traci.vehicle.setContainerStop('v1',
'containerStop_4469078#5_0_1', duration=300)

Using the whole path the vehicle does stop for 300 seconds at the
container stop, but while using only the two extremes it does not. Is
this behavior intended? Or I am missing something?

Yours faithfully,
Paolo
_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/sumo-user