You are on page 1of 410

Introduction to CPS-3

GeoFrame 4.031
November 6, 2002

GF4_CPS3_6Nov02.pdf www.geoquest.com
Copyright Notice

2002 Schlumberger. All rights reserved.

No part of this manual may be reproduced, stored in a retrieval system, or


translated in any form or by any means, electronic or mechanical, including
photocopying and recording, without the prior written permission of
GeoQuest, 5599 San Felipe, Suite 1700, Houston, TX 77056-2722.

Disclaimer

Use of this product is governed by the License Agreement. Schlumberger


makes no warranties, express, implied, or statutory, with respect to the product
described herein and disclaims without limitation any warranties of
merchantability or fitness for a particular purpose. Schlumberger reserves the
right to revise the information in this manual at any time without notice.

Trademark Information

GeoFrame, CPS-3 and certain other software applications mentioned in


this material are trademarks of Schlumberger.

All other products and product names are trademarks or registered trademarks
of their respective companies or organizations.
Schlumberger Contents

Contents

Chapter 1 . . . . . . . . . . . . . . . . . . . . . . . . About this Course


Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Training Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
How to Use the Training Guide . . . . . . . . . . . . . . . . . . . . . . 1-5
Common Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Typographic Conventions. . . . . . . . . . . . . . . . . . . . . . . . 1-7
Procedures and Exercises . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Exercise: Create a cross section . . . . . . . . . . . . . . . . . . . . . 1-9
Standard Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Chapter 2 . . . . Training Data - Inventory and Description


Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Volumetrics Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Data Inventory for GullFaks CPS-3 Training. . . . . . . . . . . . 2-3
Location Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Interpretation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Interval Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Lease Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Project Coordinate System Information . . . . . . . . . . . . . 2-7
Project Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Project Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Selected Fault Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Reservoir Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Chapter 3 Introduction to the GullFaks GeoFrame Project


Exercise: Start up GeoFrame and Prepare the Project . . . . 3-2
Startup the GullFaks Project . . . . . . . . . . . . . . . . . . . . . . 3-2
Enter General Data Manager to Inspect Database Organization
3-3

GeoFrame 4 Introduction to CPS-3 iii


Contents Schlumberger

Exercise: Set GeoFrame Display Units to Metric, and Verify


Coordinate System3-6
Review the Coordinate System for the Project . . . . . . . . 3-8
Exercise: Review Interpretation - Optional . . . . . . . . . . . 3-10
Exercise: Execute CPS-3 and Remove all Data Components from
the CPS-3 DSL3-11
Import Supplementary Data Files . . . . . . . . . . . . . . . . . 3-12
Setting Plotter Units . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Chapter 4 CPS-3 Menu Organization and Capabilities Overview


CPS-3 Main Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Main Module Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 4-2
X,Y Tracker Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Measuring Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Main Module Status Window . . . . . . . . . . . . . . . . . . . . . 4-6
UNIX Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
CPS-3 Map Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
CPS-3 Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
CPS-3 Color Palette Editor . . . . . . . . . . . . . . . . . . . . . . 4-11
CPS-3 Control Point Data Editor . . . . . . . . . . . . . . . . . 4-12
CPS-3 Set-Subset Reorganizer . . . . . . . . . . . . . . . . . . . 4-13
CPS-3 Map Layer Manager . . . . . . . . . . . . . . . . . . . . . 4-16
Menu Navigation by Topic . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Icon Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Chapter 5 . . . . . . . . . . . . . . . CPS-3/GeoFrame Integration


CPS Local Data Store (dsl) and GeoFrame Storage . . . . . . . 5-2
Controlling Where Sets are Stored or Retrieved. . . . . . . 5-2
Accessing Data in GeoFrame and IESX - Data Links . . . . . 5-3
Binary Data Links for CPS-3 . . . . . . . . . . . . . . . . . . . . . 5-3
How to access specific data types from CPS-3. . . . . . . . 5-3
Geoshare Links for Cartography. . . . . . . . . . . . . . . . . . . 5-4
Geographic Coordinate Systems. . . . . . . . . . . . . . . . . . . . . . 5-5
Rules of the Road for Automatic Coordinate System
Conversion in CPS-3 Sets. . . . . . . . . . . . . . . . . . . . . . . . 5-5
Enhancements in CPS-3 for GeoFrame 4.0 . . . . . . . . . . . . . 5-7

iv GeoFrame 4 Introduction to CPS-3


Contents Schlumberger

Enhancements in CPS-3 for GF4.0. . . . . . . . . . . . . . . . . 5-7


Examples of Macro Enhancements. . . . . . . . . . . . . . . . . 5-9

Chapter 6 . . . . . . . . . . . . Understanding CPS-3 Set Types


A Typical CPS partition in a GeoFrame Project. . . . . . . 6-1
Session Sets (or Session Files) . . . . . . . . . . . . . . . . . . . . 6-2
Data Sets (.dcps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Fault Sets (.fcps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Polygon Sets (.pcps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Surface Sets (.scps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Map Sets (.mcps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

Chapter 7 . . . . . . . . . . . . . . . . . . . . Loading Location Data


ASCII Input of Locations as Extended Data. . . . . . . . . . 7-1
Using GFLink for Seismic and Well Location data . . . . 7-2
Exercises: Loading Location Data . . . . . . . . . . . . . . . . . 7-2
Exercise: Loading 2D Locations from GeoFrame . . . . . . . 7-3
Exercise: Loading 2D Location Data from Ascii Files. . . . 7-5
Exercise: Displaying 3D Surveys in CPS-3 . . . . . . . . . . . 7-13
Exercise: Accessing 3D Locations from ASCII files . . . 7-15
Loading of ASCII surveys versus display in GF . . . . . 7-16
Exercise: Loading Well Locations and Well Paths . . . . . 7-17
Exercise: Check out the Statistics of the Sets Loaded . . . 7-20
Exercise: Verify the Data Just Loaded . . . . . . . . . . . . . . . 7-21

Chapter 8 . . . . .Set Selection, Creation, and Management


Exercise: Set Selection and Creation . . . . . . . . . . . . . . . . . 8-2
Listing Existing Sets/Editing Attributes . . . . . . . . . . . . . 8-2
Exercise: Specifying New Sets (Set Creation) . . . . . . . . . . 8-6
Copying Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Other Set Management Facilities . . . . . . . . . . . . . . . . . . 8-8
Exercise: Renaming, Deleting, and Viewing Statistics . . . 8-9
Renaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Viewing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Deleting Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

Chapter 9 Defining a Display Environment and Examining Data

v GeoFrame 4 Introduction to CPS-3


Contents Schlumberger

Coverage
Definition of Mapping Environment Components . . . . . . . . 9-3
Display Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Modeling Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
The Relationship between CPS-3 Modeling Environments and
GeoFrame Binsets (Grid Libraries) . . . . . . . . . . . . . . . . 9-4
More Notes on Binsets . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Making Use of Environments . . . . . . . . . . . . . . . . . . . . . 9-6
Multiple Environments . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Setting Up for Horizontal and Vertical Scaling/Limiting 9-9
Storing and Retrieving Environment Definitions . . . . . . 9-9
Rotated Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
Association of Environments with Sets . . . . . . . . . . . . 9-11
Specifying Display and Modeling Environments . . . . . 9-12
Exercises for the Display Environment . . . . . . . . . . . . 9-13
Exercise: Setting Standard Parameters . . . . . . . . . . . . . . . 9-14
Exercise: Define a Display Environment for the Basemap 9-15
Exercise: Enlarge the Display Environment Window . . . 9-20
Exercise: Redisplay the Three 3D survey locations . . . . . 9-21
Exercise: Preparing a Location Basemap . . . . . . . . . . . . . 9-22
Border, Labels, Scale Bar, and Title . . . . . . . . . . . . . . . 9-22
Display 3D Survey Locations . . . . . . . . . . . . . . . . . . . . 9-24
Display 2D Seismic Line Posting . . . . . . . . . . . . . . . . . 9-25
Move the Relative Position of a Map Layer . . . . . . . . . 9-26
Post Borehole Locations . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Post Bottom Hole Locations . . . . . . . . . . . . . . . . . . . . . 9-27
Save the Display as a Map Set . . . . . . . . . . . . . . . . . . . 9-28
View the Entire Basemap . . . . . . . . . . . . . . . . . . . . . . . 9-29
Create a Larger Display Environment . . . . . . . . . . . . . 9-29
Delete Old Display Environment . . . . . . . . . . . . . . . . . 9-30
Removing/Replacing Map Layers . . . . . . . . . . . . . . . . 9-30

Chapter 10 Accessing and Displaying Interpretation and Well Mark-


ers
Accessibility of Seismic Components by CPS-3 . . . . . 10-1

vi GeoFrame 4 Introduction to CPS-3


Contents Schlumberger

Gridding 3D interpretation . . . . . . . . . . . . . . . . . . . . . . 10-2


How do I distinguish an interpretation grid ? . . . . . . . . 10-2
Interpretation Models and CPS-3 . . . . . . . . . . . . . . . . . 10-3
Destinations of Imported Interpretation Components . 10-4
Exerises for Data Retreival . . . . . . . . . . . . . . . . . . . . . . 10-5
Exercise: Locate 3D Seismic Horizon Interpretation and
Associated Fault Boundaries10-6
Exercise: Load Well Markers with GFLink . . . . . . . . . . . 10-9
Exercise: Well markers as scatter sets . . . . . . . . . . . . . . 10-12
Exercise: Summary o Interpretation Data Available . . . 10-13
Exercise: Examine Data Statistics . . . . . . . . . . . . . . . . . 10-14
Exercise: Rename faults, and remove z-values . . . . . . . 10-17
Exercise: View Data Sets before Gridding . . . . . . . . . . . 10-20
Bunnkritt Interpretation Grid Set . . . . . . . . . . . . . . . . 10-20
Tarbert Interpretation Grid Set . . . . . . . . . . . . . . . . . . 10-22
Ness Interpretation Grid . . . . . . . . . . . . . . . . . . . . . . . 10-23
Rannoch and Drake Interpretation Grids . . . . . . . . . . 10-24

Chapter 11 . . . . . . . . . . . . . . . . . . . .Gridding Fundamentals


What is Gridding? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Judging the Quality of the Grid . . . . . . . . . . . . . . . . . . 11-3
Gridding Algorithms. . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
How Do I Prepare for Gridding? . . . . . . . . . . . . . . . . . 11-4
How Do I Choose A Gridding Algorithm?. . . . . . . . . . 11-6
List of CPS-3 Gridding Algorithms . . . . . . . . . . . . . . . 11-7
How Do I Set Gridding Parameters? . . . . . . . . . . . . . . 11-9
Common Gridding Problems and Their Solutions . . . 11-10
How Do Fault Traces Affect Gridding? . . . . . . . . . . . 11-10
Gridding Decisions - 2D/3D Seismic Examples. . . . . 11-12
Importance of Fault Zone Definition During Gridding 11-15
Techniques for Filling in Fault Zones. . . . . . . . . . . . . 11-16
Contour Visibility in Fault Zones . . . . . . . . . . . . . . . . 11-17

Chapter 12 . . . . . . . . . . . . . . . . CPS-3 Gridding Parameters


Selecting the Grid Spacing . . . . . . . . . . . . . . . . . . . . . . 12-2
Simple Guidelines for Choosing SNAP/CONVERGENT

vii GeoFrame 4 Introduction to CPS-3


Contents Schlumberger

parameters for Seismic data . . . . . . . . . . . . . . . . . . . . 12-10


Defining the Fault Zone in a Horizon - Yes or No . . . 12-11
When Are Fault Surfaces Needed? . . . . . . . . . . . . . . . 12-13

Chapter 13 Set Modeling Environment and Compute Horizon Grids


Exercise: Define Modeling Environment . . . . . . . . . . . . . 13-3
Exercise: Gridding the Horizons. . . . . . . . . . . . . . . . . . . . 13-7
Grid the Bunnkritt Unconformity . . . . . . . . . . . . . . . . . 13-7
Grid the Tarbert Horizon . . . . . . . . . . . . . . . . . . . . . . 13-14
Grid the Ness Horizon . . . . . . . . . . . . . . . . . . . . . . . . 13-24

Chapter 14 Contouring, Colorshading, and More Basemapping


Understanding Graphic Size and Resolution Parameters:
Text/Symbol Size, Map Scale, Contour Quality. . . . . . . . . 14-2
Time of Execution for Contour Generation . . . . . . . . . 14-4
Guidelines to Optimize Contouring Speed . . . . . . . . . . 14-5
Exercise: Understanding Graphic Size Parameters . . . . . 14-6
Exercise: Contouring a Single Z-value. . . . . . . . . . . . . . 14-10
Color Shaded Contours . . . . . . . . . . . . . . . . . . . . . . . . 14-11
Make Room for a Color Bar . . . . . . . . . . . . . . . . . . . . 14-13
Display the Color Bar . . . . . . . . . . . . . . . . . . . . . . . . . 14-14
Exercise: More Basemapping . . . . . . . . . . . . . . . . . . . . . 14-15
Return to GullFaks_Overview Display Environment. 14-15

Chapter 15 Demonstrate Inverse Interpolation and Control Point


Arithmetic
Display Ness_tops. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Exercise: Compare Ness Grid and Ness_tops Data Set . . . . 24
Use Inverse Interpolation to Store Grid Value . . . . . . . . . 24
Use Control Point Arithmetic to Compute Difference . . . 26

Chapter 16 . . . . . . . . . . . . . . . . . . Fault Surface Operations


Creating Fault Surfaces. . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Predefined Techniques for Fault Surface Gridding . . . 16-3
GullFaks Fault Patterns. . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Exercise: Load Fault Segments (Cuts) . . . . . . . . . . . . . . . 16-7
Exercise: Inspect Fault Data Points and Create Fault Grids16-8

viii GeoFrame 4 Introduction to CPS-3


Schlumberger Contents

Creating the fault grids . . . . . . . . . . . . . . . . . . . . . . . . . 16-8


Exercise: Run the Fault Gridding Macro . . . . . . . . . . . . 16-10
Establishing Set Attributes for the Fault Surfaces . . . 16-12

Chapter 17 Visualizing Relationships Among Surfaces with Cross-


Sections
Exercise: Determine If Ness and Tarbert Cross . . . . . . . . 17-2
Use Multiple Surface Arithmetic Operations to Subtract the
Grids, then Display Overlapping Areas . . . . . . . . . . . . 17-2
Conform the Ness Grid to the Tarbert Grid Where They
Overlap
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
Exercise: ExamineRelationshipsamongHorizonsandSealingFaults
17-6
Digitize Profile Baselines . . . . . . . . . . . . . . . . . . . . . . . 17-6
Establish Z-scale Attributes in the Display Environment17-8
Create Profile Displays . . . . . . . . . . . . . . . . . . . . . . . . . 17-9

Chapter 18 . . . . . . . . . . . . . Creating a Volumetric Envelope


RecommendedSequenceforComputinganIsochoreforVolumetrics
18-2
Location of the Zero Line in Isochores. . . . . . . . . . . . . 18-3
Accounting for Non-vertical Fault Discontinuities in the
Volumetric Isochore . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Example of Creating a Structural Envelope . . . . . . . . . 18-6

Chapter 19 Prepare the Tarbert/Ness Envelopes and Create the


Gross Isochore
Exercise: Create Top of Envelope for Tarbert/Ness Interval193
Create 2200m and 2100 m Fluid Contact Grids . . . . . . . 193
Create Top Envelope. . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Create Base Envelope . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Prepare the Fault Traces for the Gross Thickness Grid 1910

Chapter 20 Applying Reservoir Properties to the Gross_Isochore for


Oil in Place
Origin of property data used by CPS-3. . . . . . . . . . . . . 20-2
Quality and Characteristics of Property Grids . . . . . . . 20-4

GeoFrame 4 Introduction to CPS-3 ix


Contents Schlumberger

Continuing with the OIP Equation . . . . . . . . . . . . . . . . 20-6


Computing Oil in Place with Volumetrics . . . . . . . . . . 20-7
Exercises for Oil in Place Calculations. . . . . . . . . . . . . 20-9
Exercise: Load Zone Properties from GeoFrame . . . . . . 20-10
Exercise: Create Property Grids . . . . . . . . . . . . . . . . . . . 20-12
Determine Initial Grid Interval and Algorithm. . . . . . 20-12
Quick Property Gridding. . . . . . . . . . . . . . . . . . . . . . . 20-13
The Sparse Data Problem - A Technique . . . . . . . . . 20-14
Grid the Property Data . . . . . . . . . . . . . . . . . . . . . . . . 20-16
Exercise: Apply Property Grids to Gross_Isochore . . . . 20-20
Compute Net_Isochore Grid . . . . . . . . . . . . . . . . . . . . 20-21
Compute Net Pore Volume Grid. . . . . . . . . . . . . . . . . 20-22
Compute Net Pay Grid . . . . . . . . . . . . . . . . . . . . . . . . 20-23
Verify Net Pay Grid . . . . . . . . . . . . . . . . . . . . . . . . . . 20-25
Fault Boundaries and Grid-to-grid operations . . . . . . 20-26
Exercise: Lease Blocks from ASCII Files . . . . . . . . . . . 20-27
Load the Polygon File of Leases. . . . . . . . . . . . . . . . . 20-28
Display the Polygons . . . . . . . . . . . . . . . . . . . . . . . . . 20-29
Exercise: Computing Oil In Place . . . . . . . . . . . . . . . . . 20-32

Chapter 21 . . . . . . . . . . . . . . . . . . . . . . . . . Editing Exercises


Model Editor Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Starting the Model Editor . . . . . . . . . . . . . . . . . . . . . . . 21-3
Model Editor functions . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Typical Editor session. . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Tips Regarding Grid Editing. . . . . . . . . . . . . . . . . . . . . 21-6
Exercise: Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7
Overview of the CPS-3 Map Editor . . . . . . . . . . . . . . . . . . 21-8
Starting the Map Editor. . . . . . . . . . . . . . . . . . . . . . . . . 21-9
Pull-down menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-10
Exercise: Map Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-14
Exercise: Color Palette Editor. . . . . . . . . . . . . . . . . . . . . 21-15
Basic Facts - 127 and 256 Color Limits . . . . . . . . . . . 21-15

x GeoFrame 4 Introduction to CPS-3


Schlumberger Contents

Chapter 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . CPS-3 Macros


Basic Macro Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Creating Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Running Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
Making a Macro Universally Useful. . . . . . . . . . . . . . . 22-3
Current Constraints: Macros and Environments. . . . . . 22-8
Compatibility: Running Pre-GF3.5 Macros . . . . . . . . . 22-9
Managing Macros - Enhancements for GF4.0 . . . . . . . 22-9

Chapter 23 . . . . . . . . . . . . . . . Graphic Operations in CPS-3


Graphic Display in CPS . . . . . . . . . . . . . . . . . . . . . . . . 23-1
Honoring the Active Display Environment . . . . . . . . . 23-2
When Are Graphic Objects Clipped? . . . . . . . . . . . . . . 23-3

Chapter 24 . . . . . . . . . . . . . . . . . . . . . . . CPS-3 Ascii Loader


General Requirements/Options. . . . . . . . . . . . . . . . . . . 24-2
Defining Subsets During Loading . . . . . . . . . . . . . . . . 24-2
Extended and Non-Extended Data Sets . . . . . . . . . . . . 24-6
Examples of File Formats . . . . . . . . . . . . . . . . . . . . . . . 24-7
Data Transformations . . . . . . . . . . . . . . . . . . . . . . . . . 24-11

Chapter 25 . . . . . . . . . . . . Convergent Algorithm Overview


Iterative Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2
Blending Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-3

Chapter 26 . . . . . . . . . . . . . . . . Glossary of Mapping Terms

GeoFrame 4 Introduction to CPS-3 xi


Contents Schlumberger

xii GeoFrame 4 Introduction to CPS-3


Chapter 1
About this Course

Overview
This course is a comprehensive introduction to the CPS-3 software system
and designed for GeoFrame 4. The user learns about project preparation,
internal data storage conventions, as well as the basics of data flows between
other applications such as IESX, Charisma, WellPix, and ResSum.

This course has a specific workflow which begins with data import and ends
with the computation of oil in place with the CPS-3 Volumetric procedure. In
between, all basic mapping operations are exercised, including basemapping,
gridding, contouring, profiling, surface operations, data operations, utilities,
map editing, model editing, and more.

This course makes use of a fully populated GeoFrame project to provide data
for the workflow. Some ASCII files are used as well.

The emphasis for this course is to provide a solid overview of the operations
involved in computer modeling and basemapping. Although this course is
oriented toward beginning users, it is also recommended for those already
conversant with computer modeling who wish to learn the specifics of CPS-3.

GeoFrame 4.0 Introduction to CPS-3 Chapter 1 - 1


About this Course Schlumberger

Course Objectives
After completing this course, you will be able to:
Access data which has been created by GeoFrame, Charisma, IESX,
WellPix, ResSum, and others.
Access/display well locations, well paths, and markers.
Access/display 2D and 3D navigation data.
Access/display 2D/3D interpretation, and fault boundaries.
Access/display property data.
Create basemaps.
Load and display ASCII extended data.
Understand how to choose gridding parameters for a range of data
distribution types.
Generate grids from data sets.
Create displays of geologically faulted grid models, including color-
shaded contour maps.
Perform surface logic and math operations; perform z-field arithmetic.
Generate structural envelopes.
Fetch property averages from GeoFrame and make property grids.
Apply property grids to gross rock thickness and perform volume
calculations.
Write, execute, and edit macros.
Edit surfaces, faults, and data with the Model Editor.
Create custom palettes with the Color Palette Editor.
Perform simple map editing.

Chapter 1 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger About this Course

Training Workflow

About the course, training data, and project set up


Lesson 1 - Find out about this Course and the current Release.
Lesson 2 - Learn about the training data.
Lesson 3 - Open GullFaks training project.

About CPS-3 in general, integration issues, CPS-3-specific sets


Lesson 4 - Learn the overall capabilities of CPS-3. Learn to use a
simple How_To table for menu navigation.
Lesson 5 - Review conceptual changes in CPS-3 for GeoFrame 4
integration; Learn about Environments
Lesson 6 - Learn how CPS-3 internal data sets are organized

Getting data into CPS-3 and how to manage it


Lesson 7 - Learn about accessing GeoFrame 4 data from CPS-3; load
seismic and well location data.
Lesson 8 - Learn to select, create, and manage sets in CPS-3

Looking at location data - load data and do simple basemapping


Lesson 9 - Learn about environments. Define display environment and
examine data locations

Loading horizon data - introduction to gridding procedures


Lesson 10 - Load seismic horizon interpretation, well tops, and fault
segments
Lesson 11 - Learn about the fundamentals of gridding
Lesson 12 - Apply gridding principles to GullFaks data, learn more
about gridding parameters
Lesson 13 - Establish modeling environment and grid the Gullfaks
data; learn the basics of contouring and display

More about basemapping, map composition


Lesson 14 - Learn more about contouring, color-shading basemapping

Control point operations


Lesson 15 - Perform inverse interpolation and do control point
operations to compute grid error at wells.

GeoFrame 4.0 Introduction to CPS-3 Chapter 1 - 3


About this Course Schlumberger

Introduction to volumetric envelopes, properties, OIP


Lesson 16 - Learn faulting conventions, create fault grids for envelopes
Lesson 17 - Managing crossing surfaces, visualizing relationships;
cross sections
Lesson 18 - Learn about volumetrics and isochores
Lesson 19 - Prepare the top and base envelopes; compute gross
isochore grid
Lesson 20 - Fetch and grid property data; compute volumetric grids,
compute OIP

Interactive Editors in CPS-3


Lesson 21 - Introduction to interactive editing models in CPS-3 -
Model Editor, Color Palette Editor, Map Editor

Miscellaneous Topics with no Exercises


Lesson 22 - Introduction to Macros
Lesson 23 - Graphic Operations in CPS-3
Lesson 24 - Learn how to format data for the CPS-3 Ascii Loader
Lesson 25 - A brief overview of the Convergent gridding algorithm
Lesson 26 - A glossary of mapping terminology

Chapter 1 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger About this Course

How to Use the Training Guide


Certain conventions in this guide make it easier to use. The following sections
describe the conventions used throughout the training guide.

Common Commands
The following table describes the most common commands you will
encounter throughout the exercise and training guides.
.

Command Generally Refers to Action Required Example


Click Buttons or objects in a Position the cursor over the Click Start.
window or dialog box button or object and click the
left mouse button once.

Right click Right Mouse Button Position the mouse cursor Right click the Field
(MB3) over a button or other area of icon to open the
a window, and click the right Insert Structure
mouse button. dialog box.

Double-click Items in a window or Position the cursor over the Double-click the
dialog box item and click the left mouse location name to
button twice rapidly. open the Location
Editor.

Drag Cursor 1. Position the mouse Drag the cursor from


cursor over a specified 7000 to 7500 feet.
area of a window.
2. Press and hold the left
mouse button.
3. Drag the cursor to
another area of the
window.

Enter Text fields 1. Position the cursor over Enter the item
the text field. number.
2. Click the left mouse
button once to activate
the field.
3. Type the desired text.

Open Windows and dialog Select the appropriate menu Open the Print
boxes option or click the appropriate window.
button or object to display the
designated window.
Press Keys on the physical Press the designated key. Press F9.
keyboard

GeoFrame 4.0 Introduction to CPS-3 Chapter 1 - 5


About this Course Schlumberger

Command Generally Refers to Action Required Example


Select Menus and menu 1. Position the cursor over Select File > New.
items in a window the menu.
2. Click the left mouse
button once. A drop list
appears.
3. Move the cursor to the
desired menu item.
4. Click the left mouse
button once.

Select Drop lists 1. Position the cursor over Select a location from
the arrow to the left of the the drop list.
drop list field.
2. Click the left mouse
button once on the arrow
to display the drop list
items.
3. Move the cursor over the
item to be selected. Click
the left mouse button
once to select the item.

Type Entries Text fields 1. Position the cursor over 1. Type the path
(An entry to be typed the text field. and file name in
appears in bold 2. Click the left mouse the Database
courier font). button once to activate field.
the field. 2. Enter MARG for
3. Type the desired text. Formation top.
3. Type SECTION 1
in the Name field.

Chapter 1 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger About this Course

Typographic Conventions
The following table lists the special formatting you will encounter throughout
the training and exercise guides.

Item Shown As Description Example


Important Italic text Highlights important Always enter the date
Information information within the in the format MM-DD-
text YY.

Typed Entries Bold text, courier font Indicates the specific Type 112298 in the
information you must Date field.
type into a field or
command line

Buttons, menu Bold text Highlights items on the 1. Click OK.


and menu window or buttons on 2. Select File > New.
item names, the keyboard with which
keyboard keys you must interact 3. Press Tab.

Mouse Keyboard key name(s) Indicates the 1. Press <Alt><F4>.


command and/or mouse combination of 2. Control-click
and/or key command separated keyboard keys or mouse WELL-O and
combinations by a hyphen action and keyboard key WELL-K.
you must perform
Menus and Menu names and Indicates the sequence Select XSection >
Menu Items menu item name(s) of menu names and Create in the Prospect
separated by an arrow menu item(s) the user window.
(>) must select
File names, Bold text, Courier font Highlights system 1. If you receive the
System messages or text that error Database
Messages and appears in a window not found,
Screen Text contact the system
administrator.
2. Exported files are
stored in a user
specified directory
with a user
specified name
and a .pbf
extension
(PowerPlan
Backup File).

System Bold text, Courier font Highlights system If you receive the error
Messages/ messages or text that Database not
Screen Text appears on a window found, contact the
system administrator.

GeoFrame 4.0 Introduction to CPS-3 Chapter 1 - 7


About this Course Schlumberger

Item Shown As Description Example


Caution Text displayed in a A statement to proceed
highlighted box cautiously and avoid
preceded by the word conditions that, if Caution: Take care in
Caution. unheeded, may applying spatially
adversely affect a varying static misties
procedure function or because they can cause
data. Less severe than false structures to
Warning appear in the seismic
section.

Warning Text displayed in a A statement of


highlighted box information to avoid
preceded by the word conditions that, if Warning: You must
Warning. unheeded, will enter an end date that is
adversely affect a later than the start date
procedure, function, or to correctly calculate the
data. More severe than duration.
Caution

Note Italic font, preceded by Provides supplemental


the Illustrated graphic information
symbol and the word Note: Clicking List
Note Summary displays only
the item names.

Tip Italic font, preceded by Provides helpful


the Illustrated graphic suggestions. Often used
symbol and the word in Exercises. Tip: If the user cant tell
Tip the difference between
shading on or off, zoom
in to see the seismic
more clearly.

Best Practice Italic font, preceded by Provides guide to


the Illustrated graphic efficient work flow.

symbol and the words Best Practice: The
Best Practice basemap will look less
cluttered if only one zone
per layer is posted.

Buttons, Noted in bold type. Highlights specific Click OK.


Dialog box window and field names Open the Create
and Window dialog box.
titles, Field Select the Edit option.
Names, and
menu options.

Chapter 1 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger About this Course

Procedures and Exercises


The training guide contains high-level procedures for various tasks. The
exercise guide contains exercises that list specific steps for you to perform and
specific data to enter.

Procedures

Procedures appear in a procedure table as shown below. Notice that


procedures contain general steps and do not contain data to select or enter.

Exercises

Exercises are introduced by a description of the steps to follow, as shown in


the example below. The steps appear in a numbered list of specific actions to
take and data for you to select or enter.

Exercise

Create a cross section

1. Select XSection > Create in the Prospect window.

2. Type SECTION 1 in the Name field.

3. Click OK to confirm the entry and close the XSection Create dialog box.

GeoFrame 4.0 Introduction to CPS-3 Chapter 1 - 9


About this Course Schlumberger

Standard Buttons
Use command bar buttons to inform the system that an action or command is
complete. All dialog boxes contain one or more of the following buttons:
OK applies the current settings and closes dialog box
Apply applies the current settings
Reset clears any changes or entries in the dialog box without saving
any information
Default restores the settings/information in the dialog box to the
system default
Cancel cancels any unsaved changes and closes dialog box
Close closes dialog box
Help displays help on the currently-active dialog box.

Chapter 1 - 10 GeoFrame 4.0 Introduction to CPS-3


Chapter 2
Training Data - Inventory and
Description

Overview
In this chapter, well make an inventory of data in the GeoFrame GullFaks
project which is used by this class.

The GullFaks field is well-documented and information on this field is


available via the Schlumberger intranet.

This course uses only some of the data available in the project and includes

Well top locations, bottom locations, and well paths


Geologic markers
3D seismic interpretation, both horizons and fault segments
Fault boundaries
Layer-based net, gross, porosity and saturation averages

Other data used in the class includes


2D seismic line data from ASCII files
Lease block polygon data from ASCII files

Velocity functions have been provided for the seismic cube, so that both
seismic and well data are available in time and depth. In this training course,
we will use depth data.

GeoFrame 4.0 Introduction to CPS-3 Chapter 2 - 1


Training Data - Inventory and Description Schlumberger

Table 2.1- Seismic Horizon Data and Geological Marker Names


Geological Seismic Horizon CPS Fault Interpretation Density /
Marker in in IESX Horizon Poly Description
GeoFrame Name
BUNNKRITT BUNNKRITT Bunnkritt no unfaulted/asap(1X1)

TARBERT TARBERT Tarbert yes sparse (20X20)

NESS NESS Ness yes dense/2d3d + asap (1.x1)

RANNOCH RANNOCH Rannoch no sparse (20x20)

DRAKE DRAKE Drake no dense (1x1)

Naming Conventions
Be aware that since projects can be shared by several persons in different
disciplines, different names for different versions of interpretation, names of
GeoFrame containers, marker names, and the like must be coordinated
among those working in the project.

Volumetrics Notes
In this class, we will compute volume between the Tarbert and the Ness
horizons. Because of large erosion zones in the Tarbert caused by the Bunkritt
unconformity, the top of the reservoir must be a merging of the Tarbert and the
unconformity.

Most of the data for this course will come from the GeoFrame data base.
There will be several methods for gaining access to it from CPS-3. In addition,
some of the data will come from outside of the project. Regardless of its
origin, the next section provides an inventory of the data sets which will be
used in CPS-3 for this course.

Chapter 2 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Training Data - Inventory and Description

Data Inventory for GullFaks CPS-3 Training

Location Data

2D Locations
mm_2d_gullfaks_shtpt.dat (ASCII)

3D Locations
mm_3d_85acip_survey
mm_3d_g1_survey
mm_3d_offset_survey

Well Top Locations


mm_Well_Locations_wtloc

Well Bottom Locations


mm_Well_Locations_wbloc

Well Paths
mm_Boreholes_Depth_wpath

Interpretation

Horizons/Fault Polygon Sets (Time)

BUNKRITT
BUNKRITT_time_intrp

TARBERT
TARBERT_time_intrp
TARBERT_time_intrp_fpolys

NESS
NESS_time_intrp
NESS_time_intrp_fpolys

RANNOCH
RANNOCH_time_intrp
RANNOCH_time_intrp_fpolys

GeoFrame 4.0 Introduction to CPS-3 Chapter 2 - 3


Training Data - Inventory and Description Schlumberger

DRAKE
DRAKE_time_intrp
DRAKE_time_intrp_fpolys

Horizons/Fault Polygon Sets (Depth)

BUNKRITT
mm_BUNNKRITT-1_BU-285_Depth_intrp

TARBERT
mm_TARBERT_smooth_Depth_intrp
mm_Tarbert

NESS
mm_NESS_smooth_Depth_intrp
mm_Ness

RANNOCH
mm_RANNOCH_smooth_Depth_intrp

DRAKE
mm_DRAKE_smooth_Depth_intrp

Fault Segments (Time)


F2...etc...
F2a
F3
F4
F5
F6
F6a
F7
F7a
F8
F9
F11
F12
F13
F14

Chapter 2 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Training Data - Inventory and Description

F15
F15a
F16
F17
F18
F19
F20
F21

Fault Segments (Depth)


mm_F2_Depth_fsegs
mm_F2a_Depth_fsegs
mm_F3_Depth_fsegs
mm_F4_Depth_fsegs
mm_F5_Depth_fsegs
mm_F6_Depth_fsegs
mm_F6a_Depth_fsegs
mm_F7_Depth_fsegs
mm_F7a_Depth_fsegs
mm_F14_Depth_fsegs
mm_F15_Depth_fsegs
mm_F15a_Depth_fsegs
mm_F16_Depth_fsegs
mm_F17_Depth_fsegs
mm_F18_Depth_fsegs
mm_F20_Depth_fsegs
mm_F21_Depth_fsegs

GeoFrame 4.0 Introduction to CPS-3 Chapter 2 - 5


Training Data - Inventory and Description Schlumberger

Well Marker Sets (Depth)


mm_BUNNKRITT_Depth_wmrkr
mm_TARBERT_Depth_wmrkr
mm_NESS_Depth_wmrkr
mm_RANNOCH_Depth_wmrkr
mm_DRAKE_Depth_wmrkr

Well Marker Sets (Time)


BUNNKRITT_Time_wmrkr
TARBERT_Time_wmrkr
NESS_Time_wmrkr
RANNOCH_Time_wmrkr

Interval Definitions

Zone Versions
(none at present)

Zones
(none at present)

Properties

Net-to-Gross Thickness (Data set)


mm_TARBERT_NESS_net-gross

Net Pay Porosity (Data set)


mm_TARBERT_NESS_Porosity

Net Pay Water Saturation (Data set)


mm_TARBERT_NESS_WSat

Lease Information

Lease polygons
mm_north_leases.ply (ascii)
mm_North_Leases

Chapter 2 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Training Data - Inventory and Description

Project Coordinate System Information


Datum: European 1950, Norway and Finland
Ellipsoid: International 1924
Projection: UTM, Zone 31, CM = 3.0
Hemisphere: Northern

Project Units
Metric

Project Location
North Sea

Figure 2.1 GullFaks Fault Patterns and 3D survey

GeoFrame 4.0 Introduction to CPS-3 Chapter 2 - 7


Training Data - Inventory and Description Schlumberger

Above, you can see fault patterns over the area as well as the limits of the 3D
survey in black. Two platforms are the source of many well trajectories
shown in red. The white dotted rectangle shows the approximate interpretation
coverage of the highest of the horizons - the Tarbert. Subsequently lower
horizons will cover more and more area towards the East. Well coverage for
the higher horizons such as the Tarbert are restricted to the lower SE quadrant
of the dotted rectangle

The interpretation for the upper unconformity (Bunnkritt) covers all of the 3D
rectangular area except for a small portion in the NW corner.

The figure below shows a smaller area which is focused on the extent of the
well paths. The Bunkritt interpretation is in white, and covers just about all the
3D survey. The Tarbert interpretation is shown in grey and covers only the
Western half. The Eastern platform has more and better distributed wells, but
does not overlap with the best seismic.

Figure 2.2 Well paths, Bunkritt interpretation, and Tarbert interpretation

Chapter 2 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Training Data - Inventory and Description

Selected Fault Patterns


For purposes of the CPS-3 training, we will use only the larger faults as shown
below.

GeoFrame 4.0 Introduction to CPS-3 Chapter 2 - 9


Training Data - Inventory and Description Schlumberger

Reservoir Geometry
The area of the GullFaks field which we will be mapping consists of a series
of tilted fault blocks with several of the upper horizons of the group, for
example, the Tarbert, containing erosion zones where no interpretation exists
above the Bunnkritt unconformity.

Bunkritt
Tarbert

Ness

Figure 2.3 Reservoir profile displaying the stratigraphic relationship of the


horizons

Chapter 2 - 10 GeoFrame 4.0 Introduction to CPS-3


Chapter 3
Introduction to the GullFaks GeoFrame
Project

OverView
In this chapter, we will inspect existing data in the training project, making
sure that it is prepared for the exercises.

GeoFrame 4.0 Introduction to CPS-3 Chapter 3 - 1


Introduction to the GullFaks GeoFrame Project Schlumberger

Exercise

Start up GeoFrame and Prepare the Project

In this exercise, we will introduce you to the GullFaks project and follow this
basic workflow:
Start GeoFrame from the Geonet menus and enter the name of the
project which the instructor will specify.
Invoke the General Data Manager to review the organization of the
existing data.
Review the coordinate system chosen for the project and set the
GeoFrame display units for Z to milliseconds.
Invoke IESX Basemapping and Seis2D/3D to view the interpreted
horizons and fault segments which will be imported into CPS-3.
Invoke CPS-3. Clear out the internal storage area.
Load external data required for this course.

Startup the GullFaks Project


1. Click GeoFrame 4 in the Geonet menu, and hold down the left mouse
button (MB1).

2. Continue holding down MB1, slide the cursor to GeoFrame and


release the button.

3. From your instructor, determine the name of the project you require,
and when the GeoFrame Login window appears, highlight the desired
project in the project list, move the cursor to the Password box and
click the middle mouse button (MB2), and then click Connect (with
MB1).

4. When the Application Manager (icon at the bottom of the Project


Manager window) becomes active no longer grayed-out, click on it.

Chapter 3 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Introduction to the GullFaks GeoFrame Project

Enter General Data Manager to Inspect Database


Organization
In this exercise, it is very important that you do not DELETE any item or
object as you view the contents of your project.

1. In the Application Manager dialog box, under Managers, click the


Data icon to open the Data Management Catalog window.

2. From the Data Management Catalog, click on Data Managers, then


double-click on General.

3. When the Data Manager comes up, place the cursor on the project
icon.

Figure 3.1 Project icon located in Data Manager window

4. Hold down the right mouse button (MB3), moving to Expand By


Type, then Horizon and release the button. (See figure below.)

GeoFrame 4.0 Introduction to CPS-3 Chapter 3 - 3


Introduction to the GullFaks GeoFrame Project Schlumberger

Figure 3.2 Expanded project node displaying partial horizon list

5. Place the cursor on one of the horizons, such as DRAKE, and press
MB1 to select it, then with the cursor still on DRAKE, press MB3.

6. Continue holding down MB3, move over to Expand by Type, then to


Grid and release the button. This reveals all grids associated with the
DRAKE horizon, or container.

Chapter 3 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Introduction to the GullFaks GeoFrame Project

Each of the Horizon containers may have been created by any one of the
numerous GeoFrame applications - IESX or Charisma during interpretation,
Stratlog or WellPix during geological interpretation, or CPS-3 during
mapping.

Below, we see the resulting hierarchical relationship when we expand the


project by field and one of the fields by well.

Figure 3.3 Hierarchical relationship between project, field, and wells

7. Click File > Close, then back in the Data Management Catalog, click
Cancel.

GeoFrame 4.0 Introduction to CPS-3 Chapter 3 - 5


Introduction to the GullFaks GeoFrame Project Schlumberger

Exercise

Set GeoFrame Display Units to Metric, and Verify


Coordinate System

1. In the Project Management folder of the Project Management


dialog box (Figure 3.4), click Edit to open the Project Parameters
dialog box.

Figure 3.4 Project Manager displaying the Project Management folder

Chapter 3 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Introduction to the GullFaks GeoFrame Project

Figure 3.5 Unit/Coordinate System menu

2. In the Project Parameter dialog box, under Unit/Coordinate


System, click the Display tab, and click Set Units. This opens the Set
Units dialog box, shown below.

Figure 3.6 Set Units dialog box

3. In the Set Units dialog box, pick the Unit classification name
Metric/Charisma, or Metric if the first is not available, and click
Inspect. This opens the Unit System dialog box, shown below.

Figure 3.7 Dialog boxes to set measurement of project data

GeoFrame 4.0 Introduction to CPS-3 Chapter 3 - 7


Introduction to the GullFaks GeoFrame Project Schlumberger

4. Scroll down to Geographic Distance, under the Measurement


column, and verify that its unit is m (representing meters). If not, click
the button under the Unit column, changing the units to m, which is
found toward the bottom of the Available Units dialog box. Click OK

5. Verify also that Length is m (meters), as well as Standard Depth


Index. If not, change the measurement as you did above.

6. Back in the Unit System dialog box, Cancel if no changes were made,
or click Save As and type in a new unit system name suffix, ms, and
click OK.

Review the Coordinate System for the Project


1. From the Edit Project Parameters dialog box, click the Display tab
under Unit/Coordinate System again, and click Set Projection on the
right.

2. Highlight any Coordinate System seen in the dialog and click the blue
i icon to see its definition. You want to select any of the coordinate
systems which have the following definition:
Datum: European 1950, Norway & Finland
Ellipsoid: Int24
Projection: UTM
UTM Zone: 31
Hemisphere: Northern Tg
as seen in the Edit Dialog.


Note: Do NOT change anything in this dialog box.

Chapter 3 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Introduction to the GullFaks GeoFrame Project

Figure 3.8 View Coordinate System dialog box

3. Click Cancel back to the Project Management dialog box which you
may then iconize. We will be using it again.

GeoFrame 4.0 Introduction to CPS-3 Chapter 3 - 9


Introduction to the GullFaks GeoFrame Project Schlumberger

Exercise

Review Interpretation - Optional

The next exercise is for those of you who want to look at the interpreted
horizons, fault boundaries, and fault segments which have been interpreted in
IESX or Charisma which will be mapped in this course. You may skip this
brief exercise if you wish. The intent is only to demonstrate the source of the
data which we will access from CPS-3 in the next few chapters. Those of you
who are IESX or Charisma users can take a moment to verify the presence of
the horizons and other data outlined in the previous chapter describing the
GullFaks project.


Note: Note that in early versions of this training course project, this exercise is not
possible.

Chapter 3 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Introduction to the GullFaks GeoFrame Project

Exercise

Execute CPS-3 and Remove all Data Components from


the CPS-3 DSL

In this exercise, we will bring up CPS-3 and remove all sets in the CPS-3
storage area in anticipation of loading auxiliary data for the course. This
operation affects nothing in the GeoFrame data base itself.

1. Bring up the Visualization Catalog from the GeoFrame Application


Manager, and click CPS-3 to reveal the Main Module application.

2. Highlight the Main Module application by clicking on it once.

3. Lower down, on the Display line, verify which workstation you want
the application to run on - 0.1 is right and 0.0 is left. After typing
in the desired location, click OK. This should bring up the Main
Module canvas:

Figure 3.9 CPS-3 Main Module

GeoFrame 4.0 Introduction to CPS-3 Chapter 3 - 11


Introduction to the GullFaks GeoFrame Project Schlumberger

4. Starting at the top menu bar in the CPS-3 Main Module, click
Utilities > Sets > List_Manage_Sets.

5. Sets marked as CPS are stored in the CPS-3 dsl, sets marked as
GeoFrame are stored in the GeoFrame database. We do not want to
delete any sets from the GeoFrame data base.

6. Toggle on All in the Set Type, Surface Type, and Property boxes,
changing them to red. Toggle only CPS in the Storage box

7. Click the Filter button at the bottom and VERIFY THAT ONLY
CPS3 IS TOGGLED ON WITHIN THE STORAGE BOX.
STOP TO MAKE SURE THAT THE RIGHT
P A N E L S H O W S O N L Y S E T S I N C P S . I F
SETS IN GEOFRAME SHOW UP, GO BACK
T O S T E P 4.

8. Highlight all sets in the right panel of the dialog and click the Delete
icon, the large red X. This will remove all CPS-3 sets in the CPS-3
dsl.

6. Back in the left side of the dialog in the Storage panel, click on All,
then click Filter. We should only see GeoFrame sets in the list, if
anything. These are grids, fault boundaries, and other items created by
other applications.

7. Close the List Manage Sets dialog box.

Import Supplementary Data Files


At this point, we will load some external data files which will be used in this
course. These are files which are not part of the GullFaks project, but are
necessary for training purposes, such as auxiliary data files, macros, ASCII
files, and so forth, which are used in some of the exercises.

1. In the CPS-3 Main Module, go to File > Import > Project.

2. Click on Select Coordinate System and in the next dialog box,


highlight the proper coordinate system which we verified earlier as
being the correct one for this project, and click OK.

3. Click on the by Directory toggle near the bottom.

Chapter 3 - 12 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Introduction to the GullFaks GeoFrame Project

4. Type or swipe the fully qualified pathname given to you by the


instructor. (This path is the location of the external data which you will
load into your CPS-3 DSL.)

5. Make sure that the last character in the pathname is a forward slash
/, as seen in the following figure.

Figure 3.10 Path to location of external data destined for CPS-3 DSL

6. Click OK.

7. Click OK or Yes to all messages which appear, but note the files which
are being loaded in the CPS Status Window.

8. Close the Multiple Set Selector dialog box which appears.

9. In the CPS-3 Main Module, go to Utilities > Sets > List/Manage


Sets.
You should now see several sets which were not visible earlier, and
whose Storage is CPS. These are the files we just loaded in the CPS-3
DSL. Refer to next figure.
Depending on the status of your particular project, you may also see
other GeoFrame files interspersed with the mm files just loaded

GeoFrame 4.0 Introduction to CPS-3 Chapter 3 - 13


Introduction to the GullFaks GeoFrame Project Schlumberger

Figure 3.11 Multiple Set Selector displaying files loaded to CPS-3 DSL

Setting Plotter Units


In earlier versions of CPS-3, plotter units were defined before execution time
by the use of an environment variable in the GeoFrame .login file called
CPS3MUNIT, which could be set to METRIC or to ENGLISH.
In this version of CPS-3, the units that you see in the CPS-3 dialogs regarding
character sizes, symbol sizes, scaling, and so forth, will be in the units system
as specified for Geographic Distance in the GeoFrame Display Units tab. If
the Geographic Distance units are set to Meters, then the character sizes in
CPS-3 will be specified in centimeters. If the Geographic Distance is
defined in feet, the CPS-3 plotter units will be in inches.

Chapter 3 - 14 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Introduction to the GullFaks GeoFrame Project

The recommendation is to establish your desired Display Units settings as


early as possible. Switching from meters to feet (or visa-versa) in the middle
of a session or in a mature project can be difficult. In this Gullfaks-based
training course, we will use metric units.

GeoFrame 4.0 Introduction to CPS-3 Chapter 3 - 15


Introduction to the GullFaks GeoFrame Project Schlumberger

Chapter 3 - 16 GeoFrame 4.0 Introduction to CPS-3


Chapter 4
CPS-3 Menu Organization and
Capabilities Overview

Overview
This chapter provides a brief overview of all functionality provided from the
CPS-3 Main Module, and how it is organized. In addition, a navigational
summary of the menu hierarchy is given.

The full capability of CPS-3 is divided among the following independent


modules which are described in this chapter:
Main Module - modeling and mapping tools
Map Editor - simple graphic editing of Map sets
Model Editor - comprehensive grid and data editing
Color Palette Editor - customize/create palettes

In addition, the following data management tools are available from the Main
Module:
Control Point Editor - interactive spreadsheet editor for Data sets
Subset Reorganizer - a fault management tool
Map Layer Manager - a tool for reorganizing graphic layers of a map

In this chapter we also present a convenient How To... Matrix which cross-
references common mapping operations with the menu navigation instructions
for how to get there. This cross-reference is at the end of the chapter.

GeoFrame 4.0 Introduction to CPS-3 Chapter 4 - 1


CPS-3 Menu Organization and Capabilities Overview Schlumberger

CPS-3 Main Module


The Main Module is where most of the traditional modeling and mapping
tools are located, and where you will probably spend most of your time in
CPS-3. In the previous chapter, we learned how to invoke the Main Module
from either a stand-alone or a GeoFrame 3.0-or-later installation. In this
chapter, we will learn many things about the environment of the Main
Module - its conventions, resources, organization, and concepts.

Main Module Dialog Box


The figure on the opposite page displays the current Main Module graphic
dialog box. Note the following features emphasized in the figure.
Pull-Down Menus:
All CPS-3 functionality can be accessed through these pull-down
cascading menus.
Icons:
For more convenient access to commonly used functions, these icons
can be a shortcut instead of traversing the menu tree.
Icon Descriptions:
As the cursor is moved over the icons, a description of each is
presented here.
Scroll Bars:
When zoomed in, use these slider bars for panning across the display.
Display Environment Box:
Every display environment you define in CPS-3 contains the definition
of an x, y, z box called the Volume of Interest (VOI). What is shown
here is simply the x, y portion of the box. The system attempts to
maximize the amount of canvas space allocated to your currently
active x, y box.
Canvas:
This is simply the total potential screen area (or paper plot area, when
plotting) where the x, y box can be located. The lower left corner of
the canvas represents the origin(0,0) for the internal graphic coordinate
system in inches or centimeters.

Chapter 4 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Menu Organization and Capabilities Overview

Pull-Down Menus

Icons Icon Descriptions Scroll Bars Display Environment Box Canvas

Figure 4.1 CPS-3 Main Module

GeoFrame 4.0 Introduction to CPS-3 Chapter 4 - 3


CPS-3 Menu Organization and Capabilities Overview Schlumberger

X,Y Tracker Display


When moving the graphic cursor during zooming, the x,y location of the
cursor is echoed at the bottom of the Main Module dialog box as shown in
the following figure. The position is echoed in both engineering units and
plotter (viewport) units.

The x,y tracking also occurs during screen digitizing initiated from the
Digitize pull-down menu.

Figure 4.2 Main Module displaying x,y locations of graphic cursor

For convenience, the tracker may also be invoked at any time with the tracker
icon:

Figure 4.3 Display x and y position at cursor icon (aka Tracker icon)

Chapter 4 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Menu Organization and Capabilities Overview

Measuring Tool
The measure distance icon in the following figure provides facilities for
measuring distances and angles on the graphic display.

Figure 4.4 Measure distance icon

Figure 4.5 Determining distance using the Measure distance icon

GeoFrame 4.0 Introduction to CPS-3 Chapter 4 - 5


CPS-3 Menu Organization and Capabilities Overview Schlumberger

Main Module Status Window


The figure on the next page provides an example of the Main Module status
window, on which the following components should be noted:
Currently open Data set:
This table provides a list of the currently open sets by set type (Data,
Fault, Polygon, Surface, and Map). This particular example shows
one active Data set. Note that the table scrolls downward and has
room for up to seven active sets per type.
Currently open Surfaces:
In this example, there is one open Surface set.
Native Command Entry:
By clicking the cursor in this box, you can type native commands here,
as an alternative to menu or icon selection.
Online status report dialog:
This window displays a real-time status report of all operations you
perform during the CPS-3 session. This information is also written to a
file called
<username>.rep
where <username> is your login id. This file is overwritten each time
you start another CPS-3 session.
Swap Screens Icon:
The CPS-3 Status Information window can be instantly moved from
the current screen to the opposite screen by simply toggling the Swap
Screens icon in the upper right of the display.

Chapter 4 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Menu Organization and Capabilities Overview

Swap
Screens
Currently open Data set Currently open Surfaces Icon

Native Command Entry Online status report dialog

Figure 4.6 Main Module displaying CPS-3 Status Information window

GeoFrame 4.0 Introduction to CPS-3 Chapter 4 - 7


CPS-3 Menu Organization and Capabilities Overview Schlumberger

UNIX Environment
In the Main Module go to User > Show Environment to bring up the CPS-3
Environment window. This window can remain visible while you perform
other mapping operations. Its purpose is to provide you with information
about where CPS-3 is installed, and where the configurable resource files are
located. It also serves to remind you of the path to your open project, so that
copying of configuration files into your project area from an xterm is
simplified.

Figure 4.7 CPS-3 Environment window

Chapter 4 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Menu Organization and Capabilities Overview

CPS-3 Map Editor


The Map Editor in the following figure is a graphic editing tool used after
creating the Map Set in the CPS-3 Main Module. Users can edit attributes
such as colors and fonts. Overposting can be cleaned up interactively.
Symbols and text can be added. Composite maps can also be created in the
Map Editor.

Figure 4.8 CPS-3 Map Editor

GeoFrame 4.0 Introduction to CPS-3 Chapter 4 - 9


CPS-3 Menu Organization and Capabilities Overview Schlumberger

CPS-3 Model Editor


The Model Editor in the figure below is for editing surfaces, points, faults,
polygons, and features. Users can make changes to the model (surface) by
moving, deleting, or redrawing contours, modifying data (points), modifying
fault data, using polygons for constraints, adding feature data, or by modifying
the actual grid nodes.

After each edit, the model is regridded and saved upon completion of the
editing. The final model (grid) is then brought back into the CPS-3 Main
Module.

Figure 4.9 CPS-3 Model Editor

Chapter 4 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Menu Organization and Capabilities Overview

CPS-3 Color Palette Editor


The Color Palette Editor in the following figure allows users to define their
own color palettes to use when drawing color shaded contour maps. Colors
can be associated with a specific z-value. Each individual color can be set, or
the system will interpolate between two colors set by the user. The color
palettes are then saved to a color palette name in the users project directory.
These palettes can be accessed in the Main Module when specifying
parameters for displaying color shaded contours.

Figure 4.10 CPS-3 Color Palette Editor

GeoFrame 4.0 Introduction to CPS-3 Chapter 4 - 11


CPS-3 Menu Organization and Capabilities Overview Schlumberger

CPS-3 Control Point Data Editor


In the CPS-3 Main Module, go to Utilities > Sets > Edit Data Set to access
the spreadsheet-formatted data editor which is shown below. This feature is
very useful for removing z-fields, changing subset names, and editing graphic
symbology such as symbol codes, or even well names in data sets.

The data set shown below is a well marker data set, which was loaded as an
Extended data set with three z-fields, a well name, and symbol code - all of
which are available for editing.

The Help text for this dialog is very useful.

Figure 4.11 Main Module displaying spreadsheet-formatted data editor

Chapter 4 - 12 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Menu Organization and Capabilities Overview

CPS-3 Set-Subset Reorganizer


This utility performs data management functions among various CPS-3 set
types, reordering information from one domain into useful information in
another. For example, assume that you mapped three surfaces, each with two
major fault polygons having z-values attached. The three fault polygons
migrate in x and y as they move downdip in each of the horizons. If you now
wanted to create gridded surfaces for the two faults, it would be impossible
with the fault sets because the x,y,z points are organized by horizon
(Figure 2.12). What is needed is a resorting of these x,y,z points by fault,
rather than by horizon (Figure 2.13). Individual files in these figures are
indicated by separate fill patterns.

Figure 4.12 Sorted x, y, z points according to horizon

GeoFrame 4.0 Introduction to CPS-3 Chapter 4 - 13


CPS-3 Menu Organization and Capabilities Overview Schlumberger

Figure 4.13 Sorted x, y, z points according to fault

The Set/Subset Reorganizer will perform this reordering for you. As the
different shades of gray in the first diagram above indicate, x,y,z fault traces
are grouped in Fault sets, one per horizon. In the Set/Subset Reorganizer
dialog box, select the Fault sets for all horizons which contain valid x,y,z
points to use in the gridding of the fault surfaces. From each of those selected
fault sets, you can choose any or all of its subsets (individual fault traces for a
single fault) which you want to be included in the output data sets.

In this example, we have asked for the output to be written to a Data set as
shown below. There will be as many output Data sets as there are unique
subset names (fault names) in the selected Fault sets. Each of the output Data
sets can then be gridded to obtain a model of the fault surface.

The Help text for the Set/Select Reorganizer is very informative.

Chapter 4 - 14 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Menu Organization and Capabilities Overview

Figure 4.14 Set/Subset Reorganizer

GeoFrame 4.0 Introduction to CPS-3 Chapter 4 - 15


CPS-3 Menu Organization and Capabilities Overview Schlumberger

CPS-3 Map Layer Manager


The Map Layer Manager (Figure 2.15) is an extremely useful tool for
reordering the subsets stored in a map set. It is often the case that color shaded
contours (Figure 2.16) obliterate other map elements simply because of the
order in which they were displayed on the screen. The Map Layer Manager
will allow you to reposition map layers (subsets) to optimize your graphic
output without having to regenerate the graphics on the screen.

Figure 4.15 Map Layer Manager

Chapter 4 - 16 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Menu Organization and Capabilities Overview

In this example, the picture below and on your screen was generated with
separate graphic commands; then the Map Layer Manager (Figure 2.15) was
invoked with the Manipulate current map layers icon (Figure 2.17).

Figure 4.16 Example of colored contour map

Figure 4.17 Manipulate current map layers icon

Each layer on the screen is shown as a line in the dialog table.

To reorder the layers of an existing map, simply clear the screen, display the
map, then invoke the Map Layer Manager.

Layers can be temporarily turned on or off. Layers may also be deleted. As


with other CPS-3 dialogs, the Help text for this facility is very useful.

GeoFrame 4.0 Introduction to CPS-3 Chapter 4 - 17


CPS-3 Menu Organization and Capabilities Overview Schlumberger

Menu Navigation by Topic


GENERAL

Set expert level - UTIL/ SYSTEM/ SET-EXPERT-LEVEL

Set control switches - UTIL/ SYSTEM/ SET-TOGGLE-SWITCHES

Find out the path to the CPS dsl - USER/ SHOW-ENVIRONMENT

See statistics on a CPS-3 set - UTIL/ SETS/ VIEW-CONTENTS-...

Look at the CPS-3 on-line Users Manual - TOOLS/ USER-MANUAL

DISPLAY

Create display environment -


Sixth icon from top on left, then click CREATE on the Display row.

Display borders, labels, North arrow, titles, etc. - DISPLAY /BASEMAP

Display contours and color shaded maps - DISPLAY/ CONTOURS

Display cross-sections - DISPLAY/ 2D-XSECTION

Display color bar - DISPLAY/ COLOR-SHADING-PALETTE

Display ortho contours - DISPLAY/ CONTOUR/Orthocontours

Erase/delete/reorganize graphic layers - DISPLAY/ MAP-LAYERS

Save display as map set -


Fifth icon from bottom on left

Zoom in- VIEW/ ZOOM-IN

Zoom out - VIEW/ ZOOM-OUT

Erase the screen -


Big red X icon

Erase last graphic layer


Blue back-arrow icon above big red X icon

Set graphic margins - DISPLAY/DISPLAY_FUNCTIONS/


SET_GENERAL_DISPLAY_PARAMETERS/

Chapter 4 - 18 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Menu Organization and Capabilities Overview

GRIDDING/MODELING

Create a modeling environment -


Sixth icon from top on left/ then click CREATE on the Modeling row

Create a grid from data - MODELING/ SINGLE-SURFACE

Use faults during gridding -


MODELING/ SINGLE-SURFACE/ Make sure Fault is clicked on and
selected

Select the gridding algorithm -


MODELING/ SINGLE-SURFACE/ Click on the Algorithm box

Conformal Gridding - MODELING/CONFORMAL_SURFACE

SINGLE GRID MODIFICATION

Refine a grid - OPERATIONS/ GRID/ REFINE

Smooth a grid - OPERATIONS/ GRID/ SMOOTH

Differentiate a grid - OPERATIONS/ GRID/ DIFFERENTIATE

Blank a grid - OPERATIONS/ GRID/ BLANK

Clip a grid -OPERATIONS/ GRID/ LOGICAL/ Use 1ST or 3rd Operation

Perform grid arithmetic - OPERATIONS/ GRID/ SINGLE-GRID

Tie a grid to data - OPERATIONS/GRID/TIE_GRID_TO_DATA

Chance a grid lattice - OPERATIONS/GRID/MODIFY_GRID_LATTICE

Extract a grid (Peek) - OPERATIONS/GRID/EXTRACT_GRID

Insert a grid (Poke) - OPERATIONS/GRID/INSERT_GRID

MULTIPLE GRID ARITHMETIC/LOGIC

Subtract two grids to create a thickness grid -

GeoFrame 4.0 Introduction to CPS-3 Chapter 4 - 19


CPS-3 Menu Organization and Capabilities Overview Schlumberger

OPERATIONS/ GRID/ MULTIPLE-GRIDS

Merge two grids -]


OPERATIONS/ GRID/ Under MULTI-GRIDS, use Operations 1 - 4

MACROS

Run a macro - MACROS/ EXECUTE

Create a macro - MACROS/ CREATE

Edit a macro - Create a macro, then user the text editor of your choice

DIGITIZE

Digitize data, faults, polygons, text - DIGITIZE as needed

DATA POINT ARITHMETIC

Compute values from a grid at arbitrary (well) locations -


OPERATIONS/ CONTROL POINTS/Interpolate from........,

Perform arithmetic on control point z-fields -

OPERATIONS/ C.P./CONTROL-POINT-MATH

SET MANAGEMENT/SET MANIPULATION

Rename a z-field - UTILITIES/ SYSTEM/ MANAGE Z-FIELD NAMES

Delete a set - UTILITIES/ SETS/ DELETE

Copy a set - UTILITIES/ SETS/ COPY

Rename a set - UTILITIES/ SETS/ RENAME

Unlock a set - UTILITIES/ SETS/ UNLOCK

Edit a data set - UTILITIES/ SETS/ EDIT DATA SET

View all subsets of a set -


UTILITIES/SETS/VIEW_CONTENTS_&_STATISTICS/ LIST_SUBSETS

Chapter 4 - 20 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Menu Organization and Capabilities Overview

Print all values in a set -


UTILITIES/SETS/VIEW_CONTENTS_&_STATISTICS/ LIST_CONTENTS

OTHER CPS-3 APPLICATIONS

Run the Model Editor - TOOLS/MODEL-EDITOR

Run the Map Editor TOOLS/MAP-EDITOR

Run the Color Palette Editor TOOLS/ COLOR-PALETTE-EDITOR

Run SurfViz - TOOLS/ SURFVIZ

Run the GeoFrame Link - TOOLS/ GEOFRAME-LINK

Run the IESX/CPS Link - in Visualization Catalog under CPS-3

Run the Charisma/CPS Link - from Charisma menu

DATA IMPORT/EXPORT

Import/export ascii files - FILE/ IMPORT and EXPORT

GeoFrame 4.0 Introduction to CPS-3 Chapter 4 - 21


CPS-3 Menu Organization and Capabilities Overview Schlumberger

Icon Definitions

Stop current process View set statistics

Zoom in Subset utilities

Reveal all graphics List/Manage sets

Unzoom to last zoom Get x,y coordinates

DisplayEnv from Zoom Measure distance/angle

Select/edit environment Quick map

Set map scale Single surface gridding

Undo last graphic display 2D Profiles

Erase the screen Borehole intersections

Refresh display Volumetrics

Basemap menu Model editor

Contour Color palette editor

Map layers Customize icon bar

Save display as mapset Hide icons

Record a macro GeoFrame Link

Stop recording macro GF grid data manager

Execute a macro GF grid library data manager

Unlock a set

Chapter 4 - 22 GeoFrame 4.0 Introduction to CPS-3


Chapter 5
CPS-3/GeoFrame Integration

Overview
This chapter reviews the nature and extent of data integration for CPS-3
within the GeoFrame data base.

In GF4.0, CPS-3 still maintains its own local data store, that subdirectory
known as the CPS-3 DSL, where CPS-3 binary sets are stored. However,
much of the data in GeoFrame is visible to CPS-3, either directly, or via the
GeoFrame data link, GFLink. It is up to the user whether individual sets are
stored in GeoFrame, or in the CPS-3 DSL.

GeoFrame 4.0 Introduction to CPS-3 Chapter 5 - 1


CPS-3/GeoFrame Integration Schlumberger

CPS Local Data Store (dsl) and GeoFrame Storage


Historically, CPS-3 has used an internal data management system called the
Storage Manager. This internal data store will eventually be replaced by the
GeoFrame Oracle data base, but in GeoFrame, the CPS-3 internal storage
facility is still in place. Even so, there are some CPS-3 sets which may, at the
users option, be stored in the GeoFrame data base at the time of their
creation. In particular,
Data sets may be stored in GeoFrame as scatter sets, however, subset
organization is lost.
Fault sets may be stored in GeoFrame with subset (fault name)
organization maintained.
Surfaces sets may be stored in GeoFrame with the fault set
association maintained.
Polygon sets may be stored in GeoFrame (new in GF4.0).

Controlling Where Sets are Stored or Retrieved


During Set Creation:
At the time any CPS-3 set is created, the menus give you the choice of
storing the data in either the CPS local data store or in GeoFrame.
During Set Selection:
At the time any existing CPS-3 set is being selected, the menus show
you the current storage location of all available sets (CPS local data
store or GeoFrame), and allow you to select from either location.

GeoFrame data items are synonymous with CPS-3 sets, but data items stored
in GeoFrame must now also be identified with the following attributes:
Container name
Container type
Property code
Unit of measurement

Chapter 5 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3/GeoFrame Integration

Accessing Data in GeoFrame and IESX - Data Links and


Menus

Binary Data Links for CPS-3


The previous IESX and CHARISMA Links for Seismic Locations and
Interpretation are no longer necessary for CPS-3, since seismic data,
navigation data, and interpretation are now stored directly in the GeoFrame
data base and can be accessed by CPS-3 in other ways. The GeoFrame Link
(GFLink), on the other hand, is still required, and has been expanded and
improved for GF4.0.

How to access specific data types from CPS-3


Here is a brief summary of how selected data classes are accessed from CPS-3
in GF4.0:

2D survey location data are now accessed via the GFLink and can be posted
with the existing Extended data seismic line posting feature.

3D survey location data is accessed and displayed via the Display menu. A
new 3D seismic line posting feature is available.

Horizon interpretation is now seen from the CPS-3 file selection dialogs as
grids in GeoFrame. Use the Source set attribute to distinguish actual
interpretation grids from derivative grids. Note that in Modeling Office,
Horizon Modeling has been modified to accept GeoFrame grids directly as
input. In the CPS-3 Main Module, however, GeoFrame interpretation grids
must be Copied to Data sets before using them in Single Surface Gridding.

Fault Segment Interpretation is accessed as Fault Cut Sets from GFLink.

Fault Boundary Interpretation is seen in the CPS-3 file selection dialogs as


fault boundary sets in GeoFrame, just as before.

Fault Contact Interpretation is seen in the CPS-3 file selection dialogs as


scatter Data sets in GeoFrame.

IESX Cartography, which will not reside in GeoFrame, will be brought into
CPS-3 with a new Culture Loader which will be invoked from the CPS-3
menus and from the Visualization catalog in place of the old IESX Link.This
facility will not be released in 4.0, but in one of the later versions such as 4.01.

Well location data, such as top location, bottom hole locations, and borehole
trajectories are accessed from the GFLink, just as before.

GeoFrame 4.0 Introduction to CPS-3 Chapter 5 - 3


CPS-3/GeoFrame Integration Schlumberger

Well markers for specific Horizons are accessed from the GFLink, just as
before.

Property summations for specific Zones are accessed from the GFLink, just
as before.

Tip Loops created by Framework 3D are stored in GeoFrame, but are visible
from CPS-3 as Polygons.

All other GeoFrame surfaces, scatter sets, and fault boundaries can be seen
directly in the CPS-3 file selection dialogs, and, if necessary, can be COPYed
to the CPS-3 dsl, just as before.

Geoshare Links for Cartography


Although a CPS-3 Geoshare sender and receiver have been more or less
unavailable in GF3.5 through GF3.8, a facility exists in GF3.8 to import.rp66
and .gf66 files which have been created by Finder, and contain cartographic
information. Use the File > Import > Geoshare Culture menu path to this
facility.

The new menu item File/Import_IESX_Cartography is now available and


supersedes the previous IESX Link.

Chapter 5 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3/GeoFrame Integration

Geographic Coordinate Systems


Although the decision to store or not store data in GeoFrame is optional, the
use of geographic coordinate systems is not. Every set created in CPS-3
must be associated with a coordinate system which has been defined in
GeoFrame.

Sets are associated with a geographic coordinate system, or with the default
coordinate system at the time of their naming and creation.

If two sets are associated with different coordinate systems, CPS-3 will
automatically perform the numerical conversions required during operations
which use both sets. Specific rules for these conversions are covered in a later
chapter.


Tip: You may load data having any range of cartesian X,Y values into any
GeoFrame project. As long as you reference the same GeoFrame coordinate
system definition where necessary, the system will not attempt any kind of
conversion. It will simply accept the data as it is.

Rules of the Road for Automatic Coordinate System


Conversion in CPS-3 Sets
Every set in CPS-3 is now associated with a particular coordinate system by
virtue of its assigned Display or Modeling environment under which it is
created. Here are the basic rules governing how coordinate systems are
initiated or modified under certain common conditions.


Best Practice: Unless your project requires something different, the recommendation is to use
one coordinate system for all sets in your project.

Note that only coordinate systems (which includes rotation) are


automatically converted in CPS-3. There are no ad hoc facilities for
conversion of either units (feet, meters,...), or domain (time, depth,...).

GeoFrame 4.0 Introduction to CPS-3 Chapter 5 - 5


CPS-3/GeoFrame Integration Schlumberger

Surfaces:
In practice, surfaces cannot be transformed from one coordinate
system to another. However, graphic manifestations of a surface, such
as contours or postings of nodes, can be transformed.
Reading ASCII data in geographic coordinates:
Data with geographic coordinates (degrees, minutes, seconds, or
decimal degrees) will be transformed using the currently active
Display environment.
Reading ASCII data in x, y coordinates:
In this instance, no conversion takes place. The data being loaded takes
on the stamp of the active Display environment.
Surface Arithmetic and Surface Operations:
The environments of all surfaces in the operation must match the
current Modeling environment.
Gridding:
During gridding, control points and fault traces are transformed to
match the coordinate system of the active Modeling environment.
Graphic Display:
Any set displayed will be transformed to match the coordinate system
of the currently active Display environment.
Data Links such as GFLink:
Any data moved into CPS-3 via these data links will be automatically
transformed to match the coordinate system of the currently active
Display environment. Note that units and domain of the output set is
established by the GeoFrame Display Units, not the currently active
CPS-3 Display environment.

Chapter 5 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3/GeoFrame Integration

Enhancements in CPS-3 for GeoFrame 4.0


In this technical note, well outline the enhancements added to CPS-3 in
GeoFrame 4.0.

Enhancements in CPS-3 for GF4.0


1 Framework 3D Integrated into Modeling Office (MO)
provides FW3D and P3D on same canvas
reverse thrust fault capability added to Framework 3D
ITC selection added to Model Editor for communication with Modeling
Office

2 New CPS-3 Menus for Viewing FW3D output


Display Framework contours including reverse fault contouring
Display Framework Cross-sections
Display Framework Allen diagrams

3 Model Editor enhanced with ITC for communication with MO


surface changes in Modeling Office are seen in the Model Editor session

4 New modeling feature in Single Surface gridding allows conformal


modeling
uses upper and lower reference surfaces
uses same algorithm as Horizon Modeling, but without fault framework

5 New surface operation allows updating of a grid with a new data


set
gives user ability to establish radius of influence for the data set

6 New versions of MSEDIT, MSPEEK, and MSPOKE are available and


support rotated grids

7 Grid operations with automatic lattice matching to current


modeling environment

8 New icon added to create display environment from current zoom


window (GF3.8.1)

9 Macro facilities enhanced

GeoFrame 4.0 Introduction to CPS-3 Chapter 5 - 7


CPS-3/GeoFrame Integration Schlumberger

can now spawn a system task from a macro and wait (GF3.8)
can now spawn a background task (GF3.8)
access to macros from three categories - system, project, user
can add descriptions to macros which are visible during macro selection
define and assign macro categories which are displayed during selection
new Yes/No prompt type
new prompt facility - select from list of options
prompt titles and prompt strings can now be variables
can load extended data with existing format
can define set attributes

10 Faster color-shading algorithm

11 New, faster contouring algorithm

12 Vector display function enhanced to accommodate rotated grids

13 Ability to delete rows in Data Editor

14 Polygon fill limit increased to 5000 vertices

15 Controls for posting fault names and z-values has been enhanced

16 Added creation/modification time and date as new set attributes

17 Added capability to select which attributes to display in the set

selector dialog

18 Added set utility (copy, delete...) icons to List/Manage Sets dialog

19 Expert Level removed

20 Ability to customize the Display menu

21 GFLINK now has better borehole selection tools

22 GFLINK can now access fault cuts.

23 Specify line echo color in Digitizing dialog.

24 3D Seismic Survey Display

Chapter 5 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3/GeoFrame Integration

Examples of Macro Enhancements

The following macro excerpt shows how you can now use a variable string for the
dialog title and the prompting text. It also shows a simple Unix command can be
spawned.

Spawning detached tasks can also be done with the spawn command if you use the
ampersand at the end.

The next example shows how to establish the set attributes for new sets.

GeoFrame 4.0 Introduction to CPS-3 Chapter 5 - 9


CPS-3/GeoFrame Integration Schlumberger

The example menu below shows that you may have three basic sources for
collections of macros a system-wide collection, a project-related collection, and
any number of user collections which can be identified simply by a path name.

In this menu, the project-based collection of macros has been selected and its
macros listed. One of them has been highlighted which causes its internal
description lines to be displayed.

The next figure shown an example of a macro_index.txt file, whose purpose is to


subdivide a collection of macros into categories. In this example, each category is
defined with a CATEGORY: keyword followed by the user-supplied category
name. Following this, all macros belonging to that category are listed. The macros
and the macro_index.txt file must be in the same directory.

Chapter 5 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3/GeoFrame Integration

In this example, the System macro group has been chosen, and the names of all
macros in the Display category have been displayed for selection.

GeoFrame 4.0 Introduction to CPS-3 Chapter 5 - 11


CPS-3/GeoFrame Integration Schlumberger

Chapter 5 - 12 GeoFrame 4.0 Introduction to CPS-3


Chapter 6
Understanding CPS-3 Set Types

Overview
In this lesson, we will describe the way in which CPS-3 sets are organized.
Historically, all CPS-3 sets were stored in its own local data store (the CPS-3
DSL), maintained by the CPS-3 Project Manager independently of the
GeoFrame data base. Now, however, many of these sets are just as easily
stored in GeoFrame.

Please refer to a previous lesson which discusses the integration status


between CPS-3 and GeoFrame.

A Typical CPS partition in a GeoFrame Project


The CPS partition is simply a pointer to a disk directory, for example:

/home/disk1/user1/projects/CLOUDSPIN/CPS

The first part of the path /home/disk1/user1/projects is determined by


the owner of the project CLOUDSPIN.

The remainder of the path /CLOUDSPIN/CPS is determined by


GeoFrame.

In this example, the full path shown above defines the location of the CPS
local data store, or partition, within the GeoFrame project Cloudspin. In this
directory, you will find everything which is managed by the CPS Project
Manager.

As mentioned in the previous lesson about GeoFrame integration, it is


possible in this release to optionally store some CPS-3 sets in the GeoFrame
data base, which is separate from this partition.

GeoFrame 4.0 Introduction to CPS-3 Chapter 6 - 1


Understanding CPS-3 Set Types Schlumberger

Ultimately, the data to which you have access in CPS-3 will be stored in one
or more of the file types outlined below. These files will reside in your CPS
dsl. Note that each is distinguished by its UNIX file extension which is not
seen in the CPS-3 menus or dialogs.
.1cps files - session files; files containing parameter values
.dcps files - data files; x,y,z files
.fcps files - fault trace files; x,y files; optionally, x,y,z files
.pcps files - polygon files; x,y only
.scps files - surface (grid) files; z only; x,y is inferred
.mcps files - map files; picture files
.tcps files - table files such as created by Framework3D

Data, Fault, and Surface sets may optionally be stored in either the local
project files, as shown above, or in the GeoFrame Oracle data base, or both.

Each CPS-3 set can consist of one or more named subsets.

Session Sets (or Session Files)


Usually, there is only one session set in your dsl location. It has the name
<your login id>.1cps and contains the most recent values for all parameters
you set during your CPS-3 session. This includes definitions of your modeling
and mapping environments. You will also see session files created for batch
processes you initiate from CPS-3. Each will have a unique file name.

Data Sets (.dcps)

Description

Data sets contain information which is to be gridded or displayed, such as data


points. Examples are well markers, seismic interpretation, and scatter data.

Data Types

CPS-3 uses a data sets Data Type to compute defaults for some of the
modeling and display parameters. M ost of the Data Types indicate a type of
spatial distribution pattern which can be exploited by certain algorithms. Data
types are shown in the following lists:

Chapter 6 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Understanding CPS-3 Set Types

Data Types Having Z-values


Scattered points
Contours
2D Interpretation
3D Interpretation
Fault Segments/Cuts
Fault Contacts
Pseudo Grid
Feature Lines
Borehold Trajectories
Well Markers

Data Types Without Z-values


2D Lines (locations)
3D Lines (locations
Well Surface Locations
Well Bottom Hole Locations

Data Content - Z Fields

Each data point loaded into CPS-3 must have at least an X and Y coordinate,
but may also have up to 50 z-fields. These z-fields are numeric, and can
represent any variable which is spatially distributed. A vertical well, for
example, might have one z-field value for each horizon it passes through
(markers), or a single well point may have one horizon depth value, and an
associated thickness to the next layer. Z-fields may also contain dip and strike
information for the horizon being mapped. There are no predefined
combinations of z-fields which are required for CPS-3. Each z-field can
represent anything you like. The most common data files loaded by CPS-3 are
data files containing x,y, and a z-value representing time or depth.

As you will see when loading data for the course, there are two attributes
associated with each z-field:
Z Field Name (z1, z2, top, bottom,...
Z Field Type (depth, elevation, isochore,...

GeoFrame 4.0 Introduction to CPS-3 Chapter 6 - 3


Understanding CPS-3 Set Types Schlumberger

Data Content - Text Fields

Some data files contain textual information for each point which is to be
posted on the map; for example, well name or operator name. There are two
methods for storing Data sets in CPS-3 - Extended Data, and non-extended
Data.

Non-Extended Data

A data point in stored in this form may have up to 50 numeric z-fields, but no
text fields. The only text allowed with this form of storage is a subset name.
For well data, this can represent the well name if you select the x,y,z + Name
Field option for loading. Use this type of Data for simple x,y,z points to be
gridded when no special display capabilities are required.

Extended Data

This type of data allows all of the above, but also allows the storage and
posting of up to 10 text fields, as well as the storage and utilization of graphic
symbology attributes. Symbology attributes, such as symbol type, size, and
color, can be associated with each data point. At present, Extended Data
cannot be exported from CPS-3, nor can Extended Data be loaded by the use
of macros.

Subsets

Data sets can be organized into subsets which makes certain processing easier.
For example, line-oriented data (2D seismic, digitized contours) should be
identified as such during ASCII loading so that each line becomes an
identifiable subset in CPS-3. Several formats suitable for controlling
line-oriented data will be illustrated below in the examples.

Fault Sets (.fcps)

Description

Fault sets in CPS-3 store those polylines which are commonly referred to as
fault traces, or in GeoFrame terminology, fault boundaries. To the CPS-3
procedures, it does not matter how these polylines are geometrically defined.
For example, a non-vertical fault pattern associated with a particular horizon
can consist of two separate lines - an upthrown line and a downthrown line, or
it may consist of a single closed polygon.

Chapter 6 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Understanding CPS-3 Set Types

Types of Faults

Faults can be categorized by the user in CPS-3 as either vertical or


non-vertical at the time the faults are loaded. In other cases, some CPS-3
operations in Framework3D automatically classify faults which they have
created as being fault traces, fault centerlines, or fault polygons.

Fault Attributes

Each fault trace must have an x,y coordinate, but other information is optional.
For example, if z-values are available on the trace, then these values should be
loaded along with the x,y values to help in the gridding of the associated
horizon. Vertical and horizontal separation, as well as dip values are also
valid numeric fields which can optionally be loaded with fault traces.

Associations

Fault traces used as input to a gridding operation are automatically associated


with the surface which is created. That is, the name of the fault set is stored in
the parameter block of the surface set. This means that when contouring, you
dont have to remember which fault set to use for each surface.

Subsets

In a fault set for one horizon in CPS-3, there is typically one fault trace
pattern for each named fault in the reservoir. The pattern for each named fault
is stored as a separate subset in the fault set. Several loading formats will be
shown in the examples to ensure that individual lines are identifiable in
CPS-3.

Polygon Sets (.pcps)

Description

There are two main purposes for polygon sets - the first is to define some
cartographic basemapping feature, such as a shoreline which is to be posted
on a basemap. Note that unclosed polylines are also valid to store in a polygon
set. The other use of polygon sets is to define some region in the modeling
area within which operations are to be performed or excluded from being
performed, for example, grid blanking or volumetrics calculation.

Types

Polygon sets can be typed as either open (polylines) or closed (polygons).

GeoFrame 4.0 Introduction to CPS-3 Chapter 6 - 5


Understanding CPS-3 Set Types Schlumberger

Subsets

A polygon set can consist of multiple polygons, or polylines, each of which is


a separate subset.

Surface Sets (.scps)

Description

Surface sets hold the grids in CPS-3. Only the z-value at each grid node is
stored. Parameters stored with the surface, such as the lower left corner of the
grid, and the grid spacing in x and y, are used by the system to compute the
x,y coordinates of each node location when needed.

Classification

Surfaces can be classified as one of the following:


horizon surface
fault surface
truncated (blanked)
truncated (filled)
These classifications are generated automatically by the software, in
particular, the Framework3D operations.

Associations

As mentioned under Fault Sets, the input fault trace set is associated with the
output surface in a gridding operation. In addition, there are spreadsheet-like
operations in CPS-3, particularly in Framework3D, where groups of surfaces
are defined. These groups of surfaces become associated during the creation of
a Table set (a .tcps file in the project directory). For example, a fault
framework Table set is created as the user loads surfaces in to the framework.
If a surface in a table happens to be deleted, the system will recognize its
absence the next time the table set is invoked.

Chapter 6 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Understanding CPS-3 Set Types

Map Sets (.mcps)

Description

Essentially, a Map set is a picture file. The picture on the screen can be saved
to a Map set at any time in CPS-3. Although it is possible, Map sets are not
usually loaded into CPS-3 from ASCII source files.

Subsets/Map Layers

All graphic components created by a single graphic operation are grouped as a


separate subset in the saved map set. These separate graphic layers can be
deleted, moved, or even hidden temporarily in CPS-3 with the Map Layer
Manager.

In the map set shown below, there are seven subsets, each of which is created
by a separate display operation.
Border
Border Labels
Scale Bar
Contours
Wells
Seismic Lines
Fault Traces

GeoFrame 4.0 Introduction to CPS-3 Chapter 6 - 7


Understanding CPS-3 Set Types Schlumberger

Figure 6.1 Example of a map set displaying seven subsets

Chapter 6 - 8 GeoFrame 4.0 Introduction to CPS-3


Chapter 7
Loading Location Data

Overview
There are many routes by which data can be made available to CPS-3. One of
the traditional methods is using ASCII files, which we will demonstrate in
this chapter. However, continuing integration of CPS into the GeoFrame
environment provides faster, more efficient, data access methods. For
example, interpretation which has been performed in IESX or Charisma
should be visible to CPS-3 as grids in GeoFrame. Seismic locations in
GeoFrame will also be visible to CPS-3, as we will demonstrate in this
chapter via the GeoFrame Link (GFLink). Well locations are also accessible
via GFLink.

In this chapter, we demonstrate the following:


Access 2D seismic location data from an ASCII file and/or the
GeoFrame database
Access 3D seismic location data and well location data from the
GeoFrame database using GFLink.
Generate statistics for the location data

ASCII Input of Locations as Extended Data


CPS-3 has a robust ASCII reader and can read just about any kind of column-
oriented data containing x and y coordinates. When you import Data sets in
CPS-3, you have a choice of loading the ASCII file as an ordinary Data set,
which allows the preservation of only one text field (subset name), or as an
Extended Data set. which allows the preservation of several text fields and
symbology fields, such as well name and symbol code. Please refer to
Chapter 27 which gives a broader outline of the formats and requirements for
the CPS-3 ASCII Loader.

GeoFrame 4.0 Introduction to CPS-3 Chapter 7 - 1


Loading Location Data Schlumberger

In the exercises, we will load an ASCII file containing Line name, Shot Point
number, x-coordinate, and y-coordinate as an Extended Data set so that we
can create a proper 2D line posting.

Using GFLink for Seismic and Well Location data


Note that the previous IESX and CHARISMA Links for Seismic Locations
and Interpretation are no longer necessary for CPS-3, since seismic data,
navigation data, and interpretation are now stored directly in the GeoFrame
data base and can be accessed by CPS-3 in other ways.

For example 2D/3D location data are now accessed via the GFLink as we
will demonstrate in the exercises.

Exercises: Loading Location Data


In these exercises, we show how to access both seismic and well location data
from GeoFrame. In addition, we will also introduce you to the CPS_3 ASCII
reader to show how to load 2D seismic location data from an ASCII file.

1. First, well show where to load 2D seismic locations data from the
GeoFrame Link

2. Then, well show how to use the CPS-3 ASCII loader to load a
complex 2D location file.

3. Afterwards, well load a simpler 2D location file which we will use


specifically for this GullFaks field.

4. Then, well see how to view 3D surveys directly from CPS-3

5. Next, well show how to load 3D locations from ASCII files.

6. Finally, well show how to load top and bottom hole well locations,
then well trajectories from the GF Link.

Chapter 7 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Loading Location Data

Exercise

Loading 2D Locations from GeoFrame

2D seismic locations are accessed from CPS-3 via the GeoFrame Link.

1. Click on the GeoFrame Link icon in the CPS-3 Main Module

2. Click the Load from GeoFrame tab, then click Data Types and
highlight 2D Navigation Lines in the second panel. Click OK.

GeoFrame 4.0 Introduction to CPS-3 Chapter 7 - 3


Loading Location Data Schlumberger

3. Back in the GFLink dialog, click on GeoFrame Data. If there were


2D navigation data in GeoFrame, you would see it in the next dialog
and select it from there.


Note: Temporarily, there are no 2D surveys. Shortly, this training project will be
updated with a 2D survey. As an alternative, we will load an ASCII file of 2D
locations.

Chapter 7 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Loading Location Data

Exercise

Loading 2D Location Data from Ascii Files

1. Open an xterm, by clicking MB1 in a unoccupied area of the display,


and selecting New Window.

2. In the CPS-3 Main Module, click User > Show Environment. (This
opens the CPS-3 Environment window.)

3. Highlight the path to your CPS-3 dsl which is found next to Project
Location.

4. In the xterm, type cd, skip a space, and click MB2. (The path to your
CPS-3 dsl should appear.)

5. Type ls *.dat. One of the files that you see should be named
mm_2d_gullfaks_shtpt.dat. (an ASCII file) part of which is shown
below, containing 2D locations. Look at this file using any editor you
like.

GeoFrame 4.0 Introduction to CPS-3 Chapter 7 - 5


Loading Location Data Schlumberger

This file is column-organized and contains the Line name in the first column,
the Shotpoint number in the second column, and the x and y coordinates in
columns three and four. This is an example of a very simple location file
which can be easily read by the CPS-3 ASCII reader. This file was copied
into your CPS dsl along with the other information, which we imported By
Directory earlier.

Below is another ASCII file we imported By Directory named


charis_2d_nav.dat. It was created in Charisma and represents similar 2D
location data as the first file, but in a different coordinate system and format.
This file contains more information, but can also be read by the CPS-3 ASCII
reader, as well demonstrate.

Chapter 7 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Loading Location Data

Well use the second file to demonstrate how to use the CPS-3 ASCII loader.

The first section of this file, where the lines all start with H, is a file header.
This header will be skipped during import. This file contains X and Y values
in both Cartesian coordinates and geographic coordinates.

The only columns that we want from this file are the Line name, Shotpoint
number, and the X and Y cartesian coordinates which begin after the letter W
in each line. In order to read this file, we will need to count the number of
header lines to skip, which is 32.

1. In the CPS-3 Main Module menu bar, go to File > Import > ASCII >
Extended Data to open the following dialog box.

2. In the Load Options section, type in 32 next to Lines to Skip.

3. In the File/Set Selection section, click New next to Output Set. (This
opens an additional dialog similar to the one in the following page.)

GeoFrame 4.0 Introduction to CPS-3 Chapter 7 - 7


Loading Location Data Schlumberger

4. In this dialog box, do the following:


type charis_2d_nav for the Name
select 2D Lines from the Subtype down-arrow list
set Surface (container name) to Unknown from the down-arrow
list
click OK to close this dialog box.


Tip: When loading files as Extended data, it is always a good idea to specify the
Subtype before you give the Input File name, since the system will do a better
job of automatic column assignment when it knows the Subtype. It is also
necessary to specify the number of Lines to Skip before you provide the Input
File name.

5. Under the File/Set Selection section, click Pick next to Input File.
(This opens the File Selection dialog box.)

6. Highlight charis_2d_nav.dat and click OK.

Chapter 7 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Loading Location Data

7. Under Line Name, click MB1 so that an insertion point appears


between the first and second S in the name Sslb1, then click on the
Split button in the Load Options section.

8. Click on Line Name, which now should have only a single S, and
scroll down within the Field Type popup menu, and select Ignore.

9. Above the column containing slb1, click on Ignore, then scroll down
within the Field Type popup menu, and select Line Name.

10. As above, change the Shotpoint Number column to read Ignore.

11. In the next Ignore column, split the text between the 20328 and
857.22N, then change the 20328 column to Shotpoint Number.

12. Note that the Z column is unnecessary, since all the z-values will be
0.0. We can leave it as it is, it will not cause any harm.
When the ASCII Input Data section of your dialog box looks like the
following one, click OK to load the data and close that dialog box.

GeoFrame 4.0 Introduction to CPS-3 Chapter 7 - 9


Loading Location Data Schlumberger

13. When the data has finished loading, in the CPS-3 Main Module menu
bar, go to Utilities > Sets > View Contents/Statistics to open the
following Main Module dialog box.

14. In the Set Type column, toggle the Data (D) button to red, and select
the data set we just loaded, charis_2d_nav, and then click OK.

Chapter 7 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Loading Location Data

In the CPS-3 Status Information window, you should see a statistical


report with values as shown below.

Note that every set loaded from ASCII will be stamped with the
coordinate system of the current Display environment. We have not
yet defined a Display environment, but every new project has a
default Display environment, which is based on the GeoFrame
Display coordinate system.

The 2D locations, which we just imported into an Extended Data set, do not
actually match the map area we will define for the GullFaks project, however,
it allowed us to see how the ASCII Loader works.

Now, well import the first 2D location file we looked at which was much
simpler in organization, and will be used to define the initial GullFaks map
area.

1. Load the ASCII file mm_2D_gullfaks_shtpt.dat into Extended data


in a similar manner to the previous file. Give it an output name of
mm_2D_gullfaks_shtpt, and make sure to set Number of Records to
Skip back to zero. Generate statistics for the set after loading. Please
note that this file contains only Line, Shot Point, X, and Y.

2. Even though we have not yet defined a Display environment, the


default Display environment from GeoFrame should allow us to
display the data we have just loaded.

3. The instructor will show you how to edit the Default display
environment so that it has a Map Ratio scale of 1650, giving a map
size of approximately 450x450cm.

4. When the editing for the display environment is complete, click on


Display > Basemap > Data, and pick the Data set
mm_2D_gullfaks_shtpt and then click OK.

5. Click Parameters, and choose a solid colored line.

6. Set the symbol size to 0.

GeoFrame 4.0 Introduction to CPS-3 Chapter 7 - 11


Loading Location Data Schlumberger

7. Click on No Text at the right, so it is red.

8. Then click OK, then OK again. You should see the display, as shown
below:

Data Set mm_2D_gullfaks_shtpt

Chapter 7 - 12 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Loading Location Data

Exercise

Displaying 3D Surveys in CPS-3

Depending on your version of GeoFrame 4, 3D locations stored in


GeoFrame can be seen from CPS-3 from the Display > 3D Survey dialog.
No data is loaded, only a display is created. Just like any other graphics in
CPS-3, the display can be saved into a Map set.

1. Click Display > 3D Surveys.

2. We see what appears to be one or more versions of the two basic


survey areas - GullFaks north and GullFaks south. At present, both
IESX and Charisma must maintain their own copies of the seismic
volumes.

3. Highlight the gullfaks_north survey, whose source is Charisma, and


then click the Display tab. This allows selection of specific inline and
crossline ranges, and a increment or modulus incremental posting.

4. Select all lines in the Inline Range by moving the scroll bars to the min
and max positions. Set Increment = 10, and then click the
Appearance tab.

5. Choose all items for display except Tick Marks, Line Names, and
Location symbols.

GeoFrame 4.0 Introduction to CPS-3 Chapter 7 - 13


Loading Location Data Schlumberger

6. Click OK or Apply, and then experiment with other settings, if you


like.

7. Highlight the gullfaks_south survey whose source is Charisma and


create a posting of it with similar parameters

8. If it is lit, click the Reveal All Graphics icon to see the entire map.

Chapter 7 - 14 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Loading Location Data

Exercise

Accessing 3D Locations from ASCII files (optional)

In the interest of time, this exercise may be skipped, and you may use the
following Data sets in the CPS-3 dsl, which have already been loaded for
subsequent exercises:
mm_3d_g1_survey
mm_3d_85acip_survey
mm_3d_offset_survey

If you want more experience with the Extended Data Loader in CPS-3,
please continue. We will use these surveys in a basemap exercise which
follows after loading the well locations.

In the exercise which follows, we will make use of three ASCII files, each
containing a 3D survey exported from Charisma in a different project.
3d_g1_survey.dat (skip first 30 lines)
3d_85acip_survey.dat (skip first 30 lines)
3d_offset_survey.dat (skip first 30 lines)

1. Use the Extended Data Loader, just as we did with the 2D data, to
load these three ASCII files into CPS-3, creating the following data
sets
3d_g1_survey
3d_85acip_survey
3d_offset_survey

These three sets will represent the location data for the three 3D surveys in
this GullFaks project: Review the procedure for ASCII loading, and the
instructor will provide assistance if you need it.

GeoFrame 4.0 Introduction to CPS-3 Chapter 7 - 15


Loading Location Data Schlumberger


Note: In order to load these three ASCII survey locations properly, you must
remember to specify Lines to Skip (30) first. You must load these data as 3D
lines, and also use the correct format, as shown below:

Loading of ASCII surveys versus display of GeoFrame


surveys
Notice that there is a difference in actually loading the data in this manner,
rather than simply displaying it, as in the previous exercise. In this case, we
can compute statistics on the data and manipulate it in ways which are not
possible with simply a map derived from its display. We can also use each of
the 3D surveys as a much more accurate basis for a Display or Modeling
environment.

Chapter 7 - 16 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Loading Location Data

Exercise

Loading Well Locations and Well Paths Using GFLink

Now, we will demonstrate the loading of top and bottom well locations, and
the wellpaths. Once more well use the GeoFrame Link.

1. Click on the GeoFrame Link icon in the CPS-3 Main Module.

2. Click the Load From GeoFrame tab, and then click the Data Types
icon to open the folder. This opens the GeoFrame Data Types dialog
box and again lets us identify the type of data we want to load.

3. Highlight Well Locations in the lower panel sections of the Surface


Types dialog box and click OK. Then click the GeoFrame Data
button.

4. In the GeoFrame Surface Selection dialog box, locate the Bottom-


hole Locations item on the left panel and highlight it. Do the same for
Surface Locations.

GeoFrame 4.0 Introduction to CPS-3 Chapter 7 - 17


Loading Location Data Schlumberger

5. Highlight both locations in the Representation section, and then click


OK. This will add the two items to the CPS-3 Output Sets list in the
GFLink dialog.

6. Click Data Types again, and this time select Borehole Trajectories,
and click OK.

7. Click GeoFrame Data again, and find Depth in the list on the left.
Highlight it and click OK.

8. Highlight the item on the left and click OK, putting it on the output
list, as seen below.

Chapter 7 - 18 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Loading Location Data

9. Now highlight all the items on the output list on the right and click
Run. This transfers the items to the CPS-3 dsl.

10. In the CPS-3 GeoFrame Link dialog box, highlight the Boreholes...
item on the right, and then click Run.

11. Iconize the GFLink dialog, since we will need it again.


Note: No provisions are made for specifying an output set name when loading data
with the GFLink. You have to simply accept the naming conventions, which
are actually quite clear. You may, however, use the CPS-3 Rename function
after the data is loaded.

GeoFrame 4.0 Introduction to CPS-3 Chapter 7 - 19


Loading Location Data Schlumberger

Exercise

Check out the Statistics of the Sets We Loaded

1. In the CPS-3 Main Module menu bar, click on Utilities > Sets >
View Contents/Statistics, so that we can look at the statistics for the
data sets that we just loaded.

2. Look for the Data sets Well_Locations_wbloc,


Well_Locations_wtloc, and Boreholes_Depth_wpath.

3. View the statistics for these sets, as before.

Chapter 7 - 20 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Loading Location Data

Exercise

Verify the Data We Just Loaded

Even though we have not yet discussed Display or Modeling environments,


we will quickly define a Display environment here, just so we can see the data
weve been loading.

1. Click on the small [x,y] icon in the left column, the sixth icon from the
top.

2. At the bottom, in the Display environment panel, click Create.

3. At the top, name this environment Quick_Look.

4. Click the Copy/Compute tab on the right.

5. Toggle Action to Copy Set Limits, toggle Set Type to Data, then
click Pick Set and highlight the data set mm_2D_gullfaks_shtpt, and
click OK.

6. Back in the Create Environment dialog, at the bottom left, set a Map
Ratio scale of 3000, then click OK.

Later, we will define a more accurate Display environment to create a proper


basemap of this location data. But at this point, we just want a quick look at it,
and we know that the 2D survey covers the largest area.

7 Click Display > Basemap > Data.

8. Click Pick Sets and pick the set named mm_3d_85acip_survey. For
quick display, show only the lines. Set the symbol size to zero, and set
the No Text toggle to red.

9. Click Apply.

10. Click Data again, then click Pick Sets, and pick mm_3d_g1_survey.

11. Click Set Parameters, changing the color of the lines, then click
Apply.

GeoFrame 4.0 Introduction to CPS-3 Chapter 7 - 21


Loading Location Data Schlumberger

12. Repeat this procedure to display the set mm_3d_offset_survey,


clicking OK instead of Apply. Your display should look similar to
this:

7. Next click Display > Basemap > Data, and repeat the processes to
display mm_2d_gullfaks_shtpt.
Display well_Locations_wtloc.
Display well_Locations_wbloc as Extended Data, showing the well
name in black, and using about 4.0 or 5.0 as the symbol size.
Display boreholes_Depth_wpath in black.

8. Change colors as needed for visibility. Your map should resemble the
display below:

Chapter 7 - 22 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Loading Location Data

Here, we see the three 3D survey locations, the 2D locations, the top and
bottom well locations, as well as the borehole trajectories. This is not what we
would call a proper basemap, but it is meant to quickly show that the data has
been properly loaded, and to see the extents and relationships among the data.
Next, we will proceed to define a permanent Display environment, better
suited to our basemapping exercises.

GeoFrame 4.0 Introduction to CPS-3 Chapter 7 - 23


Loading Location Data Schlumberger

Chapter 7 - 24 GeoFrame 4.0 Introduction to CPS-3


Chapter 8
Set Selection, Creation, and
Management

Overview
Before proceeding with setting a display environment for inspection of the
data we loaded in the last chapter, we must take the time to become familiar
with the way in which CPS-3 sets and subsets are manipulated. In this
chapter, we will learn about many utilitarian features in CPS-3 to help us keep
up with all of our different sets; for example:
listing existing sets by type
selecting existing sets for input operations from either GeoFrame, or
from the local CPS-3 data store.
changing the attributes of existing sets
creating new sets
renaming sets
deleting sets
copying sets

GeoFrame 4.0 Introduction to CPS-3 Chapter 8 - 1


Set Selection, Creation, and Management Schlumberger

Exercise

Set Selection and Creation

In the following exercises, we will introduce you to the menus and dialogues
which create sets and the procedure for selecting existing sets from either the
CPS local store or the GeoFrame database.

Listing Existing Sets/Editing Attributes


Almost all workflows in CPS-3 will involve the use of the CPS-3 Multiple
Set Selector a very useful set management tool.

1. In the CPS-3 Main Module menu bar, click Utilities > Sets >
List/Manage Sets to open the following dialog box.

The left panel is a filter which can be used to control which sets you
see on the right panel. The right panel contains the list of sets and their
attributes. In the text entry fields for the filter, you may use wildcards
to control the contents of the list. Note that the Surface Name is the
GeoFrame Container Name.

Chapter 8 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Selection, Creation, and Management

In the Set Type panel, you can activate All sets, or just one type. The
Surface Type panel lets you filter on the Container name. The
Property panel lets you filter on that attribute. Normally, you toggle
the buttons that you want to red, and then click the Filter button to
update the list.

2. De-select All and activate only the Data button in Set Type. Click the
Filter button to refresh the list.

3. Now click and hold on the small rectangle to the right of the Filter
button, and drag it all the way to the left, effectively hiding the filter
dialog area.
The sets you see may not be the same as you see here, but the
procedure will be the same.

4. Move the horizontal scroll bar to the right to reveal all the parameters
associated with each set. All the information that you see on a single
line is actually stored in the set.

5. Click on the Storage column heading and you will see all entries
sorted on that column. (The sorting works for all column headings.)

GeoFrame 4.0 Introduction to CPS-3 Chapter 8 - 3


Set Selection, Creation, and Management Schlumberger

Most of the information fields are obvious such as Owner, Create


Date, and Modify Date. However, the meaning of the following fields
may not be.
Access is the GeoFrame access code such as udo which means
Update/Delete/Ownership.
Storage tells whether the grid exists in the local data store (CPS),
or in GeoFrame.
Surface Type is the GeoFrame Container type.
Surface Name is the GeoFrame Container name.
Records is the number of physical records in the set.
Subsets is the number of subsets contained in the set.
Subtype is a further subdivision of data type such as Digitized
contours or 3D interpretation.
Type is the set type.
Name is the set name.
Property is the classification of the z-value in the set, for example,
depth or Time.
Measurement shows the classification of the units of the property,
for example, Length or Depth.
Z Unit shows the units of the z-value of the set, for example, m
(meters).
Surface Patch indicates the assigned level of overlapping fault
blocks in the case of reverse-thrust faults (for grids and seismic
interpretation.)
Grid Library indicates the binset associated with each grid.
Source tells where the set originated

6. You can control which attributes are displayed on the right panel by
clicking on the yellow smiley-face icon.

7. Position the cursor over the ten icons (but do not click) in the right
hand corner of the Multiple Set Selector dialog box to see a quick
description of each at the bottom of the dialog.


Note: The Edit attributes and Delete icons operate on multiple sets.

Chapter 8 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Selection, Creation, and Management

8. In the Multiple Set Selector dialog box, highlight the Data set
g_wells, and click the Edit attributes icon. The Main Module dialog
box opens.

9. Set the fields as shown above, and click OK.

10. Review the edited attributes in the Multiple Set Selector dialog, and
click Close.

GeoFrame 4.0 Introduction to CPS-3 Chapter 8 - 5


Set Selection, Creation, and Management Schlumberger

Exercise

Specifying New Sets (Set Creation)

Many operations in CPS-3 require the specification of a new set name. For
every new set you create, you will make use of the same dialog. Lets learn to
make use of the new set dialog by copying one set to a new set.

Copying Sets
1. In the CPS-3 Main Module menu bar, click Utilities > Sets > Copy to
open the Main Module Copy Sets dialog box.

2. In the Copy Sets dialog box, toggle the Data button on, click the
Filter button, and select the set g_wells, and click OK.

3. In the Copying Set dialog box, leave Set Type as Data, and click
New.

Chapter 8 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Selection, Creation, and Management

4. Enter my_data_set as a Name for the new Data set.

5. Select Scattered Points from the Subtype down-arrow list.

6. Select a Storage location of CPS. (Note that GeoFrame is also


available.)

7. Remember that Surface on these dialog boxes actually refers to


GeoFrame container type and name, so for Surface select Horizon
and Unknown in the next box for name.

8. Make sure that the Property Code is Depth, and the Z Unit is ft.
Click OK to close this dialog box.

9. Click OK to return to the CPS-3 Main Module.

10. In the CPS-3 Main Module menu bar, click Utilities > Sets >
List/Manage Sets and find my_data_set in the Data set list, verifying
that the attributes were set properly.

11. Click Close.


Note: When creating Polygon and Map sets in CPS-3, Storage Location, Container
Type, and Container Name are inactive.

GeoFrame 4.0 Introduction to CPS-3 Chapter 8 - 7


Set Selection, Creation, and Management Schlumberger

Notes on GeoFrame Container

A container represents a collection of information at a particular place in the


data base organization hierarchy. There are various types of containers, for
example, Horizon, Fault, and Unconformity. Containers also have names,
and are sometimes referred to as Surfaces. A Surface in GeoFrame holds,
among other things, grids and their associated fault boundaries, and even the
data sets which created the grids. Multiple versions of elements can also be
stored in the same container.

Other Set Management Facilities


Access to set and subset utilities is available by clicking on Utilities > Sets.
Except for Edit Data Set, these utilities allow manipulation of sets and
subsets, but not individual points.

We have already completed a Copy example in the previous exercise, but in


the next exercise, you will learn how the other utilities work.

Chapter 8 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Selection, Creation, and Management

Exercise

Renaming, Deleting, and Viewing Statistics of CPS-3


Sets

Renaming
1. In the CPS-3 Main Module menu bar, click Utilities > Sets >
Rename to open the Main Module Rename Sets dialog box.

2. In the Set Type column, toggle the Data (D) button on, and click
Filter.

3. Select my_data_set from the set list, and click Rename.

4. Type in the new name new_data_name, and click OK again.

5. In the Rename dialog, scroll down through the set list to verify that
the name was changed, then click on Cancel.

GeoFrame 4.0 Introduction to CPS-3 Chapter 8 - 9


Set Selection, Creation, and Management Schlumberger

Viewing Statistics
1. In the CPS-3 Main Module menu bar, click Utilities > Sets > View
Contents/Statistics to open the following dialog box.

2. Toggle the Basic Statistics button on.

3. In the Set Type column, toggle the Data button on.

4. Identify new_data_name from the list.

5. Click OK.

You will see statistics for the chosen set in the CPS-3 Status Information
window, in a form similar to the report below.

Chapter 8 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Selection, Creation, and Management

More sophisticated statistics are available in the Extended Statistics mode,


which allows statistics to be computed, for example, by subset, or by arbitrary
geographic polygonal areas.

Deleting Sets
Although you can delete a set from the Multiple Set Selector dialog box, you
may prefer using the Utilities menu, which allows you to change set types
more easily during deletion.

1. In the CPS-3 Main Module menu bar, click Utilities > Sets > Delete
to open Main Module Delete Sets dialog box.

2. In the Set Type column, toggle the Data button on.

3. Select the set new_data_name, click Delete and answer Yes to the
affirmation message.

GeoFrame 4.0 Introduction to CPS-3 Chapter 8 - 11


Set Selection, Creation, and Management Schlumberger

Chapter 8 - 12 GeoFrame 4.0 Introduction to CPS-3


Chapter 9
Defining a Display Environment and
Examining Data Coverage

Overview
Here, we will discuss the concept of mapping environments and their
attributes. We will show the difference in environment attributes required to
perform display functions, versus the attribute requirements to perform
modeling operations. We will discuss the reason for having multiple
environments, and, in a later chapter, we will have exercises to create
environments, store them, and edit them.

Just to get started, we will make the following simple, but true, statement:

Before you can display anything, like the map below, you must define a
display environment. Before you can create a grid, you must define a
modeling environment.

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 1


Defining a Display Environment and Examining Data Coverage Schlumberger

Granted, a default mapping and modeling environment is provided as


environment #1, however, it may not cover the exact area nor grid lattice that
you really want.

The material in this section is designed to provide formal definitions of


environments, their attributes, overall purpose, and management in a fairly
concise lecture format. You will learn most about environments by working
with your data. However, it is anticipated that you may refer to this section
frequently until you have gained a full understanding of the use of
environments.

Chapter 9 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

Definition of Mapping Environment Components


An Environment is a named collection of information associated with the
creation of maps or surface models in a CPS-3 project.

Attributes which are associated with environments are:


Name and optional Description
Usage Classification
Both Modeling and Display, or
Display only
Volume of Interest - minimum and maximum values for x, y, and z,
defining the mapping area and its vertical extents.
Geographic Coordinate System specification
Geodetic datum (ellipsoid plus shifts)
Map projection: transformation method and associated parameters
Rotation: origin and angle
Definition of horizontal and vertical units
Definition of horizontal and vertical scale factors
Definition of vertical property code

Attributes which are associated with Modeling operations are:


Definition of a grid geometry
name, description, units
lattice origin, offset
lattice spacing
rotation angle

Display Environment
A Display environment is used only for display purposes. It does not contain
the definition of a grid geometry. Data displayed through the currently active
Display environment will undergo the following procedures:
transformed to the active Geographic Coordinate System
scaled to the active scale
converted to the active horizontal units
clipped in x and y by the active Volume of Interest

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 3


Defining a Display Environment and Examining Data Coverage Schlumberger

Modeling Environment
A Modeling environment is used to create a grid or perform other modeling
operations. Think of a modeling environment as simply a display environment
to which a grid geometry has also been added. An environment which does
not contain a binset definition cannot be used for modeling, only display.
Grids created in modeling operations will assume the grid origin and spacing
of that defined in the currently active Modeling environment.

The Relationship between CPS-3 Modeling Environments


and GeoFrame Binsets (Grid Libraries)
The new concept of CPS-3 mapping environments is tied to the GeoFrame
data base, at least in terms of binsets or grid libraries. Every Modeling
environment in CPS-3 must point to a specific binset in GeoFrame. Display
environments, as you will discover, do not require grid lattice definitions.

Just as all sets must be associated with a particular coordinate system in


GeoFrame, the grid spacing in all CPS-3 surfaces must now be defined in
terms of a specified Grid library (binset). All binsets are stored in
GeoFrame. A binset is a formal definition of a grid lattice and has several
attributes, including x-spacing, y-spacing, rotation, x-offset, and y-offset, but
not all of the parameters are associated with a CPS-3 Modeling environment.
At present, however, all we need to know is that we must either define a new
binset (the most common option), or select one from an existing list, in order
to specify x and y spacings for surfaces.

Later in this course, exercises will be provided to demonstrate the mechanics


of how data can be stored in either CPS-3 or GeoFrame. Also, we will
demonstrate how to create, delete, and edit mapping environments.

Chapter 9 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

More Notes on Binsets


1. Binsets existed in GeoFrame before CPS-3 began offering Display
and Modeling environments. All three concepts are similar, in that
they define a collection of mapping parameters which control
high-level display operations and/or the granularity of a geological
model. The related concept of Grid Library, which is effectively
synonymous with binset in GeoFrame, was invented years ago to
guarantee that grids from different applications would overlay. Nodes
from all grids created under the same grid library would, by definition,
overlay.

2. Once a binset has been created, it cannot be modified through the


CPS-3 menus. Even if you could, you would NOT want to do this
because, in a sense, binsets are shared by all users in the GeoFrame
project, and modification would cause problems for all child-objects.

3. Be careful if you delete binsets because every surface you delete,


which was created with the binset to be deleted, will become unusable
in GeoFrame. Use the following procedure to find out which
GeoFrame surfaces were created with a particular binset:

Procedure: Determining a Particular Binset


1. From the GeoFrame Data Manager, go to Grid Libraries. (This opens the
Project Grid Library Data Manager.)

2. Highlight the desired binset and click the Get information... icon. (You will see
a list of all Surfaces containing grids which were created with the selected
binset.)

4. In our example, we picked x and y-intervals which divided evenly into


our x and y ranges. When the division is uneven, the system
automatically increases the x-maximum and/or y-maximum values so
that the division will be exact.

5. The coordinate system defined for the binset always becomes


associated with the environment for which we are defining a binset.
Thus, any previous coordinate system in the active environment will be
overwritten by the one in a selected binset. This is true for the binset
we created, and would also be true had we used a method of creating
our Modeling environment which involved the picking of an existing
binset from the list.

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 5


Defining a Display Environment and Examining Data Coverage Schlumberger

Making Use of Environments


To perform any function in, an appropriate environment must be selected.
Listing Available Environments
Environments are selected, created, and edited using the Select
Environment icon which opens the following dialog box.

Figure 9.1 Select Environment dialog box


Selecting An Environment for Display or Modeling or Both
Select an environment by clicking on it with MB1 in order to highlight
it in the Select Environment dialog box, and then clicking Select under
the Modeling or Display panel, or both, as appropriate. If the
highlighted environment has no binset defined, it will show No under
the Model column, and cannot be used for modeling.
Creating A New Environment
Click Create under the Modeling or Display panel, as appropriate.
Editing An Environment
Highlight the desired environment, and click Edit Current under the
Modeling or Display panel, as appropriate, or simply click the Edit
icon.

Chapter 9 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

Reviewing Environment Attributes


Highlight the desired environment, then click the Review icon.
Deleting Environments
Highlight the desired environment, then click the Delete icon.

In the many exercises which follow, you will become familiar with the use of
these functions.
Notes
If during the creation or editing of an a Modeling environment,
you select an existing binset, then the binsets x,y box and
geographic coordinate system replaces the x,y box and coordinate
system of the Modeling environment you are creating or editing.
Environments you define are stored in your current session file,
<login id>.1cps, which is located in the CPS partition of the
project. Refer to a later section regarding the storing and
retrieval of session files.
Because of the closer integration with GeoFrame, and the
institution of environments, CPS-3 procedures have become more
sensitive to units and domains. For example, an attempt to
compute borehole intersections with a surface set, which is stored
in milliseconds from a borehole set which was loaded from
GeoFrame in seconds, will result in an error message.
Just as procedure sensitivity to environments may cause error
messages in some cases, it will also provide benefits. For example,
during many operations, input data from sets with differing
coordinate systems will be automatically converted to match the
coordinate system of the output set.

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 7


Defining a Display Environment and Examining Data Coverage Schlumberger

Multiple Environments
The most apparent characteristic of a display or modeling environment is its
x,y extent - the area of interest, or, as it used to be called, the engineering
window.

From the sample map at the beginning of this section, it can be seen why more
than one environment is needed in typical projects. The Modeling
environment, as its name suggests, is used for defining that area where grid
nodes are computed. The Display environment, on the other hand, has more
to do with defining the extent of the graphic entities making up a basemap.
Continuing with the example map, a basemap might be required which
included all available seismic surveys including the 2D, but the area required
for gridding and volumetric calculation may cover only the smaller 3D survey.

In this case, we would define a small Display/Modeling environment


covering the 3D survey area, and a larger Display environment covering the
entire 2D extents, as shown below.

Figure 9.2 Example of CPS-3 ability to define 2D and 3D data on same


basemap

Thus, with this version of CPS-3, it is possible to perform graphic operations


covering one geographic area, while creating grids in another area at the same
time.

Chapter 9 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

Setting Up for Horizontal and Vertical Scaling and


Limiting
Besides establishing a traditional x,y map scale, Display environments let
you define the attributes needed to control vertical scaling, which is an issue
during 3D visualization provided by the Assembly tab in Modeling Office, as
well as the display of profiles, or cross sections.

This is how you set the horizontal This is how you set the Z-limits for
scale along the baseline for your Extended Statistics and 2D cross-sections.
cross sections.

This is how you set the Z-scaling


for your cross-sections. Exaggerated
Horizontal is a linear multiplier of the
baseline scale above, left.

Figure 9.3 Setting vertical and horizontal scaling and limits

Storing and Retrieving Environment Definitions


The current Environment Selector and Environment Editor are sufficient
for the management of environments in most cases. However, because your
environments are actually stored in your session file, they are somewhat at risk
when it becomes necessary to remove the session file during remedial project
cleanup activities. Certain temporary problems can be cleared up in CPS-3 by
removing the session file, and allowing the system to create a new version.
Unfortunately, you lose your environment definitions because they are stored
there. For this reason, the recommendation is to make use of the save and
read commands to periodically backup your current environment definitions.
These commands are activated in the Command line box at the bottom of the
Status Window. Here is how it works.

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 9


Defining a Display Environment and Examining Data Coverage Schlumberger

Make a permanent copy of your environments periodically


Whenever you create a new environment, save your session file as
follows:
Type save <file name> in the command line.
This causes your entire session file, which contains the latest values of
all parameters you have set, plus your environment definitions, to be
written to the file name <file name>.1cps. This file will reside in your
CPS partition.
Reinstating lost environments
If your session file is lost, you can reload all your environments in
append mode to your current session file as follows:
Type read <file name> in the command line.
This will cause all parameters and environments in the file
<file name>.1cps to be appended to your current session file.


Tip: When an environment with an associated binset is loaded, the system searches
the GeoFrame data base for the first binset which matches the attributes of
the one in the session file, and links it to the environment being loaded,
regardless of the name of the original binset. If a matching binset is not found,
the environment is not loaded. For this reason, it is not recommended to make
use of sessions files from other projects.

Chapter 9 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

Rotated Grids
By virtue of the attributes available in the definition of Modeling
environments, a new facility is now available in CPS-3 the ability to
create rotated grids. The rotation attribute in the coordinate system
specifications allows the definition of grids like the one shown in the map
below, which is based on the survey azimuth.

Figure 9.4 Example of a fault map with rotated grid

Association of Environments with Sets


Whenever any of these set types are created, attributes from the unrotated
active Modeling environment are stored in the parameter block of the set:
Data, Fault, Polygon. Attributes from the rotated active Modeling
environment are stored in the parameter block of the set: Surface, Map.

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 11


Defining a Display Environment and Examining Data Coverage Schlumberger

Specifying the Characteristics of Display and Modeling


Environments
As you create these two types of environments, you will notice that there is a
wide degree of flexibility in the specification of such parameters as X and Y
limits, and even grid spacing.

For example, when specifying the X and Y limits of a Display environment,


you can use the existing X and Y limits of any selected set. You can also type
the X and Y limits in directly in cartesian coordinates, or you can specify
them in decimal degrees.

When creating Modeling environments, you have the same flexibility. For
example, you have the ability to create a Modeling environment by simply
pointing to an existing binset in GeoFrame. If you use this procedure, please
make note of the following:


Note: If you happen to choose a method to create your Modeling environment
which involves the selection of a particular binset from the GeoFrame list of
binsets, you should know that binsets contain not only a grid lattice definition,
but specifications for x, y limits and a coordinate system, both of which will
supersede those values you may have already entered for your new
environment in the CPS-3 dialogs.

Chapter 9 - 12 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

Exercises for the Display Environment


Having loaded 2D and 3D location data, as well as top and bottom hole
locations, and the well paths, we are ready to define a Display environment
so that we can build a basemap of this location data.

The instructor should, by this point, have discussed the concept display and
modeling environments in CPS-3.

In these exercises, our workflow will be as follows:


set some standard graphic parameters
define a Display environment
display data locations
evaluate data coverage and decide which area to map and grid.

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 13


Defining a Display Environment and Examining Data Coverage Schlumberger

Exercise

Setting Standard Parameters

Before beginning with our graphic operations, we will set the background
color and the screen margins.

Set Screen Background Color

To change the color of the background of your screen, do the following:

1. In the CPS-3 Main Module menu bar, click Display > Display
Functions > Set Background Color.

2. Click on the Screen background color button to open the Select a


Color palette. A white background is recommended for this exercise.

Set Screen Margin

3. In the CPS-3 Main Module menu bar, click on Display > Display
Functions > Set General Display Parameters. This opens the
General Display Parameters dialog box.

4. In the Set Screen Display Margin section, set the Left, Right, Top,
and Bottom margins to 1, 6, 1, and 1, respectively.

Chapter 9 - 14 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

Exercise

Define a Display Environment for the Location Basemap

Well now create a display environment based on the extent of the 2D seismic
locations, because it appears to cover more area than the 3D locations. This
will give us a quick look at the extent of the data that we have.

We know that the 3D surveys in this project overlap and anyone who has seen
the two surveys in IESX knows that the 2D survey covers a much larger area
than the 3D. Therefore, we will define our initial Display environment so that
its x, y extents match those of the 2D survey data set.

1. In the CPS -3 Main Module, click the Select Environment icon.


This opens the Select Environment dialog box.

2. Click Create in the Display Environment section of the Select


Environment dialog box.

3. Click on the Lat/Lon Box tab, and ensure that the Coordinate System
is set to UTM, Zone 31.

4. In the Display Environment Editor dialog box, click on the


Copy/Compute tab.

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 15


Defining a Display Environment and Examining Data Coverage Schlumberger

5. In the Copy/Compute tab, do the following:


Enter GullFaks_Overview in the Name text entry field.
Enter 2d and 3d Survey Areas in the Remarks text field.
Toggle Copy Set Limits in the Action section to red, then toggle
Data in the Set Type section to red.
Click on the Pick set button in the Set Type section, and select the
mm_2D_gullfaks_shtpt data set from the list. Make sure the filter
in the file selection dialog is wide open ("all").
Click OK to return to the Display Environment Editor.

Chapter 9 - 16 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

In the Horizontal Scale section, set Map Mode to Direct and


enter 635.0 for Map Scale.
Please note that in certain early versions of GF4, the scale shows as
(m/in), which is incorrect. It should be (m/cm) since the computed
size is in centimeters
Press Return. The Width and Height for the Resulting Map Size
(Paper) is computed, and should be approximately 22 cm x 20cm.
Disregard the Vertical Axis and Scale section for now.

6. Click OK to end the creation process.

7. If the sizes appeared incorrect above, click on Edit Current in the


Display Environment panel and see if it now shows the correct value,
then click Cancel to return.

8. Highlight the GullFaks_Overview environment.

9. To see all attributes associated with this new environment, click the
Review Environment icon.

10. Close the report.

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 17


Defining a Display Environment and Examining Data Coverage Schlumberger

Post the 2D and 3D locations in the new Display environment

We will display only minimal information at first, just to see the orientation
and coverage of the data.

1. In the CPS-3 Main Module menu bar, click Display > Basemap to
open the following Basemap Display dialog box.

2. In the Basemap Display dialog box,


toggle Border to red in the Basic Elements section.
toggle Extended Data to red in the Display Sets section, and click
on the Pick Sets button.
select the mm_3d_85acip_survey data set, and click OK.
Click the Set Parameters button and set the following values:
turn off the Line display
turn on the line annotation display, set the size to .05, set
WhichEnd to Start of Line.

Chapter 9 - 18 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

turn off the shotpoint annotation.


turn on symbol parameters; set increment to 5, set size to .05.
click OK

3. Click Apply in the Basemap Display dialog box.

4. Repeat this process for the two other 3D survey location data sets,
"mm_3d_g1_survey" and "mm_3d_offset_survey", but change the line
color for each. Click OK out of the Basemap dialog.

At this point, we see that the first 3D survey locations may possibly go beyond
the lower border, and so well demonstrate how to edit the current Display
environment to make it larger.

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 19


Defining a Display Environment and Examining Data Coverage Schlumberger

Exercise

Enlarge the Current Display Environment Window

1. Erase the screen using the Erase current display icon located in
the CPS-3 Main Module.

2. Click the Select Environment icon, to open the Select


Environment dialog box.

3. In the Select Environment dialog box, highlight the


GullFaks_Overview environment.

4. Click on the Edit the highlighted environment icon or click the


Edit Current button in the Display Environment section of the
Select Environment dialog box. This opens the Display
Environment Editor.

5. In the Display Environment Editor window, click the Simple XY


Box tab.

6. In the Simple XY Box folder, modify the Y-Minimum value to be


6779000.0, and click OK.

7. Click OK in the Select Environment dialog box.

Chapter 9 - 20 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

Exercise

Redisplay the Three 3D survey locations

1. Return to the Basemap Display dialog box, and redisplay the same 3D
data sets as before.

2. Add a border on the display.

This quick posting shows the 3D locations now to be completely


contained within the environments x,y limits,

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 21


Defining a Display Environment and Examining Data Coverage Schlumberger

Exercise

Preparing a Location Basemap

Now we have an environment where we can see all of the data weve loaded.
Lets create a proper location map of the area. This exercise will introduce you
to some of the basemapping facilities in CPS-3.

Border, Labels, Scale Bar, and Title


1. Erase the screen using the Erase current display icon located in the
CPS-3 Main Module.

2. In the CPS-3 Main Module menu bar, click Display > Basemap or
the Display basemap icon to open the Basemap Display dialog
box.

3. In the Basemap Display dialog box, make the following settings:


Toggle Border in the Basic Elements section to red.
Toggle Labels in the Basic Elements section to red, and then click
Set Parameters to open the Display Window Labels dialog box.

4. In the Display Window Labels dialog box, type the following values:
X:label size = .5
Y:label size = .5
X:label increment = 5000.0
Y:label increment = 5000.0

5. Click OK to close the Display Window Labels dialog box.

6. In the Basemap Display dialog box, toggle Scale Bar in the Basic
Elements section to red.

7. Click Set Parameters to open the Display Map Scale Bar dialog box.

Chapter 9 - 22 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

8. In the Display Map Scale Bar dialog box, make the following
settings:
Toggle Use environment units, located across from Scale bar
units, to red.
Distance per scale bar segment = 2000
Number of segments in scale bar = 5
Positioning index = Center
X_position of scale bar = 8.0
Y_position of scale bar = -3.5
Scale conversison factor = 1
Text size = 0.4

9. Click OK to close the Display Map Scale Bar dialog box.

10. In the Basemap Display dialog box, toggle Map Title in the
Basemap Display section to red, and click Set Parameters to open
the Display Map Title dialog box and make these settings:
Bottom margin title = GullFaks - 2D, 3D, and Well
Locations
Bottom margin text size = 0.5
Bottom margin X position of text center = computed
Bottom margin Y position of text center = - 2.2
Left margin text size = 0.5

11. Click OK to close the Display Map Title dialog box.

12. Click OK in the Basemap Display dialog box to display the graphics
in the CPS-3 Main Module.

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 23


Defining a Display Environment and Examining Data Coverage Schlumberger


Note: It is a common occurrence that some graphic elements seem to fall off the
edges of the display. For example, the map title and scale bar, placed below
the y-axis are not visible at this time. However, we will continue with the
display of the basemap components, knowing that these elements have not
been lost and will be restored to visibility shortly.

Display 3D Survey Locations


1. Click Display > Basemap > Data and display the two 3D location
data sets, mm_3d_85acip_survey and mm_3d_offset_survey, just as
before, but use grey for both.

2. Click Display > Basemap > Extended Data and select the data set
mm_3d_g1_survey.

3. Click Set Parameters and make the following settings:


Toggle Line parameters to red.
Color = light blue
Width = thin line
Style = solid line
Toggle Line annotation parameters to red.

Chapter 9 - 24 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

Color = dark blue


Quality = Graphic Art
Font = 1
Size = .1
Which End = Start of Line
Enclosure = [ ]
Angle =Parallel

4. Click OK to close the dialog box.

5. Click Apply in Basemap Display dialog box.

Display 2D Seismic Line Posting


1. Click Display > Basemap > Extended Data

2. Click Pick Sets and select the data set 2d_gullfaks_shtpt, and click
OK.

3. Click Set Parameters and make the following settings:


Toggle Line parameters to red.
Color = black
Width = thin line
Shotpoint gap = 1000
Style = solid line
Toggle Line annotation parameters to red.
Color = red
Which end = Both Ends
Quality = Filled
Enclosure = Rounded
Font = 1
Angle = Parallel
Size = 0.2
Toggle Shotpoint annotation parameters to red.
Color = red
Mode = Incremental
Quality = Graphic Art
Increment = 50
Font = 3

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 25


Defining a Display Environment and Examining Data Coverage Schlumberger

Angle = Perpendicular
Size = 0.12
Toggle Symbol parameters to red.
Color = black,
Increment = 25
Size = 0.12
Click on the Symbol code button and select a hollow circle.
Mode = Incremental
Toggle z1 to gray.

4. Click OK to close the dialog box.

5. Click OK in the Basemap dialog.

Note that the Shotpoint annotation increment is every 50th, and the
Shotpoint symbol increment is every 25th.

The system continues by drawing the 2D posting as specified.

Move the Relative Position of a Map Layer


The smaller 3D survey seems to have become less visible. We will continue
by moving its posting location out from behind the blue survey.

1. Click Display > Map Layers.

2. Highlight the line Data Set mm_3d_offset_survey, and then click the
down arrow once, to position it in the list as shown above.

Chapter 9 - 26 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

3. Click OK. The smaller survey should move in front of the light blue
survey.

We will continue with posting of the boreholes and the bottom hole locations.

Post Borehole Locations


1. In the Basemap Display dialog box, toggle Data to red, and click
Pick Sets.

2. Select the set Boreholes_Depth_wpath, and click OK.

3. Click Set Parameters to open the Display a Set dialog box and make
the following settings:
In the Set Data Line Parameters section
Line style = solid line
Line width = thin line
Line color = black
In the Set Data Symbol Parameters section, Symbol size = 0.0.
In the Set Data Text Parameters section, toggle No text to red.

4. Click OK to close the Display a Set dialog box.

5. Click OK in the Basemap Display dialog box.

Post Bottom Hole Locations


1. In the Basemap Display dialog box, toggle Extended Data to red,
and click Pick Sets.

2. Select the set Well_Locations_wbloc, and click OK.


Click Set Parameters, and set the following values:
Toggle Symbol Parameters to red.
Color = black
Symbol code = select symbol number 16
Size = .125
Toggle z1 off.
Toggle Borehole Name to red.
Color = black
Size = .125

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 27


Defining a Display Environment and Examining Data Coverage Schlumberger

Quality = Graphic Art


X Offset = 0.0 or blank
Position = below
Y Offset = 0.0 or blank
Font = 3
Toggle all other categories off.

3. Click OK to close the dialog box.

4. Click OK to close the Basemap Display dialog box.

This completes the basemap, but as we noted, there are elements in the map
which we cannot yet see, such as the title at the bottom of the map.

Having spent a considerable time creating the display on the screen, lets save
our work, before worrying about the hidden parts.

Save the Display as a Map Set


To retain all the work we have done, we will save the graphics on the screen to
a permanent Map set. Afterward, we will also make a final change to our
Display environment, GullFaks_Overview, so that it also shows the graphics
which, at present, are hidden from view.

1. In the CPS-3 Main Module, click on the Save currently displayed


map icon. This opens the following dialog box.

2. Enter the name GullFaks_Overview, and click OK to save the


Map set.

All graphics on the screen, as well as the portions hidden from view, have now
been saved into a permanent CPS-3 Map set, which can subsequently be
displayed in its entirety with one operation.

Now lets zoom out and look at the hidden annotation around the map.

Chapter 9 - 28 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

View the Entire Basemap


Note the Reveal all graphics icon which is the third from the top. When
this icon is bright, it means that there are graphics posted which are beyond
the current x,y limits of the active Display environment.

1. To reveal the graphic in its entirety, click on the Reveal all graphics
icon. All of the displayed graphic is now visible.

The system creates a temporary display environment which is large enough


to show all previously displayed graphics. In this graphic state, the current
Display window is still represented by the border around the map, but we are
simply zoomed out, in a temporary window.

Create a Larger Display Environment Which Covers the


Entire Map
As you can see, the annotation we have added to the map has increased the
total area of the display which does not fit inside the defined Display window.
For convenience, we would like to increase the size of the display window so
that it is approximately the size that we now see. We have two ways to do this:
by using the feature Create Display Environment from Zoom, or
by saving the display as a Map set (which we have already done), and
then creating a new Display environment based on the X,Y limits of
the Map set.

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 29


Defining a Display Environment and Examining Data Coverage Schlumberger

Well demonstrate the first method:

1. Click the Create Display Environment from Zoom icon.

2. Call the new environment Gullfaks_Better_Overview, or


whatever you like. Click OK.

3. When the Display Environment is Changing dialog appears, click on


Copy Existing Graphics... at the top, and Clip To New Window... at
the bottom, and then click OK

Without even using the Environment dialog, we have created a new Display
environment, activated it, and transferred the entire contents of the screen
display to the new environment. Had anything gone wrong, or if we had taken
a wrong step along the way, we can still go back to the Map set we saved
earlier, and use it as a basis for the new environment.

Delete Old Display Environment


Now that we have a new Display environment which lets us see all of the
graphics at once, we can remove the first display environment,
Gullfaks_Overview, as follows:

1. Click on the Select Environment icon and in the subsequent


dialog, highlight the line for the Gullfaks_Overview Display
environment.

2. Click on the red X icon in the upper right-hand corner.

Now, let us assume that we wish to change the location of the scale bar, but
leave everything else in the map unchanged.

Removing/Replacing Map Layers


Remember, the graphics you see on the screen are composed by a series of
overlays, or layers. Each time you displayed a set or graphic entity on the
map, a layer was created. What we want to do is to remove the current layer
containing the scale bar, and put a new one on in a different location.

1. Click on Display > Map Layers to reveal the Map Layer Manager
dialog similar to the one below.

Chapter 9 - 30 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Defining a Display Environment and Examining Data Coverage

2. Toggle the Delete button to red, next to the layer named Map Scale
Bar, then click OK.
Having removed the Map Scale Bar, we will now reposition it in a
different location.

3. In the CPS-3 Main Module, click on the Display basemap icon to


open the Basemap Display dialog box.

4. Toggle Scale Bar to red, and click Set Parameters.

5. In the Display Map Scale Bar dialog box, retain all the previous
parameter settings, but toggle the Use cursor button for both the X and
Y-position of scale bar.

6. Click OK to close the Display Map Scale Bar dialog box.

7. Click OK to close the Basemap Display dialog box.


When the system is ready to accept the location of the scale bar, a
graphic cursor (a + symbol) will appear on the screen.

8. Position the cursor to the center, center-justified location of the scale


bar.
Once you click its position, the scale bar is drawn, but the graphic
cursor remains on the screen. You may click MB1 to accept the
current position, or you may click MB3 to reposition the scale bar at
another location.

GeoFrame 4.0 Introduction to CPS-3 Chapter 9 - 31


Defining a Display Environment and Examining Data Coverage Schlumberger

Chapter 9 - 32 GeoFrame 4.0 Introduction to CPS-3


Chapter 10
Accessing and Displaying
Interpretation and Well Markers

Overview
In GeoFrame 4.0, components of seismic interpretation are stored in the
GeoFrame data base and are accessible to CPS-3 in a variety of methods.
Some discussion of these new data relationships is needed, however, before
the exercises become intuitive. Here is a summary:

Accessibility of Seismic Components by CPS-3


3D seismic interpretation is stored as Grids in the data base and is visible
directly in the CPS-3 Set Selector dialog.

2D interpretation is stored as Line/Scatter Data and must be loaded into


the CPS-3 dsl by the GeoFrame Link.
Fault Cuts are not directly visible from CPS-3 but are loaded into the CPS-3
dsl with the GeoFrame Link.
Fault Contacts are not directly visible from CPS-3 and are loaded into the
CPS-3 dsl with the GeoFrame Link.
Fault Polygons are directly visible in the CPS-3 Set Selectors as Fault sets.

Seismic Attributes are stored as Grids in GeoFrame and are directly visible
in the CPS-3 Set Selector dialog.

2D locations are not directly visible in CPS-3 and are loaded into the CPS-3
with the GeoFrame Link.
3D locations are visible in CPS-3 and can be posted in the Display menu

Cartography in IESX can be imported into CPS-3 using


File/Import/IESX_Culture

GeoFrame 4.0 Introduction to CPS-3 Chapter 10 - 1


Accessing and Displaying Interpretation and Well Markers Schlumberger

Gridding 3D interpretation
Now, when gridding a 3D horizon, CPS-3 must be able to accept grids in
GeoFrame as input to the gridding algorithms. The Gridding menus have been
changed accordingly. Note the Single Surface gridding dialog now allows the
selection of either Data or Grid input:

How do I distinguish an interpretation grid from other


grids?
One of the most common objects stored in GeoFrame are grids. The problem
arises on how to identify the primary interpretation grids for a particular
horizon from other derivative grids which can be computed by dozens of
other applications. This problem is compounded by the fact that all time
interpretation grids have the name Time and all depth interpretation grids
have the name Depth in IESX. A similar repetitive grid naming convention
exists in Charisma.

However, as we examine the file selection dialog in CPS-3, our searching can
be clairified by the following facts:
There can be only one Time interpretation grid per horizon
There can be only one Depth interpretation grid per horizon
There will be only ONE set in the CPS-3 set selection dialog having
Name = Time, Surface = the desired horizon name, and Grid
Library = the correct grid library for the horizon. This set will be the
Time interpretation for the Horizon.

Chapter 10 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Accessing and Displaying Interpretation and Well Markers

There are other ways of identifying interpretation grids as well. In any


GeoFrame dialog which allows the display of component attributes, you can
examine the Source Code and Property Code attributes of a grid. If the
Source is Charisma or IESX, and the Property Code is Time, then this
is a pretty good indication that you are looking at the primary time
interpretation for a particular horizon. A Property Code of Depth would
indicate primary interpretation in depth. Other, derivative grids will have
different Property Codes, for example, Integrated_Reflection_Strength. A
different Source Code also indicates that the grid is not primary interpretation,
for example, Surface Manager means that the grid was derived from some
other grid.

Interpretation Models and CPS-3


A new concept in GF4.0 is the Interpretation Model. The interpretation
model is a name given to some collection of interpretation objects - 2D line
interpretation, 3D grid interpretation, fault cuts, fault contacts, and fault
boundaries, which are related in some way, for example, all being done by the
same interpreter. The interpretation model may consist of several horizons and
each horizon can consist of multiple patches.

In many applications, the Interpretation Model can be used as a filter when


selecting data. For example, during Horizon Modeling in Framework
Modeling, you may choose to select input data only from a particular
interpretation model. At this time, CPS-3 does not interact with the
Interpretation Model concept. All data is seen in the set selection dialog,
regardless of its model.

GeoFrame 4.0 Introduction to CPS-3 Chapter 10 - 3


Accessing and Displaying Interpretation and Well Markers Schlumberger

Destinations of Interpretation Components When


Imported into CPS-3
When imported from GeoFrame, the following interpretation components are
stored as indicated:
Geological horizon markers are stored as CPS-3 Data sets (.dcps)
2D horizon interpretations are stored as CPS-3 Data sets (.dcps)
3D horizon interpretations are stored as CPS-3 Grid sets (.scps)
2D/3D fault segment interpretations are stored as CPS-3 Data sets
(.dcps)
Seismic fault contacts are stored as CPS-3 Data sets (.dcps)
Seismic fault polygons are stored as CPS-3 Fault sets (.fcps)

Chapter 10 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Accessing and Displaying Interpretation and Well Markers

Exercises for Data Retreival


In these exercises, we will retrieve those interpretation components which are
not directly visible in CPS-3, and will demonstrate how to identify those that
are.

Specifically, we will show how to access all necessary interpretation data


3D interpretation
well markers
fault boundaries

in order to create grids for the following horizons:


Bunnkritt
Tarbert
Ness
Rannoch
Drake

The fault boundaries we will use here are the polygonal fault boundaries
which represent the intersection of the fault surface with the horizon surface.
In a later chapter, we will use fault segment data in order to create grids for
one or more of the fault surfaces.

After loading or identifying the data for these horizons, we will look at their
basic statistics, and then display each data set to get an idea of the density and
distribution of its points. This will help us establish gridding parameters.

GeoFrame 4.0 Introduction to CPS-3 Chapter 10 - 5


Accessing and Displaying Interpretation and Well Markers Schlumberger

Exercise

Locate 3D Seismic Horizon Interpretation and


Associated Fault Boundaries

In GeoFrame 4, 3D seismic interpretation for horizons does not need to be


transferred into CPS-3. It is already visible in the CPS-3 set selection
dialogs as grids. From the previous lecture, we learned how to identify it by
Surface and Grid Library, or Property Code and Source Code.

1. Click on Utilities > Sets > List_Manage_Sets

2. Select grid as the Set Type, Select only GeoFrame for the Storage,
and then click the Filter icon.

3. Click on the Name column heading

From the Surface Name column we see that the first five grids, all named AA,
represent a depth interpretation for each the five horizons which we use in this
project. You may not see these grids in your project listing, but these
particular versions of the interpretation were done in Charisma.

The important point is that no loading is necessary. CPS-3 has direct access
to the 3D interpretation for gridding.

Chapter 10 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Accessing and Displaying Interpretation and Well Markers

We will be using a different version of the interpretation for these horizons. In


particular, those 3D seismic interpretation grids in GeoFrame which begin
with the prefix mm_ will be used to identify the data we want to use in this
class.

For example, these are the seismic interpretation grids we will use for our
models in this course. Note the filter settings.

In the same way, the fault polygons associated with some of these 3D horizon
interpretations can also be seen directly in the CPS-3 Set Selector. Fault
polygons created during seismic interpretation will be seen as below:

4. In the List/Manage Sets dialog, select Fault as the Set Type, select
GeoFrame as Storage, then click Filter.

GeoFrame 4.0 Introduction to CPS-3 Chapter 10 - 7


Accessing and Displaying Interpretation and Well Markers Schlumberger

In this project, we see only these two fault boundary sets, but in practice, there
are usually more - typically one for each interpreted seismic horizon, and even
several versions. It is up to the user(s) to keep track of these boundary sets by
using the assignment facilities in IESX.

If Interpretation Models are used, then it is easy to keep track of these fault
boundary sets at the seismic interpretation level, although only one version of
each fault boundary is allowed for one horizon.

In a similar fashion, in CPS-3, there are ways of associating or disassociating


fault boundary sets with particular horizon grids seen there.

Chapter 10 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Accessing and Displaying Interpretation and Well Markers

Exercise

Load Well Markers with GFLink

1. From the CPS-3 Main Module, click Tools > GeoFrame Link to
open the CPS-3 GeoFrame Link dialog box.

2. In the CPS-3 GeoFrame Link dialog box, click the Load From
GeoFrame tab.

3. In the Load From GeoFrame folder, click Data Types to open the
GeoFrame Surface Types dialog box so that we can focus on the type
of data we want to bring across.

4. In the GeoFrame Surface Types dialog box,


click Horizons under Containers
click Markers under Representations, and then click OK.

5. Return to the CPS-3 GeoFrame Link dialog box, click GeoFrame


Data, to open the GeoFrame Surface Selection dialog box.

6. Select Depth from the Vertical Domain pop-up list.

GeoFrame 4.0 Introduction to CPS-3 Chapter 10 - 9


Accessing and Displaying Interpretation and Well Markers Schlumberger

7. From the Containers list, pick BUNNKRITT, DRAKE, NESS,


RANNOCH, and TARBERT.


Note: For each pick under the Containers list, a DEPTH entry under the
Representations list should appear.

8. Highlight all items on the right by clicking the Select all


Representations in the list icon, and then click OK.

Selected items appear in the GeoFrame Link dialog box as above.


The [D] notation to the left of the name in the CPS-3 Output Sets list
indicates that the output set will be a Data set.

9. Highlight all five items in the CPS-3 Output Sets list, and then click
Run.

10. Click Exit when finished.


This demonstrates the correct method for retrieving well markers in
CPS-3, which, as we see, are not automatically visible from CPS-3, as
are interpretation grids and fault boundary sets.
We will not be using these particular marker sets in our exercises, and
so well remove them as described in the next step.

Chapter 10 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Accessing and Displaying Interpretation and Well Markers

11. Return to the CPS-3 dialogs, and from the List/Manage Sets dialog,
delete these five markers data sets which we just loaded. They will be
found in the CPS-3 storage area, not in GeoFrame. Do not remove
anything from the GeoFrame data area:

BUNNKRITT_Depth
DRAKE_Depth
NESS_Depth
RANNOCH_Depth
TARBERT_Depth

GeoFrame 4.0 Introduction to CPS-3 Chapter 10 - 11


Accessing and Displaying Interpretation and Well Markers Schlumberger

Exercise

Well markers as scatter sets

In this class, we will be using a different set of markers for each of these
horizons than the ones which are available via the GFLink. The ones we will
use were loaded into GeoFrame from a different source, and because the
source was external to this current project, they are visible to CPS-3 in its file
selector dialog, as well marker scatter sets. See below:

Chapter 10 - 12 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Accessing and Displaying Interpretation and Well Markers

Exercise

Summary of Basic Horizon Interpretation Data Available

Having spent some time discussing the various data available for our horizon
modeling, lets look at a quick summary of what we have for each horizon in
stratigraphic order for the Bunnkritt, Tarbert, Ness, Rannoch, and Drake

3D Interpretation Well Markers Faults

mm_BUNNKRITT_50X50_Depth_intrp mm_BUNNKRITT_Depth_wmrkr none

mm_TARBERT_Depth_intrp mm_TARBERT_Depth_wmrkr mm_Tarbert

mm_NESS_Depth_intrp mm_NESS_Depth_wmrkr mm_Ness

mm_RANNOCH_Depth_intrp mm_RANNOCH_Depth_wmrkr none

mm_DRAKE_Depth_intrp mm_DRAKE_Depth_wmrkr none

The Bunnkritt unconformity is unfaulted and the Rannoch and Drake do not
have permanent fault boundary sets at this time.

GeoFrame 4.0 Introduction to CPS-3 Chapter 10 - 13


Accessing and Displaying Interpretation and Well Markers Schlumberger

Exercise

Examine Data Statistics

Let us look at the statistics of some of the data we have just loaded.

1. From the CPS-3 Main Module, click Utilities > Sets > View
Contents/Statistics to open the View Set Contents/Statistics dialog
box.

2. In the View Set Contents/Statistics dialog box,


toggle Basic Statistics to red
toggle Data [D] to red
Highlight GF:mm_BUNNKRITT_Depth_wmrkr.
This data set contains the well markers for the Bunnkritt horizon. The
GF: prefix indicates that they are stored in GeoFrame, not the CPS-3
dsl.
Click OK

3. The statistics should appear in the CPS-3 Status Information


window, as below:

Chapter 10 - 14 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Accessing and Displaying Interpretation and Well Markers

Note that the basic statistics report always provides information


regarding the sets native coordinate system and transformations first.
In the second section, the x, y, and z minimums and maximums are
displayed, along with units information. If a set has more than one z-
field, the limits of all z-fields are displayed.

4. Display the basic statistics for the following Data sets:


mm_TARBERT_Depth_wmrkr
mm_TARBERT_Depth_intrp
mm_NESS_Depth_wmrkr
mm_NESS_Depth_intrp

5. Verify that their z-ranges are specified in Depth (m) and are in the
following range:
Tarbert: 1781 - 2389
Ness: 1712 - 2400

GeoFrame 4.0 Introduction to CPS-3 Chapter 10 - 15


Accessing and Displaying Interpretation and Well Markers Schlumberger

Let us review the fault boundaries for the Tarbert and Ness horizons.

6. From the CPS-3 Main Module, click Utilities > Sets > View
Contents/Statistics.

7. In the View Set Contents/Statistics dialog box, toggle Basic


Statistics to red.

8. Toggle Data to gray, and toggle Fault to red.

9. Highlight the following Fault sets:


GF:mm_Ness
GF:mm_Tarbert

10. Click OK.

11. Determine from the statistics whether or not these fault sets have any
z-values.

Chapter 10 - 16 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Accessing and Displaying Interpretation and Well Markers

Exercise

Rename faults, and remove z-values

In this exercise, we are going to remove the mm_ prefixes from the fault set
names, and strip off their z-values.

1. In the CPS-3 Main Module, click Utilities > Sets > Rename to open
the Rename Sets dialog box below.

2. Toggle only Fault [F] to red, and click Filter

3. Highlight the GeoFrame mm_Ness Fault set, and click Rename at the
bottom.

4. Provide a new name Ness, and then click OK.

5. Repeat the process for mm_Tarbert, changing its name to


Tarbert.

GeoFrame 4.0 Introduction to CPS-3 Chapter 10 - 17


Accessing and Displaying Interpretation and Well Markers Schlumberger

6. Exit from the Rename dialog, and then click Utilities > Sets > Copy.

7. Highlight the GeoFrame set Ness, and click Copy.

8. In the dialog which appears, set Output Set Type to Polygon, and
click New.

9. Define a Polygon set with the same name, Ness, define it to be stored
in GeoFrame, and click OK, then OK again.

10. From the Copy dialog, repeat the process for the Tarbert fault
boundary set.

11. Still in the Copy dialog, toggle Set Type to only Polygon and click
Filter.

12. Highlight the Ness polygon, and click Copy.

13. Toggle Output Set Type to Fault and click Pick. Choose the original
Ness fault set and click OK, then OK again, to overwrite the original
version.

14. Repeat this process for the Tarbert polygon.

15. Now repeat the statistics on both of these fault sets to verify that there
is no z-value field.

16. Make sure that your display environment is still set to Quick_Look.
Erase the screen, and click Display > Basemap
Toggle Border to red.
Toggle Faults to red, and click Pick Sets.
Select the Tarbert fault set, and then click OK.

Chapter 10 - 18 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Accessing and Displaying Interpretation and Well Markers

GeoFrame 4.0 Introduction to CPS-3 Chapter 10 - 19


Accessing and Displaying Interpretation and Well Markers Schlumberger

Exercise

View Data Sets before Gridding

Without worrying about grid spacing or other gridding algorithms, lets have a
quick look at these data sets, which are really interpretation grids. We will
display each one using color-shaded symbols. This will not only show us the
data distribution and density, but will also give us a preview of the structure in
some cases.

Bunnkritt Interpretation Grid Set


1. In the CPS-3 Main Module, click the Select environment icon.

2. Select the Gullfaks_Overview environment, and click OK.

3. Click Utilities > System > Set_Toggle_Switches, and make sure that
the switch Show Graphic Entities... does not have a red box next to it.

4. Click Display > Basemap, to open the Basemap Display dialog box.

5. In the Basemap Display dialog box, make the following settings.


Under Basic Elements, toggle Border and Labels to red.
Under Display Sets, toggle Grid Nodes to red, and click Pick
Sets.
Set the filter attribute Storage = only GeoFrame, then click Filter.
Select mm_BUNNKRITT_50x50_Depth_intrp, and click OK.
Click Set Parameters, and make the following settings in the
Display a Set dialog box:
Symbol code = 122
Symbol Size = .3
In Set Grid Node Text Parameters, toggle No text to red
In Set Overpost Protection Parameters, set both values to 1.
In Set Grid Node Elevation Coloring Parameters, set
Surface coloring method = Use color range.
In Set Palette Parameters, Invert Palette = NO

Chapter 10 - 20 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Accessing and Displaying Interpretation and Well Markers

Click OK, then OK again to start the display.

This unconformity is unfaulted, and its interpretation is very dense.

GeoFrame 4.0 Introduction to CPS-3 Chapter 10 - 21


Accessing and Displaying Interpretation and Well Markers Schlumberger

Tarbert Interpretation Grid Set


1. Erase the screen using the Erase current display icon or
Display > Display Functions > Erase Display in the CPS-3 Main
Module.

1. Use the previous procedure to display the


mm_TARBERT_Depth_intrp interpretation grid set. The system
should remember the parameter settings, and you should only have to
specify a different grid name.

This horizon has large erosion zones next to the fault zones which have been
eroded by the previously displayed Bunnkritt unconformity.

Display the fault set Tarbert on top of this display if you like.

Chapter 10 - 22 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Accessing and Displaying Interpretation and Well Markers

Ness Interpretation Grid


Use the same method as before to display the mm_NESS_Depth_intrp
interpretation grid.

This horizon also has similar erosion zones, but are limited to the Eastern half
of the map.

Display the fault set Ness on top of this display, if you like.

GeoFrame 4.0 Introduction to CPS-3 Chapter 10 - 23


Accessing and Displaying Interpretation and Well Markers Schlumberger

Rannoch and Drake Interpretation Grids


The Rannoch and Drake horizons are not used much in this training course,
but their interpretation grids are shown below.

Rannoch

Drake

Chapter 10 - 24 GeoFrame 4.0 Introduction to CPS-3


Chapter 11
Gridding Fundamentals

Overview

Figure 11.1 Data coverage polygon and grid lattice

The purpose of this chapter is to introduce you to the most important aspects
of gridding. You will learn how to select the most critical gridding parameters
which affect the quality and appearance of your surface. There are many
algorithms from which to choose, and many parameters which can affect your
map. However, for the typical mapping task, very good maps can be generated
using only a few of these parameters. An Advanced Topics class is available
for those who wish to study the inner workings of the gridding algorithms
more deeply, but the schedule for this course does not allow for all algorithms
and their parameters to be covered in depth. In this course, we will try to take
the pragmatic approach and give you the tools to get the best map possible in
the shortest time.

It is recommended to read the chapter in the on-line Users Guide which


covers gridding. It gives many details which may be overlooked in this course.

GeoFrame 4.0 Introduction to CPS-3 Chapter 11 - 1


Gridding Fundamentals Schlumberger

What is Gridding?
Gridding is the process of transforming randomly located or other data into a
regularly spaced lattice of values representing the z-dimension of the x, y, and
z data. After the transformation, the data points are redundant and
unnecessary, since the model of the surface is now embodied totally within the
grid and the associated fault traces, if any. Even though defined by a finite
number of points, the grid is meant to be thought of as continuous surface.

Grid Terminology

1 2 Grid Columns 5 6 7 8 9
YMAX
4550

Row 2

Grid Node
Row 3

Row 4

Row 5

Grid
YINC

Cell
1800
YMIN
3400 XINC 7800
XMIN XMAX
Figure 11.1 Map grid and components

The above grid covers a range in X of 3400 to 7800, and in Y of 1800 to 4550.

This grid is a 6 by 9 grid, meaning 6 rows by 9 columns. The grid cell size,
the number of rows and columns and the grid range are related as follows:
X-interval = Range in X divided by (Number of Columns -1)
Y-interval = Range in Y divided by (Number of Rows -1)

CPS-3 may increase XMIN or YMAX to ensure that the range in x and y is
evenly divisible by xinc and yinc.

Chapter 11 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Gridding Fundamentals

Judging the Quality of the Grid


After the gridding has taken place, the quality of this model can be determined
by inspection of some manifestation of the grid, for example, contours. If the
contours indicate that the values of the grid near the data points are consistent
with the data point values, then the first criteria has been passed.

Next, examine the contours in the areas of the grid between the data points.
Are the contours reasonable?
Are they what you would expect?
Are they relatively smooth, considering the data?
Do they continue the trends established by the data?

If the answer to these questions is yes, then the second criteria has probably
been fulfilled. Remember that after gridding, your model is represented by the
grid and fault traces - the data has become redundant.

Gridding Algorithms
As you will see, CPS-3 has many gridding algorithms, but each of them is
designed to solve the basic gridding problem below:
Given the data points and fault traces above, create a model of regularly-
spaced grid points which honor the data and exhibit a smooth transition of
the surface between data points and the edge of the map.

Figure 11.1 Common gridding problem showing data and fault traces

GeoFrame 4.0 Introduction to CPS-3 Chapter 11 - 3


Gridding Fundamentals Schlumberger

How Do I Prepare for Gridding?


At first, we will assume that the only data to be gridded is the well data shown
above. The data for this class includes both 2D and 3D seismic interpretation
as well, but for the moment we will disregard it and focus on the wells.

Following is a checklist to help you most effectively grid your data:


Inspect your data points
Inspect your fault traces
Decide on the modeling area
Decide on grid spacing
Decide which algorithm to use
Decide how to set gridding parameters

Data Inspection and Selection of Modeling Area

Inspecting our data shown in the previous figure, let us assume for a minute
that we want to create a grid from only this well data and the faults shown. We
will assume that we want to include the far western well in the grid and so the
modeling area will cover the area shown. Looking at the fault traces, we note
that the horizontal separation is narrow for some of the faults, but significant
for others. We also note fairly thin fault blocks between several of the faults.

Determining the Grid Cell Size

In its most basic form, the method for determining the proper grid spacing can
be stated as follows:
Find the closest two data points whose difference must be distinguishable in
the grid and let the grid spacing be 1/2 the distance between them.

This method is almost guaranteed to yield a grid having the desired criteria,
that is, a contour map which shows the difference between the two chosen
points. However, there may be other limiting conditions which you should
consider before settling on this grid spacing. For example, it could be that
such spacing generates a grid whose number of rows and columns is so large
that the gridding takes an inordinate amount of time. Is is also possible that
such a spacing is so small that it produces a grid which contains a very large
amount of high-frequency noise. While the stated method of choosing a grid
interval is a very good way to start, there are even more reasons why you
should look at other characteristics of your data as shown below.

Chapter 11 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Gridding Fundamentals

Looking at our simple example again in the figure below, we can get a better
feel for the scale of our data and the grid spacing by introducing a graphic
lattice on the display. The lattice shown is 500 meters on a side. Judging from
the spacing of the well points, 500m is not a good grid spacing since there are
several points closer than this whose difference we will want to see.

Also note the size of the grid cell relative to the size of the thin fault blocks.
These blocks will hardly be defined with such large spacing. Sometimes, the
ultimate criteria for defining a grid size is the horizontal separation in the fault
zone. If it is desired to define the fault zones for volumetric purposes, then the
chosen grid size must provide enough nodes in each fault zone so that it can
be modeled along with the fault blocks.

Figure 11.1 Data points and fault traces with grid lattice

If we were to use the distance between the two closest points criteria for
selecting the interval in this data set, we might choose the two points, each of
which borders on a north/south-oriented fault trace toward the southeast center
of the map. As we have just noted, however, the width of the fault blocks in
that area is even smaller than the distance between these points. Clearly, the
width of these fault blocks should be the defining feature to be resolved in
the final grid. We would therefore choose a grid interval of approximately
100m in this example, which will allow us to define the fault blocks, but not
all of the fault zones.

GeoFrame 4.0 Introduction to CPS-3 Chapter 11 - 5


Gridding Fundamentals Schlumberger

Considering only the well data and the fault patterns, we have determined a
reasonable grid interval based on close inspection of the features in our data.
But in your project data, you may also have 2D or 3D seismic interpretation
to go along with the well data. This same sort of analysis should be applied to
the seismic data.

As you can see, there is no magic formula for determining a gridding interval,
other than deciding on the size of the smallest feature you want to resolve in
the resulting surface.

How Do I Choose A Gridding Algorithm?


If your gridding task falls into one of the following special categories, you
should use the algorithms which are especially recommended for those tasks.
Otherwise, you should use the Convergent Gridding algorithm.
create a stratigraphic display of rock types
create fault plane maps whose features are highly linear
create a grid honoring very dense grid-like data
gridding isopachs with partial penetration data
create a grid having a constant value
create a mathematically-correct trend grid
create a mathematically-exact evaluation of a polynomial in x and y
create a grid of distance or density statistics from a data set

Those gridding tasks mentioned above are special cases and do not represent
the typical task of creating a structural model from well data, fault traces, and
seismic interpretation, which is the most common modeling exercise. The
operations above and the algorithms used for the creation of their surfaces are
important to learn about, but in the exercises for this chapter, we will focus on
the Convergent Gridding algorithm, which is recommended for day-to-day
structural modeling.

Chapter 11 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Gridding Fundamentals

List of CPS-3 Gridding Algorithms

Convergent

A very stable, fast, general purpose algorithm for computing a smooth, but
accurate fit to almost all types of data. This algorithm provides trend-like
extrapolation, and being the flagship of the CPS-3 gridding algorithms, it
should be the first one considered for almost any structural data.

Below is a schematic showing the refinement of a surface being created by


successive iterations of the Convergent Gridding algorithm. After
establishing an initial trend with a coarse grid, each successive step reduces
both the grid cell size, and the radius of influence for each control point, until
the surface is locally tied to the data.

Figure 11.1 Internal surface refinement by the Convergent Gridding


algorithm

GeoFrame 4.0 Introduction to CPS-3 Chapter 11 - 7


Gridding Fundamentals Schlumberger

Contour to Grid

Contour to Grid is a derivative of the Convergent Gridding algorithm with


the parameters optimized to honor digitized contour data. When generating a
grid using digitized contour data as your input, this algorithm will provide the
best fit to the contour data.

Least Squares

Least Squares is a general purpose algorithm used for computing a best-fit to


scattered data points. It retains the regional trend surrounding grid nodes,
while effectively smoothing out some local variation. Although not a good
extrapolator, this algorithm is sometimes used for gridding fault surfaces
which have little curvature. Before the Convergent Gridding algorithm was
developed, Least Squares was the vanguard gridding algorithm in CPS-3.

Moving Average

This is a simple, general purpose algorithm used for computing an average fit
to scattered data. Moving Average is mostly used for a quick-look or for
gridding noisy or statistical data. Use this algorithm when you do not want the
surface to contain values which fall beyond the range of the data.

SNAP

SNAP is the building block algorithm incorporated into Convergent


Gridding. It can be used by itself to grid dense data (3D Seismic,
Bathymetry), or for fitting data to an existing grid.

Isopach

Isopach is a specialized version of Least Squares or Convergent Gridding


which treats zero values as surface limits. All positive, non zero-values are
honored while zero-values are used to define the zero line for the Isochore.

Trend

Trend is a general purpose algorithm used for computing data trends. You
specify the order of the trend (1st, 2nd, etc.).

Polynomial

Polynomial is a special purpose algorithm used for computing fixed value


grids as polynomial functions of x and y.

Chapter 11 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Gridding Fundamentals

Step

Step is a special purpose algorithm for use in producing lithology, soil or


variable hydrocarbon contact maps. Grid node values are set to the value of
the nearest control point.

Distance

Distance is a special purpose algorithm used to quantify the spatial


distribution of the data points. Grid node values equal the distance to the
nearest control point.

Density

Density is a special purpose algorithm used for modeling data distribution.


Grid values are set to the number of data points falling within the Search
Limit Radius (SLM) centered on the node.

How Do I Set Gridding Parameters?


In this course, we will focus on the Convergent Gridding algorithm. For the
purpose of this course, and possibly for most of the data you will be gridding
in the near future, there are only a few parameters which you will routinely
consider changing.
Final grid interval
Initial grid interval (Computed)
Number of Nodes To Snap To (16)

There are many other parameters which can be manipulated in the


Convergent algorithm, but for the scope of this class, we will highlight these
three as being by far the most important.

In the first gridding attempt of any new surface, the recommendation is to


determine the Final grid interval, just as we discussed earlier in this chapter,
and to take the default values (shown in bold italics above) for the other two.
The only time you may not want to take the default value for the Initial grid
interval is when you know that you have very dense data. If this is the case,
you may want to reduce this number to only twice the Final grid interval,
and also reduce the Number of Nodes to Snap To to 2 - 4.

If, after the first attempt, you are not satisfied with the grid, use the following
guidelines for changing one or several of the three parameters above.

GeoFrame 4.0 Introduction to CPS-3 Chapter 11 - 9


Gridding Fundamentals Schlumberger

Common Gridding Problems and Their Solutions


The following table contains some of the common gridding problems
encountered and their solutions.

Problem Solution
Grid does not honor control points Make Final grid interval smaller

Grid takes forever to compute Make Final grid interval larger or Initial
grid interval smaller

Not enough extrapolation beyond data Make Initial grid interval bigger
points

Holes in the final grid Make Initial grid interval bigger

Grid too noisy Make Final grid size larger or do a single


smoothing operation

Grid does not show features inherent in Make Final grid interval smaller
the data

How Do Fault Traces Affect Gridding?


Many surfaces to be gridded are known to be faulted, and the intersections
have already been located within the horizon as fault traces or fault
boundaries. Other than for display considerations, it does not matter how a
fault boundary is geometrically defined in CPS-3. For example, a non-vertical
fault boundary could be digitized in any of these ways:
a series of straight-line segments
an upthrown polyline and a downthrown polyline
a closed polygon around the entire fault zone

Regardless of the gridding algorithm chosen, fault boundaries are utilized in


the same manner by all algorithms as explained below.

The spacing of the nodes in the figure below represents the 50m x 50m grid
spacing which we decided to use for this training data. This figure shows a
zoomed-in area of our data, and, for purposes of this faulting discussion, we
will assume that the only data we are using for gridding is the well data.

This figure shows how data is selected to be used or not used during the
computation of a grid node value, depending upon its spatial relationship to
the node being computed and the fault patterns.

Chapter 11 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Gridding Fundamentals

Figure 11.1 Representation of 50m x 50m grid node spacing

Any algorithm in CPS-3 which is computing the value of a grid node, such as
the one marked + in the figure above, will treat each fault line segment as a
barrier during the interpolation process. Data points which can potentially
contribute to the value of a node, must first pass a visibility test to see if they
will be used or discarded. If any point is in the shadow of any fault line
segment, then it will not be used in the computation of the node. For example,
in the figure above, points A, B, C, and D are in the shadow of at least one of
the faults, and will therefore not be used in the computation of that nodes
value. None of the other points are in the shadow of any other faults, and so
they will be used for the computation.

The idea is that only data points which are on the same side of a fault as the
node being computed will be used to compute that nodes value. Nodes on the
other side of a fault or on another fault block are not used.

Note that this same visibility criteria is also used by the CPS-3 grid-based
interpolator during the computation of other manifestations of a surface, such
as contouring, volumetrics, and refinement. That is, all grid-based procedures
in CPS-3 are cognizant of where the faults are located and will modify their
results based on the faults, as long as they are specified on input.

GeoFrame 4.0 Introduction to CPS-3 Chapter 11 - 11


Gridding Fundamentals Schlumberger

Gridding Decisions - 2D/3D Seismic Examples


We have discussed how to choose a grid cell size with simplistic well data,
and now we provide some guidelines for other geometries. For each of the
types of data distributions shown below, we will give recommendations for the
Final grid spacing, the Initial grid spacing, and Number of Nodes to Snap
To.

2D Seismic

In general, for 2D seismic:


Final interval - roughly the same as the shot point spacing, but be
careful not to make it so small as to create noise along the lines
Initial interval - as large as 1/2 the distance between the two
furthest-apart contiguous lines
Number of Nodes To Snap To - 16

Figure 11.1 2D seismic display

Chapter 11 - 12 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Gridding Fundamentals

Line-Decimated 3D

The characteristics of line-decimated data is similar to 2D seismic - very


dense points along lines which are far apart, relative to the points. This type of
data results when the interpreter interprets every 5th, 10th...etc. line.

Figure 11.1 Example of Line-Decimated 3D data

For Line-Decimated 3D:


Final interval - 1/2 to 1/4 the distance between lines
Initial interval - distance between lines
Number of Nodes to Snap To - 4

GeoFrame 4.0 Introduction to CPS-3 Chapter 11 - 13


Gridding Fundamentals Schlumberger

Dense 3D

The characteristic of this data is its homogeneous density. In the example


below the homogenous pattern is prevalent, but broken by large void areas in
the data. Here, the interpreter appears to have interpreted every line or every
other line, except in the void areas. Some of the void areas represent faults,
others may represent unclear seismic information.

Figure 11.1 An example of dense 3D interpretation

For dense 3D, the first thing to decide is if you really need all the data points
which may be present. In some cases, 25m or 50m cdp spacing may lead to
grids in CPS-3 which exceed the reasonable limits. At present reasonable
limits are determined accordingly:
150x150 grid - a modest grid
300x300 grid - an average-to-large grid
500x500 grid - a very large grid which is manageable, but may cause
some delay in processing and require lots of storage if many horizons
are involved
1000x1000 grid - unless you have an extremely fast server and lots of
swap space and lots of storage, grids of this size are not manageable at
this time.

Chapter 11 - 14 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Gridding Fundamentals

For this type of data, the interpretation is typically at a density which is equal
to or greater than the Final interval you might choose. For this reason, the
proper algorithm to select for gridding is SNAP, not Convergent. Choosing
SNAP and setting the parameters as indicated below will produce either a
literal copy of your interpretation (without any interpolation taking place), or a
sub-sampling of it, depending upon whether the data density is, respectively,
equal to, or greater than the selected Final interval.
Final interval: decide based on how much you want to invest in
gridding time, grid maintenance time, and storage space.
Initial interval: same as Final interval
Number of Nodes to Snap To: 1

Importance of Fault Zone Definition During Gridding


If your goal involves accurate volume computations between horizons with
non-vertical faults, it is important to get a reasonable thickness grid definition
in the fault zones. The reason for this is that unless the fault wedge zones for
the two horizons are defined in their grids, their resulting isochore grid will
not be suitable for accurate volume calculations. If, for example, in the figure
below, the Top surface were defined in the grid only in its upthrown and
downthrown blocks, and not in the fault wedge zone from A to B, then the
thickness grid cannot be defined in the interval from A to B. Similarly, if the
Base horizon is blank in its fault zone, the thickness grid will also be blank
from C to D. In those locations where the initial thickness grid is blank, no
volume will be computed

Figure 11.1 Non-vertical fault zone displaying fault wedge zones

GeoFrame 4.0 Introduction to CPS-3 Chapter 11 - 15


Gridding Fundamentals Schlumberger

As an integral part of the horizon being mapped, the fault zone should receive
as much attention as the fault blocks.

Techniques for Filling in Fault Zones


In order to fully define these fault zones, there are several techniques
available. A summary is presented below.

Blanking and Regridding

In this technique, you first grid the horizons fault blocks as well as possible,
while using the fault boundaries during gridding. This ensures the integrity of
shape for each block. When this initial grid is complete, blank out this grid
inside all fault polygons. This cleans the fault zones of any spurious
definitions caused by data which happened to fall in the fault zones. Next,
copy the blanked grid to a data set, then use that data set to recreate a grid of
the horizon with the convergent algorithm WITHOUT using the faults. The
theory of this technique is that the best possible data to define the fault zones
are the grid nodes right at their edges.

Using Fault Polygon Z-values

If you have quality z-values on your fault boundaries, then this is excellent
data to use to define the fault zone. Simply make sure that the gridding
algorithm can see and will use these z-values by setting the appropriate
switches when specifying gridding parameters. This technique requires only
one step, but also requires some quality control for the fault boundaries and
their z-values, and assumes there is no conflicting data which might happen to
fall in the fault zones.

Using Existing Fault Surfaces

This technique is not an easy one if you have more than a few faults. It does,
however, lend itself to being incorporated into a macro. The reason for this is
that it requires several operations per fault. Here is the outline of the steps for
one fault:
blank the existing fault surface outside of its associated fault boundary
polygon
perform the surface operation which replaces nodes in one grid (the
horizon grid) with nodes from another (the blanked fault surface). In
particular, the surface operation required is the 10th Multiple Surface
Logical Operation, A in Union, otherwise defined as
C=A, but if A or B is Null, then C = Valid(A,B) (-255)

Chapter 11 - 16 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Gridding Fundamentals

Contour Visibility in Fault Zones


It is sometimes difficult to tell if grid nodes have been defined in fault zones.
When horizontal separation is small, only a few nodes can fit across the heave.
In this case, contours may not be generated in the fault zone, even though the
nodes are defined. (See the example below.)

Figure 11.1 Grid nodes across a fault zone

The algorithms visibility of grid nodes is sometimes restricted by the


upthrown and downthrown traces as it tries to compute inside the fault zone.
Not enough nodes are visible to generate reasonable contours. The best way to
determine if nodes are defined here or not is to turn off the System switch
Show Graphic Entities When Z is Null, and display the grid nodes
themselves. Null grid nodes will not appear on the display.

GeoFrame 4.0 Introduction to CPS-3 Chapter 11 - 17


Gridding Fundamentals Schlumberger

Chapter 11 - 18 GeoFrame 4.0 Introduction to CPS-3


Chapter 12
CPS-3 Gridding Parameters

Overview

The purpose of this chapter is to apply the information we learned in the


chapter about Gridding Fundamentals to specific data sets. Well discuss the
following:

1. Assuming that we will use both well data and seismic data in gridding,
well go through the decision-making process to settle on a Final
gridding increment for the sample data sets.

2. We will present some easy-to-remember guidelines for choosing the


most important Convergent/Snap gridding parameters - Starting Grid
Interval and Number of Nodes to Snap.

3. We will also discuss the topic of defining the fault zones in a horizon,
and when it is necessary.

4. Finally, well talk about when it is convenient to grid the fault surfaces
themselves, and describe a macro which uses a specific technique for
gridding fault surfaces.

GeoFrame 4.0 Introduction to CPS-3 Chapter 12 - 1


CPS-3 Gridding Parameters Schlumberger

Selecting the Grid Spacing

The Rule of Thumb

As you may recall from Chapter 11 - Gridding Fundamentals, the grid


spacing required to replicate all features in a data set is sometimes determined
two methods:
half the distance between the two closest points
half the distance between the two closest points whose
difference you wish to distinguish
This rule of thumb works fine most of the time for well data. However, for
very dense seismic interpretation, we may end up with a grid which is too fine.
Let us now examine our data in detail to help us pick the appropriate spacing.

Well data

Lets look only at our well data for a minute. In the map below, several of the
wells are fairly close together. The closest are about 50 feet apart.

Figure 12.1 Well location map

Things to Consider When Choosing a Grid Interval

In some cases, wells can be so close that choosing a gridding interval, based
on their distance, can lead to a grid which contains an inordinate number of
nodes. If we choose an xinc based on the two closest wells, according to the
rule of thumb, we will have a grid with a spacing of 25 feet, 490 columns, and
600 rows.

Chapter 12 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Gridding Parameters

If this were all the data we had, and our concern was to reflect all data in the
grid as accurately as possible, then we might use the 25 foot spacing,
especially if the z-values in the two closest wells indicated a substantial
difference in slope from the rest of the map. This would guarantee that each
data point fell in its own grid cell, and the difference in z-values between the
two points would be preserved in the grid and the resulting contours.

If, as is often the case, the z-values of the two wells are not very different,
then, for all practical purposes, we only need one of them in the gridding
operation. This means that we could ignore their separation as a criteria for the
grid spacing and use a larger grid separation.

Here is another way to look at it. There are only two wells which are as close
as 50 feet. If there were many wells in the data set, then one might be willing
to accept a bit of averaging in the grid around these two wells, if it meant the
difference between a modest grid and a very large grid.

Looking at the rest of the wells, it appears that the next smallest separation is
approximately 100 or 200 feet. Let us assume that the difference in z-values of
the two closest wells is not significant. Then, this inspection of only the well
data tells us that we might use a grid interval of about 100 feet. This will
provide a surface which is relatively modest in size, but which will resolve any
important features inherent in this well data.


Note: It is appropriate to look closely at the well data when determining a grid
spacing, since traditionally, well data is considered to be of a higher quality
than the seismic interpretation.

Let us now look at the seismic data to see if it tells us anything different about
the grid spacing.

GeoFrame 4.0 Introduction to CPS-3 Chapter 12 - 3


CPS-3 Gridding Parameters Schlumberger

Seismic Data

As seen below, seismic data comes in a variety of densities and geometries.


The one characteristic of all these different interpreted horizons, however, is
based on the fact that both cdp and shot point spacing is 55 feet in the
Cloudspin project. This defines the closest points in the seismic data. Let us
see if this affects our chosen grid interval.

Figure 12.2 Seismic data in a variety of densities and geometries

Chapter 12 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Gridding Parameters

Varieties of Seismic data geometries in Cloudspin

1. Seed Interpretation

Seed interpretation, or line-decimated interpretation, is interpretation which


has been done at a subsampling of the cdp or inline spacing - for example,
every 20th inline and crossline, as seen in the figure below. This is a good way
to get a horizon interpreted quickly - pick every 20 inline/crossline and let
ASAP fill in the rest!

Figure 12.3 Seed interpretation subsampling every 20th inline/crossline

Cloudspin interpreted horizons having INTRP in their names fall into this
category. This means that the lines are about 1100 feet apart. This particular
geometric distribution of data points is characterized by lines which are
relatively far apart with respect to the density of points along each line.This
type of data distribution sometimes requires extra work in the normally simple
gridding operations, especially when a grid spacing is chosen which is close to
the distance between points on the lines.

The reason for the extra work is to overcome the tendency of any gridding
algorithm to tie the grid closely to the many points along the line, while giving
an average solution at nodes between the lines. The following figure shows
why the extra step is sometimes needed. It shows a grid computed from seed
interpretation data where only a simple convergent step was applied. Note
the bulls-eyes along the lines.

GeoFrame 4.0 Introduction to CPS-3 Chapter 12 - 5


CPS-3 Gridding Parameters Schlumberger

Figure 12.4 Seed interpretation grid displaying noise and bulls-eyes along
data

With this type of data, it is sometimes necessary to increase the final grid size
in order to reduce the noise and bulls-eyes along the data line. If you have
several horizons which must maintain the same x,y extent and grid spacing,
this can be a problem, only if this type of data happens to be available for one
of the horizons. In this case, the recommendation is to grid the data at the
smallest final grid interval which minimizes the bulls-eyes, but then refine the
grid down to the smaller required size.

2. ASAP Interpretation

Cloudspin horizons having ASAP in their name fall in this category. This
type of geometry infers that every cdp in the survey area is potentially defined,
as is almost the case in the portion of our Jakarta horizon shown in the
following figure.

Chapter 12 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Gridding Parameters

Figure 12.5 Horizon interpretation using ASAP

The IESX automatic picking procedure called ASAP was used in the above
figure to finish the horizon interpretation between the 20x20 lines picked by
the interpreter. Dense data like this is usually very simple to grid. However,
holes in the interpretation can cause gridding problems. For example, in an
ASAP version of the Kobe horizon below, we see patches of missing
interpretation, especially below the Hobart fault in the lower part of the map.

Figure 12.6 Example of holes in the interpretation

GeoFrame 4.0 Introduction to CPS-3 Chapter 12 - 7


CPS-3 Gridding Parameters Schlumberger

When using the Convergent gridding algorithm, the key is to make the
Starting interval large enough to that holes in the grid are avoided. For the
Least Squares algorithm, make the Search Radius larger when unwanted
holes in the grid are identified.

3. Combinations

The Paris horizon below contains both 20x20 and ASAP interpretation
geometry, but it should not be any more difficult to grid than the others. All
data distribution types shown here can easily be gridded with the Snap and
Convergent Gridding algorithms, as we will demonstrate.

Figure 12.7 Horizon displaying 20x20 and ASAP interpretation geometry

Chapter 12 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Gridding Parameters

4. 2D Only

This type of data is similar to the seed distribution type, in that, data exists in
very dense points along lines which are sparsely distributed. As with the seed
data, the potential exists for bulls eyes along the lines if a too small xinc is
used initially. Either post-refinement of a somewhat larger final grid size, as
mentioned above, or smoothing of a required final grid size can help here.

5. Other Seismic Considerations

There are many options available in seismic interpretation packages, and some
can affect the way in which data is gridded in the mapping stages. For
example, in the Cloudspin project, not all horizons were interpreted with the
automatic smoother activated. We will see one or more of our horizons
exhibit high-frequency noise in the initial contours. A small bit of smoothing
in CPS-3 can remove this noise with little affect to data tying.

Conclusion of the data inspection

We chose a grid spacing of 100 feet based on the well data, but note that for
the densely-interpreted seismic horizons, many of the data points are 55 feet
apart. The choice of a 50 foot grid spacing would give us a grid having 225
columns and 280 rows. This is not an extremely large grid, and 50 feet would
be an appropriate spacing if this reservoir were modeled with the intent of
computing accurate oil in place.

GeoFrame 4.0 Introduction to CPS-3 Chapter 12 - 9


CPS-3 Gridding Parameters Schlumberger

Simple Guidelines for Choosing SNAP/CONVERGENT


parameters for Seismic data
1. If the seismic interpretation data is dense enough that interpretation
exists in every grid cell of the selected gridding lattice in all locations
of the map where grid definition is desired, then use SNAP with
Number of Nodes = 1

2. If the interpretation contains holes or does not exist in areas where the
grid must be defined, then use the CONVERGENT algorithm with
Number of Nodes = 16, and Starting Grid Interval = half the diameter
of the largest hole in the data.

Figure 12.8 Incompletely defined seismic interpretation

For example, if the figure above represents 3D seismic interpretation, the


Starting Grid Interval should be at least several times the distance between the
data points in order for the grid to fill in the holes in the data.

Chapter 12 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Gridding Parameters

Defining the Fault Zone in a Horizon - Yes or No


As you prepare to create grids for your horizons, you should think ahead to
the end of your particular workflow. If your only concern is to create a
structure map, it is common practice to blank out the fault zones on the
contour map. You can do this by blanking the grid inside of the fault zone, or
you may choose to do it graphically, by simply color-filling the fault zone
during display.

As you will see in the exercises, defining the fault zones in a horizon does not
require the presence of a surfaces for the faults, which is discussed in a
different context below.

Importance of Fault Zone Definition


In horizons with non-vertical faults, it is very important to get a reasonable
thickness grid definition in the fault zone if your goal involves accurate
volume computations. The reason for this is that unless the fault wedge zones
for the two horizons are defined in the grid, their resulting isochore grid will
not be suitable for accurate volume calculations. If, for example, in the figure
below, the Top surface were defined in the grid only in its upthrown and
downthrown blocks, and not in the fault wedge zone from A to B, then the
thickness grid cannot be defined from A to B. Similarly, if the Base horizon is
blank in its fault zone, the thickness grid will also be blank from C to D. In
those locations where the initial thickness grid is blank, no volume will be
computed

Figure 12.9 Non-vertical fault zone displaying fault wedge zones

GeoFrame 4.0 Introduction to CPS-3 Chapter 12 - 11


CPS-3 Gridding Parameters Schlumberger

Contour Visibility in Fault Zones

It is sometimes difficult to tell if grid nodes have been defined in fault zones.
When horizontal separation is small, only a few nodes can fit across the heave.
In this case, contours may not be generated in the fault zone, even though the
nodes are defined. (See the example below.)

Figure 12.10 Grid nodes across a fault zone

The algorithms visibility of grid nodes is sometimes restricted by the


upthrown and downthrown traces as it tries to compute inside the fault zone.
Not enough nodes are visible to generate reasonable contours.


Tip: Even though display functions like contouring may not be able to visually
render every portion of a gridded surface, it is still important that the nodes
be defined properly for structural reasons.

Chapter 12 - 12 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Gridding Parameters

When Are Fault Surfaces Needed?

Figure 12.11 Normal faults in profile view

Then answer to this question depends on how much detail you want in the
structural envelope you create for volumetrics. If your structural envelope
does not involve sealing faults, then you probably dont need to grid your fault
surfaces. If the envelope does involve one or more sealing faults, but having
very modest horizontal and vertical separation, you may still decide not to
grid the fault surfaces, and simply treat the faults as vertical faults. However,
in the case of large throw or large heaves on the sealing faults, you will
probably get more accurate results in your volumetrics if you include the fault
surface in the structural envelope.

A Predefined Technique for Fault Surface Gridding

Here, well discuss a technique for gridding fault data which may not be
necessary for all fault data sets, but which is a very useful alternative to
Convergent gridding. The origin of this gridding technique is the realization
that most fault surfaces have strong linear components in the direction of dip.
With the typically sparse data provided by fault segments, as interpreted in the
seismic, strong linear trends are not always honored by the Convergent
algorithm. The gridding technique consists of the following:

Create an initial 2nd order Trend grid from the fault data points.
At all data point locations, compute the difference between the Trend
surface and the z-value in the data point.
Subtract the two values, creating a new z-field called Error.
Create a grid of the Error and add it to the initial Trend grid, giving
the final grid which contains a strong fault-like trend downdip, but also
ties to the observed data.

This technique is contained in the macro called k_grid_fault.mac

GeoFrame 4.0 Introduction to CPS-3 Chapter 12 - 13


CPS-3 Gridding Parameters Schlumberger

Chapter 12 - 14 GeoFrame 4.0 Introduction to CPS-3


Chapter 13
Set Modeling Environment and
Compute Horizon Grids

Overview
In this chapter, we will focus on that geographic area where the horizon grids
will be computed, and define the Modeling environment for it.

Figure 13.1 Modeling environment shown as subset of Display environment

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 1


Set Modeling Environment and Compute Horizon Grids Schlumberger

We will also create grids for the following horizons


Bunnkritt
Tarbert
Ness

keeping in mind the guidelines that we learned from the lectures on gridding
techniques.

Chapter 13 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Modeling Environment and Compute Horizon Grids

Exercise

Define Modeling Environment

The Tarbert interpretation, shown below in white, defines the area which we
want to map. This horizon pinches out against an upper unconformity, the
Bunnkritt, towards the East, but yet there are still plenty of wells in the area
from the Western platform. At this time, there is no interpretation for the 2D
survey locations. They have been used mainly for basemapping exercises. We
will therefore define an area which surrounds the Tarbert interpretation and
create a modeling environment for it.

Figure 13.2 GullFaks region, surrounding extent of Tarbert interpretation

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 3


Set Modeling Environment and Compute Horizon Grids Schlumberger

1. Click the Select Environment icon in the Main Module and then
click on Create in the Modeling panel.

2. Enter gullFaks_gridding for the Name.

3. Click the Data Extents tab, then make sure that the coordinate system
is correct.

4. Click Pick Sets, and select the GeoFrame Grid set


mm_TARBERT_Depth_intrp.

5. You will see a message that the system has accepted the coordinate
system. Click OK to this message, and continue by clicking the
Min/Max tab.

6. Then, under the X Axis and Y Axis panels, modify the limits of the
data minimums to match the following:
X-Minimum = 453700
Y-Minimum = 6784500

7. Set the grid spacing as follows:


X and Y-Increment = 50.0
The system will automatically round up the maximum x and y values
so that the Increment is evenly divisible into the x and y range.

8. So that your maps will match the maps shown in these exercises,
increase or decrease the x and y maximums in your dialog, so that the
following values are reflected:
X-Maximum = 459600
Y-Maximum = 6792100
Column Count = 119
Row Count = 153

9. Click the Property Code down-arrow and select Depth. (Z Units


should be meters.)

10. Click OK, then highlight the associated display environment called
StdView:gullfaks_gridding, and click Edit Current in the Display
panel.

Chapter 13 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Modeling Environment and Compute Horizon Grids

11. Set the Map Scale Mode to Direct and specify a Scale of 250 m/cm.
Note that early versions of GF4 may incorrectly show (m/in) instead
of (m/cm). Verify that your plot is the same size as shown in the figure
above and click OK to return to the Environment dialog box.
Returning to the Select Environment dialog box, note that there are
now two new environments. One is our new Modeling environment,
the other is a companion Display environment called
StdView:gullfaks_gridding, which is useful, but only if the Modeling
environment is rotated.

12. Well remove the companion display environment,


StdView:gullfaks_gridding by highlighting it and clicking on the red
X icon in the upper right of the Select Environment dialog box.
If the Modeling environment that we just created were a rotated
environment, then we would not want to delete this companion
environment, since it would serve a very useful purpose - its x, y box is
the minimal rectangle of the rotated x, y box.

13. Now, highlight the Modeling environment, gullfaks_gridding and


click on the Select button in the Display environment panel, thus
selecting this Modeling environment to be used as the active Display
environment as well.

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 5


Set Modeling Environment and Compute Horizon Grids Schlumberger

Remember:


Note: If you happen to choose a method to create your Modeling environment
which involves the selection of a particular binset from the GeoFrame list of
binsets, you should know that binsets contain not only a grid lattice definition,
but specifications for x, y limits and a coordinate system, both of which will
supersede those values you may have already entered for your new
environment in the CPS-3 dialogs.

Chapter 13 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Modeling Environment and Compute Horizon Grids

Exercise

Gridding the Horizons

Grid the Bunnkritt Unconformity


Below, we see the distribution of interpreted data points for the Bunnkritt, an
unfaulted unconformity. This surface will be very easy to grid because of its
density of data.

We will choose the Snap algorithm in its most simple mode to obtain a grid
which is almost a literal copy of the interpretation. This is a very fast
procedure, since the algorithm is not required to make more than one iteration
through the data.

1. In the CPS-3 Main Module, click the Select environment icon.

2. In the Select Environment dialog box, activate gullfaks_gridding as


the active Display and Modeling environment, and click OK.

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 7


Set Modeling Environment and Compute Horizon Grids Schlumberger

Create the Grid

The single Snap procedure should be used with very dense data like the
Bunnkritt, where the data points are as close, or closer, than the grid spacing,
and there are no appreciable gaps or holes in the interpretation.

3. From the CPS-3 Main Module, select Modeling > Single Surface to
open the Single Surface Gridding dialog box.

Chapter 13 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Modeling Environment and Compute Horizon Grids

4. In the Single Surface Gridding dialog box, make the following


settings:
Under Input Data/Grid, toggle the first position to red, and click
on Pick Set.
In the selection dialog which appears, set the filter so that Set Type
= only Grid, and Storage = only GeoFrame. Then click Filter.
Select the interpretation grid named:
mm_BUNNKRITT_50x50_Depth_intrp. Click OK.
Back in the gridding dialog, toggle the second input set position to
red, click Pick Set, and in the set selection dialog, change Set
Type to only Data, and click Filter again.
Select the well markers named:
mm_BUNNKRITT_Depth_wmrkr as the second input data set
for the gridding.
Toggle off (gray) Fault and Polygon.
Select Snap from the Algorithm pop-up list.
Set Number of Nodes to snap to = 1
Under Output Grid, click New to open an additional Single
Surface Gridding dialog box.

Enter Bunnkritt as the new output surface Name.


Storage should be CPS, and the Surface (Container) Type
should be Horizon, and the Surface (Container) Name should
be BUNNKRITT as picked from the list.
Click OK to return to the original Single Surface Gridding
dialog box.
Click OK to start the gridding which will return you to the
CPS-3 Main Module.

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 9


Set Modeling Environment and Compute Horizon Grids Schlumberger

Contour the Grid

4. Erase the screen, then click Display > Contours to open the Display
Contours and/or a Shaded Surface dialog box.
Select Bunnkritt for the Grid.
Make sure that Display Line Contours is toggled to red, and click
Set Parameters. This opens the Parameters for Contouring a
Surface dialog box.
Start contour level - toggle Computed to red.
Increment between contours - specify 5.
Number of contours - toggle Computed to red
Further down, on the right, click No Bolding, No Blanking,
and No Labeling.
Click OK to close the Parameters for Contouring a Surface
dialog box.
Click OK to start the contouring.

Add a Border and Labels to the Display

5. Select Display > Basemap.

6. In the Basemap Display dialog box, make the following settings:


Toggle Border to red, and click Set Parameters to open the
Display Window Border dialog box.
Border line width = thin
Border line color = black
Click OK to close the dialog box.
Toggle Labels to red, and click Set Parameters to open the
Display Window Labels dialog box.
X: label size and Y: label size =.4
X: label increment and Y: label increment - set both to 2500.
Click OK to close the dialog box.

7. Click OK to begin the display.

Chapter 13 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Modeling Environment and Compute Horizon Grids

This is a start, but we note two problems with this grid:

1. Because the data is skewed slightly to the Northeast, a few of the grid nodes
on the East and West edges were not defined by the simple snap gridding to
the two closest nodes. In order to fill out the entire grid, we need to re-grid
with different parameters, to force some extrapolation to occur at the edges.

2. There also appears to be some alignment or mistie problem in the data,


resulting in the small vertical and horizontal features. If we were to look
closely at the data, we would note that it is not truly equal-spaced in X and Y.
This is due to the way this data was prepared for this project. It illustrates the
nature of the SNAP algorithm when Number of Nodes is 1 or 2.

Both of these minor problems can probably be repaired by simply setting the
number of nodes to a larger value, perhaps 8 or 16 for this particular data set.

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 11


Set Modeling Environment and Compute Horizon Grids Schlumberger

Re-grid the Bunnkritt with Number of Nodes = 8, then 16


Repeat the gridding step above, but set Number of Nodes = 8
instead of two. Answer Yes to both grid questions which appear.

This is better, but the border shows that we still have some missing nodes at
the edges.
Re-grid again, using Number of Nodes = 16

You will see that this will also not carry the grid all the way to the edge. With
this data set and map area, well have to use the Convergent algorithm with a
Starting Grid Interval of approximately 200m, in order to extrapolate all the
way to the edge
Re-grid again, this time select the Convergent algorithm and set
the Initial Grid Interval to 200m.

Chapter 13 - 12 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Modeling Environment and Compute Horizon Grids

This map of the Bunnkritt is complete all the way out to the edges, and the
horizontal and vertical features have also disappeared. Well use this as the
final map for the Bunnkritt unconformity.

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 13


Set Modeling Environment and Compute Horizon Grids Schlumberger

Grid the Tarbert Horizon


In the Tarbert horizon, whose data components are seen in the following
figure, we have a different type of data distribution than in the Bunnkritt; i.e.,
we have many holes in the interpretation data. Some of these holes are the
result of poor seismic definition, others show where the horizon has been
eroded, and others represent fault zones. Clearly a single SNAP gridding
would not work with this data since much of the grid would be undefined.
Well therefore use the Convergent algorithm with all of its extrapolation
capabilities.

Most of the wells are coincident with the seismic interpretation. We trust that
calibration has been performed. One of the wells provides some additional
data in the erosion zone to the West of the F4 fault, but other than that, the
wells do not cover much geography in this horizon.

We also note that a few of the fault boundaries appear to be spurious, forming
fault blocks (see the arrows) where there is no data to define them.

F14

F7a_D

F6a

F15a
F6

In these cases, we have the option to remove the fault patterns for the F6a.
F7a_D, F15a, and F6 faults and obtain a simplified model. Another option will
also be discussed when we address filling in the fault zones.

Chapter 13 - 14 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Modeling Environment and Compute Horizon Grids

What is the ultimate purpose of the horizon grids?

If we were only making structure maps, and the long-term goal of our
exercises did not involve the computation of volumes, or the derivation of an
envelope for the gross isochore, we might forget about the fault zones and
simply grid this surface using the fault polygons provided, blanking out the
fault zones in the map. We will do this at first, but since the real purpose of
these grids is to construct an envelope for a specific lithologic zone, we must
address the gridding of the fault zones in the next phase.

Grid the Tarbert Using the Fault Patterns

1. Click Modeling > Single Surface.

2. Make the following settings in the Single Surface Gridding dialog


box.
Select the GeoFrame grid, mm_TARBERT_Depth_intrp, as the
first Data set from the down-arrow or Pick Set list.
Select the GeoFrame data set, mm_TARBERT_Depth_wmrkr as
the second Data set.
Toggle Fault to red, and pick the GeoFrame Fault set mm_Tarbert
as the Fault set.
Toggle Polygon to gray.
Select Convergent from the Algorithm pop-up list, and set the
Initial Interval (Starting Grid Interval) to 300. (We will explain
later in the chapter why we use this value.)
Click the Advanced parameters button, and under Set Modeling
Parameters, verify that Number of Nodes to snap to is 16.
Click OK to return to the Single Surface Gridding dialog box.
Under Surface, click New to open the Single Surface Gridding
dialog box.

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 15


Set Modeling Environment and Compute Horizon Grids Schlumberger

Double-click on the current name and hit the Delete key.


Enter Tarbert as the new grid Name, and then click OK to
return to the original Single Surface Gridding dialog box.
Click OK to start gridding and return to the CPS-3 Main Module.

Display the Tarbert Contours

3. Erase the screen, and click on Display > Contours.


Select the Tarbert grid, Its associated fault set, mm_Tarbert
should already be selected in the Faults panel.
Toggle Display Line Contours to red.
Click OK to start the contouring.

Chapter 13 - 16 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Modeling Environment and Compute Horizon Grids

Analyze Map Quality of Tarbert Grid

As suspected, we have several fault blocks on the East side which are
undefined or poorly defined. At present, we do not have any other data with
which to define these blocks, and so we will remove the fault patterns
mentioned earlier.

We also note that the computed grid does not cover the entire map area due to
lack of data. We have the option of increasing the size of the initial grid
interval which will have the effect of causing more extrapolation into these
blank grid areas.

When we zoom in, closer to the well locations, we notice several large
discrepancies between the well and seismic interpretation. We will continue
without the well data when we re-grid this horizon just to get a smooth map,
but in a real project, of course, the geologist and seismic interpreter should
resolve the differences at the wells.

Another characteristic of this map which requires some remediation are the
contours in the fault zone. In this first part of the exercise for the Tarbert
horizon, well simply blank them out after removing the fault patterns and
regridding as mentioned above.

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 17


Set Modeling Environment and Compute Horizon Grids Schlumberger

The last problem with this grid is that there is some inherent noise in the data
which is evidenced by the horizontal streaks. Again, this comes from the way
in which the data was prepared and will be remedied by smoothing as we
proceed.

Remove Irrelevant Fault Patterns and Re-grid Tarbert with More


Extrapolation, Without the Wells, Adding Contour Data

In order to remove the proper fault polygon subsets from the Tarbert fault set,
youll need to know that the faults we want to remove have the following
subset numbers:
3: F7a_D
9:F15a
10: F6
12: F6a

4. Click Utilities > Sets > Subset, then click Delete, then Fault, and pick
the CPS set named mm_Tarbert.
Select subsets 3, 9, 10, and 12
Click Apply, then Cancel.

5. At this point, we will decide not the use the Tarbert wells because of
the bulls eyes we see in the final map. We will also decide to make use
of another secondary data set called
mm_TARBERT_contour_interp. This data set is derived from
previous experience, knowing that in the lower right-hand corner of the
map, we will have crossing grid problems with the Ness horizon unless
we control this part of the Tarbert horizon, which is so lacking in data.

6. Erase the screen and re-grid the Tarbert grid using Single Surface
gridding as before, except change the Initial Grid Interval to
500.0m. Remove the wells from the input data and instead use the
mm_TARBERT_contour_interp data set as the second data set.

7. Select the CPS Fault boundary set mm_Tarbert, as before.

8. When the gridding finishes, color-shade the contours, setting the


contour interval to computed, and you should see a map similar to
the one below.

Chapter 13 - 18 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Modeling Environment and Compute Horizon Grids

There is still an area in the East edge of the map where the grid is not defined.
In this case, the reservoir which we will be modeling does not exist there, and
so we can leave the grid defined as it is.

We also note many parts of the fault zones are not defined. The reason for this
is that there was no data explicitly provided to model them. To complicate the
situation, there were many horizon interpretation data points which were
incorrectly left inside these zones by the interpreter. During gridding, the
algorithm used them with the result that you see - badly defined fault zones
with holes in them.

Now let us finish the first section for this Tarbert horizon by showing one way
to correctly handle the display and modeling of the fault zones.

Here is the strategy well use:


Smooth the grid to get rid of the high frequency noise we noted earlier
Blank out all fault zone values in the Tarbert grid
Since blanking can only be done with a polygons, well first have
to copy the fault traces (which surround the fault zones) to a
polygon set.
Fill in the blanked-out fault zones by using the grid itself as data

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 19


Set Modeling Environment and Compute Horizon Grids Schlumberger

A Final Smoothing

Color-shading does not reveal the fact that there are some areas of high-
frequency noise, coming from the data. We also saw this in the Bunnkritt.

9. Click Operations > Grid > Smooth, then select the Tarbert grid and
its fault boundary set as input. Click OK.

10. Choose a convergent threshold of 2% and click OK. This will remove
the kinks in this grid, which can be verified by dense line contours.

Blanking the Tarbert Fault Zones

11. Since we know that the fault zones in this grid were created by
improper and incomplete data, the first step will be to simply blank
them out in the grid.
Click on Utilities > Sets > Copy and copy the Tarbert fault set to a
polygon set of the same name.
In the Copy Sets dialog box, toggle Fault [F] to red.
Select mm_Tarbert, and click Copy.
In the next dialog box, select Polygon for Output set type and
provide a new Output Set Name of mm_Tarbert, then click
OK.
In the Copy dialog, click Cancel to exit the copy procedure.

12. Click Operations > Grid > Blank to open the Blank a Grid dialog
box.
For Grid (input), select Tarbert.
For Polygon (input), select mm_Tarbert, and click OK. This
opens the Blank a Grid dialog box.
Select Inside only as the Calculation mode, and click OK to
begin the blanking.

13. Erase the screen and color-shade the Tarbert grid as before.

Chapter 13 - 20 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Modeling Environment and Compute Horizon Grids

We now have a grid which is representative of the data. It has been somewhat
extrapolated in certain areas, and the fault zones have been blanked. If we
were only creating structure maps using limited extrapolation, we might say
that the map is finished.

In this class, however, our workflow extends all the way to volumetrics, and as
the instructor has explained, this will require us to fill in the fault zones for
each horizon in the structural envelope so that we do not end up with holes in
the isochore grids

Filling in Fault Zones for Tarbert Horizon

There are actually several ways to fill in fault zones, but the one presented
here is the most direct and requires the least amount of extra data. We will
simply use the grid itself as data to re-grid the entire horizon without the
faults, since the fault blocks have already been very well defined. The grid
nodes along the edges of each blanked fault zone will be extremely good
data with which to define each of the fault surface patches which we need
to fill in the blank areas. When we re-grid in this manner, well also choose to
do a little more extrapolation on the fault blocks towards the East, as well.

1. From the Single Surface Gridding dialog box, re-grid the Tarbert
horizon as follows:
Under Data, select the Tarbert grid as the only Data set.

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 21


Set Modeling Environment and Compute Horizon Grids Schlumberger

Toggle Fault and Polygon to gray.


Select Convergent from the Algorithm pop-up list, and set the
Initial Interval to 200. This is the approximately half the largest
horizontal displacement exhibited by the fault patterns in this
horizon. It is the largest distance between data points which define
the holes in this data.
Click the Advanced button, and verify that Number of Nodes to
snap to is 16. and select the Deterministic weight function and
Moderate damping.
Click OK to return to the Single Surface Gridding dialog box.
Under Surface, select Tarbert again.
Click OK to start the gridding, replacing the Tarbert grid with a
new version.

Because we created this version of the grid without using the fault boundaries,
the grid will not be automatically associated with a fault set. Therefore, we ill
force the association before we contour.

11. Click Utilities > Sets > Associate_Set_With_Grid. Identify the


Tarbert grid and its associated fault set, mm_Tarbert, then click OK.

12. Erase the screen, and click on Display > Contours and contour the
Tarbert surface.

Chapter 13 - 22 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Modeling Environment and Compute Horizon Grids

If you like, you can color-shade this new grid to verify that there a few, if any,
areas which are not defined.

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 23


Set Modeling Environment and Compute Horizon Grids Schlumberger

Grid the Ness Horizon


Using the same procedures as for the Tarbert, create a smoothed grid of the
Ness horizon where the fault zones are filled in and the grid has been
extrapolated all the way to the edges of the map. The seismic data is named
mm_Ness_Depth_intrp, the well data is mm_NESS_Depth_wmrkr, and the
fault boundaries are mm_Ness. Fault subsets 1 and 8 should be deleted in the
mm_Ness fault set before gridding. Try a Starting Grid Interval of 400 for
this data set. Note that the well data and the seismic data in this data set are
not calibrated, and so you may want to use only the seismic for gridding, just
to get a smoother overall map for the class.

When finished, your map should be named Ness, and should resemble the one
shown below:

We now have three of the several components we need to build the structural
envelope for the lithozone between the Tarbert and the Ness horizons. In
particular, we have the unconformity grid, Bunnkritt, and the two horizon
grids below it- the Tarbert and the Ness.

Chapter 13 - 24 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Set Modeling Environment and Compute Horizon Grids

Well take a break from modeling activities for a moment to learn a little more
about Basemapping and ASCII file input in the next exercises.

GeoFrame 4.0 Introduction to CPS-3 Chapter 13 - 25


Set Modeling Environment and Compute Horizon Grids Schlumberger

Chapter 13 - 26 GeoFrame 4.0 Introduction to CPS-3


Chapter 14
Contouring, Colorshading, and More
Basemapping

Overview
In this chapter we will look at more options available for basemapping. We
will introduce you to colorshading, and demonstrate many of the graphic
parameters which we did not take the time to discuss during the gridding.

GeoFrame 4.0 Introduction to CPS-3 Chapter 14 - 1


Contouring, Colorshading, and More Basemapping Schlumberger

Understanding Graphic Size and Resolution Parameters:


Text/Symbol Size, Map Scale, Contour Quality
When specifying text size, symbol size, or contour quality, what you see on
the screen will depend on the scale defined for the currently active Display
environment.

During screen display, CPS-3 first creates all graphics in a manner and scale
appropriate to the size of the plot you have specified in your Display
environment. It then renders a smaller version of this on your workstation
screen.

Plot
Size

You specify the plot to be this big and


pick graphic sizes appropriate to this

CPS-3 then miniaturizes this


picture and puts it on your screen.

Thus, rendering of character sizes, symbol sizes, and even contour quality are
a function of the physical size of the plot you specify when you scale your
Display environment. There are three modes by which you may set the map
scale Ratio, Direct, or NoScale.

Chapter 14 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Contouring, Colorshading, and More Basemapping

When you select either Ratio, or Direct scaling methods, you have the ability
to define a plot size of your own choosing, for example, 18 inches for X and
22 inches for Y. This means that if you select a text size of, say, .25 inches for
contour labels, then they will be .25 inches high when the map is plotted at the
specified size. On your screen, the text will be smaller since the workstation
screen always presents a miniature version of your scaled map, except in the
rare case when you specify a plot size which is actually smaller than your
workstation screen.

When you select No Scale, CPS-3 simply assumes a default maximum plotter
size of 12 inches by 12 inches, then scales everything and maintains the aspect
ratio accordingly.

English and Metric Units

Even though your sets in CPS-3 are stored in meters or feet, you have may
choose to specify character sizes and other graphic dimensioning in English or
Metric notation. This is determined by the GeoGraphic Distance attribute in
the GeoFrame Display Units which is managed from the Project Manager
dialog.

When you select a particular GeoFrame Display Units definition in metric


units, for example, then graphic sizing and scale specification will be done in
metric units.

Rendering

No matter how you actually specify the size of your paper plot, text sizing,
and symbol sizing, will be relative to that plot size, as shown in the previous
diagram. Stated another way - if you set a posting symbol size of .25 inches,
the symbol will be .25 inches high on the final map, not .25 inches on the
workstation screen.

When you select contour quality, the system attempts to tie the selected
quality specification to a measurable result on the physical plot. This is
accomplished by refining the contoured grid to levels which will cause smaller
and smaller contour line segments. If time permits, the instructor might
provide a basic description of the contouring algorithm at this point., but the
basic fact is that refining the grid before generating contour loci will cause the
individual contour line segments to become smaller. Below is a table which
maps Contour Quality to Refine Grid Cell Size in inches.

GeoFrame 4.0 Introduction to CPS-3 Chapter 14 - 3


Contouring, Colorshading, and More Basemapping Schlumberger

Quality Cell size


1 .50
2 .45
3 .40
4 .35
5 .30
6 .25
7 .20
8 .15
9 .10
10 .05

A special Quality of 0 will cause contouring of the grid with no refinement.

Note that in later versions of the software, this feature may work slightly
differently, but the on-line Help is always available for current details.

Time of Execution for Contour Generation


The contouring algorithm in CPS-3 is both fast and accurate; however, factors
which affect the speed of execution are:

Density of Contoured Grid


The fewer rows and columns, the faster the contouring

Using Faults During Contouring


Faulted grids simply take more time to contour

Values for Contour Parameters


Frequency of contour labels (more labels are slower)
Contour increment and numbers of contours (smaller increments and
more contours are slower)
Contour Quality (higher quality is slower)

Map Size
For a given grid and a given Contour Quality, smaller plot sizes will
contour quicker than larger ones.

Chapter 14 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Contouring, Colorshading, and More Basemapping

Guidelines to Optimize Contouring Speed


During interactive sessions not involving hard-copy plots, specify a
scale for your Display environment which yields a plot size that fits
within a 12x12 inch space.
When contouring, begin with a Quality of Zero. Your grid may be fine
enough so that Zero Quality provides adequately smooth contour lines
without having to resort to refinement.
Try contouring without labels for modeling work. They tend to
obscure the shape of the structure in some cases, and you can put the
labels on later, when you want to generate presentation maps.
Use a Contour Increment which is reasonable. Extremely fine
contour increments can generate contour displays which sometime
appear to sculpture the surface, but take a long time to generate.

GeoFrame 4.0 Introduction to CPS-3 Chapter 14 - 5


Contouring, Colorshading, and More Basemapping Schlumberger

Exercise

Understanding Graphic Size Parameters

In this exercise, we will learn how plot size affect the size of characters on the
screen. The assumption is that the GeoFrame Display Units are still
Metric/Charisma.

1. Click the Select Environment icon. This opens the Select


Environment dialog box.
Verify that the GullFaks_Gridding Display environment is still
active, highlight it, and click Edit Current under the Display
Environment panel.

Changing Map Scale Mode


In the Horizontal Scale section, set Map Scale to 650 Direct
(m/cm). The computed plot size should be 9.1 x 11.7 cm.
Click OK, returning to the Main menu.

2. Erase the screen, and click Display > Contours


Select Ness as the Surface.
Toggle Display Line Contours to red and click Set parameters.
Set these parameter values:
Start contour level - Computed
Increment between contours = 50
Number of contours - Computed
Bolding rate = None (No Bolding)
Contour label rate = 1
Distance to First Label = 2
Distance between labels = 8
Contour label size = .63
Number of Decimal Places in Label = 0
Click OK to close the dialog, then again to contour.

Chapter 14 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Contouring, Colorshading, and More Basemapping

Text is about
1/4 inch high

About 3.6 inches on the screen

Placing a border on the plot shows the physical size of the Display
environment as rendered on the screen. It should be very close to 9.1 by
11.7cm, or about 3.6 by 4.6 inches, which corresponds to the size specified in
the Display environment. In this case, text size on the screen is the same as
what you have specified in the parameters because the plot size is smaller
than the screen, and the system does not have to shrink it.

4. Now, return to the Select Environment dialog and again edit the
GullFaks_Gridding Display environment.
Change the Horizontal Map Scale Mode to be Direct, and the
Scale to be 120 meters/cm. Striking the <Return> key will cause a
new Resulting Map Size to be displayed. This should be 49.2 by
63.3 cm.
Click OK back to the Main menu, discarding any existing graphics
on the screen.

5. Contour the Ness grid as before, not changing any of the contouring
parameters.

GeoFrame 4.0 Introduction to CPS-3 Chapter 14 - 7


Contouring, Colorshading, and More Basemapping Schlumberger

Two things have happened simply by changing map scale:

1. The physical size of the plot no longer fits in the workstation viewport
and so the system has shrunk it to fit.

2. The same text size (.5cm) has been rendered to show how it would
look on the plot with the specified size, therefore, it appears smaller on
the workstation screen.

Text is about
1/16 inch high

About 6 1/4 inches on the screen

Now return again to the Environment dialogs and change the map
scale for the GullFaks_gridding Display environment to 250
meters/cm.
Recontour the Ness grid, changing the following contour
parameters:
Distance to First Label = 1

Chapter 14 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Contouring, Colorshading, and More Basemapping

Distance Between Labels = 20


Contour Label Size =.35.

GeoFrame 4.0 Introduction to CPS-3 Chapter 14 - 9


Contouring, Colorshading, and More Basemapping Schlumberger

Exercise

Contouring a Single Z-value

1. Erase the scrren and contour the Ness grid as follows


set Start contour level = 1800
set Increment between contours = 1
set Number of contours = 1
set Map quality = 0
set Line width for normal (non-bold) contours = #3
toggle No bolding to red
toggle No blanking to red
toggle No labeling to red, and click OK.

This shows the locus of the 1800m contour lines against the background of the
fault patterns.
Now bring up the contour menu again, and click Help. Point to
several parameter fields and make sure you understand the
meaning of the parameters.
Experiment with the other contouring parameters, such as Bolding
rate, Contour label rate, and Distance to first label.

Chapter 14 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Contouring, Colorshading, and More Basemapping

Color Shaded Contours


1. Erase the screen, and click Display > Contours.
Select Ness for Surface.
Toggle Display Line Contours off
Toggle on Display a Shaded Grid, and click Set Parameters.
This opens the following Parameters for Color Shaded Contours
dialog box.

Set the first three parameters to Computed.


Set X and Y Resolution to .25 and Grid Refinement to .2
Make sure that Color palette is set to Rainbow.
Set Invert palette to Yes.
Click OK to close the dialog box.

GeoFrame 4.0 Introduction to CPS-3 Chapter 14 - 11


Contouring, Colorshading, and More Basemapping Schlumberger

Toggle on Display Faults and click Set Parameters. This opens the
Parameters for Displaying Faults dialog box.

Set Line color = black


Set Symbol Size to 0.
Set Annotate Names and Annotate Z-values to No
Set Fault polygon fill method = No Fill
Click OK back to the Main menu to start the color-shading.
Go to Display > Basemap to set Borders and Labels around the map.

Chapter 14 - 12 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Contouring, Colorshading, and More Basemapping

This is a medium-to-high resolution shaded contour map. By reducing the X


and Y resolutions and the Faulted Cell resolution, quicker maps can be
generated.

Make Room for a Color Bar


1. Click Display > Display Functions > Set General Display
Parameters to open the General Display Parameters dialog box.

2. In the Set Screen Display Margin section, set the Left margin to 6
and the Right margin to 2, and then click OK.

GeoFrame 4.0 Introduction to CPS-3 Chapter 14 - 13


Contouring, Colorshading, and More Basemapping Schlumberger

Display the Color Bar


1. Click Display > Color-shading Palette to open the Display Color
Table dialog box.
Set Method of positioning color table to Use cursor.
Set Label text size to .3.
Set Label text color to black.
Set Label text font to 5.
Set Label text quality to Filled, and click OK. Use MB1 to place
the color bar next to your map display. Click and hold to define the
rectangle, then click again to verify.

2. Put a bold, black border around the map, but no labels.

3. Save as a new map set called Ness_shade, and erase the screen.

Chapter 14 - 14 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Contouring, Colorshading, and More Basemapping

Exercise

More Basemapping

We will finish this exercise by creating a map using some of the basemapping
tools which we have yet not tried.

Return to GullFaks_Overview Display Environment


1. Go to Display > Display Functions > Set General Display
Parameters,
set Left margin to 1
set Right margin to 4
click OK to return CPS-3 Main Module

2. Go to the Select Environment dialog and activate the


Better_GullFaks_Overview display environment.

3. Click the Display basemap icon to open the Basemap Display dialog
box.
Toggle on Map Set and select Ness_shade from Pick Sets.
Click Apply to display the map.
Toggle on Border.
Toggle on Labels and click Set Parameters.
Set X: label size and Y: label size to .2.
Set X: label increment and Y: label increment to 5000.
Click OK.
Toggle on Map Title and click Set Parameters.
Bottom margin title = Ness Structure and
Surrounding Surveys
Bottom margin text size = .5
Bottom margin X position of text center = Computed
Bottom margin Y position of text center = 1.5
Left margin text size = .5
Click OK.

GeoFrame 4.0 Introduction to CPS-3 Chapter 14 - 15


Contouring, Colorshading, and More Basemapping Schlumberger

Set Additional Parameters


Toggle on X,Y Grid Lines and Tics and click Set
Parameters.
Grid lines layout = Reference crosses (+)
Method of spacing grid lines = User specified
Starting X value (origin) for vertical lines = 449804
Starting Y value (origin) for horizontal lines = 6775767
X and Y axis grid line spacing = 2000
Labeling option = No Labeling
Line color = black
Tick mark color = black
Tick mark size = .4
Click OK.
Toggle Lat/Lon Lines and Labels and click Set Parameters.
Set first six parameters to Computed
Display control for lines and crosses = Both latitude and
longitude lines
Labeling control = Border labels on all sides
Label Format Control = Degrees, Minutes, Seconds
Line color = black
Text size = .6
Text color = Magenta
Text quality = Filled
Click OK.

4. Click Apply on the Basemap Display dialog box. Your display should
look similar to the following figure, which shows some of the graphics
off the workstation screen. We will remedy this in a minute.

Chapter 14 - 16 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Contouring, Colorshading, and More Basemapping

5. Back in the Basemap dialog, toggle on Extended Data and post the
2D seismic location set, mm_2d_gullfaks_shtpt, just as we did for the
previous basemap. Click OK.

6. Click the Reveal all graphics icon to expand the x,y box.

7. Click on User/Show_Environment to bring up the project location.


Swipe the path to the project and stick it into an Xterm.

8. Click the Display basemap icon again.


Toggle on Title Block and click Set Parameters to open the
dialog box. Set the following parameters:
Caption justification point = Lower left of display window
X and Y offset from justification point - toggle on Position
with cursor
Caption scale factor =.5
Click Select file, then blank out the Filter text field, and
replace it with the path to your CPS dsl swiped from the Xterm
Add /*.cst to the end of the path and press <Return>.
Choose the caption file schlum_title.cst, and click OK.

GeoFrame 4.0 Introduction to CPS-3 Chapter 14 - 17


Contouring, Colorshading, and More Basemapping Schlumberger

Click Enter title block field values at the bottom of the


Caption Information dialog to open the Draw a Title Block
dialog box.
In the following figure, you see the information in the title block
fields which you want displayed on your map.

Top of Ness
Depth/M

In the next figure, you see the names of the fields where you enter the
information for each of the locations in the title block.

In the Draw a Title Block dialog box, enter the appropriate


information in the text entry fields. For example, in the Author
text entry field, enter your name; in the Map Title text entry
field, enter Top Of Ness, and click OK.
Click OK again, and click Apply.

Chapter 14 - 18 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Contouring, Colorshading, and More Basemapping

When the cursor becomes a +, position the title block to the


right of the lower right border corner, even with the lower
border. Use MB1 to position the block, then click it again to
accept the location. If you want to reposition, click the right
button and start again.

9. In the Basemap Display dialog box, select Projection Block, and


click Set Parameters. Set the following parameters:
Caption justification point = Lower left of display window
X and Y offset from justification point - toggle on Position with
cursor
Caption scale factor = .5
Click OK.
Click OK to close the Basemap Display dialog box.

10. Position the projection block similarly to the title block, in a location
of your choice.

11. Add a scale bar as before.


Your display should now resemble the one below.

GeoFrame 4.0 Introduction to CPS-3 Chapter 14 - 19


Contouring, Colorshading, and More Basemapping Schlumberger

12. Click the Save currently displayed map icon, and save the display to
a new map set called Ness_Overview.

Chapter 14 - 20 GeoFrame 4.0 Introduction to CPS-3


Chapter 15
Demonstrate Inverse Interpolation and
Control Point Arithmetic

Overview
The purpose of this chapter is to demonstrate the use of inverse interpolation
and control point arithmetic. The workflow will involve computing the
error, if any, in the Ness structure grid at certain marker locations which well
load from an ASCII file shown below. The file contains Well Name, Symbol
Code, and Symbol Color information as well as X, Y, Z data.

GeoFrame 4.0 Introduction to CPS-3 Chapter 15 - 21


Demonstrate Inverse Interpolation and Control Point Arithmetic Schlumberger

Display Ness_tops
1. Clear the screen and go to Display > Select Environment to verify
that the active Display environment is GullFaks_Gridding.

2. Click Display > Basemap and toggle on Extended Data.

3. Select Ness_tops, and click Set Parameters.

4. Click Set Parameters, and set the parameters shown below:


Toggle Symbol Parameters to red
Click the Symbol code icon which reveals the symbol code table
shown below.

Note that the symbol you pick in this case represents only the default
symbol because the symbol codes were already loaded in this
particular data set. However, in case a well did not have a symbol code
in the ASCII file, the one selected here will be used.

5. Toggle the second field, z1 to red in the dialog box. This will be the Z-
value in each well. Choose parameter values which seem appropriate.

Chapter 15 - 22 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Demonstrate Inverse Interpolation and Control Point Arithmetic

6. Toggle the Text1 field to red. This will be the well name. Choose
appropriate parameter values.

7. When finished with the parameters dialog box, click OK to close it

8. Click OK again to begin the display.

9. When the wells appear on the screen, use the Rubberband zoom-in
icon to view details of a few of the wells.

10. Click the Un-zoom icon , and return to the full area of interest.

GeoFrame 4.0 Introduction to CPS-3 Chapter 15 - 23


Demonstrate Inverse Interpolation and Control Point Arithmetic Schlumberger

Exercise

Compare Ness Grid and Ness_tops Data Set

Use Inverse Interpolation to Store Grid Value


Remember that we gridded the Ness surface with only 3D seismic data. We
will now learn something about inverse interpolation as we see how different
the Ness grid is from the Ness_tops Data set.

1. Click on Operations > Control Point > Interpolate from Grid to


Data, to open the Compute data from a Grid dialog box.
Select Ness as the Grid. Notice that the correct Fault boundary set
automatically appears.
Toggle Polygon to null.
Select Ness_tops as the Data set, and click OK.

2. In the ensuing dialog box, toggle on Results to new Z Field, and type
in grid_value in the Selection box.

Chapter 15 - 24 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Demonstrate Inverse Interpolation and Control Point Arithmetic

3. Click OK to begin the calculation.


This operation will create a second z-field in the Ness_tops data set.
For each well in the data set, the second z-field represents the value
from the Ness grid, while the first z-field represents the original value
(pick) from the ASCII file.
After execution, note the statistics in the CPS-3 Status Information
window, and note the z-range of the second z-field, grid_value.

4. Now click Utilities > Sets > View_Contents_Statistics. At the top of


the next dialog, click List Contents, toggle Data to red, then select the
data set Ness_top, and click OK.

5. In the CPS-3 Status Information window, down near the bottom,


click the cursor in the long white box labelled Enter Response.
Leaving the cursor in the box, type the number: 100.

What you see is a listing of all stored data for the data set Ness_tops.
Across the page you see sequence number, X, Y, original Z, grid Z
(which we just calculated), symbol code, symbol color, and borehole
name for each well.
Note that some of the grid Z values are null (INDT). These are wells
which fall outside the area of the grid, and a value could not be
computed.

GeoFrame 4.0 Introduction to CPS-3 Chapter 15 - 25


Demonstrate Inverse Interpolation and Control Point Arithmetic Schlumberger

Use Control Point Arithmetic to Compute Difference


6. Click on Operations > Control Point > Control Point Math.

7. Select Ness_tops as the Data set, and click OK.

For the Algebraic expression enter @z2-@z1


Toggle on Results to new Z Field
Enter the name error in the Selection text entry field, and click
OK.

8. Look at the statistics which appear in the Status Information window


again, and see the range of the error.
Note that this error can be mapped and its distribution displayed. There is a
system macro for this purpose called Show_Error.mac.

Chapter 15 - 26 GeoFrame 4.0 Introduction to CPS-3


Chapter 16
Fault Surface Operations

Overview
In this chapter, we will turn our attention to another step in the workflow
whose culmination will be the computation of oil in place in a reservoir

O/W

Fault A Fault B

Figure 16.1 Sealing Faults

In those cases where a reservoir is bounded by sealing faults, it will be


necessary to make grids of the fault surfaces, unless they are actually vertical.

We have already discussed the importance of defining the fault zones when
volumetrics is the workflow focus, and we should have already accommodated
this requirement when gridding the top and base structures as depicted below.

GeoFrame 4.0 Introduction to CPS-3 Chapter 16 - 1


Fault Surface Operations Schlumberger

Horizon 1

Fault Horizon 2
Zones

We are careful when creating grids to be used in volumetrics to define all fault
zones in each horizon. There are many techniques for doing this as discussed
in a previous chapter, and not all of them require an actual fault surface. The
definition, during gridding, of all fault zones should be done for volumetrics
whether there are any sealing faults or not. It simply guarantees that the top
and base envelope will be continuous and that the resulting isochore will not
have any holes in it due to undefined fault zones

Creating Fault Surfaces


In this chapter, we continue with modeling requirements in the case of sealing
faults, where one or more fault surfaces must be integrated into the top or base
envelope, or both.
The technique is to simply define the fault surface as well as possible with
whatever data is available. This data could be
scatter points
fault cuts (segments) from seismic interpretation
digitized contours
external grid

There are many algorithms to choose from when gridding faults, just as there
are when gridding any data. One of the differences between typical horizon
interpretation data and fault interpretation data is that the fault data tends to be
sparser and of a lower quality. For this reason, it is not always possible to
obtain a good model of the fault on the first iteration.

Chapter 16 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Fault Surface Operations

Try the Convergent algorithm first, or any other algorithm you choose. If you
like the resulting grid and it honors the data, then thats probably as far as you
need to go.

In the GeoQuest modeling system called Framework 3D, faults are gridded
many at a time, and a specific algorithm is used there which has a high
probability of creating a good grid on the first try. This algorithm can be
duplicated by several CPS-3 procedures and embodied in a macro. There is
another algorithm which has already been put into a macro which uses even
another technique. Both of these are discussed below.

Both of these techniques work well for. Be aware the output grid may not tie
to all of the data points, but it works well for fault input data which is either
very noisy or very sparse. Below is a description of it.

Predefined Techniques for Fault Surface Gridding


Trend Method

This is a technique for gridding fault data which may not be necessary for all
fault data sets, but which is a very useful alternative to Convergent gridding.
The origin of this gridding technique is the realization that most fault surfaces
have strong linear components in the direction of dip. With typically sparse
data, strong linear trends are not always honored by the Convergent
algorithm, nor ingrained in the fault cut data set.

This particular technique is directly available in the CPS-3 set of System


macros. Its called GridFault. Here is an outline of how it works:
Create an initial 2nd order Trend grid from the fault data points.
At all data point locations, compute the difference between the Trend
surface and the z-value in the data point.
Subtract the two values, creating a new z-field called Error.
Create a grid of the Error and add it to the initial Trend grid, giving
the final grid which contains a strong fault-like trend downdip, but also
ties to the observed data.
Display the contours for the fault grid
Display the original data points for the grid.

Slope Method

In FW3D, a new fault gridding algorithm for GF4.0 has been installed which,
in most cases, gives better results than the Trend Method. It may not be in the
CPS-3 set of System Macros, depending of the version of your software, but it
works like this:

GeoFrame 4.0 Introduction to CPS-3 Chapter 16 - 3


Fault Surface Operations Schlumberger

Use the data you have to create a fault surface using the Convergent
gridding algorithm for a grid which is 4 times a coarse as the desired
final grid size.
Use the Control Point operations to compute slopes at all control
points so that you have an augmented control point set containing
X,Y,Z,dZ/dX, dZ/dY.
Use the augmented control point set to create the fault grid at the final
grid size.

Chapter 16 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Fault Surface Operations

Now, lets review the geometry of the Gullfaks faults and horizons, decide on
the location of the reservoir to model, and grid those fault surfaces we need
for incorporation into the structural envelopes.

GullFaks Fault Patterns


In general, the Gullfaks horizons are tilted fault blocks having fault zones
running North/South. Higher horizons contain numerous erosion zones with
corresponding lack of data. Below are some representative fault patterns in the
area we are mapping.

In the figure below, we see a schematic East-West section through an assumed


reservoir area.

GeoFrame 4.0 Introduction to CPS-3 Chapter 16 - 5


Fault Surface Operations Schlumberger

Bunnkritt
Unconformity

Tarbert

Ness

Fault 2 Fault 4

For the volumetric exercises, we will focus on the interval between the
Tarbert and the Ness between Fault 2 and Fault 4, which we will assume are
sealing faults. Notice that the top envelope of the reservoir is defined by both
the Tarbert and, in its erosion zones, by the Bunkritt unconformity. In a later
chapter, we will also introduce the oil/water contact.

In this exercise, we will create the grids for Faults 2 and 4.

Chapter 16 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Fault Surface Operations

Exercise

Load Fault Segments (Cuts)

1. In the CPS-3 Main Menu, click on the GeoFrame Link icon:


.

2. Click Controls, and highlight all surveys.

3. Click Data Types. In the next dialog, under Containers, select Faults,
and under Representations, select Fault Cut Sets, and click OK.

4. Click GeoFrame Data, and in the next dialog, set the Vertical
Domain to Depth.

5. In the left panel, select the F2 fault. You may see several items appear
under the Representations panel on the right, but highlight only the
row saying Fault Cut Set.

6. Click F4 in the left panel and on the right, highlight the row saying
Fault Cut Set, then click OK.

7. Back in the GeoFrame Link dialog, highlight both of the items in the
right panel, and then click Run.

These sets will be stored in the CPS-3 dsl as data sets named F2_Depth and
F4_Depth.

GeoFrame 4.0 Introduction to CPS-3 Chapter 16 - 7


Fault Surface Operations Schlumberger

Exercise

Inspect Fault Data Points and Create Fault Grids

1. If you like, display the fault cuts for the F2 and F4 faults. As seen
below against the background of the three surveys we have used, you
can see that each runs North/South with F2 on the left and F4 on the
right. It is not necessary to replicate this figure, only display the faults
in your current Display environment.

Creating the fault grids


At this point, we will introduce you to the concept of macros in CPS-3. We
will grid these two faults using a predefined macro which embodies the fault
gridding technique which was discussed in the reference material for this
topic.

Chapter 16 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Fault Surface Operations

In a later chapter, you will learn how to create macros. Here, we simply want
to introduce you to how they can be used. The macro you will run was created
in CPS-3, then modified by adding Macro Command Language, which
allows prompting, substitution, and other useful features inside of macros.

GeoFrame 4.0 Introduction to CPS-3 Chapter 16 - 9


Fault Surface Operations Schlumberger

Exercise

Run the Fault Gridding Macro

1. Click the Select environment icon, and set both the Modeling and
Display Environments to gullfaks_gridding.

2. Answer Discard and Do not clip to the change of environment


message.

3. Delete the data set named macwork, if it exists.

4. Click Macros > Execute and toggle on Show System Macros.

5. Click on the list widget next to it, and select Fault Gridding. This will
cause the macro named GridFault.mac to appear under the Macros
panel. Highlight it, and you will see the description of the macro. This
macro represents one of several methods for gridding fault surfaces
and seems to work well with the data we have.

6. Click OK to start the macro

7. When the Select a Data Set dialog pops up, select the data set
F2_depth, and then click OK.

8. When the Type output surface name dialog pops up, type in the
name: F2_fault.

9. When the Enter an slm... dialog pops up, enter 2500.00, and
the macro will begin execution. When finished, it will display the
contours for the fault grid and the data points as below.

Chapter 16 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Fault Surface Operations

F2_fault

This is a reasonable-looking fault surface and so well continue and repeat the
macro for the second fault F4_depth. Specify an output name of F4_fault,
and an slm of 2500.

F4-fault

GeoFrame 4.0 Introduction to CPS-3 Chapter 16 - 11


Fault Surface Operations Schlumberger

Establishing Set Attributes for the Fault Surfaces


Macros do not always establish the set attributes for grids which they create. It
is up to the macros author whether or not it is done, and the macro that we
used to create these surfaces does not. This will give us the opportunity to
show how to set attributes in the Set Manager dialog.

1. Click on Utilities > Sets > List_Manage_Sets, and set the filter so that
only grids are listed.

2. Highlight the F2_fault grid, and click on the i icon (information)


which also allows editing of set attributes.

3. Toggle on Replace All at the top

4. Change Surface from Unknown to Fault

5. Pick the Surface Name F2 from the list

6. Set Property Code to Depth

7. Set Z-Unit to meters, and then click OK.

Chapter 16 - 12 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Fault Surface Operations

8. Repeat this process for the F4_fault surface, but choose F4 as the
Surface Name

GeoFrame 4.0 Introduction to CPS-3 Chapter 16 - 13


Fault Surface Operations Schlumberger

Chapter 16 - 14 GeoFrame 4.0 Introduction to CPS-3


Chapter 17
Visualizing Relationships Among
Surfaces with Cross-Sections

Overview
In this chapter, we will continue with our modeling work and introduce you to
a simple quality control tool which is useful for understanding the relationship
between two surfaces.

We will discover something about the Ness and Tarbert horizons, and will
have to make some adjustments in the Ness.

We will also discuss the procedure for generating traditional cross sections
using CPS-3, which are useful when trying to understand the spatial
relationships among many surfaces.

GeoFrame 4.0 Introduction to CPS-3 Chapter 17 - 1


Visualizing Relationships Among Surfaces with Cross-Sections Schlumberger

Exercise

Determine If the Ness and Tarbert Surfaces Cross

Geologically, the Tarbert and the Ness are separate events and their grids
should not cross. We worry about this for two reasons:

1. Relative to their grid spacing (50m.), the Ness and Tarbert are not very
far apart (about 100m), and have many faults.

2. Both horizons have missing data areas caused by erosion, or by lack of


seismic definition.

We want to see if the extrapolation which occured during gridding in those


missing data areas is reasonable, Since we intend to use these horizons as the
basis for the top and base of our reservoir envelope, we want to remove any
areas which might cross.

To begin this quality-control procedure, simply subtract the two grids to create
an isochore. Then color-shade only the negative portion of the isochore grid
which, if we subtract the Tarbert from the Ness, will reveal where the Ness
deviated above the Tarbert.

Use Multiple Surface Arithmetic Operations to Subtract


the Grids, then Display Overlapping Areas
1. Click Operations > Grid > Multiple_Grids > C=AB
For grid C, create a new set called Diff
For grid A, select the Ness grid
For grid B, select the Tarbert grid
Click OK

2. Click Display > Contours


Select the Diff grid
Un-select Faults
Toggle on Display a Shaded Grid, and un-select all other options.

3. Click Parameters beside Display a Shaded Grid

Chapter 17 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Visualizing Relationships Among Surfaces with Cross-Sections

set Start Contour Level = 0.


set Increment = 10
set Number of Contours = Computed, and then click OK.

After displaying a border and labels, your msp should resemble the one below.

Note that most crossings occur where the fault zones of the two horizons
overlap. This is an indication that the interpretation along these zones should
probably be improved, since these horizons are already so close together.
When horizons are so close, this is also an indication that a more rigorous
method of filling in the faults zones might be required.

The larger crossings in the corners of the map occurred even though we made
use of some digitized contours to control the Tarbert horizon, which we felt
was diving too steeply to the Southeast. These crossings are all caused by lack
of data in one or the other of the horizons and might be mitigated somewhat
by more careful interpretation, some data editing, and some changes in the
gridding parameters.

In order to move along quickly, we can apply a global type of remediation to


this problem which is already available in a macro.

GeoFrame 4.0 Introduction to CPS-3 Chapter 17 - 3


Visualizing Relationships Among Surfaces with Cross-Sections Schlumberger

In particular, we have a macro available which will do the following:


Force a lower grid to conform to an upper grid in all locations where
the lower grid is above the upper.

This macro was designed to remove discrepancies which were much smaller
than the ones we have, but in this training environment, the data is designed to
demonstrate principles of operation.

Conform the Ness Grid to the Tarbert Grid Where They


Overlap
1. Click Macros, and toggle on Show System Macros

2. Select the macro Conform_to_Upper.mac, and click OK.


Pick Upper Surface = Tarbert
Pick Lower Surface = Ness
Pick new Output Surface = Ness_conformed
Pick new Output Boundary = Ness_overlaps

When finished, youll see a display of the Ness_overlaps boundary set, as


well as a color shaded map of the Ness_conformed.

After finishing with this macro, well use the dialog in


Utilities/Sets/Associate_Set_with_Grid to associate the fault set, mm_Ness
with the grid Ness_conformed.

One final step remains, and that is to give the output grid a final smoothing.
This is recommended, but it is not part of the macro we ran.

3. Click Operations > Grid > Smooth, and set the following parameters:
Set Input Grid = Ness_conformed
Set Faults = mm_Ness
Set Polygon = null
Set Output Grid = null
Smoothing Operator = Biharmonic
Max # Passes = 1, and then click OK to start the smoothing.

The output grid should resemble the one shown below.

Chapter 17 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Visualizing Relationships Among Surfaces with Cross-Sections

We will leave it you to verify that the overlap zones have diminished
considerably by inspecting the z-range of the diff grid which you can
recompute by subtracting the Ness_conformed grid from the Tarbert.

4. Now delete the Ness grid, and rename the Ness_conformed grid to
Ness.

GeoFrame 4.0 Introduction to CPS-3 Chapter 17 - 5


Visualizing Relationships Among Surfaces with Cross-Sections Schlumberger

Exercise

Examine Relationships among Horizons and Sealing


Faults

We would like to inspect the interrelationships among the Bunnkritt, the


Tarbert, and the Ness horizons, as well as the two sealing faults, F2 and F4.
By using profiles baselines which cut the map area at the top, bottom, and
along a diagonal, we should be able to get a good idea of the spatial
relationships among these grids.

Digitize Profile Baselines


1. Erase the screen and from the CPS-3 Main Module, click Display >
Select Environment.

2. Select the GullFaks_Gridding environment.

3. Clear the screen and display a Border with Labels. Use a label
increment of 2000.

4. Display the mm_Tarbert Fault set.

5. Click Digitize > Polygon


Toggle on Screen digitizing and click New.
Enter Baselines as a new Polygon set Name. Set Surface Type
to Unknown
Toggle Append off
Set the Echo color to Black, and click OK.

6. Click No to Close polygon?, and then click OK.

7. Type Upper_EW for the polygon name, and click OK.

8. Using MB1, click the first point in the polyline on the left border at
approximately Y = 6790150. Click the second point at the same y-
location on the right border. If you need to delete a point, click MB3,

Chapter 17 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Visualizing Relationships Among Surfaces with Cross-Sections

then click Delete on the menu. Repeat as many times as necessary.


After the second point has been successfully digitized, click MB3,
then Finish in the dialog which appears.

9. Answer Yes to Create another subset? Give the second polyline the
name Lower_EW, and in a similar fashion as above, digitize a line
from left to right at approximately Y = 6786200.

10. Answer Yes to Create another subset? Call it UL_to_LR, and in a


similar fashion, digitize a baseline from the upper left corner of the
map to the lower right corner as shown in the map below.

Y = 6790150

Y = 6786200

12. Answer No to Create another subset? to stop the digitizing.

13. Erase the screen, display the fault set mm_Tarbert, and the polygon
set Baselines.
Note that when these baselines are used in the profiling procedure, the
left side of the profiles corresponds with the first point digitized.

GeoFrame 4.0 Introduction to CPS-3 Chapter 17 - 7


Visualizing Relationships Among Surfaces with Cross-Sections Schlumberger

Establish Z-scale Attributes in the Display Environment


Before we move on to the 2D XSection dialog boxes, we will first make sure
that the x,y scaling and z-scaling is set up properly in the current Display
environment, or we will never see our cross sections.

1. Bring up the Display environment GullFaks_Gridding for editing.


Below, you can see which fields in this dialog will affect our profile
display:

This is how you set the horizontal


scale along the baseline for your
cross sections.

This is how you set the Z-scaling


for your cross sections. Exaggerated
Horizontal is a linear multiplier of the
baseline scale above, left.

2. For the X-section horizontal scale, enter 100.0 Direct scale

3. For the X-section vertical scale, enter 50.0 Direct scale.

4. Click OK back to the Main menu.

Chapter 17 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Visualizing Relationships Among Surfaces with Cross-Sections

Create Profile Displays


Now, we will return to the CPS-3 Main Module and set up for the cross
section displays.

1. Click on Display > 2D XSection to open the dialog box.


Toggle XSection Method = Quick
Pick the Polygon/Baseline set = Baselines
Toggle Extract Method = Normal baseline
Click on Simple Baseline Method.

Click on Select All, which selects all baselines in the set, and will
cause a profile to be drawn through each.
Click OK.

2. Select the following grids to be included in the profile display:


Bunnkritt
Tarbert
Ness
F2_fault
F4_fault

3. You can Add each grid separately, or highlight all at once by using the
<Control> key as you pick.

4. Click Secondary Option.


Toggle XSection Type = Normal/Structural
Toggle XSection Mode = Prohibit: Clip...
Toggle Invert Z-Axis = On

GeoFrame 4.0 Introduction to CPS-3 Chapter 17 - 9


Visualizing Relationships Among Surfaces with Cross-Sections Schlumberger

Click on Set General Display Parameters and set the Large Text
Size =2., Small Text Size =.1, and Symbol Size =.2 Click OK.
Click on Vertical Profile Limits and set the Axis Limitation to
XSections, then OK.
Click Primary Options to return to the top dialog.

1. Click OK to start the profile display, and click No to Save Graphics?

Your display should resemble the one above.

7. Click Zoom Profile in the small dialog associated with the profile
display, and zoom into upper right corner, and other parts of the
display.

8. Click Do Next Profile to see the profile for the next baseline, then the
next, and click Close to exit.

9. Restart the profile display


Under Secondary Options, click Vertical Profile Limits, and set
the Axis Limitation to Manual, typing Z-minimum = 1000 and
Z-maximum = 3000.
Click OK, then Primary Options, then OK again to redisplay the
profiles.

Chapter 17 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Visualizing Relationships Among Surfaces with Cross-Sections

GeoFrame 4.0 Introduction to CPS-3 Chapter 17 - 11


Visualizing Relationships Among Surfaces with Cross-Sections Schlumberger

Chapter 17 - 12 GeoFrame 4.0 Introduction to CPS-3


Chapter 18
Creating a Volumetric Envelope

Overview
The first step in computing oil in place within an interval is to define the top
and the base of the oil-bearing rock. If the top and base horizons were flat
surfaces, cleanly defined across the entire area, then the gross rock thickness
could be computed by simply subtracting the two surfaces. However, we must
consider the common case where both of these surfaces intersect, or at least
onlap or baselap an unconformity or other bounding strata. In addition, we
will also consider the common condition where a fault surface seals the
envelope along one of its boundaries as well. These surface-to-surface
interactions mean that we must perform other mapping operations to create an
envelope which surrounds only the oil-bearing rock in this interval.

Since we must also account for the presence of water and gas within the
structural envelope, one of the last steps will be the integration of the gas/oil
and oil/water contacts into the final envelope.

Here, we will outline all the steps required to compute a volumetric envelope.
These steps should also work for any reservoir that you encounter outside of
class.

GeoFrame 4.0 Introduction to CPS-3 Chapter 18 - 1


Creating a Volumetric Envelope Schlumberger

Recommended Sequence for Computing an Isochore for


Volumetrics
The following steps may be taken when computing an oil-only isochore
between two horizons. This procedure is designed to preserve the true location
of the zero line in the isochore. Refer to Location of the Zero-Line in
Isochores which follows.

Assumptions:
Z-units are assumed to be in depth
Fault zones associated with the top and base structure are assumed to
be completely gridded and integrated in the structure grid.
The goal of this operations is to end up with a top envelope and a base
envelope which cleanly intersect along their edges, but do not overlap (are
not coincident). This method does not minimize discontinuities in slope.
Create the Top Envelope:

1. Identify the top of the interval for which the isochore is to be


computed.

2. If the top is truncated by any unconformity, or a sealing feature, merge


the two grids, retaining the deeper portions of both.

3. If the top intersects a gas/oil contact, merge the two, retaining the
deeper portions of both.
Create the Base Envelope:

4. Identify the base of the interval for which the isochore is to be


computed

5. If the base is truncated by any lower surface, including sealing faults,


merge the two, retaining the shallower portions of both

6. Merge the result of step 5 with the oil/water contact, if any, retaining
the shallower portions of both

7. Subtract the top envelope, the result of step 3, from the base envelope,
the result of step 6, which will give a final positive isochore in the
reservoir and a negative isochore everywhere else.

Chapter 18 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Creating a Volumetric Envelope

Location of the Zero Line in Isochores


Isochores, created for the purpose of contouring or volumetrics, should
preserve the location of the zero line in the grid by containing negative values
on the other side of the zero line. This does not have to be artificially
introduced, since it can be a natural by-product of the process of creating the
structural envelopes. If the isochores are left clipped to zero, as can happen
when surfaces are prematurely truncated, it effectively moves the zero contour
line, shrinking the perimeter of the positive isochore. The contouring and
volumetrics algorithms will both do a much better job when isochores are not
clipped. You should, however, clip isochores to zero when using them for
surface operations, such as adding them to a top or base structure.

A visual symptom of isochores which have been clipped to zero are ragged
contours along the zero line. See example below which exhibits a wobbly zero
contour in the north.

Figure 18.1 Isochore clipped to zero displaying ragged contour along zero
line

In this example, the clipping was not explicitly performed. It was the result of
premature merging or truncation of surfaces, as is explained below.

GeoFrame 4.0 Introduction to CPS-3 Chapter 18 - 3


Creating a Volumetric Envelope Schlumberger

How Did the Top and Base Envelope Become Coincident?

The profile below shows a top envelope and a base envelope which are the
origin of the isochore contoured above. There is a section along the profile on
the left where both surfaces are coincident. This is what is causing the flat
zero area in the isochore, and the loss of the true location of the intersection.
The coincidence in the envelopes was caused when the two original horizons
were truncated along an unconformity at some step along the way. While
these envelopes are geologically correct, they are not formed to gain the best
results from volumetric calculations.

Figure 18.2 Top envelope and base envelope of isochore in Figure 18.1

If the preceding Preferred Sequence of Operations had been followed, this


loss of volume would not have happened, because the base envelope would
not have been merged with the upper unconformity. Only the top envelope
interacts with the upper unconformity.

Chapter 18 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Creating a Volumetric Envelope

Accounting for Non-vertical Fault Discontinuities in the


Volumetric Isochore
For the most accurate results involving faulted horizons, an extra step is
needed for the preparation of the fault boundary sets used during the volume
calculations. Thinning of the isochore is the reason for this extra step, and is
shown in the following figure. A is the location of the upthrown side of the
fault boundary for the Top. B is the location of the downthrown side. C and D
are the corresponding locations for the Base.

Figure 18.3 Non vertical zone displaying wedge zones

As you can see, the thickness grid resulting from the subtraction of two
faulted structure grids, is, itself, faulted, or at least discontinuous in z in the
fault zones. It requires the boundary sets of both of the structure grids to
separate one discontinuous zone from another, and to allow the algorithm to
compute the most accurate results. For this reason, we will prepare fault sets
to use during the volume calculations for both intervals. Each prepared fault
set will be the combination of the fault traces for the top and bottom of the
associated envelope. We will do this below with a simple Copy/Merge
operation for each isochore.

It should be noted that if the fault zones are large, fault surfaces should
normally be used as part of the structural envelope, if available, and if the
faults are sealing.

GeoFrame 4.0 Introduction to CPS-3 Chapter 18 - 5


Creating a Volumetric Envelope Schlumberger

Example of Creating a Structural Envelope


We use an example from the GullFaks field. Below is the diagram of a typical
section through a reservoir. Our job at the moment is to identify those
structural components which contribute to the TOP of the reservoir. First, we
recognize that the F-2 fault will become the Western edge of the BASE of the
envelope, and so this gives us a convenient starting place for identifying the
top of the envelope.

Starting just to the right of the sealing F-2 fault, at the Tarbert horizon, we will
examine each intersection which occurs, noting which of the two intersecting
grids is the stratigraphicly LOWEST at the right of the intersection. That one
which is lower then becomes the upper boundary. For example the first
intersection with the Tarbert is along the 2100 g/o contact. Moving to the
right, the g/o contact then intersects the Unconformity, which now becomes
the boundary. Continuing on in this manner we can see that, excluding the
faults, the top of the reservoir is formed by sections of the Tarbert, the 2100
o/w contact, the Unconformity, and the F-4 fault.

Therefore, it is these four grids which we must merge to form the top.

F-2 F-4

U
2100
Tarbert
2200

Ness

Merging takes place two grids at a time, using a CPS-3 logical operation
which will take the stratigraphicly lower value of the two grids at each node
location. When one grid does not exist, output takes the other value.

Note that in all cases, the concept of maximum, minimum, highest,


and lowest in CPS-3 are to be taken ALGEBRAICALLY, not
GEOLOGICALLY. This means that you must consider the Z-units of the
grids which you are manipulating. If your units are in elevation, rather than
depth, then your choice of operation from the table below will be different.

Chapter 18 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Creating a Volumetric Envelope

The operation highlighted in the dialog above is the one we want for merging
the top envelope components, since we are in depth. When units are in depth,
the lower component will have the higher depth values.

Luckily, it does not matter which order in which these operations occur, the
result will be the same. Lets merge these components in the following order:
Merge the Tarbert with the Unconformity
Merge the result with the G/O contact
Merge the result with the F_4 fault
See each result below

GeoFrame 4.0 Introduction to CPS-3 Chapter 18 - 7


Creating a Volumetric Envelope Schlumberger

F-2 F-4

U
2100
Tarbert

F-2 F-4

U
2100
Tarbert

F-2 F-4

U
2100
Tarbert

Chapter 18 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Creating a Volumetric Envelope

Now for the bottom of the envelope. We can see that its components are the
F_2 fault, the Ness horizon, and the O/W contact.

In the same manner we can merge these components, using a different logical
operation, one that takes the minimum (higher values in depth) from the two
grids at each step. Well merge in this order:
Merge F_2 fault with Ness, giving the result below

F-2 F-4

2200

Ness

Merge result with O/W contact.

F-2 F-4

2200

Ness

The next step, of course, is to make sure that the top envelope and the base
envelope cross at the edges, so that their subtraction will result in positive
isochore, where needed, as well as negative isochore where needed.

GeoFrame 4.0 Introduction to CPS-3 Chapter 18 - 9


Creating a Volumetric Envelope Schlumberger

Below, we have superimposed the top and base envelopes.

F-2 F-4

U
2100
Tarbert
2200

Ness

(-) (+) (-) (+) (-)

0.0

Isochore

We see that top and base envelopes cross well, but we see some characteristics
which may not be what we want. We note the small negative component in the
isochore in the middle of the map, but realize that this will not cause any
problems and can be disregarded. However, the top and the base of the
isochore have three areas where they are coincident. We would like to avoid
this, if possible. Therefore, when the isochore map is created, we must
examine the extent of these resulting flat zero areas. They may be small and
insignificant, but it is also possible that the isochore may need some repair.

Lets see how these coincident areas occurred and what we can do about them.

Chapter 18 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Creating a Volumetric Envelope

Fault

Coincident
Zone
Top
Top

Base
Base

A B

In the case of a bounding fault grid which forms one side of the reservoir, a
potential problem exists in the isochore. If the Fault is merged with the Base
to form the bottom envelope, and the Top is left by itself to form the top
envelope as in Case A, then when they are subtracted, there will be a small
zone where the top envelope and bottom envelope overlap, causing a flat zero
area in the isochore grid, where, instead, there should be an abrupt change to
negative values. In many cases, these areas are very small and insignificant,
but, in others, must be addressed. One way to address this problem is to edit
the top envelope so that it does not coincide with the base envelope, but cuts
cleanly across it, as in Case B.

GeoFrame 4.0 Introduction to CPS-3 Chapter 18 - 11


Creating a Volumetric Envelope Schlumberger

Chapter 18 - 12 GeoFrame 4.0 Introduction to CPS-3


Chapter 19
Prepare the Tarbert/Ness Envelopes
and Create the Gross Isochore

Overview
In this chapter, we will make use of the CPS-3 arithmetic and logical surface
operations to prepare the volumetric envelope for the Tarbert/Ness interval.
The reservoir is limited horizontally by the two sealing faults Fault_2 and
Fault_4. It is limited vertically by the base horizon Ness and top horizon
Tarbert, which is also truncated by the Bunnkritt unconformity. The oil/water
contact is at 2200m and the gas/oil contact is at 2100 m. as shown below. T

Fault_2 Fault_4

2100 g/o

2200 o/w

Figure 19.1 Tarbert/Ness interval with gas/oil/water contacts.

GeoFrame 4.0 Introduction to CPS-3 Chapter 19 - 1


Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore Schlumberger

We can get some idea of the shape of the bottom of the reservoir by
contouring the base surface, Ness, at the depth of the oil/water contact. This
contour line is shown in the figure below. We also know that the reservoir falls
between the two sealing faults, Fault 2 and Fault 4. Until we put all the pieces
together, it is not clear whether the reservoir will close in the South within the
map boundaries.

Fault 2

Fault 4

Figure 19.2 Relationship of base of reservoir with sealing faults.

In preparation for volumetrics, the instructor should have already discussed


the proper way to create a structural isochore. In the exercises which follow,
well decide which components will be used for the top of the envelope, and
which will be used for the base, then compute the isochore between them.


Note: It is very important that the instructor covers the lecture material for these
exercises, so that you will understand why certain operations are performed.
Refer to the lecture materials for this chapter.

Chapter 19 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore

Exercise

Create Top of Envelope for Tarbert/Ness Interval

First, lets create the contact surfaces.

Create 2200m and 2100 m Fluid Contact Grids


1. In the CPS-3 Main Module, click Modeling > Single Surface to
open the Single Surface Gridding dialog box.
Disregard the input Data text entry fields and select the Constant
Z Value algorithm.
Set the Z Value to 2200.
In the Surface section, click New.
Name the output surface ow_2200.
Associate it with the Unknown container name, and click OK.
Click OK to return to the CPS-3 Main Module.
In the same manner, create the grid named go_2100 at a depth of
2100 meters.

Create Top Envelope


Taking the lead presented in the lecture material well merge these four grids
together to form the top of the envelope.
Tarbert
Bunnkritt Unconformity
Gas/Oil Contact (go_2100)
F4 Fault

We will not make direct use of the CPS-3 Logical Surface Operations as in
the lecture notes. Instead, well use some easier-to-understand macros which
were designed for this purpose.

GeoFrame 4.0 Introduction to CPS-3 Chapter 19 - 3


Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore Schlumberger

Merge Tarbert with Bunnkritt using Toplap Macro

1. Click Macros > Execute, then toggle Show System Macros to red.

2. Select the Toplap.mac macro in the Macros panel and read the
description, then click OK to start the macro running.
Select Horizon = Tarbert
Select Unconformity = Bunnkritt
Select Output Grid = Tarbert-Bunnkritt; create a new grid name
and select an unknown Surface Type
Select Boundary = Tarbert-Bunnkritt; create a new boundary
name and select an unknown Surface Type.

3. The macro should produce a color-shade map of the result as well as a


rendering of the location of the boundary set it created.

4. Display the interpretation grid points for the Tarbert,


mm_TARBERT_Depth_intrp,

Your display should resemble the map above showing the correlation
of the eroded zones (boundaries created by macro) and the distribution
of the interpretation.

Chapter 19 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore

Merge Result with Gas/Oil Contact

5. As before, bring up the macro Execute dialog and then select the
System macro called ClipTOP_at_GO.mac, which will clip the result
from the first macro to the Gas/Oil contact.
Set Top Envelope = Tarbert_Bunnkritt
Set GOC grid = go_2100
Set Output grid = Tarbert_Bunnkritt_2100 (Surface Type =
unknown)
Set Boundary = Tarbert_Bunnkritt_2100 (Surface Type =
unknown)
The macro will generate a map similar to the one below. The white
line close to the boundaries can be eliminated by increasing the
colorshade resolution in the macro.

Merge Result with F-4 Fault

6. As before, bring up the macro Execute dialog then select the User
macro called a_SealTop.mac, which will seal the top envelope with a
fault surface.
Set Top Envelope = Tarbert_Bunnkritt_2100
Set Fault grid = F4_fault

GeoFrame 4.0 Introduction to CPS-3 Chapter 19 - 5


Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore Schlumberger

Set Output grid = Tarbert_Bunnkritt_2100_F4 (Surface Type =


unknown)
Set Boundary = Tarbert_Bunnkritt_2100_F4 (Surface Type =
unknown)

The deep portions of the fault surface dominate the colors in this
display. Those of you who wish, can verify the accuracy of this grid by
displaying a cross-section using the same baselines we used earlier.
Remove the other grids from the profile except the contact grids.

Chapter 19 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore

Create Base Envelope


We will now create the base envelope using these components:
Ness horizon
Oil/Water Contact (ow_2200)
F2 Fault

Merge Ness with O/W Contact

1. As before, bring up the macro Execute dialog and then select the
System macro called ClipBASE_at_OW.mac, which will clip the
Ness horizon to the Gas/Oil contact.
Set Base Envelope = Ness
Set OWC grid = ow_2200
Set Output grid = Ness_2200 (Surface Type = unknown)
Set Boundary = Ness_2200 (Surface Type = unknown)

GeoFrame 4.0 Introduction to CPS-3 Chapter 19 - 7


Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore Schlumberger

Merge Result with F_2 Fault

2. As before, bring up the macro Execute dialog and then select the
Project macro called a_SealBase.mac which will merge the sealing
fault F_2 with the result from the first macro.
Set Fault grid = F2_fault
Set Horizon or Base = Ness_2200
Set Output grid = Ness_2200_F2 (Surface Type = unknown)
Set Boundary = Ness_2200_F2 (Surface Type = unknown)

Compute the Isochore

Now, we can simply subtract the base envelope from the top envelope to see
what the isochore looks like

3. Click Operations/Grid/Multiple_Grids/C=A-B
Set C = new grid named Gross_Isochore
Set A = Ness_2200_F2
Set B = Tarbert_Bunnkritt_2100_F4, then click OK.

4. Color-shade the Gross_Isochore grid, but only values above zero, and
use an increment of 5.0.

5. Click on Display > Color-shading-Palette to show the color bar.

Chapter 19 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore

6. Click on Utilities > Sets > Statistics and view the Basic statistics for
the Gross_Isochore grid, in particular, the z-range

GeoFrame 4.0 Introduction to CPS-3 Chapter 19 - 9


Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore Schlumberger

Prepare the Fault Traces for the Gross Thickness Grid


It is sometimes desirable to use fault traces for both the top and the base when
computing volumes, since the isochore, itself, has many discontinuities in it
when there are non-vertical faults present. If you want to maintain as much
accuracy as possible, heres how to merge these two sets.

Merging mm_Ness and mm_Tarbert Fault Boundaries

Sets are merged with the Copy Sets command on the Utilities menu. Below is
how to merge the fault sets for the Tarbert and Ness into a single set.

1. Click Utilities > Sets > Copy, and toggle on Fault [F] and click the
Filter button.

2. Select mm_Ness, then mm_Tarbert (holding down the <Control>


key), then click OK

3. Click New, and create a new fault set named Ness_Tarbert.

4. Associate it with the Unknown container name, and click OK.

5. Click OK in the Copy the Set dialog box.

6. When the dialog appears again, click Pick Set, and pick the
Ness_Tarbert set, then back in the Copying a Set dialog, toggle on
Append To Set and click OK.
The system copies (appends) the set Tarbert to the fault set
Ness_Tarbert.

7. Display the fault set Ness_Tarbert to see what the result looks like.

Chapter 19 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore

GeoFrame 4.0 Introduction to CPS-3 Chapter 19 - 11


Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore Schlumberger

Chapter 19 - 12 GeoFrame 4.0 Introduction to CPS-3


Chapter 20
Applying Reservoir Properties to the
Gross_Isochore for Oil in Place

Overview
In this chapter we will learn how to gain access to the necessary reservoir
property data from GeoFrame so that we can compute oil in place according
to this simple formula:

Oil in Place = Gross Isochore Volume* Net/Gross * Porosity * Saturation

Well discuss the origins of the Zone properties, as stored in GeoFrame, and
demonstrate the calculation of each of the property grids, as well as the
series of volumetric grids:
Net Isochore
Net Pore Volume
Net Pay

Finally, well demonstrate the use of the volumetric procedure and discuss the
report which it produces.

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 1


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

Origin of property data used by CPS-3


The origin of the property data used in volumetrics are the well logs.
Reservoir engineers or petrophysicists determine accurate values for many of
the reservoir properties such as porosity and saturation. In GeoFrame, the
tools required to do this are found on the Geology and Petrophysics catalogs.
Applications such as BoreView, PetroViewPlus, WellPix, Geology Office,
and ResSum all help to define these property values.

Ultimately, average property values are computed by ResSum for properties


in each lithozone. There can be many versions of these average
calculations, and so they are grouped and categorized by Zone Version. When
we compute volumes in CPS-3 for a particular interval, or lithozone, we need
to make sure and extract the property values from the proper Zone Version.
Zone Versions allow different interpretations to exist for the same lithozone.
For each property calculation within a specific Zone Version, ResSum
provides accumulations of the value based on different geometries - for
example, according to True Vertical Thickness (TVT), Measured Depth (MD),
and others. Where available, TVT or TVD computations should be chosen for
volumetrics.

Lets assume that we wish to compute Oil in Place between two horizons
named Jakarta and Kobe. A typical GeoFrame workflow for computing the
required properties in ResSum is:
Load the appropriate well logs
Create the geological markers for the Jakarta and the Kobe, either in
WellPix or by loading them with the General Ascii Loader
In Well Pix, define a lithozone between the Jakarta and the Kobe and
establish a Zone Version.
In ResSum, calculate the ratios and property averages for the layer.

When imported into CPS-3 via the GeoFrame link, each property value for a
particular Zone Version will take on the characteristics similar to a set of
markers; that is, a set of scatter points based on the well paths. The X and Y
values for these property values do not sit at the top or base of the lithozone,
but, rather, in the middle of it as seen below, depending on the particular
computational geometry chosen (TVT, MD, ...).

Chapter 20 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

Approximate
property marker
locations

Lithozone

Zone Property Values and Grid Calculations

Typically, the following ResSum properties are the ones used in the
volumetric equation for CPS-3:
Net Thickness, Gross Thickness, Net Porosity, and Net Pay Water Saturation.

Each is retrieved as a scatter set from the GeoFrame data base with the
GFLink. and then gridded. These property grids can then be applied to the
gross isochore with CPS-3 grid arithmetic operations.

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 3


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

Quality and Characteristics of Property Grids

In the example shown, note that the gross isochore (shaded area) covers only a
portion of our Area of Interest (AOI). When we look at the quality of each
property grid we create, we will not be concerned with areas which are not
within this pay zone. Within the pay zone, however, there are certain criteria
which must be met:
Porosity and Saturation values must remain between 0. and 1.0.
This means that we may have to change parameters, or even gridding
algorithms if too much slope is introduced into the grids by the
algorithm.
The grids must be completely defined within the pay zone. No holes
in the grid are allowed, otherwise, no volume can be calculated there.
As with other grids, the grid values must honor the values in the
wells.
The grids should be relatively smooth between the well data points,
and should not contain sharp discontinuities which are not
associated with the existing fault boundaries, if used.

Chapter 20 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

Typical Difficulties When Gridding Properties

1. Faulting can affect property values during deposition, as well as after


deposition. In some reservoirs, the fault boundaries for either the top
of zone or base of zone are used during property gridding to help
provide discrete ranges of the property value in certain fault blocks,
where appropriate.

2. Good property data for all lithozones is typically hard to come by and
data from the wells is usually sparse. This type of data can be
challenging to model adequately. We see that in the example below, the
data points for which we have property values barely reaches into the
reservoir area.

If seismic attributes exist for which it can be shown that there is a correlation
with property data, then interval property grids can be improved with various
techniques including the use of the application Log Property Mapping
(LPM) which can extend the accurate extent of property grids beyond the
lateral limits imposed by the well data.

Gridding Guidelines

With sparse data, we will probably get the best results using the Convergent
algorithm. When gridding property data, it is almost invariable that
extrapolation will be required.

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 5


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

The only other issue to worry about is the value for the Starting Grid Interval
when using the Convergent algorithm. The rules of thumb we discussed in the
earlier gridding chapter can be summarized here for sparse data:

Pick the larger of


the largest empty distance between control points
the largest empty distance between a control point and the edge of the
pay zone.

Remember, this number is not critical to determine the very first time. If it is
too small (pay zone not fully defined, or holes in the grid), then well simply
re-grid and make it bigger the next time.

Continuing with the OIP Equation


Once the individual property grids exist, the following series of grids are
normally computed individually with Single and Multiple Grid Operations.
Net-to-Gross = Net Thickness / Gross Thickness
Net Isochore = Net-to-Gross * Gross_Isochore
Net Pore Volume = Net Isochore * Net Porosity
Net Pay = Net Pore Volume * (1.0 - Net Pay Water Saturation)

Items in boldface are the individual property grids. The Gross_Isochore is the
structural envelope thickness, which is simply the difference of the top and
base structural envelopes. The final Net Pay grid becomes the input to the
Volumetrics operation, along with any associated fault polygons and the lease
polygons.

All operations involve only grid arithmetic when applying the properties.
When we created the structural envelope, we used primarily grid logical
operations.

Using the Formula Processor for a Shortcut

Instead of computing the grids above independently, it is possible to compute


the Net Pay grid from the Gross_Isochore and the individual property grids
in a single operation. In the exercises for this chapter, well show you how to
solve the OIP equation at the beginning of the chapter in one step from the
dialog under OPERATIONS/FORMULA.

Chapter 20 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

Note on Arithmetic and Logical Operations

In all the logical operations which we have performed to shape the envelope,
and all the grid arithmetic we have performed to compute the Net_Pay grid,
we have not used the fault boundaries (traces) at all. The reason for this is
that the CPS-3 logical operations and grid arithmetic functions perform their
calculations node-by-node, vertically, on corresponding grid nodes of the
input grids.

Computing Oil in Place with Volumetrics


We use the CPS-3 Volumetrics procedure to calculate oil in place. This
procedure has the ability to perform numerical integration between a grid
and a base plane. It accumulates volume grid cell by grid cell and has the
ability to differentiate the volumes on either side of a fault or lease polyline
when a cell is dissected by the line. Refer to the on-line documentation for this
procedure for an summary of its operation.

If the volumetric input grid were a gross isochore, the results would simply
be volume of rock. However, having applied all of the required rock properties
to the thickness grid, the volumetric input grid is no longer in a simple
thickness domain, and the result on the volumetrics report will be oil in place.
We have an option to report the results in barrels or other units, if desired. A
separate report for each lease polygon is generated.

The inputs to the Volumetric procedure are:


single Net_Pay grid which we have just calculated.
set of combined top and base fault boundaries
lease polygons

The output from the Volumetric procedure is a report such as the example
shown below.

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 7


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

Volume is the integrated volume between the grid and the base plane

Flat Area is the flat area of that portion of the grid ABOVE or BELOW the
base plane. The area of the polygon (lease) is also a flat area.

Surface area is the curvilinear area of that portion of the grid ABOVE or
BELOW the base plane and should always be equal or greater than the Flat
Area.

For a Net_Pay volumetric grid which is based on an isochore, and whose


values of interest should be positive, we are only interested in numbers above
zero, and so we need only to look at the Integrated Results ABOVE the
Horizontal Reference Plane in the report. The other sections are useful when
the volumetric grid is a structural model and Civil Engineering issues are to be
studied, such as cut and fill for highway design.

Chapter 20 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

Exercises for Oil in Place Calculations


In this chapter we will fetch the necessary reservoir property data from the
GeoFrame database so that we can compute oil in place according to this
simple formula:

Oil in Place = Gross Isochore Volume * Net/Gross * Porosity * Saturation

Once these data are accessible, we will grid them in CPS-3 to create one grid
per property, then apply each to the Gross Isochore grid using Multiple Grid
Arithmetic according to the formula above.

Specifically, we will compute the following series of grids:


Net Isochore = Net-to-Gross * Gross_Isochore
Net Pore Volume = Net Isochore * Net Porosity
Net Pay = Net Pore Volume * (1.0 - Net Pay Water Saturation)

As mentioned in the lecture for this chapter, the zone property values falling in
this lithozone are computed by ResSum, and are similar to geological
markers. For example, the porosity is a set of X,Y,Z points, where the Z-value
is an average porosity value in each borehole for the interval. Similarly, the
saturation and net/gross are sets of X,Y,Z points originating from the
boreholes, containing average values. X,Y locations of the strat markers will
fall along the borehole, midway between the geological markers.

You will recall that zone property values from ResSum are available in MD,
TVT, TVD, and TST form. For our purposes, we can use either the TVT or
TVD. Well start by accessing the property data from GeoFrame.

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 9


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

Exercise

Load Zone Properties (Net/Gross, Porosity, and Water


Saturation) from GeoFrame

As mentioned in the reference discussions, these zone properties are


calculated in ResSum. When the scatter set switch is set during these
calculations, a scatter set for each property calculated will be created and
stored in GeoFrame. In this case, these properties can be accessed directly
from CPS-3.

In this project, however, the scatter set switch was not set, and the purpose
of this exercise is to show you how to use the GeoFrame Link to obtain
access to these property scatter sets in CPS-3

1. Click on Tools > GeoFrame Link.

2. Click on the Load from GeoFrame tab, then click Zones to open
GeoFrame Zone Interval Properties, then click Zone Version and
select Formation, and then click OK.

3. In the Lithologic Layers section, highlight Tarbert.

4. In the Model Name section, highlight CPS3_Intro.

5. In the Property Versions section, highlight ResSum_Output_3.

6. Highlight the Net/Gross_Thickness_Ratio, Net_Reservoir_Porosity,


and Net_Pay_Water_Saturation properties, and then under Index
highlight TVD, and click OK.

7. Highlight all three CPS-3 Output Sets, and click Run.


This will load three data sets in the CPS-3 DSL, one for each property.
When finished, click Exit to return to the CPS-3 Main Module.


Note: In early versions of the training project, the output sets may be empty.

Chapter 20 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

8. If the sets are not empty, go to Utilities > Sets > View
Contents/Statistics to display the statistics for the data created, to see
if the values are reasonable.

9. We will now delete these particular property data sets

Tarbert_Net_Pay_Water_Saturation_TVD_Formation
Tarbert_Net_Reservoir_Porosity_TVD_Formation
Tarbert_Net_Gross_Thickness_Ratio_TVD_Formation

since we plan to use a different spatial distribution of well data:

mm_TARBERT_NESS_Porosity
mm_TARBERT_NESS_WSat
mm_TARBERT_NESS_Net-gross

in order to demonstrate a particular property gridding technique.

10. Before we use these data sets for gridding, let us go to


Utilities/Sets/List-Manage-Sets and edit their attributes such that
Surface = Rock Feature, Surface Name is Tarbert, and the
Property Code is appropriate for the set, for example, Net Pay
Porosity, etc.

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 11


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

Exercise

Create Property Grids

Determine Initial Grid Interval and Gridding Algorithm


1. Contour the Gross Isochore.

2. Display the mm_TARBERT_NESS_Porosity data set with large


symbols.

3. Go to Utilities > System > Set Toggle Switches and make sure that
the toggle Show graphic entities when z is null is off.

If time permits, it is recommended to skip the next section called Quick


Property Gridding, and to go instead to the procedure titled A Technique for
Obtaining Better Property Grids. If, however, time is of the essence, use the
quick gridding.

Chapter 20 - 12 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

Quick Property Gridding


Do this section only if you are going to skip the better technique, ...Obtaining
Better Property Grids due to lack of time. This exercise will create the
propery grids needed to continue on to the volumetrics, but if possible more
time should be taken to undersand the best way to do this.

1. Grid all three of the following datasets

mm_TARBERT_NESS_net-gross
mm_TARBERT_NESS_Porosity
mm_TARBERT_NESS_WSat

Use the Moving Average Single Surface gridding algorithm.


Do not use the faults during gridding
Use all default parameters, except for those below
Set Extrapolation distance = 3000 m.
Set Search Radius = 3000 m.
In Advanced parameters, set Z-minimum to 0.0 and Reset Mode
to Blank.
Name the output grids Netgross, Porosity, and Saturation,
respectively.
This will guarantee to create useable grids where the property values
exist everywhere that the reservoir exists. However, these grids will be
relatively simplistic, with the typical tight bullseyes around the wells.

2. Go directly to the exercise titled Apply Property Grids to Gross


Isochore.

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 13


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

The Sparse Data Problem - A Technique for Obtaining


Better Property Grids
Property data is typically available only at the wells. Judging from the
distribution of the well data points relative to the pay zone in the map above,
we have what might be called a better-than-average amount of data with
which to define the property grids. We only must define these grids within the
pay zone. It is not always necessary to extrapolate to the edge of the map
when developing the property grids.

Even so, however, when the Ness_Tarbert fault set is displayed, you can see
that the reservoir extends across three fault blocks, and the data is still sparse
when compared to seismic distributions. Some extrapolation will still be
necessary even with this relatively good data distribution.

Now the question is which gridding algorithm to use. Recall that the
Convergent algorithm provides the best extrapolator available, we should use
it. The lecture notes give a good general procedure to follow, but we will
depart from it here because we actually have fairly numerous data inside of
our fault blocks.

We will define a two-step gridding technique where we use the Convergent


algorithm to define accurate property values close to the data, and use it again
with different parameter settings to damp unrelated data values when
completing the grid in the extrapolated areas. We accomplish this as follows:

1) Using a very small initial grid size in the first grid, we take advantage of the
Convergents slope projection, but only closely around the data points. We
will use the faults in the first gridding to make sure that these initial values are
not tainted by data from different fault blocks.

2) Copy the first grid as data for a second gridding where well produce a
weighted average solution in extrapolated areas, instead of projecting
values. We wont use the faults in this gridding.

Overall, this will give a better-behaved property grid from sparse data for
which the fault blocks have been taken into consideration.

No matter how we grid the property, it must be defined in all areas of the pay
zone. Well store a map set of the pay zone for comparative purposes:

3) Erase your screen and display only line contours for the Gross_Isochore.
Use a light blue contours.

4) Save the display as a map set called PayZone.

Chapter 20 - 14 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 15


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

Grid the Property Data


1. Click on Modeling > Single Surface and use Convergent gridding to
create a grid for each property.
Pick Data = mm_TARBERT_NESS_Porosity
Set Algorithm to Convergent.
Pick Fault = Ness_Tarbert.
Toggle OFF Polygon.
Set Initial Interval to 250.
Click on Advanced parameters, and
Set Order of Projection to First (This uses linear slope projection)
Set Weight Function to Statistical (This tends to spread the
weights fairly evenly)
Set Z_Limiting_Mode = Smooth Clip
Set Z_min. = .1
Set Z_max. = .8.
Let the name of the output grid default to the name of the data set,
mm_TARBERT_NESS_Porosity
Click OK.

2. Use Fast Color-shading to render the grid, then display the data points
on top. You should see a grid similar to the one below:

Chapter 20 - 16 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

The advantage of using the fault boundaries during gridding is that we get a
much more accurate model. Luckily, there is enough data in each fault block
to define almost all of the blocks.

The one exception is the small block in the North which is included in the pay
zone, but not defined in the property grid. This will become defined in the next
property gridding step. Note how the grid is tightly defined only around the
data. We controlled this with a small Initial Grid Interval.

Lets now continue with the second gridding for the final property grid.

3. Copy the property grid, mm_TARBERT_NESS_Porosity to a data


set called Porosity

4. Create another grid called Porosity with the Convergent algorithm


using the same parameters except the following:
Use Porosity as the input data.
Dont use any fault boundaries during gridding
Set the Initial Grid Interval to about 500 m.
Set Order of Projection to Zero
Set Weight Function to Uniform

5. Color-shade the resulting grid, using the faults for contouring, but not
for display, and display the map set PayZone on top.

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 17


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

This final porosity grid covers the area of the pay zone and looks to be
OK.

6. Now repeat this process for the net/gross data set and the saturation
data sets mm_TARBERT_NESS_net-gross and
mm_TARBERT_NESS_WSat_, creating a similar grid for each, one
called NetGross, the other called Saturation

The initial and final grids for each are shown below.

Chapter 20 - 18 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 19


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

Exercise

Apply Property Grids to Gross_Isochore

As outlined in the lecture notes, well now use the CPS-3 multiple grid
operations to create the volumetric grids. We could use the multiple-grid
formula processor in CPS-3 to compute the final volumetric grid in one
process, but for sensitivity studies and for investigating results using different
Zone Versions for properties, well calculate the traditional intermediate grids
one at a time.

Quality Control Considerations for the Property Grids

At this point, the most important things to verify about our three property
grids are:

1. Make sure that all three grids are defined within the area of the gross
isochore.

2. Make sure that none of the grids have flat, zero areas, or negative
areas. Its OK to be blank outside of the gross isochore, but no
property grid should not be negative anywhere.

If the property grids do not fit these requirements, they should be regridded
with different parameters until they do.

Quality Control Considerations for the Intermediate Volumetric


Grids

For the grids we will be creating in this exercise,


Make sure that the shape of the reservoir is maintained in each grid. In
other words, the zero line of all of these grids should be the same
Ensure that false positive features are not introduced in the grids. This
means that no new positive areas should show up outside of the
original zero line. This can happen if any of the property grids are
allowed to go below zero.

Chapter 20 - 20 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

Compute Net_Isochore Grid


1. Click Operations > Grid > Multiple Grids and select C = A * B.

2. For C, create a new set named Net_Isochore, and click OK.

3. For A, select Gross_Isochore.

4. For B, select NetGross.

5. Click OK. Use the statistics tool to check the Z-range of the output
grid. The grid should retain negative vales from the gross isochore.

6. Create a contour map of the output grid with these parameters:


Start contour level = 0.0
Increment between contours = 10.0

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 21


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

Compute Net Pore Volume Grid


1. Click Operations > Grid > Multiple Grid and select C = A * B.
For C, create a new set name, Net_Pore_Volume.
For A, pick Net_Isochore.
For B, pick Porosity.
Click OK.

2. Go to Display > Contours and color-shade the output grid as above

Chapter 20 - 22 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

Compute Net Pay Grid


For the Net_Pay grid, we will use the CPS-3 Formula Processer to finish the
calculations. So far, we have calculated:

Gross_Thickness * Net_to_Gross * Porosity.

The remaining term in the equation is (1.0 - Water_Saturation) and it will


give us the desired grid, Net_Pay, from which to compute oil in place.

1. Click on Operations > Grid > Formula.

2. Enter C=A*(1.0-B) under the Formula Editor.

3. Click the Scan button (below the formula field) and a semicolon
should appear at the end of the formula. If it does not, you will see
Syntax error in the Status text field - this means the formula was not
entered correctly. Try again until the semicolon appears after clicking
Scan.

4. Highlight C (NULL) in the Formula Variable Definition section, and


type Net_Pay in the bottom text entry field.

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 23


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

5. Press Return.

6. Highlight A (NULL) in the Formula Variable Definition section.

7. Scroll through the Surface Set list, and highlight Net_Pore_Volume.


Click Associate.

8. Highlight B (NULL) in the Formula Variable Definition section, and


in a similar manner as above, associate B with the grid Saturation.

9. Click Calc and answer No to Conformal Limiting.

10. After the calculation is finished, click Save and provide the name of a
file in which to save the formula. (Dont forget to specify the file suffix
of .frm.)

11. Click Dismiss.

12. Erase the screen and display contours for the Net_Pay grid, which
should resemble the map below.

Chapter 20 - 24 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

Verify Net Pay Grid


In this particular reservoir, we know that there should be only positive volume
everywhere within its boundary as shown above.

1. Verify that this final grid is positive everywhere within its boundary by
doing the following:
Erase the screen
Contour the Zero Line of the Net Pay grid.
Color shade the Net Pay grid, but color shade values only
beginning at 0.0 using a contour interval of -10.

If any color-shaded contours appear within the reservoir boundary, this means
that one of the previous operations did not work as intended. The instructor
will help you determine which step of the procedure caused the problem.

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 25


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

Fault Boundaries and Grid-to-grid operations


In all the logical operations which we have performed to shape the envelope,
and all the grid arithmetic we have performed to compute the Net_Pay grid,
we have not used the fault boundaries (traces) at all. The reason for this is that
the CPS-3 logical operations and grid arithmetic functions perform their
calculations node-by-node, vertically, on corresponding grid nodes of the
input grids.

For these operations, the fault boundaries are not needed.

Chapter 20 - 26 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

Exercise

Lease Blocks from ASCII Files

Since volumetrics is typically computed within specific lease blocks, we will


load an ASCII file containing four leases and then compute OIP associated
with each.

Here are two ASCII files, each containing the same basic information for our
lease polygons. The first file contains subset markers with the lease name to
mark the beginning of each subset. The second file contains the lease name in
every record, and CPS-3 can tell the end of one lease when the name changes.
Use either format you like for loading polygons.

k_leases_a.ply k_leases_b.ply

This file which we will actually use today is the file named
mm_north_leases.ply, which is to be found in your CPS-3 dsl. It resembles
the first file above, in that it contains CPS-3 subset markers to identify each
lease polygon.

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 27


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

Load the Polygon File of Leases


1. Click File > Import > ASCII > Polygon.

2. Select mm_north_leases.ply from the File Selection Dialog. (This


opens the Input a Polygon File dialog box.)

3. Click New to create a Polygon set called Leases as the Output Set.

4. Click OK to return to the Input a Polygon File dialog box. Click on


Assign Input/Output Parameters to open the Read/Write an ASCII
File dialog box, and make the following selections:
Close polygon? = Yes
Calculation mode = Inside only
File Type = CPS-3 (because it has subset markers)
Record type = XY
Format = Ordered Input/Output
Click OK to close the dialog box.
Click OK to return to the CPS-3 Main Module.

Chapter 20 - 28 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

Display the Polygons


1. Go to Display > Basemap.
Toggle Border and Labels on.
Set your own parameters, and click OK.
Toggle Polygons on, and pick Leases.
In Parameters, select a thick black line and click OK.

2. Click OK in Basemap Display dialog box.

Note that portions of some of the polygons fall outside the border of
the Display environment. This will not affect the volumetric
calculations.

3. Go to Display > Basemap again.

4. Toggle Polygons on, ensure Leases is selected, and click Set


Parameters.

5. For this procedure, set the following parameters:


Line color = light gray
First polygon of set to use = 1
Number of polygons to use = 1

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 29


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

Polygon fill method = Solid Fill


Click OK.

6. Click Apply in the Basemap Display dialog box.

7. Display the polygon set again, but make the following settings:
Line color = red
First polygon of set to use = 2

8. Display the polygon set again, but make the following settings:
Line color = yellow
First polygon of set to use = 3

9. Display the polygon set again, but make the following settings:
Line color = light blue
First polygon of set to use = 4

10. Now display the whole polygon again with a black line, setting First
Polygon = 1, Number of Polygons = All, and Polygon Fill Method =
NoFill.

11. Click OK to close the parameter dialog box.

12. Toggle Map Set to red, and select the Lease_Names map set for
display.

13. Click OK to close the Basemap Display dialog box.

Chapter 20 - 30 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 31


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

Exercise

Computing Oil In Place

The CPS-3 Volumetrics procedure is used to calculate oil in place. This


procedure performs numerical integration between a grid and a base plane. It
calculates volume grid cell by grid cell, and has the ability to differentiate
the volume on either side of a fault or lease line whenever a cell is dissected
by it. The instructor should provide a discussion of the volumetrics algorithm
based on the on-line documentation for this procedure. In particular, the
refinement parameter should be discussed.

Follow these steps to compute the oil in place from the Net_Pay grid.

1. In the CPS-3 Main Module, Click on Operations>Volumetrics.

2. Select the input Grid as Net_Pay.

3. Toggle on Faults and select Ness_Tarbert.

4. Toggle on Polygon and select North_Leases. Click OK.

North_Leases
Polygon Set

Chapter 20 - 32 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

Set Volume algorithm to Full Refinement.


Set Reference plane elevation (Z units) to 0.0.
Set Scale factor for all area results to meter^2 => acres.
Set Scale factor for all volume results to m^2*m => MMBL.
Toggle on Dont do slice volumes.
Make sure that First Polygon is 1 and Number to Use is All
Click OK.

Looking at the CPS-3 Status Information window, the report for the last
polygon, End_o_Rainbow, should be visible.

GeoFrame 4.0 Introduction to CPS-3 Chapter 20 - 33


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

MyPart

We are only interested in the first section of numbers:

Integrated Results ABOVE the Horizontal Reference Plane in the report.

The other sections are useful only if your volumetric grid represents a
structural model (topography) and you want to compute differences between
volumes above a certain elevation and below that elevation which is useful in
earth movement applications.

Note that the Volume reported, 42.1967 is in MMBL, and all Areas reported
are in acres. Your results will probably be slightly different due to the
multitude of steps required to get to this point.

Had we used something other than Full Refinement for the volume algorithm,
the results might have been somewhat less accurate, but would have run a bit
faster. When accuracy is the main consideration, use Full Refinement.

Chapter 20 - 34 GeoFrame 4.0 Introduction to CPS-3


Chapter 21
Editing Exercises

Overview
The purpose of this chapter is to introduce students to the interactive editing
tools available in CPS-3:
Model Editor
Color Palette Editor
Map Editor

The exercises suggested here are relatively unstructured and the recommended
procedure is for the instructor to present the lecture notes for each topic, then
demonstrate the facilities, and then let the students follow suit after each
demonstration. Student experimentation is encouraged with help from the
instructor.

GeoFrame Introduction to CPS-3 Chapter 21 - 1


Editing Exercises Schlumberger

Model Editor Overview

Figure 21.1 CPS-3 Model Editor displaying its Pan/Zoom feature

The CPS3 Model Editor is a powerful tool that lets you edit gridded surface
models, along with data, faults, polylines, and cultural features. Surfaces are
edited though manipulation of contour lines and/or data values and fault
locations. After the edits are complete, the surface is then regridded using the
changed contours and/or data.
You may also change a grid by simply editing the node values directly in a
variety of ways.

The Model Editor gives you greater control during modeling, and allows you
to focus in specific areas for modification. It lets you integrate your knowledge
and interpretation into the modeling process.

Aside from editing the gridded model itself, the Model Editor has many
provisions for making changes to your Data sets, Fault sets, and Polygon
sets.

Chapter 21 - 2 GeoFrame Introduction to CPS-3


Schlumberger Editing Exercises

Starting the Model Editor


There are four locations at which the Model Editor may be launched. There
are also two modes in which launching occurs: independent mode and open
mode.

Independent Mode

When launched in independent mode, the Model Editor makes no


assumptions regarding the sets which you may wish to edit. After it comes up,
you load each set you want by clicking File > Load as below.

Figure 21.1 CPS-3 Model Editor displaying its load features

The Model Editor is launched in independent mode from the following two
two locations:
In the GeoFrame Visualization Catalog, click on Model Editor.
At the bottom, designate on which monitor you want the Model
Editor to be launched.
< machine_name>:0.0 will launch it on the left monitor, :0.1 will
launch to the right.
Click OK.
In the CPS-3 Main Module, click Tools > Model Editor.

Open Set Mode

When launched in open set mode, the Model Editor assumes that you want it
to load those sets which are currently open in your CPS-3 session. Look at
your CPS-3 Status Information window and it will show you the currently
open sets at the top of the window. The following dialog box appears in open
set mode, and you can change any of the set names before the Model Editor
launches and loads them.

GeoFrame Introduction to CPS-3 Chapter 21 - 3


Editing Exercises Schlumberger

Figure 21.1 Link to Model Editor dialog box

The Model Editor is launched in open set mode in the following two
methods:
In the CPS-3 Main Module, click Operations > Surface/Model
Editor.
Click on the Model Editor icon.

Chapter 21 - 4 GeoFrame Introduction to CPS-3


Schlumberger Editing Exercises

Model Editor functions


The Model Editor has many features within its icons and menus, and there
are many ways to actually modify a grid, based on personal preference. Here,
we refer you to the on-line CPS-3 Users Guide which contains
menu-by-menu and icon-by-icon documentation of every feature included in
the Model Editor.

We recommend that you read this documentation if you intend to use the
Model Editor to any degree.

In this chapter, however, we want to go through examples of some of the most


common editing tasks using the Model Editor, rather than recite the function
of each menu and icon. which is well done in the document above.

Typical Editor session


Launch Model Editor.
Load the surface set, along with relevant data and faults, if any.
Generate surface contours lines.
Identify the area need to be edited, zoom in if necessary.
Edit the contours, data points, faults, polylines, etc., as needed.
Set an edit window to enclose all your modifications in this area.
Regrid the area defined by the edit window.
If the regridded results, showing as contours in a different color,
are NOT satisfactory, Undo regrid.
Go back to editing, and regrid again.
Recalculate contours to match the contours for the regridded node
values, if the regridding reached the desired results.
Repeat Step 2 - 6, as needed, until you are satisfied with the entire
surface.
Save your edits.

GeoFrame Introduction to CPS-3 Chapter 21 - 5


Editing Exercises Schlumberger

Tips Regarding Grid Editing


It is better to edit your data and regrid the entire surface in the CPS-3
Main Module, if possible, to make the corrections you desire. In this
way you are able to recreate the grid at any time, as long as the
original data is available.
If your surface requires editing in large areas, do not try to do it in the
Model Editor. The Model Editor was not designed to do regional
edits, but is most useful in small local edits to simply clean up a grid.
3. Edit each area independently, zooming into the smallest area
possible, and setting the smallest regridding area possible.
4. Save your grid often; use the Save As to retain intermediate versions
so that you do not lose your work.
5. Try to finish all your data and fault edits before moving on to your
surface edits.

Chapter 21 - 6 GeoFrame Introduction to CPS-3


Schlumberger Editing Exercises

Exercise

Model Editor

After presentation of the lecture notes (Topic 23 - Model Editor), these


exercises are suggested:

1. Load a faulted grid

2. Select a structural feature to flatten

3. Cut, Draw, and Extend contours as required to flatten the area, then
regrid, recalculate contours, and Save the grid.

4. Load fault traces

5. Move traces, Move points, create new traces, then Save.

6. Load scatter data set

7. Add new data points, delete points, change z-value, digitize a new
closed polygon, delete points inside polygon.

GeoFrame Introduction to CPS-3 Chapter 21 - 7


Editing Exercises Schlumberger

Overview of the CPS-3 Map Editor


The CPS-3 Map Editor lets you perform simple graphic editing on saved
map sets. Map sets are saved during sessions in the CPS-3 Main Module and
contain graphic objects and their attributes. Map sets are identifiable by their
UNIX file extension, .mcps. The Map Editor is not a substitute for a full-
featured CAD program. It does, however, provide a number of useful editing
features.
Add, move, copy, and delete text and symbols.
Modify graphical attributes, such as font, size, color, rotation angle,
justification, etc., for text and symbols.
Modify graphical attributes for lines and polygons (polylines), such as
line color, style, thickness.
View and edit map subsets.
Combine up to five map sets into a composite map.


Tip: The Map Editor performs only graphic editing, and is limited to moving and
creating simple objects and modifying their attributes, such as color, font, size,
line style, width. The main use of this application is to clean up maps which
have already been created. The Map Editor is NOT designed for editing
contours, data sets, fault sets, polygon sets, or grids. These should be edited in
the CPS-3 Model Editor. Changes made in the Map Editor will only be
reflected in the CPS-3 Map set.

Chapter 21 - 8 GeoFrame Introduction to CPS-3


Schlumberger Editing Exercises

Starting the Map Editor


There are two ways to start the Map Editor.
GeoFrame Application Manager > Visualization icon >
Visualization Catalog
Click on the CPS-3 folder
Click once on Map Editor to highlight it, and at the bottom,
designate the monitor on which to launch it.
Click OK.
You may also launch the Map Editor from the CPS-3 Main Module,
under Tools. (The target screen is controlled at the bottom of the
Visualization Catalog.

Figure 21.1 CPS-3 Map Editor main menu

GeoFrame Introduction to CPS-3 Chapter 21 - 9


Editing Exercises Schlumberger

Pull-down menus
The pull-down menus - File, Activate, Mode, View and Options are located
across the top of the Map Editor window. Most of the functions under the
pull-down menus are also available as icons in the tool bar. Here are some of
the functions:

File
Load: you may load up to 5 map sets for each session;
Save: save the edited map set;
Save as: save the edited map set under a different name;
Unload: unload a map set from the session;
Exit: exit the session.

Activate
Map set: same as the icon (ACTIVATE:) Map. Among the loaded
map sets (up to 5 sets), only one of them is active. If not picked here,
the last one loaded to the session will be the active map set, which is
the one on display.
Editable Layers: same as the icon (ACTIVATE:) E Layers. All
elements/subsets of the active map set are listed here as separate
layers. You may turn ON and OFF any of them to allow selected ones
to be edited. The layers you turn off may NOT be edited.
Viewable Layers: same as the icon (ACTIVATE:) V Layers. All
elements/subsets of the active map set are listed here as separate
layers. You may turn off certain layers to hide them temporarily if you
do not want them to be on display.

Mode

Under Mode, you will see three groups of functions, Select, Add and
Composite. Functions under each group are also iconized in the tool bar.

Figure 21.1 CPS-3 Map Editor bar menu

Chapter 21 - 10 GeoFrame Introduction to CPS-3


Schlumberger Editing Exercises

Select Mode
Browse: This function displays the x,y location of the cursor as you
click the mouse button.
Move: This function allows you to move an object. Click on the Move
button, and click on the object that you want to move. You will see a
white frame enclosing the object you just picked. Leave the cursor
inside the white frame and click the mouse button again to pick the
white frame up and drop to the place you want to move to. You can
only move one object at a time.
Delete: This function allows you to delete an object. Click on the
Delete button, and click on the object that you want to delete. You will
see a white frame enclosing the object you just picked. Leave the
cursor inside the white frame and click the mouse button again to
delete the object. You can only delete one object at a time.
Copy: This function allows you to copy an object. Click on the Copy
button, and click on the object that you want to copy. You will see a
white frame enclosing the object you just picked. Leave the cursor
inside the white frame and click the mouse button again to pick the
white frame up and drop to the place you want to copy to. You can
only copy one object at a time.
Attribute: This function allows you to change the graphic attributes of
an object. To change attributes, click on the Attr button, and click on
the object you want to change. You will see a white frame enclosing
the object that you just picked. Leave the cursor inside the white frame
and click the mouse button again, an attribute dialog box will pop up.
If the object you picked is text, you can change the text content, size,
rotation angle, font, color, quality and justification. If it is a symbol,
you will be able to select a different symbol, along with size, color and
rotation angle. If it is a line, you may change the line style, width,
color and smoothness. After you input the new attributes, click on
Apply button. The changes will display on screen. You can only
change attributes on one object at a time.


Note: Changing of text font will not show up in the Map Editor display.

GeoFrame Introduction to CPS-3 Chapter 21 - 11


Editing Exercises Schlumberger

Add Mode

This feature allows you add text and symbols to a map set.
Text: To add text, click on the (ADD:) Text button, displaying a dialog
box which allows you to specify text attributes. After setting the text
attributes, click on the Apply button. Then move the cursor to the Map
Editor window, a white frame will appear. Locate the white frame at
where you want the text to be, click the mouse button again to display
it.
Symbol: To add a symbol, click on the (ADD:) Symbol button,
displaying a dialog box which allows to you pick a symbol from the
library and specify its attributes. After setting the symbol attributes,
click on the Apply button. Then move the cursor to the Map Editor
window, a white frame will appear. Locate the white frame at where
you want the symbol to be, click on mouse button again to display it.

Composite Mode

Composite functions allow you to combine up to five map sets to make a


single, composite map.
Base: This provides you with a blank canvas on which you can size
and arrange the active map set, leaving space for pasting additional
map sets. If Grid is turned ON, the canvas will show grid marks. If the
Snap to Grid function is ON, the size of the map set will be snapped
to the nearest grid mark.
Paste: Other than the active map set, all additional map sets loaded
into the session (up to four sets) can be pasted onto the canvas. You
can resize and rearrange these map sets. The Grid and Snap function
works the same way as in Base mode.
Frame: This function allows you to enlarge the border of your
composite map set.
Grid: This function allows you to turn the grid mark on the canvas ON
and OFF, turn Snap to Grid function ON and OFF, and define the size
of the grid on the canvas.

View
Refresh - redraws the contents of the screen.
Zoom - provides zoom functions - In, Out, Extents

Chapter 21 - 12 GeoFrame Introduction to CPS-3


Schlumberger Editing Exercises

Options
Icon Bar -toggles to icon bar on and off.
Info Window - toggles the info window on and off
Set Background Color - changes the background color of the canvas
Set Line Edit On - edits a line
Set Point Edit On - edits a single point
Set Quick Screen Repair - sets quick refresh

GeoFrame Introduction to CPS-3 Chapter 21 - 13


Editing Exercises Schlumberger

Exercise

Map Editor

After presentation of the lecture notes (Topic 25, Map Editor), these exercises
are suggested:

1. Import a map

2. Move characters, change colors

3. Save map.

Chapter 21 - 14 GeoFrame Introduction to CPS-3


Schlumberger Editing Exercises

Exercise

Color Palette Editor

Basic Facts - 127 and 256 Color Limits


Each application, which runs on a UNIX workstation, uses up a certain
number of the 256 maximum colors per color map currently allowed at this
time by UNIX.

Sometimes 256 colors is insufficient, and it may be necessary to shut down


certain applications known to be color hogs in your work environment. It is
also possible to invoke the version of CPS-3 which uses a private color map.
This will provide a separate 256-color UNIX color map for the CPS-3
applications. The only drawback to the private color map is the annoyance of
color flashing which occurs as you move the cursor from one application to
another.

In this exercise, we will define less than 30 colors, so we should not be


affected by the lack of colors in the UNIX color map. Note that regardless of
how many colors are available in the UNIX color map, the 127-color limit for
the Color Palette Editor will still remain. If you do have palettes with more
than 127 colors, use the Starting color index in the upper left of the menu to
establish the first of the 127 colors you wish to see. For example, the CPS-3
Rainbow palette has 171 colors. If you want to work with the last 127 colors
in this palette, then set the Starting color to 43.

1. Create a simple palette for use in error mapping. Color 1 = red, Color
2 = White, and Color 3 = blue.

2. Create a distributed 100-color palette with Yellow at the top, Blue in


the middle, and White at the end. Assign a z-value of 1000 to the top,
2000 to the middle and 2500 to the bottom.

GeoFrame Introduction to CPS-3 Chapter 21 - 15


Editing Exercises Schlumberger

Chapter 21 - 16 GeoFrame Introduction to CPS-3


Chapter 22
CPS-3 Macros

Overview

One of the most useful features in a mapping package is the ability to perform
a series of predefined steps at different times or under different conditions.
CPS-3 has had the ability to make macros for some time, but macro
extensibility has not been generally possible. Recently, however, macros were
made much more powerful with the introduction of a flexible macro
command language, which are an addition to the current macro structure, and
allow prompting, variable substitution, and other features to make macros
more powerful than before.

There are 3 categories of macros, defined by where they are stored:

1. System macros - stored in <install_path>/cps3_run_mac/

2. Project macros - stored in the projects CPS-3 dsl.

3. User macros - stored in user-specified location

GeoFrame 4.0 Introduction to CPS-3 Chapter 22 - 1


CPS-3 Macros Schlumberger

Basic Macro Format


A macro is a simple ASCII file that contains a series of CPS-3 native
mapping commands. Native commands are documented in the Reference
Manual, which is available on-line under Tools in the CPS-3 Main Module.
You do not need to know native commands in order to use macros. Those who
run macros frequently become knowledgeable about native commands, but it
is not necessary to begin using them. Being stored in ASCII files, macros are
easily transported and edited. A portion of an ASCII macro file is shown
below as seen from the Unix TextEdit: file editor.

Creating Macros
Macros are built, one command at a time, interactively in the CPS-3 Main
Module, as you step through the dialog boxes performing the actions which
you want to be stored in the macro. You can choose to only go through the
motions when creating a macro, or you can literally execute the steps as you

Chapter 22 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Macros

create it. By executing the steps as you go, you can catch errors which you
would not see if you only go through the motions, however, both methods
have their uses.

Once created, the macro is placed in the Project macro directory, which is the
projects CPS-3 dsl.

Macro Grouping

For all your macros, you have the option to organize them into meaningful
groups. Read how to do this in the online CPS-3 User Manual. You can
define group names in a simple file, and assign each macro to a different
group. As you access the Macro functions from the Main Module menu, you
then have the opportunity to select your macros by group.

Running Macros
After you create a macro from CPS-3, you can run it macro interactively, or
in the background while you continue other mapping tasks. Macros enable
you to automate common, repetitive mapping tasks, as well as mapping tasks
that take a long time to complete.

Making a Macro Universally Useful


As created from CPS-3, macros contain the actual set names which were used
for input and output as the macro was created. This limits the flexibility of
macros, and this is why the macro command language was added to the
system - to be able to transform the fixed-name initial macro into a universal
tool which itself is able to prompt the user for the names of input and output
sets. The macro command language also adds other capabilities to macros
besides prompting such as executing loops, executing system commands, and
calling other macros.

Below, youll see how to modify a fixed-name macro into one which prompts
for input.

Besides the Project macros, this version of CPS-3 supports access to an


existing library of macros called System macros which are found in the
GeoFrame installation directory under the sub-directory .../cps3_run_mac/.

GeoFrame 4.0 Introduction to CPS-3 Chapter 22 - 3


CPS-3 Macros Schlumberger

The New Macro Language Abilities

The new language provides you with a variety of abilities within any macro
you create with CPS-3. These abilities are listed below.
Establish named variables in a macro for your own purposes.
Variables can contain characters, numbers, set names, or colors.
Perform arithmetic and logical operations between variables.
Control the flow of the macro with these operators:
While statement
If - Then - Else
Add interactive prompting inside the macro to establish variable
values.
Perform substitution operations on set names and parameter values
before the macro is run.
Spawn detached processes, or spawn a process and wait for it to finish.


Note: For detailed descriptions of each of these language facilities, please refer to
the chapter about Macros in the CPS-3 Users Manual.

Chapter 22 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Macros

Basic Facts about Macro Syntax and Organization


Every line in the macro which starts with an exclamation point is a
comment.
Every line in the macro which starts with a six-letter command
beginning with F, such as F1SWIT is a parameter-setting command.
Each value following a parameter-setting command sets the value of a
specific parameter. Some commands contain only one parameter,
others contain many more parameters.
Every line in the macro which starts with a six-letter command
beginning with M, such as M1OPEN, is an operation command.
Some operation commands rely on previous parameter-setting
commands to establish how the command will be executed, such as
MSTRN1. Others rely on parameters which occur on the same line of
the operation, such as M1OPEN.
All parameter-setting commands and operation commands are
documented in detail in the CPS-3 Reference Manual, which can be
found under Tools in the CPS-3 Main Module.

GeoFrame 4.0 Introduction to CPS-3 Chapter 22 - 5


CPS-3 Macros Schlumberger

Typical Prompting Language Added to a Macro

Below, you see some typical macro commands relating to prompting


components which are added to macros. These commands are in a file call
k_prompt.mac in the external training data for CPS-3.

This file could be inserted as it is into a macro if you wanted to prompt for a
Data set, and an output Surface set name. As you can see, this file could be
used as simple template and you can change the names, or even add others
sets to be prompted for. Refer to the on-line Users Manual for details.

Looking at each command in this example, we see that

declare defines variables such as set names or strings.

let assigns initial values to the variables

begin_dlg and end_dlg bracket the prompting commands for a single


dialog

prompt activates a single prompt line in the dialog for one variable

In general, variables should be declared as set, if they will be used for the
selection of existing input sets. Variables declared as string are set by the user
only by typed response.

Substituting Fixed Set Names with Variable Names

The next phase in making a macro universally useful is to find all places lower
in the macro where the fixed-name sets are specified, and change them to the
appropriate variable name. For example, if the original unedited macro
contained the line

Chapter 22 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Macros

M1OPEN DA mysetname UNKNOWN

which opens a Data set named mysetname, we should replace the fixed set
name (including double quotes) with the variable name $DATA1 (including
the Dollar sign):
M1OPEN DA $DATA 1UNKNOWN

After all fixed set names have been replaced as shown with the proper variable
name, the macro will have been converted into a universally useful tool which
can be passed around for anyone to use in their own project.

Scan the Edited Macro for Errors


If you like you can scan an edited macro for errors before you actually try to
use it. Use the MACROS/SCAN features

GeoFrame 4.0 Introduction to CPS-3 Chapter 22 - 7


CPS-3 Macros Schlumberger

Current Constraints: Macro Execution and Environments


1. At present, no information is written to a macro during Macro Creation
during Environment selection, creation, or editing.

2. At present, there is no macro command language to create new


environments or edit existing environments

3. At present, when a macro executes, it assumes that the currently


active display and modeling environments are to be used. You can
change this, as will be shown below, by inserting various environment-
related commands in the macro.

Getting Around the Constraints


Future releases may improve upon these constraints, but until then, we must
use whatever tools are available to help us manage environments within
macros. Below, we document what is available in this release of the software.
These capabilities exist because environments are stored in the CPS-3 session
files.

To cause a specific session file be used in a macro:

Add the following line in the macro.

READ <full path to a saved session file name>

Session files are files of the form <login_id>.1cps.

To add a display environment specification in a macro:

Add the following line in the macro:

F1DRAW n

where n is an environment number in the current session file. The only way to
determine n is to view all environments in CPS-3 and identify it in the GUI.

To add a modeling environment specification in a macro

Add the following line in the macro:

F1MODL n

where n is an environment number in the current session file.

Chapter 22 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Macros

To save the currently defined modeling environments to a session


file when in CPS-3:

Although not specifically applicable inside of a macro, this function is run


from the CPS-3 Main Module and is useful in preparing a session file for a
macro to use. In the CPS-3 Status Information window, enter the following
command at the bottom of the dialog box in the field labeled CPS-3
Command. This command can be done at any time, but should probably be
done just before you begin to make your macro.

SAVE <name of file to contain the saved session file>

Compatibility: Running Pre-GF3.5 Macros


Since many internal formats and parameter storage mechanisms have changed,
older macros must be converted to the current macro format before being
executed. The rules for pre-GF3.5 macros are as follows:

The macro is read and then converted to a 6.0 macro, having a naming
convention of CPS60_<old name>. During this process, older native
commands such as F1WINE, F1GINC, F1ZTYP, F1UNIT, and F1VSCL,
which were previously used to establish a primitive mapping environment, are
commented out.

After a macro has been converted, it contains a header record at the beginning
of the file which looks like

!CPS_VERSION_6.0 T=98

which means that CPS-3 will read and execute the macro without assuming
that it needs conversion. All macros created in GF3.5 and later will contain the
same header, so that no conversion will be attempted.

Managing Macros - Enhancements for GF4.0


Please refer to the Lecture Document I40_c05_Newfor40 which describes
new capabilities for macros regarding their organization, description, and
selection.

GeoFrame 4.0 Introduction to CPS-3 Chapter 22 - 9


CPS-3 Macros Schlumberger

Chapter 22 - 10 GeoFrame 4.0 Introduction to CPS-3


Chapter 23
Graphic Operations in CPS-3

Overview

In this chapter, you will be introduced to many concepts in CPS-3 associated


with the creation, storage, modification, clipping, viewing, and plotting of
graphic displays. In earlier chapters, we talked about mapping environments
and how the X,Y box is the most visible of environment attributes. Here, we
will show how graphic objects are classified and how each interacts with the
X,Y box of the changing Display environments during your CPS-3 session.

Graphic Display in CPS


Whenever anything is displayed on the screen in CPS-3, it is recorded in
screen memory, which is actually a hidden CPS-3 map set used to refresh the
screen quickly.

GeoFrame 4.0 Introduction to CPS-3 Chapter 23 - 1


Graphic Operations in CPS-3 Schlumberger

If a permanent copy of the screen contents is desired, use the Save currently
displayed map icon to write screen memory to a permanent CPS-3 map
set.

Saved map sets retain all displayed graphic components and their attributes. In
addition, subset markers are written into the map set so that the graphic output
of one process can be distinguished from another. These layers of a saved map
set can be deleted, or rearranged, if desired. Use the Manipulate current
map layers icon to invoke the Map Layer Manager.

We will perform an exercise later in the course to illustrate how map layers are
rearranged and deleted.

Honoring the Active Display Environment


Before anything is actually stored in screen memory, the active display
environment determines if any type of transformation is required. In
particular, the displayed data may be:
transformed to the active Geographic Coordinate System
scaled to the active scale
converted to the active horizontal and vertical units
clipped by the active Volume of Interest (VOI)

Chapter 23 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Graphic Operations in CPS-3

It is the last operation, clipping, which provides the main focus for this
chapter. We will discuss conditions when graphic displays become clipped, or
when they are merely hidden.


Note: The basic 2D clipping rectangle is defined by the X and Y extents of the
Volume of Interest. However, these can be enlarged by the temporary
specification of a Top, Bottom, Right, and Left margin, if desired.

When Are Graphic Objects Clipped?

Two Display Classes

For clipping purposes, objects to be displayed in CPS-3 fall into one of two
classes - Inside objects and Outside objects.

Inside

Inside objects (see the following) are clipped to the Volume of Interest
during display.
Data
Faults
Polygons
Surfaces
Maps (optional)

Any graphic manifestations of the CPS-3 set types shown above, such as point
display, polylines, data value display, or contouring, are also considered to be
Inside objects, and any graphics generated outside the X,Y box will be
discarded.

Upon displaying a Map set, you will be given the choice of treating it as an
Inside or Outside object, as desired.

Outside

Outside objects are NOT clipped during display. The following are
considered Outside objects:
Maps (optional)
Borders,
Labels

GeoFrame 4.0 Introduction to CPS-3 Chapter 23 - 3


Graphic Operations in CPS-3 Schlumberger

Title blocks
North arrows
In general, graphic output from all Basemap dialog boxes, except
Display Set and Lines and Annotation sections, is considered
Outside graphic objects.

Clipping During Graphic Display

When Inside objects are displayed on the screen, they are clipped exactly to
the active Volume of Interest, and then stored in Screen Memory. This
occurs whether the user is zoomed in or not.

When Outside objects are displayed on the screen, they are NOT clipped, and
are stored in their entirety in Screen Memory, even though they may not be
visible. Again, this occurs whether or not the user is zoomed in. Even though
Outside graphics may not fall within the visible area of the display, they can
be made visible by creating and activating a Display environment whose
display volume is large enough to include the data.

Alternatively, clicking the Reveal all graphics icon, will show all
graphic elements currently in screen memory.

The Reveal all graphics icon is activated when the current display does not
show all graphic components stored in Screen Memory. An example might be
a title block which was placed at some x and y offset from the lower left
corner of the map, but which fell outside the current viewing area.


Note: There was no mention of the current zoom window in the previous discussion
concerning clipping. Since there is now only one clipping window, which is
defined by the X, Y limits of the currently active Display environment, and the
margins, display of data while zoomed in will NOT cause the data to be
clipped to the zoom window. This means that when you zoom out again after
having displayed some data, you will see all of it inside the X, Y limits, not just
a piece of it, as in earlier versions.

In the exercises which follow, we will demonstrate the concept of graphic


clipping, and the difference between Inside and Outside graphic objects.

The exercises for this chapter will provide the opportunity to demonstrate the
principles discussed here.

Chapter 23 - 4 GeoFrame 4.0 Introduction to CPS-3


Chapter 24
CPS-3 Ascii Loader

Overview
The CPS-3 ASCII Data Loader is invoked from the CPS-3 Main Module
menu bar and offers a very wide variety of data loading features.

Click on File > Import > ASCII to see that you can load any of the five basic
set types in CPS-3 from ASCII files.

Figure 27.1 Available ASCII file types

The Extended Data type at the bottom is an enhanced method of loading


Data sets when it contains textual information or graphic symbology in the
file. This will be explained later.

While the CPS-3 ASCII Data Loader is very flexible and can load many
different file formats, there are certain conventions, regarding the organization
of these files, which are outlined in this chapter.

GeoFrame 4.0 Introduction to CPS-3 Chapter 24 - 1


CPS-3 Ascii Loader Schlumberger

General Requirements/Options
In general, each physical record in a data file represents one data point or
vertex in CPS-3.

All information associated with one point must be on the same physical
record.

There is a storage limit of 50 z-attributes per data point. That is, a data point
can have up to 50 z-values, each representing a measurement.

You can skip any number of records at the beginning of a file, but you
CANNOT skip any at the end. Trailer records, which are not data records,
must be physically deleted from the end of the file before loading.

Comments, prefaced with a ! in column 1 of a record, can be embedded in


any of the ASCII file types, and will be ignored.
The order of x, y, z, text, and symbology fields in each record is irrelevant,
since the location of each can be identified during input, This is not true,
however, when using the Ordered Input/Output loading method because the
system expects data fields to occur in this order: x, y, z1, z2,...zn.

Each x, y, z, text, and symbology field must be justified to the same column in
each record.

Defining Subsets During Loading


There are three ways to maintain the integrity of line-oriented data when
loading into CPS-3 from ASCII files. These methods apply to the loading of
Data, Fault, and Polygon sets.
Use subset markers in the file.
Encode the identifying name in each record in the file.
If no subset markers or names exist in the file, then a difference
threshold criteria will be initiated by CPS-3 while loading the points
to help it identify separate lines. The threshold works like this:
Let D1 be the distance between the current point being loaded and
the previous point loaded.
Let D2 be the distance between the previous point loaded and the
point before it.
If D1/D2 is greater than the threshold, then the current point being
loaded is considered to be the beginning of a new line.

Chapter 24 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Ascii Loader

ASCII Data Loading Menu

Most of the parameters on the following menu are self-explanatory, such as


the Number of Z fields parameter. File Type and Format, however, may need
some extra explanation.

Figure 27.2 Read/Write an ASCII File dialog box

Format

Format actually refers to the manner in which you want to define the contents
of the data fields in the ASCII file. These options apply to Data, Fault,
Polygon, Surface, and Map set loading.

1. Fortran Format Specification

In earlier versions of CPS-3, you could actually specify a Fortran format


statement to be used by CPS-3 when loading the different fields in your
ASCII data file. You can still do this by typing in the format in the menu, or
by including the format statement as the first record in the file. However, more
convenient methods are available as alternative choices in the menu.

GeoFrame 4.0 Introduction to CPS-3 Chapter 24 - 3


CPS-3 Ascii Loader Schlumberger

2. Ordered Input/Output

This method causes the system to read data in the following order from each
record without the user having to specify a format:

x, y, z1 ....zn

Each field must be separated by a comma and/or at least one space.

3. Point to Fields

This option provides you with a special menu on which your data file is
displayed so that you can pick the column limits for each field you want to
read into CPS-3.

File Types

There are almost no limits to the way in which ASCII data can be organized.
However, these predefined formats are simplistic enough to cover just about
any kind of data which is loaded into CPS-3.

1. X,Y,Z Only

This file format contains only x,y,z values in each data record and is typically
read using non-extended mode.
x1 y1 z1 . . . z1.n
x2 y2 z2 . . . z2.n
x3 y3 z3 . . . z3.n
...

2. X, Y, Z Plus Name Field

This format includes the name (for example, line name or well name) in each
record. This type is typically read using non-extended mode. All points having
the same name field will be grouped into the same subset with that name. If
the name field is a unique well name, then each well becomes its own subset,
and its name can be posted during graphic display.
x1 y1 z1 . . . z1.n JOE
x2 y2 z2 . . . z2.n SALLY
x3 y3 z3 . . . z2.n FRED
...

Chapter 24 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Ascii Loader

3. CPS-3 ASCII Format

Unlike other formats, this one incorporates the setting of parameter values at
the top of the file and uses subset markers to define subsets. When exported in
this format, the parameters associated with the set are automatically recorded
by the system. This can be an advantage when transferring sets from one
network node to another while still retaining certain set characteristics
embodied in the parameters. It is not common practice to load data with these
parameters unless reloading one which was exported from CPS-3. The main
advantage of this format is the use of the subset markers to define individual
lines and polylines. As with the other set formats, multiple z-fields may be
present.
! comments
! comments
...
native parameter command 1
native parameter command 2
native parameter command 3
...
->subset 1 name
x1 y1 z1 ...
x2 y2 z2 ...
x3 y3 z3 ...
->subset 2 name
x4 y4 z4 ...
x5 y5 z5 ...
x6 y6 z6 ...
...

GeoFrame 4.0 Introduction to CPS-3 Chapter 24 - 5


CPS-3 Ascii Loader Schlumberger

4. X,Y,Z with Text Fields and Symbology

In this format, multiple text fields exist in each record, as well as symbol
codes or other graphic attributes which are to be associated with the individual
data point or vertex represented by the record. As with other file formats,
multiple z-fields may be present. Data in this format should be loaded with the
Extended Data loader, so that all fields and symbology can be stored and
used.
x1 y1 z1 . . . Text1.1, 1.2 . . . Attribute1.1, 1.2 . . .
x2 y2 z2 . . . Text2.1, 2.2 . . . Attribute2.1, 2.2 . . .
x3 y3 z3 . . . Text3.1, 3.2 . . . Attribute3.1, 3.2 . . .

Extended and Non-Extended Data Sets


When loading Data sets, there are two loaders to choose from as mentioned
previously - the standard Data loader and the Extended Data loader.

Load data into non-extended data sets if it does not contain, or you do not
wish to use, textual or symbology fields. For example, if your ASCII data file
contains a well name and a well symbol code, but you do not plan to make use
of them, load just the x,y,z portion into a non-extended data set, ignoring the
other fields in the record.

Load data into extended data sets if the ASCII file contains text, numerics, or
symbology fields which you wish to display, or make use of, on a base map.
Examples of text fields - well name and operator name
Examples of numeric fields- shot point number and line number
Examples of symbology - well symbol, well symbol size, and well
symbol color

Chapter 24 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Ascii Loader

Examples of File Formats

Data Files

Here is an example of an X,Y,Z Only data file:


6438.0 3593.0 1017.91
6176.0 2636.2 991.80
6903.7 5122.1 967.90

Here is an example of X,Y,Z Only with multiple z-fields:


6438.0 3593.0 1017.91 43.4
6176.0 2636.2 991.80 52.9
6903.7 5122.1 967.90 46.7

Here is an example of well data in X,Y,Z Plus Name Field format with a well
name:

6438.0 3593.0 1017.9 R-01


6176.0 636.2 991.80 R-02
6903.7 5122.1 67.90 R-03

Here is an example of the same portion of the data file above in which the
fields are separated only by commas. This file can be read by selecting the
Ordered Input/Output format.

6438.0,3593.0,1017.9,R-01
6176.0,636.2,991.80,R-02
6903.7,5122.1,967.90,R-03

GeoFrame 4.0 Introduction to CPS-3 Chapter 24 - 7


CPS-3 Ascii Loader Schlumberger

Here is an example of simple 2D seismic data CPS-3 ASCII format:


! This data contains 2D seismic lines from the Wellington survey
! Use the vertical faults for Block Beta
->RAD-90-001
5547.700 2264.800 1131.000
5580.413 2284.136 1124.000
5613.125 2303.473 1119.000
5649.281 2324.845 1114.000
5691.462 2349.779 1108.000
5744.835 2381.328 1100.000
5792.182 2409.315 1094.000
5823.173 2427.634 1089.000
->CON-66-004
7472.566 3590.510 1021.000
5251.076 3663.922 1025.153
6405.266 1892.124 1097.970

...

Here is an example of X,Y,Z with Text Fields and Symbology with some
comments at the top, three z-fields, a well name, operator name, symbol code,
and a symbol color associated with each well location.The Extended Data
loader is best used to load these types of data files.
! This file contains example well data,
! for three horizons, Z1, Z2 and Z3,
! including a well name and symbol code
6438.0 3593.0 1017.9 1047.9 1.E+30 R-01 Mobil 2 4
6176.0 2636.2 991.80 1023.8 1054.3 R-02 Mobil 13 5
6903.7 5122.1 967.90 1000.9 1.E+30 R-03 Chevron 18 3
7472.5 3590.5 1021.0 1064.5 1104.0 R-04 Chevron 18 4
5251.0 3663.9 1025.1 1051.5 1.E+30 R-05 Chevron 19 2
6405.2 1892.1 1097.9 1136.9 1187.4 R-06 Chevron 56 3
5596.1 5106.4 993.00 1020.0 1.E+30 R-07 Chevron 42 7
6667.8 4027.9 1039.0 1073.0 1089.5 R-08 Mobil 19 5
5374.2 2944.7 1077.4 1103.4 1111.4 R-09 Chevron 18 5
7054.7 3155.6 1037.7 1070.5 1188.5 R-10 Chevron 18 6
6682.0 6009.0 969.10 1000.1 1.E+30 Z-01 Chevron 12 2
5420.7 4355.6 1009.4 1036.9 1.E+30 R-12 Chevron 17 1

Chapter 24 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Ascii Loader

6505.1 3030.2 1003.0 1034.0 1049.0 R-13 Chevron 42 1


6432.7 4873.2 1039.3 1068.8 1.E+30 R-14 Mobil 16 5
6720.8 3555.2 975.00 1012.6 1035.6 R-15 Mobil 55 4
5705.2 4187.9 996.10 1022.6 1.E+30 R-16 Chevron 16 5
3533.2 3956.2 1135.7 1157.7 1.E+30 Z-02 Chevron 13 1

Fault Files

Here is an example of a fault file showing the use of the subset markers to
define the separate fault traces for each named fault. It is valid for fault
vertices to contain z-values to aid in the gridding process. We would choose a
fault attribute of x,y only and a file type of CPS-3 format for loading this
data.

->Northwest_vertical
6101.402 2260.635
6037.690 2552.553
5958.145 2881.542
5867.917 3162.905
5905.114 2886.946
5989.938 2520.760
6101.402 2260.635
->Southern_Green_A
6398.598 3401.793
6387.917 3629.874
6387.917 3667.197
6377.361 3959.115
6377.361 4192.600
6414.432 3969.671
6430.392 3746.742
6425.114 3640.556

GeoFrame 4.0 Introduction to CPS-3 Chapter 24 - 9


CPS-3 Ascii Loader Schlumberger

Next is an example showing the same fault traces, but having the fault name
encoded on each vertex record, removing the need for the subset markers.We
would choose the attribute x,y only attribute, and the X,Y Plus Name Field
file type to load these faults.
6101.402 2260.635 Northwest_vertical
6037.690 2552.553 Northwest_vertical
5958.145 2881.542 Northwest_vertical
5867.917 3162.905 Northwest_vertical
5905.114 2886.946 Northwest_vertical
5989.938 2520.760 Northwest_vertical
6101.402 2260.635 Northwest_vertical
6398.598 3401.793 Southern_Green_A
6387.917 3629.874 Southern_Green_A
6387.917 3667.197 Southern_Green_A
6377.361 3959.115 Southern_Green_A
6377.361 4192.600 Southern_Green_A
6414.432 3969.671 Southern_Green_A
6430.392 3746.742 Southern_Green_A
6425.114 3640.556 Southern_Green_A

Polygon Files

Here is an example of a polygon lease file with lease names used as the subset
names.

->Smith_Hawking Lease
4101.402 2660.635
4037.690 2852.553
3958.145 2281.542
3867.917 3362.905
3905.114 2786.946
3989.938 2120.760
->Wiley_Chevron Lease
6698.598 2401.793
6787.917 2629.874
6787.917 2667.197
6477.361 2959.115
6477.361 3192.600

Chapter 24 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger CPS-3 Ascii Loader

Data Transformations
As ASCII data is imported or exported from CPS-3, transforms can be
applied to the data to move it, rotate it, scale it, or perform other arithmetic
operations. The transformation menu is shown below

Figure 27.3 Data Transforms dialog box

GeoFrame 4.0 Introduction to CPS-3 Chapter 24 - 11


CPS-3 Ascii Loader Schlumberger

List of Arithmetic Transforms


Absolute value of X
Absolute value of Y
Absolute value of Z
Translate in X
Translate in Y
Translate in Z
Scale in X, centered about an X-position
Scale in Y, centered about a Y-position
Scale in Z, centered about a Z-position
Rotate parallel to X-axis about a Y-Z position
Rotate parallel to Y-axis about a Z-X position
Rotate parallel to Z-axis about a X-Y position
Min/max limit in X
Min/max limit in Y
Min/max limit in Z
Set min/max limit condition to CLIP
Set min/max limit condition to REJECT (default)
Log of X
Log of Y
Log of Z
Set log to BASE-10 log
Set log to NATURAL log (default)
Reject record if any Z-field is INDT
Reject record if Z-field n is INDT

Chapter 24 - 12 GeoFrame 4.0 Introduction to CPS-3


Chapter 25
Convergent Algorithm Overview

Overview
The Convergent gridding algorithm has proven to be a very reliable and
predictable general-purpose gridding algorithm. Its innovative methodology
has clearly set a standard for the industry. In this chapter, we will give you a
brief overview of the mechanics of its operation, so that you can use the
information to your advantage.

Figure 28.1 Internal surface refinement in Convergent gridding

GeoFrame 4.0 Introduction to CPS-3 Chapter 25 - 1


Convergent Algorithm Overview Schlumberger

Iterative Procedure
Convergent gridding gets its name from a process whereby grid node values
are converged upon by iteratively assigning control point values to nearby grid
nodes. The process starts with a large grid cell size, the Starting Interval, in
the first iteration, and the process ends when the grid cell size reaches its
desired size, the Final Interval. The grid is refined to smaller and smaller cell
sizes between each iteration. At each iteration, each control point value is
assigned to a certain number of the closest grid nodes, specified by the
parameter Number of Nodes to snap to. Thus, the most important parameters
associated with the Convergent gridding algorithm are:
Starting Interval
Final Interval
Starting Number of Nodes to snap to (max = 16)

At each iteration, the algorithm performs the following operations:


assigns or interpolates control point values to nearby nodes. (In the
case of nodes already having a values, implement the blending scheme
described in the following Blending Algorithm section.)
smooths the grid
refines the grid

Through all iterations, the following become smaller:


The grid cell size
The Number of Nodes to snap to parameter (1 on the last
iteration)

As you can see, in the early iterations, each control point contributes to a large
geographic area, but in the final iterations, each control point is tied to a very
small area. The result of the Convergent gridding technique is that areas
outside of the data have been modeled with a smooth, trend-like solution, but
yet in the middle of the data, the grid ties the data as closely as the final grid
size will allow.

In the case of faulted surfaces, the Convergent algorithm applies the standard
visibility criteria when determining if a particular data point is appropriate to
use in the computation of grid node values.

Chapter 25 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Convergent Algorithm Overview

Blending Algorithm
Multiple weighted Z values assigned by several control points to the same grid
node are mathematically merged using a sophisticated blending function. The
function is based on the Taylor Series, which allows the prediction of a shape
at any point x by knowing the behavior of the shape at several points a.

( f ( a ) ) 2
f ( x ) = f ( a ) + f ( a ) ( x a ) + ----------------- ( x a )
2!

X is the grid node location, and a are the data point locations.

The Convergent process involves multiple iterations of interpolation,


smoothing and refining to achieve a trend like surface in extrapolation and an
accurate fit in the presence of data. It starts with course grid interval which
controls the extrapolation and ends with a fine grid interval approximating the
data density, therefore controlling the accuracy of the model.

Slope and curvature information is calculated on the first iteration and carried
from one iteration to the next.

There are certain options available during gridding:


Gridding inside of a polygon
Weighting the different control point sets
Providing dip and strike information along with the z-value in the
control points.

We will not explicitly discuss these options in class, but you can read about
them in the on-line Users Guide.
To help you see how the Convergent algorithm computes the final grid, the
following schematics of several iterations illustrate the process.

GeoFrame 4.0 Introduction to CPS-3 Chapter 25 - 3


Convergent Algorithm Overview Schlumberger

1 2 3

4 5 X 6

X
YINC

7 8 9

XINC = YINC = 2200m


XINC
Number of Nodes to snap to = 16 (max. possible)

Figure 28.1 Convergent gridding: first iteration

At the beginning of the first iteration, the grid is null, and all control points
will contribute, to some degree, to all grid node values. The effect of each data
point depends upon its distance to the grid node. At the end of the first
iteration, the grid is essentially a weighted average. Note that the amount of
overall extrapolation desired around the edge of the data can be controlled by
the Initial grid interval.

Chapter 25 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Convergent Algorithm Overview

1 2 3 4 5

6 7 8 X 9 10

11 12 13 X 14 15

X
16 X 17 18 19 20

X
YINC

21 22 23 24 25

XINC = YINC = 1100m


XINC
Number of Nodes to snap to = 8

Figure 28.1 Convergent gridding: second iteration

In this iteration, the grid starts with the refined values of the first iteration, and
the area affected by each control point has become smaller. For example, the 8
closest nodes for the upper left control point are 1, 2, 6, 7, 11, 12, 8, and 3.
Because the grid starts with existing values in this iteration, the assignment of
control point values now becomes the projection of control point values using
the slopes and curvature computed from the grid.

GeoFrame 4.0 Introduction to CPS-3 Chapter 25 - 5


Convergent Algorithm Overview Schlumberger

X
X

XINC = YINC = 550m


Number of Nodes to snap to = 4

Figure 28.1 Convergent gridding: third iteration

In this iteration, the grid begins with the refined values from the second
iteration, and the area affected by each control point has become even smaller.
Each control point in this iteration will change only the four nodes of the cell
in which it falls, but the overall trend in the grid is retained. The change and
readjustment of the four nodes continues as the projection of control point
values along the slopes and curvature computed from the grid.

Chapter 25 - 6 GeoFrame 4.0 Introduction to CPS-3


Chapter 26
Glossary of Mapping Terms

Overview
anisotropic: Having properties that differ according to the direction of
measurement. Least-Squares gridding allows for directional bias based on
user-defined trends.

Ex. If a region is known to have high porosity trends running northeast-


southwest, the user may wish to use anisotropic weighting when gridding.

area of interest (AOI): A rectangular geographic area in which CPS-3


models data, performs data and surface operations and displays 2-D graphics.
The AOI boundaries are defined by the minimum and maximum, X and Y
engineering coordinates. (See also engineering window.)

audit trail: When activated, the audit trail records all parameters and
operations used to create or modify data, grids, faults, polygons and maps.
The user can request an audit report for a specific set or all sets in the project.

azimuth: Direction used to specify dip direction or 3-D viewing angle.


Measured clockwise from north.

batch execution: The execution of a user-specified list of commands (macro)


as a background computer process without user intervention. This mode is
useful when immediate results are not necessary or when cup intensive
mapping tasks are to be run in offbeat computer load periods. This mode is
also used when hardcopy graphics are required.

bathymetric data: x,y,z data sets describing the depth of large bodies of
water

biharmonic filter: See smoothing.

blanking: A procedure for setting the value of selected grid nodes to a null
(indeterminate) value. Nodes are usually selected by enclosing them in
polygons.

GeoFrame 4.0 Introduction to CPS-3 Chapter 26 - 1


Glossary of Mapping Terms Schlumberger

bulls-eye: A contour pattern consisting of tightly spaced concentric circular


contours which stand out as an anomalous area on the map. This pattern is
generally the result of a bad data point, seismic misties, or data that varies
greatly, in relation to the contour interval, within a small distance.

cell: The base unit of the grid; bounded by four grid nodes. The dimensions of
a cell are defined by the x- and y-increment.

clipping: There are two types of clipping. 1.Surface clipping--Surface


operations can be used to ensure a surface is not greater than/less than a user
specified cutoff value. All areas of the surface greater than/less than the cutoff
will be set either to the cutoff value or to indeterminate. 2.Map clipping--CPS-
3 allows graphics to be deleted from an existing map set either inside or
outside user specified polygons.

color-shade contours: A user specified color palette is used to color the space
between contour intervals. A single color from the palette is used to paint the
area of the surface falling within a defined contour interval. Adjacent contour
intervals are painted with adjacent colors from the color palette.

column: Within a computed grid, all nodes with equal X locations, but
different Y locations comprises a single grid column

command: A single word entered at the command line to invoke a mapping


function or procedure. (See the CPS-3 Quick Reference Guide.)

conformal limiting: An option used during surface modeling (gridding,


surface operations) to control the z minimum and maximum of the created
surface. The surface limits can be controlled by either user defined constants
or surfaces.

container: A named collection of information in GeoFrame. For example, a


surface container holds various versions of gridded models for a specific
horizon and the fault traces which are associated with them; a data container
holds various versions of data points or scatter points for a particular
horizon.A container has no intrinsic data except as a holding tank for other
collections of information.

contours: There are two types of contours within CPS-3. 1.Normal contours--
lines on a map joining points of equal z-values (elevation). 2. Orthogonal
contours--These are generally drawn perpendicular to normal contours to
indicate direction of flow.

contour interval: The difference between z-values of adjacent normal


contours (see contours).

contour-to-grid: See gridding.

Chapter 26 - 2 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Glossary of Mapping Terms

control points: A point on a map represented as X,Y,Z1,Z2...Zn where X and


Y determine the location of the point on the map and Zn represents the value
of surface n at that point.

convergent gridding: See gridding.

coordinate system: A means of spatially locating X and Y data on a flat plane


such as a map. It may be a simple XY coordinate system in which the area has
been defined by a minimum to maximum X and Y values. If the data is
located by another means such as latitude and longitude, the X,Y axes must be
defined with those coordinates. Latitude/Longitude may transformed to other
coordinate systems via different projections (UTM, Lambert, etc).

cultural data: Any information, such as political boundaries, roads, rivers and
lease boundaries used as reference points on a map.

data transformation: Any function that can be performed on the data during
it's import/export into CPS-3. System functions include scaling, shifting the
origin, rotation, or converting from latitude/longitude to X,Y.

default (default value): A software supplied answer to a question posed by


the program. Most default values represent a typical situation. The default
value may be changed or left as is.

density gridding: See gridding.

deterministic data: Control points with very precise Z-values, such as well
data.

digitize: Method of directly entering new data into CPS-3 via a mouse
attached to a digitizing tablet or the screen.

digitizing tablet: A peripheral device for converting 2-D picture (hardcopy)


data such as cultural data, contours, or well locations into CPS-3 format.

dip: The amount of slope at a particular control point measured in degrees


from horizontal.

distance gridding: See gridding.

edge effect: Term used to describe undesirable gridding (contouring) results


beyond the edge of the data limits. This is due to erroneous extrapolation
outside the data limits; most often associated with least squares gridding.

engineering units: The units of measure contained within the users' data,
usually feet, meters, miles, or kilometers.

GeoFrame 4.0 Introduction to CPS-3 Chapter 26 - 3


Glossary of Mapping Terms Schlumberger

engineering window: A three dimensional geographic area in which CPS-3


models data, performs data and surface operations and displays graphics. The
boundaries are defined by the minimum and maximum X, Y and Z
engineering coordinates. The Z limits are used for 3-D graphic displays only.
(see also area of interest).

extrapolation: The process of projecting, extending, or expanding slope and


gradient information from known data into an unknown area. CPS-3 uses
extrapolation during the gridding process.

fault boundaries: These are equivalent to polygonal fault traces (see below).
In IESX, fault boundaries can be digitized directly, or initialized from the fault
contacts (see below).

fault contacts: Those points computed in IESX which are the actual or
projected intersection of an interpreted fault surface and a specific interpreted
horizon along a seismic line. Viewed in plan view, the fault contacts for a
particular horizon and fault approximate the fault boundaries which, in IESX,
can be derived from the contacts. Fault contacts in IESX can be identified by
horizon, by fault, and by upthrown or downthrown side. Typically, the fault
contacts are used as a guide to digitize or initialize the fault boundaries
(polygons).

fault cuts or fault segments: Seismic interpretation of a fault surface along


one or more seismic lines. The collection of fault cuts for a particular fault can
be used as data points to create a gridded model of the surface.

fault intersections: These are equivalent to fault boundaries, fault traces,


and fault polygons.

fault trace (fault): A line marking any discontinuity (abrupt change in


elevation or slope) in a surface model. Typically a fault trace marks the
intersection of a fault surface with the modelled surface as viewed from the
top. Fault traces are minimally defined by X,Y vertices. A more complete fault
definition can include elevation (Z) and vertical throw (T) in the format of
(X,Y,Z,T). Non-vertical faults are represented by closed polygons (fault
traces) and vertical faults are represented by lines.

field: Within an ASCII data file, a field contains one item of information in a
computer record (a record may have one or more fields). In multiple records, a
given field should always contain the same type of data. An example is a well
record in which one field stores the well name, an X-field contains latitude, a
Y field contains longitude and the Z-field contains a formation top.

Chapter 26 - 4 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Glossary of Mapping Terms

filter: There are two types of filters within CPS-3. 1.File filter--The graphical
interface allows the user to limit the file list when dealing with files external to
CPS-3. Ex. When importing ascii fault files into CPS-3, the user, by default, is
allowed to select the file from a list of all existing .flt files. If the users file has
a different extension (.dat), the filter can be changed to .dat. The user will
then be allowed to select the correct file. 2.Smoothing Filter--There are two
types of filters which may be used during the smoothing process: a. The
biharmonic filter is a converging filter requiring one or more passes through
the surface to converge on the final smoothed surface model. This filter
minimizes curvature without affecting local slopes. This is usually the
preferred filter and is always used during snap or convergent gridding. b. The
ring convolution filter is a non-converging filter that passes through the grid a
user-specified number of times to create the final smoothed surface model.
This filter reduces both slope and curvature. (see also smoothing).

fishnet isometric: A common method of representing a surface in three


dimensions. The user specifies an azimuth and elevation from which to view
the surface. The surface is represented by a grid lattice where grid nodes are
placed at their correct grid elevation revealing the peaks and valleys of the
model. There are two such types of 3-D displays. 1.No Hidden Line Removal
(Fishnet)--All segments of the grid lattice are displayed regardless of whether
they would be obscured from the users view because they fall behind other
features of the surface. 2.Hidden Line Removal (Isometric)--Grid lattice
segments which fall behind portions of the surface being displayed are not
displayed.

graphic displays: Two or three-dimensional map view representations of any


data, cultural information, faults, surfaces, etc.

grid: A model showing the distribution of a user defined attribute such as


depth, porosity or contaminant concentration. Often referred to as a surface.
The grid consists of a set of ordered Z (attribute)-values occurring at regular
intervals of rows and columns usually calculated from a set of user-defined
attributes at irregular X,Y locations. As a verb, grid is the process of creating
the model from the data (see also gridding).

grid blanking: See blanking.

grid cell: See cell.

grid column: See column.

grid increment: See increment.

grid node: See node.

grid refinement: See refine.

GeoFrame 4.0 Introduction to CPS-3 Chapter 26 - 5


Glossary of Mapping Terms Schlumberger

grid row: See row.

gridding: The basic computer mapping process for transforming user x,y,z
data into a regularly distributed x,y,z data set referred to as a grid. There are
several algorithms within CPS-3 for creating grids.

contour-to-grid--Modified convergent gridding algorithm used


for creating grids from digitized contour data.

convergent--Iterative gridding process which begins with a very


coarse grid increment which continually refines and reties data to
the grid until the final grid increment is reached. Excellent
algorithm for all common data type Minimizes edge effects
producing a model more closely resembling a hand drawn contour
map.

density--Grid node values are set to the number of valid control


points within the search limit radius.

distance--Grid node values are set to the distance between the


grid node and nearest control point.

isopach--Specialized gridding for data sets where a zero value


indicates the modelled attribute is not present at that location.
Commonly used for gridding isopach data. Uses a data
preprocessor to project a proper zero line and assign the
appropriate negative number to the zero data value before
gridding takes place. Can be used with both convergent and least
squares gridding techniques.

least squares--One of the oldest methods of computing grids. Can


be used for all types of data except digitized contours. Should not
be used where extrapolation across large areas is required due to
undesirable edge effects.Can use dip and azimuth information at
control points if available. Allows for anisotropic weighting of the
data.

moving average--Does not consider slope or curvature


information when creating the grid. Performs a weighted average
on data within the Search Limit Radius to calculate the grid node
value. Not recommended for most data types. Produces acceptable
results for point-source data or dispersion modelling

polynomial--Grids created from the function:


Z=C1+C2*X+C3*Y+C4*X^2+C5*X*Y+C6*Y^2+C7*X^3+C8*X^2*
Y+C9*X*Y^2+C10*Y^3

where C# is a user-specified constant. A constant value


grid is created by setting C1 to the constant value and C2-C10 to
0.

Chapter 26 - 6 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Glossary of Mapping Terms

gridding (continued)...

snap--A single iteration of convergent gridding. Data is tied to the


nodes of a new or existing surface. Excellent for quick look
gridding (especially 3-D seismic).Also used to tie an existing
surface to new or modified data.

step--Grid node values are set to the value of the closest control
point.

trend--Used to generate regional trend and residual maps. An


approximation of the data model which reveals gross features only
and hides local data variations.

horizon: A particular stratigraphic geologic sequence. In most instances this


may also be referred to as a grid or surface. FFMS uses the horizon name as a
key word for naming the surfaces and faults it calculates.

increment (interval): This is the basic measuring unit of a grid. It


corresponds to the X, Y dimensions of a grid cell and determines the
resolution of the map or model.

indeterminate value (INDT): A value used to indicate a null condition such


as the absence of data at a particular location. When assigned to a grid node,
the surface is undefined in that area. The abbreviation used by CPS-3 is INDT.
The value is internally stored as 1.0E+30.

interactive execution: The processing mode in which the software performs


operations immediately upon command of the user. Graphic output is
normally sent to a terminal for immediate viewing. This mode is sometimes
referred to as foreground execution. (see also batch execution).

interpolation: A process used during gridding to estimate values that lie


between two known values.

inverse interpolation: A process that back-interpolates a z-value from a grid


at a given xy location or cursor location as in the browse facility in the model
editor.

isochore: A surface which represents the true vertical thickness between two
other surfaces. Often the result of subtracting two surfaces.

isometric display: See fishnet isometric

GeoFrame 4.0 Introduction to CPS-3 Chapter 26 - 7


Glossary of Mapping Terms Schlumberger

isopach: Literally it is the true stratigraphic thickness between two other


surfaces. This surface is always greater than or equal to the isochore thickness.
CPS-3 does not calculate true isopach surfaces. However, many people use the
term isopach synonymously with isochore, particularly when the bed dip
angle is negligible.

isopleth: A grid representing the spatial distribution of some property or


attribute.

isotropic: Having equal properties in any direction of measurement. Most


gridding assumes isotropic properties. (see also anisotropic).

lattice: The wire-mesh figure created by drawing line segments through each
column and row in a grid.

least squares gridding: See gridding

macro: A text file consisting of one or more commands which perform one or
more mapping tasks. These can be built interactively using the macro build
command within CPS-3 and recording your commands or macros can be built
using the macro builder under the CPS-3 Application Manager.

map: The entire graphic image generated by CPS-3. Maps may be displayed
on the screen or sent to plotters for hardcopy output.

menu: A list of options presented to the user for selection. Menu choices may
invoke mapping functions or lead to other menus.

moving average gridding: See gridding

multiple surface operations: Algebraic or logical operations which can be


performed between two surfaces.

native commands: Low-level commands underlying CPS-3 that provide


access to the functions of the subroutine library. (see also parameter,
procedure)

node: The intersection points of the rows and columns of the grid lattice.
These are the locations of the calculated Z-attributes of the grid model.

normal contours: See contours

orthogonal contours: See contours

Chapter 26 - 8 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Glossary of Mapping Terms

parameter: User- or system-specified values that a procedure uses to perform


a task. For example, the native command FSGRID is a parameter specifying
the initial grid interval for gridding. The naming convention for CPS
parameters is as follows:

Fcxxxx--where F signifies this is a parameter, c identifies the category


(system, data, fault polygon, surface, map), and xxxx is a mnemonic
descriptor. (See also procedure.)

plotting units: The units of measure used to define the size of graphical items
posted on the plot or the size of the plot itself. The default units of measure
are inches but can be changed to centimeters.

plotting window: A rectangle which positions the engineering window on the


plotting device (screen or plotter). If a map scale is not set, displays will be
created to fit within the specified treated as a temporary work file or
permanent archive from session to session. It stores data, faults, surfaces,
maps. The project file will be obsolete from CPS-3 v4.0 onward.

projection: Used to convert data defining a three-dimensional body, such as a


sphere, into a two-dimensional drawing (a flat plane). In cartography, many
different projections exist to represent points on the earth in map view.
Example: Mercator, Transverse Mercator, Lambert Conformal Conic.

refine: The process of changing the X- and Y-increment of an existing grid to


a different (larger/smaller) X- and Y-increment by resampling the existing
grid.

report file: During each interactive CPS-3 mapping session a file called
project_name.rep is created. This file contains a summary of all the
commands and parameters used during that session.

response file: A text file that stores all the user responses made during
creation of a macro within the Macro Builder Module. The response file is
used to edit a macro previously created with the module. Response files have
an .rsp extension.

ring convolution filter: See filter.

row: Within a computed grid, all nodes with equal Y locations, but different
X-locations comprises a single grid row.

search limit (SLM): The length of the radius used to describe a circle which
contains all control point data used to calculate a value for a grid node at the
center of the circle. A search limit radius is used in least squares and moving
average gridding algorithms.

GeoFrame 4.0 Introduction to CPS-3 Chapter 26 - 9


Glossary of Mapping Terms Schlumberger

single surface operations: Algebraic or logical operations which can be


performed on an existing surface.

smoothing: A procedure performed on a surface (grid) to reduce the surface


curvature and produce a surface that is smooth and free of irregularities. There
are two types of filters which may be used by the smoothing process. (also see
filters).

snap gridding (snapping): See gridding.

statistical data: Control points with relatively imprecise Z-values, such as


magnetometer and seismic data. Statistical data is not meant to be honored as
strictly as deterministic data.

step gridding: See gridding.


strike: The direction of a line formed by the intersection of a fault with a
surface. In the CPS-3 FFMS module, by default, this is measured in degrees
positively counter-clockwise from north.

subroutine library: The core of the CPS-3 system. The library is comprised
of a set of highly organized subroutines for performing all of the mapping
functions available with the software.

surface: See grid.

surface strike: The direction normal to the dip of a surface. Normal contours
follow surface strike.

switch: See toggle switch

symbol code: A numeric code used by CPS-3 to post the appropriate symbol
at a particular location. Numbers 1-65 represent stroked symbols. The default
symbols and codes are shown in Appendix C of the CPS-3 User's manual.
Symbol numbers 1001 and greater are machine symbols and are posted much
quicker.

throw: The amount of vertical separation across a fault trace.

toggle (switch): To change the status of a parameter or other item from ON to


OFF or vice versa. CPS-3 provides a number of global parameters (also called
switches) that can be turned ON or OFF. Example. INDT is a switch which
when ON displays all graphic items. When it is OFF, only items with a valid
z-value are displayed.

transformation sequence: The order in which X,Y and/or Z values are


manipulated during CPS-3 input/output. (See data transformation.)

Chapter 26 - 10 GeoFrame 4.0 Introduction to CPS-3


Schlumberger Glossary of Mapping Terms

trend gridding: See gridding.

unconformity: A surface of erosion or non deposition that separates younger


strata from older rocks.

vertices: The x,y locations defining a polygon or fault.

viewport: See plotting window.

volumetric: The computations performed on one or more surfaces to compute


the volumes within an enclosed area.

X-increment: The length of a grid cell along the x-axis measured in


engineering units. The distance between grid columns.

Y-increment: The length of a grid cell along the y-axis measured in


engineering units. The distance between grid rows.

Z-value: Value of any attribute to be modeled at a specific location. Typical


attributes are depth, porosity and saturation values. Data points, grid nodes
and fault vertices can all contain z-values.

GeoFrame 4.0 Introduction to CPS-3 Chapter 26 - 11


Glossary of Mapping Terms Schlumberger

Chapter 26 - 12 GeoFrame 4.0 Introduction to CPS-3

You might also like