As a new user, we recommend starting by viewing the tutorial movies and checking the user manual.

If you still have questions, please contact our support team, via the contact form or email. Whether you're a paying customer or an evaluation user, we want to help!

Download the installer package from the download page.

Standard packages are included for Windows, Linux, and Mac OS X, which you can install in the standard way, usually by simply double-clicking the file. You may need to have administrator permissions to install software.

A ZIP file is also provided for Linux users. You can unzip this file anywhere, and run the "insight" script contained within. No further installation is required.

For more information about installation, please see the user manual or contact our support team.

99.9% of the time, problems with the 3D view are caused by buggy, out-of-date video drivers, not Insight itself.

Almost all modern hardware is capable of running Insight's 3D view, when paired with modern drivers.

For more information, please read this page all about 3D issues and their solutions.

A survey file defines the basic parameters of a Survey, and is used during data loading and visualisation. It is the first file that you need when creating a new DUG Insight session.

The SEG-Y Loader will create a survey file when converting SEG-Y to dugio volumes. Early in the process, it will ask if you have an existing survey file. Leave the default "No" button selected, and follow the rest of the SEG-Y loading process. It will create a survey file before it writes the data.

For more information about survey files, see the user manual.

SEG-Y data cannot be loaded directly into DUG Insight; it must first be converted into DUG's optimised dugio format.

From the application launcher, choose the SEG-Y Loader. The SEG-Y Loader will guide you through the process of creating a Survey file and writing dugio data volumes.

For more information about the SEG-Y Loader, see the user manual.

You can also download a small amount of sample data already in dugio format.

SEG-Y is the recommended format for transferring trace data into Insight.  More information on the SEG-Y format is available here.

The DUG SEG-Y Loader supports both SEG-Y Revision 0 (1975) and Revision 1 (2002).

The trace data format must be specified in the Data Sample Format Code. The codes are:

• 1 = 4-byte IBM floating-point
• 2 = 4-byte, two's complement integer
• 3 = 2-byte, two's complement integer
• 4 = 4-byte fixed-point with gain (NOT SUPPORTED)
• 5 = 4-byte IEEE floating-point
• 6 = Not currently used
• 7 = Not currently used
• 8 = 1-byte, two's complement integer

We do not support trace data in 4-byte fixed-point with gain format.

DUG Insight can load horizon data from multiple text formats.

For horizons in a UTM X/Y coordinate space, DUG Insight can load standard GeoQuest or CPS-3 formatted horizons. Most software can export one of these two types. Each file must be stored in a separate file.

To load a horizon in the Inline/Crossline coordinate space, DUG Insight requires a simple three-column text file. Each line is of the format:

inline crossline time

or

inline crossline depth

Comment lines begin with a hash (#) character. For example:

# subgrid=il:1272-3492[10]+cl:1320-3520[10]
# vertical_dimension=time
    1272     1320   3005.008
    1272     1330   3005.050
    1272     1340   3005.117
    1272     1350   3005.179
    1272     1360   3005.238
    1272     1370   3005.294
    1272     1380   3005.378
    1272     1390   3011.869

The comments at the top defining the grid and vertical dimension are not required. IL/CL horizons are usually saved with a suffix of ".ilclt" for time horizons, or ".ilclz" for depth.

DUG Insight can load and save horizon data using either the GeoQuest IESX V11 format, or using its own .dufault text format which consists of a single X/Y point per line, separated by whitespace, and a blank line to indicate a new fault stick:

x1 y1
x2 y2
x3 y3

x1 y1
x2 y2

x1 y1
x2 y2
x3 y3
x4 y4

Summary

DUG Insight reads Well data from text files.

Curve and log data should be stored in LAS format, with a single LAS file per well.

Checkshots, deviation surveys, and markers should be converted to geoEAS format, defined below.

Finally, the first time you import a well for use in DUG Insight, you'll use the Well Import dialog to create a duwell file. The duwell file describes the well, and contains pointers to the LAS, checkshot, deviation, and markers files. To create a duwell file in DUG Insight:

1. open the Wells tab
2. click the New icon, a plus (+) sign
3. fill in all of the relevant information for your well

Once you have a duwell file, you can load it in this or any other DUG Insight session by clicking the Load icon, which looks like a small folder.

The geoEAS Format

geoEAS is a simple text format used by many geostatistical packages. Checkshot (time-depth) surveys, deviation surveys, and marker data must be stored in geoEAS format files:

• The first line of the file contains a comment or title for the data.
• The second line of the file contains the number of columns of values (N).
• The next (N) lines contain the column names, one column per line.
• The remaining lines contain the data values, each line containing (N) values separated by at least one space, or a single comma.

Checkshot (time-depth) Surveys

Time-to-depth information is required for DUG Insight to display well data in time. Checkshot data points require two values:

• the measured depth at the well, and
• its corresponding two-way-time

The depth column label should indicate the depth datum. Expected depth labels are:

• MDKB: Measured Depth from Kelly Bushing / Round Table
• MDSS: Measured Depth Sub Sea
• MD: Measured Depth (assumed to be MDKB)

The time column label should be "TWT". No other time formats are accepted.

Sample checkshot survey:

	Time-depth survey for Well-1
2
MDKB
TWT
1210.00 1170.07
1710.00 1500.07
2210.00 1800.04
2700.00 2150.06
3200.00 2520.03
3730.00 2810.07
4000.00 2960.74

Deviation Surveys

Deviation surveys are required for DUG Insight to accurately display deviated wells. Deviation surveys require four values for each point:

• the measured depth
• the true vertical depth
• the UTM X coordinate at this depth
• the UTM Y coordinate at this depth

The measured depth column label should indicate the datum. Expected measured depth labels are:

• MDKB: Measured Depth from Kelly Bushing / Round Table
• MDSS: Measured Depth Sub Sea
• MD: Measured Depth (assumed to be MDKB)

The true vertical depth column label should indicate the datum. Expected true vertical depth labels are:

• TVDKB: True Vertical Depth from Kelly Bushing / Round Table
• TVDSS: True Vertical Depth Sub Sea
• TVDBML: True Vertical Depth Below Mud Line
• TVD: True Vertical Depth (assumed to be TVDKB)

The UTM X and Y columns should be labelled "UTMX" and "UTMY" or "X" and "Y", respectively.

Sample deviation survey:

	Deviation survey for Well-1
4
MDKB
TVDSS
X
Y
    0.00       -20.06      39844.56     24589.34
    1000.00    1020.02     39844.47     24588.95
    2000.00    1990.05     39845.82     24590.47
    3000.00    2980.00     39895.21     24524.15
    4000.00    3410.03     40453.486    23864.922
    5000.00    3910.05     41009.257    23219.492
    6000.00    4890.06     41036.517    23192.534

Well Markers

Markers are text labels applied to points along the well path. Well marker files require two values:

• the marker name (the text placed beside the point at the well)
• the marker depth

The marker name column should be a short description of the point. Spaces and commas are not allowed in the name. We recommend the use of underscore '_' or hyphens '-' to replace spaces. The marker name column should be labelled "Name".

The marker depth column should indicate the datum, as above.

Sample marker file:

	Markers for Well-1
2
NAME
MDKB
WaterBottom   185.0
Cretaceous    2700.00
Jurassic      3200.00
Triassic      3730.00
Permian       4000.00

There is limited support in DUG Insight for loading directly from certain databases. Please contact us to find out about your specific situation.

Alternatively, you can export volume data as SEG-Y files; well log data as LAS files; and horizons or faults as GeoQuest CardImage 7 files, then load those into DUG Insight.

After loading data, first make sure to open an appropriate view. Open the View menu and select "IL/CL View" for inline and crossline cross-section views of data volumes. In the upper right-hand corner of the window there is a volume selector drop-box. Make sure to choose the volume that you wish to view, and that you're viewing an inline or crossline that contains data.

If you wish to see time or depth slices, select "Map View" from the View menu. If the map view displays the survey region but not the volume, go to the Volumes tab, find the panel for your data, then check the “On Map” checkbox.

If you have a view window open and you still can't see your data, you may need to adjust your group settings. In the Volumes tab, find the panel for your data and look at which group settings it is using (the default group is called "Default Seismic"). In the Groups tab, find the panel for those settings. Examine the maximum and minimum clipping values for your colourbar and make sure they are correct for your data. If the values are far too large, your data will appear as a single colour, often white.

More information about Group Settings can be found in the manual.

If your problem persists, please contact us for assistance.

"Delivery software is a trace-based Bayesian seismic inversion code for use in oil reservoir characterisation at the early development and appraisal stage."

You can find out more about this software at this web site.

To load a model generated by Delivery in DUG Insight:

1. You need:
   • A survey or grid file
   • A volume of other data to load (velocities, seismic, anything)
   • Your Delivery model (.su)
   • A Delivery properties file
     The properties file must be named the same as the .su file, with the suffix ".properties" and stored in the same directory.
     e.g.
     Model = deliveryModel.su
     Properties = deliveryModel.su.properties
     Be sure that the properties file contains exactly the list of properties that are included in the model.
     The properties file should contain a single line with a list of the properties in the model, separated by commas and no spaces. e.g.
     Fluid_Probability,Interval_Velocity,Property1,Property2
2. Launch DUG Insight
3. From the Surveys tab, click the folder icon to load your Survey file
4. From the Volumes tab, click the folder icon to load your volume of data (not the model)
5. From the Models tab, click the folder icon to load the Delivery .su file
6. The group display settings window gives you the chance to assign display settings to each of the properties
7. In the Models tab, an entry will appear for your model.
8. Under "Section View Settings" you can control which property is being displayed and its associated group.
9. You can also turn individual layers on and off via the checkboxes

When you first launch any DUG application, a small launch dialog will appear. Choose or type any number (in megabytes) to limit the application to the amount specified.

We recommend reserving 1 to 2 GB of RAM for your operating system, and allowing DUG Insight to use the remainder for best performance.

You definitely do not want to choose a number so large that your OS and applications cannot fit in physical memory. If your computer slows to a crawl after using the application for a short time, then you are almost certainly running out of RAM. Try a smaller number.

You can purchase commercial licenses online via credit card; to pay via purchase order, please contact our sales team.

All DUG software licenses are node-locked, so to issue your license we need the hardware code produced by any DUG application. To retrieve your hardware code:

1. launch any DUG application
2. if you're running an evaluation copy, you will be prompted to open the License Manager; otherwise, open the License Manager from the Help menu
3. choose "Purchase or Replace a License"; click Next
4. click the button to save the hardware code to a file
5. include that file with your purchase request, or email it to support@dugeo.com

Please allow up to one business day for the license to be generated and sent by email.

Once you've received your license, installation is easy. Remember that each license file is for a specific application and computer:

1. launch the application you wish to license
2. open the License Manager at the prompt, or via the Help menu
3. choose "Install a License"; click Next
4. click the button on the right to select the license file
5. click "Install License"

If you have any issues, please contact our support team.

DUG Insight is designed for working with pre-stack data - providing an extra data dimension to your interpretation environment. Gathers may be selected by inline-crossline and displayed together with post-stack or pre-stack (constant offset) inlines and crosslines. Gathers can be interpreted by extrapolating a post stack (or constant offset) horizon across all offsets - this provides both an autotracked horizon (useful for trim statics) and a calculated residual moveout curve (useful for iterative depth migration).

DUG Insight version 2.2, to be released in Q2 2010, will also include a built-in stacking process.

Load at least one gather volume, then select one of the gather views (Gather, IL/Gather/CL, or 2D/Gather) from the View menu.

.

For more information about gathers and views, see the user manual.

When a disk is mounted in Mac OS X, it appears in the sidebar on the left-hand side of the Finder. In DUG software and other applications that don't use the native file browser, these mounted volumes (hard disks, USB drives, DVDs, etc.) can be found under the /Volumes directory.