Laser Model Interface

Reference Manual

AVEVA Solutions Ltd

Disclaimer
Information of a technical nature, and particulars of the product and its use, is given by AVEVA
Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim
any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.
Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or
entity for any actions, claims, loss or damage arising from the use or possession of any information,
particulars, or errors in this publication, or any incorrect use of the product, whatsoever.

Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every
part of it (including source code, object code, any data contained in it, the manual and any other
documentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.
All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained in
this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval
system, or transmitted without the prior written permission of AVEVA Solutions Ltd Where such
permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently
displayed at the beginning of every copy that is made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material
or electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also not
reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the
product described in this publication may be incorporated into any third-party software, product,
machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted by
law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal
prosecution.
The AVEVA products described in this guide are to be installed and operated strictly in accordance with
the terms and conditions of the respective license agreements, and in accordance with the relevant
User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.
First published September 2007
AVEVA Solutions Ltd, and its subsidiaries
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom

Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised
use of the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trade mark rights, or other intellectual property rights in any other product, its name or
logo belongs to its respective owner.

Laser Model Interface Reference Manual

Laser Model Interface Reference Manual

Contents

Page

Laser Model Interface

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Who Should Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
How the Guide is Organised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Product Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Driver Subcommand - Accessing Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Querying Driver Attributes and Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Opening and Accessing Laser Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
Creating an External Geometry Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
Importing Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
Using the Vendors Model Browse Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5

Driver Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5

Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6
Manipulating Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6
Clash Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7

Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A:1

12.0

Laser Model Interface Reference Manual

ii

12.0

Laser Model Interface Reference Manual

Introduction

Introduction
The Laser Model Interface (LMI) is a separately licenced module within the AVEVA Plant
DESIGN AVEVA Marine Outfitting products. Used in conjunction with a supported Laser
Model server application, it allows:

1.1

the display of Laser Models within PDMS, combined with normal PDMS geometry

clashing calculations between Laser Models and PDMS geometry, and display of the
resulting clashing regions

picking of points within Laser Models, and creating tie-in points between Laser
Models and geometry

implementation of third party defined extended functionality.

Who Should Use This Guide

This guide is intended for end users of the Laser Model Interface. It describes the PDMS
commands used for accessing Laser Model functionality. It is also intended for IT staff who
are implementing extended Laser Model functionality within PDMS, using PML
programming.
Note: The licensing of the Laser Model Interface product is managed by AVEVAs Flexman
security system. A separate licence key must be obtained from AVEVA for the Laser
Model product.

1.2

How the Guide is Organised

Commands describes the new commands within the LMI module, and extensions to existing
commands for handling Laser Models.

1.3

Product Compatibility
In addition to the Windows operating system, other AVEVA and non-AVEVA products are
required for the Reference Manual of Laser Model functionality.
For all users:

1.4

PDMS

A supported Laser Model package.

Installation
For an introductory guide and installation information, refer to the appropriate Laser Model
Server Application.

1:1

12.0

Laser Model Interface Reference Manual

Introduction

1:2

12.0

Laser Model Interface Reference Manual

Commands

Commands
All Laser Model commands use the command verb LMI. The following sections detail the
various sub-commands available.

2.1

Driver Subcommand - Accessing Drivers

Several LMI commands use the DRIVER subcommand, for example:

LMI DRIVER abc|c:\abc\prog.dll|login=user QUERY APIVERSION

The string following the driver keyword - the vendors identification string - contains between
one and three fields separated by bar (|) characters. The fields are, i) a tag string, ii) the full
path to the driver dynamic link library (DLL) file, and iii) the drivers connect string. The
drivers connect string can be any string, as required by the vendor company to connect to
their driver, or it can be omitted if the driver requires no special connection information.
Once one LMI DRIVER command has been used, the string can be shortened to just the tag
for all subsequent commands, for example:

LMI DRIVER abc QUERY DRIVERVERSION

Or, the DRIVER subcommand can be omitted completely, in which case the command is
directed to the most recently referenced driver:

LMI QUERY DRIVERVERSION

2.2

Querying Driver Attributes and Capabilities

[VAR {var}] LMI [DRI/VER {string}]

Q/UERY {APIVER/SION |
DRIVERVER/SION |
BAN/NER |
LAST ERR/ORMESSAGE |
MAX/IMUM {MOD/ELS |
VIEWS |
REGIONSOFINT/EREST |
HIGHL/IGHTREGIONS |
CLASHVOL/UMES |
VIEWQ/UALITY {IN/SIDE | OUT/SIDE} |
VIEWP/ORT {W/IDTH | H/EIGHT}}
SUPP/ORT {FBCLIP/PING |
RENDERFAST |
LOWRESEVERYWHERE |
TESTVOLUMEFAST |
TESTGEOMETRYEXACT}}

2:1

12.0

Laser Model Interface Reference Manual

Commands

{var}
{string}

PDMS variable
driver name and connection details in the following format,
enclosed in single quotes:

{name}[|{path to dll}[|{vendors connect

string}]]
This command connects to, and queries attributes of, the named driver. The result string is
returned in variable {var}, or if this is omitted, output in the PDMS command window.
The DRIVER {string} subcommand should be included the first time an LMI command is
used for a particular driver, but need not be repeated for subsequent calls to the same
driver. See Driver Subcommand - Accessing Drivers.
The available attributes are:

APIVERSION
DRIVERVERSION
BANNER
LAST ERRORMESSAGE

The version string for the LMI.

MAXIMUM MODELS

The maximum number of models that can be opened

simultaneously (range 1 - unlimited).

MAXIMUM VIEWS

The maximum number of views that can be rendered

efficiently (range 1 - unlimited). Note: since calls to render
views are made sequentially, any number of views can be
rendered, however the rendered images are generally
cached by the vendor software for efficiency, and this
command returns the maximum number of views for which
this caching is supported.

MAXIMUM
REGIONSOFINTEREST

The maximum number of regions of interest that the driver

supports (range 0 - unlimited). Regions of interest define
areas where a higher view quality may be used.

MAXIMUM
HIGHLIGHTREGIONS
MAXIMUM
CLASHVOLUMES
MAXIMUM
VIEWQUALITY
MAXIMUM VIEWPORT
WIDTH / HEIGHT
SUPPORT
FBCLIPPING
SUPPORT
RENDERFAST
SUPPORT
LOWRESEVERYWHERE

The maximum number of highlighted regions that the driver

can support (range 0 - unlimited).

The version string for the driver.

The driver manufacturers banner text.
The last error message (or an empty string if no error has
occurred).

The maximum number of highlighted clash volumes that the

driver can support (range 0 - unlimited).
The maximum view quality that the driver supports INSIDE
or OUTSIDE the regions of interest (range 1 or higher).
The maximum viewport width / height that the driver
supports (range 1 - unlimited).
Whether the driver supports front and back clipping planes
(true or false).
Whether the driver supports fast rendering (true or false).
Whether the driver supports rendering in low resolution
everywhere mode (true or false).

2:2

12.0

Laser Model Interface Reference Manual

Commands

SUPPORT
TESTVOLUMEFAST
SUPPORT
TESTGEOMETRYEXACT

2.3

Whether the driver supports a fast (but less accurate)

version of volume testing for clashing.
Whether the driver supports testing geometry for clashing at
the exact check level.

Opening and Accessing Laser Models

Laser models are represented in the PDMS DESI database by XGEOM (external geometry)
elements. The XGEOM element records the reference strings to identify a particular laser
model and the relevant external laser model server application which manages access to
the detailed point cloud data.
The XGEOM can be used naturally in many existing PDMS commands and GUI
interactions, for example, to add or remove point cloud models in the display list and other
lists. There are also some laser model specific commands that apply to XGEOMs. These
are listed in Manipulating Views.
Below the XGEOM, PDMS also builds up a coarse spatial occupancy map to give PDMS
functions some guidance about the distribution of points in the point cloud model. This map
is used, for example, to determine volumetric limits for the laser model and to support the
internal PDMS spatial map used during clash calculations. This map is built up as a
hierarchy of XCLTN, XCELS and XCELL elements below the XGEOM. It is not normally
necessary for users to create or access these elements directly.
There are 2 ways to create XGEOMs and the associated spatial occupancy map. You can
use the standard PDMS NEW command then generate the spatial occupancy map by
command - this approach is covered in Creating an External Geometry Element.
Alternatively you can use the laser model specific import command which will create the
XGEOM and the spatial occupancy map in one go - this is described in Importing Models
and Using the Vendors Model Browse Dialog.

2.3.1

Creating an External Geometry Element

This command creates a new XGEOM element at the current geometry level, and makes it
the current element. The current geometry level must be at or below a ZONE. The vendors
identification string can optionally be supplied (see note below), as can the model
identification string. These attributes can also be supplied using separate VENID and
MODID commands after the XGEOM has been created.
The vendor identification string should identify the Laser Model server application where the
actual point cloud data resides. The model identification string should identify a model within
the vendors model database.

2:3

12.0

Laser Model Interface Reference Manual

Commands

Once the XGEOM has been created and the attributes set, PDMS adds the XGEOM to the
display. This happens automatically, both when the full form of the command above is used,
and when the attributes are set individually. (It also happens if the value of an attribute is
changed.) At this point, the values of the attributes are checked for validity, and if valid, the
XGEOM is made visible and the display is updated. If any attribute(s) are invalid or missing,
an error condition results, and the XGEOM is not added to the display.
Note: The vendor identification string format is described in Driver Subcommand Accessing Drivers. The VENID can be provided as either the long form of the string,
specifying the path to the vendor DLL and the vendors connect string, or the short
form that includes just the tag. The former provides all the information necessary to
open the Laser Model and add the XGEOM to the display. However, it suffers the
drawback that any change to the DLL path (which may happen for example when
accessing the database from a different node) or the vendor connect string (which
might for example contain embedded username / password information) will cause
the load to fail and the XGEOM not to be added to the display. For these reasons,
the short form of the VENID string is preferred. Note, however, that an XGEOM with
the short form VENID string can only be added to the display after another LMI
DRIVER {string} command has been used with the long form string, thus setting
the association between the tag and the other parameters for the session.
Once an XGEOM element has been created by the NEW command, the spatial occupancy
map can be built using the command:

LMI REMAP
The XGEOM should be the current element when this command is used.
LMI REMAP can be re-applied if the spatial occupancy map becomes out of date, for
example if the laser model is extended with extra scans. However users of Clash Manager
should be aware that identification of clash details with the laser model relies on the
persistence of the Dabacon REFNO of the clashing XCELL elements. Re-application of the
REMAP command will re-assign REFNOs and hence any related clash history will be
broken.

2.3.2

Importing Models

LMI [DRI/VER {string}] IMPORT {mname}

{string}

driver name and connection details in the following format, enclosed in

single quotes:{name} string}]]

{name}[|{path to dll}[|{vendors connect string}]]

{mname}

model name enclosed in single quotes

This command creates a new XGEOM element to represent the selected model, and opens
the model in the vendor driver.
The current element must be at or below a ZONE: if at a ZONE, the XGEOM will be created
as the first element in the list; if below a ZONE the XGEOM will be created as the next
element in the ZONE list. The new XGEOM becomes the current element.

2:4

12.0

Laser Model Interface Reference Manual

Commands

After creating the XGEOM, the following actions occur:

2.3.3

the XGEOMs VENID attribute is set to {string}

the XGEOMs MODID attribute is set to the vendor defined model name (i.e. the name
necessary to access the model in the vendors database without using the browse
function)

the XGEOMs DATIM attribute is set to the current time

the model is opened in the vendor driver

the spatial map is calculated, and stored below the XGEOM (as XCLTN, XCELS and
XCELL elements).

Using the Vendors Model Browse Dialog

LMI [DRI/VER {string}] IMPORT BRO/WSE

{string}

driver name and connection details in the following format, enclosed in

single quotes:

{name}[|{path to dll}[|{vendors connect string}]]

The BROWSE form of the IMPORT command (if the vendor supports it) causes the
vendors model browse dialog to be displayed, and allows the user to select a model for
import. Once the model is selected and the dialog closed, the import action is exactly the
same as the IMPORT {mname} form of the command described in the section above.
Note: Once the model has been imported with BROWSE, the MODID attribute can be
queried to discover the model name.

2.4

Driver Extensions

[VAR {var}] LMI [DRI/VER {string}] EXT/ENSION {command}

{var}
{string}

PDMS variable
driver name and connection details in the following format, enclosed in
single quotes:

{name}[|{path to dll}[|{vendors connect string}]]

{command}

command string enclosed in single quotes

This command executes the driver specific command in the named driver. The result string
(if any) is returned in variable {var}, or if this is omitted, output in the PDMS command
window.

2:5

12.0

Laser Model Interface Reference Manual

Commands

2.5

Licensing

[VAR {var}] LMI LIC/ENCED

{var}

PDMS variable

This command retrieves the licence status of the LMI module. The result string is returned in
variable {var}, or if omitted, output in the PDMS command window.

2.6

Manipulating Views
This section is provisional, as the syntax and functionality of the LMI VIEW commands has
not yet been finalised. It is possible that these commands may change, or be completely
removed at a later date, as views are not LMI specific, and an existing syntax exists within
PML to access and manipulate views and view parameters.

LMI VIEW DETAILS

This command outputs a summary of the LMI parameters associated with the selected view
(or all views, if none selected).

LMI VIEW SET VIEWQ/UALITY {in} {out}

{in}
{out}

the view quality inside the regions of interest (%)

the view quality outside the regions of interest (%)

This command sets the view quality inside / outside the regions of interest within the view
specified (or all views if none specified). The % quality specified is translated as near as
possible to a view quality supported by each vendors software. Where a precise match is
not possible, the view quality is rounded up.
LMI VIEW ADD {type}
X/LENGTH {len} Y/LENGTH {len} Z/LENGTH {len}
AT E/AST {pos} N/ORTH {pos} U/P {pos}
LMI VIEW REM/OVE {type}
VAR {var} LMI VIEW {type} {COU/NT | {n}}

{view}
{type}

view number
one of:
REGIONSOFI/NTEREST, HIGHL/IGHTREGIONS

2:6

12.0

Laser Model Interface Reference Manual

Commands

{len}
{pos}
{n}

a length value
a position value
index of the item in the list of {type} items

These commands create, delete and query regions of the type specified, within the view
specified (or all views if none specified).
The ADD command adds a region, preserving any regions of the same type already
present. The REMOVE command removes all regions of the type specified.
The COUNT subcommand returns the number of regions of the type specified. The {n}
subcommand returns the bounds (volume) of the n-th region.

2.7

Clash Testing
This section provides addition options for detecting and displaying clashes between PDMS
primitives and the external laser model. Before the XGEOM element can be clashed the
spatial occupancy map must be up to date, once the map has been built there generally is
no need to regenerate it.
DESCLASH LMI [TEST {option} | [DISP/LAY {display}] EXIT
{option} one of:
CELLS, EXACT/GEOMETRY
{display} one of:
CELLS, EXPAND/CELLS {off}, TIGHTBOXES, EXACT/GEOMETRY
The TEST command determines the level the clash test will take place, if CELLS the
primitive will test for clash with the spatial occupancy map only (default). Using the
EXACTGEOMETRY option the primitive will be clashed against the spatial occupancy map,
if there is a clash then the primitive will be clashed against the laser external model. The use
of EXACTGEOMETRY clash will produce a more accurate result however it will take longer
to process the data.
The DISPLAY command determines the manner in which the graphical feedback of the
clash will be displayed. By default the CELLS display option will be used: if there is a clash
then all points within the spatial occupancy cell will be highlighted as clashing. The
EXPANDCELLS option will highlight points within the spatial occupancy cell expanded by
the additional offset as clashing. The TIGHTBOXES option will highlight points within the
overlap between the spatial occupancy cell and the containment box for the PDMS primitive.
The EXACTGEOMETRY option will only highlight the points of the laser model that clash
with the primitive itself: as a result the clash display will normally be obscured by the
primitive. The use of the EXACTGEOMETRY display option may reduce the performance of
the display (or initial update of the display).

2:7

12.0

Laser Model Interface Reference Manual

Commands

2:8

12.0

Laser Model Interface Reference Manual

Quick Reference

Quick Reference

NEW XGEOM [/{name}] [VENID {id}] [MODID {mid}]

LMI [DRI/VER {string}] IMPORT {BRO/WSE | {mname}}
LMI REMAP
[VAR {var}] LMI [DRI/VER {string}]
Q/UERY {APIVER/SION |
DRIVERVER/SION |
BAN/NER |
LAST ERR/ORMESSAGE |
MAX/IMUM {MOD/ELS |
VIEWS |
REGIONSOFINT/EREST |
HIGHL/IGHTREGIONS |
CLASHVOL/UMES |
VIEWQ/UALITY {IN/SIDE | OUT/SIDE} |
VIEWP/ORT {W/IDTH | H/EIGHT}}
SUPP/ORT {FBCLIP/PING |
RENDERFAST |
LOWRESEVERYWHERE |
TESTVOLUMEFAST |
TESTGEOMETRYEXACT}}
[VAR {var}] LMI LIC/ENCED
[VAR {var}] LMI [DRI/VER {string}] EXT/ENSION {command}
LMI VIEW DETAILS
LMI VIEW SET VIEWQ/UALITY {in} {out}
LMI VIEW ADD {type}
X/LENGTH {len} Y/LENGTH {len} Z/LENGTH {len}
AT E/AST {pos} N/ORTH {pos} U/P {pos}
LMI VIEW REM/OVE {type}
VAR {var} LMI VIEW {type} {COU/NT | {idx}}

A:1

12.0

Laser Model Interface Reference Manual

Quick Reference

A:2

12.0

Laser Model Interface Reference Manual

Index

Symbols

DRIVERVERSION . . . . . . . . . . . . . . . . . 2:2

{in} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6
{len} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7
{n} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7
{out} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6
{pos} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7
{type} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6
{view} . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6

E
EXACTGEOMETRY . . . . . . . . . . . . . . . . 2:7
EXPANDCELLS . . . . . . . . . . . . . . . . . . . 2:7
External Geometry Element . . . . . . . . . . 2:3

FBCLIPPING . . . . . . . . . . . . . . . . . . . . . 2:2
Flexman . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Accessing Laser Models . . . . . . . . . . . . . 2:3

ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7
APIVERSION . . . . . . . . . . . . . . . . . . . . . 2:2

HIGHLIGHTREGIONS . . . . . . . . . . . . . . 2:2

B
BANNER . . . . . . . . . . . . . . . . . . . . . . . . . 2:2

C
CELLS . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7
Clash Testing . . . . . . . . . . . . . . . . . . . . . 2:7
CLASHVOLUMES . . . . . . . . . . . . . . . . . 2:2
Commands . . . . . . . . . . . . . . . . . . . . . . . 2:1
COUNT . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7

D
DESI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . 2:7
Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Driver Attributes . . . . . . . . . . . . . . . . . . . 2:1
Driver Extensions . . . . . . . . . . . . . . . . . . 2:5

I
Importing Models . . . . . . . . . . . . . . . . . .
Installation . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Introduction#_Introduction . . . . . . . . . . .

2:4
1:1
1:1
1:1

L
LAST ERRORMESSAGE . . . . . . . . . . .
Licensing . . . . . . . . . . . . . . . . . . . . . . . .
LMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOWRESEVERYWHERE . . . . . . . . . . .

2:2
2:6
2:1
2:2

M
Manipulating Views . . . . . . . . . . . . . . . . 2:6
MAXIMUM MODELS . . . . . . . . . . . . . . . 2:2

Index page 1

12.0

Laser Model Interface Reference Manual

MAXIMUM VIEWPORT . . . . . . . . . . . . . 2:2

MAXIMUM VIEWS . . . . . . . . . . . . . . . . . 2:2
MODID . . . . . . . . . . . . . . . . . . . . . . 2:3, 2:5

O
Opening . . . . . . . . . . . . . . . . . . . . . . . . . 2:3

R
REGIONSOFINTEREST . . . . . . . . . . . . . 2:2
REMAP . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
RENDERFAST . . . . . . . . . . . . . . . . . . . . 2:2

T
TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7
TESTGEOMETRYEXACT . . . . . . . . . . . 2:3
TESTVOLUMEFAST . . . . . . . . . . . . . . . 2:3
TIGHTBOXES . . . . . . . . . . . . . . . . . . . . . 2:7

V
VENID . . . . . . . . . . . . . . . . . . . . . . . 2:3, 2:4
VIEWQUALITY . . . . . . . . . . . . . . . . . . . . 2:2

X
XCELL . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
XCELS . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
XCLTN . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
XGEOM . . . . . . . . . . . . . . . . . . . . . . 2:3, 2:7

Index page 2

12.0