$PTOLEMY/mk/config-$PTARCH.mkfor the particular architecture you are running under.
vemthat can make the process grow quite big. After editing a few dozen icons, you may wish to exit
pigiRpcmay fail to start up on 4 bit (16 color) screens. At UC Berkeley, we use 8 bit and 24 bit screens. Black and white (1 bit) support in vem is a little weak. If you are on a black and white screen, you may need to modify
$PTOLEMY/lib/pigiXRes9. (Note that
$PTOLEMY/lib/pigiXRes9.bwis read when the
pigioptions is used to create black and white screen dumps from a color monitor.
pigiXRes9.bwhas very little to do with running on a black and white screen).
VEMBINARYenvironment variable is set, then
bin/pigiEnv.cshwill use the contents of that variable as the
vembinary. However, the binary must be named
vem, or there will be minor problems with X resources, such is small fonts and incorrect snap. Most users will never use the
VEMBINARYenvironment variable, it is primarily used to debug
vemmay crash. One workaround is to not run color
vemnow mean that
vemis more picky about text label heights. Currently, the range for text label heights is 0 to 80. If you select text and then use E, to edit the label, you may see an error if your text height is greater than 80. One workaround is to delete the text and reenter it with a height that is within the proper range. Another workaround is to use an old
vembinary to edit the height and set it to within the range.
And.input=2refer to the same star, but the former can have any number of inputs, while the latter has exactly two inputs. As of this writing, this facility does not work for galaxies. You should create only one icon for each galaxy.
$PTOLEMY/bin/pigiis a link to
$PTOLEMY/bin/pigiEnv.cshwhich may add to your path. Under certain circumstances, you may get the message `Warning: ridiculously long PATH truncated'. To work around this problem, try shortening your path. One trick is to use shorter pathnames in your path, perhaps using symbolic links.
pigimay crash. One workaround is to not run color hogs like
netscape, or to limit the number of colors
.hfile for the incrementally linked in star cannot be found by compile-SDF. As a workaround try editing the makefile in
~/PTOLEMY_SYSTEMSand adding the directory where the incrementally linked stars is. Then build the binary by hand.
File. These two new data types should be useful in creating Design Flow Management (DFM) universes. However, there are only a few DFM demos.
NOWam) CGC target is slow, but it does run under Solaris.
cgddf) CGC target, two files must be recompiled. The
PortHole.ccand Higher Order Functions (
HOF) are incompatible, the
HOFMapGrstar breaks. The changes to
parScheduler.ccare a fairly radical shift in how Ptolemy handles disconnected graphs. These changes could break other parallel schedulers. The script
$PTOLEMY/bin/mkcgddfwill build a
pigiRpc.ptrim.debugbinary that contains the
cgddftarget. This script is basically untested, but should work.
tycho, the Ptolemy syntax manager. Development of
tychois ongoing, so the version included in Ptolemy 0.6 is by no means the final version. In particular, there are many more features to be implemented.
tycho -ptrim &), then exiting from the MATLAB console may hang. The workaround is to place your
tychoprocess into the foreground. This is a known bug with MATLAB.
pxgraphis given only one point to plot, nothing appears in the plot window.
pxgraphis given exceptional numeric input, such as the IEEE floating point
NaN, then it displays a blank window only.
pxgraphis given an empty file to plot, all it does is send a message "problems with input data" to the standard output.