Usually, ArtiSynth applications involve the use of models or packages defined outside of the ArtiSynth core. In order for these to be visible to Java from inside MATLAB, it is necessary to add their classpaths to MATLAB’s Java classpath. There are three ways to do this:
Add the classpaths to the ArtiSynth’s external class path. Instructions for doing this are given the section “Setting the external classpath” of the User Interface Guide.
Add the classpaths within the MATLAB session using the javaaddpath() command. This should be done before the first call to artisynth(), perhaps within a startup script.
Add the classpaths to an ASCII text file called javaclasspath.txt located in one of the directories in the MATLAB search path, as described in Section 7.
When adding classpaths for external ArtiSynth models, be sure to add all dependencies. For example, if your model resides under /home/artisynth_projects/classes, but also depends on classes in /home/artisynth_models/classes, then both of these must be added to MATLAB’s Java classpath.
Calling javaaddpath() after the first call to artisynth() may result in some warnings about existing ArtiSynth classes, such as
Warning: Objects of artisynth/core/driver/Main class exist - not clearing java > In javaclasspath>doclear at 377The added classes may also not be visible to ArtiSynth instances created by subsequent invocations of artisynth().