Chapter 9. Sequence Charts

Table of Contents

Introduction
Creating an Eventlog File
Sequence Chart
Legend
Timeline
Zero Simulation Time Regions
Module Axes
Gutter
Events
Messages
Displaying Module State on Axes
Zooming
Navigation
Tooltips
Bookmarks
Associated Views
Filtering
Eventlog Table
Display Mode
Name Mode
Type Mode
Line Filter
Navigation
Selection
Searching
Bookmarks
Tooltips
Associated Views
Filtering
Filter Dialog
Range Filter
Module Filter
Message Filter
Tracing Causes/Consequences
Collection Limits
Long-Running Operations
Other Features
Settings
Large File Support
Viewing a Running Simulation's Results
Caveats
Examples
Tictoc
FIFO
Routing
Wireless

Introduction

This chapter describes the Sequence Chart and the Eventlog Table tools. Both of them display an eventlog file recorded by the OMNeT⁠+⁠+ simulation kernel.

An eventlog file contains a log of messages sent during the simulation and the details of events that prompted their sending or reception. This includes both messages sent between modules and self-messages (timers). The user can control the amount of data recorded from messages, start/stop time, which modules to include in the log, and so on. The file also contains the topology of the model (i.e. the modules and their interconnections).

Note

Please refer to the OMNeT⁠+⁠+ Manual for further details on eventlog files and their exact format.

The Sequence Chart displays eventlog files in a graphical form, focusing on the causes and consequences of events and message sends. They help the user understand complex simulation models and help with the correct implementation of the desired component behaviors. The Eventlog Table displays an eventlog file in a more detailed and direct way. It is in a tabular format, so that it can show the exact data. Both tools can display filtered eventlogs created via the Eventlog Tool filter command as described in the OMNeT⁠+⁠+ Manual, by a third party custom filter tool, or by the IDE's in-memory filtering.

Using these tools, you will be able to easily examine every detail of your simulation back and forth in terms of simulation time or events. You will be able to focus on the behavior instead of the statistical results of your model.