
RODEO
Getting Started
To start Rodeo, you need to do the following things:
- setup an environment variable PSCAN_TCL_LIB that would
point to the Rodeo installation directory, e.g., in a C
shell:
> setenv PSCAN_TCL_LIB /foo/bar/pscan/lib/tcl/
or in a Bourne shell:
% set PSCAN_TCL_LIB=/foo/bar/pscan/lib/tcl/
% export PSCAN_TCL_LIB
- copy file .pscanrc.tcl from the Rodeo
installation directory to your current working directory or create
this file using any text editor. Initially, the file should contain
only one line:
source $PSCAN_TCL_LIB/rodeo.tcl
The following should work fine at any UNIX box:
% cat > .pscanrc.tcl
source $PSCAN_TCL_LIB/rodeo.tcl
^D
%
Do not include anything else in this file, since it may be overwritten
by Rodeo! Also, be sure that this file is at least
owner-readable. All customizations must reside in the
files .pscanrc or ~/.pscanrc.
- If you are planning to run Rodeo in a hierarchical
model, you probably want to check if the files
extern.map, xextern.map, script.map, and
netlist.map reside in your current working directory and are
at least owner-readable. You may also want to have
customized mapping files.
- Note that Rodeo will try to write to your current working
directory, so make sure it is at least owner-writable.
- And, last but not least: you must have a PSCAN executable file
(e.g., dzSampl) and PSCAN data file that has the same name as
the executable file with the .dat extension (e.g.,
dzSampl.dat).
Now, you can start your PSCAN analysis program from the command line
prompt of your terminal. If the process of loading is going fine,
Rodeo will print its version information and a list of
customization and mapping files it is going to use. Be sure to check
that this list is what you want!
Finally, Rodeo Tcl interpreter prompts you for the
interaction. The prompt name as it appears in the command line is
exactly the same as the name of your executable file. The command
line has a built-in editor and a history buffer.
The interpreter recognizes any valid Tcl expression. An expression
can spread over several input lines. Multiple expressions (e.g., in
the body of a loop or of a procedure) be better separated with a
semicolon:
dzSampl> proc dummy {foo} {
dzSampl> set bar $foo;
dzSampl> return $bar
dzSampl> }
Customization Files