Overview

This section describes the options under the Whittle 4D menu (the Whittle 4D version to which this documentation applies is shown on the menu).

The documentation assumes that you have an understanding of Vulcan block models, the Whittle 4D programs and their associated data files.

To access the Whittle 4D programs in Vulcan the following must be set:

  • The environment variable WHITTLE_EXE. This variable must point to an existing directory.
  • The Whittle 4D programs must reside in WHITTLE_EXE.
  • The Whittle initialisation file FD.INI must reside in the current working directory.

The Whittle 4D interface provides an intuitive approach to using Whittle 4D pit optimisation programs.

The interface consists of two parts:

  • Vulcan block model interface.
  • Whittle program access.

The steps to follow for using the Whittle interface are:

  1. Insert appropriate Whittle variable names into your Vulcan block model and, where necessary, assign values to them using block model scripts.

    For example, variables total-tons and proc-fac could, respectively, hold the pre-calculated total tonnage and processing factor when dumping blocks. Similarly, variable pit could store the pit number when importing mined (results) blocks. Block model scripts are described in the Manipulation section.

    For more information on the Whittle 4D interface, see Appendix C .

  2. Create a Whittle model parameter file to describe the pit optimisation required. It is often easier to modify an existing parameter file to suit your needs rather than starting a new one.
  3. Perform a Whittle run (this is a combination of several steps).

Note:   The Whittle 4D interface allows both regular and irregular (sub blocked) block models.

The Whittle programs may be run from Vulcan or from the shell prompt. Each program has a four letter identifier and can be accessed using the WHITTLE_EXE environment variable. Make sure that this environment variable is correct before starting Vulcan. It contains the path to the directory containing the Whittle 4D programs.

For example:

% setenv WHITTLE_EXE $VULCAN/whittle/exe

The variable is usually defined in either a user or Vulcan login shell script. If this variable is undefined, the Whittle 4D programs cannot be run from Vulcan. The spawned window will disappear before the Whittle 4D program executes.

The Whittle 4D program identifiers are:

  • FDRB (re-blocker)
  • FDST (arc creator)
  • FDOP (optimiser)
  • FDPR (block printer)
  • FDED (parameter editor)
  • FDAN (results analyser)
  • FDUT (utility

Default file names and file extensions can be specified in the Whittle 4D initialisation file ( Edit FD.INI option). If this is not used, then the hardcoded defaults will apply. The Setup option to specify whether to use the FD.INI file or the hardcoded file extensions.

Note:   We recommend that a FD.INI file is used as this to change the .res and .wrk file extensions. This is important as these extensions are also used by, respectively, (Block) Reserve calculation options and Vulcan design databases. Failure to change these file extensions may be confusing and lead to corrupted files.

The Whittle interface generates temporary files that are put in the default temporary directory. This directory is cleared when exiting Vulcan unless the environment variable ENVIS_W4D_KEEP is set to TRUE or 1 prior to running Vulcan. Refer to the System Administration documentation for details on environment variables.

If an auto log file exists for a Whittle 4D program it will be used when the program is executed instead of the Vulcan commands file. To prevent this, the auto log file is saved with the name:

auto<programidentifier>.log_sav

When the program has successfully finished the auto log file is restored to its original name. Any error messages are stored in the w4d_interface.err file.