The application’s user interface is highly customizable, allowing you to arrange tool windows like the Viewer, Properties, and Application Network to best suit your workflow. Windows can be “docked” to the edges of the main application or other window, grouped with other windows in tabs, or “floated” as independent windows on your desktop. This flexibility enables you to create a personalized layout that keeps the tools you need most frequently within easy reach.

Window Title Bar and Context Menu

Each tool window has a title bar containing several controls for managing its state. You can access these functions by right-clicking the title bar or by using buttons provided on the title bar directly.

Undocking and Floating Windows

A floating window is one that is detached from the main application window and can be moved freely around your screen, even to a second monitor. To make a window float:

• Drag the Title Bar: Click and hold the title bar of any docked window and drag it away from the edge. As you drag it towards the center of the screen, it will detach and become a floating window.
• Drag the Tab: For windows docked as tabs in same pane as other windows, drag the window by its tab.
• Use the Context Menu: Open the window’s context menu and select the Float option. The window will immediately detach from its docked position.

Docking Windows

To dock a floating window, simply drag it by its title bar. As you move it over the main application window or any floating window, a set of docking guide icons will appear. Dropping the window onto one of these icons will dock it to the corresponding location.

• Edge Docking: The four arrow icons at the edges of the screen will dock the window to the top, bottom, left, or right side of the main application, spanning its full width or height.
• Pane Docking: The five-icon control that appears in the center of an existing window pane allows for more precise placement. The four outer arrows will dock the window to the side of that specific pane, creating a split view. The center icon will dock the window as a new tab within that pane group.
• Document Area: One pane is designated as the central document area. It occupies the main, central space of the application window. The other docking guides for top, bottom, left, and right positions are usually arranged around this central area.
• Context Menu Docking: You can also use the context menu of a floating window. Dock will typically return it to its last docked position, while Dock as Document will place it as a tab in the central document area.

Note: The Application window is the central point of any EVS application and layout. It can only be either docked in the Document Area or made a floating window.

Auto-Hiding Windows (Pinning)

The Auto-Hide feature allows you to keep windows accessible without them permanently taking up screen space. You can control this using the pin icon in the window’s title bar or the Auto Hide option in the context menu.

• Pinned (Vertical Pin): When the pin icon is vertical, the window is pinned open. It will remain visible in its docked location.
• Unpinned / Auto-Hidden (Horizontal Pin): When the pin icon is horizontal, the window is set to auto-hide. It will collapse into a named tab on the edge of the window. To temporarily view it, simply hover your cursor over its tab. It will slide out for you to use and slide away again when you move your cursor off it. To keep it open, click the pin icon to return it to the pinned state.

Saving and Loading Layouts

When you created a layout you like, you can save it through the Options in the Menu. Layouts can be switched to previously saved ones through either the Menu or the Window Layouts button in the Main Toolbar.

Presentation Mode optimizes the user interface for interacting with a completed application. It simplifies the workspace by hiding development-focused UI elements, allowing you to focus on the application’s controls and outputs.

Accessing Presentation Mode

You can enable Presentation Mode using the Presentation Mode button in the Main Toolbar.

Presentation mode can be left using the Edit Mode button in the Main Toolbar. This button is only visible when Presentation Mode is active.

Purpose of Presentation Mode

Presentation Mode provides a cleaner, more streamlines experience ideal for presenting your work or for any scenario where you are primarily executing and interacting with the application rather than building or modifying it.

For this reason, the following elements are hidden or inactive:

• Application Window: The window containing the application workflow and for adding new modules is hidden.
• Module and Port Connections: The ability to create or modify connections between modules is disabled.
• Main Toolbar: Most buttons focused on creating applications are hidden.

Presentation Mode vs. EVS Presentation Files

While Presentation Mode is similar to the view when loading an EVS Presentation file, it is less restrictive. An EVS Presentation file (.evsp) is a self-contained, read-only version of an application that limits user editing and intended for delivery to end users. Its main purpose is for distribution to clients who need to run an application and change predetermined properties, but not modify it.

In contrast, Presentation Mode still allows for editing of module and application properties and options. It is merely a simplified user interface. This provides a flexible way to display interactive applications that are simplified for presentations but not entirely locked down.

Accessing Help

The help can be found through the Help Windows button in the Main Toolbar.

General Application Help

For general information, searching, and browsing all help topics, you can use the main Help window.

1. In the Main Toolbar, click the Help Windows button.
2. From the dropdown menu, select Contents.

This action opens the main Help window, where you can search for topics.

Module-Specific Help

When the Module Help window is opened, any module being edited (selected in the application window) will also show its help contents in the Module Help window. As you edit different modules, the Module Help will reflect the currently selected module.

To get help for a module which hasn’t been instanced, follow these steps:

1. Hover your mouse over the question mark in the desired module in the Module Library.
2. Wait for the module’s tooltip to appear:
   1. 
3. While the tooltip is visible, press the F1 key.

This will open the Module Help window containing specific information for that module.

The Tools menu provides a collection of utilities for file conversion, data processing, and creating animations. These tools are designed to help you prepare your data for use in EVS.

Accessing Tools

The Tools button can be found in the Main Toolbar. Clicking it will open a list of available tools.

Tool Buttons

EVS Input File Conversions

This section contains tools for processing and converting various data files into formats optimized for EVS.

Image and Animation Tools

This group of tools helps you create animations and prepare images for use in your projects.

Legacy File Processing

This section provides tools for working with older, outdated file formats.

• Images To Animation

  The Images To Animation tool allows you to compile a sequence of individual image files into a single video animation. This is ideal for creating time-lapse visualizations, showcasing model changes over time, or presenting a series of related images, for example written by EVS through sequences and Python Scripting, as a dynamic video.

• Georeference Image

  The Georeference Image tool is a useful utility for assigning real-world geographic coordinates to raster images. This process, known as georeferencing, allows you to accurately overlay images with other spatial data in your project. The tool enables you to create and edit world files (e.g., .jgw, .tfw) or ground control point files (.gcp), which store the image’s location, scale, and orientation information.

Opening Projects

The Open screen, accessible from the main application Menu, provides a comprehensive interface for loading existing projects. It is designed to give you quick access to your recent work, sample files, and any project on your system, complete with metadata and visual previews to help you find the right file quickly.

File Access Options

Info

While applications on network drives or shared drives may load, our customers often experienced file locking or similiar access issues when saving them. For the best experience, we recommend loading applications from a local filesystem if possible.

| | Recent Documents | The default view, offering the quickest way to resume work. It presents a scrollable and searchable list of your most recently accessed projects, ordered from newest to oldest. | | Custom Path | Acts as a configurable bookmark for frequently used folders. Once you set a directory in the application’s options, this button lists all application files in that location, saving you from navigating to it manually.

Note: The Custom Path option will not recurse subdirectories. Only application files directly in the favorited directories will be shown.
| | Sample Projects | Provides access to a curated collection of official C Tech sample applications that demonstrate best practices and diverse capabilities. These are the applications used in the EVS Training tutorials.

Note: If this list is empty, the C Tech Sample Applications have not been installed. You can obtain the installer from the C Tech website at www.ctech.com.
|

Filtering and Searching

When using the open file views, you can use the search and filter boxes to quickly locate a specific project. These tools are especially useful when dealing with a long list of files.

Project Information and Preview

When you select a file, the right-hand side of the screen populates with detailed information about that project.

The Operation and User Preferences window is the central hub for configuring application-wide settings in Earth Volumetric Studio. It allows you to customize the user interface, set default behaviors for new projects, manage system resources, and personalize user information. Tailoring these settings can significantly improve your workflow and efficiency.

To access this window, click the Options button on the main application menu located on the left side of the screen.

The window is divided into several logical sections, each handling a different aspect of the application’s configuration.

The options on the left side are all user preferences, and determine the look, feel, and operation of EVS for the current user. The options on the right side change the default values used for new modules and applications.

User

This section specifies the active user and their organization. This information is saved with .evs application files and other outputs, helping to track authorship and ownership of projects.

System

The System section controls settings that impact the core operation of EVS system-wide, including file handling, hardware utilization, and integration with external tools like Python.

Setting	Description
Open EVS Files With Existing Instance	When enabled, any .evs file you open from Windows File Explorer will launch within the currently running instance of Earth Volumetric Studio. If disabled, a completely new instance of the program will be launched for each file.
Processing settings	This section allows you to manage how EVS utilizes your computer’s hardware.

• **Logical Processors (CPU) to keep unused**: Reserves a specific number of your CPU's logical processors (cores/threads) for the operating system and other applications. This prevents EVS from consuming 100% of your CPU during intensive calculations, keeping your system responsive.
• **Use GPU for fast calculations**: When enabled, EVS leverages your graphics processing unit (GPU) to accelerate certain calculations. It is recommended to keep this enabled if you have a dedicated graphics card.
• **Force Emulated GPU**: An advanced troubleshooting setting. It forces EVS to use a software-based GPU emulator instead of your physical graphics card, which can help diagnose graphics-related issues but at a significant performance cost.

User Interface Options

This section controls the visual appearance and layout of the EVS user interface.

Setting	Description
Theme	Choose a visual theme for the application. For more details, see the Themes topic. Light: A bright theme with dark text. Dark: A dark theme with light text, which can reduce eye strain.
Window Layouts	Save, manage, and apply different arrangements of the application’s windows. For more about creating layouts, see Docking and Undocking Windows and Windows and Layout.

• **Layout List**: Displays all saved layouts.
• **+ / - Buttons**: Save the current window arrangement as a new layout or delete the selected layout.
• **Apply Selected Layout**: Applies the window positions from the selected layout.
• **Overwrite Current Layout**: Updates the selected layout with the current arrangement of windows.
• **Revert to Default**: Resets the selected layout to its original state.

• **Full Size**: The default style, featuring large icons with descriptive text.
• **Comfortable**: A more compact style with smaller icons and text.
• **Compact**: A minimal style with icons only.
• **Display in Title Bar**: Moves the toolbar into the application's title bar to maximize vertical space.

• **Hide Viewer Connections**: Hides connection lines to and from Viewer modules to reduce visual clutter.
• **Always Display Minor Ports**: When enabled, all module ports are visible. When disabled, less-used "minor" ports are hidden until you hover over the module.
• **Connection Checking**: Determines how strictly EVS validates module connections. "Strict Checking" ensures data types are perfectly compatible.
• **Connection Style**: Sets the visual style of connection lines (Curved or Straight).
• **Highlight Potential Connections**: Controls which available ports are highlighted as valid targets when dragging a connection (Major Ports Only, Include Minor Ports, or None).
• **Max Potential Connections**: Limits the number of potential connections highlighted at once to maintain performance.

• **Display Expert Properties**: Reveals advanced or less commonly used module parameters.
• **Always Show Critical Properties**: Ensures that important parameters are always visible, even if their category is collapsed.
• **Automatically Collapse Categories**: When enabled, all property categories collapse when you select a new module.

• **Include Deprecated Modules**: Shows older modules kept for backward compatibility.
• **Automatically Collapse Module Categories**: When enabled, all module categories in the Module Library will be collapsed by default.

New Module and Application Default Settings

This area defines the default settings that are applied to new applications, modules, and data processing tasks.

New Application Defaults

Setting	Description
Z Scale	Sets the default vertical exaggeration (Z-Scale) for new applications.
Explode	Sets the default explode factor for new applications, which pushes modules apart in the 3D viewer.
Application Colors	Sets the default colors for elements in the Viewer window for new applications.

• **Coloring Option**: Select from predefined color schemes (Light, Dark) or choose "Custom" to enable the color pickers below.
• **Background Color**: Sets the solid background color of the Viewer.
• **Gradient Color**: Creates a two-color vertical gradient with the Background Color.
• **Foreground Color**: Defines the default color for text, axes, and other primary annotations.
• **Secondary Color**: Defines the default color for less prominent visual elements.

Module Defaults

Setting	Description
Viewer Settings	Defines the default rendering and behavior for new Viewer modules.

• **Auto Fit Scene**: Controls when the viewer automatically rescales to fit all objects (On Significant Change, On Any Change, or Never).
• **Background Style**: Sets the default background rendering style (Two Color Gradient, Solid, or Vignette).
• **Smooth Lines**: When enabled, applies anti-aliasing to produce thicker, smoother lines.

• **Default Font**: Sets the default font family for text in new modules.
• **Force True Type Fonts**: When enabled, forces modules to use scalable TrueType fonts.
• **Include Language Specific Fonts**: Loads additional font sets for displaying characters from non-Latin languages (e.g., Chinese, Japanese, or Korean).

Model Generation Defaults

Provides fine-grained control over the default parameters used in modules for gridding, data processing, and statistical estimation.

Setting Area	Description
Gridding Defaults	Defines the default settings for new gridding modules like krige_3d.

• **Grid Resolution**: Sets the default number of nodes in the X, Y, and Z dimensions.
• **Boundary Offset**: Defines a default percentage to expand the grid boundary beyond the input data extents.
• **Use Convex Hull**: When enabled, automatically uses the convex hull of the input data as the gridding boundary.
• **Use Adaptive Gridding**: When enabled, uses adaptive gridding techniques by default.

• **Pre Clip Minimum**: Sets the default minimum clipping value applied to data **before** interpolation.
• **Post Clip Minimum**: Sets the default minimum clipping value applied to data **after** interpolation.

• **Horizontal Vertical Anisotropy**: Sets the default ratio of horizontal to vertical anisotropy.
• **Use all samples if # samples below**: When enabled, the module uses all data samples for estimation if the total count is below the specified limit.
• **Number of Points**: Specifies the number of nearby data points to use for estimation.
• **Statistical Confidence Tolerance**: Sets the default tolerance for statistical confidence when data processing is "Linear".
• **Statistical Confidence Factor**: Sets the default factor for statistical confidence when data processing is set to "Log Processing".
• **Confidence for Min and Max Plume**: Sets the default statistical confidence level for determining plume extents.

Reset All Options

The Reset All Options button at the bottom of the window reverts all settings to their original factory defaults. This action is irreversible and affects all sections, so it should be used with caution.

Earth Volumetric Studio features a flexible interface composed of several windows. You can customize their size, position, and docking state to create a layout that suits your workflow.

Customizing Your Workspace with Window Layouts

EVS provides a flexible windowing system that allows you to customize the layout of your workspace. You can control the position, size, grouping, and visibility of most windows to suit your workflow. These customized layouts can be saved and reloaded, which is useful for different tasks or screen resolutions.

For example, here is an application with a personalized window layout:

Window Visibility and Docking

You can manage window visibility and docking using the controls located on each window’s title bar. While most windows can be moved, resized, or closed, there are a couple of exceptions:

1. Application Window: The main area for adding and connecting modules is always part of the main EVS application window, except in EVS Presentations or when working in Presentation mode.
2. Viewer Window: The Viewer cannot be closed, but it can be undocked and moved to another monitor for a multi-screen setup.

Example: Optimizing for a Larger Viewer

You can create different layouts to optimize your workspace. For instance, the layout below is configured to maximize the Viewer’s screen space. Notice how windows are tabbed together to save space:

• The Application and Viewer windows are tabbed, with the Viewer active.
• The Information, Packaged Files, and Output Log windows are tabbed, with the Output Log active.

Saving a Custom Window Layout

Once you have arranged the windows to your liking, you can save the layout for future use.

1. Click the Options button in the Main Toolbar.
2. In the Options window, expand the Window Layouts section.
3. Here you have the option to create a new layout or overwrite the currently active layout.
   1. Create a new layout: Click the + (Add) button to save your current window arrangement as a new layout. It will appear in the list along with any previously saved layouts and the “Default” configuration.
   2. Overwrite the current layout: Click the Overwrite Current Layout button.

Loading or reverting a Custom Window Layout

There are two ways to switch to a different layout.

The Options window

You can load a previous or revert a layout in the same section as described above.

1. Click the Options button in the Main Toolbar.
2. In the Options window, expand the Window Layouts section.
3. Here you have the option to load a layout or revert to the “Default” layout.
   1. Load a layout: Select the desired layout and click the Apply Selected Layout button or alternatively revert to the “Default” layout using the Revert to Default button.
   2. Revert to default: Click the Revert to Default button to revert the current layout to the one saved as “Default”.

The Quick Access Button

You can easily switch between your saved layouts directly from the Main Toolbar.

1. Click the dropdown arrow next to the Window Layouts button in the Main Toolbar.
2. Select your desired layout from the list to apply it instantly.

The Application Properties provide a centralized location to access critical parameters needed to control your application. Any property that impacts the application itself and is not specific to an instanced module will show here.

Accessing Application Properties

The Application Properties are available via a button in the Application Window toolbar:

Alternatively, you can also access these when editing the Application Favorites. When the Application Favorites are displayed in the Properties window, click the Switch to Application Properties button at the top.

Finally, double clicking on the background of the network area will open the Application Favorites or Application Properties (whichever was most recently viewed).

Available Application Properties

Below is the default content of Application properties.

Following is a description of each category:

• Bookmarks

  Bookmarks provide an easy way to save and recall specific configurations of your application. They act as saved “snapshots” that can instantly change the camera view, which objects are visible, and the current state of any sequences. They also export to C Tech Web Scenes. This is essential for creating presentations, standardizing views for analysis, and optimizing the user experience in any exported C Tech Web Scenes.

• Application Colors

  The Application Colors feature provides a centralized way to manage a consistent color palette across your entire application. By setting a few base colors, you can ensure that various annotation modules - such as titles, legends, and axes - as well as the viewer background all share a coordinated and professional look. This feature is particularly powerful when used with linked properties, as it allows you to switch between entire color themes (e.g., from a light to a dark theme) with a single click.

The Application Favorites feature provides a powerful way to create a custom control panel for your EVS application. It allows you to gather the most important properties from various modules and global settings into a single, centralized location within the Properties window.

This is especially useful in large or complex applications, as it eliminates the need to navigate to each individual module to adjust key parameters. Instead, you can manage all critical settings from one convenient view.

Accessing Application Favorites

The Application Favorites are available via a button in the Application Window toolbar:

Alternatively, you can also access these when editing the Application Properties. When the Application Properties are displayed in the Properties window, click the Switch to Application Favorites button at the top.

Finally, double clicking on the background of the network area will open the Application Favorites or Application Properties (whichever was most recently viewed).

The Application Favorites View

Once you switch to the Application Favorites view, you will see a list of all the properties you have marked with a star. The properties are organized into groups based on their source module. For example, global settings like Z Scale and Explode are listed under “Application Properties,” while module-specific properties are grouped under the name of their respective module (e.g., “viewer”).

You can edit any of these properties directly from this view, just as you would in the standard properties editor.

How to Favorite a Property

You can favorite almost any property from any module.

1. Select a module in the Application Network to display its parameters in the Properties window.
2. To favorite a property, click in the empty space to the left of its name. A star icon will appear, indicating that the property has been added to your Application Favorites.

It is important to note that this action favorites the property for that specific instance of the module, not for all modules of that type. This allows you to select different key parameters from different modules. The same property from different modules can appear in the Application Favorites at the same time.

How to Remove a Property from Favorites

To remove a favorited property, simply click the star icon in either the module or the Application Favorites again.

Module Properties

When you select a module in the Application Network, its settings are displayed in the Properties window. This window allows you to configure the module’s parameters and control its execution behavior. At the top of the window, the name of the module you are editing is displayed.

Switch to Display Properties

This button provides a quick way to access the properties of the module’s primary Renderable Port (red) if they are being displayed in a viewer. The Red Port Properties will also feature a button to quickly switch back again.

Execution Control

The toolbar at the top of the Module Properties window provides powerful tools for managing when and how a module executes.

• Run Toggle: This switch controls the module’s automatic execution. By default, it is on, meaning the module will automatically run whenever one of its properties is changed or when an upstream module it depends on finishes running. Toggling this off prevents the module from running automatically. This is particularly useful when you want to make multiple changes to a module’s settings without triggering potentially time-consuming computations after each adjustment. This is also displayed and configurable on the modules in the Application Network. See Module Status Indicators.
• Run Once Button: When available, this button allows you to manually trigger the execution of the currently selected module. It forces the module to run a single time. This is most effective when the Run toggle is turned off, as it lets you apply your changes and see the result without having to re-enable automatic execution.

Module-Specific Properties

Below the execution controls, the Properties section contains all the configurable parameters for the selected module. The settings here are unique to each module’s function. These properties allow you to customize the module’s behavior to fit the specific needs of your analysis.

Property Description

At the bottom of the Properties window is a description panel. This panel is your first and most important resource for understanding what a specific property does. When you select a property from the list, this panel automatically updates to show a detailed explanation of that property and its function. For instance, selecting “Data Processing” will display text explaining that this property allows to declare whether the input data is to be treated as linear or log processed. This immediate, context-sensitive help makes it easy to learn and configure even complex modules without having to consult external documentation.

Here is an example for the Property Description of the “Glyph Size” property:

Understanding Linked Properties

In Earth Volumetric Studio, a Linked Property is a parameter whose value is automatically determined within the application, rather than being manually set by the user. This dynamic connection allows for a more intelligent and consistent workflow. You can identify a linked property by the link icon located next to it in the Properties window

• When the link icon is closed/connected, the property is linked, and its value will update automatically based on its source.
• When the link icon is broken, the property is unlinked, and its value is fixed to whatever you have manually set.

You can toggle a property’s linked state by simply clicking on the link icon.

Linked Property:	Unlinked Property:

Info

Not all properties can be linked. If a property does not have a link icon next to it, it is a manual property. Its value may be set directly by the user and will not change automatically.

The Purpose of Linked Properties

Linked properties are a core feature of the EVS expert system, designed to streamline the modeling process. By linking properties, EVS can ensure consistency across your entire application, provide smart defaults based on your data, and maintain visual coherence. For example, linking the Z Scale of multiple modules to the global Application Z Scale means you only have to change it in one place, but can still unlink and override it as needed. Linked properties may also provide good automatic starting values for further unlinked manual refinement.

While you can unlink any linked property to gain manual control, it is generally recommended to keep properties linked unless you have a specific reason and understand the effect of the change. This approach leads to a faster and better-looking result.

Info

Re-linking a previously unlinked property will cause its value to revert to the automatic, context-driven setting. This change may also trigger the module to re-execute immediately to reflect the new state, unless the module’s Run toggle is turned off.

Common Categories of Linked Properties

Z Scale

This is the most common linked property and the one you should change least often. Nearly every module that deals with 3D data has a Z Scale property that is, by default, linked to the global Z Scale found in the Application Properties. This ensures that all visual components in your scene use the same vertical exaggeration, which is critical for correct spatial representation.

Colors

Many modules that create visual elements, such as titles or legends, have color properties that are linked to the global Application Colors setting. When you switch the application theme between Dark, White, or Custom, these linked colors will automatically adjust to ensure they remain visible and aesthetically pleasing against the new background color. Unlinking a color property, such as Title Color, will fix it to a specific color, and it will no longer adapt to theme changes.

Coordinates

Many modules that process spatial data have coordinate properties (e.g., Min/Max extents) that are linked to the incoming data. When the module is run, it analyzes the input field and automatically populates these properties with the correct coordinate values. If the input data changes, re-running the module will cause these linked properties to update accordingly.

Expert System Parameters

EVS includes an expert system that analyzes your data to provide intelligent, scientifically appropriate default values for complex parameters. This is most common in geostatistical modules like kriging or lithologic modeling. Parameters for kriging and variogram settings are often linked to the expert system, which suggests optimal values based on the input data. Unlinking these properties allows for manual fine-tuning but overrides the data-driven recommendations.

Port Properties

When you double-click an output port on a any module in the Application Network, the Properties window displays detailed information and settings for that specific port. While the properties shown vary depending on the type of data the port provides, certain elements are common to all ports.

At the top of the window, a Switch to Module Properties button provides a convenient way to navigate back to the properties of the module that owns the port.

Common Port Properties

All output ports display a Port Information section with the following properties:

• Red Port Properties (Renderable Port)

  Renderable Object Port Properties In Earth Volumetric Studio, a red port is a Renderable Object port. It outputs a visual object—such as a surface, a set of points, or a volume—that can be displayed in a viewer. By editing the properties of this port, you can control every aspect of how the object is visualized in the 3D scene. See the Visualization Fundamentals section for additional details on rendering options.

• Blue Port Properties (Field Port)

  Field Port Properties In Earth Volumetric Studio, a blue port is a Field Port. It is the most common port type and is responsible for passing grid structures and their associated data between modules. A “field” contains the geometry (nodes and cells) as well as any data values defined on that grid, such as analytical results or material properties.

Introduction to Datamaps

In the fields of scientific and geometric visualization, a datamap is a fundamental concept that serves as the bridge between raw numerical data and its visual representation. At its core, a datamap is a function or a lookup table that translates data values into visual properties, most commonly color. Think of it as a sophisticated legend that instructs the rendering engine how to “paint” the data onto a geometric object, such as a surface, a volume, or a set of points.

Every value in your dataset, whether it represents temperature, contaminant concentration, pressure, or a geologic material type, is assigned a color based on the rules defined in the datamap. This transformation is what turns an abstract collection of numbers into an intuitive and immediately understandable visual model. Without datamaps, a 3D model of contaminant distribution would be a colorless, featureless shape, providing no insight into where the highest concentrations are or how they vary in space. The datamap is what brings the data to life, allowing us to see the patterns, trends, and anomalies that would otherwise be hidden in spreadsheets and data files.

The Purpose of Datamaps in EVS

In Earth Volumetric Studio, datamaps are the primary tool for communicating the meaning of your data within a visual context. Their purpose extends beyond simply making things colorful; they are a critical component of data analysis and presentation for several key reasons.

First, they make complex data interpretable. A bright red area in a plume model is instantly recognizable as a “hotspot” of high concentration, while a transition from green to blue can clearly show the gradient where values are decreasing.

Second, they provide a quantitative reference. A well-designed datamap, coupled with a legend, ensures that the visualization is not just a pretty picture but a scientifically accurate representation. Each color corresponds to a specific data value or range, allowing a viewer to probe any point on a model and understand its precise quantitative meaning.

Finally, they are essential for highlighting features of interest. Data in environmental and geological sciences often spans many orders of magnitude. A datamap can be carefully designed to focus the visual contrast on the most critical parts of the data range, making subtle but important variations stand out while de-emphasizing less relevant data.

Types of Data and Datamap Processing

Datamaps in EVS are highly flexible and can be configured to handle different types of data and distributions. The way a datamap translates values to color can be linear, non-linear, or categorical.

Linear Datamaps

A linear datamap applies a smooth, uniform color gradient across the entire range of the data. The relationship between a data value and its position in the color gradient is a straight line. For example, in a dataset ranging from 0 to 1000, a value of 500 would be mapped to the exact middle of the color ramp. This type of mapping is best suited for data that is evenly distributed and where the importance of changes is consistent across the entire range, such as a simple temperature scale.

Non-Linear Datamaps

A non-linear datamap is used when the data is not uniformly distributed or when certain ranges are more important than others. In this case, the relationship between data values and colors is not a straight line. This allows you to allocate more “color space” to the most critical parts of your data range.

A classic example is contaminant concentration data, which might range from 0.01 to 10,000. If a linear datamap were used, most of the color gradient would be dedicated to the high-end values, making it impossible to distinguish between low-level concentrations (e.g., 0.1 vs. 1.0), which might be the most critical range for regulatory purposes. A non-linear datamap can be configured to stretch the color gradient across the lower values, providing high visual contrast where it is needed most.

The colors of breaks on both sides don’t have to be continuous. If the Lock Adjacent Breaks toggle in the Datamap Editor is disabled, you can choose both colors separately.

A note on precision: Due to the nature of precision in floating-point calculations, a value that is identical to a break point can be categorized into either the adjacent upper or lower interval. If you need to ensure a specific value is colored correctly, we recommend slightly shifting the break point. For example, changing a break from 500.0 to 500.0001 ensures the value 500.0 falls into the lower interval.

Categorical Data

Datamaps are also used for categorical data, which is qualitative rather than quantitative. Examples include geologic material types (“Sand”, “Clay”, “Gravel”), land-use classifications, or sample location IDs. For this type of data, the datamap assigns a single, discrete color to each unique category. There is no gradient or blending between colors. In EVS, this is typically handled by assigning an integer ID to each category (e.g., Sand=1, Clay=2). The datamap is then configured with distinct colors for each integer value, effectively creating a color key for your categorical data.

Logarithmic Processing

Logarithmic processing is a specific type of non-linear mapping designed for data that spans several orders of magnitude. By taking the logarithm of the data values before mapping them to color, vast ranges are compressed into a more manageable scale. This makes logarithmic datamaps the standard and most effective way to visualize data like hydraulic conductivity or contaminant concentrations. EVS handles this transformation automatically when the log processing option is selected in many modules, so you do not need to manually convert your data. The datamap works with the log-transformed values, but associated legends will still display the original, human-readable values.

• Datamap Editor

  The Datamap Editor is the primary tool in Earth Volumetric Studio for creating and customizing the mapping between your data values and the colors used to represent them in a visualization. It provides a powerful, interactive interface to control color gradients, data ranges, and scaling, allowing you to effectively highlight the features of interest in your data.

The Module Library is a core component of the Application window, serving as the repository for all modules used to build data processing and visualization workflows. It is located on the left side of the Application window and a fixed part of it. Unlike most other windows, it cannot be undocked, but it can be hidden when not in use.

Modules are organized into collapsible categories, such as Estimation and Geology, allowing you to easily browse and find the tools you need. You can control whether these categories are expanded or collapsed by default in the Options menu of the Application window. To add a module to your workflow, simply drag it from the library and drop it onto the Application Network canvas. Alternatively, double clicking a module will also create a new instance on the Application Network.

At the top of the Module Library, you will find controls for searching and docking.

The Search bar allows you to quickly filter the list of modules. As you type, the library will display only those modules whose names match your search query. You can also use the keyboard shortcut Ctrl+M to focus on the search bar, even if the Module Library is unpinned and closed.

Next to the search bar is the Pin button. This button controls the auto-hide behavior of the Module Library. When the library is pinned, it remains permanently visible. If you unpin it, the library will automatically slide away when not in use and can be reopened by clicking the Show Module Library button in the Application window’s toolbar or via the keyboard shortcut Ctrl+M.

Annotations

At the bottom of the Module Library is a set of tools for adding visual annotations to your Application Network. These elements help document your workflow, clarify connections, and organize complex applications. Clicking on an annotation shows contextual menu items such as Delete, Copy, Paste and a coloring option.

The Application Network is the primary workspace in Earth Volumetric Studio for building and managing your data processing workflows. It is a visual, node-based environment where you construct “applications” by placing modules and connecting them to define a data flow from input to final visualization.

Modules

Modules are the fundamental building blocks of an application. Each module performs a specific task, such as reading data, performing a calculation, creating a geometric object, or rendering a scene. They are represented by rectangles on the Application Network, each stating a user-defined name and the module type under it. You add modules to your network by dragging them from the Module Library onto the Application Network canvas.

Each module has a set of icons that appear when you hover over it, providing quick access to key functions:

See Module Icons for more information.

Ports and Connections

Modules communicate with each other through ports. Each module has one or more input ports (on the top) and output ports (on the bottom). You create Connections between modules which define the top-down Data Flow of the application, directing the output of one module to become the input for the next. See the Connecting and Disconnecting Modules topic.

Ports are color-coded to indicate the type of data they handle, and you can only connect ports of a similar color. While there are many port types, the two most critical and frequently used are Field ports and Renderable Object ports.

See Port Colors, Red Port Properties (Renderable Port) and Blue Port Properties (Field Port) for more information about ports.

How to Remove connections

Connections can be removed by selecting the connection with the left mouse button in the Application Network and then either using the DEL key or by clicking the right mouse button and choosing the Disconnect option.

Module Right-Click Menu

Right-clicking on any module in the Application Network opens a context menu that provides quick access to several common actions and properties for that module.

Input Port Context Menu

Right-clicking on a module’s input port opens a context menu providing details and actions for the incoming connection.

Output Port Context Menu

Right-clicking on a module’s output port opens a context menu with information and actions related to that specific port.

• Module Icons

  Modules in the Application Network feature a set of icons directly on their surface that provide at-a-glance information and quick control over their execution and visibility. Modules that can be executed or produce a visible output have icons on their left and right sides. The right-side icon controls execution, while the left-side icon controls visibility in the viewer.

• Module Status Indicators

  Modules in the Application Network display several visual cues to indicate their current status. These indicators help you quickly understand which module is selected, which is being edited, whether a module has run successfully, and if it is set to execute automatically. This allows for efficient management of your application’s workflow. Selection and Editing Status The border of a module changes color to reflect its selection and editing state.

• Connecting and Disconnecting Modules

  Modules in the Application Network are linked together by connections, which represent the flow of data from an output port of one module to an input port of another. Creating and removing these connections is fundamental to building and modifying your application’s workflow. The system helps ensure that you only make valid connections between compatible port types.

• Port Colors

  The color of the ports on a module provides an immediate visual cue about the type of data they accept or output. Understanding these colors and types helps in quickly assessing a module’s function and ensuring you are making valid connections within the Application Network. Port Types Each port type is designed to handle a specific kind of data. The primary types are listed below.

Finding Modules in the Application Network

For large or complex application networks, the search functionality provides an efficient way to locate specific modules. The search tool is located in the toolbar at the top of the Application window.

Using the Search Tool

The appearance of the search tool depends on the available width of the Application window. In narrower views, it may appear as a magnifying glass icon. In wider views, it will be displayed as a full search box labeled “Search for Module in Application”.

To use the search, you can either begin typing the name of the module you wish to find or click on the search box (or icon). Clicking will reveal a dropdown list containing all modules currently in the Application Network. Selecting a module from this list will immediately locate it.

Search Results

When you select a module from the search results, two actions occur simultaneously in the user interface:

1. The Application Network view will automatically pan and zoom to center on the selected module, which will be highlighted with a green outline for easy identification.
2. The **Properties**window will update to display the parameters for the selected module. This allows for immediate access to view or edit the module’s settings without needing to manually select it in the network.

This integrated functionality streamlines the process of navigating and editing complex workflows, making it easy to manage even the most extensive application networks.

The Viewer is the primary 3D visualization window in Earth Volumetric Studio. It includes a dedicated user interface for navigating the 3D scene, managing the visibility of objects, and accessing various tools. Additional, more advanced properties are available in the Properties window when the viewer module is selected.

Viewer Window Interface

The Viewer window features a sidebar on the left that contains controls for orientation, scene management, and a table of contents

View Orientation Controls

At the top of the sidebar, the orientation controls allow for precise camera positioning.

Scene and View Controls Toolbar

A toolbar below the orientation controls provides quick access to common scene management functions.

Button	Icon	Description
Save Viewer Snapshot		Saves the current contents of the viewer to an image file. Clicking the main button saves with the last used settings, while the dropdown arrow reveals several options to control the output:

• **Use Transparent Background**: If enabled (and using PNG format), the viewer background will be transparent in the saved image.
• **Prefer Lossless**: When enabled, attempts to save in a lossless format like PNG.
• **Quality**: Sets the compression quality for lossy formats like JPEG (1-100).
• **View Scale**: A multiplier for the output resolution. A scale of 2.0 will produce an image twice the width and height of the current viewer size.
• **Scale Forward Facing Text**: Ensures that text elements scale correctly with the View Scale to maintain their relative size.

Table of Contents

The Contents section at the bottom of the sidebar acts as a layer manager for your scene. It displays a hierarchical tree view of every object connected to the viewer module in the Application Network.

• Visibility Control: Each item in the list has an eye icon next to it. Clicking this icon toggles the visibility of that object in the viewer. This allows you to quickly show or hide different components of your model without disconnecting modules. Objects hidden in the Table of Contents will also be hidden in exported C Tech Web Scenes (.ctws).
• Tree Structure: If you use modules like group_objects, the Table of Contents will reflect that structure. You can expand or collapse parent items to show or hide their children, and toggling the visibility of a parent will affect all the objects grouped under it.
• Double Click Interaction: Double left-click with your mouse on any item in the Table of Contents will select that module in the the-application-window.mdApplication, as well as show it’s properties in the Properties Window.

The Python Script Editor is the integrated environment within Earth Volumetric Studio for writing, editing, and running Python scripts. It provides a full-featured text editor with syntax highlighting, code formatting tools, and direct access to execution and debugging functions, making it the central hub for all your scripting activities.

Accessing the Python Script Editor

You can open the editor through the Python Scripting button located in the Main Toolbar.

The dropdown menu provides three main options:

Once a script is created or opened, the Python Script Editor window will appear.

Editor Toolbar Reference

The toolbar at the top of the editor provides a wide range of tools for managing and editing your code.

File and Edit Operations

Execution and Recording

Code Formatting and Navigation

Additional Menus

On the far right of the toolbar are two dropdown menus for additional functionality.

Information Menu

This menu provides access to related information and output windows.

Editor Options Menu

This menu (gear icon) controls the visual display of the text editor itself.

The Python Interactive window provides a real-time environment to execute Python statements and expressions. This tool allows you to test code snippets, perform quick calculations, and inspect data without needing to run a full script.

Window Components

The interface is divided into three primary sections:

To get started with the Python Interactive window, follow these steps:

1. Enter Code: Click into the input field at the bottom of the window.
2. Evaluate: Type a mathematical expression (e.g., 42 * 29.29) or a Python command.
3. Submit: Click the play icon on the right or press your execution hotkey.
4. Review: Check the Output Area for the result or any potential error messages.

While useful as a general tool (such as using as a calculator, as shown above), the window is typically used for interacting with the EVS API directly.

This is particularly useful when writing scripts, as you can interactively inspect the structure of the EVS API calls, and modify as needed.

For example, you can see the values in a dictionary returned by the API directly:

Clicking on the grey text in the Output Area will re-select it and enter it into the Input Box, which can then be edited. Using the above, this allows us to click on the previous code (evs.get_module_exte….), and then add the entry for SelectedOption to test and make sure we are fetching the results we would expect (the name of the analyte):

This shows us the results of the entered code, which could then be reused in a Python script (such as fetching the current analyte name above for use in a title).

You can programmatically read and set the properties of any module using Python Scripting. This is a powerful feature for automating workflows and creating complex interactions between modules. The scripting engine provides programmatic access to the same underlying properties that are exposed as controls in the Properties window. This allows scripts to read, evaluate, and update values, mirroring manual user interaction. The easiest way to script a property is to copy the required syntax directly from the Properties window.

Getting a Property’s Value

To get the current value of a property and assign it to a Python variable:

1. Open the Properties window for the module you want to control.
2. Right-click on the property you want to read.
3. Select Get Value or Get Extended Value from the context menu.

This action copies a line of Python code to your clipboard. You can then paste this code into the Python Script Editor.

Reading Value Example

Right-clicking on the Explode property of the explode and scale module and selecting Get Value will copy the following syntax:

explode = evs.get_module('explode and scale', 'Properties', 'Explode')

After executing this line, the explode variable in your script will hold the current value of the Explode property. Note that the Python API call has three arguments: the module name, the category name, then the property name.

Difference between Get Value and Get Extended Value

The context menu provides two options for getting a value. The Get Value option will use the evs.get_value API call, which fetches the value that is used when saving an application, and contains whatever is required to set the property. This is the value that should be used if using evs.set_value.

The extended option will use evs.get_extended_value, which typically results in a dictionary with the original value, as well as other metadata. For example, a drop down with a list of analytes will typically just return the selected item by index in get_value, but the extended option will include other information, such as the list of options, the selected value by name and index, and more.

Setting a Property’s Value

To set the value of a property:

1. In the Properties window, right-click on the property you want to modify.
2. Select Set Value from the context menu.

This copies the Python syntax for setting the property to your clipboard. Paste the code into the Python Script Editor or the Python Interactive Window and utilize the value as needed.

Updating Value Example

For example, using the same Explode property, the copied syntax would be:

evs.set_module('explode and scale', 'Properties', 'Explode', {'Linked': True, 'Value': 0.0})

You can change 0.0 to any valid value for that property, such as:

evs.set_module('explode and scale', 'Properties', 'Explode', {'Linked': False, 'Value': 1.0})

When dealing with a Linked Property, you should disable the link to manually when setting its value. This is done by setting the corresponding Linked boolean property to false. If you attempt to set the value while it is still linked, your change may be overridden as the value is determined automatically.

Executing this command in the Python Script Editor or the Python Interactive Window will update the property in the module, and the change will be immediately visible in the Properties window.

Python Functions & Operators

Earth Volumetric Studio supports Python 3.12 and 3.13. It will use the highest supported system installed version by default, but can be configured in options.

A listing of Python Functions & Operators can be found at python.org. Below are links to relevant pages:

• Functions

• Math Operators

• String Operators

• Date and Time Operators

  • Date & time syntax

Please note: C Tech does not provide Python programming or syntax assistance as a part of Technical Support (included with valid subscriptions). Python scripting and functionality is provided as an advanced feature of Earth Volumetric Studio, but is not required to use the basic functionality.

Below are Earth Volumetric Studio specific functions and classes which provide means to get and set parameters, read field data, and act upon the modules in the libraries and network. All functions below are available through the evs module unless otherwise noted.

Module Properties

These functions read and write property values on modules. For a detailed walkthrough with examples, see Accessing Properties Using Python.

evs.get_module(module, category, property)

Gets a property value from a module within the application.

Returns: The property value.

explode = evs.get_module('explode and scale', 'Properties', 'Explode')

evs.get_module_extended(module, category, property)

Gets an extended property value from a module within the application. Extended values include additional metadata beyond the basic value.

Returns: The extended property value.

evs.set_module(module, category, property, value)

Sets a property value on a module within the application.

evs.set_module('explode and scale', 'Properties', 'Explode', {'Linked': False, 'Value': 1.0})

evs.set_module_interpolated(module, category, property, start_value, end_value, percent, interpolation_method)

Sets a property value by interpolating between two values. Useful for animating properties across sequence states.

The interpolation_method parameter accepts one of the following evs.InterpolationMethod values:

# Interpolate the Explode value from 0.0 to 5.0 at 50%
evs.set_module_interpolated('explode and scale', 'Properties', 'Explode',
    {'Linked': False, 'Value': 0.0},
    {'Linked': False, 'Value': 5.0},
    0.5, evs.InterpolationMethod.Cosine)

Port Properties

These functions read and write property values on module ports.

evs.get_port(module, port, category, property)

Gets a value from a port on a module within the application.

Returns: The port property value.

evs.get_port_extended(module, port, category, property)

Gets an extended value from a port on a module within the application.

Returns: The extended port property value.

evs.set_port(module, port, category, property, value)

Sets a property value on a port in a module within the application.

evs.set_port_interpolated(module, port, category, property, start_value, end_value, percent, interpolation_method)

Sets a port property value by interpolating between two values. Accepts the same evs.InterpolationMethod values as set_module_interpolated.

Reading Field Data

These functions and classes allow Python scripts to read the contents of field data from module ports. This is useful for extracting coordinates, node data, and cell data from computed fields.

evs.get_field_info(module, port)

Gets a FieldInfo object for reading field data from a module port. The returned object should be used within a with statement, or you must call close() manually when finished.

Returns: FieldInfo — a field reader for accessing coordinates and data.

Raises: ValueError if the field reader cannot be created for the specified module and port.

with evs.get_field_info('kriging', 'Output Field') as field:
    print(f"Nodes: {field.number_coordinates}, Cells: {field.number_cells}")
    print(f"Units: {field.coordinate_units}")

    # Read coordinates
    for x, y, z in field.coordinates:
        print(f"  ({x}, {y}, {z})")

    # Read node data
    for i in range(field.number_node_data):
        data = field.get_node_data(i)
        print(f"  {data.name} ({data.units}): {len(data.values)} values")

evs.FieldInfo

Represents a field, providing access to its coordinates, node data, and cell data. Should be used within a with statement to ensure resources are properly released.

Properties:

Methods:

evs.FieldData

Represents one node or cell data component of a field. Returned by FieldInfo.get_node_data() and FieldInfo.get_cell_data().

Properties:

Application and Module Management

evs.get_application_info()

Gets basic information about the current application.

Returns: dict — a dictionary with the following keys:

evs.get_modules()

Gets a list of all module names in the application.

Returns: list of str — module names.

for name in evs.get_modules():
    print(f"{name}: {evs.get_module_type(name)}")

evs.get_module_type(module)

Gets the type of a module given its name.

Returns: str — the module type.

evs.get_module_position(module)

Gets the position of a module in the network editor.

Returns: tuple of (x, y) — the module’s position coordinates.

evs.rename_module(module, suggested_name)

Renames a module and returns the actual new name. The actual name may differ from the suggested name if a module with that name already exists.

Returns: str — the actual new name of the module.

evs.delete_module(module)

Deletes a module from the application.

Returns: bool — True if successful.

evs.instance_module(module, suggested_name, x, y)

Creates a new instance of a module in the application at the specified position.

Returns: str — the actual name of the instanced module.

name = evs.instance_module('Estimation.kriging', 'my kriging', 100, 200)
print(f"Created module: {name}")

Module Connections

evs.connect(starting_module, starting_port, ending_module, ending_port)

Connects a port on one module to a port on another module.

Returns: bool — True if successful.

evs.connect('kriging', 'Output Field', 'cut', 'Input Field')

evs.disconnect(starting_module, starting_port, ending_module, ending_port)

Disconnects two previously connected module ports.

Returns: bool — True if successful.

Execution Control

evs.check_cancel()

Checks whether the user has requested to cancel the script. If a cancellation has been requested, the script will stop at that point. Insert this in loops that may run for a long time so that canceling the script remains possible.

for i in range(10000):
    evs.check_cancel()
    # ... do work ...

evs.suspend()

Suspends the execution of the application until resume() is called. Use this when making multiple property changes to prevent the application from updating between each change.

evs.resume()

Resumes the execution of the application, causing any operations that were suspended to run.

evs.suspend()
evs.set_module('kriging', 'Properties', 'Allow Run', True)
evs.set_module('kriging', 'Properties', 'Variogram Range', 500.0)
evs.resume()

evs.refresh()

Refreshes the viewer and processes all mouse and keyboard actions in the application.

evs.is_module_executed()

Returns whether the script is being executed by a module (such as trigger script) as opposed to being run directly by the user.

Returns: bool — True if executed by a module, False when the user executes directly (e.g., hitting play in the script window).

Number Formatting

evs.sigfig(number, digits)

Rounds a number to a specified number of significant figures.

Returns: float — the rounded value.

evs.sigfig(123456.789, 4)  # Returns 123500.0

evs.fn(number, digits, include_thousands_separators, preserve_trailing_zeros)

Formats a number as a string using a specified number of significant figures. Also available as evs.format_number().

Returns: str — the formatted number.

evs.fn(1234567.89)           # "1,234,570"
evs.fn(1234567.89, 3)        # "1,230,000"
evs.fn(1234567.89, 6, False) # "1234570"

evs.fn_a(number, adapt_size, digits, include_thousands_separators, preserve_trailing_zeros)

Formats a number as a string, adapting the precision to the magnitude of a second number. This is useful when formatting a value relative to a step size or range. Also available as evs.format_number_adaptive().

Returns: str — the formatted number.

Export Scripting

The export scripting API allows Python scripts to respond to events during a web scene export. When the export web scene module writes a CTWS file, it triggers the attached Python script at each stage of the process. Use get_export_stage() to determine the current stage and respond accordingly.

evs.get_export_stage()

Gets the current export stage and related information.

Returns: ExportStage — an object describing the current stage of the export process.

stage = evs.get_export_stage()

# Run initialization code at the start of an export
stage.handle_init(lambda: print("Export starting"))

# Handle a specific module being exported
stage.handle_module('kriging', lambda: print("Kriging exported"))

# Handle sequence states with state number and name
stage.handle_sequence('scripted sequence', lambda num, name: print(f"State {num}: {name}"))

# Run finalization code at the end of an export
stage.handle_finalize(lambda: print("Export complete"))

evs.ExportStage

Represents the current export stage and provides handler methods for responding to specific stages. Constructed by get_export_stage().

Properties:

Stages:

Handler Methods:

Python Assets

evs.import_asset(name)

Imports a Python module included in the Python Assets section of the Application Properties. This is used instead of a standard import statement when working with EVS presentation files or packaged data, since Python assets are embedded within the application rather than stored as separate files on disk.

Returns: module — the imported Python module.

Raises: ModuleNotFoundError if no Python asset exists with the given name.

helpers = evs.import_asset('my_utilities')
helpers.do_something()

Date Conversions (evs_util)

The evs_util module provides functions for converting between three date representations used in EVS:

Each function converts from one format to another. The naming convention is {source}_to_{target}:

import evs_util
import datetime

# Convert an EVS date string to a Python datetime
dt = evs_util.evsdate_to_datetime("2024-06-15T14:30:00")

# Convert to an Excel date number
excel_num = evs_util.datetime_to_excel(dt)

# Convert back to an EVS date string
evs_date = evs_util.excel_to_evsdate(excel_num)

Testing

evs.test(assertion, error_on_fail)

Asserts that a condition is true. If the assertion is false, the specified error message is printed as an error.

value = evs.get_module('kriging', 'Properties', 'Allow Run')
evs.test(value == True, "Expected Allow Run to be enabled")

Let’s load an application to get an idea of how EVS works.

Browse to

Find and double click the file “painting-facility-interactive-labels.intermediate.evs”.

The application will run and in less than one minute you will see:

For more on opening applications see the topic Open Files.

Transformations with the Mouse

Now that we have an application loaded, let’s investigate the many ways we can interact with it.

Rotate the model

• Hold down the left mouse button and move the mouse pointer in various directions. The model rotates.
• Vertical motions rotate the model about a horizontal axis.
• Horizontal motions rotate the model about a vertical axis.
• Roll is suppressed so that mouse rotations always keep vertical objects (e.g. telephone poles) vertical.

Scale (zoom) the model

• The wheel on wheel mice also zooms in and out.
• Alternate method:
  • Hold down both the Shift key and the left mouse button (or the middle button alone).
  • Keeping the Shift key and mouse button held down, move the mouse pointer downward or to the left. As we do, the model scales down. Moving the mouse pointer upward or to the right scales up.

Move (Translate or Pan) the model

• Hold down the right mouse button and drag the object up, down, and around, then center the model.

or

Hold down the Shift key and drag the object with the left mouse button (Shift-LMB)

or

Use the middle mouse button or wheel as a button without Shift |

Transformations with the Azimuth and Inclination Controls

Azimuth and Inclination controls are available in two places and gives us more precise ways to transform (scale, pan and rotate) an object:

1. The viewer’s Properties window.
2. The viewer’s slide-out properties in the Viewer window.

Double click on the viewer module to open the Properties window with view controls including sliders and an array of buttons. These controls allows you to instantly select a view from any azimuth and inclination. For a given (positive) inclination, selecting different azimuth buttons is equivalent to flying to different compass points on a circle at a constant elevation. The azimuth buttons are the direction from which you view your objects. (i.e. 180 degrees views the objects from the south). An inclination of 90 degrees corresponds to a view from directly overhead, 0 degrees is a view from the horizontal plane (side view) and -90 degrees is a view from the bottom.

c. Use the Azimuth and Inclination Panel to obtain a specific view by setting the scale slider and inclination slider to desired settings and click once on the desired azimuth button. If you choose a scale of 1.0, an Inclination of 30 degrees and an azimuth of 200 degrees

The viewer will show:

The Advanced options provide the ability to allow rotations about a user defined center, as opposed to the default center of the objects, which is chosen by EVS. Additionally you can apply a ROLL to the view which will make vertical objects (such as the Z axis) not appear vertical. If you do not see the options, click on the Advanced category in the Properties window to expand them.

Below the Advanced options, there are three buttons

1. Set to Top View: Returns the model view to Azimuth 180, Inclination 90 and Scale of 1.0
2. Zoom To Fit: Returns the Scale to 1.0
3. Center On Picked: This button is normally inactive, but is activated by probing with CTRL-Left mouse on any object in the view. The default center of an object shown in our viewer is midway between the min-max of the x, y and z dimensions. This button then causes the view to recenter on the selected point. When you pick a point on an object, the following information is displayed in the Information window.

The Perspective Mode toggle switches to Perspective (vs. Orthographic) viewing. In perspective mode, parallel lines no longer appear parallel but instead would point to a vanishing point.

The Field of View determines the amount of perspective. Larger values result in more perspective distortion.

The Render selection allows you to choose between OpenGL and Software renderers. On some computers with minimal graphics cards Software renderer may perform better or be more stable.

Auto Fit Scene: The choices here include:

• On Significant Change: This is the default behavior which causes the view to recenter and rescale if the extents of the view would change significantly. Otherwise the view is unaffected.
• On Any Change: This causes the view to recenter and rescale if the extents of the view changes at all
• Never: The view will not change if objects change.

The Window Sizing options

• Fit to Window: The view size is determined by the size of the viewer window
• Size Manually: The view size is set in the Viewer Width and Height type-ins below to a specific size. The viewer then has scroll bars if the view size exceeds the window size.

At any time after modules have run, you can quickly obtain basic statistical and model extents data merely by double left mouse clicking on any FIELD (blue) output port.

Let’s demonstrate this by using the second output port of the cut module

When we double-click here, the following information appears in the Properties window.

This quickly tells us that this port has a model with the following data and coordinate extents

• 211,200
• 181,779 cells
• We can select any of the three nodal data (TOTHC is shown)
• The X, Y & Z Minimum, Maximum and Extents are provided

For more comprehensive statistical analysis of the nodal data, click on the “Open Statistics Window” button, and the following appears.

Before we end this first workbook, let’s interact with this application in another way.

In the Application window, double click on the intersection_shell module, and you will see a green border around it. This green border designates the selected module whose properties are available for editing.

This will open its Properties in the Properties window in the upper right. In this application, intersection_shell is performing two tasks. It is cutting the model using information provided by the cut module and it is also subsetting what remains by Total Hydrocarbon (TOTHC) level. It might seem strange at first that the cut module isn’t actually cutting the model. But if it did, it would only provide one side or the other. By giving us data that is the “signed” distance from the specified cutting plane, we are able to use cut’s data to create the cut for the front side giving us the plume and the back side giving us the geologic layers. We can also offset any distance from the theoretical cutting plane without actually moving the cutting plane, but only changing the “cut” Subsetting level. In fact, in this application we’re cutting 100 feet from the specified cutting plane.