You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As stated in the title, defining traffic light logic with TrafficLightParams from flow.core.params does not create the appropriate output in the .net.xml file for SUMO to read.
After defining phases and using the TrafficLightParams.add(node_id, programID = , phases=), I can see that they are correctly accepted when checking TrafficLightParams.get_properties().
However, I noticed that in the SUMO GUI, the traffic lights were exhibiting default behavior (with parameter value for "programID" as "0"). Upon checking the .net.xml file lines associated with the traffic lights, the tlLogic program id is indeed 0, and the phases are all default values.
The text was updated successfully, but these errors were encountered:
Bug Description:
As stated in the title, defining traffic light logic with TrafficLightParams from flow.core.params does not create the appropriate output in the .net.xml file for SUMO to read.
After defining phases and using the TrafficLightParams.add(node_id, programID = , phases=), I can see that they are correctly accepted when checking TrafficLightParams.get_properties().
However, I noticed that in the SUMO GUI, the traffic lights were exhibiting default behavior (with parameter value for "programID" as "0"). Upon checking the .net.xml file lines associated with the traffic lights, the tlLogic program id is indeed 0, and the phases are all default values.
The text was updated successfully, but these errors were encountered: