3d estimation

3d estimation performs parameter estimation using kriging and other methods to map 3D analytical data onto volumetric grids defined by the limits of the data set, or by the convex hull, rectilinear, or finite-difference grid extents of a geologic system modeled by gridding and horizons. 3d estimation provides several convenient options for pre- and post-processing the input parameter values, and allows the user to consider anisotropy in the medium containing the property.

3d estimation also has the ability to create uniform fields, and the ability to choose which data components you want to include in the output. There are a couple significant requirements for uniform fields. First, there cannot be geologic input (otherwise the cells could not be rectangular blocks). Second, Adaptive_Gridding must be turned off (otherwise the connectivity is not implicit).

Module Input Ports

• Filename [String / minor] Allows the sharing of file names between similar modules.
• Input Geologic Field [Field] Accepts a data field from gridding and horizons to krige data into geologic layers.
• Input External Grid [Field / minor] Allows the user to import a previously created grid. All data will be kriged to this grid.
• Input External Data [Field / minor] Allows the user to import a field contain data. This data will be kriged to the grid instead of using file data.

Module Output Ports

• Filename [String / minor] Allows the sharing of file names between similar modules.
• Output Field [Field] Outputs a 3D data field which can be input to any of the Subsetting and Processing modules.
• Status Information [String / minor] Outputs a string containing module parameters. This is useful for connection to write evs field to document the settings used to create a grid.
• Uncertainty Sphere [Renderable / minor] Outputs a sphere to the viewer. This sphere represents the location of maximum uncertainty.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Grid Settings: control the grid type, position and resolution
• Data Processing: controls clipping, processing (Log) and clamping of input data and kriged outputs.
• Time Settings: controls how the module deals with time domain data
• Krig Settings: control the estimation methods
• Data To Export: specify which data is included in the output
• Display Settings: applies to maximum uncertainty sphere
• Drill Guide: parameters association with DrillGuide computations for analytically guided site assessment

Variogram Options:

There are three variogram options:

1. Spherical: Our default and recommended choice for most applications
2. Exponential: Generally gives similar results to Spherical and may be superior for some datasets
3. Gaussian: Notoriously unstable, but can “smooth” your data with an appropriate nugget.

I specifically want to discuss the pros and cons of Gaussian. Without a nugget term, Gaussian is generally unusable. When using Autofit, our expert system will apply a modest nugget (~1% of sill) to maintain stability. If you’re committed to experimenting with Gaussian, it is recommended that you experiment with the nugget term after EVS computes the Range and Sill. Below are some things to look for:

• If you find that Gaussian kriging is overshooting the plume in various directions, your nugget is likely too small.
• However, if the plume looks overly smooth and is too far from honoring your data, your nugget is likely too big.

The “Power Factor” is only used for exponential or gaussian variograms. The default value of 3 is the most common value used for exponential in most software. For gaussian, 2 is most common, though anything from 0.1->3 is typically acceptable. This is effectively the “a” term described here: https://en.wikipedia.org/wiki/Variogram#Variogram_models

Advanced Variography Options:

It is far beyond the scope of our Help documentation to include an advanced Geostatistics course. The terminology and variogram plotting style that we use is industry standard and we do so because we will not provide detailed technical support nor complete documentation on these features, which would effectively require a geostatistics textbook, in our help.

However, there is an Advanced Training Video on how to take advantage of the complex, directional anisotropic variography capabilities in 3d estimation (which applies equally well to lithologic modeling). This class is focused on the mechanics of how to employ and refine the variogram anisotropy with respect to your data and the physics of your project such as contaminated sediments in a river bottom. The variogram is displayed as an ellipsoid which can be distorted to represent the Primary and Secondary anisotropies and rotated to represent the Heading, Dip and Roll. Overall scale and translation are also provided as additional visual aids to compare the variogram to the data, though these do not affect the actual variogram.

We are not hiding this capability from you as the Anisotropic Variography Study folder of Earth Volumetric Studio Projects contains a number of sample applications which demonstrate exactly what is described above. However, we assure you that understanding how to apply this to your own projects will be quite daunting and really does require a number of prerequisites:

• A thorough explanation of these complex applications
• An understanding of all of the variogram parameters and their impact on the estimation process on both theoretical datasets as well as real-world datasets.

This 3 hour course addresses these issues in detail.

2d estimation

2d estimation performs parameter estimation using kriging and other methods to map 2D analytical data onto surface grids defined by the limits of the data set as rectilinear or convex hull extents of the input data.

Its Adaptive Griddingfurther subdivides individual elements to place a “kriged” node at the location of each input data sample. This guarantees that the output will accurately reflect the input at all measured locations (i.e. the maximum in the output will be the maximum of the input).

The DrillGuide functionality produces a new input data file with a synthetic boring at the location of maximum uncertainty calculated from the previous kriging estimates, which can then be rerun to find the next area of highest uncertainty. The naming of the “DrillGuide^©” file which is created when 2d estimation is run with all types of analyte (e.g. chemistry) files ends in apdv1, apdv2, apdv3, etc. the output file name will be .apdv2, apdv3, apdv4…. There are no limits to the number of cycles that may be run.

The use of 2d estimation to perform analytically guided site assessment is covered in detail in Workbook 2: DrillGuide^© Analytically Guided Site Assessment.

This process can be continued as many times as desired to define the number and placement of additional borings that are needed to reduce the maximum uncertainty in the modeled domain to a user specified level. The features of 2d estimation make it particularly useful for optimizing the benefits obtained from environmental sampling or ore drilling programs. 2d estimation also provides some special data processing options that are unique to it, which allow it to extract 2-dimensional data sets from input data files that contain three-dimensional data. This functionality allows it to use the same .apdv files as all of the other EVS input and kriging modules, and allows detailed analyses of property characteristics along 2-dimensional planes through the data set. 2d estimation also provides the user with options to magnify or distort the resulting grid by the kriged value of the property at each grid node. 2d estimation also allows the user to automatically clamp the data distribution to a specified level along a boundary that can be offset from the convex hull of the data domain by a user defined amount.

Module Input Ports

• Input External Grid [Field / minor] Allows the user to import a previously created grid. All data will be kriged to this grid.
• Input External Data [Field / minor] Allows the user to import a field contain data. This data will be kriged to the grid instead of using file data.
• Filename [String / minor] Allows the sharing of file names between similar modules.

Module Output Ports

• Output Field [Field] Outputs a 3D data field which can be input to any of the Subsetting and Processing modules which have the same color port
• Filename [String / minor] Allows the sharing of file names between similar modules.
• Status Information [String / minor] Outputs a string containing module parameters. This is useful for connection to write evs field to document the settings used to create a grid.
• Surface [Renderable] Outputs the kriged surface to the viewer

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Grid Settings: control the grid type, position and resolution
• Data Processing: controls clipping, processing (Log) and clamping of input data and kriged outputs.
• Time Settings: controls how the module deals with time domain data
• Krig Settings: control the estimation methods
• Data To Export: specify which data is included in the output
• Display Settings: applies to maximum uncertainty sphere
• Drill Guide: parameters association with DrillGuide computations for analytically guided site assessment

Variogram Options:

There are three variogram options:

1. Spherical: Our default and recommended choice for most applications
2. Exponential: Generally gives similar results to Spherical and may be superior for some datasets
3. Gaussian: Notoriously unstable, but can “smooth” your data with an appropriate nugget.

I specifically want to discuss the pros and cons of Gaussian. Without a nugget term, Gaussian is generally unusable. When using Autofit, our expert system will apply a modest nugget (~1% of sill) to maintain stability. If you’re committed to experimenting with Gaussian, it is recommended that you experiment with the nugget term after EVS computes the Range and Sill. Below are some things to look for:

• If you find that Gaussian kriging is overshooting the plume in various directions, your nugget is likely too small.
• However, if the plume looks overly smooth and is too far from honoring your data, your nugget is likely too big.

gridding and horizons

The gridding and horizons module uses data files containing geologic horizons or surfaces (usually .geo, .gmf and other ctech formats containing surfaces) to model the surfaces bounding geologic layers that will provide the framework for three-dimensional geologic modeling and parameter estimation. Conversion of scattered points to surfaces uses kriging (default) or spline (previously in the spline_geology module), IDW or nearest neighbor algorithms.

gridding and horizons creates a 2D grid containing one or more elevations at each node. Each elevation represents a geologic surface at that point in space. The output of gridding and horizons is a data field that can be sent to several modules (e.g. 3d estimation, horizons to 3d, horizons_to_3d_structured, surfaces from horizons, etc.)

Those modules which create volumetric models convert the quadrilateral elements into layers of hexahedral (8-node brick) elements. The output of gridding and horizons can also be sent to the surface from horizons(s) module(s) which allow visualization of the individual layers of quadrilateral elements (the surfaces) that comprise the surfaces.

gridding and horizons has the capability to produce layer surfaces within the convex hull of the data domain, within a rectilinear domain with equally spaced nodes, or within a rectilinear domain with specified cell sizes such as a finite-difference model grid. The finite-difference gridding capabilities allows the user to visually design a grid with variable spacing, and then krige the geologic layer elevations directly to the finite difference grid nodes. gridding and horizons also provides geologic surface definitions to the post_samples module to allow exploding of boreholes and samples by geologic layer.

Note: gridding and horizons has the ability to read .apdv, .aidv and .pgf file to create a single geologic layer model. This was not done as a preferred alternative to creating/representing your valid site geology. However, most sites have some ground surface topography variation. If 3d estimation is used without geology input, the resulting output will have flat top and bottom surfaces. The flat top surface may be below or above the actual ground surface at various locations. This can result in plume volumes that are inaccurate.

When a .apdv or .pgf is read by gridding and horizons the files are interpreted as geology as follows:

1. If Top of boring elevations are provided in the file, these values are used to create the ground surface.

2. If Top of boring elevations are not provide in the file, the elevations of the highest sample in each boring are used to create the ground surface.

3. The bottom surface is created as a flat surface slightly below the lowest sample in the file. The elevation of the surface is computed by taking the lowest sample and subtracting 5% of the total z-extent of the samples.

When reading these files, you will get a single layer which goes to either the Top column (if it exists) otherwise, the top sample in each boring, and 5% below the lowest sample in the file (flat bottom). This allows you to create a convex hull around data without having geology info. It also provide a topographic top surfaces if your analyte (e.g. chemistry) or PGF file has Tops (grounds surface elevations). Also nice for doing indicator kriging (since a single, well-defined pgf can give you an entire indicator model now). Be aware that if Top is specified, but all values are exactly 0.0, the top sample elevation for each boring will be used.

Module Input Ports

• Filename [String / minor] Receives the filename from other modules.

Module Output Ports

• Geologic legend Information [Geology legend] Supplies the geologic material information for the legend module.
• Output Geologic Field [Field] Can be connected to the 3d estimation, 3D_Geology Map, and surface from horizons(s) modules.
• Filename [String / minor] Outputs a string containing the file name and path. This can be connected to other modules to share files.
• Status Information [String / minor] Outputs a string containing module parameters. This is useful for connection to write evs field to document the settings used to create a grid.
• Geology Export Output [Vistas Data / minor] Provides input to the export horizons to vistas and other modules which create raster output.
• Grid [Renderable / minor] Outputs the geometry of 2D grid.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Grid Settings: control the grid type, position and resolution
• Krig Settings: control the estimation methods
• Computational Settings: define computational surfaces included in the output. This allows a single surface file to define a layer specified by elevation or depth.

analytical realization

The analytical realization module is one of three similar modules (the other two are lithologic realization and stratigraphic_realization), which allows you to very quickly generate statistical realizations of your 2D and 3D kriged models based upon C Tech’s Proprietary Extended Gaussian Geostatistical Simulation (GGS) technology, which we refer to as Fast Geostatistical Realizations^^®^ or FGR^^®^. Our extensions to GGS allow you to:

• Create realizations very rapidly
• Exercise greater control over the frequency and magnitude of noise typical in GGS.
• Control deviation magnitudes from the nominal kriged prediction based on a Min Max Confidence Equivalent.
  • Deviations are the absolute value of the changes to the analytical prediction (in user units)
• Apply Simple or Advanced Anisotropy control over 2D or 3D wavelengths

C Tech’s FGR^^®^ creates more plausible cases (realizations) which allow the Nominal concentrations to deviate from the peak of the bell curve (equal probability of being an under-prediction as an over-prediction) by the same user defined Confidence. However, FGR allows the deviations to be both positive (max) and negative (min), and to fluctuate in a more realistic randomized manner.

Module Input Ports

• Realization [Special Field] Accepts outputs from 3d estimation and krig_2d to allow for EGGS models to be created

Module Output Ports

• Output Field [Field] Outputs the subsetting level
• Deviations Field [Field] Outputs the deviations from the nominal kriged model

Important Parameters

There are several parameters which affect the realizations. A brief description of each follows:

• Randomness Generator Type
  • There are four types, each of which create a different 2D/3D random distribution
• Anisotropy Mode
  • Two options here are Simple or Advanced. These are equivalent to the variogram settings in 3d estimation or krig_2d
• Seed
  • The “Seed” is used in the random number generator, and makes it reproducible.
  • Unique seeds create unique realizations
• Wavelength
  • The 2D or 3D random distribution is governed by a mean wavelength that determines the apparent frequency of deviations from the nominal kriged result.
  • Wavelength is in your project coordinates (e.g. meters or feet)
  • Longer wavelengths create smoother realizations
  • Shorter wavelengths create more “noisy” variations in the realizations
  • Very short wavelengths will give results more similar to GGS (aka Sequential Gaussian Simulations)
• Min Max Confidence Equivalent
  • This parameter determines the magnitude of the deviations.
  • Values close to 50% result in outputs that deviate very little from the nominal kriged result.
    • (we do not allow values below 51% for algorithm stability reasons)
  • Values at or approaching 99.99% will result in the greatest (4 sigma) variations (more similar to GGS)

stratigraphic realization

The stratigraphic realization module is one of three similar modules (the other two are analytical_realization and lithologic realization), which allows you to very quickly generate statistical realizations of your stratigraphic horizons based uponC Tech’s Proprietary Extended Gaussian Geostatistical Simulation (GGS), which we refer to as Fast Geostatistical Realizations^^®^ or FGR^^®^. Our extensions to GGS allow you to:

• Create realizations rapidly
• Exercise greater control over the frequency and magnitude of noise typical in GGS.
• Control deviation magnitudes from the nominal kriged prediction based on a Min Max Confidence Equivalent.
  • Deviations are the absolute value of the changes to surface elevations for each stratigraphic horizon.
• Apply Simple or Advanced Anisotropy control over 2D wavelengths
• For stratigraphic realizations only: we support Natural Neighbor as well as kriging for the input model.

Module Input Ports

• Realization [Special Field] Accepts outputs from gridding and horizons to allow for FGR^^®^ models to be created

Module Output Ports

• Output Field [Field] Outputs the subsetting level
• Deviations Field [Field] Outputs the deviations from the nominal kriged model

Important Parameters

There are several parameters which affect the realizations. A brief description of each follows:

• Randomness Generator Type
  • There are four types, each of which create a different 2D/3D random distribution
• Anisotropy Mode
  • Two options here are Simple or Advanced. These are equivalent to the variogram settings in gridding and horizons
• Seed
  • The “Seed” is used in the random number generator, and makes it reproducible.
  • Unique seeds create unique realizations
• Wavelength
  • The 2D or 3D random distribution is governed by a mean wavelength that determines the apparent frequency of deviations from the nominal kriged (or Natural Neighbor) result.
  • Wavelength is in your project coordinates (e.g. meters or feet)
  • Longer wavelengths create smoother realizations
  • Shorter wavelengths create more “noisy” variations in the realizations
  • Very short wavelengths will give results more similar to GGS (aka Sequential Gaussian Simulations)
• Min Max Confidence Equivalent
  • This parameter determines the magnitude of the deviations.
  • Values close to 50% result in outputs that deviate very little from the nominal kriged (or Natural Neighbor) result.
    • (we do not allow values below 51% for algorithm stability reasons)
  • Values at or approaching 99.99% will result in the greatest (4 sigma) variations (more similar to GGS)

lithologic realization

The lithologic realization module is one of three similar modules (the other two are analytical_realization and stratigraphic_realization), which allows you to very quickly generate statistical realizations of your 2D and 3D lithologic models based upon C Tech’s Proprietary Extended Gaussian Geostatistical Simulation (GGS), which we refer to as Fast Geostatistical Realizations^^®^ or FGR^^®^. Our extensions to GGS allow you to:

• Create realizations rapidly:
  • Though indicator_realizations are the slowest of the three because:
  • The material probabilities must be additionally processed to assign materials
  • When Smooth option is on, this process often takes nearly as long as the original kriging
• Exercise greater control over the frequency and magnitude of visual noise typical of GGS.
• Control deviation magnitudes from the nominal kriged probability prediction based on a Min Max Confidence Equivalent.
  • Deviations are the absolute value of the changes to each material’s probability
• Apply Simple or Advanced Anisotropy control over 2D or 3D wavelengths

Module Input Ports

• Realization [Special Field] Accepts outputs from 3d estimation and krig_2d to allow for EGGS models to be created

Module Output Ports

• Output Field [Field] Outputs the subsetting level
• Deviations Field [Field] Outputs the deviations from the nominal kriged probabilities

Important Parameters

There are several parameters which affect the realizations. A brief description of each follows:

• Randomness Generator Type
  • There are four types, each of which create a different 2D/3D random distribution
• Anisotropy Mode
  • Two options here are Simple or Advanced. These are equivalent to the variogram settings in lithologic modeling
• Seed
  • The “Seed” is used in the random number generator, and makes it reproducible.
  • Unique seeds create unique realizations
• Wavelength
  • The 2D or 3D random distribution is governed by a mean wavelength that determines the apparent frequency of deviations from the nominal kriged probabilities results.
  • Wavelength is in your project coordinates (e.g. meters or feet)
  • Longer wavelengths create smoother realizations
  • Shorter wavelengths create more “noisy” variations in the realizations
  • Very short wavelengths will give results more similar to GGS (aka Sequential Gaussian Simulations)
• Min Max Confidence Equivalent
  • This parameter determines the magnitude of the deviations.
  • Values close to 50% result in outputs that deviate very little from the nominal kriged probabilities results.
    • (we do not allow values below 51% for algorithm stability reasons)
  • Values at or approaching 99.99% will result in the greatest (4 sigma) variations (more similar to GGS)

Lithologic assessment provides a way to determine the quality of a lithologic model on an individual material basis. The concept and procedure to do this is:

• Select the material to be assessed (Basalt shown below)

• Choose a Min Max Confidence Equivalent value (95% shown below)

  • A 50% confidence will result in the Min or Max being equal to the nominal model
  • High confidence values (90+%) will show greater difference from nominal

• Select the Direction (Max or Min)

• Choose the data to be exported

Module Input Ports

• Realization [Special Field] Accepts output from lithologic modeling

Module Output Ports

• Output Field [Field] Outputs the subsetting level
• Deviations Field [Field] Outputs the deviations from the nominal kriged probabilities

external_kriging

The external_kriging module allows users to perform estimation using grids created in EVS (with our without layers or lithology) in GeoEAS which supports very advanced variography and kriging techniques. Grids and data are kriged externally from EVS and the results can then be read into EVS and treated as if they were kriged in EVS.

This an advanced module which should be used only by persons with experience with GeoEAS and geostatistics. C Tech does not provide tech support for the use of GeoEAS.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
• Input Data [Field] Allows the user to import a field contain data. This data will be kriged to the grid instead of using file data.
• Input Grid [Field] Allows the user to import a previously created grid. All data will be kriged to this grid.

Module Output Ports

• Output [Field] Outputs a 3D data field which can be input to any of the Subsetting and Processing modules.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: defines Z Scale and grid translation(s)
• Export Data: controls the file names and data processing for creation of GeoEAS inputs.
• Export Grid: Exports the grid and data to GeoEAS formats. A grid and data must be connected to the import ports
• Import Data: Imports the grid and data to GeoEAS formats. A grid and data must be connected to the import ports

create stratigraphic hierarchy

The create stratigraphic hierarchy module reads a special input file format called a pgf file, and then allows the user to build geologic surfaces based on the input file’s geologic surface intersections. This process is carried out visually (in the EVS viewer) with the use of the create stratigraphic hierarchy user interface. The surface hierarchy can either be generated automatically for simple geology models or for every layer for complex models. When the user is finished creating surfaces the gmf file can be finalized and converted into a *.GEO file.

Boring States:

• Preserve Bottom tells the module that when the TIN has reached the bottom of a boring don’t drop it from the geology but continue to add the same point to the remaining surfaces.

  • The Preserved state is automatically applied when the Preserve Bottom toggle is on, and you reach the bottom of the boring.

• To Be Dropped is just for your information (this is not a state that you can set). When the tin continues below a boring that boring gets dropped from the remainder of the surfaces.

• Boring Dropped is a way of removing a boring from the geology for the current surface and below, this will happen automatically when the TIN reaches the bottom of a boring but can be done at any point by changing this state.

horizons to 3d

The horizons to 3d module creates 3-dimensional solid layers from the 2-dimensional surfaces produced by gridding and horizons, to allow visualizations of the geologic layering of a system. It accomplishes this by creating a user specified distribution of nodes in the Z dimension between the top and bottom surfaces of each geologic layer.

The number of nodes specified for the Z Resolution may be distributed (proportionately) over the geologic layers in a manner that is approximately proportional to the fractional thickness of each layer relative to the total thickness of the geologic domain. In this case, at least three layers of nodes (2 layers of elements) will be placed in each geologic layer.

Please note that if any portions of the input geology is NULL, these cells will be omitted from the grid that is created. This can save memory and provide a means to cut (in a Lego fashion) along boundaries.

Module Input Ports

• Input Geologic Field [Field] Accepts a data field from gridding and horizons to krige data into geologic layers.

Module Output Ports

• Output Field [Field] Outputs a 3D data field which can be input to any of the Subsetting and Processing modules.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: controls Z Scale and Explode distance
• Layer Settings: resolution and layer settings
• Data To Export: controls what data to outputs.

horizons_to_3d_structured

The horizons_to_3d_structured module creates 3-dimensional solid layers from the 2-dimensional surfaces produced by gridding and horizons, to allow visualizations of the geologic layering of a system. It accomplishes this by creating a user specified distribution of nodes in the Z dimension between the top and bottom surfaces of each geologic layer.

This module is similar to horizons to 3d, but does not duplicate nodes at the layer boundaries and therefore the model it creates cannot be exploded into individual layers. However, this module has the advantage that its output is substantially more memory efficient and can be used with modules like crop_and_downsize or ortho_slice.

The number of nodes specified for the Z Resolution may be distributed (proportionately) over the geologic layers in a manner that is approximately proportional to the fractional thickness of each layer relative to the total thickness of the geologic domain.

Module Input Ports

• Input Geologic Field [Field] Accepts a data field from gridding and horizons to krige data into geologic layers.

Module Output Ports

• Output Field [Field] Outputs a 3D data field which can be input to any of the Subsetting and Processing modules.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: controls Z Scale and Explode distance
• Layer Settings: resolution and layer settings
• Data To Export: controls what data to outputs.

layer from horizon

The layer from horizon module will create a single geo layer based upon an existing surface and a constant elevation value.

The Surface Defines option will allow the user to set whether the selected surface defines the top or the bottom of the layer. For example if the Top Of Layer is chosen the selected surface will define the top, while the Constant Elevation for Layer will define the bottom of the layer. The ‘Material Name / Number’ will define the geologic layer name and number for the newly created layer.

surface from horizons

This module allows visualization of the topology of any single surface.

surface from horizons can explode the geologic surface analogous to how explode_and_scale explodes layers created by horizons to 3d or 3d estimation. The ability to explode the surface is integral to this module.

surface from horizons also allows the user to either color the surface according to the surface Elevation or any other data component exported by gridding and horizons.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
• Explode [Number] Accepts the Explode distance from other modules
• Input Geologic Field [Field] Accepts a data field from gridding and horizons to krige data into geologic layers.

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Explode [Number] Outputs the Explode distance to other modules
• Surface Name [String / minor] Outputs a string containing the selected surface’s name
• Output Field [Field] Outputs a 3D data field which can be input to any of the Subsetting and Processing modules.
• Surface [Renderable]: Outputs to the viewer.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: controls Z Scale and Explode distance
• Surface Settings: controls translation, hierarchy and surface selection
• Data Settings: controls clipping, processing (Log) and clamping of input data and kriged outputs.

surfaces from horizons

The surfaces from horizons module provides complete control of displaying, scaling and exploding one or more geologic surfaces from the set of surfaces output by gridding and horizons. This module allows visualization of the topology of any or all surfaces and\or the interaction of a set of individual surfaces.

surfaces from horizons can explode geologic surfaces analogous to how explode_and_scale explodes layers created by horizons to 3d or 3d estimation. The ability to explode the surfaces is integral to this module.

surfaces from horizons also allows the user to either color the surface according to the surface Elevation or any other data component exported by gridding and horizons.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
• Explode [Number] Accepts the Explode distance from other modules
• Input Geologic Field [Field] Accepts a data field from gridding and horizons to krige data into geologic layers.

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Explode [Number] Outputs the Explode distance to other modules
• Output Field [Field] Outputs a 3D data field which can be input to any of the Subsetting and Processing modules.
• Surface [Renderable]: Outputs to the viewer.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: controls Z Scale and Explode distance
• Surface Settings: controls translation, hierarchy and surface selection
• Data Settings: controls clipping, processing (Log) and clamping of input data and kriged outputs.

lithologic modeling

lithologic modeling is an alternative geologic modeling concept that uses geostatistics to assign each cell’s lithologic material as defined in a pregeology (.pgf) file, to cells in a 3D volumetric grid.

There are two Estimation Types:

• Nearest Neighbor is a quick method that merely finds the nearest lithology sample interval among all of your data and assigns that material. It is very fast, but generally should not be used for your final work.
• Kriging provides the rigorous probabilistic approach to geologic indicator kriging. The probability for each material is computed for each cell center of your grid. The material with the highest probability is assigned to the cell. All of the individual material probabilities are provided as additional cell data components. This will allow you to identify regions where the material assignment is somewhat ambiguous. Needless to say, this approach is much slower (especially with many materials), but often yields superior results and interesting insights.

There are also two Lithology Methods when Kriging is selected.

• The default method is block. This method is the quickest since probabilities are assigned directly to cells, and lithology is therefore determined based on the highest probability among all materials. However the resulting model is “lego-like” and therefore requires high grid resolutions in x, y & z in order to give good looking results.
• The other method is Smooth. With Smooth, probabilities are assigned to nodes. In much the same way as analytical data, nodal data for probabilities provides an inherently higher effective grid resolution because after kriging probabilities to the nodes, there is an additional step where we “Smooth” the grid by interpolating between the nodes, cutting the blocky grid and forming a new smooth grid. MUCH lower grid resolutions can be used, often achieving superior results.

Module Input Ports

• Input Geologic Field [Field] Accepts a data field from gridding and horizons to krige data into geologic layers.
• Filename [String / minor] Allows the sharing of file names between similar modules.
• Refine Distance [Number] Accepts the distance used to discretize the lithologic intervals into points used in kriging.

Module Output Ports

• Geologic legend Information [Geology legend] Supplies the geologic material information for the legend module.
• Output Field [Field] Contains the volumetric cell based indicator geology lithology (cell data representing geologic materials).
• Filename [String / minor] Outputs a string containing the file name and path. This can be connected to other modules to share files.
• Refine Distance [Number] Outputs the distance used to discretize the lithologic intervals into points used in kriging or displayed in post_samples as spheres.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Grid Settings: control the grid type, position and resolution
• Krig Settings: control the estimation methods
  • NOTE: The Quick Method assigns the lithologic material cell data based on the nearest lithologic material (in anisotropic space) to your PGF borings. This is done based on the cell center (coordinates) and an enhanced refinement scheme for the PGF borings. In general the Quick Method should not be used for final results

Advanced Variography Options:

It is far beyond the scope of our Help to attempt an advanced Geostatistics course. The terminology and variogram plotting style that we use is industry standard and we do so because we will not provide detailed technical support nor complete documentation on these features, which would effectively require a geostatistics textbook, in our help.

However, we have offered an online course on how to take advantage of the complex, directional anisotropic variography capabilities in 3d estimation (which applies equally well to lithologic modeling and adaptive_indicator_krig), and that course is available as a recorded video class. This class is focused on the mechanics of how to employ and refine the variogram anisotropy with respect to your data and the physics of your project such as contaminated sediments in a river bottom. The variogram is displayed as an ellipsoid which can be distorted to represent the Primary and Secondary anisotropies and rotated to represent the Heading, Dip and Roll. Overall scale and translation are also provided as additional visual aids to compare the variogram to the data, though these do not affect the actual variogram.

We are not hiding this capability from you as the Anisotropic Variography Study folder of Earth Volumetric Studio Projects contains a number of sample applications which demonstrate exactly what is described above. However, we assure you that understanding how to apply this to your own projects will be quite daunting and really does require a number of prerequisites:

• A thorough explanation of these complex applications
• A reasonable background in Python and how to use Python in Studio
• An understanding of all of the variogram parameters and their impact on the estimation process on both theoretical datasets as well as real-world datasets.

This 3 hour course addresses this issues in detail.

Discussion of Lithologic (Geologic Indicator Kriging) vs. Stratigraphic (Hierarchical) Geologic Modeling

Stratigraphic geologic modeling utilizes one of two different ASCII file formats (.geo and .gmf) which contain “interpreted” geologic information. These two file formats both describe points on each geologic surface (ground surface and bottom of each geologic layer), based on the assumption of a geologic hierarchy.

The easiest way to describe geologic hierarchy is with an example. Consider the example below of a clay lens in sand with gravel below. Some borings will see only sand above the gravel, while others will reveal an upper sand, clay, and lower sand.

The geologic hierarchy for this site will be upper sand, clay, lower sand, and gravel. This requires that the borings with only sand (above the gravel) be described as upper sand, clay, and lower sand, with the clay described as being zero thickness. For this simple example, determining the hierarchy is straightforward. For some sites (as will be discussed later) it is very difficult or even impossible.

For those sites that can be described using the above method, it remains the best approach for building a 3D geologic model. Each layer has smooth boundaries and the layers (by nature of hierarchy) can be exploded apart to reveal the individual layer surface features. In the above example, the numbers represent the layer numbers for this site (even though layers 0 and 2 are both sand). Two examples of much more complex sites that are best described by this original approach are shown below.

Geologic Example: Sedimentary Layers and Lenses

Geology Example & Figure: Outcrop of Dipping Strata

EVS is not limited to sedimentary layers or lenses. The figure below shows a cross-section through an outcrop of dipping geologic strata. EVS can easily model the layers truncating on the top ground surface.

However, many sites have geologic structures (plutons, karst geology, sand channels, etc.) that do not lend themselves to description within the context of hierarchical layers. For these sites, Geologic Indicator Kriging (GIK) offers the ability to build extremely complex models with a minimum of effort (and virtually no interpretation) on the part of the geologist. GIK can also be a useful check of geologic hierarchies developed for sites that do lend themselves to a model based upon hierarchical layers.

GIK uses raw, uninterpreted 3D borings logs as the input file. The .pgf (pre-geology file) format is used to represent these logs. PGF files contain descriptions of each boring with x,y, & z coordinates for ground surface and the bottom of each observed geologic unit. Consecutive integer values (e.g. 0 through n-1, for n total observed units in the site) are used to describe each material observed in the entire site.

NOTE: It is important to start your material ID numbering at zero (0) instead of 1.

Usually, materials are numbered based upon a logical classification (such as porosity or particle size), however the numbering can be arbitrary as long as the numbers are consecutive (don’t leave numbers out of the sequence). For the example given above, we could number the materials as shown in the figure below (even though it is not a numbering sequence based on porosity or particle size).

For a .pgf file, borings that do not see the clay (material 2 in the figure) would not need to consider the sand as being divided into upper and lower. Rather, every boring is merely a simple ASCII representation of the raw borings logs. The only interpretation involves classification of the observed soil types in each boring and assigning an associated numbering scheme.

mask horizons

mask horizons receives geologic input into its left input port and an optional input masking surface into its right port.

Module Input Ports

• Input Field [Field] Accepts a data field.
• Input Area [Field] Accepts a field defining a surface of the area for masking

Module Output Ports

• Output Field [Field] Outputs the processed field.

NOTE: The mask is normally applied to the first surface only. If this surface is removed, the mask is lost. However the “Allow Subsetting” toggle will apply the mask to all horizons, but it will slow down processing and use more memory.

edit_horizons is an interactive module which allows you to probe points to be selectively added to the creation of each and every stratigraphic horizon. This provides the ability to manual edit horizon surfaces prior to the creation of geologic models.

The method of connecting edit_horizons is unique among our modules. It uses the pink output port from gridding and horizons as its primary input, and it also requires the purple side port from viewer since it requires interactive probing. Its blue output port then becomes equivalent to the blue output of gridding and horizons, but with edited surfaces.

Regardless of the estimation method used originally, edit_horizons uses Natural Neighbor to perform its near-real-time modifications. For this reason, there is a Use Gradients toggle at the top of the user interface, which is identical in function to the one in gridding and horizons.

The other important parameter at the top of the user interface is the Horizon Point Radius. The default (linked) value for this parameter is computed for you as 2% of the X-Y diagonal extents of your input geology. If any of the original data points for the selected horizon being edited fall within the Horizon Point Radius, then we don’t use your probed point based on the assumption that the original data is more defensible and should take precedence.

Next there is the Probe Action, which has 3 options:

1. None (default state when the module is instanced)
2. Reset Position (allows you to move points)
3. Add Point (allows you to add new surface control points for the selected horizon)

The Horizons list shows all of your geologic horizons. Here, you select the horizon surface you wish to modify. The points that you add only affect the selected horizon. When you change the selected horizon, you can add new points for that surface. You are able to add as many points as you need for any or all of the horizons.

The Horizon Point List is the list of points that you have added by probing in your model. You can only probe on actual objects. These objects can be surfaces from horizons, slices, tubes, or whatever objects you’ve added to your viewer. Slices are very useful since you can move them where you need them so you can probe points at specific coordinates. You are also able to manually change the X, Y, and/or Z coordinates or any point as needed. For each point, a Note: box is provided so you can keep a record of your actions and reasons.

horizon_ranking

The horizon_ranking module is used to give the user control over individual surface priorities and rankings. This allows the user to fine tune their hierarchy in ways much more complex than a simple top-down or bottom-up approach.

Module Input Ports

horizon_ranking has one input port which receives geologic input from modules like gridding and horizons

Module Output Ports

horizon_ranking has one output port which outputs the geologic input with re-prioritized hierarchy

Module Input Ports

• Input Field [Field] Accepts a data field from 3d estimation or other similar modules.

Module Output Ports

• Output Field [Field] Outputs the subsetted field as edges
• Geologic legend Information [Geology legend] Outputs the geologic material information

material_mapping

This module can re-assign data corresponding to:

• Geologic Layer
• Material ID
• Indicator
• Adaptive Indicator

for the purpose of grouping. This provides great flexibility for exploding models or coloring.

Groups are processed from Top to Bottom. You can have overlapping groups or groups whose range falls inside a previous group. In that event, the lower groups override the values mapped in a higher group.

For example, if you have ten material ids (0 through 9) and you want to have them all be 0 except for 5 & 6 which should be 1, this can be accomplished with two groups:

1. From 0 to 9 Map to 0
2. From 5 to 6 Map to 1

Please note that in the animator, you can animate these values. Each group has From, To and Map To values that are numbered zero through eleven (e.g. From0, MapTo5)

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the processed field.

combine horizons

The combine horizons module is used to merge up to six geologic horizons (surfaces) to create a field representing multiple geologic layers.

The mesh (x-y coordinates) from the first input field, will be the mesh in the output. The input fields should have the same scale and origin, and number of nodes in order for the output data to have any meaning.

It also has a Run toggle (to prevent downstream modules from firing during input setting changes).

combine horizons provides an important ability to merge sets of surfaces or add additional surfaces to geologic models. It is important to understand the consequences of doing so and the steps that must be taken. The Brown-Grey-Light Brown-Beige port contains the material_ID numbers and names and it is important that the content of this port reflect the current set of surfaces/layers reflected in the geology. When Material_ID or Geo_Layer is presented in a legend, this port is necessary to automatically provide the layer names. When combine horizons is used to construct modified geologic horizons, its Geologic legend Information port MUST be used vs. the same port in gridding and horizons

Module Input Ports

• Input Geologic Field [Field] Accepts a field with data whose grid will be exported.
• Input Field 1 [Field] Accepts a data field.
• Input Field 2 [Field] Accepts a data field.
• Input Field 3 [Field] Accepts a data field.
• Input Field 4 [Field] Accepts a data field.
• Input Field 5 [Field] Accepts a data field.

Module Output Ports

• Geologic legend Information [Geology legend] Supplies the geologic material information for the legend module.
• Output Geologic Field [Field] Outputs the field with selected data
• Output Object [Renderable]: Outputs to the viewer.

subset horizons

The subset horizons module allows you to subset the output of gridding and horizons so that downstream modules (3d estimation, horizons to 3d, Geologic Surface) act on only a portion of the layers kriged.

subset horizons is used to select a subset of the layers (and corresponding surfaces) export from gridding and horizons. This is useful if you want (need) to krige parameter data in each geologic layer separately.

This is not normally needed with contaminant data, but when you are kriging data such as porosity that is inherently discontinuous across layer boundaries, it is essential that each layer be kriged with data collected ONLY within that layer.

subset horizons eliminates the need for multiple gridding and horizons modules reading data files that are subsets of a master geology. Inserting subset horizons between gridding and horizons and 3d estimation allows you to select one or more layers from the geology.

This functionality is very useful when you want to krige groundwater and soil data using a single master geology file that represents both the saturated and unsaturated zones.

Module Input Ports

• Input Geologic Field [Field] Accepts a data field from gridding and horizons to krige data into geologic layers.

Module Output Ports

• Geologic legend Information [Geology legend] Supplies the geologic material information for the legend module.
• Output Geologic Field [Field] Can be connected to the 3d estimation, 3D_Geology Map, and surface from horizons(s) modules.

collapse horizons

The collapse horizons module allows you to subset the output of gridding and horizons so that downstream modules (3d estimation, horizons to 3d, Geologic Surface) act on only a single merged layer.

collapse horizons is used to merge all layers (and corresponding surfaces) export from gridding and horizons into a single layer (topmost and bottommost surfaces).

collapse horizons eliminates the need for multiple gridding and horizons modules reading data files that are single layer subset of a master geology. Inserting collapse horizons between gridding and horizons and 3d estimation kriges all data into a single geologic layer. When used with subset horizons it allows for creating a single layer that represents a only a portion (subset) of the master geology file.

Module Input Ports

• Input Geologic Field [Field] Accepts a data field from gridding and horizons to krige data into geologic layers.

Module Output Ports

• Geologic legend Information [Geology legend] Supplies the geologic material information for the legend module.
• Output Geologic Field [Field] Can be connected to the 3d estimation, 3D_Geology Map, and surface from horizons(s) modules.

displace_block

displace_block receives any 3D field into its input port and outputs the same field translated in z according to a selected nodal data component of an input surface allowing for non-uniform fault block translation.

This module allows for the creation of tear faults and other complex geologic structures. Used in conjunction with distance to surface it makes it possible to easily model extremely complex deformations.

Module Input Ports

• Input Field [Field] Accepts a volumetric field
• Input Surface [Field] Accepts a 2D surface grid with elevation nodal data. This type of grid is created by gridding and horizons and import raster as horizon.

Module Output Ports

• Output Field [Field] Outputs the displaced field
• Output Object [Renderable]: Outputs to the viewer.

post_samples

The post_samples module is used to visualize:

• Sampling locations and the values of the properties in .apdv files
• The lithology specified in a .pgf, .lsdv, .lpdv or .geo files
• The location and values of well screens in a .aidv file

Along with a representation of the borings from which the samples/data were collected. The post_samples module has the capability to process property values to make the posted data values consistent with data used in kriging modules. Data can be represented as spheres or any user specified glyph. The sampling locations may be colored and sized according to the magnitude of the property value, and labels can be applied to the sampling locations with several different options.

Each sampling location can probed for data by holding the Ctrl button and left-clicking on the sample location.

When you read any of the supported file types, the module automatically selects the proper default settings to display that data type. However, some file formats can benefit from different options depending on your desires and the quantity of data present.

Below is the Properties window for post samples after reading a .PGF file. Note that “Samples” and “Screens” are selected.

The result in the viewer is below.

If we turn on Well Labels and Sample Labels (with some subsetting to declutter), the viewer shows:

The post_samples module can also represent downhole geophysical logs or Cone Penetration Test (CPT) logs with tubes which are colored and/or sized according to the magnitude of the data. It can display nonvertical borings and data values collected along their length, and can also explode borings and sample locations to show their correct position within exploded geologic layering.

When used to read geology files, post_samples will place surface indicators at the top (ground) surface and the bottom of each geologic layer that are colored according to the layer they depict. When a geology file (.geo or .gmf) is exploded without using geologic surface input from gridding and horizons there will be surface indicators at the top and bottom of each layer. You may color the borings by lithology.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
• Explode [Number] Accepts the Explode distance from other modules
• Date [Number] Accepts a date to interpolate time domain data
• Input Geologic Field [Field] Accepts a data field from gridding and horizons to krige data into geologic layers.
• Subsetting Feature [Field] Accepts a (1D) line or (2D) surface to be used to subset the borings.
• Sample Glyph [Field] Allows the user to import a field containing a geometric object which will be the glyph displayed at each sample location.
• Filename [String / minor] Allows the sharing of file names between similar modules.

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Explode [Number] Outputs the Explode distance to other modules
• Geologic legend Information [Geology legend] Supplies the geologic material information for the legend module.
• Boring Tubes [Field / minor] Outputs the tube paths as lines with data
• Boring Data [Field / minor] Outputs the tube paths as lines with data
• Filename [String / minor] Allows the sharing of file names between similar modules.
• Analytes Name [String / minor] Outputs a string containing the name of the currently selected analyte or date
• Sample Data [Renderable]: Outputs to the viewer

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: 
  • selected data component
  • Z Scale (remember this should be set on the Home tab or Application properties)
  • Display Toggles: including screens, borings, well and/or sample labeling, etc.
• Sample Settings: controls clipping, processing (Log) and clamping of data.
• Collapse to 2D: controls how 3D data is subset to 2D
• Geology Settings: controls the display of geologic data
• Time Settings: controls how the module deals with time domain data
• Boring Tube Settings: controls how borings are displayed
• Color Tube Settings: controls the display of colored tubes as an alternative representation (vs. spheres or glyphs)
• Label Settings: parameters association with labeling of borings and samples
  • Remember that toggles to turn on labels for Wells or Samples are at the top in Properties.
  • There are type-ins which receive Python expressions providing a great deal of power to adjust how you label wells and samples
  • Default expressions (which vary by file type) are automatically created for you (when these are Linked) to make the labeling more logical.

EXAMPLE .PT FILE & OUTPUT

TRUETYPE, 20.000000, LC, 180.000000, 90.000000, 0.000000, 0.847059, 0.847059, 0.858824, 0.050000, False, 0.200000, 5.000000, None, "Noto Sans"

0.000000, 300.000000, 0.000000, 0, "TTF"

TRUETYPE, 20.000000, LC, 180.000000, 90.000000, 0.000000, 0.847059, 0.847059, 0.858824, 0.050000, False, 0.200000, 5.000000, Bold, "Noto Sans"

250.000000, 300.000000, 0.000000, 0, "TTF Bold"

TRUETYPE, 20.000000, LC, 180.000000, 90.000000, 0.000000, 0.847059, 0.847059, 0.858824, 0.050000, False, 0.200000, 5.000000, Italic, "Noto Sans"

500.000000, 300.000000, 0.000000, 0, "TTF Italic"

TRUETYPE, 20.000000, LC, 180.000000, 90.000000, 0.000000, 0.847059, 0.847059, 0.858824, 0.050000, False, 0.200000, 5.000000, Bold Italic, "Noto Sans"

750.000000, 300.000000, 0.000000, 0, "TTF Bold Italic"

TRUETYPE, 20.000000, UC, 180.000000, 90.000000, 0.000000, 0.847059, 0.847059, 0.858824, 0.050000, True, 0.200000, 5.000000, None, "Noto Sans"

0.000000, 200.000000, 0.000000, 0, "Outlined"

TRUETYPE, 20.000000, UC, 180.000000, 90.000000, 0.000000, 0.847059, 0.847059, 0.858824, 0.050000, True, 0.200000, 5.000000, Bold, "Noto Sans"

250.000000, 200.000000, 0.000000, 0, "Outlined Bold"

TRUETYPE, 20.000000, UC, 180.000000, 90.000000, 0.000000, 0.847059, 0.847059, 0.858824, 0.050000, True, 0.200000, 5.000000, Italic, "Noto Sans"

500.000000, 200.000000, 0.000000, 0, "Outlined Italic"

TRUETYPE, 20.000000, UC, 180.000000, 90.000000, 0.000000, 0.847059, 0.847059, 0.858824, 0.050000, True, 0.200000, 5.000000, Bold Italic, "Noto Sans"

750.000000, 200.000000, 0.000000, 0, "Outlined Bold Italic"

TRUETYPE, 20.000000, UC, 180.000000, 90.000000, 45.000000, 0.847059, 0.847059, 0.858824, 0.050000, False, 0.200000, 5.000000, Bold, "Noto Sans"

250.000000, 400.000000, 0.000000, 0, "TTF Bold at 45° roll"

LINEFONT, 20.000000, UC, 180.000000, 90.000000, 0.000000, 0.847059, 0.847059, 0.858824, 0.050000, None

0.000000, 100.000000, 0.000000, 0, "Singleline"

LINEFONT, 20.000000, UC, 180.000000, 90.000000, 0.000000, 0.847059, 0.847059, 0.858824, 0.050000, Italic

500.000000, 100.000000, 0.000000, 0, "Singleline Italic"

FORWARDFACING, 0.847059, 0.847059, 0.858824, None

0.000000, 0.000000, 0.000000, 0, "ForwardFacing"

END

explode_and_scale

The explode_and_scale module is used to separate (or explode) and apply a scaling factor to the vertical dimension (z-coordinate) of objects in a model. explode_and_scale can also translate the fields in the z direction, and control the visibility of individual cell sets (e.g. geologic layers).

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
• Explode [Number] Accepts the Explode distance from other modules
• Input Field [Field] Accepts a data field from 3d estimation or other similar modules.

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Explode [Number] Outputs the Explode distance to other modules
• Output Field [Field / minor] Outputs the field with the scaling and exploding applied.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: controls the scaling, exploding and Z translation
• Explode And Scale Settings: controls layer exploding and cell sets

plume shell

The plume_shell module creates the external faces of a volumetric subset of a 3D input. The resulting closed volume “shell” generally is used only as a visualization of a plume and would not be used as input for further subsetting or volumetric computations since it is hollow (empty). This module creates a superior visualization of a plume as compared with other modules such as plume passing to external_faces and is quicker and more memory efficient.

Module Input Ports

• Input Field [Field] Accepts a data field.
• Isolevel [Number] Accepts the subsetting level.

Module Output Ports

• Output Field [Field] Outputs the subsetted field as a closed surface.
• Status [String / minor] Outputs a string containing a description of the operation being performed (e.g. TCE plume above 4.00 mg/kg)
• Isolevel [Number] Outputs the subsetting level.
• Plume [Renderable]: Outputs to the viewer.

intersection_shell

The intersection_shell is a powerful module that incorporates some of the characteristics of plume_shell, yet allows for a large number of sequential (serial) subsetting operations, just like intersection.

To get the functionality of (the now deprecated) constant_shell module, you would turn off Include Varying Surface.

Because this module has “intersection” in its name, it allows you to add any number of subsetting operations.

Each operation can be “Above” or “Below” the specified Threshold value, which in Boolean terms corresponds to:

• A and B where both the A & B operations are set to Above or
• A and (NOT B) where the A operation is set to above and the B operation is set to Below.

However the operator is always “and” for intersection modules. If you need an “or” operator to achieve your subsetting, you need the union module.

This module creates an efficient and superior visualization of a plume that can be sent directly to the viewer for rendering. The intersection_shell module outputs a specialized version of a sequentially subset plume that is suitable for VRML export for 3D printing to create full color physical models.

For output to 3D printing, please jump to the Issues for 3D Printing topic.

Without intersection_shell it is very difficult if not impossible to create a VRML file suitable for printing, especially with complex models.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the subsetted field as a closed surface.
• Output Object [Renderable]: Outputs to the viewer.

intersection_shell is the module that can create an ISOSURFACE. In other words, a surface (not volume) representing part(s) of your plume.

It has two (+) toggles which control the visibility of a plume “shell”.

In general a plume external shell has two components:That portion which is exactly EQUAL to the Subsetting LevelThat portion which is greater than the Subsetting Level

When both toggles are on (default) the plume is

If you display only the Constant Surface (component 1) you get this

If you display only the Varying Surface (component 2) you get this

change_minmax

The change_minmax module allows you to override the minimum and/or maximum data values for coloring purposes. This functionality is commonly needed when working with time-series data. For example, the user can set the minmax values to bracket the widest range achieved for many datasets, thus allowing consistent mapping from dataset to dataset during a time-series animation or individual sub-sites.

This way 100 ppm would always be red throughout the animation, and if some times did not reach a maximum of 100 ppm, there would be no red color mapping for those time-steps.

NOTE: The Clamp toggle actually changes the data. Use with caution as this will change volumetrics results.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the field with altered data min/max values
• Output Object [Renderable]: Outputs to the viewer.

band data

band data provides a means to color surfaces or volumetric objects (converted to surfaces) in solid colored bands.

band data can contour by both nodal and cell data.

This module does not do subsetting like plume_shell , plume. It is used in conjunction with these modules to change the way their output is colored.

Module Input Ports

• Input Field [Field] Accepts a data field.
• Input Contour Levels [Contours]: Accepts an array of values representing values to place contours

Module Output Ports

• Output Field [Field] Outputs the field with altered data min/max values
• Output Contour Levels [Contours]: Outputs an array of values representing values to be labeled in the legend.
• Output Object [Renderable]: Outputs to the viewer.

volume_renderer

Volume_renderer directly renders a 3D uniform field using either the Back-to-Front (BTF) or Ray-tracing volume rendering techniques. The Ray-tracing mode is available to both OpenGL and the software renderer. The BTF renderer, which is configured as the default, is available only in the OpenGL renderer.

NOTE: This module and its rendering technique are not supported in C Tech Web Scenes (CTWS files).

The basic concept of volume rendering is quite different than anything other rendering technique in EVS. Volume_renderer converts data into a fuzzy transparent cloud where data values at each point in a 3D grid are represented by a particular color and opacity.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Object [Renderable]: Outputs to the viewer.

opacity by nodal data

opacity by nodal data provides a means to adjust the opacity (1 - transparency) of any object based on its data values using a simple ramp function which assigns a starting opacity to values less than or equal to the Level Start and an ending opacity to values greater than or equal to the Level End. The appearance of the resulting output is often similar in appearance to volume rendering. opacity by nodal data converts data into partially transparent surfaces where data values at each point in a grid are represented by a particular color and opacity.

NOTE: Any module connected after opacity by nodal data MUST have Normals Generation set to Vertex (if there is a Normals Generation toggle on the module’s panel, it must be OFF).

1. The leftmost port accepts an input field

Module Output Ports

1. The output field which passes the original data with a special new “opacity” data component for use with downstream modules (e.g. slice, plume_shell, etc.)
2. The (red) port for connection to the viewer.

slope_and_aspect

The slope_and_aspect module determines the slope and aspect of a surface. The slope is the angle between the surface and the horizon. The aspect is the cardinal direction in degrees (rotating clockwise with 0° being North) that the slope is facing.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration).
• Input Field [Field] Accepts a field with scalar or vector data.

Module Output Ports

• Output Field [Field] Outputs both slope and aspect data as a field
• Output Slope Object [Renderable]: Outputs to the viewer.
• Output Aspect Object [Renderable]: Outputs to the viewer.

select single data

The select single data module extracts a single data component from a field. select single data can extract scalar data components or vector components. Scalar components will be output as scalar components and vector components will be output as vector components.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the subsetted field as faces.
• Output Object [Renderable]: Outputs to the viewer.

The import _wavefront_obj module will only read Wavefront Technologies format .OBJ files which include object textures which are represented (included) as a single image file. Each file set is actually a set of 3 files which must always include the following 3 files types with the same base file name, which must be in the same folder:

1. The .obj file (this is the file that we browse for)
2. A .mtl (Material Template Library) file
3. An image file (e.g. .jpg) which is used for the texture. Note: there must be only ONE image/texture file. We do not support multiple texture files.

This module provides the user with the capability to integrate complex photo-realistic site plans, buildings, and other 3D features into the EVS visualization, to provide a frame of reference for understanding the three dimensional relationships between the site features, and characteristics of geologic, hydrologic, and chemical features.

• Output Object [Renderable]: Outputs to the viewer

Properties and Parameters

The Properties window includes the following parameters:

Texture Options: These allow you to enhance the image used for texturing to achieve the best looking final output.

Transform Settings: This allows you to add any number of Translation or Scale transformations in order to place your Wavefront Object in the same coordinate space as the rest of your “Real-World” model. It is very typical that Wavefront Objects are in a rather arbitrary local coordinate system that will have no defined transformation to any standard coordinate projection.

Generally you should know if the coordinates are feet of meters and if those are not correct, do that scaling as your first set of transforms.

It will be up to you to determine the set of translations that will properly place this object in your model. Hopefully rotations will not be required, but they are possible with the Transform List.

volumetrics

The volumetrics module is used to calculate the volumes and masses of soil, and chemicals in soils and ground water, within a user specified constant_shell (surface of constant concentration), and set of geologic layers. The user inputs the units for the nodal properties, model coordinates, and the type of processing that has been applied to the nodal data values, specifies the subsetting level and soil and chemical properties to be used in the calculation, and the module performs an integration of both the soil volumes and chemical masses that are within the specified constant_shell. The results of the integration are displayed in the EVS Information Window, and in the module output window.

The volumetrics module computes the volume and mass of everything passed to it. To compute the volume/mass of a plume, you must first use a module like plume or intersection to subset your model.

NOTE: Do not use plume_shell or intersection_shell upstream of volumetrics since their output is a hollow shell without any volume.

The volumetrics module computes volumes and masses of analytes using the following method:

• Each cell within the selected geologic units is analyzed
• The mass of analyte within the cell is integrated based on concentrations at all nodes (and computed cell division points)
• The volumes and masses of all cells are summed
• Centers of mass and eigenvectors are computed
• For soil calculations the mass of analyte is directly computed from the computed mass of soil (e.g. mg/kg). This is affected by the soil density parameter (all densities should be entered in gm/cc).
• For groundwater calculations, the mass of analyte (Chemical Mass) is computed by first determining the volume of water in each cell. This uses the porosity parameter and each individual cell’s volume. From the cell’s water volume, the mass of analyte is directly computed (e.g. mg/liter).
• The volume of analyte (Chemical Volume) is computed from the Chemical Mass using the “Chem Density” parameter (all densities should be entered in gm/cc).

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration).
• Explode [Number] Accepts the Explode distance from other modules
• Input Field [Field] Accepts a field with data.
• String for Output [String]
• Input Subsetting Level [Number] Accepts the subsetting level

Module Output Ports

• Output Subsetting Level [Number] Outputs the subsetting level
• Soil Volume Level [Number] Outputs the computed soil volume
• Soil Mass Level [Number] Outputs the computed soil mass
• Chemical Volume Level [Number] Outputs the computed chemical volume
• Chemical Mass Level [Number] Outputs the computed chemical mass
• Nodal Data Component [String] The name of the analyte
• Volume Units [String] The units of the volume calculations (e.g. m3)
• Result Value [Number] The final output
• Output Second Moment Object [Renderable]: Outputs to the viewer

You can use the Geologic Layers selection list which allows you to choose the cell sets (geologic layers) that you want to perform computations on.

The Soil Density and Porosity inputs allow the user to input the properties of the soil matrix in which the chemicals reside. Note that if the mass of chemicals in a combined soil and ground water plume are to be estimated, one of the geologic layers should be set up to have a boundary within it that corresponds to the water table position. In essence, this will create two layers out of one geologic unit that can be used to separate the soil domain from the ground water domain. The user can then choose the appropriate Nodal Data Units for each layer in the two domains, and obtain volumetrics estimates by summing the results in individual layers. There are several other alternative methods for completed volumetrics estimates in continuous soil and ground water plumes, which involve either setting up separate soil and ground water models, or using the Field Math module to remove and include specified areas of the domains.

The Chemical Density input allows the user to input the density of the chemical constituent for which mass estimates are being completed. Note that this value is used to calculate the volume of chemical in the specified constant_shell, as the mass units are calculated directly from the nodal data.

Volume Dollars is used along with the total volume of the chemical to indicate the cost of the removal of the chemical.

Mass Dollars is used, along with the total chemical mass, to determine the value of the chemical mass.

Volume Units is used to select which units the volume should be calculated in. For the Specified Unit Ratio the units to convert to are liters. For example if your units were Cubic Meters the ratio would be 1000.

Mass Units is used to select which units the mass should be calculated in. For the Specified Unit Ratio the units to convert to are Kilograms.

The Output Results File toggle causes volumetrics to write a file to the ctech folder (volumetrics_results.txt) that contains all volumetrics information in a format suitable for input to programs like Excel (tab delimited .txt file). This file is written to in an append mode. It will grow in size as you use volumetrics. You should delete or move the file when you’re done with it.

The Run Automatically toggle, when selected, causes the module to run as soon as any of the input parameters have changed. When not selected the accept button must be pushed for the module to run.

There is an advanced window that can be opened by checking the Advanced Output Options toggle.

The advance panel provides many capabilities including Spatial Moment Analysis.

• Spatial Moment Analysis involves computing the zeroth, first, and second moments of a plume to provide measures of the mass, location of the center of mass, and spread of the plume.
• The zeroth moment is a mass estimate for each sample event and COC. The estimated mass is used to evaluate the change in total mass of the plume over time.
• The first moment estimates the center of mass of the plume (as coordinates Xc , Yc, & Zc).
• The second moment indicates the spread of the contaminant about the center of mass (sxx,syy andszz), or the distance of contamination from the center of mass. This is somewhat analogous to the standard deviation of the plume along three orthogonal axes represented as an ellipsoid created using the eigenvalues as the ellipsoid major and minor axes, and the eigenvectors to orient the ellipsoid. The orientation of the ellipsoid is aligned with the primary axis of the plume (not the coordinate axes).
• The Second Moment ellipsoid represents the spread of the plume in the x, y and z directions. Freyberg (1986) describes the second moment about the center of mass as the spatial covariance tensor.
• The components of the covariance tensor are indicative of the spreading of the contaminant plume about the center of mass. The values of sxx,syy andszz represent the axes of the covariance ellipsoid. The volumetrics module provides a scaling parameter that allows you to view the ellipsoid corresponding to the one-sigma (default) or higher sigma (higher confidence) representation of the contaminant spread.

The Water Density type in window allows the user to specify the density of water. The default of 0.9999720 g/mL (gm/cc) is the Density of Water at 4.5 degrees Celsius.

The Output Filetype radio list is used to select the format of the output file. The default is a tab spaced single line output, the second choice will format the output the same as the display window, and the third option will format the output separated by tabs on multiple lines. Changing these options will not cause the module to run, you must hit accept or change an input value for the module to run.

Overwrite causes the output file to be overwritten instead of appended to. This toggle will only be selected for one run and then will unselect itself and begin appending again, unless it is rechecked. Selecting this toggle will not cause the module to run, you must hit accept or change an input value for the module to run.

The Date type in allows you to set the date, which is output only in the Tabbed Multi-Line file.

Connecting the Red Output Port of volumetrics to the viewer will display the Second Moment Ellipsoid and the Eigenvectors (if turned on).

The three toggles:

1. Display Mass Along Major Eigen Vector
2. Display Mass Along Minor Eigen Vector
3. Display Mass Along Interm(ediate) Eigen Vector

allow you turn on and off the lines lying along the Major, Minor, and Intermediate Eigenvectors. These vectors represent the second moment of mass, and by default have chemical data mapped to them. These lines are of the same orientation as the second moment ellipse but they stretch only to the extents of the model. To output these lines the Export Results button must be pushed.

The Segments In Lines type in allows you to control the number of segments making up each line, the larger the number of segments the closer the node data along the line will match the node data of the model.

The Color Lines by Axis toggle strips the node data from the lines leaving them colored by the axis the represent.

EllipsoidResolution is an integer value determines the number of faces used to approximate the analytically smooth ellipsoid. The higher the resolution the smoother the ellipsoid.

EllipsoidScale is a scaling factor for the second moment ellipsoid. A value of 1.0 (default) is analogous to one-sigma (67%) statistical confidence. Higher values would provide an indication of the size of the eigenvalues with a higher statistical confidence.

cell_volumetrics

The cell_volumetrics module provides cell by cell volumetrics data. It creates an extremely large output file with volume, contaminant mass and cell centers for every cell in the grid.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration).
• Explode [Number] Accepts the Explode distance from other modules
• Input Field [Field] Accepts a field with data.
• String for Output [String]
• Input Subsetting Level [Number] Accepts the subsetting level

Module Output Ports

• Output Subsetting Level [Number] Outputs the subsetting level

compute surface area

The compute surface area module is used to calculate the areas of the entire field input. The input data to compute surface area must be a two dimensional data field output from krig_2d, slice, or any subsetting module which outputs two-dimensional data (slice, plume with 2D input, or plume_shell). The results of the integration are updated each time the input changes.

Module Input Ports

• Input Field [Field] Accepts a data field which is a surface.

Module Output Ports

• Output Area [Number] The area in user units squared
• Units [String] The units (e.g. ft or m)

file_statistics

The file_statistics module is used to check the format of: *.apdv; *.aidv; *.geo; *.gmf; *.vdf; and *.pgf files, and to calculate and display statistics about the data contained in these files. This module also calculates a frequency distribution of properties in the file. During execution, file_statistics reads the file, displays an error message if the file contains errors in format or numeric values, and then displays the statistical results in the EVS Information window

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
• Filename [String / minor] Allows the sharing of file names between similar modules.

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Sample Data [Field / minor] Outputs the data as points (size of points can be controlled).
• Filename [String / minor] Allows the sharing of file names between similar modules.
• Mean Level [Number]Outputs the mean data value
• Median Level [Number] Outputs the median data value
• Min Level [Number] Outputs the minimum data value
• Max Level [Number] Outputs the maximum data value
• Number Of Points [Number] Outputs the number of points
• Statistics [String / minor] Outputs a string containing the full output normally sent to the Information window
• Sample Object [Renderable]: Outputs to the viewer

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Data Processing: controls clipping, processing (Log) and clamping of input data
• Time Settings: controls how the module deals with time domain data

statistics

The statistics module is used to analyze the statistical distribution of a field with nodal data. The data field can contain any number of data components. Statistical analyses can only be performed on scalar nodal data components. An error occurs if a statistical analysis is attempted on vector data. Output from the statistics module appears in the EVS Information Window. Output consist of calculated min and max values, the mean and standard deviation of the data set, the distribution of the data set, and the coordinate extents of the model.

The first port (the leftmost one) should contain a mesh with nodal data. If no nodal data is present, statistics will only report the extents and centroid of your mesh. Data sent to the statistics module for analysis will reflect any data transformation or manipulation performed in the upstream modules. Any mesh data sent to the port is used for calculating the X, Y and Z coordinate ranges. The mesh coordinates have no affect on the data distribution. Cell based data is not used.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
• Input Geologic Field [Field] Accepts a data field from upon which statistics are computed

Module Output Ports

• Mean Level [Number]Outputs the mean data value
• Median Level [Number] Outputs the median data value
• Min Level [Number] Outputs the minimum data value
• Max Level [Number] Outputs the maximum data value
• Number Of Points [Number] Outputs the number of points
• Statistics [String / minor] Outputs a string containing the full output normally sent to the Information window

Delete this text and replace it with your own content.

legend

The legend module is used to place a legend which help correlate colors to analytical values or materials . The legend shows the relationship between the selected data component for a particular module and the colors shown in the viewer. For this reason, the legend’s RED input port must be connected to the RED output port of a module which is connected to the viewer and is generally the dominant colored object in view.

Many modules with red output ports have a selector to choose which ONE of the nodal or cell data components are to be used for coloring. The name of the selected data component will be displayed as the Title of the legend if the Label Options are set to Automatic (default).

If the data component to be viewed is either Geo_Layer or Material_ID (for models where the grid is based upon geology), the Geologic legend Information port from gridding and horizons (or lithologic modeling) must also be connected to legend to provide the Geologic Layer (or material) names for automatic labeling. When this port is connected it will have no affect if any other data component is selected.

The minimum and maximum values are taken from the data input as defined in the datamap. Labels can be placed at user defined intervals along the color scale bar. Labels can consist of user input alphanumerical values or automatically determined numerical values.

Module Input Ports

• Geologic legend Information [Geology legend] Accepts the geologic material information from modules that read geologic data.
• Contour Levels [Contours]: Accepts an array of values representing values to be labeled in the legend.
• Input Object [Renderable]: Accepts the output of a module to which the legend corresponds.

Module Output Ports

• Output legend [Field] Outputs the legend as a field to allow texturing
• Title Output [String] Can be connected to the 3d estimation, 3D_Geology Map, and surface from horizons(s) modules.
• Output Object [Renderable]: Outputs to the viewer.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Label Options: controls the legend labeling
• Scale Options: controls the legend size and placement

Text Formatting:

Text formatting can be performed with a very restrictive subset of Markdown Syntax

• Bold **bold text**

• Italic _italicized text_

• Headings (Larger and bolder text)

  • H1

  • H2

  • H3

The legend module is used to place a legend which help correlate colors to analytical values or materials . The legend shows the relationship between the selected data component for a particular module and the colors shown in the viewer. For this reason, the legend’s RED input port must be connected to the RED output port of a module which is connected to the viewer and is generally the dominant colored object in view.

Many modules with red output ports have a selector to choose which ONE of the nodal or cell data components are to be used for coloring. The name of the selected data component will be displayed as the Title of the legend if the Label Options are set to Automatic (default).

If the data component to be viewed is either Geo_Layer or Material_ID (for models where the grid is based upon geology), the Geologic legend Information port from gridding and horizons (or lithologic modeling) must also be connected to legend to provide the Geologic Layer (or material) names for automatic labeling. When this port is connected it will have no affect if any other data component is selected.

The minimum and maximum values are taken from the data input as defined in the datamap. Labels can be placed at user defined intervals along the color scale bar. Labels can consist of user input alphanumerical values or automatically determined numerical values.

Module Input Ports

• Geologic legend Information [Geology legend] Accepts the geologic material information from modules that read geologic data.
• Contour Levels [Contours]: Accepts an array of values representing values to be labeled in the legend.
• Input Object [Renderable]: Accepts the output of a module to which the legend corresponds.

Module Output Ports

• Output legend [Field] Outputs the legend as a field to allow texturing
• Title Output [String] Can be connected to the 3d estimation, 3D_Geology Map, and surface from horizons(s) modules.
• Output Object [Renderable]: Outputs to the viewer.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Label Options: controls the legend labeling
• Scale Options: controls the legend size and placement

Text Formatting:

Text formatting can be performed with a very restrictive subset of Markdown Syntax

• Bold **bold text**

• Italic _italicized text_

• Headings (Larger and bolder text)

  • H1

  • H2

  • H3

axes

General Module Function

The axes module is used to place 3D axes in the viewer scaled by the model data and/or user defined limits. Axes accepts data from many of the Subsetting and Processing modules and outputs directly to the viewer. Data passed to Axes should come from modules which have scaled or transformed the mesh data, for example explode_and_scale. Axes generated by axes and displayed in the viewer are transformable with other objects in the viewer.

The User interface to axes is very comprehensive. Each coordinate direction axis can be individually controlled. Axis labels and tick marks for each axes can be specified. The label font, label precision, label orientation, and other label parameters are all user specified. Many of the parameters do not have default values that will produce the desired results because many variables control how the axes should be defined.

axes requires a field input to position and size the axes. If you disconnect the (blue/black) field input port, you no longer lose the axes bounds values and your axes remain in place. This is useful when field data changes in an animation so that you don’t constantly recreate the axes.

Also, the size of text and tick marks is based on a percentage of the x-y-z extent of the input field. This now allows you to set the extent of one or more axes to zero so you can have a scale of only one or two dimensions.

Module Input Ports

• View[View] This is the primary Purple port which connects to the viewer to receive the extent of all objects in the viewer AND outputs the axes.
  • This port can be used as your only connection from axes to the viewer and no other connections are needed.
• Input Geologic Field [Field] Accepts a field to receive the extent
• Input Objects [Renderable]: Accepts a renderable output port to receive the extent
• Minor Ports not needed for most all cases
  • Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
  • Explode [Number] Accepts the Explode distance from other modules

Module Output Ports

• Output Object [Renderable] Outputs the axes to the viewer.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: controls the scaling and exploding
• Spatial Definition: Controls the extents and grid densities
• Display Settings: controls layer exploding and cell sets
• All Axes Settings: Controls parameters for XYZ simultaneously
• X Axes Settings: Controls parameters for X axis
• Y Axes Settings: Controls parameters for Y axis
• Z Axes Settings: Controls parameters for Z axis

in_view (Purple) : This port accepts the output of the viewer directly. It will draw the axes around everything displayed in the viewer. This port will only cause the module to run when the port is connected or when the “Accept Current Values” button is pressed. If the models coordinate extents are going to change often then another input port should be used.

objects_in (Red) : This port accepts any number of (Red) output ports from other modules. When any of those modules are run the axes module will run as well.

meshs_in (Blue/Black) : This port accepts any number of (Blue/Black) output ports from other modules. When any of those modules are run the axes module will run as well.

explode (Grey/Green) : This port accepts a float value representing the explode distance from explode_and_scale. If you have an explode distance set to anything but 0, the Z axis tick labels are not printed.

z_scale (Grey/Brown) : This port accepts a float value representing Z exaggeration of the model from modules like explode_and_scale to ensure that the Z axis is correctly labeled.

direction indicator

The direction indicator module is used to place a 3D North Arrow or Rose Compass in the 3D viewer scaled by the model data and/or user defined parameters.

Module Input Ports

• View[View] This is the primary Purple port which connects to the viewer to receive the extent of all objects in the viewer AND outputs the north arrow or compass rose.
  • This port can be used as your only connection from direction indicator to the viewer and no other connections are needed.
• Minor Ports not needed for most all cases
  • Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
  • Explode [Number] Accepts the Explode distance from other modules

Module Output Ports

• Output For Transform [Renderable] Provides an additional output port if you want to duplicate place_text’s output via a transform_group module.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: controls the scaling and positioning
• North Arrow Settings:
• Compass Rose Settings:

viewer to frame

The viewer to frame module is used to place a image of one viewer inside a second viewer’s non-transformable overlay. It is extremely easy to use.

There are sliders to adjust size and position.

Module Input Ports

• View [View] Connects to the viewer used as an overlay

Module Output Ports

• Output Object [Renderable] Outputs the input view as a 2D overlay in the viewer.

add_logo

The add_logo module is used to place a logo or other graphic object in the viewer’s non-transformable overlay. It is extremely easy to use. There are sliders to adjust size and position and a button to select the image file to use as a logo.

Module Input Ports

• View [View] Connects to the viewer

Module Output Ports

• Output Object [Renderable] Outputs the logo as a 2D overlay in the viewer.

titles

Titles connects to the red port on the viewer and provides a means to place text in the non-transformable 2D Overlay of the viewer. The text is not transformed by viewer transformations and is positioned using sliders in the Titles user interface.

Module Input Ports

• Input String [String] Accepts the string to display.
• Number 1 [Number]: Accepts a number used to construct a the title. (this is effectively a simple version of format_string
• Number 2 [Number]: Accepts a number used to construct a the title
• String 1 [String]: Accepts a number used to construct a the title

Module Output Ports

• Output Object [Renderable]: Outputs to the viewer. NOT REQUIRED when the View port is used.

Text Formatting:

Text formatting can be performed with a limited subset of Markdown Syntax.

• If you need multiple spaces or need to indent with spaces, you must use this instead of a space: ** **

  • 4 spaces in a row would be: ** ** ** ** ** ** ** **

• **bold** = bold

• _italics_ = italics

• Numbered List

  • 1. First Item
    2. Second Item
    3. Third Item
  • Only works with Left Justified text

• Bulleted List

  • • First Item
    • Second Item
    • Third Item
  • Only works with Left Justified text

• Monospaced the text to be monospaced is surrounded by *tick* marks

  • Note: This uses the Tick mark which is the character below the tilde "~"

• Horizontal Rule (line across entire width) ___

  • Note: three underscore characters

• Colored Text

• This is the default text, but<font color="#FF0000">these words are red.</font>

• Font Size

• Some big text in the middle

Font Change

• Some larger Monospaced Font text in the middle.
• <h?> … </h?> Heading (?= 1 for largest to 6 for smallest, eg h1)
• ** … ** Bold Text
• • … * Italic Text
• … Underline Text
• … Strikeout
• ^… Superscript - Smaller text placed below normal text
• _… Subscript - Smaller text placed below normal text
• … Small - Fineprint size text

3d titles

3d titles connects to the red port on the viewer and provides a means to place text in 3D space of your model. The text is transformed by viewer transformations and is positioned using X, Y & Z sliders in the Titles user interface.

Module Input Ports

• Input String [String] Accepts the string to display.

Module Output Ports

• Output Object [Renderable]: Outputs to the viewer. NOT REQUIRED when the View port is used.

place_text

place_text replaces both Text3D and MultiText3D and provides a means to interactively place 2D and 3D renderable text strings or to read a .PT File (or legacy .EMT file) to place the text.

Module Input Ports

• View [View] This is the primary Purple port which connects to the viewer to receive the extent of all objects in the viewer AND outputs the test.
• This port can be used as your only connection from place_text to the viewer and no other connections are needed.
• Minor Ports not needed for most all cases
  • Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
  • Explode [Number] Accepts the Explode distance from other modules

Module Output Ports

• Output For Transform [Renderable] Provides an additional output port if you want to duplicate place_text’s output via a transform_group module.
• Minor Ports not needed for most all cases
  • Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
  • Explode [Number] Outputs the Explode distance to other modules

interactive_labels

The interactive_labels module allows the user to place formatted labels at probed locations within the viewer. The data displayed is the data at the probed location

Module Input Ports

• Z Scale [Number / minor] Accepts Z Scale (vertical exaggeration) from other modules
• Number Variable [Number / minor] Accepts a number to be used in the expression
• Input String Variable [String / minor] Accepts a string to be used in the expression
• View [View / minor] Connects to the viewer to allow probing on all objects.

Module Output Ports

• Z Scale [Number / minor] Outputs Z Scale (vertical exaggeration) to other modules
• Output Number Variable [Number / minor] Outputs a number to be used in the expression
• Output String Variable [String / minor] Outputs a string to be used in the expression
• Output Object [Renderable] Outputs to the viewer.

format_string

format_string allows you to construct a complex string (for use in titles or as file names) using multiple string and numeric inputs. An expression determines the content of the output.

The Expression is treated as Python f-string which allows for the use of the variables with Python expressions.

Module Input Ports

• Date [Number] Accepts a date
• Number 1 [Number] Accepts a number
• Number 2 [Number] Accepts a number
• Number 3 [Number] Accepts a number
• Number 4 [Number] Accepts a number
• String 1 [String] An input string
• String 2 [String] An input string
• String 3 [String] An input string

Module Output Ports

• Output String [String] The resultant string output

Note: Strings cannot be formatted or subsetted

The available floating point presentation types are:

• ’e’ - Exponent notation. Prints the number in scientific notation using the letter ’e’ to indicate the exponent.
• ‘E’ - Exponent notation. Same as ’e’ except it converts the ’e+XX’ to uppercase ‘E+XX’ .
• ‘f’ - Fixed point. Displays the number as a fixed-point number.
• ‘g’ - General format. For a given precision p >= 1, this rounds the number to p significant digits and then formats the result in either fixed-point format or in scientific notation, depending on its magnitude.

  • The precise rules are as follows: suppose that the result formatted with presentation type ’e’ and precision p-1 would have exponent exp. Then if -4 <= exp < p, the number is formatted with presentation type ‘f’ and precision p-1-exp. Otherwise, the number is formatted with presentation type ’e’ and precision p-1. In both cases insignificant trailing zeros are removed from the significant, and the decimal point is also removed if there are no remaining digits following it.

    • Positive and negative infinity, positive and negative zero, and nans, are formatted as inf, -inf, 0, -0 and nan respectively, regardless of the precision.
    • A precision of 0 is treated as equivalent to a precision of 1.
    • The default precision is 6.
• ‘G’ - General format. Same as ‘g’ except switches to ‘E’ if the number gets to large.
• ’n’ - Number. This is the same as ‘g’, except that it uses the current locale setting to insert the appropriate number separator characters.
• ‘%’ - Percentage. Multiplies the number by 100 and displays in fixed (‘f’) format, followed by a percent sign.
• ’’ (None) - similar to ‘g’, except that it prints at least one digit after the decimal point.

The following are example formats and the resultant output:

• N1 = 3.141592654 | Expression set to {N1:.4f} | Result is 3.1416
• N1 = 12345.6789 | Expression set to {N1:.6e} | Result is 1.234568e+04
• N1 = 123456789.0123 | Expression set to {N1:.6G} | Result is 1.23457E+08
• N1 = 123456789.0123 | Expression set to {N1:.6g} | Result is 1.23457e+08
• N1 = 123456.0123 | Expression set to {N1:.6G} | Result is 123456
• N1 = 123456.0123 | Expression set to {N1:.9G} | Result is 123456.012
• N1 = 123456.0123 | Expression set to {N1:.5f} | Result is 123456.01230
• N1 = 0.893 | Expression set to {N1:.2%} | Result is 89.30%
• N1 = 3.141592654 | Expression set to {N1} | Result is 3.141592654

f-string examples:

• N1 = 3.06 | S1 = “TOTHC Above 3.060 mg/kg”

  • Expression set to {S1.split()[0]} above {N1*1000:,.0f} ug/kg
  • Result is TOTHC above 3,060 ug/kg

REFERENCE: https://www.python.org/dev/peps/pep-3101/

F-STRING REFERENCE: https://www.python.org/dev/peps/pep-0498/

Notes:

1. Because the format depends on the current locale, care should be taken when making assumptions about the output value. Field orderings will vary (for example, “month/day/year” versus “day/month/year”), and the output may contain Unicode characters encoded using the locale’s default encoding (for example, if the current locale is , the default encoding could be any one of , , or ; use to determine the current locale’s encoding).

2. The method can parse years in the full [1, 9999] range, but years < 1000 must be zero-filled to 4-digit width.

   Changed in version 3.2: In previous versions, method was restricted to years >= 1900.

   Changed in version 3.3: In version 3.2, method was restricted to years >= 1000.

3. When used with the method, the directive only affects the output hour field if the directive is used to parse the hour.

4. Unlike the module, the module does not support leap seconds.

5. When used with the method, the directive accepts from one to six digits and zero pads on the right. is an extension to the set of format characters in the C standard (but implemented separately in datetime objects, and therefore always available).

6. For a naive object, the and format codes are replaced by empty strings.

   For an aware object:

• • is transformed into a 5-character string of the form +HHMM or -HHMM, where HH is a 2-digit string giving the number of UTC offset hours, and MM is a 2-digit string giving the number of UTC offset minutes. For example, if returns , is replaced with the string .
• • If returns , is replaced by an empty string. Otherwise is replaced by the returned value, which must be a string.

  Changed in version 3.2: When the directive is provided to the method, an aware object will be produced. The of the result will be set to a instance.

7. When used with the method, and are only used in calculations when the day of the week and the year are specified.

Copyright ^© 2001-2014 Python Software Foundation; All Rights Reserved

external_faces

The external_faces module extracts external faces from a 2D or 3D field for rendering. external_faces produces a mesh of only the external faces of each cell set of a data set. Because each cell set’s external faces are created there may be faces that are seemingly internal (vs. external). This is especially true when external faces is used subsequent to a plume module on 3D (volumetric) input.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the subsetted field as faces.
• Output Object [Renderable]: Outputs to the viewer.

external_edges

The external_edges module produces a wireframe representation of of an unstructured cell data mesh. This is generally used to visualize the skeletal shape of the data domain while viewing output from other modules, such as plumes and surfaces, inside the unstructured mesh. external_edges produces a mesh of only the external edges which meet the edge angle criteria below for each cell set of a data set. Because each cell set’s external faces are used there may be edges that are seemingly internal (vs. external). This is especially true when external edges is used subsequent to a plume module on 3D (volumetric) input.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration).
• Input Field [Field] Accepts a data field from 3d estimation or other similar modules.

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Output Field [Field] Outputs the subsetted field as edges
• Output Object [Renderable]: Outputs to the viewer

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: controls the Z scaling and edge angle used to determine what edges should be displayed
• Data Selection: controls the type and specific data to be output or displayed

cross section

cross section creates a fence diagram along a user defined (x, y) path. The fence cross-section has no thickness (because it is composed of areal elements such as triangles and quadrilaterals), but can be created in either true 3D model space or projected to 2D space.

It receives a 3D field (with volumetric elements) into its left input port and it receives lines or polylines (from draw_lines, polyline processing, import_cad, isolines, import vector gis, or other sources) into its right input port. Its function is similar to buffer distance, however it actually creates a new grid and does not rely on any other modules (e.g. plume or plume_shell) to do the “cutting”. Only the x and y coordinates of the input (poly)lines are used because cross section cuts a projected slice that is z invariant. cross section recalculates when either input field is changed (and Run Automatically is on) or when the “Run Once” button is pressed.

If you select the option to “Straighten to 2D”, cross section creates a straightened fence that is projected to a new 2D coordinate system of your choice. The choices are XZ or XY. For output to ESRI’s ArcMAP, XY is required.

NOTE: The beginning of straightened (2D) fences is defined by the order of the points in the incoming line/polyline. This is done to provide the user with complete control over how the cross-section is created. However, if you are provided a CAD file and you do not know the order of the line points, you can export the CAD file using the write_lines module which provides a simple text file that will make it easy to see the order of the points.

Module Input Ports

• Input Field [Field] Accepts a volumetric data field.
• Input Line [Field] Accepts a field with one or more line segments for the creation of the fence cross-section. Only the XY coordinates are used. Data is not used.

Module Output Ports

• Output Field [Field] Outputs the field
• Output Object [Renderable]: Outputs to the viewer.

slice

The slice module allows you to create a subset of your input which is of reduced dimensionality. This means that volumetric, surface and line inputs will result in surface, line and point outputs respectively. This is unlike cut which preserves dimensionality.

The slice module is used to slice through an input field using a slicing plane defined by one of four methods

• 1. A vertical plane defined by an X or Easting coordinate

  2. A vertical plane defined by a Y or Northing coordinate

  3. A Horizontal plane defined by a Z coordinate

  4. An arbitrarily positioned Rotatable plane which requires:

     1. A 3D point through which the slicing plane passes. This point can be displayed using the Reference Spherewhose size, visibility and transparency can be controlled. Please note that the same slicing result can be achieved with an infinite number of 3D points, all of which would be on the same slicing plane.
     2. A Dip direction
     3. A Strike direction

Module Input Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Input Field [Field] Accepts a data field.

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Output Field [Field] Outputs the field
• Output Object [Renderable]: Outputs to the viewer.

isolines

The isolines module is used to produce lines of constant (iso)value on a 2D surface (such as a slice plane), or the external faces of a 3D surface, such as the external faces of a plume. The input data for isolines must be a surface (faces), it cannot be a volumetric data field. If the input is the faces of a 3D surface, then the isolines will actually be 3D in nature. Isolines can automatically place labels in the 2D or 3D isolines. By default isolines are on the surface (within it) and they have an elevated jitter level (1.0) to make them preferentially visible. However they can be offset to either side of the surface.

Module Input Ports

• Input Field [Field] Accepts a data field.
• Input Contour Levels [Contours]: Accepts an array of values representing values to place isolines

Module Output Ports

• Output Field [Field] Outputs the field with altered data min/max values
• Output Contour Levels [Contours]: Outputs an array of values representing values to be labeled in the legend.
• Output Object [Renderable]: Outputs to the viewer.

pcut

The cut module allows you to create a subset of your input which is of the same dimensionality. This means that volumetric, surface, line and point inputs will have subsetted outputs of the same object type. This is unlike slice which decreases dimensionality.

The cut module is used to cut away part of the input field using a cutting plane defined by one of four methods

The cut module cuts through an input field using a slicing plane defined by one of four methods

• 1. A vertical plane defined by an X or Easting coordinate

  2. A vertical plane defined by a Y or Northing coordinate

  3. A Horizontal plane defined by a Z coordinate

  4. An arbitrarily positioned Rotatable plane which requires:

     1. A 3D point through which the slicing plane passes. This point can be displayed using the Reference Spherewhose size, visibility and transparency can be controlled. Please note that the same slicing result can be achieved with an infinite number of 3D points, all of which would be on the same slicing plane.
     2. A Dip direction
     3. A Strike direction

The cutting plane essentially cuts the data field into two parts and sends only the part above or below the plane to the output ports (above and below are terms which are defined by the normal vector of the cutting plane). The output of cut is the subset of the model from the side of the cut plane specified.

Module Input Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Input Field [Field] Accepts a data field.

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Cut Field [Field] Outputs the field with “cut” data to later use for subsetting
• Output Field [Field] Outputs the subsetted field
• Output Object [Renderable]: Outputs to the viewer.

plume

The plume module creates a (same dimensionality) subset of the input, regardless of dimensionality. What this means, in other words, is that plume can receive a field (blue port) model with cells which are points, lines, surfaces and/or volumes and its output will be a subset of the same type of cells.

This module should not normally be used when you desire a visualization of a 3D volumetric plume but rather when you wish to do subsequent operations such as analysis, slices, etc.

Module Input Ports

• Input Field [Field] Accepts a data field.
• Isolevel [Number] Accepts the subsetting level.

Module Output Ports

• Output Field [Field] Outputs the subsetted field as a volume.
• Status [String / minor] Outputs a string containing a description of the operation being performed (e.g. TCE plume above 4.00 mg/kg)
• Isolevel [Number] Outputs the subsetting level.
• Plume [Renderable]: Outputs to the viewer.

intersection

intersection is a powerful module that incorporates some of the characteristics of plume, yet allows for any number of volumetric sequential (serial) subsetting operations.

The functionality of the intersection module can be obtained by creating a network of serial plume modules. The number of analytes in the intersection is equal to the number of plume modules required.

The intersection of multiple analytes and threshold levels can be equated to the answer to the following question (example assumes three analytes A, B & C with respective subsetting levels of a, b and c):

“What is the volume within my model where A is above a, AND B is above b, AND C is above c?”

The figure above is a Boolean representation of 3 analyte plumes (A, B & C). The intersection of all three is the black center portion of the figure. Think of the image boundaries as the complete extents of your models (grid). The “A” plume is the circle colored cyan and includes the green, black and blue areas. The intersection of just A & C would be both the green and black portions.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the subsetted field
• Output Object [Renderable]: Outputs to the viewer.

union

union is a powerful module that automatically performs for a large number of complex serial and parallel subsetting operations required to compute and visualize the union of multiple analytes and threshold levels. The functionality of the union module can be obtained by creating a network fragment composed of only plume modules. However as the number of analytes in the union increases, the number of plume modules increases very dramatically. The table below lists the number of plume modules required for several cases:

From the above table, it should be evident that as the number of analytes in the union increases, the computation time will increase dramatically. Even though union appears to be a single module, internally it grows more complex as the number of analytes increases.

The union of multiple analytes and threshold levels can be equated to the answer to the following question (example assumes three analytes A, B & C with respective subsetting levels of a, b and c):

“What is the volume within my model where A is above a, OR B is above b, OR C is above c?”

The figure above is a Boolean representation of 3 analyte plumes (A, B & C). The union of all three is the entire colored portion of the figure. Think of the image boundaries as the complete extents of your models (grid). The “A” plume is the circle colored cyan and includes the green, black and blue areas. The union of just A & C would be all colored regions EXCEPT the magenta portion of B.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the subsetted field
• Output Object [Renderable]: Outputs to the viewer.

subset by expression

The subset by expression module creates a subset of the input grid with the same dimensionality. What this means, in other words, is that plume can receive a field (blue port) model with cells which are points, lines, surfaces and/or volumes and its output will be a subset of the same type of cells.

subset by expression is different from plume in that it outputs entire cells making its output lego-like.

It uses a mathematical expression allowing you to do complex subsetting calculations on coordinates and MULTIPLE data components with a single module, which can dramatically simplify your network and reduce memory usage. It has 2 floating point variables (N1,N2) which are setup with ports so they can be easily animated.

Subset By: You can specify whether the subsetting is based on either Nodal data or Cell data.

Expression Cells to Include: Is a Python expression where you can specify whether the subsetting of cells requires all nodes to match the criteria for a cell to be included or if ANY nodes match, then the cell will be included. The second option includes more cells.

Operators:

• == Equal to
• < Less than

• Greater Than

• <= Less than or Equal to

• = Greater Than or Equal to

• or
• and
• in (as in list)

Example Expressions:

• If Nodal data is selected:
  • D0 >= N1 All nodes with the first analyte greater than or equal to N1 will be used for inclusion determination.
  • (D0 < N1) or (D1 < N2) All nodes with the first analyte less than or equal to N1 OR the second analyte less than or equal to N2 will be used for inclusion determination.
• If Cell data is selected:
  • D1 in [0, 2] where D1 is Layer will give you the uppermost and third layers.
  • D1 in [1] where D1 is Layer will give you the middle layer.
  • D1 == 0 where D1 is Layer will give you the uppermost layer
  • D1 >= 1 where D1 is Layer will give you all but the uppermost layer

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the subsetted field as a volume.
• Status [String / minor] Outputs a string containing a description of the operation being performed (e.g. TCE plume above 4.00 mg/kg)
• Isolevel [Number] Outputs the subsetting level.
• Plume [Renderable]: Outputs to the viewer.

footprint

The footprint module is used to create the 2D footprint of a plume_shell. It creates a surface at the specified Z Position with an x-y extent that matches the 3D input. The footprint output does not contain data, but data can be mapped onto it with external kriging.

NOTE: Do not use adaptive gridding when creating the 3D grid to be footprinted and mapping the maximum values with krig_2d (as in the example shown below). Footprint will produce the correct area, but krig_2d will map anomalous results when used with 3d estimation’s adaptive gridding.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the subsetted field.
• Output Object [Renderable]: Outputs to the viewer.

NOTE: Creating a 2D footprint with the maximum data within the plume volume mapped to each x-y location requires the external data and external gridding options in krig_2d. A typical network and output is shown below.

slope_aspect_splitter

The slope_aspect_splitter module will split an input field into two output fields based upon the slope and/or aspect of the external face of the cell and the subset expression used. The input field is split into two fields one for which all cells orientations are true for the subset expression, and another field for which all cells orientations are false for the subset expression.

All data from the original input is preserved in the output.

Flat Surface Aspect: If you have a flat surface then a realistic aspect can not be generated. This field lets you set the value for those sells.

1. To output all upward facing surfaces: use the default subset expression of SLOPE < 89.9. If your object was a perfect sphere, this would give you most of the upper hemisphere. Since the equator would be at slope of 90 degrees and the bottom would >90 degrees.

(Notice there is potential for rounding errors use 89.9 instead of 90)

Note: If your ground surface is perfectly flat and you wanted only it, you could use SLOPE < 0.01, however in the real world where topography exists, it can be difficult if not impossible to extract the ground surface and not get some other bits of surfaces that also meet your criteria.

2. General expression (assuming a standard cubic building)

A) SLOPE > 0.01 (Removes the top of the building)

B) SLOPE > 0.01 and SLOPE < 179.9 (Removes the top and bottom of the building)

3. Since ASPECT is a variable it must be defined for each cell. In cells with a slope of 0 or 180 there would be no aspect without our defining it with the flat surface aspect field

4. Units are always degrees. You could change them to radians if you want inside the expression. (SLOPE * PI/180)

Module Input Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Input Field [Field] Accepts a data field.
• Number Variable 1 [Number] Accepts the first numeric value for the slope or aspect expression
• Number Variable 2 [Number] Accepts the second numeric value for the slope or aspect expression

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Output True Field [Field] Outputs the field which matches the subsetting expression
• Output False Field [Field] Outputs the opposite of the true field

crop_and_downsize

The crop_and_downsize module is used to subset an image, or structured 1D, 2D or 3D mesh (an EVS “field” data type with implicit connectivity). Similar to cropping and resizing a photograph, crop_and_downsize sets ranges of cells in the I, J and K directions which create a subset of the data. When used on an image (which only has two dimensions), crop removes pixels along any of the four edges of the image. Additionally, crop_and_downsize reduces the resolution of the image or grid by an integer downsize value. If the resolution divided by this factor yields a remainder, these cells are dropped.

crop_and_downsize refers to I, J, and K dimensions instead of x-y-z. This is done because grids are not required to be parallel to the coordinate axes, nor must the grid rows, columns and layers correspond to x, y, or z. You may have to experiment with this module to determine which coordinate axes or model faces are being cropped or downsized.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the subsetted field
• Output Object [Renderable]: Outputs to the viewer.

select cell sets

select cell sets provides the ability to select individual stratigraphic layers, lithologic materials or other cell sets for output. If connected to explode_and_scale multiple select cell sets modules will allow selection of specific cell sets for downstream processing. One example would be to texture map the top layer with an aerial photo after one select cell sets and to color the other layers by data with a parallel select cell sets path. This can be accomplished by multiple explode_and_scale modules, but that would be much less efficient.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the subsetted field
• Output Object [Renderable]: Outputs to the viewer.

orthoslice

The orthoslice module is similar to the slice module, except limited to only displaying slice positions north-south (vertical), east-west (vertical) and horizontal. orthoslice subsets a structured field by extracting one slice plane and can only be orthogonal to the X, Y, or Z axis. Although less flexible in terms of capability, orthoslice is computationally more efficient.

The axis selector chooses which axis (I, J, K) the orthoslice is perpendicular to. The default is I. If the field is 1D or 2D, three values are still displayed. Select the values meaningful for the input data.

The plane slider selects which plane to extract from the input. This is similar to the position slider in slice but, since the input is a field, the selection is based on the nodal dimensions of the axis of interest. Therefore, the range is 0 to the maximum nodal dimension of the axis. For example, for an orthoslice through a grid with dimension 20 x 20 x 10, the range in the x and y directions would be 0 to 20.

edges

The edges module is similar to the External_Edges module in that it produces a wireframe representation of the nodal data making up an unstructured cell data mesh. There is however, no adjustment of edge angle and therefore only allows viewing of all grid boundaries (internal AND external) of the input mesh. The edges module is useful in that it is able to render lines around adaptive gridding locations whereas external_edges does NOT render lines around this portion of the grid.

bounds

bounds generates lines and/or surfaces that indicate the bounding box of a 3D structured field. This is useful when you need to see the shape of an object and the structure of its mesh. This module is similar to external_edges (set to edge angle = 60), except, bounds allows for placing faces on the bounds of a model.

bounds has one input ports. Data passed to the first port (closest to the left) must contain any type of structured mesh (a grid definable with IJK resolution and no separable layers). Node_Data can be present, but is only used if you switch on Data.

distance to 2d area

distance to 2d area receives any 3D field into its left input port and it receives triangulated polygons (from triangulate_polygon, or other sources) into its right input port. Its function is similar to buffer distance or distance to shape. It adds a data component to the input 3D field and using plume_shell, you can cut structures inside or outside of the input polygons. Only the x and y coordinates of the polygons are used because distance to 2d area cuts a projected slice that is z invariant. distance to 2d area recalculates when either input field is changed or the “Accept” button is pressed.

Module Input Ports

• Input Field [Field] Accepts a data field.
• Input Area [Field] Accepts a field with the area to include/exclude

Module Output Ports

• Output Field [Field] Outputs the field with area data to allow subsetting

The first thing to know, is that distance to 2d area does not cut.

It provides data with which you can then subset using other modules like plume or intersection.

Without the subsetting modules AFTER distance to 2d area, you would see no affect of having distance to 2d area in your application other than it adds a new nodal data component called distance to 2d area (or whatever you’ve renamed your module to be).

distance to 2d area needs a SURFACE as its input. It does not care where that surface comes from and it certainly does not need to be from a DWG file. The surface can be complex, meaning that it can have holes in it, or it can be separate disjoint pieces of surface(s).

If you’re starting with lines, it is required that the lines form a closed polyline. It is not enough that the lines appear to be a closed path, they must be truly closed, with each successive segment precisely connected to the last and next. CAD files are often poorly drawn and are not closed (though they can be well drawn and properly closed also).

Our draw_lines module can certainly be used to create a Closed polyline, but you must make sure to turn on the “Closed” toggle for each line segment to ensure it is closed.

Once you have one or more closed polylines, you will need to pass those through triangulate_polylines modules to create a TIN surface from the closed polylines. You should confirm (by connecting it to the viewer) that you are getting the correct surface before proceeding to distance to 2d area. If triangulate_polylines will not run, your lines are not closed.

Once you have your surface(s) and you pass that to the right input port of distance to 2d area, the output of distance to 2d area is data with which you can subset your original model. The data is zero (0.0) at the boundaries of your surface: is less than zero (negative) inside the surface; and is greater than zero (positive) outside of the surface. To get everything inside, you need to choose “Below Level” in the subsetting modules rather than the Default “Above Level”.

distance to surface

distance to surface receives any 3D field into its left input port and it receives a surface (from create_tin, surface from horizons, slice, etc.) into its right input port. Its function is similar to distance to shape. It adds a data component to the input 3D field referencing the cutting surface. With this new data component you can use a subsettting module like plume to pass either side of the 3D field as defined by the cutting surface, thereby allowing cutting of structures along any surface. The surface can originate from a TIN surface, a slice plane or a geologic surface. The cutting surface can be multi-valued in Z, which means the surface can have instances where there are more one z value for a single x, y coordinate. This might occur with a wavy fault surface that is nearly vertical, or a fault surface with recumbent folds.

distance to surface recalculates when either input field is changed or the “Accept” button is pressed.

The general approach with distance to surface is:

• Create a cutting surface representing either a fault plane, a scouring surface (unconformity), or an excavation.
• Create a 3D model of the object you wish to cut.
• Pass the 3D model into the left port of distance to surface, and the cutting surface to the right port of distance to surface and hit accept.

Module Input Ports

• Input 3D Field [Field] Accepts a data field.
• Input Surface [Field] Accepts a field with the surface to cut the input volume/surface

Module Output Ports

• Output Field [Field] Outputs the field with distance to surface data to allow subsetting

distance to shape

distance to shape receives any 3D field into its input port and outputs the same field with an additional data component. Using plume_shell, you can cut structures with either a cylinder or rotated rectangle. The cutting action is z invariant (like a cookie cutter). Depending on the resolution of the input field, rectangles may not have sharp corners. With rectilinear fields (and non-rotated rectangles), the threshold module can replace plume_shell to produce sharp corners (by removing whole cells). plume can be used to output 3D fields for additional filtering or mapping.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the field with data to allow subsetting.

buffer distance

buffer distance receives any 3D field into its left input port and it receives polylines (from read_lines, import vector gis, import_cad, isolines, or other sources) into its right input port. Its function is similar to distance to shape. It adds a data component to the input 3D field and using plume_shell, you can cut structures along the path of the input polylines. Only the x and y coordinates of the polylines are used because buffer distance creates data to cut a projected region that is z invariant. buffer distance recalculates when either input field is changed or the “Execute” button is pressed. “Thick Fences” can be produced with the output of this module.

Module Input Ports

• Input Field [Field] Accepts a data field.
• Input Fence LIne [Field] Accepts a field with the line(s) to cut the input volume/surface

Module Output Ports

• Output Field [Field] Outputs the field with distance to path(s) data to allow subsetting

distance to tunnel center

The distance to tunnel center module is similar to the distance to surface module in that it receives any 3D field into its left input port, BUT instead of a surface, it receives a line (along the trajectory of a tunnel, boring or mineshaft) into its right input port. The distance to tunnel center module then cuts a cylinder, of user defined radius, along the line trajectory. The algorithm is identical in concept to distance to surface in that it adds a data component to the input 3D field referencing the distance from the line (trajectory). With this new data component you can use a subsetting module like plume_volume to pass either portion of the 3D field (inside the cylinder or outside the cylinder), thereby allowing cutting tunnels along any trajectory. The trajectory line can originate from any one of a number of sources such read_lines, import cad or import vector gis.

The general approach is to subset the distance to tunnel center data component with either constant_shellor plume_volume. The choice of 1.0 for the subsetting level will result in cutting AT the user radius, while less than 1.0 is inside the cylinder wall and greater than 1.0 is outside the cylinder wall.

Module Input Ports

• Input Field [Field] Accepts a data field.
• Input Tunnel Line [Field] Accepts a field with the surface to cut the input volume/surface

Module Output Ports

• Output Field [Field] Outputs the field with distance to tunnel line data to allow subsetting

overburden

The overburden module computes the complete volume required to excavate a plume or ore body given the pit wall slope (measured from vertical) and the excavation digging accuracy (we refer to as buffer size).

overburden receives any 3D field into its input port and outputs the same field with an additional data component. Its function is similar to distance to shape, but instead involves computing a new data component based on the nodal values in the 3D field and two user defined parameter values called Wall Slope and buffer size (addressing excavation accuracy). The data component is subset according to a concentration input (based on the subsetting level you want excavated). For example, once overburden has been run for GOLD at a 45 degree pit wall slope, the user would select 45-deg:overburden_GOLD and subset all data below 1 ppm to render a 45 degree slope pit which would excavate everything higher than 1 ppm concentration. A volumetrics calculation could be made on these criteria which would encompass the excavation and the ore body above 1 ppm.

NOTES:

• It is much safer and more understandable to work at Z Scale = 1. Otherwise, the apparent angle of your pit will be very different than the input angle

  • As the Z Scale increases, the angle of pit sidewalls looks more vertical, since the tangent of the apparent angle is the tangent of the actual angle multiplied times the Z Scale.

• The overburden module must be placed before any scaling modules (such as explode_and_scale) to ensure an accurate slope angle during computations and subsequent visualizations.

• The grid resolution and resulting cell aspect ratios are very important.

  • You cannot see any pit wall slope differences if those differences create a slope which is less than one cell wide from the bottom of the pit to the top.
  • Therefore, very high resolutions in X-Y are needed for large sites with shallow pits. Expect long run times for overburden.

Note on angles: Angles are defined from the vertical and are specified in degrees.

• A vertical wall pit is created with an angle of Zero (0.0) degrees
• A 2:1 pitch slope from horizontal would be an angle whose arctangent = 2.0. This is 63.4 degree from horizontal and therefore you would enter 26.6 degrees (from vertical)

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the enhanced field with overburden data

Create Buffer Around Plume - This toggle determines if the overburden computations are rigorous and determine the buffer on all side of the plume (ore body). If this is off, the module runs much quicker.

Buffer Size - An accuracy level resulting in the amount of excavation outside the subsetting level of interest. For example, a type-in of 10.0 would result in 10 feet of over-excavation from the subsetting level of interest.

Overburden creates a data component name that includes the wall slope, module name (including #1 or #2 if there are more than one copy in your application), and original data component (analyte) name. (i.e. 30-deg:overburden#1 of Benzene)

The overburden data component may be subset by modules such as plume, isosurface, plume_shell, etc.

node_computation

The node_computation module is used to perform mathematical operations on nodal data fields and coordinates. Data values can be used to affect coordinates (x, y, or z) and coordinates can be used to affect data values.

Up to two fields can be input to node_computation. Mathematical expressions can involve one or both of the input fields**. Fields must be identical grids. This means they must have the same number of nodes and cells, otherwise the results will not make sense.**

Nodal data input to each of the ports is normally scalar, however if a vector data component is used, the values in the expression are automatically the magnitude of the vector (which is a scalar). If you want a particular component of a vector, insert an extract_scalar module before connecting a vector data component to node_computation. The output is always a scalar. If a data field contains more than one data component, you may select from any of them.

Module Input Ports

• Input Field 1[Field] Accepts a data field.
• Input Field 2[Field / minor] Accepts a data field.
• Input Value N1 [Number / minor] Accepts a number to be used in the field computations.
• Input Value N2 [Number / minor] Accepts a number to be used in the field computations.
• Input Value N3 [Number / minor] Accepts a number to be used in the field computations.
• Input Value N4 [Number / minor] Accepts a number to be used in the field computations.

Module Output Ports

• Output Field [Field] Outputs the subsetted field as faces.
• Output Value N1 [Number / minor] Outputs a number used in the field computations.
• Output Value N2 [Number / minor] Outputs a number used in the field computations.
• Output Value N3 [Number / minor] Outputs a number used in the field computations.
• Output Value N4 [Number / minor] Outputs a number used in the field computations.
• Output Object [Renderable]: Outputs to the viewer.

Module Parameters

• Data Definitions: You can have more than one new data component computed from each pass of node_computation. By default there is only Data0.
  • Add/Remove buttons allow you to add or remove Data Definitions
• Name: The data component name (e.g. Total Hydrocarbons)
• Units : The units of the data component (e.g. mg/kg)
• Log Process: When your input data is log processed, the values within node_computation will always be exponentiated.
  • In other words, even when your data is log processed, you will always see actual (not log) values.
  • This toggle should be ON whenever you are dealing with Log data.
  • If you want to perform math operations on the “Log” data, you must take the log of the An* or Bn* values within node_computation
  • If you do take the log of those values, you should always exponentiate the end results before exiting node_computation.

Each nodal data component from Input Field 1 is assigned as a variable to be used in the script. For example:

• An0 : First input data component
• An1 : Second input data component
• An2 : Third input data component
• An^N^ : Nth input data component

The min and max of these components are also added as variables :

• Min_An0 : Minimum of An0 data
• Max_An0 : Maximum of An0 data
• Min_An* : Minimum of An* data

For Input Field 2 the variable names change to:

• Bn0 : First input data component
• Bn1 : Second input data component
• Bn2 : Third input data component
• Bn^N^ : Nth input data component

An interesting and simple example of using node_computation can be found here.

The equation(s) used to modify data and/or coordinates must be input as part of a Python Script. The module will generate a default script and by modifying only one line (for the X coordinate)we get:

which with the following application:

Gives us the ability to view densely sampled data as line plots beside each boring

cell_computation

The cell_computation module is used to perform mathematical operations on cell data in fields. Unlike node_compuation, it cannot affect coordinates.

Though data values can’t be used to affect coordinates (x, y, or z), the cell center (average of nodes) coordinates can be used to affect data values.

Up to two fields can be input to cell_computation. Mathematical expressions can involve one or both of the input fields.

Cell data input to each of the ports is scalar.

If a data field contains more than one data component, you may select from any of them.

Module Input Ports

• Input Field 1[Field] Accepts a data field.
• Input Field 2[Field / minor] Accepts a data field.
• Input Value N1 [Number / minor] Accepts a number to be used in the field computations.
• Input Value N2 [Number / minor] Accepts a number to be used in the field computations.
• Input Value N3 [Number / minor] Accepts a number to be used in the field computations.
• Input Value N4 [Number / minor] Accepts a number to be used in the field computations.

Module Output Ports

• Output Field [Field] Outputs the subsetted field as faces.
• Output Value N1 [Number / minor] Outputs a number used in the field computations.
• Output Value N2 [Number / minor] Outputs a number used in the field computations.
• Output Value N3 [Number / minor] Outputs a number used in the field computations.
• Output Value N4 [Number / minor] Outputs a number used in the field computations.
• Output Object [Renderable]: Outputs to the viewer.

Each cell data component from Input Field 1 is assigned as a variable to be used in the script. For example:

• An0 : First input data component
• An1 : Second input data component
• An2 : Third input data component
• An* : Nth input data component

The min and max of these components are also added as variables :

• Min_An0 : Minimum of An0 data
• Max_An0 : Maximum of An0 data
• Min_An* : Minimum of An* data

For Input Field 2 the variable names change to:

• Bn0 : First input data component
• Bn1 : Second input data component
• Bn2 : Third input data component
• Bn* : Nth input data component

combine_nodal_data

The combine_nodal_data module is used to create a new set of nodal data components by selecting components from up to six separate input data fields. The mesh (x-y-z coordinates) from the first input field, will be the mesh in the output. The input fields should have the same scale and origin, and number of nodes in order for the output data to have any meaning. This module is useful for combining data contained in multiple field ports or files, or from different Kriging modules.

Module Input Ports

• Model Field [Field] Accepts a field with data whose grid will be exported.
• Input Field 1 [Field] Accepts a data field.
• Input Field 2 [Field] Accepts a data field.
• Input Field 3 [Field] Accepts a data field.
• Input Field 4 [Field] Accepts a data field.
• Input Field 5 [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the field with selected data
• Output Object [Renderable]: Outputs to the viewer.

interpolate data

The interpolate data module interpolates nodal and/or cell data from a 3D or 2D field to either a 2D mesh or 1D line. Typical uses of this module are mapping of data from a 3D mesh onto a geologic surface or a 2D fence section. In these applications the 2D surface(s) simply provide the new geometry (mesh) onto which the adjacent nodal values are interpolated. The primary requirement is that the data be equal or higher dimensionality than the mesh to be interpolated onto. For instance, if the user has a 2D surface with nodal data (perhaps z values), then a 1D line may be input and the nearest nodal values from the 2D surface will be interpolated onto it.

NOTE: This module supplants interpolate nodal data and interpolate cell data.

Module Input Ports

• Input Data Field [Field] Accepts a data field.
• Input Destination Field [Field] Accepts a field onto which the data will be interpolated

Module Output Ports

• Output Field [Field] Outputs the field Destination Field with new data
• Output Object [Renderable]: Outputs to the viewer.

The compute thickness module allows you to compute the thickness of complex plumes or cell sets such as lithologic modeling’s materials.

Module Input Ports

• Input Field The field to map thickness data onto
• Input Volume The (volumetric) field to determine thickness data from

Module Output Ports

• Output Field The surface (or 3D object) with mapped thickness data

Important Features and Considerations

The right input port must have a 3D field as input.

• There is no concept of thickness associated with 2D or 3D surfaces
• Volumetric inputs can be plume_shell or intersection_shell objects which are hollow.
  • Thickness will be determined based upon the apparent thickness of the plume elements.
  • When 3D Shells are input, they must be closed objects.

Determining thickness of arbitrary volumetric objects is a very computationally intensive operation. You can use this module to compute thickness in two primary ways:

• Compute the thickness distribution of a 3D object and project that onto a 2D surface (generally at the ground surface)
  • A surface (such as from geologic surface) would connect to the first (left) input port
  • The volumetric object connects to the second (right) input port
• Compute the thickness distribution of a 3D object and project that onto the same object
  • The volumetric object connects to the first (left) input port
  • The same volumetric object connects to the second (right) input port

Note: In all cases run times can be long. Coarser grids and the first option will run faster, but the complexity and resolution of the volumetric object will be the major factor in the computation time.

translate by data

The translate by data module accepts nearly any mesh and translates the grid in x, y, or z based upon either a nodal or cell data component or a constant.

The interface enables changing the Scale Factor for z translates to accommodate an overall z exaggeration in your applications. This module is most useful when used with the import vector gis module to properly place polygonal shapefile cells at the proper elevation.

Warning: The scale factor is always applied. If translating along any axis other than z, it is unlikely that you want to use the Z Exaggeration factor used elsewhere in your application.

• When translating by a Constant, the amount is affected by the Z Scale Factor.
• When translating by Cell Data, a radio box appears to allow specification of the cell data component
• When translating by Node Data, a radio box appears to allow specification of the nodal data component

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration).
• Input Field [Field] Accepts a data field from 3d estimation or other similar modules.

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Output Field [Field] Outputs the subsetted field
• Scale Link
• Output Object [Renderable]: Outputs to the viewer

cell data to node data

The cell data to node data module is used to translate cell data components to nodal data components. Cell data components are data components which are associated with cells rather than nodes. Most modules in EVS that deal with analytical or continuum data support node based data. Therefore, cell data to node data can be used to translate cell based data to a nodal data structure consistent with other EVS modules.

Module Input Ports

• Input Field [Field] Accepts a field with cell data.

Module Output Ports

• Output Field [Field / Minor] Outputs the field with cell data converted to nodal data
• Output Object [Renderable]: Outputs to the viewer.

The node data to cell data module is used to translate nodal data components to cell data components. Cell data components are data components which are associated with cells rather than nodes. Most modules in EVS that deal with analytical or continuum data support node based data, and those that deal with geology (lithology) tend to use cell data. Therefore, node data to cell data can be used to translate nodal data to cell data.

Module Input Ports

• Input Field [Field] Accepts a field with nodal data.

Module Output Ports

• Output Field [Field / Minor] Outputs the field with nodal data converted to cell data
• Output Object [Renderable]: Outputs to the viewer.

shrink cells

The shrink cells module produces a mesh containing disjoint cells which can be optionally shrunk relative to their geometric centers. It creates duplicate nodes for all cells that share the same node, making them disjoint. If the shrink cells toggle is set, the module computes new coordinates for the nodes based on the specified shrink factor (which specifies the scale relative to the geometric centers of each cell). The shrink factor can vary from 0 to 1. A value of 0 produces non-shrunk cells; 1 produces completely collapsed cells (points). This module is useful for separate viewing of cells comprising a mesh.

Module Input Ports

• Input Field [Field] Accepts a field

Module Output Ports

• Output Field [Field / Minor] Outputs the field with modified cells
• Output Object [Renderable]: Outputs to the viewer

cell centers

cell centers module produces a mesh containing Point cell set, each point of which represents a geometrical center of a corresponding cell in the input mesh. The coordinates of cell centers are calculated by averaging coordinates of all the nodes of a cell. The number of nodes in the output mesh is equal to number of cells in the input mesh. If the input mesh contains Cell_Data it becomes a Node_Data in the output mesh with each node values equal to corresponding cell value. Nodal data is not output directly. You can use this module to create a position mesh for the glyphs at nodes module. You may also use this module as mesh input to the interpolate data module, then send the same nodal values as the input grid, to create interpolated nodal values at cell centroids.

Module Input Ports

• Input Field [Field] Accepts a field.

Module Output Ports

• Output Field [Field / Minor] Outputs the field as points representing the centers of the cells.
• Output Object [Renderable]: Outputs to the viewer.

This module allows you to assign data and subset all (or selected) discrete (disconnected) regions of plumes or lithologic materials.

• OVERVIEW: When we create subsets of models, either based upon analytical data, stratigraphic or lithologic modeling these subsets often exist as several disjoint pieces.

  • In the case of analytical (e.g., contaminant) plumes, the number and size of regions (pieces) can strongly depend on the subsetting level.
  • With lithologic models, the number and size of the regions depends on the complexity of the lithologic data and the modeling parameters.

• FUNCTION: The connectivity assessment module assigns a new data component to these dis-connected regions.

  • The pieces are sorted based upon the number of cells in each piece.

    • This is generally well correlated to the volume of that regions, but it is definitely possible that the region with the most cells may not have the greatest volume.

  • The highest cell count region is assigned to 0 (zero) and regions with descending cell counts are assigned higher integer values.

• PARAMETERS:

  1. Merge Cell Sets (toggle): Merges cell sets such as stratigraphic layers or lithologic materials. Generally should be on when dealing with analytical data.

  2. Assessment Mode: Determines the criteria for subsetting of regions and/or assigning data

     1. Add Region ID Data: Does not subset, but assigns Cell Data corresponding to cell counts
     2. Subset By Region ID(s)
     3. Region Closest to Point
     4. Region with most cells: Outputs Region ID = 0 without assigning data.

  3. Point Coordinate: Is the X, Y, Z coordinate to be used for “Closest region”

  4. Region IDs: The list of regions to include in the output if Selection Mode is set to “Subset By Region ID”

read evs field

read evs field reads a dataset from the primary and legacy file formats created by write evs field.

• .EF2: The only Lossless format for models created in 2024 and later versions
• .eff ASCII format, best if you want to be able to open the file in an editor or print it. For a description of the .EFF file formats click here.
• .efz GNU Zip compressed ASCII, same as .eff but in a zip archive
• .efb binary compressed format, the smallest & fastest format due to its binary form

Output Quality: An important feature of read evs field is the ability to specify two separate files which correspond to High Quality (e.g. fine grids) and Low Quality (e.g. coarse grids a.k.a. fast).

You can see that read evs field is specifying two different EFB files. The Output Quality is set to Highest Quality and is Linked (black circle). The viewer shows:

If we change the Output Quality on the Home Tab

It changes the setting in read evs field and the viewer changes to show:

Though you “can” change the Output Quality in read evs field, it is best to change it on the Home Tab to make sure that all read evs field modules in your application will have the same setting. This is not relevant to this simple application, but if we were using a cutting surface (saved as fine and coarse EFBs) and doing distance to surface operations on a very large grid, this synchronization would be important.

read evs field effectively has explode_and_scale and an external_faces module built in. This allows the module to perform:

• Z Scaling
• Exploding
• Nodal or Cell data selection
• Selection of cell_sets

Module Output Ports

• Geologic legend Information [Geology legend] Supplies the geologic material information for the legend module.
• Output [Field] Outputs the saved field.
• File Notes [String / minor] Outputs a string to document the settings used to create the field.
• Output Object [Renderable]: Outputs to the viewer.

• EFF File

  EVS Field File Formats and Examples EVS Field file formats supplant the need for UCD, netCDF, Field (.fld), EVS_Geology by incorporating all of their functionality and more in a new file format with three mode options. .eff ASCII format, best if you want to be able to open the file in an editor or print it

import vtk

import vtk reads a dataset from any of the following 9 VTK file formats. Please note that VTK’s file formats do not include coordinate units information, not analyte units. There is a parameter which allows you to specify coordinate units (meters are the default).

• vtk: legacy format
• vtr: Rectilinear grids
• vtp: Polygons (surfaces)
• vts: Structured grids
• vtu: Unstructured grids
• pvtp: Partitioned Polygons (surfaces)
• pvtr: Partitioned Rectilinear grids
• pvts: Partitioned Structured grids
• pvtu: Partitioned Unstructured grids

Module Output Ports

• Output [Field] Outputs the saved field.
• Output Object [Renderable]: Outputs to the viewer.

import cad

General Module Function

The import cad module will read the following versions of CAD files:

• AutoCAD DWG and DXF files through AutoCAD 2021 (version 24.0)
• Bentley Microstation DGN files through Version 8.

This module provides the user with the capability to integrate site plans, buildings, and other 2D or 3D features into the EVS visualization, to provide a frame of reference for understanding the three dimensional relationships between the site features, and characteristics of geologic, hydrologic, and chemical features. The drawing entities are treated as three dimensional objects, which provides the user with a lot of flexibility in the placement of CAD objects in relation to EVS objects in the visualization. The project onto surface and geologic_surfmap modules allow the user to drape CAD line-type entities (not 3D-Faces) onto three dimensional surfaces.

Virtually all AutoCAD object types are supported including points, lines (of all types), 3D surface objects and 3D volumetric objects.

AutoCAD drawings can be drawn in model space (MSPACE) or paper space (PSPACE). Drawings in paper space have a defined viewport which has coordinates near the origin. When read into EVS this creates objects which are far from your true model coordinates. For this reason, all drawings for use in our software should be in model space.

Module Side Port

• Z Scale Use the Global Z Scale and avoid using this port in general: [Number] Accepts Z Scale (vertical exaggeration) from other modules.

Module Output Ports

• Output [Field] Outputs the CAD layers.
• Output Object [Renderable]: Outputs to the viewer

import vector gis

The import vector gis module reads the following vector file formats: ESRI Shapefile (*.shp); Arc/Info E00 (ASCII) Coverage (*.e00); Atlas BNA file (*.bna); GeoConcept text export (*.gxt); GMT ASCII Vectors (*.gmt); and the MapInfo TAB (*.tab) format.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Output [Field] Outputs the GIS data.
• Output Object [Renderable]: Outputs to the viewer

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties controls Z Scale
• Data Processing: controls clipping, processing (Log) and clamping of input data

import raster as horizon

The import raster as horizon module reads several different raster format files in EVS Geology format. These formats include DEMs, Surfer grid files, Mr. Sid files, ADF files, etc.. Multiple import raster as horizon modules can be combined with combine horizons into a 3D geologic model. Alternatively, a single file can be displayed as a surface (with surfaces from horizons) or you can export its coordinates (with export nodes) to use the values in a GMF file.

Module Output Ports

• Geologic legend Information [Geology legend] Supplies the geologic material information for the legend module.
• Output Geologic Field [Field / minor] Outputs a 2D grid with data similar in functionality to gridding and horizons

buildings

The buildings module reads C Tech’s .BLDG file and creates various 3D objects (boxes, cylinders, wedge-shapes for roofs, simple houses etc.), and provides a means for scaling the objects and/or placing the objects at user specified locations. The objects are displayed based on x, y & z coordinates supplied by the user in a .bldg file, with additional scaling option controls on the buildings user interface.

Each object is made up of 3D volumetric elements. This allows for the output of buildings to be cut or sliced to reveal a cross section through the buildings.

Selecting the “Edit Buildings” toggle will open an additional section which provides the ability to interactively create 3D buildings in your project.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
• View [View] Connects to the viewer to allow interactive building creation.

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Output [Field] Outputs the buildings as a field which can be sliced, cut or further subsetted.
• Output Object [Renderable]: Outputs to the viewer

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties controls Z Scale and file input and output
• Default Building Settings: Defines the default values when a building is interactive created
• Building Settings: Shows the parameters for all buildings.

• Sample Buildings File

  Sample Buildings File Below is an example buildings file. Note that the last 4 columns are optional and contain RGB color values (three numbers from zero to 1.0) and/or a building ID number that can be used for coloring. If only color values are supplied (3 numbers) the ID is automatically determined by the row number. If four numbers are provided it is assumed that the last one is the ID. If only one number is provided it is the ID.

read_lines

The read_lines module is used to visualize a series of points with data connected by lines. read_lines accepts three different file formats, with the APDV file format the lines are connected by boring ID, with the ELF (EVS Line File) format each line is made by defining the points that make up the line, and with the SAD (Strike and Dip) file format, there is a choice to connect each sample by ID or by Data Value.

SAD files connect by ID – If a *.sad file has been read the lines will be connected by ID.

SAD files connect by Data – If a *.sad file has been read the lines will be connected by the data component.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Output Field [Field] Outputs the subsetted field as faces.
• Output Object [Renderable]: Outputs to the viewer.

EVS Line File Example

Discussion of EVS Line Files

EVS line files contain horizontal and vertical coordinates, which describe the 3-D locations and values of properties of a system. Line files must be in ASCII format and can be delimited by commas, spaces, or tabs. They must have an .elf suffix to be selected in the file browsers of EVS modules. Each line of the EVS line file contain the coordinate data for one sampling location and up to 300 (columns of) property values. There are no computational restrictions on the number of lines that can be included in a file.

EVS Line Files

EVS Line Files consist of file tags that delineate the various sections of the file(s) and data (coordinates, nodal and/or cell data). The file tags are discussed below followed by portions of a few example files.

FILE TAGS:

The file tags for the ASCII file formats (shown in Bold Italics) are discussed below with a representative example. They are given in the appropriate order. If you need assistance creating software to write these file formats, please contact support@ctech.com.

COORD_UNITS “ft” Defines the coordinate units for the file. These should be consistent in X, Y, and Z.

NUM__DATA 7 1

Number of nodal data components followed by the number of cell data components.

NODE_DATA_DEF 0 “TOTHC” “log_ppm”

NODE_DATA_DEF specifies the definition of a nodal data component. The second value is the data component number, the third is the name, and the 4th is the units.

CELL_DATA_DEF 0 “Indicator” “Discreet Unit”

Definition of cell data. Same options as NODE_DATA_DEF

LINE 12 1

Beginning of a line segment is followed on the same line by the cell data values.

Following this line should be the points making up the line in the following format:

X, Y, Z coordinates followed by nodal data values.

64718.310547 37500.000000 -1250.000000 1 -1250.000000

63447.014587 35101.682129 -2000.000000 2 -2000.000000

CLOSED

This flag is used at the end of a line definition to indicate the end of the line should be connected to the beginning of the line.

END

Marks the end of the data section of the file. (Allows us to put a password on .eff files)

EXAMPLE FILE

NUM_DATA 2 0

NODE_DATA_DEF 0 “Node_Number” “Linear_ID”

NODE_DATA_DEF 1 “Distance” “Linear_ft”

LINE

1900297.026154 677367.319824 72.000000 0.000000 0.000000

1900314.256775 677438.611328 72.000000 1.000000 73.344208

1900314.687561 677442.703522 72.000000 2.000000 77.459015

1900316.410645 677447.011261 72.000000 3.000000 82.098587

1900319.641266 677447.442018 72.000000 4.000000 85.357796

1900345.487030 677441.411530 72.000000 5.000000 111.897774

1900360.563782 677439.472870 72.000000 6.000000 127.098656

1900363.579193 677447.226807 72.000000 7.000000 135.418289

1900365.517822 677447.226807 72.000000 8.000000 137.356918

1900365.948608 677438.396118 72.000000 9.000000 146.198105

1900379.733032 677436.888245 72.000000 10.000000 160.064758

1900405.578766 677432.150055 72.000000 11.000000 186.341217

1900497.331879 677416.427002 72.000000 12.000000 279.431763

1900511.331512 677414.919464 72.000000 13.000000 293.512329

1900525.762268 677411.257721 72.000000 14.000000 308.400421

1900527.269775 677405.442444 72.000000 15.000000 314.407898

1900524.900696 677399.411926 72.000000 16.000000 320.887085

1900522.531311 677391.012024 72.000000 17.000000 329.614746

1900517.362366 677357.196808 72.000000 18.000000 363.822754

1900501.854828 677266.951569 72.000000 19.000000 455.390686

1900501.639282 677262.213379 72.000000 20.000000 460.133789

1900500.777710 677255.321014 72.000000 21.000000 467.079773

1900496.470306 677250.151733 72.000000 22.000000 473.808472

1900487.208862 677241.751816 72.000000 23.000000 486.311798

1900450.378204 677201.906097 72.000000 24.000000 540.572083

1900403.568481 677152.368134 72.000000 25.000000 608.727478

1900356.758759 677102.830177 72.000000 26.000000 676.882874

1900309.949036 677053.292221 72.000000 27.000000 745.038269

1900286.257172 677028.523243 72.000000 28.000000 779.313721

1900278.718445 677022.923517 72.000000 29.000000 788.704651

1900269.672546 677024.431061 72.000000 30.000000 797.875305

1900217.334717 677035.200397 72.000000 31.000000 851.309631

1900232.196075 677097.230453 72.000000 32.000000 915.095154

1900247.057434 677159.260513 72.000000 33.000000 978.880615

1900252.226715 677179.937317 72.000000 34.000000 1000.193787

1900267.159851 677242.326401 72.000000 35.000000 1064.345215

1900282.093018 677304.715485 72.000000 36.000000 1128.496460

1900297.026154 677367.104584 72.000000 37.000000 1192.647827

END

read strike and dip

General Module Function

The read strike and dip module is used to visualize sampled locations. It places a disk, oriented by strike and dip, at each sample location. Each disk is probable and can be colored by a picked color, by Id, or by data value. If an ID is present, such as a boring ID, then there is an option to place tubes between connected disks, or those disks with similar Id’s.

Strike and dip refer to the orientation of a geologic feature. The strike is a line representing the intersection of that feature with the horizontal plane (though this is often the ground surface). Strike is represented with a line segment parallel to the strike line. Strike can be given as a compass direction (a single three digit number representing the azimuth) or basic compass heading (e.g. N, E, NW).

The dip gives the angle of descent of a feature relative to a horizontal plane, and is given by the number (0°-90°) as well as a letter (N,S,E,W, NE, SW, etc.) corresponding to the rough direction in which feature bed is dipping.

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Output [Field] Outputs the subsetted field as edges
• Output Object [Renderable]: Outputs to the viewer

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: controls the Z scaling and edge angle used to determine what edges should be displayed
• Display Settings: controls the type and specific data to be output or displayed

Strike and Dip File Example

Discussion of Strike and Dip Files

Strike and dip files consist of 3D coordinates along with two orientation values called strike and dip. A simple disk is placed at the coordinate location and then the disk is rotated about Z to match the strike and then rotated about Y to match the dip. An optional id and data value can be used to color the disk.

Format:

You may insert comment lines in C Tech Strike and Dip (.sad) input files. Comments can be inserted anywhere in a file and must begin with a ‘#’ character.

Strike can be defined in the following ways :

1. For strikes running along an axis:

N, S, NS, SN are all equivalent to 0 or 180, and will always have a dip to E or W

E, W, EW, WE are all equivalent to 90 or 270, and will always have a dip to N or S

NE, SW are both equivalent to 135 or 315, and can have a dip specified to N, S, E, or W

NW, SE are both equivalent to 45 or 225, and can have a dip specified to N, S, E, or W

2. For all other strikes: any compass direction between 0 and 360 degrees can be specified, with the dip direction clarifying which side of the strike is downhill.

Dip can be defined only in degrees in the range of 0 to 90.0 followed by a direction such as 35.45E

There is no required header for this file type.

Each line of the file must contain:

X, Y, Z, Strike, Dip, ID (optional), and Data (optional).

NOTE: The ID can only contain spaces if enclosed in quotation marks (ex “ID 1”).

EXAMPLE FILE

x y z strike dip

51.967 10.948 26.127 35.205 59.8031E

50.373 33.938 26.127 13.048 68.49984E

51.654 60.213 26.127 139.18 76.74215E

50.529 83.203 26.127 213.50 62.94599E

64.358 76.634 11.471 114.23 80.38694E

66.430 33.938 -6.849 41.421 60.38837E

75.901 50.360 -21.505 60.141 72.88960E

72.943 7.663 -21.505 5.255 65.51247E

101.90 30.654 -72.801 77.675 65.9524E

81.339 50.360 -43.489 244.95 70.7079E

72.263 73.350 -21.505 82.929 69.3159E

89.897 73.350 -61.809 31.531 55.6570E

END

FILE TAGS:

The file tags for the ASCII file formats (shown in Bold Italics) are discussed below with a representative example. They are given in the appropriate order. If you need assistance creating software to write these file formats, please contact support@ctech.com.

COORD_UNITS “ft” Defines the coordinate units for the file. These should be consistent in X, Y, and Z.

END (this is optional, but should be used if any lines will follow your actual data lines)

read glyph

read glyph replaces the Glyphs sub-library that was in the tools library. It reads glyphs saved in any of the three primary EVS field file formats and allows you to modify the shape and orientation of the glyph to allow it to be used in various modules that emply glyphs in slightly different ways. These include glyphs at nodes, place_glyph,drive_glyphs, advector, post_samples, etc. Most modules EXCEPT post_samples will use the glyphs without chaning the default alignment. The supported file formats are:

1. .eff ASCII format, best if you want to be able to open the file in an editor or print it

2. .efz GNU Zip compressed ASCII, same as .eff but in a zip archive

3. .efb binary compressed format, the smallest & fastest format due to its binary form

For a description of the .EFF file formats click here.

The objects saved in the .efx files should be simple geometric objects ideally designed to fit in a unit box centered at the origin (0,0,0). For optimal performance the objects should not include nodal or cell data. You may create your own objects or use any of the ones that C Tech supplies in the ctech\data\glyphs folder.

Module Output Ports

• Output [Field] Outputs the saved glyph.
• Output Object [Renderable]: Outputs to the viewer.

General Module Function

The import geometry module will read STL, PLY, OBJ and .G files containing object geometries.

This module provides the user with the capability to integrate site plans, topography, buildings, and other 3D features into the EVS visualizations.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

Transform Settings: This allows you to add any number of Translation or Scale transformations in order to place your Wavefront Object in the same coordinate space as the rest of your “Real-World” model. It is very typical that Wavefront Objects are in a rather arbitrary local coordinate system that will have no defined transformation to any standard coordinate projection.

Generally you should know if the coordinates are feet of meters and if those are not correct, do that scaling as your first set of transforms.

It will be up to you to determine the set of translations that will properly place this object in your model. Hopefully rotations will not be required, but they are possible with the Transform List.

write evs field

The write evs field module creates a file in one of several formats containing the mesh and nodal and/or cell data component information sent to the input port.

This module is useful for writing the output of modules which manipulate or interpolate data (3d estimation , 2d estimation, etc.) so that the data will not need to be processed in the future.

The saved and processed data can be read using read evs field, which is much faster than reprocessing the data.

Principal recommended format: EF2

• The newest and strongly recommended format is EF2. This format is capable of containing additional field data and mesh types which are not supported in our Legacy format. Please note that this is the only LOSSLESS format for current and future EVS fields. Although the files created in EF2 format are generally larger than >EFBs, the further subsetting and/or processing of these updated fields can be dramatically more efficient.

  • Uniform fields
  • Geology (from gridding and horizons)
  • Structured fields (such as irregular fields read in from Read_Field)
  • Unstructured Cell Data (UCD format) general grids with nodal and/or cell data
  • Special fields containing spheres (which are points with radii)
  • Special fields containing color data (such as LIDAR data)

Legacy formats:

• The legacy formats below were the recommended formats in software releases before 2024. With our enhancements to EVS Fields, these formats must be considered LOSSY, meaning that some data and the (EF2) optimized grids will be compromised if these formats are use. We strongly recommend using theEF2 format.
  • .eff ASCII format, best if you want to be able to open the file in an editor or print it. For a description of the .EFF file formats click here.
  • .efz GNU Zip compressed ASCII, same as .eff but in a zip archive
  • .efb binary compressed format, the smallest & fastest format due to its binary form

Module Input Ports

• Geologic legend Information [Geology legend] Accepts the geologic material information for the legend module.
• Input Field [Field] Accepts the field to be saved.
• File Notes [String / minor] Accepts a string to document the settings used to create the field.

Module Parameters

There are only a few parameters in write evs field, but they provide important functionality and should be understood.

• Check for Cell Set Data (EF2 Only): Causes any cell data that is constant across a cell set to be saved as cell set data. This is more efficient and is recommended.
• Translate by (Application) Origin): Normally on, this should be turned off if the contents represent content which is not in your application origin. Examples are glyphs or inputs to modules such as cross section tubes
• LEGACY FILE OPTIONS
  • Split Into Separate Files: This toggle applies only to EFF format files and makes it easier to create your own EFF files from similar data. It separates the header file (.eff) from the coordinates, data and connectivity.
  • Force Nodal in Output: This toggle is on by default and ensures that fields without data are tagged as having data because many EVS modules may not allow connections for fields without data. It does not add data, it only tags the file as having data (even if it doesn’t)
  • Force Cell in Output: Similar to the toggle above, but needed far less often.

export web scene connects via the vew port and writes all objects in your view as a “C Tech Web Scene” (*.ctws), a single file which you and your customers can load and view at: https://viewer.ctech.com/

Details on its use at How to Create C Tech Web Scenes.htm

WARNINGS:

• DATAMAPS ARE USED FOR PROBING: When using unlinked values (Min and Max) such that the resulting datamap is a subset of the true data range, probing in C Tech Web Scenes will only be able to report values within the truncated data range. Values outside that limited range will display the nearest value within the truncated range. This applies to the use of the Datamap parameters in post samplesor when the data range is truncated by clipping in the estimation modules or with the change min max module.

export pdf scene connects via the vew port and writes all objects in your view as a .evspdf file that C Tech’s PDF Converter can convert to a 3D PDF. This module requires a valid PDF Converter license in order to function.

This module will export the entire view (model) in the following formats to allow importing to other 3D modeling software:

• glTF 2.0 (.glb binary format)
• FBX (.fbx)
• COLLADA (.dae)

All files are written in a coordinates system where the X-Y origin (0,0) is the Application Origin. This is done to preserve precision in these formats which are fundamentally single precision.

export nodes

export nodes provides a means to export an ASCII file containing the coordinates (and optionally the data) of any object in EVS. The output contains a header line and one row for each node in the input field. Each row contains the x, y, & z coordinates and optionally node number and nodal data.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
• Input Field [Field] Accepts a field with or without data

export cad

General Module Function

export cad will output one or more individual objects (red port) or your complete model (purple input port from the viewer). Volumetric objects in EVS are converted to surface and line type objects.

export cad preserves the colors of all cells and objects by assigning cell colors to each AutoCAD surface or line entity according to the following procedure:

a) If nodal data is present, the first nodal data component is averaged to the cells and that color is applied. This is equivalent to the appearance of surfaces in EVS with flat shading mode applied.

b) If no nodal data is present, but cell data is, that color is applied. This is equivalent to the appearance of surfaces in EVS with flat shading mode applied.

c) If neither nodal or cell data is present the object’s color is used.

The results should look fairly similar to the viewer in EVS except:

• AutoCAD has a very limited color palette with only 256 total colors. With some datamaps this limitation will be more problematic and it is possible that the nearest AutoCAD color may apply to multiple colors used in a subtle geology datamap.
• AutoCAD lacks of Gouraud shading support (as mentioned above) so all cells are flat shaded.

All “objects” in EVS are converted to separate layers based upon the EVS object name (as shown in the viewer’s Object_Selector).

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
• View [View] Connects to the viewer to receive all objects in the view
• Input Object [Renderable]: Receives inputs from one or more module’s red port

export surface to raster

The export surface to raster module will create a raster file in the GeoTiff format.

It takes any input field, and writes a raster (in plan view) of the data provided from that field. Regions outside of the input area are masked with an appropriate NoData flag. A single data component (node or cell) can be exported to the GeoTiff file.

Raster resolution can be controlled via the Grid Cell Size parameter, which will default (when linked) to a size which generates a raster of up to four million pixels, with fewer generated depending on how much the input shape deviates from having square extents.

When exporting certain cell data, such as Lithology, connecting the Geologic Legend Information port will allow the raster to include additional metadata in a raster dataset attribute table file. This additional file will allow programs such as ESRI’s ArcGIS Pro to automatically load the GeoTiff with proper names associated with each material.

Module Input Ports

• Input Field [Field] Accepts a field with data to export
• Geologic Legend Information Accepts the geologic information from an appropriate module, such as lithologic modeling, to associate data with names

export vector gis

The export vector gis module will create a file in one of the following vector formats: ESRI Shapefile (*.shp); GMT ASCII Vectors (*.gmt); and MapInfo TAB (*.tab).

Although C Tech allows non-ASCII analyte names, ESRI does not. Please see this link on acceptable shapefile field (attribute) names. It basically says that only A-Z, a-z, 0-9 and “_” are allowed. The only thing we can do when writing a shapefile is to change any unacceptable (non-ASCII) character to “_” and add a number if there are more than one.

If you plan to create a shapefile it will be better to change the analyte names to an ASCII equivalent that is more meaningful, but uses on the acceptable character set.

export horizon to raster

export horizon to raster is used in conjunction with gridding and horizons with rectilinear grids of geologic data. A large number of formats are supported such as Surfer and ESRI grids. For some formats, each cell in your grid should be the same size. This will require you to adjust the extents of your grid and set the grid resolution according to:

Cell size = (Max:xy - Min:xy) / (grid-resolution -1)

NOTE: YOU MUST SELECT RECTILINEAR GRIDDING IN gridding and horizons

Module Input Ports

• Geology Export Output [Vistas Data] Accepts output from gridding and horizons for conversion to raster grids.

write_lines

The write_lines module is used to save a series of points with data connected by lines. These lines are stored in the EVS Line File format.

Module Input Ports

• Input Field [Field] Accepts a field with or without data which represents lines

export horizons to vistas

export horizons to vistas is used in conjunction with gridding and horizons. gridding and horizons can create finite difference grids based on your geologic data.

It writes the fundamental geologic grid information to a file format that Ground Water Vistas can read.

The output includes the x,y origin; rotation; and x-y resolutions in addition to descriptive header lines proceeded by a “#”.

Module Input Ports

• Geology Export Output [Vistas Data] Accepts output from gridding and horizons for conversion to Groundwater Vistas format

The driven sequence module controls the semi-automatic creation of sequences for the following modules:

• slice
• cut
• plume
• plume shell

Control over these modules is via the purple “Sequence Output” ports on the driven modules and the “Sequence Input” port on driven sequence.

All modules to be grouped in the Sequence must have their red output ports connected to driven sequence instead of the viewer. Consider driven sequence to act like a group objects module.

Module Input Ports

• Sequence Input Receives special port from only plume, plume shell, and slice modules
• Input Objects [Field] Accepts any number red object ports from modules changed within the sequence.

Module Output Ports

• Current State Title
• Output Object [Renderable]: Outputs to the viewer.

Other modules not listed above may be included if one of the “driven modules” controls those modules. Examples are titles, isolines, band data, etc.

driven sequence has only a Current State slider which allows you to test the sequence or directly access any state. The latter is useful when using this module in EVS or EVS Presentations. Please note that in this case, selecting a state requires that all controlled modules must run. This is much slower than selecting a (saved) state of a .CTWS file.

The State Name output port provides a simple way to include a title which specifies the current displayed state in sequences.

The Driven Modules have the bulk of the settings which determine what controls and states will be available such as:

• Use Sequencing: This toggle must be on when using driven sequence with a driven module.

• State Control: Choose between

  • Slider
  • Combo Box
  • List Box

• Sequence Type: Choose between

  • By Count (set the number of states between minimum and maximum values)
  • By Step Size (set the increment between each step)

• State Titles are automatically generated for you

Please note: For Log Data, the state values are determined using the same logic (algorithm) which we have traditionally applied to modules such as isolines, band data and legend. This means that for:

• By Count: If the number of Frames results in:

  • 2 steps per decade, then the states will be .1, .3, 1, 3, 10, 30, etc.
  • 3 steps per decade, then the states will be .1, .2, .5, 1, 2, 5, 10, 20, 50, etc.

• By Step Size: If the increment is:

  • 0.5 , then the states will be .1, .3, 1, 3, 10, 30, etc.
  • 0.33333, then the states will be .1, .2, .5, 1, 2, 5, 10, 20, 50, etc.

The scripted sequence module provides the most power and flexibility, but requires creating a Python script which sets the states of all modules to be in the sequence.

Module Input Ports

• Input Value 1 [Number] Accepts a number
• Input Value 2 [Number] Accepts a number
• Input Value 3 [Number] Accepts a number
• Input Value 4 [Number] Accepts a number
• Input Objects [Field] Accepts any number red object ports from modules changed within the sequence.

Module Output Ports

• Output Value 1 [Number] Passes the number
• Output Value 2 [Number] Passes the number
• Output Value 3 [Number] Passes the number
• Output Value 4 [Number] Passes the number
• Current State Title
• Output Object [Renderable]: Outputs to the viewer.

The process for using this module is:

1. Determine which modules’ output will be affected (controlled) by the Python script and therefore contained in one or more states.
2. Connect the red output ports of those modules to scripted sequence instead of the viewer
3. Set the number of states and their names. This can be done manually or in a secondary (separate) Python Script.
4. Choose and set the State Control type: Choose between
   • Slider
   • Combo Box
   • List Box
5. Create and test the Python script which will control all modules, which must be set under Filename.

This is the simplest of the sequence modules, but also the easiest to abuse (vs. using scripted sequence where you can be more efficient).

You create “states” merely by connecting modules (including groups) to the object sequence’s input port. This module works much like a group object module, in that you can rearrange the order of the modules within, each of which creates a “state” named with that module’s (or group’s) name.

Module Input Ports

• Input Objects [Field] Accepts any number red object ports from modules changed within the sequence.

Module Output Ports

• Current State Title
• Output Object [Renderable]: Outputs to the viewer.

3d streamlines

The 3d streamlines module is used to produce streamlines or stream-ribbons of a field which is a 2 or 3 element vector data component on any type of mesh. Streamlines, which are simply 3D polylines, represent the pathways particles would travel based on the gradient of the vector field. At least one of the nodal data components input to streamlines must be a vector. The direction of travel of streamlines can be specified to be forwards (toward high vector magnitudes) or backwards (toward low vector magnitudes) with respect to the vector field. Streamlines are produced by integrating a velocity field using the Runge-Kutte method of specified order with adaptive time steps.

Module Input Ports

• Input Field [Field] Accepts a data field.
• Input Locations Field [Field] Accepts the starting points for each line

Module Output Ports

• Output Field [Field] Outputs the streamlines or ribbons
• Output Object [Renderable]: Outputs to the viewer.

surface streamlines

The surface streamlines module is used to produce streamlines on any surface based on its slopes. Streamlines are 3D polylines representing the paths particles would travel based on the slopes of the input surface. The direction of travel of streamlines can be specified to be downhill or uphill for the slope case. A physics simulation option is also available which employs a full physics simulation including friction and gravity terms to compute streamlines on the surface.

The Physics radio buttons allow the user to specify whether streamlines will be computed based on the slopes of the surface only or whether a full physics simulation including friction and gravity terms will be used to compute streamlines on the surface. When Gravity is selected Segments perCell and Order do not apply but additional parameters appear for the module. These are:

Integration Time Step is the time step for the numerical integration of the paths. For typical gravity units (like 32 feet per second-squared) this value is in seconds.

Gravity is the coefficient of gravity for your units. If your coordinate units are feet, the appropriate (default) value would be 32 feet per second-squared.

Viscosity Coefficient (v) is the friction term that depends on velocity.

Drag Coefficient (v2) is the friction term that depends on velocity-squared.

Module Input Ports

• Input Surface [Field] Accepts a data field which must be a surface with elevation data.
• Input Locations Field [Field] Accepts the starting points for each line

Module Output Ports

• Output Field [Field] Outputs the streamlines
• Output Object [Renderable]: Outputs to the viewer.

The create drill path module allows you to interactively create a complex drill path with multiple segments.

Each segment can be defined by one of three methods:

1. Continue Straight: for the specified “Total Length” along the current direction or Initial Drill Direction, if just starting.
2. Target Coordinate: Begin deviating with specified “Segment Length” and specified “Max Angle of Change” (per segment) until you reach the specified “(X,Y,Z)” coordinate.
3. Move to Heading: Begin deviating with specified “Segment Length” and specified “Max Angle of Change” (per segment) until you reach the specified “Heading” and “Dip”

modpath

The modpath module uses the cell by cell flow values generated from a MODFLOW project along with head values and other MODFLOW parameters to trace the path of a particle of water as it moves through the ground. The paths are calculated using the same algorithms used by U.S. Geological Survey MODPATH and the results should be similar.

The modpath module at this point does not handle transient simulations the same way that the U.S.G.S. MODPATH does. It treats each time step as a steady state model, and uses the parameters from the .dwr/.dwz file based on the starting time.

A valid modpath field file (.eff/.efz) should contain the following as cell data components: Head; CCF; ELEV_TOP; ELEV_BOT; and POROSITY. The Head component should contain the head value for each cell, the ELEV_TOP and ELEV_BOT should components should contain the elevation of the top of the cell, and the elevation of the bottom of the cell respectively, and the POROSITY should contain the flow due to porosity for that each cell. All other MODFLOW parameters (drains, wells, recharge, etc..) should be written into a .dwr/.dwz file.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration) from other modules
• Input Field [Field] Accepts a data field.
• Input Starting Locations [Field] Accepts the starting points for each line
• Start Date [Number] The starting time
• Ending Date [Number] The ending time

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Output Field [Field] Outputs the streamlines
• Start Date [Number] The starting time
• Ending Date [Number] The ending time
• Output Object [Renderable]: Outputs to the viewer.

scalars to vector

The scalars to vector module is used to create an n-length vector by combining n selected scalar data components. The vector length is determined by the Vector Type selector (2D or 3D).

Once the required number of components has been selected, any other data components are grayed out and not selectable. To change selections, first deselect one of the vector components and then select a new component. If no components are selected, then all components are selectable. The order in which the components are selected will determine in which order they occur in the vector.

Module Input Ports

• Input Field [Field] Accepts a data field with 2 or more nodal data components.

Module Output Ports

• Output Field [Field] Outputs the field with selected data
• Output Object [Renderable]: Outputs to the viewer.

The vector to scalars module converts all vector nodal data components into individual scalars. For example, a vector data component named “velocity” will be converted to three scalar nodal data components such as:

1. velocity_x
2. velocity_y
3. velocity_z

If multiple vector data components exist in the field, all will be converted.

Module Input Ports

• Input Field [Field] Accepts a data field with 1 or more vector nodal data components.

Module Output Ports

• Output Field [Field] Outputs the field with vector data converted to scalars.

vector magnitude

The vector magnitude module calculates the vector magnitude of a vector field data component at every node in a mesh. Input to vector magnitude must contain a mesh of any type and nodal data. Nodal data components can be scalar or vector with up to 3 vector subcomponents.

Module Input Ports

• Input Field [Field] Accepts a vector data field

Module Output Ports

• Output Field [Field] Outputs the scalar data field
• Output Object [Renderable]: Outputs to the viewer

Related Modules

gradient

gradient

The gradient module calculates the vector gradient field of a scalar data component at every node in a mesh. Input to gradient must contain a mesh of any type and nodal data, with at least one scalar nodal data component. Gradient uses a finite-difference method based on central differencing to calculate the gradient on structured (rectilinear) meshes. Shape functions and their derivatives are used to calculate the gradient on unstructured meshes.

Please note that the gradient of (pressure) head points in the direction of increasing head, not the direction that groundwater would flow. Please see the seepage_velocity module if you wish to compute groundwater flow

Module Input Ports

• Input Field [Field] Accepts a data field

Module Output Ports

• Output Field [Field] Outputs the vector data field
• Output Object [Renderable / Minor]: Outputs to the viewer

Related Modules

->vector magnitude

capture_zone

The capture_zone module utilizes 3d streamlines technology to determine the volumetric regions of your model for which groundwater flow will be captured by one or more extraction wells.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration).
• Input Field [Field] Accepts a field with vector data.
• Well Nodes [Field] Accepts a field of points representing the well locations

Module Output Ports

• Output Field [Field] Outputs the volumetric regions which are captured

seepage_velocity

The seepage_velocity module is used to compute the vector groundwater flow field visualizations of the vector field.

The input data requirements for the seepage_velocity module are:

1. A data component representing head (can have any name).
2. A Geo_Layer data component.
3. A Material_ID data component. If there is no Material_ID, we treat each layer as a separate material. Layer 0 becomes material -1 Layer 1 becomes material -2 Layer 2 becomes material -3, etc.

Note: If you use 3d estimation to krige head data with geologic input (in Version 6.0 or later) your output will meet these criteria (provided you toggle on these data components under Kriging Parameters).

The Run toggle determines if the module runs immediately when you change conductivity values.

Head Data Component determines which data component is used to scale and rotate the seepage_velocity velocity vectors. The default selection is the first data component. The Map component radio button list also displays all data components passed to seepage_velocity. Map component determines which data component is used to color the seepage_velocity velocity vectors. By default, the first (0th) data component is selected.

Head Data Component list displays all data components passed to seepage_velocity.

Current Material: allows you to select the Material (or geologic layer) to assign conductivity and porosity properties.

HeadUnits radio button list allows you to specify the units of your head data.

Output Conductivity Units: radio button list allows you to choose the units for specifying the conductivity in all three (x, y, z) directions for each geologic layer. You can choose any units (regardless of your head and coordinate units) and the appropriate conversions will be made for you.

The Conductivity sliders (with type-ins) allow you to change the log10 of the x, y, & z conductivity. These specify log values because conductivities vary over many orders of magnitude. These update when the (Linear) type-ins are changed.

The Conductivity type-ins allow you to change the x, y, & z conductivity. These are actual values and update when the sliders are changed.

The Effective Porosity slider (with type-in buttons) allows you to change the value of effective porosity.

Material (#/Name): allows you to specify the material type if it is not specified in your geologic layers. This is only to help you assign proper conductivities.

Data passed to the field port must be a 3D mesh with data representing heads and normally multiple Materials (or geologic layers).

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration).
• Input Field [Field] Accepts a data field with geologic and head data

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Output Field [Field] Outputs the vector data field

Technical Details

Inherent in the solution of seepage velocity implemented in this module is the assumption that within each geologic layer/material the conductivities are uniform. Clearly, this will never be completely accurate, however we would contend that there is seldom if ever a better measure of the site conductivities (true conductivity tensor) than the site heads because head is far easier to measure. Furthermore, geologic materials can be deposited such that their conductivities are very complex and directional and most groundwater models (e.g. MODFLOW) do not provide a way to reflect this EVEN IF IT COULD BE MEASURED.

This approach allows users to quickly investigate the impact on flow paths due to changes in the conductivity assigned to each layer/material, BASED ON THE MEASURED/KRIGED HEAD DISTRIBUTION. Clearly, the more accurately the head is characterized the better.

At this point, we don’t propose to provide a mechanism to account for conductivity variations within a geologic layer. We obviously cannot account for natural or artificial barriers (low conductivity regions) UNLESS they are represented by the geologic materials.

Our approach is:

Compute the true seepage velocity (Vx, Vy, Vz) at each node, by taking the gradient of (kriged) head (without any z-exaggeration) and multiplying each component of head gradient by the component of conductivity at that node (based on its material) (Kx, Ky, Kz) and dividing by the Effective Porosity for that material.

Vx = dH/dx * Kx / Ne

Vy = dH/dy * Ky / Ne

Vz = dH/dz * Kz / Ne

Darcy Flux = -K * (dh/dl), also known as Darcy Velocity, Specific Discharge or apparent velocity, and

Seepage Velocity = -K * (dh/dL) / ne, where:

• K = hydraulic conductivity, is the proportionality constant reflecting the ease with which water flows through a material (L/T)
• dh = difference in hydraulic head between two measuring points as defined for Equation 14 (L)
• dL = length along the flow path between locations where hydraulic heads are measured (L)
• dh/dL = gradient of hydraulic head (dimensionless)
• ne = effective porosity

regional_averages

The regional_average module averages nodal data values from the input field that fall into the input polygon regions. It then outputs a point for each region that contains the average x, y coordinates and the average of each selected nodal data component.

These polygons must contain at least 1 cell data component representing the regional ID.

Module Input Ports

• Input Field [Field] Accepts a data field.
• Input Surface [Field] Accepts a cell data field defining a regions

Module Output Ports

• Output Field [Field] Outputs the processed field.
• Output Object [Renderable]: Outputs to the viewer

draw_lines

The draw_lines module enables you to create both 2D and 3D lines interactively with the mouse.

The mouse gesture for line creation is: depress the Ctrl key and then click the left mouse button on any pickable object in the viewer. The first click establishes the beginning point of the line segment and the second click establishes each successive point.

draw_lines allows adding of points that are outside the model extents, undoing of the last picked point, and the clearing of all picked points. Unlike most modules which create mesh data to used by other modules, the draw_lines module receives input from the viewer, and also passes on field data to be used by other modules.

There are two drawing modes:

1. Top View Mode creates 2D lines which are always at Z=0.0. You must be in a Top View to draw with this mode, but you may pick points anywhere in the viewer screen.

2. Object Mode creates 3D lines which are drawn by probing objects in your model. You cannot draw at a point without having an object there or specifying a coordinate using the x-y-z type-ins.

NOTE: Because draw_lines saves your lines with your application, when an application is saved, the purple port is automatically disconnected from the viewer. This ensures that when you load an application the resulting objects (lines, fence-diagrams, etc.) will look exactly the same as when you saved the application. However, if you wish to draw new lines you will need to reconnect the purple port from the viewer.

Module Input Ports

• View [View] Connects to the viewer to receive the extent of all objects in the viewer for scaling lines and drawing on objects.

Module Output Ports

• Output Field [Field / minor] Outputs the field with the scaling and exploding applied.
• Sample Data [Renderable]: Outputs to the viewer.

polyline processing

The polyline processing module accepts a 3D polyline and can either increase or decrease the number of line segments of the polyline. A splining algorithm smooths the line trajectory once the number of points are specified. This module is useful for applications such as a fly over application (along a polyline path drawn by the user). If the user drawn line is jagged with erratically spaced line segments, polyline spline smooths the path and creates evenly spaced line segments along the path.

Module Input Ports

• Input Field [Field] Accepts a 3D polyline field

Module Output Ports

• Output Data [Field] Outputs the splined lines
• Output Object [Renderable]: Outputs to the viewer

triangulate_polygons

triangulate_polygons converts a closed polyline into a triangulated surface. This surface can be extruded or used by the distance to 2d area module to perform areal subsetting of 3D models.

Polylines with WIDTH in AutoCAD DWG files are converted by import_cad into triangle strips of the specified width. As you zoom in on polylines with width, the apparent width will change, whereas the apparent width of lines DOES NOT change. However, once they are triangles, they DO NOT define a closed area and therefore would not work with triangulate_polygons.

Module Input Ports

• Input Field [Field] Accepts a data field representing closed polygon(s).

Module Output Ports

• Output Field [Field] Outputs the surface(s) field
• Output Object [Renderable]: Outputs to the viewer.

triangle refinement

triangle refinement is primarily for use with distance to surface. It can subdivide triangular and quadrilateral cells until none of the sides of the output triangles exceed a user specified length (a default value is calculated as 5% of the x-y extent of your input surface). This increases the accuracy of distance to surface especially when the input surface comes from create_tin and the nodes used to create the TIN are poorly spaced. It can also correct the normals of a surface. It does this by organizing all of the triangles and quadrilaterals in a surface into disjoint patches, and then allowing the user to select which patches have normals that need to be flipped. The maximum number of triangles in a patch is 130,000, any triangles above this number will be considered to be in the next patch.

Removing small cells is used to remove extremely small cells (based on area in your coordinate units squared) that sometimes are generated with CAD triangulation routines that might have their normal vectors reversed and would contribute to poor cutting surface definition. Try this option if you find that distance to surface is giving anomalous results.

The maximum edge length allows the maximum length of each triangle side to be set for when the Split Cells option is set.

The ability to fix normals is used to check to that all of the triangles in selected patches of the surface have the same normal vector direction. If the normal is backwards, you can flip the normal of the patch in two ways. The first way is Alt + Right click on a cell in the patch that you wish to flip and then click the Add patch to flip list button. You only need to do this for one cell in each patch. Another way to do this is to set the Cell ID and Cell Data value of a cell in the patch you wish to flip. The Cell Id and Cell Data values must be obtained from the surface being output from triangle refinement, and not the surface being input.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the refined grid.
• Sample Data [Renderable]: Outputs to the viewer.

tubes

The tubes module is used to produce open or closed tubes of constant or data dependent radius using 3D lines or polylines as input. Tube size, number of sides and data dependent coloring is possible.

Rotation of the tubes are done with the Phase slider (or type-in), which is specified in degrees. There are two methods used to maintain continuity of the tube orientation as the path meanders along a 3D path. These are specified as the Phase Determination method:

• Force Z Up: is the default and is most appropriate for paths that stay relatively horizontal. This option keeps the tube faces aligned with the Z axis and therefore with a slope of 30 degrees, the effective cross sectional area of the tube would be reduced by cos(30) which would be a 14% reduction. However for the typical slopes found with tunneling this effect is quite minimal and this option keeps the tube perfectly aligned.
• Perpendicular Extrusions: keeps the tube cross-section aligned with the tube (extrusion) path and therefore preserves the cross-section no matter what the path. However, tube rotation creep is possible.

Module Input Ports

• Input Field [Field] Accepts a field with or without data containing lines which represent the paths of the tubes.

Module Output Ports

• Output Field [Field] Outputs the field as tubes.
• Output Object [Renderable]: Outputs to the viewer.

volumetric_tunnel

The volumetric_tunnel module allows you to create a volumetric tunnel model that is defined by a polygonal surface cross-section along a complex 3D path. Once this volumetric grid is defined, it can be used as input to various modules to map analyte and/or geologic data onto the tunnel. These include:

• 3d estimation: external grid port: to map analytical data
• lithologic modeling: external grid port: to map lithologic data
• interp_data to map analytical data
• interp_cell_data: to map stratigraphic or lithologic material data

The requirements for the tunnel path and cross-section are:

• The path must be defined by a line input to the Right input port.
• The tunnel cross-section is defined by a surface input to the Left input port.
  • The cross-section should be defined in the X-Y plane at Z = 0 (2D)
  • The coordinates (size) of the cross-section should be actual scale in the same units as the tunnel path (generally feet or meters).
    • Do not use cm for cross-section and meters for path.
    • Generally, the X-Y Origin (0, 0) should lie within the cross-section and should represent where the tunnel path should be.

cross_section_tubes

The cross_section_tubes module is used to produce open or closed tubes of user defined cross-section and constant or data dependent radius using 3D lines or polylines as input for the centerline and a single 2D polyline as the cross-section of the tubes.

Module Input Ports

• Input Field [Field] Accepts a field with or without data containing lines which represent the paths of the tubes.
• Input Cross Section Field [Field] Accepts a field which has the cross-section of the tubes.

Rotation of the cross-section is done with the Phase slider (or type-in), which is specified in degrees. There are two methods used to maintain continuity of the tube orientation as the path meanders along a 3D path. These are specified as the Phase Determination method:

• Force Z Up: is the default and is most appropriate for paths that stay relatively horizontal. This option keeps the tube cross-section aligned with the Z axis and therefore with a slope of 30 degrees, the effective cross sectional area of the tube would be reduced by cos(30) which would be a 14% reduction. However for the typical slopes found with tunneling this effect is quite minimal and this option keeps the tube perfectly aligned.
• Perpendicular Extrusions: keeps the tube cross-section aligned with the tube (extrusion) path and therefore preserves the cross-section no matter what the path. However, cross-section rotation creep is possible.

The cross section field input must be a closed polyline that is drawn in the X-Y plane in the correct size. It should be balanced about the origin in X, usually with the Y axis (X=0) at the floor of the tunnel. This results in the tunnel being created such that the tunnel path will be at the centerline FLOOR of the tunnel as shown in the picture below.

This tube was created with an EVS Line File (.elf) that was very simple and is shown below:

LINE

-10 0 0

-10 7 0

-7 10 0

7 10 0

10 7 0

10 0 0

CLOSE

END

As you can see, all of the Z coordinates are zero since they are irrelevant. This shape is balanced about the Y axis and is all Y >= 0

Module Output Ports

• Output Field [Field] Outputs the subsetted field as faces.
• Output Object [Renderable]: Outputs to the viewer.

extrude

The extrude module accepts any mesh and adds one to the dimensionality of the input by extruding the mesh in the Z direction. The interface enables changing the height scale for extruded cells and extruding by a constant, any nodal or cell data component. This module is often used with the import vector gis module to convert polygonal shapefiles into extruded volumetric cells.

When Node Data Component is chosen, the output cells will be extruded by the Scale Factor times the value of whichever nodal data component is selected on the right. With nodal data extrusion you must select “Positive Extrusions Only” or “Negative Extrusions Only”. Since each node of a triangle or quadrilateral can have different values, it is possible for a single cell to have both positive and negative data values at its nodes. If this type of cell is extruded both directions, the cell topology can become tangled.

For this reason, nodal data extrusions must be limited to one direction. To extrude in both directions, merely use two extrude modules in parallel, one set to positive and the other to negative.

Module Input Ports

• Input Field [Field] Accepts a field with or without data

Module Output Ports

• Output Field [Field / Minor] Outputs the field
• Output Object [Renderable]: Outputs to the viewer

drive_glyphs

The drive_glyph module provides a way to move any object (glyph or object from Read_DXF, etc.) along multiple paths to create a “driving” animation.

Module Input Ports

drive_glyphs has three input ports.

Data passed to the first port is the paths to follow (normally from read_lines).

The second port accepts the glyph or vehicle to drive, usually read in with the read glyph module.

The third port is a float parameter for the position of the glyphs.

Module Output Ports

drive_glyph has three output ports.

The leftmost output port is a float parameter for the position of the glyphs along the input paths.

The center port is the animated glyphs.

The right output port is the animated glyphs in a renderable form for the viewer.

place_glyph

General Module Function

The place_glyph module is used to place a single scalable geometric objects (glyph) at an interactively determined location.

glyphs at nodes

The glyphs at nodes module is used to place geometric objects (glyphs) at nodal locations. The glyphs can be scaled, rotated and colored based on the input data. If the input data is a vector, the glyph can be scaled and rotated to represent the direction and absolute magnitude of the vector field. In a scalar data field, the objects can be scaled based on the magnitude of the scalar. The glyphs can represent the data field of one data component while being colored by another data component. Arrow glyphs are commonly used in vector fields to produce visualizations of the vector field.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration).
• Input Field [Field] Accepts a field with scalar or vector data.
• Input Glyph [Field] Accepts a field representing the glyphs

Module Output Ports

• Output Field [Field] Outputs the glyphs
• Output Object [Renderable]: Outputs to the viewer.

create_fault_surface

The create_fault_surface module creates a 3D grid that is aligned to a specified strike and dip.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration).
• Input Field [Field] Accepts a field to extract its extent

Module Output Ports

• Z Scale [Number] Outputs Z Scale (vertical exaggeration) to other modules
• Output Field [Field / Minor] Outputs the surface
• Fault Surface [Renderable]: Outputs to the viewer

create_grid

The create_grid module produces a 2D or 3D uniform grid that can be used for any purpose. A typical use is starting points for 3d streamlines or advector. In 2D (default) mode it creates a rectangle of user adjustable grid resolution and orientation. In 3D mode it creates a box (3D grid). The number of nodes will depend on the X, Y & optional Z resolutions as well as the cell type specified.

Module Input Ports

• Input Field [Field] Accepts a field to extract its extent and properly set the application origin. Do not use this module without input to this field, which can be as simple as post samples.

Module Output Ports

• Output Field [Field / Minor] Outputs the surface
• Surface [Renderable]: Outputs to the viewer

project onto surface

project onto surface provides a mechanism to drape lines and triangles (surfaces) onto surfaces. Please note that a pseudo-3D object like a building made up of triangle faces will be flattened onto the surface. The 3D nature will not be preserved. Lines and surfaces are subsetted to match the size of the cells of the surface on which the lines are draped. In other words, draped objects will match the surface precisely.

Module Input Ports

• Input Geologic Field [Field] Accepts a geologic field
• Input Lines [Field] Accepts a field with the lines to be draped

Module Output application-network.md#portsPorts

• Output Field [Field] Outputs the draped lines
• Surface [Renderable]: Outputs the draped lines to the viewer.

transform_field

The transform_field module is used to translate, rotate or scale the coordinates any field. Uses for this module would be to rotate and translate a modflow or mt3d grid (having a grid origin of 0,0,0) to the actual coordinate system of the modeled area.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the transformed field.
• Output Object [Renderable]: Outputs to the viewer.

transform objects

transform objects is a special group object that allows all connected objects to be rotated (about a user defined center) and/or translated. This is useful if you wish to move objects that are complex, such as group objects like post_samples or axes and therefore cannot be contained in a single field (blue-black) port.

An example of this, would be the axes module. If you wanted an axes with an origin that did not match your data, it could be created separately and moved using the transform objects module.

Module Input Ports

• Input Objects [Field] Accepts any number red object ports from modules to be grouped and transformed

Module Output Ports

• Output Object [Renderable]: Outputs to the viewer.

Limitations

• The transform objects modules does not change the coordinates that you will see when you probe.

  • We consider this module’s primary purpose to be visualization.
  • We most often use it to display a copy of an existing object in the application. In situations like this we want to retain the original coordinates.

• In some circumstances transform objects cannot be used with 4DIMs. It can cause the 4DIM extents to be different than they were in the EVS viewer. This has been noted when doing rotations.

• In most cases, the transform_field module can be used instead, however it does not allow for multiple objects to be connected to its input.

overlay_aerial

The overlay_aerial module will take as input a field and then map an image onto the horizontal areas of the grid. The image can be projected from one coordinate system to another. It can also be georeferenced if it has an accompanying All vertical surfaces (Walls) can be included in the output but will not have image data mapped to them.

Note: If you need to georeference your image or adjust the georeferencing, you can do so with the Georeference Image Tool on the Tool Tab

Module Input Ports

• Input Field [Field] Accepts a data field.
• Filename [String] The image filename

Module Output Ports

• Output Field [Field] Outputs the subsetted field as faces.
• Filename [String] The image filename
• Output Object [Renderable]: Outputs to the viewer.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: controls the placement of the texture image
• Wall Properties: controls how walls are viewed
• Image Processing: allows for the alteration of the image brightness, contrast, etc.

Image Quality: This selector limits the max resolution of the image being read. Most graphics cards support the High resolution of 2048, but relatively few support 4096 and only professional level cards and some of the newest DirectX 10 cards support 8192. Obviously higher resolution images will take more memory and more time to read, but will look much better when zoomed in.

Georeferencing Method: There are 8 different texture mapping modes as follows:

1. Map to Min/Max - Map image to the min/max extents of the input surface, or a user-defined value (can be typed into overlay_aerial directly).

2. Translate - Translate the image. Only requires a single GCP. No rotation or scaling is performed.

3. 2 pt: Trans./Rot. - Translate, Scale, and rotate the image. The image scaling is always the same in X&Y. Only a valid option if you have 2 GCP points. Good option if you only know 2 GCP points, and they are co-linear or near co-linear.

4. Translate/Scale - Translate and scale the image. Scale in X and Y are not the same. This keeps the image orthorectified. Can be used with 2 or more GCP points.

5. Affine - Perform a full affine transformation (1st order transformation) on the image. Requires a world file or 3 or more GCP points (from a gcp file). This is the default option which can be fully described with a World File.

6. 2nd Order - Perform a 2nd order polynomial transformation. This requires 6 or more GCP points (from a gcp file). It will map straight lines in the image into arcs. Allows an image that was georeferenced previously into LAT/LON coordinates to be “straightened” out and handled correctly. This can also be used to adjust for minor problems in the image due to topography. This option cannot be described with a World File because it uses a second order polynomial with more terms than are available in a world file. It requires the use of a GCP file.

7. 3rd Order - Perform a 3rd order polynomial transformation. Requires 10 or more GCP points. Allows you to adjust for drift in the image, “wedge” shaped photography, and more.

8. 4th Order - Perform a 4th order polynomial transformation. Requires 15 or more GCP points. Allows adjustments to be made where different portions of the image move in opposite directions. Requires many GCP points to use effectively.

Image Processing: These options allow for the adjustment of image brightness, sharpness, etc..

Image Projection Options: This toggle allows for the reprojection of the image. Each coordinate system is divided into either Geographic or Projected coordinate systems. The coordinate system types are navigated by selecting the appropriate system type in the far left window. When a general coordinate system has been selected a specific coordinate system can be selected from the center window. If there are any details regarding the selected specific coordinate system, they will appear in the text window on the right. A specific coordinate system must be selected both to project from and to project to, and then the Project Image toggle must be turned on.

texture_cross_section allows you to apply images along a complex non-linear cross section (cross-section) path and compensate for the image scale and registration points at various points along the fence path.

This functionality provides the mechanism to accurately apply hand-drawn cross-sections to 3D fence diagrams. When combined in an application with edit_horizons, texture_cross_section allows you to modify your 3D stratigraphic geology to accurately match your hand-drawn cross-sections.

texture cell sets

The texture cell sets module will texture multiple images onto a field based on the geologic data in the field.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Object [Renderable]: Outputs to the viewer.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: controls the placement and scale of the textures
• Image Processing: allows for the alteration of the image brightness, contrast, etc.

texture_walls

General Module Function:

The texture_walls module provides a means to project an image onto surfaces such as walls of buildings to add more realism to your visualizations.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Object [Renderable]: Outputs to the viewer.

Properties and Parameters

The Properties window is arranged in the following groups of parameters:

• Properties: controls the placement and scale of the texture
• Image Processing: allows for the alteration of the image brightness, contrast, etc.

export georeferenced image

This module will output a image in one of the following formats: BMP; TIF; JPG; and PNG. It will also output a world file that will allow the image to be placed correctly in applications that allow georeferencing.

Module Input Ports

• Objects [Renderable]: Receives one or more renderable objects similar to the viewer

fly_through

fly_through is an animation module which facilitates controlling the viewer or creating an animation in which the view follows a complex 3D path:

• on,
• through, or
• around your model.

The method by which this module controls fly-throughs allows the user to pause at any time and interact with the model using their mouse or the Az-Inc panel.

Az-Inc parameters (azimuth, elevation, scale, field of view, rotation/scaling center, etc.) are updated by fly_through in real time. This can be seen by running fly_through with the Az-Inc window open. However, please note that this will slow your animation substantially because of the need to continously update the parameters in Az-Inc.

IMPORTANT NOTE: Be sure to TURN OFF “Animate viewer” in the Animator module if you’re controlling fly_through with the Animator.

texture_sphere

texture_sphere  provides a means to (texture map) project images onto a sphere.

texture_cylinder

texture_cylinder  provides a means to (texture map) project images onto a cylinder.

The read eft module provides a mechanism to open saved OBJ file sets which require multiple files (geometry and textures) as a single file. This is required in order to Package Files which is a requisite step in the creation of EVS Presentations.

read_tcf

The read_tcf module is specifically designed to create models and animations of data that changes over time. This type of data can result from water table elevation and/or chemical measurements taken at discrete times or output from Groundwater simulations or other 3D time-domain simulations.

The read_tcf module creates a field using a Time Control File (.TCF) to specify the date/time, field and corresponding data component to read (in netCDF, Field or UCD format), for each time step of a time_data field. All file types specified in the TCF file must be the same (e.g. all netCDF or all UCD). The same file can be repeated, specifying different data components to represent different time steps of the output.

read_tcf effectively includes internal interpolation between appropriate pairs of the files/data_components specified in the TCF file. Its internal structure only requires reading two successive time steps rather than the complete listing of time steps normally represented in a time_data field.

Module Input Ports

• Date [Number] Accepts a date

Module Output Ports

• Start Date [Number] Outputs the starting date
• End Date [Number] Outputs the ending date
• Date [Number] Output date
• Output Field [Field] Outputs the data field

• TCF File

  TCF File Format and Example The listing below is the full contents of the Time Control File control_tce_cdf.tcf. Blank lines or any lines beginning with a “#” are ignored. Valid lines representing time steps must be in order of ascending time and consisting of: a) a date and/or time in Windows standard format b) a file name with an absolute path or just the filename (if the data files are in the same directory as the TCF file). This is not a true relative path (..\file.cdf and subdir\file.cdf don’t work, but file.cdf does), but gives some of the relative path abilities.

read_multi_tcf

The read_multi_tcf module is one of a limited set of Time_Data modules. These modules are specifically designed to create models and animations of data that changes over time. This type of data can result from water table elevation and/or chemical measurements taken at discrete times or output from Groundwater simulations or other 3D time-domain simulations.

The read_multi_tcf module creates a field using one or more Time Control Files (.TCF). Click here for an example of a TCF fileand a description of the format.

The read_multi_tcf module creates a mesh grid with the interpolated data from a user specifed number of TCF files (n). It outputs the first data component from the first (n-1) TCF files and all of the time interpolated data components from the nth TCF file.

For example, if you were trying to create a time animation of the union of 3 analytes (e.g. Benzene, Toluene & Xylene), read_multi_tcf allows you to select all three separate TCF files. Only the first data component from Benzene.tcf (nominally the concentration of benzene) is output as the new first data component. The first data component from Toluene.tcf (nominally the concentration of toluene) is output as the new second data component. All of the data components from Xylene.tcf are then output (typically xylene, confidence_xylene, uncertainty_xylene, Geo_Layer, Material_ID, Elevation, etc.). This allows you to explode layers and do other typical subsetting and processing operations on the output of this module.

The TCF files should be created using identical grids with date ranges that overlap the time period of interest.

read_multi_tcf effectively includes an inter_time_step module internally in that it performs the interpolation between appropriate pairs of the files/data_components specified in the TCF file. Its internal structure only requires reading two successive time steps rather than the complete listing of time steps normally represented in a time_data field.

• TCF File

  TCF File Format and Example The listing below is the full contents of the Time Control File control_tce_cdf.tcf. Blank lines or any lines beginning with a “#” are ignored. Valid lines representing time steps must be in order of ascending time and consisting of: a) a date and/or time in Windows standard format b) a file name with an absolute path or just the filename (if the data files are in the same directory as the TCF file). This is not a true relative path (..\file.cdf and subdir\file.cdf don’t work, but file.cdf does), but gives some of the relative path abilities.

time_value

The time_value module is used to parse a TVF file consisting of dates, values, and (optional) labels. The starting and end dates are read from the file and the controls can be used to interpolate the values to the date and time of interest.

Module Input Ports

• Date [Number] Accepts a date

Module Output Ports

• Start Date [Number] Outputs the starting date
• End Date [Number] Outputs the ending date
• Date [Number] Output date
• Current Date and Time Label [String] Resulting string for the output date
• Current Date and Time Value [Number] Resulting value for the output date

• TVF File Format

  TVF files provide a way to generate a time varying numeric and option string (label). The file is similar to the TCF file, but does not reference info

time horizon

The time horizon module allows you to extract a surface from a set of time-based surfaces. The time for the extracted surface can be any time between the start and end of the surface set. It will interpolate between adjacent known times.

time_loop

General Module Function

The time_loop module is one of a limited set of Time_Data modules. These modules are specifically designed to create models and animations of data that changes over time. This type of data can result from water table elevation and/or chemical measurements taken at discrete times or output from Groundwater simulations or other 3D time-domain simulations.

The time_loop module allows you to loop through a series of times or specify a time for interpolation from a time field.

group objects

group objects is a renderable object that contains other subobjects that have the attributes that control how the rendering is done. Unlike DataObject, group objects does not include data. Instead, it is meant to be a node in the rendering hierarchy that groups other DataObjects together and supplies common attributes from them. This object is connected directly to one of the viewers (for example, Simpleviewer3D) or to another DataObject or to group objects. A group objects is included in all the standard viewers provided with the EVS applications chooses.

Module Input Ports

• Input Objects [Field] Accepts any number red object ports from modules to be grouped

Module Output Ports

• Output Object [Renderable]: Outputs to the viewer.

group objects combines the following:

* DefaultDatamap to convert scalar node or cell data to RGB color values. By default, the datamap’s minimum and maximum values are 0 and 255, respectively. This datamap is inherited by any children objects if they do not have their own datamaps.

* DefaultProps to control color, material, line attribute, and geometrical attributes.

* DefaultModes to control point, line, surface, volume, and bounds rendering modes.

* DefaultPickInfo to contain information when this object is picked.

* DefaultObject to control visibility, pickability, caching, transform mode, surface conversion, and image display attributes.

group objects to 2d overlay

The group objects to 2d overlay moduleprovides a module that applies any connected module’s output to the viewer’s 2D overlay. Objects in the overlay are not transformed (rotated, zoomed, panned). These objects are locked in position. This provides a mechanism to apply graphics like drawing title blocks or company logos.

However, you must ensure that the object sent to the 2D overlay fits inside its limited spatial extent. The 2D overlay is a window with an x-extent from -1.0 to 1.0. The y-extent is dependent on the aspect ratio of the viewer. With a default viewer having a 4:3 aspect ratio, it is three-quarters of the x-extent (e.g. -0.75 to 0.75).

trigger_script

The trigger_script module provides a powerful way to link parameters and actions of multiple modules. This gives you the ability for a sequence of events to be “triggered” as the result of one or more parameters changing.

The modules requires a Python script be created, which runs when you “Add” triggers. Triggers are module parameters that might change and thereby cause the script to be run. The script can do just about ANYTHING.

In addition to the Triggers that you specify, there are 4 input (and output) ports that accept numbers (such as a plume level) that can be used in your script, and are more readily accessible without accessing the Python script.

Module Inpu & Output Ports

• N1 [Number] Accepts a number
• N2 [Number] Accepts a number
• N3 [Number] Accepts a number
• N4 [Number] Accepts a number

merge_fields

merge_fields combines the input fields from up to 4 separate inputs into a unified single field with any number of nodal data components, which can be output to other modules (for processing), OR directly to the viewer. This is useful when you want to slice through or otherwise subset multiple fields using the same criteria (modules).

You must be aware that fields contain more than just grids and data. They contain meta-data set during the creation of those grids and data, including, but not limited to:

• Data Processing (log or linear)
• Coordinate units
• Data units (mg/kg or %)
• Data Min and Max values (ensures that datamaps from kriging match datamaps in post samples)

NOTE: There are potential dangers and serious consequences of merging fields because we allow for merging of data without requiring strict name or meta data matching.

• Meta data from the leftmost input field is always used for the merged result.

• You can only merge fields having the same number of nodal and/or cell data components.

• We do not require strict name matching, therefore it is possible to merge data with very negative consequences. Examples are:

  • Benzene data from one input field with Toluene from another field.
  • Log Processed TPH data with linear processed TPH data.
  • One field with coordinate units of meters with another in feet.

• Overlapping Volumes: When you merge fields you must be aware that this is not an alternative way to create the union of multiple plumes.

  • The merge fields modules does not remove overlapping volumes.
  • Volume calculations with volumetrics can count overlapping regions multiple times giving nonsensical values.

The Merge Cell Sets When Possible option works only if you have matching types and names. A good, and appropriate example is merging fault blocks so that all “Clay” cell sets are controlled as a single entity.

Module Input Ports

• First Input Field [Field] Accepts a data field.
• Second Input Field [Field] Accepts a data field.
• Third Input Field [Field] Accepts a data field.
• Fourth Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the field with all inputs merged
• Output Object [Renderable]: Outputs to the viewer.

float_math

This module provides a simple means to perform mathematical operations on numbers coming from up to 4 input ports. By using multiple float_math modules, any number of values may be combined.

The panel for float_math is shown above. The default equation is f1 + f2 + f3 + f4 which adds all four input ports.

Pop-upAvailable Mathematical Operators hereorJump to Available Mathematical Operators here

Any of these operators may be used.

The output (rightmost output port) is the numeric value resulting from the equation.

The value will update when any of the input values are changed unless the checkbox next to the input value is turned off.

Module Input Ports

• Input Value1 [Number] Accepts number 1
• Input Value 2 [Number] Accepts number 2
• Input Value 3 [Number] Accepts number 3
• Input Value 4 [Number] Accepts number 4
• Input String 1 [String] An input string

Module Output Ports

• Output Value1 [Number] Outputs number 1
• Output Value 2 [Number] Outputs number 2
• Output Value 3 [Number] Outputs number 3
• Output Value 4 [Number] Outputs number 4
• Output String 1 [String] An input string
• Result Value [Number] The final output

create_tin

The create_tin module is used to convert scattered sample data into a three-dimensional surface of triangular cells representing an unstructured mesh.

“Scattered sample data " means that there are discrete nodes in space. An example would be geology or analyte (e.g. chemistry) data where the coordinates are the x, y, and elevation of a measured parameter. The data is “scattered” because there is not necessarily an implicit grid of data.

create_tin uses a proprietary version of the Delaunay tessellation algorithm.

Module Input Ports

• Input Points [Field] Accepts a data field of points or uses the nodes (points) from lines

Module Output Ports

• Output Field [Field] Outputs the surface data field
• Output Object [Renderable]: Outputs to the viewer.

material_to_cellsets

material_to_cellsets is intended to receive a 3D field into its input port which has been processed through a module like plume. If the original field (pre-plume) had multiple cell sets related to geologic units or materials the output of plume will generally have only two cell sets which comprise all hexahedron and all tetrahedron cells. The ability to control the visibility of the layer-cell sets is normally lost.

This module takes plume’s output and recreates the cell sets based on nodal data. However, since each geologic layer will likely have two cell sets each (one for all hexahedron and all tetrahedron cells), the output tends to have twice as many cell sets as the original pre-plume field).

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the processed field.

loop

The loop module iterates an operation. For example, you could use a loop object to control the movement of an object in your application; such as incrementing the movement of a slider for a slice plane.

modify_data_3d

The modify_data_3d module provides the ability to interactively change data in 3D volumetric models. This is not a recommended practice since volumetric models created in EVS generally have underlying statistical measures of quality that will be meaningless if the data is modified in any way.

However, it is not unusual for a model to occasionally have regions where extrapolation artifacts cause shards of plumes to appear. This module provides a way to remove those.

The basic approach is to move the modification sphere to the problem region and set the size and shape of the ellipsoid before changing your data.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration).
• Input Field [Field] Accepts a data field from 3d estimation or other similar modules.

Module Output Ports

• Output Field [Field] Outputs the field with modified data
• Sample Data [Renderable]: Outputs to the viewer

The figure below shows the cloud of points display from this module. Note the adaptively gridded regions with clusters of nodes!

Note: This module does not modify the upstream data.

Delete this text and replace it with your own content.

viewer

The viewer accepts renderable objects from all modules with red output ports to include their output in the view.

Module Input Ports

• Objects [Renderable]: Receives renderable objects from any number of modules

Module Output Ports

• View [View / minor] Outputs the view information used by other modules to provide all model extents or interactivity

viewer Properties:

The user interfaces for the viewer are arranged in 10 categories which cover interaction with the scene, the characteristics of the viewer as well as various output options.

• These features are all available in the Viewer Properties and many of them are accesible in the Viewer Contents. The categories are:

1. Properties: includes the ability to set the view (Azimuth, Inclination, Scale, Perspective, etc.), pick objects and probe their data and control how the view scale reacts as new objects or data are added to the scene.
2. Window Size: sets the size of the viewer. The view has apparent size (the size of the visible window) and the true image size. Outputting a high resolution image involves setting a true image size to match your desired output dimensions.
3. Output Image: includes the ability to export the view in PNG, BMP, JPG, or TIF format. Additional view scaling options are included.
4. Distance Tool: provides an interactive means to measure the distance between points in the viewer’s scene and to export the line between two points in C Tech’s ELF format.
5. Background: sets the style and colors for the background.
   1. The default, 2 color background will be saved in 4DIMs and will display in all output.
   2. Use Unlocked Background for VRML output. Please note that Unlocked Backgrounds are not inherited in a 4DIM and therefore the background can be changed.
6. View: provides controls for depth sorting.
7. Lights: provides the ability to control one or more lights in the scene and their properties.
8. Camera: provides detailed controls over the camera’s interaction with the scene of objects.
9. Record 4DIM: provides the ability to export the scene in C Tech 4DIM format. Please note that 4DIMs have been officially supplanted by CTWS and will likely be deprecated in late 2024.
10. Write_VRML: provides the ability to export the scene for 3D printing.

Object Manipulation in the viewer

When the viewer is instanced, it opens a window in which objects connected to the viewer are rendered and can be manipulated. Objects can be transformed and scaled in the viewer window by using combinations of mouse actions and various keys on the keyboard.

• Rotation of objects in the viewer is accomplished by clicking and dragging on any portion of the viewer window with the left mouse button.
• Translation of objects in the viewer is accomplished by clicking and dragging on any portion of the viewer window with the right mouse button.
• Zooming of an object in the viewer is accomplished using the mouse wheel. Alternatively by depressing the Shift button while clicking and dragging the middle-mouse towards the upper right to zoom IN or lower left to zoom OUT.

• output images

  Output Images The View Scale parameter allows you to specify that your image to be output will be “n” times larger (or smaller if a fraction less than 1.0 is specified) than your current Window Size When the Autoscale FF Font toggle is selected all Forward Facing fonts in the image will be scaled depending upon the size of the output image.

• Recording (Capturing) 4DIM Files

  Recording (Capturing) 4DIM Files The Record 4DIM output option in the Viewer provides the ability to export in C Tech’s proprietary 4DIM vector animation format. Limitations In some circumstances transform_group cannot be used with 4DIMs. It can cause the 4DIM extents to be different than they were in the EVS viewer. This has been noted when doing rotations. In most cases, the transform_field module can be used instead, however it does not allow for multiple objects to be connected to its input. volume_renderer is not compatible with 4DIMs 4DIM files will not record any object whose cache has been disabled. This occurs when large fields are connected to the viewer. When this occurs (for external_faces in this example), the following message appears in the Status Window: — Warning from: module: external_faces —

• write vrml

  write_vrml The write_vrml output in the viewer is able to output most graphics objects in the viewer to a VRML-formatted file. VRML is a network transparent protocol for communicating 3D graphics. It has fallen out of favor on the web, though it is still a standard for 3D model output. We provide VRML output for two primary purposes:

scat_to_unif

The scat_to_unif module is used to convert scattered sample data into a three-dimensional uniform field. Also, scat_to_unif can be used to take an existing grid (for example a UCD file) and convert it to a uniform field. scat_to_unif converts a field of non-uniformly spaced points into a uniform field which can be used with many of EVS’s filter and mapper modules. “Scattered sample data " means that there are disconnected nodes in space. An example would be geology or analyte (e.g. chemistry) data where the coordinates are the x, y, and elevation of a measured parameter. The data is “scattered” because there isn’t data for every x/y/elevation of interest.

scat_to_unif lets you define a uniform mesh of any dimensionality and coordinate extents. It superimposes the input grid over this new grid that you have defined. Then, for each new node, it searches the input grid’s neighboring original nodes (where search_cube controls the depth of the search) and creates data values for all the nodes in the new grid from interpolations on those neighboring actual data values. You can control the order of interpolation and what number to use as the NULL data value should the search around a node fail to find any data in the original input.

Module Input Ports

• Input Field [Field] Accepts a data field

Module Output Ports

• Output Data [Field] Outputs the volumetric uniform data field

merge_fences

The merge_fences module is used to merge the output from multiple krig_fence modules into one data set (i.e., to merge cross sections into a fence diagram). This is useful for performing uniform data manipulation procedures on fence data from several krig_fence outputs. For example, if several krig_fence modules are used, they should all pass through a merge_fences module before being passed to explode and scale. Therefore, all fences will be exploded and scaled the same amount and only one dialog box is needed to control all fences. merge_fences should always be used when more than one krig_fence module is used.

Module Input Ports

• First Input Field [Field] Accepts a data field.
• Second Input Field [Field] Accepts a data field.
• Third Input Field [Field] Accepts a data field.
• Fourth Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the field with all inputs merged

project_field

General Module Function

The project_field module is used to project the coordinates in any field, from one coordinate system to another.

Module Control Panel

The control panel for project_field is shown in the figure above.

Each coordinate system is divided into either Geographic or Projected coordinate systems. The coordinate system types are navigated by selecting the appropriate system type in the far left window. When a general coordinate system has been selected a specific coordinate system can be selected from the center window. If there are any details regarding the selected specific coordinate system, they will appear in the text window on the right. A specific coordinate system must be selected both to project from and to project to as in the picture below.

Module Input Ports

• Input Field [Field] Accepts a data field.

Module Output Ports

• Output Field [Field] Outputs the subsetted field as faces.

geologic_surfmap

This module is deprecated and replaced by project onto surface.

geologic_surfmap provides a mechanism to drape lines onto Geologic surfaces. It compares to project onto surface, but lines are not subsetted to match the size of the cells of the surface on which the lines are draped. In other words, only the endpoints of each line segment are draped.

Module Input Ports

• Z Scale [Number] Accepts Z Scale (vertical exaggeration).
• Input Geologic Field [Field] Accepts a geologic field
• Input Lines [Field] Accepts a field with the lines to be draped