I\'m trying to evaluate an application that runs on a vehicular network using OMNeT++, Veins and SUMO. Because the application relies on realistic traffic behavior, so I decided
There are two things you can do here for reducing the number of sent messages in Veins:
Use the OMNeT++ Warm-Up Period as described here in the manual. Basically it means to set warmup-period
in your .ini
file and make sure your code checks this with if (simTime() >= simulation.getWarmupPeriod())
. The OMNeT++ signals for result collection are aware of this.
The TraCIScenarioManager
offers a variable double firstStepAt @unit("s")
which you can use to delay the start of it. Again this can be set in the .ini
file.
As the VEINS FAQ states, the TraCIScenarioManagerLaunchd
offers two variables to configure the region of interest, based on rectangles or roads (string roiRoads
and string roiRects
). To reduce the simulated area, you can restrict simulation to a specific rectangle; for example, *.manager.rioRects="1000,1000-3000,3000"
simulates a 2x2km area between the two supplied coordinates.
With both solutions (best used in combination) you still have to run SUMO - but Veins barely consums any of the time.