Re: [sumo-user] Speed below 0

A simple solution would be to limit decel per time step to the current vehicle speed.
Within a timeStep there is practically no difference whether the vehicle brakes from 0.1 to 0 with decel 4.5 or decel 0.1 because other vehicles only "see" the end result after the step.
Basically, you are dealing with discretization errors due to step-length. Of course you could lower the step-length to reduce this error. (At step-length 0.02 you could brake the last 0.1m/s with 5m/s^2 in a single step).

Am Mo., 20. Apr. 2020 um 08:34 Uhr schrieb Bae, Jong In <jbae42@xxxxxxxxxx>:
Good morning,

My team is developing a scenario with aggressive merging behavior. As shown on the screenshot attached, blue vehicles are trying to merge in front of the first yellow vehicle as aggressively as possible. Our goal is to slow down the first yellow vehicle (target vehicle) significantly and bring it close to stop as results of the aggressive merging events. While we were able to achieve our goal as seen in the vehicle speed on the attached screenshot, we are running into an error saying that the speed cannot be below 0.

We understand that this error is due to the deceleration rate of -4.50 when the speed is 0.10.  But we are curious if there is any way we can make this vehicle go to 0m/s instead of negative speed despite the deceleration rate greater than the current speed. We are also seeking any alternative ways that we can have events like these (vehicles coming to stop due to hard braking) without errors.

Any suggestion would be greatly appreciated.