There are a number of known bugs that we have not had a chance to fix. You may find useful information about architecture dependencies in $PTOLEMY/mk/config-$PTARCH.mk for the particular architecture you are running under.
- When graphical animation is turned on and a simulation is running, if you execute the "look-inside" command,
vem terminates the pigiRpc application.
- Deleting wires that are too long (i.e., end of wire is past the terminal, but near it) can result in
vem dumping core.
- Labels that end with a carriage return are neither displayed nor printed correctly.
- Editing icons stimulates a memory leak in
vem that can make the process grow quite big. After editing a few dozen icons, you may wish to exit vem and restart.
- The "layer" command only works when editing icons, not when editing schematics.
- The "copy-objects" command will copy from one window to another only when editing icons, not when editing schematics.
vem or pigiRpc may 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.bw is read when the -bw pigi options is used to create black and white screen dumps from a color monitor. pigiXRes9.bw has very little to do with running on a black and white screen).
- If the
VEMBINARY environment variable is set, then bin/pigiEnv.csh will use the contents of that variable as the vem binary. 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 VEMBINARY environment variable, it is primarily used to debug vem.
- If your X server runs out of colors,
vem may crash. One workaround is to not run color
hogs like netscape, or to limit the number of colors netscape can use.
- Bug fixes to
vem now mean that vem is 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 vem binary to edit the height and set it to within the range.
- If you re-read a facet that has an open run window, you won't be able to dismiss the run window. The workaround is to open a new run window.
- It is possible to make more than one icon to represent a given star. For instance, the icon
And and And.input=2 refer 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/pigi is a link to $PTOLEMY/bin/pigiEnv.csh which 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.
- If your X server runs out of colors,
pigi may crash. One workaround is to not run color hogs like netscape, or to limit the number of colors netscape can use.
- The compile-SDF target fails if a galaxy has incrementally linked in stars. The problem is that the
.h file for the incrementally linked in star cannot be found by compile-SDF. As a workaround try editing the makefile in ~/PTOLEMY_SYSTEMS and adding the directory where the incrementally linked stars is. Then build the binary by hand.
- Ptolemy 0.6 contains two new data types in the kernel:
String and File. These two new data types should be useful in creating Design Flow Management (DFM) universes. However, there are only a few DFM demos.
- The Networks Of Workstations active messages (
NOWam) CGC target is slow, but it does run under Solaris.
- To use the Dynamic Dataflow Code Generation (
cgddf) CGC target, two files must be recompiled. The cgddf changes in PortHole.cc and Higher Order Functions (HOF) are incompatible, the HOFMapGr star breaks. The changes to parScheduler.cc are a fairly radical shift in how Ptolemy handles disconnected graphs. These changes could break other parallel schedulers. The script $PTOLEMY/bin/mkcgddf will build a pigiRpc.ptrim.debug binary that contains the cgddf target. This script is basically untested, but should work.
- The compile-SDF target cannot handle star parameters that use the Tcl Interpreter to evaluate Tcl commands.
Ptolemy 0.6 contains the first release of tycho, the Ptolemy syntax manager. Development of tycho is 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.
Copyright © 1990-1997, University of California. All rights
reserved.