Classes of Simulation Output
Discrete event simulations can generate a variety of types of output which are applicable in different situations. Given that discrete event simulations can contain user-defined code, it is clearly also possible to define and compute new types of simulation output which can be reported during simulations or afterwards for post-processing. This section describes common forms of simulation output and indicates the type of support that Modeler provides for generating it. Automatic support means that Modeler computes and records the information with no programming required by the modeler. Programmatic support means that Modeler provides programmatic interfaces that allow the modeler to record customized output. Finally, unsupported means that the output the modeler can use the general mechanisms of the programming language and the Operating System to generate the output, but Modeler provides no specific implementation support.
Table 115: Forms of Simulation Output
| Form of Output | Details | Support |
|---|---|---|
| Output Vectors | The history of a system variable can be captured as it varies over time in the form of an output vector. (OV) OVs provide insight into the manner in which the system evolves and its response to particular incidents during a simulation. Each OV consists of a series of values and associated times. A simulation can be configured to simultaneously collect multiple independent OVs. | Automatic for built-in statistics included in standard models; programmatic for customized statistics computed by user-defined code. |
| Output Scalars | Certain metrics of interest do not vary with time. Instead, they are one value that is representative of the system’s performance over the course of the simulation (e.g., the throughput of the network). Each of these statistics is called an output scalar (OS). Each output scalar is typically recorded only once per simulation. Output scalars from multiple simulations are then combined to analyze their dependency on simulation inputs, also recorded as scalars. | Automatic for built-in statistics included in standard models; programmatic for customized statistics computed by user-defined code. |
| Animation | Visualization of system activity can be a valuable tool for gaining insight into behavior and interactions between components. Simulations can generate animations as they run or save them for playback after they complete. | Automatic for standard forms of animation included in standard models; programmatic for customized graphics computed by user-defined code. |
| Proprietary Reports and Files | Because Modeler allows inclusion of user-defined processes and link models, it is possible to generate customized reports or output files as the simulation runs, or when it completes. The general facilities of the C language and the operating system are used for this purpose. | Not supported by Riverbed; relies on C language and OS access. |
Output Files
As mentioned above, simulation results can take on several different forms including visual animations, time-dependent series of values, and parametric relationships. For those forms of output that are not interactively utilized (i.e., as the simulation continues to run), results are accumulated in files residing in the host computer’s filesystem, until a simulation completes. The contents of these files may be displayed at the user’s convenience using appropriate tools. There are three types of output files that may be directly generated by the Simulation Kernel.
Table 116: Simulation Output Files
| File Type | Details |
|---|---|
| Output Vector | Generated by simulations to store time-series data. Each simulation generates only one output vector (OV) file that contains all OVs that are selected for the run. OV files may have user-specified names, or default to the name of the network model. OV files can grow to be quite large depending upon the number and length of the vectors contained within them. A vector contains a series of time-value pairs; both are stored as C doubles (typically 16 bytes per pair). OV files are identified by the“.ov” file suffix. Simulations overwrite identically named OV files. |
| Animation History | Generated to support post-simulation visualization of a modeled system’s behavior. An animation history (AH) file contains a sequence of animation commands which can be interpreted by the animation viewer to display selected model activity during the simulation. Each simulation can generate at most one AH file. Identically named AH files are overwritten. AH files are identified by the “.ah” suffix. |
Riverbed Modeler also maintains a log of errors and significant events that occurred during a simulation. This log (a tab-delimited ASCII file) may be examined using the simulation log browser. For details, see Chapter 3 “Project Editor” on page 89.