Chapter 12. Debrief maintainer's guide
- Table of Contents
- 12.1. Installation Guidance
- 12.2. Fault-Diagnosis Instructions
- 12.3. Debrief Properties
12.1. Installation Guidance
12.1.1. System Requirements
Table 12-1. Requirements for Debrief
Requirement |
Minimum |
Recommended |
|---|---|---|
|
Processor |
800 MHz |
1400 MHz |
|
Memory |
128 Mb |
256 Mb |
|
Java Virtual Machine |
JVM 1.3 (Debrief relies on JVM 1.3 for its updated Table control. For a JVM1.2 version of Debrief, please contact the administrator). |
As new as possible. JVM 1.4.1 includes mouse-wheel control, has been seen to provide the fastest performance, and provides the most robust 3-d plotting support (JVM1.4.0 experienced problems with 3-d plotting). |
|
Java 3D Libraries (required for viewing Debrief plots in 3D a ) | Java 3D 1.3 |
Java 3D 1.3 |
|
XML Libraries |
SAX and DOM support (through the enclosed jaxp.jar and parser.jar libraries) | |
|
Java Media Framework (required for copying Debrief sessions to video file). |
2.1.1 (through the enclosed jmf.jar library) | |
|
OpenMap libraries (used for plotting NIMA's Vector Map data) |
4.2.1 (through the enclosed openmap.jar library) | |
| Notes: a. To interactively view Debrief plots in 3 dimensions the Java 3d runtime files and libraries must be installed on the machine. These libraries are a free download from the Java website. | ||
12.1.2. Directory Structure
The directory where the application startup script is installed is called the "Startup Directory". The Startup Directory is set during the installation of Debrief, and defaults to c:\Program Files\Debrief 2002. In this directory you should find a collection of REP and XML files, some icons, the CHM help file, the d2ksettings.prp properties file. In a sub-directory titled lib, are Debrief's supporting libraries (mostly third party), and in the directory named UninstallerData are the files necessary to support removing Debrief.
12.1.3. Starting the program
The shortcut placed on the menu actually calls the Debrief 2002.exe file found in the startup directory. This application sets the class-path for the application and starts Debrief itself (which is contained in D2002.jar). It is also possible to start the application by double-clicking on D2002.jar itself.
There are instances when Debrief has an insufficient memory allocation (of 64Mb) and halts processing reporting an out of memory error to the trace.txt. Such instances occur more frequently with ETOPO data loaded. To increase the maximum memory allocated to Debrief, insert the following lines into the top of Debrief launch properties file, titledDebrief 2002.lax:
# Debrief OPTIONS, inserted by HAND - 11/Jul/02
# --------------------
# Increase the maximum memory available to Debrief
lax.nl.java.option.additional=-Xmx200mThe example shown above allows the memory allocated to Debrief to expand up to 200 Mb if necessary.
 | As you may be aware, Debrief uses the InstallAnywhere Now! application from ZeroG for its installation. In addition to copying Debrief and its supporting files into the correct directories, the installer provides an executable which can be used to start Debrief - particularly useful for MS Windowsusers are used to starting applications which a exe suffix. This application is called Debrief 2002.exe. The application loads Debrief using the settings and parameters contained in a data-file, which takes the same name as the application but adds a lax suffix. The workaround described above adds a property to this settings file to increase the memory available to Debrief. Other settings in the .lax file specify where Java is installed on the current machine, and what library files Debrief relies on. |