PDP++ interprets a large number of startup arguments. It looks for any of the arguments that can be passed to CSS (see section 7.4.3 CSS Startup options), which includes a script file that can be used to automate a set of actions to be taken in the simulator. This is particularly useful for running simulations in the background. The file `css/include/startup.css' provides an example of a startup file that loads in a saved project, sets some log files to record, and then runs the training or batch process. After the process is completed, the program will quit (unless the CSS argument -i was given).
The following arguments are PDP++ specific:
-nogui
-p <project_file>
bp++
xor.proj.gz
, and it will automatically load the project.
-d <default_file>
root->default_file =
"default_file"
. This can be based on the executable name by examining
argv[0]
, which contains the name of the executable being run.
In addition to the CSS arguments, PDP++ interprets all of the arguments for controlling the InterViews graphical user interface. These arguments allow one to select a different "look and feel" from the default one, which is an enhanced version of the Motif style:
-openlook
-motif
-monochrome
If you are logging in remotely or are somehow restricted to a non
XWindows environment, you have to use the -nogui
argument. This
turns off the graphical user interface completely, and leaves you with
the CSS interface.
Note that when you run simulations in the background, you will want to
use -nogui
.
Finally, there are some other InterViews arguments that might be useful:
-nodbuf
-visual <dpy type>
xdpyinfo
to obtain the visual class(es) supported by your x
display) (e.g., PseudoColor for standard 8 bit (256 color) X displays),
you can obtain a private color map for the PDP++ session. This can be
useful if you are running out of colors in your shared colormap (e.g.,
because Netscape is such a color hog!).