Next: The Script Reader
Up: The Neosim interface [
Previous: Why discrete event simulation?
The neosim interface is a collection of classes specified
in Java (but with a C++ binding). The basic classes do
very little in themselves, they must be extended
in order to provide the interesting behaviours. Only
experienced developers are expected to deal directly with
the low level neosim classes; modellers will be provided
with extended versions of these classes which provide
a script language interface.
The most important classes of the interface are:
- ScriptReader. The main() for the simulation, a hook
for the user to provide a sequential control program.
- Entity. This is the superclass for all simulation
objects which change with time. An entity can send and receive
events via ports to other entities.
- Event. The superclass for all timestamped objects
which get sent between entities. An event can be something
simple like a single spike, or a more complex object including
a large data structure and methods.
- Population. A class for referring to an entire
set of entities at once, and for providing rapid lookup
of member entities.
- Projection. A class for specifying a set of connections
between two populations of entities.
They are described in detail below.
Next: The Script Reader
Up: The Neosim interface [
Previous: Why discrete event simulation?
Fred Howell
8/15/1999