|Re: [sumo-user] Traffic lights consideations: static/actuated related to OSM-based net|
I'm coping with a city ring around the city center where all TLS have a fixed cycle time, as investigation (on location) showed me. As a first step, I changed the default status of all OSM-import related traffic lights to static (using a text editor, applied to osm.net.xml). At least that makes things simpler, and as such I also increased the phase times such, that the total cycle time does add to 120 instead of 90 seconds.
Yesterday - upon the investigation - I found that there is some variety in phase times. As such, actuated must be reactivated. However, cycle time remains constant at 120 ms. And the actuation should conform to that, e.g. using a fixed parameter setting.
The documentation (.../Simulation/Traffic_Lights.html#coordination) hints upon this as follows:
<tlLogic id="0" programID="my_program" offset="10" type="actuated">
<param key="coordinated" value="true"/> # should be important!
<param key="cycleTime" value="60"/> # here to insert: 120
My specific questions:
lLogic id="0" while my net file shows up unique id's for every traffic light controlled junction. And programID="0" for all TLS'es. I'm quite a bit confused what these parameters exaclty mean, in the sense of e.g. using a certain program flow that is defined once and used in several traffic light locations.
Is it true that using coordination and cycleTime specification - any green prolonging from any edge would automatically result in a shorting of a perpendicular edge? In the real world case I see inductive loops only in the streets coming from outside the city ring, not on the ring itself. This would quite simply allow exactly that what I ask in this text paragraph.
Any suggestions highly appreciated.
sumo-user mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
Back to the top