InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Distributed Integrated Simulation Environment

IP.com Disclosure Number: IPCOM000110774D
Original Publication Date: 1994-Jan-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 72K

Publishing Venue


Related People

Brown, L: AUTHOR [+6]


Figs. 1 and 2 show the process flow and the timing flow, respectively, for the simulation environment.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 69% of the total text.

Distributed Integrated Simulation Environment

      Figs. 1 and 2 show the process flow and the timing flow,
respectively, for the simulation environment.

      The process flow (Fig. 1) begins with the event simulator which
is the time keeper for the simulation environment (a).  It controls
all of the cycle simulators and provides one cycle's worth of input
stimulus to all simulators (b).  The cycle simulators run one cycle
in parallel to each other (c) while the event-driven simulator
prepares for the outputs from the cycle simulators.  The event
simulator receives these outputs in its queue (d).  The event
simulator also propagates the output values with timing delays and
distributes them to the appropriate cycle simulator for the next
cycle's inputs.  This method provides the ability to add timing to
the cycle simulation models at their inputs and outputs, giving the
appearance of cycle simulation with timing (a).  Once all cycle
values are propagated, the event-driven simulator advances the time
and repeats the process for the next cycle.

      The timing sequence (Fig. 2) begins when the event simulator
starts processing (a).  The event simulator writes data to each cycle
simulator (b) via a communications network.  Each cycle simulator
runs in parallel (c) as it reads the data, evaluates the model,
clocks the model if necessary, and then writes data back to the event
simulator.  During this time, the event simulator is idle.  The event