

Not to worry though, SUMO has this covered with a *.typ.xml file which we will take a look at in the next section.īefore we finish this section, let’s quickly summarise what we know about the definitions of nodes and edges so far of TraCI_tls with this illustration:įurther reading: On node types (extract from here:): But this file has lots of repetitive codes, and this is not ideal from a programming point of view. “*o” edges which have a lower priority of 46.Īpart from priority, we also have numLanes and speed as attributes for edges. “*i” edges, have a higher priority of 78 than those exiting the junction, i.e. In this model, edges going into the juction (node 0), i.e. To answer our earlier question regarding the priority typed nodes, we see that each edge has a priority attribute which has numerical values meaning that edges can be compared according to their prioritys.

But what does priority mean for all the other nodes? After consulting this documentation on SUMO’s XML schema, it appeared that this is related to the priority attribute of edges, so let’s take a look at our next file :įrom this file we have definition of a bunch of edges, each again has a unique id such as “1i” for the edge going from node “1” to node “0”. It must be a junction controlled by traffic lights. Without consulting more documentation, it is easy to understand what “traffic_light” means being node 0’s type. The x and y locations of each node are also given in the definition of each node. Edges are the paths connecting these reference points. Nodes are the reference points on a map, i.e. Nodes and edges are the most basic elements of a SUMO model. Let’s take a look at what’s in this folder. For TraCI, it is good practice to separate these definitions from the Python scripts in a data folder. Compared to the vehicles and their movements, these are the static elements of the model. Building the Road NetworkĮach SUMO model is built on a network of roads, junctions, traffic lights, and other infrastructure items such as induction loop detectors.

We will begin by going through the files contained in the data folder. Source codes of this model is hosted here.įirst let’s take a look at the file structure of TraCI_tls: Therefore, we provide this study note to supplement the TraCI_tls tutorial. The official tutorial also does not provide a complete list of wiki pages that are essential to help the user to understand the model. After going through the tutorial material given here, we find that the tutorial may be improved in terms of helping the user to understand the model from a software’s point of view. It is a perfect starting point for anyone who is interested in using SUMO and the TraCI tool. TraCI_tls is a simple SUMO model developed as part of SUMO’s tutorial on TraCI. We give introduction to the TraCI tool by studying the TraCI_tls model.
