Running Livingstone/L2 Tools/StanleyVJMPL on Ames Solaris Platforms
In a fresh xterm: # set your JAVA_HOME, e.g. % setenv JAVA_HOME /usr/local/j2sdk1_4_1_01 # Solaris 5.8 % stanley Assuming you have added the following or its equivalent to your .<shell>rc file (e.g. for .cshrc) -- set path = ( $path /home/taylor/L2Root/released ) Otherwise ... % cd /home/taylor/L2Root/released_2.7.8.2/l2-tools/stanley-jmpl/interface % ./stanley Optional parameters to "stanley": pass to the Java Virtual Machine the value for -Xms the initial GC space (L2 Tools default 32), in mb -gcinit 64 pass to the Java Virtual Machine the value for -Xmx the maximum GC space (L2 Tools default 192), in mb -gcmax 258
Running Livingstone/L2 Tools/StanleyVJMPL on Solaris or Linux Platforms
In a fresh xterm: # set your JAVA_HOME, e.g. % setenv JAVA_HOME /usr/local/j2sdk1_4_1_01 % cd <root_directory>/l2-tools/stanley-jmpl/interface % ./stanley Optional parameters to "stanley": pass to the Java Virtual Machine the value for -Xms the initial GC space (L2 Tools default 32), in mb -gcinit 64 pass to the Java Virtual Machine the value for -Xmx the maximum GC space (L2 Tools default 192), in mb -gcmax 258
Running Livingstone/L2 Tools/StanleyVJMPL on Windows Platforms
In Cygwin window #1 ------------------- % tcsh # set your L2_ROOT, e.g. % setenv L2_ROOT D:/cygwin/home/wtaylor/L2Root # set your JAVA_HOME, e.g. % setenv JAVA_HOME D:/progra~1/jdk1.4.1_01 % cd $L2_ROOT/l2-tools/stanley-jmpl/interface % ./l2tools -win32 Optional parameters to "l2tools": pass to the Java Virtual Machine the value for -Xms the initial GC space (L2 Tools default 32), in mb e.g. -gcinit 64 pass to the Java Virtual Machine the value for -Xmx the maximum GC space (L2 Tools default 192), in mb e.g. -gcmax 258 In Cygwin window #2 ------------------- % tcsh # set your L2_ROOT, e.g. % setenv L2_ROOT D:/cygwin/home/wtaylor/L2Root # set your JAVA_HOME, e.g. % setenv JAVA_HOME D:/progra~1/jdk1.4.1_01 % cd $L2_ROOT/l2-tools/stanley-jmpl/interface % ./stanley -win32 -exists
L2 Tools/User/Workspace Preferences
Stanley "pull-down" menu selection "Edit->Preferences->L2 Tools/User/Workspace" cascades into "View", "Edit User", and "Edit Workspace". Current preference values are determined from loading the L2 Tools defaults, <release root>/l2-tools/preferences/prefLabels <release root>/l2-tools/preferences/prefDefaults then the user preferences, ${HOME}/.stanley/userPrefs and then the workspace preferences $<workspace root>/workspacePrefs For workspaces other than stanley-sample-user-files, the default Stanley and Livingstone preferences, defined in <release root>/l2-tools/preferences/pref*, can be overriden at the user level, by selecting "Edit User", or at the workspace level, by selecting "Edit Workspace". Normally the stanley-sample-user-files workspace is read-only, because it may be shared with multiple users. If you desire it to be writable, edit <release root>/l2-tools/stanley-jmpl/interface/RUN-STANLEY-VJMPL.csh and change "setenv STANLEY_SUPERUSER taylor", replacing taylor with your login name, for the appropriate operation system.Additional Workspace Configuration
Since each workspace is a unique directory, addition configuration can be done for each workspace. o Component/Module Bitmaps In Lieu Of Rectangles Directory <workspace root>/bitmaps optionally contains pairs of files, created by the unix bitmap utility: <nodeClassName> => bitmap; 1 = foreground; 0 = background <nodeClassName>-mask => bitmap; 1 = show fg/bg; 0 = transparent (nodes are either components or modules) o Component/Module Mode State Names and Colors Having entries in file <workspace root>/display-state-color-prefs is optional. It can contain pairs of mode state names (Java syntax) and associated X11 color names, one pair per line, e.g. lowPressure lightBlue nominalPressure lawnGreen highPressure brickRed ... To add or modify entries in this file, use "Edit->Preferences->Workspace Display State Colors". The mode state names are used in the "Edit->Header->Display Attribute" code to provide background colors representing the current Livingstone mode states. The number of pairs has no practical limit, and are displayed using "Tools->Display Mode State Legend".Managing Workspaces
The default read-only workspace is "stanley-sample-user-files". It contains two simple schematics: "car", a very simple representation of an automobile, and "cbAndLeds" a simple set of a power source, fifteen circuit breakers and eight leds. Also a more complex schematic/model named "mainPropulsionSystem", with sub-modules "pneumaticValveAndMicroSwitches", "pressurizationLineSolenoidValveAndMicroSwitch", and "solenoidValveAndMicroSwitch" is included. These are useful as guides to modeling physical systems. You may create new "template" workspaces with "File->New Workspace", which will create a file hierarchy with no component or module class definitions. There will, however, be abstraction, relation, structure, symbol, and value definitions. "File->New Empty Workspace", on the other hand, will have no definitions, at all. If you have a populated workspace outside of Stanley, and want Stanley to be able to "know" about it, use "File->Import Workspace", which brings up a directory browser. When you make a selection, Stanley does validity checking to make sure this is a valid workspace, and if so, it becomes your current workspace. Stanley them creates auxiliary files which it needs by loading each component and module and writing out the files -- it may take a few minutes to complete. Use menu command "File->Open Workspace" to change between "known" workspaces. "File->Forget Workspace" will make a "known" workspace, "unknown" -- it will no longer appear in the "File->Open Workspace" menu list.