Very long delays on first startup of new install
There is a very long delay when a new version of Kepler is first executed. This
is particularly noticable on the Mac. This delay is due to the Python actor
going through all jars on the the classpath to build a bunch of stuff in the
PTII/lib/cachedir directory! It is only done the first time a new version is
run, but it seems to go through every class in Java. The delay is so long that
many users will think that kepler is not working.
#1 Updated by Christopher Brooks almost 15 years ago
In Ptolemy II, the Jython actor only expands the jar files when
Actors -> More Libraries -> Python is opened in the actor tree widget.
This suggests that Kepler is instantiating all the actors at start up
instead of delaying this until the actors are needed.
In the short term, perhaps you could remove the Jython actor?
Is anyone in the Kepler group using it?