--------------------------------------------------------------------------------
MODULE TRIDER

--------------------------------------------------------------------------------
REPLACES PANACEA module PANDER

--------------------------------------------------------------------------------

FUNCTION

--------------------------------------------------------------------------------

FORMAT

--------------------------------------------------------------------------------

COMMAND QUALIFIERS

DESCRIPTION

--------------------------------------------------------------------------------

DESCRIPTION

--------------------------------------------------------------------------------

GENERAL

--------------------------------------------------------------------------------

TRIDER AND IMAGINARY POINT ESTIMATION

--------------------------------------------------------------------------------

TRIDER GRAPHICS OUTPUT OPTION

--------------------------------------------------------------------------------

TRIDER COMMANDS

_@ COMMAND

--------------------------------------------------------------------------------
_@

--------------------------------------------------------------------------------
FORMAT: _@file-spec<CR>

--------------------------------------------------------------------------------
Command parameters:

--------------------------------------------------------------------------------
DESCRIPTION:

TRIDER offers the facility of command input from an indirect command file. The '@' character preceding a file-spec will cause TRIDER to open and read commands from the specified file until:

Nested command files are not supported (i.e. a command file containing an '@' command), although sequential '@' commands are supported when read from SYS$COMMAND.

As an aid to batch log interpretation TRIDER will echo all commands read from an indirect command file.

--------------------------------------------------------------------------------
Messages:

The following messages are specific to the _@ command:

*** WARNING *** "@" must precede a file-spec

*** WARNING *** Indirect file error - returning to terminal input

*** ERROR *** Can't open indirect command file 'file-spec'

--------------------------------------------------------------------------------
Examples:


$ TRIDER<CR>
DTMCREATE module TRIDER of 16:30:12 20-NOV-87
TRIDER> @FLOW2<CR>
TRIDER> ENABLE DIAGNOSTICS
TRIDER> ENABLE GRAPHICS
TRIDER> IMAGINARY FIXED 0.0 1.0
TRIDER> RETURN
TRIDER>

_! COMMAND

--------------------------------------------------------------------------------
_!

--------------------------------------------------------------------------------
FORMAT: _! [comment text]

--------------------------------------------------------------------------------
Command parameters:

--------------------------------------------------------------------------------
DESCRIPTION:

An exclamation mark is the standard DTM package comment delimiter. All text (and numbers) which lie to the right of a '!' character are excluded from command interpretation. Comments are useful for annotating command procedures used in batch processing etc_.

--------------------------------------------------------------------------------
Messages: None.

--------------------------------------------------------------------------------
Examples:


TRIDER> _! a comment for the sake of it<CR>
TRIDER> ENABLE GRAPHICS ! turn graphics on<CR>
TRIDER> ! get files and estimate the derivatives
TRIDER> FILEIN DUA0:[TESTDATA]IDAHO<CR>
_.DTA file DUA3:[DEMONSTRATION]IDAHO_.DTA;15 opened for read
_.NOD file DUA3:[DEMONSTRATION]IDAHO_.NOD;15 opened for read
_.DER file DUA3:[DEMONSTRATION]IDAHO_.DER;15 opened for write
TRIDER> GO<CR>
ELAPSED: 00:05:25.84 CPU: 0:00:05.71 BUFIO: 281 DIRIO: 46 FAULTS: 263
_$

DISABLE DIAGNOSTICS COMMAND

--------------------------------------------------------------------------------
DISABLE DIAGNOSTICS

--------------------------------------------------------------------------------
FORMAT: DISABLE DIAGNOSTICS

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
DESCRIPTION:

DISABLE DIAGNOSTICS allows the user to cancel the effect of a previous ENABLE DIAGNOSTICS command.

--------------------------------------------------------------------------------
Messages: None.

--------------------------------------------------------------------------------
Examples:


TRIDER> ENABLE DIAGNOSTICS<CR>
TRIDER> SHOW ENABLE<CR>
DIAGNOSTICS ............................................... On
GRAPHICS .................................................. Off
PME ....................................................... Off
TRIDER> DISABLE DIAGNOSTICS<CR>
TRIDER> SHOW ENABLE<CR>
DIAGNOSTICS ............................................... Off
GRAPHICS .................................................. Off
PME ....................................................... Off
TRIDER>

DISABLE GRAPHICS COMMAND

--------------------------------------------------------------------------------
DISABLE GRAPHICS

--------------------------------------------------------------------------------
FORMAT: DISABLE GRAPHICS

--------------------------------------------------------------------------------
Command parameter: None.

--------------------------------------------------------------------------------
DESCRIPTION:

The DISABLE GRAPHICS command cancels the effect of a previous ENABLE GRAPHICS command.

--------------------------------------------------------------------------------
Messages: None.

--------------------------------------------------------------------------------
Examples:


$ TRIDER<CR>
DTMCREATE module TRIDER of 13:30:39 20-AUG-87
TRIDER> SHOW ENABLE<CR>
DIAGNOSTICS ............................................... Off
GRAPHICS .................................................. Off
PME ....................................................... Off
TRIDER> ENABLE GRAPHICS<CR>
TRIDER> SHOW ENABLE<CR>
DIAGNOSTICS ............................................... Off
GRAPHICS .................................................. On
PME ....................................................... Off
TRIDER>

DISABLE PME COMMAND

--------------------------------------------------------------------------------
DISABLE PME

--------------------------------------------------------------------------------
FORMAT: DISABLE PME

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
DESCRIPTION:

The ENABLE PME and DISABLE PME commands are reserved for Laser-Scan use. PME is a code optimisation tool and should be invoked by LSL software personnel only.

DISABLE PME disables the effect of a previous ENABLE PME command and causes the PME_EXIT routine to be invoked.

--------------------------------------------------------------------------------
Message:

The following warning message is specific to the DISABLE PME command:

*** WARNING *** You were not using PME anyway!

--------------------------------------------------------------------------------
Examples:


$ TRIDER<CR>
DTMCREATE module TRIDER of 13:30:39 20-AUG-87
TRIDER> ENABLE PME ! turn PME on<CR>
TRIDER> DISABLE PME ! turn it off again!!<CR>
TRIDER> FILEIN FAITH<CR>
_.DTA file DUA3:[DEMONSTRATION]FAITH_.DTA;15 opened for read
_.NOD file DUA3:[DEMONSTRATION]FAITH_.NOD;15 opened for read
_.DER file DUA3:[DEMONSTRATION]FAITH_.DER;15 opened for write
TRIDER> GO<CR>
ELAPSED: 00:05:25.84 CPU: 0:00:05.71 BUFIO: 281 DIRIO: 46 FAULTS: 263
_$

ENABLE DIAGNOSTICS COMMAND

--------------------------------------------------------------------------------
ENABLE DIAGNOSTICS

--------------------------------------------------------------------------------
FORMAT: ENABLE DIAGNOSTICS

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
DESCRIPTION:

ENABLE DIAGNOSTICS allows the user to enable diagnostic printout.

Because it is usually used in a batch processing environment, by default TRIDER produces minimal diagnostic printout. If however, the user wishes to receive indications of processing progress and of the effect of selections on data input, diagnostic printout may be selected with the ENABLE DIAGNOSTICS command.

It should be noted that if DIAGNOSTICS are enabled, TRIDER can produce voluminous printout.

If SYS$OUTPUT is directed to a video screen terminal, messages indicating percentage progress are issued.

--------------------------------------------------------------------------------
Messages: None.

--------------------------------------------------------------------------------
Examples:


TRIDER> ENABLE DIAGNOSTICS<CR>
TRIDER> SHOW ENABLE<CR>
DIAGNOSTICS ............................................... On
GRAPHICS .................................................. Off
PME ....................................................... Off
TRIDER> DISABLE DIAGNOSTICS<CR>
TRIDER> SHOW ENABLE<CR>
DIAGNOSTICS ............................................... Off
GRAPHICS .................................................. Off
PME ....................................................... Off
TRIDER>

ENABLE GRAPHICS COMMAND

--------------------------------------------------------------------------------
ENABLE GRAPHICS

--------------------------------------------------------------------------------
FORMAT: ENABLE GRAPHICS

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
DESCRIPTION:

TRIDER offers the option to generate graphic output to indicate processing progress. By default graphic output is disabled. To prevent a user selecting graphics when it is inappropriate to the current terminal, TRIDER uses a lookup table of terminal characteristics associated with all available terminal lines (see Appendix 1). An invalid graphics selection will result in a warning message and the default NO GRAPHICS option being selected.

Graphics selection may be cancelled with the DISABLE GRAPHICS command.

--------------------------------------------------------------------------------
Messages:

The following messages are specific to the ENABLE GRAPHICS command:

*** ERROR  *** reading lookup file at line 'integer'
*** WARNING *** Unable to open "LSL$LOOKUP:TERMTYPE.DAT"
Sorry 'name' terminal  'terminal-ident' isn't in the lookup table
Sorry 'name' terminal 'terminal-ident' can't support graphics
*** ERROR  *** translating logical name LSL$DTMCREATETERMINAL

--------------------------------------------------------------------------------
Examples:


$ TRIDER<CR>
DTMCREATE module TRIDER of 13:30:39 20-AUG-87
TRIDER> SHOW ENABLE<CR>
DIAGNOSTICS ............................................... Off
GRAPHICS .................................................. Off
PME ....................................................... Off
TRIDER> ENABLE GRAPHICS
TRIDER> SHOW ENABLE<CR>
DIAGNOSTICS ............................................... Off
GRAPHICS .................................................. On
PME ....................................................... Off
TRIDER> DISABLE GRAPHICS<CR>
TRIDER> SHOW ENABLE<CR>
DIAGNOSTICS ............................................... Off
GRAPHICS .................................................. Off
PME ....................................................... Off
TRIDER>

ENABLE PME COMMAND

--------------------------------------------------------------------------------
ENABLE PME

--------------------------------------------------------------------------------
FORMAT: ENABLE PME

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
DESCRIPTION:

The ENABLE PME and DISABLE PME commands are reserved for Laser-Scan use. PME is a code optimisation tool and should be invoked by LSL software personnel only.

ENABLE PME causes the PME_INIT routine to be invoked.

--------------------------------------------------------------------------------
Message:

The following warning message is specific to the ENABLE PME command:

*** WARNING *** You are already using PME!

--------------------------------------------------------------------------------
Examples:


$ TRIDER<CR>
DTMCREATE module TRIDER of 13:30:39 20-AUG-87
TRIDER> ENABLE PME<CR>
TRIDER> FILEIN FAITH<CR>
_.DTA file DUA3:[DEMONSTRATION]FAITH_.DTA;15 opened for read
_.NOD file DUA3:[DEMONSTRATION]FAITH_.NOD;15 opened for read
_.DER file DUA3:[DEMONSTRATION]FAITH_.DER;15 opened for write
TRIDER> GO<CR>
ELAPSED: 00:05:25.84 CPU: 0:00:05.71 BUFIO: 281 DIRIO: 46 FAULTS: 263
_$

FILEIN COMMAND

--------------------------------------------------------------------------------
FILEIN

--------------------------------------------------------------------------------
FORMAT: FILEIN file-spec

--------------------------------------------------------------------------------
COMMAND PARAMETERS:

--------------------------------------------------------------------------------
DESCRIPTION:

TRIDER expects as input the 2 binary structured data files (the matched pair of _.NOD and _.DTA files) produced by TRIANG or TRIEDIT. It produces an output file containing the slope derivatives estimated for each data point contained in the triangulation.

The specification of the output file has the same device, directory filename and version number as the input files but is given the extension _.DER.

Since it is essential that the file version numbers of the _.NOD, _.DTA and _.DER file always match, TRIGRID performs checks on file version numbers. If mismatches are found, TRIDER complains and aborts execution. Similarly, an error occurs if TRIDER attempts to create a new _.DER file which has a version number which already exists.

--------------------------------------------------------------------------------
Messages:

The following messages are specific to the FILEIN command:

*** WARNING *** You must specify a file-spec argument to the FILEIN command
For example FILEIN SWAREA
*** ERROR *** Unable to interpret input file-spec

*** ERROR *** opening input file

_.DTA file 'file-spec' opened for read
_.NOD file 'file-spec' opened for read
_.DER file 'file-spec' opened for write

--------------------------------------------------------------------------------
Examples:


TRIDER> FILEIN DUA3:[DEMONSTRATION]IDAHO<CR>
_.DTA file DUA3:[DEMONSTRATION]IDAHO_.DTA;15 opened for read
_.NOD file DUA3:[DEMONSTRATION]IDAHO_.NOD;15 opened for read
_.DER file DUA3:[DEMONSTRATION]IDAHO_.DER;15 opened for write
TRIDER>

GO COMMAND

--------------------------------------------------------------------------------
GO

--------------------------------------------------------------------------------
FORMAT: GO

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
DESCRIPTION:

When all necessary files have been read in the GO command will commence the gridding process. Unless relatively small data-sets are being handled (say less then 50,000 data points) it is strongly recommended that TRIDER is run in batch mode at an off-peak time.

When grid creation is complete, TRIDER closes the output DTI file and then exits.

--------------------------------------------------------------------------------
Messages:

Once the GO command has been issued no more conversational messages of the *** WARNING *** format will be issued. Any messages will relate to serious processing problems and will normally result in abnormal TRIDER termination. The messages relating to non-interactive processing problems are presented at the end of this document.

--------------------------------------------------------------------------------
Examples:


TRIDER> GO<CR>

ELAPSED: 0 00:05:21.82 CPU: 0:00:01.40 BUFIO: 51 DIRIO: 15 FAULTS: 170
$

HELP COMMAND

--------------------------------------------------------------------------------
HELP

--------------------------------------------------------------------------------
FORMAT: HELP subject

--------------------------------------------------------------------------------
Command parameters:

--------------------------------------------------------------------------------
Description:

The HELP command looks the rest of the line up in the DTMCREATE HELP library. This library contains a brief summary of the operation of each command.

The information is looked up in the TRIDER section of the DTMCREATE help library, LSL$HELP:DTMCREATE.HLB.

--------------------------------------------------------------------------------
Messages:

Where required, warning messages are output via the VMS LBR$OUTPUT_HELP utility.

--------------------------------------------------------------------------------
Examples:


TRIDER> HELP RETURN<CR>

RETURN

TRIDER>

IMAGINARY BOX COMMAND

--------------------------------------------------------------------------------
IMAGINARY BOX

--------------------------------------------------------------------------------
FORMAT: IMAGINARY BOX interpolation reloc

--------------------------------------------------------------------------------
Command parameters:

--------------------------------------------------------------------------------
DESCRIPTION:

This imaginary point height estimation option performs a distance weighted interpolation based on points discovered by means of an expanding hollow box search. The box search is in turn based around the box structure generated by TRIANG. The interpolation is formed by standard methods. The box size expands automatically until sufficient points have been discovered. This method is probably most applicable to genuinely variable data of the seismic or non contour type. If spot heights form a large proportion of the data set or any other irregularly distributed data is used, the box option should be chosen as it will provide a very smooth edge around the data area.

IMAGINARY BOX and imaginary point relocation

As an interpolation option has been chosen for the imaginary points then in most cases it will be sensible, if not vital, to keep the imaginary points close to the grid itself. This ensures that the imaginary points are most closely controlled by those points falling closest to them. Thus set the imaginary point relocation proportion to 0.0 or close to 0.0.

--------------------------------------------------------------------------------
Messages:

*** WARNING *** Please use the IMAGINARY command again and choose from FIXED
TREND, BOX or SHELLNEIGHBOUR as the first command argument.
The default method of imaginary point estimation is
'method', which remains unchanged

*** ERROR *** Missing IMAGINARY command arguments

*** ERROR *** Missing weighting function name

*** WARNING *** "LINEAR" interpolation selected by default

*** ERROR *** Missing relocation proportion

*** ERROR *** Reading relocation proportion

--------------------------------------------------------------------------------
Examples:


TRIDER> IMAGINARY BOX QUARTIC 0.0<CR>
TRIDER>

IMAGINARY FIXED COMMAND

--------------------------------------------------------------------------------
IMAGINARY FIXED

--------------------------------------------------------------------------------
FORMAT: IMAGINARY FIXED fixval reloc

--------------------------------------------------------------------------------
Command parameters:

--------------------------------------------------------------------------------
DESCRIPTION:

The fixed option assumes that the user wishes the surface to decline to some fixed value all the way around the edge of the triangulated area at some distance (yet to be determined) from the main grid coverage. By using the FIXED option the user can specify the value to be used for the imaginary point Z values. TRIDER will then automatically insert this value at all imaginary point locations and will also insert zero partial derivatives at each of the imaginary points. This will have the effect of making the surface flatten to a plane by the time that the imaginary points are reached. This plane will be horizontal because the derivatives have been set to zero.

IMAGINARY FIXED and imaginary point relocation

When the IMAGINARY FIXED option is chosen, it is sensible to locate the imaginary points reasonably far away from the edge of the grid. This is necessary to ensure that the surface has a fairly flexible approach to reaching the imaginary point values. In areas where the surface is not close to the fixed value it needs room to manoeuvre itself to these values!

--------------------------------------------------------------------------------
Messages:

*** WARNING *** Please use the IMAGINARY command again and choose from FIXED
TREND, BOX or SHELLNEIGHBOUR as the first command argument.
The default method of imaginary point estimation is
'method', which remains unchanged

*** ERROR *** Missing IMAGINARY command arguments

*** ERROR *** Missing relocation proportion

*** ERROR *** Reading relocation proportion

--------------------------------------------------------------------------------
Examples:


TRIDER> IMAGINARY FIXED 0.0 1.0<CR>
TRIDER>

IMAGINARY SHELLNEIGHBOUR COMMAND

--------------------------------------------------------------------------------
IMAGINARY SHELLNEIGHBOUR

--------------------------------------------------------------------------------
FORMAT: IMAGINARY SHELLNEIGHBOUR interpolation reloc

--------------------------------------------------------------------------------
Command parameters:

--------------------------------------------------------------------------------
DESCRIPTION:

IMAGINARY SHELL/NEIGHBOUR - The method of collection of data points employed is that of successively finding the neighbours of the point in question by running through the triangular node/neighbour data structure created by program TRIANG and stored in a file. The process can be thought of as that of picking up points in a series of layers. Thus the first layer consists of the neighbours of the point itself. The second layer contains the neighbours of the neighbours that have been picked up but not including any previously found points. This process could obviously continue until all data points in the data set have been found!

A height for every imaginary point will then be estimated using a specified weighting function, using the neighbours that have been found. If an insufficient number of of real neighbours has been found then the program will automatically search deeper into the data structure.

If any of the first layer neighbours contain points marked as discontinuous during the initial data formation stage at the beginning of TRIANG then a further search is made. This checks whether any layer 1 adjacent neighbours are:

If so then the interpolation point is assigned the same value as these. The reason for this is that it is quite possible that there will be flat plateau-like areas on a contour map which should remain flat at the edges of a map. Usually, and hopefully, there will be control points in these flat areas at the edges to help the automatic calculation process along. But sometimes this can be difficult and hence this check for discontinuous points is an attempt to ensure locally that the imaginary points are biased towards representing locally flat discontinuous structures.

IMAGINARY SHELLNEIGHBOUR and imaginary point relocation

As an interpolation option has been chosen for the imaginary points then in most cases it will be sensible, if not vital, to keep the imaginary points close to the grid itself. This ensures that the imaginary points are most closely controlled by those points falling closest to them. Thus set the imaginary point relocation proportion to 0.0 or close to 0.0.

--------------------------------------------------------------------------------
Messages:

*** WARNING *** Please use the IMAGINARY command again and choose from FIXED
TREND, BOX or SHELLNEIGHBOUR as the first command argument.
The default method of imaginary point estimation is
'method', which remains unchanged '

*** ERROR *** Missing IMAGINARY command arguments

*** ERROR *** Missing weighting function name

*** WARNING *** "LINEAR" interpolation selected by default

*** ERROR *** Missing relocation proportion

*** ERROR *** Reading relocation proportion

--------------------------------------------------------------------------------
Examples:


TRIDER> IMAGINARY SHELLNEIGHBOUR QUADRATIC 0.0<CR>
TRIDER>

IMAGINARY TREND COMMAND

--------------------------------------------------------------------------------
IMAGINARY TREND

--------------------------------------------------------------------------------
FORMAT: IMAGINARY TREND reloc

--------------------------------------------------------------------------------
Command parameters:

--------------------------------------------------------------------------------
DESCRIPTION:

Quite often the user will not have any idea what individual values to give the imaginary points but will know that he does not want a fixed horizontal plane at the edge of his data. The default IMAGINARY option therefore is to assign the values of the imaginary points to be those calculated from a linear trend surface fitted through all the data points in the interpolation area. The derivatives assigned to the imaginary points will then be those partial derivatives estimated for the plane itself. Thus if the data set has a definite trend (for instance increasing in height to the south west) this option would produce an equivalent trend in the heights of the imaginary points.

IMAGINARY TREND and imaginary point relocation

When the IMAGINARY TREND option is chosen, it is sensible to locate the imaginary points reasonably far away from the edge of the grid. This is necessary to ensure that the surface has a fairly flexible approach to reaching the imaginary point values. In areas where the surface is not close to the trend value it needs room to manoeuvre itself to these values!

--------------------------------------------------------------------------------
Messages:

*** WARNING *** Please use the IMAGINARY command again and choose from FIXED
TREND, BOX or SHELLNEIGHBOUR as the first command argument.
The default method of imaginary point estimation is
'method', which remains unchanged '

*** ERROR *** Missing IMAGINARY command arguments

*** ERROR *** Missing relocation proportion

*** ERROR *** Reading relocation proportion

--------------------------------------------------------------------------------
Examples:


TRIDER> IMAGINARY TREND 1.0<CR>
TRIDER>

PAUSE COMMAND

--------------------------------------------------------------------------------
PAUSE

--------------------------------------------------------------------------------
FORMAT: PAUSE

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
DESCRIPTION:

Pauses TRIDER execution and issues a prompt for a carriage return to continue execution. This command is designed for use in software demonstration situations.

--------------------------------------------------------------------------------
Messages: None.

--------------------------------------------------------------------------------
Examples:


TRIDER> PAUSE<CR>


Press to continue<CR>
TRIDER>

QUIT COMMAND

--------------------------------------------------------------------------------
QUIT

--------------------------------------------------------------------------------
FORMAT: QUIT

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
Description:

The QUIT command causes TRIDER to exit immediately, closing all input files and closing and deleting all output files.

(pressing the Ctrl and Z keys together) may also be used to quit from the program.

--------------------------------------------------------------------------------
Messages: None.

--------------------------------------------------------------------------------
Examples:

TRIDER> QUIT<CR>
ELAPSED: 00:05:25.84 CPU: 0:00:05.71 BUFIO: 281 DIRIO: 46 FAULTS: 263
_$

RETURN COMMAND

--------------------------------------------------------------------------------
RETURN

--------------------------------------------------------------------------------
FORMAT: RETURN

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
DESCRIPTION:

Restores command input from an indirect file to SYS$COMMAND.

A typical application is to allow the user to use an indirect command file to set up those run time defaults which are constant within a flowline and then return to input from the terminal (or batch stream) for the run specific commands. To do this RETURN must be the last command in the indirect command file.

--------------------------------------------------------------------------------
Messages:

The following messages are specific to the RETURN command:

RETURN command detected - returning to terminal input
RETURN command ignored - command input is already from terminal

--------------------------------------------------------------------------------
Examples:


TRIDER> @FLOW2<CR>
TRIDER> ENABLE DIAGNOSTICS
TRIDER> FRT FLOW2
FRT file LSL$FRT:FLOW2.FRT;8 opened for read
TRIDER> SELECT OPEN_CLIFF_FC OUTCROPS,7,COAST
TRIDER> RETURN
TRIDER>

SHOW COMMAND

--------------------------------------------------------------------------------
SHOW

--------------------------------------------------------------------------------
FORMAT: SHOW subject

--------------------------------------------------------------------------------
Command parameters:

--------------------------------------------------------------------------------
DESCRIPTION:

SHOW enables the user to examine the current status of TRIDER options and parameter settings.

--------------------------------------------------------------------------------
Messages:

TRIDER issues the following message if the SHOW command is specified without an argument:


*** ERROR *** Specifying command SHOW

Available SHOW command qualifiers are:

ENABLE      FILES      IMAGINARY        ZLIMITS

This feature can be used to advantage if the user wishes to quickly determine for which items the SHOW facility is available.

--------------------------------------------------------------------------------
Examples:

$ TRIDER<CR>
DTMCREATE module TRIDER of 17:02:12 23-JAN-89

TRIDER> SHOW<CR>
*** ERROR *** Specifying command SHOW

Available SHOW command qualifiers are:

ENABLE      FILES      IMAGINARY        ZLIMITS


TRIDER> SHOW ENABLE ! examine current option settings<CR>
DIAGNOSTICS ............................................... Off
GRAPHICS .................................................. Off
PME ....................................................... Off
TRIDER>

SHOW ENABLE COMMAND

--------------------------------------------------------------------------------
SHOW ENABLE

--------------------------------------------------------------------------------
FORMAT: SHOW ENABLE

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
DESCRIPTION:

SHOW ENABLE enables the user to examine the current status of TRIDER processing options that are set or unset using the ENABLE and DISABLE commands.

--------------------------------------------------------------------------------
Messages: None.

--------------------------------------------------------------------------------
Examples:

$ TRIDER<CR>
DTMCREATE module TRIDER of 17:02:12 23-JAN-89

TRIDER> SHOW ENABLE ! examine current option settings<CR>
DIAGNOSTICS ............................................... Off
GRAPHICS .................................................. Off
PME ....................................................... Off
TRIDER>

SHOW FILES COMMAND

--------------------------------------------------------------------------------
SHOW FILES

--------------------------------------------------------------------------------
FORMAT: SHOW FILES

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
DESCRIPTION:

SHOW FILES enables the user to examine the current status of TRIDER input files.

--------------------------------------------------------------------------------
Messages: None.

--------------------------------------------------------------------------------
Examples:

$ TRIDER<CR>
DTMCREATE module TRIDER of 17:02:12 23-JAN-89

TRIDER> SHOW FILES ! examine input file-specs<CR>
Input filename not yet specified.
TRIDER> FILEIN SW100230 ! get input files<CR>
_.DTA file DUA3:[DEMONSTRATION]SW100230_.DTA;6 opened for read
_.NOD file DUA3:[DEMONSTRATION]SW100230_.NOD;6 opened for read
_.DER file DUA3:[DEMONSTRATION]SW100230_.DER;6 opened for write
TRIDER> SHOW FILES ! examine input file-specs<CR>
_.DTA file: DUA3:[DEMONSTRATION]SW100230_.DTA;6
_.NOD file: DUA3:[DEMONSTRATION]SW100230_.NOD;6
TRIDER>

SHOW IMAGINARY COMMAND

--------------------------------------------------------------------------------
SHOW IMAGINARY

--------------------------------------------------------------------------------
FORMAT: SHOW IMAGINARY

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
DESCRIPTION:

SHOW IMAGINARY enables the user to examine the current status of TRIDER imaginary point processing options that are set using the IMAGINARY commands.

--------------------------------------------------------------------------------
Messages: None.

--------------------------------------------------------------------------------
Examples:

$ TRIDER<CR>
DTMCREATE module TRIDER of 17:02:12 23-JAN-89

TRIDER> SHOW IMAGINARY ! examine imaginary points settings<CR>
Imaginary point estimation option ......................... TREND
Relocation proportion for imaginary points ................ 1.00
TRIDER>

SHOW ZLIMITS COMMAND

--------------------------------------------------------------------------------
SHOW ZLIMITS

--------------------------------------------------------------------------------
FORMAT: SHOW ZLIMITS

--------------------------------------------------------------------------------
Command parameters: None.

--------------------------------------------------------------------------------
DESCRIPTION:

SHOW ZLIMITS enables the user to examine the current status of TRIDER Z-limits parameters set using the ZLIMITS commands.

--------------------------------------------------------------------------------
Messages: None.

--------------------------------------------------------------------------------
Examples:

$ TRIDER<CR>
DTMCREATE module TRIDER of 17:02:12 23-JAN-89

TRIDER> SHOW ZLIMITS ! examine ZLIMITS points settings<CR>
No Z-limits will be applied to imaginary point height estimation
TRIDER> ZLIMITS 0.0 450.0<CR>
TRIDER> SHOW ZLIMITS ! examine ZLIMITS points settings<CR>
Imaginary point height estimation lower z-value limit = 0.0
Imaginary point height estimation upper z-value limit = 450.0
TRIDER>

SPAWN COMMAND

--------------------------------------------------------------------------------
SPAWN

--------------------------------------------------------------------------------
FORMAT: SPAWN command-line

--------------------------------------------------------------------------------
Command parameters:

--------------------------------------------------------------------------------
DESCRIPTION:

The SPAWN command enables you to create a subprocess while within TRIDER. When the subprocess terminates control is returned to TRIDER.

--------------------------------------------------------------------------------
Messages:

The following warning messages are specific to the SPAWN command:

*** WARNING *** SPAWN requires a valid DCL command line
*** ERROR *** Unable to spawn command, returning to TRIDER

--------------------------------------------------------------------------------
Examples:


TRIDER> SPAWN DIRECTORY *_.DTA;*<CR>

Directory DUA3:[DTMCREATE.ACCEPTANCE_TESTS]
TEST1_.DTA;1              8/8       18-AUG-1987 07:56  [LSL,TIM]
TEST2_.DTA;2              7/8       18-AUG-1987 17:17  [LSL,TIM]
TEST2_.DTA;1              7/8       18-AUG-1987 17:07  [LSL,TIM]
Total of 3 files, 22/24 blocks.

TRIDER>

WAIT COMMAND

--------------------------------------------------------------------------------
WAIT

--------------------------------------------------------------------------------
FORMAT: WAIT seconds

--------------------------------------------------------------------------------
Command parameters:

--------------------------------------------------------------------------------
DESCRIPTION:

The WAIT command causes processing to be suspended for a specified number of seconds. It is designed for use in software demonstration situations and is of no value in a production flowline.

--------------------------------------------------------------------------------
Messages:

The following warning message is specific to the WAIT command:

*** WARNING *** You must specify the number of seconds to wait

--------------------------------------------------------------------------------
Examples:


TRIDER> WAIT 4.0<CR>
TRIDER>

ZLIMITS COMMAND

--------------------------------------------------------------------------------
ZLIMITS

--------------------------------------------------------------------------------
FORMAT: ZLIMITS real1 real2

--------------------------------------------------------------------------------
COMMAND PARAMETERS:

--------------------------------------------------------------------------------
Description:

The ZLIMITS command enables the user to specify lower and upper ZLIMITS to imaginary point height estimation. If an imaginary point height is calculated which falls outside of the specified limits the height will be truncated to the relevant limit.

By default TRIDER applies no limits to imaginary point height estimation.

It is not necessary to specify the ZLIMITS command if the IMAGINARY FIXED imaginary point height option is used.

IMPORTANT If one of the height modification options was selected in TRIANG using ENABLE MULTIPLYBY, ENABLE TOFEET etc_., you must give the TRIDER ZLIMITS argument values in the target measurement system or height range (ie feet if the TRIANG TOFEET command was specified). Failure to do this may result in flattening of all model relief!

--------------------------------------------------------------------------------
Messages:

The following messages are specific to the ZLIMITS command:

*** ERROR *** You must specify minimum and maximum ZLIMITS arguments For example ZLIMITS 80.0 3000.0

--------------------------------------------------------------------------------
Examples:


TRIDER> SHOW ZLIMITS<CR>
No ZLIMITS will be applied to imaginary point height estimation
TRIDER> ZLIMITS 0.0 800.0<CR>
TRIDER> SHOW ZLIMITS<CR>
Imaginary point height estimation lower z-value limit = 0.0
Imaginary point height estimation upper z-value limit = 800.0
TRIDER>

--------------------------------------------------------------------------------

EXAMPLES

$ TRIDER<CR> DTMCREATE module TRIDER of 15:53:45 26-NOV-87 TRIDER> ENABLE DIAGNOSTICS<CR> TRIDER> FILEIN TST<CR> _.DTA file DATA$DISK:[DTMCREATE.TRIANG]TST_.DTA;1 opened for read _.NOD file DATA$DISK:[DTMCREATE.TRIANG]TST_.NOD;1 opened for read _.DER file DATA$DISK:[DTMCREATE.TRIANG]TST_.DER;1 opened for write TRIDER> GO<CR> +----------------------------------------------------------------+ | | | Setting up memory/random file for neighbours | | | +----------------------------------------------------------------+ +----------------------------------------------------------------+ | | | Calculating slope derivatives | | | +----------------------------------------------------------------+ Partial derivatives estimated for 774 points ELAPSED: 0 00:02:05.51 CPU: 0:00:25.60 BUFIO: 13 DIRIO: 25 FAULTS: 332
_$

$ TRIDER<CR> DTMCREATE module TRIDER of 15:53:45 26-NOV-87 TRIDER> ENABLE DIAGNOSTICS<CR> TRIDER> ZLIMITS 80 500<CR> TRIDER> IMAGINARY SHELLNEIGHBOUR QUADRATIC 0.0<CR> TRIDER> FILEIN QUARRY5<CR> _.DTA file DATA$DISK:[DTMCREATE.TRIANG]QUARRY5_.DTA;1 opened for read _.NOD file DATA$DISK:[DTMCREATE.TRIANG]QUARRY5_.NOD;1 opened for read _.DER file DATA$DISK:[DTMCREATE.TRIANG]QUARRY5_.DER;1 opened for write TRIDER> GO<CR> +----------------------------------------------------------------+ | | | Setting up memory/random file for neighbours | | | +----------------------------------------------------------------+ +----------------------------------------------------------------+ | | | Imaginary point interpolation - collect star neighbours | | | +----------------------------------------------------------------+ 446 imaginary point neighbourhoods determined +----------------------------------------------------------------+ | | | Starting derivative calculation phase | | | +----------------------------------------------------------------+ %TRIDER-W-DERFAIL, derivative estimation failure at X = 2000.02 Y = 70.315 Partial derivatives estimated for 22402 points +----------------------------------------------------------------+ | | | Imaginary point interpolation - interpolation phase | | | +----------------------------------------------------------------+ 446 imaginary points interpolated +----------------------------------------------------------------+ | | | Calculating slope derivatives | | | +----------------------------------------------------------------+ Partial derivatives estimated for 68820 points ELAPSED: 0 00:05:58.79 CPU: 0:04:56.19 BUFIO: 317 DIRIO: 236 FAULTS: 1368 _$

See tridermsg.html generated from TRIDERMSG.RNO.