-
Notifications
You must be signed in to change notification settings - Fork 41
Performance Analysis
The OMNeT++ provides basic tools for performance analysis. On this page, we will describe how to collect data from the simulation and analyze the results with OMNeT++ IDE and python.
What we can get in the performance analysis is some plots like these.

First, we need to add a parameter to the .ned file. You can decide the name of the parameter you take. To record a parameter you need to add the following:
@signal ["parameter name"](type="paramter type")
@statistic["paramter name"](title, record, interrpolationmode)
For details about these parameters, please refer to this section in the OMNeT++ documentation.
Next, we have to connect the .ned file to the actual source code. In the example below, we have a private variable called recog_resSignalwith type simsignal_t.

registerSignal function.
In the simulation, we have to update parameters with the emit function.
At the point where the parameter actually changes, we have to update the parameter by using the emit function.
Those are the requirements for measuring performance. Let's run the simulation. When you run the simulation, it's better to specify the name of the output files. In the .ini file, you can specify the name of the vector file as
output-vector-file = "filenane.vec"
When the simulation is completed, the .vec file should be inside the network folder.
Click the .vec file in the network.
Format of a vector file is,

- running date and time
- attributes of simulation
- parameters of the simulation
- information of vector
- actual values are included.
Let's try to run quisp/networks/vector_test.ini. Just run the simulation and show the vector file in the IDE.






