VelPAK User Guide

Energy Upstream
Kingdom® 2018
VelPAK User Guide
February 2018
2 © 2018 IHS Markit™. All Rights Reserved.
Trademarks and Copyright
This manual was produced by IHS Markit.
February 2018
.
1401 Enclave Pkwy Ste 500

Houston, Texas 77077
U.S.A.
Tel: (281) 531-4660
Fax: (832) 531-9966
Website: www.ihs.com/kingdom
Sales: etasales@ihs.com
Support: kingdom_support@ihsmarkit.com
The following trademarks appear in this manual.
IHS Markit Kingdom® software and all of its components, AVOPAK, CGMPAK, GeoSyn®,
LoadPAK, PAKnotes®, Petra®, SynPAK®, Tunnel L+, Tunnel O, VelPAK®, VuPAK®,
Kingdom 1D Forward Modeling, Kingdom Colored Inversion, The Kingdom Company,
Kingdom Data Management, Kingdom DM Catalog Builder Kingdom Illuminator
Kingdom Seeker, and Kingdom I3D Scan are trademarks of IHS Markit.
Portions of data loading are copyrighted by Blue Marble Geographics.
Mapping API for the Spatial Explorer map provided by Esri ArcGIS Runtime SDK for .NET.
Kingdom Geophysics contains components under U.S. Patent Numbers 6,675,102,
8,265,876, and 9,105,075.
VuPAK® includes OpenInventor® and VolumeViz from FEI Visualization Sciences Group,
Inc. Some components or processes may be licensed under U.S. Patent Number 6,765,570.
Tunnel L+ includes OpenWorks® and SeisWorks® Development Kit from the Halliburton
Corporation.
Kingdom Connect and Tunnel O include OpenSpirit® FrameWork from OpenSpirit, a
TIBCO Software Group Company. Kingdom Data Management includes components from
OpenSpirit and are copyrighted by OpenSpirit, a TIBCO Software Group Company.
Kingdom Gateway plug-in for Petrel* E&P software platform uses the Ocean* software
development framework and * is a mark of Schlumberger.
Kingdom®1D Forward Modeling® includes software developed as part of the NPlot library
project available from: http://www.nplot.com/.
Portions of Kingdom® bitmap graphics are based on GD library by Boutell.Com, Inc. Further
information about the company can be found at www.boutell.com.
PAKnotes TIFF support is based in part on libtiff.
© 2018 IHS Markit™. All Rights Reserved. 3

Rock Solid Attributes® is a registered trademark of Rock Solid Images Inc. and contains
confidential, proprietary, and trade secret information of Rock Solid Images Inc. Copyright©
Rock Solid Images Inc. All Rights reserved.
HDF5 (Hierarchical Data Format 5) Software Library and Utilities Copyright 2006-2015 by
The HDF Group. NCSA HDF5 (Hierarchical Data Format 5) Software Library and Utilities
Copyright 1998-2006 by the Board of Trustees of the University of Illinois.
VelPAK and Seismic Inversion are developed by Equipoise Software Ltd on behalf of IHS
Markit.
Baker Hughes JewelSuiteis a trademark of Baker Hughes. JewelSuite contains
confidential, proprietary and trade secret information of Baker Hughes.
Microsoft is a registered trademark of Microsoft Corporation. Windows 7, Windows 8
operating systems, MS-DOS and SQL Server are trademarks of Microsoft Corporation.
Oracle® Databases are registered trademarks of Oracle Corporation.
OpenWorks, SeisWorks, Interpret 2000 and Interpret 2003 are registered trademarks of
Halliburton Corporation.
IHS Markit incorporates BMC® AppSight™ Black Box Technology in its software. BMC
Software, BMC Software logos and all other BMC Software product and service names are
registered trademarks or trademarks of BMC Software Inc. © 2009 BMC Software, Inc. All
rights reserved.
All other trademarks are the property of their respective owners.
Copyright Notice
© 2011 - 2018 IHS Markit. For Internal use only. All rights reserved.
This manual contains confidential information and trade secrets proprietary to IHS Markit Ltd.
and its affiliated companies (“IHS Markit”). No portion of this manual may be reproduced,
reused, distributed, transmitted, transcribed or stored on any information retrieval system, or
translated into any foreign language or any computer language in any form or by any means
whatsoever without the express written permission of IHS Markit. For more information,
please contact Customer Care at kingdom_support@ihsmarkit.com.
Misuse Disclaimer
IHS Markit makes no representation or warranties of any kind (whether express or implied)
with respect to this manual or the Kingdom® software and to the extent permitted by law, IHS
Markit shall not be liable for any errors or omissions or any loss or damage or expense
incurred by an user. IHS Markit reserves the right to modify the Kingdom® software and any
of the associated user documentation at any time.
Acknowledgments
IHS Markit wishes to gratefully acknowledge the contributions of the many client software
testers in preparing the Kingdom® software. The enthusiastic Beta testers, smoke testers,
amber testers and staff greatly appreciate their invaluable feedback and contributions.

Table of Contents
VelPAK - Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
The DATA TYPES stored within a VelPAK model . . . . . . . . . . . . . . . . . . 29

The MODULES and what they can do for you. . . . . . . . . . . . . . . . . . . . . 30
The Wizard Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
The Layer Module (Advanced User only). . . . . . . . . . . . . . . . . . . . . . 31
The Profile Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
The Fault Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
The Surface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Gridding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Depth Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Trim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
The Velocity Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
The Well Log Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
The Curve Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
The 3D Visualization Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
The Optimize Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
The Workflow Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
The Analyse Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Integration and Links with Kingdom data . . . . . . . . . . . . . . . . . . . . . . 46
The Origins and Rationale of Snapping in Profile mode . . . . . . . . . . 46
VelPAK as a Mapping Package pre-processor. . . . . . . . . . . . . . . 46
The VelPAK Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Layout - docking and floating windows. . . . . . . . . . . . . . . . . . . . . . . . . . 49

To detach a window of VelPAK: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Command Drop Down Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Print Page Set-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
ToolBar 1 - Standard Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
ToolBar 2 - Module windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Abort. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Model Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Model Tree - Top Bar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Refresh Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Show Unused slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Model Tree - the Data Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Model - Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Model - Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Model - Surface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Event Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Model - Well. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Model Tree - The Expanded Data Slots . . . . . . . . . . . . . . . . . . . . . . . . . 72
Model Tree - Cut/Copy/Paste/Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Surface and Slot Selection (“Surface&Slot”) . . . . . . . . . . . . . . . . . . . . . 75
Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Zoom and Pan Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Color Tables in VelPAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Color Table options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
VelPAK - The Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
The Wizard - for easy Depth Conversion . . . . . . . . . . . . . . . . . . . . . . . . 83

Wizard Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Using the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
General Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
The Wizard runs in parallel to the main application . . . . . . . . . . . . . . 85
The Previous button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Help information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Windows layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
The Reset button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
The Create and Looped buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Input / Output for VelPAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Import and Input into VelPAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Binary Model Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Kingdom Link Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
ASCII Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Scanit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Input into VelPAK - Binary/Open Project File. . . . . . . . . . . . . . . . . . . . . . 90
Input into VelPAK - via the TKS link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Reading data into a New project or an Existing project . . . . . . . . . . . 91
Using a New project to read the data into. . . . . . . . . . . . . . . . . . . 91
Using an Existing project to add data to . . . . . . . . . . . . . . . . . . . . 91
Select OpenTKS via Merge or Replace . . . . . . . . . . . . . . . . . . . . . . 92
Replace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Merge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
The OpenTKS Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Types of Data for selection and what you can do with them in VelPAK
93
Output Data and run VelPAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
ASCII Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Replace/Merge/Ignore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
VelPAK Generic Format for individual data types imported into VelPAK 107
Export and Output from VelPAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Binary Save Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
ASCII Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Output from VelPAK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Binary/Save Project File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Kingdom Link Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

ASCII Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
The ASCII Export Process:
Common Procedures for Output all data types . . . . . . . . . . . . . . 116
Profile Data Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Surface Data Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Well Location, Top, Curve, Layer, Seismic Data Output. . . . . . . . 133
Scanit - a Stand-Alone Tool for re-formatting ASCII data . . . . . . . . . . . 137

Overview of Scanit Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Filters: Reformatting data imported to and exported from VelPAK . . . 139

Using Predefined Filters in the Filters Tab . . . . . . . . . . . . . . . . . . . . . . . 139
Using the Filters Tab to write your own Filter . . . . . . . . . . . . . . . . . . . . . 141
Writing your Filter - the Language . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Filter Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Filters supplied with VelPAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
LOAD - Filters For Profile Event Data . . . . . . . . . . . . . . . . . . . . . . . . 144
LOAD - Filters For Profile Fault Data . . . . . . . . . . . . . . . . . . . . . . . . 144
LOAD - Filters For Well Time-depth Data (CURVE) . . . . . . . . . . . . . 144
LOAD - Filters For Navigation Data (LINE) . . . . . . . . . . . . . . . . . . . . 145
LOAD - Filters For Polygon Data (POLY) . . . . . . . . . . . . . . . . . . . . . 145
LOAD - Filters For Stacking Velocity Data (STACK) . . . . . . . . . . . . 145
LOAD - Filters to load Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
SAVE - Filters For Profile Event Data . . . . . . . . . . . . . . . . 147
SAVE - Filters For Profile Fault Data . . . . . . . . . . . . . . . . . . . . . . . . 147
SAVE - Filter For Cont Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
SAVE - Grid Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
GNU GENERAL PUBLIC LICENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Layer Tool Module (Advanced VelPAK use only) . . . . . . . . . . . 153
Introduction to Advanced Layer Module. . . . . . . . . . . . . . . . . . . . . . . . . 154
Horizontal Wells. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Steps to Using the Layer Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Inactive Tops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Extra Tops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Layer Module Panels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Table Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Table Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Applying the Layer Definition to the Well Module . . . . . . . . . . . . . . . . . 169
Profile Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Profile Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Display Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Overlay Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Profile Edit Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Other Profile Display Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Display Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Display Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Display Dialog - Range Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Range Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Display Dialog - Name Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Display Dialog - Color Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Snap Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Snap Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Snap Dialog - Bias Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Discussion - Biassing the Profile Data . . . . . . . . . . . . . . . . . . . . . . . . 194
The 3 Methods of setting BIAS on your profile data. . . . . . . . . . . . . . 195
Snap Dialog - Missing Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Discussion - Why Use Missing? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Snap Dialog - Pod Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Discussion - Snapping with Pods . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Pod Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Snap Dialog - Clean Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
What is Clean? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Clean Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Depth Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Depth Dialog - General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Depth Dialog - Parameters Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Depth Dialog - Formula Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Depth Formulae Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
The Expanded Data Slots in the Model Tree - . . . . . . . . . . . . . . . . . . . . 211
For Depth Conversion supplemental data . . . . . . . . . . . . . . . . . . . . . 211
Advanced Notes for Profile Depth Conversions . . . . . . . . . . . . . . . . . . . 213
Writing and Saving your own process method . . . . . . . . . . . . . . . . . 213
The VUP and VDOWN Option within VelPAK Depth Conversion . . . 213
Advanced Process Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
The PRINT statement in the process methods . . . . . . . . . . . . . . 214
The PLOT statement in the process methods . . . . . . . . . . . . . . . 215
Negative Datum Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Reint Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Discussion - Reint Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Reint Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Stuff Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Stuffing in Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Stuffing in Depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Stuff Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Discussion - Using the Stuff Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
What Stuff does at Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Profile Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Profile Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Discussion - Multi Z-value Bias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Discussion - Producing Time or Depth profiles from Event or Grid. . . . . 229
Mistie Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Using Grid data to produce a Random Profile . . . . . . . . . . . . . . . . . . . . 232
Notes about generating a Random Profile . . . . . . . . . . . . . . . . . . . . . . . 233
XYZ Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

........................................................ Form
of Profile XYZ output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
XYZ Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Profile Edit Icons in Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Point Edit Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Pick . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Segment Edit Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Merge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Void . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Term . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Fault Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Theory of Fault Allan Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
What to do with an Allan Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Summary of Steps for the successful creation of an Allan Diagram . . . . 258
Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Display Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Visible Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Edit Mode Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Fault Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Fault Dialog - Select Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Tips and Advise for producing Allan Diagrams . . . . . . . . . . . . . . . . . . . 265

How to insert a Map Fault Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
When you have your Map Fault Polygons defined. . . . . . . . . . . . . . . 267
Errors that can occur in your Allan Diagram display . . . . . . . . . . . . . . . . 268
Hints if an error occurs in your Allan Diagram display . . . . . . . . . . . . . . . 270

Surface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Introduction to Surface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Display Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Basic Surface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Ribbon Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Contour Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Shaded Contour. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Overlay Layers Visible Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275
Overlaying/Displaying the Different Elements Types . . . . . . . . . . . . 276
Layers Visible - XYZ, Fault, Polygon, Grid Display . . . . . . . . . . . 276
Layers Visible - Seismic Line Display. . . . . . . . . . . . . . . . . . . . . . 277
Layers Visible - Flag Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Layers Visible - Stack Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Layers Visible - Well Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Layers Visible - Top Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Layers Visible - Deviation Display . . . . . . . . . . . . . . . . . . . . . . . . 282
Edit Mode Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Surface Edit Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Selection/De-selection of Lines and Wells . . . . . . . . . . . . . . . . . . . . . . . 285
Line selection for Ribbon Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Profile selection for 3d displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Wells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Saving Your Edits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
XYZ Edit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Fault Edit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
How to insert a Surface Fault Plane . . . . . . . . . . . . . . . . . . . . . . . . . 292
Polygon Edit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Grid Edit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Seismic Line Edit Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Process for Producing a Random 2D Surface Line . . . . . . . . . . . . . 299
Event Flag Edit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Velocity Edit Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Well Location Edit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Well Top Edit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Deviation Edit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Selecting Basemap lines; the Deselect and Invert Options . . . . . . . . . . 307

Surface Display Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Display Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Snapped, Unsnapped and Merged Data - A Discussion . . . . . . . . . . 312
Display Dialog - Range Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Display Dialog - Color Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Display Dialog - Mask Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Details of the Mask Value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Grid Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Where the Grids are stored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
A Quick Guide to Gridding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Grid Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Grid Dialog - Range Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Grid Dialog - Variogram Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Quick Guide to using the Variogram. . . . . . . . . . . . . . . . . . . . . . . . . . 330
Producing a Sensible display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Variogram Inputs, Icons and Displays . . . . . . . . . . . . . . . . . . . . . . . . 331
Grid Dialog - Randomize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Gridding Method Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Popular Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Kriging Methods; Kriging, Simple Kriging and SGS Kriging. . . . . . . . 338
METHOD = ‘Kriging’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
METHOD = ‘Kriging Simple’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
METHOD = ‘Kriging Sgs (Sequential Gaussian Simulation)’ . . . . 340
Smoothing Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
METHOD = ‘SMOOTH’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
METHOD = ‘LOESS Gridding’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Specialist Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
METHOD = ‘ Krig_Sgs’ - see Kriging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
METHOD = ‘Radial Basis Function’ . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Depreciated Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
METHOD = ‘Global’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
METHOD = ‘Random’. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
METHOD = ‘Cluster’. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
METHOD = ‘Weighted’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Process Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Process Dialog - Parameter Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Process Dialog - Formula Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Processing Formulae Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Merge Shallow/Merge Deep Examples . . . . . . . . . . . . . . . . . . . . . . . 354
Writing and Saving your own process method . . . . . . . . . . . . . . . . . . . . 356
Depth Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

Depth Dialog - General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Depth Dialog - Parameter Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
The Expanded Data Slots in the Model Tree . . . . . . . . . . . . . . . . . . . . . 363
For Depth Conversion supplemental data . . . . . . . . . . . . . . . . . . . . 363
Depth Dialog - Formula Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Depth Formulae Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Writing and Saving your own process method . . . . . . . . . . . . . . . . . . . . 365
The Language used in Depth Conversion . . . . . . . . . . . . . . . . . . . . . 366
Language Definition of Xpress . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Depth Conversion Supplied Variables/Functions . . . . . . . . . . . . . 366
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Listing of VelPAK’s Depth Conversion Formulae . . . . . . . . . . . . . 371
Trim Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384

Trim Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Group Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

Group Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
An example of defining Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
XYZ Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

Well Log Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Introduction to Well Log Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Well tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

Viewing a Well. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Manual Selection of the grid thicknesses on the curve from the Tops . . 398
Data tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Display Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Visible Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Edit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

Tops Mode Edit: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Curve Mode Edit: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Set as Depth Conversion Well. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Well Log Display General Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Tie Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

Tie Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
General comments for producing the best Error Grid via this method 412
Calibrate Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

Calibrate Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Using the Calibrate option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Manually Picking Tops. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

Viewing the Well and Picking the Tops . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Display of all Grids on one Well Curve . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Well Data Type Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Well Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Well Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Vertical Apparent IV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Misties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Further Details on Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
STACK CURVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Stack Curve - Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Stack Curve - TimeDepth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Stack Curve - Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
STACK LAYER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Stack Layer - Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Stack Layer - Isochron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Stack Layer - Isopach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Stack Layer - TimeDepth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Stack Layer - Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
SURFACE XYZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
SURFACE GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
WELL CURVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Well Curve - Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Well Curve - Residual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Well Curve - Time Depth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

Well Curve - Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
WELL LAYER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Well Layer - Isochron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Well Layer - Isopach. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Well Layer - Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Well Layer - Residual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Well Layer - Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Well Layer - Time Depth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Well Layer - Time Depth Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Well Layer - Velocity Average. . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Well Layer - Velocity Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
WELL TOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Well Top - Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Well Top - Time Depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Velocity Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Velocity Module - Display Types Options . . . . . . . . . . . . . . . . . . . . . . . 448

What the display shows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Layers Visible Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Velocity Display Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
To see which type of velocity is read in to your project. . . . . . . . . . . . . 451
Display Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
Dix/ Calibrate Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453

What processing does the DIX option perform? . . . . . . . . . . . . . . . . 454
Dix / Calibrate Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Dix / Calibrate Dialog - Factor Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
XYZ Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

Amalg Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

Amalg Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Amalg Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
What the Amalg display shows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Well Module display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Surface Module Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477

Velocity Module Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Velocity Volume Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480

Generating a dummy 3D volume for 2D data . . . . . . . . . . . . . . . . . . . . . 481
Velocity Dialog - General 3D Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Velocity Dialog - General 2D Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Velocity Dialog - Location Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Batch Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Stepped Guide - How to generate a volume in VelPAK using the Velocity
Volume Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
3d Visualization Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Introduction to 3d Visualization Module . . . . . . . . . . . . . . . . . . . . . . . . . 497
Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498

Overlay Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
3d Display fly-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501

3d Dialog - Range Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
3d Display - Surface Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
3d Display - Profile Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Curve Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Quick Guide to the Curve Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Curve Module Option Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

Zoom and Pan controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Graph Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Data Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512

Moving the Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Filtering the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Custom Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Custom Display of Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Curve Fit Display Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517

Curve Fit Display Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . 517

Curve Fit Generate Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Curve Fit Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Curve Fit Dialog - Standard Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Standard Graphs available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Curve Fit Dialog - Advanced Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Curve Fit Dialog - Randomize Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Curve Fit XYZ Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Advanced Curve Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532

Well Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Well Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Vertical Apparent IV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Misties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Detailed explanations of Advanced Curve X and Y axis inputs . . . . . . .539
STACK CURVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Stack Curve - Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Stack Curve - TimeDepth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Stack Curve - Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
STACK LAYER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Stack Layer - Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Stack Layer - Isochron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Stack Layer - Isopach. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Stack Layer - TimeDepth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Stack Layer - Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
SURFACE XYZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
SURFACE GRID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
WELL CURVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Well Curve - Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Well Curve - Residual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Well Curve - Time Depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Well Curve - Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
WELL LAYER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Well Layer - Isochron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Well Layer - Isopach. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Well Layer - Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Well Layer - Residual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545

Well Layer - Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Well Layer - Time Depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Well Layer - Time Depth Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Well Layer - Velocity Average . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Well Layer - Velocity Interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
WELL TOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Well Top - Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Well Top - Time Depth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Optimize Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
The Optimizing process within VelPAK . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Concepts of Optimizing in VelPAK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Types of Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Fit Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
Calculation Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
Well_Grid_Fit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Well_Line_Fit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Well_Point_Fit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Layer_Grid_Fit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Layer_Line_Fit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Layer_Point_Fit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Residual Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Well_Grid_Residual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Well_Line_Residual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Well_Point_Residual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Layer_Grid_Residual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Layer_Line_Residual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Layer_Point_Residual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Overlay displays available in the 2D Parameter Space . . . . . . . . . . 568
Grid Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Line Fit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Line Residual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Point Fit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Point Residual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
Point User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573

A Quick Guide to Generating Optimize Data . . . . . . . . . . . . . . . . . . . . . 574
Trouble Shooting - reasons your display doesn’t work: . . . . . . . . . . . . 575
Icons on the Optimize Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576

Icons on the Top Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Previous/Next Arrows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Display Type Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Basic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Ribbon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Contour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Shaded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Layers Visible Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Edit Mode Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Point Edit Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Point Pick/ Point Edit - Selection and De-selection of wells . . . . . 580
Value Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
The Graph and Data Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584

Data Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Moving the Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
Filtering the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
Custom Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Custom Display of Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Optimize Display Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588

Display Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Display Dialog - Range Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Display Dialog - Color Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
The Different Displays that Map_Type and Well_Type give . . . . . . . . . . 593
Well_Fit and None . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Well_Fit and Current_Well . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Well_Fit and All_Wells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Well_Residual and None . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Well_Residual and Current_Well . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Well_Residual and All_Wells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Layer_Fit and None . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Layer_Fit and Current_Well. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Layer_Fit and All_Wells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Layer_Residual and None . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598

Layer_Residual and Current_Well . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Layer_Residual and All_Wells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Generate Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600

Various Discussion topics regarding Generation of the Optimize Display 600
Zooming in on your display - Regenerate at new XY Min/Max . . . . . 601
Fixing a parameter in a three (or more) parameter function: . . . . . . . 602
Velocity Function Parameter Ranges . . . . . . . . . . . . . . . . . . . . . . . . . 602
When Instantaneous Velocity Decreases (“Negative K”) . . . . . . . . . . 603
Recommended First Pass Parameter selection for Speedy results . . 604
Generate Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
Generate Dialog - Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
Generate Dialog - Randomise Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
XYZ Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611

Method - Error, Fix_X, Fix_Y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Fix_Y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Fix_X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
VelPAK Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Pre-defined Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
The Nested Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
The Nested Workflow Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
The ‘Start Here’ Simple Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621

Guide to setting up the Simple ‘Master’ Workflow . . . . . . . . . . . . . . . . . . 621
Example Running a Depth Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Looking at the Event Workflow in detail . . . . . . . . . . . . . . . . . . . . . . 622
Running the Master Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Where Workflows are Stored and Saved . . . . . . . . . . . . . . . . . . . . . . . . . 628
Parts of the Workflow Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630

Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
Scratch1,2,3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
Top Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
Right Hand Property Grids. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

Workflows Property Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Nodes Property Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Nodes Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
The Types of Pre-defined Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . 646

Workflows Property Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Workflows - Start Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Classic Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
User Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Write Your Own Workflows - (Component & Utility Workflows) . . 648
Writing a Workflow from scratch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650

Building Your Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Workflow Control Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653

Pause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Execute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Building your Branch Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Loop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Seed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Repaint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
Batch Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
List of Pre-defined Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

Interval Velocity v Depth Well Layer Graphs. . . . . . . . . . . . . . . . . . . . . . 673
Interval velocity vs. Well Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Average Velocity v Time Well Layer Graphs . . . . . . . . . . . . . . . . . . . . . . 675
V0KZ Optimize Fix K Map V0 Methods. . . . . . . . . . . . . . . . . . . . . . . . . . 675
V0KZ Optimize Single V0 K Map Error Methods . . . . . . . . . . . . . . . . . . 677
V0KZ Optimize Fix K Map V0 Using External Drift of Time. . . . . . . . . . . 677
Sonic Log Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678

Stacking Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Analyze Module:
Stochastic Modelling in VelPAK . . . . . . . . . . . . . . . . . . . . . . . . . 681
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
P10, P50, P90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Parametric Variation and Sequential Gaussian Variation (SGS) . . . . . . . 682
Methods of Parametric Variation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
Sequential Gaussian Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
Using VelPAK for Stochastic Modelling. . . . . . . . . . . . . . . . . . . . . . . . . . 687

Definition of Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
Spill Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
Viewing the Spill Point and Crest on a Map . . . . . . . . . . . . . . . . . . . 690
Viewing a combination of Spill Points on one map for a number of realisa-
tions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
Statistics Collection and Analyze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Volumetric Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Typical VelPAK workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
Introduction to Analyze Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695

Model vs Wells Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
Icons on the Analyze Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
Graph, Data, Data2, Anim and Summary Tabs . . . . . . . . . . . . . . . . . . . . 700

Analyze Info Tool Tip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Drill Down Image display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
Moving the Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
Select Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
Filtering the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
Custom Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
Custom Display of Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Column Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Well Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707

Model Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Data2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Analyze Display Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
Generate Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714

Analyze Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Standard Graphs grouped by Model . . . . . . . . . . . . . . . . . . . . . . . . . 716
Scatter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
Histogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
Standard Graphs grouped by Well . . . . . . . . . . . . . . . . . . . . . . . . . . 717
Scatter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
Histogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
Generate Dialog - Advanced Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
Model vs Well plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
Statistics Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

Using Statistics General dialog as a “one-shot” Volume generator and QC
tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Using Statistics dialog within the workflow . . . . . . . . . . . . . . . . . . . . 722
Selecting the Volume method - Top, Base and Contact or Spill . . . . 723
Top Depth only being used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Top Depth with Contact or Spill point . . . . . . . . . . . . . . . . . . . . . . 724
Top and Base Depth grids being used . . . . . . . . . . . . . . . . . . . . . 724
Top and Base with Contact or Spill point . . . . . . . . . . . . . . . . . . . 725
Statistics Dialog - General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
Statistics Dialog - Statistics Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Properties
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
Anim Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
AOI or Area of Interest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735

Apparent Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Average Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Background Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
BIN file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
D ......................................................... 737
Datums . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Depth conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Diagnostic mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Dix Interval Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
F. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
Fly out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
G ......................................................... 741
Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
GridEvent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
GridDesc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
GridType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
I .......................................................... 744
Interpretation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Interval Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
INDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Instantaneous Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Isochron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Isopach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
J . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
L. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746

Layer cake depth conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
Layer definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
M......................................................... 747
Model Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Model Tree Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
P ......................................................... 749
Pods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
Profile Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
Property Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
Pseudo Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
RMS Velocity, Vrms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
S ......................................................... 752
Seismic Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Stacking Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Surface Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
TKS Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
V ......................................................... 754
V0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
VelPAK Model File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
Velocity Gradient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
Velocity Intercept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
Velocity Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
Velocity Volume Generation (VVG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
Well Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756

X-Y-Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
XYZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757

VelPAK - Introduction
VelPAK can be used in three main ways - using the Wizard, Workflows or driving the software
manually.
• The Wizard allows the user to depth convert layer by layer quickly and efficiently using a
variety of standard depth conversion methods. The wizard forms an excellent introduction
to depth conversion techniques and the capabilities of the software, and should cover
most depth conversion scenarios.
• Workflows - Allows for more complex depth conversions to be performed. Many of the
VelPAK processes can be turned into Workflows which step-by-step can lay out the
actions required to complete a particular task. Tasks that are cumbersome and/or
repetitive can be completed with a click of the mouse in WorkFlows. They guide you
through each process step-by-step, leaving very little room for error and confusion.
The following topics are included in the VelPAK user manual:

• The Wizard
• The VelPAK Main Window
• Input / Output for VelPAK
• Layer Tool Module
• Profile Module

• Fault Module
• Surface Module—The SURFACE Module displays and analyzes data with XY co-
ordinates.
• Well Log Module—The Well Module is used to view and specify well curves, tops and
layers and to specify which tops correspond to the top and base of each seismic layer.
• Velocity Module—The stacking velocity module is designed to take raw stacking
velocities from the seismic processing run, and extract the velocity information from these
values.
• 3d Visualization Module—The 3d surface viewer allows the display of multiple surfaces,
wells and profiles in an interactive environment.
• Curve Module—The Curve module enables you to cross plot various data items from
VelPAK and visually inspect the relationship between those items.
• Optimize Module—In the Optimize module, parameter values are derived for different
velocity functions, and various displays are produced to derive best-fit parameter values
for all classic V0 and K depth-conversion methods for each required layer.
• VelPAK Workflow—Many of the VelPAK processes can be turned into Workflows which
step-by-step can lay out the actions required to complete a particular task.
• Analyze Module: Stochastic Modelling in VelPAK—A stochastic modeling tool for
estimating probability distributions of potential outcomes by allowing for random variation
in one or more inputs over time. The Analyze tool enables the user to develop a
reasonable estimate of depth uncertainty based on a large number of depth models
derived from one or more depth conversion scheme and allows the user to identify the
key parameters controlling the range of Gross Rock Volume.
VelPAK user manual describes the following topics:
• Depth Conversion of Profile and Volumes
• Profile Snapping
• Well Layer Definition
• Stacking Velocity tools
• Curve Fitting
• Fault Allan Diagrams
• Mapping
• Optimization
• 3D Visualization
• Analyse
A Wizard is used to guide the inexperienced user through the complex Depth Conversion
routines.

The DATA TYPES stored within a VelPAK model
VelPAK can store many different types of data.
These can be placed into four broad groups:
a. MAP data
b. STACK data
c. WELL curves
d. PROFILE data
Group Type Description Method(s) of Input Function
Mapping,
Location Standard navigation - Import ASCII file provide the
data read into VelPAK - via seismic X,Y data for all
to produce a basemap workstation link other VelPAK
functions
Map Fault points - Import ASCII file. Gridding

Faults information with - Digitize on-screen. Mapping
vectors joining them
- Fault Gen program Allan
to display a spatial
- via seismic Diagrams
Fault Pattern viewed
workstation link
on a map for a
selected horizon
MAP
Grids Production of grids of - Import ASCII file. 3D Map
data from the Profile - Created internally displays
information or XYZ from data Depth
data stored in VelPAK - via seismic Conversion
model workstation link Output
XYZ Storage of XYZ - Import ASCII file. Gridding

values, independent - Read in as part of Map Displays
of the Time, Velocity VelPAK binary model
or Depth values - via seismic
associated with the workstation link
Seismic Profile data
Polygons Used to bunch - Import ASCII file. Display,

together similar data - Read in as part of Gridding,
on-screen VelPAK binary model Processing
- Digitize on-screen and Depth
- via seismic Conversion
workstation link

Group Type Description Method(s) of Input Function
PROFILE Profile Intrinsic part of the - Import ASCII file. Linking these
Faults Profile data - Create new profile to the Map
faults inside VelPAK faults is the
- via seismic basis of Allan
workstation link Diagrams
Events Profile horizon data - Import ASCII file. SNAP it and

- Create new horizons MAP it
inside VelPAK
- via seismic
workstation link
STACK Stack Time -Velocity Pairs - Import ASCII file. Depth

- VelPAK binary model Conversion
calculation
Location Well Locations - Import ASCII file. Depth

- VelPAK binary model Conversion
calculation
- via seismic
WELL
workstation link
Tops Well Tops Depth
Conversion
calculation
Curve Well Log Curves Depth

Conversion
calculation
Layer Defining layers Depth

between Tops and Conversion
Grids for Horizons calculation
The MODULES and what they can do for you

Modules are:
The WIZARD Module
The LAYER Module (Advanced User only)
The PROFILE Module
The FAULT Module
The SURFACE Module
The VELOCITY Module
The WELL LOG Module

The CURVE Module
The 3D VISUALIZATION Module
The OPTIMIZE Module
The WORKFLOW Module
The ANALYSE Module
The Wizard Module

The Wizard is very useful for quickly preparing certain data, such as velocity grids from
seismic velocities, or computing XYZ data that can then be used manually.
Once data has been loaded into the model and layer definition and log calibration performed
(if required), the user may launch the Wizard module.
This allows the user to depth convert layer by layer quickly and efficiently using a variety of
standard depth conversion methods. Most of these tasks generate standard velocity
functions or apply typical depth conversion methods to the selected event.
GO TO the Wizard Main Documentation
The Layer Module (Advanced User only)

It is necessary in VelPAK to relate the seismic pick to the geological top. This often cannot be
achieved simply because of missing sections at the top and/or base of layer.
Usually the Layer Definition within VelPAK will have been set up through the import link
where for every layer in the VelPAK window that you have inserted a time grid surface you
need to define one top (or more) to be associated with that surface.
However it may be necessary to revisit the layers when in VelPAK.
LAYER Module takes tops information typically used in a VelPAK project and produces a
Preliminary Master List containing all the tops used but in chrono-stratigraphic order.

GO TO the Layer Module Main Documentation
The Profile Module

SNAPPING
Within this module, you read in your profile data and SNAP the horizons so that each horizon
produces a continuous layer for output.
GO TO a detailed discussion of the Origins and Rationale of Snapping
PROFILE DEPTH CONVERSION
Layer Cake Depth Conversion, using either pre-stored methods or user-defined methods,
utilizing Constants, Grids, Curves and a large number of standard formulae. Processing of
grids.
RE-INTERPOLATION
Re-Interpolation of profile horizon data to a SMALLER shotpoint increment. (Re-interpolation
never acts on data to make the increment larger between shotpoints.)
STUFFIT
Allows you to create and add any number of new horizons into VelPAK using given isochrons
or isopachs. Any new migrated fault position is calculated semi-automatically.
PRODUCTION OF NEW PROFILES
From profile data on intersecting lines or from selected grids stored in the INFO page.

VARIOUS HORIZON DISPLAYS
- Fills of the profile in time, depth and velocity, including instantaneous velocity.
- Intersections between lines and misties between horizons can be displayed on your filled or
unfilled profile.

GO TO the Profile Module Main Documentation
The Fault Module

Creation of Allan Diagrams; fault polygons picked on a Map Display can be selected and
viewed in profile with all horizon data going into and/or out of the fault.
Takes all the profile faults for a selected Map fault and displays them in an axis of their own,
allowing you to see at a glance the quality of the horizon picks at the faults. It is a useful
check for snapping errors or interpretation errors at the faults.
By displaying horizons both coming into and going out of the fault the abutment of the fault
throw can be viewed.

GO TO the Fault Module Main Documentation
The Surface Module

Module comprises:
DISPLAYS
GRIDDING
DEPTH CONVERSION
PROCESS
FAULT GENERATION
TRIM
GROUP
GO TO the Surface Module Main Documentation

Displays
Base Maps
The Basic Map option displays on-screen a basic basemap stick plot of the map data within
the memory model, along with an XY grid around the map.
FAULTS and other types of flags taken from the snapped profiles can be marked onto
basemaps, with the ability to view these Flags on any selected horizon on the standard
basemap.

Fault Polygons can be drawn on-screen on the basemap, joining the Fault Upper and/or Fault
Lower Flags taken from the profile data for each line.
Once these Fault Polygons are assigned a name, these polygons can be viewed in profile to
produce Allan Diagrams (in the Fault Module) of the horizons that run into and out of the fault.
Ribbon Maps
This will construct a polygon of color varying with the time/velocity/depth values that are
posted along a seismic line, for any selected horizon within your model.
You DO NOT need to SNAP your data before displaying them as a Ribbon Map, and thus this
can act as a very useful QC check on your data when they have just been read in, to check
for inconsistencies in the general trend of the data.

Contour Maps
The Contour Map option provides quick and simple on-screen contour displays, with or
without basemap details.
VelPAK will grid the selected horizon data and display the associated contour pattern.
Gridding Parameters can also be changed by you.
Shaded Contour Maps

Produces a color fill contour display of your selected horizon data.

Gridding
A comprehensive gridding package to grid the snapped horizon data.
Although selecting a contour display MAP does an on-the-fly gridding run to produce the grid,
the gridding option allows you to edit the Gridding Parameters manually to suit the
requirements of the particular VelPAK model, for example to change the Method of gridding,
or change the Search Radius.
VelPAK uses GTGRID as its basis for Gridding, providing access to a library of gridding
routines prepared by Geophysical Techniques (GT), Inc..
Gridding and contouring can either be done on the horizon data displayed for your selected
horizon, on a previously created and stored grid within VelPAK, or on XYZs. Grids created
externally from VelPAK, previously created grids from within VelPAK or XYZs are stored and
can be viewed from within the INFO page of VelPAK, for any selected horizon.
Depth Conversion
Depth Conversion of surface data within VelPAK, using a variety of methods or ‘Create-your-
Own’ methods.
Process
Grid manipulation; multiplying, adding etc. grids together, or with constants to produce new
grids. Also a whole set of other processes are available including Grid-to-Grid depth
conversions. Or ‘Create-your-Own’ methods.

Fault Generation
The ability to generate Map Fault patterns for horizons, using a map fault pattern already
picked.
VelPAK will essentially ‘shift’ a map fault pattern down or up to the next horizon, displaying a
Map Fault Pattern that exactly matches the Fault Upper and/or Fault Lower flags from the
Profile data for the same named fault for the next horizon.
This gives you the option of only having to pick one set of Map Faults for this pattern to be
reproduced on all horizons (including new horizons added into the Model from grids using the
‘STUFFIT’ option) in the correct XY position for the lower (or higher) horizons.
Note: Fault Generation only generates further Map Faults on lower (or higher) horizons
using the fault pattern picked. Profile faults occurring only in lower horizons that do
not appear in the original horizon from which the Map Fault pattern was picked would
not appear as fault patterns, and therefore you would have to pick them manually.
FAULT1
FU
FL
FU
FL
FAULT1 FAULT1
FU
FU
FL
FL
Map Fault Pattern picked by user, using Map Fault pattern generated by
FU/FL information from Profile. Fault Gen using Green Horizon
FU - Fault Upper Flag Fault pattern picked by user, and
FL - Fault Lower Flag
Trim
Allows you to Trim data in a model, using polygon(s) as control. Polygons are used as trim
control for data either within them or outside the polygons, as selected in the dialog.
Data trimmed in the model are not retrievable. It is recommended that if you trim data, you
use the SAVE AS option to save your trimmed data as a new model, keeping your original
data model intact.

Group
GROUP controls how wells are grouped together. This can be used to take account of
different geological provinces in an area, or to include / exclude particular wells from the
calculations. Wells can be grouped either by drawing polygons on the map display, or by
editing the group number of each well. When groups are defined, VelPAK will only use the
wells in the current group. Grouping also applies to stacking velocities.
The Velocity Module

This module is designed to take raw stacking velocities from the seismic processing run, and
extract the velocity information from these values.
These corrected data can then be transformed for use in depth conversion either by taking a
horizon-consistent slice, or by creating pseudo-wells.
The Dix Option performs a Dix transformation, and integrates the interval velocities obtained
from this to generate time-depth relationships for each individual stacking velocity location.
Performing debiassing removes the effects of refraction on the Maximum Coherency
Stacking (MCS) velocities.
A percentage reduction can be performed on each interval velocity to take account of the
anisotropy and heterogeneity effects. This has a built-in default value.
GO TO the Velocity Module Main Documentation

The Well Log Module
The well log module is used to specify which tops correspond to the top and base of seismic
layers. The Well Curve is displayed in the centre of the display. To the right the thicknesses
are shown according to the grid isopachs generated between seismic layers.
To the left thicknesses are shown according to the Well Tops picked by you to define that
layer.
The Tie is a method to check how well the current depth conversion method ties to the well
data in the model.
GO TO the Well Log Module Main Documentation
The Curve Module

The Curve Fit module enables you to cross plot various data items from VelPAK and visually
inspect the relationship between those items. A line of best fit is generated and displayed.
You can then interactively edit which items contribute to the fit.
A comprehensive list of items are given in the Advanced Tab selection; whilst in the Standard
Tab option there are a selection of well used Graphs, Cross Plots and Relationships that can
be selected. Values derived from graphing can be used in the VelPAK Depth Conversion.
Once your display data are on view, you can interactively edit the points and the view using
the ‘Style’ option and direct mouse actions on the graph display.

GO TO the Curve Module Main Documentation

The 3D Visualization Module
The 3d surface viewer allows the display of multiple surfaces, wells and profiles in an
interactive environment. It becomes much easier to validate the depth conversion against
wells and other surfaces, and to visualise how velocity fields vary prior to generating volumes
to give a more efficient, quality controlled workflow.
GO TO the 3D Visualization Module Main Documentation
The Optimize Module

In the Optimize module, parameter values are derived for different velocity functions, and
various displays are produced to derive best-fit parameter values for all classic V0 and K
depth-conversion methods for each required layer.
Optimize uses non linear least squares curve fitting of time-depth curve data derived from
sonic logs, check-shots or tops and times to derive the best function parameters for each
well. It has the facility for allowing one parameter to be fixed and the other mapped e.g. fixed
K and contoured V0. With close interaction between the parameter grid and the mapping
modules you can immediately see the V0 and k values that best suit your data.
GO TO the Optimize Module Main Documentation

The Workflow Module
Many of the VelPAK processes can be turned into Workflows which step-by-step can lay out
the actions required to complete a particular task. Tasks that are cumbersome and/or
repetitive can be completed with a click of the mouse in WorkFlows. They guide you through
each process step-by-step, leaving very little room for error and confusion.
VelPAK makes extensive use of workflows to assist you.
GO TO the Workflow Main Documentation
The Analyse Module

For risk reduction analysis, this allows plotting, display and animation of results of multiple
realizations of the VelPAK model.
The Analyse tool enables the user to develop a reasonable estimate of depth uncertainty
based on a large number of depth models derived from one or more depth conversion
scheme and allows the user to identify the key parameters controlling the range of Gross
Rock Volume.
An 'absolute' answer to the depth conversion problem is impossible; the looped depth
conversion processes available in the workflow system will generate multiple depth
conversion models. The Analyze Module then allows filtering and analysis of the results and
gives confidence as to the likely range of uncertainty in the model, and the deterministic
parameters which will yield credible P50 (most likely) and end-point (P10, P90) solutions.

Integration and Links with Kingdom data
VelPAK is fully integrated with the TKS Kingdom project. Relevant data can be selectively
brought in from the Kingdom project via the TKS Link.
The Origins and Rationale of Snapping in Profile mode

The industry-wide adoption of workstation technology for seismic interpretation, and the
power of data visualization that it brings has almost overnight made seismic stratigraphy
accessible to explorationists of all disciplines.
Domination of the seismic market by 3D surveys has led to an explosion in the sheer volume
of interpretation “picks” going forward to the mapping process.
The downside of this has been that an increasing reliance on computer gridding (to handle
the vastly increased volume of seismic horizon picks) has tended to distance the interpreter
from their traditional skills of contouring and map making.
Experience has shown that the production of a coherent set of maps from a complex dataset
(in the absence of an effective means of quality control prior to gridding) is a slow and
iterative process. Discussions with experienced Oil Company geophysicists have elucidated
that for a typical North Sea 3D survey up to 50% of budgeted project time must be allowed for
the mapping and depth conversion phase.
Does this need to be so? The answer is no, and mapping time can be cut dramatically if the
problem areas can be eliminated prior to the gridding phase.
Increasingly the busy interpreter is relying on the services of a specialist computer mapping
analyst for the map-making phase of the work.
This specialist will process the interpretation output files through standard gridding
procedures, including clipping, fault polygon filling and conformal limiting (matching individual
horizon grids to one another in three dimensional time-space) to produce a best effort at a
gridded representation of the geological strata the interpreter picked in profile mode on-
screen.
To what extent is this gridded representation a match with the interpreter’s model? In many
commonly occurring situations the match is surprisingly poor, and it is this loss of fidelity in
the transfer from picked profile to gridded map that has prompted the development of
VelPAK.
VelPAK as a Mapping Package pre-processor.

The primary function of VelPAK is to produce re-integrated time profiles from a suite of
seismic picks. Many other procedures and applications follow naturally from this, but this
apparently simple operation is the key to all of them.
Why is this re-integration necessary? To understand this we need to consider the procedures
for digital “capture” of the time image of the geological model visualized by the interpreter
either on paper on-screen.
Seismic interpretation is essentially a boundary recognition procedure.
Horizon “picks” are marked up by the interpreter to signify lithological unit boundaries
(interfaces), be they sequential, intrusive, erosional or faulted.

The interpreter constructs a layered model (on paper or on-screen) by identifying and
marking up (picking) segments of primary horizon boundaries wherever they are correlated.
Except in very simple geological situations these segments may not be continuous across the
profile; they will be present only in those places where the seismic interpreter can recognize
the seismic “character” corresponding to a correlatable boundary.
Segment breaks may correspond to fault positions, local limits of the horizon due to
truncation (inconformity) or intrusion (salt piercement?) or combinations of these.
A boundary of geological significance such as “Top Triassic” may be represented in the
seismic interpreter’s model by two or more horizons; for example both “Top Triassic” and
“Base Cretaceous” where progressive erosion of the pre-Cretaceous sequence has occurred.
Opportunities to view and visualize geologic structure from almost any aspect, automatic
digitizing to a pre-defined horizon characteristic (peak, trough) and storing of picks as they
are made encourages the interpreter to pick ever more interfaces to define his layer cake
model. And full advantage of data visualization tools will be taken to define fault traces with
precision, honouring cycle terminations at intermediate horizons between their mapped
boundaries.
How, therefore, is all this precision so often lost in the conventional mapping process?
To understand this we must revert again to the processes of digital data capture, and
appreciate that the data capture process (from paper sections on a digitizing table or straight
from a workstation window) is horizon segment oriented; that is the horizon output file will
contain only a set of variable length segments representing elements of the primary bed
boundary as identified by the interpreter.
The mapping analyst will be supplied with files of these segments relating to one horizon at a
time; initially he will have no idea of the relationship of this horizon to its neighbors, and often
no idea of the faulting other than perhaps a set of fault polygons delimiting the area of offset
in which the bed top or base is represented by a fault plane.
Commonly the fault trace pick- the position of the line of fracture offsetting a sequence of
beds - is used only as an interpretational aid in correlating faults from bed to bed. Beyond
defining “fault polygons”, its vital bed boundary information plays no further part in the
mapping process, being replaced by a crude re-sampling procedure called “fault filling”.
Thus horizons are gridded and contoured in isolation, then “fitted together” to produce a
three-dimensional model: the conformally-limited grid stack.
It is in this departure in the mapping process from the intra-horizon relationships so clearly
visualized and defined (in profile mode) by the interpreter that the problem lies. In the re-
creation of valid isochores from the conformally-limited grid stack, which is the industry
standard today, many subtle problems and inaccuracies may remain undetected.
And it is by “re-integrating” or reconstructing the profile from the horizon segment picks, prior
to the mapping stage, that VelPAK so successfully eliminates these problems.

The VelPAK Main Window
Layout - docking and floating windows
All visible windows and pop-out dialogs within VelPAK have the ability to be detached from
the main VelPAK window and placed anywhere on your screen (floating mode) or anywhere
else within the VelPAK window (docked mode).
Customized
VelPAK
window with all
views docked
in main
window

Customized
VelPAK
window with
some views
floating
outside of
main window
If you close a design and reopen it, the document windows have the last layout that you used.
This means that the same windows are open, and they have the same sizes and positions.
Your favorite lay-out can be loaded and saved from the File drop-down.
If no Layout has been defined, the views will initially be displayed in Tab form, clicking will
bring the required module to the front.
Tabs - click to bring

each VIEW to top

To detach a window of VelPAK:
1. Drag it away from its position using the top window bar, or tab if it is a tabbed item.
Note: For pop-outs these need to be pinned out before dragging is possible.
2. Continue to drag the item over the window; you will see docking icons appear:
3. As you drag the detached window over these docking icons the area of the window will
become shaded showing you where the window will be attached when you lift your finger
up.
Docked
Position if
held over
right hand
docking
icon
Floating
Window
4. Unless you drop the window when the docking icons are displaying a shaded zone
showing where the window will be docked, the window will be a floating one.

Command Drop Down Menus
File
New - Will clear the current model allowing you to load a new set of data.
Open - the option for loading a VelPAK binary save file previously created from VelPAK.
Go to Input/Output from VelPAK for full details
Open TKS - the option for importing relevant data from your open TKS project.
Go to Kingdom Link input for full details.
Save/ Save As - the options to save your data as an internal VelPAK binary model. Save
will automatically save it as a previously defined named model, Save As will ask you to
give a new file name.
If the model contains SEG Y velocity volumes using "File> Save As..." will prompt if you
wish to copy those to the new model or not (press Cancel at the prompt and the SEGYs
will not be copied).
Note that if you have a project with a lot of data in it, for example grids and images, you
can turn on/off the data you wish to save from the Preferences tab of the Model Tree.
Import/Export - the method of reading data in or exporting data as ASCII files.
Go to Input/Output from VelPAK for full details.
Printing Options - standard Windows printing options available to you are utilized here.
See below for details.

Layout - allows you to load or save the layout you have designed for your VelPAK
windows. Default will restore the standard VelPAK window. Go to Layout - docking and
floating details.
Recent Files - A list of recently used VelPAK projects will appear here.
Printing
Print Page Set-Up
Use the Page Setup dialog box to determine the paper size, page orientation and margin
width.
To set or change the page setup:
• In the “Paper” panel, select the paper size and its source in the printer.
• Orientation:
- Portrait orientation places the top of the image against one of the page's narrow sides.
- Landscape orientation places the top of the image against one of the page's wide
sides.
• Enter the appropriate values in the margin boxes. The left and top margins indicate the
position on the page of the image’s left and top edges; the opposite for the right and
bottom.
• Click Printer to select a different printer.
• Click OK to close the dialog box and save the settings.

Print Preview
To the left of a thumbnail shot of the generated image. Drag the red window over this
thumbnail to move the main image or use the standard zoom keys to view the generated
image in larger of smaller detail.
Print
Standard ‘Windows’ Print page. Before using this dialog box, open the Print Setup dialog box
to select the paper size, page orientation and margin width.
• Select a printer in the Printer name box.
• Select print range if you have more than one image to print from the Print Preview.
• To print the image to a file instead on the printer, select the “Print to file” check box.
Clicking Print opens the Print to File dialog box, where you can choose a location and
name for the new file.
• Set the number of copies you want to print.
• Click OK. VelPAK sends the file to the printer or opens the Print to File dialog box.
Note: Print, Print Set Up and Print Preview are also available from Icons on all the Module
tabs.

Print Print Print

Set Up Preview
Edit
}
}
The Edit Delete options provide ‘multi-layers’ of delete, so that single or all elements can be
removed from the memory model.

Delete All
Lines, Faults, Surface, Wells
This option will delete ALL elements stored under the various type of data you select to
delete. Proceed with caution.
Delete Profile Faults/ All Event / Selected Event
Use this option to delete elements of your VelPAK model relating to the Profile data; that
is Faults and Horizons.
Delete Surface Data
Any type of Map data can be selectively deleted.
This includes XYZs, Faults, Polygons and Grids as well as all or some of the Surface
Location navigation lines.
For the navigation lines you need to select the lines you wish to delete from a basemap,
unless you want to delete all the navigation data. Go to Delete Options below.
All other types of MAP data refer to the slot or slots in the Model Tree under the horizon
where the data are stored.
Note: For deletion of individual items of data in slots within the Model Tree, use the Model
Tree delete options.
Delete Options
All
As this suggests, all data held under the selected type will be deleted.
Selected
Certain delete functions give you the option to delete selected lines. These are lines
selected from your basemap. Go to Select Lines.
Current
This deletion option refers to the line currently selected on the map, profile or from
within the Model Tree.
Unsnapped
For profile data and map location data this will delete all unsnapped lines.

No Interpretation
For Surface locations with no profile data attached
Delete Stacking Velocities
All
All stacking velocities in the model will be deleted.
Current
Delete Stacking Velocities on the currently selected line.This deletion option refers to
the line currently selected on the map, profile or from within the Model Tree.
Selected
Delete Stacking Velocities on certain, selected lines. These are lines selected from
your basemap. Go to Select Lines.
Unsnapped
Delete stacking velocities on all unsnapped lines.
No Interpretation
Delete stacking velocities for Surface locations with no profile data attached
Sort Model
Provides an option to either sort and display the lines within your VelPAK model
Numerically or Lexically within the line selection display. It is preferable to sort 2D lexically
but 3D numerically.
Reset Cache
Some items of VelPAK are stored within the Cache (grids for example). This option will
reset/clear all items from the cache memory.
Rebuild
On rare occurrences when you may suspect the VelPAK model you are working in has
been corrupted in some way, using this option will rebuild the data base.
This option would usually only be used after consulting with the Help Desk staff.

View
Opens the main Modules including the Workflow into the main VelPAK window.
Tools
Lever Analyse - The Analyse Utility launches an external program; it takes the data from the
Analyse module of VelPAK and performs sensitivity analysis/spider plotting - comparing the
relative importance of the results of multiple realizations in producing the volume data derived
from the Analysis module of VelPAK. An on-line help system is available from the Help drop
down within Analyse.
HiDef Tool - launches a new window that allows log-scale velocity detail to be applied to a
SEGY velocity volume whilst honouring the depth conversion velocity trends and geological
layering
Scanit - Scanit is a visual, general purpose data formatting tool which allows you to reformat
your data files into any columnar flat file format you require.
An on-line help system is available from the Help drop down within Scanit.

Volume - Volume is a stand-alone program available from the Tools drop-down menu.
Working on volumes within TKS (possibly generated by VelPAK but not necessarily) its main
usages are two-fold
Time-Depth Curve text file production - This uses an Interval Velocity, Average Velocity
or RMS Velocity Volume loaded into TKS to produce Time-Depth curve values for
selected wells within the area of the volume. ASCII time-depth pairs are produced which
are then read into the TKS for the selected wells.
Velocity Volume text file production - This will extract velocities from a velocity volume
and produce an ASCII text file of the Time/Velocity pairs that can be read into VelPAK via
the Import - Profile Stack option.
An on-line help system is available from the Help drop down within Scan

Calculator - brings up the standard Windows calculator.
Window
Shows you which modules of VelPAK you currently have open and allows you to switch
between them in a similar fashion to pressing the tab for each window.
Note: This only shows modules that are currently docked as opposed to floating.

Help
Brings up VelPAK standard Windows Help system on either the Contents, Index or Search
page.
Explore takes the user to the directory where the pdf versions of the helps are stored.
StartUp will bring up the ‘What’s New’ start up screen that comes up when you first open
VelPAK.
About will show the version of VelPAK that you are using.

ToolBar 1 - Standard Icons
ToolBar 1 - Standard Icons
New Open Save Save as Help Help Help

Model Search Index Contents
Tool Bar 1 on the main VelPAK window displays standard use Icons for VelPAK operations.
These are documented in the following places:
New/Open/Save
Help

ToolBar 2 - Module windows

The module windows display the individual modules of VelPAK; Layer, Profile, Fault, Surface,
Well Log, Stacking Velocities, Curve Fit, 3D Visualization and Workflow.
Example: PROFILE Module window

Editing functions available to a Activation button for actions

Profile section e.g. point delete, relating to the profile
Previou segment move, insert. module - snapping, depth
s/Next
Arrows:
Move
from
current
Display
Types
Icon: A
drop
down
selection
of the
types of
All pop-ups and fly-outs can be made into a fixed “PROPERTY GRIDS”
window by clicking the ‘drawing pin’ icon to the top for actions relating to
right, in standard Windows fashion. the profile module;
All pop-ups and fly-outs can be removed from main crucial options to

Abort
Abort
Any process within VelPAK can be aborted by using the Abort button.

Model Tree
Model Tree
Expanded to
show unused
slots
The Model tree displays all data within the model you are looking at. Each element can be
expanded in standard ‘Windows’ fashion. Use the Model tree (or the Surface & Slot selector)
to select the surface, line or profile or well etc. you wish to analyze and the data within that
element.
You can use the Model Tree to delete specific elements from your model - used along side
the main bank of delete options available from the Edit drop-down at the top of the main
VelPAK window.
Data Elements stored under the Model Tree such as Fault files, XYZ files, Grids can be
moved or copied into other slots within the Model Tree within the same horizon. Go Here for
details of this.
Double-clicking on certain elements of the Model Tree will automatically turn on the overlay
for that data: for XYZ data, for example, XYZ and XYZ Label overlays are turned on. Double
clicking on a grid name will automatically display the grid in "Shaded" mode.
Double-click on an item in the project tree now For XYZ, XYZ and XYZ Label overlays are
turned on. For grids, the default is automatically set to "Shaded".
The Model Tree can be removed from view by clicking on the Drawing pin to the top right. It
will sit as a tab at the left of the window ready to be opened up. It can also be made to be an
independent window by clicking on it and dragging the top bar away from the main VelPAK
window.
Note: Data can NOT be deleted from the Model Tree

Model Tree
Model Tree - Top Bar Icons
Refresh Show Unused
Refresh Tree
The tree should automatically update and refresh itself after most procedures; however you
can manually update the Model Tree using this button.
Show Unused slots

Under some data types stored and displayed in the Model Tree there could be many different
elements stored.
The ‘Show Unused’ toggle at the top of the Model Tree allows you to view only those slots in
the Model Tree that are occupied by a valid data item.
For example in the expanded Model Tree shown below, under the XYZ type of data for
horizon one, there is the ability to store this many different data files, all XYZ files but with a
differing value of Z for each file.
For details of the meaning of the Expanded data slots Go Here.

Model Tree
Toggle On
If the same example is toggled so that the unused slots are hidden, the Model Tree becomes
considerably more manageable:

Model Tree
Toggle Off
Model Tree - the Data Elements

All data that are stored and used within VelPAK has an assigned slot within the Model Tree.
Many processes within VelPAK expect you to activate a slot for the data to be used within the
required process. Correct usage of the Model Tree and Surface&Slot selector is essential to
the successful use of VelPAK.
Model - Profile
Seismic Lines are stored under the Profile Data Element. You can scroll through the lines in
the Model Tree to select the Profile to be displayed in the Profile Module. Double-clicking on
a line name will display the profile in the Profile module window.
Note: If the profile has not been depth converted the ‘Display Type’ must be set to ‘Time’ for
the display to be shown.
The selected line will also be displayed on the Surface Module as the selected line (in blue).
• Random 2D lines are displayed as R:[Line Name]
• Inlines are displayed as I:[Line Name]
• Crosslines are displayed as X:[Line Name]
Note: Random 2d or in-lines &/or cross-lines with no interpretation will not populate the
Profile section of the Model Tree.

Model Tree
Model - Fault
Named Profile Faults are stored under the Fault Data Element. These are faults that have
been assigned a name, either from within VelPAK or from the external package that originally
produced the fault patterns.
Right-clicking on Faults on this part of the Model tree will delete surface named faults but not
profile faults (use Edit -> Delete Profile Faults to delete fault sticks on a profile).
Within VelPAK, Profile Faults need to be named in order to select them for display as Allan
Diagrams.
Model - Surface
All data relating to Surface within VelPAK. All data are stored under the relevant horizon
number.
Note: For Layers the convention is that these are always stored under the horizon at the
base of the layer.
For details of the meaning of the Expanded data slots Go Here.
Note: Double-clicking on an item in the project tree will automatically turn on the overlay for
that data, where appropriate.
Event Number
Up to 32 Events/Horizons can be utilized within a VelPAK project. Eight horizons will be
shown unless you are using the Model Tree in the Show Unused mode.

Model Tree
XYZ
All XYZ data are stored under these slots.
Fault
Surface Map Fault Polygons [not Profile Faults stored under the Fault Data Element]. These
can be read in via the Input/Output routines or manually digitized from the Profile flag pattern
on a Surface. Putting the fault patterns in different slots within the Model Tree allows you to
switch on and off between separate fault patterns.
Note: You can not display more than one slot at the time on your surface; to ‘merge’
separate fault patterns you will need to export the data to ASCII, concatenate the file
and import the data into a new slot.
For details of how to enter Surface Faults manually. Go Here.
Polygon
Polygons - used in Trim, Analyse and Group to define areas for manipulation.
Polygons can be stored in any slot (Time, Depth, General01 etc.) within a certain event but
you can not display polygons from more than one slot together on your surface.
More than one polygon area can be defined within the one slot within one event.
If polygons have been read in from you seismic workstation, a number of polygons can be
read in and stored within the same slot of your VelPAK model. These will retain the same
names as they have been assigned in the original project. Their names can be checked in
Polygon mode within the Surface module by selecting the polygon on screen using the
Polygon Segment Edit option.
Alternatively if you are digitizing polygons on screen from within the Surface module of
VelPAK you can name each polygon individually using the Polygon Segment Edit option. For
details of how to enter Surface Polygon manually. Go Here.
Note: To ‘merge’ polygons from different slots or events you will need to export the data to
ASCII, concatenate the file and import the data into your selected new slot.
Grid
All the grids produced from within VelPAK or Input into VelPAK from an external source are
stored here. Grids can be moved or copied into other slots within the Model Tree within the
same horizon event. Go Here for details of this.
Interpretation
Due to their nature, interpretation slots within the Model Tree are slightly different from the
rest of the Data Elements. The Time, Velocity and Depth interpretation data are stored under
these slots for each horizon within the model but you do not need to ‘activate’ them from here
in order to display the data on a Surface.
This is because routines which access the Interpretation data within VelPAK can use
Snapped, Un-snapped or Merged (a mixture of the two) data; the choice of these three types

Model Tree
being made in the Property Grids that relate to the features that use these data; for example
Gridding when you can use between the following as your input XYZ data:
Note: You can only Delete interpretations from these slots; a function you can also do from
the Edit Drop-down menu which would give you more control on the deletion routines.
For a discussion of Snapped, Unsnapped and Merged Data, Go Here.
Model - Well
A list of all the Wells within the model. Wells can be deleted from this list.
Model Tree - The Expanded Data Slots

If you expand the data slots in the ‘Show Unused’ mode you will see that under every Data
Type under the Surface element there are 40 data slots each with a unique name.
While some of them are for use as General slots allowing you to place any item within the
slot, most of the slots have been assigned a name. The first four slots are called Time,
Interval Velocity, Depth and Error allowing for the Primary data of that sort to (usually) be
placed in the these slots.

Model Tree
Toggle On
Further down, the slots named Average Velocity, Isochron, through Stack Interval Velocity
Smooth, Stack Debiased Velocity Smooth through to Depth Conversion System 06 are all
named to be used in various Depth Conversion processes. The standard supplied processes
within the Depth Conversion modules allow for all these interim values (usually grids) to be
output into their relevant slots here while producing the final required Depth Grid.
For an example of a depth conversion that would use these slots Go Here.
While Grids and XYZ are the most common elements to be stored in these slots, there are
the same named slots available under Fault and Polygon data types.

Model Tree
Model Tree - Cut/Copy/Paste/Delete

Data Elements in the Model Tree can be moved and copied between slots of the same type
on the same Horizon/Event and deleted entirely from the Model. Holding down the right hand
mouse button over the selected element will bring up a menu for cutting, copying, pasting or
deleting.
Note: Profile and corresponding Line data can only be deleted using this technique, not
copied etc.
You may need to

expand the Tree
to see the empty
slot you wish to
Cut move or copy
Copy your data
Paste
Delete
element to.
To Copy and Paste:

Select the element you wish to copy, select ‘Copy’ from the right hand mouse button menu
and then select the slot where you wish the element to be copied and select ‘Paste’. An alert
will come up warning you of what is about to happen.
.
Major Data Types - Profiles, Fault, Surface and Well can also be deleted via this method.
This will delete ALL the data elements stored under that Data Type, so proceed with caution,
and as Alert says we aware that if there is a large amount of data stored under that Type then
it could take some time to delete.
Delete
Note: The Edit Delete option from the Command Drop Down menus at the top of the main
VelPAK window provide ‘multi-layers’ of delete, so that single or all elements can be
removed from the memory model. This may be a more appropriate method of deleting
data elements or types. Go Here for details.

Surface and Slot Selection (“Surface&Slot”)
Surface and Slot Selection (“Surface&Slot”)
The Surface&Slot selectors are directly linked to the Model Tree; they show and allow you to
select the various surfaces and data slots currently active within VelPAK.
Keeping the Surface&Slot selectors open and on display helps you to see at a glance what
slots are active and what surface you are currently working in.
Note: This information is also shown at the bottom right of the main VelPAK window.
The Previous / Current horizon event selection is not available under the Surface&Slot
selection; due to its nature it is only available as a feature of the Workflow Module within
VelPAK.

Properties
Properties
The Properties window displays the values for the data type and element that has been
selected in the Model Tree.
For example selecting a ‘Profile seismic line name in the Model will display the min/max
values associated with this.
Selecting a Surface in the Model will display other relevant information associated with it.
The Properties window can be pinned out or removed from view by clicking on the drawing
pin to the top right. If removed it will sit as a tab at the left of the window ready to be opened
up. It can also be made to be an independent window by dragging the top bar.

Preferences
Preferences
The Preferences tab is stored behind the Properties tab. It has two distinct options
Save
The save part of the tab allows the user to select which items from the VelPAK project you
wish to save when you save the project as another named file and project. For example you
may have a a number of images generated from a realisation run or a large SEGY file stored
with in the project directory files. You can turn the various items on or off (Yes//No to save) so
that these are not saved in the new project.
You can manually copy them across to the correct directory if required at a later date.
Well
The Well part of the Preferences tab stored behind the Properties tab allows the user to
select what part of the well labels they wish to have displayed on map. Choose to turn on or
off the Name, Number or Unique Well Identifier as shown in the screen grabs below.

Console
Console
The console shows you what action VelPAK is taking following each user button press.
In some modules clicking the mouse button - either the left hand or middle button - will bring
up certain values for the data element you have clicked on. For example Stacking Velocities
in the Surface module- by pressing the middle mouse button on a velocity point you would
get a display in the Console of all the values for that point:
Like all other fly-out windows in VelPAK the console window can be kept out on display by
‘pinning’ the drawing pin on the top right of the window. It can also be made to be an
independent window by dragging the top bar.

Zoom and Pan Controls

Zoom
On all module tabs except Layer and Workflow there is the option to Zoom either as a pop-up
menu using the right-hand mouse button within the VelPAK display window or activated as a
toolbar within the top set of options. The toolbar zoom option is turned on by default but can
be turned off by right-clicking on the toolbar and toggling the check mark. Individual buttons
can also be removed.
Use the middle mouse button by clicking, holding and dragging it to move the display up or
down; moving the middle wheel while holding the button down will zoom the display in or out.
Tool tips on each icon provide a reminder as to the keyboard hotkey to enable the zoom/pan
interactions
Hot Key
z
i
o
p
u
d
l
r
f
t
Zoom - Any map data displayed can be enlarged by selecting Zoom from the View Menu.
Zoom under the View Menu allows you to define a window, with the mouse, in which you
wish to zoom. This is done by holding the arrow cursor down at one corner of the area of
interest and dragging it over to the opposite corner of the area. If you wish to stop your
zoom operation drag around a small area only.

Zoom In - Selecting Zoom In from the View Menu enlarges the centre of the display by
50%. When you have ‘zoomed into’ an area you can zoom out by selecting Zoom Out or
Reset from the View Menu.
Zoom Out - Selecting Zoom Out from the View Menu decreases the centre of the display
by 50%.
Pan - Selecting this option, wherever the mouse arrow is pointing, on activation will
become the centre of the new display. Pan Up, Down, Right and Left are self explanatory.
Refresh - Will refresh whatever is currently displayed in the window.
Reset - This will reset a zoomed display back to the original display parameters.

Color Tables in VelPAK
The color tables within VelPAK allow selection from standard VelPAK color bars, or import of
user's color bars. Color palettes can also be made and saved.
Available within:
Surface >Display > Contour_Colour
where it sets the color bar for grid/horizon displays
Profile >Display > Velocity_Colour
where it sets the color bar for time or depth velocity fill options
Profile >Display > Seismic_Colour
where it sets the color bar for SEG Y seismic file display
3D >Display > Contour_Colour
where it sets the color bar for mesh contours.
Color Table options

Stored Color Tables
The color tables on the right allow the user to select from a number of stored color tables.

The Top Bar
New Save Test Convert from

Kingdom
New - Resets the palette ready for the user to create a new color table.
Save - will save the color table as designed as a text file.
Test - will produce a test color table and apply it on the current display within VelPAK.
Convert from IHS Kingdom - will read in tables from your Kingdom project and
store them locally in the VelPAK color table area.
The Color Bar
Click on the color table bar to insert pegs which can then be used to set the color-range
according to the color palettes on the left.

VelPAK - The Wizard
The Wizard - for easy Depth Conversion
The Wizard is very useful for quickly preparing certain data, such as velocity grids from
seismic velocities, or computing XYZ data that can then be used manually.
Once data has been loaded into the model and layer definition & log calibration performed (if
required), the user may launch the Wizard module.
This allows the user to depth convert layer by layer quickly and efficiently using a variety of
standard depth conversion methods. Most of these tasks generate standard velocity
functions or apply typical depth conversion methods to the selected event.
The Wizard Overview page opens in a new tab.
This tab may be docked and floated just like all the other tabs.
Note: Generally when running the Wizard it is a good idea to float it away from the other
windows, so you can interact efficiently with both the Wizard dialogs and the screens
it presents.

Wizard Overview
The Wizard Overview gives a summary of the state of the current model. The top table shows
one row per layer in the model, with columns indicating the status of those layers.
Extensive context help screens assist the user in understanding the methods available.
Wizards may be “replayed” to update the model should minor changes to the model data be
made without user interaction required.
For a detailed guide for individual methods selectable from the wizard refer to the extensive
Helps on each individual Wizard screen.
The Wizard screen starts with the Help screen open.
To start the Wizard running, click the Run button in the Run Wizard column for the event you
wish to use. If you are working in a new model, you would naturally run the wizard for the first
event, then again for the second event, etc.
To change the depth conversion method for an existing layer, you can go back into the set up
via the Run option for that event.
Note: It is important to remember that if you change the depth conversion function or
method for a given layer, all layers below that become invalidated and you will need to
re-run the Wizard for the deeper layers.
When you have set up a Run for an event the final screen for the Wizard for that event is to
save the run as a run file named after the event and type of depth conversion method you
have just set up. This run file can be replayed by pressing the Review Wizard button and
selecting the run file that corresponds to the run you wish to recreate. This can be useful if
data in the model has changed (for example, well data added or deleted) but you wish to
assess the changes to the model using the same options as before.
Note: Be careful to review any regressions, optimisation results etc. Also be aware that you
would typically need to replay the wizard from top to bottom if data has changed. Only
the most recently run Wizard options are stored in the replay file.

Using the Wizard
On pressing the Run button, the user is presented with an option on which type of method
you would like to use. Subsequent steps through the wizard “drill deeper” down into options
based on the initial options selected.
The Previous button at any stage to go back a step in the Wizard.
The Wizard provides an excellent introduction to the capabilities of the software. Many
popular depth conversion methods are supported, but it is not exhaustive.
General Concepts
The Wizard runs in parallel to the main application
The Wizard runs “in parallel” to the main application. This means that you can fully interact
with the application, even part way through the Wizard (assuming it isn’t doing any
processing, gridding etc.). This enables you to display, edit, correct or delete data mid-Wizard
and continue. Most Wizard pages feature an action button, typically labeled “Generate” or
“Apply” depending upon the context. If you edit data within the model, press the appropriate
action button to update the changes to the model, graphs etc.
If in doubt, simply rerun the Wizard from the beginning - most options are very quick to work
through.
Certain operations should not be done during Wizard execution unless you fully understand
the consequences to your model.
• Do not change the Surface number, either through the use of the icons, or setting
the Surface number selector. If you have pressed an action button in the Wizard to
generate results, you can change the Surface number to compare the results with a
different Surface, but ensure you change the Surface back before pressing the action or
Next button again.
• Do not change the layer definition. If this is required, exit the Wizard, re-do the layer
definition, the rerun the Wizard for all layers.
• If you use Save or Save As in the model mid-Wizard & then close & reload the model, the
Wizard state is not saved. Therefore you will need to rerun the Wizard for a given layer
from the start.
• Do not run a workflow mid-Wizard – results will not be guaranteed to be correct from
either the Wizard or Workflow.
• f you close the Wizard window, you will need to restart the Wizard from the beginning.
The Previous button
The Previous button is used to step back a page in the Wizard.
Note: Note that if you go back a page, you may need to reset the parameters as they are not
always stored in the user interface.

You may need to regenerate plots or graphs, even if you do not change any parameters,
before you can use the Next button again.
Help information
Each Wizard page has a corresponding Help screen. It gives extensive hints and tips on what
the function or method is doing. Hyperlinks make navigation around the information efficient.
You can right-click on the help display and select Back to go back to a previous point as
required.
If you no longer wish to see the help, you can “collapse” the help screen down using the Help
icon to give you more space on the screen.
Windows layout
To make using the Wizard as efficient as possible, it’s a good idea to make a layout of the
main tools that makes window switching as “click-free” as possible. Layouts may be saved
and loaded using the File > Layout menu.
If you are unfamiliar with how the modules can be moved and docked, and how to save your
layout for future sessions, please refer to the Tutorial provided with the software (found in the
program installation folder doc\Tutorial subfolders).
Generally you will always need to see the Surface and Well module, so ensure these are
docked and visible at all times.

The Reset button
The Reset button is used to remove the Wizard history from the model. Replay files
are deleted and the Run Type column cleared. However, any data in the model generated by
the Wizard is not deleted.
The Create and Looped buttons
The Create button allows the user to create a Workflow from the run files currently used in the
Wizard. The Workflow module can be used to load the workflow (the default workflow name
is Wizard.xml) & run it. You can customise the workflow as required.
Using the Looped toggle option Looped Toggle and the adjacent number field, you can create
a “looped” workflow that randomises the parameters according to the multi-realisation ranges
selected by the user when running the Wizard. his allows a range of models to be generated
(typically 500-1000) using slightly different parameters. The variation in the depth surfaces
(and volumetrics if computed) allow the use to get some understanding of the stability of the
depth conversion and the P90/P50/P10 volumetrics distribution.

Input / Output for VelPAK
Import and Input into VelPAK
General Overview - Input into VelPAK
Binary Model Load
This is a VelPAK Model that has already been loaded and displayed within VelPAK. This is
the best way to save data within VelPAK as all the data are stored in one file.
Kingdom Link Load

A direct link to a Kingdom “.tks” file allowing selected data to be transferred from Kingdom
into a VelPAK binary model.
ASCII Load
Data can be loaded into VelPAK via space delimited ASCII data files. As long as the data are
in the correct order per line, and are separated by gaps, then VelPAK will be able to read it in.
If the data are not already in the VelPAK Generic Format there are two methods available to
the user to re-format the data to read it in. These two methods are by using Scanit or using
Filters.
Scanit
Scanit is a valuable, visual, general purpose data formatting stand-alone tool which allows
you to reformat your data files into any columnar flat file format you require. It is available
from the ‘Tools’ drop-down menu at the top of VelPAK.
Scanit will produce output ASCII files in the correct format for VelPAK which can then be read
into VelPAK via the Input routines.
This is a more modern, visual method of re-formatting data to load into VelPAK.
Filters
Various filters exist to import GeoQuest and Charisma and Landmark ASCII data in to
VelPAK.
If an appropriate FILTER does not exist you can write your own and store it for future use.
This is done in the Filter Tab of the ASCII load window; for details Go Here.
Using a Filter will re-format the input file as it reads the data into VelPAK. This is the older,
more complex version of reading data into VelPAK which relies on the user having some
knowledge of ‘gawk’ - an old unix programming language. Although most users would now
move to Scanit to re-format their files the Filters method has been left in VelPAK so that users
may still use filters previously written.

Input into VelPAK - Binary/Open Project File
VelPAK Binary models are read into VelPAK using the Top Line of VelPAK options: File -->
Open --> Model.
This loads a VelPAK Model that has been previously loaded, displayed and stored within
VelPAK.
Select the FILE option at the top of the VelPAK window and select Open.
A standard Windows File selector will open allowing you to scroll through your directories to
find your VelPAK Binary model.
The default Model File Name is ‘.bin’. If your model name is not named to this convention
change the ‘Files of type’ extension window to show All Files (*.*) to find your model.

Input into VelPAK - via the TKS link
Data can be read in to VelPAK directly from the KINGDOM project via the TKS Link.
Further data can be read in to the VelPAK project from the same or different TKS project at a
later date by simply repeating the process in Replace or Merge mode.
Reading data into a New project or an Existing project

Using a New project to read the data into
If you are intending to use the Link to create a new VelPAK project, rather than Merge or
Replace data into an existing project, you must give your VelPAK project a name before you
proceed with Open TKS by selecting New first.
Go to the directory you wish your VelPAK project area to be stored and give a name to your
VelPAK file area and the actual binary model. This will be populated once data from TKS has
been read in.
Then select the OpenTKS option.
First - Make New Project
Then Open TKS
Using an Existing project to add data to

Select the Name of your VelPAK Project and Bin Model using the Open from the drop-down
menu.

Then select the OpenTKS option.
Select OpenTKS via Merge or Replace

Select File > Open > OpenTKS
If you are opening a new project Merge or Replace will work in the same way.
If you are using Merge or Replace on an already created project it is important to select the
correct mode for Replacement or Merging of the data.
Replace
In replace mode all data of a certain type (e.g. Wells) will be deleted and replaced with the
new selection. If you have 1000 wells in a project and then select one more well in replace
mode, all wells will be deleted and you will be left with th one well you have just selected.
Merge
Merge mode will attempt to merge newly selected data with the data already within the
project. Due to the nature of the different data types Merge will work in different ways
dependent on the data. This is outlined in the table below:
Data Type Merge Action
Event - Fault Appends new data to existing set
Profile Event - Event Appends new data to existing set
Stack Appends new data to existing set

Line If the line exists replace locations
Zval Appends new data to existing set
Surface Fault Appends new data to existing set
Polygon Appends new data to existing set
Grid Always replaces
Location If well exists location is replaced
Tops If well exists tops are cleared first

Well
Curve If well exists curves are cleared first
The OpenTKS Link

The Link takes the form of a number of flowing dialogs guiding you through each type of input
you wish to import.
Full details of the link are on the help pop-ups for each screen of the link.
Types of Data for selection and what you can do with them in VelPAK
Wells
Well locations, sonic logs or time-depth charts and well tops.
Surfaces

Any grids from TKS can be read into VelPAK – most often Time grids but other slots are
available in the VelPAK tree as will be seen. Grids will be re-interpolated and rounded on
transfer to conform to a master lattice, but can be re-sampled if necessary within the
program.
2D Seismic
2D volume slices can be read into VelPAK to produce navigation data in VelPAK for display
as a Surface basemap.
3D Seismic
3D information can be read in to display the extents of any 3D survey selected and will be
displayed on the Surface Map module and can be used within the Volume output for
generation of a new volume.
3D SEGY volumes are used for visual displays within the 3D Visualization module or as a
backdrop in the 2D profile module of VelPAK.
Note: Any transfer of SEGY volumes will take time!
2D Horizon and 3D Horizon

Interpreted picks for display in the Profile module within VelPAK.
Polygons
For use once in VelPAK define required areas of the data surveys. Polygon control is not
used with the Link – data must be selected via polygons or other methods within TKS prior to
transfer.

Output Data and run VelPAK
Once selection has taken place through the Link, pressing Apply will proceed to process the
data to read into VelPAK.
Abort will stop the process if required.
The process will announce when it has finished reading the data in.
Press Exit to close the Link and VelPAK will have the project loaded.
It is recommended that you save the model immediately.

ASCII Input
Data can be initially read into VelPAK via space delimited ASCII data files. As long as the
data are in the correct order per line, and are separated by gaps, the relevant selected input
program within VelPAK will be able to read it in.
Note: If the data are not already in the VelPAK Generic Format there are two methods
available to the user to re-format the data to read it in. These two methods are by
using Scanit or using Filters.

ASCII Data Input - TIPS for loading
a. Data are space delimited; consequently you must not use any spaces in Well Names,
Top Names or Line Names. If you have a Well called, for example, BASE WELL
ONE, this could be specified in the data input file as BASE_WELL_ONE.
b. VelPAK is not easily confused by the format of floating point numbers.
c. Character strings have a character limit; Well Names have a limit of 82 characters,
and Line Name has a 32 character limit.
Deviated wells can be loaded in by varying the X and Y coordinates for the time-depth
curves. If you have no time-depth data for a deviated well, but you want to use the deviation
information and your tops to check your depth conversion, load the file with 0 (zero) in the
time column.

The ASCII Input Process
File Set
Using the File Set option will allow the reading in of external files containing all the data in the
VelPAK project. This will have been produced by the File -> Export -> File Set option.
The data will default to be stored in the ‘export’ directory of the project directory from which
the data was exported. The default directory from importing data is the import directory of the
project directory for your current project but both of these directories can be changed using a
standard File Selector if required.
On selecting File Set and moving to the correct directory where all the data files and the index
file are stored, the index file name needs to be selected, standardly this will be called
“index.txt”. This index file provides the indexing such that these files will be read in and
labeled correctly and swiftly on import.
This means that data can be exported from VelPAK and imported into a new project
seamlessly without having to define each individual data type for import/export.
This process may take some time if there are a lot of data in the project.

Profile Data Input
For the import of Event Horizons, Event Faults and Seismic Stacking Velocity data.
Profile Faults, Profile Events

Horizons and Faults are read in as Time only. When selected, the option will bring up the
window to enter where the Profile data files are stored.
Since profile data are dependent on horizons, it is expected that you will be entering a
data file for each horizon you wish to assign in the project.
Bring up the file selector by pressing the ‘...’ to the right of the input window and move
through the file directories to find your data file to read in.
Select the required filter from the Filter Tab if required. Press OK to load the file.
For details of the Replace/Merge/Ignore option Go Here.

Profile Stack
Stacking data are not loaded per horizon so only one input line is available on the load
page.
Note: The LINE data must be loaded before the stack data are loaded.
Stacking data comes from a variety of sources and it is very likely you will need to re-
format the data using Filters or Scanit to load the data into VelPAK. For further assistance
on this contact your local helpdesk.
Prefix - Lines within VelPAK brought in from elsewhere are prefixed with the Survey
Name. The Prefix option here will add the Survey Name to the Line Name of your
stacking velocity file. The drop down in the Prefix slot will display all Surveys for line
names currently held in the VelPAK project allowing you to select the relevant survey
name.
Surface Data Input

Apart from Surface Location Data, these are data stored under a specific horizon name/
number (but note that this could also be referring to the layer which is above the horizon).
Subsequently on input you will be required to define the horizon Event under which you wish
the data to be stored, as well as the branch slot of the Model Tree where it will be stored.
Type of data categorized under Surface data:
Surface LOCATION DATA
Surface FAULTS
GRIDS
XYZS
POLYGONS

Surface Location Data
Selecting the File -> Import -> Surface Location option will bring up the window to select
where the Surface location data file is stored. Bring up the file selector by pressing the ‘...’
to the right of the input window and move through the file directories to find your data file
to read in.
In-lines (Lines) are prefixed I: .
X-lines (Traces) are prefixed X: .
Random lines are prefixed R: .

Note: The line name recorded in the map data format file must be consistent with the line
names for any Profile horizon data for the data to tie.
VelPAK does not deal with Latitude and Longitudes. If these are in your original data file
they will be ignored.
Surface XYZs, Surface Faults, Surface Polys and Surface Grids
From the slots tab that comes up on selecting which data you are to import, choose from
the list Time, Depth, Velocity, Error, Misc 01...and so on, for the branch slot in the Model
Tree you want the imported data to be stored in.
For example, if you have a Velocity Grid for Event 1 to be imported you will select Import -
> Surface Grid
The Load Event Grid window will be displayed. Select which slot you want the data to go
into from the Slots tab on display.

Move to the Files tab and bring up the file selector by pressing the ‘...’ to the right of the
input window for the horizon you wish to import your grid under, and select the Grid you
wish to import.
Note: For data files you wish to read in relating to an Event horizon within the VelPAK model
you can read in files for each horizon at the same time. Up to 32 horizons can be used
with a single VelPAK model.
When you have selected the file(s) to read in, press OK to load the file. Select the
required filter from the Filter Tab if required.
Once the data are read into VelPAK the Model Tree will be populated accordingly.

See Model Tree for full details of the tree.
Well Data Import
Well Location, Well Top, Well Curve, Well Layer

Selecting the File -> Import -> Well XX option will bring up the relevant window to select
where the specific well data file is stored. Bring up the file selector by pressing the ‘...’ to
the right of the input window and move through the file directories to find your data file to
read in.

Replace/Merge/Ignore
On all the import file load pages, against each input assigned there is the drop-down option to
Replace, Merge or Ignore the particular data file you have selected.
Replace
This is the default which is used when loading in new data or for replacing that already in
the memory model.
Replace will over-write any data in the project that has the same name or identity,
regardless of whether that data in the model has been modified from the original input file.
Merge
This option is used for adding other data into your model.
Merge does not replace or delete the data at all and must be used for separate areas of
data otherwise you will get duplication of data in the model.
Ignore
Ignores or does not load the file.
Data Type Merge Action
Event - Fault Appends new data to existing set
Profile Event - Event Appends new data to existing set
Stack Appends new data to existing set
Line If the line exists replace locations
Zval Appends new data to existing set
Surface Fault Appends new data to existing set
Polygon Appends new data to existing set
Grid Always replaces

Location If well exists location is replaced
Tops If well exists tops are cleared first

Well
Curve If well exists curves are cleared first

VelPAK Generic Format for individual data types imported into VelPAK
Data can be initially read into VelPAK via space delimited ASCII data files. As long as the
data are in the correct order per line, and are separated by gaps, the relevant selected input
program within VelPAK will be able to read it in. If your data are not in VelPAK Generic Format
you will need to use the filters or write a new one to change the format. See Filters for full
details.
Profile Fault Data Generic Format

Data file style expected:
Line Shotpoint Time Seg Type Name
Segment Number - Denotes a single segment; a change of number denotes a new

segment.
Type - 0 = Random, 1 = Inline, 2 = Xline.
Name - Name of fault (Optional).
Profile Event Data Generic Format

Line Shotpoint Time Segment Number Type Segment Name
Segment Number - Denotes a single segment; a change of number denotes a new

segment.
Type - 0 = Random, 1 = Inline, 2 = Xline.
Segment Name - Optional.
Profile Stacking Velocity Data Generic Format
Note: Line Navigation data must be input before the Stacking Velocities are input.
Data file format expected for 2d surveys:
SURVEY SHOT RMS DEPTH AVERAGE X Y ORIGINAL TYPE

NAME POINT TIME VELOCITY [OPTIONAL] VELOCITY [O] [O] VELOCITY CODE
[OPTIONAL] [OPTIONAL] [OPTIONAL]
SurveyName – Survey name (this must match that previously loaded exactly).
Shot Point – Shotpoint in the 2d survey.
Time - Time of stack velocity curve in milliseconds.
RMS-Velocity - Max. Coherency Stacking Velocity (as picked on semblance plot).
Depth – optional column of depths (set to zero if not required).

Average-Velocity – optional column of Average Velocities (if these are provided there is
no requirement to apply the Dix equation to the RMS Velocities).
X/Y - optional XY values.
Original Velocity - optional column for Original/Other velocity.
Type Code - optional column for Type Codes. (These will be allocated internally according
to the columns anyway):
Old(dix) = 0
Average =1
Interval = 2
RMS = 3
Unknown = 4
All optional values should be 0 (zero) if not used.

Data file format expected for 3d surveys:
INLINE CROSSLINE TIME RMS DEPTH AVERAGE X Y OTHER TYPE

VELOCITY [OPTIONAL] VELOCITY [O] [O] VELOCITY CODE
[OPTIONAL] [OPTIONAL] [OPTIONAL]
Inline – the Inline number. If this number is not prefixed with the survey name (e.g.
Galleon:1500), you must select the survey prefix on the ‘File >> Import >> Profile Stack…’
dialog. Go Here further details.
Crossline – the crossline number.
Time - Time of stack velocity curve in milliseconds.
RMS-Velocity - Max. Coherency Stacking Velocity (as picked on semblance plot).
[Depth] – optional column of depths (set to zero if not required).
[Average-Velocity] – optional column of Average Velocities (if these are provided there is
no requirement to apply the Dix equation to the RMS Velocities).
X/Y - optional XY values.
Original Velocity - optional column for Original/Other velocity.
Type Code - optional column for Type Codes - as above.
All optional values should be 0 (zero) if not used.

Surface Location Data Generic Format
LINE SHOTPOINT X Y TYPE
Line - Line Name.

Shotpoint - Shotpoint.
X and Y values are surface UTM co-ordinates or similar.
Type - 2D or 3D inline/cross line; 0 = Random, 1 = Inline, 2 = Xline.
Note: VelPAK does not deal with Latitude and Longitudes. If these are in your original data
file they will be ignored.
Surface XYZ Generic Format

X Y Z

Z - Any required value.
Surface Fault Data Generic Format
X Y Z SEGMENT_NUMBER SEGMENT_NAME
X - X co-ordinate.
Y - Y co-ordinate.

Z - Z depth (not used on input - use 0).
SEGMENT_NUMBER - A number that denotes a single segment; a change of number
denotes a new segment.
SEGMENT_NAME - A name assigned to the surface fault within VelPAK (optional).
Surface Polygon Data Generic Format.
X - X co-ordinate.
Y - Y co-ordinate.
Z - Z depth (not used on input - use 0).
SEGMENT_NAME - The name of the polygon (optional). If the data is from a TKS project
this will be the name as allocated in that project.
Surface Grid Data Generic Format

CPS1 GRID NAME
Grid in CPS1.sav (MAPS15) binary format.
Note: This option will only accept ‘Unix’ CPS1 Binary formats (not ‘PC’ based). This option
will accept grids previously output from software packages VelPAK and Cubit.
Well Location Data Generic Format

Well Location should be loaded first in the WELL group.
WELLNAME: UWI : BOREHOLE X Y
WELLNAME :UWI : BOREHOLE - is a character string -with no spaces- identifying the

well; the UWI (Unique Well Identifier) and Borehole must be separated by a colon. If no
UWI or Borehole is within the data file the program will read in just the Well Name. The
user can choose what part of this Well Name string they wish to have displayed once the
wells are read into VelPAK using the Well Preferences.
WELLNAME is a common key and must be consistent when used in reading in other data
types from the WELL group.
Well Formation Top Data Generic Format

WELLNAME TOPNAME Z
WELLNAME is a character string -with no spaces- identifying the well

TOPNAME is the geological name of the horizon.
Z is the measured depth to the formation marker from the seismic reference datum.

Well Curve Data Generic Format
WELL X Y CALIBRATED DEPT UNCALIBRATED TDC or CURVE

NAME TIME H TIME UNC or NAME
DEV
WELL NAME is a character string -with no spaces- identifying the well.

X and Y are the co-ordinate at the particular depth. Obviously for a straight hole the
surface location will be repeated throughout the file.
For a deviated hole the X and Y value must be correct and are taken into account in the
VelPAK process.
CALIBRATED TIME - this column must be set to zero if values are not calibrated.
CALIBRATED TIME and DEPTH can be obtained from a variety of sources:
• Calibrated Sonic Log
• Check shots
• VSP
• Time/Depth pairs from Well Tops
Given due respect to relative data quality, then data can be successfully mixed, even to
the point of extending a partly complete log with tops data from a well database.
UNCALIBRATED TIME - (optional but note this column must be set to zero if values are
not calibrated.) Time that results from intergrating an uncalibrated sonic log. It should be
treated with caution as it is the time that is relative to the start of the logging and should
not be regarded as an absolute value.
TDC or UNC or DEV - an entry must be put in this column stating whether the values in
this file relate to Time Depth Curves, Uncalibrated times or whether this file is a Deviation
Value file with no times within it, just X, Ys and depth.
Note: If the file is a Deviation file then the Time slots must be INDT and not zero values.
Note: HORIZONTAL DRILLED wells must be entered as deviated wells with DEV in the
appropriate column. This format allows for reversal of time and/or depth within the
data file.
Well Layer Data Generic Format

WELLNAME DEPTH TOP DEPTH BASE
WELLNAME is a character string -with no spaces- identifying the well.

DEPTH TOP - Depth to top of layer to be studied.
DEPTH BASE - Depth to base of layer to be studied.

Export and Output from VelPAK

General Overview - Export from VelPAK
Binary Save Model
The VelPAK binary save model is an internal format that cannot be used within any other
packages. However, it is the simplest way of saving your data while working within VelPAK.
This method of save allows you to quickly read the data back into your VelPAK memory
model.
ASCII Export
There are a number of ASCII formats available to output data from VelPAK.
The EXPORT options are laid out in the same form as all data are stored and viewed within
VelPAK, and are therefore split into Profile, Surface, Well and Curve types of export.
Output from VelPAK

Binary/Save Project File
The Save and Save As options from the drop down are only used to save a binary VelPAK
model.
All other forms of output are accessed via the EXPORT drop down option.
The VelPAK binary save model is an internal format that cannot be used within any other
packages. However, it is the simplest way of saving your data while working within VelPAK.
This method of save allows you to quickly read the data back into your VelPAK memory
model.
Save
The Save Option will save the model as the file name that has previously been assigned
to the model. No warning message will come up to warn you that you are saving the
model over the previously saved file. If no file name has been assigned to the model yet,
the following message will appear.

Use the Save As option to assign the name.

Save As
Used to initially name the Binary model or to name the file as another file name. A
standard Windows File Save window will appear allowing you to navigate to the directory
you wish to save your model in.
The default is to assign the extension ‘.bin’ to the model name.
Kingdom Link Output

Pseudo-wells (with tops) and Grids can be read back into TKS from VelPAK.
Use the check boxes to select or deselect the data required to be read in to TKS.
If pseudo-wells are being read back in a Pseudo-Well Unit of mt/s or ft/s will have to be
selected.
Within TKS the pseudo-wells will provide a well location, a set of tops, a well log and time-
depth chart for each well that can be used within the Dynamic Depth Conversion routines of
TKS. All this information for one pseudo-well will be assigned the name ‘Velpak’ and a
number unique to the information for this one well, for ease of differentiation and grouping
within TKS.
When selection has happened, press Apply to transfer the data into TKS.
Note: The TKS project will need to be restarted for the data to be seen in it,

ASCII Output
The EXPORT options are laid out in the same form as all data are stored and viewed within
VelPAK, and are therefore split into Profile, Surface, Well and Curve types of export.
The ASCII Export Process:

Common Procedures for Output all data types
File Set
Using the File Set option will produce external indexed data files all the data in the VelPAK
project.
The process produces a series of data files for all the different data types within VelPAK.
Along with these there will be an Index.txt file which provides the indexing such that these
files will be read in and labelled correctly on import.
The data will default to be stored in the ‘export’ directory of the project directory from which
the data was exported. This directory can be changed using a standard File Selector if
required.
This means that data can be exported from VelPAK and imported into a new project
seamlessly and swiftly without having to define each individual data type for import/export.
On selecting File Set an index file a name needs to be assigned, standardly “index.txt”. This
is the file that will then be selected on Import into another VelPAK project.
This process may take some time if there is a lot of data in the project.

Export of Individual Data

On selecting the type of data you wish to export from VelPAK a Save dialog will come up.
Firstly you will need to select which slot (from the Model Tree) you want to export.
If the data type you are exporting is linked to an Event, the Files dialog will have a number of
event horizon slots listed on the page allowing you to export the data against each Event
within the project.
Bring up the file selector by pressing the ‘...’ to the right of the export window and move
through the file directories to where you want your data file to go.
Select the required filter from the Filter Tab if required.

SAVE/IGNORE
Selecting IGNORE allows you to retain the save file name information in the slots, but to
ignore the output of data to these files.
Press OK to save the file.
Note: If you want your data exported in something other than the generic format for the
output you have specified you will need to use the filters provided under the Filter Tab

or write a new one to change the format. See Filters for full details. Alternatively you
can output the data in VelPAK generic format and edit the output file to the format you
require by using Scanit from the Tools drop-down menu.
Profile Data Output

For the export of Event Horizons, Event Faults and Seismic Stacking Velocity data.
Profile Faults
Faults can be output as Time, Velocity or Depth.
Use Filters to output data in a format other than VelPAK generic format.
Fault Data Format

Data file style output:
X - X co-ordinate
Y - Y co-ordinate
Z - Z depth
SEGMENT_NAME - The name assigned to the surface fault within VelPAK.
Profile Events
Note: There are three types of Profile Event output available from the drop-down menu; this
is just one of them. The other two are Profile XYZ and Profile Cont. These output the
profile data in certain different ways to the Profile Event option. For details of the
styles of output and which one may be more suitable for you go to the relevant
sections.
Outputs the data in a VelPAK generic format The data does NOT need to be snapped to
output it in this form.
One purpose of this is to be the inverse of the input; you would use this format to dump
your VelPAK model in ASCII and re-input.
However, it is also possible to use Filters with this export method so that data are
exported in a different format. Alternatively you can output the data in VelPAK generic
format and edit the output file to the format you require by using Scanit.
Horizons can be output as Time, Velocity or Depth When one of these is selected, a
window will come up to enter where you wish the data files to go.
Since profile data are dependent on events, it is expected that you will be enter an output
data file for each event you wish to export.

Form of Profile Events output

This format with or without a filter, will output each event. It does not follow the layer that the
event has been snapped to.
For example, the snapping process within VelPAK causes an event pierced by another event
to track the layer over the piercement:
Unsnapped Profile
Snapped Profile
However, VelPAK generic format will output the real event data. So that in the above
example, just the data for:
and
will be output as two separate files, according to the original event data.
Overhanging events..:

..will have the data output continuously along the event, so that there is a possibility that one
shotpoint could have multiple Z values. Therefore this output is not appropriate for
GRIDDING techniques. (Use XYZ output for Gridding.)
Type in the names you want as your output files.
Note: On the Event output you can press the widget SAVE/IGNORE so that you can select
which events you wish to output out of all the events in your model.
Select the directory you wish the data files to go into, and select a filter if required.

Profile Data Format: Standard generic output
Line Shotpoi Time/ Segment Typ Segment X Y

Name nt Velocity Number e Name
/
Depth
EW-001 177 224 0 0 R/EW-001/1/ 478918.4 6145025.

0 1 5
EW-001 190 221 0 0 R/EW-001/1/ 479259 6145024

0
EW-001 202 231 0 0 R/EW-001/1/ 479579.8 6145029

0 1
EW-001 212 225 0 0 R/EW-001/1/ 479847 6145027.

0 5
EW-001 224 225 0 0 R/EW-001/1/ 480161.8 6145025.

0 1 5
EW-001 237 226 0 0 R/EW-001/1/ 480513.0 6145024.

0 9 5
EW-001 250 224 0 0 R/EW-001/1/ 480865 6145023

0
EW-001 263 221 0 0 R/EW-001/1/ 481207 6145021.

0 5
EW-001 279 214 0 0 R/EW-001/1/ 481629.3 6145019

0 1
EW-001 292 209 0 0 R/EW-001/1/ 481974.8 6145018

0 1
EW-001 307 207 0 0 R/EW-001/1/ 482376.9 6145016.

0 1 5
EW-001 321 203 0 0 R/EW-001/1/ 482750.9 6145009

0 1
EW-001 338 204 0 0 R/EW-001/1/ 483206.5 6145007

0 9
Profile XYZ
This produces an XYZ file in either Time, Velocity or Depth, that allows a VelPAK model to be
read into any suitable software package that can read in ASCII files.

This format is detailed here.

Use the Filter Tab on output to provide the option of writing Awk filters to produce custom
output.
Note: Your data must be successfully snapped for this output style to work.
Form of Profile XYZ output

The XYZ file will contain the line name, the X coordinate, the Y coordinate, and the Z
value(s), which can either be Time, Velocity or Depth, depending on your choice.
A separate file is produced for each event. Every event within the memory model will be
output.
The fault file will not be touched in any way: any flags that have been marked on the section
will also be output as part of the XYZ file format.
The output can accommodate multiple Z-values for any one horizon at any one shotpoint.
This considers the over-thrusting of horizon data that can occur - as shown in the examples
below:
Time 1
Time 2
Time 3
Time 1
In a six Z situation (multiple over-thrusting) - below - the following result will be seen: Time 1
will start again as soon as it can, in order to produce one continuous layer that can be read
into a Mapping package (such as Equipoise Software’s XGEO) and displayed on a scaled,
posted map.

Time 1
Time 2
Time 3
Time 1
Time 2
Time 3
Time 1
The FLAG field in the data file will can be defined as follows:
FUR
FU
FL FLR
T
P
Within the XYZ file, the MASK value is particularly interesting as it represents the geological
situation. This can be of great benefit to advanced computer mappers.
For full details of the MASK value Go Here.
At a Glance: Diagrams to show XYZ output format

XYZ output on a situation like this....:

.. will output data for this continuous layer ....:
... and this continuous layer.
For an overhanging structure:
the following will be output.

Z1 value
Z2 value
Z3 value
Z1 value
Profile Data Format: XYZ
Masks/
Line Shot Segme
X Y Z1 Z2 Z3 Event
Name point Name
No.
EW-001 499225.91 6144965.50 939.00 345 1e+30 1e+30 4 1 2 R/EW-00
2/0
EW-001 499674.41 6144962.50 956.00 335 1e+30 1e+30 4 0 2 R/EW-00
2/0
EW-001 499836.41 6144958.00 962.00 338 1e+30 1e+30 4 0 2 R/EW-00
2/0
EW-001 499989.56 6144952.50 967.63 368.233 1e+30 1e+30 4 1 2 R/EW-00
2/0
Field Field
Number Name
1 LINE NAME
2 X
3 Y
4 SHOTPOINT
5 Z1

Field Field
Number Name
6 FLAG
7 Z2
8 FLAG
9 Z3
10 FLAG
11 MASK
12 MASK2
13 EVENT NUMBER
14 SEGMENT NAME
FORTRAN FORMAT - X, Y, Z
(A16, 3(1X, F10.2), 3(1X, F10.0, 1X, A4), 2(1X,Z8), 1X, I2, 1X, A32)
Indeterminate Z value = 1.0E+30
Profile Conts
This produces an XYZ file that will not split up the horizons or events when encountering
reversal zones. The continuous output file produced is not suitable for most mapping
packages, it’s primary use is for volume modelling.
This format is detailed here.
output.
Form of Profile Conts output

The continuous output file produced will contain the line name, the X coordinate, the Y
coordinate, and all three Z values Time, Depth or Velocity.
This file will also output the VUP and VDOWN (where V stands for velocity) values if
calculated via VelPAK’s Depth Conversion routines. The Vup/Vdown theory section.
A separate file is produced for each event. Every event within the memory model will be
output.
Faults are not dealt with separately: any flags that have been marked on the section will also
be output as part of the continuous output file format as for the XYZ file.

If the segment name has been included on input it will also be output.
The output file produced consists of only one value for X,Y and Z in all circumstances.
The continuous output option

will produce a file with only
Time 1 one Z value, in an
circumstance.
Time 1
Time 1
Time 1
For example, the overthrust illustrated above would produce a file with three Z values
(Z1,Z2,Z3) if output as an XYZ file but only one Z value if output as a continuous output file.
The Continuous file produced contains FLAG’s and MASK values as described for the XYZ
output.
For full details of the MASK value Go Here
At a Glance: Diagrams to show CONTinuous output format

A situation like this....:
.. will output data for this continuous layer....:

... and this continuous layer.

Note that CONTINUOUS OUTPUT will

output overhanging data in one file so that in
a situation like this it is likely that you will
have multiple Z values for one shotpoint.
Profile Data Format: Continuous
Line Segment
X Y Shotpoint Time Velocity Depth Vup/Vdown / Flag/Masks/
Name Name
Event Number
EW-001 478918.41 6145025.50 177.00 801.5 2730 954.047 1e+30 1e+30 4 0 2 R/EW-001/2
EW-001 479180.41 6145024.50 187.00 809 2730 965.727 1e+30 1e+30 4 0 2 R/EW-001/2
EW-001 479392.50 6145026.50 195.00 821 2730 979.936 1e+30 1e+30 4 0 2 R/EW-001/2
EW-001 479633.59 6145028.50 204.00 832 2730 992.055 1e+30 1e+30 4 0 2 R/EW-001/2
EW-001 479977.00 6145026.50 217.00 829 2730 990.96 1e+30 1e+30 4 0 2 R/EW-001/2
EW-001 480295.31 6145025.00 229.00 835 2730 998.91 1e+30 1e+30 4 0 2 R/EW-001/2
EW-001 480622.00 6145024.00 241.00 846 2730 1013.92 1e+30 1e+30 4 0 2 R/EW-001/2
Field Field
Number Name
1 LINE NAME
2 X
3 Y
4 SHOTPOINT
5 TIME
6 VELOCITY

Field Field
Number Name
7 DEPTH
8 VUP
9 VDOWN
10 FLAG
11 MASK
12 MASK2
13 EVENT NUMBER
14 SEGMENT NAME
FORTRAN FORMAT - CONTINUOUS

(A16, 3(1x, F10.2), 5(1X, F10.0), 1X, A4, 2(1X, Z8), 1X, I2, 1X, A32)
Profile Stack
Outputs the data in a VelPAK GENERIC FORMAT style.
output. Alternatively you can output the data in VelPAK generic format and edit the output
file to the format you require by using Scanit.
Example of STACK DATA file output for this case:

Profile Stack Data Format
Line Shot Original

Time Velocity Depth AVel X Y Type
Name Point Velocity
1021 1238 0.0000 1843.199951 0.000000 1920.000 11491800.00 3261950.00 1e+30 0
1021 1238 100.0000 1843.199951 92.160004 1920.000 11491800.00 3261950.00 1e+30 0
1021 1238 130.0000 2041.688354 132.709747 2160.000 11491800.00 3261950.00 1e+30 0
1021 1238 170.0000 2155.924072 183.253540 2280.000 11491800.00 3261950.00 1e+30 0
1021 1238 210.0000 2208.175781 231.858459 2330.000 11491800.00 3261950.00 1e+30 0
1021 1238 450.0000 2568.179199 577.840332 2710.000 11491800.00 3261950.00 1e+30 0
1021 1238 640.0000 2670.361816 854.515747 2810.000 11491800.00 3261950.00 1e+30 0
1021 1238 900.0000 2889.761475 1300.392578 3050.000 11491800.00 3261950.00 1e+30 0
1021 1238 1210.0000 3245.625732 1963.603516 3498.000 11491800.00 3261950.00 1e+30 0
1021 1238 1250.0000 3289.496338 2055.935059 3550.000 11491800.00 3261950.00 1e+30 0
Surface Data Output
Surface Location data

The method used to output your navigation data. This is in standard UKOOA format
according to the UKOOA procedure guide 1978-P1-84.
Note: No filters are available through this option to save the data in any other format than
the one stated above.
Surface XYZ, Fault, Poly Grid data
Note: Only XYZ Export gives you the option to export values using a filter. The filters
available for XYZ output are for 2DI and EarthVison formats.
Grid Data
Saves the internal grids generated in VelPAK as an external CPS1 Maps 15 format grid.
If you wished to use your internal grid in another package as another style of grid other
than CPS1, the recommended course of action would be to turn the grid values into XYZs
from the Model tree, and output the XYZ data file for use in another package. See Model
Tree for full details of how to do this.
From the File Export Surface data drop down menu choose from the list Time, Depth,
Velocity, Error, Misc 01...and so on, for the branch slot in the Model Tree where your data to
be exported is sitting.

For example, if you want to export a Surface Velocity Grid for Event 1 you will select Export -
> Surface Grid
The Save Event Grid - Velocity window will be displayed on the Slots tab; select which
allows you to select which grid slot you want to export; in this case you would select the
Interval Velocity slot.
Then select the FIles tab and select where you want the files to be stored; bring up the file
selector by pressing the ‘...’ to the right of the export window to give an output file name to
the grid to be output for that event from the Model Tree (in this example stored within the
velocity slot for that particular event).


SAVE/IGNORE
Well Location, Top, Curve, Layer, Seismic Data Output
Note: There are no pre-defined filters available for Well data output.
From the File Export Well data drop down menu choose the type of Well data you wish to
output.

The relevant Save Well window will be displayed. Bring up the file selector by pressing
the ‘...’ to the right of the export window to give an output file name.
SAVE/IGNORE
For details of the Filters tab and option that is used to change VelPAK generic format into
output ASCII files of varying formats Go Here. Alternatively you can output the data in
VelPAK generic format and edit the output file to the format you require by using Scanit.
Well Location Data Format
WELLNAME X Y

Well Tops Data Format
WELLNAME TOPNAME Z

TOPNAME is the geological name of the horizon.
Z is the depth to the horizon.

Well Curve Data Format
WELL X Y TIME DEPTH UNCALIBRATED VINST VAVG LAYER

NAME TIME NUMBER

X and Y are the co-ordinate at the particular depth. For a straight hole the surface location
will be repeated throughout the file.
UNCALIBRATED TIME -time that results from intergrating an uncalibrated sonic log. [It
should be treated with caution as it is the time that is relative to the start of the logging
and should not be regarded as an absolute value.]
VINST - is the instantaneous velocity (sonic log value) at each sample.
VAVG - is the average velocity from surface.
LAYER NUMBER - The number of the layer that the curve point falls within.
Well Layer Data Format
WELLNAME DEPTH TOP DEPTH BASE

DEPTH TOP - Depth to top of layer.
DEPTH BASE - Depth to base of layer.
Well Seismic Data Format

A special, non-flat ‘hierarchical’ file originally designed to link with the software ‘DepWiz’
but can be useful for transfer of information elsewhere.
It takes the values of the time-depth curve and presents the values of the grids for each
point along the time-depth curve. (The file can thus be very large.)
Note: Grids need to be in the TIME SLOT of the Model Tree for appropriate event for them
to be read.
Also note that Layers need to be defined in your model for this to work.
On deviated wells the values will be taken as shown in the diagram below.

x x Top Winterton
Time-depth curve x x x
lies on curve; layer
will be labelled in
x
output file.
x x
x x x Rot Halite
No layer for
time-depth
curve; marked as x
‘NONE’
x
x x x x
Brockelschiefer
Time-depth curve values on well

x Interpolated values of grid from time-depth XY value
% ---% Well Curve for 'curve' in Well Seismic Format

% -------------------------------------------------------
%Input Well Curve data
%3 Number of Layers to be listed
% Top Winterton
% Rot Halite
Event Name
% Brockelschiefer
% 41/99A-1, 605716, 5939590, 0, 0, 0,TOP_OF_WELL,3
% 1, 749.69
Value of Grid at this point
% 2, 1178.6
% 3, 1462.3
% 41/99A-1, 605716, 5939590, 43.431568, 53.029999, 0,NONE,3
% 1, 759.6
% 2, 1176.2
% 3, 1502.3
% 41/99A-1, 605716, 5939590, 122.431568, 133.029999, 1,Top_Winterton,3
% 1, 854.6
WellName, X, Y, Time, Depth, Layer Number, TopName, No. of Layers
% 2, 1472.2
NB TopName can be ‘NONE’ if track falls between tops
% 3, 1905.3

Scanit - a Stand-Alone Tool for re-formatting ASCII data

Scanit is a stand-alone Tool available from the ‘Tools’ drop down menu at the top of the
VelPAK main screen. There is a separate manual for it outlining its comprehensive features
and going through some examples of data re-formatting. An on-line help system is available
from the Help drop down within Scanit and the .PDF of the manual with examples is available
in the VelPAK local documentation area.
Scanit is a valuable, visual, general purpose data formatting tool which allows you to reformat
your data files into any columnar flat file format you require.
The input and output files are seen on screen together with a Pattern Window above the
Input Window and a Middle Window for extraction of subsets from the original file.
Typically, users would use the Pattern Window as the means of extracting required data from
the Input Window as a subset of data to be placed in the Middle Window. This subset would
be displaying the data in a way that allowed the extraction of columns of data to be processed
and displayed in the bottom Output Window.
Once the output file has been created to the satisfaction of the user, a template of the actions
just used on screen to produce the required format can be saved for future use.
Overview of Scanit Features

• General purpose re-formatter typically used within VelPAK to re-format Stacking
Velocity data which comes in many different formats to the simple format required for
VelPAK Stacking Velocity Input.
• Can be used to re-format any text file into any format columnar output file.

• Users can build up a paint-box of color-coded actions in the Pattern Window to be

able to extract the required fields of information from the input data file from even the
most complicated input files.
• Detection of errors in specifying field-widths: Auto-field expansion detects a field width
increasing to more columns than has been originally selected and alerts the user of
whether they wish to increase the field width or not.
• Use of colors to highlight which fields have been selected.
• Ability to ‘Unwrap’ rows of data (in pairs or otherwise) and place them into columns.
This is a common occurrence in Velocity data files.

Filters: Reformatting data imported to and exported from VelPAK
Filters: Reformatting data imported to and exported from

VelPAK
The Filters Tab on the Input and Output File Selector window is a valuable and powerful
function used to create filters to allow all sorts of ASCII data files to be reformatted and read
in to/out of VelPAK
Using the Filter Tab is an older, more complex version of reading data into VelPAK which
relies on the user having some knowledge of ‘gawk’ - an old unix programming language.
Although most users would now move to Scanit to re-format their files the Filters method has
been left in VelPAK so that users may still use filters previously written, both for input and
output of data from VelPAK.
For example, ASCII horizon data read out GeoQuest in their M7 2D format can be passed
through the relevant filter in VelPAK and turned into the correct VelPAK generic format to be
read into VelPAK. This is shown in the example dialog above.
For a list of all the Filters provided with the VelPAK refer to the end of this chapter, Go Here.
Using Predefined Filters in the Filters Tab

Note: When selecting from the list of available Filters, only the ones available for the type of
data you are trying to load/output will be displayed. If no filter is available for the type
of data you are reading in or outputting, then the entire Filter selection drop down will
be BLANK.
‘NONE’ means no filter has been selected from the available list yet.
1. Select the Files you wish to read in /read out of VelPAK on the Files Tab.
See ASCII Input Process and ASCII Export for details.
2. Select the Filters Tab.

3. Select the Filter you wish to use for the data from the Filter drop-down.
Use the down arrow () to select from available inputs.
Double click to bring it into the filters window.
4. The Filters code will be displayed in the Filters window. Press OK to run the files through
the filters selected either into VelPAK or out of it.

Using the Filters Tab to write your own Filter

Note: You can resize the Filters window to a more convenient size for writing a filter,
however this may take some time if a very large data file is already loaded in it.
1. You can either write your own filter or, to modify a ready made filter, select the Filter you
wish to modify for the data from the Filter drop-down.
2. Refer to Writing your Filter for details of the language used to write the filters.
3. Load your input file to test the filter you have written by selecting the LOAD option next to
the Input window. A File Select window will come up allowing you to move to the directory
where your data are stored and select the relevant file.
4. Press TEST to test the filter you have written against the data you have loaded into the
Input window. In the output window it will either show you the file as it appears having
been passed through the filter you have written, or else you will see an error from with the
filter.
5. If you are happy with the output from the filter you have written, use Save As to save the
filter with a suitable file name in the specific filter’s directory for the data you have written
the filter for.
6. You can then use this new filter as the selected filter on this tab for when you go back to
the Files Tab to select the data files you wish to read in/ read out using the new filter.

Writing your Filter - the Language

All VelPAK filters are written in ‘gawk’.
Gawk is a derivative of the ‘Awk’ UNIX command. Both Gawk and Awk derive their names
from its creators Aho, Weinberger, and Kernighan: the G for Gawk comes from ‘Gnu”!. Both
Awk and Gawk are standard unix commands.
Gawk is a simple programming language that permits easy manipulation of structured data
and the generation of a formatted report. The VelPAK filters facility has packaged the gawk
language into a friendly user interfaced environment and provides libraries and ready made
filters.
Gawk is a very powerful tool. The complexities of it cannot be covered in a manual such as
this.
The manual is available on line from the Gnu organization here: http://www.gnu.org/software/
gawk/manual. You are also referred to the book: ‘Sed & Awk’ by Dale Dougherty, published
by O’Reilly & Associates, Inc. (103 Morris St., Suite A, Sebastopol, CA 95472).
Note: Any user of the VelPAK filters Gawk routines are reminded of the Gnu General Public
License Terms and Conditions of use.
Filter Libraries
Supplied with VelPAK filters are several gawk library routines which will be of use to anyone
creating their own filters or for those just trying to understand the filters supplied. The library
routines are located in the following file:
$TOPIXDIR/filters/LIBRARY
Routines to note are:
• CHRLENReturns the length of a character string without trailing spaces.
• CHRLEFTReturns the character string minus the leading blanks.
• CHRFILLReplaces blanks in a character string with underscores.
• CHRUNFILLReplaces underscores in a character string with blanks.
• ABSGives the absolute value.
• INDIRECTPerforms a process prior to the filter execution.
For details of all the functions see the LIBRARY file.

Filters supplied with VelPAK

LOAD:
Profile Event Data
Profile Fault Data
Well Time-Depth Data (Curve)
Navigation Data (Line)
Polygon Data (Poly)
Stacking Velocity Data (Stack)
Grid Data
SAVE
Profile Event Data
Profile Fault Data
Cont Data
Grid_Data

LOAD - Filters For Profile Event Data
DATA
FILTER NAME DESCRIPTION
TYPE
EVENT GEOQUEST_M7_2D Load GeoQuest M7 2D Event

Data
GEOQUEST_M7_3D Load GeoQuest M7 3D Event

Data
LANDMARK_2D_DEFAULT Load Landmark 2D Event Data
LANDMARK_3D_INLINE_DEFAULT Load Landmark 3D Inline Event

Data
LANDMARK_3D_XLINE_DEFAULT Load Landmark 2D Xline Event

Data
LOAD - Filters For Profile Fault Data
DATA
TYPE
FAULT GEOQUEST_M7_2D Load Geoquest 2D Fault Data
GEOQUEST_M7_3D Load Geoquest 3D Fault Data
LOAD - Filters For Well Time-depth Data (CURVE)
DATA
TYPE
CURVE TD_CURVE_CALIBRATED Turns old ‘VelPAK’ format curve files and turns
them into the correct format for VelPAK.
TD_CURVE_DEVIATED_ONLY Sets the Deviated column to DEV to read in

deviated data
TD_CURVE_UNCALIBRATED Sets the Uncalibrated column to UNC to read

in Uncalibrated data

LOAD - Filters For Navigation Data (LINE)
DATA
TYPE
LINE UKOOA_2D_P1-84 Loads UKOOA 2D navigation format (P1-84)
UKOOA_2D_P1-90 Loads UKOOA 2D navigation format (P1-90)
LOAD - Filters For Polygon Data (POLY)
DATA
TYPE
POLY LOAD ALL POLYS
This polygon filter would not tend to be used by the user in the Filter Tab of the Input Polygon
routine. This is the awk script that is used within the TKS Link to use Polygons (previously
defined in TKS) to draw in specific Well information into VelPAK. Go Here for information
about this in the TKS link.
LOAD - Filters For Stacking Velocity Data (STACK)
DATA
TYPE
STACK VARIOUS EXAMPLES for Stack Descriptions within the Filter file
Column data
VARIOUS EXAMPLES for Stack Descriptions within the Filter file

Multi Value data
A number of filters exist for the many varied formats of Stacking Velocities. Please look at the
different examples give if required.
It is recommended however that Scanit should be usually used to re-format Stacking Velocity
data.

LOAD - Filters to load Grids
Data
Filter Name Use
Type
GRID Grid_Zmap_to_Cps1 Imports ZMAP format grids to

VelPAK (CPS1 format)

SAVE - Filters For Profile Event Data
Data
Filter Name Use
Type
EVENT GEOQUEST_M7_2D_3D Save Geoquest 2D / 3D Event

Data
SAVE - Filters For Profile Fault Data
Data
Filter Name Use
Type
FAULT GEOQUEST_M7_2D_3D Save Geoquest 2D / 3D Fault

Data
SAVE - Filter For Cont Data
Data
Filter Name Use
Type
CONT Profile_Cont_to_TKS_CUL
Profile_Cont_to_TKS_CUL_PLUS_DEPTH_N
O_F
Profile_Cont_to_TKS_LINE TRACE TIME
Profile_Cont_to_TKS_LINE TRACE XY TIME
SAVE - Grid Data
Data
Filter Name Use
Type
GRID GRID_CPS1_TO_ZMAP Exports VelPAK grids (CPS1

format) to ZMAP format

GNU GENERAL PUBLIC LICENSE

Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it
is not allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By
contrast, the GNU General Public License is intended to guarantee your freedom to share and change
free software -to make sure the software is free for all its users. This General Public License applies to
most of the Free Software Foundation’s software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by the GNU Library General
Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses
are designed to make sure that you have the freedom to distribute copies of free software (and charge
for this service if you wish), that you receive source code or can get it if you want it, that you can
change the software or use pieces of it in new free programs; and that you know you can do these
things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to
ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the
recipients all the rights that you have. You must make sure that they, too, receive or can get the source
code. And you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which
gives you legal permission to copy, distribute and/or modify the software.
Also, for each author’s protection and ours, we want to make certain that everyone understands that
there is no warranty for this free software. If the software is modified by someone else and passed on,
we want its recipients to know that what they have is not the original, so that any problems introduced
by others will not reflect on the original authors’ reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger
that redistributors of a free program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any patent must be licensed for
everyone’s free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION
AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright
holder saying it may be distributed under the terms of this General Public License. The “Program”,
below, refers to any such program or work, and a “work based on the Program” means either the
Program or any derivative work under copyright law: that is to say, a work containing the Program or a
portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter,
translation is included without limitation in the term “modification”.) Each licensee is addressed as
“you”.
Activities other than copying, distribution and modification are not covered by this License; they are
outside its scope. The act of running the Program is not restricted, and the output from the Program is

covered only if its contents constitute a work based on the Program (independent of having been made
by running the Program). Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program’s source code as you receive it, in any
medium, provided that you conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to
the absence of any warranty; and give any other recipients of the Program a copy of this License along
with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer
warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based
on the Program, and copy and distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices stating that you changed the files and
the date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is
derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties
under the terms of this License.
c) If the modified program normally reads commands interactively when run, you must cause it, when
started running for such interactive use in the most ordinary way, to print or display an announcement
including an appropriate copyright notice and a notice that there is no warranty (or else, saying that
you provide a warranty) and that users may redistribute the program under these conditions, and
telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on the Program is not required to
print an announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not
derived from the Program, and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those sections when you distribute them
as separate works. But when you distribute the same sections as part of a whole which is a work
based on the Program, the distribution of the whole must be on the terms of this License, whose
permissions for other licensees extend to the entire whole, and thus to each and every part regardless
of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by
you; rather, the intent is to exercise the right to control the distribution of derivative or collective works
based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a
work based on the Program) on a volume of a storage or distribution medium does not bring the other
work under the scope of this License.
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or
executable form under the terms of Sections 1 and 2 above provided that you also do one of the
following:
a) Accompany it with the complete corresponding machine-readable source code, which must be
distributed under the terms of Sections 1 and 2 above on a medium customarily used for software
interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge
no more than your cost of physically performing source distribution, a complete machine-readable
copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on
a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source
code. (This alternative is allowed only for noncommercial distribution and only if you received the
program in object code or executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an
executable work, complete source code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to control compilation and installation of the
executable. However, as a special exception, the source code distributed need not include anything
that is normally distributed (in either source or binary form) with the major components (compiler,
kernel, and so on) of the operating system on which the executable runs, unless that component itself
accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated place,
then offering equivalent access to copy the source code from the same place counts as distribution of
the source code, even though third parties are not compelled to copy the source along with the object
code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided
under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void,
and will automatically terminate your rights under this License. However, parties who have received
copies, or rights, from you under this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else
grants you permission to modify or distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program
(or any work based on the Program), you indicate your acceptance of this License to do so, and all its
terms and conditions for copying, distributing or modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient
automatically receives a license from the original licensor to copy, distribute or modify the Program
subject to these terms and conditions. You may not impose any further restrictions on the recipients’
exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties
to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason
(not limited to patent issues), conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of
this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License
and any other pertinent obligations, then as a consequence you may not distribute the Program at all.
For example, if a patent license would not permit royalty-free redistribution of the Program by all those
who receive copies directly or indirectly through you, then the only way you could satisfy both it and
this License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the
balance of the section is intended to apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims
or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of
the free software distribution system, which is implemented by public license practices. Many people
have made generous contributions to the wide range of software distributed through that system in
reliance on consistent application of that system; it is up to the author/donor to decide if he or she is
willing to distribute software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of
this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by
copyrighted interfaces, the original copyright holder who places the Program under this License may
add an explicit geographical distribution limitation excluding those countries, so that distribution is
permitted only in or among countries not thus excluded. In such case, this License incorporates the
limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public
License from time to time. Such new versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of
this License which applies to it and “any later version”, you have the option of following the terms and
conditions either of that version or of any later version published by the Free Software Foundation. If
the Program does not specify a version number of this License, you may choose any version ever
published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution
conditions are different, write to the author to ask for permission. For software which is copyrighted by
the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions
for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of
our free software and of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR
THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO
THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO
LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU
OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best
way to achieve this is to make it free software which everyone can redistribute and change under
these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each
source file to most effectively convey the exclusion of warranty; and each file should have at least the
“copyright” line and a pointer to where the full notice is found.
<one line to give the program’s name and a brief idea of what it does.> Copyright (C) 19yy <name of
author>

This program is free software; you can redistribute it and/or modify it under the terms of the GNU
General Public License as published by the Free Software Foundation; either version 2 of the License,
or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without
even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See
the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not,
write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY
NO WARRANTY; for details type `show w’. This is free software, and you are welcome to redistribute it
under certain conditions; type `show c’ for details.
The hypothetical commands `show w’ and `show c’ should show the appropriate parts of the General
Public License. Of course, the commands you use may be called something other than `show w’ and
`show c’; they could even be mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your school, if any, to sign a
“copyright disclaimer” for the program, if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision’ (which makes
passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989 Ty Coon, President of Vice
This General Public License does not permit incorporating your program into proprietary programs. If
your program is a subroutine library, you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use the GNU Library General Public License
instead of this License.36

Layer Tool Module (Advanced VelPAK use only)
The layer definition in VelPAK can be used if necessary to relate the seismic pick to the
geological top; to associate the well formation top depth layers with the time grid layers. This
often cannot be achieved simply because of missing sections at the top and/or base of layer.
If you are using well data, layer definition is always necessary.
However, usually the Layer Definition within VelPAK will have been set up through the import
link where for every layer in the VelPAK window that you have inserted a time grid surface
you need to define one top (or more) to be associated with that surface.
Note: If you load new well data into the model, or change existing well data, it will be
necessary to perform set up the layer definition again in the import link.
Note: If you are using only stacking velocities and no well data, then layer definition is not
necessary. If you generate pseudo-wells from stacking velocities, pseudo-tops are
automatically created and added to the existing layer definition.
The following chapter outlines the advanced layer definition procedures that are available
within VelPAK. In particular how to set VelPAK to work with horizontal wells when the track
may well exit and re-enter the target horizon.

Introduction to Advanced Layer Module
If you load new well data into the model, or change existing well data, it is necessary to
perform the advanced layer definition again if you are using it. Layer definition should always
be performed immediately after well data import to ensure model integrity.
If you are using only stacking velocities and no well data, then layer definition is not
necessary. If you generate pseudo-wells from stacking velocities, pseudo-tops are
automatically created and added to the existing layer definition.
Layer Module takes tops information typically used in a VelPAK project and produces a
Master Layer Definition containing all the tops used but in chronostratigraphic order.
The Master Layer Definition contains flags against each top:
OK - Order completely resolved.
Check - Order almost certainly correct but not completely resolved.
Bad - A contradiction has occurred.
The Model Tops List can be used to deactivate tops that serve no purpose in the Layer
Definition - they will not appear in the Master Layer Definition which makes it easier to select
the tops that are to be used.
Minor ordering problems that are caused by repeated tops (e.g. Zechstein Rafts) can be
tolerated. The VelPAK model is then updated by applying the Master Layer Definition to the
well data – doing an automatic layer definition.
Note: Clearly, tops relating to the seismic pick must always be correct, however tops that
do not relate to the layers do not have to be correct; tops marked ‘check’ or ‘bad’
(although they should be checked) that do not interfere with the layering can be
ignored or can be turned inactive’.

The actual sorting and searching theory that the program uses to establish the Chronological
listing is extremely complex. If the reader desires this can be investigated further by referring
to the following book:
D. Knuth. The Art of Programming, Vol. 3 (Sorting and Searching). Addison-Wesley, 1973.
Saving the Information

The Master Layer Definition and the Well Layer Definition are saved as part of the
VelPAK model when the model is saved.
The Master Layer Definition can also be output as Excel spreadsheet information.

Horizontal Wells
Horizontal Wells
Horizontal wells can be accommodated in VelPAK.

These need to be read in as deviated wells (‘DEV’ classification in Well Curve Data Generic
Format input.).
When geosteering a well through a layer a time/depth mistie may mean the track will exit the
target horizon. It is possible within VelPAK to go through a depth conversion corrective
procedure each time the well steers out of the target horizon and recalculate and revise the
velocity model based on the new formation top information.
For these well tracks that ‘porpoise’ in and out of a horizon only the first instance of the
horizon being pierced by the well must be used within the Layer Definition. Further piercings
going out and in to the horizon again must be marked as ‘Unused’ and ‘Extra’ in the Model
Tops List, that is, they are used for residual mistie correction but aren't involved in the model
in any other way. The velocity model can be quickly updated (by simply re-running a pre-
defined workflow for example).
Full details of using VelPAK for tracking a Horizontal well and depth conversion can be found
in the standalone document, please contact customer support for further details.

Steps to Using the Layer Definition

1. Build all tops in the model to produce a list in Chronostratigraphic Order. This is usually
done automatically on entering Layer module for the first time. See Build.
2. Review the alphabetical Model Tops List to make any unused tops ‘Unused’and to mark
‘Extra’ tops per layer.
3. Check integrity of each Well OK/Check/Bad in the Master Layer Definition. See Check.
4. Assign/Select tops to define layers in Master Layer Definition. See Assign.
5. Apply to the Well Layer Definition. See Apply.
Inactive Tops
Inactivating tops is simply a method of making the layer definition easier to manage by
making unused tops inactive/invisible.

Highlight the top you wish to inactivate or active and use the -/+ icons at the top of the Model
Tops List or click the right hand mouse button on the left panel next to the top name to change
the top’s mode.
Making a top active or inactive will cause it to be displayed or removed from the Master Layer
Definition panel.
Extra Tops
‘Extra’ tops are for use in drilling horizontal wells. If a well track ‘porpoises’ in and out of a
layer the measured depths for where the track cuts through the layer can be entered as Extra
‘tops’ which are then used in the error correction of a re-depth conversion to more accurately
define the layer.
Full details of using VelPAK for tracking a Horizontal well and depth conversion can be found
in the standalone document, please contact customer support for further details.
Extra tops need to be assigned the numerical value of the layer which the track cuts through.
This is always the top of the layer the track cuts through, regardless of whether the track is
cutting into or out of the layer, as shown in the picture below.
To use the Extra function, highlight the top you wish to make and and use the Extra Icon
icon at the top of the Model Tops List or click the right hand mouse button on the left panel
next to the top name and select Extra.
An alert box will pop up allowing you to assign the Extra top to the correct layer.
A top assigned as ‘Extra’ automatically becomes inactive in the Master Layer Definition.

Main Top for Layer 2 (not an ‘Extra’)

‘Extra’ tops all assigned
2
as Layer 2
Main Top ‘Extra’ top assigned

for Layer 3 as Layer 3
4 (not an ‘Extra’)

Layer Module Panels
Layer Module Panels

Model Top List
Panel
The left panel, Model Tops List, is a list of the formation tops sorted into alphabetical order.
Here tops can be assigned a tag as to whether they are used in layer definition, whether they
are to be used purely for residual error correction ("Extra" tops), or they specific tops can be
deleted from the model entirely if they are not relevant for layer definition. Deleting from the
model does not affect the tops in the original seismic database - deletion applies only to the
current VelPAK model.
Note: Tops may be multi-selected using CTRL+ Click.
Build Don’t Used Extra Find Rename Delete

Use
Select the pop up menu using right hand mouse button

Build - a build occurs automatically when entering the Layer module.
Don’t Use - Selected tops are not used in the model and are removed from the Master
Layer Definition list.
Use - Sets selected unused tops as used in the model and restores them to the
Master Layer Definition list (by default, all tops are used).
Extra - Make a top an ‘extra’ for use within horizontal drilling scenarios. These tops
will have a residual error computed for them, but they are not part of the layer
definition and cannot be used for layer definition. Select the event for residual error
correction when prompted.

Layer Module Panels
Find - Find the highlighted well in both the Master Layer Definition and Well Layer
Definition lists.
Rename - Allows you to rename your tops. Selecting the top will bring up the alert box
to allow renaming.
Delete - Deletes the selected and highlighted tops from the model permanently.
Master Layer Definition

Panel
Build Find
Select pop up menu using right hand mouse button.

The Master Layer Definition is where the layer definition is performed. It is a list of all
the unique tops names, sorted into sequence by depth, shallowest to deepest. The
Status column indicates whether the top is considered "Ok", "Check" or "Bad". The
Current column indicates the current status of the layer definition, as a useful
reference if you are revising the layer definition. Initially a value of 0.000 will indicate
there is no active layer definition.

Layer Module Panels
The "Surface" at the top of the list is a nominal top created by VelPAK to represent a
top at the seismic datum, and cannot be deleted. Double-click in the grey cell to the
left of the top name to assign it to a layer.
Build - Builds the Master Layer Definition list from the information in the model. The
resultant display will be what you use to check and assign the layers.
Find in Wells - Given a highlighted top in the Master Layer Definition, selecting this
will highlight all references to that top in the Well Layer Definition.
Table Headers
Top - The Name of the Top. You may find that the same actual top has been entered
in the model with different spellings, for example. This display allows you to see any
discrepancies and fix them to turn ‘Check’ or ‘Bad’ into ‘OK’.
Layer - The Layer number and color will be displayed here when layers have been
assigned.
Status - Check/Bad/OK. See Status below.
Current - Allows you to see what layer the top is currently defined as - for use when
adding extra tops into the list or changing the layer of a top.
Well Name - List of the well names.
Well Layer Definition

The Well Layer Definition window shows each well in the model with the Tops in ascending
order assigned to their Layers as defined in the Master Layer Definition display to the left of
the default window.

Layer Module Panels
Panel
Apply Find Check Delete

in Wells
Select pop up menu using right hand mouse button

Apply - This is the button to apply the layer definition in the Master Layer Definition to
the wells (and becomes the Current layer definition)
See Well Log Module for full details of the Manual procedure that this button does
automatically. The layers will be seen on activating the Well Log Module. Grids within
the model will be shown if available to the right of the well curve. (None on display in
image below.)

Layer Module Panels
Find in Wells - Given a highlighted top in the Master Layer Definition or Well Layer
Definitions, selecting this will highlight all references to that top in both panels.
Check - A very powerful facility; designed to give you a quick check of the data before
(or indeed after) proceeding with the building of the well definitions. Once the Master
Well Definition has been run and each top in the model assigned an ID number
(ascending chronologically), pressing Check will highlight in the Well Layer Definition
tab which tops are out of order according to the ID number. You can then review these
tops and see why they are out of order.
However; bare in mind that it may not be the highlighted top that is at fault;
Find in Master - Given a highlighted top in the Well Layer Definition, selecting this will
highlight that top in the Master Layer Definition.
Delete in Wells - Deletes the selected and/or highlighted tops from the model
permanently.

Layer Module Panels
Table Headers
Well Name - List of the well names.

Top - The Name of the Top. You may find that the same actual top has been entered
in the model with different spellings, for example. This display allows you to see any
discrepancies and fix them to turn ‘Check’ or ‘Bad’ into ‘OK’.
Depth - Depth of top.
Layer - The Layer number and color will be displayed here when layers have been
assigned.
Status - Check/Bad/OK. See Status below.

Layer Module Panels
Assigned
First Well in List
Layers
for this
Well
Second Well
in List
Status - Check/Bad/OK/Unused
When the preliminary Master List has been Built, it will contain one of the three following flags
against each top:
OK - Order completely resolved.
Check - Order almost certainly correct but not completely resolved; some tops are
imperfectly defined but statistically the top is likely to be in the right place.
Bad - A direct contradiction has occurred between at least two wells. Note that this
does not mean that the entry is necessarily wrong - for example it is quite geologically
valid to have a repetition of a layer down a well. However the instance needs to be
looked at.

Layer Module Panels
Unused - if set as inactive in Model Tops List.

The Check and Bad flags need to be looked at before assigning the layers to the tops.
Note: Clearly, tops relating to the seismic pick must always be correct, however tops that
do not relate to the layers do not have to be correct; tops marked ‘check’ or ‘bad’
(although they should be checked) that do not interfere with the layering can be
ignored.
Assigning the Layers (selecting the tops)

Note: For any method you use to select the layers on the Master Well List Definition the
corresponding tops will be assigned the layers for each well listed in the Well Layer
Definition display.
Tops bounding the top/bottom of layers are selected as shown here:

Layer Module Panels
Double-Click on the gray box All older tops will become assigned
to the left of the top that defines the as the next layer, in this case Layer 2.
next layer.
Double-click on the top that defines the next layer.

This will assign all subsequent layers as the next layer,
in this case Layer 3.
Continue your selection of tops that defines the layers until all layers have been defined.
Tip: Undo an incorrect selection by Double-Clicking on the gray bar again.
Tip: Use ‘Unassign All’ to clear the whole selection to start again.

Applying the Layer Definition to the Well Module
Once you have defined you Master Well List you will want to apply the layers to the wells in
your project.
Referring to the first screen-shot in this chapter (Go Here) you will see that the suggested
display for working in the Layer Tool Module has both Layer Tool Tabs on display along with
the Well Module on display to the right to visualize the Layers once applied being displayed
on the curve.
Apply - Applies the Master Well List to the Well Logs. See Well Log Module for full
details of the manual procedure that this button does automatically. The layers will be
seen on activating the Well Log Module. Grids within the model will be shown if
available to the right of the well curve.


Profile Module
Introduction
SNAPPING
A major feature option for VelPAK. Event Horizons are snapped to form continuous
layers. Only snapped data within VelPAK can be mapped, depth converted, re-
interpolated or displayed in fill mode.
Snapping a horizon usually means some amount of editing to the data. The snapping
routines behave intelligently, however there are some situations where human
intervention is necessary. You would therefore expect to use the POINT EDIT and
SEGMENT EDIT options during snapping of the data, when the snapping alert messages
appear informing you that there is some situation the program can not cope with on its
own.
DEPTH CONVERSION
Layer Cake Depth Conversion, using either pre-stored methods or user-defined methods,
utilizing Constants, Grids, Curves and a large number of standard formulae. Generation
of Vup and Vdown information.
RE-INTERPOLATION
Re-Interpolation of profile horizon data to a SMALLER shotpoint increment. (Re-
interpolation never acts on data to make the increment larger between shot points.)
STUFF
Allows you to create and add any number of new horizons into VelPAK using given
isochrons or isopachs. Any new migrated fault position is calculated semi-automatically.
PROFILE
Allows you to create new profiles from random picks over the mapping area. data are
derived from either intersection profiles or from Grids within the model.

Profile Displays
Profiles display supports instantaneous velocity displays and "previews" of the section as if
generated using Velocity > Volume, as well as enhance seismic overlays and wiggle displays
from SEGY files.
Display Options
Previous/Next Arrows
Event Well Line
Use the previous/next arrows at the top of the module tab to move to the previous or next
Event, Well or Line within the VelPAK model.

Display Types
Select type of Profile to display.

Use the down arrow () or double click on input name to select from available inputs.
Time - Simple Time display of profile data (the usual display while Snapping data).
Depth - Depth display. Note - profiles must be Depth Converted to be able to display
profile in Depth!
Time/Depth Filled - Display the time /depth section with each layer filled in color.
Tip: Using the Time Filled / Depth Filled in conjunction with the Event Fill Verify Option
allows you to verify the layer model, to check that Snap has worked according to the
geological model. It can be a very useful check to see that the layers are being read
correctly. Basically, if the Fill model you are looking at looks OK, in that all the colors for
all your layers are falling within the layer you expect, you can be fairly confident that
your Depth Conversion will work correctly, layer by layer.
Time or Depth/Vel Shaded - Displays a filled section in Time or Depth filling with the
instantaneous, average or interval velocities set up in an option further down the list on
the Event Option dialog. Thus this display can show a gradational color fill through out the
different horizon layers.
Note: Verify Fill Process can not be used with the T/V or D/VFILL.

Time/Vel Volume - Displays the Velocity_Type as a filled section based on survey
parameters set in the Velocity > Volume fly-out. The 2d or 3d geometry must be set in the
Velocity > Volume fly-out first.
Overlay Options
Display on
Display off
Label on
Label off
Turn Display element ON or OFF for display on the Profile. With or without element label
Line Mistie - Displays intersections and mistie ‘blobs’ on your time or depth profile, with a
line display and the line name of the intersecting line displayed when the ‘Line Value
Display’ is switched on.
On TIME profiles,
Green line intersections show SNAPPED lines.
Red line intersections show UNSNAPPED lines.
On DEPTH profiles,
Green line intersections show DEPTH CONVERTED lines.
Red line intersections show lines NOT DEPTH CONVERTED

Line Mistie Display Selected
Gives the Event ‘Blobs’.
Line Mistie Value Display Off

no Line Intersections seen.
Line Mistie Display On

Gives the Event Blobs.
Line Mistie Value Display On

shows Line Intersections
and Line Names.

Grid Profile -Will display the Grid nodes intersecting with the Profile you are viewing.
Grid Display On
Gives the Event Blobs
Grid Value Display On

shows grid spacing
Grid Display On
Gives the Event Blobs
Grid Value Display Off

No Grid spacing seen.
Well Track -
Displays the well locations and well tracks stored in your model on the profile.
The extreme distance a well can be situated to include it or exclude it from being
displayed on a Profile is set under the Event Dialog.

Deviated Wells on a map looking like
the fictional one above..
Will be displayed on Profile like
this...
Well Track Label Off Well Track Label On

displays all displays just PICKED
Tops for that Well Tops for that Well
Seismic Backdrop - will display the SEG Y as a back drop for the profile. You will need to tell
VelPAK where the SEG Y data are; the data are not read in but cached as the display
progresses through the model’s Profiles. Random lines created from the surface module (Go
Here) will also display a crude back drop.

Point - displays the points of the profile faults. Point Label on displays the FU, FL on the
faults.
Profile Edit Icons
Insert Delete Edit Move Pick Insert Delete Edit Move Split Merge Swap Flip Void Term
Point Edit Segment Edit
The Profile Edit options within VelPAK are crucial to being able to modify horizon data such
that they can be successfully snapped, and used in applications such as MAP or Depth
Conversion.

Note: You are able to edit not only the time profile, but the resultant depth profiles. However,
if you do this then the relationship between the time profile and depth profile will be
lost.
Pressing the left-hand mouse button over the option you require will cause that option to be
activated. The Console Window of VelPAK displays what edit mode you are in.
Here follows a summary of each option. For full details of each option select the appropriate
Edit option Details.
Note: For any of these procedures to work, you must select a data point on the event
horizon, not the line joining them.
Point Insert - Allows you to insert extra points - one at a time- onto a selected horizon.
Go To Details
Point Delete - Allows you to delete points onto a selected horizon. Go To Details
Point Edit - Selecting edit and then a particular data point brings up a dialog box where
the values for this point are displayed. Go To Details
Point Move - Allows you to select a point and move it. Go To Details
Point Pick - Used as a method of selecting the event horizon you want to edit. Go To
Details
Segment Insert - Allows you to insert a new distinct segment within the current event
horizon. Go To Details
Segment Delete - Will cause an entire segment or event horizon to be deleted. Go To
Details
Segment Edit - Selecting a particular segment of data brings up a dialog box where the
segment name is displayed. Go To Details
Segment Move - Allows you to move an entire segment to another area of the profile. Go
To Details
Segment Split - Allows a segment to be split. Go To Details
Segment Merge - Allows a merge of two segments of an uncontinous event horizon
together. Go To Details
Segment Swap - Allows you to swap the priority of segments within a model. It does not
swap the data information for any given segment, merely the number of the segment. Go
To Details
Segment Flip - Provides a reverse snapping direction for an individual event horizon or
event horizon segment. Go To Details
To Flip the whole profile to its mirror image, use the function from the Profile -> Event drop
down menu)
Segment Void - Voiding a segment allows you to retain a segment within your model,
which is not used in any application or output routine within VelPAK. Go To Details

Segment Term - Term can be used to terminate an event horizon or segment when data
are missing. Upon snapping, when VelPAK finds a terminated segment, it does not
attempt to snap to the end of the line or to join the ends of two segments together, instead
VelPAK draws a vertical line to the event horizon above. Go To Details
Other Profile Display Icons
Apply options for the Profile procedures:
Event Snap Depth ReInt Stuff Profile
Further procedures:
Flip Undo Undo

Event Line
FLIP LINE
Allows you to display the profile in mirror image. Segment numbering and direction will
also be flipped, and snapping will simply begin from the other end of the section. (VelPAK
always snaps in the direction of minimum to maximum shotpoints.)
1 1
Note: The option ‘FLIP SEGMENT’ for individual segments can be found under Event
Segment Edit.
UNDO LINE
This clears all the edits to all the event horizons made since the last save of the model for
the line you are currently displaying in profile.
An alert box appears before undoing, for verification of the process.
UNDO EVENT
This option allows you to undo the single last edit you have done to the model.
An alert box appears before restoring the last saved model, for verification of the process.

Repeated use of this option allows you to work backwards doing a point-by-point deletion
of the edits you have made. If you have just inserted a whole segment, this option will still
just delete the last point of that segment, and so on, and not the whole segment.

Display Dialog
Display Dialog
Tabs include:
General tab - to change the main input features of the Profile display.
Range tab - gives you the opportunity to display a range of the profile; in the X and Y
directions (Y being time, depth or velocity.
Name tab - to change the name of the event horizon. For user reference only.
Color tab - to change the color of the event horizon displayed on the profile.

Display Dialog
Display Dialog - General Tab
When you have made your edits. Press to apply the changes and activate the
option.
Option
Display_Type - Same selection as Display Type drop down on main Profile window. Go
Here for details.

Display Dialog
Fill_Verify- If this is activated, between each layer filling there will be an alert box asking
you whether you wish to display the next layer.
Tip: The reason for this is to be able to keep an eye on the layer-filling to check that each
layer is filling correctly. The data may have appeared to have snapped correctly, but for
some reason something has not quite worked correctly. You could then get a layer being
filled by one layer/color, and then overwritten by another. This would cause the depth
conversion to act incorrectly. If you had ‘No Verify’ activated it is unlikely that you would
be able to see the layers behaving incorrectly due to the speed of the fill.
Reversal_Display -
No - Do not highlight reversal zones.
Yes -Highlight reversal zones for all event horizons.
Current Event - Only highlight reversal zones for current event horizon.
R1 Reversal Zones are

areas where a deeper
sequence overlies a
shallower sequence.
R1
Current Event_Z1_Z2_Z3 - only highlight reversal for current event horizon with a color
coding to differentiate between the multiple Z values occurring in the reversal zone.
These different Z values can be output separately into an output file for gridding
purposes.

Display Dialog
Z1
Z2
Z3 Z1
Search_Events - Used as an aid for editing event horizons when points from different
event horizons lie on top of each other. You can set VelPAK to pick one in preference to
the other.
Search Upwards - Searches up from the bottom of the model’s defined event horizon
list to select what is usually termed an ‘older’ event horizon.
Search Downwards - Searches down from the top of the model’s defined event
horizon list to select what is usually termed a ‘younger’ event horizon.
Segment_Numbering - Show on the Profile display the number of each segment and the
segment direction This can be particularly useful to debug a troublesome event horizon. It
may be easier to see a problem just using the ‘One Event’ option rather than displaying
the number and direction of all event horizons. Select the event horizon via the
Surface&Slot selector.
Velocity
Velocity_Color - Choose the stored color table to best suit your display. Click on the box
to the right of the color selection slot to bring up a list of color tables available to you. The
color tables within VelPAK allow selection from standard VelPAK color bars, or import of
user's color bars. Go Here for further details of the Color Table options.
Velocity_Increment - Defines the resolution of the fill display. A value of 1 will give a fine
gradation on display, a value of 50 (maximum) will give a very ‘blocky’ display.
Velocity_Type - The type of Velocity you wish to view when your section is filled.
Interval Velocity - fills with the interval velocity between layers (not supported for
Time_Vel_Volume fill).
Instantaneous Velocity - will calculate the Instantaneous Velocity for each layer
using the Vup/Vdown calculated during the Depth Conversion process. It fills with the
instantaneous velocity computed at each sample (this replaces the Vup/Vdown fill in
older versions of VelPAK).
Average Velocity - will display as standard the average velocity.

Display Dialog
Note: The Vup/Vdown option must be activated within the Depth Conversion Options for this
to be calculated when Depth Converting and thus available for use in the display
here.
Seismic
Segy_FileMode - Segy3D/Segy2D - The name of the Segy 2D or 3D file.
Segy_FileName - Select the File where your SEG Y file is stored. Note this is not read in
to the project but remains cached while you are in the Seismic Overlay mode.
Segy_Iline - User supplied value for the in-line header word location for 3d SEGY files
(typically 17 for a SEGY export)
Segy_Xline - User supplied value for the cross-line header word location for 3d SEGY
files (typically 25 for a SEGY export)
Seismic_Color - Choose the stored color table to best suit your display. Click on the box
Seismic_Type - Density, Wiggle or Contour. Note that on large data files Wiggle can
cause a very dense display and Contour can look very similar to Density until zoomed in
(and also take a while to generate).
Density - Sample values represented by color raster display.
Wiggle - Wiggle traces plotted using parameters set in
Wiggle_Factor - Factor of wiggle amplitude
Wiggle_Fill - Positive or negative or both.
Wiggle_Line - enable wiggle line - Yes/No.
Wiggle_Skip - number of traces to skip.
Wiggle_Type - Type of Wiggle - Fill_Mono/ Wiggle_line/ Fill_color/ Shade_color.
Well -
Well_AOI - Marks the extreme distance a well can be situated to include it or exclude it
from being displayed on a Profile. Default of 50 is in whatever units the X-Y values are in.
Overlays/Labels - These are exactly the same as the ‘Overlay’ options available at the
top of the top of the Profile module tab. The overlays and their labels can be turned on
here via a Yes/No toggle or by the Overlay drop down. For full details of what these
displays do Go Here.

Display Dialog
Display Dialog - Range Tab
When you have made your edits press to apply the changes and activate the
option.
Range Tools
AOI Flip Out In Up Down Reset

Seismic Colorbar
AOI - Copies the currently displayed Area of Interest (AOI) into the Range extents and
sets the XY_Type to "User".
Seismic Colorbar options - allows user to scroll, flip and reverse the color bar
selected on the Display -> General -> Seismic_Colour slot.
Options

Display Dialog
Axis
X_Type, Y_Type - ‘Auto’ displays each profile using the range of the entire model. ‘User’
allows you to define the Shot Range and Time/Velocity/Depth range as required.
Range
Depth_Max, Depth_Min - Specify the Depth unit range down the Y axis that you wish to
display.
Shot_Max, Shot_Min - Specify the Shotpoint range along the X axis that you wish to
display.
Time_Max, Time_Min - Specify the Time unit range down the Y axis that you wish to
display.
Velocity_Max, Velocity_Min - Specify the Velocity unit range down the Y axis that you
wish to display.
Scale
Depth_Scale, Time_Scale, Velocity_Scale - The number of Time/Vel/Depth units per
cm you wish to have displayed.
Shot_Scale - Specify the number of Shotpoints per cm to display.
Display Dialog - Name Tab
option.
NAME - allows you to type in an actual Geological name for your event horizons. This
name can not be read in to this from any of the ASCII input processes, nor can it be

Display Dialog
output through any ASCII output processes. However, this name will be displayed in the
Properties dialog for the relevant event horizon.
Display Dialog - Color Tab
option.
COLOR - provides a slide bar for selecting a color to correspond with a particular event
horizon or fault within VelPAK. There are 32 colors available ranging from ‘color 0’ (black)
to ‘color 32’ (white). The color you have selected will be displayed in the ‘COLOR’ column
along with its respective number.

Snap Dialog
Snap Dialog
Tabs include:
General tab - to change the main input features for the Snap option.
Bias tab - to aid the snapping procedure by telling the program the way to go to keep the
horizon integrity - be that ‘UP’ or ‘DOWN’.
Missing tab - This provides an up or down option to tell VelPAK what to do when event
horizon data are missing. from the profile, since the layer above an event horizon that is
missing due to truncation would be different from a layer above an event horizon that has
been pierced.
Pod tab - to designate certain event horizons as ‘Pods’ or ‘Lens’ if required, which thus
are discontinuous over the Profile.
Clean tab - to assist in the cleaning of horizons that abut profile faults and thus speed up
the snapping routine.
Discussion
Data output from workstations basically consists of segment orientated data i.e. a collection
of digitized data points measured by SP/CDP and TWT. These points are collected into a
segment until there is a break in the data - usually caused by a fault.
The primary purpose of the SNAP process is to:

Snap Dialog
1. By extrapolating the end points of segments, join adjacent segments.

2. Equalize ‘edges’ (ends of profile) such that each event horizon begins or ends at the
same shotpoint.
3. ‘Track’ or reconstructs the layer such that every event horizon is continuous over the
whole profile.
4. Generate flagging information for use in the mapping process e.g.
FU FUR
FL FLR
5. Generate a unique code describing the geological situation of the data point. This is
known as the Mask value. Full details of this powerful feature Go Here.
6. Generate closed polygons of the layers such that color filled displays can be generated
and depth conversion can be accomplished.
Once the process has been completed and the data has been re-interpolated (if necessary)
the data generated by the DATA OUTPUT procedure represents a highly sampled description
of the geological top or base of layer. If these data then gridded up with VelPAK using the
gridding routines then the resulting grids will accurately represent the top or base of the
layer along the profiles.
Note: You do not need to snap the whole model to use Depth Conversion routines or display
the profile surfaces as Ribbon Maps; you have the options of ‘Snap, Unsnapped or
Merged’ to select the data which suits your model best. For a discussion on this Go
Here.

Snap Dialog
Snap Dialog - General Tab
option.
Option
Snap_Thickness - Will change the thickness of the tracking line; a visual aid to watching
the snapping track process.
Snap_Type -
Current Line - Only the current line will be snapped and then the process will stop.
Un-snapped Lines - The memory model flags whether a section, has been snapped or
not. The bracketed word ‘(snapped)’ appears after the line name. This option will
therefore only process ‘un-snapped’ sections.
All Lines - Regardless of the sections ‘snap status’ all lines will be (re)processed.
Snap_Verify - this will ask for verification before snapping the next line. A layer-by-layer
time-filled display will be seen of your profile before continuing to the next profile to be
snapped.
Aperture
A specification of how far an event horizon or a fault can automatically be extrapolated by
the program. An example of when you would want to use this is to either make sure the
fault planes connect to an event horizon above or below, thus giving your event horizons

Snap Dialog
a path, or to make sure the fault planes do not connect to an event horizon above or
below, thereby stopping the event horizon following an incorrect path.
Event_Point - The number of shotpoints or CDPs to search in the X direction.
Event_Value - The Y axis of the search radius for extrapolation - measured in msecs or
metres (for depth profiles).
Fault_Point - The number of shotpoints or CDPs to search in the X direction.
Fault_Value - The Y axis of the search radius for extrapolation - measured in msecs or
metres (for depth profiles).
Ignore_Points - The number of points of an event horizon leading into a fault to ignore.
Typical setting is 1 to ignore a possible spurious point as the last point leading up to a
fault.
Use_Points - The number of points to use in the least-square fit equation to extend/
interpolate the event horizon up to a fault.
Delay
Delay - A numerical input. In complex situations it can be useful to watch the SNAP
process work. This delay factor shows the process so you can watch the decision making
process. The speed is dependent on the number of points on each event horizon of your
profile; changing the value of Delay from 0 to 1 may be enough to slow the process down.
Note: Use the Keyboard ESC key to stop the snap if the Delay is set too slow.
Delay_Type -
All Events - Will apply the delay to all event horizons in the profile.
Current Event - Will apply the delay to just the currently selected event horizon.
Thinking_Time - The amount of ‘thinking time’ you allow the model before it will give up
and request manual intervention.
Expert
When snapping less than perfect data, you will experience a lot of Alert boxes where the
program is either awaiting confirmation before proceeding to do something automatically
(such as merge) or expecting you to do some edits to the data. If you have a lot of
segmented data where the merges or splits are obvious you have the option to tell
VelPAK to do these auto-merges and auto-splits without an Alert Box popping up every
time.
Auto_Intersect - will allow segments to cross horizons.
Auto_Merge - will automatically merge segment data together without asking for
verification.
Auto_Splits - will automatically split data where appropriate with out asking for
verification.
Show_Pauses - Yes/No - Switches off any other non-essential alert boxes that are not to
do with ‘AUTO SPLIT’ or “AUTO MERGE’.

Snap Dialog
Note: The EXPERT OPTIONS will only Auto Merge or Auto Split the simple merges and
splits common to this feature. If VelPAK finds a more complex and difficult situation
which it can not cope with, it will still stop and alert you.
Snap Dialog - Bias Tab
option.
Bias
Bias - Select whether to change Bias to be Up or Down. See discussion below.
Discussion - Biassing the Profile Data

Why BIAS?
When a layer within the model is being tracked along the whole profile, there will be times
when particular layers are absent, either due to fault cuts, unconformity, or onlapping. In most
cases the intelligence behind VelPAK can work it out for itself as to where the absent layer
should go. However there are cases where it would need a ‘nudge’ to help it on its way. This

Snap Dialog
is where a BIAS can be used; where you can tell VelPAK that should the event horizon
disappear, the way to go to keep the horizon integrity would be either ‘UP’ or ‘DOWN’.
Example of using the ‘BIAS’ option
ORIGINAL In the example to the left, it should

PROFILE be obvious that the tracking of the
lighter event horizon should go
down, within the fault block.With
BIAS set to ‘UP’ (the default value)
the snapping process will cause the
‘UP’ BIAS layer to track Upwards. So the
ON SNAPPING BIAS must be changed to ‘DOWN’
in order that the lighter event
horizon layer behaves geologically
correctly.
‘DOWN’
BIAS
ON SNAPPING
VOID SEGMENT: It should be said at this point that there is another method available to
suggest to VelPAK the way to go to keep the layer integrity. This entails inserting a ‘VOID’
segment in an appropriate place to force the layer down (or up). This would be done on
profiles where any one event horizon would require to go both up and down to keep the
geological structure sensible. For full details of how to edit this:
GO TO ‘VOID’
The 3 Methods of setting BIAS on your profile data

The method of setting the BIAS is dependent on your profile data, and how selectively you
want to the BIAS to work.
(Available BIAS methods are UP or DOWN.)
1. BIAS set for one selected event horizon over WHOLE MODEL. This would be used for a
particular geological situation that occurs throughout the data stored in your VelPAK
model.
This is set in the Snap Dialog from within the ‘Bias’ Tab.
2. BIAS set for a chosen event horizon for Selected Line (Also known as ‘Line Bias’). This
sets the chosen event horizon to a particular BIAS that could be different to the event
horizon on an adjacent line.
3. BIAS set for Single Segment (Also known as ‘Seg Bias’) of one event horizon. Usually
used to get around a particular unique geological situation.

Snap Dialog
Both these methods are set by selecting the Segment Edit Option on the data. Clicking on the
chosen segment will highlight that segment, and will call up a Segment Edit dialog box where
you can set the BIAS for either this one segment, or the whole event horizon for that one
profile currently displayed. GO TO Segment Edit.
Snap Dialog - Missing Tab
option.

Snap Dialog
Missing
Missing - Select whether a missing event horizon has disappeared ‘Up’ or ‘Down’. See
discussion below.
Discussion - Why Use Missing?

The example illustrated below shows a situation where a geological structure or feature, such
as onlap, creates discontinuous event horizon data. By flagging the event horizon as Missing
within the Event Option page, VelPAK is advised as to the correct course of action to take
upon snapping.
Limit of seismic line

If event 2 is flagged as missing,
VelPAK will recognize that the
event horizon is absent and will
Event 1 snap correctly.
A If event 2 is marked as down then

area ‘A’ will be filled with the
color of event 2.
Event 2 If event 2 is marked as up then
area ‘A’ will be filled with the
color of event 3.
Event 3

Snap Dialog
Snap Dialog - Pod Tab
Discussion - Snapping with Pods
VelPAK’s definition of a Pod is a lens-like layer of rock that is discontinuous which does not
on-lap or pinchout; it will exist as an isolated layer within another layer.

Snap Dialog
Pods can be depth converted successfully within VelPAK. Any number of pods (up to a
maximum of 32 named event horizons) can be accommodated within a profile and each pod
can have its own or a common velocity method.
In normal usage VelPAK presumes and expects layers to be continuous over the whole
profile. If a layer has disappeared it is because it has been truncated by a younger event
horizon or pierced by an older event horizon; the snapping logic will then continue the
tracking of the layer that has disappeared along this new event horizon until the end of the
profile.
Clearly with Pods this is not the case and so a special case needs to be made to inform the
VelPAK snapping logic to treat the pods as single, discontinuous instances.
To distinguish between pods and usual, continuous event horizons within VelPAK there are
two things a user must know to do within the set up:
1. The event horizons in VelPAK which are assigned to a pod must occur as an event
horizon number greater than the oldest normal horizon in the model (as if chronologically
older.) For example:
Event 1
Event 2
Event 3
Event 4
Event 8
Event 5
2. The event horizons in VelPAK which are assigned to a pod must be identified as such
under the Pod tab of the Snap Property Grid within the Profile module.

Snap Dialog
Details of how to correctly read horizons into VelPAK as Pods can be found in the technical
paper ‘Overhangs & Pods’ available in the Standalone Documents directory of VelPAK
documentation.
Pod Options
option.

Snap Dialog
Pod
01_Pod, 02_Pod - Yes/No - Select which horizons in your model are to be treated as
Pods. As discussed, Pod horizons need to occur chronologically below the oldest
normal horizon in the model.
Snap Dialog - Clean Tab
What is Clean?
A utility designed simply to automatically clean the horizon data that abut faults - and
sometimes inadvertently overrun the fault - in profile mode and thus speed up the snapping
routine. This is often caused by the different picking techniques of horizons and faults within
the workstation environment and when brought into VelPAK the program would be unable to
successfully snap horizon data which overrun the fault. Manual editing of these few points
that overrun the faults would be laborious; Clean mode will do this automatically.

Snap Dialog
Successful
Snapping
In this example ‘Clean’ would remove the points that

overrun the faults at both the Upper and Lower points
Clean Options
option.
Option
Clean Type - Select which profiles are to be cleaned in the model; current, unsnapped or
all lines.
Clean
Clean_Point - Specifies the number of shot points from a fault segment inside which
horizon data points are deleted. The point where the horizon touches (or overruns) the
fault will become the center of a circle of deletion which will be this number of shot points
in radius.

Snap Dialog
Setting the Clean Point to 20 will mean

data points will be deleted for 20 shot
points either side of the Fault.
Clean_Verify - Yes/No. Yes will allow the user to see graphically what will be deleted/
cleaned. You must select this option to be No for the cleaning process to actually take
place.
Note: There is no Undo facility on this option; it is recommended you save your model
before activating the clean process.

Depth Dialog
Depth Dialog
Depth Conversion methods within the Profile Module of VelPAK work solely on the TIME
PROFILE data.
For Grid-to-Grid Depth Conversion and manipulation use the Depth Module or Process
Module available from the Surface Module. Go Here.
Once data within VelPAK has been successfully snapped, a layer cake depth conversion can
be performed on the data.
Depth conversion methods are set up under the Parameters tab.
Within VelPAK’s depth conversion options, there are a certain number of depth conversion
methods already defined. These can just be utilized for any given layer, by inserting the
correct variable values, according to your depth conversion parameters.
However, there is the added dimension within VelPAK’s depth conversion in that you can
write your own methods, or amend the ready stored methods, and save them for future use.
The Depth Conversion methods within VelPAK are written in a language called Xpress. This
has been specifically designed so that it is possible for non-programmers to write the text for
a new depth conversion method.
For details of how to write a depth conversion method in Xpress, go to Writing and Saving
your own process method.
Note: All event horizons within your model need to have a valid depth Conversion method
set up in order for the Profile Layer-Cake depth conversion to run successfully. Set up
is done per event horizon; set up one event horizon in the Depth Dialog Parameters
and then move to a new event horizon via the VelPAK Surface&Slot selector and set
up a new set of Depth Conversion Parameters for that event horizon...and so on.
Tabs include:

Depth Dialog
General tab - setting up the event horizons to be depth converted.

Parameter tab - for entering formula inputs and outputs.
Formula tab - for viewing the formula you are using.
Depth Dialog - General Tab
option.
Option
Depth_Type -
Current Line - Only the current line will be depth converted.
Unconverted Lines - Any lines not already depth converted will be converted.
All Lines - All lines regardless of depth converted status will be converted.
Depth_Verify -
No - No depth display is shown while depth converting.
Yes - Displays a filled depth section after each section is completed.
Hide Graphics
No - Will show the actual profile data points that have been layer-cake depth
converted.
Yes - Will not show data points converted during the process.
Expert
Calc_VupVdown - Options - No/Yes/Yes With Logging.

Depth Dialog
Allows you to have the Depth Conversion calculate the Velocity Up and the Velocity
Down, with or without a log.
Details of the theory behind these options can be found in the Vup/Vdown theory section
- Go Here. The ‘Yes with Logging’ produces a file called ‘VelPAK.log’. This would contain
a listing for EVERY SINGLE DATA POINT FOR EVERY SINGLE EVENT HORIZON FOR
EVERY SINGLE LINE in your project! It is therefore not advised that this option is turned
on unless you seriously need to look at each individual VUP VDOWN value. (Don’t forget
that you can see individual VUP VDOWN values for selected data points using the POINT
PICK or POINT EDIT option).
However, should you so decide, the log will look something like this:
The print out will go into the directory from which you loaded your model.
Depth Dialog - Parameters Tab

Setting up the Formula to use in the Parameter Tab will change the Inputs in the Property
Grid. Each of these Input banks relate to an input or output element from the defined depth
conversion formula for this event horizon. They will change to being filled in with inputs
relevant to the Depth Conversion method selected.

Depth Dialog
Input
Bank 01
Input
Bank 02
Options
Formula - Select the formula to use from the drop down list. Go Here for further details of
the Formulae available.
From - Specify where the values are to some from:

Depth Dialog
User Defined
You can enter your own parameters directly into the appropriate Parameter banks
below this input.
Optimize
Selecting an Optimize option will call in the relevant parameters as derived from the
Optimize module.
Note: Your Depth Conversion method here would have to be the same as the method used
to derive the parameters in Optimize.
User - The point selected by the User in the Optimize module.

Fit - The point fit derived from the values of V0 and K that best fit the well curve
information.
Residual - The point residual, the point along the ‘zero error’ line that is closest to the
Point fit.
Curve Fit
The parameters are drawn from the values derived from the Curve Fit module. If using
this option, you MUST select the Depth Conversion method that relates to the Curve
Fit routine:
Input Banks -
When you enter a Formula from the drop down selection the Input banks will fill up
various fields with the names of the input/outputs it requires. Other fields have to be
filled in by you if you have specified User as where the information for your Depth
Conversion is coming from.
Having a look at the actual formula selected in the Formula tab will show the list of input/
output variables that have to be defined.
For example:

Depth Dialog
2 Variables
The formula for “LINEAR (Vo+KZ)” in Profile

mode has 2 variables to be entered as input .
These 2 variables have a separate Input bank to
define and set up, telling the program which slot
in the Model Tree to find the grid to use or to
place the created grid, or what the Constant
value is.
The relevant number of Input banks will appear depending on the Conversion method
selected. These will be labelled with the type of input required such as Input v0, Input k.
01_Value - If the input is a constant value, the value will be entered here.
If a Grid is to be used and not a Constant then the following are to be entered:
01_GridEvent - The Event Horizon under which the grid to be used as input 01 is stored
in the Model Tree. Note the Previous / Current option which allows you select the
previous or current event horizon rather than name a specific event horizon where the
grid is to be found. Usually this option is only utilized when constructing Generic
Workflows which can work on any event horizon.
01_GridType - The slot under the event horizon in the Model Tree where the grid is
stored.

Depth Dialog
Tip: A complete list of the system Depth Conversion Methods already stored within VelPAK
and are listed. Go Here. In that section, the entire method has been written out, along
with a discussion on that particular method.
Depth Dialog - Formula Tab
Non-editable display of the Formula you have selected from the parameters tab.

Depth Dialog
Depth Formulae Available

SIMPLE INTERVAL VELOCITY
SIMPLE AVERAGE VELOCITY
LINEAR (V0+KZ)
LINEAR WITH UPLIFT FROM BASE
LINEAR FROM SEA FLOOR
HOUSTON
BINOMIAL
SLOTNICK
FAUST
HYPERBOLIC TANGENT
PARABOLIC
The Expanded Data Slots in the Model Tree -

For Depth Conversion supplemental data
If you expand the data slots of the Model Tree in the ‘Show Unused’ mode you will see that
under every Data Type under the Surface element there are 32 data slots each with a unique
name.
For an example:
The Depth Conversion method LINEAR (V0+KZ) has a number of these slots defined for use.
You can see these if you go into the Formula tab once you have defined the method from the
Parameters tab.

Depth Dialog
Toggle On

Depth Dialog
Advanced Notes for Profile Depth Conversions

Writing and Saving your own process method
Depth Conversion Methods displayed in VelPAK come from two text files; one is the set file
supplied with the system which can not be altered. The other file is a ‘User-Defined’ text file
containing processes written originally by the Users. An original ‘User-Defined’ file is also
supplied with VelPAK but this can be edited from the original by a user.
If you wish to write your own process, write it in a standard text editor and append it in the
standard format to the file ‘process_user.txt’. This can be found in the VelPAK/sys directory.
Contact your local helpdesk for assistance with this if necessary.
Be aware of syntax convention for the name of the formula such that it is read by VelPAK.
Tip: Always make a back up of the user-defined process text file before attempting to write
your own method.
If you experience difficulties in saving, with an error saying that the program is unable to save
this process to this file, it is likely that the process_user.txt file is still write-protected. Check
with your System Administrator to change the write protection for this file.
Full details of how to write a depth conversion method are given here.
The VUP and VDOWN Option within VelPAK Depth Conversion

You have the chance to calculate the VUP and VDOWN values for each Depth Converted
point.
VUP and VDOWN are the local (instantaneous) velocities immediately above and below the
event horizon point in question. As with routine depth conversion the appropriate velocity
model is used for any given point.
The velocities are determined directly from the time-depth curve using three point
approximation. For example, to determine the velocities above and below point A in the
situation shown below, the following procedure is used:

Depth Dialog
V1
X X X EVENT 1
X V2
X A VUP X X
EVENT 2
X
VDOWN
V3
X X X EVENT 3
X
For VUP, calculate depths at two slightly greater times - in this case 0.01ms and 0.02ms,
using the V2 method (starting at Event 1) and then calculate the velocity using the formula:
4Z 1 – 3Z – Z 2
V up = ----------------------------------
-
2t
where Z is the depth at A, Z1 is the depth 0.01ms below A, Z2 is the depth 0.02ms below A
and Dt is 0.01ms. This formula gives a more accurate value than a formula just based on Z
and Z1.
For VDOWN, also calculate depths at 0.01ms and 0.02ms below A, but using the V3 method
(starting at Event 2) instead and then calculate the velocity using the same formula:
4Z 1 – 3Z – Z 2
V down = ----------------------------------
-
2t
Advanced Process Methods

The PRINT statement in the process methods
It is possible to write into the methods a print statement such that the output will be displayed
in the console window of VelPAK.
This is an example of using print statements as a way of debugging Express code and testing
a depth conversion.
$LINEAR (V0+KZ)
# LINEAR (V0+KZ)
#
# V = Vo + kZ
#

Depth Dialog
extern v0,k,last_time,time,last_depth,depth,error
if (indt(v0) || indt(k) || indt(last_time) || indt(time) || indt(last_depth) || indt(error)) {

depth=INDT
} else {
#
# Calculate interval one way time in seconds
#
isoc_owt_secs = (time - last_time) / 2000
if( v0==0.0 && k==0.0) {

depth = last_depth
} else if( k==0.0) {
depth = error + last_depth + v0 * isoc_owt_secs
} else {
tmp1 = exp((k * isoc_owt_secs))
tmp2 = last_depth * tmp1
depth = tmp2 + (v0 / k * (tmp1 - 1))
depth=depth+error
print ("tmp1=" , tmp1)
print ("tmp2=" , tmp2)
print ("isoc_owt_secs=" , isoc_owt_secs)
}
}
For more detail of these options refer to The Language used in Depth Conversion
The PLOT statement in the process methods

Use the supplied PLOT function within your Depth Conversion routine to plot blobs of color to
show where the Depth Conversion is taking place on your profile.

Depth Dialog
Event 2
In the above example the Depth Conversion processes have distinguished between where
Event 2 is an actual ‘pick’ and where it has become the base of a layer. Where Event 2 is the
Current event horizon and it is a real pick, colored ‘blobs’ have been plotted. Where the blobs
have been plotted; an error of
-100.0 has been added.
This displays two features of the Depth Conversion Xpress processes; firstly the ability for
you to select portions of the event horizons to have depth processes (usually errors) added,
and secondly for the window display to plot ‘blobs’ on the event horizon at the points on the
event horizon where the process will act, thus allowing you to see at a glance if the process is
acting as and where you wish.
plot(x,y,color,size) .
For more detail of these options refer to The Language used in Depth Conversion
Negative Datum Handling

In the processing of seismic data, sea level is taken as the line for where time is equal to
zero. In areas of land, especially mountainous regions, a special case is created where the
two way travel times are negative.

Depth Dialog
-400.0
Event 1
-200.0
TWT (ms)
Sea Level 0.0

Event 2
200.0
400.0
The example above shows a theoretical situation where two event horizons have negative
two way times.
Within VelPAK by the inclusion of the following code in the depth conversion formulae most
depth conversion problems can be avoided.
# Check for Negative Time
if (last_time < 0 {
last_time = 0
last_depth = 0
}

Depth Dialog
-400.0 D = -500ft
D = -300ft
At = -400ms
-500
AD= 2000 *2000
-200.0 = -400ft At = -300ms
-500
AD= 2000 *2000
= -300ft
*D = -200ft
IT = -100ms
ID = -100 *4000
2000
= -200ft
Event 1
Sea Level 0.0
IT = 100ms
TWT (ms)
At = 200ms 100
ID= *4000
200 2000
ID = 2000 *2000 = 200ft
D = 200ft
= 200ft
Event 2
IT = 400ms
400
200.0 D = 200ft ID = *8000
2000
= 1600ft
IT = 100ms
100 IT = 300ms
ID= *4000
2000 300
ID = *8000
= 200ft 2000
D = 400ft = 1200ft
IT = 100ms
100
ID = 2000 *8000
400.0 = 400ft
D = 800ft *D = 1600ft D = 1400ft
LAYER 1 AVERAGE VELOCITY = 2000 ft/s

AT = Average Time
LAYER 2 INTERVAL VELOCITY = 4000 ft/s
AD = Average Depth
LAYER 3 INTERVAL VELOCITY = 8000 ft/s
IT = Interval Time
ID = Interval Depth
When calculating this interval, last_time is negative.
D = Depth
To achieve the correct result it is necessary to set
last_time and last_depth to zero.
Diagram to show the calculation of Interval Depths for a theoretical Situation.
As shown in the diagram above by setting the last time and depth to zero, the correct depths
can be calculated. It should be noted that the full interval is not calculated.
This technique fails with the interval method when the second event horizon is also above
zero. The part of event 2 that is above zero is not used in the calculation of the depth for
event 1 (since we calculate depth 1 first, regardless of event 2). An average method must
therefore be used to calculate the depth for event 1 in this particular case.

Depth Dialog
-400.0 Event 1
-200.0
Event 2
Sea Level 0.0
200.0
DEPTH (ft)
400.0
600.0
800.0
1000.0
1200.0
1400.0
1600.0
Results of Depth Conversion using the method described above.

Reint Dialog
Reint Dialog
The Re-interpolation option of VelPAK allows data to be re-interpolated to a smaller shotpoint
increment.
Note: The re-interpolation option never acts on data whose shotpoint increment is already
smaller than the re-interpolated data.
Discussion - Reint Dialog

The reasoning behind doing re-interpolation on data are based in the gridding up of the data.
Take an event horizon that is faulted:
Event points from Workstation Picks

Fault points from Workstation Picks
Output from a Seismic Workstation would naturally have more points picked for the event
horizon than for a fault plane, as in the example above. If the model for this event horizon

Reint Dialog
was output into an XYZ data file to be gridded, control down the fault would not be so great as
for the rest of the event horizon.
Re-interpolation allows you to re-interpolate at whatever shotpoint increment you want to so
that there will be as many points along a fault as along the event horizon.
Event points from Workstation Picks

Fault points from Workstation Picks
Re-Interpolated Points
On selection of the Options within Re-Interpolation you have the chance to select what
shotpoint increment you wish your points to re-interpolate to, and whether you want the re-
interpolation to occur on just the line on display on-screen, or for other selected lines within
the memory model.
Reint Dialog - General Tab
option.

Reint Dialog
Option
Reint_Type -
Current Line - Only the current line will be re-interpolated and then the process will stop.
Un-snapped Lines - Only ‘un-snapped’ sections will be re-interpolated.
All Lines - All lines will be re-interpolated.
Reint_Verify - between each event horizon re-interpolation there will be an alert box
asking you for verification to continue.
Shot_Increment - a value to select for the shotpoint increment you wish to re-interpolate
to.
When all the values have been selected as you wish, pressing APPLY will activate the re-
interpolation. You will see any re-interpolated points appear as white points. They will remain
white until the event horizons are re-displayed, or the data are snapped once more.
Note: Re-interpolation turns the data into ‘Unsnapped, raw’ data again regardless of
whether it has been snapped in the past. If you wish to snap your data you must run
the snap routine (again) on the data. Re-running the snap process should not take a
long time (in editing time) if it has already been snapped once.

Stuff Dialog
Stuff Dialog
The Module ‘Stuff’ is designed to allow you to add an event horizon to your model using
isochron/isopach grids stored within the VelPAK Model Tree.
Note: The grids to be used are always isopachs of some description, not absolute values.
The Stuff Module stuffs layers above or below the selected event horizon.
WARNING:
STUFF WILL MESS UP YOUR MODEL (with regard to Time/Depth relationship)! Make
sure you actually want to do it before proceeding.
STUFF should be the final procedure you do on a Model.
It would probably be recommended that you made a copy of your original model before
proceeding with a STUFF.
The Stuff Module can work on either Time or Depth profiles. Stuff assumes whichever mode -
time or depth - you are currently displaying is the mode to Stuff in.
Stuffing in Time
Your model needs to be snapped before you can Stuff. Adding in a new event horizon will
mean you will need to re-snap your model in order to continue working on the model with
other processes.
Stuffing in Depth
If you are adding depth event horizons via the Stuff Process then you will end up with a model
that has broken the relationship between time and depth - in that you will have depth event
horizons with no time event horizons.
VelPAK warns you of this before you Stuff new depth event horizons.

Stuff Dialog
Stuff Dialog - General Tab
Note: The grids to be used are always isopachs of some description not absolute values.
option.
Option
Stuff Test - Allows you to see what the stuffed event horizon would look like. A visual
white line is displayed where the new event horizon(s) will go.
Tip: Don’t try and zoom on this white line, since it will disappear.
Stuff Type - Select to use your chosen ‘springboard’ event horizon to stuff UP or DOWN
from it.
Stuff Verify - Verify gives alert messages before each new event horizon is stuffed.
Surface_Number - The surface to be used as the ‘spring board’ for the new Event. For
example if Event 2 is selected here and Stuff Type is set to Down then the new event
horizon will be placed between Event 2 and Event 3.
Input
Grid - Select the isopach/isochron grid which is to be used in the Stuff procedure from the
Model Tree or the Surface&Slot selector.

Stuff Dialog
Extrapolation
Ignore Points - The number of points of an event horizon leading into a fault to ignore for
the least square fit equation. Typical setting is 1 to ignore a possible spurious point as the
last point leading up to the fault.
Shot Aperture - Shotpoint Aperture. The shotpoint distance within which to check for
intersections with faults and event horizons - if the ends of (stuffed) segments are outside
this distance they do not generate new points and just terminate where they are.
Use Points - The number of points to use in the least square fit equation to extend/
interpolate the event horizon up to a fault.
Discussion - Using the Stuff Module

What Stuff does at Faults
Simple Fault
A
Stuffed
Layer
Original B
Layer
Simple Fault,
Stuffing one Event
Situation A
The Stuffed event horizon is simply chopped off where it meets the fault.
Situation B
Clearly the stuffed event horizon needs to be extended/interpolated to reach the
fault. This is done doing a ‘least square fit’ on the points preceding the end of the
fault. However, the very last point of the event horizon leading up to the fault can
often be spurious, and so the default is set to ignore the last point. The default
number of points to use to interpolate the event horizon to the fault is four. These
values can be changed in the Stuff General tab.

Stuff Dialog
What Stuff does when it is stuffing a layer that is too thick to fit.
Event 1
Event 2
Isochron to add to
Event 2
The isochron to add to Event 2 in some places is too thick for the thickness
between Event 2 and Event 1.
In this case, VelPAK will chop the isochron where it extends beyond Event 1, thus
truncating the new Event 2 against Event 1.
New Event 2
Event 1
New Event 3

Profile Dialog
Profile Dialog
This option is usually used in conjunction with the generation of a 2D Random Line over your
map data, using the Line Insert Edit mode. See Process for Producing a Random 2D Map
Line.
Once you have your Random line, use the Profile Mode to generate profile data over the line.
Random lines can be generated in Time or Depth.
For Time Profile generation the feeder profiles must be snapped first.
For Depth Profile generation the profiles must be depth converted first.
Profile Dialog - General Tab

option.
Option
Profile_Mode - Specify whether you want the profile generated in Time or Depth. If Depth
is specified, a time profile will also be generated.
Tip: Lines must be snapped for time profile generation and depth converted for depth profile
generation.
Profile_Type

Profile Dialog
Event - Takes the data from all snapped intersecting profile event horizons that the
random line crosses through.
Grid - Takes the data from Grids stored in the selected Model Tree slot for each event
horizon in the model. This would usually be the default TIME or DEPTH slot for the
event horizon (depending on whether it is a time or depth profile you wish to
generate), but any Miscellaneous slot can be activated for any event horizon of
required.
Expert
Multi_Bias - Used to change the default Bias of the joining algorithms when there is
multiple Z values for one shotpoint. See discussion below.
Recalc_Distance - Specify interpolation distance.
Recalc_Shot - When the Profile is generated the original 1,2,3,4,5 style numbering of the
Shotpoints will AUTOMATICALLY be generated using the XY locations. The Re-Calculate
Shot option gives you further control over the interpolation distance if required.
Discussion - Multi Z-value Bias

Used to change the default Bias of the joining algorithms when there is multiple Z values for
one shotpoint.
The changing of the Bias from Up to Down can have a dramatic effect.
Take the following example using the VelPAK display to display just the Faults for the profile
selection of the Multi Z-value Bias Up and Bias Down can significantly improve (or not) the
joining of the multiple faults over the area of the profile.

Profile Dialog
Bias feature executed on

same Fault data with
Bias set differently.
Discussion - Producing Time or Depth profiles from Event or

Grid
First you need to have produced a Random 2D line from the Map Module.
Go in to the Profile Module.
Select Overlay to show Mistie and/or Grid overlaid on the Profile; either from the drop-down
or from the Property Grid. This display would act as a check plot before generating your new
profile.

Profile Dialog
Line Mistie - takes the random line profile data from the other profiles in the model.
Grid Profile - takes the values for each event horizon from the XY point on the Grid stored in
the Time or Depth slot for that particular event horizon in the Model Tree.

Profile Dialog
Mistie Display
Green, Blue or Red lines display the Line Intersections or Grid node points.
Colored blobs represent where the event horizon would be.
Turn the Lines on/off

using the Label option

Profile Dialog
On TIME profiles,
Green line intersections shows an intersection with a SNAPPED line.
Red line intersections shows an intersection with a UNSNAPPED line.
On DEPTH profiles,
Green line intersections shows an intersection with a DEPTH CONVERTED lines.
Red line intersections shows an intersection with a line that is NOT DEPTH
CONVERTED.
Using Grid data to produce a Random Profile

The Grid option takes the data from Grids stored in the selected slot in the Model Tree for
each event horizon in the model. This would usually be the TIME or DEPTH slot for the event
horizon depending on whether you were generating a time or depth profile, but any
Miscellaneous slot can be activated for any event horizon of required.
Activating the Grid display option before generating the Profile will give you a display similar
to a Mistie display of the Grid values for each event horizon for the XYZ of the Random Line
map data.

Profile Dialog
Notes about generating a Random Profile

1. Activating the Apply Profile on any line previously picked will wipe the profile data already
stored for that data and produce a new profile. An alert message does appear warning
you of this.
2. The first display shown on your profile, the Mistie or Grid display option can show a great
distortion of the data, depending on how you have picked the Random Line; and how
many shotpoints it initially has.
If you pick a line like this with the geological structure thus:
1X X
2
X3
The original display on the profile, using misties or grids would space each shotpoint out
like this, below; causing possible distortion of data.

Profile Dialog
X X X
1 2 3
Example on real data:
Picked
Random
Line
Original mistie or grid display using shotpoints number 1,2,3,...
All data bunched

up in one end
Profile generated using true XYs will produce a truer picture, using shotpoint numbers
valid through out the model. These values will remain unless the line and profile data are
deleted.

Profile Dialog
(Mistie lines turned OFF)

XYZ Dialog
XYZ Dialog
This produces up to 3 XYZ files in either Time, Velocity or Depth that will be placed in three
separate user-defined slots in the Model Tree.
Form of Profile XYZ output

The output can accommodate multiple Z-values for any one horizon at any one shotpoint.
The XYZ file will be split according to the Z value being an overthrust/repeat at the same
shotpoint. The file will contain the X coordinate, the Y coordinate, and the Z1, Z2 or Z3 value,
which can either be Time, Velocity or Depth.
The XYZ values are only output for the profile data for the selected event horizon within the
model.
The fault file will not be touched in any way: any flags that have been marked on the section
will also be output as part of the XYZ file format.
This considers the over-thrusting of horizon data that can occur - as shown in the examples
below;

XYZ Dialog
Time 1
Time 2
Time 3
Time 1
In a six Z situation (multiple over-thrusting) - below - the following result will be seen: Time 1
will start again as soon as it can, in order to produce one continuous layer that displayed on a
map.

XYZ Dialog
Time 1
Time 2
Time 3
Time 1
Time 2
Time 3
Time 1
XYZ Dialog - General Tab
option.
Option
XYZ_Type - Time/Depth/Velocity. Select the type of Z value to produced. Time will be
snapped time.
Output
Output_XYZ - Select the slot in the Model Tree where the first of up to three XYZ files will

XYZ Dialog
be put, containing Z1, Z2 and Z3 data in that order. If there are no Z2 or Z3 data then the
subsequent slots will not be filled.

Profile Edit Icons in Detail
Editing Procedures
Insert Delete Edit Move Pick Insert Delete Edit Move Split Merge Swap Flip Void Term
The Profile Edit options within VelPAK are crucial to being able to modify horizon data such
that they can be successfully snapped, and used in applications such as MAP or Depth
Conversion.
Note: You are able to edit not only the time profile, but the resultant depth profiles. However,
if you do this then the relationship between the time profile and depth profile will be
lost.
activated. The bottom right of the VelPAK window displays what edit mode you are in.
Point Edit Options
Insert Delete Edit Move Pick

Point Edit
Insert

This allows you to insert extra points - one at a time- onto a selected horizon.
The event horizon on which points are to be inserted is instantly defined by VelPAK as soon
as you select it from the Surface selector or Model Tree.The cursor must be on a data point
on the event horizon (rather than the line joining the data points) in order for the event horizon
to be found. Keeping the mouse held down, move to where you want the inserted point to be.
Note the different directions of insertion for the left and middle mouse buttons.
Inserts Point Forward

of the selected point.
Original Data
Point
Inserted Data
Held Down Point
Inserts Point Backward
of the selected point.
Held Down
Delete
This allows you to delete points onto a selected horizon.

The mouse must be on a data point on the event horizon (rather than the line joining the data
points) in order for the event horizon to be found. Clicking on a data point will then delete
that point, and jump to the next point on the event horizon.
Note the different directions of deletion for the left and middle mouse buttons.

Deletes point Forward

of the cursor.
Held Down
Deletes point Backward

of the cursor.
Held Down

Edit
Selecting Edit and then a particular data point brings up a dialog box where the values for
this point are displayed.
You can then edit any of the values displayed for this datum point. Pressing DONE will store
these values, overwriting any values generated from anywhere else. Doing another Depth
Conversion, for example, on the data will overwrite these manually edited values.
Move
This allows you to select a point and move it. This is done by using the arrow mouse to select
the point you wish to move, pressing the LEFT-HAND mouse button or MIDDLE mouse
button and keeping it held down to drag the point to where you want it.
Using the Middle button will give you a real time and shotpoint display as the point is being
moved. The values appears in Console

Move
Out
Left or Middle Button Held Down
Display if MIDDLE Button is pressed.
Pick
Point Pick can be used as a method of selecting the event horizon you want to edit. Clicking
on an event horizon in Point Pick mode will change the selected Event in the model, allowing
you to ‘Insert a new Segment’ of that event horizon type, for example.
Pick gives information about the selected point in the Console window.
Shotpoint Velocity Held Down

Number (m/s) Flag & Mask
Velocity Up/ Depth

Event Number Time Velocity Down
or fault name (msecs) (m)
values (m/s)
(if present)
Clicking with the middle mouse button provides a generic browser that displays the Time and
Shotpoint for the current position of the mouse.

Held Down
Segment Edit Options
e Insert Delete Edit Move Split Merge Swap Flip Void Term
Segment Edit
Insert
This allows you to insert a new distinct segment within the current event horizon.
The current event horizon to be inserted can be defined by one of three ways:
1. Selecting the event horizon in the EVENT OPTION page or:
2. Selecting POINT PICK and clicking on an event horizon point or:
3. Selecting the event horizon in the Event Selection list always displayed along the top of
the VelPAK window.
To insert a segment:
On activating the Segment Insert option, the first point of the data can be selected by
clicking and holding down the left mouse button. By releasing the mouse button over the
desired area the end of the segment is specified and the segment drawn.
Delete

This option will cause an entire segment or event horizon to be deleted. Selecting a data
point within a segment will cause that segment to be highlighted.
There will be an alert box asking for verification of the process before deletion takes place.
If you wish to delete only part of an event horizon you can use the Split function described
below to break the event horizon line.
The Undo facility can be used to restore data that should not have been deleted.
Edit
Selecting Edit and then a particular segment of data brings up a dialog box where the
segment name is displayed.
You then have the ability to change this name as you wish.
The LINE BIAS and SEG(ment) BIAS refer to additional biases that can be added to the
whole line or just the segment you have called up to help nudge the snapping routines into
geologically correct snapping.
The Bias is explained in BIASSING THE PROFILE DATA.
Move
Allows you to move an entire segment to another area of the profile.

On activating segment Move, select the segment you wish to move. The segment with be
highlighted. Select a point on the segment and drag it to where you want that point to lie in
the segments new position. On releasing the mouse the entire segment will move to that
position and an alert box will ask you for confirmation of the move.

Split
This option allows a particular segment to be split.

.
x1
Merge
This allows you to merge two pieces of an uncontinous event horizon together.
Data can be merged from left to right or right to left.
On activating the Merge option, the end data point of the segment of data must be found
using the cursor arrow. Keeping the mouse pressed, the arrow is then dragged over to the
other point of the segment to be merged with.
You may find you need to Zoom in to be able to select the Start Point and End Point for the
merge.
A message will appear: ‘Merge specified segments?’ if the data point has been found and the
join highlighted.

Find Start Point

Find End Point of Segment
of Segment
Held Down
Swap
Swap is designed to allow you to swap the priority of segments within a model.
It does not swap the data information for any given segment, merely the number of the
segment.
Usually, the priority of segments within the VelPAK model is from left to right across the
section, and usually this would cause the snapping no problem when it came to following the
layers.
However, when you are dealing with complicated over-thrusting or reverse faulting there may
be a time when you realize that the priority of two segments need to be swapped, to get the
layer following correct.
VelPAK stores the number of each segment and the tracking process see Profile Module -
SNAP Procedure aims to join the segments in order. In the case of complex faulted
overthrusts these segment numbers can be inappropriate.
Use the option under EVENT to activate the DISPLAY SEGMENT NUMBERS to make this
clear. The SWAP facility then becomes quite clear as segments can be swapped such that if
segments are joined in ascending order the appropriate geological situation is achieved.
On activating the Swap option, select the first of the two segments you wish to swap. This will
become highlighted. Then select the segment you want to swap it with. This too will become
highlighted and an alert box will appear asking if you want to swap these two segments.

Flip
The FLIP option provides a reverse snapping direction for an individual event or event
segment.
Note: To flip the whole profile to its mirror image, use the function from the main bank of
Profile Display Icons. Go Here for details.
The example below shows a situation where flip would be used to advice VelPAK as to the
correct way to snap the event horizon.
(Turn on Segment Numbering within EVENT OPTION Dialog)
Snapping Direction
VelPAK ‘snaps’ in the direction of

2
minimum to maximum shotpoint.
C D For this example, VelPAK would
assume that because C occurs
before B, that point C should join
Reverse this point A. By reversing or flipping
1 segment the segment VelPAK will snap
from A to B to C to D.
A
B
0
Void
Voiding a segment allows you to retain a segment within your model, which is not used in any
application or output routine within VelPAK.
The Void option is usually used on small segments of horizons, rather than an entire horizon.
On activating the Void option, the segment to be voided is selected by holding the cursor over
a data point within the required segment.

The segment will turn white, and an alert box will prompt for verification of the process.
Once a segment has been voided, it remains white.

A segment can be ‘un-voided’ by selecting the void section, while in Void Mode, and replying
‘Cancel’ to the Void Alert Box.
Why would I want to Void part of a segment?
Voiding a segment can be an incredibly useful and powerful tool within VelPAK.
When a layer within the model is being tracked along the whole profile, there will be times
when particular layers are absent, either due to fault cuts, unconformity, or on-lapping.
Take the example below:
1 1
1
2
2
In this example, VelPAK would not necessarily know where the event 2 should go;
whether it should track the layer above or the fault below.
The BIAS option could be used to induce the tracking to go down, or up, however it may
be the case that a BIAS of ‘down’ in this particular geological case would cause another
geological case within the same model to behave incorrectly. It is therefore necessary to
be able to define some way of imposing a situation purely for the geological case in hand.
In the above example, a ‘Void’ segment of horizon two inserted at the bottom of the ‘V’ of
the fault block tells the model to track the layer downwards.
When the data are snapped, the void segment is read as normal, and the layer tracking
for the layer two would behave correctly. However, having the segment as ‘Void’ implies
to the model that the data must not be read into any application or output procedure,
since the segment is actually false, (since we know from the original picks that horizon
two is absent within the fault block).
So, in the example given, a Void segment can be inserted within the fault block. This can
be ‘Voided’ so that it shows up as white (on a black background).

Small segment inserted

using ‘Insert’ Mode and
Voided.
Term
Term can be used to terminate an event horizon or segment when data are missing. Upon
snapping, when VelPAK finds a terminated segment, it does not attempt to snap to the end of
the line or to join the ends of two segments together, instead VelPAK draws a vertical line to
the event horizon above.
To mark a section as terminated click Term and select the end of the event horizon or
segment to be terminated. VelPAK then draws a vertical line from this point to the event
horizon above.
Click Once
Click end point
On depth conversion VelPAK ignores the terminated event horizon area and the event
horizons immediately below it.


Fault Module
Introduction
For the creation of Allan Diagrams; fault polygons picked on a Map Display can be selected
and viewed in profile with all event horizon data going into and/or out of the fault.
Theory of Fault Allan Diagrams

What is an Allan Diagram?
An Allan Diagram takes all the Profile faults for a selected Map fault and displays them in an
axis of their own, allowing you to see at a glance the quality of the event horizon picks at the
faults. It is a useful check for snapping errors or interpretation errors at the faults.
By displaying event horizons both coming into and going out of the fault the abutment of the
fault throw can be viewed.

Looking at a Surface
Simplistic Diagram
of the 4 planes of
viewing data
SURFACE
SURFACE
FAULT FU
PROFILE
FAULT
F
F Looking at a Profile
F ILE
ALL F PRO
AN D
IAG.
FL
Looking at a view perpendicular

Looking at a standard Allan Diagram to an Allan Diagram
The standard form of looking at an Allan Diagram is to select the directional axis most
appropriate to viewing the diagram ‘head on’; down the throw of the fault.

However, viewing the view perpendicular to the standard Allan diagram can also lead to an
interesting view of the fault trend. This is possibly viewed best turning off all the event
horizons to be displayed, and just viewing the fault planes.

With event
horizons
displayed
Without event
horizons
displayed
A standard Allan diagram of a fault on random lines which may not be straight would bring all
the lines ‘up’ or ‘down’ to lie on the one flat plane of the diagram. The lines may therefore not
lie at regular intervals along the diagram.
The view perpendicular to the standard Allan diagram would display the faults where they lie.
Profile faults would therefore be hidden behind other Profile faults. Since the display is
‘hollow’ all the profile faults would actually be displayed, but the results may appear
confusing.
What to do with an Allan Diagram

The usefulness of the Allan Diagram is best shown by example.
Example 1
Checking for Snapping or Interpretation errors.

Picking on this point on
the Allan diagram produces This is what is going on
a Profile for that line, with on the profile at this point.
a black line marking the point. (Zoomed In)
Picking the adjacent fault point

which appears to be behaving
correctly:
It appears that in the section that is behaving incorrectly, two

faults have been picked on the profile; the named fault on the
Allan diagram being the left-hand fault. The snapping routines
have tracked down to the bottom of the extra fault where it
reaches the named fault at a greater TWT, whereas on other
Example 2
Checking for Fault Abutments.

A useful and immediate tool for seeing how the fault throws lie for
each event along a fault plane. For this to be truly effective, you
need to have on display the
Thinner lines represent

events going INTO the fault,
thicker lines represent
events leaving the faults.
In the example to the right,
the layer created by the
orange at the top, and the
yellow at the bottom going
into the fault is entirely
disconnected from the layer
leaving the fault.
This can be seen on the
profile for one of the lines
displayed in the Allan
Diagram.
Meanwhile, the layer
Summary of Steps for the successful creation of an Allan

Diagram
1. Have Map Fault Polygons on your map for all or selected event horizons. These can
either be drawn in on-screen, or read from a data file imported into the Faults section of
the Model Tree.
2. Make sure that the Map Fault polygon points exactly snap onto the Fault Flags displayed
on your map surface from the Event Profile. (Snapped points will appear red, unsnapped
points will appear black.)
3. Name your Map Fault Polygons and joining Profile Fault Polygons.
4. In the Fault Module, select your named Fault from the top of the dialog Fault display. Turn
on the Event Horizons you wish to have displayed from within the Fault Module Display
dialog. Press Fault display.

Display Options
Display Options
Event Well Fault
Event, Well or Fault within the VelPAK
model.
Display Types
Time/Depth - Displays the diagram in either time or depth as the Y axis.
Note: the data would need to have been depth converted for the depth display.
Visible Layers
Only Faults can be selected as a visible layer in the Fault Module.
Edit Mode Options
The only mode available is Line pick mode, with the only edit option available Fault Segment
Pick.

Display Options
FAULT SEGMENT PICK

When you have your Allan diagram displayed, the cursor is always in ‘Fault Segment
Pick’ mode; that is, clicking the cursor on one of the Faults will give you the corresponding
profile, with a black line running down the profile showing you where the fault is that you
picked.

Display Options
Clicking On Fault..
..will give you the profile with a black line at that point
Tip: The Allan diagram display supports full Zoom facilities.
Fault Dialog
Fault Dialog- General Tab
option.

Display Options
Display
Display_Type - Choose to display faults in Time or Depth.
Option
Line_Label - Choice of labelling displays which best suits the density of data you are
displaying.
Line_Type - Choose which set of lines to choose. The choice here between in-lines or
cross-lines would affect the directional axis required for a standard Allan diagram.
Random is also available as an option.
View_Direction - You have the option of selecting the best directional axis in which to
view the fault plane ‘head-on’; along the throw of the fault. The other directional axis can
be selected to view the display perpendicular to the standard Allan diagram.
For example; Viewing South - North instead of North - South would simply ‘flip’ the display
you see.
A standard Allan diagram of a fault random lines which may not be straight would bring all
the lines ‘up’ or ‘down’ to lie on the one flat plane of the diagram. The lines may therefore
not lie at regular intervals along the diagram.
The view perpendicular to the standard Allan diagram would display the faults where they
lie. Profile faults would therefore be hidden behind other Profile faults. Since the display is
in fact hollow, all the profile faults would actually be displayed, but the results may appear
confusing
.
VIEW NORTH-SOUTH
Standard
‘Head-On’
directional
axis chosen
(Same Data)
VIEW EAST-WEST
Perpendicular
to standard diagram
directional
axis chosen
Overlays
Overlays_Into - Yes/No
Overlays_Leaving - Yes/No
Choose to have just one set of lines on the display for event horizon data for one side of

Display Options
the fault plane, either going into the fault as displayed, or leaving the fault (depending on
the directional view selected) or have both set of lines displayed, showing faults going
into and leaving the fault.
If ‘Yes’ is selected for both, the thinner lines will represent event horizons going INTO the
fault, thicker lines represent event horizons LEAVING the faults, according to the
directional view selected.
Event going
INTO fault
Event
LEAVING fault
Fault Dialog - Select Tab
option.

Display Options
Display
01_Display/02_Display - Yes/No options allowing you to select the event horizons you
wish to display.
The default is to just display the profile fault planes. You can if you wish turn these fault
planes off and just view the event horizons.

Tips and Advise for producing Allan Diagrams

Detailed account of producing a perfect Allan Diagram display
How to insert a Map Fault Plane
1. In the Model Tree select the event horizon you want to draw the Surface Faults on.
2. In Surface Module, turn the Visible Layers on for Flag data, including labels, and Faults.
You may or may not also want to have the line locations displayed.
.
3. Select Fault from the Edit Mode and then Segment Insert.

4. Use your cursor to click on every Fault Flag location you wish to include in your fault
plane. You may well need to zoom in close to be sure you are getting the fault plane
points close enough to the flag points for them to be successfully snapped onto them.
5. Use the Fault POINT MOVE option to move the fault segment points you have just
inserted to snap onto the Fault Flag points. Black, unsnapped Fault Plane points will turn
red when they are snapped onto the points.
This point is successfully

snapped onto the Flag ‘FU’
with the Fault point displaying
as red.
This point is not snapped onto

the Flag ‘FU’; the fault point is
displayed in black.
Note: You can change the range for this Fault snapping process to pick up on faults, and
you can even turn the automatic snap feature off altogether, all available from the
Surface Display General dialog. Go there.
A useful check at this point to see if all your points are snapped is to turn all the
displays OFF on your Map, apart from Fault. You will then see at a glance if any fault
points are black and not red.
6. NAME your fault segment/plane using the Segment Edit option. Select this option and
then click on a data point for the Fault Plane you wish to name. The following alert box will
pop up.

This option will name/rename not only the Fault Plane you have just defined, but will
also rename the profile faults for that plane, if you answer ‘OK’ to the alert box that
follows. The Profile faults must be named the same as the Map fault for the Allan
diagrams, under the Fault Module, to work successfully for all profile faults along the
plane.
When you have your Map Fault Polygons defined

• Go into the Fault module.
• Select the named fault from the list in the Model Tree.
• Go into the Fault Display Dialog and select whether the best view to be perpendicular to
the throw of the fault is North-South or East-West. Under the Select tab, select which
event horizons you wish to have displayed on your Allan diagram, and:
• Press the Apply tick at the top of the Fault Display dialog.

Errors that can occur in your Allan Diagram display
Situation 1
Situation 1 - referring to the diagram above.
Clearly on a 3D survey it becomes easily apparent that some lines are not being
displayed on the Allan Diagram.
Reasons for this:
1. The simplest reason is that the fault flag on the missing line(s) has not been picked, or
that the flag has been picked but the pick was not close enough to the point for it to be
automatically snapped onto it. (Turning the black Map Fault Plane point to red).
To solve this, go back the Surface display and edit / insert the Surface fault plane points.
2. The Profile Faults for the missing line(s) are not the same name as the Surface Fault
Plane. The profile faults should be automatically named the same if you answer Yes to
the prompt when you come to name your Surface Fault Plane. However it is possible to
re-edit the names of these profile faults (especially if you are selecting more Surface
Map Fault Planes for another event horizon and the same profile fault is selected).

To solve this, in Profile mode do a segment edit on the profile fault not appearing and
change its name manually.
Situation 2
Situation 3
Situation 2 - referring to the above diagram.

This is not necessarily an error. In this case a fault that further along the display is a
long deep fault which cuts through many event horizons has after three lines turned
into a smaller shallower fault which only cuts through one event horizon.
Situation 3 - referring to the above diagram.
The wrong fault flag has been picked when inserting the Surface Fault Plane, and so
the wrong Profile fault has been named. Find the profile at fault and manually re-
name the correct profile fault.
Do this by using the Line Pick option on the Allan diagram on the fault with the
problem. The profile will be displayed with a black line through the profile where
picked on the Map.
On the profile you can then use Segment Edit on the faults on display to see what
their names are.

Hints if an error occurs in your Allan Diagram display

1. Detach each module window
It is often handy to detach the Profile module, the Surface Module and the Fault Module
so that you can see the situation from every angle at once.
2. Display only the faults in the Surface Module
In the Surface Module, where you are looking at your Surface Map Fault turn all the
displays OFF on your Map, apart from Fault.
You will then see at a glance if any fault points are black and not red. This means they are
not snapped. This check can be further enhanced by using the Fault+Labels option so
that the names of the faults are displayed on your map.
Spot the black, unsnapped point
3. Display the names of the fault segments on the Profile

To check the names of your profile faults, go into Profile display and in Event Options turn
on the ‘All Event Numbering’ or ‘Current Event Numbering’ (depending on how busy your
profile is).
This will display not only the segment numbers and direction of the event horizons, but
also display the names of your profile fault segments. This gives a very quick method of
checking exactly which profile fault has actually been picked, and moving through
Previous and Next profiles you can see quickly if a different fault has been inadvertently
named on one (or more) profile.

Surface Module
Introduction to Surface
The SURFACE Module displays and analyzes data with XY co-ordinates.
Surface displays - basemaps, ribbon maps, contour maps, filled contour maps.
Gridding - of selected event horizons or of XYZS stored in the INFO page, with the
option of using various Gridding Methods.
Processing - for the manipulation of produced grids, multiplying, adding etc. grids
together or with constants to produce new grids. Also a whole host of other processes are
available including Grid-to-Grid depth conversion. Or ‘Create-your-Own’ methods.
Depth Conversion - Layer Cake Depth Conversion, using either pre-stored methods or
user-defined methods, utilizing Constants, Grids, Curves and a large number of standard
formulae. Generation of Vup and Vdown information.
Inserting, Moving And Editing - Surface Data types in your model. For example,
inserting a Surface fault pattern, drawing polygons, moving XYZ points and grid nodes.
Viewing the XYZ location for a selected point.
Random Surface Line Profile Generation - Using Snapped profiles a random 2D line
can be inserted on the Surface data. A minimum of 2 lines must be defined. Line names
and Shotpoint ranges can be defined.

Display Options
Display Options
Event Well Line
Event, Well or Line within the VelPAK model
Display Type
Select type of Surface display to view.
Basic Surface
The Basic option displays on-screen a basemap stick plot of the surface data within the
memory model, along with an XY grid around the surface.
Selection of a new profile to be displayed in the memory model can take place by pressing
the mouse on the required, displayed, line.
The color varies on lines over the area depending on the line’s current state:

Display Options
The current line is displayed blue.

Lines displayed Red have NOT been Snapped yet.
Lines displayed a “dull” green have been Snapped.
Lines displayed gray have no profile data associated with it.
Lines displayed as a lighter or brighter green shade have been selected for other
mapping purposes. For details of how to make selections Go Here.
Ribbon Map
This will construct a polygon of color varying with the time/velocity/depth values that are
posted along a seismic line.
You DO NOT need to SNAP your data before displaying it as a Ribbon Map.
The size of each polygon, and hence the thickness of the color ribbon along each seismic line
is defined by the value at which the ‘ribbon value’ on the options dialog is set.
• Select the type of Ribbon map you wish to display; Snapped, Unsnapped or Merged
Time, Velocity or Depth or XYZs from the Surface Dialog page.
The Ribbon Size Scale Bar allows the ribbon thickness to be changed. These values are
simply relative to each other; a value of 1 will produce a smaller ribbon than a value of 5.
Contour Map
The Contour Map option provides an on-screen contour display, with or without basemap
details according to the set up.In order to produce the contour map VelPAK uses the gridding
parameters specified within the GRIDDING Dialog.

Display Options
Tip: The Contour Map display supports full Zoom facilities.
Shaded Contour
The shaded contour map produces a map display similar to the one shown below.
The shades of colors used are selected on the Surface Dialog.
The colors are according to the color shading table selected. A key down the right-hand side
of the display shows what values the colors represent.
There is the option for gray shading if you want to produce a hard copy display on a black and
white printer.
The contour interval required is defined on the Surface Dialog.

Display Options
Overlay Layers Visible Options
Display off
Display on
Label off
Label on
Turn Display element ON or OFF for display on the Surface. With or without element labels.
Displaying one or all of these display types will give you the option of EDITING, INSERTING
or MOVING points and/or segments (depending on what type of data you are actually in) Go
here for details of these procedures.
Note: These layers can also be made visible or not via the Surface Display General
Property Grid.

Display Options
Overlaying/Displaying the Different Elements Types

Layers Visible - XYZ, Fault, Polygon, Grid Display
Displays the selected points or the selected points and actual values associated with the
points over your map.
Data stored - or created - as Fault or Polygon data will have lines joining data points of the
same segment.
XYZ DISPLAY WITHOUT VALUES
XYZ DISPLAY WITH VALUES (zoomed in)
Select XYZ, FAULT, POLYGON or GRID from the Layers Visible drop down. Select the
relevant label from the Layers Visible drop-down to see the values for that element.
Note: This option is intrinsically linked to the Model Tree and Surface&Slot selector. In order
to get your values displayed (be they points or points and numerical values), you need
to select the relevant input on the Model Tree or Surface&Slot selector under the
relevant event horizon.
For example:

Display Options
Interval velocity XYZ values will be

displayed on Surface Display
Note: You must have the same event horizon selected on the Model Tree/Surface&Slot
selector for a surface to be displayed with this selected information on it.
Layers Visible - Seismic Line Display

Displays the Basemap information on your selected surface map.
If you only want to display a line location basemap of your area, then this option will definitely
have to be switched on (but note that the posted value option does not display any values on
a basemap).
If you wish to display a contour map or a shaded contour map, you may well not want to view
your line locations on top of the contours.

Display Options
Contour Map with

Line Overlay ON
Layers Visible - Flag Display

Displays Event Horizon FLAG information on your basemap. This is the flag information that
the snapping routines of VelPAK have put in when particular situations have occurred on the
profile data for the particular event horizon, for example FU for a Fault Upper contact and FL
for a Fault Lower contact.
The flag information can be displayed over an area without the basemap line information
necessarily being displayed.
Requesting the Flag overlay information to be on, without labels, will give you spotted points
for where the flag information is.
Requesting points with labels will give you a display with the flags marked too.

Display Options
Line Location Overlay +

Event Overlay, no values
Line Location Overlay +

Event Values ON
No Line Location Overlay

Event Values ON.
Layers Visible - Stack Display

Displays the STACK data on the basemap.
Use Point Pick Mode to get information displayed in the console window of VelPAK.
The left-hand mouse button will give you full Stack Information for that point.

Display Options
The full Stack Information will display the Line Name(Inline) and Shot point and the
following information for that point.
DEPTH TIME AVERAGE RMS ORIGINAL TYPE

VELOCITY VELOCITY CODE
Type -
Old(dix) = 0
Average =1
Interval = 2
RMS = 3
Unknown = 4

Display Options
Layers Visible - Well Display

Displays Well Locations with/without Well Names (by turning the Label overlay on/off).
Well Locations displayed using this feature will be displayed through all event horizons.
Deviated Well track information is taken from the Curve file, and therefore can/will be
displayed on activating the well Deviation Overlay.
A Black Well
is your currently selected well. On selection, any colored well will turn black. The well will
return back to the original color on de-selection.
A Green Well
Means there are:
TOPS and
CURVE data stored for that well in the Model,
and the layer has been defined for this event horizon either in Time or Time and Depth.
See The Well Log Module.
An Orange Well
Means there are:
TOPS and
CURVE data stored for that well in the Model, but the layer has not been defined for
the selected event horizon.

Display Options
A Blue Well
Means there are
No TOPS but either a real or a dummy CURVE for that well in the Model.
Layers Visible - Top Display

Turning this display option on will display the location and name of the picked tops on the
well curve track.
Turning on the Value Display will give you the names of all tops held for that well.
Layers Visible - Deviation Display

If deviated, the Well Deviation track can be displayed on your basemap by turning Curve
Overlay on.
Turning on the Label Display will give you the XY points for the deviation as shown below (on
a fictitiously deviated well).

Display Options
Edit Mode Options
Turn data elements ON for editing and selection on-screen using Edit. See Surface Edit
Icons (below) for details. Default is None so no Edit type will be selected.

Surface Edit Icons
Surface Edit Icons
Insert Delete Edit Move Pick Insert Delete Edit Move Split Merge
Note: The Edit Icons will be shown as ACTIVE depending on what Element of data you are
editing. Select the Element from the Mode Drop-Down. If the Edit Icon is grayed out
then it is not available as an Edit method for that Data Element.
Each data type available for display within the Surface Module also has various edit facilities
associated with it.
These are used not only to EDIT or MOVE data points on-screen but also to INSERT new
data points or segments of data such as Fault Planes or Polygons.
Random 2D lines can also be added to the model through this method. See Random Line
Generation.
The actual edit procedures for Points and Segments appear in the same form as they do for
Event Profile editing; however you will notice that not all edit procedures are available for all
data types.
The middle mouse button on Point Pick mode for some (not all) data types will give you an
extended data listing in the Console.
See individual data type editing below for details.
Note: To successfully use the edit procedures for each type of data, make sure the data
type display you want to edit is switched from the Edit Mode drop-down. If it is not
turned on, VelPAK will prompt you to switch the data type on for you.

Surface Edit Icons
Selection/De-selection of Lines and Wells

Line selection for Ribbon Maps
Selection is by pressing the middle mouse button while in Line Point Pick Mode.
De-selection of a single line is also made by pressing the middle mouse button.
De-selection of all your selected lines can be done from the relevant options on the
top of VelPAK. From this same drop down you can invert your selection; de-selected
lines become selected and vice versa.
Deselect Invert
Lines
Profile selection for 3d displays
Selection is by pressing the CTRL key on the keyboard along with the left mouse button
while in Line Point Pick Mode.

Surface Edit Icons
Any number of lines can be selected for display as profiles on the 3d display.
Whatever the display type is set to be on the Surface-Display-General tab (Inline/
Crossline/Random/All) this will be the type of line available to you for selection for display
your 3D profile.
Wells
This option is only for selecting or inverting your selection of wells for display on a 3D
display.To select wells use the Edit Mode Well -> Point Pick and as in the profile selection
above, use the Ctrl Button on your keyboard and the left hand mouse button to select or de-
select the wells you wish to view in the 3D display. Use the Deselect or Invert icons to
deselect or toggle (invert)your entire selection.

Surface Edit Icons
Deselect Invert
Wells
Saving Your Edits

Inserting, editing or saving surface data types affects the VelPAK Model Tree.
For data that you have already stored in a VelPAK binary model, all the surface data points
you see will be called up to display from the selected slot within the Model Tree.
If you make any changes to the data points on-screen, the slots containing the data points in
the Model Tree will automatically hold the changed data. On saving your VelPAK binary
model, these slots will contain the changed data files.
For information that you are creating/inserting on-screen, a default slot will automatically
store the data, unless you specifically highlight another slot within the Model Tree for your
data to go in. The default slot would usually be the first slot (‘Time’) to occur in the Model Tree
for the particular type of data you are inserting...but if you go into the Model Tree before
starting the insertion of points and select another slot for the type of data you are about to
enter then the data will fall into that slot.
Remember that to see hidden/unused slots in the Model Tree you need to expand the Tree
using the icon at the top:
It is not necessary to have to assign a name to your data in the Model Tree slot, but if you
have many different fault patterns, for example, these would all be stored under different slots
of the Model Tree, to keep them separate, and you may find it easier to name them to keep
track of them.

Surface Edit Icons
To export these internally created files you need to use the File - Export options from the top
menu of VelPAK. Selecting the correct data type to output will place and external file in a
selected directory.
See Data Export.
XYZ Edit Mode
Select XYZ to Edit from MODE
Point
Insert DeleteEdit Move Pick
There are no SEGMENT

EDIT options for XYZs.
Edit facilities available for XYZ are, by their nature, all POINT edit options.
Insert
Allows you to add XYZs to your model. In this mode, click on the window where you want
a new XYZ to be, and the following box will appear, asking you for a value for your new
XYZ point.

Surface Edit Icons
Delete
Deletes XYZ points by clicking on them on the window. No alert will come up for
confirmation of this process...proceed with caution!
Edit
Edit your XYZ by clicking on your selected XYZ point. The following box will pop-up for
you to change the value as required.
Move
Click down on your selected XYZ and keeping the mouse button depressed, drag your
XYZ over to its new location. No alert will come up for confirmation of this process, and no
undo function is available..proceed with caution!
Pick
Will bring up information of your selected XYZ point. The information is the X,Y location,
the Z value and the PNT is the line in the data file your selected XYZ is on.

Surface Edit Icons
Fault Edit Mode
Select FAULT to Edit from MODE
Point Segment
Insert Delete Move Pick Insert Delete Info Move Split Merge
For Editing Surface Fault planes but also for INSERTING new surface fault planes and the
FAULT module (display of Allan diagrams).
For Surface Fault Planes to be used successfully within VelPAK for Allan diagrams, when
inserting fault planes the points must be SNAPPED to the flag markers from the Event
Profiles. The snapping takes place automatically if you get the surface fault point close
enough to the Event Flag point. (The snapping mentioned has no connection to the VelPAK
snapping module.)
These edit options react in a similar way to the Event Module Point and Segment options. For
details of how to use any of the options (for example how to insert to the left or to the right of
the point you are on) see Profile Edit Icons in Detail.
Point Insert
This allows you to insert extra points - one at a time - onto a selected fault plane.
Point Delete
This allows you to delete points from a selected fault plane.
Point Move
Moves fault plane points. In this case usually towards an event horizon flag point. Moving
the fault plane point to within a short distance of the event horizon flag point will cause the
fault plane point to automatically snap onto the event horizon flag point, which is the
desired effect for the Fault module. Fault plane points that have successfully snapped
onto the Flag point appear red; ones that are only ‘close, but not touching’ appear black.
Point Pick
This gives information in the status bar (and also in the Console window if it is open)
about a selected surface fault point within the display.

Surface Edit Icons
Segment Insert
This allows you to insert a new Surface Fault segment on the current event horizon. This
would usually involve joining Flags from the Event Profile marked on a basemap to create
a new Surface Fault plane.
On activating the Segment Insert option, the first point of the data can be selected by
clicking and holding down the left mouse button. By releasing the mouse button over the
desired area the end of the segment is specified and the segment drawn.
For full details of this important option see How to insert a Surface Fault Plane.
Segment Delete
This option will cause an entire fault segment to be deleted. Selecting a data point within
a segment will cause that segment to be highlighted.
There will be an alert box asking for verification of the process before deletion takes
place.
If you wish to delete only part of a fault you can use the SPLIT function described below
to break the surface fault.
Segment Info
Selecting Info and then a particular fault segment will bring up a dialog box where the
segment name is displayed.
In order for the Fault Module to work successfully, your Surface faults must have a
designated name. On changing the name in this dialog box and pressing OK, the
following alert will appear:

Surface Edit Icons
Replying ‘OK’ to this will name/rename not only the Fault Plane you have just defined, but
will also rename the profile faults for that plane (providing your fault plane points have
been successfully snapped onto the flag points such that they appear RED on the VelPAK
display). The Profile faults must be named the same as the Surface fault for the Allan
diagrams, under the Fault Module, to work successfully for all faults along the plane.
Segment Move
Allows you to move an entire fault to another area of the surface.
On activating the segment Move, select the fault segment you wish to move, by selecting
a point on the segment, and drag it to where you want that point to lie in the segment’s
new position. On releasing the mouse button the entire segment will move to that position
and an alert box will ask you for confirmation of the move.
Segment Split
Allows you to split a designated fault segment. Select the point you wish the fault to be
split at.
An alert box will ask you for confirmation of this action.
Segment Merge
This allows you to merge two uncontinous faults together.
On activating the Merge option, the end data point of the segment of data must be found
using the cursor arrow. Keeping the mouse button pressed, the arrow is then dragged
over to the other point of the segment to be merged with. A message will appear “Merge
specified segments’ if the data point has been found.
The NAME of the fault will be taken from the fault segment picked on first, to merge with
the other segment.
How to insert a Surface Fault Plane

Select the Event Horizon you are going to insert the Fault Plane on from the Model Tree.
In Surface Display select the Fault, Flag+ Labels Overlay Display. You may or may not also
want to have the Seismic line locations displayed.

Surface Edit Icons
Line Location Overlay + No Line Location Overlay

Fault Values ON Fault Values ON.
Also make sure you are in Fault Edit Mode.
Go into the Surface&Slot selector (or Model Tree) and for the event horizon you are working
in select the slot under the Faults slot you wish these data to be stored in. If you do not select
a slot then the data will default to being in the first slot (Time). You do not need to assign a
name to this slot yet - or ever if you wish - but it is useful to name it eventually to keep track of
what that slot within the Model Tree page holds.

Surface Edit Icons
Select FAULT SEGMENT INSERT. Use your cursor to click on every Fault Flag location you
wish to include in your fault plane. You may well need to zoom in close to be sure you are
getting the fault plane points close enough to the flag points for them to be successfully
snapped onto them.
Use the Fault POINT MOVE option to move the fault segment points you have just inserted to
snap onto the Fault Flag points. Black, unsnapped Fault Plane points will turn red when they
are snapped onto the points
.
This point is successfully

snapped onto the Flag ‘FU’
with the Fault point displaying
as red.
This point is not snapped onto

the Flag ‘FU’; the fault point is
displayed in black.
Note: You can change the range for this Fault snapping process to pick up on faults, and
you can even turn the automatic snap feature off altogether from the SURFACE
Dialog. Go there.
NAME your fault segment/plane using the Segment Edit option. Select this option and then
click on a data point for the Fault Plane you wish to name. The following alert box will pop up.

Surface Edit Icons
This option will name/rename not only the Fault Plane you have just defined, but will also
rename the profile faults for that plane, if you answer ‘OK’ to the alert box that follows. The
Profile faults must be named the same as the Surface fault for the Allan diagrams, under the
Fault Module, to work successfully for all profile faults along the plane.
Polygon Edit Mode
Select Polygon to Edit from MODE
Point Segment
Insert Delete Move Pick Insert Delete Edit Move
For INSERTING new polygons and editing existing ones.

These edit options react in a similar way to the Event Module Point and Segment options. For
details of how to use any of the options (for example how to insert to the left or to the right of
the point you are on) see Profile Edit Icons in Detail.
Point Insert
This allows you to insert extra points - one at a time - onto a selected polygon (already
existing).
Point Delete
This allows you to delete points within a polygon.
Point Move
Moves polygon points.
Point Pick
Brings up information about a selected surface polygon point within the display.

Surface Edit Icons
Segment Insert
This allows you to insert a new polygon on the current event horizon.
Note: The last point inserted always joins up with the first point of the polygon. Each
polygon created will be one complete and separate ‘segment’ on the display.
Segment Delete
This option will cause an entire polygon to be deleted. Selecting a data point on a polygon
will cause that segment to be highlighted.
There will be an alert box asking for verification of the process before deletion takes
place.
Segment Edit
Selecting a particular polygon from a number you may have displayed for that event for
that Model Tree Data type will bring up an alert allowing you to name that polygon - or see
the name of the individual polygon if it had been brought in from your original project.
Individual named polygons can be used within the Analyze module.
Segment Move
Allows you to move an entire polygon to another area of the map.
On activating the segment Move, select the polygon you wish to move, by selecting a
point on the polygon, and drag it to where you want that point to lie in the polygon’s new

Surface Edit Icons
position. On releasing the mouse button the entire polygon will move to that position and
an alert box will ask you for confirmation of the move.
Grid Edit Mode
Select GRID to Edit from MODE
Point
Delete Edit Pick
No SEGMENT EDIT Features
Edit facilities available for Grid nodes are, by their nature, all POINT edit options.
Delete
Changes the GRID node value to Indeterminate (INDT) by clicking on the selected node
on the window. The grid node will turn from being blue to being purple. No alert will come
up for confirmation of this process...proceed with caution!
Edit
Edit your Grid node by clicking on your selected node on-screen. The following box will
pop-up for you to change the value as required.
Pick
Brings up a hover window over the points dynamically over the grid.

Surface Edit Icons
Seismic Line Edit Mode
Select SEISMIC LINE to Edit from MODE
Point Segment
Insert Delete Edit Move Pick Insert Delete Edit
Note: Unlike all other display elements Line data does not need to be switched on/displayed
to be able to use Point Pick to pick a line. This is due to the large volume of data that
can occur with line data; you may not always want to see it all even though you want
to pick from it.
Used for INSERTING 2d Random Lines into your model. Go to Details.

Also used for selecting and viewing the Profile for the line picked.
Point Insert
This allows you to insert extra points into line surface data.
Point Delete
This allows you to delete points from your line surface data.
Point Edit
This allows you to edit points in your line surface data.
Point Move
This allows you to move points in your line surface data.
Point Pick
Selecting this will allow you to select and view the Profile for the line picked.
Use the left-hand mouse button to select your line in Profile. Use the middle button to
select the line for selective display procedures, such as Fence Diagrams.
Segment Insert
This allows you to insert a 2D Random line into our model. See Process for Producing a
Random 2D Surface Line Default line name is ‘None’.
Segment Delete
Deletes individual lines of data. An alert message will warn you that this will take place.

Surface Edit Icons
Segment Edit
Select the Edit Info option on the random line you have just created to rename the line as
you wish.
Process for Producing a Random 2D Surface Line

1. Go into Surface Module.
2. Select Seismic LINE Segment Insert.
Select SEISMIC LINE to Edit from MODE
Segment
Insert
3. Use left hand mouse button to insert your Random line over your data area.
4. The name of your line will default to be ‘None’. Select the Edit Info option on the line you
have just created and rename the line as you wish.
Segment
Info
5. You now have a line with as many shotpoints on as points you have drawn. There will be
a blank profile attached to this line, to produce the Random profile, you need to go in to
Profile mode. See Profile Module - Profile Mode.

Surface Edit Icons
Note: Random Profile generation works by taking the data from SNAPPED profile data,
only.
X
X X
Random Line X
Inserted
Event Flag Edit Mode
No Edit Options available
There are no options to edit event horizon data from within the Surface Module.
To edit profile data you would need to go into the Profile module.

Surface Edit Icons
Velocity Edit Mode
Select Velocity to Edit from MODE
Point
Delete Pick
For deleting Velocity Stack Points and reading velocity information on individual points.
Pick
Using the left-hand mouse button on Point Pick to bring up all the information for that
point.
Edit
Select the stack point: usually only used to change the stack point’s Fit status to be active
or inactive in the Optimize and Curve modules.

Surface Edit Icons
Well Location Edit Mode
Select WELL LOCATION to Edit from MODE
Point
Insert Delete Edit Move Pick
No Segment Options
For editing aspects of the Surface Well displays and displays under the layer definition for the
selected well. New Well locations can also be INSERTED from here.
Insert
Select the point where you want to insert a well or select a well to edit and press the
mouse button. This Insert dialog will appear allowing you to assign the name to the well
and also to fine-tune the XY Location as required.
Delete
Select the well you want to delete. An alert will appear for confirmation.

Surface Edit Icons
Edit
Well Edit is used to not only edit the XY location or name of a well but also the status of
the well.
Also the value (Yes or No) for the well’s Fit and/or Residual values can be made active or
inactive in the Optimize and Curve modules.
The well selected can be assigned in a particular group.
Deselect Layer? Yes/No - will deselect the layer for the current event layer displayed in
the Surface module (and shown at the top of the Edit dialogue box).
Note: Deselection of the layer can not be undone. It will need to redefined in the Layer
Definition module.

Surface Edit Icons
The layer will be deselected in the Well Module and in the data tab of the Optimise
module:
Move
Select the Well and drag it to where you want to re-locate it.
WARNING - No alert appears for confirmation about the move, and there is no UNDO
facility.
Pick
Hovering over the well location in Pick mode will show you information about the well.
Clicking on a well using the left-hand mouse button will select it and change the display in
the Well module to that well.

Surface Edit Icons
Well Top Edit Mode
Select WELL TOP to Edit from MODE
Point
Pick
Only Point Pick is available.

Point Pick
Using the left-hand mouse button on Point Pick mode gives a pop-up with information for
the well and the tops associated with that well.

Surface Edit Icons
Deviation Edit Mode
Select DEVIATION to Edit from MODE
Point
Pick
Only Point Pick is available.

Point Pick
Using the left-hand mouse button on Point Pick mode gives information at the bottom of
the VelPAK window.

Surface Edit Icons
Selecting Basemap lines; the Deselect and Invert Options
Deselect Invert
Lines displayed as a lighter or brighter green shade on the map have been selected for
mapping purposes.
DESELECT
Will deselect all basemap lines selected.
INVERT
Inverts your selection of lines. All your selected lines will become deselected and vice-
versa.
Single line selection and de-selection is by pressing the middle mouse button while in
Line Point Pick Mode.

Surface Display Dialog
The Surface Dialog under Surface Module deals with the display style and set up of surfaces
to be displayed in the VelPAK Surface Module window.
Tabs include:
General tab - Basic set up details for particular maps.
Range tab - The definition of how the range the Surface display will show is selected.
Color tab - Changes the color of various items on the Surface.
Mask tab - The setting up of the MASK value within VelPAK which allows a unique
number to be given to any geological situation occurring within the memory model.

option.
Parameter - - Calculates the Contour Increment taking the Z range of the data on
display. Pressing this will automatically update the Contour - Contour_Increment value
further down this Property Grid. Roughly speaking the contour increment is calculated to give
you approximately 25 levels between the minimum and maximum irrespective of the
magnitude of the range; computed to be a number divisible by 2, 4, 5, 10 etc. or the inverse of
this if the number falls between 0 and 1.
Option
Display_Type - Same selection as Display Type drop down on main Surface window. Go
Here for details.
Line_Type - Random/ In-lines/ Crosslines/ All/ Current

Select the type of lines you wish to have displayed on the surface display. This also
makes the Line Type selected available for selection from your surface display to be
shown as a profile on the 3d display.
Spacing_Inline /Spacing_Outline - Gives control of inline and crossline spacing for
clearer displays
Well_Box - Yes/No - draws a white box around the Well Label to be able to read the label
on a busy map.
Well Box On Well Box Off

Well_Type - Select type of wells to display - normal or stack wells (pseudo-wells)
produced from the Amalg option.
XYZ_Box - Yes/No - draws a white box around the XYZ Label to be able to read the label
on a busy map.
XYZ Box On XYZ Box Off

Contour
Contour_Auto - Automatic computation for the grid contour for each grid displayed.
For existing models, this is set to No. For new models, this is defaulted to Yes.
Yes - the grid contour increment is automatically computed for each grid displayed.
No - the Contour_Incr value is used for the contour increment on each grid displayed.
Contour_Color - Choose the stored color table to best suit your display. Click on the box
Contour_Increment - Choose the increment that best suits the contouring of your data.
Contour_Smooth - A smoothing algorithm that can be used to make maps with large
grid cell spacing smoother. Note this option does not work on Faulted data.
Fault
A feature for the insertion of Surface Faults on your surface. See Inserting Surface Fault.
Fault_Aoi - Allows you to increase or decrease the range on your map that the fault
snapping option works. The measurement is in metres on the ground, with the default set
to 25m.
Fault_Snap - Yes/No
Allows you to turn the whole automatic fault snapping process on or off. If this is set to No

points inserted that are close to Surface Fault point will not automatically snap to the
point.
Ribbon
Ribbon_Size - Select the ribbon thickness. These values are simply relative to each
other; a value of 1 will produce a smaller ribbon than a value of 5. Default of 3.
Ribbon_Type - Time/Velocity/Depth/XYZ
Select the type of Ribbon map you wish to display. These data can either come from
Profile data (Time, Velocity or Depth in Snapped or Unsnapped or Merged mode) or and
XYZ slot that has been selected from the Model Tree or Surface&Slot selector.
For a discussion of Snapped, Unsnapped and Merged Data, Go Here.
Volumetrics
Spill_Crest - None/Spill/Crest/Both - if selected, the spill point or the crest from the last
run within the VelPAK project is shown on the map on the target horizon.
Note: A display of a summary of the spill points for a multiple realisation run can be seen by
selecting the XYZ layers visible of the XYZ data slot ‘Height Above: Analyse Spill
Location Values’ Go Here for further details.
Overlays/Labels - These are exactly the same as the ‘Layers Visible’ overlay options
available at the top of the top of the surface module tab. The overlays and their labels can
be turned on here via a Yes/No toggle or by the Layers Visible drop down. For full details
of what these displays do Go Here.

Snapped, Unsnapped and Merged Data - A Discussion
When displaying data on a Ribbon Map or using data for Gridding, you are able to specify
what type of data they wish to use in terms of whether the data are Snapped, Unsnapped or
Merged.
These are terms relating solely to the mapping of Profile data within the Model.
Note: If you are not using profile data to grid or Ribbon display then the Input would always
be coming from an XYZ slot within your model and the correct input to select would
always be Xyz_slot.
Snapped Data
In an area of intense geology within your profile-based model, where there is heavy
faulting or over thrusts, truncations or piercements, in order to be able to Depth Convert
the structures you would probably find you would need to Snap the data to make
continuous surfaces to depth convert.
For a fuller discussion about snapping Go Here.
Unsnapped Data
It may be that the whole model does not require snapping due to the nature of the
geology or time constraints. In this case the data can be left unsnapped.
Note: Surfaces which are not continuos throughout a profile, but are profile (layer-cake)
depth converted will experience velocity errors if left as unsnapped. Use QC layer
display tools within the Depth Conversion routines to check for these errors. Snapping
the data would ensure that the layers were continuous and thus no velocities could
‘escape’ into the incorrect layer.
Merged Data
Possibly the most likely scenario for profile-based models is that a lot of the area within
your model may not be geologically intense or significant enough to warrant the time
needed to snap the data. You would snap the area of interest but leave the rest of the
profiles unsnapped.
In this case you would select the merged data option for gridding and display. Merged
option takes the snapped profile data if it exists, otherwise it uses the unsnapped profile
data.

Note: You can not snap part of a line and leave the rest unsnapped the whole of a profile
needs to be snapped from one end to the other for all event horizons. If this is
impossible to do you would need to split the line and hold it as two separate lines -
with two separate line names - within the model. ( Trim may be the best method to use
to do this.)
Note: Leaving defaults as Auto, you would not usually have to change these values unless
you wanted to work only on a specific area of your model.
Press to apply the changes and activate the option.
Get Current AOI - Copies the currently displayed Area of Interest (AOI) into the Range
extents and sets the XY_Type to "User".
Axis
Are Of Interest
Type
Current - sets the AOI to that defined in the dialog.
Polygon - sets the AOI to the extents of the currently displayed polygon set.
XY_Type -
Auto - Takes the extent of the model as the range displayed in the Surface.
Grid - Takes the range of the Grid currently selected in the Model Tree as the extent of
the display area of the Map.
User - Allows you to define your own Range entirely independent from Grid or Model.
Z_Type -
Auto - Takes the Zmin and Zmax of the model as the range displayed in the Z direction
on the Surface.

Grid - Takes the Zmin and Zmax of the Grid currently selected in the Model Tree as Z
direction
User - Allows you to define your own Zmin and Zmax Range entirely independent from
Grid or Model.
Range
X_Min/X_Max .Y_Min/Y_Max . Z_Min/Z_Max.
If User is selected above you will need to assign the Min/Max range of values for your
surface display here.
Scale
XY_Scale - Adjust the display to real size as opposed to the usual ‘shrink to fit’ window
display.
Allows you to choose the color you wish to display the various elements on your map.
option.
Color
F_Color - Fault flag marker displayed on your map (if requested) taken from your
snapped profile data.
FL_Color - Fault Lower flag marker displayed on your map (if requested) taken from your
FT_Color - Fault with no Throw flag marker displayed on your map (if requested) taken
from your snapped profile data.
FU_Color - Fault Upper flag marker displayed on your map (if requested) taken from your
Grid_Color - Color of Grid Nodes displayed on your map (if requested).

Indt_Color - Color of Indeterminate Grid Nodes displayed on your map (if requested).
P_Color - Piercement flag marker displayed on your map (if requested) taken from your
Polygon_Color - Color of Polygons displayed on your map (if requested).
Note: For Polygon colors - old models will use yellow as the default colour, new models will
default to the more easily visible orange.
T_Color - Truncation flag marker displayed on your map (if requested) taken from your
XYZ_Color - Color of XYZs displayed on your map (if requested).
Display Dialog - Mask Tab
option.
The MASK value within VelPAK allows a unique number to be given to any geological
situation occurring within the memory model.
This MASK number is written in HEX.
VelPAK will consider 32 event horizons and the event horizon ID is represented internally by
setting a bit in a 32 bit word.

This option gives you a chance to map out a particular MASK and see its extent over the
model area.
Taking the scenario below for example:
Mask value (HEX) of the Blue

Event represented
in information in the
Console of the VelPAK
window using Point Pick
option
Type in the HEX relevant to the geological situation in the Mask tab.
Select the Ribbon Surface = Yes to produce a ribbon map of the Mask value. (if you leave this
as No you will get a Ribbon map display of whatever is currently selected in the Surface
Display Property Grid.
Note: You must select RIBBON MAP option on the main SURFACE window of VelPAK
Display drop down to have your chosen ribbon map displayed.

Details of the Mask Value

The MASK column within the XYZ format allows a unique number to be given to any
geological situation occurring within the memory model.
This MASK number is written in HEX.
VelPAK will consider 32 event horizons and the event horizon ID is represented internally by
setting a bit in a 32 bit word.
Bit 1 2 3 4 5 6 7 8 9 10 11 1 et 3
Number 2 c. 2
Binary 1 2 4 8 1 3 6 1 2 etc.
Value 6 2 4 2 5
8 6
Event Faul 1 2 3 4 5 6 7 8 etc...

Number ts
Example 1) Event 3 on a fault plane would be represented thus:
Bit Number 1 2 3 4 5 6 7 8 9
Binary Value 1 2 4 8 16 32 64 128
Binary Mask 1 0 0 1 0 0 0 0
Value
In the above example; the Hex number 9 represents Event 3 on a fault plane.
Example 2) Event 3 and 4 on a fault plane would be represented thus:
Bit Number 1 2 3 4 5 6 7 8 9 10
Binary Value 1 2 4 8 16 32 64 128 256
Binary Mask 1 0 0 1 1 0 0 0 0
Value
In the above example, the Hex number 19 represents Event 3 and 4 on a fault plane.
MASK 2

Gives a flag to indicate the status of the point.
Bit Number ASCII Value Status

- 0 The point has not been modified
1 1 The point has been moved
2 2 The point has been inserted
3 4 The point has been interpolated
4 8 The point is a termination point
It is possible for more than one bit to be set, for example, an inserted point may have been
moved (ASCII 3).
Various utility programs to further manipulate these data field are available from Software
Technical Support.

Grid Dialog
Grid Dialog
Gridding allows you to grid data from a variety of different sources:
Grid time, velocity or depth data from a selected event horizon on a profile in your
model. This can either be snapped, unsnapped raw or merged (both raw and snapped).
Grid any XYZ data file stored in the XYZ slots from the Model Tree page.
VelPAK uses GTGRID as its basis for Gridding, providing access to a library of gridding
routines prepared by Geophysical Techniques (GT), Inc..
Fault Polygons and other Polygons can be used within the gridding methods.
Where the Grids are stored

Grids are stored and selected within the Model Tree under the relevant event horizon of the
‘Surface’ Branch.
Model Tree
Time Grid1
Interval Grid1
showing four
Grids stored
under Event 1
Grids are also selected in the Surface&Slot selector for each event horizon, along with other
VelPAK elements - XYZ files Polygons, and Faults. For each event horizon the Surface&Slot
selector will show which Grid is currently selected - this will be the grid that will be displayed
on the Surface display.

Grid Dialog
A Quick Guide to Gridding

1. Decide what you want to Grid!
The data can come from either an XYZ file (already read in and stored within VelPAK and
seen in the Model Tree) or from Profile Data.
2. Select the Event Horizon you will be gridding data for, either from the Model Tree or the
Surface&Slot selector:
3. On the Grid General tab select the Method of Gridding:
4. On the Grid General tab select where your Input data are going to come from. If it is an
XYZ file select what slot in the Model Tree the input XYZ file is stored:
5. On the Grid General tab select where you want your Output grid to go:
6. On the Grid Range tab set up the Range for your grid selecting from the Range Tools at
the top of the tab. Get range from the XYZ file, from a defined parent Grid use the
extremes of the entire Model or Blank parameters to manually enter values.

Grid Dialog
Range Tools
7. If you are using a Parent Grid to define the Range set up the Event Horizon and Slot
where this can be found.
8. Press the Parameter Tool at the top of the tab to automatically fill in the gridding
parameters.
Parameter
Tool
9. Press the Apply tick to start the Gridding Process and select OK to the
Confirmation of Gridding Parameters Alert.
10. To see contours displayed on your map make sure you have the display type set to
Contour or Shaded contour.
11. If the contours are too close together or there are too few of them change the Contour
Increment in the Surface General display.

Grid Dialog

Grid Dialog
Grid Dialog - General Tab
Note: The Variogram and Data tabs are only used if Krig is selected as the Gridding Method
option.
The property grid will change depending on which gridding method has been selected.
Details of the inputs can be found with the gridding methods om this manual.
Option
Tools
Tools
Delete - - will delete the grid currently selected in the Output_Grid slot. If you have
changed the AOI of the grids in the VelPAK model it may be advisable to delete grids
otherwise there may be errors. Used mostly in the wizard and workflows.
Note: Grids can also be deleted in the Model Tree.

Grid Dialog
XYZ Parameter calculation - - Used to compute certain gridding parameters from the
xyz data for particular gridding methods - for example if Fast Kriging is selected as the
gridding method this will calculate the Kriging Mean of data value.
Option
Method - Select the Gridding method to use.
When you click on the Method, click on the down arrow to the right (as usual) to bring up
the selection. Not ‘as usual’, however, is this will then bring up a set of tabs where you
can select the type of grid and the actual grid method you require.
Move through the types using the left/right arrows that will appear.
See Methods available which summarizes the advantages and disadvantages of each
method and the types of data best suited to each method.
Type - Selecting ‘Grid all Events’, output grid files for each event horizon will be
generated. The output grids will be stored in the slot selected in Output grid, under each
separate event horizon.
Verify - Set to yes for alert dialog to appear before gridding proceeds and a grid
generated.
Input
Input - Select what type of data you are going to use for gridding; snapped or unsnapped/
raw or merged profile data in depth, time or velocity or XYZ data files from any variety of
sources and currently stored in an XYZ slot within the Model Tree.
For a discussion of Snapped, Unsnapped/Raw and Merged Data, Go Here.
Input_Drift - used in Kriging - Select the data slot from the Model Tree where the grid is
being stored. This allows you to input a grid data set which is present at all locations
which are to be estimated by kriging, to use as a trend. The resulting map from kriging
with an external drift will honour the “hard” input data points, but will follow the trend or

Grid Dialog
shape of the external drift where there is no hard data. Go here for further details of
External Drift.
Input_Fault - If faults are being used in gridding routine - Select the data slot from the
Model Tree where the fault polygons are being stored. For example selecting ‘General 1’
here will access the Fault Polygon data set that is currently sitting under the Fault branch
for the event horizon you are in.
Input_Polygon - - If polygons are being used in gridding routine - Select the data slot
from the Model Tree where the polygons are being stored.
For example selecting ‘General 1’ here will access the Polygon data set that is currently
sitting under the Polygon branch for the event horizon you are in.
Input_XYZ - If XYZ datafiles have been selected as the input data type - Select the data
slot from the Model Tree where the XYZ data file are being stored. For example selecting
‘Interval Velocity’ here will access the XYZ data set that is currently sitting under the
Polygon branch for the event horizon you are in, under ‘Interval Velocity’.
Output
Output_Grid - Select which slot in the Model Tree the generated grid file is to be placed.

Grid Dialog
This will relate to the event horizon you are gridding up. If you have selected to grid all
event horizons a grid will be placed in the same slot for each of the event horizons being
gridded.
Output_Variance - Select a slot to place a grid of variance - if required; a grid of variance
is produced from Kriging showing the uncertainty at each of the output points.

Grid Dialog
Grid Dialog - Range Tab
option.
The Range Tab allows you to set the X,Y and Z range for the grid to be generated, as well as
other gridding set up inputs. You can either type these values in for yourself or bring values in
from other sources; the Model range, the XYZ file range or a ‘Parent’ grid range. Since grid-
to-grid processes within VelPAK rely on the grids being entirely compatible and congruent
using a Parent Grid to determine the range of the Grid you are wishing to grid up is very often
the method to use.
Option
Range Tools and Parameter Tool
Range Tools Parameter

Tool
Range Tools
The square boxed Range Tools at the top of the Range tab are there for you to select the
method by which your Area of Interest will be calculated.

Grid Dialog
XYZ - - Use XYZ file (selected in General Tab) to calculate Area of Interest.
Grid - - Use Parent Grid (entered at the bottom of this tab) to calculate Area of
Interest.
Model - - Use the Model extremes to give the Area of Interest.
Blank - - Blank the parameters that are shown on the tab.

Parameter Tool
Parameter - - Use data to calculate gridding parameters. This option will estimate the
Interpolations and the Radius given the data and the range that you wish to grid up.
NOTE that this must be done AFTER the Range tool has been used to define the AOI of
your grid!
The Parameter Tool takes the area of Grid definition and divides it by the number of data
points it finds. Once it knows the area per point it then works out the radius of the circle
which would encompass on average 64 points. If the density of the data you are working
on is very variable this will not work correctly and you will need to work out a suitable
radius yourself.
Area Of Interest
Increment Factor - default =1. If required a value of 10 or 20 would be entered here, but a
factor of 0.1, for example, can also be used.
This will multiply the XY Increment by the given factor and recalculates it to generate a
(usually) coarser grid without changing the XY increment set-up itself.
A default of 1 will use the XY increment as defined in the inputs below in the property grid.
A particular usage of this option would be when using the Krig_Sgs method of
gridding or some other form of Kriging, which can be very slow using the standard XY
increment from your project. The grid can be generated using an increment factor but
in order to make the grid match the Parent grid in the project the data points would
have to be output from VelPAK, read back in and used to make a grid compatible with
the Parent grid using a quick gridding method such as ‘Global’.
Note that every time the grid is run using an increment factor it uses the set XY increment
from the parent grid as its base to calculate the increment. So the effect is not cumulative
if the increment factor is used more than once.
Number_Columns - The defined number of columns of nodes which will be generated in
your grid. These values are determined by the program once you have input the XY Min/
Max and the XY Increment.
Number_Rows - The defined number of rows of nodes which will be generated in your
grid. These values are determined by the program once you have input the XY Min/Max
and the XY Increment.
X_Increment, Y_Increment - These control the size of the grid increment, in coordinate
units. This is an important variable as it not only affects the process run time but also the

Grid Dialog
quality of data fit. A ‘noisy’ detailed surface requires a fine grid to fit each point. A less
detailed surface only requires a coarse grid.
X_Maximum, X_Minimum, Y_Maximum, Y_Minimum - These values are deduced from
whichever XY source you choose as defined from the Range Tools at the top of this page.
Alternatively you can type your own range in from scratch.The program will round these
up and down according to your XY Increment. You can change these to select just a
portion of your data file to be gridded.
Parent
If you are to use parameters from a grid already in the model this is where you enter the
Event Horizon number and the slot in which that grid is to be found. When you have
selected these, press the at the top of the tab to read in the parameters into the
relevant AOI slots.
Parent_Event - Select the Event Horizon under which the parent grid is stored.
Parent_Grid - Select the slot from the Model Tree where the parent grid is stored.
Note: You must press the Range tool at the top of the tab to call the Parent grid values
in as the AOI.
Grid Dialog - Variogram Tab
Estimated Value
per lag
Variance model fit
Points per lag
Note: The Variogram Tab is only used if KRIG is selected as the Gridding Method.

Grid Dialog
The variogram is a plot showing the spatial variation within a data set. This is a cross-plot
of distance between points against variance. To show the underlying trends, the data are
grouped into a number of “lags”, each lag corresponding to a range of distances.
The calculated variogram displays the points for each lag and the experimental model fit.
By changing the Nugget, Range and Sill in the Model parameters set up the curve can be
best fitted to the red lag points and these values used in gridding.
The process works on the XYZ data file selected in the ‘General’ tab of the Gridding
Properties.
Quick Guide to using the Variogram

1. Select the XYZ data file you are going to be running the variogram on and select the XYZ
slot as the Input under the General Tab.
2. Press the Parameter Tool to estimate the variogram set up from the number of points in
the data set.
3. Press the Calculate Tool to produce a variogram display.
4. Change values in the Model options area to make a best fit of the blue curve onto the red
lag groups.
Producing a Sensible display

When you first press the Calculate and Display Tool from the Variogram tab, this can give
you an idea of what the parameters should be. It will be a reasonable approximation using
the Estimate Parameters tool values based on the statistics drawn from the XYZs, but it
will not be good at using outlying points. You would expect, therefore, to have to adjust
this initial model’s parameters before reaching a model you are happy with.
Where to Start
• Make sure the direction is set to 0 and the tolerance to 90.
• For a data set such as seismic velocity data, start with 100 lags of 300 metres each (this
will search a distance of 30 kilometres). If the map data are in feet, then 900 is a sensible
lag length.
This will quickly show you what correlations occur within your data.

Grid Dialog
WHAT IF...
The graph stops part way across?

The data are concentrated over a smaller area, and the number of lags
or the lag length can be reduced.
The plot continues to the right hand side?

It would be a good idea to increase the lag length or number of lags, to
look at the whole data set.
The variogram looks mostly random with no sensible structure?

More averaging probably needs to be performed: the lag length should
be increased, and the number of lags decreased correspondingly.
The variogram looks “too smooth to be true”?

In this unlikely event, try decreasing the lag length and increasing the
number of lags, in order to look in more detail at the structure of the
Variogram Inputs, Icons and Displays

Calculate Tool and Parameter Tool
Calculate Parameter
Tool Tool
The square boxed Tools at the top of the Variogram tab are to calculate and display the
variogram and estimate the variogram parameters.
Parameter - - Estimates the Experimental variogram parameters given the number

and of points.
Calculate and Display - - using the parameters estimated from the Parameter tool
this will calculate, display and update the variogram. An initial model is calculated and
displayed using a Spherical function. This can give you an idea of what the parameters
should be. It will be a reasonable approximation using the most likely values based on the
statistics drawn from the XYZs, but it will not be good at using outlying points. You would
expect, therefore, to have to adjust these parameters before reaching a model you are
happy with.
Options:
Experimental
Direction - The direction vector in which to look. This is a compass bearing, so 0 is North.

Grid Dialog
Lags - The total number of lags to be considered. The largest separation between points
which will be considered will be (lag length) x (number of lags).
Length - The length of each individual lag.
Number - A number indicating the number of XYZ to be used in the calculation of the
experimental variogram. These points are chosen systematically and at equal spacing,
from the order in which they are loaded.
It is recommended that a small number of points is used first, until you are happy with the
rest of the Variogram parameters; a large number of points selected can make the
generation of the variogram very slow.
Tolerance - The tolerance (in degrees) either side of the direction. A tolerance of 90 will
include all data values.
Model
Anisotropy - The difference in range for different directions. For example, a data set
composed of North-South channels would have a much larger correlation range in the
northerly direction than in the easterly direction. In this case, there would be significant
anisotropy. Within VelPAK, the anisotropy is a number between 0 and 1. If the anisotropy
is 1, there is no anisotropy (the correlation length is the same in all directions. If the
anisotropy is 0.5, then the correlation length is twice as long in one direction as it is in the
perpendicular direction).
Azimuth - The direction of the Anisotropy. This is a compass bearing, so 0 is North.
Nugget - The value of variogram at zero lag. Data samples at the same location may
have different values due to, for example, measurement error. If this is the case, the
variogram will not go through zero at zero lag.
Range - The distance at which the variogram reaches the “sill”. The value of the
variogram will generally increase with increasing lag, until it levels off at some value. The
distance at which this happens is called the range. This parameter is also known as the
correlation length. Points which are closer than this distance will show some degree of
correlation. Outside this distance, points are independent.
Sill - The value of the variogram where it flattens off - where there is no longer seen to be
any apparent correlation between the variance and the distance. Typically the lower the
value entered here the less noise would be seen on the grid.
If you require the SGS result to match a particular Standard Deviation then set the Sill
parameter to SD squared.
Type
The type of model function to be used. Each function gives rise to a different shaped
curve, corresponding to fundamentally different types of data distribution. The most
appropriate function is usually fairly evident from the experimental data.

Grid Dialog
Grid Dialog - Randomize
Used in conjunction with the variogram tab for Kriging depth conversion methods.
Randomise - - pressing this will take a random value from within the Range Min/Max
and place it in the Range slot within the Variogram tab for variogram generation.
Range Min/Max - User entered values between which the program will generate the
random number for the Range within the Variogram tab.

Grid Dialog
Gridding Method Types
List of Gridding Method Types available for Gridding within VelPAK:

Popular
Kriging Fast
Krig_Simple
Krig
Radial Basis Function
Natural Neighbours 3
Smoothing
Smooth
Loess
Specialist
Krig_Sgs
Randomised
System of Linear Equations
Minimum Curvature
Multi Level B Spline
Natural Neighbours
Natural Neighbours 2
Triangulation
Inverse Distance
Block Kriging Fast
Block Radial Basis Function

Grid Dialog
Depreciated (no longer will be used)

Global
Random
Cluster
Weighted
With most data sets the default gridding method, Kriging with a linear variogram is quite
effective.
A very close second is Radial Basis Function. Either of these methods is likely to produce a
reasonable representation of your data.
The table below summarizes the advantages and disadvantages of some of these methods
and the types of data best suited to each method. The methods are described in detail
following the table.
Gridding Methods: Advantages and Disadvantages
Method Advantages Disadvantages Intended Data
Popular
Kriging_Fast Optimised Ordinary or Can be slow with a large Small to medium sized
Simple kriging. No number of points. data sets. Will tie the
need to construct data.
variogram. Favourite
method for residual or
parameter mapping at
well locations.
Kriging Ordinary Kriging Can be slow with a large Small to medium sized
based on GSLIB. An number of points with a data sets. Will tie the
opportunity to variogram needed to be data.
examine data and constructed. It is more
construct a complex to set up than other
variogram. One of the gridding method and more
best gridding methods prone to user errors
available. therefore.
Simple Simple Kriging based Slow (but not as slow as Small to medium sized
Kriging on Gstat. An normal Kriging). data sets. Will tie the
opportunity to data.
examine data and
construct a
variogram. One of the
best gridding methods
available.
Quicker than Kriging.

Grid Dialog
Radial Basis Good general- Tends to ramp off in areas Small to medium sized
Function purpose method. of poor data. Unable to data sets. Will tie the
Result similar to control with variogram. data.
Kriging.
Natural Very fast and stable Poor in sparse data areas. Large data sets with
Neighbours method. good coverage. Will tie
3 the data.
Smoothing
Smooth Generates a smooth Only suitable for dense data Noisy data such as
map. sets. derived from stacking
velocities.
Loess Good smoothing Can take a long time if there Stacking Velocities.
algorithm for noisy are lots of input data points. There is no limit to the
data such as stacking Gridding time surfaces from size of dataset,
velocities. 3D interpretation can take a however the larger it is
Visually very pleasing long time.Does not always the longer it takes.
results. honour the input data so not
good for gridding well
parameters such as interval
velocity.
Specialist
Kriging Sgs Adds noise back into Slower than normal Kriging. Error maps and depth
(Sequential the data to undo the Due to the randomization conversion parameter
Gaussian smoothing effect of factor of this algorithm the maps such as V0.
Simulation) Kriging. grid will be different each Typically only used in
If you require the SGS time generated and the multiple realizations.
result to match a corresponding contour map
particular Standard could also show dramatic
Deviation then set the differences which could be
Sill parameter to SD disconcerting.
squared.
Randomised Produces a grid of a Useful in writing

constant value workflows where a
between -1.0 and random scalar is
+1.0. required.

Grid Dialog
System of
Linear
Equations
Minimum Generates smooth

Curvature surfaces and is fast for
most data sets.
Multi Level B
Spline
Natural Very fast and stable Will not extrapolate beyond

Neighbours method. a Convex Hull of the data.
Natural Very fast and stable Will not extrapolate beyond

Neighbours method. a Convex Hull of the data.
2
Triangulation Very fast and stable Will not extrapolate beyond

method. a Convex Hull of the data.
Natural Neighbours is
preferred choice.
Inverse Fast Has the tendency to generate

Distance "bull's-eye" patterns of
concentric contours around the
data points.
Block As Kriging Fast but Larger, dense data

Kriging Fast splits large data sets sets.
into blocks.
Block Radial As Radial Basis but Can Leave artefacts from Larger, dense data
Basis splits large data sets blocking in sparse data sets.
Function into blocks. areas.
Depreciated
Global Fast. Only works for a small data Small data sets with no
Visually pleasing set (<10000 points). discontinuity (faults).
results. Performs excessive
averaging on larger data
sets.

Grid Dialog
Random Handles faults and Not appropriate for noisy Random, large data
large data sets well. data - if data are noisy, sets with or without
Honours local spurious results can occur. discontinuity.
gradient.
Cluster Good for use with Excessive averaging of Randomly distributed

data that is close closely spaced points is noisy data with or
together or noisy. appropriate only for noisy without discontinuity.
Ignores excessive data.
gradients implied by
closely spaced noisy
data.
Weighted Fast. No gradient calculations are Very large data sets.

Good for visualizing made.
input data with a small
radius.
Gives a “quick look”.
Popular Methods
Kriging Methods; Kriging, Simple Kriging and SGS Kriging.
Kriging is a group of geostatistical techniques to interpolate the value of a random field at an
unobserved location from observations of its value at nearby locations.
Kriging belongs to the family of linear least squares estimation algorithms. As illustrated in
the graph below the aim of kriging is to estimate the value of an unknown real-valued
function, f, at a point, x* given the values of the function at some other points x1 ,..., xn. , A
kriging estimator is said to be linear because the predicted value is a linear combination.

Grid Dialog
METHOD = ‘Kriging’
Kriging is a statistical gridding technique. Kriging produces the most statistically likely
map, given the statistical distribution of the input data. Put another way, the average of a
large number of random models (each of which is constrained to match the distribution
shown by the input data) will tend towards the kriged results; the variance of these
models will tend towards the variance from kriging.
Kriging is an “exact interpolator”: in other words, if a grid node is exactly coincident with
an input data point, then the grid node will be assigned that value. Otherwise, kriging
generates a smooth map, which tends to the mean value of the data at large distance
away from the data points.
The power of kriging comes partly from the large number of parameters that are available
to specify how the interpolation is to occur, particularly through the specification of a
variogram model. The ability to incorporate soft information through the use of an external
drift is also extremely powerful.
There are a number of excellent Geostatistical textbooks available, and it is
recommended that the interested reader obtains one of these if any of the concepts
mentioned in this part of the manual are unfamiliar.
Kriging with External Drift

Kriging with external drift is a method of incorporating the trend information from a
densely sampled data set in the gridding of a sparsely sampled data set.
This is handled in VelPAK by using a grid (surface) of the external drift variable. This is
then interpolated to get the drift values at the data locations of the sparse data set.

Grid Dialog
The curve-fit module should be used to check that the drift data set is well correlated with
the data to be gridded. If a drift surface is used which bears no resemblance to the
primary data, the answers can look very strange.
Another consideration with external drift is the search radius. If the search radius is very
small, external drift kriging will still generate a value everywhere where the drift surface is
present. Away from the data values, the resulting surface will be identical to the drift
surface.
METHOD = ‘Kriging Simple’

Simple kriging is mathematically the simplest, but the least general type of kriging.. It
assumes the expectation of the random field to be known, and relies on a covariance
function. However, in most applications neither the expectation nor the covariance are known
beforehand.
The practical assumptions for the application of simple kriging are:
Wide sense stationarity of the field.
The expectation is zero everywhere: μ(x) = 0.
Known covariance function c(x,y) = Cov(Z(x),Z(y))
METHOD = ‘Kriging Sgs (Sequential Gaussian Simulation)’

Stochastic simulation is a means for generating multiple equiprobable realizations of the
property in question, rather than simply estimating the mean. Essentially - adding back in
some noise to undo the smoothing effect of kriging. This possibly gives a better
representation of the natural variability of the property in question and gives a means for
quantifying the uncertainty regarding the real structure.
The basic idea of sequential Gaussian simulation (SGS) is very simple. Recall that kriging
gives us an estimate of both the mean and standard deviation of the variable at each grid
node, meaning we can represent the variable at each grid node as a random variable
following a normal (Gaussian) distribution. Rather than choosing the mean as the estimate at
each node, SGS chooses a random deviate from this normal distribution, selected according
to a uniform random number representing the probability level.

Grid Dialog
In the above diagram the thin dashed line shows how the data actually behaves, but this is
only known at the well locations. The solid line represents the velocity model derived by
kriging the values at the well points. It represents the best guess away from control points.
The thick dashed red line represents the uncertainty of the kriged estimate (lines of +/- two
standard deviations). The thin dotted line is a random realization generated using Sequential
Gaussian Simulation. It is no more accurate than the kriged estimate, but it is more “realistic”.
Note: Due to the randomization factor of this algorithm the grid will be different each time
generated and the corresponding contour map could also show dramatic differences.
An advanced method of using SGS is to use it in multiple realisations and setting the sill to
the square of the Standard Deviation. The grids generated can be QCed in the Analyse
module in the Statistics -> Statistics Fly-out using Type = Standard Deviation - the grid-of-
grids generated should show the same value as the SD squared entered into the spill.
Smoothing Methods
METHOD = ‘SMOOTH’
The Smooth method uses a simple unweighted circular average method to generate a
smooth map. The only parameter it uses is the Search Radius. All the input data values
within the search radius of each node are averaged, and the result is assigned to that grid
node. There is no octant test, so the output grid will extrapolate beyond the data by the
search radius. You can chop off this extra coverage using PROC to constrain the grid to
have the same areal extent as one of your time grids, for example.
METHOD = ‘LOESS Gridding’

LOESS is short for LOcal regrESSion. Local regression assumes the input data are
measurements (with some error) of a smooth surface. Within a neighborhood containing
some of the data, a regression surface (either a plane or a quadratic surface) is fitted
through the data. The errors can be specified by either a symmetric or gaussian

Grid Dialog
probability distribution; this affects how much weight is given to outlying points (those with
extreme Z values). Optionally, a series of iterations can be performed which progressively
down-weight points which are a long way from the regression surface. The following
parameters therefore need to be specified:
Span
Degree
Family
Iterations
For more information on LOESS please refer to CLEVELAND, W.S. and GROSSE, E.,
1991, Computational methods for local regression, Statistics and Computing, 1, 47-62.
Specialist Methods
METHOD = ‘ Krig_Sgs’ - see Kriging
METHOD = ‘Radial Basis Function’

Radial Basis Function interpolation is a diverse group of data interpolation methods. In terms
of the ability to fit your data and to produce a smooth surface, the Multiquadric method is
considered by many to be the best. All of the Radial Basis Function methods are exact
interpolators, so they attempt to honor your data. You can introduce a shaping factor to all the
methods in an attempt to produce a smoother surface. Regardless of the R2 value, the Radial
Basis Function is an exact interpolator.
n = 0 RBF_FAMILY_LINEAR = 0
n = 1 RBF_FAMILY_THIN_PLATE_SPLINES_BETA_NOEVEN = 1; // Thin-Plate r^beta
n = 2 RBF_FAMILY_GAUSSAIN = 2; //Gaussian exp(-c*r^2)
n = 3 RBF_FAMILY_MULTIQUADRICS = 3; // Multiquadric (c^2 + r^2)^(beta/2)
n = 4 RBF_FAMILY_THIN_PLATE_SPLINES_BETA_EVEN = 4; // Thin-Plate splines (-1)^(beta/2+1)*r^(beta)*log(r)
n = 5 RBF_FAMILY_SOBOLEW_SPLINES = 5; // Sobolew splines (2*PI^(c))*K(nu,2*PI*r)*(r^nu)/gamma(c)
n = 6 RBF_FAMILY_THIN_PLATE_SPLINES_WITH_C = 6; // Thin-plate splines (cr)^2 * log(cr)
n = 7 RBF_FAMILY_MADYCH_AND_NELSON = 7; // Madych & Nelson II -2*sqrt(pi*(1+r^2))
METHOD = ‘Randomised’
Produces a grid of a constant value between -1.0 and +1.0. Useful in writing workflows where
a random scalar is required.
METHOD = ‘System of Linear Equations’

For information of theory behind thsi method we recommend the Wikipedia page:
https://en.wikipedia.org/wiki/System_of_linear_equations

Grid Dialog
METHOD = ‘Minimum Curvature’

The interpolated surface generated by Minimum Curvature is analogous to a thin, linearly
elastic plate passing through each of the data values with a minimum amount of bending.
Minimum Curvature generates the smoothest possible surface while attempting to honor your
data as closely as possible. Minimum Curvature is not an exact interpolator, however. This
means that your data are not always honored exactly.
METHOD = ‘Multi Level B Spline’

Multilevel B-spline algorithm for spatial interpolation of scattered data as proposed by Lee,
Wolberg and Shin (1997). The algorithm makes use of a coarse-to-fine hierarchy of control
lattices to generate a sequence of bicubic B-spline functions, whose sum approaches the
desired interpolation function. Large performance gains are realized by using B-spline
refinement to reduce the sum of these functions into one equivalent B-spline function.
Reference:
- Lee, S., Wolberg, G., Shin, S.Y. (1997): 'Scattered Data Interpolation with Multilevel B-
Splines', IEEE Transactions On Visualisation And Computer Graphics, Vol.3, No.3
METHOD = ‘Natural Neighbours’

What is Natural Neighbor interpolation? Consider a set of Thiessen polygons (the dual of a
Delaunay triangulation). If a new point (target) were added to the data set, these Thiessen
polygons would be modified. In fact, some of the polygons would shrink in size, while none
would increase in size. The area associated with the target's Thiessen polygon that was
taken from an existing polygon is called the "borrowed area." The Natural Neighbor
interpolation algorithm uses a weighted average of the neighboring observations, where the
weights are proportional to the "borrowed area."
METHOD = ‘Natural Neighbours 2’

Very fast and stable method. Will not extrapolate beyond a Convex Hull of the data.
METHOD = ‘Triangulation’
This algorithm creates triangles by drawing lines between data points. The original points are
connected in such a way that no triangle edges are intersected by other triangles. The result
is a patchwork of triangular faces over the extent of the grid. This method is an exact
interpolator.
METHOD = ‘Inverse Distance’

The Inverse Distance gridding method is a weighted average interpolator, and can be either
an exact or a smoothing interpolator.
With Inverse Distance to a Power, data are weighted during interpolation such that the
influence of one point relative to another declines with distance from the grid node. Weighting

Grid Dialog
is assigned to data through the use of a weighting power that controls how the weighting
factors drop off as distance from a grid node increases. The greater the weighting power, the
less effect points far from the grid node have during interpolation. As the power increases, the
grid node value approaches the value of the nearest point. For a smaller power, the weights
are more evenly distributed among the neighboring data points.
METHOD = ‘Block Kriging Fast’

As Kriging Fast but splits large data sets into blocks. Intended for larger, dense data sets.
METHOD = ‘Block Radial Basis Function’
As Radial Basis but splits large data sets into blocks but it can Leave artefacts from blocking
in sparse data areas. Intended for larger, dense data sets
Depreciated Methods
METHOD = ‘Global’
The Global method provides an approximation for generating a minimum curvature
solution. This method can only be used on data that contains less than 10,000 points. It is
the fastest gridding method for small data sets, and also tends to produce the most
visually pleasing results.
This method employs points averaging whenever the number of points exceeds 1000.
This may cause the resulting surface to not pass directly through the input points that
were averaged out.
All nodes are calculated regardless of the input point distribution. The resulting surface as
represented by the Z values at each node in the grid is the exact solution to a set of
equations that approximates the relationships among a thin metal plate, a set of desired
displacements at the random input points, and the forces applied at each point.
By solving this system of equations the necessary values of the force are determined at
each point. These values are then used to compute the plate displacement at every grid
node. If no averaging is performed, this solution provides a surface that passes through
every point specified and has the least amount of curvature possible, as shown in Figure
1.
If averaging was performed to reduce the number of points, the solution will not
necessarily pass through those points that were averaged.

Grid Dialog
input points (d,z),

where d is the xy plane. no averaging performed
l
l
l
l
l
z l
d
grid spacing
Interpolated curve, shown in two dimensions, using the Direct method
No averaging is performed.
METHOD = ‘Random’
The Random method uses the Radial Search for Scattered Points algorithm. This is the
default method for GTGRID. This approach is good for large data sets that contain noisy
data.
The radial search uses randomly positioned input points to compute grid nodes in the
“immediate vicinity” of each input point.
The radial search technique relies on localized fits of a plane to the selected subsets of
the input points. Using each input point as an origin, a subset of the surrounding points is
formed by selecting the nearest two points in each octant about the origin. Each point is
then weighted according to its displacement from the origin. The plane is also constrained
to pass through the point selected as the origin.
If a successful fit is accomplished, the grid nodes about the point selected as an origin are
then assigned Z values.
Only grid nodes that are interior to the convex hull of the input data point distribution will
be assigned a Z value (the convex hull is a boundary that encompasses all the data
points. For example, if each data point were a nail in a board, the convex hull could be
represented by a rubber band stretched around all the nails). This is done to minimize
edge effects that are inherent to this approach.
This process repeats using every input point as an origin. GTGRID attempts to assign all
unassigned grid nodes during secondary gridding. Note that some grid nodes are
computed more than once if the input point distribution is such that more than one point is
contained within a grid cell.
METHOD = ‘Cluster’
The Cluster method uses the Radical Search for Clustered or Linear Data algorithm. The
Cluster Method differs from the Random Method in that additional effort is employed
during calculation of grid nodes near input points to minimize the extrapolation of
excessive gradients due to noise or points that are very close together.

Grid Dialog
Therefore, it is recommended that this method be used especially if noisy or clustered

data are being processed.
METHOD = ‘Weighted’
This method uses the Weighted algorithm. This is a relatively fast method of mapping
points onto a specified grid without any attempt at interpolation or gradient estimation.
Use this method if you want to input a set of values which were computed on a grid size
desired. Each grid node is a weighted combination of the data points surrounding it within
adjacent cells. Secondary gridding is then employed to fill unassigned grid nodes. If the
input distribution is fairly uniform, this method is much faster than the others. Figure 2
shows the curve fit produced with this method.
input points (d, z),

where d is the xy plane. averaged Z values
l l
gradient = 0
l
l
l
z l
d
grid spacing
Interpolated curve, shown in two dimensions, produced using

the weighted method.

Process Dialog
Process Dialog
The Grid Processing Property Grid is an extremely powerful tool to deal with grid
manipulation; multiplying, adding etc. grids together or with constants to produce new grids.
A whole host of other processes are available including Grid-to-Grid depth conversions. You
also have the opportunity to make ‘Create-your-Own’ methods. Go Here for details.
Grids can be processed to give new grids which you can then display or use. In common with
other VelPAK programs, the grids are stored internally within the binary VelPAK model. They
can only be accessed for processes external to VelPAK by using the File/Export/Surface
Grid option.
The grid processing methods are set up from the Parameter Tab.
Note: Each set up refers to one event horizon. Once you have set up the Process run for
one event horizon select a new event horizon from the Surface&Slot selector or
Model Tree and then select the process to occur on that event horizon.
Tabs include:
General tab - (currently inactive).
Setting up the Formula to use in the Parameter Tab will change the Parameter banks in the
Property Grid. These banks of information will change from simply saying Unused to being
filled in with inputs such as Name: top_time, Type Input..etc. Each of these Parameter banks
relate to an input or output element from the defined process formula for this event horizon.

Process Dialog
Process Dialog - Parameter Tab
Input
Bank 01
Input
Bank 02
When you have made your edits. Press to activate the option.
Options
From - [currently inactive].
Input Banks -
various fields with the names of the input/outputs it requires. Other fields have to be filled
in by you if you have specified User as where the information for your process is coming
from.

Process Dialog
For example:
7 Variables
The formula for “VO GIVEN DEPTH

ERROR” has 7 variables to be entered,
either input or output. Each one of the 7
variables has a separate Input bank to
define and set up, telling the program
which slot in the Model Tree to find the
grid to use or to place the created grid,
or what the Constant value is.
Each Input or Output Bank has its own values to be set up - for example:
01_Value - If the input is a constant value, the value will be entered here.
If a Grid is to be used and not a Constant then the following are to be entered:
01_GridEvent - ** User Entered ** - The Event Horizon under which the grid to be used
as input 01 is stored in the Model Tree. Note the Previous / Current option which allows
you select the previous or current event horizon rather than name a specific event horizon
where the grid is to be found. Usually this option is only utilized when constructing
Generic Workflows which can work on any event horizon.
01_GridType - ** User Entered ** - The slot under the event horizon in the Model Tree
where the grid is stored.

Process Dialog
Process Dialog - Formula Tab

Process Dialog
Processing Formulae Available
Process Description
MATH: + (ADD) GRIDS add CONSTANT or INPUT2 to INPUT1
MATH: - (SUBTRACT) subtract CONSTANT or INPUT2 to INPUT1

GRIDS
MATH: * (MULTIPLY) multiply INPUT1 by CONSTANT or INPUT2.

GRIDS
MATH: / (DIVIDE) divide INPUT1 by CONSTANT or INPUT2

GRIDS
MOVE GRIDS move INPUT1 to Output
MERGE SHALLOW If INPUT1 is less than INPUT2 then the result equals
INPUT2
otherwise the result will be INPUT1. Go here for detailed
example.
Input:
2
1
Output:

Process Dialog
Process Description
MERGE SHALLOW If INPUT1 is less than INPUT2 then the result is INDT
AND BLANK otherwise it equals INPUT2. Go here for detailed
example.
Input:
2
1
Output:
MERGE DEEP If INPUT1 is greater than INPUT2 then the result is

INPUT2 otherwise result is INPUT1. Go here for detailed
example.
Input:
1
2
Output:
MERGE DEEP AND If INPUT1 is greater than INPUT2 then the result is INDT
BLANK otherwise it equals INPUT2. Go here for detailed
example.
Input:
1
2
Output:
CONVERT FEET TO Converts Input to Metres

METRES
CONVERT METRES Converts Input to Feet

TO FEET

Process Dialog
Process Description
MAKE CONSTANT Set grid nodes to constant with no INDT values

GRID (NO INDTS)
MAKE CONSTANT Set grid nodes to constant keeping INDT values

GRID (PRESERVE
INDTS)
SQUARE ROOT GRID Produces Square Root of Input
ABSOLUTE OF A Takes negative values of grids and makes them positive.

GRID Positive grid values remain untouched
INVERT INDTS AND Changes Input grid values from INDT to 1 and from
SET TO 1 values to INDT
MATH FUNCTIONS Gives you the various outputs of Math functions: arccos,
arcsin, arctan, cosine, hcosine, exponential, natural_log,
log_10, sine, sineh, tangent, tangenth
PRESERVE INSIDE Given a constant or grid upper and lower limits the
BAND INPUT1 grid will be trimmed above and below these
values. Idealistically the resultant would look like a donut
grid:
Input
Band Upper - 20
Band Lower - 10
10
20 30
Output
Resultant
10
20 Grid
BLANK INSIDE BAND Given a constant or grid upper and lower limits the
INPUT1 grid will be blanked inside these values.
GENERAL Does a calculation on the grid in the form:

POLYNOMIAL a0 + a1*x + a2*x2 + a3*x3 + a4*x4
VELOCITY, ISOPACH Produces Velocity, Isopach and Isochron from INPUT1

& ISOCHRON
V0 given DEPTH, Works out V0 given the Depth, Error and K from INPUT1
ERROR & K

Process Dialog
Merge Shallow/Merge Deep Examples

Given two grids called ‘Shallow’(Input1) and ‘Deep’(Input2):
“Shallow” “Deep”
Input1 Input2
Shallower Deeper
Deeper Shallower

Process Dialog
‘Merge Shallow’ Process ‘Merge Deep’ Process

# MERGE SHALLOW # MERGE DEEP
extern input1,input2,result extern input1,input2,result
if(indt(input1) || indt(input2)) { if(indt(input1) || indt(input2)) {
result = INDT result = INDT
} else { } else {
if (input1 < input2) { if (input1 > input2) {
result = input2 result = input2
} else { } else {
result = input1 result = input1
} }
} }
Note: You can work on these examples yourself by accessing the ‘merge deep & shallow’
directory containing the binary file and a workflow from within the VelPAK training set
of directories.

Process Dialog

Processing Methods displayed in VelPAK come from two text files; one is the set file supplied
with the system which can not be altered. The other file is a ‘User-Defined’ text file containing
processes written originally by the Users. An original ‘User-Defined’ file is also supplied with
VelPAK but this can be edited from the original by a user.
Tip: Always make a back up of the user-defined process text file before attempting to write
your own method.
The language that the processes are written in is the same as that which the Depth
Conversion methods are written in. For more details of this language Go Here.

Depth Dialog
Depth Dialog
For Depth Conversions of Profile data use the Depth tab within the Profile Module.
The depth conversion methods are set up from within the Depth Option module.
Note: Each set up refers to one event horizon. Once you have set up the Process run for
one event horizon select a new event horizon from the Surface&Slot selector or
Model Tree and then select the process to occur on that event horizon.
The depth conversion option can use the values, such as V0 and k, created by the
‘OPTIMIZE’ part of VelPAK. If you select a Depth Conversion method that uses these values,
they will be automatically displayed to show what values are being used.
Within VelPAK depth conversion options, there are a certain number of depth conversion
methods already defined. These can be utilized for any given layer, either by using the
calculated values generated via the Optimize option or by inserting the correct variable
values, according to your depth conversion parameters.
These ready-stored depth conversion contain all the usual methods you would expect; such
as Interval Constants, Interval Grids and Curves, as well as a number of standard formulae
such as velocity varying with two-way time.
However, there is the added dimension within VelPAK’s depth conversion in that you can
write their own methods, or amend the ready stored methods, and save them for future use.
The Depth Conversion methods within VelPAK are written in a language called Xpress. This
has been specifically designed so that it is possible for non-programmers to write the text for
a new depth conversion method. For details of writing your own methods Go Here.
Tabs include:
General tab - setting up the event horizons to be depth converted.
Setting up the Formula to use in the Parameter Tab will change the Parameter banks in the
Property Grid. These banks of information will change from simply saying Unused to being
filled in with inputs such as Name: vel, Type Input ..etc. Each of these Parameter banks relate
to an input or output element from the defined depth conversion formula for this event
horizon.

Depth Dialog
Depth Dialog - General Tab
Option
Type - Select whether the Depth Conversion to be set up under the Parameters tab is to
run on just the current event horizon or whether all Depth Conversions set up for all event
horizons are to be activated.
Initially you would probably set this to Current_Event as you set up the parameters for
each event horizon separately and run them; but once you have set the depth conversion
up for each event horizon you would probably set this to All_Events to be able to run the
depth conversion again for all layers in the event horizon of changing one layer.
Verify - will verify the parameters set up before running.

Depth Dialog
Depth Dialog - Parameter Tab
Input
Bank 01
Input
Bank 02

Depth Dialog
When you have made your edits. Press to activate the option.
Options
From - Specify where the values are to some from:
User Defined
You can enter your own parameters directly into the appropriate Parameter banks below
this input.
Optimize
Selecting an Optimize option will call in the relevant parameters as derived from the
Optimize module.
Note: Your Depth Conversion method here would have to be the same as the method used
to derive the parameters in Optimize.
User - The point selected by the User in the Optimize module.

Fit - The point fit derived from the values of V0 and K that best fit the well curve
information.
Residual - The point residual, the point along the ‘zero error’ line that is closest to the
Point fit.
Curve Fit
The parameters are drawn from the values derived from the Curve Fit module. If using
this option, you MUST select the Depth Conversion method that relates to the Curve Fit
routine:

Depth Dialog
Input/Output Banks -
various fields with the names of the input/outputs it requires. Other fields have to be filled
in by you if you have specified User as where the information for your Depth Conversion
is coming from.
For example:

Depth Dialog
Variables
The formula for “SIMPLE INTERVAL

VELOCITY” has a number of variables either
input or output. Each one of these variables has
a separate Input bank telling the program which
slot in the Model Tree to find the input or result. .
Go Here for further details of the Expanded Slots
definition
01_Name - The name of the first input to be defined. This is automatically entered as a
named variable from the formulae list (as shown in the example above).
01_Value - If the input is a constant value, the value will be entered here. If you have
selected ‘User’ as where your depth conversion method will come from you must enter a
value in this slot. If you have selected an Optimize or Curve method to be used for your
depth conversion method then this value will be filled with the a0 value derived
(standardly the V0 value).
If a Grid is to be used and not a Constant then the following are to be entered...
01_ GridDesc - The name of the grid (as displayed in the Properties panel and Model
Tree).
01_GridEvent - ** User Entered ** - The Event Horizon under which the grid to be used
as input 01 is stored in the Model Tree Note the Previous / Current option which allows

Depth Dialog
you select the Previous or current event horizon rather than name a specific event
horizon where the grid is to be found. Usually this option is only utilized when constructing
Generic Workflows which can work on any event horizon.
01_GridType - ** User Entered ** - The slot under the event horizon in the Model Tree
where the grid is stored.
The Expanded Data Slots in the Model Tree

For Depth Conversion supplemental data
If you expand the data slots of the Model Tree in the ‘Show Unused’ mode you will see that
under every Data Type under the Surface element there are 32 data slots each with a unique
name.
For an example:
The Depth Conversion method LINEAR (V0+KZ) has a number of these slots defined for use.
You can see these if you go into the Formula tab once you have defined the method from the
Parameters tab:

Depth Dialog
Toggle On

Depth Dialog
Depth Dialog - Formula Tab
Depth Formulae Available

ONE WELL TIME-DEPTH CURVE (Note: this will only be available for selection if the
Single Well has been selected within the Well Log module Go Here)
LINEAR (V0+KZ)
LINEAR WITH UPLIFT FROM BASE
HOUSTON
BINOMIAL
SLOTNICK
FAUST
HYPERBOLIC TANGENT
PARABOLIC
CurveFit [XXXX] - various methods derived from Standard Curve functions from the
Curve Module. Go Here for details of Curves. The Curve number here relates to the curve
number under the Standard Curve.
Optimize [XXXX] - various methods derived from the Optimize Module. Go Here for
details.

Depth Conversion Methods displayed in VelPAK come from two text files; one is the set file
supplied with the system which can not be altered. The other file is a ‘User-Defined’ text file

Depth Dialog
containing processes written originally by the Users. An original ‘User-Defined’ file is also
supplied with VelPAK but this can be edited from the original by a user.
Tip: Always make a back up of you-defined process text file before attempting to write your
own method.
The Language used in Depth Conversion

Language Definition of Xpress
Xpress is case-sensitive like C.
Spaces are only significant inside quotes (i.e. a character variable).
It is not fussy about integer or real - everything is converted to double precision floating point.
Xpress is a formula evaluator with a C-like syntax. It is case-sensitive, like C, and spaces are
only significant within quotes.
Depth Conversion Supplied Variables/Functions

VelPAK depth conversion is defined using a C-like syntax called Xpress. This gives you great
flexibility to define any method they may choose.
The standard methods supplied with VelPAK are defined in an ASCII file that resides in
$TOPIXDIR/sys/formula.txt.
VelPAK reserves the following key words:
time Current event horizon two way time msecs

last_time Previous event horizon two way time msecs
last_depth Previous depth
depth Result of depth conversion (all methods must resolve down to
‘depth=’)
x X location
y Y location
shot Shotpoint

Depth Dialog
mask Binary mask value of the current point being depth converted.
This can be viewed interactively in a profile window by using
point pick mode and checking the resulting information
vdown_array - not guaranteed correct in overthrust situations contains and
array of velocity down values that correspond to the
intersections above Values can be retrieved using the new
xpress user function called getarr - see below
depth_array - not guaranteed correct in overthrust situations contains and
array of depth values that correspond to the intersections above
Values can be retrieved using the new xpress user function
called getarr - see below
inflect Contains a 1 if are in a reversal zone Contains a 0 if we are not
“fault” Contains a 1 if not on a fault Contains a 0 if we are not
real_event Contains a 1 if converting real existing data points and Contains
a 0 if we are converting virtual intersections with other event
horizons
multi_event Contains a 1 if there are multiple intersections with this event
horizon, down from the surface Contains a 0 if there are not.
current_event Contains the current event horizon number we are depth
converting This is also set for virtual intersections, down from
the surface
total_intersect Contains the number of intersections down from the surface to
this point
current_intersect Contains the current intersection we are depth converting
event_array contains and array of event horizon numbers that correspond to
the intersections above Values can be retrieved using the new
time_array contains and array of time values that correspond to the
intersections above Values can be retrieved using the new
vel_array - not guaranteed correct in overthrust situations contains and

array of velocity values that correspond to the intersections
above Values can be retrieved using the new xpress user
function called getarr - see below
vup_array - not guaranteed correct in overthrust situations contains and
array of velocity up values that correspond to the intersections
above Values can be retrieved using the new xpress user
function called getarr - see below

Depth Dialog
plot(x,y,color,size) e.g.: plot(shot,time,2.0,3.0) - plot big red blob at current shot,

time. See below for color table.
getarr(“xxxx_index) e.g.: time=getarr(“time_array”,3) - get 3rd intersections time
value down from the surface
Color Table used in Plot Command

Pen Color
Attribute
1 White
2 Red
3 Deep Purple
4 Light Purple
5 Dark Blue
6 Light Blue
7 Turquoise
8 Blue Green
9 Deep Green
10 Light Green
11 Yellow
12 Orange
13 Brown
14 Dark Grey
15 Light Grey
16 Black
Expressions
Expressions must consist of one of the following:
numeric constant e.g. 5, 123.4
character constant e.g. “ABC”
variable e.g. time, temp1
expr operator expr e.g. var1+10.2, diff^2
- expr e.g. -3, -intvel
(expr) e.g. (total*10)

Depth Dialog
Brackets may be used to override normal operator precedence and may be nested to any
level.
^ exponentiation
- unary minus (negation)
*/ multiplication, division
+- addition, subtraction
Logical Expressions
Logical expressions have the following syntax:
expr lop expr e.g. sum<10.1, var!=5
< less than

<= less than or equal
== equal
!= not equal
>= greater than or equal
> greater than

Depth Dialog
Functions
Xpress has a rich set of built-in functions. All function arguments may be either constants or
variables. Functions have the following syntax: function(arguments) e.g. log(x),
grid(“GGTIME”,x,y).
abs(x) absolute value of x

acos(x) arc cosine of x
asin(x) arc sine of x
atan(x) arc tangent of x
atan2(y,x) arc tangent of y/x
cos(x) cosine of x
cosh(x) hyperbolic cosine of x
exp(x) exponential function e^x
mod(x,y) remainder of x/y with same sign
as x
log(x) natural logarithm of x
log10(x) logarithm, to base 10, of x
sin(x) sine of x
sinh(x) hyperbolic sine of x
sqrt(x) square root of x
tan(x) tangent of x
tanh(x) hyperbolic tangent of x
grid(file,x,y) interpolated value from grid file,
at coordinate x,y
curve(file,x) interpolated value from curve
file, at x
Control Flow
a. If-Else
if(lexpr) {
statements
} else {
statements
}
b. Else-IF

Depth Dialog
if(lexpr) {
statements
} else if(lexpr) {
statements
} else if(lexpr) {
statements
} else {
statements
}
Comments
Comment lines start with a # (hash) and are ignored by the parser.
Statements
A statement must consist of one of the following:
variable=expression e.g. total=sum1*(value-1.2)
control flow statement (if, else if, else)
comment
Example
Clearly the Xpress language is a powerful tool for writing virtually any depth conversion
method.
For example, supposing a multi-variant statistical method has been derived where:
V=(X*A)+(Y*B)+(2WT*C)+(ISOC*D)+E
X=X UTM coordinate
Y=Y UTM coordinate
2WT = Two way time in msecs
ISOC = Interval time in msecs
A = -0.02
B = -0.03
C = 1.6
D = -2.4
E = 112328
The Xpress code would be as follows:
a = -0.02
b = -0.03
c = 1.6
d = -2.4
e = 112328
isoc = last_time - time
intvel = (x*a)+(y*b)+(time*c)+(isoc*d)+e
isop =intvel * (isoc / 2000)
depth = last_depth + isop
Listing of VelPAK’s Depth Conversion Formulae

Depth Dialog
LINEAR (V0+KZ)
Discussion:
Linearly accelarating velocity function1
# LINEAR (V0+KZ)
# V = Vo + kZ
if (indt(v0) || indt(k) || indt(last_time) || indt(time) ||

indt(last_depth) || indt(error)) {
depth=INDT
} else {
if( v0==0.0 && k==0.0) {
depth = last_depth
} else if( k==0.0) {
} else {
tmp1 = exp((k * isoc_owt_secs))
depth = tmp2 + (v0 / k * (tmp1 - 1))
depth=depth+error
1.Least Square Determination of the Velocity function V=V0 + KZ for any set of time depth data - Geo-
physics Volume 8. J.A. Legg Jr. J.J. Rupnik.

Depth Dialog
LINEAR WITH UPLIFT

Discussion:
Linearly accelarating velocity function with uplift component
# LINEAR WITH UPLIFT
# V = Vo + kZ - pkZ
# t
extern v0,k,p,last_time,time,last_depth,depth,error
if (indt(v0) || indt(k) || indt(p) || indt(last_time) || indt(time) ||

depth=INDT
} else {
if( v0==0.0 && k==0.0) {
depth = last_depth
} else if( k==0.0) {
v01 = v0 - k * p * last_depth
} else {
tmp1 = exp(k * isoc_owt_secs)
depth = tmp2 + (tmp1 - 1) * (v0 - k*p*last_depth) / k
depth = depth + error

Depth Dialog

# LINEAR FROM SEA FLOOR
# V = Vo + kZ - kS
extern v0,k,last_time,time,last_depth,depth,error,sea_floor

indt(last_depth) || indt(error) || indt(sea_floor)) {
depth=INDT
} else {
if( v0==0.0 && k==0.0) {
depth = last_depth
} else if( k==0.0) {
} else {
tmp1 = exp(k * isoc_owt_secs)
depth = tmp2 + (tmp1 - 1) * (v0 - k*sea_floor) / k
HOUSTON
# HOUSTON
# 1/2
# V = Vo.(kZ + 1)

Depth Dialog

depth=INDT
} else {
if( v0==0.0) {
depth = last_depth
} else if( k==0.0) {
depth = error + last_depth * v0 * isoc_owt_secs
} else {
tmp1 = isoc_owt_secs *v0 * k / 2
tmp2 = sqrt(k * last_depth + 1)
depth = ((tmp1 + tmp2) ^ 2 - 1) / k
BINOMIAL
# BINOMIAL
# 1/m
# V = Vo.(kZ + 1)
extern v0,k,m,last_time,time,last_depth,depth,error

Depth Dialog
if (indt(v0) || indt(k) || indt(m) || indt(last_time) || indt(time) ||

depth=INDT
} else {
if( m==0.0) {
depth = INDT
} else if( v0==0.0) {
depth = last_depth
} else if( k==0.0) {
} else if( m==1.0) {
tmp = ( 1 + k * last_depth) * exp( k * v0 * isoc_owt_secs)
depth = error + ( tmp - 1) / k
} else {
p = (m-1)/m
tmp1=(k*last_depth + 1)^p
tmp2=(p*k*v0*isoc_owt_secs + tmp1) ^ (1/p)
depth=(tmp2 - 1)/k
depth=depth+error
SLOTNICK
# SLOTNICK
# kZ
# V = Vo.e

Depth Dialog
extern v0, k, last_time, last_depth, time, depth, error
if (indt(v0) || indt(k) || indt(last_time) || indt(last_depth) ||

indt(time) || indt(error)) {
depth = INDT
} else {
if( v0==0.0) {
depth = last_depth
} else if( k==0.0) {
} else {
tmp1 = exp((-k) * last_depth)
tmp2 = v0 * k * isoc_owt_secs
tmp3 = 1 / (tmp1 - tmp2)
depth = (1/k) * log(tmp3)
FAUST1
# FAUST
# 1/m
# V = a.Z
extern a,m,last_time,time,last_depth,depth,error
1.Seismic Velocity as a function of depth and geological time. Geophysics Volume 16. L.Y. Faust

Depth Dialog
if (indt(a) || indt(m) || indt(last_time) || indt(time) || indt(last_depth)

|| indt(error)) {
depth=INDT
} else {
if( m==0.0) {
depth = INDT
} else if( a==0.0) {
depth = last_depth
} else if( m==1.0) {
depth = error + last_depth * exp( a * isoc_owt_secs)
} else {
# Calculate one way time in seconds
time_secs = time / 2000
tmp1 = (m - 1) / m
if(last_time == 0.0) {
depth = ((a * tmp1) * time_secs) ^ (1 / tmp1)
} else {
tmp2 = ((a * tmp1) * isoc_owt_secs)
depth = ((last_depth ^ tmp1) + tmp2) ^ (1 / tmp1)
depth=depth+error

Depth Dialog
HYPERBOLIC TANGENT
# HYPERBOLIC TANGENT
# V = V tanh(aZ + b)
# 1
extern a, b, v1, time, depth, last_time, last_depth, error
if (indt(a) || indt(b) || indt(v1) || indt(time) || indt(last_time) ||

depth = INDT
} else {
a1 = a/1e6
b1 = b/1e3
if( v1==0.0) {
depth = last_depth
} else if( a==0.0) {
depth = error + last_depth + v0 * tanh( b) * isoc_owt_secs
} else {
tmp1 = sinh(a1 * last_depth + b1)
tmp2 = exp(a1 * v1 * isoc_owt_secs)
tmp3 = tmp2 * tmp1
tmp4 = log(tmp3 + sqrt(1 + tmp3^2)) - b1
depth = tmp4 / a1

Depth Dialog
PARABOLIC
# PARABOLIC
# 1/2
# V = (w + eZ)
extern e, w, time, depth, last_time, last_depth, error
if (indt(e) || indt(w) || indt(time) || indt(last_time) || indt(last_depth)

|| indt(error)) {
depth = INDT
} else {
if( e==0.0 && w<=0.0) {
depth = INDT
} else if( e==0.0 && w>0.0) {
depth = error + last_depth + sqrt( w) * isoc_owt_secs
} else {
tmp1 = sqrt(w + e * last_depth)
tmp2 = e * (isoc_owt_secs ^ 2) / 4
depth = last_depth + isoc_owt_secs * tmp1 + tmp2

Discussion:
Each isochron is assigned a constant interval velocity and the resulting isopach is added to
the previous depth.
# SIMPLE INTERVAL VELOCITY

Depth Dialog
extern vel,last_time,time,last_depth,depth,error
if (indt(vel) || indt(last_time) || indt(time) || indt(last_depth) ||

indt(error)) {
depth=INDT
} else {
depth = (isoc_owt_secs * vel) + last_depth

Discussion:
A constant average velocity is applied to the one-way time in seconds.
# SIMPLE AVERAGE VELOCITY
extern vel,time,depth,error
if (indt(vel) || indt(time) || indt(error)) {
depth=INDT
} else {
# Calculate one way time in seconds

Depth Dialog
time_secs = time / 2000
depth = (time_secs * vel)
ONE WELL TIME-DEPTH CURVE

Discussion
Well to be used must be selected within the Well Module. Go Here
# [General] ONE WELL TIME-DEPTH CURVE
# Given seismic time from grid, interpolate depth from nominated well
time-depth curve
extern
last_time,time,last_depth,depth,error,isochron,isopach,interval_velocity,av
erage_velocity
if (indt(last_time) || indt(time) || indt(last_depth) || indt(error)) {
depth = INDT
isopach = INDT
isochron = INDT
interval_velocity = INDT
average_velocity = INDT
} else {
depth=well("none",time)
depth=depth+error

Depth Dialog
isopach = depth-last_depth
isochron = time-last_time
interval_velocity = isopach / isoc_owt_secs
average_velocity = (depth * 2000) / time

Trim Dialog
Trim Dialog
Allows you to Trim data in the model, using polygon(s) as control. Polygons are used as trim
control for data either within them or outside the polygons, as selected in the Options.
THIS TRIM IS A FINAL SOLUTION! - data trimmed in the model is not retrievable. It is
recommended that if you trim data, you use the SAVE AS option to save your trimmed data
as a new model, keeping your original data model intact.
You can select what types of data are to be trimmed from the selected polygon area by
selection on the Options page. In ‘Current Event’ mode the trim option will only trim data on
the Event Horizon selected in the Surface&Slot. In this case the Polygon used to trim would
need to be the current selected polygon under the current event. In ‘All_Events’ mode all of
the specified data types will be trimmed for all of the events. In this case the Polygon to be
used to trim can be stored under any event but it must still be the selected, current polygon in
the current event.
Line Data which runs through all event horizons would also be deleted whatever Events are
selected.
You can select more than one Polygon area for trimming in any one trim process; the process
will prompt for a Yes/No against each polygon in the model. By the nature of the trim process
however, this would only work with trimming data inside individual polygons.
For Grids the Trim option will trim just the selected grid under the selected event. The ‘All
Events’ option does not work for Grids.
For details of inserting and defining your Polygons please refer to Polygon Edit Mode.

Trim Dialog
Trim Dialog - General Tab
option.
Option
Events - Choose to Trim data on all event horizons or selected event horizon. Note that
this option is inactive for Grid Trimming which needs to be done event by event.
Type - Choose to Trim your data inside or outside your defined Polygon.
Verify -YES will give you an alert box will pop up for verification of your action before.
proceeding to Trim.
This option is especially useful if you have a number of Polygons defined over an area for
one event horizon and you wish to pick and choose which Polygons you which to trim
within and which you do not.

Trim Dialog
Data
Event, Grid, Location, Stack, Well, XYZ
Select the type of data you which to have trimmed. Note that for Grids the Trim option will
trim just the selected grid under the selected event. The ‘All Events’ option does not work
for Grids.

Group Dialog
Group Dialog
Group controls how wells are grouped together. This can be used to take account of different
geological provinces in the area, or to include / exclude particular wells from the calculations.
Wells can be grouped either by drawing polygons on the surface display, or by editing the
group number of each well. When groups are defined, VelPAK will only use the wells in the
current group. Grouping also applies to stacking velocities.
Draw a polygon around the wells you want to group. Refer to Polygon Edit for details of
inserting Polygons into your VelPAK model. When you apply the Group set-up those wells
inside the Polygon you have just drawn will become grouped.
Note: Editing group numbers with Well Point Edit.

There is an alternative way of assigning a well to a particular group. The Well Point
Edit GIS function allows you to edit the group number. This is a more precise way of
assigning groups, and means that you don’t have to draw a polygon if you just want to
assign a few wells to a group. Also, if you have included a well in a group, and then
decide you don’t want it there, you can edit the group number back to 0, even if it is
still within the polygon. Pressing GROUP overrides all the group number assignments
you have made using this method.

Group Dialog
Group Dialog - General Tab
option.
Option
Active - Some parts of VelPAK operate on the active group only, and this can be changed
by using this value. When grouping is active, all wells numbered 0 are ignored. The
current group of wells is colored white, and the other groups are also color-coded by their
different number. Hence, when grouping is active, the normal well colors (which tell you
how much data are available) are replaced by a color scheme which tells you which group
each well is in. This is particularly important when you have overlapping polygons.
Because VelPAK implements the grouping concept by assigning a number to each well, it
is not possible for one well to be in two different groups. The well color will tell you which
group the well has been put in if it is within a polygon.
Type - Group or Ungroup. The default option ‘Group’ is used to make the groups, while
the ‘Ungroup’ option resets the group number, so all the wells have group 0 as their group
number (i.e. they are not in a group).

Group Dialog
An example of defining Groups
The original data
This is the original dataset, with the wells colored according to their data (in this case all
green showing that they are fully loaded). The current well is black.
1. Select the Event Horizon you are going to be working on.
2. Draw a polygon around three of the wells.
3. Bring out the Group Property Grid and apply the group of wells within the polygon to the
first group by pressing the Activate tick.

Group Dialog
4. The wells are now colored by group rather than by data. The currently active group is
colored black, and wells in group 0 (in other words not in a group) are colored red.
5. Under Edit Mode select Well Location and Point Edit and click on one of the selected,
black wells.
You will see that the box that appears for the well selected will show that this well is now
defined as being in Group 1.
6. Next, draw another polygon around one of the other wells and press Apply Group again.
This will fall into Group 2 since it is in a different polygon to those wells in Group 1.
7. Now, two groups are defined. The new group defined by the smaller polygon has well(s)
colored yellow. This indicates that they are in Group 2. The current group is still Group 1

Group Dialog
so they are still colored black. In order to select Group 2 as the active group, change the
Active Group to 2 in the Property Grid. and press the ‘tick’.
8. The well that is in Group 2 which was yellow has turned black since it is now the active
well. The wells in Group 1 have now changed to being orange in color since they are no
longer active.

XYZ Dialog
XYZ Dialog
XYZ produces or manipulates XYZ data files from the grids stored within the model.
The options are:
Convert
Interpolate
Delete
Copy
Concatenate

XYZ Dialog
option.
Option
Type
Convert converts your grid into XYZ, placing them in the XYZ slot you define in the
Output_XYZ slot. This will produce a XYZ file with XY values at regular spacing exactly as
the Grid nodes were defined
Interpolate will take the random XY values from a selected XYZ datafile in the Input_XYZ
then go to a selected Grid and extract Z values from the Grid at the given random XY
values. A new XYZ data file will be created and placed in the slot defined in Output_XYZ.
You can thus produce any number of XYZ files, all with the same XY values but with new
Z values. Reasons for doing this include determining grid values at specific locations,
such as the XY values of a deviation survey.
Note: Interpolate processes can take some time to complete.
Delete will delete the XYZ data file selected in the Input_XYZ slot.
Copy will allow you to copy the XYZ data file selected in the Input_XYZ slot and place it in
the slot selected in the Output_XYZ.
Concatenate adds the selected XYZ values from Input_XYZ onto the Output_XYZ slot
XYZ file. The result will be stored in the slot selected under Output_XYZ.

XYZ Dialog
Verify- Yes/No
Will bring up an alert clarification showing you what the process is about to do.
Input
Input_Grid - Grid selected from Model Tree to be used in conversion or interpolation.
Input_XYZ - Not used in Convert mode. Select the input XYZ file from which the XYs
are to be used to extract interpolated Z file from the Input Grid file named above.
Output
Output_XYZ - Select slot in the Model Tree where the output XYZ file is to be put.

Well Log Module
Introduction to Well Log Dialog
The Well Module (default display Well Tab) is used to view and specify well curves, tops and
layers and to specify which tops correspond to the top and base of each seismic layer. Grid
thicknesses can be related to portions of the curve as a means of QC.
The layers can be individually selected for each well manually via this module; or can be
automatically derived using the Master Well List produced from the Layer Module.
The Tie dialog can be used as a method to check how well the current depth conversion
method ties to the well data in the model in either volume mode or profile mode. Optionally,
the results from this mode can be used to modify the depth conversion process so that the
wells are tied perfectly.
Select the well that is to be displayed using the Well Selection in the Model tree.
The Data Tab displays a summary of information for all the wells in the model.

Well tab
Well tab
What you are looking at on the Well Display
Sea Floor
Horizon 1
Horizon 2
Horizon 3
} Grid 1
Grid 1 for layer 1
is thickness between
Surface and Horizon 3
Horizon 4
Horizon 5
} Grid 2
Grid 2 for layer 2
is thickness between
Horizon 3 and Horizon 5
}
Horizon 6
Grid 3
Horizon 7 Grid 3 for layer 3
Horizon 8 is thickness between
Horizon 5 and Horizon 8
Tops Curve Grids
Horizon 1
Horizon 2
Horizon 3
Horizon 4
Horizon 5
Horizon 6
Horizon 7
Horizon 8
Viewing a Well

Well tab
When you click the Well Module option,

the current well (as selected from the
Model Tree) will be displayed on the
window.
If there is not enough data loaded for
this well (i.e. it is colored red or blue on
the map display) then a message to
this effect will be displayed on the
window.
Otherwise, the velocity curve for the
well will be displayed.
For the event horizon you have
currently selected in the Model Tree or
Surface&Slot Selector: If the well pierces
the time grids at the top and base of the
layer, the right hand side will be
highlighted to show you roughly where
Well: 12/34a the layer is.
Well has no curve
Well has no tops
Note: If the well does not pierce a time grid at top and base of the layer, there will be no
highlighting.
The grid titles are displayed on the Well display. If the grid label is empty (“None”) or auto-
generated (“XPRESS”) then the posted label is taken from the Surface name, otherwise the
user defined grid label is posted

Well tab
Manual Selection of the grid thicknesses on the curve from the

Tops
Unless you use the semi-automated (and therefore much quicker) Layer Tool to define your
layers within your model from a Master List, for every time grid you wish to use within the
model you will need to specify the layer your grid represents on the curve, for each event
horizon and for every well.
Note: Your TIME grid must be stored in the TIME GRID slot within the Model Tree for the
relevant event horizon i.e. NOT the DEPTH GRID slot, not the General 01 SLOT etc.
The normal procedure for selecting the tops is to start with Event 1 and the first well curve.
You then select the tops corresponding to Time grids.
A detailed example of how to pick Tops follows is here.

Data tab
Data tab
For a better understanding of the well layer properties, there is a summary Data table tab in the Well
display.
This table can be copy/pasted to Excel etc. by clicking on the top left hand corner of the table to
highlight the whole data area.
Details of how this data table can be sorted and the columns filtered is documented in the
Curve chapter here.
Details of what each columns means can be found at the end of this chapter here

Display Types
Display Types
Select type of Well Curve to display:

Time/Depth
Visible Layers
Only ‘None’ is currently available for Layer to have displayed on the Well Log. This can not be
turned off.

Edit Mode
Edit Mode
Select what EDIT mode you are in; whether you are in TOPS edit mode or CURVE edit
mode.
activated. The bottom right of the VelPAK window displays what edit mode you are in.
Switching between the two you will notice the Edit options (icons to the right of mode) will
change according to what edit options are available under which mode.
Tops Mode Edit:

Tops Edit functions:
Point Insert : Delete : Edit : Pick
Tip: Use Tops Pick to manually select Layer Tops/Bases. Go here for details.
Insert
Used to insert a new top in your well display in depth or time (depending on the current
axes). Press the mouse button at the point on the curve you wish to enter a new Top.

Edit Mode
When you release the mouse a dialog box will pop up showing the time or depth you have
selected and asking you what you want to call the top.
Delete
Click on Delete and select a well to delete. An alert box will pop up for verification.
Edit
Click on a top to rename it or change the time or depth. An alert box will pop up for you to
edit the values.

Edit Mode
Pick
Pick mode is used to select and deselect the layers to define each layer.
Click on Top to
define layer for
event 1
After selecting tops for the first well, move onto the next well in the model, select the
thickness that represents the time grid and so on.
After completing the selection for Event 1, select Event 2 and repeat the selection
process for each well.
You can then repeat the process for the remaining event horizons.
A detailed example of how to pick Tops follows is here.

Edit Mode
Curve Mode Edit:

Curve Edit functions:
Point Insert Delete Move
Split
Note: Curve editing must be done in Depth mode.
Insert
Used to insert a new curve point in your curve.

Edit Mode
Delete
Click on Delete and select a curve point to delete.
Note: There will be no alert to warn you are deleting curve points but you will be able to see
that you have ‘hit’ or ‘missed’ the points to delete by looking at the Console window
information.
Move
Move a curve point.

Split
Splitting a Sonic Log - Click on the point of the sonic curve down to which you which the
sonic to be deleted.
Set as Depth Conversion Well

Using the Button ‘Set as single well’ the user can select the current well as the single well to
use for depth conversion. Within the Depth Conversion module the General formula ‘One
Well Time Depth Curve’ must be used to read this well.
Find depth conversion well - Makes VelPAK jump to whichever well in the model has
been selected as the single well to use within depth conversion.

Edit Mode
Set as Find
Single Depth
Well Conversion
Well

Well Log Display General Dialog
option.
General Tab
Option
Display_Type - Select between Time or Depth display for the well.
Overlay_Model - Yes/No - overlays the current depth converted velocity curve function.
Overlay_Stack - Yes/No - View your stack (pseudo) wells if you have a created them (via
the Amalg option of the Velocity module. Particularly useful if you have created them at
your Well Location so you can compare the two. Moving on to another well on the display
using the red arrows will move this display on to the next well too.

Overlay_Well - select which well (if any) you wish to overlay on top of the well selected.
Default of blank will not overlay any well trace. Moving on to another well on the display
using the red arrows will NOT move this display on to the next well too.
Show_Events - Choose between ALL Event Horizons being shown (as Grids to the right
and picked layers to the left of the well curve) or just ‘Current’ being the event horizon
currently selected in the Surface&Slot.
ALL Event Horizons Displayed Current Event Horizon Displayed
Top_Type - Choose to display which tops are to be displayed on your well display:
All - displays all formation tops in the model for the current well
Layer - displays only tops used in the layer definition
Used - displays all tops flagged as “Used” in the Layer definition table
UsedAndExtra - displays all tops flagged as “Used” and “Extra” in the Layer definition
table
Range Tab

Allows the user to set the range of the well display.

Tie Dialog
Tie Dialog
Tie can be used as a method to check how well the current depth conversion method ties to
the well data in the model.
Optionally, the results from this dialog can be used to modify the depth conversion process so
that the wells are tied perfectly. Activating the TIE process produces X,Y, Z error points and
these need to be gridded to form an ‘ERROR’ grid.
Tip: After TIE has run you will need to go to the GRID option in the Surface Module and set
up a Grid run from these XYZ values generated.
Note: The TIE option honors the Residual Flag within the Data Tab of the Curve and
Optimize modules. If the Residual Flag for a well is turned off within the Data tab it will
not be used to produce the Error XYZ data file here.
At each well position, TIE uses the current depth conversion method to calculate a depth at
each well. This depth is the depth which you would get if you were to depth convert the entire
time grid. You do not need to have activated the Depth Conversion set-up before using this
option, but you do need to have gone into the Depth Property Grid and selected your depth
conversion method.
CURVE DATA TIME GRID DATA
Depth Grid 1
DEPTH
Depth Grid 2
Straight or
Deviated Wells
In order to activate the TIE feature, the wells in your model need to have had the Well
Layers from tops defined for each layer via Layer Module or as previously described in
the Edit facilities of this module.
Note: To use the Grid or Curve Depth Conversion the Time Seismic grids need to be
available and defined for each layer.
Note: TIE sets the values of the ‘error’ slot in the Depth Conversion Parameter page to zero
because it uses the depth conversion formula to work out what the error should be;
the reason for this being if an old error grid was present then the TIE procedure would
give you the error INCLUDING the old error grid and thereby give you an erroneous
result.

Tie Dialog
Tie Dialog - General Tab

The option will act according to the OPTION information set up for the Tie Process for that
procedure.
option.
Reset Error Before/Reset Error After-

Reset Error Before
This will produce a set of XYZ values in the Error slot of the Model Tree which can be
gridded up and used in the the Depth Conversion method in the standard way as
described.
Reset Error After
This will give the Depth Error of the Depth Grid at the point BOT_XY. If all the wells have
been tied then the resultant values here should be zero. So this acts as a useful check.
Also it can be used as a means of cross-validation of wells in the model by excluding a
valid well from the Depth Conversion (by de-selecting it in the Optimize Residual data tab)
and seeing what value the Depth Conversion with Error produces for this well. Values will
appear in the ’Error After’ slot of the Model Tree.
Tie_Type:
Time_Grid_Converted - This option uses the time grid as the source of the time. It will
calculate the errors at the wells, producing X,Y, Z error points.

Tie Dialog
After TIE has run you will need to go to the GRID Dialog to set up a Grid run from these
generated XYZ values.
The file will be stored under the Error XYZ slot for the relevant event horizon. For
Time_Grid_Converted option the file will be called Depth Errors(Tie to Time Grid).
Time_Curve_Converted - This option uses the CVL time from the Well Curves as the
source of the time. It will calculate the errors at the wells, producing X,Y, Z error points.
After TIE has run, you will need to go to the GRID Dialog page to set up a Grid run from
these XYZ values generated.
The file will be stored under the Error XYZ slot for the relevant event horizon. For
Time_Curve_Converted option the file will be called Depth Errors(Tie to Curve Grid).
Note: The time grid method will interpolate the depth value at the top of the layer from the
defined depth grid. The time-depth curve method will use the stored Top. Therefore, if
the previous depth grid has not been TIED to the wells, the different errors obtained
by the two techniques may not be entirely due to the CVL/seismic time mistie.
General comments for producing the best Error Grid via this method
1. The Grid spacing for the error grid must be small enough to account for the error values
from each well spot.
2. If you are using the depth conversion methods that rely on conditional variables, care
must be taken that these conditional variables act as you want them to act. These can be
tested using the ‘plot’ option within the Depth Conversion.

Calibrate Dialog
Calibrate Dialog
The Well Calibration module assigns a time to a depth on a log. If you have a log that has not
been processed from the surface then the time curve will start at a different place to the depth
curve. The Calibrate module assigns an adjustment to the time curve, either by using a grid
layer to shift the curve or by using a constant value.
Note: The calibration technique only works on Uncalibrated logs.
This is a simple method of calibration that does not rely on Check Shot data.
Calibrate Dialog - General Tab

option.
General
Option
Type - Choose to use an Event to base the shift on, a Constant or to Uncalibrate the
log. Using an Event Horizon will shift the log so that the chosen event horizon is aligned
(in time) to the picked top for the layer.
Wells - Current well or All wells in the model to apply the calibration to.
Value
Constant - If you have chosen ‘Constant’ as your Type, this is the constant time shift
value to apply.
Event - If you have chosen ‘Event’ as your Type, this is the event horizon to use for the
time shift.

Calibrate Dialog
Using the Calibrate option

1. Check that your well log is ‘Uncalibrated’. You can tell from the title of the log plot as
follows
Note: VelPAK assumes that check-shots or time-depth curves are ‘Calibrated’ i.e. the times
are good, so only ‘Uncalibrated’ will appear in the title if they are not calibrated.
2. To reset the status of the well change the type to 'Uncalibrate' as follows:
3. Once this done then the well can be re-calibrated in two ways:
a. Either a constant shift:

Calibrate Dialog
or
b. Use the Two way time from the an event (surface), this is the more common option
Before After

Manually Picking Tops

For every time grid you wish to use within the model the layer your grid represents on the
curve must be defined, for each event horizon and for every well. This can be done manually
in this option, or by use of a MASTER WELL LIST produced in the Layer Dialog (which you
will find a much quicker option).
Note: In order that your Time grid is found and used it grid must be stored in the TIME
GRID slot within the Model Tree under the relevant Event; i.e. NOT the DEPTH GRID
slot, not the General 01 SLOT etc.

Viewing the Well and Picking the Tops
When you click the Well Module option,

the current well will be displayed on the
window.
If there is not enough data loaded for
this well (i.e. it is colored red or blue on
the map display) then a message to
this effect will be displayed on the
window.
Otherwise, the velocity curve for the
well will be displayed.
For the event horizon you have
currently selected in the Model Tree or
Selector: If the well pierces the time
grids at the top and base of the layer,
the right hand side will be highlighted to
show you roughly where the layer is.
Well: 12/34a
Well has no curve
Well has no tops
Note: If the well does not pierce a time grid at top and base of the layer, there will be no
highlighting.
The normal procedure for selecting the tops is to start with Event 1 and the first well curve.
You then select the tops corresponding to Time grids.
Note: You must be in Tops Point Pick mode to select your top.

Tops Edit functions: Point Insert Pick
Event 1 will be from the Surface. Select the Surface by pointing the cursor arrow on the
‘Hidden Top’ at the zero time. (To find the ‘Hidden Top’ you can zoom out on the display to
see it). This defines the top of the layer. Then point the cursor on the Top that should
represent the base of the layer represented by the Time grid for event 1.
Select the top

that represents
the base of the
grid.
x1
Left Hand
Side of Right Hand Side of curve
curve: displays thickness of Grid
displays
thickness
Any discrepancy To CANCEL your pick,

select the Top again.
The shading will
disappear, allowing you
Event2: Follows on immediately from event 1.

Select event 2 from the Model Tree or Surface&Slot selector. The curve will be displayed
ready to select the top and bottom Tops to be defined as your Event 2 layer.

Select the Top that

represents the top of
the grid.
x1 Select the Top that
represents the bottom
of the grid.
Grid thickness will be
displayed to the right.
(Note discrepancy in
To CANCEL your pick
top or bottom, select the
top or bottom Top again.
The shading will
disappear, allowing you
to select a new Top (top
or bottom). (You will not
be able to select a
If no grid is being picked up

by the tops program, you
will see a display like this,
with no display to the right
When you have gone through and selected all the grid thicknesses you want to have
defined within your model, you will select another well and do the process again. (You
could also go through your model selecting Event One’s thickness on the Tops for all
wells, and then select Event two, define the Tops for all wells, and so on.)
Display of all Grids on one Well Curve

There are two methods to display ALL the Grids and Layers on the Well Curve display.
Either:
Use the Show_Event ALL option from the Well Display Property Grid.
or:

Selecting Surface 0 (Faults) from the Model Tree or Surface&Slot selector will display all the
picked grid thicknesses for the well you are currently viewing.

Well Data Type Listing

Summary
WELL_NAME Well Name

SURF_X Surface X location The X surface location of the well.
This is taken from the well location
data, not from the time-depth curve
SURF_Y Surface Y location The Y surface location of the well.

This is taken from the well location
data, not from the time-depth curve
TOP_X X location of top of layer The X surface location of the well

bore at the top well pick. The value
is interpolated from the well curve
data at TOP_DEPTH. ‘A’ on the
diagram here.
TOP_Y Y location of top of layer The Y surface location of the well

bore at the top well pick. The value
data at TOP_DEPTH. ‘A’ on the
diagram here.
MID_X X location of midpoint of The X surface location of the well

bore at the mid-point depth between
layer the top and base well picks. The
value is interpolated from the well
curve data at MID_DEPTH. ‘C’ on
the diagram here.
MID_Y Y location of midpoint of The X surface location of the well

bore at the mid-point depth between
layer the top and base well picks. The
value is interpolated from the well
curve data at MID_DEPTH. ‘C’ on
the diagram here.
BOT_X Xlocation of base of layer The X surface location of the well

bore at the base well pick. The value
data at BOT_DEPTH. ‘B’ on the
diagram here.

BOT_Y Y location of base of layer The Y surface location of the well

bore at the base well pick. The value
data at BOT_DEPTH. ‘B’ on the
diagram here.
TOP_TIME Time from time-depth The time at the top well pick. This
value is obtained by interpolating the
curve at the top of the time-depth curve at Top_Depth.
layer
TOP_DEPTH Depth at the top of the The depth at the top well pick.
layer
TOP_TIME_GRD Depth from time grid at The value of the top time grid
top of layer using T-D interpolated at the top well pick (i.e.
at TOP_X, TOP_Y)
curve
TOP_DEP_TIM_GRD Depth from time grid at Interpolate Depth from T-D curve
top of layer using T-D using time from time grid at TOP_X,
curve TOP_Y. These are the values
displayed on the right-hand side of
the WELL TOPS display in velocity-
depth mode
TOP_TIM_DEP_GRD Time from depth grid at Interpolate Time from T-D curve
top of layer using T-D using depth from depth grid at
curve TOP_X, TOP_Y
TOP_DEPTH_GRID Depth from depth grid at TOP_DEPTH_GRID at TOP_X,

top of layer TOP_Y
TOP_TIM_GRD_BOT Depth from depth grid at TOP_TIME_GRID at BOT_X,

BOT_Y
top of layer,at XY of base
of layer
TOP_DEP_GRD_BOT Time from time grid at top TOP_DEPTH_GRID at BOT_X,
BOT_Y
of layer, at XY of base of
layer
TOP_WELL_AV Average well velocity from TOP_DEPTH / TOP_TIME *2000
surface to top of layer
TOP_APP_AV Apparent average velocity TOP_DEPTH / TOP_TIME_GRD
from surface to top of *2000
layer

TOP_RES_AV Resultant average velocity TOP_DEPTH_GRID /

from surface to top of TOP_TIME_GRD
layer *2000
MID_TIME Time at midpoint of layer

MID_DEPTH Depth at midpoint of layer
BOT_TIME Time from TD curve at
base of layer
BOT_DEPTH Depth of base of layer
BOT_TIME_GRD Time from time grid at
base of layer
BOT_DEP_TIM_GRD Depth from time grid at
base of layer
BOT_TIM_DEP_GRD Time from depth grid at
base of layer
BOT_DEPTH_GRD Depth from depth grid at
base of layer
BOT_WELL_AV Average well velocity from BOT_DEPTH / BOT_TIME *2000
surface to base of layer
BOT_APP_AV Apparent average velocity BOT_DEPTH / BOT_TIME_GRD
*2000
from surface to base of
layer
BOT_RES_AV Resultant average velocity BOT_DEPTH_GRD/
BOT_TIME_GRD *2000
from surface to base of
layer
WELL_IV Well interval velocity WELL_ISOPACH / (BOT_TIME -
TOP_TIME) *2000
APP_IV Apparent interval velocity WELL_ISOPACH /

GRID_ISOCHRON *2000
RES_IV Resultant interval velocity GRID_ISOPACH/

GRID_ISOCHRON *2000
VERTICAL_IV_BOT Vertical well interval WELL_ISOPACH/

GRID_ISOCHRON *2000
velocity

VERTICAL_IV_TOP Vertical well interval WELL_ISOPACH/

GRID_ISOCHRON
velocity
( TOP_X, TOP_Y) *2000
VERTICAL_APP_IV Vertical apparent interval

velocity
VERTICAL_RES_IV Vertical resultant interval GRID_ISOPACH /
GRID_ISOCHRON *2000
velocity
AH_WELL_ISOCHRON Along hole well isochron
AH_GRID_ISOCHRON Along Hole grid isochron
AH_WELL_ISOPACH Along hole well isopach
AH_GRID_ISOPACH Along hole grid isopach
Layer number
CF_ERROR (Internal Only) Calc shifted
formula RMS error
DF_ERROR(grid tie) (Internal Only) Depth
formula(tied to grid)RMS
error
DF_ERROR(well tie) (Internal Only) Depth
formula(tied to well)RMS
error
SHIFT (Internal Only) Well shift to

the calc parameters
DEPTH_ERROR Depth error at the well
CALC_DISCREP-CALC (Internal Only)
NUM_POINTS Number of points in the

layer
BOT_TIME_MISTIE Time mistie between well BOT_TIME - BOT_TIME_GRD
and seismic
BOT_DEPTH_MISTIE Depth mistie between well BOT_DEPTH - BOT_DEPTH_GRD
and seismic.

SOLUTION_GRADIENT (Internal Only)
SOLUTION_INTEREPT (Internal Only)
SOLUTION_CORRELATION (Internal Only)
SOLUTION_POINTS (Internal Only)
GRID_ISOCHRON BOT_TIME_GRD -
TOP_TIME_GRD
WELL_ISOCHRON BOT_TIME - TOP_TIME
GRID_ISOPACH BOT_DEPTH_GRD -
TOP_DEPTH_GRID
WELL_ISOPACH BOT_DEPTH - TOP_DEPTH
WELL_LAYER_GLOBAL_FIT_0 (Internal Only)
WELL_LAYER_GLOBAL_FIT_1 (Internal Only)
WELL_LAYER_GLOBAL_RES_0 (Internal Only)
WELL_LAYER_GLOBAL_RES_1 (Internal Only)
WELL_LAYER_WELL_FIT_0 (Internal Only)
WELL_LAYER_WELL_FIT_1 (Internal Only)
WELL_LAYER_WELL_RES_0 (Internal Only)
WELL_LAYER_WELL_RES_1 (Internal Only)

Well Location
There are four different locations associated with a well: the surface location, the location of
the well bore at the top well pick, the location of the well bore at the base well pick and the
location of the well bore at the mid-point depth. The values will be identical for a vertical well,
but will be different in the case of a deviated well.
The different locations are illustrated below.
MidX,MidY TopX,TopY
BotX,BotY A - XY Top of Pick
B - XY Bottom of Pick
C - XY Mid Point
A
C
B
rid
G
p
To
id
Gr
se
Ba
B C A
Top Time or Depth Grid
Time /
Depth
Base Time or Depth Grid
Well Definitions
The following diagram of a log defines the terms Top Well Pick and Base Well Pick.

Top Well Pick TOP_TIME,TOP_DEPTH
MID_TIME, MID_DEPTH
BOT_TIME, BOT_DEPTH
Base Well Pick
Top Time - (TOP_TIME)

The time at the top well pick. This value is obtained by interpolating the time-depth curve
at Top_Depth.
Middle Time - (MID_TIME)
The time at the mid-point depth. This value is obtained by interpolating the time-depth
curve at Mid_Depth.
Bottom Time - (BOT_TIME)
The time at the base well pick. This value is obtained by interpolating the time-depth
curve at Bot_Depth.
Top Depth - (TOP_DEPTH)
The depth at the top well pick.
Middle Depth - (MID_DEPTH)
The mid-point depth between the top and base well picks.
Bottom Depth - (BOT_DEPTH)
The depth at the base well pick.
Surface X, Surface Y - (SURF_X, SURF_Y)
The surface location of the well. This is taken from the well location data, not from the
time-depth curve.
Top X, Top Y - (TOP_X, TOP_Y)
The XY surface location of the well bore at the top well pick. The value is interpolated
from the well curve data at TOP_DEPTH. ‘A’ on the diagram below.
Middle X, Middle Y - (MID_X, MID_Y)
The XY surface location of the well bore at the mid-point depth between the top and base
well picks. The value is interpolated from the well curve data at MID_DEPTH. ‘C’ on the
diagram below.
Bottom X, Bottom Y - (BOT_X, BOT_Y)
The XY surface location of the well bore at the base well pick. The value is interpolated
from the well curve data at BOT_DEPTH. ‘B’ on the diagram below.

Surf_X, Surf_Y
B C A
Top Time Grid
Time
Base Time Grid Top_X, Top_Y
Bot_X, Bot_Y
Mid_X, Mid_Y

Grid Definitions
TopX,TopY
MidX,MidY
BotX,BotY
A
C
B
id
Gr
me
Ti
p
To
rid
G
e
m
Ti
se
Ba
B C A
Top_Depth_Grd
Top_Time_Grd
Bot_Depth_Grd
Bot_Tim_Grd
Remember that you may need to consider Mistie discrepancies between Grid and Well
Pick.
Bottom Time - (Bot_Tim_Grd)
The value of the base time grid interpolated at the base well pick (i.e. at BOT_X, BOT_Y).
Top Depth - (Top_Depth_Grd)
The value of the top depth grid interpolated at the top well pick (i.e. at TOP_X, TOP_Y).
Top Time - (Top_Tim_Grd)
The value of the top time grid interpolated at the top well pick (i.e. at TOP_X, TOP_Y).
Bottom Depth - (Bot_Depth_Grd)
The value of the base depth grid interpolated at the base well pick (i.e. at BOT_X,
BOT_Y).

Vertical Apparent IV
THIS IS THE VALUE NEEDED IN A DEPTH CONVERSION TO TIE THE TIME GRID WITH
THE WELL DEPTH.
The interval velocity derived from the top time and depth grids, TOP_TIM_GRD_BOT and
TOP_DEP_GRD_BOT and the time and depth values at the well base pick BOT_TIME_GRD
and BOT_DEPTH.
Top_Tim_Grd_Bot
Top Time (BotXY)
Vertical Apparent
Interval Velocity
Bot_Depth_Grd
Bot_Tim_Grd
Misties
With deviated wells (or indeed straight wells) the values of the tops would not necessarily tie
exactly with the grid for the same surface. If this is the case you will need to be aware which
of the two values you will want.
The diagram below shows an exaggerated mistie between the well pick and grid. This
highlights the fact that if GRIDS are used then it is the X,Y position of point A (the surface XY
location of the well’s top pick) that is used as the Grid Value; not where the well track ‘enters’
the grid surface.

TopX,TopY
BotX,BotY
rid
G
e
m
Ti
p
To
A
Time Top Grid Time
Top XY Well Pick

Top Time Grid

Further Details on Inputs

Tip: Use Hypertext links over the Graphics to go to diagrams and explanations.
This information also covers the Curve inputs. Not all inputs are relevant to the Well Log Data
table.
STACK CURVE
Stack Curve - Location

X Coordinate
Y Coordinate
Stack Curve - TimeDepth

Stack Curve - Velocity

STACK LAYER
Stack Layer - Location

X Coordinate
Y Coordinate
Stack Layer - Isochron

Layer(GridTime,GridTime,BotXY)
Stack Layer - Isopach

Layer(StackDepth,StackDepth)
Stack Layer - TimeDepth

Top Time(GridTime)
Middle Time(GridTime)
Bottom Time(GridTime)
Top Depth(GridTime)
Middle Depth(GridTime)
Bottom Depth(GridTime)
Stack Layer - Velocity

Average Velocity(GridTime)
Interval Velocity(GridTim, Grid Time)
RMS Velocity(GridTime)

SURFACE XYZ
SURFACE GRID
WELL CURVE
Hold Cursor over

Entry
to go to Link
Well Curve - Location

X Coordinate
The X coordinate for each sample in the layer. Curve data can be displayed for more than
one well. All the samples within the current layer are displayed.
Y Coordinate The Y coordinate for each sample in the layer. Curve data can be
displayed for more than one well. All the samples within the current layer are displayed.
Well Curve - Residual

Calculated Well Depth Error
Well Curve - Time Depth

Calibrated Time
Values created as a result of running the calibration program or reading in calibrated data.
The time value at each depth sample. Curve data can be displayed for more than one
well. All the samples within the current layer are displayed.

Uncalibrated Time
The uncalibrated time value at each depth sample. Curve data can be displayed for more
than one well. All the samples within the current layer are displayed.
Depth
The depth value at each sample (these first 5 columns are what are loaded in to the File-
>Import ->Well Curve file). Curve data can be displayed for more than one well. All the
samples within the current layer are displayed.
Calculated Well Depth
Depth results that come from the current depth conversion set-up
Well Curve - Velocity

Average Velocity
The average velocity from the surface to this sample. Curve data can be displayed for
more than one well. All the samples within the current layer are displayed.
Instantaneous Velocity
The instantaneous velocity between adjacent samples. This is what is displayed on the
TOPS display. Curve data can be displayed for more than one well. All the samples within
the current layer are displayed. Curve data can be displayed for more than one well. All
the samples within the current layer are displayed.
WELL LAYER
Well Layer - Isochron
Hold Cursor over

Entry
to go to Link
Along Hole(GridTime) - (AH_GRID_ISOCHRON)

The isochron based on the top and base time grid values (i.e. TOP_TIME_GRD and
BOT_TIME_GRD).VALUES ARE ONLY MEANINGFUL FOR VERTICAL WELLS. They
should be treated with caution for deviated wells.

Top Time Grid

TOP_TIME_GRD
Time
Base Time Grid
Along Hole(GridTime)
BOT_TIME_GRID
Along Hole(WellTime) - AH_WELL_ISOCHRON

The isochron based on the top and base time values (i.e.TOP_TIME and BOT_TIME).
These may well be offset from the grid values for top and base of layer due to misties (as
shown in the diagram below). Values are only meaningful for vertical wells. They should
be treated with caution for deviated wells.
Top Time Grid

TOP_TIME
(top well pick)
Time
Base Time Grid
Along Hole(Well Time)
BOT_TIME
(base well pick)
Layer(GridTime,WellTime,BotXY)

Well Layer - Isopach
Hold Cursor over

Entry
to go to Link
Along Hole(Grid) - (AH_GRID_ISOPACH)

The isopach based on the top and base depth grid values (i.e. TOP_DEPTH_GRD and
BOT_DEPTH_GRD).Values are only meaningful for vertical wells. They should be treated
with caution for deviated wells.
Top Depth Grid

TOP_DEPTH_GRD
Depth
Base Depth Grid
Along Hole(Grid Depth)
BOT_DEPTH_GRID
Along Hole(Well)
The isopach based on the top and base well picks (i.e.TOP_DEPTH and
BASE_DEPTH).These may well be offset from the grid values for top and base of layer
due to misties (as shown in the diagram below). Values are only meaningful for vertical
wells. They should be treated with caution for deviated well.

Top Depth Grid TOP_DEPTH

(top well pick)
Depth
Base Depth Grid
BASE_DEPTH
(base well pick)
Layer(GridDepth,GridDepth,BotXY)
Layer(GridDepth,WellDepth,BotXY)
Well Layer - Location
Hold Cursor over

Entry
to go to Link
Locations from one of the main VelPAK curve Definitions. Go Here for details.
Well Layer - Residual
Time(WellTime,GridTime,BotXY)
Depth(TieMode,BotXY)
Depth(WellDepth,GridDepth,BotXY)

Well Layer - Optimization
Global Fit ()
Global Fit ()
Global Residual ()
Global Residual ()
Well Fit ()
Well Fit ()
WellResidual ()
WellResidual ()
Well Layer - Time Depth
Hold Cursor over

Entry
to go to Link
Pick.
Top Time
One of the main Well Definitions. Go Here for details.
Top Time(GridDepth) - (Top_Time_Dep_Grd)
The time obtained by interpolating the well time-depth curve at TOP_DEPTH_GRD. Time
values are obtained by interpolating the well time-depth curve at the grid-derived depths:

B C A
Top Depth Grid
Top Time (Grid Depth)

Time Base Depth Grid
Middle Time
Bottom Time
Bottom Time(GridDepth) - (Bot_Tim_Dep_Grd)
The time obtained by interpolating the well time-depth curve at BOT_DEPTH_GRD. Time
values are obtained by interpolating the well time-depth curve at the grid-derived depths.
B C A
Top Depth Grid

Time/
Depth
Base Depth Grid
Bottom Time (Grid Depth)
Top Depth

Top Depth(GridTime) - (Top_Dep_Tim_Grd)

The depth obtained by interpolating the well time-depth curve at TOP_TIME_GRD. Depth
values are obtained by interpolating the well time-depth curve at the grid-derived times.
These are the values displayed on the right-hand side of the WELL TOPS display in
velocity-depth mode.
B C A
Top Time Grid

Time/
Depth
Top Depth (Grid Time)

Base Time Grid
Middle Depth
Bottom Depth
Bottom Depth(GridTime) - (Bot_Dep_Tim_Grd)
The depth obtained by interpolating the well time-depth curve at BOT_TIME_GRD. Depth

B C A
Top Time Grid

Time/
Depth
Base Time Grid
Bottom Depth (Grid Time)
Well Layer - Time Depth Grid
Hold Cursor over

Entry
to go to Link
Grid values interpolated at well locations.

The grid values are interpolated from the time and depth grids at the top and base well picks.
The time grid values are illustrated below, again with a greatly exaggerated mistie between
the well and grid data.
Remember that you may need to consider Mistie discrepancies between Grid and Well Pick.
Top Time - (Top_Time_Grd)
One of the main Grid Definitions. Go Here for details.
Top Time(BotXY) - (Top_Tim_Grd_Bot)
The value of the top time grid interpolated at the base well pick (i.e. at BOT_X, BOT_Y).

B C A
Top Time Grid

Top Time (BotXY)
Top_Tim_Grd_Bot
Time
Base Time Grid

Top Depth(BotXY) - (Top_Dep_Grd_Bot)
The value of the top depth grid interpolated at the base well pick (i.e. at BOT_X, BOT_Y).
B C A
Top Depth Grid Top Depth (BotXY)

Top_Dep_Grd_Bot
Depth
Base Depth Grid


Well Layer - Velocity Average

Average velocities to top of layer.
Hold Cursor over

Entry
to go to Link
Top(GridTime,GridDepth)
The average velocity from the surface to the top of the layer, based purely on the grid
values i.e. TOP_TIME_GRD and TOP_DEPTH_GRD.
Top(GridTime,WellDepth)
The average velocity to the top of the layer, based on the grid time and well depth i.e.
TOP_TIME_GRD and TOP_DEPTH.
Top(WellTime,WellDepth)
The average velocity from the surface to the top well pick, based purely on the well values
i.e. TOP_TIME and TOP_DEPTH.
Bottom(GridTime,GridDepth)
The average velocity from the surface to the base of the layer, based purely on the grid
values i.e. BOT_TIME_GRD and BOT_DEPTH_GRD.
Bottom(GridTime,WellDepth)
The average velocity to the base of the layer, based on the grid time and well depth i.e.
BOT_TIME_GRD and BOT_DEPTH.
Bottom(WellTime,WellDepth)
The average velocity from the surface to the base well pick, based purely on the well
values i.e. BOT_TIME and BOT_DEPTH.
Well Layer - Velocity Interval

Interval velocities based on layer average velocities Interval velocities are based on the
average velocities to the top and base of the layer. They are only strictly correct for vertical
wells and should be treated with caution if the well is deviated.

Hold Cursor over

Entry
to go to Link
Along Hole(GridTime,WellDepth)
The interval velocity based on the grid times and well depths i.e. TOP_TIME_GRD,
TOP_DEPTH, BOT_TIME_GRD and BOT_DEPTH.
Along Hole(WellTime,WellDepth)
The interval velocity between the well picks, based purely on the well values i.e.
TOP_TIME, TOP_DEPTH, BOT_TIME and BOT_DEPTH.
Layer(GridTime,GridDepth,BotXY)
The interval velocity based purely on the grid times and depths i.e. TOP_TIME_GRD,
TOP_DEPTH_GRD, BOT_TIME_GRD and BOT_DEPTH_GRD.
Layer(GridTime,GridDepth,TopXY)
The interval velocity derived purely from the top time and depth grids interpolated at the
base well pick (i.e.(TOP_TIM_GRD_BOT, TOP_DEP_GRD_BOT, BOT_TIME_GRD and
BOT_DEPTH_GRD).Vertical Interval velocities.The vertical interval velocities are derived
at the location of the base well pick (i.e. at BOT_X, BOT_Y). They correspond more
closely with the interval velocities used in depth conversion.
Layer(GridTime,WellDepth,TopXY)
Layer(GridTime,WellDepth, BotXY)
Layer(GridTime,WellDepth,BotXY,Well Tie)
The interval velocity derived from the top time and depth grids (TOP_TIM_GRD_BOT and
TOP_DEP_GRD_BOT) and the time and depth values at the well base pick (
BOT_TIME_GRD and BOT_DEPTH).
THIS IS THE VALUE NEEDED IN A DEPTH CONVERSION TO TIE THE TIME GRID
WITH THE WELL DEPTH.
The vertical interval velocities are derived at the location of the base well pick (i.e. at
BOT_X, BOT_Y)). They correspond more closely with the interval velocities used in depth
conversion.
WELL TOP
Well Top - Location
X Coordinate
The X coordinate of this top; this is calculated by looking at the time-depth curve, and
interpolating the X coordinate off the deviation information there.

Y Coordinate
The Y coordinate of this top, calculated as above. In a deviated well, the X and Y
coordinates will be different at each top.
Well Top - Time Depth

Time(WellDepth)
The time to this top, calculated from the time-depth curve.
Depth
The depth to this top, as loaded in to the File->Load->Well->Tops option.

Velocity Module
Introduction
The velocity module is used for conditioning and modelling velocities within VelPAK.
From the link, RMS, Average or Interval velocities can be read in and stored within VelPAK.
Within this module these velocities can be calibrated spatially against the well data, have the
Dix routine applied to RMS velocities, have pseudo wells produced and generate velocity
volumes.
Amalg
The amalgamation process creates a combined time depth curve (pseudo-well) from
surrounding time depth curves generated via the Dix process. This works by gathering data
within a search radius.
Pseudo-wells at the same location as a true well can be generated and the results compared.
Alternatively a grid of pseudo-wells can be generated automatically or from the survey
locations.
Calibrate
The Calibrate fly out is used to calibrate the velocities within VelPAK layer by layer to the well
velocities in the model.

If the velocities are RMS processing velocities then DIX is also performed on them within this
process.
Calibration of the velocities can be done by a single percentage value, by a grid of
percentages that vary at each well over the area or by a volume slice per layer that has been
produced from the processing velocities and conditioned in the HiDef module.
Volume
Velocity Volume Generation generates 2D or 3D velocity volumes.
XYZ
The XYZ option implements a simple and fast method for getting velocity information from the
stacking velocity data.
Velocity Module - Display Types Options
The data can be plotted in the time-velocity or depth-velocity domains.

What the display shows
The different types of velocity are

color coded;
Black: RMS (original)
Red (curve) Currently selected
Well velocity.
Blue (curve): Other Well
velocities
Green: (Once performed) AVG:
after DIX transformation and
integration from surface
Layers Visible Options
Display on Display off
Individual controls on which of the various velocity data types to plot as well as the well
curves.
Note: From the Model Tree select Event 0 (no event horizon) to display all velocities for all
event horizons.
Select the specific event horizon you require from the Model Tree for detailed display
of one event horizon.

Well - Well velocity curves (selected well in Blue other wells in Purple).
RMS - RMS Debiassed velocity (Black).
Average - Velocity after DIX transformation and integration from surface (Green).
Velocity Display Icons

Apply options for the Velocity procedures:
Velocity Calibrate Amalg Volume XYZ

Display

To see which type of velocity is read in to your project.
To see which type of velocity is read in to your project.

To see which type of velocity you have read in you can see either in Velocity Module or on the
Surface Map.
In the Velocity module - hovering over the points in Point mode will bring up information for
the point. In this example, it is Dix (RMS) mode:
In the Map Module – In Edit mode make sure it is set to velocity so that you get the Velocity
points displayed on the map.
In Point Pick mode select a stacking velocity point. The dialogue of values associated with tat
point will pop up. The Mode column tells you what type of Velocity it is. Old(Dix) = 0, Average
=1, Interval = 2, RMS = 3, Unknown = 4.

Display Dialog
Display Dialog
option.
Display
Display_Type - Controls the display rather than the calculation.The data can be plotted in
the time-velocity or depth-velocity domains.
Size - Controls the size of the symbols on the plot.
Overlays
These are exactly the same options as the ‘Overlays’ options from the top of the Velocity
module tab. The overlays can be turned on here via a Yes/No toggle or by the Overlay
drop down.
Choose which Velocities to display -
Average_Overlay - Velocity after DIX transformation & integration from surface (Green).
RMS_Overlay - RMS Debiassed velocity (Black).
Well_Overlay - Well velocity curves (selected well in Blue other wells in Purple).

Dix/ Calibrate Dialog

Overview of Dix / Calibrate Option
The Dix / Calibrate Option is used to calibrate the velocities within VelPAK layer by layer to
the well velocities in the model. VelPAK supports RMS, Interval and Average velocity import.
These too can be calibrated as required.
Calibration of the velocities can be done by a single percentage value (factor), by a grid of
percentages that vary at each well over the area or by a stacking velocity volume slice per
layer that has been produced from the processing velocities and conditioned in the HiDef
module.
If RMS velocities are used then this process will perform a Dix transformation, and integrates
the interval velocities obtained from this to generate time-depth relationships for each
individual stacking velocity location.
The DIX process does not depend on the current event horizon, well or line, as the process is
performed on every stacking velocity data point.
Note: DIX only operates on the current selected GROUP of stacking velocities. Go To
Group Overview.

What processing does the DIX option perform?

Whether or not debiassing is performed, pressing Calibrate Apply (Value) will automatically
perform a Dix transformation to generate interval velocities. These are then multiplied by the
percentage calibration factor entered on this page, before being integrated from the surface
to form a time vs depth relationship. The multiplication factor is a joint correction for
heterogeneity and anisotropy effects, and needs to be chosen so that the final data provide a
reasonable tie to the wells.The average velocities generated at the end of all this are
displayed as green points. When the calibration is correct, the green points will over lie the
blue points, which correspond to the well data in the same domain (average velocity from
surface). It is possible to set up a different calibration factor for each event horizon.
Input data RMS velocities

Vrms Plotted in Black
DIX
Interval velocity is RMS over the
Vint rms interval
ANISOTROPY AND
HETEROGENEITY Calibration factor
CORRECTIONS
Interval velocity is average

Vint avg over the interval
INTEGRATE
Vavg Average velocity from

surface. Plotted in green.

Dix / Calibrate Dialog - General Tab
option.
The General tab is used to specify the path name to the stacking velocity volume segy file to
be used in the calibration routine and byte positions for the if it is going to be used for the
calibration routine.
Note: For this to be used the Type must be set for each or any of the Events on the Factor
tab to Volume.

Dix / Calibrate Dialog - Factor Tab
option.
This tab sets up the calibration and the method for each event.
Note: If all events are being calibrated they should all be done at once.
Go Here for a guide on how to create a Calibrated Velocity Grid.

Go Here for a guide on how to create a HiDef Velocity Volume for calibration purposes.
Note: Only the number of events that are in the project will be shown. Each Factor set up
01_Factor...02_Factor etc. relates to the relevant event layer in the model. For
example - if there are only 4 event layers in the model there will only be four Factors
available for input. The above example is for a seven layer model.
Note: If RMS velocities are being stored and used, this calibration will perform the DIX
equation on the values. If other calibration methods (Grid, Volume) are being used a

Dix Value Factor MUST BE PERFORMED as part of the calibration routine to start
with by running the Calibration at 100%.
01_Factor/02_Factor..Set up the type of calibration to be used:

Type - Value / Volume / Grid slot
Value - If RMS velocities are being stored this value will perform the Dix transformation to
generate interval velocities.
Enter the percent calibration factor for each event layer selected to have a constant
value.
Volume - set to Volume if you have a calibrated stacking velocity volume to use. Go Here
for a guide on how to create a HiDef Velocity Volume for calibration purposes.
Grid - select the Grid slot your calibrated grid you have produced for that layer. Go Here
for a guide on how to create a Calibrated Velocity Grid.
How to create a Calibrated Velocity Grid

1. If RMS velocities are being used they must have DIX run on them before producing the
stack well logs:
2. Use the Calibration option type as Value with the value set to 100 and press Apply.
• This will create Dix velocities with no calibration applied.
3. In the Amalg Fly Out: make pseudo wells generated at the well locations.
• Press the Create from Wells ‘+’ at the top of the Amalg Property Grid.
Create From
Grid From Survey
Wells Locations

• Press Apply on Amalg to create pseudo well logs at the well locations
• These can be reviewed in the Well display module:

Stack generated wells

at well locations will be
displayed below
the real wells
in the Model Tree
with the name of the
normal well preceded
by stack.
Set Overlay Well to be the Stack generated

overlay well of the well on display
Overlay Well Stack
‘Real’ Well Trace
4. In the Velocity XYZ property grid:

• Select Type as Percent and the Output as General01 and press Apply.

• This will produce XYZ data at the wells of the factor calculated by comparing the
pseudo-well isopach for the chosen event from stack data with the real isopach.
• These values generated can be displayed on the surface module by selecting ‘XYZ
Layer Visible’ and the correct XYZ slot - in the example above the slot General_01.
5. Grid these values up using the Surface Grid option making sure General01 (in this
example) is the XYZ slot selected for gridding and the Gridding method is Global:

6. Review the Grid in the Surface module. If the Grid of the calibration factors are not good
you can de-select one or any number of the XYZ points from being used in the grid run.
For example:
The following grid shows a bull’s eye where the XYZ values is 109.34.

To de-select the point:

• Set Edit Mode to Well

• Set Display to only show the Stack wells over the area and not the ‘real’ wells by
setting Well_type to Stack.
• Click on the well. The Edit Well dialogue will come up:
• Tick the check box next to Deselect Layer.

This will deselect this layer for this stack well.
Note: It is not easy to get this layer back once deselected so only do this if you are sure you
do not want this XYZ point for this layer used in the calibration!

• Back in the Velocity module re-generate the XYZ percent overwriting the XYZ file
stored in General01.
• In the Surface module re-generate the grid (Global gridding method):
Once you are happy with the grid of the calibration factor enter the grid as the factor type
for the calibration process:

• In the Velocity module set the Factor for the event you have been working with from
Value to the grid slot the percent Calibration grid is stored – in this example
General01 and press Apply.
How to create a HiDef Velocity Volume

1. If RMS velocities are being used they must have DIX run on them before producing the
stack well logs:
2. Use the Calibration option type as Value with the value set to 100 and press Apply.
• This will create Dix velocities with no calibration applied.
3. In the Amalg Fly Out: make pseudo wells at well locations

• Press the Create from Wells ‘+’ at the top of the Amalg Property Grid.
Create From
Grid From Survey
Wells Locations
• These can be reviewed in the Well display module:
Stack generated wells

at well locations will be
displayed below
the real wells
in the Model Tree
with the name of the
normal well preceded
by stack.
Set Overlay Well to be the Stack generated

overlay well of the well on display
Overlay Well Stack

• In the above example you can see the variation between the Real well trace and the
well trace developed from the well stack. This is what we are aiming to change in this
case by creating a HiDef velocity volume.
4. Run HiDef Tool from the Tools drop down menu.
5. You will not necessarily have a back ground model. IN this case you do not want a
background model - so say No to the alert that comes up.
6. Select the .sgc for the geometry of the volume. If no survey is selected it makes one
called None.sgc. It contains more or less all of the information in the Volume property grid
in VelPAK. It is needed to define geometry, SEGY type etc. Note that VelPAK always
makes a .sgc when it makes a velocity volume also.
7. Set geological model spread parameters for each layer from the HiDef - Set Up tab.
Within the layers you have defined are intermediate micro-layers or micro-horizons which
are modelled on the geological relationship bounding the horizons.
You will need to assign what relationship to the bounding horizons this layer has, typically
geology running proportionally to the bounding horizons or running parallel to the upper
horizon or parallel to the lower horizon.
Refer to the HiDef User Guide for full details of this process.
8. In the Project Parameters Tab, in Simple View use the Bulk Selection of Wells option to
turn off all real wells, leaving only stack wells(wells) on.
You will see that wells that have the status ‘Has Tops Has Logs’ layer definitions assigned
to them will have turned off (de-activated). The stack wells, however, that can be seen if
you scroll down to the bottom of the list of wells will remain on.

Active Off on ‘real’ wells

Stack wells are left on.
Once the wells are turned off you now want to generate the Instantaneous velocity
volume using just the pseudo wells.
9. In the 3D range of the HiDef fly out select a name for the Output SEGY. Make sure it is an
appropriate name - you will need to select it again soon.
Set Output Type to Instantaneous.

10. Go to the Run 3D tab and set how many processors you wish to have used in processing
the volume and press Apply. You will see the progress of each Task on the progress bar.
11. When this has processed, exit HiDef.

12. Run HiDef again.

13. Choose the Volume you have just created as background model and set the geological
model as you did previously.
14. In the same way you did before, in the Project Parameters tab, turn all stack wells
(wells) [meaning the stack wells generated at the wells which is what we have generated]
off and all real wells on. (Note this is the opposite to what you did before).
15. Go into the HiDef tab, 3D Range and set output type to “Percentage” and set an Output
file name (it will be called something appropriate with ‘Percentage’ at the end)
16. Set the volume generation going under the Run 3D tab in the same way you did before.
This will be the velocity volume of the percentage difference between the derived stack
wells and the actual well curve that will be used to calibrate the velocities back in the
Calibrate fly out in the Velocity module of VelPAK.
Overlay Well Stack
When it has finished generating:

17. Go back into the Velocity module. In the Calibrate General tab set the Segy_Filename to
point to the percentage volume just generated and check the byte positions are set to 17
and 25 and press Apply.

Once the process has completed you must re-generate the values of the pseudo-well
velocities via the Amalg feature:
18. Go into the Amalg fly out and press Apply again.
The velocities will be re-generated at the well-locations.
19. Check the calibrated well against the real well trace in the well module (you may need to
refresh the Well display).
Overlay Well Stack

(calibrated)

XYZ Dialog
XYZ Dialog
Overview of XYZ Option
The XYZ option implements a simple and fast - (but less predictive than Amalg) - method for
getting velocity information from the stacking velocity data.
It is necessary to process the stacking provelocities using the DIX option before using
LAYER. This generates a horizon-consistent velocity slice. The data created is in the form of
an XYZ file, which is stored in the Velocity XYZ slot under the relevant event horizon in the
Model Tree. The XYZ file created is assigned the name StackvelsXXX where XXX is the
method used.
AV - Average Velocity.
IV - Interval Velocity.
RMS - RMS (Debiassed) Velocity.
This can then be gridded up using the Grid option (under the Surface module), and an
average velocity or interval velocity depth conversion can be performed.
The horizon-consistent velocities are extracted by performing a linear interpolation on each
stacking velocity curve at the time from the time grid.
Note: Be sure to have the correct Event Horizon selected in the Model Tree or Surface&Slot
selector.
option.

XYZ Dialog
Option tab
Display
Velocity_Type - Interval/ Average/ RMS - used to select the type of velocity to be
extracted.
Interval velocity calculates the interval velocity between the current event horizon and
the next event horizon above. This is suitable for use with the Simple Interval Velocity
depth conversion method.
Average velocity type generates average velocity from surface down to the current event
horizon. This is suitable for use with the Simple Average Velocity depth conversion
method on the DEPTH Option page.
RMS velocities can also be extracted.
Verify - Yes/No
Output
Select the slot in the Model Tree where you want the output file to be stored. Typically this
will be the Velocity slot under the XYZ data for the event horizon you have selected,
although any slot can be allocated:
The XYZ file created is assigned the name StackvelsXXX where XXX is the method used.
AV - Average Velocity.
IV - Interval Velocity.
RMS - RMS (Debiassed) Velocity.

Amalg Dialog
Amalg Dialog
Overview of Amalg Option
The amalgamation process creates a combined time depth curve (pseudo-well) from
surrounding time depth curves generated via the Dix process. This works by gathering data
within a search radius. It can be particularly interesting to generate a pseudo-well at the same
location as a true well and compare results. Alternatively a coarse grid of pseudo-wells can
be generated automatically or from the survey locations. This is a powerful technique to
smooth the errors in the stacking velocity data whilst maintaining information. Once the grid
of pseudo-wells is complete the Curve module can be used to generate a set of control points
of interval velocity for gridding.
The pseudo-wells generated by this process are identical to real wells as far as the rest of the
program is concerned. So you can use these pseudo-wells in the Optimize module to fit
functions to them, as well as obtaining interval velocity maps etc. It is recommended that
function generation on pseudo-wells is performed in the velocity-depth domain.
The time-depth curve for each pseudo-well is defined for all layers defined in the current
model.
For the Amalg process to distinguish between ordinary wells and stacking velocity pseudo-
wells, the pseudo-wells will have the word “stack” in lower case as the first five characters of
the well name. If generated as a coarse grid teach well will be assigned a number following
the ‘stack’ name. If generated at an actual well the ‘stack’ will be followed by the actual well
name.
The process steps for using Amalg are as follows
1. Decide whether to run the process as a Grid of pseudo-wells, at well locations or survey
locations.
2. Create them by pressing the correct ‘+’ at the top of the Amalg Property Grid.
Create
Grid From From
Wells Survey
Locations
3. Decide on the Radius around each well the process is to gather the information from and
the spacing, if applicable.
4. Press the Apply button to generate the curves associated for your created well(s).
5. View the generated locations on the Surface module - selecting Stack as your Well_Type
in Display.
6. View the curve in the Well Module noting that for pseudo-wells at actual well locations you
can choose the Overlay_Well as either the stack well or the real well to view both curves
on the same display.

Amalg Dialog
Making additional Stack Pseudo-Wells in a data set

Making further pseudo-wells in a project will cause pseudo-wells already in the project to
behave differently, depending on whether the pseudo-wells are created from a Grid, at the
well locations or from survey locations:
• If you add a new grid of stack wells the old grid of stack wells will automatically be
deleted.
• Adding new well based stack wells will add to the existing set.
• If you add a new survey of stack wells ONLY old stack wells of the same survey
name are removed first. This means you can produce multiple surveys of pseudo-
wells.
Amalg Dialog - General Tab
When you have created your well(s). Press to apply the changes and activate the
option. Go Here for details of what happens when this is activated.
Delete - - Use to delete all the wells locations prefixed with a ‘stack’ within the model.
Create - - Used to create either a regular grid of pseudo-wells, at

survey locations or pseudo-wells at actual locations. These will all be prefixed ‘stack’.
General
Option
Radius - The radius is the UTM distance around each well that the program will search to
gather the information to produce the curve for the pseudo-well. It should be sufficient to
get in a number of stacking velocity curves. Suggested starting value is 4000.

Amalg Dialog
Spacing - The UTM spacing for the generation of your grid of pseudo-wells. The wells are
always positioned starting at the origin of your data area. They are orientated parallel to
the X-Y axis.
Verify - Yes/No - Setting this to Yes the program will expect verification via an Alert Box
as to whether to create each ‘Stack’ well. Obviously when creating a large grid over a
Model area this could slow the procedure down greatly.
Amalg Methodology
Stacking velocity analysis locations

Search radius
Pseudo-well
Time grid for
event (n-1)
Time grid for

event n
When the Amalg Apply tick is activated, VelPAK scans the list of wells in the Model Tree until
it finds one called “stackXX”. It then works out if there are any stacking velocity points it can
use to generate a pseudo-sonic. It generates a cylinder, with a radius of the search distance
based on the value of the mute distance (fixed from Dix) at the midpoint. The top and base of
the cylinder are the time grids for the top and base of the layer. Only data points from within
this cylinder are considered. If a stacking velocity analysis has only one Time-Velocity pair
inside then it is ignored.
These ‘cylinders’ are then added together to create a curve for the whole trace length. Note
that there may be overlaps due to the geology between the layers. This is compensated for
using the Two-way time at that point.
VelPAK then combines the data points within the cylinder, and rearranges them to form a
pseudo-sonic log. It does this by calculating an interval velocity between each sample down
each stacking velocity analysis curve, and a midpoint depth for each of these sample pairs. It
then sorts these midpoint depths into order, and re-integrates to get a time-depth curve. This
is then in the same form as all the other VelPAK sonic logs, which are stored as time-depth
curves.

Amalg Dialog
If Verify is set to ‘Yes’ - the program then asks for confirmation of whether you want to
create this pseudo-well. If you click on Cancel, the program deletes that particular “stack”
well, and then asks you if you want to carry on with Amalg.
If you click OK on this second dialog, VelPAK will proceed to the next “stack” well.
Note: If a “stack” well has no data points within its cylinder, VelPAK will not ask whether to
create the pseudo-well; it will just delete it.
There are two possible reasons for VelPAK deleting a “stack” well without asking you about it:
1. The “stack” well may be so far from the stacking velocity data that no analysis locations
are within the cylinder.
or
2. The “stack” well grids are indeterminate at the location. However, the process with seek
to go as far down the trace as possible so if only higher grids are present and lower grids
are absent a curve will be generated down to where the grids are absent.
What the Amalg display shows

To see what the Amalg process has done with your model you ideally need to look at the
Velocity module, the Well module and the Surface module display at once. This can be done
by dragging the respective tabs out of the main VelPAK window.
Refer to ‘Detaching a window from the main VelPAK window’ for information on how to do
this.

Amalg Dialog
Well Module display

The Well Module display shows a segment of time-depth curve data.
It is possible for the time-depth curve to extend above and below the time grid range if the
time grids have a substantial variation over the radius of the input data. It is also possible that
the generated curve data may not initially cover the entire time grid range because the
amalgamation process only works with midpoint values. However, in this case, the curve will
be extrapolated upwards or downwards, as necessary, using the first and last interval velocity
values in order to ensure that the time-depth curve is defined at both the top and base time
grids.
The top and base TOPS values for the pseudo-well are calculated by interpolating the
pseudo-well time-depth curve at the top and base grid times. This ensures that the well layer
will always tie perfectly with the time grids.
If several analyzes have similar midpoint depths but different interval velocities, this will lead
to a strange looking pseudo-sonic. However, because the intervals are very small, these
points do not have a serious effect on the time-depth curves. Before deciding that a pseudo-
sonic looks unrealistic, check the information on a time-depth display. You may find that it is
quite OK when looked at in this domain, Go Here for details of how to do this.
Surface Module Display

Turning the Wells ON from the ‘Layers Visible’ tab will show you all the Stack wells that have
been generated. These will not necessarily be distributed over the whole surface area of your
model since it will dependent on the well data available.

Amalg Dialog
Stack Wells generated but

the curves have not yet
been created (hence there
is a grid of pseudo-wells
over the entire Area of
Interest of the Model)
Curves are now

generated; Stack
Wells with no curve
data associated have
been deleted from the
Model.
Velocity Module Display

There will be a display (in purple) of all the well curves from generated pseudo-wells.

Amalg Dialog

Velocity Volume Generation

Velocity Volume Generation generates 2D or 3D velocity volumes. A 3D velocity volume is
made from a VelPAK velocity model, while the generation of 2d velocity volumes to SEGY is
done from snapped and depth converted 2d profiles.
The velocity volume can be visualized in VuPAK, displayed in vertical section in 2d3dPAK,
used for seismic trace depth conversion in TracePAK, and used for surface depth conversion
using 2d3dPAK. It may also be exported for use by other software packages.
In order to output a velocity volume, a velocity model must first be generated within VelPAK.
The module selects the velocity model for a given point within the volume based on an X, Y, Z
co-ordinate.
General 3d and 2d survey information can be automatically imported into the relevant slots in
the Velocity Volume Generation Fly Out Survey slot. These Survey slots display the 3d
survey or 2D survey exported to any VelPAK project under that author into the export
directory.
The Z Co-Ordinate is termed the first dimension and can only be time.
A depth conversion method needs to be set up for all layers in your model before producing a
Velocity Volume. Ideally this would already have been run within your model, layers depth
converted and reviewed before generating a volume so that any errors in the set-up will
already have been corrected.
Any depth conversion formulae written by you, must conform to the VelPAK convention of
referring to depth and time in the equation.
The process can be run in BATCH mode allowing any number of CPUs on the PC (or indeed
on the network) to be utilized.
Since the volume generated in small increments - (typically 4ms to conform with other
packages) this depth conversion method must be appropriate for such a small increment; for
example in the diagram below of an Interval Velocity vs Isochron layer fit, the fit is good for an
Isochron reading of 80 to 340ms, but if this was extrapolated to an isochron value of 4ms the
velocity would be more like 6000m/s which would produce a very inaccurate result.

6000
4ms
Isochron
For the second layer onwards, the last_time and last_depth must also be specified in the
equation.
Note: In order to generate a velocity volume which is referenced to the sea surface, (zero
time, zero depth), a velocity model must be defined for all intervals. In some cases the
velocity model may start at the seafloor, for which a depth grid has been imported into
VelPAK from another source. If this is the case then a depth conversion must be
entered for Event 1, as a velocity model must be defined for this interval.
A Step-by-step Guide of how to Generate a volume from this tool is here.
Generating a dummy 3D volume for 2D data

When working with 2D data, it is necessary to create s ‘dummy’ 3D volume to slot the 2D into.
The workflow for this is as follows:
1. In Kingdom, create grids from horizons that cover the extents of all the 2d surveys (and
any 3d surveys) in project
2. Build the velocity model in VelPAK in the usual way.
3. Before generating the velocity volume, use the Volume fly-out to define a new 3d survey.
The survey corner points should coincide with the corner points of the grids (click on a
grid in the Model Tree to see the extents in the Properties tab).
4. Set the trace spacing in the inline and crossline directions to approximately match the
spacing of the traces in the 2d lines (or a multiple of that to ensure the generated 3d
volume doesn't become too large and too slow to generate) .
5. Generate the instantaneous velocity volume for this survey in the usual way.

Velocity Dialog - General 3D Tab
option.
Parameter Increment Tool

Parameter
Increment
Update
Parameter - - Calculates the correct volume starts and stops taking in to account the
selected increment to conform with the SEGY selection.
Options
File - Output file name. Use the File Selector to select a location and filename or accept
the default “volume.out”. It may help to suffix SEG-Y filenames with sgy and TDQ format
file with avf (the standard Landmark naming convention).
Survey - Load Survey Information - this accesses a list in the author directory created
during the Link procedure of every 3d survey loaded to any VelPAK project under that
author. An alert message will pop up. Select the survey you wish the 3d information to be
loaded from and press OK.
Type - The output maybe a diagnostic, a SEG-Y file or an ASCII file in Landmark’s TDQ
format.
Diagnostics - Produces a text file containing diagnostic information about the model,
methods and values for each layer written to it as text values.
TDQ from Grid - A TDQ volume made using the grids in the model will be generated
The Volume ASCII output follows Landmark’s TDQ format. AWK filters can be used to
reformat the output file into another format, such as ESSO V2, if required. Contact
software support for advise on this.
Segy from Model or Segy from Profile - This output is required so that the velocity
volume can be loaded into interpretation software such as the Kingdom Suite, Petrel,
OpenWorks or GeoFrame.
The commonest form is a SEGY from Model velocity volume (of type Dimension) from
the model and defined surveys extents will be generated

A SEGY from Profile velocity volume (of type Dimension) from the snapped, depth
converted profiles for this survey will be generated.
The format is a 3D regular orthogonal mesh with a velocity at each node. (The
velocity may be interval, RMS or average velocity.)
The mesh co-ordinate dimensions are:
• X location (UTM co-ordinate).
• Y location (UTM co-ordinate).
• Time or Depth.
• The output is an IEEE format SEG-Y. The trace header locations are as follows;
• in-line is byte position 189, integer format.
• crossline is byte position 193, integer format.
• X co-ordinate is byte 73, floating point format.
• Y co-ordinate is byte 77, floating point format.
• no. of samples per trace is byte 115, integer format.
• sampling interval is byte 117, floating point format.
- The SEG-Y output only allows constant sampling.
Note: Remember, the data and trace header formats are IEEE not IBM.
Verify - Yes / No.

Profile
Profile Order - Profile processing order for segy creation.
Parameters
Volume Modelling requires the X and Y co-ordinates for two points on one line and one
point from another line. These points may define the entire survey or just a small part.
These values can be set up automatically on loading the Survey but can be amended
manually.
Dimension
Depth / Instantaneous / Average - A SEGY volume with depth/ instantaneous velocity/
average velocity values at each time sample will be generated. (Note: Interval velocity
volumes are no longer supported as they are largely useless.)
Inline / Xline
The increments here specified will affect the resolution of the output file and the size of
the file. This option allows you to use the corner points of your 3D survey to define the
geometry, but output the velocity cube over a smaller area.
Survey
First_Inline - 1st Inline point value.
First_XLine - 1st Crossline point value.
First_XLocation - X Location of first point.

First_YLocation - Y Location of first point.

Second_XLine - 2nd Crossline point along the same line as the 1st point.
Second_XLocation - X Location of second point.
Second_YLocation - Y Location of second point.
Third_Inline - 3rd inline point value.
Third_XLine - 3rd Crossline point value.
Third_XLocation - X Location of third point.
Third_YLocation - Y Location of third point.
Diags
Constant - Yes/No - (used with Interface option) - Usually set to ‘Yes’ to generate
samples at regular intervals within a fixed range this can be switched off if Interface is set
to ‘Y’es to generate samples only at the Interface between layers as a crude sampling
technique in a large volume.
Depth_Diags - Event_Diags - Time_Diags - Type_Diags -Vave_Diags - Vinst_Diags -
Vint_Diags - Vrms_Diags
The output reflects the chosen Volume parameters, so values will be given for the area of
interest at the sample rate specified. Each file is made up of a header containing the
Volume parameters followed by the diagnostics requested.
Interface - (used with Constant option) - Set to ‘Yes’ will calculate two values per VelPAK
event horizon, at a value above and below the event horizon as specified in the VUP/
VDOWN parameter. Choose this option if you wish to check the velocity model to ensure
that the estimated instantaneous velocities above and below the event horizon are
geophysically plausible.
Both Constant and Interface methods can be switched to ‘Yes’, enabling the interface
samples to be generated at the same time as the constant samples. Packages such as
TDQ perform linear interpolation on their input files. In order to minimize the size of the
output file while retaining accuracy, a large sample rate can be used together with the
interface samples. This gives the detail in the output file only when necessary. See the
diagrams below for more information.


Velocity Dialog - General 2D Tab
Option
File - output volume file name. This will be stored in the <model name>/volume directory.
Survey - Select the 2d survey loaded from the Kingdom project you wish to use for
volume generation (or Profile volume or seismic display) by clicking here and then on the
Select icon.
The Survey SP/Trace table is displayed below for the selected survey.
Parameters
Dimension - Instantaneous, Average Velocity or Depth (less common). A SEGY
volume with depth/ instantaneous velocity/ average velocity values at each time sample
will be generated. (Exactly as 3D).
Time_Increment - Output time increment of the time volume - typically 4ms
Time_Min - Minimum time, for example 0ms.
Time_Max - Maximum time of the time volume.
Survey
Trace, Shot, Ratio - for information.

Velocity Dialog - Location Tab
Apply - Pressing Apply on this tab with generate the Geometry. **Proceed with
caution** this option does not generate your Volume!! (Use the Apply tick on the
General 3D/2D ) ** this option will replace all the 3D or 2D seismic map location data
in your project. This can be thought of as a separate facility to the rest of the Volume
Generator in that given the 1st, 2nd and 3rd point inputs it will generate real seismic
line data within your project. An alert will come up to warn you of this before
proceeding.
Geometry Test - - Once you have set up the X Y limits of the area you are going to
generate the volume of, pressing this option will give you a (2d) visualization of that area.
The red that you see is not a real item on the display; zooming in will cause it to
disappear. It is there purely to test that your 3 point XY parameters are sensible.
Note: You must have the Surface Module open to visualize this (although not necessarily
displayed as the top tab).

Inline / Xline
The increments here specified will affect the resolution of the output file and the size of
the file. This option allows you to use the corner points of your 3D survey to define the
geometry, but output the velocity cube over a smaller area.
Inline/Xline_Clipping - Inline/Xline_Rounding - The rounding and clipping parameters
help define the points for which values are output. For example a crossline range of 1004
to 1037 with an increment of 5; if rounding only is toggled on, then for inline 1200 values
will be output at crosslines, 1004, 1005, 1010..1035,1037. If both rounding and clipping
are switched on then values will be output for crosslines, 1005, 1010,......1035. If neither
are switched on then values will be output for, 1004, 1009, 1014 etc.
Line Type - Inline/Xline or both.
Values - Yes/No. To generate values or not.
Batch Execution
When running a velocity volume it is possible to generate the volume in batch mode
accessing as many processors on the PC as you want and are available.

Select the Batch Execution using Multi Processors seen on the of bank of icons for the
module.
Inline Start / Inline Stop - Setting the Inline Start and Stop here here will override
whatever value is set in the Property Grid.
Number of Tasks - Taken from the number of processors the PC has this would usually
be left as the default allowing all CPUs to be used during the batch execution.
Abort - Allows you to Abort the process at any time.
This can be used as an Advanced use for batch on a number of different computers:
• Set up the Number of Tasks - CPUs to be used
• Press the Abort button once the 12 Tasks have started
• Pass the batch files to the other computers (since they are ‘simple’ batch files)
• When they have finished using the Collate button will collate these task batches
Collate - this is an advanced user option as mentioned above. The process will take a
while and the progress of it will be shown in the console window.
Note that running the batch process on one computer (over a number of CPUs) will
automatically collate the runs on finishing.

When ready, press Execute to start the batch process.
What happens during the Batch Execution

The process will begin by allocating however many loops to each task.
Progress will be seen in the main box of the Batch window.
The Tasks will start and progress will be seen as a blue bar moving across each Task bar.
The task manager Performance tab will show all CPUs in use.
Eventually all processors will be running their allocated loops.

As the processors finish their allocated loops the bar will turn green.
Finally all the processors will finish.
In the directory of the VelPAK project there will now be a new sub-directory called ‘batch’.
Within this sub-directory will be further sub-directories containing all the information that is
generated during a workflow looping run for each of the tasks run.

There are also batch files (*.bat) stored in the batch directory which have been used to run
the processes. For advanced users, these would allow you re-run each task individually if
required. They can also put onto another PC entirely and re-run - providing VelPAK is
installed on that PC too. (Advanced use only!)
When the process is finished all the information stored in the ‘batch’ directory sub-directories
will be collated pied across to the relevant directories of the project.
Stepped Guide - How to generate a volume in VelPAK using the

Velocity Volume Generator
• A depth conversion method needs to be set up for all layers in your model before
producing a Velocity Volume. Ideally this would already have been run within your model,
layers depth converted and reviewed before generating a volume so that any errors in the
set-up will already have been corrected.
• Since the volume generated in small increments - (typically 4ms to conform with other
packages) this depth conversion method must be appropriate for such a small increment;
for example in the diagram below of an Interval Velocity vs Isochron layer fit, the fit is
good for an Isochron reading of 80 to 340ms, but if this was extrapolated to an isochron
value of 4ms the velocity would be more like 6000m/s which would produce a very
inaccurate result.

6000
4ms
Isochron
• A Volume Generation can take a long time to generate on a large Survey. You may like to
select a portion of ten or so Inlines (possibly over an area where there is some good well
information available) to begin with to check that what you are setting up to generate is
what you want.
• Once the depth conversion is set, go to the Velocity Volume General Tab.

• Dimension 1 is already set to time (This is the Z value).

• Set Dimension2 to the type of volume you want, for example Interval Velocity.
• Set file name to something suitable with the extension usually corresponding to the type
of file it will be (e.g. “.sgy”). The file will be generated in your author directory.

• Set Type to Segy for reading into your seismic package. You may want to run ‘Diagnostic’
as the type before you run the actual Segy. This will produce a file containing values for
the parameters set up. Selection of which diagnostics to output happens at the bottom of
the Property Grid. But NOTE that this will be a very large file even if you just select one
line from a survey to output; it is recommended you use the Inline and Xline specifiers
below to output a small portion of one line.
• Select Survey button to get survey - an alert box will pop up allowing you to select from
the number of Surveys stored within your VelPAK project and press the P button at the
top to get the correct volume start stop extremes limit.
Galleon_3D
Southern North Sea
Teasmade Dome
Correct Volume Start Stop
• If you want to set up just a portion of the survey to output as a volume to test it, set the
Inline Min/Max values to reflect this. Note that Max input comes before Min in the inputs.
• Set Z Range Z_increment to be 4ms.
• Set Z_Max to the limit of your data which you can read off a Profile if one is available.
Press the Activate button.

3d Visualization Module
Introduction to 3d Visualization Module
The 3d surface viewer allows the display of multiple surfaces, wells and profiles in an
interactive environment. It becomes much easier to validate the depth conversion against
wells and other surfaces, and to visualise how velocity fields vary prior to generating volumes
to give a more efficient, quality controlled workflow.
Changing the Perspective of your 3d display

The perspective of the 3d display can be changed by holding the mouse arrow over the
picture and dragging with the left mouse button pressed.

Display Options
Display Options
Event Well Line

Event or Well or Line (Profile) within the VelPAK model.
Display Types
The method of selecting what type of display you wish to see.
The only display type available is 3.
Overlay Options
All the overlay options are basic on/off selections. Selecting the item once will turn on the
relevant display, selecting it again will turn the display off. You can build up as many of the
overlay option selections as you wish.
Well - Selecting this will display the well curve tracks stored in your model. The display of
the well track can be edited in the Display -> General fly-out.

Display Options
Surface - displays the selected surfaces on the 3d display.

Selection of which surfaces to display can be made via the Display -> Surface fly-out.
Profile - displays profiles with surfaces on the 3d display.

Selection of the profiles for display on the 3d takes place on the Surface module display.
Go Here for details. Various aspects of display for the profiles on the 3d display can be
changed through the Display -> Profile fly-out.

Display Options
Contour - Adds contours to the surfaces selected. For this reason contour overlay always
must have surface overlay on also. Contour increment can be edited in the Display ->
General fly-out

3d Display fly-out
3d Display fly-out
3d Display - General Tab
Use the down arrow () or double click on input name to select from available input.
option.
Cache All Lines - Allows the display of profile lines if the Segy is set up in the Profile
module (Display General Fly-Out).
Option
Background_Colour - choose the background colour of the 3d display.
Grid_Colour - Choose the colour of the grid and axes within which the 3d display is
presented.
Legend_Type - choose between seeing a Legend of the values of the surface, velocity or
seismic or no legend
Surface
Surface_Colour - select color tables for the surfaces. Go here for details of the color
tables in VelPAK.
Surface_Contour - Choose the increment that best suits the contouring of your data.
Surface_Slot - select the type of grid for display in the 3d display.

3d Display fly-out
Profile
Profile_Mipmap - Yes/No - Yes can reduce memory usage and speed up graphics on a
low-end graphics card.
Profile_Trim - Yes/No - trims the interpretation of the profiles back to the interpretation
min/max.
Profile_Type - Selected/Current - choose between a number of selected profiles to be
displayed (selected via the selection procedure outlined here) or the current profile
selected on the profile module display.
Note: If current is selected, detaching one of either the Profile or 3d modules from the main
VelPAK window will allow you to move through the profiles in the profile module (using
the blue Line arrows at the top of the display) and view the profile on the 3d display.
Well
Top_Colour - the colour of the tops displayed on the wells will either be colored by layer
or by well.
Top Colored by Layer Top Colored by Well
Top_Disc - A disk can be drawn to highlight where the tops are on the wells. Color of the
disk relates to whether Top_Colour is set to Layer or Well (above).

3d Display fly-out
Top Disc Size = 0 Top Disc Size = 500 Top Disc Size = 2000
Top Colored by Layer Top Colored by Layer Top Colored by Layer
Top_Size - Size of font for tops displayed on the wells.
Top_Type - choose to display which tops are to be displayed on the well curve of the 3d
display:
All - displays all formation tops in the model for the current well
Layer - displays only tops used in the layer definition
Used - displays all tops flagged as “Used” in the Layer definition table
UsedAndExtra - displays all tops flagged as “Used” and “Extra” in the Layer definition
table
Velocity_Colour - select color tables for the velocity displayed within the well trace
column. Go here for details of the color tables in VelPAK.
Well_Colour - color of well label.
Well_Text - size of font of the well label.
Well_Thick - based on pixels a value between 1 - 10
Well Thick = 1 Well Thick = 10
Well_Type - Selected/Current/ Normal / Stack - Type of well to be displayed. Selecting

‘Current’ will show just the one well currently viewed in the Well module. Normal or stack
wells produced from the pseudo-well generation VelPAK routines. Selected wells are
chosen via the selection procedure outlined here from the Surface display.
Overlays
This option can also be accessed from the Overlay drop-down at the top of the 3d
window. Go Here for details.

3d Display fly-out
3d Dialog - Range Tab

option.
Axis
XY_Type - Auto, Grid, User - select the XY range either from the entire range as defined
for the whole model, or for just the selected grid or define your own XY range.
Z_Type - Auto, Grid, User - select the Z axis value to be derived from either the range of
the entire model for all event horizons, or for just the event horizon you are displaying or
use User Define to enter your own range. This value can be taken from the Event Time/
Depth/Velocity for you selected event horizon or from a XYZ slot from the Model page.
Range
X_Min, X_Max, Y_Min, Y_Max, Z_Min, Z_Max - User defined entries when Axis (above)
has User selected.

3d Display fly-out
Velocity
Velocity_Max, Velocity_Min - Velocity unit range for display.
Seismic
Seismic_Max, Seismic_Min - Seismic unit range down the Y axis for display.
Light
X_Light, Y_Light, Z_Light - Allows the light shading of the display to be adjusted
according to the surfaces and profiles on display
Rotation
XY_Rotate, Z_Rotate - interactively changed when dragging the left mouse button over
the display, this input allows you to set an exact numerical rotation for XY and Z rotations.
XY - An angle from 0 to 360 (where 0 and 360 are True North) from which to view the
model.
Z - The angle of elevation between 0 to 90 from which to view the model.
Scale
X_Scale, Y_Scale, Z_Scale - change the perspective of the X,Y, Z axes relartive to each
other.
Translate
X_Translate, Y_Translate, Z_Translate - Translation of cube values to real world
coordinates. (Not generally used).
3d Display - Surface Tab
Select the surface grids layers to be displayed. The type of grid i.e. Time/Depth etc. from
slots in the Model Tree - is selected on the General tab.
As well as the option Yes/No the amount of opacity can also be selected - allowing individual
surface more or less see-through. The options are 25/50/75 which relate to being 25%, 50%
or 75% see-through.

3d Display fly-out
3d Display - Profile Tab
Use this tab to edit the display for the Profile on the 3d display. Go Here for details of the
Profile tab.

Curve Module
Introduction
The Curve module enables you to cross plot various data items from VelPAK and visually
inspect the relationship between those items. A line of best fit can be generated and
displayed. You can then interactively edit which items contribute to the fit.
Selection and activation of the curve data occurs from the Property Grid to the right of the
window. A comprehensive list of items are given in the Advanced Tab selection; whilst in the
Standard Tab option there are a selection of well used Graphs, Cross Plots and Relationships
that can be selected. Values derived from graphing can be used in the VelPAK Depth
Conversion.
Once your display data are on view, you can interactively edit the points and the view using
the ‘Style’ option and direct mouse actions on the graph display.
Data that can be selected comes from Curve, Layers, Stack, Surface, Tops and XYZ data.
All data plotted on the Graph display are also displayed numerically on the Data tab. The
Data tab allows you to manipulate or filter the data displayed and add and delete sets of data.
Data continues to be added cumulatively to this displayed data file until cleared by you or
exiting the module.
Clicking on a Well Location on the Curve will automatically bring up that well within the Well
Module.
The XYZ tab dialog allows you to export the data from the curve into XYZ slots within VelPAK
for use within Gridding.
The data can be exported in Microsoft Excel format or an specialist curve “.cft” file which
would allow the same graph with the same set up parameters to be brought in and displayed
at a later date.

Note: The current event defines the base of the layer, while the top of the layer comes from
the previous event horizon. For the first event horizon, the top of the layer is assumed
to be the surface (i.e. zero depth and zero time)..
Using the Stack Curve Show option under the Display Property Grid you can select or
deselect whole groups of data points rather than individually. This curve will then become
deselected permanently; including within the Optimize module.
Quick Guide to the Curve Module

1. The Graph is displayed in the Graph tab.
2. The plotted data are displayed numerically in the Data tab. This can be filtered and re-
displayed in the graph.
3. The visual look of the Graph is managed by inputs from the Display Property Grid.
4. The data for plotting is selected either from the Generate Standard Property Grid or the
Advanced Property Grid.
5. Once you have selected the data for plotting, activate the procedure by pressing the
Activate ‘tick’ on the Generate or the Display Property Grid.
Activate Clear
6. Selected data can and will be added to the existing graph and data tab unless you clear
the graph using the clear icon.
Curves can be saved using the special feature icons available only in this module.
Graphs can be saved/read in as a curve-fit “.cft” files and data can be saved in ‘.xls’
format.
Note: Curves are NOT saved in the VelPAK model.
7. Export the XYZ data produced from the curve using the XYZ data tab.

Curve Module Option Icons
Curve Module Option Icons
New Open Save Save Various General Options Curve

as Excel De-select/Select
New - clears data from Graph and Data tab. Your data will be lost if it has not been saved
previously.
Open - opens a previously stored curve file in the ‘.cft’ format.
Save - saves the curve information as a ‘.cft’ format file. This will bring in numerical data
in the Data tab and display the Graph including any styles you have selected to display
your curve and any filtering that you have done to the numerical data.
Note: The name of the default ‘.cft’ curve file is stored within the Properties of the model for
reference.
Save as Excel - will save the numeric data as an Excel file (.xlsx) . Filtered data will be
displayed within the Excel file but will be in ‘gray’ rather than default black to distinguish it.
Point Edit- Use to de-select and select wells to make them inactive for graphing
purposes.
Point Pick - used to select wells on the curve to display in the well module.
Note: The other options on the icon bar for the curve module are either currently inactive or
are documented elsewhere - in the case of the Printing options.
Zoom and Pan controls

Zoom features are available on Curve via either a pop-up menu using the right-hand mouse
button within the VelPAK curve window or activated as a toolbar within the top set of options.
Moving the middle mouse button as a wheel while holding the button down will zoom the
display in or out.
Go Here for more details of zoom and pan features in general.

Graph Tab
Graph Tab
Displays the selected graph, values and fit.

Use the Curve Fit Display Property Grid to change any display parameters.
Clicking on a Well Location on the Curve will automatically bring up that well within the Well
Module.
You can toggle wells active or inactive by clicking on them on this display using Point Edit.
Legend
This can be toggled on or off and set in whichever corner is most convenient by using the
Legend Option in the Display Property Grid. On display in the legend are the results of the
curve fit generated and plotted on the graph:

Graph Tab
A0, A1, A2 - The values derived from the fit; just A0 is constant with A1 the gradient for a
linear fit with A2 for a second order fit and so on.
Standard Error - the estimated standard deviation of the error in that method
R2 - R2 is a statistic that will give some information about the goodness of fit of a model.
In regression, the R2 coefficient of determination is a statistical measure of how well the
regression line approximates the real data points. An R2 of 1.0 indicates that the
regression line perfectly fits the data.
Adjusted R2 - Adjusted R2 is a modification of R2 that adjusts for the number of
explanatory terms in a model. Unlike R2, the adjusted R2 increases only if the new term
improves the model more than would be expected by chance. The adjusted R2 can be
negative, and will always be less than or equal to R2.
F-stat - Tests the null hypothesis that the straight-line model is right. Since the non-
central F-distribution is stochastically larger than the (central) F-distribution, one rejects
the null hypothesis if the F-statistic is too big. How big is too big—the critical value—
depends on the level of the test and is a percentage point of the F-distribution.
User P0/ User P1 (only if Show_User is set to Yes) - the A0 and A1 values derived from
the gradient for a linear fit selected in User option

Data Tab
Data Tab
Data that is selected to be displayed on the Graph is displayed numerically in this Tab. Each
selection of data are added to the end of the data already on display. The ‘Clear Graph’
option that clears the graph of all its display would also clear this tab window. Data can be
filtered to your specifications here to be displayed on the graph. Data that has been filtered
out are displayed in gray. Data that are still active are shown in black.
Clicking on the top of each column will sort the data alphanumerically in standard fashion.
Data can be sorted using more than one column using a ‘nested’ sort by holding the ‘shift’
button down while sorting.
For more control over which well data is utilised in the model, particularly with projects with
many wells, the Data table filters are cumulative. The right-mouse button context menu to
allow fast resetting of all the filters applied, and to force the data table to be rebuilt from the
model.
Data seen in the tab can be output as an Excel ‘.xlsx’ file to read into a spreadsheet. These
data and any filtering that has been done to it can also be saved as a ‘.cft’ file.

Data Tab
Label - the well label

Fit / Residual - Yes / No to select to use both values for the well or one or other.
Z1 Z2 - the actual values of the X and Y axes data
Group/Mode/Inactive - Internally derived values for plotting the curve; not used by the
user
Moving the Columns

The columns can be moved to wherever you wish by clicking on the gray title box and
dragging it to where you require. When you have the title box in a suitable position to drop it,
big red arrows will pop up allowing you drop the column in place.

Data Tab
Filtering the Data
Data can be filtered on any number of columns within the file. Filter criteria are brought up for
the individual columns by clicking on the ‘funnel’ icon at the top of each column. This funnel
icon will change from gray to blue if a filter has been applied on that column:
Filter Applied Filter Not Applied
You can select a number of methods as the filter for individual columns:
All - All elements will be displayed (default).
Custom - User defined selection of Operator and Operand to filter data. See below for
details.

Data Tab
Blanks - Will filter out blank values in the field.

NonBlanks - Will filter out non-blank values in the field.
Column Values - Lists all data in the field to select.
Custom Filter
Gives you the ability to build up a list of conditions with which to filter the data.
You can use ‘And’ or ‘Or’ to select the operators used.
Operand - The objects that are manipulated.
Operator - The symbol that represent specific actions.
As the operand you can select another column label from the data file being used as the
qualifier for this filter, or a value from within the column currently being filtered.
For example, to select data only within a certain Block you could set up the filter for the X
Location column to be X values within the block limits (shown below), and similarly for the Y
Location.

Data Tab
Custom Display of Columns
The layout of the columns can be changed to suit your requirements by accessing the arrow
to the right of the filter motif. Clicking on it will bring up a list of the columns within the Data
tab. You can then select which column you wish to be placed in this position.

Curve Fit Display Dialog
On this Dialog you will select which data are to be plotted on which axis, and from what
source your data are to come from (i.e. Well Values or XYZs), how the fit is to be applied and
how the graph will look.
Tabs include only:
General tab
Listing the display variables for the points and fitted curve. Selection of the type of Graph
Fit to take place.
Curve Fit Display Dialog - General Tab


option.
For any changes to these inputs to take effect, press the Apply tick.
The Apply Robust button. turns off the outliers in the model.
Option
Flip_X - Yes/No - selecting Yes the X axis will be flipped.
Flip_Y - Yes/No - selecting Yes the Y axis will be flipped.
Inactive - Choose to show or not show inactive points selected. Will be shown as grey if
selected to show.
Label - Labelling of points on the Graph.
Label_Color - Color of label for point. See Color Below.
Lable_Font - Font used for the label of points on the graph. See Fonts Below.
Title
Title, X_Title, Y_Title - These are automatically filled according to what has been
selected as the graph to be displayed. They can also be edited here if required. A list of
the automatically generated titles are the same as the definitions for the Advanced Curve
Definitions.
Confidence
The confidence region is calculated in such a way that if a set of measurements were
repeated many times and a confidence region calculated in the same way on each set of
measurements, then a certain percentage of the time, on average, (e.g. 95%) the
confidence region would include the point representing the "true" values of the set of
variables being estimated. However, it does not mean, when one confidence region has
been calculated, that there is a 95% probability that the "true" values lie inside the region,
since we do not assume any particular probability distribution of the "true" values and we
may or may not have other information about where they are likely to lie.
Constant_Factor - only used when generating a constant; it is the factor of the standard
deviation used to generate the constant.
Linear_Percent - the percent confidence region to be displayed.
Show_Bands - green and blue bands displayed on the graph showing the upper and
lower confidence limit.
Show_User - a red line showing the randomise fit.
Fit
Fit - Type of Fit to select:
None - No fit will be drawn on the Graph.
Constant - A horizontal, flat line will be drawn giving a constant value.
Linear - Fits the data to a straight line:
y = mx + c
and will produce two out put values, constant ‘c’ and coefficient ‘M.’.

Polynomial_2 thru Polynomial_5 -

Applies a fit method to a quadratic form;
Polynomial_2 is the form:
y = ax2 + mx + c
and will produce three output values, constant ‘c’ and coefficients ‘m’ and ‘a’.
Polynomial_3 is the form:
y = ax3 + bx2 + mx + c
and will produce four output values, constant ‘c’ and coefficients ‘m’, ‘a’ and ‘b’.
Note: These derived values, ‘c’,’m’,’a’ and ‘b’ are displayed in the Results section below.
The ‘c’ value (constant) is always A0, the ‘m’ is always A1, and in the examples above
the ‘a’ value would be A2 and ‘b’ would be A3.
Fit_Color - The color of the fitted line on the graph. See Color Below.
Fit_Font - See Fonts Below.
Fit_Symbol - Pick a keyboard symbol to use. Default is no symbol.
Legend - The results of the curve fit can be plotted on the graph.
Choose from None / BottomLeft / BottomRight/ TopLeft / TopRight.
Go Here for a discussion on what the results being displayed are.
The example below shows BottomRight selection, with adjusted Font size and Font Color.
Legend_Color - Color of text displayed as the Legend. See Color Below.

Legend_Font - The size and style of the Font on the Legend. See Fonts Below.
Robust
Robustness (Robust NonLinear Regression) is a mathematical algorithm which is
designed to reduce the influence of outliers in the Fit.
Note: Full and mathematical details of the Robust Algorithms are from the book ‘Robust
Regression and Outlier Detection’ by Peter J. Rousseeuw and Annick M. Leroy.
1987.Wiley Series in Probability and Mathematical Statistics.
Robust - Yes/No. Yes will reduce the influence of outliers. The following options will
change the look of any outlying points excluded due to setting Robust to ‘Yes’.

Robust_Color - See Color Below.

Robust_Font - See Fonts Below.
Robust_Symbol - Pick a keyboard symbol to use. Default is ‘X’.
Robust_V0 - The default value of 2.5 is a standard value entered in the first iteration of
the robust algorithm.
Robust_V1 - The default value of 1.5 is a standard value entered in the second iteration
of the robust algorithm.
Results
Result_A0 - Always the constant value from the derived equation.
For a Fit Method set to Constant this would be the only value displayed in the results
area.
For a Fit Method set to Linear this is the constant ‘c’ from the equation
y = mx + c
For a Fit Method set to Polynomial this is the constant ‘c’ from the equation like
y = ax2 + mx + c
Result_A1 - Result appears when a straight line fit is chosen.
For a straight line this the coefficient ‘m’ from the equation
y = mx + c
Result_A2 - Appears from Polynomial 2nd order fit and beyond.
For a quadratic equation curve fit this is the coefficient ‘a’ from the equation
y = ax2 + mx + c
Result_A3 - Appears from Polynomial 3rd order fit and beyond.
For a Polynomial 3rd order fit this is the coefficient ‘b’ from the equation
y = bx3 + ax2 + mx + c
Result_A4 - Appears from Polynomial 4th order fit and beyond.
For a Polynomial 4th order fit this is the coefficient ‘d’ from the equation
y = dx4+ bx3 + ax2 + mx + c
Stack Curve
Stack_Curve_Color - See Color Below.
Stack_Curve_Font - See Fonts Below.
Stack_Curve_Show - Yes/No. Default is No. - Important option. If
Stack_Curve_Show curve is set to No then data points on the display will not be
joined together and a Scatter display would be shown. Setting this as Yes then all
scatter points will be joined and it could take a considerable time to display. However
in order for you to have the ability to turn off a whole Stack Curve while in this mode
you need to first set this value to Yes, have all the points displayed and then use the
left-hand mouse button to de-select the whole curve. This curve will then become
deselected permanently; including within the Optimize module.

Stack_Curve_Symbol - Pick a keyboard symbol to use. Default is ‘X’.

Stack Layer
Stack Layer_Color - See Color Below.
Stack Layer_Font - See Fonts Below.
Stack Layer_Symbol - Pick a keyboard symbol to use. Default is ‘X’.
Surface Grid
Surface_Grid_Color - See Color Below.
Surface_Grid_Font - See Fonts Below.
Surface_Grid_Symbol - Pick a keyboard symbol to use. Default is ‘X’.
Surface Xyz
Surface_Xyz_Color - See Color Below.
Surface_Xyz_Font - See Fonts Below.
Surface_Xyz_Symbol - Pick a keyboard symbol to use. Default is ‘X’.
Well Curve
Well_Curve_Color - See Color Below.
Well_Curve_Font - See Fonts Below.
Well_Curve_Show - Yes/No. Default is No. If Well_Curve_Show curve is set to No then
well curve data points on the display will not be joined together and a Scatter display
would be shown. Setting this as Yes then all scatter points will be joined and it could take
a considerable time to display. However in order for you to have the ability to turn off a
whole Well Curve while in this mode you need to first set this value to Yes, have all the
points displayed and then use the left-hand mouse button to de-select the whole curve.
This curve will then become deselected permanently; including within the Optimize
module.
Well_Curve_Symbol - Pick a keyboard symbol to use. Default is no symbol.
Well Layer
Well_Layer_Color - See Color Below.
Well_Layer_Font - See Fonts Below.
Well_Layer_Symbol - Pick a keyboard symbol to use. Default is ‘X’.
Well Top
Well_Top_Color - See Color Below.
Well_Top_Font - See Fonts Below.
Well_Top_Symbol - Pick a keyboard symbol to use. Default is ‘X’.
Color - All of the above Color inputs have the same color options. Select the color for the
input from either two sets of pre-defined color tables Tabs; Web and System, or from the
customized Tab.

Fonts - All the above Font inputs have the same set up options. On selecting the Font
option, the following standard font box appears to allow you to set up the font as you wish.
These changes and more can also be made by expanding the ‘Fonts’ input line using the
‘+’ symbol to the left of the input.
Name - Name of the Font, selected from drop down list.

Size - Size of Font (in Units - set up in next option).
Unit - Of size of font:
World
Pixel
Point
Inch

Document
Millimeter
Bold - True/False.
GdiCharSet - Specifies the GDI character set that this Font object uses.
GdiVerticalFont - True if this Font object is derived from a GDI vertical font; otherwise,
false.
Italic - True/False.
Strikeout - True/False.
Underline - True/False.

Curve Fit Generate Dialog

Tabs include:
General tab
Various labelling set-ups of the graphical display. But also where you can use to filter data
according to the Fit or Residual values from the Optimize module.
Standard tab
Setting out a number of ready derived scatter graphs to use.
Advanced tab
Setting out a complete list of all the data available to fit. Once the options required are
selected press the Activate tick to activate the display.
Activate Clear
Curve Fit Dialog - General Tab
Options
Filter - Normal/Fit/ Residual - in Normal mode filtering will take place according to how
the wells have been de-selected in the Data tab; any de-selected wells will not be used. If
however only the Fit or the Residual of a well has been de-selected then using this Filter
will allow only one or the other’s values to be displayed on the Curve. This option is
intrinsically linked to the Optimize module and vice versa.
Point_Reduction - Multiple by which to down sample number of data points used.

Info
X_Mnemonic - Automatically filled input from either the Standard or Advanced graph sets
selection of the X-axis value to display. It is not possible to re-name the axis here - it is
given its active text status to allow you to copy and paste the mnemonic to elsewhere.
Y_Mnemonic - Automatically filled input from either the Standard or Advanced graph sets
selection of the Y-axis value to display. It is not possible to re-name the axis here - it is
given its active text status to allow you to copy and paste the mnemonic to elsewhere.
Curve Fit Dialog - Standard Tab
Lists standard selection of a number of ready derived scatter graphs to use.
Note: The X and Y axis titles are displayed at the top of this tab; this is for reference only. If
you wish to change the label titles this should be done in the Display property grid fly-
out.
Select the graph required and press the Activate tick to activate the display.
Activate Clear
Go Here for a Guide to activating the Curve Module.

Standard Graphs available
Standard Graph
Well Layer
Interval Velocity v Isochron This defines the relationship between
Interval Velocity and Isochron for the
specified layer. A typical application
would be where a salt layer interval
velocity increases as the salt thins.
Interval_Velocity_v_Time_to_Top_of_Layer (Not necessarily a justifiable method

geophysically). Same as above but
values taken to top of layer.
Interval_Velocity_v_Time_to_Middle_of_Layer (Not necessarily a justifiable method
values taken to middle of layer.
Interval_Velocity_v_Time_to_Bottom_of_Layer (Not necessarily a justifiable method
values taken to bottom of layer.
Interval_Velocity_v_Depth_to_Top_of_Layer As below but values taken to top layer.
Interval_Velocity_v_Depth_to_Middle_of_Layer **Good method** Popular simple
graphing method to derive VoK.

Standard Graph
Interval_Velocity_v_Depth_to_Bottom_of_Layer As above but values taken to bottom
layer.
Average_Velocity_v_Time_to_Base_of_Layer Simple Approximation
Time_v_Seismic_Time WELL_LAYER_BOT_TIM
v,WELL_LAYER_BOT_TIME_GRD
Well Curve
V0 v Kz from sonic log
Values calculated by linear regression
Depth v Time from sonic log of sonic logs.
Average Velocity v time from sonic log

Curve Fit Dialog - Advanced Tab
Each of the axis selectors is used to specify what data are displayed in which axis within the
graphing window.
Note: The X and Y axis titles are displayed at the top of this tab; this is for reference only. If
you wish to change the label titles this should be done in the Display property grid fly-
out.
Note: The current event defines the base of the layer, while the top of the layer comes from
the previous event horizon. For the first event horizon, the top of the layer is assumed
to be the surface (i.e. zero depth and zero time).
Select the axes required and press the Activate tick to activate the display.

Activate Clear
Go Here for a Guide to activating the Curve Module.
A DETAILED GUIDE to all the inputs under the Advanced Curve tab is at the end of this
chapter and available Here.
Curve Fit Dialog - Randomize Tab
Randomise - - pressing this will take a random value.

Curve Fit XYZ Dialog
The XYZ tab dialog allows you to export the data from the curve into XYZ slots within VelPAK.
Note: The Save as Excel icon option on the Curve module also allows you to save the
numeric data as an external ‘Excel’ file.
This module takes the values of the X and Y axes from the graph and produces XYZ values
as required in the designated slots.
Type - Normal/Predicted - Predicted - only works on linear regressions. Given the X
value of a point it will work out the Y value for the point that will cross the line. Only hte
predicted ‘new’ X,Y points will be output in the XY output file produced.
X
X
X X Predicted value
X
X X Value
X
X
Verify - Yes/No - verify output.

Active_XYZ1 slot takes the values for the X axis.
Active_XYZ2 slot takes the values for the Y axis.

Inactive_XYZ1 slot takes the values that have been selected as currently inactive for the
X axis.
Inactive_XYZ2 slot takes the values that have been selected as currently inactive for the
Y axis.
For each output type select the XYZ Model Tree slot you wish the XYZ data to be stored in.
For example:
Active
Values Inactive
Values
X
X
X
Active_XYZ2 (Yaxis) X X
Values X
X
X X XX
X X
X
Inactive_XYZ2 (Yaxis) X
Values X
Active_XYZ1 (Xaxis) Inactive_XYZ1 (Xaxis)

Values Values

Advanced Curve Inputs

General Concepts for the Advanced Curve inputs
Well Location
There are four different locations associated with a well: the surface location, the location of
the well bore at the top well pick, the location of the well bore at the base well pick and the
location of the well bore at the mid-point depth. The values will be identical for a vertical well,
but will be different in the case of a deviated well.
The different locations are illustrated below.

MidX,MidY TopX,TopY
BotX,BotY A - XY Top of Pick
B - XY Bottom of Pick
C - XY Mid Point
A
C
B
rid
G
p
To
id
Gr
se
B C Ba A
Top Time or Depth Grid
Time /
Depth
Base Time or Depth Grid
Definitions
As you will see from the selection of definitions available from the Advanced curve option
there is a vast array to choose from to make your curve.
Most of the definitions stem from a few main definitions as listed below.
Well Definitions
The following diagram of a log defines the terms Top Well Pick and Base Well Pick.

Top Well Pick TOP_TIME,TOP_DEPTH
MID_TIME, MID_DEPTH
BOT_TIME, BOT_DEPTH
Base Well Pick
Top Time - (TOP TIME)

The time at the top well pick. This value is obtained by interpolating the time-depth curve
at Top_Depth.
Middle Time - (MID TIME)
The time at the mid-point depth. This value is obtained by interpolating the time-depth
curve at Mid_Depth.
Bottom Time - (BOT TIME)
The time at the base well pick. This value is obtained by interpolating the time-depth
curve at Bot_Depth.
Top Depth - (TOP DEPTH)
The depth at the top well pick.
Middle Depth - (MID DEPTH)
The mid-point depth between the top and base well picks.
Bottom Depth - (BOT DEPTH)
The depth at the base well pick.
Surface X, Surface Y - (Surf_X, Surf_Y)
The surface location of the well. This is taken from the well location data, not from the
time-depth curve.
Top X, Top Y - (Top_X, Top_Y)
The XY surface location of the well bore at the top well pick. The value is interpolated
from the well curve data at TOP_DEPTH. ‘A’ on the diagram below.
Middle X, Middle Y - (Mid_X, Mid_Y)
The XY surface location of the well bore at the mid-point depth between the top and base
well picks. The value is interpolated from the well curve data at MID_DEPTH. ‘C’ on the
diagram below.
Bottom X, Bottom Y - (Bot_X, Bot_Y)
The XY surface location of the well bore at the base well pick. The value is interpolated
from the well curve data at BOT_DEPTH. ‘B’ on the diagram below.

Surf_X, Surf_Y
B C A
Top Time Grid
Time
Base Time Grid Top_X, Top_Y
Bot_X, Bot_Y
Mid_X, Mid_Y

Grid Definitions
TopX,TopY
MidX,MidY
BotX,BotY
A
C
B
id
Gr
me
Ti
p
To
rid
G
e
m
Ti
se
Ba
B C A
Top_Depth_Grd
Top_Time_Grd
Bot_Depth_Grd
Bot_Tim_Grd
Pick.
The value of the base time grid interpolated at the base well pick (i.e. at BOT_X, BOT_Y).
The value of the top depth grid interpolated at the top well pick (i.e. at TOP_X, TOP_Y).
Top Time - (Top_Tim_Grd)
The value of the top time grid interpolated at the top well pick (i.e. at TOP_X, TOP_Y).
The value of the base depth grid interpolated at the base well pick (i.e. at BOT_X,
BOT_Y).

Vertical Apparent IV
THIS IS THE VALUE NEEDED IN A DEPTH CONVERSION TO TIE THE TIME GRID WITH
THE WELL DEPTH.
The interval velocity derived from the top time and depth grids, TOP_TIM_GRD_BOT and
TOP_DEP_GRD_BOT and the time and depth values at the well base pick BOT_TIME_GRD
and BOT_DEPTH.
Top_Tim_Grd_Bot
Top Time (BotXY)
Vertical Apparent
Interval Velocity
Bot_Depth_Grd
Bot_Tim_Grd
Misties
With deviated wells (or indeed straight wells) the values of the tops would not necessarily tie
exactly with the grid for the same surface. If this is the case you will need to be aware which
of the two values you will want.
The diagram below shows an exaggerated mistie between the well pick and grid. This
highlights the fact that if GRIDS are used then it is the X,Y position of point A (the surface XY
location of the well’s top pick) that is used as the Grid Value; not where the well track ‘enters’
the grid surface.

TopX,TopY
BotX,BotY
rid
G
e
m
Ti
p
To
A
Time Top Grid Time
Top XY Well Pick

Top Time Grid

Detailed explanations of Advanced Curve X and Y axis inputs

Tip: Use Hypertext links over the Graphics to go to diagrams and explanations.
STACK CURVE
Stack Curve - Location

X Coordinate
Y Coordinate
Stack Curve - TimeDepth

Stack Curve - Velocity

STACK LAYER
Stack Layer - Location

X Coordinate
Y Coordinate
Stack Layer - Isochron

Stack Layer - Isopach

Layer(StackDepth,StackDepth)
Stack Layer - TimeDepth

Top Time(GridTime)
Middle Time(GridTime)
Bottom Time(GridTime)
Top Depth(GridTime)
Middle Depth(GridTime)
Bottom Depth(GridTime)
Stack Layer - Velocity

Average Velocity(GridTime)
Interval Velocity(GridTim, Grid Time)
RMS Velocity(GridTime)

SURFACE XYZ
SURFACE GRID
WELL CURVE
Hold Cursor over

Entry
to go to Link
Well Curve - Location

X Coordinate
The X coordinate for each sample in the layer. Curve data can be displayed for more than
one well. All the samples within the current layer are displayed.
Y Coordinate The Y coordinate for each sample in the layer. Curve data can be
displayed for more than one well. All the samples within the current layer are displayed.
Well Curve - Residual

Calculated Well Depth Error
Well Curve - Time Depth

Calibrated Time
Values created as a result of running the calibration program or reading in calibrated data.
The time value at each depth sample. Curve data can be displayed for more than one
well. All the samples within the current layer are displayed.

Uncalibrated Time
The uncalibrated time value at each depth sample. Curve data can be displayed for more
than one well. All the samples within the current layer are displayed.
Depth
The depth value at each sample (these first 5 columns are what are loaded in to the File-
>Import ->Well Curve file). Curve data can be displayed for more than one well. All the
samples within the current layer are displayed.
Calculated Well Depth
Depth results that come from the current depth conversion set-up
Well Curve - Velocity

Average Velocity
The average velocity from the surface to this sample. Curve data can be displayed for
more than one well. All the samples within the current layer are displayed.
The instantaneous velocity between adjacent samples. This is what is displayed on the
TOPS display. Curve data can be displayed for more than one well. All the samples within
the current layer are displayed. Curve data can be displayed for more than one well. All
the samples within the current layer are displayed.
WELL LAYER
Well Layer - Isochron
Hold Cursor over

Entry
to go to Link
Along Hole(GridTime) - (AH_GRID_ISOCHRON)

The isochron based on the top and base time grid values (i.e. TOP_TIME_GRD and
BOT_TIME_GRD).VALUES ARE ONLY MEANINGFUL FOR VERTICAL WELLS. They
should be treated with caution for deviated wells.

Top Time Grid

TOP_TIME_GRD
Time
Base Time Grid
Along Hole(GridTime)
BOT_TIME_GRID
Along Hole(WellTime) - AH_WELL_ISOCHRON

The isochron based on the top and base time values (i.e.TOP_TIME and BOT_TIME).
These may well be offset from the grid values for top and base of layer due to misties (as
shown in the diagram below). Values are only meaningful for vertical wells. They should
be treated with caution for deviated wells.
Top Time Grid

TOP_TIME
(top well pick)
Time
Base Time Grid
Along Hole(Well Time)
BOT_TIME
(base well pick)
Layer(GridTime,WellTime,BotXY)

Well Layer - Isopach
Hold Cursor over

Entry
to go to Link
Along Hole(Grid) - (AH_GRID_ISOPACH)

The isopach based on the top and base depth grid values (i.e. TOP_DEPTH_GRD and
BOT_DEPTH_GRD).Values are only meaningful for vertical wells. They should be treated
with caution for deviated wells.
Top Depth Grid

TOP_DEPTH_GRD
Depth
Base Depth Grid
BOT_DEPTH_GRID
Along Hole(Well)
The isopach based on the top and base well picks (i.e.TOP_DEPTH and
BASE_DEPTH).These may well be offset from the grid values for top and base of layer
wells. They should be treated with caution for deviated well.

Top Depth Grid TOP_DEPTH

(top well pick)
Depth
Base Depth Grid
BASE_DEPTH
(base well pick)
Layer(GridDepth,GridDepth,BotXY)
Layer(GridDepth,WellDepth,BotXY)
Well Layer - Location
Hold Cursor over

Entry
to go to Link
Locations from one of the main VelPAK curve Definitions. Go Here for details.
Well Layer - Residual
Time(WellTime,GridTime,BotXY)
Depth(TieMode,BotXY)
Depth(WellDepth,GridDepth,BotXY)

Well Layer - Optimization
Global Fit ()
Global Fit ()
Global Residual ()
Global Residual ()
Well Fit ()
Well Fit ()
WellResidual ()
WellResidual ()
Well Layer - Time Depth
Hold Cursor over

Entry
to go to Link
Pick.
Top Time
Top Time(GridDepth) - (Top_Time_Dep_Grd)
The time obtained by interpolating the well time-depth curve at TOP_DEPTH_GRD. Time
values are obtained by interpolating the well time-depth curve at the grid-derived depths:

B C A
Top Depth Grid
Top Time (Grid Depth)

Time Base Depth Grid
Middle Time
Bottom Time
Bottom Time(GridDepth) - (Bot_Tim_Dep_Grd)
The time obtained by interpolating the well time-depth curve at BOT_DEPTH_GRD. Time
values are obtained by interpolating the well time-depth curve at the grid-derived depths.
B C A
Top Depth Grid

Time/
Depth
Base Depth Grid
Bottom Time (Grid Depth)
Top Depth

Top Depth(GridTime) - (Top_Dep_Tim_Grd)

The depth obtained by interpolating the well time-depth curve at TOP_TIME_GRD. Depth
B C A
Top Time Grid

Time/
Depth
Top Depth (Grid Time)

Base Time Grid
Middle Depth
Bottom Depth
Bottom Depth(GridTime) - (Bot_Dep_Tim_Grd)
The depth obtained by interpolating the well time-depth curve at BOT_TIME_GRD. Depth

B C A
Top Time Grid

Time/
Depth
Base Time Grid
Bottom Depth (Grid Time)
Well Layer - Time Depth Grid
Hold Cursor over

Entry
to go to Link
Grid values interpolated at well locations.

The grid values are interpolated from the time and depth grids at the top and base well picks.
The time grid values are illustrated below, again with a greatly exaggerated mistie between
the well and grid data.
Remember that you may need to consider Mistie discrepancies between Grid and Well Pick.
Top Time - (Top_Time_Grd)
Top Time(BotXY) - (Top_Tim_Grd_Bot)
The value of the top time grid interpolated at the base well pick (i.e. at BOT_X, BOT_Y).

B C A
Top Time Grid

Top Time (BotXY)
Top_Tim_Grd_Bot
Time
Base Time Grid

Top Depth(BotXY) - (Top_Dep_Grd_Bot)
The value of the top depth grid interpolated at the base well pick (i.e. at BOT_X, BOT_Y).
B C A
Top Depth Grid Top Depth (BotXY)

Top_Dep_Grd_Bot
Depth
Base Depth Grid


Well Layer - Velocity Average

Average velocities to top of layer.
Hold Cursor over

Entry
to go to Link
Top(GridTime,GridDepth)
The average velocity from the surface to the top of the layer, based purely on the grid
values i.e. TOP_TIME_GRD and TOP_DEPTH_GRD.
Top(GridTime,WellDepth)
The average velocity to the top of the layer, based on the grid time and well depth i.e.
TOP_TIME_GRD and TOP_DEPTH.
Top(WellTime,WellDepth)
The average velocity from the surface to the top well pick, based purely on the well values
i.e. TOP_TIME and TOP_DEPTH.
Bottom(GridTime,GridDepth)
The average velocity from the surface to the base of the layer, based purely on the grid
values i.e. BOT_TIME_GRD and BOT_DEPTH_GRD.
Bottom(GridTime,WellDepth)
The average velocity to the base of the layer, based on the grid time and well depth i.e.
BOT_TIME_GRD and BOT_DEPTH.
Bottom(WellTime,WellDepth)
The average velocity from the surface to the base well pick, based purely on the well
values i.e. BOT_TIME and BOT_DEPTH.
Well Layer - Velocity Interval

Interval velocities based on layer average velocities Interval velocities are based on the
average velocities to the top and base of the layer. They are only strictly correct for vertical
wells and should be treated with caution if the well is deviated.

Hold Cursor over

Entry
to go to Link
Along Hole(GridTime,WellDepth)
The interval velocity based on the grid times and well depths i.e. TOP_TIME_GRD,
TOP_DEPTH, BOT_TIME_GRD and BOT_DEPTH.
Along Hole(WellTime,WellDepth)
The interval velocity between the well picks, based purely on the well values i.e.
TOP_TIME, TOP_DEPTH, BOT_TIME and BOT_DEPTH.
Layer(GridTime,GridDepth,BotXY)
The interval velocity based purely on the grid times and depths i.e. TOP_TIME_GRD,
TOP_DEPTH_GRD, BOT_TIME_GRD and BOT_DEPTH_GRD.
Layer(GridTime,GridDepth,TopXY)
The interval velocity derived purely from the top time and depth grids interpolated at the
base well pick (i.e.(TOP_TIM_GRD_BOT, TOP_DEP_GRD_BOT, BOT_TIME_GRD and
BOT_DEPTH_GRD).Vertical Interval velocities.The vertical interval velocities are derived
at the location of the base well pick (i.e. at BOT_X, BOT_Y). They correspond more
closely with the interval velocities used in depth conversion.
Layer(GridTime,WellDepth,TopXY)
Layer(GridTime,WellDepth, BotXY)
Layer(GridTime,WellDepth,BotXY,Well Tie)
The interval velocity derived from the top time and depth grids (TOP_TIM_GRD_BOT and
TOP_DEP_GRD_BOT) and the time and depth values at the well base pick (
BOT_TIME_GRD and BOT_DEPTH).
THIS IS THE VALUE NEEDED IN A DEPTH CONVERSION TO TIE THE TIME GRID
WITH THE WELL DEPTH.
The vertical interval velocities are derived at the location of the base well pick (i.e. at
BOT_X, BOT_Y)). They correspond more closely with the interval velocities used in depth
conversion.
WELL TOP
Well Top - Location
X Coordinate
The X coordinate of this top; this is calculated by looking at the time-depth curve, and
interpolating the X coordinate off the deviation information there.

Y Coordinate
The Y coordinate of this top, calculated as above. In a deviated well, the X and Y
coordinates will be different at each top.
Well Top - Time Depth

Time(WellDepth)
The time to this top, calculated from the time-depth curve.
Depth
The depth to this top, as loaded in to the File->Load->Well->Tops option.


Optimize Module
Introduction
In the Optimize module, parameter values are derived for different velocity functions, and
various displays are produced to derive best-fit parameter values for all classic V0 and K
depth-conversion methods for each required layer.
Optimize uses non linear least squares curve fitting of time-depth curve data derived from
sonic logs, check-shots or tops and times to derive the best function parameters for each
well. It has the facility for allowing one parameter to be fixed and the other mapped e.g. fixed
K and contoured V0. With close interaction between the parameter grid and the mapping
modules you can immediately see the V0 and k values that best suit your data.
Tip: For the new user there are many different aspects of the Optimize module which could
well appear confusing. It is thoroughly recommended therefore that a new user works
through the Training guide for the Optimize module which will lead you through a typical
flow of work.
The Optimizing process within VelPAK

• The Layer Definition process has to firstly be defined; this enables VelPAK to split the logs
into layers to match the seismic interpretation. From there Optimization of the specific
layer can be run.

• A depth conversion method is then defined. For example Vz=V0+Kz.
• A rough estimate of the Parameter Space is then defined. This is the range of V0’s and
K’s to examine. This can be changed and the real area of interest zoomed into when it
becomes apparent.
• This process is completed for each well.
This example shows a

Parameter Space of
1000 to 3000 for V0
and 0 to 3 for K with
a grid spacing of
50*50.
• For each node on the grid, Optimize calculates the best ‘Fit’; how well the V0,K parameter
pair fits the log data for this one well. The ‘Residual Line’ is also calculated; any
parameter pair down this Residual line would result in a zero depth error for this well

.
Point A Best Fit

represents the
Best Fit and the
zero residual,
combined.
Point A
Residual
Line
For each pair of points on the time depth curve Optimize compares the known depth of
the base point (B) against the depth predicted by the function parameters.
A
B
Depth
Time
In the case of Vz = V0+Kz the depth conversion formula is:

Given the known depth of point A (Zt),and the V0 and K parameters Optimize can predict the
depth at point B (Zb).
• So for each possible V0,K pair Optimize calculates an RMS residual. It then minimizes this
value using it’s optimization techniques.
This provides us with the Best Fit function.
• Optimize then looks at the Best Fit for all of the wells and the mean Best Fit.
This is called the ‘Layer Fit’.
• Optimize can also look at the residual lines for all wells. This can be used to detect and
exclude outliers. The best residual is the point at which the mean value of the residuals and -
given that - the fit to the log data are optimum.

Residual
User
Fit
Concepts of Optimizing in VelPAK

1. Through out the displays you will see the Gradient is always the Y axis; the Intercept is
always the X axis.

Gradient
(k)
Intercept (V0)
2. It is useful or advisable to always have the gradient starting at zero. This would therefore
show you along this axis the V0 values that would produce no error for each selected
well.
3. Given the type of well and curve data you have it may not even be appropriate for you to
run Optimize on it. For a good result from Optimization then the Residual lines for all wells
should show some sort of convergency in the V0 and k domain. If the Residuals did not
converge then you may as well use a function or simple contour V0 grid for your depth
conversion.
Residuals Residuals
Display Display
k k
Vo Vo
Good Data for Optimization Bad Data for Optimization
4. All values are re-generated if a well is selected or de-selected. If you have set some
values in the Generate General tab to ‘No’ then the original values of these will be wiped
and replaced with blanks. (It will not keep the values as derived from an earlier
generation).

5. Some generated values are dependent on other values being generated and therefore
require these other values to be selected to be generated as well as themselves. Go Here
for a table for dependencies.
6. Selecting and de-selecting wells will be necessary if you have outliers in your model.
These will show up as Line Fits which do not appear to conform to the rest of the data, as
shown in this image below. Go Here for how to select/de-select wells.
Non-
Conforming
Outliers
7. Curves and tops can be selected or de-selected separately; you may well have sound
tops where the curve is poor or vice versa.
Types of Optimize
Optimize types can be a baffling mix of lines and grids, fits and residuals. Here we try and
explain all the different elements; how they are calculated and what their displays show.

There are twelve different types of values that can be generated and displayed. These are
listed in the table below.
RESIDUAL
FIT The ‘zero-error’ line; the set
How well the data fits to the log data of V0 and K values that would produce a
zero-error for a well
WELL Grid WELL Grid

Information relates Well_Grid_Fit Information relates Well_Grid_Residual
solely to currently solely to currently
selected well Line selected well Line
Well_Line_Fit Well_Line_Residual
Point Point
Well_Point_Fit Well_Point_Residual
LAYER Grid LAYER Grid

An average of all the Layer_Grid_Fit An average of all the Layer_Grid_Residual
selected wells in the selected wells in the
model Line model Line
Layer_Line_Fit Layer_Line_Residual
Point Point
Layer_Point_Fit Layer_Point_Residual
Fit Values
How well the data fits to the log data for the given depth conversion method set-up.
Calculation Details
For each pair of sample points on the well curve the depth isopach is worked out using the
given V0 and K pair for that point and the time from the well. Optimize compares the known
depth of the base point against the depth predicted by the function parameters for each
sample. The RMS is then taken of all these difference values for the given V0 and K and this
is the value that is assigned the point or node. Note that values are Normalized within the
process so values are always under ‘1’. Also be aware that each calculation for each sample
down the curve takes the true time-depth value for the sample above as its starting value so
the effect of the calculations are not cumulative down the curve.

0.5 } V0,K value for this = 0.48, difference = 0.02
Sample 0.5 } V0,K value for this = 0.46, difference = 0.04
Rate } V0,K value for this = 0.49, difference = 0.01
0.5
A
0.5 } V0,K value for this = 0.46, difference = 0.04
B
Depth
} ....etc
RMS of Total Difference = 0.0275
This is the value assigned to the Grid

Node for the given Vo, K value on the
Time
Graph
Well_Grid_Fit
Given the depth conversion parameters entered, a grid is generated for each well in the
model. The generation takes each pair of V0 and K values and works out the depth value,
comparing it to the time-depth curve data for that layer, for that well. The value plotted is the
difference between these two values. As the value of V0 and K become more true then the
grid values will reach a low (or trough). Contouring these values up will therefore show where
the best values of V0 and K will be.

Well_Line_Fit
This method scans on the Y axis and gives the best fit of the solution trough for the V0. The Y
axis is divided up into 10 sample to provide the fixed k values across the Optimize area.
Although the method for derivation of the value for each point is the same as is shown in the
diagram above the results will be slightly due to the sample rate.
Taking the seed value the calculations along the sample lines begin at a point somewhere in
the middle of the optimize area. When each point is generated the routine checks to see if
that value is lower than the point on either side of it along the line. Thus the lowest value point
along the line is calculated and it is through this point that the line fit passes.
Values get closer Values get further away
Y (k)
10
samples
Well Line Fit
X (V0)
If you displayed both the Well Grid Fit result and the Well Line Fit as shown in the magnified
example below there will be slight discrepancy due to the angle of the trough not being
exactly perpendicular to the fixed Y axis. However this is usually insignificant.
Magnified example
of possible discrepancy
between grid and line fit
Actual value taken
Fixed Y parameter
Y (k)
Well Grid Fit value

- tangent taken Well Line Fit
(not fixed Y parameter)
X (V0)
Well_Point_Fit
The best fit given the values that produced the Line Fit and the Y (k) value. Naturally this
should always fall on the Line Fit at the very bottom of the contour trough.

Layer_Grid_Fit
An average of all the values calculated for each grid node for all the wells in the model. If
there are some poor-data wells within the data this could produce a shifted result. (In this
case moving through the displays of individual well fits and line fits may well show you some
outlying wells which would need to be de-selected and the Optimization re-generated for a
more robust result).
This Grid is stored within the Model Tree under the Expanded Slot ‘Optimization Fit’.
However, it should be remembered that these grids do not conform to the other surface grids
in the model.
Layer_Line_Fit
An average of all the Line Fits generated for the Selected wells in the model. These values
need to be generated from ‘scratch’ again in the same method that the Well Line Fit is
generated except that each calculation uses all the well values at each point.

Layer_Point_Fit
One point calculated from the average of all the Well Point Fit values.This value will be
generated from scratch again in the same method the Well Point Fit is generated except that
each calulation uses all the values at each point.
Whereas Grid calculations by their nature have to stay in the boundaries of the grid defined
minimum and maximum, if the Layer and Point fits occur outside the Min/Max then the values
will still be correctly calculated but not displayed in the Display window!
The Average value for all the Layer Fits is an average RMS calculated by:
Residual Values
The ‘zero-error’ line; the value at which any combination of V0 and K would produce a zero-
error for a well, for the given depth conversion method set-up. Bare in mind this is a non-
unique solution and a combination of bad V0 and Ks could give the same zero-error as a
combination of ‘best’ V0 and Ks could give.
The actual methodology of calculating the values for Grid, Line and Point are the same as for
the FIT; however what the procedure is calculating for the Residual values is obviously
different. Given the seismic time at the top and base of layer, the last depth (if a buried layer)
and the depth conversion formula set up, the generation calculates the error using the V0 and
K of that point. In essence it does exactly what the Tie option within VelPAK does.
Well_Grid_Residual
The Grid Residual display tends to be striped contours (as opposed to the trough usually
seen in the Fit Contour display) where the focus would be the zero contour (implying zero
error along that line).

Well_Line_Residual
Should be a line (close to the zero contour of the Grid residual) marking the line down which
the error would be zero. This is calculated in the same way as the Well_Line_Fit calculation.
Well_Point_Residual
How can a Well Point Residual be calculated, when any of the V0 and K pairings down the
Well Line Residual line can give zero error? The answer is that for this value the best Fit is
calculated also, and the Well Point Residual is the point that falls on the Well Line residual
line, closest to the Fit point.
Note: The relationship between the Well Fit and the Residual may not make this point a
valid or useful point; this should be kept in mind when viewing this point!
The Well Point Residual is the value

on the Residual line which passes by
the lowest value of the Fit (as shown
by the Fit contours).
Well Point
Residual Well Point Fit
Layer_Grid_Residual
The average of the grid values calculated for the selected wells.

Layer_Line_Residual
An average of all the Line Residuals generated for the Selected wells in the model. These
values need to be generated from ‘scratch’ again in the same method that the Well Line
Residual is generated except that each calulation uses all the well values at each point.
Layer_Point_Residual
One point calculated from the average of all the Well Point Residual values.This value will be
generated from scratch in the same method the Well Point Residual is generated except that
each calulation uses all the values at each point.
Overlay displays available in the 2D Parameter Space
Grid Nodes
The nodes of the grid that has been generated for the current active Map Type.
Standardly this grid will be displayed as pink dots. Zooming in on the nodes with the Grid
Node Label switched ‘on’ will show the values of the node which would be currently displayed
as a contour map.
Note: These are grids of specific data relating to the Optimize generation routines and
should not be confused with standard grids stored within VelPAK.The layer grids are,
however, still stored within the Model Tree under the Expanded Slot ‘Optimization Fit’.

Line Fit
The Fit showing how good the fit is between the Well and the log data. The current well or all
wells can be selected from the Display Property Grid.

Line Residual
The ‘zero-error’ line; the value at which any combination of V0 and K would produce a zero-
error for a well.The current well or all wells can be selected from the Display Property Grid.

Point Fit
The best fit given the values that produced the Line Fit and the Y (k) value.

Point Residual
Displays the lowest point of the Residual (zero error) line; the point where residual is closest
to the Well Fit.

Point User
Displays the point picked by you when the Point Edit option is activated.

A Quick Guide to Generating Optimize Data
A Quick Guide to Generating Optimize Data

1. Make sure you are in the correct Event Horizon you want Optimize to be run on!
2. Make sure you have your Layers determined. (See Layer Tool Module)
3. In Surface Depth Conversion property grid, set up the formula to use. Make sure it is set
to come from [Optimize]method. You do not enter any values in the Parameter banks
since you do not know them yet (this is what Optimize will be calculating for you!).
4. In the Optimize module in the Generate property grid, enter the Parameters Vo and K for
your Optimize methods. This is the value of the ‘seed’ and increment and the min and
max values.
5. Generate the optimize values, parameters and display.
6. Look at the results and decide upon the best Vo and K!

Trouble Shooting - reasons your display doesn’t work:
Trouble Shooting - reasons your display doesn’t work:

First of all check the four different types of display from the Display option to see whether you
are getting any type of display.
No display at all!
• Are you in a selected Layer? Check you are not in ‘Layer 0’ (not selected layer).
Check that this is for all wells, not just the well currently selected. Bringing up the well
curve display (from the Well module) may well help you see a reason for yourself.
• If you fail to get any reasonable display it may be because you have not defined the
layers within this module. Layer display in this case will provide a display of one color
band over the entire area.
Some types display; some do not..

• No display under Well Fit - but display under all three others; you have no well curve
for the layer you are working in. For example, the well could look like this:
Curve does not start until

further down well.
• You may find that it is just this one well you have no fit data for; scrolling through other
wells either in the Well Module or in the optimize display may show this up for you.
• You have no Point or Line display but you have contours; although there is no ‘trough’
and they appear to veer off to a corner.
Your Optimize calculation window has been incorrectly defined. Re-define your
Optimize generation Min/Max window to a larger window of calculation. (Standardly a
V0 of 0 to 5000 and k of 0 to 3 are sufficient). Note that using the Point Edit option on
the Display would give you the values of the Fit and Residual Points and from there
you should be able to see what sort of values are expected.

Icons on the Optimize Window
Icons on the Top Level
Save as Print Print Print

Excel Set Up Preview
Standard and Non-standard use Icons for VelPAK operations.
Print options - Standard VelPAK icons, Go Here for details.
New, Open, Save - These icons within the Optimize module (not referring to the main
VelPAK window which uses the same icons) refer to New, Open and Save as ‘Excel’ file
which will save the current state of the data grid i
Note: Saving the model in the usual ‘Save’ method will only save the current set up as the
situation is when you press the save option.
Event Well
Event or Well within the VelPAK model.

Display Type Options
Select type of display to view on your Optimize window. It is likely you would want Contour or
Shaded Contours shown at all times while you are working in the Optimize module.
Basic
Will display just the fit and/or residual lines and Map Types as selected.
Ribbon
Reflects the underlying value of the parameter space along a fit or residual line. Particularly
useful for looking at a Line Fit since they can prove invaluable at spotting outliers whose Fit
appears to be valid (as a line) but the value of each point on the Fit line shows discrepancy.

Contour
Black contours of the Optimize grid will be displayed.
Shaded
Shaded color contours of the Optimize grid will be displayed.

Layers Visible Options
Turn Display element ON or OFF for display on the Optimize view. With or without element
labels.
Note: These visible layers can also be selected to be on or off via the Display General
Property Grid.
Go Here for a full discussion and examples of the Layers Visible Overlays.
Line Fit - The Line showing well the data fits to the log data for a fixed Y value (usually k).
Line Residual - The ‘zero-error’ line; the value at which any combination of V0 and K
would produce a zero-error for a well.
Point Fit - The actual lowest point of discrepancy for the fit down the line.

Point Residual - The actual lowest point of residual error for the fit down the line.
Point User - Displays where the User point has been selected.
Surface Node - Displays the Surface Grid nodes over the Optimize display.
Labels - displays the labels of the respective items on display.
Edit Mode Options
Only Point Edit is available as an Edit mode in the Optimize module.
Point Edit Icons
Point Point Value Value

Edit Pick Edit Move
Point Pick/ Point Edit - Selection and De-selection of wells
Note: For both these options, selection can occur on the well as well as the line on display.
Point Pick -selects the current well as active - and switches the display to this well in the
Well Module.
Point Edit - will allow you to select or deselect wells within the model for use within the
Optimization routine. The wells will become grayed out until you regenerate again.
Note: If you deselect a well you will need to regenerate the Optimize display which can take
some time. Once you have regenerated the display the de-selected wells will cease to
be visible. If you wish to re-select them (and therefore have to re-generate the display
again) you will need to go in to the Data Tab and make the de-selected wells active
again.
Value Edit

In Value Edit mode, using the left mouse button on the optimize display will allow you to
change the position of the User value point on the display. Select Value Edit and then click on
the place on the display where you want your User value point to be. A blob of color will
appear on the display and an Alert style window will pop-up with all the relevant information
for that point.
Tip: If you click a point and do not see a point appear then check in the Display Color tab that
your ‘Layer_User_Color’ is not set to Foreground or the same color as the color contour
over the area.
The alert window will show the values of the v0 and k at the selected User point.
Pressing OK will fix the User value point on the Optimize display to be this value until this
method is executed again.
Note: The User values are the values that will be used in the Depth Conversion if the
Formula is set to come from Optimize_User (as shown below).

Value Move
Selecting the Value Move button over the optimize window at the required place will
activate an impressive set of processes! At a click of the button you will get a grid display
(in the Surface module) of either the X or Y axis - whichever is set to be variable - for all
the (selected) wells in the area. Standardly this would be ‘Fixed k’ and a ‘variable v0’;
allowing you at the click of the middle button to produce and view a “V0 to tie” error map
which would calculate the V0 necessary given the fixed k to tie your wells over the area.
Note: In order that you get the required instantaneous display of the correct values, certain
parts of VelPAK need to be set up or selected before pressing the middle button. This
is documented below.
Step-by-step process of what pressing the Value Move does:

- Using the current XYZ tab set-up;
- Using the current Gridding set-up and
- Using the current Surface Display set-up:
1. If User is the selected Type on the XYZ tab - A point is selected on the display; this will
become the User value of V0 and k.
[If Residual or Fit is selected on the XYZ tab then these values will be used as the Type].
Values will be output to the three slots in the Model Tree as named in the XYZ tab. (Go
Here for details of what values will be output for each slot.
{
}
2. The XYZ slot selected in the Gridding set-up will be gridded up and the resultant grid
displayed (if the Surface display is set to contour the correct grid.)

‘V0 to tie’ Error map
Note: It is worth noting that once all these tabs and property grids are set up, if ‘User’ is
selected as XYZ Type then using the Value Edit option will give you an almost-
immediate error grid for the selected User V0 and k, time after time after time with no
further set-up required.

The Graph and Data Tabs
Graph Tab
Provides the 2D Parameter Space for the optimized display, values and fit.
Use the Optimize Display Property Grid to change any display parameters.
Data Tab
Data that is displayed on the Optimize window is displayed numerically in this Tab.
Data can be filtered to your specifications here to be displayed on the graph.
Comment column - note the Comment column which will store any comment you have
regarding individual wells (like for example why you chose to make a well Inactive).

Moving the Columns

Filtering the Data

Custom - User defined selection of Operator and Operand to filter data. See Custom
Filter for details.
Custom Filter
Location.


Optimize Display Dialog

The Display property grid deals with the display style and set up of the 2D Parameter space
to be displayed in the VelPAK Optimize Module window.
Tabs include:
General tab - Basic set up details for particular aspects of the display.
Range tab - Allows you to select the Range of your display from the Grid.
Color tab - Changes the color of various items on the Optimize display.
Note: The display generated by Optimize can be re-displayed using the Activate tick of the
Display property grid, so you do not need to re-generate the values every time. All the
displays are saved in the binary model, so pressing the Display Activate after re-
loading the model will re-generate the displays.
option.


Option
Display_Type - select type of surface to display: basic, ribbon or contours.
Map_Type - type of map to display; Well Fit, Well Residual, Line Fit or Line Residual.
Well_Box - Yes/No - draws a white box around the Well Label to be able to read the label
on a busy display.
Well_Type - type of well selection; all wells or current well or none. Although you may
have selected the Map_Type as ‘Well_Fit’, which will display contours, lines and/or points
for a single (selected) well; you can request here a display of all the selected wells in the
model to be put on the display. Use Layers Visible to request what elements from each
well you want to display.
User_Point_Box - Yes/No - draws a white box around the User Point Label to be able to
read the label on a busy display.
Note: Map Type and Well type above two options are used in conjunction with each other;
Go Here for a discussion of what the combinations of the two selections would
display.
Contour
Contour_Color - Click on the box to the right of the color selection slot to bring up a list of
color tables available to you. The list will bring up all the color tables previously defined in
TKS (as well as some default VelPAK color tables available; Cyan_Red, Grey,
Topographic and Seismic).
This option utilizes stored TKS color tables that are usually stored in the ‘Colorbars’
directory of the TKS installation on your PC. If this directory is moved elsewhere then
VelPAK will still be able to find it.
To create a new color table for use within VelPAK you will need to go into TKS and define
and save it in the standard way; the list within VelPAK will automatically be updated with
the new color table the next time it is brought up.
Contour_Fit_Incr[ement] - choose the increment that best suites the contouring of the
FIT data.

Contour_Fit_Maximum - maximum of surface to be used for contouring of the FIT.

(Affects the display only, not the data.)
Contour_Fit_Minimum - minimum of surface to be used for contouring of the FIT.
(Affects the display only, not the data.)
Contour_Residual_In[crement] - choose increment that best suits the contouring of the
data of the RESIDUAL.
Contour_Residual_Maximum - maximum of surface to be used for contouring of the
RESIDUAL.
Contour_Residual_Minimum - minimum of surface to be used for contouring of the
RESIDUAL.
Contour_Smooth - A smoothing algorithm that can be used to make maps with large
grid cell spacing smoother. Note this option does not work on faulted data.
Ribbon
Ribbon_Size - thickness of the ribbon mark. Values are relative to each other; 1
produces a thinner line that 5.
Ribbon_Type - Color ribbons according to surface value.
Overlays
Color is set using Color tab on this Property Grid.
Go Here for a full discussion and examples of the Overlays.
Grid_Node - Choose display overlay to be on or off. Displays the Surface Grid nodes
over the Optimize display in the same form as Grid node display on the Surface module.
Line_Fit - Choose display overlay to be on or off.
Line_Residual - Choose display overlay to be on or off.
Point_Fit - Choose display overlay to be on or off.
Point_Residual - Choose display overlay to be on or off.
Point_User - Choose display overlay to be on or off.
Labels
Grid_Node_Labels - labels on an off if Overlay selected.
Line_Fit_Labels - labels on an off if Overlay selected.
Line_Residual_Labels - labels on an off if Overlay selected.
Point_Fit_Labels - labels on an off if Overlay selected.
Point_Residual_Labels - labels on an off if Overlay selected.
Point_User_Labels - labels on an off if Overlay selected.

Allows you to select the Range of your display from the ‘Grid’ - [the parameters of generation
of the Optimize window as setup in the Parameters tab of the Generate property grid] or
leave it as Auto, in which case any spurious value-displays that fall outside the grid area will
also be shown within the window.
option.
Option
Axis
XY_Type - Select the XY range either from the entire range as defined for the whole
optimization or just the selected grid.

option.
Use the down arrow ()to select from the available colors.
Color - All of the Color inputs have the same color options. Select the color for the drop-down
selections.

The Different Displays that Map_Type and Well_Type give
Once the Optimize values have been generated a crucial part of the procedure is to be able
to display and view exactly what you want to see on your display. This is done using a
combination of the Map_Type and the Well_Type on the display Property Grid. Here we set
out what each selection would display.
Note: In this listing it is presumed that all the Layers Visible are switched on (although not
necessarily the labels). It is also presumed that the Display Type is set to ‘Shaded’
(contours) unless otherwise stated.

Well_Fit and None
The Well Grid Fit grid is displayed as a shaded contour map for the current well. No other Fit
methods are displayed since no ‘Well Type’ has been selected.
Well_Fit and Current_Well
The Well Grid Fit grid is displayed as a shaded contour map for the current well. The Current
Well Line Fit and the Well Point Fit is displayed as the light blue line. Note that the Well Line
Residual and the Well Point Residual for the current well is also displayed. (These are
displayed because they are selected as ON in the Layers Visible and therefore can easily be
turned off if deemed incongruous on the Fit display.)

Well_Fit and All_Wells
The Well Grid Fit grid is displayed as a shaded contour map for the current well. The line fits
and residuals for all (selected) wells are displayed over the contour pattern of the current
well. This would allow you to compare the fits of all the wells with the contour fit pattern of this
one selected well.
Well_Residual and None
Displays the Well Grid Residual contour display for the currently selected well.

Well_Residual and Current_Well
Displays the Well Grid Residual contour display for the currently selected well. The current
Well Line Residual and the Well Point Residual is displayed as the dark blue line. The Well
Line Fit and the Well Point Fit for the current well is also displayed. (These are displayed
because they are selected as ON in the Layers Visible and therefore can easily be turned off
if deemed incongruous on the Residual display.)
Well_Residual and All_Wells
The Well Grid Residual grid is displayed as a shaded contour map for the current well. The
line fits and residuals for all (selected) wells are displayed over the contour pattern of the
current well. This would allow you to compare the residual of all the wells with the contour fit
pattern of this one selected well.

Layer_Fit and None
The average of all the well grid fits will be shown as the Layer_Grid_Fit contour display. The
line and point layer fit and line and point layer residual will also be displayed if switched on
under Layers_Visible even though the actual well selection is set to None.
Layer_Fit and Current_Well
The average of all the well grid fits will be shown as the Layer_Grid_Fit contour display.
The fit and residual of the current well is also shown as well as the average fit and residual of
the layer’s selected wells.

Layer_Fit and All_Wells
The average of all the well grid fits will be shown as the Layer_Grid_Fit contour display.
All well fits and residuals will also be displayed.
Layer_Residual and None
The average of all the well grid residuals will be shown as the Layer_Grid_Residual contour
display. The line and point layer fit and line and point layer residual will also be displayed if
switched on under Layers_Visible even though the actual well selection is set to None.

Layer_Residual and Current_Well
display.
The fit and residual of the current well is also shown as well as the average fit and residual of
the layer’s selected wells.
Layer_Residual and All_Wells
display.
All well fits and residuals will also be displayed if switched on under Layers Visible.

Generate Dialog
Generate Dialog
Note: The display generated by Optimize can be re-displayed using the Activate tick of the
Display property grid, so you do not need to re-generate the values every time. All the
displays are saved in the binary model, so pressing the Display Activate after re-
loading the model will re-generate the displays.
The Generate Property Grid consists of two tabs:

General tab - given all the different types of results the Optimize module can generate,
this tab is the selection procedure for the different results. Default is ‘Yes’ meaning all
results possible will be generated (you don’t have to use them all!).
Parameters tab - setting the minimum and maximum range of values to be used within
the calculation and the number of increments.
Various Discussion topics regarding Generation of the Optimize

Display
Set-up of the Generate parameters can essentially be thought of as similar to producing a
grid consisting of grid nodes; you define the XY minimum and maximum, and the number of
divisions you wish your graph to be divided up into and the program will work out the values
for you.

Generate Dialog
5000
A Level
Another Level
} A Step (Increment)
V0 } Another Step
Y-axis Levels = 10
Step= 500
x x x
x x x
0
Figure 1: Values 0 (Minimum) 5 (Maximum)
will be calculated at k
each of these
Levels = 16
points, and then X-axis
Step= 0.31225
contoured.
Zooming in on your display - Regenerate at new XY Min/Max

The right hand mouse button will produce a ‘pop-up’ allowing you to Zoom/Pan into your
contour display to view your data in more detail.
You can zoom on the 2D Parameter Space Optimize display.

The whole display can then be re-calculated using the new X/Y Min-Max values for V0 and k.
On pressing the Generate activate tick once the plot has been zoomed an alert will appear to
warn you that the results will be replaced.

Generate Dialog
Note: Note that since the values are being re-calculated the display generated could be
slightly different from the original one.
Fixing a parameter in a three (or more) parameter function:

You can still use the Optimize method for functions with more than two variable parameters,
by fixing one of those parameters. This is done by putting in exactly the same value in the
Minimum and Maximum slot on the Parameter Bank number relating to that parameter. (An
example of this would be using the Hyperbolic Tangent Function, the first given parameter, V1
(Maximum Velocity) could be given a fixed value of 5000 m/s.).
HOWEVER you can not use this method to fix either V0 or k in a two parameter function such
that there is only one variable parameter. To do this you need to go to the XYZ Property Grid
and fix the parameter you require to be fixed and produce an output of the data.
Velocity Function Parameter Ranges

It is difficult to give precise ranges for the parameters of the various velocity functions, but the
following tables should give a good indication of the expected order of magnitude for each
parameter. Table 1 below shows the parameter values which give the closest fit to a synthetic
time-depth curve, with the depth measured in metres. The time-depth values were based on
the linear velocity function V0+kZ, with V0 set to 2000m/s and k set to 1. The fit was
calculated over the depth range 1000 to 3000 metres.
Example velocity parameters using metric data.
Function Parameters
Linear V0=2000, k=1.000
Houston V0=910.7, k=0.009240
Binomial V0=2000, k=0.000500, n=1.000
Slotnick V0=2376, k=0.000258
Faust a=110.6, m=2.115
Hyperbolic tangent V1=5000, a=498.2, b=133.3

Generate Dialog
Example velocity parameters using metric data.
Function Parameters
Parabolic w=8.294x105, e=7664
Asymptotic slowness S0=173.1, Sm=55, q=1146
Constant V0=3894
The limiting velocities used in the asymptotic methods (V1 in the Hyperbolic tangent function
and Sm in the Asymptotic slowness function) were constrained to realistic values.
The corresponding parameter values when using data with depths measured in feet are
shown in Table 2 below.
Example velocity parameters using imperial data.
Function Parameters
Linear V0=6562, k=1.000
Houston V0=2988, k=0.002816
Binomial V0=6561, k=0.000153, n=1.000
Slotnick V0=7794, k=0.000079
Faust a=207.2, m=2.116
Hyperbolic tangent V1=16404, a=151.8, b=133.2
Parabolic w=8.929x106, e=25140
Asymptotic slowness S0=50.28, Sm=16, q=4162
Constant V0=12780
Even when real time-depth data are used, it is unlikely that the best fit parameter values will
vary from the values in the tables by more than a factor of 10, although this is by no means
guaranteed. However, these values should normally provide a good starting point for any
optimization.
When Instantaneous Velocity Decreases (“Negative K”)

Given the question - How do I correctly model the data when the velocity log shows the
instantaneous velocity to be decreasing downwards at each well location.?
Here is the Answer - There are two common situations where the instantaneous velocity
in a given unit decreases downwards. The first situation is where the unit encompasses

Generate Dialog
two intervals, the top one having a higher velocity than the lower one. Ideally, one should
then sub-divide the unit into two units. This is not always welcome news because it
means that one would need to identify the corresponding seismic horizon separating the
two units. The second situation is where the instantaneous velocity is continuously
decreasing downwards at each location. Clearly, in such a case, the unit cannot and
should not be split into sub-units. Almost invariably, in such cases, while the
instantaneous velocity is decreasing downwards at each location, the individual velocity
components increase in value with depth when followed regionally. Hence, as the unit is
followed from a shallow location to a deeper location, the individual components increase
in value and the interval velocity has likewise increased with depth.
There are three alternative ways to model the unit when the gradient is negative, given
below in order of preference (i.e. to produce the best velocity model):
(i) Have a small tolerance limit (e.g. 1ms solution trough) for all locations. Fix k at an
appropriate negative value and produce a map of V0 over the area, guided by
variations in the depth of the unit, (depth of the base of the unit that immediately
overlies it).
(ii) Revert to an interval velocity model, again guided by variations in the depth of the
unit.
(iii) Accept the regional V0, k combination on the positive side of k. This is the most
convenient alternative but is likely to give large residuals. These residuals would
again follow the depth to the top of the unit (in general) and can therefore be removed
accordingly.
Recommended First Pass Parameter selection for Speedy results

Some of the requested parameters to generate can take a ‘long’ time to generate on a large
data set (for example when each individual point on a curve for each well needs to be
generated); possibly 20 minutes or so although obviously this is entirely dependent on the
data you have and the qualities of the PC you are running it on.
It is therefore recommended that if you are using a large data set that you do not select ‘Yes’
to generate all the given parameters in your first pass.
Note: The Green, Amber, Red Symbols on the General Generate property grid
are there to aid you in this by setting the inputs to the Minimum (green), Medium
(amber) and Maximum set of values that can be generated. Generating a Green set
of values will generate the quickest values, the Red set will generate more types of
values and thus take longer to complete.
Standardly you would define a rough estimate of the Parameter Space first to give a range of
V0’s and K’s to examine. This would then be changed and the real area of interest zoomed
into when it becomes apparent from the initial run. Once you have defined this real area of
interest you may then request further parameters to generate since the area of which it has to
calculate is smaller.

Generate Dialog
Dependency
Recommen
Parameter on any other Recommen Recommend
Display in d
to parameter Speed d on third
VelPAK on second
Generate being on first pass pass
pass
generated
Well Grid Independent Fast Yes Yes

Fit
Well Grid Independent Fast Yes Yes

Residual
Well Line Independent Slow Yes Yes Yes

Fit
Well Line Independent Fast Yes Yes Yes

Residual
Well Point Independent Fast Yes

Fit
Well Point Dependent Fast Yes

Residual on Well Line
Residual
Layer Grid Dependent Fast Yes Yes

fit on
Layer Grid Dependent Fast Yes Yes

Residual on Well Grid
Fit
Layer Line Independent Very Yes

Fit Slow
Layer Line Independent Very Yes

Residual Slow
Layer Point Independent Very Yes

Fit Slow
Layer Point Dependent Very Yes

Residual on Layer Slow
Line
Residual

Generate Dialog
Generate Dialog - General Tab
option.
Note: Remember that you need to set up the depth conversion method (but no input
parameters) you wish to use on the layer from the Surface module depth conversion
property grid set-up before generation of the Optimize values can occur.
Create Data Grid Tool -

The square boxed ‘Create Data Grid Tool’ at the top of the General tab is there for you to
produce the information within the Data tab. A useful feature of this is that you can update the
Data tab to reflect changes you have made to the Optimize window (for example making a
particular well inactive) without having to re-generate the whole optimize window.
Green, Amber, Red Symbols

Used to set up the Minimum (green), Medium (amber) and Maximum set of values that can
be generated, according to the set of values listed below on the Property grid. Generating a
Green set of values will generate the quickest values, the Red set will generate more types of
values and thus take longer to complete.
Note: Setting these values will automatically change the Display of the optimize window to
the ‘best’ display given the values generated.
Option
Filter - Normal/Fit/ Residual - in Normal mode filtering will take place according to how
the wells have been de-selected in the Data tab; any de-selected wells will not be used. If
however only the Fit or the Residual of a well has been de-selected then using this Filter
will allow only one or the other’s values to be displayed in the Optimize window. This
option is intrinsically linked to the Curve module and vice versa.

Generate Dialog
Info - Information on the Optimization process will be displayed in the Console window
Residual - How the error per well will be generated either as RMS or an Average.
Samples - The number of curve samples to use. Using 0 means use ALL curves.
Well
All values are re-generated if a well is selected or de-selected. If you have set some
values in the Generate General tab to ‘No’ then the original values of these will be wiped
and replaced with blanks. (It will not keep the values as derived from an earlier
generation).
Go Here for full details of the values that can be calculated.
Well_Grid_Fit - Given the depth conversion parameters entered, a grid is generated for
each well in the model. The generation takes each pair of V0 and K values and works out
the depth value, comparing it to the time-depth curve data for that layer, for that well. The
value plotted is the difference between these two values.
Well_Grid_Residual - Given the seismic time at the top and base of layer, the last depth
(if a buried layer) and the depth conversion formula set up, the generation calculates the
error using the V0 and K of that point. In essence it does exactly what the Tie option
within VelPAK does.
Well_Line_Fit - This method scans on the Y axis (k) and gives the best fit of the solution
trough for the V0. The Y axis is divided up into 10 sample to provide the fixed k values
across the Optimize area. Taking the seed value the calculations along the sample lines
begin at a point somewhere in the middle of the optimize area. When each point is
generated the routine checks to see if that value is lower than the point on either side of it
along the line. Thus the lowest value point along the line is calculated and it is through
this point that the line fit passes.
Well_Line_Residual - Using the given depth conversion formula, a line per well, in the
parameter space (close to the zero contour of the Grid residual) marking the line down
which the error would be zero.
Well_Point_Fit - Using the depth conversion formula, a point per well, in the parameter
space, this is the best fit given the values that produced the Line Fit and the Y (k) value.
Naturally this should always fall on the Line Fit at the very bottom of the contour trough.
Well_Point_Residual - Using the depth conversion formula, a point per well, in the
parameter space, this will be the point that falls on the Well Line residual line, closest to
the Fit point.
Layer
Layer_Line_Fit - Using the depth conversion formula, a line per layer, an average of
all the Line Fits generated for the Selected wells in the model.
Layer_Line_Residual - Using the depth conversion formula, a line per layer, an
average of all the Line Residuals generated for the Selected wells in the model.
Layer_Point_Fit - Using the depth conversion formula, the average of all currently
selected wells, representing the best possible layer surface fit to the time-depth data.
Layer_Point_Residual - Using the depth conversion formula, a point per layer, in the
parameter space, representing the best possible layer surface fit calculated by
searching down the layer line residual.
Layer_Grid_Fit - An average of all the currently selected well values calculated for
each grid node for all the wells in the model.
Layer_Grid_Residual - The average of all currently selected wells in the parameter
space, representing all possible residual values for the time-depth data.

Generate Dialog
Generate Dialog - Parameters Tab
Input
Bank 01
Input
Bank 02
option.
Note: Normally just the X-axis value and the Y-axis Values are set here in the Parameter_01
and Parameter_02 banks; however some depth conversion definitions have a third
and fourth parameter banks to set up. Go Here for details of FIXING a parameter in a
three (or more) parameter function.
Get AOI Parameters Tool -

The square boxed ‘Get AOI Parameters’ Tool at the top of the Parameters tab is there for
you to change the min/max display of your 2D Parameter Space to the area you are
currently seeing on the display. Pressing this change the min/max currently set on this
Parameters tab to the extremes of the display as currently seen on the display.
Calculate AOI Parameters Tool -

The square boxed ‘Calculate AOI Parameters’ Tool at the top of the Parameters tab will
input default values worked out against the maximum value of the vertical apparent
interval velocity. Use this button to set up your original AOI on first generation of the
Optimize window.
Input Banks -
This is where you set up the limits and ranges for each parameter on the display. Go Here
for a advice and discussion about the velocity function parameter ranges.
Each parameter in the method has a minimum, maximum and number of steps, which
control where the program looks.
Set-up of the Inputs can essentially be thought of as similar to producing a grid consisting
of grid nodes; you define the XY minimum and maximum, and the number of divisions

Generate Dialog
you wish your graph to be divided up into and the program will work out the values for
you.
Input v0 - standardly the first input would be the V0 parameter; the parameter along the
X-axis.
01_ Increment - The number of divisions between your Min/Max range you wish to act
on. Standardly this value is set to 50 (or 51 to give an even count for the Min/Max of the
grid).
01_Maximum - (note MAXIMUM is set before MINIMUM) - the maximum value of the
initial Optimize display.
01_Minimum - (note MINIMUM is set before MAXIMUM) - the minimum value of the
Note: Once generated the Minimum and Maximum can be refined either by editing this
value here or by using the standard VelPAK Zoom facility on the display.
Input k - standardly the second input would be the k parameter; the parameter along the
Y-axis.
02_Maximum - (note MAXIMUM is set before MINIMUM) - the maximum value of the
02_Minimum - (note MINIMUM is set before MAXIMUM) - the minimum value of the
Note: Once generated the Minimum and Maximum can be refined either by editing this
value here or by using the standard VelPAK.
Further Banks of Inputs; 03_Increment etc. and beyond - Some formulae expect more
inputs than just the two standard V0 an k. An example of a formulae that requires more
than two parameters to be set up is the “Hyperbolic Tangent Function”. (Go Here for
details of this formulae). In this case the other Input Banks here would be set up in a
similar way to the Input banks 01 and 02 detailed above.

Generate Dialog
Generate Dialog - Randomise Tab
The mechanism which allows you to do a random hit in the parameter space selected using
the parameter constraints given.

XYZ Dialog
XYZ Dialog
The XYZ Property grid is used to output XYZ values generated on your display from your
Optimize set-up parameters to be used within other parts of VelPAK. For example the
generation of a ‘V0 to tie’ error grid to be added to your Depth Conversion method.

option.
Option
Info - Diagnostic Information on the optimization process will be displayed within the
console [for advanced use only].
Method - Method to use for residual calculation. Error, FixX or FixY. Go Here for
explanation/discussion of this.
Minimise - Residual/ Fit
Default is Residual which minimises the residual - if one value was fixed (e.g. fix K) then
V0 was calculated to tie the well depth.
Changing this to ‘Fit’ outputs the best fit value. Graphically, the 'Fit' option will output the
intersection with the 'Fit Lines' and not the 'Residual Lines', that is, the fit error is
minimised. Go to discussion and diagrams under Fix_Y for further information about
these.

XYZ Dialog
Type - The ‘Fix X or Fix Y’ values will use either the User, Residual or Fit point displayed
as the value at which to fix the axis.
Residual
Output
The slots within the Model Tree where the value generated will be placed.
Errors - Output slot for Errors XYZs (Fixed X and Y).
X_Axis, Y_Axis - Output slots for the Gradient and Intercept.
All these values have a specialized default slots within the Model Tree where they will go
if you do not select any other slot. For example, the ‘Depth Conversion Gradient’ slot is
one of the ‘Expanded Slots’ within the Model Tree named just for this output.
Note: All three output Model Tree slots will be filled regardless of which of the three you
have selected. This is to avoid confusion with over-writing; all slots will always store
the values generated for the last XYZ run. The table below shows what values will be
placed in the slots according to what method you have selected.

XYZ Dialog
Output Y-axis slot Output X-axis slot

Method Output Error Slot
(Gradient) (Intercept)
Fix X All values assigned Variable ‘k’ values Constant

to zero (or other gradient values
values)
Fix Y All values assigned Constant Variable ‘V0’ values

to zero values (or other intercept
values)
Error Variable ‘residual’ Constant Constant

values values values
Method - Error, Fix_X, Fix_Y

Error
Fixed X and Fixed Y - gives the best V0 and K pair and works out the residual for it would be.
An advanced Optimization option!
Fix_Y
Standardly it is the Fix_Y option here that would be used (output) most since this would be
the intercept, usually V0, value given a fixed k for your selected Type (User, Fit or Residual).

XYZ Dialog

XYZ Dialog
Fix_X
Since rocks tend to have a fixed gradient the Fixed_X option would not usually be used.
However, should it be used then it is of the same principle as Fix_Y but with the fixed value
being the X axis.

XYZ Dialog

VelPAK Workflow
Introduction
Many of the VelPAK processes can be turned into Workflows which step-by-step can lay out
the actions required to complete a particular task. Tasks that are cumbersome and/or
repetitive can be completed with a click of the mouse in WorkFlows. They guide you through
each process step-by-step, leaving very little room for error and confusion.
You can load workflows for each depth conversion type and expert knowledge can be
incorporated and workflows extended. This makes workflows ideal for audit trail and Quality
Assurance.
You can design your own workflow and save them; they can be specific to a company or a
province. Workflows can also be used for tutorials, training, testing and demonstration.
VelPAK is designed to run from XML.
It is sometimes not practical or possible to automate all activities within VelPAK, in which
case Pause options are introduced allowing you the input required before continuing.

Pre-defined Workflows
There are a number of ready-written generic workflows provided with the VelPAK software
designed to run VelPAK’s main depth conversion processes with minimal effort from the user.
Pre-defined Workflows are nested and usually involve many ‘sub-routine’ of processes.
Note: It is recommended that the user become familiar with the workings and concepts of
the Ready Made Workflows as an introduction to the Workflows processes within
VelPAK
Go Here for a discussion and list of Pre-defined workflows.

• Users unfamiliar with the workflow system should go to the ‘Start Here’ directory found in
the Workflows fly-out. This will lead you through creation of your own tailor-made
workflow. Go Here for assistance using this start workflow.
• Older, ‘classic’ Workflows are still active in later versions even though the workflow
system has been updated. They can be found in the ‘Classic Workflows’ directory from
the Workflow fly-out.
• Pre-defined workflows can be used with the simplest user intervention to set them up for
each or any Event Horizon.
• There is a bank of Workflows to select from which can be used to run the major VelPAK
processes and a bank of Components which are drawn in to each workflow which contain
repetitive routines of work such as initializing the grids and displaying particular map
types.
• The user can edit the workflows as they wish. These then default to being saved in the
local project directory. The system workflows will not be written over.
• If there is a locally stored workflow or node stored in the project directory this will always
be the one used in the workflow - not the system parameter set. This allows the user to
change displays and parameters as they wish solely for the project they are in while
retaining the main system’s integrity.
The Nested Workflows

All processes within VelPAK have a Node assigned to them within the workflow module. Most
processes within VelPAK are suitable to run in a workflow - although some would not suitable,
for example Profile Snapping of a geologically-complex profile. Each process that is suitable
has a Node assigned to it in the workflow area. In the workflow area these can be joined
together with a start and an end to produce a workflow.

Getting workflows to run at node level is a reasonably complex thing to do. For example to
display a curve you would need:
• one node to clear the graph canvas,
• one node to set up which curve to show,
• one node to set the display correctly (i.e. labels).
Fortunately workflows have already been created within the Workflow area containing the
correctly assembled nodes to run a certain task. These are known as Component
Workflows.
A depth conversion process workflow for one event would be made up of a number of
component workflows. For example:
• Selecting the depth conversion method
• Possibly extracting XYZ values from stored stacking velocities, for example
• Running the depth conversion
• Gridding the results.
• Displaying a contoured map
• Running the whole depth conversion process with an Error correction.
Again, the correct order to get all this achieved is set up in the Event Workflows.
Once the event workflow has been selected, this is put into a Master Workflow where the
event is selected and the process run for the whole project.
Unless you are an advanced user it is unlikely you will need to use anything other than a
Master Workflow to set your depth conversion running.
Within the component and Event workflows the workflows will pause to ask relevant
questions allowing the user to decide the flow. For example - what gridding method you want
to use or what contour level you want the map to be displayed at.
The Nested Workflow Hierarchy

A user would tend to start with the ‘Start Here’ Simple, Master Workflow:

Start
Start Here ‘Master’ Event 1
Workflow Workflow
Select the Simple Workflow from the ‘Start Here’ directory Event 2
in the Workflows property grid fly-out and following the
instructions select the Event Workflows you require for Mapping
Workflow
each Event in your project.
End
Start
Event Depth
Workflow Pause
Event independent pre-written workflows for a particular
VelPAK process built up of component workflows. Pause Gridding
nodes will stop the flow and prompt the user for relevant
Mapping
information if necessary (with a “Don’t Ask Me Again”
check box). Error
End
Start
Component Node
Workflow Pause
A number of Nodes with a Start and End pre-written for
certain repetitive tasks. Built in Pause nodes will stop the Node
flow and prompt the user for relevant information if
Node
necessary (with a “Don’t Ask Me Again” check box).
A real example of expanding a workflow like this can be Node
seen here.
End
Node
The Node is the link to the property grid fly outs in the main
VelPAK program - change the values in the fly out from the
Model Tab of the workflow - the changed values will then be
saved under this node.

The ‘Start Here’ Simple Workflow

A starting workflow has been created allowing the user to build a depth conversion workflow
that works with very little background knowledge of VelPAK or its workflow system.
The workflow will guide you through building your own complex workflow.
Guide to setting up the Simple ‘Master’ Workflow

1. Find the workflow under the Start Here workflow sub-directory (the number ‘1’ is only
there to keep this listed alpha-numerically at the top of the list if users add their own
workflows.)
2. Drag the workflow into the canvas area - the workflow will automatically expand.
The Simple Workflow is set up to run a process for two events. More events can be added
if necessary.
All Workflows must have a Start Node and an ‘Initialize All’ Node. There then follows a
workflow which sets the event to ‘1’.
The default workflow set for event 1 is ‘Curve IntervalVelocity v DepthToMiddle Multi.xml’
but you can change this to any methods within the Depth part of the Workflows Property
grid fly-out:
3. Click the blue workflow ‘Curve IntervalVelocity v DepthToMiddle Multi.xml’ so that it
becomes highlighted. Press delete to clear it. The workflow will delete along with arrows
joining it from Event1 and to Event 2.
4. Open the Depth directory on the Workflow Property Grid fly-out and select the depth
conversion method you wish to use.
5. Drag this method into the canvas and join it up from the Event 1 node and to the Event 2.
How to Join Nodes
Holding your cursor over the Event 1 node will give you a red dot where the programme is

anticipating that you wish to join this node to another node in the flow. The cursor
changes to the standard ‘finger pointer’.
Select the red dot on the Start and drag the resulting arrow to the Event workflow node.
This should be fairly easy; the arrow line is trying to join with a node at all times so you
should see it snap to the node without having to be too precise.
6. If you have an Event 2 in the project to depth convert you will need to repeat this process
under the Event 2 selector node.
To add more events to the workflow:
7. In the Workflows property grid fly-out open up the Event directory/tree. You will see all the
Event workflows listed.
8. Drag the workflow for the Event you require into the canvas.
9. You will probably need to delete arrows to fit the event workflow and subsequent depth
event workflow into the Master Workflow.
10. Make sure the End node is attached to the final depth conversion method you have put in.
11. Save your workflow! This will default to be saved within the workflow sub-directory of your
project. This is not the ‘User Workflows’ seen in the Workflows property grid fly-out which
is part of the VelPAK system.
Example Running a Depth Workflow

Looking at the Event Workflow in detail
As discussed in the Nested Workflows section, the ‘Optimise V0kz Residual Error Multi.xml’
master workflow is a top-level workflow which contains nodes, control nodes and component
workflows designed to run the process correctly.
Double-clicking on this ‘Optimise V0kz Residual Error Multi.xml’ workflow on the canvas will
expand out this workflow in the Scratch 1 tab:

Control Node
Node
Node
Control Node
Node
Component Workflow
Control Node
Control Node
Node
Node Node
Component Component The ‘Optimise V0kz Residual Error

Workflow Workflow Multi.xml’ workflow is made up of
Node nodes, control nodes and
Node
Component Workflows drawn from
the Component area of the Workflow
property grid.
Double-clicking on the ‘Optimise Main Residual.xml’ component workflow within this workflow
will expand out the workflow in Scratch 2 tab:

Control Nodes
Node
Node
Node
Node
Component
Workflow
Node
Control Nodes The ‘Optimise Main Residual.xml’ workflow

is made up of even more nodes, control
nodes and Component Workflows drawn
from the Component area of the Workflow
property grid.
Under this expanded workflow there are more nodes, control nodes and component
workflows. Double-clicking on the ‘Optimise Parameter Choice.xml’ component workflow will
open it up in the Scratch 3 tab, where the Pause nodes that ask the questions the user will
have to answer to proceed through in the main run of the Master Workflow are actually
stored:

Running the Master Workflow

Working through what you will see when you run the Master workflow on some valid data. (In
this case the example is using data from the Southern North Sea.)
Running the Master Workflow for the first time with your selected depth conversion method
will result in many questions coming up, as shown below. Subsequent runs will not ask these
questions if you check the ‘Do not ask me again’ check box on each pause. Stored workflow
information is saved in the local project area - in the ‘cache’ of the project. The cache would
need to be cleared to get the questions asked again by using the ‘Clear Run Cache’ cross at
the top of the workflow window.
In this example the Event Workflow ‘Optimise V0kz Residual Error Multi.xml’ is the selected
depth method.
Note: To be able to see what is going on within VelPAK while you run this workflow it is
recommended that you detach the workflow tab and have it away from the main
VelPAK window.
1. Pressing the Start button, the program will move through the workflow - (the nodes turn
red when they are in action). The process moves through the Initialise and Event nodes
and pauses on the Depth Event workflow. The Pause comes up asking the question
which you can see above is actually sitting in the workflow ‘Optimise Parameter
Choice.xml’ which is nested within the workflow ‘Optimise Main Residual.xml’ which is
nested within the Event Workflow ‘Optimise V0kz Residual Error Multi.xml’ chosen for this
depth conversion.

This is a ‘Branch’ - the decision you choose will change which branch the flow goes down
- as seen in the screenshot above.
2. Say Yes to the question and press OK. Almost immediately the next pause will come up;
this is also shown in the screenshot above as the text in the left branch pause.
The program has attempted to work out the Optimize Ranges for this model. To the right
you can see the model set up; if these look acceptable press ‘OK’.
Note: The Do not ask again check box- check this if you do not want this pause to pop up
next time you run the workflow on this project.
3. The next pause to come up is another Branch to select the gridding method you want to
use for the error.

Select Global as your method. If you were to answer Kriging a number of very different
pause-questions would need to be answered.
4. There then follows a number of branches and pauses as the program displays the error
grids depth maps, velocity maps etc.
Although on the Master Workflow the Optimise V0kz Residual Error Multi.xml is still
showing red showing it is this that is still being used, the program has moved on from the
nested workflows discussed above and is now accessing the workflow component
‘Display Maps Multi.xml which is nested under the ‘Error Multi.xml’ further on in the flow of
the ‘Optimise V0kz Residual Error Multi.xml’.

Where Workflows are Stored and Saved

Pre-defined System workflows supplied with VelPAK are stored in the ‘workflows’ directory
of the VelPAK system area and viewed under the workflow property grid fly-out of the
workflows module. These should not be over-written, however new workflows and/or
directory of workflows can be added to this area as the user requires: these will be seen
within the workflow directory structure of the workflow tab.
Project workflows - For Primary workflows pertaining to the project as a whole, these can
be stored in the project workflow area and accessed via the ‘Open Workflow’ icon on the
workflow page. New workflows (or amended pre-defined workflows) can be saved in the
project directory using the standard ‘Save Workflow’ icon on the workflow screen which will
open automatically in the project workflow area.
Edited ‘Cached’ workflows - Any component, users or pre-defined workflows that are
loaded into the project and edited in some way are automatically stored in the ‘cache’ of the
project which are sub-directories of the project’s workflow area, stored per event in the form:
C:\Software\VelPAK\galleon\workflow\01
C:\Software\VelPAK\galleon\workflow\02
C:\Software\VelPAK\galleon\workflow\03 ...etc
This local variation of the supplied workflows will be named the same as the supplied
workflows and will be the default workflow used in all workflow runs from that project. In

order for the supplied System workflow of the same name to be used again the cached
workflow will need to be cleared (using the Clear Run Cache clear option from the top line of
the Workflow screen) or renamed.
Note: A User can also store a workflow anywhere on the system and load it as required
using the standard File Selector.

Parts of the Workflow Window

Workflow/Scratch Canvases
Workflow
The main area where you can see your workflow; set it up and run it.
Process Nodes building bricks are dragged across to this window and set up in the order the
workflow is to process them.
The size of the workflow can be changed using the Tool bar options at the top of the Workflow
window.
Scratch1,2,3
Three areas that can be used to set up rough preliminary workflows or parts of a workflow.
The scratch areas work in exactly the same way as the main View area; data can be saved,
run, edited etc.
Note: Saving your workflow will only save either the Scratch window or the Workflow
window that is currently on display. If you wish to save all the windows you will need to
save into four separately named files.
If you are looking at a component workflow and you wish to expand it then double-clicking on
it will expand the workflow in the next tab. However, note that a workflow expanded when in
the final Scratch area ‘Scratch 3’ will be expanded within that tab.

Workflow Expands into next Scratch area
Except for
Scratch Area 3
which will
expand a
workflow
into itself.
Workflows and Scratch areas can be brought out from their default tabbed display and all
presented in the workflow module window as single panels, as shown below.

Top Toolbar
New Open Save Set Up Preview Print

Workflow Print
Previous Next Model Run Pause Stop Ignore Watch Clear

Event Event Realization Pause Sublevel Run
Selector Nodes Execution Cache
Edit Undo Redo Zoom Zoom Size Zoom

Cut Copy Paste Delete Select In Out to Fit Normal
All
Align Same Same Same Hide Allow Allow

Left Middle Right Top Center Bottom Width Height Size Arrows Resize Edit
New Workflow - New will clear the View window. Make sure you have saved your
previous workflows before pressing New (Note that Undo will restore it if cleared in error).

Open Workflow -Will bring up the standard file selectors to open your workflow.
Workflows always have the extension ‘.xml’.
Note: The name of the default ‘.xml’ workflow file is stored within the Properties of the model
for reference purposes.
Save Workflow - Will bring up the standard file selectors to save your workflow.
Workflows always have the extension ‘.xml’. If the file name exists already and alert with
come up for clarification of the action.
Note: Saving your workflow will only save either your Scratch or your View window in one
saved file depending on which of the two tabs is on display. If you wish to save both
you will need to save into two files.
Print Set Up/ Preview/ Print - Print information icons.

Previous/Next Event - move to the previous or next event.
Model Realization Selector - Used in multiple realization mode. This allows the user to
analyze a particular run from the multiple of runs achieved. Due to the way randomization
works within multiple realization, setting a number will cause the program to have to
process the run from Model 0 to the model number entered here and then stop, it will not
simply run the Model number entered. Note it does not have to run all the models up to
the number entered but it will take a moment or two to reach the selected Model number.
The exact model relating to the P10, P50 or P90 can also be selected.
Run - Will run the workflow.
Pause -
Turning Pause ‘ON’ and then pressing Run will make the workflow pause after every
process node for clarification. This can be useful when setting workflow up. (You can also
enter a Pause node from the Node property grid into the flow for a permanent ‘hard’
pause in the run if required.)
If pressed during a workflow in action it will cause the workflow to pause at the next
opportunity.
Stop - Stops execution of the workflow.
Ignore Pause Nodes - Allows the user to ignore pause modes placed in the workflow.

Watch Sublevel Execution - Will expand the sub-level workflows while running the
workflow. A useful tool to see what is going on during the workflow. Each component and
node will be highlighted as the workflow runs.
Clear Run Cache - Clears any locally stored workflows that have been created or
modified and stored in the ‘cache’ directory under the project you are working in (under
the event they have been created for). The option gives you the choice of clearing the
cache from all events or just the current event.
Edit - Cut, Copy, Paste, Delete, Select All - Allows the Edit of all elements of the Node.
To select the item to edit click on it with the mouse; alternatively use the Select All to
highlight all items in the workflow. Using the mouse button to drag over and area will allow
selection of those elements within the drag window. Use the Control or Shift Key to select
specific items.
Note: For editing of text use Allow Edit.
Undo - To Undo an action. Clicking more than once will undo the previous actions too.
The undo pertains to the set up of the workflow display and does not work on internal
changes made to the Node.
Redo - Will redo an action you previously undid. Continual pressing of this option will redo
all previous actions you undid until you have reached the present state at which time
pressing it will do nothing further.
Zoom In, Out, Size to Fit, Normal - Zoom In and Out will do what it states; Size to Fit will
take the whole workflow display and fit it in the View window at the size the window is.
Normal will take it back to the default size of text and nodes boxes.
Align Left, Middle, Right, Top, Center, Bottom - Allows you to align the selected node
boxes amongst themselves in the alignment mode selected. Joining flow lines will not
align, but they will of course move according to where their attached nodes have moved
to.
Same Width, Height, Size - Select a start node and one or more further nodes to turn the
same width, height or overall size as the start node. The start node will be selected with a
green highlight, other nodes will be light blue.
Hide Arrows -

Turning this ON will hide the arrows of the joining flow lines.
Allow Resize -
Turning this ON will allow the node boxes to be resized.
Allow Edit -
Turning this ON will allow the text in the node boxes to be edited. You can enter as much
text in the node box as required. The box will resize if there is a large amount of text
within the box, regardless of whether the ‘Allow Resize’ option is turned on or off.
Right Hand Property Grids
Right Hand Side Tabs
Workflows Property Grid

All the Pre-defined Workflows supplied with VelPAK are set out within this tab in a directory
structure that groups similar workflows together.
All the Component and Event workflows are stored under here.
These workflows are stored within the VelPAK system directories.

Workflow ‘.xml’s can be created or modified and stored in the User sub directory within in this
area or alternatively the user can add a directory of company workflows, for example, to this
area which will be instantly viewable within the Workflow Property grid, as shown below.

Add a directory in Windows Explorer Will show in Workflow

Property Grid
Note: Care should be taken not to clutter this area up since it is the system area accessible
by all users and all projects.
These workflows are being continually updated as well as added to by the user, so the
Workflow Property Grid may not look exactly as it does above, however here is a run through
of the main top level directories.
When a workflow node/process/component etc. is dragged onto the canvas you will see that
they appear different colors or react differently. This is so you can tell what type of node/
process/component it is within the workflow.
For full details of all the types of workflows available from within the Workflows Property Grid
fly-out Go Here.

Nodes Property Grid
The Nodes tab holds building blocks for each individual VelPAK process that can be added to
the workflow.
Drag the nodes from the Nodes Property Grid into the View window to build up your workflow.
Set up of the nodes are done via the Model tab.
Within the Nodes Property Grid you will see Workflow Control nodes, followed by Selector
nodes followed by Module nodes:
Workflow Control Nodes - These are nodes that are used within the running of the
workflows; the Start, End and Pause nodes and Comment/Balloon options, the Execute,
Branch, Loop and Surface nodes. They tend to control the flow of the workflow process
(although not always).

Note: Further description of what each of the Workflow Control Nodes does along with
examples can found here.
Comment / Balloon allow you to add comments to the workflow. Use Allow Edit from the
top toolbar to edit the comments.
Start /End - Start the flow with the Start node and end the flow with the End node.
Pause - If you wish to pause the workflow you can add a Pause node into the flow. An
alert will come up and the workflow will only start again once you have selected ‘Y’ to start
it running again. (You can also run the whole workflow in Pause mode from the toolbar at
the top of the workflow window. This would allow you to pause after each node but not
have to edit the workflow to have Pause nodes within it). The Pause that comes up will
have two areas on display; to the left it shows you the Pause comment (if any) and the
ability to turn the Pause off, to the right shows you the set-up of the property grid of the
node that is following the pause. The user can then use this pause in the workflow to edit
this property grid - for example the contour increment.

This is described more thoroughly in the Workflow Control Nodes section here.
Execute - is used when you are working with pre-defined and nested workflows. It is the
name of the ‘sub-routine’ nested workflow that is to be run within another top-level
workflow.
For example, you would make up a workflow you were happy with, save and name it
‘Example1.xml’. When you want to run this workflow within another workflow you would
bring in the Execute node and rename its display name from ‘Execute’ to ‘Example1.xml’.
When you are running this top level workflow and it reaches the Execute node named
‘Example1.xml’ the workflow routine will go and run all the processes stored within the
workflow ‘Example1.xml’ before returning back to the top-level workflow.
Note: All the pre-defined workflows already stored within VelPAK have their name.xml
shown in the Workflows property grid. These nodes are all Execute nodes that
have been re-named to the name of the processes they will do.
Branch - Allows the user to branch the workflow to have a choice of up to three
different paths to take. There is also the option to ignore the branch option question
and always select a particular branch if required - set up in the Parameters tab. This is
described more thoroughly - with examples - in the Workflow Control Nodes section,
here.
Loop - Allows the user to loop the workflow process for as many times as specified in
the Parameters tab. Used in re-iteration processes or for creating a ‘movie’ of a
display feature that is changing as the program loops. The number of iterations to be
used is set up in the Parameters tab. This is described more thoroughly - with
examples - in the Workflow Control Nodes section, here.
Pin - A ‘cosmetic’ node, which can be used to make the workflow look neater - as its
name suggests it can pin the flow lines anywhere within the display. A Pin node can
have up to three input and one output flow lines with any of the four edge connectors
being used for the output flow arrow; thus it can bring together three branches back

into one flow line to continue with the workflow with a neater looking display. This is
here.
Check - Acts to check whether the run you are doing is part of a multiple realization
loop or a single run. It is a three pronged automatic conditional branch executable
dependable on the model number of the run it is executing. If it is a single run then
there is no model number involved and the check button will run through the workflow
in standard fashion. If a model number is detected (be that zero for the first run or a
positive value for subsequent runs) it will go through the run and loop back to run
again in multiple realization mode. This is described more thoroughly - with examples
- in the Workflow Control Nodes section, here.
Seed - used in multiple realizations; this resets the seed to get the same random
number starting point for each multiple flow. Otherwise you would not be able to
recreate the exact same run if the run started from a different random number every
time. This is described more thoroughly - with examples - in the Workflow Control
Nodes section, here.
Layout - Loads the currently saved layout. This is described more thoroughly - with
examples - in the Workflow Control Nodes section, here.
Image - will record the current image seen on the screen as ‘*.png’ file and store it in
the model directory under an ‘image’ directory. Under the image directory they will be
stored in directories labelled per event. The name of the image captured will be the
same as the name of the image node (which therefore would default to image.png).
This is described more thoroughly - with examples - in the Workflow Control Nodes
section, here.
Repaint - Refreshes the graphics during a run or turns them on or off. This is
here.
Selector Nodes - Allows you to select the various data slots you want to be currently
active in the workflow that relate to the Surface&Slot and Preferences selectors within
VelPAK.
In a standard workflow you would find that you would put one or both the Selector
process nodes in as one of the first nodes in a workflow since they allows you to select
the various data slots and surfaces you want to be currently active in the workflow. It is
also quite likely you would add one or both of the Selector process nodes many times
within a work flow as you change event horizon or selected surface. For full details of the
Selector Go Here.
Modules - All VelPAK property grids are laid out under the respective Module names.
Dragging the relevant node into the workflow or scratch canvas areas will allow you to set
up the entries within the grid via the Model tab.

Nodes Edit Menu

When a node is placed on the canvas, clicking the right hand mouse button will bring up a
menu for editing that node.
Cut/Copy/Paste/Delete - these options do exactly the same as on the top toolbar. They
allow the Edit of all elements of the Node.
Toggle Resize/Edit - will toggle one of the two buttons on the top toolbar to allow resize
or edit of the node. The icons on the top toolbar will go orange when these modes are
on.
Resize will allow the node boxes to be resized.
Edit will allow the text in the node boxes to be edited. You can enter as much text in
the node box as required. The box will resize if there is a large amount of text within
the box, regardless of whether the ‘Allow Resize’ option is turned on or off.
Properties - Will bring up the Parameter Property Grid:

This is exactly the same as the Parameters Property Grid which is discussed here.

Model
The Model Tab will be blank on initial entry in the Workflow module.
Once you have dragged a process node into the View window and double-clicked on the
node the Model Tab will display the details corresponding to the Property Grid for that node.
Note: The Model Tab is showing exactly what is set up in the relevant Property Grid within
VelPAK.
Full details of the different property grids are found in the relevant parts of the VelPAK
manual.

Parameters
The Parameter Tab contains the information stored in the selected node.
Note: This information also comes up from the clicking on a node within the canvas using
the right hand mouse button as discussed here.
Text - This box shows you what text is currently in the selected node. The text can be
changed in this option, or by editing the node on the canvas itself.
Type - Tells you what type of node it is; unless you have renamed the text line above
these will both say the same. However, it is likely that when developing a work flow you
will want to rename them to tell you what the node is in the flow to do - in which case the
Type input here allows you to see what the original name of the node was and therefore
the type of node it is. This is also useful in looking at ready-made workflows.
Color - Changes the color of the selected node and its Text.
Execute - Yes/No - (default yes) - allows you to switch off the execution of the node.
Certain options in VelPAK require setting up of more than one property grid before the
option can be successfully activated; for example the Gridding routines where you would
need to set up items in the ‘Range’ tab as well as the ‘General’ tab before activation. In
this case you would set the first node to set up as ‘Execute - No’ allowing the workflow to
set up that node information but not execute the Gridding generation until the next node
has been set up as required. The second of these nodes in this example would remain
with the default ‘Execute - Yes’ and the gridding would therefore be activated on the
second node.
A node can be seen to be set to ‘No’ at a glance within a workflow when there is a small
red square in the top right corner of the node as seen below.

Execute Node - No Execute Node - Yes
Branch - Choice - Ask, A, B, C - The default set up for the Branch node is ‘Ask’ which
means that when the workflow comes across a Branch node it will ‘Ask’ which branch you
wish to go down. If you set the Branch node to ‘Do not ask me again’ while you select
Branch A, B or C then the option here in the Parameters will become set to A, B or C. The
Branch node will then not ask you which branch you wish to proceed down. The setting
can be changed back to ‘Ask’ here or set to A, B or C before running the workflow so that
it will not pause during the run on the Branch Node.
Ask Yes - Resets the ‘Do not ask again’ option on the branch to be unchecked to force the
branch to ask again.
Loop - How many times the Loop node option is to be run - set to the number of times
you wish it to loop.
Value - What this is depends on what the node is that the Parameters fly out is showing.
For example the Repaint and Check nodes would have a value here of zero or one
depending on whether it was to be ‘on’ or ‘off’. Other nodes would not use this value input
at all. Value details are documented against the relevant inputs in the in the Workflow
Control Nodes section, here.

The Types of Pre-defined Workflows

Workflows Property Grid
All the Pre-defined Workflows supplied with VelPAK are set out within this tab in a directory
structure that groups similar workflows together.
All the Component and Event workflows are stored under here.
These workflows are stored within the VelPAK system directories.

Workflow ‘.xml’s can be created or modified and stored in the User sub directory within in this
area or alternatively the user can add a directory of company workflows, for example, to this
area which will be instantly viewable within the Workflow Property grid, as shown below.
Add a directory in Windows Explorer Will show in Workflow

Property Grid
Note: Care should be taken not to clutter this area up since it is the system area accessible
by all users and all projects.
These workflows are being continually updated as well as added to by the user, so the
Workflow Property Grid may not look exactly as it does above, however here is a run through
of the main top level directories.
When a workflow node/process/component etc. is dragged onto the canvas you will see that
they appear different colors or react differently. This is so you can tell what type of node/
process/component it is within the workflow.

Workflows - Start Here

Beginning workflow and templates that will guide you through building your own complex
workflow. Any workflow in the Examples or Templates subdirectories ‘auto-expand’ when
they arrive in the canvas to aid you to see what processes are going on.
A step-by-step guide of what to use the Start Here workflow is documented here.
xpand
Autoe
Depth
All the depth conversion processes are stored under this area. Note they are blue workflow
processes.
When you have selected the depth conversion process you want to run, you would usually
add this to the Simple workflow found under the Example directory. A step-by-step guide of
what to do is documented here.
A full list of these are described here.
Event
The event sub-directory list simple workflows that will change the event to that numbered.
These are intended to be used as a ‘component’ workflow within a top level workflow to move
to the next event to be processed.

Note that Event workflows are always pink in color.

.
Classic Workflows
Contains classic workflows and component workflows from previous releases.
User Workflows
An area for users to store their own workflows (blank on installation).
Write Your Own Workflows - (Component & Utility Workflows)

Contains Component and Utility workflows.

Components are pre-defined workflows which contain repetitive routines of work such as
initializing the grids and displaying particular map types. They are intended to be nested
within a top level workflow to run required but repetitive routines within it.
Note that component workflows are green in color. Double-clicking on the node will open
up the component workflow in a scratch tab. There may well be further nested workflows
within the this one component.
Utility workflows allow for Grids to be saved externally for use in the Analyse module
Statistics tab.

Writing a Workflow from scratch

It should not be necessary to write a workflow from scratch within VelPAK since there are
workflows and components for all VelPAK routines that require one. However, should you
want to do so here is a short guide to writing a workflow from scratch.
Once you have decided what you wish to achieve from a particular workflow...
1. Detach the Workflow window from the main VelPAK window and preferably make it as
large as you can.
2. Open up the Nodes and Model Tabs and pin them out.
3. Select from the Nodes the process node you want and drag the node across to the View
window.
4. Edit the Model Property Grid to conform to the set up you want.
5. Determine whether the node is to execute when the flow reaches it or is it to be just a set-
up node (default is execute). Change to non-execute in the Parameters tab if required.
6. Repeat steps 3 - 5 for all the process nodes you want to run.
7. Join the nodes with arrows in the order in which you wish them to be run and put a Start
and End box in the appropriate places of the workflow.
8. Save the workflow as an external .xml file.
9. Press Run/Play.
Building Your Workflow

You can build your own workflow from Nodes within the Nodes Property Grid tab or by using
pre-defined Workflow and Component nodes from the Workflows Property Grid. Either way, a
workflow needs to have a Start and an End and joined with arrows.
From the Nodes tab or Workflows tab drag across the Start box and the End box into the
Workflow Canvas.

Pin
Drag
Holding your cursor over the Start node will give you a red dot where the programme is
anticipating that you wish to join this node to another node in the flow. The cursor changes to
the standard ‘finger pointer’.
Select the red dot on the Start and drag the resulting arrow to the End node. This should be
fairly easy; the arrow line is trying to join with a node at all times so you should see it snap to
the End node without having to be too precise.
Once you have started the workflow add various processes between the Start and the End
node. You will need to delete the line joining the Start and End nodes as shown above, by
clicking on it and deleting using the right hand mouse button, the red delete cross on the top
toolbar or the keyboard delete key.

Double clicking on the node will allow you to activate the node without necessarily having to
join the nodes up to make a flow until the end when you are happy you have produced the
workflow you want.
Clicking with the right hand mouse button on a node in the canvas will bring up a menu with
certain edit options for the node and it’s properties allowing you to change them as you wish.

Workflow Control Nodes

A detailed discussion, with examples, on what the Workflow Control Nodes do.
Pause
If you wish to pause the workflow you can add a Pause node into the flow. An alert will come
up and the workflow will only start again once you have selected ‘Y’ to start it running again.
You can also run the whole workflow in Pause mode from the toolbar at the top of the
workflow window. This would allow you to pause after each node but not have to edit the
workflow to have Pause nodes within it.
The Advanced use of the Pause button is that it allows you to see and if necessary edit the
node that follows the pause. The user can then use this pause in the workflow to edit this
property grid - for example the contour increment.
The Pause displays the Property Grid that follows the

Pause allowing the user to change any value within it -
for example the Contour Interval
Note: Any changes you make to the Property Grid linked to the pause node will be
automatically saved as an edited ‘cached’ copy of this workflow. This locally stored
workflow will be the workflow used by default when called in to the program again.

Execute
Execute - is used when you are working with pre-defined and nested workflows. It is the
name of the ‘sub-routine’ nested workflow that is to be run within another top-level workflow.
For example, you would make up a workflow you were happy with, save and name it
‘Example1.xml’. When you want to run this workflow within another workflow you would bring
in the Execute node and rename its display name from ‘Execute’ to ‘Example1.xml’. When
you are running this top level workflow and it reaches the Execute node named
‘Example1.xml’ the workflow routine will go and run all the processes stored within the
workflow ‘Example1.xml’ before returning back to the top-level workflow.
Note: All the pre-defined workflows already stored within VelPAK have their name.xml
shown in the Workflows property grid. These nodes are all Execute nodes that
have been re-named to the name of the processes they will do.
Note: This is not to be confused with the ‘Execute - Yes/No’ option in the Parameters tab.
Go Here for details of this.
Branch
Branch - Allows the user to branch the workflow to have a choice of up to three different
paths to take. A ‘Do not ask again’ check box allows a particular branch to be selected
permanently if required.
The default set up for the Branch node is ‘Ask’ which means that when the workflow comes
across a Branch node it will ‘Ask’ which branch you wish to go down. If you set the Branch
node to ‘Do not ask me again’ while you select Branch A, B or C then the option here in the
Parameters will become set to A, B or C. The Branch node will then not ask you which branch
you wish to proceed down. The setting can be changed back to ‘Ask’ here or set to A, B or C
before running the workflow so that it will not pause during the run on the Branch Node.
Note: The ‘Do not ask again’ option once unchecked can be changed back to ‘Ask’ in the
Parameters tab.
Having made the choice the program can then merge and go back to running the same
nodes.

Branch Node (with Text edited for A, B, C Choices)
Running the Branch Node will Bring

up the ‘Ask’ Alert for the user to
select Choice A, B or C.
Note ‘Do not ask again’ check box.
Selecting ‘Do Not Ask Again’ will

‘hard code’ the Branch to run one
of the three branches - in this
example the middle (bottom) branch.

Building your Branch Node

A branch node can have two or three branches. Setting up the branch node up with a list of
two choices will make it a two branch node, setting a list of three choices will make it a three
branch node.
To make the branch operate you must use a ‘carriage return’ must within the branch text set
up in the appropriate place as shown below:
Carriage Return
Carriage Returns
in between each
branch item will
give you the
correct set-up
No Carriage
Returns will give
you just the one
(incorrect) input
Note: You do not need to precede the choices with a), b) or c) or 1), 2) 3) etc.
For a two choice branch enter only two options.

Entering only
two items
will give only
two branch
options
The branch to the left is always the first choice in the list, the branch to the bottom will always
be the second choice in the list and the branch to the right will always be the third choice in
the list (if used).
Loop
Loop - Allows the user to loop the workflow process for as many times as specified. Used in
re-iteration processes or for creating a ‘movie’ of a display feature that is changing as the
program loops. The number of iterations to be used is set up in the Parameters tab.

Prior Processes
End or further
individual processes
Return Looped Processes
Unlike most other nodes, the loop node can be joined from or to another node on all four
sides of the node; however each of the four join-points are specific in what they do:
Top Join Point - The prior processes in the workflow must be joined to the loop from the
top point
Bottom Join Point - The process to be looped must be joined to the loop node from the
bottom point
Left Join Point - The process must be returned to the loop node for a further iteration at
the left join point
Right Join Point - When all iterations have completed the ‘End’ or further individual
processes must be joined to the Loop node from the Right join point.
Pin
Pin - A ‘cosmetic’ node, which can be used to make the workflow look neater - as its name
suggests it can pin the flow lines anywhere within the display. A Pin node can have up to
three input and one output flow lines with any of the four edge connectors being used for the

output flow arrow; thus it can bring together three branches back into one flow line to
continue with the workflow with a neater looking display.
It is a useful way of adding a comment within the workflow itself rather than adding a
comment to the side. Note that the comment entered in a pin node will not be displayed when
the workflow is running unlike a comment put in a Pause mode.
The same workflow
One with Pins making

the flow neater to the eye
and with comments...
This one does not have

Pins - the flow lines take
any direction they can to
join the nodes up.
Check
Check - Acts to check whether the run you are doing is part of a multiple realization loop or a
single run. It is a three pronged automatic conditional branch executable dependable on the
model number of the run it is executing. If it is a single run then there is no model number

involved and the check button will run through the workflow in standard fashion. If a model
number is detected (be that zero for the first run or a positive value for subsequent runs) it will
go through the run and loop back to run again in multiple realization mode.
Seed
Seed - used in multiple realizations; placing the seed node in a flow as shown below will reset
the seed to get the same random number starting point for each multiple flow. Otherwise you
would not be able to recreate the exact same run if the run started from a different random
number every time.

Use a workflow that has the seed node placed within it in conjunction with the Model
Realisation Selector to move to the model you want to within the run.
Model Realization Selector
Layout
Layout - Loads the currently saved layout.
Image
Image - will record the current image seen on the screen as ‘*.png’ file and store it in the
model directory under an ‘image’ directory. Under the image directory the images will be
stored in directories labelled per event. The name of the image captured will be the same as
the name of the image node (which therefore would default to image.png).

If this is run in multiple realization mode then the model run number of the run will also be part
of the run. The name of the image will contain the model number along with the name of the
image node; for example Depth000.jpg, Depth001.jpg, Depth002.jpg etc.
Note that the images will be overwritten if another run with the same node name and run
model number under the same event is run. In workflows that have already been set to
produce images, (and found under the component workflows) a branch question precedes
the image generation node to warn the user.
Repaint
Repaint - Refreshes the graphics during a run or turns them on or off.

Batch Execution
Batch Execution
When running a large number of workflows for stochastic modelling it is possible to run the
workflows in batch mode accessing as many processors on the PC as you want and are
available.
Select the Batch Execution using Multi Processors

Batch Execution
Loop Start / Loop Stop - In the same way that the loop parameter and node can be set
within a workflow, this will set the workflow process to loop for as many times as
specified. Setting it here will override whatever value for loop is set in the workflow.
Number of Tasks - Taken from the number of processors the PC has this would usually
be left as the default allowing all CPUs to be used during the batch execution.
Abort - Allows you to Abort the process at any time.
This can be used as an Advanced use for batch on a number of different computers:
• Set up the Number of Tasks - CPUs to be used
• Press the Abort button once the 12 Tasks have started
• Pass the batch files to the other computers (since they are ‘simple’ batch files)
• When they have finished using the Collate button will collate these task batches
Collate - this is an advanced user option as mentioned above. The process will take a
while and the progress of it will be shown in the console window.
Note that running the batch process on one computer (over a number of CPUs) will
automatically collate the runs on finishing.
When ready, press Execute to start the batch process.
What happens during the Batch Execution

The process will begin by allocating however many loops to each task.
Progress will be seen in the main box of the Batch window.
The Tasks will start and progress will be seen as a blue bar moving across each Task bar.

Batch Execution
The task manager Performance tab will show all CPUs in use.
Eventually all processors will be running their allocated loops.
As the processors finish their allocated loops the bar will turn green.

Batch Execution
Finally all the processors will finish.
In the directory of the VelPAK project there will now be a new sub-directory called ‘batch’.
Within this sub-directory will be further sub-directories containing all the information that is
generated during a workflow looping run for each of the tasks run.

Batch Execution
There are also batch files (*.bat) stored in the batch directory which have been used to run
the processes. For advanced users, these would allow you re-run each task individually if
required. They can also put onto another PC entirely and re-run - providing VelPAK is
installed on that PC too. (Advanced use only!)
When the process is finished all the information stored in the ‘batch’ directory sub-directories
will be copied across to the relevant directories of the project.
Memory Allocation
Be aware that if you do not have a PC with ‘a lot’ of RAM running this amount of processes
may cause the PC to run out of RAM and move into ‘Swap space’ which will slow the
processing down considerably.
For every VelPAK run it tells you how much memory 1 model takes to run and store the data
down at the bottom right of the VelPAK screen.
In the example above running 8 models at once using the 8 CPUs available on this PC would
use up approximately 3.2GB of RAM. Therefore it needs to be run on a PC with at least 4GB
of RAM (to allow for other processes running on the PC at the same time).
(You can check the amount of RAM on your Windows 7 PC by looking at the System
information from the Control Panel.)

Batch Execution
To abort the process

To Abort the processes press the Abort button within the Batch screen.

List of Pre-defined Workflows

Depth Workflows
There are currently 52 depth Event Workflows available from the Workflows Property Grid fly
out. For each of these, once selected and the run started the user is then prompted to select
which gridding method they favor.
The workflows available are shown below; the checks against each method shows what
gridding methods you will be asked to choose from during the run.
Methods Kriging
Re
Global
Family of
None
Ordinary
Ext. Drift
Functi sid
Simple
Method
SGS
Function Name on ual
Type Ty
pe
Note: If Kriging is selected then a further sub-selection will be required for Ordinary Kriging,
Simple Kriging, Kriging with External Drift or SGS Kriging (Go Here for details of
Kriging.)
Gridding Method
Methods Kriging
Smooth
Functio
Global
Loess
Family of
None
Ordinary
Ext. Drift
Resid
Simple
n
SGS
Method Function Name ual

Type
Type*
Optimise V0kz Fit FixK X X X X X X

Optimise V0kz Fit Error X X X X X X

Gridding Method
Methods Kriging
Smooth
Functio
Global
Loess
Family of
None
Ordinary
Ext. Drift
Resid
Simple
n
SGS
Type
Type*
Optimise V0kz Residua FixK X X X X X X

l
Optimise V0kz Residua Error X X X X X X
l
Optimise V0kz User FixK X X X X X X
Optimise V0kz User Error X X X X X X
Optimise V0KZUpliftFromBase Fit FixK X X X X X X
Optimise V0KZUpliftFromBase Fit Error X X X X X X
Optimise V0KZUpliftFromBase Residua FixK X X X X X X
l
Optimise V0KZUpliftFromBase Residua Error X X X X X X
l
Optimise V0KZUpliftFromBase User FixK X X X X X X
Optimise V0KZUpliftFromBase User Error X X X X X X
Optimise V0KZFromSeaFloor Fit FixK X X X X X X
Optimise V0KZFromSeaFloor Fit Error X X X X X X
Optimise V0KZFromSeaFloor Residua FixK X X X X X X
l
Optimise V0KZFromSeaFloor Residua Error X X X X X X
l
Optimise V0KZFromSeaFloor User FixK X X X X X X
Optimise V0KZFromSeaFloor User Error X X X X X X
Optimise Faust Fit FixK X X X X X X
Optimise Faust Fit Error X X X X X X
Optimise Faust Residua FixK X X X X X X
l
Optimise Faust Residua Error X X X X X X
l
Optimise Faust User FixK X X X X X X
Optimise Faust User Error X X X X X X

Gridding Method
Methods Kriging
Smooth
Functio
Global
Loess
Family of
None
Ordinary
Ext. Drift
Resid
Simple
n
SGS
Type
Type*
Curve AverageVelocity v Time to X X X X X X

Base
Curve IntervalVelocity v Constant X X X X X X
Curve IntervalVelocity v DepthToBase X X X X X X
Curve IntervalVelocity v X X X X X X
DepthToMiddle
Curve IntervalVelocity v DepthToTop X X X X X X
Curve IntervalVelocity v Isochron X X X X X X
Curve IntervalVelocity v TimeToBase X X X X X X
Curve IntervalVelocity v
X X X X X X
TimeToMiddle
Curve IntervalVelocity v TimeToTop X X X X X X
Curve Isopach v Isochron X X X X X X
Mapping AverageVelocity X X X X X X
Mapping Depth X X X X X X
Mapping IntervalVelocity X X X X X X
Mapping Isopach X X X X X X
Sonic Log Time Depth Curve Look up X X X X X X
Sonic Log Polynomial from time depth X X X X X X
Sonic Log V0k from Velocity depth X X X X X X
Sonic Log Constant X X X X X X
StackingVelocit IntervalVelocity & Calibrate
X X X X X X X
y
StackingVelocit IntervalVelocity
X X X X X X X X
y
StackingVelocit AverageVelocity
X X X X X X X X
y
StackingVelocit RMSVelocity
X X X X X X X X
y
User Interval X X X X X X

Gridding Method
Methods Kriging
Smooth
Functio
Global
Loess
Family of
None
Ordinary
Ext. Drift
Resid
Simple
n
SGS
Type
Type*
User Average X X X X X X
User Mid point depth v IV X X X X X X
User IV v isochron X X X X X X
User Isopach v isochron X X X X X X
User V0KZ X X X X X X
* Residual Type - Choose to correct in the error domain or depth conversion intercept domain
(typically V0K but in the case of Faust this is ‘M’).

Interval Velocity v Time Well Layer Graphs

Data Requirements
Method Discussion
within VelPAK
Interval Velocity v This defines the Tops. Layers Defined.

Isochron.xml relationship between Time Grids covering area
Interval Velocity and of your wells (check that
Isochron for the specified deviated curves do not
layer. A typical application take well out of the area
would be where a salt defined by the grid). Depth
layer interval velocity conversion to layer above
increases as the salt thins. already been done.
Interval Velocity v (Not necessarily a As above

Time to Top of justifiable method
Layer.xml geophysically). Same as
above but values taken to
top of layer.

Time to Middle of justifiable method
middle of layer.

Time to Bottom of justifiable method
bottom of layer.
Interval Velocity v Depth Well Layer Graphs

Data Requirements
Method Discussion
within VelPAK
Interval Velocity v As below but values taken Tops. Layers Defined.

Depth to Top of to top layer. Time Grids covering area
Layer.xml of your wells (check that
deviated curves do not
take well out of the area
defined by the grid). Depth
conversion to layer above
already been done.

Data Requirements
Method Discussion
within VelPAK
Interval Velocity v **Good method** Popular As above

Depth to Middle of simple graphing method to
Layer.xml derive V0K.
Interval Velocity v As below but values taken As above

Depth to Bottom of to bottom layer.
Layer.xml

Interval velocity vs. Well Layer

Data Requirements
Method Discussion
within VelPAK
Grid Interval Mapping method. Tops. Layers Defined.

Velocity.xml Typical Application is Time Grids covering area
where graphing failed to of your wells (check that
establish a simple deviated curves do not
relationship take well out of the area
already been done.
Constant Interval Simple and quick As above

Velocity.xml approximate depth
conversion
Average Velocity v Time Well Layer Graphs

Data Requirements
Method Discussion
within VelPAK
Average Velocity Simple Approximation Tops. Layers Defined.

vs Time to Bottom Time Grids covering area
of Layer.xml of your wells (check that
deviated curves do not
take well out of the area
defined by the grid).
V0KZ Optimize Fix K Map V0 Methods

Data Requirements
Method Discussion
within VelPAK
Optimize V0K Best Uses Vz=V0+Kz depth Tops. Layers Defined.

Fit Fix K Map conversion method to Time Grids covering area
V0.xml search for optimum FIT V0 of your wells (check that
K parameters. Fixes K and deviated curves do not
generates V0 values to take well out of the area
Tie, maps V0 and depth defined by the grid). Depth
converts. Also checks conversion to layer above
residual error is zero. already been done.

Data Requirements
Method Discussion
within VelPAK
Optimize V0K Best Uses Vz=V0+Kz depth As above

Residual Fix K conversion method to
Map V0.xml search for optimum
RESIDUAL V0 K
parameters. Fixes K and
generates V0 values to
Tie, maps V0 and depth
converts. Also checks
residual error is zero
Optimize V0K Best Uses Vz=V0+Kz depth As above, also: USER

User Fix K Map conversion method. Uses VALUE must be set
V0.xml current USER VALUE.
Fixes K and generates V0
values to Tie, maps V0
and depth converts. Also
checks residual error is
zero.

V0KZ Optimize Single V0 K Map Error Methods

Data Requirements
Method Discussion
within VelPAK

Fit Map conversion method to Time Grids covering area
Error.xml search for optimum FIT V0 of your wells (check that
K parameters. Uses V0K deviated curves do not
parameters to generate take well out of the area
error values to Tie, maps defined by the grid). Depth
error values and depth conversion to layer above
converts. already been done
Optimize V0K Best Uses Vz=V0+Kz depth As above

Residual Map conversion method to
Error.xml search for optimum
RESIDUAL V0 K
parameters. Uses V0K
parameters to generate
error values to Tie, maps
error values and depth
converts
Optimize V0K Best Uses Vz=V0+Kz depth As above, also: USER

User Map conversion method to VALUE must be set
Error.xml search for optimum USER
VALUE V0 K parameters.
Uses V0K parameters to
generate error values to
Tie, maps error values and
depth converts.
V0KZ Optimize Fix K Map V0 Using External Drift of Time

Data Requirements
Method Discussion
within VelPAK

Fit Fix K Map V0 conversion method to Time Grids covering area
Using Krige search for optimum FIT V0 of your wells (check that
External Drift K parameters. Fixes K and deviated curves do not
Time.xml generates V0 values to take well out of the area
Tie, maps V0 and depth defined by the grid). Depth
converts. Also checks conversion to layer above
residual error is zero. already been done.

Sonic Log Methods

Data Requirements
Method Discussion
within VelPAK
Constant Interval Constant velocity Tops. Curves. Layers

Velocity From calculated from regression Defined. Time Grids
Sonic Log.xml of sonic logs. covering area of your wells
(check that deviated
curves do not take well out
of the area defined by the
grid). Depth conversion to
layer above already been
done.
V0K From Sonic V0 and K parameters As above

Log.xml calculated by linear
regression of sonic logs.
Depth v Time 2nd order polynomial As above but also data

Polynomial.xml calculated from time-depth must be calibrated
curves.
Single Well Time Production of curve using User must select well to
Depth Curve.xml single well use in the Well Module
Stacking Velocity
Data Requirements
Method Discussion
within VelPAK
Stack Velocity Dix Extraction of Dix interval Stacking Velocities must

Smooth.xml velocity smoothing using be loaded. Tops. Layers
xxx metres and depth Defined. Time Grids
conversion using covering area of your wells
smoothed grid. (check that deviated
curves do not take well out
of the area defined by the
grid). Depth conversion to
layer above already been
done.
Stack Velocity Dix Extraction of Dix Interval As above but also ‘Well
Smooth Calib.xml velocity, calibration to well Curves’
velocities, smoothing
using xxx metres and
depth conversion using
smoothed grid

Utilities
Data Requirements
Method Discussion
within VelPAK
Test Depth Surface Grids the depth at base of Tops. Layers Defined.
for Tie to Wells.xml layer and compares this to Time Grids covering area
depth surface; maps the of your wells (check that
result which should be deviated curves do not
zero at all wells. take well out of the area
already been done.


Analyze Module:
Stochastic Modelling in VelPAK
Introduction
A stochastic model is a tool for estimating probability distributions of potential outcomes by
allowing for random variation in one or more inputs over time. The random variation is usually
based on fluctuations observed in historical data for a selected period using standard time-
series techniques.
Depth conversion is generally responsible for the bulk of the uncertainty in the estimation of
field reserves. The standard VelPAK depth conversion routines [and associated workflows]
produce accurate velocity models very quickly, but it is important to derive an estimate of the
uncertainty in the depth horizons of interest.
The Analyze tool enables the user to develop a reasonable estimate of depth uncertainty
Rock Volume.
An 'absolute' answer to the depth conversion problem is impossible; the looped depth
conversion processes available in the workflow system will generate multiple depth
conversion models. The Analyze Module then allows filtering and analysis of the results and
P10, P50, P90

The Analyze Module can estimate Proved, Probable and Possible (P90, P50, P10) Gross
Rock Volumes.
Proved (P90) - The lowest figure, 90% of models are larger.
Proved and Probable (P50) - The most likely figure (median), the figure that is
expected to be closest to the true reserves.
Proved and Probable and Possible (P10) - The highest figure, 90% of models are
smaller than this figure.

Parametric Variation and Sequential Gaussian Variation (SGS)
VelPAK uses two main approaches,
Parametric Variation - depth variation resulting from uncertainty in the function
parameters in a deterministic model.
Sequential Gaussian Simulation (SGS) - used to explore lateral uncertainty in
mapped velocity parameters such as V0 or depth residuals.
Methods of Parametric Variation

• Curve Fitting using Optimization – using sonic logs, check-shots or time-depth curves to
analyze goodness of fit and derive a range of depth conversion parameters.
VelPAK can exploit a ‘Solution Trough’ to vary parameters; except for hypothetical cases
that are never encountered in practice, the solution for the parameters of analytic velocity
versus depth functions (e.g. Vz = V0+Kz) is inherently non-unique. This non-uniqueness
means that there is no particular parameter combination that represents the solution. The
average discrepancy between the observed velocity-depth (or time-depth) curve and the
calculated function curve gives a measure of the degree of fit between the two curves. In
the parameter space, within a given degree of fit that may be considered as the margin of
tolerance for the particular problem in hand, every parameter combination provides a
valid solution. The solution trough is defined as the region in the parameter space (e.g.
V0 and K) containing these solutions.

• RMS of Residual Errors – analyze residual depth errors for a range of depth conversion
parameters. VelPAK generates RMS depth error surfaces in parameter space. Many
models with almost the same RMS error are generated.

• Curve Fitting and RMS Error - using a combination of both the above methods within
acceptable curve fitting and RMS error ranges.
Confidence of regression – use the statistical calculation of Confidence (typically 95%) to
perturb any depth conversion regression. This generates a distribution of regression
values within confidence bounds.
The Confidence term in statistical analysis is used to represent the uncertainty in an

estimate of a curve or function based on limited or noisy data. Confidence bands are
often used as part of the graphical presentation of results in a statistical analysis.

The confidence region is calculated in such a way that if a set of measurements were
repeated many times and a confidence region calculated in the same way on each set
of measurements, then a certain percentage of the time, on average, (e.g. 95%) the
confidence region would include the point representing the "true" values of the set of
variables being estimated.
• Kriging Parameters – perturb the Range derived from a Variogram when using Simple or
Ordinary Kriging.
Sequential Gaussian Simulation

Lateral variation may be addressed by using Sequential Gaussian Simulation (SGS). This
may be used to generate parameter maps (such as V0) that tie at the wells and show
plausible variation in the parameter value away from well control. This technique requires a
spatial model (Variogram) of the parameter being mapped.
SGS is a means for generating multiple equiprobable realizations of the property in question,
rather than simply estimating the mean. Essentially, we are adding back in some noise to
undo the smoothing effect of kriging. This gives a better representation of the natural
variability of the property in question and gives us a means for quantifying our uncertainty.
The basic idea of SGS is very simple. Recall that kriging gives us an estimate of both the
mean and standard deviation of the variable at each grid node, meaning we can represent
the variable at each grid node as a random variable following a normal (Gaussian)
distribution. Rather than choosing the mean as the estimate at each node, SGS chooses a
random deviate from this normal distribution, selected according to a uniform random number
representing the probability level.

In the above diagram the thin dashed line shows how the data actually behaves, but this is
only known at the well locations. The solid line represents the velocity model derived by
kriging the values at the well points. It represents the best guess away from control points.
The thick dashed red line represents the uncertainty of the kriged estimate (lines of +/- two
standard deviations). The thin dotted line is a random realization generated using Sequential
Gaussian Simulation. It is no more accurate than the kriged estimate, but it is more “realistic”.
Note: Due to the randomization factor of this algorithm the grid will be different each time
generated and the corresponding contour map could also show dramatic differences.

Using VelPAK for Stochastic Modelling

Stochastic Modelling within VelPAK is achieved through using the comprehensive Workflow
system looping through depth conversion with a range of values and storing and applying the
data within the Analyze module.
Setting up a depth conversion that would give a “Base Case model” (M0) that would produce
the best technical case, the VelPAK workflow system then loops to run and re-run the depth
conversion perturbing the Constraints to produce multiple depth realizations. Constraints and
ranges for the multiple realizations are set up either before the model is run or during the first
run of the workflow itself.
Typically, at least 500 models will be run and statistics and volumes for each well, for each
layer and for each volume will be stored in the form of easily analyzed Data Grids. Data can
also be output to Excel. The statistics, volumes and parameters for each realization are
recorded.
The animation option of the Analyze module will capture snapshots as required so a ‘cartoon’
can be run to watch the range of reservoir size or any other displays of interest.
All the parameters of each model are saved such that any particular realization can be re-
created by calling up the model number as required.
Definition of Constraints
The constraints put on the multiple realization depends on what method(s) you have selected
to run within your workflow.
Curve Fitting using Optimization - use the Solution Trough to define a contour
level.
RMS of Residual Errors - use the Solution Trough to define a contour level.
Curve Fitting and RMS Error - use both Solution Troughs to define contour levels.
Confidence of regression - use the Curve Regression plot to define the Confidence
level.
Kriging- use the Variogram to define the Range min and max.
Sequential Gaussian Simulation - use the Variogram to define the Range and Sill,
SGS takes care of the rest.
Spill Point
Note: It is quite likely that the spill point could be different for each realization.
The Spill Point is the structurally lowest point in a hydrocarbon trap that can retain
hydrocarbons. Once a trap has been filled to its spill point, further storage or retention of
hydrocarbons will not occur for lack of reservoir space within that trap. The hydrocarbons spill
or leak out, and they continue to migrate until they are trapped elsewhere.
If the structure is ‘filled to spill’ then the spill point and value will vary for each depth
realization. VelPAK automatically calculates the spill point and calculates the Height Above
surface accordingly.

The Column Height Algorithm works by ‘flooding’ the depth structure to determine all of the
possible accumulations based on pure structural closure.

Phase 1 - VelPAK calculates the initial Height Above Contact surface showing all
possible accumulations.
Phase 2 - VelPAK then enables the user to ‘flood’ any accumulation by using an
existing well or choosing a target or seed point.

Another accumulation can then be targeted:
Each value is collected in the data tab and an image can be generated if specified in
the workflow.
Viewing the Spill Point and Crest on a Map

The Spill Point and Crest point for the last run on the Model can be displayed on the Surface
map by selecting the Spill_crest option for display.

Viewing a combination of Spill Points on one map for a number of

realisations
A display of a summary of the spill points and crest points for a multiple realisation run can be
seen by selecting the XYZ layers visible of the XYZ data slot ‘Height Above: Analyse Spill
Location Values’ and Contact: Analyse Crest Location Values on the target horizon.
Make sure Layers Visible is set to display XYZ and XYZ labels.
For a multi-realisation of a number of runs of VelPAK with different parameters, spill points
and crests can happen many different times on the exact XYZ node. This facility has taken
the XYZ locations of the spill points from the Data tab and adds up how many fall on the same
XYZ. It is this value that is plotted on the maps if the correct XYZ data file is selected.
In the picture above the Spill is being displayed of the P50 run of a realisation and with XYZ
‘Height Above: Analyse Spill Location Values’ turned on it can be seen that 564 other runs of
1000 realisations also had their spill point at that node.

Statistics Collection and Analyze
For each run data is collected in the data tab. Any column can be graphed in histogram or
scatter mode.
Volumetric Calculation
After the ‘Height Above’ and ‘Spill Point’ calculation has calculated the correct surface –
volumetrics can be easily calculated.
Inputs – any valid combination of
Top reservoir,

Base reservoir,
Contact as surface, constant or Automatic Spill,
Multiple or individual Polygons,
Seed Point to ‘flood’.
Outputs
Cubic Metres, Cubic Feet, Acre Feet etc.

Typical VelPAK workflow

Introduction to Analyze Module
Depth conversion is generally responsible for the bulk of the uncertainty in the estimation of
field reserves. The standard VelPAK depth conversion routines [and associated workflows]
produce accurate velocity models very quickly, but it is important to derive an estimate of the
uncertainty in the depth horizons of interest. However, running a manual sensitivity analysis
is tedious and prone to error and only a limited number of test cases can be run.
The Analyze tool enables the user to develop a reasonable estimate of depth uncertainty
Rock Volume.
An 'absolute' answer to the depth conversion problem is impossible; the Analyze Module
The Analyze module will:
1. Record the depth conversion scheme in a summary table,
2. Record individual models and well results for each iteration,
3. Allow graphing of the results,
4. Allow capture of the recorded images,
5. Run volumetric calculations.

Typically the process is run as a looped depth conversion processes in the workflow system
which will generate multiple depth conversion models as shown in the “Simple Loop. xml”
shown below.
The Analyze Module then allows filtering and analysis of the results.
Model vs Wells Discussion

When looking at data within the Analyze module some data will have been generated per
model and some will have been generated per well within a model.
Although this data is hierarchical, within the Data tab of the Analyze module it is laid out as a
‘flat list’ for graphing purposes. This means that data relating to just the Model is repeated.
Laying out the lists in this way allows the user to have the option of plotting model data versus
well data if required, for example if you see that there is a strong relationship between Well A
and the positive volume of a model you can plot selected attributes from Well A against the
model positive volume. (Go to Advanced Generate fly-out for details of this.)

Theoretical, Hierarchical Display of Model and Well Data:
Model 1 Model Info X Model Info Y
Well A Well
lnfo
Well B Well
lnfo
Well C Well
lnfo
Well D Well
lnfo
Well E Well
lnfo
Model 2 Model Info X Model Info Y
Well A Well
lnfo
Actual ‘Flat listed’ Display of Data in Data Tab:
Model Well Info - per well Model Info Repeated for

(Repeated) each well in the Model

Icons on the Analyze Window
Saving the results in an ‘.ana’ or ‘.xlsx’ file.
New Open Save Save

.ana .ana .xlxs
New - will clear the data on display in the Analyze tab. A default set up will have been
saved in the model directory (under the relevant event).
Open - opens a ‘*.ana’ file saved in the model directory (under the relevant event). A
default .ana file is saved here when Analyze is first run.
Save - if you make changes to the data table in the way it is filtered you can save your
new data display as a new ‘*.ana.’ file.
Save as Excel - will save the data in Excel’s .xlsx format (Office 2000 and beyond). The
more recent format is chosen since it allows saving of more than 64,000 rows (which is
often the case in the Analyze options).
Event Well
Event, Well within the VelPAK model.
Display Type Options
No display types other than Basic are available.

Edit Mode Options
The only mode is the point pick mode; which is only available to display point values in the
Graph tab.

Graph, Data, Data2, Anim and Summary Tabs
Graph
The graph tab will show a graphical display of whatever values have been selected from the
Generate Dialog.
Analyze Info Tool Tip

Holding the cursor over points on the graph will bring up information about the point as shown
below in two differing modes of the graph, showing you what model run that point is and the
X, Y values.

Analyze Info
Histogram Mode
Scatter Mode
Drill Down Image display

On scatter plots displayed in the graph tab clicking the middle mouse button on a plotted data
point will ‘drill down’ and give you a display in the Anim tab. This facility is best viewed by
detaching the Anim tab and docking it next to the Graph tab so that both tabs are displayed at
the same time as shown in the example below.
Note: This feature will only work if the workflow you have run has been set to generate
images.
The model number of the image selected from selecting a point on the scatter plot is shown
at the bottom of the image display.

(Model and) Image Number

Data
Data that is generated through the Analyze option via the workflow run is displayed
numerically in this Tab.
Note: Some columns are only used in “Well” mode and some only used in “Model” mode.
Go Here for discussion.
Clicking on the top of each column will sort the data alphanumerically in standard fashion.
Data can be sorted using more than one column using a ‘nested’ sort by holding the ‘shift’
button down while sorting.
For more control over which well data is utilised in the model, particularly with projects with
many wells, the Data table filters are cumulative. The right-mouse button context menu to
allow fast resetting of all the filters applied, and to force the data table to be rebuilt from the
model.
Data seen in the tab can be output as an Excel ‘.xlsx’ file to read into a spreadsheet. These
data and any filtering that has been done to it can also be saved as a ‘.cft’ file.
Moving the Columns


Select Summaries
Selecting the symbol on a particular column brings up the Select Summaries box which
allows the user to display the Average, Count, Max/Min and/or the Sum of that column. The
results will be shown at the top of the column. To remove the values from display select again
and uncheck the values in the box.

Filtering the Data
Custom - User defined selection of Operator and Operand to filter data. See below for
details.
Custom Filter


Location.

Column Description
When looking at data within the Analyze module some data will have been generated per
model and some will have been generated per well within a model.
Although this data is hierarchical, within the Data tab of the Analyze module it is laid out as a
‘flat list’ for graphing purposes. This means that data relating to just the Model is repeated.
Go Here for example.
Model No. - The number of the model under which the values are generated. Model 1, for
example model is the first of the random models generated of perhaps 1000 runs and
would not be linked to Model 2 at all.
Well Information
Well Name - Name of well
Fit - Related to whether you have put Yes/No to Fit in the Optimize set up.
Residual - Related to whether you have put Yes/No to Residual in the Optimize set up.
Error Before - Z value of Error used in the gridding.
Error After - Should be zero if you have done an error correction on every well. If you turn
a well off you can see what the error should be for that well (a method of cross validation).
Base Depth - The depth at the base well pick.
Base Grid Depth - The value of the base depth grid interpolated at the base well pick
Well Isochron - The isochron based on the top and base time values (i.e. TOP_TIME
and BOT_TIME). These may well be offset from the grid values for top and base of layer
wells. They should be treated with caution for deviated wells.
Grid Isochron - The isochron based on the top and base time grid values
(i.e.TOP_TIME_GRD and BOT_TIME_GRD).VALUES ARE ONLY MEANINGFUL FOR
VERTICAL WELLS. They should be treated with caution for deviated wells.
Vertical Apparent IV - The interval velocity derived from the top time and depth grids,
TOP_TIM_GRD_BOT and TOP_DEP_GRD_BOT and the time and depth values at the
well base pick BOT_TIME_GRD and BOT_DEPTH
Well IV - Well Interval Velocity
Model Information
Opt Param1 / Opt Param 2 - the two parameters of the depth conversion function used in
the Optimise routine - most commonly the values of Vo and K. These can be two of three
parameters of a function providing that the third is constant. Another more common
function is Faust where these parameters would be ‘a’ and ‘m’ in faust. [It would be
expected that the user would know what these values refer to for each layer in the
Analyse.]
Fit Result / Res Result - the values at the given Optimize Parameters.
Regression Param1 / Regression Param2 - the values of a0 and a1 if applicable.

Confidence Value / Confidence Result - The set value and result derived from the
Confidence input in the Curve module.
Range - a Kriging parameter - if used this is the range used for that event.
Spill Point - the depth at which the Spill occurs.
Crest Value - The maximum depth of the reservoir.
Crestal
Value
0
Top Zmin / Top Zmax / Base Zmin / Base Zmax - the minimum and maximum of the
depth grid used in the volumetric calculation (if used).
Pos Volume - Positive volume in whatever units it has been generated in.
Random - (for internal purposes only) - the number of times the random number
generator had to be run to get to the start of a given model.
Inactive / Active - the current state of the the data grid - whether filtering has happened
or not.
Data2
Data2 is an internal data table which shows the data values that are displayed in the Graph
tab, which can be a useful QC tool.
Anim
The tab where the animation will show - as set up in the Anim tab.

Summary
The summary tab is used to summarize the depth conversion methods and values you have
run on the model. The Base Case shows the methods and the parameter values used for
each horizon while the Random shows the method, the values that were randomized in the
run and the minimum/maximum values assigned to the randomized values. The Random
case will also show in the relevant columns any volumetric calculations that have taken place
plus the P10, P50 and P90 values.
Summary Columns
Gives a listing of all the values for the parameters used or generated in the Base and
Random cases.
Note: Some columns pertain to only the Base Case or the Random Case and also to what
depth conversion method has been chosen.
Gives a listing of all the values for the parameters used or generated in the Base and
Random cases.
Event No. / Event Name - Listing the event number and name
Method Type - Indicates where the values have come from for the depth conversion
method.
Method Name - The Depth Conversion method used for that layer.
Param1 Name/Param1 Value - Name and value of the Parameter 1 used.
Param2 Name/Param2 Value - Name and value of the Parameter 2 used.
Grid Radius - If a grid is used as a parameter - the radius is here.
Conf Type/Conf Percent/Conf Factor - Confidence values.
Fit Min/Fit Max - Min/Max of the box used to optimize
Res Type - RMS or Average.
Res Min/Res Max - Residual Min/Max.
Range Min/Range Max - Min/Max of the ‘wobble’ variogram range value (in Kriging
mode).
Range Value - Base range value (in Kriging mode)

Sill Value - Sill value (if Kriging used)

Volume Min/Volume Max - Minimum/Maximum volume calculated throughout the run
M0 Volume - Volume value of M0 case.
P10 Model - Model number for P10 case.
P10 Volume - Volume value of P10 case.

Analyze Display Dialog

The Display dialog controls the basic graphing parameters.
option.
Options
Flip_X - Yes/No - selecting Yes the X axis will be flipped.
Flip_Y - Yes/No - selecting Yes the Y axis will be flipped.
Label - Labelling of points on the Graph.
Label_Color - Label_Color - Color of label for point. See Color Below.
Label Font - Font used for the label of points on the graph. See Fonts Below.
Title
Title - The title of your plot. This is editable here but will become over written by the
default title if another graph is selected.

X_Title - The title of your X and Y axes. These are editable here but will become over
written by the default title of another graph is selected.
Histogram
Bins - When drawing the histogram this sets how many bins or containers the data will
fall into; given the range of the X axis the program will calculate the width of the bins
accordingly.
Bin value set to 10 Bin value set to 50
Probability - Yes/No - Choose to display the probability curve that has been calculated;
showing the P10, P50, P90 and M0 points.
Color - All of the above Color inputs have the same color options. Select the color for the
input from either two sets of pre-defined color tables Tabs; Web and System, or from the
customized Tab.
Fonts - All the above Font inputs have the same set up options. On selecting the Font
option, the following standard font box appears to allow you to set up the font as you wish.

These changes and more can also be made by expanding the ‘Fonts’ input line using the
‘+’ symbol to the left of the input.

Generate Dialog
Generate Dialog
Generate Dialog - General Tab
option.
Option
Group - Model/Well - a very important selection. Go here for a discussion on Model
versus Well.
Type - Scatter/ Column/ Histogram - The type of graph to be displayed. Depending on
your selection on the standard tab this will change automatically.
Generate Dialog - Standard Tab

The standard tab gives a bank of graphs to analyze the relationship between different
models.
These standard graphs do not allow the user to select a Model data type against a Well data
type. However within the Advanced tab it is possible to select to plot a Model data type
versus a Well data type.

Generate Dialog
option.
Analyze Info
On all these graphs holding the cursor over the data will bring up the Analyze Information.

Generate Dialog
Standard Graphs grouped by Model

Scatter
For example Positive Volume vs Spill Point:
Note: The different symbols and colors do not represent anything - they merely help to
distinguish between one point and another.

Generate Dialog
Column
For example Crest Value vs Model Number:
Histogram
For example Number of Models vs Positive Volume:
Standard Graphs grouped by Well

Wells can be selected or deselected via the filter within the Data tab.
Scatter
For example Error After vs Error Before

Generate Dialog
Column
For example Error Before vs Well Name:
Histogram
For example Number of Wells vs Error after:

Generate Dialog

Generate Dialog
Generate Dialog - Advanced Tab

The Advanced tab allows the user to make up their own analysis relationships between
models.
option.
Model vs Well plots

It is possible within the Advanced tab to plot a Model data type versus a Well data type. For
example you may want to plot Well ‘Error After’ versus Model ‘Positive Volume’ to plot out the
strong relationship you can see between a particular well and the model.
Note: The number of points plotted if each well value is being plotted may be considerable
(30,000 points for example) compared to the number of points if model data is plotted.

Statistics Dialog
Statistics Dialog
Statistics Dialog - A Discussion
The General statistics dialog is the process by which the information usually generated
through a looping workflow is collected and - if requested - a Volume produced for each
model run.
The top option of the dialog page is the Active Yes/No input. Whether you put yes or no to this
will change the function of the dialog.
ACTIVE YES - VOLUME PRODUCED (and Data collected for Graphing)
ACTIVE NO - DATA COLLECTED FOR GRAPHING PURPOSES
In Inactive mode (Active = No) requested information from the looping workflow will be
collected and displayed in the Analyze data tabs.
In Active mode (Active = Yes) requested information from the looping workflow will be
collected and displayed in the Analyze data tabs and a volume will be calculated from the
parameters set up within the dialog.
Using Statistics General dialog as a “one-shot” Volume generator and

QC tool
Using the Statistics dialog from within VelPAK itself and not part of a workflow routine will
allow the user to generate a Volume from the grids set up in within the dialog.
The numerical value of the volume generated for the “one-shot” will be displayed in the
Console window. The output volume grid, which defaults to being stored in the Height Above
slot of the model tree unless changed by the user, can be viewed in the standard way in the
Surface dialog.
The “one-shot” option can be a useful method of finding the best point to place the Spill point.
By setting the spill at various places and seeing what the resultant volume grid looks like and
as a general QC tool before running a looping workflow.

Statistics Dialog
Using Statistics dialog within the workflow
Note: The workflows set up to run the Volume dialog will not pause to check that you have
set the Volume units and values correctly - you will need to set the Volume dialog up
for the correct units before running the work flow.
Below is an example of a looping workflow for running the Analyze Statistics module.
The purple nodes seen below relate to the tools at the top of the Statistics tab (shown next to
the node).
The looping work flow starts and proceeds through each event with the Analyze stats model
set to Active = No for all but the final event. This means that although all the data will be
collected for events 1 - 3 it is only event 4 where the volume calculations will take place.

Statistics Dialog
Collecting relevant data Volume Calculation

will take place
Selecting the Volume method - Top, Base and Contact or Spill

The method of calculating the Volume is set in the Statistics dialog; dependent on whether
you are going to use the Top depth grid/value and Base depth grid/value with or without a
Contact grid/value or Spill.
Note: The top grid in these calculations is the the current grid; the base grid is taken from
the event below.

Statistics Dialog
Top Depth only being used
TOP
Volume
Top Depth with Contact or Spill point
Top Structure TOP

Volume
Contact /Spill
Contact or Spill
Top and Base Depth grids being used
Volume TOP
BASE

Statistics Dialog
Top and Base with Contact or Spill point
Top Structure
Contact or Spill
Base Structure
BASE TOP
Volume
Contact or Spill
Contact or Spill
Note: the resultant

grid looks like this!

Statistics Dialog
Statistics Dialog - General Tab

Tools
The tools at the top of the Statistics dialog would usually be activated in the workflow
system - each one has a different node associated with it in the workflow system. Go
Here for further discussion about using these in the Workflow system.

Statistics Dialog
Start - - Start the data collection in the workflow loop.
Initialize - - used at the beginning of the loop to initialize it.
Record - - statistics within the loop.
End - - finalizes the run and turns the temporary data files where the data has been
collected in to the Data tabs.
Generate Volumes - - generates volumes within loop.
Save Zmap Grid - - writes a Zmap grid to the external project directory; the name of
which will be constructed from the event number and name.
Save Statistics Grid - - writes a Zmap grid to the external project directory; the
name of which will be constructed from the event number and name.
Delete Statistics Grid - - delete grids before writing new ones.

Options
Option
Active - Yes/No.
In Active (Yes) mode the volumetrics will be calculated using the information on the rest of
the dialog and requested information from the looping workflow will still be collected and
put in the Analyze data tabs.
In Inactive (No) mode no volumetrics will be calculated - but requested information from
the looping workflow will still be collected and put in the Analyze data tabs.

Statistics Dialog
ACTIVE YES - VOLUME PRODUCED (and Data collected for Graphing)
ACTIVE NO - DATA COLLECTED FOR GRAPHING PURPOSES
Note: If you want a seed point which is not represented by a well in the model you will need
to insert a pseudo-well using Well Edit Point Insert within the Surface module.
Top/Base - set up the grid or value to be used as the top and base of the reservoir in the
calculation. (Go Here for a discussion on these.)
Top_Value / Base_Value - enter a value here for the top / base of the reservoir if a
constant is to be used and not a grid for either the Top or Bottom.
Top_Grid_Event / Base_Grid_Event - Select the Event number the grid is stored under.
Top_Grid_Type / Base_Grid_Type - Select the location of the grid (usually Depth).
Note: The top grid in these calculations is the the current grid; the base grid is taken from
the event below.
Contact
The Contact can be a value or a grid.
Contact_Value - Enter a value here for the contact if a constant is to be used.
Contact_Grid_Event - Select the Event number the grid is stored under.
Contact_Grid_Type - Select the location of the grid (usually Contact).
Seed - A drop down list of all the wells in the model to select the well location controlling
the flood Spill algorithm. The seed will be activated as part of the volumetrics calculation
by selecting Spill_Active = Yes.
Spill_Active - Yes / No. Setting this to Yes will activate the seed as set above.
Note: While usually thought of as the contact between oil and water or gas and water the
contact could be used to determine the volume of a particular ‘slice’ of volume.
Polygon
Use polygon or polygons to control the reservoir volume.
Polygon_Type - select where the polygon is stored in the Model Tree.
Polygon_Type_Name - If more than one polygon is stored in the Model Tree slot the
drop down here will display all polygons stored in this slot and allow you to select which
polygon you want to use.
Volume
Mapping Units - Meters / Feet. Until this moment VelPAK has not been using units but for
volumetric purposes it obviously needs to assign the units the model is in.

Statistics Dialog
Volume_Grid_Type - the output slot where the volume grid will go. Defaults to the Height
Above slot.
Volume_Scale - Millions_Cubic_Metres / Millions_Cubit_Feet / Hectare_Meter /
Acre_Feet - The user will decide what scale is required for the volumetrics calculation.
Given the map units and the volume units VelPAK will calculate the volume in whatever
scale is entered here.
Volume_Units - Not necessarily the same as the Mapping Units; the Z measurement can
often be using feet when the Mapping units (X,Ys) are in Meters. So make sure this
Volume Unit is set to the actual unit the Volume_Grid_Type (above) is generated in.

Statistics Dialog
Statistics Dialog - Statistics Tab

The Statistics tab allows the user to analyse the grids generated (and stored externally in the
‘grids’ subdirectory) through the Utility Save Grids to Disk’ workflows.
Discussion
The statistics tab allows a selected statistical process to be run on the grids stored. One grid
will be produced and placed in a specified VelPAK slot to display the results.
For example setting the slots to be as shown below will take all the grids stored in the
external grid directory named ‘Height Above_xxx’ . For each node on each grid the value will
be read and every time the value of the node is greater than the constant (in this case zero)
one gets added to the count for that node.
When all the grids have been read, a percentage value of number of nodes achieving a value
greater than constant is assigned to that node in the out put grid.
Note: For this example the height above has already been defined since it is the ‘Height
Above’ set of grids being used - therefore Constant=0. This technique could equally
well be used on a set of depth grids with the constant being defined as the oil water
contact, for example.
Typically in the centre of a model one would expect to achieve a 100% hit rate for this
statistical process, while around the edges it would taper off - this is shown in the example
below. This therefore visually displays the probability of closure for the model.

Statistics Dialog
Total model display

of Height Above
percentage above
zero
Edge of Model
Central Model
Grid Node showing Z = 24.6 (%)
Grid Node showing Z = 100 (%)
Properties
Constant - Used for percentage above and percentage below processing types.
Input - The generic name for the set of grids to be used in the process. Select the generic
name from the drop down list. This will select the set of grids from the ‘grids’ sub-directory
from the model directories.
For example selecting ‘Height Above’ will actually select the named file:
“Height_Above_004_Base_Upper_Permian_Event_4_Created_by_Xpress_xxx.cps1” in
the grids directory where xxx is the number of the run it was generated from.

Statistics Dialog
Output - The slot in the VelPAK model tree where the calculated output grid will go.
Default is General 01.
Type - The type of statistical process to be run on selected grids:

Minimum - shows the minimum value of any grid over any and all the nodes.
Maximum - shows the maximum value of any grid over any and all the nodes.
Note: The results of the above two may look a bit strange plotted as a contour map!
Average - the true average value for each node.

Standard Deviation - Standard deviation for each node.
Percentage Above - The percentage of each nodes that fall above the given constant
value.
Percentage Below - The percentage of each nodes that fall below the given constant
value.

Anim Dialog
Anim Dialog
The Animation dialog animates the images generated during looping workflows (if the Image
option is chosen by the user during the workflow routine).
Note: To see the animation working you need to have the Anim tab to the front of the
Analyze Tabs. If it is not to the front the animation will be running out of view. Press
the abort button, bring the Anim tab to the top and play again.
Anim Dialog - General Tab
option.
Tools
Run - - plays the animation.
Previous - / Next - - moves the animation forward or back one image.

Anim Dialog
Delete Anim Images - - *Caution!* - this will delete all images in the directory with
the selected Basename.
Options
Basename - The generic name for the set of images to be displayed in animation mode.
The Image option in workflows will have generated a number of images, for example. The
name can be selected from the selector which will pop up by pressing the icon to the
right of the basename slot.
Delay - Set to an arbitrary default of 500, this can be changed to make the animation
move faster or slower as required.
Index - The number of the run you want to start the animation from.
Step - Choose to step the animation - a step of 5, for example, would mean only every
fifth image generated would be displayed in the animation.
Type - Choose to run the animation forward or back or ‘ping-pong’ will go forward and
then back and so on.

A
Glossary
A
AOI or Area of Interest
This is the region in space that the velocity model occupies. It is determined by the extents of
the data loaded into the model.
Generally it is a good idea to create a grid of sea bottom, basement, or laterally ubiquitous
event to act as a master or parent grid. You can then generate all other grids to match the X
and Y extents & cell size of this grid. Note the cell sizes in VelPAK grids must be square; the
X dimension must match the Y dimension, and all grids must have the cell size.
Note that with surface mode depth conversion, ‘holes’ in a grid are propagated downwards
through the volume, so it is important to precondition the grids correctly prior to depth
conversion. See ‘Preparing Grid Data for the VelPAK Model’ in the ‘Introduction’ chapter
under ‘Help > Tutorials > VelPAK’.
When creating a grid in the Surface module, the Grid fly out has a Range tab that features
icons for automatically setting or computing the AOI. Be consistent with these options in the
model.
Apparent Velocity
Also known as pseudo velocity. The velocity estimated by matching seismic event
interpretations in time to formation tops from wells in depth.
Average Velocity
The ratio of the depth of an event to the vertical travel time of the seismic wavefront to that
event. In VelPAK, this is referenced from the seismic datum. Note that as seismic times are
typically measured in two way travel time, the average velocity to any given depth is given by:
In the Velocity module, average velocities for wells can be plotted (after Layer Definition has
been performed). In this module average velocities can be computed from RMS stacking
velocities and overlain with the well average velocities.
An average velocity volume can be generated using the Volume fly out of the Velocity
module. The average velocity volume is most useful for depth conversion of surfaces not in
the velocity model.
See also Seismic Velocity.

B
B
Background Velocity
The regional trend of the velocity field.
BIN file
See VelPAK Model File

C
D
Datums
A discussion of datums is given in the whitepaper ‘VelPAK and Reference Datums’ available
to download on the IHS Kingdom website.
Depth conversion
Depth conversion is usually the final objective of a study using the VelPAK module. In
Surface Mode, grids are depth converted as you work down through the layers. In Profile
Mode, the velocity characteristics of each layer must be defined prior to performing the depth
conversion if each horizon interpretation.
Within Kingdom, there are a variety of methods for accomplishing each of these tasks, as
indicated in the following table.
2d3dPAK TracePAK VelPAK VelPAK

Profile Surface
Grids X X
Horizons X X
Faults X X
Seismic X
volumes
T-D chart
Diagnostic mode
There is a useful option in the Velocity Volume Generation fly out that allows you to generate
an ASCII text file that details all of the parameters in the velocity model used for depth
converting each layer. To use this option, set the ‘Type’ parameter to ‘Diagnostic’. The output
file will be that set in ‘File’ (which will be written into the author’s project folder). Set the
‘Diags’ flags to ‘Yes’ or ‘No’ to incorporate more or less information into the text file.
Note that the ASCII files generated can be huge in size so limit the velocity volume
generation range to a few traces in the area of interest!
Dix Interval Velocity

Dix derived an equation to approximate the interval velocity for a layer from the RMS
velocities at two surfaces:

C
where:
Note that this equation makes the assumption that the surfaces are flat, parallel layers.
You can apply the Dix equation to RMS stacking velocities using the Velocity module Dix fly
out. This computes both interval and average velocities for that layer. Note that as RMS
velocities are typically several percent higher than the average velocity, the default
percentages for the Dix equation are set to 92%.
See Dix, C.H. (1955), Seismic Velocities from Surface Measurements, Geophysics,20:68-86

E
E
Event
An Event is either a horizon or grid, loaded into the velocity model, which delineates a
change in velocity regime in the vertical domain. Typically these correspond to changes in
rock lithology. Events correspond to a layer number. Therefore, the first event represents the
bottom of the first geological layer in the model.
If using well data in the velocity model, formation tops must be associated to Events using the
Layer definition module.

F
F
Fly out
Fly outs are pop out menus, typically located down the right-hand side of each module
window. The fly out content are specific to each module window. Fly outs can be ‘pinned’
open by pressing the pin icon in the top right hand corner of the fly out:
Multiple fly outs can be pinned open at any one time – they will stack on the screen in order to
maximize space for the main display window.

G
G
Grid
A grid is spatial representation of data that contains data samples in regular array.
It is strongly recommended that all grids used VelPAK have a square grid cell size and have
the same extents as a master (or ‘Parent’ grid). Typically the’ Parent’ grid will be Event 1, and
should cover the whole area of interest. This typically may be water bottom, bottom of the
weathered layer etc.
Using Surface Mode, grids will be depth converted from shallowest to deepest, so if a grid
above the current event covers less of an area, only the lesser area can be depth converted.
Grids may be created in VelPAK from XYZ data points or by processing other grids (on the
Process fly out of the Surface Module).
Grids are stored in the Model tree under the Surface >> Event Name >> Grid branch, and are
stored by GridType.
See also AOI, GridEvent, GridDesc and GridType.
GridEvent
The number of the grid event in the velocity model (0 is the surface, 1 is the shallowest event
e.g. sea bed, increasing downwards). In dialogs, a grid number can be specified by number,
or by using the nomenclature of ‘Previous’ & ‘Current’. The ‘Current’ surface is the one set in
the ‘Surface’ dialog in the model tree window, ‘Previous’ is the grid directly above.
For example, if the user wished to add the isopach of the current grid 3 to the depth of grid 2
to give the new depth grid for surface 3, and surface 3 is current, the parameter declaration
would be valid as either of these options:

G
See also GridType and GridDesc.
GridDesc
Prefixed by a parameter number, GridDesc is a text field that the user can edit to apply a
short description to a grid held in the model tree. The grid description is displayed in the
model tree after the GridType label.
You can edit the description by clicking the grid in the model tree and editing the ‘Name’ field
in the ‘Properties’ table.
See also GridEvent and GridType.
GridType
Prefixed by a number, GridType refers to the named slot in the model tree to read data from
or write data to. There are a range of GridTypes predefined. You cannot add to the GridType
list but there are generic ‘GeneralXX’ types you can use to store any data type in. You can
add your own descriptive text to a GridType using the GridDesc field.
Note that it is perfectly safe to use the same input and output GridType in an operation. For
example, to multiply a depth domain grid by 0.3048, you would use the Surface module
Process fly out & set the parameters as follows:

G
The output depth grid will overwrite the input grid after it has performed the multiplication.
You can move data between GridTypes in a specified layer by right clicking the source slot,
selecting ‘Copy’, then right-clicking the destination slot and selecting ‘Paste’. If you wish to do
this in a workflow, you can use the node Surface.Process.Parameters and use the Math+
(Add) formula to add 0 to the source grid and store in the required output slot.

H
I
Interpretation
Horizon and fault interpretation is imported into the VelPAK model, using either the link or by
ASCII import. This is generally only ever used in Profile Mode and must undergo the
Snapping procedure before use.
Snapped interpretation cannot be directly put back into the Kingdom project database as the
data may have been merged to produce pods, channels and multi-Z component
interpretation. Instead it must be exported to ASCII files in segments for import back into the
project database.
Interval Velocity
The ratio of the vertical thickness of a layer to the vertical travel time of the seismic wavefront
through that layer. See also Seismic Velocity and Dix Interval Velocity.
INDT
Indeterminate or NULL value. These occur in grids where maybe a fault polygon exists, or
grid cells are divided by a zero value, or the gridding algorithm doesn’t project data between
sparse data points.
INDT values in grids can be replaced by a user specified constant (or values from another
grid) using the Surface Module ‘Process’ fly out; on the ‘Parameters’ tab set the ‘Formula’ to
‘SET INDTS TO GRID OR VALUE’, and specify the parameters as per usual.
The velocity at any given time or depth.
Isochron
A time thickness grid of a layer. After depth converting a layer, the Isochron grid for that layer
can be displayed by double-clicking the Isochron grid in the Model Tree.
Isopach
A thickness grid of a layer in the depth domain. Technically, the isopach grids generated by
VelPAK are in fact depth domain isochore maps, as they measure vertical thickness. In the
strictest terms, an isopach is the thickness of a layer measured normal to the bedding planes,
but VelPAK uses the vernacular meaning of the term.
After depth converting a layer, the isopach grid for that layer can be displayed in the ‘Surface’
module by double-clicking the Isopach grid in the Model Tree.

J
K
K
See Velocity Gradient.

L
L
Layer
Layer has two meanings in VelPAK:
1. The geological region between two surface events
2. The visible data on the Surface map and other displays. The visible layers may be toggled
on & off using the ‘Display’ fly out or the ‘Layers Visible’ drop down
Layer cake depth conversion

This is the method that VelPAK uses to depth convert grids in the ‘Surface’ module. The
overburden is separated into velocity layers, the velocity change in that layer is modeled and
then the isopach of the layer is computed. The isopach is added to the depth of the layer
above to give the depth of this layer.
Layer definition
This is the process of assigning the layer model from the layer event data to the well data.
This is done by matching up formation tops that correspond to the layer events (grids) in the
velocity model.
Layer definition is performed in the Layer module. Multiple formation tops can be assigned
within one layer. The layer model can be seen in the Well module after the model has been
applied. The layer definition in the wells is displayed to the left hand side of the well curve, the
layer definition made by the event layers (grids) is displayed to the right hand side of the well
curve. Ideally, the color blocks should match up either side of the curve.

M
M
Model Tree
Analogous to the Project Tree displayed in the main application window, the model tree
contains a list of data in the velocity model. However, the model tree differs in that it contains
a sorted arrangement of Surfaces, ordered from the shallowest layer (the seismic reference
datum) down to the deepest layer. Profile and well data is stored in alphabetical order in the
model tree.
By default, the model tree only display data that is present in the model. To display model tree
slots unoccupied by data, click the ‘Show Unused’ icon in the model tree icon bar.
Model Tree Slots

Each layer in the model will occupy a number in the range 1 to 31 (0 and 32 are reserved by
the program). The number indicates increasing layer position (so Layer 1 is shallower than
Layer 2, Layer 2 is shallower than Layer 3 etc).
See also GridEvent.
Within each Surface, there are named slots in the model tree. These names are fixed, and
represent the data store within them. For example, the ‘Time’ slot will hold time domain data
for that layer, the ‘Isochron’ slot will hold time thickness data for that layer etc.
See also GridType.
Each Surface also can have a variety of data types: XYZ, Fault, Polygon, Grid and
Interpretation. The XYZ, Grid and Interpretation data types have the same fixed name slots.
For example, XYZ data for a surface may contains’ Time’ domain control points, ‘Isochron’
time thickness control points for that layer.
When generating data in VelPAK, data to be stored in the model tree is specified by a fixed
slot name. (in contrast to creating a grid, in the main application). By using the slots available
there should be no confusion over data types created, and enables the construction of
generic workflows using data held known variables in the model.
Module
A VelPAK workspace activated by clicking the Module name icon on the main VelPAK display.
Modules may be detached from the main display by double-clicking the module name tab
after the module has been activated.
To reattach the detached module to the main display, double-click the title bar of the module
window.
The available modules are as follows:
Module Primary Function
Surface Map display, depth conversion of grids, grid math

M
Module Primary Function
Profile Horizon display, depth conversion of geology that cannot

be represented by grids
Layer Association of well formation tops with grids
Well Display & QC of well data, generation of residual errors,
basic log/top editing
Velocity Display and Dix conversion of stacking velocities, survey
definition & generation
Curve Graphing methods to derive velocity function parameters
Optimize Powerful tool for derivation of velocity function
parameters
Fault Display of Allan diagrams
3d Basic 3d display of grid surfaces
O
Optimization
In VelPAK, optimization is a powerful & robust technique to determine the best parameters for
a given velocity function using well velocity data. The objective function is set by the user in
the Surface module Depth fly out (e.g. [Optimize] Linear V0 KZ, V= V0+Kz), the parameter
space defined, the process is run and the optimal parameters displayed for automatic or user
selection.
A number of pre-defined workflows are built into the ‘Workflows’ fly out of the ‘Workflow’
module, to make using this technique very simple.

P
P
Pods
Pods are discrete geological units whose velocity can be modeled and are used exclusively
in Profile Mode. Typically they are introduced during or after the main layers of the profile
have been defined. This event number must be classed as a Pod using the Pod tab on the
Snap fly out in profile mode.
Typical uses for pods are to model channels, shallow surface anomalies, gas seepage
between layers, and even lacoliths.
Profile Mode
If the geology of the project is complex and cannot be represented by a grid, Profile mode
can be used. Typical scenarios are for regions with reverse faulting, salt diapirs and channel
systems.
A profile is a single vertical section. This could be a 2d line, inline or crossline from a 3d
survey, or a random (or arbitrary) line across multiple surveys.
Profile mode works by depth converting the data loaded into each profile. Typically this is
horizon data brought into the model from the interpretation project. The horizon data must
undergo the snapping process to produce a 2d sealed earth model, prior to modeling the
velocity changes in each layer of the profile.
Unlike Surface mode, the velocity function for each layer must be defined prior to depth
converting the profile.
Note the Profile mode can use data (e.g. interval velocity grids) to depth convert the horizons.
In addition to layers, profiles can also incorporate sealed units called pods, which may or may
not intersect with the layers in the profile.

P
Property Grid
Property grids are user interface elements that are tables of parameters and information,
typically seen in the Fly Outs. They are not to be confused with the time or depth grid data for
example (although there is a property grid, under the Model Tree, that contains information
on the grid selected in the Model Tree).
Pseudo Velocity
See Apparent Velocity.

Q
R
RMS Velocity, Vrms
Defined by:
Where Vik is the interval velocity for layer number k.

VRMS is the root mean square velocity. This is not synonymous with Stacking Velocity,
though they can converge in value at zero offset.

S
S
Seismic Velocity
The rate at which a seismic wavefront travels through the medium. Seismic velocity is
typically anisotropic within a medium. In flat-bedded sediments, typically the horizontal
velocity is higher than the vertical velocity.
With sedimentary rocks, usually the velocity increases with depth within a uniform layer due
to burial compaction and diagenetic effects. Hence there is often a velocity gradient within a
layer.
Velocities may be categorized as average velocity, interval velocity or instantaneous velocity.
Stacking Velocity
Stacking velocity is the value used to stack seismic traces, typically derived by semblance or
coherency methods in seismic processing packages. Typically hyperbolic moveout with offset
is assumed in the derivation of stacking velocities.
See also RMS Velocity.
Surface Mode
When the geological layers can be represented by a series of grids, it is best to use VelPAK
to model the layer velocities and then depth convert each grid in turn (see Layer cake depth
conversion). This situation lends itself well to the use of workflows.
When working with entirely grids, there is no advantage to be gained by bringing horizon data
into the model.
When the geological layers cannot be represented by surface grids, Profile mode can be
used to model vertical sections. Surface mode is much less labor intensive to work in than
Profile mode.

S

T
T
TKS Link
This is the link between the velocity model, and the main Kingdom project database. Data
can be loaded into the velocity model from the database using ‘File >> Open TKS…’ and
stored from the model into the database using ‘File >> Save TKS…’.
Once data has been loaded into the model, it can be edited, manipulated, or deleted without
changing the data in the Kingdom database.
See also VelPAK model file.
U
V
V0
See ‘Velocity Intercept’.
VelPAK Model File

Use ‘File >> Save’ or ‘File >> Save As…’ to save the current velocity model and all the data
therein, to a single file with the ‘.bin’ suffix. The default location for this file is the author folder
in the Kingdom project path.
The model file can be opened using ‘File >> Open’.
Saving data to a model file does not cause any data to be changed in the Kingdom project
database.
Velocity Gradient
The rate of change of seismic velocity within a layer, often denoted by the symbol ‘K’. This
typically represents the increase of velocity with depth in a homogenous layer due to
compaction, and may be referred to as the compaction gradient.
The value of K for a layer may be derived using VelPAK’s ‘Curve’ and ‘Optimize’ modules if
well velocity data is present. The latter is recommended, especially if only limited well data is
available.
It is important to note that the value of K is unique to the velocity function being used. For
example, for the Slotnick equation K may typically be 0.000258 but for the Houston equation
K may be 0.00924 for the same rock mineralogy. Please refer to the VelPAK on-line Help
section ‘Velocity Function Parameter Ranges’ for more information.
See also Velocity Intercept and Instantaneous Velocity.
Velocity Intercept
The instantaneous velocity at the seismic datum, typically denoted by V0 or V0 (V-nought).

T
It is related to the instantaneous velocity by the commonly used model function:
where:
See also Velocity Gradient and Instantaneous Velocity.
Velocity Model
A set of geological surfaces, methods and parameters are used to create a velocity model.
Typically this will be in Surface Mode, where grids are used to define the geological structure,
but this may also be in Profile Mode, where horizon interpretations and fault sticks are used
to define the structure for any given vertical section. Methods are defined for each layer in the
structural model (e.g. V = Vo+ Kz), along with any associated parameters for that method.
Depth conversion of surfaces takes place in a top-down fashion, but to generate a complete
velocity volume, methods and parameters for every layer in the model need to be defined.
Velocity Volume Generation (VVG)

A velocity volume may only be generated once the velocity model has been completed. It is
generated using the Volume fly out on the Velocity module. Note that in current versions of
VelPAK, any values below the last event are assigned a value of zero, so in order to generate
a volume with no zero values below the deepest time of the last event, it is recommended to
introduce an event at or below the last time of the velocity volume required, and assign it a
constant interval velocity.
See also Diagnostic Mode.

W
W
Well Velocity
The velocity recorded from well data. VelPAK can use either a sonic log (which is
automatically converted from slowness to velocity on import into the model) or a Time-Depth
chart for each well. If using a sonic log, ideally it should be calibrated to check shot data. If
this data is not available, a crude calibration to a time constant (or structural grid) may be
made in the Well Module.

X-Y-Z
X-Y-Z
XYZ
Collections of values representing data in space. Each surface has a number of predefined
XYZ slots associated with it; these match the GridTypes. All XYZ data must exist within the
predefined slots.
By default, horizon data imported through the Link as XYZ data will be stored in the ‘Time’
slot in the Model Tree. You can move this data to another slot by right clicking in the ‘Time’
slot, selecting ‘Copy’, then right-clicking the destination slot and selecting ‘Paste’.
To generate grids in VelPAK, the input data must be XYZ data. Therefore, to regrid an
existing grid, the grid needs to be converted to XYZ points first. This is done on the XYZ fly
out of the surface module.

X-Y-Z

VelPAK User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VelPAK User Guide

Uploaded by

Copyright:

Available Formats

Energy Upstream

1401 Enclave Pkwy Ste 500

© 2018 IHS Markit™. All Rights Reserved. 3

4 © 2018 IHS Markit™. All Rights Reserved.

The DATA TYPES stored within a VelPAK model . . . . . . . . . . . . . . . . . . 29

The VelPAK Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Layout - docking and floating windows. . . . . . . . . . . . . . . . . . . . . . . . . . 49

Command Drop Down Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

© 2018 IHS Markit™. All Rights Reserved. 5

ToolBar 1 - Standard Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

ToolBar 2 - Module windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Surface and Slot Selection (“Surface&Slot”) . . . . . . . . . . . . . . . . . . . . . 75

Zoom and Pan Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Color Tables in VelPAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

VelPAK - The Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

The Wizard - for easy Depth Conversion . . . . . . . . . . . . . . . . . . . . . . . . 83

6 © 2018 IHS Markit™. All Rights Reserved.

Input / Output for VelPAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Import and Input into VelPAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Export and Output from VelPAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

© 2018 IHS Markit™. All Rights Reserved. 7

Scanit - a Stand-Alone Tool for re-formatting ASCII data . . . . . . . . . . . 137

Filters: Reformatting data imported to and exported from VelPAK . . . 139

Layer Tool Module (Advanced VelPAK use only) . . . . . . . . . . . 153

Introduction to Advanced Layer Module. . . . . . . . . . . . . . . . . . . . . . . . . 154

Horizontal Wells. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Steps to Using the Layer Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Inactive Tops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Extra Tops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Layer Module Panels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

8 © 2018 IHS Markit™. All Rights Reserved.

Applying the Layer Definition to the Well Module . . . . . . . . . . . . . . . . . 169

Profile Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Display Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Snap Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

© 2018 IHS Markit™. All Rights Reserved. 9

Reint Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Stuff Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Profile Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

XYZ Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Profile Edit Icons in Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

10 © 2018 IHS Markit™. All Rights Reserved.

Segment Edit Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Fault Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Fault Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Tips and Advise for producing Allan Diagrams . . . . . . . . . . . . . . . . . . . 265

© 2018 IHS Markit™. All Rights Reserved. 11

Introduction to Surface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Surface Edit Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

12 © 2018 IHS Markit™. All Rights Reserved.

Grid Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Process Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

© 2018 IHS Markit™. All Rights Reserved. 13

Depth Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

Trim Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384

Group Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

XYZ Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

Well Log Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

Introduction to Well Log Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

Well tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

Data tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399