Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sumo-user] Difference between traci and sumolib

Internally, the functions use the exact same SUMO functions and are therefore expected to behave exactly the same.
The most likely reason why you observe different behavior is because your call to libsumo runs a different version of sumo compared to the traci call.
The easiest way to check this is to write any xml output file (i.e. tripinfo-output) with traci / libsumo and check for the version info at the top of the file.

Am Fr., 10. Juli 2026 um 16:20 Uhr schrieb Ramseier Thomas via sumo-user <sumo-user@xxxxxxxxxxx>:

Dear SUMO team,

 

I am working on a relatively large project (thus it is difficult to provide a minimal example) that involves numerous traci calls. To speedup the computation I switched from traci to libsumo. To do so, I simply use the command “libsumo as traci” as suggested on the SUMO website. After numerous tests, I noticed that the outputs using either traci or libsumo are different as I receive different collisions and teleportations warnings when using  either of the two packages. So, my question is: Are there some known functions that differ between traci and libsumo ? It seems especially that libsumo is not doing certain commands as I have more collisions using it compared to traci, but it runs without any error nevertheless... I suspect therefore that some silent errors are happening using libsumo. In particular libsumo.vehicle.changeLane seems to behave differently than it’s traci variant.

 

 

P.S.: I am using sumo version 1.26.0

 

Thanks in advance for your reply.

 

Thomas

 

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

Back to the top