Hi,
I'm trying to make a handover between SUMO-controlled and human-controlled vehicles. I use Vehicle::moveToXy() for that. When switching back to SUMO-controlled, I already learned to call Vehicle::setSpeed(id, -1) to get it to drive.
Now I'm getting funny results though, depending on the arguments I use to run SUMO. This is an example message in sumo-gui (note that the 'dist' here is a strange value):
Warning: Vehicle 'ego' moved by TraCI from 3400.37,1908.14 to 3400.37,1908.14 (dist 1973.84) with implied speed of 19738.40 (exceeding maximum speed 55.56). time=18.10.
Warning: Vehicle 'ego' moved by TraCI from 3400.37,1908.14 to 3400.37,1908.14 (dist 1973.84) with implied speed of 19738.40 (exceeding maximum speed 55.56). time=18.20.
Warning: Vehicle 'ego' performs emergency braking on lane '-15#1_1' with decel=9.00, wished=4.50, severity=1.00, time=18.30.
This changes when I remove '--log sumo_lastrun.log' from the arguments (which should not affect behavior, but it does and consistently so) when running, I get:
Warning: Vehicle 'ego' performs emergency braking on lane '-1300#1_1' with decel=132.50, wished=4.50, severity=28.44, time=15.60.
where edge '-1300#1_1' (it's an OpenDrive import) is nowhere near the edge (kilometers away). It then stops following the route with this emergency brake, while if I add the '--log' argument again, it continues driving on the route.
I recently updated to SUMO v1.16.0; could it be that using an older v1.15.0 library to link my application with could cause these kinds of behaviors? (different binary communication protocols or such). I also saw on another occasion the human-controlled vehicle changing size and heading erratically.
Thanks,
Ruud
