Understanding the Invocation Script

The primary reason of using an invocation script to execute an external process simulator is that the script can be easily customized by the developers and the users. Some of the possible uses of custom invocation scripts are:

In this section, we discuss the primary elements in the invocation script. It contains two interfaces: one between SansGUI and the invocation script and the other between the invocation script and the simulator. Understanding the two interfaces, you will be able to customize the invocation script and the simulator so that special features can be introduced. For detail specifications of the standard invocation script, consult the External Process Simulation Control section of the SansGUI Reference Manual.

Interfacing SansGUI and Invocation Script

SansGUI calls the invocation script and passes certain parameters to the script for further processing. The parameters include:

The sequence of the parameters that SansGUI created cannot be modified, i.e., the command line arguments to the invocation script shall not be changed.

Interfacing Invocation Script and Simulator

The standard, out of the box, interface for the invocation script to call a simulator consists of the following parameters:

To accomplish the custom features described in the beginning of this section, you may need to modify this interface so that the invocation script and the simulator can work in a harmony. You should not, however, alter the invocation script in the bin directory. Instead, store a copy of your custom invocation script file with a name specific to your simulator in the sim subdirectory and ask your simulation users to specify that invocation script in the Default external process simulation control object.


C:\FH_Suite\htmlgifs\home.gif Understanding the Process Processing Model Files

SansGUI Modeling and Simulation Environment Version 1.2

Copyright 2000-2003 ProtoDesign, Inc. All rights reserved.