Enabling event logging in MASSIVE

In the shell in which you are going to run the massive clients set the following environment variables (shown in csh style). You must do this before starting MASSIVE.

setenv STATS_FILE filename.%

This will result in a number of files being written to the current directory. There will be one file for the graphical client, one for the textual client and one for the audio client. The "%" will be replaced by the pid of each of these clients.
You'll also need to set the level of logging required:
setenv STATS_LEVEL 62 (bandwidth info)

The full range of logging levels are given below, but we ask you to use a level of 62 for the trials. Thanks.

Marks can be made in the log files by typing "M" in the graphical window. You may be asked to add marks at various stages of the meeting to aid in the analysis of files later.
After each meeting we would be grateful if the files containing the logging information could be made available to us at Nottingham (mail or ftp - we don't mind). Thanks.

Logging Levels

setenv STATS_LEVEL 0
(catches everything)
setenv STATS_LEVEL 62
(bandwidth info)
setenv STATS_LEVEL 65
(user actions and render operations)
setenv STATS_LEVEL 70
(user actions only)

Enabling Event Logging in MASSIVE

Logging Levels