MoMo and the GL-toolbox store some preferences permanently: names of
computer and user, path names of measurement and norm data, styles for the
graphical user interface and a list of recently processed sessions. The first
time a function needs values of preferences, a dialog appears to allow
definitions. The settings are saved to a folder inside Matlab's application data
path, therefore the preferences depend on the computer, user and Matlab version.
Determined this folder with GLTools_local('PrefPath'), which
replies "prefdir\JSim\".
The files found there can be deleted on problems. They are recreated
automatically asking the user for the wanted settings.
Additional help for the management of local variables:
"<MFiles>\Docs\ReadMe_LocalSystem.txt".
The function
Path_local manages default values for the
preferences. The variables and their values can be adjusted to the lab
environment with:
Path_local $edit.
This opens the file "<MFiles>\Path_local.init"
for editing. E.g. the network path to the Vicon data folder can be defined here
and the users get a valid default value in the dialog of
MoMo_local.
Nevertheless, all functions of MoMo using preferences can handle missing or
invalid values, e.g. not existing path names. Therefore editing the defaults is
optional.
You can use
Path_local for your own programs also, see there for
more help.
MoMo stores some preferences permanently for future Matlab sessions.
These preferences can be controlled by the dialog opend by
momo prefs. The different single categories are mentioned below to
be complete here (see 3.4 to 3.8), but for daily use it is enough to know
momo prefs as gateway.
After installing a new MoMo version, this dialog is opened automatically and it
is enough to run it once.
User:
- Auto config: This starts the auto configuration of the
functions in the Expert section. If the admin has defined
valid values for Default_local, this is enough for a complete
configuration of a new client computer or user. otherwise some dialogs appear to
define the needed values.
Expert:
- Machine: Name of computer, location and operating
system (3.4)
- MoMo: Paths needed by MoMo
(3.5)
- GhostScript: Absolute file name of GhostScript
executable (3.6)
- Database folder: Base folder for exported ASCII files
(3.7)
Cleanup:
- Reset MoMo: All currently stored links and paths are
reset, e.g. the user-color and research model function pointers, the database
folder, connections between the GUI and the subfunctions. This button is
equivalent to restarting Matlab.
For MoMo the command clear all would be ok also, but other
toolboxes might fail then.
- Limit cache: This button limits the disk space occupied
by locally store trial cache files to 500MB. Call this once a month.
See also: help moCacheFile.
GUI Style:
- The color scheme and font size of dialogs can be chosen here. It is defined
for a user and a specific computer.
More help for GUI styles: help DlgSkin.
The program Machine_local is responsible for the
identification of the computer, the user and the operating system. It is
started automatically, e.g. from iniGL.
- Host: Name of the computer.
- Location: Name of the lab.
- User: Name of the user - this is taken from the
operating system and cannot be edited.
- OS: Operating system - cannot be edited.
- OSType: Type of the operating system - this allows MoMo
to work with future operating system, if they are compatible with a known type,
e.g. Windows Vista can be treated as Windows XP. If the OS is recognized, you
cannot choose a deviating value here.
Default values:
Default_local.
Open dialog manually:
Machine_local $edit.
Get all variables:
Machine_local('$all').
Get specific variable, e.g. Matlab's release number:
Machine_local('MatlabRNum').
MoMo_local manages machine depending paths to allow MoMo
working in network environments. Three paths are defined permanently for future
Matlab sessions:
MoMoData
,
MotionData,
MoMoArchive.
The folder MoMoData contains subfolders for norm data,
description pictures, session sets and bug reports. Expert users can modify
these paths in the "Temporary" section, e.g. to test the creation of
norm data without the danger of overwriting original data for daily routine.
A check box must be enabled and reminds the user, that the changes are reset
automatically.
Not existing folders are marked by a red background. Although MoMo tries to
work in spite of problems with missing folders, a successful run of MoMo cannot
be guaranteed.
Permanent: Settings are saved for future Matlab sessions.
- MoMoData: The base folder, where MoMo saves and loads
norm data, session set definitions, description pictures, bug reports, logs and
the documentations. Use the open-folder button to choose a new folder.
- MotionData: The paths containing the current
measurement data folders. This path is needed for the definitions of
session-sets.
- MotionArchive: Vicon-Workstation allows to store
processed sessions in an extra archive folder. If this is not used in your lab,
set this equal to MotionData.
- WorkPath: New
This is the standard path for exported files (PDFs, picture files, tables, but
not the database export). This is new in MoMo R5.0.10 and supported only by a few
functions yet. Creating all files in the session folder pollutes the measurement
data. Some logical ideas for the WorkPath are the local
and personal TEMP folder, "<MoMoData>/Results" or a subfolder
named as the user, a study or a date.
- Default values for these fields are defined in
Default_local.
Temporary: Settings are cleared automatically.
- For "experts" only, e.g. for test environments.
- The checkbox must be enabled at first to remind the user, that these changes
are removed automatically, e.g. by
clear all, or
MoMo_local $clear, or restarting the Matlab session.
- Temporary modification of variables can be applied manually also without
this dialog:
MoMo_local('$set', NameOfVariable, Value).
- Default values for the Temporary: section are defined
in
MoMo_local.
The managed variables can be obtained e.g. with:
MoMo_local('WorkPath') or as struct with all variables:
MoMo_local('$all').
The function
Ghostscript_local stores a pointer to the
executable of
GhostScript, which is used for the
creation of PDF files. It is important to choose the command line program
"gswin32c.exe" with the trailing "c" in the name.
Default values: none - perhaps:
"C:\Program files\gs\gsX.YZ\bin\gswin32c.exe".
Choose the executable: GhostScript_local $edit
GhostScript version: GhostScript_local $version
MoMo exports trials and averaged sessions in ASCII format to the folder:
"<Base>\<ExaminationDATE:YYYYMMDD>\<ID>\". The path
is created by the function moDBFolder, which uses the <Base>
folder defined in dbPreferences as default. For testing you can
change the export folder temporarily in moDBFolder.
Default values:
dbPreferences (
Default_local
works as fallback)
Choose a folder:
moDBFolder $edit
Get current folder:
moDBFolder $basepath
Set folder temporarily:
moDBFolder('$set', <PathName>, 'temporary')
Reset temporary changes:
moDBFolder $clear
The dialog for
editing the examination
information can show popup-menus for the fields
Examinator and
Study. The user can
toggle with a right-click between the appearance of popup-menus and edit
fields for free input. The values of the popup menus can be adjusted in a
function:
edit StudyStaffList.
The predefined names might accelerate the filling of the dialog.
MoMo calls the functions SuWarn and SuError for
warnings and errors. These functions use XBeep to signal
problems. The sound can be disabled for the current sessions:
XBeep off.