↑ Top
Table of Contents

INTREPID system parameters and install.cfg (R07)

INTREPID originally required operating system environment variables to control system parameters. In the current version, you do not need to set environment variables. Instead, you set system parameters in install.cfg.

To temporarily override a system parameter for a task, set an environment variable with the same name as the system parameter.

Including the INTREPID installation directory in PATH

You need to include the full INTREPID installation path in the PATH system environment variable of your computer or task shell if you want to launch INTREPID tools using commands in any command window. See:

About INTREPID system parameters

INTREPID system parameters reside in the file install.cfg in your installation. See Ways of setting INTREPID system parameters and environment variables below for more information.

Notation for system parameters in this manual

We show the names of system parameters in capitals, (for example, INTREPID_MEMORY) except in examples of text to be typed by you.

We show values of system parameters in monospace font, for example, c:/project

You can use the value of another system parameter in a system parameter assignment (See below).

Ways of setting INTREPID system parameters and environment variables

Hierarchy of system parameter values

INTREPID determines the value of a system parameter in the following order:

  1. If the parameter is set in the task specification (.task) file, INTREPID uses that value.
  2. If the parameter is not set in the task specification (.task) file, INTREPID looks in the environment and uses any value that is set there.
  3. If the parameter is not set in the task specification (.task) file and also not set in the environment, INTREPID uses the value in the install.cfg file.

How to set system parameters under Windows

  • Temporary settings for a particular task specification (.task) file: Assign the parameter a new value in the task specification (.task) file. For example, to force memory use to the disk, you might put:

INTREPID_MEMORY = 10

  • Temporary settings for the current session only (environment variable): (Only if you are launching INTREPID tools using commands) Use the set command before typing the command that launches the INTREPID tool. For example:

set INTREPID_FAST_POINTS = YES

This environment variable setting overrides the setting in install.cfg within the current command window only.

  • Permanent settings for all uses of INTREPID: Edit the install.cfg file in the INTREPID config directory

For example, c:/Program Files/intrepid/config.

How to set system parameters under Linux

Temporary settings for a particular task specification (.task) file: Assign the parameter a new value in the task specification (.task) file. For example, to force memory use to the disk, you might put:

INTREPID_MEMORY = 10

  • Temporary settings for the current session only (environment variable): Use the export or setenv command before typing the command that launches the INTREPID tool, as appropriate for your shell. For example:

export INTREPID_FAST_POINTS=YES

setenv INTREPID_FAST_POINTS YES

This environment variable setting overrides the setting in install.cfg within the current session only.

  • Permanent settings for all uses of INTREPID: Edit the file install.cfg in your INTREPID config directory (for example, c:/intrepid/config).

Note: Using the set commands before launching a tool will override these settings.

Inserting the contents of one variable into another

  • In a task specification (.task) file, when you are simply referring to the value of a system parameter, put a $ symbol in front of its name. For example, $INTREPIDDATA
  • In a task specification (.task) file, if the reference to a system parameter is part of an expression, for example, if you are appending another string to it, put it in parentheses ( ) and put a $ symbol in front of its name. For example:

GravityDirectory = $(INTREPIDDATA)/gravity

You can adopt the practice of always using parentheses. This may help to prevent errors.

  • In install.cfg, always specify existing system parameter names in parentheses with a $ symbol. For example, $(INTREPIDDATA)

List of INTREPID system parameters

This section describes INTREPID’s system parameters.

Several of these (marked ‘*’) only have ‘on’ and ‘off’ states:

  • In install.cfg if a system parameter has value NULL then it is ‘off’. If it has any other value, it is ‘on’.
  • As an environment variable, with no value, it is ‘off’ and if it has a value it is ‘on’

The following table summarises the system parameters.

Parameter name

Contents

INTREPID

The installation directory of INTREPID.

INTREPID_ARCINFO*

Causes INTREPID to create ARC/INFO header and projection files if set.

INTREPID_BILINEAR*

Causes INTREPID to use bilinear interpolation for determining pixel colour or shade in grid dataset display.

INTREPID_ERMAPPER_UPDATE*

Prevents updating of ERMapper header files if set.

INTREPID_FAST_POINTS*

Causes INTREPID to save the sample points during bi-cubic spline initial Gridding. For new grid z only.

INTREPID_HONOUR_ORIGINAL*

Causes INTREPID to save the cell centroids and ’exact’ positions of sample points during grid initialisation in the Gridding process.

INTREPID_JAVA_DEBUG

Turns on verbose debug logging for Java components.

INTREPID_MAX_DEVIATION

Deviation from straight tolerance (in mm) for contour plotting in Hard Copy Composition.

INTREPID_MEMORY

Grid size above which INTREPID uses tiling in grid operations. Default 256 (MB).

INTREPID_NEAREST*

Causes INTREPID to use the nearest cell centroid method for determining pixel colour or shade in grid dataset display.

LD_LIBRARY_PATH

(Linux only) Paths of dynamic libraries. .