Raphael Riebl

Would you please familiarise yourself with the excellent OMNeT++ documentation at https://omnetpp.org/documentation/ The documentation covers all you need to know on how to record and process result files.

Sorry, I don't even understand your question.

Not all data occurring during simulation is actually recorded because the result files would be huge. For example, you need to explicitly enable the recording of `CaService`'s *reception* and *transmission*...

1. The MT-ITS 2017 scenario to which this issue ticket refers includes the IRC use case already, see *scenarios/mt-its2017/usecases.xml*. 2. Almost, it is lowercase *middleware*. 3. As I have written...

Add to *omnetpp.ini*: ``` *.node[*].middleware.DEN.transmission.result-recording-modes = all *.node[*].middleware.DEN.reception.result-recording-modes = all ``` There is no dedicated setting for IRC because it is simply a DEN use case.

With the described result recording settings, I have a vector named "World.node[2].middleware.DEN transmission:vector(denmCauseCode)" for which several entries with value "97" exist. Hence, the vehicle "node[2]" is known to transmit IRCs....

Yes, you can match the *denmActionId* found in the transmission vectors with those found in the reception vectors.

Every transmitted DENM has a unique *denmActionId*: For each received *denmActionId* you can scan all DEN transmission vectors for the equal *denmActionId*. Thereby you can look up the transmitting node...

I recommend using your preferred scripting language to process the result files. For example, you can convert the result files into CSV files with OMNeT++'s *scavetool* and create more advanced...

Are you looking for this code segment: https://github.com/riebl/vanetza/blob/460f76f8863ff69a8d45a5b63dd724f831f622ed/vanetza/geonet/router.cpp#L694?