Peter Alexander wrote: > Using veins to implement VANET dissemination protocols, but I find that > the > configuration options of .numVehicles and .accidentCount is not being > adhered to.
Documentation of these parameters is indeed lacking. You will get much better insights by looking at the code. Let me briefly summarize how these parameters work: "accidentCount" is specific to a single vehicle. Together with "accidentStart", "accidentInterval", and "accidentDuration" it enables you to stop vehicles at arbitrary times in your simulation (which can trigger a breakdown/crash/etc notifaction). The relevant source code is in [1]. "numVehicles" is used by Veins to determine, at each time step, if it needs to insert additional vehicles to reach the configured number. The relevant source code is in [2]. If SUMO is also inserting vehicles (i.e., if you have any vehicle flows or vehicle departures configured in your .rou.xml file) Veins will stop inserting vehicles, but it will never destroy vehicles that are already driving. This parameter is thus best used by only configuring routes in SUMO and managing the insertion of vehicles in Veins only. Best, Christoph [1] https://github.com/sommer/veins/blob/veins-3a3/src/modules/mobility/traci/TraCIMobility.cc#L148 [2] https://github.com/sommer/veins/blob/veins-3a3/src/modules/mobility/traci/TraCIScenarioManager.cc#L288 ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
