vem and pigiRpc, that communicate via Remote Procedure Calls (RPC). Vem is the first process that starts up, and it produces a vem console window in the upper left corner of the screen and a green demo window just below it. When pigiRpc starts up, you should see a window in the middle of your screen that has the Mr. Ptolemy bitmap and a brief description of the binary you are running.If the
pigiRpc process fails to connect to the vem process, you won't see the Mr. Ptolemy bitmap, and the shift-middle-button menus will not be active. This problem seems to be most common on Linux machines, in part because they are often not on a network. If you are running under Linux and your installation is configured to use the network, then you may need to rebuild Ptolemy from source.If you are running on a machine that is not connected to a network, you will need to provide some network support for
pigi to start up. vem and pigiRpc communicate with each other via RPCs, which require some intra-machine network support. One quick test is that you should be able to ping yourself:
/usr/etc/ping `hostname`There are several workarounds to this. One is to add the name of your host to the loop back line in
/etc/hosts (here we add the name myhostname):
route to route packets to your host through the loopback interface. As root, type:
ping, netstat and route commands for more information.
pigi is started in the background and the user has the line
.login or .cshrc file. This command configures the terminal to halt any process that is running in the background when it tries to write to the terminal. One fix is to run pigi in the foreground. Another fix is to eliminate this command from your login files.
At run time, if shared libraries cannot be found, you may see a message under HPUX-10.01 like:
/users/ptolemy, then this may be the problem./users/ptolemy, then you may need to set an environment variable to indicate what path should be searched for shared libraries. Under HPUX, the environment variable is SHLIB_PATH; under Solaris, the environment variable is LD_LIBRARY_PATH. The file $PTOLEMY/.cshrc should contain the proper commands to set the appropriate environment variable, though you may need to uncomment some lines. For HPUX, you could type the following command. (Do not type a space after the \ at the end of the first line, just press Return):
~/.cshrc file. It is possible that you might have to add other directories to the shared library path. For example, the Ptolemy binaries are compiled with /usr/openwin/lib as the location of the X windows libraries. If your X windows libraries are in another directory, then you will need to add that directory to the shared library path. See
"Window system problems" on page 7-182.
tycho, the Ptolemy syntax manager. $PTOLEMY/bin/tycho is a link to a script that processes command line arguments and starts up the appropriate binary. If you type tycho -pigi, tycho starts up with a binary that includes the Ptolemy system. If you type just tycho, then tycho starts up with the generic itkwish binary that is built from the itcl sources, which does not include any of the Ptolemy system.If your Ptolemy distribution is not at
/users/ptolemy, and you are running from prebuilt binaries, then if you run tycho with the prebuilt generic itkwish binary, you may see messages about:
itkwish binary we ship has the /users/ptolemy path hard coded into it and the binary is not finding the libraries it needs. The reason this happens is that we want tycho to be able to run outside of Ptolemy on machines that have only generic itkwish installed from the itcl distribution. There are a few workarounds:
/users/ptolemy to the Ptolemy distribution.
tycho -ptiny instead. The tycho script assumes that the Tcl installation is located in $PTOLEMY/tcltk if it is called with the -ptiny, -ptrim or -pigi arguments, so the script will do the right thing.
itkwish: