Simulation Components
A simulation program is a compiled program and takes the form of “object code”. Object code consists of machine instructions that the host computer is capable of executing directly, without any further translation. Each discrete event simulation consists of many separate pieces of object code that are packaged together to form a complete program. The different pieces of object code play a variety of different roles in the simulation, as listed in the following table. Some of the object files are Riverbed-provided, whereas others result from user specifications.
Table 124: Types of Object Files Included in a Simulation Program
| Object File Type | Simulation Program |
|---|---|
| Simulation Kernel | Provides the framework for all simulations including basic services such as model loading, event scheduling and delivery, statistic collection, memory allocations, etc. The Simulation Kernel contains all Kernel Procedures (KPs) that are called by user-developed models. |
| Process Models | Each process model that is included in a simulation is compiled into a C language file with suffix “.pr.c”; this file is then compiled with the host computer’s C compiler to generate an object file with suffix “.pr.o”. |
| Pipeline Stages | Relied on by link models to implement modular computations and make decisions relating to the transfer of packets between transmitters and receivers. Each pipeline stage is a C language procedure within one C file with suffix “.ps.c”. It is compiled using the host computer’s C compiler into an object file with suffix “.ps.o”. |
| External Object Files | Contain functions that play a supporting role for the process models and pipeline stages in a simulation. This software may be developed in C or in other languages that are callable from C. They can be compiled independently of Modeler and must have the suffix “.ex.o”. External files can be made known to Modeler in two ways: 1) a process model’s dependency on an external file can be expressed by declaring the external file in that model’s specification; 2) a network model can express the dependency of any of its included models on an external file, via a similar declaration. |
| External Archives | Similar to external object files, but are packaged in the form of an archive containing multiple object files. This is sometimes a more convenient way of managing groups of object files that belong together as part of a “package”. |
Modeler can generate a package (called a component file archive) containing the components used by a simulation. See “Component File Archive” on page 426 for details.