Addendum: 'until' can also denote times that are relative to the departure
of the vehicle (when the stops are part of a named route that is referenced
by the vehicle).
However, in this case the value of departure+stopUntil has the same
meaning: a vehicle cannot leave the stop before that time so if it travels
faster between the stops than your assumed in-transit times, it has to wait
until the scheduled time is reached.

Am Di., 21. Sept. 2021 um 08:02 Uhr schrieb Jakob Erdmann <
[email protected]>:

> 'until' is for absolute times that are printed in a schedule i.e. stop
> ends at "8:30:00", next stop ends at "8:34:00" (btw., sumo supports these
> human-readable time values as input and output)
> and these values force the bus to wait at least until that time before
> departing (so it will wait longer when arriving too early).
> If the bus often waits much longer than expected, this indicates that your
> schedule has too much slack or the simulated bus is driving faster than the
> real bus.
>
>
> Am Di., 21. Sept. 2021 um 02:16 Uhr schrieb vincentobiako <
> [email protected]>:
>
>> Sorry Jakob, I sent you the wrong testingbus.rou.xml file. The correct
>> one is attached.
>>
>>
>>
>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
>> Windows
>>
>>
>>
>> *From: *vincentobiako <[email protected]>
>> *Sent: *Monday, September 20, 2021 5:56 PM
>> *To: *Sumo project User discussions <[email protected]>
>> *Subject: *RE: [sumo-user] Question about Algorithms for Bus Bunching
>> Prevention SUMO
>>
>>
>>
>> Jakob
>>
>>
>>
>> I am having some trouble understanding what I am doing wrong with my bus
>> schedule that I created. I have a schedule that consists of stopping at bus
>> stops for 30 secs followed by moving to the next bus stop in 120 secs. The
>> schedule for the bus stops look something like this:
>>
>>
>>
>> *Simulation Time*
>>
>> *Bus_2*
>>
>> 3600
>>
>> BusStop
>>
>> In-Transit
>>
>> *      Until*
>>
>> 3630
>>
>> 30
>>
>> *BusStop1*
>>
>>
>>
>> 30
>>
>> 3750
>>
>>
>>
>>
>>
>> 120
>>
>> 3780
>>
>> 30
>>
>> *BusStop2*
>>
>>
>>
>> 150
>>
>> 3900
>>
>>
>>
>>
>>
>> 120
>>
>> 3930
>>
>> 30
>>
>> *BusStop3*
>>
>>
>>
>> 270
>>
>> 4050
>>
>>
>>
>>
>>
>> 120
>>
>> 4080
>>
>> 30
>>
>> *BusStop4*
>>
>>
>>
>> 390
>>
>> 4200
>>
>>
>>
>>
>>
>> 120
>>
>> 4230
>>
>> 30
>>
>> *BusStop5*
>>
>>
>>
>> 510
>>
>> 4350
>>
>>
>>
>>
>>
>> 120
>>
>> 4380
>>
>> 30
>>
>> *BusStop6*
>>
>>
>>
>> 630
>>
>> 4500
>>
>>
>>
>>
>>
>> 120
>>
>>
>>
>> The column on the far-right is representative of the “until” keyword that
>> is used in the xml code to represent when the bus can move to the next
>> stop. The issue that I am running into is that the bus at times seems to
>> stay longer 30 secs at some bus stops, especially when the simulation
>> progresses. Why exactly is this happening? Is this a built-in deviation or
>> variance in SUMO’s public transport model? Or is my xml code wrong?
>>
>>
>>
>> To give a little more context I have also attached my .net.xml, .rou.xml,
>> and additional files for the bus system. There is also traffic in this
>> model. Could that be the reason for the variation bus stop stop times?
>>
>>
>>
>> Thank you
>>
>> Ifezue
>>
>>
>>
>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
>> Windows
>>
>>
>>
>> *From: *Jakob Erdmann <[email protected]>
>> *Sent: *Friday, September 17, 2021 1:28 AM
>> *To: *Sumo project User discussions <[email protected]>
>> *Subject: *Re: [sumo-user] Question about Algorithms for Bus Bunching
>> Prevention SUMO
>>
>>
>>
>> The first thing you should do is define a real schedule with 'until'
>> values rather than relying on the 'duration' parameter alone:
>> https://sumo.dlr.de/docs/Simulation/Public_Transport.html#public_transport_schedules
>>
>> When this is used, any slack in the schedule is automatically used to
>> counteract bunching because the first bus (running behind schedule) can
>> start earlier than the second bus that has to wait for it's scheduled time.
>>
>> The tool ptLine2flows can be used to generate a synthetic schedule for
>> given sequences of stops:
>> https://sumo.dlr.de/docs/Tutorials/PT_from_OpenStreetMap.html
>>
>>
>>
>> regards,
>>
>> Jakob
>>
>>
>>
>> Am Fr., 17. Sept. 2021 um 03:13 Uhr schrieb vincentobiako <
>> [email protected]>:
>>
>> Hello Everyone
>>
>>
>>
>> I was curious to know if there was any python tools in SUMO that allowed
>> for the prevention of bus bunching from occurring with a given simulation?
>> If there is any, can you please direct me to an appropriate python tool?
>>
>>
>>
>> Thank you in advance for the help
>>
>> Ifezue
>>
>>
>>
>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
>> Windows
>>
>>
>>
>> _______________________________________________
>> sumo-user mailing list
>> [email protected]
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/sumo-user
>>
>>
>>
>>
>> _______________________________________________
>> sumo-user mailing list
>> [email protected]
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/sumo-user
>>
>
_______________________________________________
sumo-user mailing list
[email protected]
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/sumo-user

Reply via email to