1. option --yfactor 60 causes all y values to be scaled by 60 2. The latest development version supports filtering of edges as well as aggregation. See attributes 'edges', 'edgesFile' and 'aggregate' at https://sumo.dlr.de/docs/Simulation/Output/Lane-_or_Edge-based_Traffic_Measures.html. You can obtain that version at https://sumo.dlr.de/docs/Downloads.php#sumo_-_latest_development_version 3. leave out option --scatterplot 4. -i selects the attribute that controls grouping of points (same color, line graph lines). In this case grouping is by edge attribute 'id'. -s is short for --show which shows the plot intead of only writing it to a file 5. yes. I'd expect a positive correlation.
regards, Jakob Am Di., 15. Feb. 2022 um 16:56 Uhr schrieb Sumbal Malik < [email protected]>: > Jakob, many thanks for your prompt response. > > I calculated the aggregated edge data using <edgeData id="dump_15" > freq="30" file="edge_data.xml" excludeEmpty="true"/> and then used this > command to "\visualization>plotXMLAttributes.py edge_data.xml -i id -x > density -y timeLoss -s --scatterplot --legend --yfactor 60 --ylabel > TimeLoss" to plot the attached graph of density versus time loss. > > I would be thankful if you could answer the following queries: > > 1. Why the value of time loss is too large (1000) on the graph when the > maximum value of time loss is 15 in the attached edgedata output file. > 2. Can we aggregate the values of all the edges and plot them or how can > we get the output of selective edges? > 3. How can we draw a line graph using plotXMLAttributes.py > 4. What do "-i id" and "-s" represent in the above command. > 5. Does it make sense if we draw a relation between the density and the > time loss. > > Thank you > > On Tue, 15 Feb 2022 at 10:41, Jakob Erdmann <[email protected]> wrote: > >> 1. TraCI is not tailored for measuring aggregated data. I recommend doing >> this with XML outputs (i.e >> https://sumo.dlr.de/docs/Simulation/Output/Lane-_or_Edge-based_Traffic_Measures.html). >> However, you can compute traffic statistics "manually": >> - retrieve the speed or timeLoss of all vehicles in every step >> - compute vehicle density (lane.getLastStepVehicleNumber / lane.getLength) >> 2. you could run simulations with and without your special delay-causing >> vehicle and observe the difference >> >> >> Am Mo., 14. Feb. 2022 um 14:24 Uhr schrieb Sumbal Malik < >> [email protected]>: >> >>> Dear SUMO Team >>> >>> 1. How can we calculate/measure the traffic/road efficiency using traci >>> SUMO >>> 2. Can we draw a relationship between the delay caused by an individual >>> vehicle and traffic efficiency of the road segment. >>> >>> Thank you >>> >>> _______________________________________________ >>> sumo-user mailing list >>> [email protected] >>> To unsubscribe from this list, visit >>> https://www.eclipse.org/mailman/listinfo/sumo-user >>> >> _______________________________________________ >> sumo-user mailing list >> [email protected] >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/sumo-user >> > _______________________________________________ > sumo-user mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user >
_______________________________________________ sumo-user mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
