Introduction to TraCI#
TraCI is the short term for "Traffic Control Interface". Giving access to a running road traffic simulation, it allows to retrieve values of simulated objects and to manipulate their behavior "on-line".
TraCI uses a TCP based client/server architecture to provide access to sumo. Thereby, sumo acts as server that is started with additional command-line options: --remote-port <INT> where <INT> is the port sumo will listen on for incoming connections.
When started with the --remote-port <INT> option, sumo only prepares the simulation and waits for all external applications to connect and take over the control. Please note, that the --end <TIME> option is ignored when sumo runs as a TraCI server, sumo runs until the client demands a simulation end.
The number of clients which can connect can be given as an additional option --num-clients <INT>, where 1 is the default. Please note that in multi client scenarios you must explicitly specify the execution order of the clients using the SetOrder-command.
Each client must specify a unique (but otherwise arbitrary) integer value and the client commands will be handled in the order from the lowest to the highest value within each simulation step.
The clients are automatically synchronized after every simulation step. This means, the simulation does not advance to the next step until all clients have called the 'simulationStep'' command. Also, the simulationStep command only returns control to the client after the simulation has advanced.
The simulation will only start once all clients have connected.
- Control-related commands: perform a simulation step, close the connection, reload the simulation.
- Value Retrieval
- Induction Loop Value Retrieval retrieve information about induction loops
- Lane Area Detector Value Retrieval retrieve information about lane area detectors
- Multi-Entry-Exit Detectors Value Retrieval retrieve information about multi-entry/multi-exit detectors
- Calibrator Value Retrieval retrieve information about calibrators
- Traffic Lights Value Retrieval retrieve information about traffic lights
- Lane Value Retrieval retrieve information about lanes
- Vehicle Value Retrieval retrieve information about vehicles
- Person Value Retrieval retrieve information about persons
- Vehicle Type Value Retrieval retrieve information about vehicle types
- Route Value Retrieval retrieve information about routes
- PoI Value Retrieval retrieve information about points-of-interest
- Polygon Value Retrieval retrieve information about polygons
- BusStop Value Retrieval retrieve information about BusStops
- Charging Station Value Retrieval retrieve information about charging stations
- Parking Area Value Retrieval retrieve information about parking areas
- Overhead Wire Value Retrieval retrieve information about overhead wires
- Junction Value Retrieval retrieve information about junctions
- Edge Value Retrieval retrieve information about edges
- Simulation Value Retrieval retrieve information about the simulation
- GUI Value Retrieval retrieve information about the simulation visualization
- Rerouter retrieve information about the rerouter
- RouteProbe retrieve information about the RouteProbe
- State Changing
- Change Lane State change a lane's state
- Change Traffic Lights State change a traffic lights' state
- Change Vehicle State change a vehicle's state
- Change Person State change a persons's state
- Change Vehicle Type State change a vehicle type's state
- Change Route State change a route's state
- Change PoI State change a point-of-interest's state (or add/remove one)
- Change Polygon State change a polygon's state (or add/remove one)
- Change Edge State change an edge's state
- Change Simulation State change the simulation
- Change GUI State change the simulation visualization
- Accessing Generic Parameters
When using TraCI, the --end option of sumo is ignored. Instead the simulation is closed by issuing the close command. To detect whether all route files have been exhausted and all vehicles have left the simulation, one can check whether the command getMinExpectedNumber returns 0. The simulation will end as soon as all clients have sent the close command.
It is also possible to reload the simulation with a new list of arguments by using the load-command.
Using SUMO as a library#
Normally, TraCI is used to couple multiple processes: A SUMO server process and one or more TraCI client processes. Alternatively, Libsumo can be used to embed SUMO as a library into the client process. This allows using the same method signatures as in the client libraries but avoids the overhead of socket communication. Libsumo supports generating client libraries using SWIG and can therefore be used with a large number of programming languages. C++, Java and Python bindings are included when downloading a sumo-build.
- There is a tutorial on using TraCI for adaptive traffic lights (using Python).
- The Tutorials/CityMobil tutorial uses TraCI for assigning new routes to vehicles (using Python).
- The Tutorials/TraCIPedCrossing tutorial uses TraCI for building a crossing with a pedestrian triggered traffic light.
Interfaces by Programming Language#
- Python: the package tools/traci allows to interact with sumo using Python (This library is tested daily and supports all TraCI commands).
- C++: The C++ TraCIAPI is client library that is part of the sumo-source tree (API coverage is almost complete).
- C++: The Veins project provides a middle-ware for coupling sumo with OMNET++. As part of the infrastructure it provides a C++ client library for the TraCI API (API completeness is a bit behind the python client).
- .NET: TraCI.NET is a client library with almost complete API coverage.
- Matlab TraCI4Matlab. The client is included as part of each SUMO release in <SUMO_HOME>/tools/contributed/traci4matlab Not all TraCI commands have been implemented.
- Java: TraaS provides a client library that is part of the sumo-source tree (API coverage is almost complete).
- Others: Any language that can access webservices using SOAP can access SUMO using the TraaS Webservice. A Java webservice client is also included with TraaS. API lags behind the python client.
- sumo's TraCI Server is a part of the plain
distribution. The source code is located in the folder
- Axel Wegener, Michal Piorkowski, Maxim Raya, Horst Hellbrück, Stefan Fischer and Jean-Pierre Hubaux. TraCI: An Interface for Coupling Road Traffic and Network Simulators. Proceedings of the 11th Communications and Networking Simulation Symposium, April 2008. Available at ACM Digital Library
- Axel Wegener, Horst Hellbrück, Christian Wewetzer and Andreas Lübke: VANET Simulation Environment with Feedback Loop and its Application to Traffic Light Assistance. Proceedings of the 3rd IEEE Workshop on Automotive Networking and Applications, New Orleans, LA, USA, 2008. Available at IEEEXplore
Using TraCI slows down the simulation speed. The amount of slow-down depends on many factors:
- number of TraCI function calls per simulation step
- types of TraCI functions being called (some being more expensive than others)
- computation within the TraCI script
- client language
As an example use-case consider retrieving the x,y position of each vehicle during every simulation step (using the python client):
while traci.simulation.getMinExpectedNumber() > 0: for veh_id in traci.vehicle.getIDList(): position = traci.vehicle.getPosition(veh_id) traci.simulationStep()
- This script is able to process about 25000 vehicles per second.
- Using embedded python increases this to about 50000 vehicles per second
- The same value retrieval can also be sped up to 50000 vehicles per second by using subscriptions:
while traci.simulation.getMinExpectedNumber() > 0: for veh_id in traci.simulation.getDepartedIDList(): traci.vehicle.subscribe(veh_id, [traci.constants.VAR_POSITION]) positions = traci.vehicle.getAllSubscriptionResults() traci.simulationStep()
When using this script on the Bologna scenario (9000 vehicles, 5000 simulation steps) the following running times were recorded:
- without TraCI 8s
- plain position retrieval 90s
- retrieval using subscriptions 42s
- retrieval using embedded python 46s
- retrieval using subscriptions and embedded python 34s
The C++ client performance is higher:
- plain position retrieval 80s
- retrieval using subscriptions 28s
Current and Future Development#
Historically TraCI used a different (single byte) command ID for every domain (induction loops, vehicle etc.) where the more significant half of the byte denotes the command (get, set, subscribe, ...) and the lesser significant the domain itself. To allow more than the 16 domains resulting from this split, the most significant bit (which was unused until now because there were only 7 commands) is now used for the domain as well (and only three for the command). This allows for 28 domains because four general commands (like SIMSTEP) block some available combinations. Currently there are only four possible domains left.
Furthermore after the invention of libsumo some parts of the TraCI interface are so generic that it may be not so hard to invent a wrapper with Apache Kafka or Google protocol buffers which could in the long run replace the need for all the byte fiddling and the different hand crafted clients.
Output files are not closed.#
This problem occurs if the client tries to access the output while the simulation is still closing down. This can be solved by letting the client wait for the simulation to shut down. The bug report was #524
There used to be two "generations" of TraCI commands. The first one mainly uses an internal mapping between the string-typed IDs used in sumo and an external representation of these which is int-based. The mapping was done internally (within TraCI). The second "generation", the current one uses string-IDs equal to those sumo reads. If you are bound to the first generation API (for instance if you want to use TraNS) you can only use sumo up to version 0.12.3. See FAQ about obtaining an old version.