Introduction to CPS-3 - pudn.comread.pudn.com/downloads130/doc/556189/train/train/GF4_IntroCPS3... · Introduction to CPS-3 GeoFrame 4.031 November 6, ... Training Workflow ... Computing

GF4_CPS3_6Nov02.pdf www.geoquest.com

Introduction to CPS-3

GeoFrame 4.031

November 6, 2002

Copyright Notice

© 2002 Schlumberger. All rights reserved.

No part of this manual may be reproduced, stored in a retrieval system, ortranslated in any form or by any means, electronic or mechanical, includingphotocopying and recording, without the prior written permission ofGeoQuest, 5599 San Felipe, Suite 1700, Houston, TX 77056-2722.

Disclaimer

Use of this product is governed by the License Agreement. Schlumbergermakes no warranties, express, implied, or statutory, with respect to the productdescribed herein and disclaims without limitation any warranties ofmerchantability or fitness for a particular purpose. Schlumberger reserves theright to revise the information in this manual at any time without notice.

Trademark Information

GeoFrame™, CPS-3™ and certain other software applications mentioned inthis material are trademarks of Schlumberger.

All other products and product names are trademarks or registered trademarksof their respective companies or organizations.

Schlumberger Contents

9

tion

• • • • • •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-

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 Organiza3-3

GeoFrame 4 Introduction to CPS-3 iii

Contents Schlumberger

om

3

2

5

7

Exercise: Set GeoFrame Display Units to Metric, and VerifyCoordinate 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 frthe 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-1

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-

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-

Rules of the Road for Automatic Coordinate SystemConversion in CPS-3 Sets. . . . . . . . . . . . . . . . . . . . . . . . 5-5

Enhancements in CPS-3 for GeoFrame 4.0 . . . . . . . . . . . . . 5-

iv GeoFrame 4 Introduction to CPS-3


2

6

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-

Data Sets (.dcps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Fault Sets (.fcps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Polygon Sets (.pcps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

Surface Sets (.scps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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


nd

Coverage

Definition of Mapping Environment Components . . . . . . . . 9-3

Display Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Modeling Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

The Relationship between CPS-3 Modeling Environments aGeoFrame 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 Basemap9-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


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 andAssociated 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 Gridding11-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


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 PointArithmetic

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


ults

trics

7

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 theGrids, then Display Overlapping Areas . . . . . . . . . . . . 17-2

Conform the Ness Grid to the Tarbert Grid Where TheyOverlap

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4

Exercise: ExamineRelationshipsamongHorizonsandSealingFa17-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

RecommendedSequenceforComputinganIsochoreforVolume18-2

Location of the Zero Line in Isochores. . . . . . . . . . . . . 18-3

Accounting for Non-vertical Fault Discontinuities in theVolumetric Isochore . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5

Example of Creating a Structural Envelope . . . . . . . . . 18-6

Chapter 19 Prepare the Tarbert/Ness Envelopes and Create theGross 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Prepare the Fault Traces for the Gross Thickness Grid 1910

Chapter 20 Applying Reservoir Properties to the Gross_Isochore forOil 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


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


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


xii GeoFrame 4 Introduction to CPS-3

een

ds

ing,,

ns

Chapter 1

• • • • • •About this Course

Overview

This course is a comprehensive introduction to theCPS-3 software systemand designed forGeoFrame 4. The user learns about project preparation,internal data storage conventions, as well as the basics of data flows betwother applications such asIESX, Charisma, WellPix, andResSum.

This course has a specific workflow which begins with data import and enwith the computation of oil in place with theCPS-3Volumetric procedure. Inbetween, all basic mapping operations are exercised, including basemappgridding, contouring, profiling, surface operations, data operations, utilitiesmap editing, model editing, and more.

This course makes use of a fully populatedGeoFrame project to provide datafor the workflow. Some ASCII files are used as well.

The emphasis for this course is to provide a solid overview of the operatioinvolved in computer modeling and basemapping. Although this course isoriented toward beginning users, it is also recommended for those alreadyconversant with computer modeling who wish to learn the specifics ofCPS-3.

GeoFrame 4.0 Introduction to CPS-3 Chapter 1 - 1

About this Course Schlumberger

tic.

Course Objectives

After completing this course, you will be able to:

• Access data which has been created byGeoFrame, 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 datadistribution 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 arithme

• Generate structural envelopes.

• Fetch property averages fromGeoFrame and make property grids.

• Apply property grids to gross rock thickness and perform volumecalculations.

• Write, execute, and edit macros.

• Edit surfaces, faults, and data with theModel Editor.

• Create custom palettes with theColor Palette Editor.

• Perform simple map editing.

Chapter 1 - 2 GeoFrame 4.0 Introduction to CPS-3

Schlumberger About this Course

and

lt

ping

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 ofCPS-3. Learn to use asimple How_To table for menu navigation.

• Lesson 5 - Review conceptual changes inCPS-3 for GeoFrame 4integration; Learn about Environments

• Lesson 6 - Learn howCPS-3 internal data sets are organized

Getting data into CPS-3 and how to manage it

• Lesson 7 - Learn about accessingGeoFrame 4 data fromCPS-3; loadseismic and well location data.

• Lesson 8 - Learn to select, create, and manage sets inCPS-3

Looking at location data - load data and do simple basemapping

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

Loading horizon data - introduction to gridding procedures

• Lesson 10 - Load seismic horizon interpretation, well tops, and fausegments

• Lesson 11 - Learn about the fundamentals of gridding

• Lesson 12 - Apply gridding principles to GullFaks data, learn moreabout gridding parameters

• Lesson 13 - Establish modeling environment and grid the Gullfaksdata; learn the basics of contouring and display

More about basemapping, map composition

• Lesson 14 - Learn more about contouring, color-shading basemap

Control point operations

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



pes

,

Introduction to volumetric envelopes, properties, OIP

• Lesson 16 - Learn faulting conventions, create fault grids for envelo

• 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 grossisochore grid

• Lesson 20 - Fetch and grid property data; compute volumetric gridscompute OIP

Interactive Editors in CPS-3

• Lesson 21 - Introduction to interactive editing models inCPS-3 -Model Editor, Color Palette Editor, Map Editor

Miscellaneous T opics with no Ex ercises

• Lesson 22 - Introduction toMacros

• Lesson 23 -Graphic Operations in CPS-3

• Lesson 24 - Learn how to format data for theCPS-3 Ascii Loader

• Lesson 25 - A brief overview of theConvergent gridding algorithm

• Lesson 26 - Aglossary of mapping terminology



ions

How to Use the Training Guide

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

Common Commands

The following table describes the most common commands you willencounter throughout the exercise and training guides..

Command Generally Refers to Action Required Example

Click Buttons or objects in awindow or dialog box

Position the cursor over thebutton or object and click theleft mouse button once.

Click Start .

Right click Right Mouse Button(MB3)

Position the mouse cursorover a button or other area ofa window, and click the rightmouse button.

Right click the Fieldicon to open theInsert Structuredialog box.

Double-click Items in a window ordialog box

Position the cursor over theitem and click the left mousebutton twice rapidly.

Double-click thelocation name toopen the LocationEditor.

Drag Cursor 1. Position the mousecursor over a specifiedarea of a window.

2. Press and hold the leftmouse button.

3. Drag the cursor toanother area of thewindow.

Drag the cursor from7000 to 7500 feet.

Enter Text fields 1. Position the cursor overthe text field.

2. Click the left mousebutton once to activatethe field.

3. Type the desired text.

Enter the itemnumber.

Open Windows and dialogboxes

Select the appropriate menuoption or click the appropriatebutton or object to display thedesignated window.

Open the Printwindow.

Press Keys on the physicalkeyboard

Press the designated key. Press F9.



Select Menus and menuitems in a window

1. Position the cursor overthe menu.

2. Click the left mousebutton once. A drop listappears.

3. Move the cursor to thedesired menu item.

4. Click the left mousebutton once.

Select File > New .

Select Drop lists 1. Position the cursor overthe arrow to the left of thedrop list field.

2. Click the left mousebutton once on the arrowto display the drop listitems.

3. Move the cursor over theitem to be selected. Clickthe left mouse buttononce to select the item.

Select a location fromthe drop list.

Type Entries Text fields(An entry to be typedappears in boldcourier font).

1. Position the cursor overthe text field.

2. Click the left mousebutton once to activatethe field.

3. Type the desired text.

1. Type the pathand file name inthe Databasefield.

2. Enter MARG forFormation top .

3. Type SECTION 1in the Name field.

Command Generally Refers to Action Required Example



ut

Typographic Conventions

The following table lists the special formatting you will encounter throughothe training and exercise guides.

Item Shown As Description Example

ImportantInformation

Italic text Highlights importantinformation within thetext

Always enter the datein the format MM-DD-YY.

Typed Entries Bold text, courier font Indicates the specificinformation you musttype into a field orcommand line

Type 112298 in theDate field.

Buttons, menuand menuitem names,keyboard keys

Bold text Highlights items on thewindow or buttons onthe keyboard with whichyou must interact

1. Click OK .

2. Select File > New.

3. Press Tab.

Mousecommandand/or keycombinations

Keyboard key name(s)and/or mousecommand separatedby a hyphen

Indicates thecombination ofkeyboard keys or mouseaction and keyboard keyyou must perform

1. Press <Alt><F4> .

2. Control-clickWELL-O andWELL-K .

Menus andMenu Items

Menu names andmenu item name(s)separated by an arrow(>)

Indicates the sequenceof menu names andmenu item(s) the usermust select

Select XSection >Create in the Prospectwindow.

File names,SystemMessages andScreen Text

Bold text, Courier font Highlights systemmessages or text thatappears in a window

1. If you receive theerror Databasenot found ,contact the systemadministrator.

2. Exported files arestored in a userspecified directorywith a userspecified nameand a .pbfextension(PowerPlanBackup File).

SystemMessages/Screen Text

Bold text, Courier font Highlights systemmessages or text thatappears on a window

If you receive the errorDatabase notfound , contact thesystem administrator.



Caution Text displayed in ahighlighted boxpreceded by the wordCaution.

A statement to proceedcautiously and avoidconditions that, ifunheeded, mayadversely affect aprocedure function ordata. Less severe thanWarning

Caution: Take care inapplying spatiallyvarying static mistiesbecause they can causefalse structures toappear in the seismicsection.

Warning Text displayed in ahighlighted boxpreceded by the wordWarning .

A statement ofinformation to avoidconditions that, ifunheeded, willadversely affect aprocedure, function, ordata. More severe thanCaution

Warning: You mustenter an end date that islater than the start dateto correctly calculate theduration.

Note Italic font, preceded bythe Illustrated graphicsymbol and the wordNote

Provides supplementalinformation

Note: ClickingListSummary displays onlythe item names.

Tip Italic font, preceded bythe Illustrated graphicsymbol and the wordTip

Provides helpfulsuggestions. Often usedin Exercises. Tip: If the user can’t tell

the difference betweenshading on or off, zoomin to see the seismicmore clearly.

Best Practice Italic font, preceded bythe Illustrated graphicsymbol and the wordsBest Practice

Provides guide toefficient work flow.

Best Practice:Thebasemap will look lesscluttered if only one zoneper layer is posted.

Buttons,Dialog boxand Windowtitles, FieldNames, andmenu options.

Noted in bold type. Highlights specificwindow and field names

Click OK.Open the Createdialog box.Select the Edit option.

Item Shown As Description Example

• • • • •

• • • • •

• • • • • •

• • • • • •

• • • • • •



and

er.

ins to

Procedures and Exercises

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

Procedures

Procedures appear in a procedure table as shown below. Notice thatprocedures contain general steps and do not contain data to select or ent

Exercises

Exercises are introduced by a description of the steps to follow, as shownthe example below. The steps appear in a numbered list of specific actiontake and data for you to select or enter.

ExerciseExercise

Create a cross section

1. SelectXSection > Create in the Prospect window.

2. TypeSECTION 1 in theName field.

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



d is

ng

Standard Buttons

Use command bar buttons to inform the system that an action or commancomplete. 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 saviany information

• Default — restores the settings/information in the dialog box to thesystem default

• Cancel — cancels any unsaved changes and closes dialog box

• Close — closes dialog box

• Help — displays help on the currently-active dialog box.


es

se,

Chapter 2Training Data - Inventory and

• • • • • •Description

Overview

In this chapter, we’ll make an inventory of data in theGeoFrame GullFaksproject which is used by this class.

The GullFaks field is well-documented and information on this field isavailable via the Schlumberger intranet.

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

• 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 bothseismic and well data are available in time and depth. In this training courwe will usedepth data.


Training Data - Inventory and Description Schlumberger

tof

nkrittthe

on,

Naming Conventions

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

Volumetrics Notes

In this class, we will compute volume between the Tarbert and the Nesshorizons. Because of large erosion zones in the Tarbert caused by the Buunconformity, the top of the reservoir must be a merging of the Tarbert andunconformity.

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 additisome of the data will come from outside of the project. Regardless of itsorigin, the next section provides an inventory of the data sets which will beused in CPS-3 for this course.

Table 2.1- Seismic Horizon Data and Geological Marker Names

GeologicalMarker inGeoFrame

Seismic Horizonin IESX

CPSHorizonName

FaultPoly

Interpretation Density /Description

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)


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



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



• F15

• F15a

• F16

• F17

• F18

• F19

• F20

• F21

Fault Segments (Depth)

• mm_F2_Depth_fsegs

• mm_F2a_Depth_fsegs


















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



Project Coordinate System InformationDatum: European 1950, Norway and Finland

Ellipsoid: International 1924

Projection: UTM, Zone 31, CM = 3.0

Hemisphere: Northern

Project Units

Metric

Project LocationNorth Sea

Figure 2.1 GullFaks Fault Patterns and 3D survey



tion

ordrant

D

hehe

but

Above, you can seefault patterns over the area as well as the limits of the3Dsurvey in black. Two platforms are the source of manywell trajectoriesshown in red. The white dotted rectangle shows the approximate interpretacoverage of the highest of the horizons - theTarbert . Subsequently lowerhorizons will cover more and more area towards the East. Well coverage fthe higher horizons such as the Tarbert are restricted to the lower SE quaof the dotted rectangle

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

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

.

Figure 2.2 Well paths, Bunkritt interpretation, and Tarbert interpretation



wn

Selected Fault Patterns

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



es

ists

Reservoir Geometry

The area of the GullFaks field which we will be mapping consists of a seriof tilted fault blocks with several of the upper horizons of the group, forexample, the Tarbert, containing erosion zones where no interpretation exabove the Bunnkritt unconformity.

Figure 2.3 Reservoir profile displaying the stratigraphic relationship of thehorizons

.

Bunkritt

Tarbert

Ness


Chapter 3Introduction to the GullFaks GeoFrame

• • • • • •Project

OverView

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


Introduction to the GullFaks GeoFrame Project Schlumberger

it.

ExerciseExercise

Start up GeoFrame and Prepare the Project

In this exercise, we will introduce you to theGullFaks project and follow thisbasic workflow:

• StartGeoFrame from theGeonet menus and enter the name of theproject which the instructor will specify.

• Invoke theGeneral Data Manager to review the organization of theexisting data.

• Review the coordinate system chosen for the project and set theGeoFrame display units for Z to milliseconds.

• InvokeIESX Basemapping andSeis2D/3D to view the interpretedhorizons and fault segments which will be imported intoCPS-3.

• InvokeCPS-3. Clear out the internal storage area.

• Load external data required for this course.

Startup the GullFaks Project

1. Click GeoFrame 4in theGeonetmenu, and hold down theleft mousebutton (MB1).

2. Continue holding downMB1, slide the cursor toGeoFrame andrelease the button.

3. From your instructor, determine thename of the project you require,and when theGeoFrame Loginwindow appears, highlight the desiredproject in the project list, move the cursor to thePassword box andclick themiddle mouse button (MB2), and then clickConnect (withMB1).

4. When theApplication Manager (icon at the bottom of theProjectManager window) becomes active – no longer grayed-out, click on


Schlumberger Introduction to the GullFaks GeoFrame Project

Enter General Data Manager to Inspect DatabaseOrganization

In this exercise, it is very important that you do notDELETE any item orobject as you view the contents of your project.

1. In theApplication Manager dialog box, underManagers, click theData icon to open theData Management Catalogwindow.

2. From theData Management Catalog, click onData Managers, thendouble-click onGeneral.

3. When theData Manager comes up, place the cursor on theprojecticon.

Figure 3.1 Project icon located in Data Manager window

4. Hold down the right mouse button (MB3), moving toExpand ByType, thenHorizon and release the button. (See figure below.)



the

Figure 3.2 Expanded project node displaying partial horizon list

5. Place the cursor on one of the horizons, such asDRAKE , and pressMB1 to select it, then with the cursor still onDRAKE , pressMB3.

6. Continue holding downMB3, move over toExpand by Type, then toGrid and release the button. This reveals all grids associated with DRAKE horizon, orcontainer.



Each of the Horizon containers may have been created by any one of thenumerousGeoFrameapplications -IESX or Charisma during interpretation,Stratlog or WellPix during geological interpretation, orCPS-3 duringmapping.

Below, we see the resultinghierarchical relationship when we expand theproject 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 theData Management Catalog, clickCancel.



ExerciseExercise

Set GeoFrame Display Units to Metric, and VerifyCoordinate System

1. In theProject Management folder of theProject Managementdialog box (Figure 3.4), clickEdit to open theProject Parametersdialog box.

Figure 3.4 Project Manager displaying the Project Management folder



Figure 3.5 Unit/Coordinate System menu

2. In theProject Parameter dialog box, underUnit/CoordinateSystem, click theDisplay tab, and clickSet Units. This opens theSetUnits dialog box, shown below.

Figure 3.6 Set Units dialog box

3. In theSet Units dialog box, pick theUnit classification nameMetric/Charisma , or Metric if the first is not available, and clickInspect. This opens theUnit Systemdialog box, shown below.

Figure 3.7 Dialog boxes to set measurement of project data



lue

4. Scroll down toGeographic Distance, under theMeasurementcolumn, and verify that its unit ism (representing meters). If not, clickthe button under theUnit column, changing the units tom, which isfound toward the bottom of theAvailable Units dialog box. ClickOK

5. Verify also thatLength is m (meters), as well asStandard DepthIndex. If not, change the measurement as you did above.

6. Back in theUnit Systemdialog box,Cancel if no changeswere made,or click Save As and type in a new unit system name suffix,ms, andclick OK .

Review the Coordinate System for the Project

1. From theEdit Project Parameters dialog box, click theDisplay tabunderUnit/Coordinate Systemagain, and clickSet Projectionon theright.

2. Highlight any Coordinate System seen in the dialog and click the b“i” icon to see its definition. You want to select any of the coordinatesystems 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.



Figure 3.8 View Coordinate System dialog box

3. Click Cancelback to theProject Management dialog box which youmay then iconize. We will be using it again.



d in

the

ofe

ot

ExerciseExercise

Review Interpretation - Optional

The next exercise is for those of you who want to look at the interpretedhorizons, fault boundaries, and fault segments which have been interpreteIESX or Charisma which will be mapped in this course. You may skip thisbrief exercise if you wish. The intent is only to demonstrate the source of data which we will access fromCPS-3 in the next few chapters. Those of youwho areIESX or Charisma users can take a moment to verify the presencethe horizons and other data outlined in the previous chapter describing thGullFaks project.

• • • • • •

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



ExerciseExercise

Execute CPS-3 and Remove all Data Components fromthe CPS-3 DSL

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

1. Bring up theVisualization Catalog from theGeoFrame ApplicationManager, and clickCPS-3 to reveal theMain Modul e application.

2. Highlight theMain Module application by clicking on it once.

3. Lower down, on theDisplay line, verify which workstation you wantthe application to run on - “0.1” isright and “0.0” isleft. After typingin the desired location, clickOK . This should bring up theMainModule canvas:

Figure 3.9 CPS-3 Main Module



3

,

d by

s

II

4. Starting at the top menu bar in theCPS-3 Main Module, clickUtilities > 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 todelete any sets from the GeoFrame data base.

6. Toggle on “All” in theSet Type, Surface Type, andProperty boxes,changing them to red. Toggle only “CPS” in theStorage box

7. Click theFilter button at the bottom and VERIFY THATONLY“CPS3” IS TOGGLED ON WITHIN THESTORAGE BOX.

S T O P T O M A K E S U R E T H A T T H E R I G H TP A N E L S H O W S O N L Y S E T S I N “C P S “. I FS E T S I N G E O F R A M E S H O W U P , G O B A C KT O S T E P 4.

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

6. Back in the left side of the dialog in the Storage panel, click on “All”then click “Filter”. We should only seeGeoFrame sets in the list, ifanything. These are grids, fault boundaries, and other items createother applications.

7. Close theList Manage Setsdialog box.

Import Supplementary Data Files

At this point, we will load some external data files which will be used in thicourse. These are files which are not part of theGullFaks project, but arenecessary for training purposes, such as auxiliary data files, macros, ASCfiles, 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 onSelect Coordinate System and in the next dialog box,highlight the proper coordinate system which we verified earlier asbeing the correct one for this project, and clickOK .

3. Click on theby Directory toggle near the bottom.



ill

h

ch

e

4. Type or swipe the fully qualified pathname given to you by theinstructor. (This path is the location of the external data which you wload into yourCPS-3 DSL.)

5. Make sure that the last character in the pathname is a forward slas“ /”, 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 Yesto all messages which appear, but note the files whiare being loaded in theCPS Status Window.

8. Close theMultiple Set Selector dialog box which appears.

9. In the CPS-3 Main Module,go toUtilities > Sets > List/ManageSets.

You should now see several sets which were not visible earlier, andwhoseStorageis CPS. These are the files we just loaded in theCPS-3DSL. Refer to next figure.

Depending on the status of your particular project, you may also seotherGeoFrame files interspersed with the “mm” files just loaded



dingtem

.

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

Setting Plotter Units

In earlier versions ofCPS-3, plotter units were defined before execution timeby the use of an environment variable in the GeoFrame .login file calledCPS3MUNIT, 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 regarcharacter sizes, symbol sizes, scaling, and so forth, will be in the units sysas specified forGeographic Distancein theGeoFrame Display Units tab. IftheGeographic Distance units are set toMeters, then the character sizes inCPS-3 will be specified incentimeters. If theGeographic Distance isdefined in feet, theCPS-3 plotter units will be ininches.



le
The recommendation is to establish your desiredDisplay Units settings asearly as possible. Switching from meters to feet (or visa-versa) in the middof a session or in a mature project can be difficult. In this Gullfaks-basedtraining course, we will usemetric units.



p

ions

Chapter 4CPS-3 Menu Organization and

• • • • • •Capabilities Overview

Overview

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

The full capability ofCPS-3is divided among the following independentmodules 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 theMainModule:

• Control Point Editor - interactive spreadsheet editor forData sets

• Subset Reorganizer - a fault management tool

• Map Layer Manager - a tool for reorganizing graphic layers of a ma

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


CPS-3 Menu Organization and Capabilities Overview Schlumberger

ns

lay.

en

ate

CPS-3 Main Module

TheMain Module is where most of the traditional modeling and mappingtools are located, and where you will probably spend most of your time inCPS-3. In the previous chapter, we learned how to invoke theMain Modulefrom either a stand-alone or aGeoFrame 3.0-or-later installation. In thischapter, we will learn many things about the environment of theMainModule - its conventions, resources, organization, and concepts.

Main Module Dialog Box

The figure on the opposite page displays the currentMain Module graphicdialog box. Note the following features emphasized in the figure.

• Pull-Down Menus:

All CPS-3 functionality can be accessed through these pull-downcascading menus.

• Icons:

For more convenient access to commonly used functions, these icocan be a shortcut instead of traversing the menu tree.

• Icon Descriptions:

As the cursor is moved over the icons, a description of each ispresented here.

• Scroll Bars:

When zoomed in, use these slider bars for panning across the disp

• Display Environment Box:

Every display environment you define inCPS-3contains the definitionof an x, y, z box called theVolume of Interest (VOI ). What is shownhere is simply the x, y portion of the box. The system attempts tomaximize the amount of canvas space allocated to your currentlyactive x, y box.

• Canvas:

This is simply the total potential screen area (or paper plot area, whplotting) where the x, y box can be located. The lower left corner ofthe canvas represents the origin(0,0) for the internal graphic coordinsystem in inches or centimeters.


Schlumberger CPS-3 Menu Organization and Capabilities Overview

Figure 4.1 CPS-3 Main Module

Pull-Down Menus

CanvasDisplay Environment BoxScroll BarsIcon DescriptionsIcons



ker

X,Y Tracker Display

When moving the graphic cursor during zooming, the x,y location of thecursor is echoed at the bottom of theMain Module dialog box as shown inthe following figure. The position is echoed in bothengineering units andplotter (viewport) units.

The x,y tracking also occurs during screen digitizing initiated from theDigitize 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 tracicon:

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



Measuring Tool

The measure distance icon in the following figure provides facilities formeasuring distances and angles on the graphic display.

Figure 4.4 Measure distance icon

Figure 4.5 Determining distance using the Measure distance icon



re,

Main Module Status Window

The figure on the next page provides an example of the Main Module statuswindow, 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, andMap). This particular example showsone activeData set. Note that the table scrolls downward and hasroom for up to seven active sets per type.

• Currently open Surfaces:

In this example, there is one openSurface set.

• Native Command Entry:

By clicking the cursor in this box, you can type native commands heas an alternative to menu or icon selection.

• Online status report dialog:

This window displays a real-time status report of all operations youperform during theCPS-3session. This information is also written to afile called

<username>.rep

where<username> is yourlogin id. This file is overwritten each timeyou start anotherCPS-3 session.

• Swap Screens Icon:

TheCPS-3 Status Informationwindow can be instantly moved fromthe current screen to the opposite screen by simply toggling theSwapScreens icon in the upper right of the display.



Figure 4.6 Main Module displaying CPS-3 Status Information window

Currently open Data set Currently open Surfaces

Native Command Entry Online status report dialog

SwapScreensIcon



rehat

UNIX Environment

In the Main Module go toUser > Show Environmentto bring up the CPS-3Environment window. This window can remain visible while you performother mapping operations. It’s purpose is to provide you with informationabout where CPS-3 is installed, and where the configurable resource files alocated. It also serves to remind you of the path to your open project, so tcopying of configuration files into your project area from an xterm issimplified.

Figure 4.7 CPS-3 Environment window



the

CPS-3 Map Editor

TheMap Editor in the following figure is a graphic editing tool used aftercreating theMap Set in theCPS-3 Main Module. Users can edit attributessuch as colors and fonts. Overposting can be cleaned up interactively.Symbols and text can be added. Composite maps can also be created in Map Editor .

Figure 4.8 CPS-3 Map Editor



yging

CPS-3 Model Editor

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

After each edit, the model is regridded and saved upon completion of theediting. The final model (grid) is then brought back into theCPS-3 MainModule.

Figure 4.9 CPS-3 Model Editor



rst, or

ory.

CPS-3 Color Palette Editor

TheColor Palette Editor in the following figure allows users to define theirown color palettes to use when drawing color shaded contour maps. Colocan be associated with a specific z-value. Each individual color can be sethe system will interpolate between two colors set by the user. The colorpalettes are then saved to a color palette name in the user’s project directThese palettes can be accessed in theMain Module when specifyingparameters for displaying color shaded contours.

Figure 4.10 CPS-3 Color Palette Editor



isphic

anf

CPS-3 Control Point Data Editor

In theCPS-3 Main Module, go to Utilities > Sets > Edit Data Set to accessthe spreadsheet-formatted data editor which is shown below. This featurevery useful for removing z-fields, changing subset names, and editing grasymbology 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 asExtended data set with three z-fields, a well name, and symbol code - all owhich are available for editing.

TheHelp text for this dialog is very useful.

Figure 4.11 Main Module displaying spreadsheet-formatted data editor



two

we

CPS-3 Set-Subset Reorganizer

This utility performs data management functions among variousCPS-3 settypes, reordering information from one domain into useful information inanother. For example, assume that you mapped three surfaces, each withmajor fault polygons having z-values attached. The three fault polygonsmigrate in x and y as they move downdip in each of the horizons. If you nowanted to create gridded surfaces for the two faults, it would be impossiblwith 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 areindicated by separate fill patterns.

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



es

ctedor a

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

TheSet/Subset Reorganizer will perform this reordering for you. As thedifferent shades of gray in the first diagram above indicate, x,y,z fault tracare grouped inFault sets, one per horizon. In theSet/Subset Reorganizerdialog box, select theFault sets for all horizons which contain valid x,y,zpoints to use in the gridding of the fault surfaces. From each of those selefault sets, you can choose any or all of its subsets (individual fault traces fsingle 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 aData set asshown below. There will be as many outputData sets as there are uniquesubset names (fault names) in the selectedFault sets. Each of the outputDatasets can then be gridded to obtain a model of the fault surface.

TheHelp text for the Set/Select Reorganizer is very informative.



Figure 4.14 Set/Subset Reorganizer



adede

CPS-3 Map Layer Manager

TheMap Layer Manager (Figure 2.15) is an extremely useful tool forreordering the subsets stored in a map set. It is often the case that color shcontours (Figure 2.16) obliterate other map elements simply because of thorder in which they were displayed on the screen. TheMap Layer Managerwill allow you to reposition map layers (subsets) to optimize your graphicoutput without having to regenerate the graphics on the screen.

Figure 4.15 Map Layer Manager



the

In this example, the picture below and on your screen was generated withseparate graphic commands; then theMap Layer Manager (Figure 2.15) wasinvoked with theManipulate 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 map, then invoke theMap Layer Manager.

Layers can be temporarily turnedon or off. Layers may also be deleted. Aswith otherCPS-3 dialogs, theHelp text for this facility is very useful.



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 User’s 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/



d

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 anselected

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 -



• 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



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



Icon Definitions

Stop current process

Zoom in

Reveal all graphics

Unzoom to last zoom

DisplayEnv from Zoom

Select/edit environment

Set map scale

Undo last graphic display

Erase the screen

Refresh display

Basemap menu

Contour

Map layers

Save display as mapset

Record a macro

Stop recording macro

Execute a macro

Unlock a set

View set statistics

Subset utilities

List/Manage sets

Get x,y coordinates

Measure distance/angle

Quick map

Single surface gridding

2D Profiles

Borehole intersections

Volumetrics

Model editor

Color palette editor

Customize icon bar

Hide icons

GeoFrame Link

GF grid data manager

GF grid library data manager


ere

Chapter 5

• • • • • •CPS-3/GeoFrame Integration

Overview

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

In GF4.0, CPS-3 still maintains its own local data store, that subdirectoryknown 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 thGeoFrame data link, GFLink. It is up to the user whether individual sets astored in GeoFrame, or in the CPS-3 DSL.


CPS-3/GeoFrame Integration Schlumberger

hee

t

of

CPS Local Data Store (dsl) and GeoFrame Storage

Historically,CPS-3 has used an internal data management system called tStorage Manager. This internal data store will eventually be replaced by thGeoFrame Oracle data base, but inGeoFrame, theCPS-3 internal storagefacility is still in place. Even so, there are someCPS-3 sets which may, at theuser’s option, be stored in theGeoFrame data base at the time of theircreation. In particular,

• Data sets may be stored inGeoFrame as scatter sets, however, subseorganization is lost.

• Fault sets may be stored inGeoFrame with subset (fault name)organization maintained.

• Surfaces sets may be stored inGeoFrame with the fault setassociation 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 anyCPS-3 set is created, the menus give you the choicestoring the data in either theCPS local data store or inGeoFrame.

• During Set Selection:

At the time any existingCPS-3 set is being selected, the menus showyou the current storage location of all available sets (CPS local datastore orGeoFrame), and allow you to select from either location.

GeoFrame data items are synonymous with CPS-3 sets, but data items storedin GeoFrame must now also be identified with the following attributes:

• Container name

• Container type

• Property code

• Unit of measurement


Schlumberger CPS-3/GeoFrame Integration

eLink

PS-3

s

s

.

s

is.01.

le

Accessing Data in GeoFrame and IESX - Data Links andMenus

Binary Data Links for CPS-3

The previous IESX and CHARISMA Links for Seismic Locations andInterpretation are no longer necessary for CPS-3, since seismic data,navigation data, and interpretation are now stored directly in the GeoFramdata base and can be accessed by CPS-3 in other ways. The GeoFrame (GFLink ), on the other hand, is still required, and has been expanded andimproved 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 Cin GF4.0:

2D survey location dataare now accessed via theGFLink and can be postedwith the existing Extended data seismic line posting feature.

3D survey location data is accessed and displayed via theDisplay menu. Anew 3D seismic line posting feature is available.

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

Fault Segment Interpretation is accessed as Fault Cut Sets fromGFLink .

Fault Boundary Interpretation is seen in the CPS-3 file selection dialogs afault boundary sets in GeoFrame, just as before.

Fault Contact Interpretation is seen in the CPS-3 file selection dialogs asscatter Data sets in GeoFrame.

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

Well location data, such as top location, bottom hole locations, and borehotrajectories are accessed from theGFLink, just as before.



ble

Yed

Well markers for specific Horizons are accessed from theGFLink, just asbefore.

Property summations for specific Zones are accessed from theGFLink , justas before.

Tip Loops created by Framework 3D are stored in GeoFrame, but are visifrom CPS-3 asPolygons.

All other GeoFrame surfaces, scatter sets, andfault boundaries can be seendirectly in the CPS-3 file selection dialogs, and, if necessary, can be COPto the CPS-3 dsl, just as before.

Geoshare Links for Cartography

Although aCPS-3 Geosharesender and receiver have been more or lessunavailable inGF3.5 throughGF3.8, a facility exists inGF3.8 to import.rp66and.gf66 files which have been created byFinder, and contain cartographicinformation. Use theFile > Import > Geoshare Culture menu path to thisfacility.

The new menu itemFile/Import_IESX_Cartography is now available andsupersedes the previous IESX Link.



ult

ns later

tef

y

use

Geographic Coordinate Systems

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

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

If two sets are associated with different coordinate systems,CPS-3willautomatically perform the numerical conversions required during operatiowhich use both sets. Specific rules for these conversions are covered in achapter.

• • • • • •

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

Rules of the Road for Automatic Coordinate SystemConversion in CPS-3 Sets

Every set inCPS-3is now associated with a particular coordinate system bvirtue of its assignedDisplay or Modeling environment under which it iscreated. Here are the basic rules governing how coordinate systems areinitiated or modified under certain common conditions.

• • • • • •

Best Practice: Unless your project requires something different, the recommendation is toonecoordinate system for all sets in your project.

Note that onlycoordinate systems (which includesrotation ) areautomatically converted inCPS-3. There are no ad hoc facilities forconversion of eitherunits (feet, meters,...), ordomain (time, depth,...).



uch

akes

em

lly

• Surfaces:

In practice, surfaces cannot be transformed from one coordinatesystem to another. However, graphic manifestations of a surface, sas contours or postings of nodes, can be transformed.

• Reading ASCII data in geographic coordinates:

Data with geographic coordinates (degrees, minutes, seconds, ordecimal degrees) will be transformed using the currently activeDisplay environment.

• Reading ASCII data in x, y coordinates:

In this instance, no conversion takes place. The data being loaded ton the stamp of the activeDisplay environment.

• Surface Arithmetic and Surface Operations:

The environments of all surfaces in the operation must match thecurrentModeling environment.

• Gridding :

During gridding, control points and fault traces are transformed tomatch the coordinate system of the activeModeling environment.

• Graphic Display:

Any set displayed will be transformed to match the coordinate systof the currently activeDisplay environment.

• Data Links such as GFLink:

Any data moved into CPS-3 via these data links will be automaticatransformed to match the coordinate system of the currently activeDisplay environment. Note thatunits anddomain of the output set isestablished by theGeoFrame Display Units, not the currently activeCPS-3 Display environment.



on

Enhancements in CPS-3 for GeoFrame 4.0

In this technical note, we’ll outline the enhancements added to CPS-3 inGeoFrame 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 ModelingOffice

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 sessi

4 New modeling feature in Single Surface gridding allows conformalmodeling

• 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 dataset

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

6 New versions of MSEDIT, MSPEEK, and MSPOKE are available andsupport rotated grids

7 Grid operations with automatic lattice matching to currentmodeling environment

8 New icon added to create display environment from current zoomwindow (GF3.8.1)

9 Macro facilities enhanced



• 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 adddescriptions to macros which are visible during macro selection

• define and assign macrocategories 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



thebe

e the

Examples of Macro Enhancements

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

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

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



.

s to

cros

The example menu below shows that you may have three basic sources forcollections of macros asystem-wide collection, aproject-related collection, andany number of “user” collections which can be identified simply by a path name

In this menu, theproject-based collection of macros has been selected and itsmacros listed. One of them has been highlighted which causes its internaldescription lines to be displayed.

The next figure shown an example of a “macro_index.txt” file, whose purpose isubdivide a collection of macros intocategories. In this example, each category isdefined with a “CATEGORY:” keyword followed by the user-supplied categoryname. Following this, all macros belonging to that category are listed. The maand the “macro_index.txt” file must be in the same directory.



ll
In this example, theSystem macro group has been chosen, and the names of amacros in the “Display”category have been displayed for selection.



S-3

Chapter 6

• • • • • •Understanding CPS-3 Set Types

Overview

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

Please refer to a previous lesson which discusses the integration statusbetweenCPS-3 andGeoFrame.

A Typical CPS partition in a GeoFrame Project

TheCPS 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/projectsis determined bytheowner of the projectCLOUDSPIN.

The remainder of the path /CLOUDSPIN/CPS is determined byGeoFrame.

In this example, the full path shown above defines the location of theCPSlocal data store, or partition, within theGeoFrame projectCloudspin. In thisdirectory, you will find everything which is managed by theCPS ProjectManager.

As mentioned in the previous lesson aboutGeoFrame integration, it ispossible in this release to optionally store someCPS-3 sets in theGeoFramedata base, which is separate from this partition.


Understanding CPS-3 Set Types Schlumberger

sgch

dataa.

ata

Ultimately, the data to which you have access inCPS-3 will be stored in oneor more of the file types outlined below. These files will reside in your CPSdsl. Note that each is distinguished by itsUNIX file extension which is notseen in theCPS-3 menus or dialogs.

• .1cpsfiles -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

• .mcpsfiles -map files; picture files

• .tcps files -table files such as created byFramework3D

Data, Fault, andSurface sets may optionally be stored in either the localproject files, as shown above, or in theGeoFrame Oracle data base, or both.

EachCPS-3 set can consist of one or more namedsubsets.

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 parameteryou set during yourCPS-3session. This includes definitions of your modelinand mapping environments. You will also see session files created for batprocesses you initiate fromCPS-3. Each will have a unique file name.

Data Sets (.dcps)

Description

Data sets contain information which is to be gridded or displayed, such aspoints. Examples are well markers, seismic interpretation, and scatter dat

Data Types

CPS-3 uses a data set’sData Type to compute defaults for some of themodeling and display parameters. M ost of the Data Types indicate a type ofspatial distribution pattern which can be exploited by certain algorithms. Dtypes are shown in the following lists:


Schlumberger Understanding CPS-3 Set Types

,

ntrike

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 intoCPS-3 must have at least an X and Y coordinatebut may also have up to 50 z-fields. These z-fields are numeric, and canrepresent any variable which is spatially distributed. A vertical well, forexample, 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 aassociated thickness to the next layer. Z-fields may also contain dip and sinformation for the horizon being mapped. There are no predefinedcombinations of z-fields which are required forCPS-3. Each z-field canrepresent anything you like. The most common data files loaded byCPS-3aredata 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 attributesassociated with each z-field:

• Z Field Name(z1, z2, top, bottom,...

• Z FieldType (depth, elevation, isochore,...



wo

noe.

d

asier.

s

ed.one, or

Data Content - Text Fields

Some data files contain textual information for each point which is to beposted on the map; for example, well name or operator name. There are tmethods for storingData sets in CPS-3 - Extended Data, andnon-extendedData.

Non-Extended Data

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

Extended Data

This type of data allows all of the above, but also allows the storage andposting of up to 10text fields, as well as the storage and utilization ofgraphicsymbology attributes. Symbology attributes, such as symbol type, size, ancolor, can be associated with each data point. At present,Extended Datacannot be exported fromCPS-3, nor canExtended Databe loaded by the useof macros.

Subsets

Data sets can be organized into subsets which makes certain processing eFor example, line-oriented data (2D seismic, digitized contours) should beidentified as such duringASCII loading so that each line becomes anidentifiable subset inCPS-3. Several formats suitable for controllingline-oriented data will be illustrated below in the examples.

Fault Sets (.fcps)

Description

Fault sets inCPS-3 store those polylines which are commonly referred to afault traces, or inGeoFrame terminology, faultboundaries. To theCPS-3procedures, it does not matter how these polylines are geometrically definFor example, a non-vertical fault pattern associated with a particular horizcan consist of two separate lines - an upthrown line and a downthrown linit may consist of a single closed polygon.



nal.ld be

iatedin

you

faultl be

tedgong

Types of Faults

Faults can be categorized by the user inCPS-3as eithervertical ornon-vertical at the time the faults are loaded. In other cases, some CPS-3operations inFramework3D automatically classify faults which they havecreated as being fault traces, faultcenterlines, or faultpolygons.

Fault Attributes

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

Associations

Fault traces used as input to a gridding operation are automatically assocwith thesurfacewhich is created. That is, the name of the fault set is storedthe parameter block of the surface set. This means that when contouring,don’t have to remember which fault set to use for each surface.

Subsets

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

Polygon Sets (.pcps)

Description

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

Types

Polygon sets can be typed as eitheropen(polylines) orclosed(polygons).



is

f thehe

elike

ion of

ork.

Subsets

A polygon set can consist of multiple polygons, or polylines, each of whicha separate subset.

Surface Sets (.scps)

Description

Surface sets hold the grids inCPS-3. Only the z-value at each grid node isstored. Parameters stored with the surface, such as the lower left corner ogrid, and the grid spacing in x and y, are used by the system to compute tx,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, inparticular, theFramework3D operations.

Associations

As mentioned underFault Sets, the input fault trace set is associated with thoutput surface in a gridding operation. In addition, there are spreadsheet-operations inCPS-3, particularly inFramework3D, where groups of surfacesare defined. These groups of surfaces become associated during the creataTable set (a.tcps file in the project directory). For example, a faultframeworkTable set is created as the user loads surfaces in to the framewIf a surface in a table happens to be deleted, the system will recognize itsabsence the next time the table set is invoked.



ved

as a be

ated

Map Sets (.mcps)

Description

Essentially, aMap set is a picture file. The picture on the screen can be sato aMap set at any time inCPS-3. Although it is possible,Map sets are notusually loaded intoCPS-3from ASCII source files.

Subsets/Map Layers

All graphic components created by a single graphic operation are groupedseparate subset in the saved map set. These separate graphic layers candeleted, moved, or even hidden temporarily inCPS-3with theMap LayerManager.

In the map set shown below, there are seven subsets, each of which is creby a separate display operation.

• Border

• Border Labels

• Scale Bar

• Contours

• Wells

• Seismic Lines

• Fault Traces



Figure 6.1 Example of a map set displaying seven subsets


n-

n

for

Chapter 7

• • • • • •Loading Location Data

Overview

There are many routes by which data can be made available toCPS-3. One ofthe traditional methods is usingASCII files, which we will demonstrate inthis chapter. However, continuing integration ofCPS into theGeoFrameenvironment provides faster, more efficient, data access methods. Forexample, interpretation which has been performed inIESX or Charismashould be visible toCPS-3 as grids inGeoFrame. Seismic locations inGeoFrame will also be visible toCPS-3, as we will demonstrate in thischapter via theGeoFrame Link (GFLink ). Well locations are also accessiblevia GFLink .

In this chapter, we demonstrate the following:

• Access 2D seismic location data from an ASCII file and/or theGeoFrame database

• Access 3D seismic location data and well location data from theGeoFrame database usingGFLink .

• Generatestatistics for the location data

ASCII Input of Locations as Extended Data

CPS-3 has a robustASCII reader and can read just about any kind of columoriented data containing x and y coordinates. When you importData sets inCPS-3,you have a choice of loading theASCII file as an ordinaryData set,which allows the preservation of only one text field (subset name), or as aExtended Data set. which allows the preservation of several text fields andsymbology fields, such as well name and symbol code. Please refer toChapter 27which gives a broader outline of the formats and requirementsthe CPS-3 ASCII Loader.


Loading Location Data Schlumberger

e

dataII

In the exercises, we will load anASCII file containing Line name, Shot Pointnumber, x-coordinate, and y-coordinate as anExtended Data set so that wecan create a proper 2D line posting.

Using GFLink for Seismic and Well Location data

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

For example2D/3D location data are now accessed via theGFLink as wewill demonstrate in the exercises.

Exercises: Loading Location Data

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

1. First, we’ll show where to load2D seismic locations data from theGeoFrame Link

2. Then, we’ll show how to use theCPS-3 ASCII loader to load acomplex2D location file.

3. Afterwards, we’ll load a simpler2D location file which we will usespecifically for this GullFaks field.

4. Then, we’ll see how to view3D surveys directly from CPS-3

5. Next, we’ll show how to load3D locations from ASCII files.

6. Finally, we’ll show how to loadtop andbottom hole well locations,then welltrajectories from the GF Link.


Schlumberger Loading Location Data

ExerciseExercise

Loading 2D Locations from GeoFrame

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

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

2. Click theLoad from GeoFrame tab, then clickData Types andhighlight “2D Navigation Lines” in the second panel. ClickOK .



g

D

3. Back in the GFLink dialog, click onGeoFrame Data. If there were2D navigation data in GeoFrame, you would see it in the next dialoand select it from there.

• • • • • •

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



u

ExerciseExercise

Loading 2D Location Data from Ascii Files

1. Open an xterm, by clickingMB1 in a unoccupied area of the display,and selectingNew Window.

2. In theCPS-3 Main Module, click User > Show Environment. (Thisopens theCPS-3 Environmentwindow.)

3. Highlight the path to yourCPS-3 dsl which is found next toProjectLocation.

4. In the xterm, typecd , skip a space, and clickMB2. (The path to yourCPS-3 dsl should appear.)

5. Typels *.dat . One of the files that you see should be namedmm_2d_gullfaks_shtpt.dat.(anASCII file) part of which is shownbelow, containing 2D locations. Look at this file using any editor yolike.



at.

This file is column-organized and contains theLine name in the first column,theShotpoint number in the second column, and thex andy coordinates incolumns three and four. This is an example of a very simple location filewhich can be easily read by theCPS-3 ASCII reader. This file was copiedinto yourCPS dsl along with the other information, which we importedByDirectory earlier.

Below is another ASCII file we imported By Directory namedcharis_2d_nav.dat. It was created inCharisma and represents similar 2Dlocation data as the first file, but in a different coordinate system and formThis file contains more information, but can also be read by theCPS-3 ASCIIreader, as we’ll demonstrate.



We’ll use the second file to demonstrate how to use theCPS-3 ASCII loader.

The first section of this file, where the lines all start withH, is afile header.This header will beskipped during import. This file contains X and Y valuesin both Cartesian coordinates and geographic coordinates.

The only columns that we want from this file are theLine name, Shotpointnumber, and theX andY cartesian coordinates which begin after the letterWin each line. In order to read this file, we will need to count the number ofheader lines to skip, which is32.

1. In theCPS-3 Main Modulemenu bar, go toFile > Import > ASCII >Extended Datato open the following dialog box.

2. In theLoad Options section, type in32 next toLines to Skip.

3. In theFile/Set Selectionsection, clickNew next toOutput Set. (Thisopens an additional dialog similar to the one in the following page.)



r

4. In this dialog box, do the following:

• typecharis_2d_nav for theName

• select 2D Linesfrom the Subtypedown-arrow list

• setSurface (container name) toUnknown from the down-arrowlist

• click OK to close this dialog box.

• • • • • •

Tip: When loading files asExtended data, it is always a good idea to specify theSubtype before you give theInput File name, since the system will do a bettejob of automatic column assignment when it knows theSubtype. It is alsonecessary to specify the number ofLines to Skip before you provide theInputFile name.

5. Under theFile/Set Selection section, clickPick next toInput File.(This opens theFile Selection dialog box.)

6. Highlightcharis_2d_nav.dat and clickOK .



7. UnderLine Name, click MB1 so that an insertion point appearsbetween the first and secondS in the nameSslb1, then click on theSplit button in theLoad Options section.

8. Click onLine Name, which now should have only a singleS, andscroll down within theField Type popup menu, and selectIgnore.

9. Above the column containingslb1, click onIgnore, then scroll downwithin theField Type popup menu, and selectLine Name.

10. As above, change theShotpoint Number column to readIgnore.

11. In the nextIgnore column, split the text between the20328 and857.22N, then change the20328 column toShotpoint Number.

12. Note that theZ column is unnecessary, since all the z-values will be0.0. We can leave it as it is, it will not cause any harm.

When theASCII Input Data section of your dialog box looks like thefollowing one, clickOK to load the data and close that dialog box.



13. When the data has finished loading, in theCPS-3 Main Modulemenubar, go toUtilities > Sets > View Contents/Statisticsto open thefollowing Main Module dialog box.

14. In theSet Type column, toggle theData (D) button to red, and selectthe data set we just loaded,charis_2d_nav, and then clickOK .



l

otver,

In theCPS-3 Status Informationwindow, you should see a statisticareport with values as shown below.

Note that every set loaded fromASCII will be stamped with thecoordinate system of the currentDisplay environment. We have notyet defined aDisplay environment, but every new project has adefaultDisplay environment, which is based on theGeoFrameDisplay coordinate system.

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

Now, we’ll import the first 2D location file we looked at which was muchsimpler in organization, and will be used to define the initial GullFaks maparea.

1. Load the ASCII filemm_2D_gullfaks_shtpt.dat into Extended datain a similar manner to the previous file. Give it an output name ofmm_2D_gullfaks_shtpt, and make sure to setNumber of Records toSkip back tozero. Generatestatistics for the set after loading. Pleasenote that this file contains onlyLine, Shot Point,X, andY.

2. Even though we have not yet defined a Display environment, thedefault Display environment from GeoFrame should allow us todisplay the data we have just loaded.

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

4. When the editing for the display environment is complete, click onDisplay > Basemap > Data, and pick the Data setmm_2D_gullfaks_shtptand then clickOK .

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

6. Set the symbol size to0.



n

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

8. Then clickOK , thenOK again. You should see the display, as showbelow:

Data Set “mm_2D_gullfaks_shtpt ”



in

ExerciseExercise

Displaying 3D Surveys in CPS-3

Depending on your version ofGeoFrame 4, 3D locations stored inGeoFrame can be seen fromCPS-3 from theDisplay > 3D Survey dialog.No data is loaded, only a display is created. Just like any other graphics inCPS-3, the display can be saved into aMap set.

1. Click Display > 3D Surveys.

2. We see what appears to be one or more versions of the two basicsurvey areas - GullFaks north and GullFaks south. At present, bothIESX andCharisma must maintain their own copies of the seismicvolumes.

3. Highlight the “gullfaks_north” survey, whose source isCharisma, andthen click theDisplay tab. This allows selection of specific inline andcrossline ranges, and aincrement or modulus incremental posting.

4. Selectall lines in the Inline Range by moving the scroll bars to the mand max positions. SetIncrement = 10, and then click theAppearance tab.

5. Chooseall items for display exceptTick Marks , Line Names, andLocation symbols.



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

7. Highlight the “gullfaks_south” survey whose source isCharisma andcreate a posting of it with similar parameters

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



in

ExerciseExercise

Accessing 3D Locations from ASCII files (optional)

In the interest of time, this exercise may be skipped, and you may use thefollowing Data sets in theCPS-3 dsl, which have already been loaded forsubsequent exercises:

• mm_3d_g1_survey

• mm_3d_85acip_survey

• mm_3d_offset_survey

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

In the exercise which follows, we will make use of three ASCII files, eachcontaining a 3D survey exported fromCharisma 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 theExtended Data Loader, just as we did with the 2D data, toload these three ASCII files intoCPS-3, creating the following datasets

— 3d_g1_survey

— 3d_85acip_survey

— 3d_offset_survey

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



t of

• • • • • •

Note: In order to load these three ASCII survey locations properly, you mustremember to specifyLines to Skip (30) first. You must load these data as3Dlines, and also use the correct format, as shown below:

Loading of ASCII surveys versus display of GeoFramesurveys

Notice that there is a difference in actuallyloading the data in this manner,rather than simplydisplaying it, as in the previous exercise. In this case, wecan compute statistics on the data and manipulate it in ways which are nopossible with simply a map derived from its display. We can also use eachthe 3D surveys as a much more accurate basis for a Display or Modelingenvironment.



d

or

ExerciseExercise

Loading Well Locations and Well Paths Using GFLink

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

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

2. Click theLoad From GeoFrame tab, and then click theData Typesicon to open the folder. This opens theGeoFrame Data Types dialogbox and again lets us identify the type of data we want to load.

3. HighlightWell Locations in the lower panel sections of theSurfaceTypesdialog box and clickOK . Then click theGeoFrame Databutton.

4. In theGeoFrame Surface Selectiondialog box, locate theBottom-hole Locations item on the left panel and highlight it. Do the same fSurface Locations.



5. Highlight both locations in theRepresentation section, and then clickOK. This will add the two items to theCPS-3 Output Setslist in theGFLink dialog.

6. Click Data Types again, and this time selectBorehole Trajectories,and clickOK .

7. Click GeoFrame Data again, and findDepth in the list on the left.Highlight it and clickOK .

8. Highlight the item on the left and clickOK , putting it on the outputlist, as seen below.



atah

9. Now highlight all the items on the output list on the right and clickRun. This transfers the items to theCPS-3 dsl.

10. In theCPS-3 GeoFrame Link dialog box, highlight theBoreholes...item on the right, and then clickRun.

11. Iconize theGFLink dialog, since we will need it again.

• • • • • •

Note: No provisions are made for specifying an output set name when loading dwith theGFLink . You have to simply accept the naming conventions, whicare actually quite clear. You may, however, use theCPS-3 Rename functionafter the data is loaded.



ExerciseExercise

Check out the Statistics of the Sets We Loaded

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

2. Look for theData setsWell_Locations_wbloc,Well_Locations_wtloc, andBoreholes_Depth_wpath.

3. View thestatistics for these sets, as before.



s,ata

t it,

ExerciseExercise

Verify the Data We Just Loaded

Even though we have not yet discussed Display or Modeling environmentwe will quickly define a Display environment here, just so we can see the dwe’ve been loading.

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

2. At the bottom, in theDisplay environment panel, clickCreate.

3. At the top, name this environment Quick_Look .

4. Click theCopy/Compute tab on the right.

5. ToggleAction to Copy Set Limits, toggleSet Type to Data, thenclick Pick Set and highlight the data set mm_2D_gullfaks_shtpt, andclick OK .

6. Back in theCreate Environment dialog, at the bottom left, set aMapRatio scale of 3000, then clickOK .

Later, we will define a more accurateDisplay environment to create a properbasemap of this location data. But at this point, we just want a quick look aand 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. Forquick display, show only the lines. Set thesymbol size to zero, and settheNo Text toggle to red.

9. Click Apply.

10. ClickData again, then clickPick Sets, and pick mm_3d_g1_survey.

11. ClickSet Parameters, changing thecolor of the lines, then clickApply.



the

12. Repeat this procedure to display the set mm_3d_offset_survey,clicking OK instead ofApply. Your display should look similar tothis:

7. Next clickDisplay > Basemap > Data, and repeat the processes todisplay mm_2d_gullfaks_shtpt.

• Display well_Locations_wtloc.

• Display well_Locations_wbloc asExtended Data, showing the wellname 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 display below:



we has data.

Here, we see the three 3D survey locations, the 2D locations, the top andbottom well locations, as well as the borehole trajectories. This is not whatwould call a proper basemap, but it is meant to quickly show that the databeen properly loaded, and to see the extents and relationships among theNext, we will proceed to define a permanent Display environment, bettersuited to our basemapping exercises.




liar

Chapter 8Set Selection, Creation, and

• • • • • •Management

Overview

Before proceeding with setting a display environment for inspection of thedata we loaded in the last chapter, we must take the time to become famiwith the way in whichCPS-3 sets and subsets are manipulated. In thischapter, we will learn about many utilitarian features inCPS-3to help us keepup with all of our different sets; for example:

• listing existing sets by type

• selecting existing sets for input operations from eitherGeoFrame, orfrom the localCPS-3 data store.

• changing the attributes of existing sets

• creating new sets

• renaming sets

• deleting sets

• copying sets


Set Selection, Creation, and Management Schlumberger

esr the

heirs

ExerciseExercise

Set Selection and Creation

In the following exercises, we will introduce you to the menus and dialoguwhich create sets and the procedure for selecting existing sets from eitheCPS local store or theGeoFrame database.

Listing Existing Sets/Editing Attributes

Almost all workflows inCPS-3 will involve the use of theCPS-3 MultipleSet Selector – a very useful set management tool.

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

The left panel is afilter which can be used to control which sets yousee on the right panel. The right panel contains the list of sets and tattributes. In the text entry fields for the filter, you may use wildcardto control the contents of the list. Note that the Surface Name is theGeoFrame Container Name.


Schlumberger Set Selection, Creation, and Management

rsle

In the Set Type panel, you can activateAll sets, or just one type. TheSurface Type panel lets you filter on theContainer name. TheProperty panel lets you filter on that attribute. Normally, you togglethe buttons that you want to red, and then click theFilter button toupdate the list.

2. De-selectAll and activate only theData button inSet Type. Click theFilter button to refresh the list.

3. Now click and hold on the small rectangle to the right of theFilterbutton, and drag it all the way to the left, effectively hiding the filterdialog area.

The sets you see may not be the same as you see here, but theprocedure will be the same.

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

5. Click on theStorage column heading and you will see all entriessorted on that column. (The sorting works for all column headings.)



ns

e,

y,

”

Most of the information fields are obvious such asOwner, CreateDate, andModify Date. However, the meaning of the following fieldsmay not be.

• Access is the GeoFrame access code such as “udo” which meaUpdate/Delete/Ownership.

• Storage tells whether the grid exists in the local data store (CPS),or in GeoFrame.

• Surface Type is theGeoFrame Container type.

• Surface Name is theGeoFrame Containername.

• 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 “Digitizedcontours” 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 exampl“depth” or “Time.”

• Measurementshows the classification of the units of the propertfor 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 faultblocks in the case of reverse-thrust faults (for grids and seismicinterpretation.)

• Grid Library indicates thebinset associated with each grid.

• Source tells where the set originated

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

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

• • • • • •

Note: TheEdit attributes andDelete icons operate on multiple sets.



8. In theMultiple Set Selectordialog box, highlight the Data setg_wells, and click theEdit attributes icon. TheMain Module dialogbox opens.

9. Set the fields as shown above, and clickOK .

10. Review the edited attributes in theMultiple Set Selector dialog, andclick Close.



n to

ExerciseExercise

Specifying New Sets (Set Creation)

Many operations inCPS-3require the specification of a new set name. Forevery new set you create, you will make use of the same dialog. Let’s learmake use of the new set dialog by copying one set to a new set.

Copying Sets

1. In theCPS-3 Main Modulemenu bar, clickUtilities > Sets > Copytoopen the Main Module Copy Setsdialog box.

2. In theCopy Sets dialog box, toggle theData buttonon, click theFilter button, and select the set g_wells, and click OK.

3. In theCopying Set dialog box, leaveSet Type asData, and clickNew.



4. Entermy_data_set as aName for the newData set.

5. SelectScattered Pointsfrom the Subtypedown-arrow list.

6. Select aStorage location ofCPS. (Note thatGeoFrame is alsoavailable.)

7. Remember thatSurface on these dialog boxes actually refers toGeoFrame container type andname, so forSurfaceselectHorizonandUnknown in the next box for name.

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

9. Click OK to return to theCPS-3 Main Module.

10. In theCPS-3 Main Module menu bar, clickUtilities > Sets >List/Manage Sets and findmy_data_setin theData set list, verifyingthat the attributes were set properly.

11. ClickClose.

• • • • • •

Note: When creatingPolygon andMap sets inCPS-3, Storage Location, ContainerType, andContainer Name are inactive.



he

thebe

Notes on GeoFrame “Container”

A container represents a collection of information at a particular place in tdata base organization hierarchy. There are varioustypes of containers, forexample,Horizon, Fault, andUnconformity. Containers also have names,and are sometimes referred to asSurfaces. A Surface in GeoFrame holds,among other things, grids and their associated fault boundaries, and evendata sets which created the grids. Multiple versions of elements can also stored in the same container.

Other Set Management Facilities

Access to set and subset utilities is available by clicking onUtilities > Sets.Except forEdit Data Set, these utilities allow manipulation of sets andsubsets, but not individual points.

We have already completed aCopy example in the previous exercise, but inthe next exercise, you will learn how the other utilities work.



ExerciseExercise

Renaming, Deleting, and Viewing Statistics of CPS-3Sets

Renaming

1. In the CPS-3 Main Module menu bar, clickUtilities > Sets >Renameto open theMain Module Rename Setsdialog box.

2. In the Set Type column, toggle theData (D) buttonon, and clickFilter .

3. Select my_data_set from the set list, and clickRename.

4. Type in the new namenew_data_name , and clickOK again.

5. In theRename dialog, scroll down through the set list to verify thatthe name was changed, then click onCancel.



Viewing Statistics

1. In theCPS-3 Main Module menu bar, clickUtilities > Sets > ViewContents/Statisticsto open the following dialog box.

2. Toggle theBasic Statistics buttonon.

3. In the Set Typecolumn, toggle theData buttonon.

4. Identifynew_data_name from the list.

5. Click OK .

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



rary
More sophisticated statistics are available in theExtended Statisticsmode,which allows statistics to be computed, for example, by subset, or by arbitgeographic polygonal areas.
Deleting Sets

Although you can delete a set from theMultiple Set Selector dialog box, youmay prefer using theUtilities menu, which allows you to change set typesmore easily during deletion.

1. In the CPS-3 Main Module menu bar, clickUtilities > Sets > Deleteto openMain Module Delete Sets dialog box.

2. In theSet Type column, toggle theData buttonon.

3. Select the setnew_data_name, click Delete and answerYes to theaffirmation message.




o

Chapter 9Defining a Display Environment and

• • • • • •Examining Data Coverage

Overview

Here, we will discuss the concept of mapping environments and theirattributes. We will show the difference in environment attributes required tperformdisplay functions, versus the attribute requirements to performmodeling operations. We will discuss the reason for having multipleenvironments, and, in a later chapter, we will have exercises to createenvironments, 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 adisplay environment. Before you can create a grid, you must define amodeling environment”.


Defining a Display Environment and Examining Data Coverage Schlumberger

hat

y

Granted, a default mapping and modeling environment is provided asenvironment #1, however, it may not cover the exact area nor grid lattice tyou really want.

The material in this section is designed to provideformal definitions ofenvironments, their attributes, overall purpose, and management in a fairlconcise lecture format. You will learn most about environments by workingwith your data. However, it is anticipated that you may refer to this sectionfrequently until you have gained a full understanding of the use ofenvironments.


Schlumberger Defining a Display Environment and Examining Data Coverage

ters

inve

Definition of Mapping Environment Components

An Environment is anamed collection of information associated with thecreation of maps or surface models in aCPS-3project.

Attributes which are associated with environments are:

• Name and optionalDescription

• UsageClassification— BothModeling andDisplay, 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 parame

— Rotation: origin and angle

• Definition ofhorizontal and vertical units

• Definition ofhorizontal and vertical scale factors

• Definition of vertical property code

Attributes which are associated withModeling operations are:

• Definition of agrid 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 contathe definition of a grid geometry. Data displayed through the currently actiDisplay environment will undergo the following procedures:

• transformed to the activeGeographic Coordinate System

• scaled to the active scale

• converted to the active horizontal units

• clipped in x and y by the active Volume of Interest



gents

ing

ut

ewer

ics

Modeling Environment

A Modeling environment is used to create a grid or perform other modelinoperations. Think of a modeling environment as simply a display environmto which agrid geometry has also been added. An environment which doenot contain abinset definition cannot be used for modeling, only display.Grids created in modeling operations will assume the grid origin and spacof that defined in the currently activeModeling environment.

The Relationship between CPS-3 Modeling Environmentsand GeoFrame Binsets (Grid Libraries)

The new concept ofCPS-3mapping environments is tied to theGeoFramedata base, at least in terms of binsets or grid libraries. EveryModelingenvironment in CPS-3 must point to a specificbinset in GeoFrame.Displayenvironments, as you will discover, do not require grid lattice definitions.

Just as all sets must be associated with a particular coordinate system inGeoFrame, the grid spacing in allCPS-3 surfaces must now be defined interms of a specifiedGrid library (binset). All binsets are stored inGeoFrame. Abinset is a formal definition of a grid lattice and has severalattributes, including x-spacing, y-spacing, rotation, x-offset, and y-offset, bnot all of the parameters are associated with aCPS-3 Modeling environment.At present, however, all we need to know is that we must either define a nbinset (the most common option), or select one from an existing list, in ordto specify x and y spacings for surfaces.

Later in this course, exercises will be provided to demonstrate the mechanof how data can be stored in eitherCPS-3 or GeoFrame. Also, we willdemonstrate how to create, delete, and edit mapping environments.



esn,

.

to

be

ing

More Notes on Binsets

1. Binsets existed inGeoFrame beforeCPS-3 began offeringDisplayandModeling environments. All three concepts are similar, in thatthey define a collection of mapping parameters which controlhigh-level display operations and/or the granularity of a geologicalmodel. The related concept ofGrid Library , which is effectivelysynonymous withbinset in GeoFrame, was invented years ago toguarantee that grids from different applications would overlay. Nodfrom all grids created under the same grid library would, by definitiooverlay.

2. Once abinset has been created, it cannot be modified through theCPS-3 menus. Even if you could, you wouldNOT want to do thisbecause, in a sense,binsets are shared by all users in theGeoFrameproject, and modification would cause problems for all child-objects

3. Be careful if youdelete binsets because every surface you delete,which was created with thebinset to be deleted, will become unusablein GeoFrame. Use the following procedure to find out whichGeoFrame surfaces were created with a particularbinset:

4. In our example, we picked x and y-intervals which divided evenly inour x and y ranges. When the division is uneven, the systemautomaticallyincreases the x-maximum and/or y-maximum values sothat the division will be exact.

5. Thecoordinate system defined for thebinset always becomesassociated with theenvironment for which we are defining a binset.Thus, any previous coordinate system in the active environment willoverwritten by the one in a selectedbinset. This is true for thebinsetwe created, and would also be true had we used a method of creatourModeling environment which involved the picking of an existingbinset from the list.

Procedure: Determining a Particular Binset

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

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



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 theSelectEnvironment 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 withMB1 in order to highlightit in the Select Environment dialog box, and then clickingSelectundertheModeling or Display panel, or both, as appropriate. If thehighlighted environment has nobinset defined, it will showNo undertheModel column, and cannot be used for modeling.

• Creating A New Environment

Click Create under theModeling or Display panel, as appropriate.

• Editing An Environment

Highlight the desired environment, and clickEdit Current under theModeling or Display panel, as appropriate, or simply click theEditicon.



of

ate

ed

ple,

• Reviewing Environment Attributes

Highlight the desired environment, then click theReview icon.

• Deleting Environments

Highlight the desired environment, then click theDelete icon.

In the many exercises which follow, you will become familiar with the use these functions.

• Notes— If during the creation or editing of an aModeling environment,

you select an existingbinset, then thebinset’s x,y box andgeographic coordinate system replaces the x,y box and coordinsystem of theModeling environment you are creating or editing.

— Environments you define are stored in your currentsession file,<login id>.1cps, which is located in theCPS partition of theproject.Refer to a later section regarding the storing andretrieval of session files.

— Because of the closer integration withGeoFrame, and theinstitution of environments,CPS-3 procedures have become moresensitive tounits anddomains. For example, an attempt tocompute borehole intersections with a surface set, which is storin milliseconds from a borehole set which was loaded fromGeoFrame in seconds, will result in an error message.

— Just as procedure sensitivity to environments may cause errormessages in some cases, it will also provide benefits. For examduring many operations, input data from sets with differingcoordinate systems will beautomatically converted to match thecoordinate system of the output set.



itsg

ore

rid

.

redey.

same

Multiple Environments

The most apparent characteristic of a display or modeling environment is x,y extent - the area of interest, or, as it used to be called, the “engineerinwindow”.

From the sample map at the beginning of this section, it can be seen why mthan one environment is needed in typical projects. TheModelingenvironment, as its name suggests, is used for defining that area where gnodes are computed. TheDisplay environment, on the other hand, has moreto do with defining the extent of the graphic entities making up a basemapContinuing with the example map, a basemap might be required whichincluded all available seismic surveys including the 2D, but the area requifor gridding and volumetric calculation may cover only the smaller 3D surv

In this case, we would define a smallDisplay/Modeling environmentcovering the 3D survey area, and a largerDisplay environment covering theentire 2D extents, as shown below.

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

Thus, with this version ofCPS-3, it is possible to perform graphic operationscovering one geographic area, while creating grids in another area at the time.



ur

oject

s.

Setting Up for Horizontal and Vertical Scaling andLimiting

Besides establishing a traditional x,y map scale,Display environmentsletyou define the attributes needed to controlvertical scaling, which is an issueduring 3D visualization provided by theAssemblytab inModeling Office, aswell as the display ofprofiles, orcross sections.

Figure 9.3 Setting vertical and horizontal scaling and limits

Storing and Retrieving Environment Definitions

The currentEnvironment Selector and Environment Editor are sufficientfor the management of environments in most cases. However, because yoenvironments are actually stored in yoursession file, they are somewhat at riskwhen it becomes necessary to remove the session file during remedial prcleanup activities. Certain temporary problems can be cleared up inCPS-3 byremoving thesession file, and allowing the system to create a new version.Unfortunately, you lose yourenvironment definitionsbecause they are storedthere. For this reason, the recommendation is to make use of thesave andread commands to periodically backup your current environment definitionThese commands are activated in theCommand line box at the bottom of theStatus Window. Here is how it works.

This is how you set the Z-scalingfor your cross-sections. ExaggeratedHorizontal is a linear multiplier of thebaseline scale above, left.

This is how you set the horizontalscale along the baseline for yourcross sections.

This is how you set the Z-limits forExtended Statistics and 2D cross-sections.



s ofe

s

ake

• Make a permanent copy of your environments periodically

Whenever you create a new environment,save your session file asfollows:

Typesave <file name> in the command line.

This causes your entire session file, which contains the latest valueall parameters you have set, plus your environment definitions, to bwritten to the file name<file name>.1cps. This file will reside in yourCPS partition.

• Reinstating lost environments

If your session file is lost, you can reload all your environments inappend mode to your current session file as follows:

Typeread <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 associatedbinsetis loaded, the system searchetheGeoFrame data base for the firstbinset which matches the attributes ofthe one in the session file, and links it to the environment being loaded,regardless of the name of the originalbinset. If a matchingbinsetis not found,the environment is not loaded. For this reason, it is not recommended to muse of sessions files from other projects.



Rotated Grids

By virtue of the attributes available in the definition ofModelingenvironments, a new facility is now available inCPS-3 — the ability tocreaterotated grids. The rotation attribute in thecoordinate systemspecifications allows the definition of grids like the one shown in the mapbelow, 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 theunrotatedactiveModeling environment are stored in the parameter block of the set:Data, Fault, Polygon. Attributes from therotated activeModelingenvironment are stored in the parameter block of the set:Surface, Map.



s aY

,ype

se

Specifying the Characteristics of Display and ModelingEnvironments

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

For example, when specifying the X and Y limits of a Display environmentyou can use the existing X and Y limits of any selected set. You can also tthe X and Y limits in directly in cartesian coordinates, or you can specifythem in decimal degrees.

When creating Modeling environments, you have the same flexibility. Forexample, you have the ability to create a Modeling environment by simplypointing to an existing binset in GeoFrame. If you use this procedure, pleamake note of the following:

• • • • • •

Note: If you happen to choose a method to create yourModeling environmentwhich involves theselection of a particularbinset from theGeoFrame list ofbinsets, you should know thatbinsetscontain not only a grid lattice definition,but specifications forx, y limits and acoordinate system,both of which willsupersede those values you may have already entered for your newenvironment in theCPS-3 dialogs.



nd

Exercises for the Display Environment

Having loaded 2D and 3D location data, as well as top and bottom holelocations, and the well paths, we are ready to define aDisplay environmentso that we can build a basemap of this location data.

The instructor should, by this point, have discussed the concept display amodeling environments inCPS-3.

In these exercises, our workflow will be as follows:

• set some standard graphic parameters

• define aDisplay environment

• display data locations

• evaluate data coverage and decide which area to map and grid.



e.

ExerciseExercise

Setting Standard Parameters

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

Set Screen Background Color

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

1. In theCPS-3 Main Module menu bar, clickDisplay > DisplayFunctions > Set Background Color.

2. Click on theScreen background color button to open theSelect aColor palette. A white background is recommended for this exercis

Set Screen Margin

3. In theCPS-3 Main Module menu bar, click onDisplay > DisplayFunctions > Set General Display Parameters.This opens theGeneral Display Parameters dialog box.

4. In theSet Screen Display Margin section, set theLeft , Right, Top,andBottom margins to1, 6, 1, and 1, respectively.



michis

seena

ExerciseExercise

Define a Display Environment for the Location Basemap

We’ll now create a display environment based on the extent of the 2D seislocations, because it appears to cover more area than the 3D locations. Twill 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 the two surveys inIESX knows that the 2D survey covers a much larger arethan the 3D. Therefore, we will define our initialDisplay environmentso thatits x, y extents match those of the 2D survey data set.

1. In theCPS -3 Main Module, click theSelect Environmenticon. This opens theSelect Environment dialog box.

2. Click Create in theDisplay Environment section of theSelectEnvironment dialog box.

3. Click on theLat/Lon Box tab, and ensure that theCoordinate Systemis set toUTM, Zone 31.

4. In theDisplay Environment Editor dialog box, click on theCopy/Compute tab.



r

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

• EnterGullFaks_Overview in theName text entry field.

• Enter2d and 3d Survey Areas in theRemarks text field.

• ToggleCopy Set Limits in theAction section to red, then toggleData in theSet Typesection to red.

• Click on thePick set button in theSet Type section, and select themm_2D_gullfaks_shtptdata set from the list. Make sure the filtein the file selection dialog is wide open ("all").

• Click OK to return to theDisplay Environment Editor.



asd

e,

• In theHorizontal Scalesection, setMap Mode to Direct andenter635.0 for Map Scale.

Please note that in certain early versions of GF4, the scale shows “(m/in)”, which is incorrect. It should be “(m/cm)” since the computesize is in centimeters

• PressReturn. TheWidth andHeight for the Resulting Map Size(Paper) is computed, and should be approximately22 cm x 20cm.

• Disregard theVertical Axis and Scale section for now.

6. Click OK to end the creation process.

7. If the sizes appeared incorrect above, click onEdit Current in theDisplay Environment panel and see if it now shows the correct valuthen clickCancel to return.

8. Highlight theGullFaks_Overview environment.

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

10.Closethe report.



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

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

1. In theCPS-3 Main Module menu bar, clickDisplay > Basemap toopen the followingBasemap Display dialog box.

2. In theBasemap Display dialog box,

• toggle Border to red in theBasic Elements section.

• toggleExtended Datato red in theDisplay Setssection, and clickon the Pick Setsbutton.

• select themm_3d_85acip_survey data set, and clickOK .

• Click theSet Parametersbutton and set the following values:

— turn off theLine display

— turn on theline annotation display, set thesize to .05, setWhichEnd to Start of Line.



ine

nd

— turn off theshotpoint annotation.— turn onsymbol parameters; setincrement to 5, setsize to .05.

— click OK

3. Click Apply in the Basemap Displaydialog 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 lcolor for each. ClickOK out of the Basemap dialog.

At this point, we see that the first 3D survey locations may possibly go beyothe lower border, and so we’ll demonstrate how to edit the current Displayenvironment to make it larger.



ExerciseExercise

Enlarge the Current Display Environment Window

1. Erase the screen using theErase current display icon located intheCPS-3 Main Module.

2. Click theSelect Environment icon, to open theSelectEnvironment dialog box.

3. In theSelect Environment dialog box, highlight theGullFaks_Overview environment.

4. Click on theEdit the highlighted environment icon or click theEdit Current button in theDisplay Environment section of theSelect Environmentdialog box. This opens theDisplayEnvironment Editor .

5. In theDisplay Environment Editor window, click theSimple XYBox tab.

6. In theSimple XY Box folder, modify theY-Minimum value to be6779000.0, and clickOK .

7. Click OK in the Select Environment dialog box.



ExerciseExercise

Redisplay the Three 3D survey locations

1. Return to theBasemap Displaydialog box, and redisplay the same 3Ddata sets as before.

2. Add aborder on the display.

This quick posting shows the 3D locations now to be completelycontained within the environment’s x,y limits,



ed.you

ExerciseExercise

Preparing a Location Basemap

Now we have an environment where we can see all of the data we’ve loadLet’s create a proper location map of the area. This exercise will introduceto some of the basemapping facilities inCPS-3.

Border, Labels, Scale Bar, and Title

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

2. In theCPS-3 Main Modulemenu bar, clickDisplay > Basemap ortheDisplay basemap icon to open theBasemap Display dialogbox.

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

• ToggleBorder in theBasic Elementssection to red.

• ToggleLabels in theBasic Elementssection to red, and then clickSet Parameters to open theDisplay Window Labels dialog box.

4. In theDisplay 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 Labelsdialog box.

6. In theBasemap Display dialog box, toggleScale Barin the BasicElementssection to red.

7. Click Set Parametersto open theDisplay Map Scale Bar dialog box.



8. In theDisplay Map Scale Bar dialog box, make the followingsettings:

• ToggleUse environment units, located across fromScale barunits, 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 theDisplay Map Scale Bar dialog box.

10. In theBasemap Display dialog box, toggleMap Title in theBasemap Display section to red, and clickSet Parameters to opentheDisplay Map Title dialog box and make these settings:

• Bottom margin title = GullFaks - 2D, 3D, and WellLocations

• 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. ClickOK to close the Display Map Title dialog box.

12. ClickOK in the Basemap Displaydialog box to display the graphicsin theCPS-3 Main Module.



e

ot

as

• • • • • •

Note: It is a common occurrence that some graphic elements seem to “fall off thedges of the display”. For example, themap title andscale bar, placed belowthe y-axis are not visible at this time. However, we will continue with thedisplay of the basemap components, knowing that these elements have nbeen lost and will be restored to visibility shortly.

Display 3D Survey Locations

1. Click Display > Basemap > Dataand display the two 3D locationdata sets, mm_3d_85acip_survey and mm_3d_offset_survey, just before, but use grey for both.

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

3. Click Set Parameters and make the following settings:

• ToggleLine parameters to red.

— Color = light blue

— Width = thin line

— Style = solid line

• ToggleLine annotation parametersto red.



— 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 Displaydialog 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 clickOK .

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



ue

e

— Angle = Perpendicular— Size = 0.12

• Toggle Symbol parametersto red.

— Color = black,

— Increment = 25

— Size = 0.12

— Click on theSymbol code button and select a hollow circle.

— Mode = Incremental

• Togglez1 to gray.


5. Click OK in theBasemapdialog.

Note that the Shotpoint annotation increment is every50th, and theShotpoint symbol increment is every25th.

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 continby 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 thdown arrow once, to position it in the list as shown above.



ns.

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

We will continue with posting of the boreholes and the bottom hole locatio

Post Borehole Locations

1. In the Basemap Display dialog box, toggleData to red, and clickPick Sets.

2. Select the setBoreholes_Depth_wpath, and clickOK .

3. Click Set Parameters to open theDisplay a Set dialog box and makethe following settings:

• In theSet Data Line Parameters section

— Line style = solid line

— Line width = thin line

— Line color = black

• In theSet Data Symbol Parameterssection,Symbol size = 0.0.

• In the Set Data Text Parameters section, toggleNo text to red.

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

5. Click OK in theBasemap Displaydialog box.

Post Bottom Hole Locations

1. In the Basemap Display dialog box, toggleExtended Data to red,and clickPick Sets.

2. Select the setWell_Locations_wbloc, and clickOK .

• Click Set Parameters, and set the following values:

• ToggleSymbol Parameters to red.

— Color = black

— Symbol code = select symbol number 16

— Size = .125

• Togglez1 off.

• ToggleBorehole Name to red.

— Color = black

— Size = .125



map

save

ow

— Quality = Graphic Art— X Offset = 0.0 or blank— Position = below— Y Offset = 0.0 or blank— Font = 3

• Toggle all other categories off.


4. Click OK to close theBasemap Display dialog box.

This completes the basemap, but as we noted, there are elements in the 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, let’sour work, before worrying about the hidden parts.

Save the Display as a Map Set

To retain all the work we have done, we willsavethe graphics on the screen toa permanentMap set. Afterward, we will also make afinal change to ourDisplay environment, GullFaks_Overview, so that it also shows the graphicswhich, at present, are hidden from view.

1. In theCPS-3 Main Module, click on theSave currently displayedmap icon. This opens the following dialog box.

2. Enter the nameGullFaks_Overview , and clickOK to save theMap set.

All graphics on the screen, as well as the portions hidden from view, have nbeen saved into a permanentCPS-3Map set, which can subsequently bedisplayed in its entirety with one operation.

Now let’s zoom out and look at thehidden annotation around the map.



nd

theow. so this:

and

View the Entire Basemap

Note theReveal all graphicsicon which is the third from the top. Whenthis icon is bright, it means that there are graphics posted which are beyothe current x,y limits of the activeDisplay environment.

1. To reveal the graphic in its entirety, click on theReveal all graphicsicon. All of the displayed graphic is now visible.

The system creates atemporary display environment which is large enoughto show all previously displayed graphics. In this graphic state, thecurrentDisplay window is still represented by theborder around the map, but we aresimply zoomed out, in a temporary window.

Create a Larger Display Environment Which Covers theEntire Map

As you can see, the annotation we have added to the map has increasedtotal area of the display which does not fit inside the defined Display windFor convenience, we would like to increase the size of the display windowthat it is approximately the size that we now see. We have two ways to do

• by using the featureCreate Display Environment from Zoom, or

• by saving the display as a Map set (which we have already done), thencreating a new Display environment based on the X,Y limits ofthe Map set.



ken

ut

s of

yer

We’ll demonstrate the first method:

1. Click theCreate Display Environment from Zoom icon.

2. Call the new environment Gullfaks_Better_Overview , orwhatever you like. ClickOK .

3. When theDisplay Environment is Changingdialog appears, click onCopy Existing Graphics...at the top, andClip To New Window... atthe bottom, and then clickOK

Without even using theEnvironment dialog, we have created a newDisplayenvironment, activated it, and transferred the entire contents of the screendisplay to the new environment. Had anything gone wrong, or if we had taa wrong step along the way, we can still go back to the Map set we savedearlier, and use it as a basis for the new environment.

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

1. Click on the Select Environment icon and in the subsequentdialog, highlight the line for theGullfaks_Overview Displayenvironment.

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, bleave everything else in the map unchanged.

Removing/Replacing Map Layers

Remember, the graphics you see on the screen are composed by a serieoverlays, orlayers. Each time you displayed a set or graphic entity on themap, a layer was created. What we want to do is to remove the current lacontaining thescale bar, and put a new one on in a different location.

1. Click onDisplay > Map Layers to reveal theMap Layer Managerdialog similar to the one below.



2. Toggle theDelete button to red, next to the layer namedMap ScaleBar, then clickOK .

Having removed theMap Scale Bar, we will now reposition it in adifferent location.

3. In theCPS-3 Main Module, click on theDisplay basemap icon toopen theBasemap Display dialog box.

4. ToggleScale Barto red, and clickSet Parameters.

5. In theDisplay Map Scale Bar dialog box, retain all the previousparameter settings, but toggle theUse cursorbutton for both theX andY-position of scale bar.

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

7. Click OK to close theBasemap Display dialog box.

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

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

Once you click its position, the scale bar is drawn, but the graphiccursor remains on the screen. You may clickMB1 to accept thecurrent position, or you may clickMB3 to reposition the scale bar atanother location.




.ore

-3

-3

Chapter 10Accessing and Displaying

• • • • • •Interpretation and Well Markers

Overview

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

Accessibility of Seismic Components by CPS-3

3D seismic interpretation is stored asGrids in the data base and is visibledirectly in the CPS-3 Set Selector dialog.

2D interpretation is stored as “Line/Scatter”Data and must be loaded intothe CPS-3 dsl by theGeoFrame Link.

Fault Cuts are not directly visible from CPS-3 but are loaded into the CPSdsl with theGeoFrame Link.

Fault Contactsare not directly visible from CPS-3 and are loaded into theCPS-3 dsl with theGeoFrame Link.

Fault Polygonsare directly visible in the CPS-3 Set Selectors asFault sets.

Seismic Attributes are stored asGrids in GeoFrame and are directly visiblein the CPS-3 Set Selector dialog.

2D locations are not directly visible in CPS-3 and are loaded into the CPSwith theGeoFrame Link.

3D locationsare visible in CPS-3 and can be posted in theDisplay menu

Cartography in IESX can be imported into CPS-3 usingFile/Import/IESX_Culture


Accessing and Displaying Interpretation and Well Markers Schlumberger

een

lem

sn

can

Gridding 3D interpretation

Now, when gridding a 3D horizon, CPS-3 must be able to accept grids inGeoFrame as input to the gridding algorithms. The Gridding menus have bchanged accordingly. Note theSingle Surface griddingdialog now allows theselection of either Data or Grid input:

How do I distinguish an interpretation grid from othergrids?

One of the most common objects stored in GeoFrame are grids. The probarises on how to identify theprimary interpretation grids for a particularhorizon from other derivative grids which can be computed by dozens ofother applications. This problem is compounded by the fact that all timeinterpretation grids have the name “Time” and all depth interpretation gridhave the name “Depth” in IESX. A similar repetitive grid naming conventioexists in Charisma.

However, as we examine the file selection dialog in CPS-3, our searchingbe 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 havingName = “Time”, Surface = the desired horizon name, andGridLibrary = the correct grid library for the horizon. This set will be theTime interpretation for the Horizon.


Schlumberger Accessing and Displaying Interpretation and Well Markers

an

s

ion,e

e

y theand

n

There are other ways of identifying interpretation grids as well. In anyGeoFrame dialog which allows the display of component attributes, you cexamine the “Source Code” and “Property Code” attributes of a grid. If theSource is “Charisma” or “IESX”, and the Property Code is “Time”, then thiis a pretty good indication that you are looking at the primary timeinterpretation for a particular horizon. A Property Code of “Depth” wouldindicate primary interpretation in depth. Other, derivative grids will havedifferent Property Codes, for example, “Integrated_Reflection_Strength”. Adifferent Source Code also indicates that the grid is not primary interpretatfor example, “Surface Manager” means that the grid was derived from somother grid.

Interpretation Models and CPS-3

A new concept in GF4.0 is theInterpretation Model . The interpretationmodel is a name given to some collection of interpretation objects - 2D lininterpretation, 3D grid interpretation, fault cuts, fault contacts, and faultboundaries, which are related in some way, for example, all being done bsame interpreter. The interpretation model may consist of several horizonseach horizon can consist of multiple patches.

In many applications, the Interpretation Model can be used as a filter wheselecting data. For example, during Horizon Modeling in FrameworkModeling, you may choose to select input data only from a particularinterpretation model. At this time, CPS-3 does not interact with theInterpretation Model concept. All data is seen in the set selection dialog,regardless of its model.



Destinations of Interpretation Components WhenImported into CPS-3

When imported fromGeoFrame, the following interpretation components arestored as indicated:

• Geologicalhorizon markers ‘are stored asCPS-3 Data sets (.dcps)

• 2D horizon interpretations are stored asCPS-3 Data sets (.dcps)

• 3D horizon interpretations are stored asCPS-3 Grid sets (.scps)

• 2D/3D fault segment interpretations are stored asCPS-3 Data sets(.dcps)

• Seismicfault contacts are stored asCPS-3 Data sets (.dcps)

• Seismicfault polygons are stored asCPS-3 Fault sets (.fcps)



aret

ce.r

rty and

Exercises for Data Retreival

In these exercises, we will retrieve those interpretation components whichnot directly visible inCPS-3, and will demonstrate how to identify those thaare.

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 boundarieswhich represent the intersection of the fault surface with the horizon surfaIn a later chapter, we will use fault segment data in order to create grids foone or more of the fault surfaces.

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



y

,this

ExerciseExercise

Locate 3D Seismic Horizon Interpretation andAssociated Fault Boundaries

In GeoFrame 4, 3D seismic interpretation for horizons does not need to be“transferred” intoCPS-3. It is already visible in theCPS-3 set selectiondialogs as grids. From the previous lecture, we learned how to identify it bSurface andGrid Library , orProperty Code andSource Code.

1. Click onUtilities > Sets > List_Manage_Sets

2. Selectgrid as theSet Type, Select onlyGeoFrame for theStorage,and then click theFilter icon.

3. Click on theName column heading

From theSurface Namecolumn we see that the first five grids, all named AArepresent a depth interpretation for each the five horizons which we use inproject. You may not see these grids in your project listing, but theseparticular versions of the interpretation were done inCharisma.

The important point is that no “loading” is necessary.CPS-3 has direct accessto the 3D interpretation for gridding.



. In

is

izon

We will be using a different version of the interpretation for these horizonsparticular, those 3D seismic interpretation grids inGeoFrame which beginwith the prefix “mm_” will be used to identify the data we want to use in thclass.

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

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

4. In theList/Manage Sets dialog, selectFault as theSet Type, selectGeoFrame asStorage, then clickFilter .



erevents by

ltn of

g

In this project, we see only these two fault boundary sets, but in practice, thare usually more - typically one for each interpreted seismic horizon, and eseveral versions. It is up to the user(s) to keep track of these boundary seusing the assignment facilities inIESX.

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

In a similar fashion, inCPS-3, there are ways of associating or disassociatinfault boundary sets with particular horizon grids seen there.



e

ExerciseExercise

Load Well Markers with GFLink

1. From theCPS-3 Main Module, click Tools > GeoFrame Link toopen the CPS-3 GeoFrame Linkdialog box.

2. In theCPS-3 GeoFrame Link dialog box, click theLoad FromGeoFrame tab.

3. In theLoad From GeoFramefolder, click Data Types to open theGeoFrame Surface Typesdialog box so that we can focus on the typof data we want to bring across.

4. In theGeoFrame Surface Types dialog box,

• click Horizons underContainers

• click Markers underRepresentations, and then clickOK .

5. Return to theCPS-3 GeoFrame Linkdialog box, clickGeoFrameData, to open theGeoFrame Surface Selection dialog box.

6. SelectDepth from theVertical Domain pop-up list.



as

nd

7. From theContainers list, pickBUNNKRITT, DRAKE, NESS,RANNOCH, andTARBERT .

• • • • • •

Note: For each pick under theContainers list, a DEPTH entry under theRepresentations list should appear.

8. Highlight all items on the right by clicking theSelect allRepresentations in the listicon, and then clickOK .

Selected items appear in theGeoFrame Link dialog box as above.The[D] notation to the left of the name in theCPS-3 Output Setslistindicates that the output set will be aData set.

9. Highlight all five items in theCPS-3 Output Sets list, and then clickRun.

10. ClickExit when finished.

This demonstrates the correct method for retrieving well markers inCPS-3, which, as we see, are not automatically visible from CPS-3,are interpretation grids and fault boundary sets.

We will not be using these particular marker sets in our exercises, aso we’ll remove them as described in the next step.



be
11. Return to theCPS-3 dialogs, and from theList/Manage Sets dialog,
delete these five markers data sets which we just loaded. They willfound in the CPS-3 storage area, not inGeoFrame. Do not removeanything from theGeoFrame data area:

BUNNKRITT_Depth

DRAKE_Depth

NESS_Depth

RANNOCH_Depth

TARBERT_Depth



ExerciseExercise

Well markers as scatter sets

In this class, we will be using a different set of markers for each of thesehorizons than the ones which are available via theGFLink . The ones we willuse were loaded intoGeoFrame from a different source, and because thesource was external to this current project, they are visible toCPS-3 in its fileselector dialog, as well marker scatter sets. See below:



zonin

ot

ExerciseExercise

Summary of Basic Horizon Interpretation Data Available

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

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

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



he

ExerciseExercise

Examine Data Statistics

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

1. From theCPS-3 Main Module, click Utilities > Sets > ViewContents/Statistics to open theView Set Contents/Statistics dialogbox.

2. In theView Set Contents/Statistics dialog box,

• toggleBasic Statistics to red

• toggleData [D] to red

• Highlight GF:mm_BUNNKRITT_Depth_wmrkr.

This data set contains the well markers for the Bunnkritt horizon. TGF: prefix indicates that they are stored inGeoFrame, not theCPS-3dsl.

• Click OK

3. The statistics should appear in theCPS-3 Status Informationwindow, as below:



first.

z-

Note that the basic statistics report always provides informationregarding the sets “native” coordinate system and transformations In the second section, the x, y, and z minimums and maximums aredisplayed, along with units information. If a set has more than one field, the limits of all z-fields are displayed.

4. Display the basic statistics for the followingData sets:

• mm_TARBERT_Depth_wmrkr

• mm_TARBERT_Depth_intrp

• mm_NESS_Depth_wmrkr

• mm_NESS_Depth_intrp

5. Verify that theirz-ranges are specified inDepth (m) and are in thefollowing range:

• Tarbert : 1781 - 2389

• Ness:1712 - 2400



ny

Let us review the fault boundaries for theTarbert andNess horizons.

6. From theCPS-3 Main Module, click Utilities > Sets > ViewContents/Statistics.

7. In theView Set Contents/Statistics dialog box, toggleBasicStatistics to red.

8. ToggleData to gray, and toggleFault to red.

9. Highlight the followingFault sets:

• GF:mm_Ness

• GF:mm_Tarbert

10. ClickOK .

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



set

ExerciseExercise

Rename faults, and remove z-values

In this exercise, we are going to remove the “mm_” prefixes from the faultnames, and strip off their z-values.

1. In theCPS-3 Main Module, click Utilities > Sets > Renameto opentheRename Sets dialog box below.

2. Toggle onlyFault [F] to red, and clickFilter

3. Highlight theGeoFramemm_Ness Fault set, and clickRenameat thebottom.

4. Provide a new name Ness , and then clickOK .

5. Repeat the process for “mm_Tarbert”, changing its name toTarbert.



red

ere

6. Exit from theRename dialog, and then clickUtilities > Sets > Copy.

7. Highlight theGeoFrame set Ness, and clickCopy.

8. In the dialog which appears, setOutput Set Type to Polygon, andclick New.

9. Define a Polygon set with the same name, Ness, define it to be stoin GeoFrame, and clickOK , thenOK again.

10. From theCopy dialog, repeat the process for the Tarbert faultboundary set.

11. Still in theCopy dialog, toggleSet Type to onlyPolygon and clickFilter .

12. Highlight the Ness polygon, and clickCopy.

13. ToggleOutput Set Type to Fault and clickPick. Choose the originalNess fault set and clickOK , thenOK again, to overwrite the originalversion.

14. Repeat this process for the Tarbert polygon.

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

16. Make sure that your display environment is still set toQuick_Look.Erase the screen, and clickDisplay > Basemap

• ToggleBorder to red.

• ToggleFaults to red, and clickPick Sets.

• Select the Tarbert fault set, and then clickOK .





aillhee in

.

ExerciseExercise

View Data Sets before Gridding

Without worrying about grid spacing or other gridding algorithms, let’s havequick look at these “data” sets, which are really interpretation grids. We wdisplay each one using color-shaded symbols. This will not only show us tdata distribution and density, but will also give us a preview of the structursome cases.

Bunnkritt Interpretation Grid Set

1. In theCPS-3 Main Module, click theSelect environment icon.

2. Select theGullfaks_Overview environment, and clickOK .

3. Click Utilities > System > Set_Toggle_Switches, and make sure thatthe switchShow Graphic Entities... doesnot have a red box next to it

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

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

• UnderBasic Elements, toggle Border andLabels to red.

• UnderDisplay Sets, toggleGrid Nodes to red, and click PickSets.

• Set the filter attributeStorage = onlyGeoFrame, then clickFilter .

• Selectmm_BUNNKRITT_50x50_Depth_intrp, and clickOK .

• Click Set Parameters, and make the following settings in theDisplay a Setdialog box:

— Symbol code = 122

— Symbol Size = .3— In Set Grid Node Text Parameters, toggleNo text to red

— In Set Overpost Protection Parameters, set both values to 1.

— In Set Grid Node Elevation Coloring Parameters, setSurface coloring method = Use color range.

— In Set Palette Parameters, Invert Palette = NO



— Click OK, then OK again to start the display.

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



e to

een

Tarbert Interpretation Grid Set

1. Erase the screen using theErase current display icon orDisplay > Display Functions > Erase Display in theCPS-3 MainModule.

1. Use the previous procedure to display themm_TARBERT_Depth_intrp interpretation grid set. The systemshould remember the parameter settings, and you should only havspecify a different grid name.

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

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



half

Ness Interpretation Grid

Use the same method as before to display the mm_NESS_Depth_intrpinterpretation grid.

This horizon also has similar erosion zones, but are limited to the Easternof the map.

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



e,

Rannoch and Drake Interpretation Grids

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

Rannoch

Drake


ctsrs

yourated

msakele in

se.

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 aspeof gridding. You will learn how to select the most critical gridding parametewhich affect the quality and appearance of your surface. There are manyalgorithms from which to choose, and many parameters which can affect map. However, for the typical mapping task, very good maps can be generusing only a few of these parameters. AnAdvanced Topicsclass is availablefor those who wish to study the inner workings of the gridding algorithmsmore deeply, but the schedule for this course does not allow for all algorithand their parameters to be covered in depth. In this course, we will try to tthe pragmatic approach and give you the tools to get the best map possibthe shortest time.

It is recommended to read the chapter in the on-lineUser’s Guide whichcovers gridding. It gives many details which may be overlooked in this cour


Gridding Fundamentals Schlumberger

o a and

the

.

What is Gridding?

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

Grid Terminology

Figure 11.1 Map grid and components

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

This grid is a 6 by 9 grid, meaning 6 rows by 9 columns. Thegrid cell size,the number ofrows andcolumns and the gridrange are related as follows:

• X-interval = Range inX divided by (Number of Columns -1)

• Y-interval = Range inY divided by (Number of Rows -1)

CPS-3 may increaseXMIN or YMAX to ensure that the range in x and y isevenly divisible byxinc andyinc.

Grid Columns

34001800

7800

YIN

C

4550

XMIN XMAX

YMIN

YMAX

Grid Node

Grid

1 2 6 7 8 95

2

4

5

3Row

Row

Row

Row

Cell

XINC


Schlumberger Gridding Fundamentals

nedhe

ts.

Judging the Quality of the Grid

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

Next, examine the contours in the areas of the grid between the data poin

• 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 isyes, then the second criteria has probablybeen fulfilled. Remember that after gridding, yourmodel is represented by thegrid and fault traces - the data has become redundant.

Gridding Algorithms

As you will see, CPS-3 has many gridding algorithms, but each of them isdesigned to solve the basic gridding problembelow:

Given thedata points andfault traces above, create a model of regularly-spaced grid points whichhonor the data and exhibit asmooth transition ofthe surface between data points and the edge of the map.

Figure 11.1 Common gridding problem showing data and fault traces



wntion

teWe theotent

ts.

can

in

a,n

arge

rge

How Do I Prepare for Gridding?

At first, we will assume that the only data to be gridded is the well data shoabove. The data for this class includes both 2D and 3D seismic interpretaas 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 yourdata points

• Inspect yourfault traces

• Decide on themodeling area

• Decide ongrid spacing

• Decide whichalgorithm to use

• Decide how to setgridding parameters

Data Inspection and Selection of Modeling Area

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

Determining the Grid Cell Size

In its most basic form, the method for determining the proper grid spacingbe stated as follows:

Find the closest two data points whose difference must be distinguishablethe 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 criterithat is, a contour map which shows the difference between the two chosepoints. However, there may beother limiting conditions which you shouldconsider before settling on this grid spacing. For example, it could be thatsuch spacing generates a grid whose number of rows and columns is so lthat the gridding takes aninordinate amount of time. Is is also possible thatsuch a spacing is so small that it produces a grid which contains a very laamount of high-frequencynoise. While the stated method of choosing a gridinterval is a very good way to start, there are even more reasons why youshould look atother characteristicsof your data as shown below.



ter

from are

the

thecan

h ofnter

n the

t

Looking at our simple example again in the figure below, we can get a betfeel for the scale of our data and the grid spacing by introducing a graphiclattice on the display. The lattice shown is 500 meters on a side. Judging the spacing of the well points, 500m is not a good grid spacing since thereseveral 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 thinfault blocks.These blocks will hardly be defined with such large spacing. Sometimes, ultimate criteria for defining a grid size is the horizontal separation in thefaultzone. If it is desired to define the fault zones for volumetric purposes, thenchosen grid size must provide enough nodes in each fault zone so that it 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 forselecting the interval in this data set, we might choose the two points, eacwhich borders on a north/south-oriented fault trace toward the southeast ceof the map. As we have just noted, however, the width of the fault blocks ithat area is even smaller than the distance between these points. Clearly,width of these fault blocks should be thedefining feature to be resolved inthe final grid. We would therefore choose a grid interval of approximately100m in this example, which will allow us to define the fault blocks, but noall of the fault zones.



aata.

d to

val, in

sks.

sentand

s are on

Considering only the well data and the fault patterns, we have determinedreasonable grid interval based on close inspection of the features in our dBut in your project data, you may also have 2D or 3D seismicinterpretationto go along with the well data. This same sort of analysis should be appliethe seismic data.

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

How Do I Choose A Gridding Algorithm?

If your gridding task falls into one of the followingspecialcategories, youshould use the algorithms which are especially recommended for those taOtherwise, you should use theConvergent 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 reprethe typical task of creating a structural model from well data, fault traces, seismic interpretation, which is the most common modeling exercise. Theoperations above and the algorithms used for the creation of their surfaceimportant to learn about, but in the exercises for this chapter, we will focustheConvergent Gridding algorithm, which is recommended for day-to-daystructural modeling.



t

y

esntil

List of CPS-3 Gridding Algorithms

Convergent

A very stable, fast, general purpose algorithm for computing a smooth, buaccurate fit to almost all types of data. This algorithm provides trend-likeextrapolation, and being the “flagship” of theCPS-3gridding algorithms, itshould be the first one considered for almost any structural data.

Below is a schematic showing the refinement of a surface being created bsuccessive iterations of theConvergent Gridding algorithm. Afterestablishing an initial trend with a coarse grid, each successive step reducboth the grid cell size, and the radius of influence for each control point, uthe surface is locally “tied” to the data.

Figure 11.1 Internal surface refinement by the Convergent Griddingalgorithm



g ahe

t to

e fit

the

e.

Contour to Grid

Contour to Grid is a derivative of theConvergent Gridding algorithm withthe parameters optimized to honor digitized contour data. When generatingrid using digitized contour data as your input, this algorithm will provide tbest fit to the contour data.

Least Squares

Least Squares is a general purpose algorithm used for computing a best-fiscattered data points. It retains the regional trend surrounding grid nodes,while effectively smoothing out some local variation. Although not a goodextrapolator, this algorithm is sometimes used for gridding fault surfaceswhich have little curvature. Before theConvergent Gridding algorithm wasdeveloped,Least Squares was the vanguard gridding algorithm inCPS-3.

Moving Average

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

SNAP

SNAP is the building block algorithm incorporated intoConvergentGridding . 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 ofLeast Squares or Convergent Griddingwhich treats zero values as surface limits. All positive, non zero-values arehonored while zero-values are used to define the zero line for the Isochor

Trend

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

Polynomial

Polynomial is a special purpose algorithm used for computing fixed valuegrids as polynomial functions of x and y.



.

ing

e

r,.

e,

ng

Step

Step is a special purpose algorithm for use in producing lithology, soil orvariable hydrocarbon contact maps. Grid node values are set to thevalue ofthenearest control point.

Distance

Distance is a special purpose algorithm used to quantify the spatialdistribution of the data points. Grid node values equal thedistance to thenearest control point.

Density

Density is a special purpose algorithm used for modeling data distributionGrid values are set to thenumber of data pointsfalling within theSearchLimit Radius (SLM ) centered on the node.

How Do I Set Gridding Parameters?

In this course, we will focus on theConvergent Gridding algorithm. For thepurpose of this course, and possibly for most of the data you will be griddin the near future, there are only a few parameters which you will routinelyconsider 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 theConvergent algorithm, but for the scope of this class, we will highlight thesthree as being by far the most important.

In the first gridding attempt of any new surface, the recommendation is todetermine theFinal grid interval , just as we discussed earlier in this chapteand to take thedefault values (shown in bold italics above) for the other twoThe only time youmay not want to take the default value for theInitial gridinterval is when you know that you have very dense data. If this is the casyou may want to reduce this number to only twice theFinal grid interval ,and also reduce theNumber of Nodes to Snap To to 2 - 4.

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



s

a

in

ridawe

to

Common Gridding Problems and Their Solutions

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

How Do Fault Traces Affect Gridding?

Many surfaces to be gridded are known to be faulted, and the intersectionhave already been located within the horizon as “fault traces” or “faultboundaries”. Other than for display considerations, it does not matter howfault boundary is geometrically defined inCPS-3. For example, a non-verticalfault 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 utilizedthe same manner by all algorithms as explained below.

The spacing of the nodes in the figure below represents the 50m x 50m gspacing which we decided to use for this training data. This figure shows zoomed-in area of our data, and, for purposes of this faulting discussion, 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 thecomputation of a grid node value, depending upon its spatial relationship the node being computed and the fault patterns.

Problem Solution

Grid does not honor control points Make Final grid interval smaller

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

Not enough extrapolation beyond datapoints

Make Initial grid interval bigger

Holes in the final grid Make Initial grid interval bigger

Grid too noisy Make Final grid size larger or do a singlesmoothing operation

Grid does not show features inherent inthe data

Make Final grid interval smaller



s ay

le,

so

the

uchuresr

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

Any algorithm inCPS-3 which is computing the value of a grid node, such athe one marked “+” in the figure above, will treat each fault line segment as“barrier” during the interpolation process. Data points which can potentiallcontribute to the value of a node, must first pass avisibility test to see if theywill be used or discarded. If any point is in the “shadow” of any fault linesegment, then itwill not be used in the computation of the node. For exampin the figure above, pointsA, B, C, andD are in the shadow of at least one ofthe faults, and will therefore not be used in the computation of that node’svalue. None of the other points are in the shadow of any other faults, and they will be used for the computation.

The idea is that only data points which are on thesame side of a fault as thenodebeing computed will be used to compute that node’s value. Nodes onother side of a fault or on another fault block are not used.

Note that this samevisibility criteria is also used by theCPS-3 grid-basedinterpolator during the computation of other manifestations of a surface, sas contouring, volumetrics, and refinement. That is, all grid-based procedin CPS-3 are cognizant of where the faults are located and will modify theiresults based on the faults, as long as they are specified on input.



,ethe

Gridding Decisions - 2D/3D Seismic Examples

We have discussed how to choose a grid cell size with simplistic well dataand now we provide some guidelines for other geometries. For each of thtypes of data distributions shown below, we will give recommendations forFinal grid spacing, theInitial grid spacing , and Number of Nodes to SnapTo.

2D Seismic

In general, for 2D seismic:

• Final interval - roughly the same as the shot point spacing, but becareful not to make it so small as to create noise along the lines

• Initial interval - as large as 1/2 the distance between the twofurthest-apart “contiguous” lines

• Number of Nodes To Snap To - 16

Figure 11.1 2D seismic display



e of

Line-Decimated 3D

The characteristics of line-decimated data is similar to 2D seismic - verydense points along lines which are far apart, relative to the points. This typdata 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



s ineryts,

nts to

sens

ofble at

Dense 3D

The characteristic of this data is its homogeneous density. In the examplebelow the homogenous pattern is prevalent, but broken by large void areathe data. Here, the interpreter appears to have interpreted every line or evother line, except in the void areas. Some of the void areas represent faulothers 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 poiwhich may be present. In some cases, 25m or 50m cdp spacing may leadgrids inCPS-3which exceed the reasonable limits. At present “reasonablelimits” 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 causome delay in processing and require lots of storage if many horizoare involved

• 1000x1000 grid - unless you have an extremely fast server and lotsswap space and lots of storage, grids of this size are not manageathis time.



aely,

ion forlure

e

For this type of data, the interpretation is typically at a density which isequalto or greater than theFinal interval you might choose. For this reason, theproper algorithm to select for gridding isSNAP, notConvergent. ChoosingSNAP and setting the parameters as indicated below will produce either aliteral copy of your interpretation (without any interpolation taking place), orsub-sampling of it, depending upon whether the data density is, respectivequal to, orgreater than the selectedFinal interval .

• Final interval: decide based on how much you want to invest ingridding 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 withnon-vertical faults, it is important to get a reasonable thickness grid definitin the fault zones. The reason for this is that unless the fault wedge zonesthe two horizons are defined in their grids, their resulting isochore grid wilnot be suitable for accurate volume calculations. If, for example, in the figbelow, the Top surface were defined in the grid only in its upthrown anddownthrown blocks, and not in the fault wedge zone from A to B, then thethickness grid cannot be defined in the interval from A to B. Similarly, if thBase horizon is blank in its fault zone, the thickness grid will also be blankfrom C to D. In those locations where the initial thickness grid is blank, novolume will be computed

Figure 11.1 Non-vertical fault zone displaying fault wedge zones



eive

le, of

id of

nes

t

lynden to

es,s is for

ry

e

As an integral part of the horizon being mapped, the fault zone should recas much attention as the fault blocks.

Techniques for Filling in Fault Zones

In order to fully define these fault zones, there are several techniquesavailable. A summary is presented below.

Blanking and Regridding

In this technique, you first grid the horizon’s fault blocks as well as possibwhile using the fault boundaries during gridding. This ensures the integrityshape for each block. When this initial grid is complete, blank out this gridinside all fault polygons. This cleans the fault zones of any spuriousdefinitions 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 grthe horizon with the convergent algorithm WITHOUT using the faults. Thetheory of this technique is that the best possible data to define the fault zoare 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 excellendata to use to define the fault zone. Simply make sure that the griddingalgorithm can see and will use these z-values by setting the appropriateswitches when specifying gridding parameters. This technique requires onone step, but also requires some quality control for the fault boundaries atheir z-values, and assumes there is no conflicting data which might happfall in the fault zones.

Using Existing Fault Surfaces

This technique is not an easy one if you have more than a few faults. It dohowever, lend itself to being incorporated into a macro. The reason for thithat it requires several operations per fault. Here is the outline of the stepsone fault:

• blank the existing fault surface outside of its associated fault boundapolygon

• perform thesurface operation which replaces nodes in one grid (thehorizon grid) with nodes from another (the blanked fault surface). Inparticular, the surface operation required is the 10th Multiple SurfacLogical Operation, “A in Union”, otherwise defined as

“C=A, but if A or B is Null, then C = Valid(A,B) (-255)



s.ave. the

e.ay to

Contour Visibility in Fault Zones

It is sometimes difficult to tell if grid nodes have been defined in fault zoneWhen horizontal separation is small, only a few nodes can fit across the heIn this case, contours may not be generated in the fault zone, even thoughnodes are defined. (See the example below.)

Figure 11.1 Grid nodes across a fault zone

The algorithm’s visibility of grid nodes is sometimes restricted by theupthrown and downthrown traces as it tries to compute inside the fault zonNot enough nodes are visible to generate reasonable contours. The best wdetermine 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 nodesthemselves. Null grid nodes will not appear on the display.




g,

e

n,

es

Chapter 12

• • • • • •CPS-3 Gridding Parameters

Overview

The purpose of this chapter is to apply the information we learned in thechapter aboutGridding Fundamentals to specific data sets. We’ll discuss thefollowing:

1. Assuming that we will use both well data and seismic data in griddinwe’ll go through the decision-making process to settle on aFinalgridding increment for the sample data sets.

2. We will present some easy-to-remember guidelines for choosing thmost important Convergent/Snap gridding parameters -Starting GridInterval andNumber of Nodes to Snap.

3. We will also discuss the topic of defining the fault zones in a horizoand when it is necessary.

4. Finally, we’ll talk about when it is convenient to grid the fault surfacthemselves, and describe amacro which uses a specific technique forgridding fault surfaces.


CPS-3 Gridding Parameters Schlumberger

ined

ne.ing.

he

sedof

nd

Selecting the Grid Spacing

The Rule of Thumb

As you may recall fromChapter 11 - Gridding Fundamentals, the gridspacing required to replicate all features in a data set is sometimes determtwo methods:

• half the distance between the two closest points

• half the distance between the two closest points whosedifference you wish to distinguish

This rule of thumb works fine most of the time forwell data. However, forvery dense seismic interpretation, we may end up with a grid which is too fiLet us now examine our data in detail to help us pick the appropriate spac

Well data

Let’s look only at our well data for a minute. In the map below, several of twells 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, baon their distance, can lead to a grid which contains an inordinate number nodes. If we choose anxinc based on the two closest wells, according to therule of thumb, we will have a grid with a spacing of 25 feet, 490 columns, a600 rows.


Schlumberger CPS-3 Gridding Parameters

the

chhe

r the

selinghe

n iss ofll

ny

y

out

If this were all the data we had, and our concern was to reflect all data in 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 substantialdifference in slope from the rest of the map. This would guarantee that eadata point fell in its own grid cell, and the difference in z-values between ttwo 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 griddingoperation. This means that we could ignore their separation as a criteria fogrid spacing and use a larger grid separation.

Here is another way to look at it. There are only two wells which are as cloas 50 feet. If there were many wells in the data set, then one might be wilto accept a bit of averaging in the grid around these two wells, if it meant tdifference between a modest grid and a very large grid.

Looking at the rest of the wells, it appears that the next smallest separatioapproximately 100 or 200 feet. Let us assume that the difference in z-valuethe two closest wells is not significant. Then, this inspection of only the wedata tells us that we might use a grid interval of about 100 feet. This willprovide a surface which is relatively modest in size, but which will resolve aimportant features inherent in this well data.

• • • • • •

Note: It is appropriate to look closely at the well data when determining a gridspacing, since traditionally, well data is considered to be of a higher qualitthan the seismic interpretation.

Let us now look at the seismic data to see if it tells us anything different abthe grid spacing.



es. is

us

Seismic Data

As seen below, seismic data comes in a variety of densities and geometriThe one characteristic of all these different interpreted horizons, however,based on the fact that both cdp and shot point spacing is 55 feet in theCloudspin project. This defines the closest points in the seismic data. Let see if this affects our chosen grid interval.

Figure 12.2 Seismic data in a variety of densities and geometries



,way

lar

splee to

gs

e

Varieties of Seismic data geometries in Cloudspin

1. Seed Interpretation

Seed interpretation, or line-decimated interpretation, is interpretation whichhas been done at a subsampling of the cdp or inline spacing - for exampleevery 20th inline and crossline, as seen in the figure below. This is a goodto get a horizon interpreted quickly - pick every 20 inline/crossline and letASAP fill in the rest!

Figure 12.3 Seed interpretation subsampling every 20th inline/crossline

Cloudspin interpreted horizons havingINTRP in their names fall into thiscategory. This means that the lines are about 1100 feet apart. This particugeometric distribution of data points is characterized by lines which arerelatively far apart with respect to the density of points along each line.Thitype of data distribution sometimes requires extra work in the normally simgridding operations, especially when a grid spacing is chosen which is closthe distance between points on the lines.

The reason for the extra work is to overcome the tendency of any griddingalgorithm to tie the grid closely to the many points along the line, while givinan average solution at nodes between the lines. The following figure showwhy the extra step is sometimes needed. It shows a grid computed fromseedinterpretation data where only a simple convergent step was applied. Notthe bull’s-eyes along the lines.



sizeeg, one

he

ed,

Figure 12.4 Seed interpretation grid displaying noise and bull’s-eyes alongdata

With this type of data, it is sometimes necessary to increase the final grid in order to reduce the noise and bull’s-eyes along the data line. If you havseveral horizons which must maintain the same x,y extent and grid spacinthis can be a problem, only if this type of data happens to be available forof the horizons. In this case, the recommendation is to grid the data at thesmallest final grid interval which minimizes the bull’s-eyes, but then refine tgrid down to the smaller required size.

2. ASAP Interpretation

Cloudspin horizons havingASAP in their name fall in this category. Thistype of geometry infers that every cdp in the survey area is potentially definas is almost the case in the portion of ourJakarta horizon shown in thefollowing figure.



r,n

p.

Figure 12.5 Horizon interpretation using ASAP

TheIESX automatic picking procedure calledASAP was used in the abovefigure to finish the horizon interpretation between the20x20 lines picked bythe interpreter. Dense data like this is usually very simple to grid. Howeveholes in the interpretation can cause gridding problems. For example, in aASAP version of theKobe horizon below, we see patches of missinginterpretation, especially below the Hobart fault in the lower part of the ma

Figure 12.6 Example of holes in the interpretation



l

When using theConvergent gridding algorithm, the key is to make theStarting interval large enough to that holes in the grid are avoided. For theLeast Squares algorithm, make theSearch Radius larger when unwantedholes in the grid are identified.

3. Combinations

The Paris horizon below contains both20x20 andASAP interpretationgeometry, but it should not be any more difficult to grid than the others. Aldata distribution types shown here can easily be gridded with theSnap andConvergent Gridding algorithms, as we will demonstrate.

Figure 12.7 Horizon displaying 20x20 and ASAP interpretation geometry



ineed

s.

ome

g

foreet

4. 2D Only

This type of data is similar to the seed distribution type, in that, data existsvery dense points along lines which are sparsely distributed. As with the sdata, the potential exists for bull’s eyes along the lines if a too smallxinc isused initially. Either post-refinement of a somewhat larger final grid size, amentioned 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 scan affect the way in which data is gridded in the mapping stages. Forexample, in theCloudspin project, not all horizons were interpreted with theautomatic smoother activated. We will see one or more of our horizonsexhibit high-frequency noise in the initial contours. A small bit of smoothinin 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 thatthe densely-interpreted seismic horizons, many of the data points are 55 fapart. The choice of a50 foot grid spacing would give us a grid having 225columns and 280 rows. This is not an extremely large grid, and50 feet wouldbe an appropriate spacing if this reservoir were modeled with the intent ofcomputing accurate oil in place.



s

e

the

Simple Guidelines for Choosing SNAP/CONVERGENTparameters for Seismic data

1. If theseismic interpretation data isdense enough that interpretationexists in every grid cell of the selected gridding lattice in all locationof the map where grid definition is desired, then useSNAP withNumber of Nodes = 1

2. If the interpretation containsholes or does not exist in areas where thgrid must be defined, then use theCONVERGENT algorithm withNumber of Nodes = 16, andStarting Grid Interval = half the diameterof the largest hole in the data.

Figure 12.8 Incompletely defined seismic interpretation

For example, if the figure above represents 3D seismic interpretation, theStartingGrid Interval should be at least several times the distance betweendata points in order for the grid to fill in the holes in the data.

A



o

onesllure

is

Defining the Fault Zone in a Horizon - Yes or No

As you prepare to create grids for your horizons, you should think ahead tthe end of your particular workflow. If your only concern is to create astructure map, it is common practice to blank out the fault zones on thecontour map. You can do this byblanking the grid inside of the fault zone, oryou may choose to do it graphically, by simplycolor-filling the fault zoneduring display.

As you will see in the exercises, defining the fault zones in a horizondoes notrequire the presence of a surfaces for the faults, which is discussed in adifferent context below.

Importance of Fault Zone Definition

In horizons with non-vertical faults, it is very important to get a reasonablethickness grid definition in the fault zone if your goal involves accuratevolume computations. The reason for this is that unless the fault wedge zfor the two horizons are defined in the grid, their resulting isochore grid winot be suitable for accurate volume calculations. If, for example, in the figbelow, the Top surface were defined in the grid only in its upthrown anddownthrown blocks, and not in the fault wedge zone from A to B, then thethickness grid cannot be defined from A to B. Similarly, if the Base horizonblank in its fault zone, the thickness grid will also be blank from C to D. Inthose locations where the initial thickness grid is blank, no volume will becomputed

Figure 12.9 Non-vertical fault zone displaying fault wedge zones



s.ave. the

e.

s

Contour Visibility in Fault Zones

It is sometimes difficult to tell if grid nodes have been defined in fault zoneWhen horizontal separation is small, only a few nodes can fit across the heIn this case, contours may not be generated in the fault zone, even thoughnodes are defined. (See the example below.)

Figure 12.10 Grid nodes across a fault zone

The algorithm’s visibility of grid nodes is sometimes restricted by theupthrown and downthrown traces as it tries to compute inside the fault zonNot enough nodes are visible to generate reasonable contours.

• • • • • •

Tip: Even though display functions like contouring may not be able to visuallyrender every portion of a gridded surface, it is still important that the nodebe defined properly for structural reasons.



ultng

dip.the

so

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 thestructural envelope you create for volumetrics. If your structural envelopedoes not involve sealing faults, then you probably don’t need to grid your fasurfaces. If the envelope does involve one or more sealing faults, but havivery modesthorizontal andvertical separation, you may still decide not togrid the fault surfaces, and simply treat the faults asvertical faults. However,in the case of large throw or large heaves on the sealing faults, you willprobably get more accurate results in yourvolumetrics if you include the faultsurface in the structural envelope.

A Predefined Technique for Fault Surface Gridding

Here, we’ll discuss atechnique for gridding fault data which may not benecessary for all fault data sets, but which is a very useful alternative toConvergent gridding. The origin of this gridding technique is the realizationthat most fault surfaces have strong linear components in the direction of With the typically sparse data provided by fault segments, as interpreted inseismic, strong linear trends are not always honored by theConvergentalgorithm. The gridding technique consists of the following:

• Create an initial 2nd orderTrend grid from the fault data points.

• At all data point locations, compute thedifference between theTrendsurface and the z-value in the data point.

• Subtract the two values, creating a new z-field calledError .

• Create a grid of theError andadd it to the initialTrend grid, givingthe final grid which contains a strong fault-like trend downdip, but alties to the observed data.

This technique is contained in the macro called k_grid_fault.mac




rids

Chapter 13Set Modeling Environment and

• • • • • •Compute Horizon Grids

Overview

In this chapter, we will focus on that geographic area where the horizon gwill be computed, and define theModeling environment for it.

Figure 13.1 Modeling environment shown as subset of Display environment


Set Modeling Environment and Compute Horizon Grids Schlumberger

ng

We will also create grids for the following horizons

• Bunnkritt

• Tarbert

• Ness

keeping in mind the guidelines that we learned from the lectures on gridditechniques.


Schlumberger Set Modeling Environment and Compute Horizon Grids

aD. Wed

ExerciseExercise

Define Modeling Environment

The Tarbert interpretation, shown below inwhite, defines the area which wewant to map. This horizon pinches out against an upper unconformity, theBunnkritt, towards the East, but yet there are still plenty of wells in the arefrom the Western platform. At this time, there is no interpretation for the 2survey locations. They have been used mainly for basemapping exerciseswill therefore define an area which surrounds the Tarbert interpretation ancreate a modeling environment for it.

Figure 13.2 GullFaks region, surrounding extent of Tarbert interpretation



m

te

s

the

1. Click theSelect Environmenticon in theMain Module and thenclick onCreate in theModeling panel.

2. EntergullFaks_gridding for theName.

3. Click theData Extents tab, then make sure that the coordinate systeis correct.

4. Click Pick Sets, and select theGeoFrame Grid setmm_TARBERT_Depth_intrp.

5. You will see a message that the system has accepted the coordinasystem. ClickOK to this message, and continue by clicking theMin/Max tab.

6. Then, under the X Axis andY Axis panels, modify the limits of thedata minimums to match the following:

• X-Minimum = 453700

• Y-Minimum = 6784500

7. Set the grid spacing as follows:

• X andY-Increment = 50.0

The system will automatically round up the maximum x and y valueso that theIncrement 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 thatfollowing values are reflected:

• X-Maximum = 459600

• Y-Maximum = 6792100

• Column Count = 119

• Row Count = 153

9. Click theProperty Code down-arrow and selectDepth. (Z Unitsshould bemeters.)

10. ClickOK , then highlight the associated display environment calledStdView:gullfaks_gridding, and clickEdit Current in theDisplaypanel.



ure

is

y

11. Set theMap Scale Mode to Direct and specify aScale of 250 m/cm.Note that early versions ofGF4 may incorrectly show (m/in) insteadof (m/cm). Verify that your plot is the same size as shown in the figabove and click OK to return to the Environment dialog box.

Returning to theSelect Environment dialog box, note that there arenow two new environments. One is our newModeling environment,the other is a companionDisplay environmentcalled“StdView:gullfaks_gridding”, which is useful, but only if the Modelingenvironment is rotated.

12. We’ll remove the companion display environment,“StdView:gullfaks_gridding” by highlighting it and clicking on the red“X” icon in the upper right of theSelect Environment dialog box.

If the Modeling environment that we just created were arotatedenvironment, then we would not want to delete this companionenvironment, since it would serve a very useful purpose - its x, y boxtheminimal rectangle of the rotated x, y box.

13. Now, highlight the Modeling environment, “gullfaks_gridding” andclick on theSelect button in theDisplay environmentpanel, thusselecting this Modeling environment to be used as the active Displaenvironment as well.



Remember:

• • • • • •

Note: If you happen to choose a method to create yourModeling environmentwhich involves theselection of a particularbinset from theGeoFrame list ofbinsets, you should know thatbinsetscontain not only a grid lattice definition,but specifications forx, y limits and acoordinate system,both of which willsupersede those values you may have already entered for your newenvironment in theCPS-3 dialogs.



ts

ation

ExerciseExercise

Gridding the Horizons

Grid the Bunnkritt Unconformity

Below, we see the distribution of interpreted data points for theBunnkritt , anunfaulted unconformity. This surface will be very easy to grid because of idensity of data.

We will choose theSnap algorithm in its most simple mode to obtain a gridwhich is almost a literal copy of the interpretation. This is a very fastprocedure, since the algorithm is not required to make more than one iterthrough the data.

1. In theCPS-3 Main Module, click theSelect environment icon.

2. In theSelect Environment dialog box, activategullfaks_gridding asthe activeDisplay andModeling environment, and clickOK .



ing,

Create the Grid

Thesingle Snap procedure should be used with very dense data like theBunnkritt, where the data points are as close, or closer, than the grid spacand there are no appreciable gaps or holes in the interpretation.

3. From theCPS-3 Main Module, selectModeling > Single Surfacetoopen theSingle Surface Gridding dialog box.



to

4. In theSingle Surface Gridding dialog box, make the followingsettings:

• UnderInput Data/Grid , toggle the first position to red, and clickonPick Set.

• In the selection dialog which appears, set the filter so thatSet Type= only Grid , andStorage = onlyGeoFrame. Then clickFilter .

• Select the interpretation grid named:mm_BUNNKRITT_50x50_Depth_intrp. Click OK.

• Back in the gridding dialog, toggle the second input set positionred, clickPick Set, and in the set selection dialog, changeSetType to onlyData, and clickFilter again.

• Select the well markers named:mm_BUNNKRITT_Depth_wmrkr as the second input data setfor the gridding.

• Toggleoff (gray)Fault and Polygon.

• SelectSnap from theAlgorithm pop-up list.

• Set Number of Nodes to snap to =1

• UnderOutput Grid , click New to open an additionalSingleSurface Gridding dialog box.

— EnterBunnkritt as the new output surfaceName.— Storage should beCPS, and theSurface (Container) Type

should beHorizon, and theSurface (Container) NameshouldbeBUNNKRITT as picked from the list.

— Click OK to return to the originalSingle Surface Griddingdialog box.

— Click OK to start the gridding which will return you to theCPS-3 Main Module.



Contour the Grid

4. Erase the screen, then clickDisplay > Contours to open theDisplayContours and/or aShaded Surface dialog box.

• SelectBunnkritt for theGrid .

• Make sure thatDisplay Line Contours is toggled to red, and clickSet Parameters. This opens theParameters for Contouring aSurface dialog box.

— Start contour level - toggle Computed to red.

— Increment between contours - specify 5.

— Number of contours - toggleComputed to red

— Further down, on the right, clickNo Bolding, No Blanking,andNo Labeling.

— Click OK to close the Parameters for Contouring a Surfacedialog box.

• Click OK to start the contouring.

Add a Border and Labels to the Display

5. SelectDisplay > Basemap.

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

• ToggleBorder to red, and clickSet Parameters to open theDisplay Window Border dialog box.

— Border line width = thin

— Border line color = black

— Click OK to close the dialog box.

• ToggleLabels to red, and clickSet Parameters to open theDisplay Window Labels dialog box.

• X: label size andY: label size =.4

• X: label increment andY: label increment - set both to 2500.

• Click OK to close the dialog box.

7. Click OK to begin the display.



des to

s.

,

Y.the

the set.

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 noon the East and West edges were not defined by the simple snap griddingthe two closest nodes. In order to fill out the entire grid, we need to re-gridwith different parameters, to force some extrapolation to occur at the edge

2. There also appears to be some alignment or mistie problem in the dataresulting in the small vertical and horizontal features. If we were to lookclosely at the data, we would note that it is not truly equal-spaced in X andThis is due to the way this data was prepared for this project. It illustrates nature of the SNAP algorithm whenNumber of Nodes is 1 or 2.

Both of these minor problems can probably be repaired by simply setting number of nodes to a larger value, perhaps 8 or 16 for this particular data



at

ithth ae

Re-grid the Bunnkritt with Number of Nodes = 8, then 16

• Repeat the gridding step above, but setNumber of Nodes = 8instead of two. AnswerYes to both grid questions which appear.

This is better, but the border shows that we still have some missing nodesthe edges.

• Re-grid again, usingNumber of Nodes = 16

You will see that this will also not carry the grid all the way to the edge. Wthis data set and map area, we’ll have to use the Convergent algorithm wiStarting Grid Interval of approximately 200m, in order to extrapolate all thway to the edge

• Re-grid again, this time select theConvergent algorithm and settheInitial Grid Interval to 200m.



e
This map of the Bunnkritt is complete all the way out to the edges, and thehorizontal and vertical features have also disappeared. We’ll use this as thfinal map for the Bunnkritt unconformity.


e.,

atle

ing

a.ill

Grid the Tarbert Horizon

In the Tarbert horizon, whose data components are seen in the followingfigure, we have a different type of data distribution than in the Bunnkritt; i.we have manyholes in the interpretation data. Some of these holes are theresult of poor seismic definition, others show where the horizon has beeneroded, and others represent fault zones. Clearly a singleSNAP griddingwould not work with this data since much of the grid would be undefined.We’ll therefore use theConvergent algorithm with all of its extrapolationcapabilities.

Most of the wells are coincident with the seismic interpretation. We trust thcalibration has been performed. One of the wells provides some additionadata in the erosion zone to the West of the F4 fault, but other than that, thwells do not cover much geography in this horizon.

We also note that a few of the fault boundaries appear to be spurious, formfault blocks (see the arrows) where there is no data to define them.

In these cases, we have the option to remove the fault patterns for the F6F7a_D, F15a, and F6 faults and obtain a simplified model. Another option walso be discussed when we address filling in the fault zones.

F6a

F7a_D

F15aF6

F14



an

fust

rt

What is the ultimate purpose of the horizon grids?

If we were only making structure maps, and the long-term goal of ourexercises did not involve the computation of volumes, or the derivation of envelope for the gross isochore, we might forget about the fault zones andsimply grid this surface using the fault polygons provided, blanking out thefault zones in the map. We will do this at first, but since the real purpose othese grids is to construct an envelope for a specific lithologic zone, we maddress 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 theSingle Surface Gridding dialogbox.

• Select theGeoFrame grid, mm_TARBERT_Depth_intrp, as thefirst Data set from the down-arrow orPick Setlist.

• Select theGeoFrame data set, mm_TARBERT_Depth_wmrkr asthe secondData set.

• ToggleFault to red, and pick the GeoFrame Fault set mm_Tarbeas theFault set.

• TogglePolygon to gray.

• SelectConvergent from theAlgorithm pop-up list, and set theInitial Interval (Starting Grid Interval ) to 300 . (We will explainlater in the chapter why we use this value.)

• Click theAdvanced parameters button, and underSet ModelingParameters, verify thatNumber of Nodes to snap tois 16.

• Click OK to return to theSingle Surface Gridding dialog box.

• UnderSurface, click New to open theSingle Surface Griddingdialog box.



• Double-click on the current name and hit theDelete key.

• Enter Tarbert as the new gridName, and then clickOK toreturn to the originalSingle Surface Gridding dialog box.

• Click OK to start gridding and return to theCPS-3 Main Module.

Display the Tarbert Contours

3. Erase the screen, and click onDisplay > Contours.

• Select theTarbert grid, Its associated fault set,mm_Tarbertshould already be selected in theFaults panel.

• ToggleDisplay Line Contours to red.

• Click OK to start the contouring.



th

ue to

ep,d

e

Analyze Map Quality of Tarbert Grid

As suspected, we have several fault blocks on the East side which areundefined or poorly defined. At present, we do not have any other data wiwhich to define these blocks, and so we will remove thefault patternsmentioned earlier.

We also note that the computed grid does not cover the entire map area dlack of data. We have the option of increasing the size of the initial gridinterval which will have the effect of causing moreextrapolation into theseblank grid areas.

When we zoom in, closer to the well locations, we notice several largediscrepancies between the well and seismic interpretation. We will continuwithout the well data when we re-grid this horizon just to get a smooth mabut in a real project, of course, the geologist and seismic interpreter shoulresolve thedifferences at the wells.

Another characteristic of this map which requires some remediation are thcontours in thefault zone. In this first part of the exercise for the Tarberthorizon, we’ll simply blank them out after removing the fault patterns andregridding as mentioned above.



ataay

set,

use

hessta.

o

The last problem with this grid is that there is some inherent noise in the dwhich is evidenced by the horizontal streaks. Again, this comes from the win which the data was prepared and will be remedied by smoothing as weproceed.

Remove Irrelevant Fault Patterns and Re-grid Tarbert with MoreExtrapolation, Without the Wells, Adding Contour Data

In order to remove the proper fault polygon subsets from the Tarbert fault you’ll need to know that the faults we want to remove have the followingsubset numbers:

3: F7a_D

9:F15a

10: F6

12: F6a

4. Click Utilities > Sets > Subset,then clickDelete, thenFault, and picktheCPS set namedmm_Tarbert.

• Select subsets 3, 9, 10, and 12

• Click Apply, thenCancel.

5. At this point, we will decidenot the use the Tarbert wells because ofthe bulls eyes we see in the final map. We will also decide to makeof another secondary data set calledmm_TARBERT_contour_interp . This data set is derived fromprevious experience, knowing that in the lower right-hand corner of tmap, we will have crossing grid problems with the Ness horizon unlewe control this part of the Tarbert horizon, which is so lacking in da

6. Erase the screen and re-grid theTarbert grid usingSingle Surfacegridding as before, except change theInitial Grid Interval to500.0m. Remove the wells from the input data and instead use themm_TARBERT_contour_interp data set as the second data set.

7. Select theCPS Fault boundary setmm_Tarbert , as before.

8. When the gridding finishes, color-shade the contours, setting thecontour interval to “computed”, and you should see a map similar tthe one below.



ned.and

r this the

s

ay

lier

e

There is still an area in the East edge of the map where the grid is not defiIn this case, the reservoir which we will be modeling does not exist there, so we can leave the grid defined as it is.

We also note many parts of the fault zones are not defined. The reason fois that there was no data explicitly provided to model them. To complicatesituation, there were many horizon interpretation data points which wereincorrectly left inside these zones by the interpreter. During gridding, thealgorithm used them with the result that you see - badly defined fault zonewith holes in them.

Now let us finish the first section for this Tarbert horizon by showing one wto correctly handle the display and modeling of the fault zones.

Here is thestrategy we’ll use:

• Smooth the grid to get rid of the high frequency noise we noted ear

• Blank out all fault zone values in the Tarbert grid

— Since blanking can only be done with a polygons, we’ll first havto copy the fault traces (which surround the fault zones) to apolygon set.

• Fill in the blanked-out fault zones by using the grid itself as “data”



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 andits fault boundary set as input. ClickOK .

10. Choose a convergent threshold of 2% and clickOK . This will removethe 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 byimproper and incomplete data, the first step will be to simply blankthem out in the grid.

• Click onUtilities > Sets > Copyand copy the Tarbert fault set to apolygon set of the same name.

— In theCopy Sets dialog box, toggleFault [F] to red.

— Selectmm_Tarbert , and clickCopy.— In the next dialog box, selectPolygon for Output set type and

provide a newOutput Set Name of mm_Tarbert , then clickOK .

— In theCopy dialog, clickCancel to exit the copy procedure.

12. ClickOperations > Grid > Blank to open theBlank a Grid dialogbox.

• For Grid (input) , selectTarbert .

• For Polygon (input), selectmm_Tarbert , and clickOK . Thisopens theBlank a Grid dialog box.

• SelectInside only as theCalculation mode, and clickOK tobegin the blanking.

13. Erase the screen and color-shade the Tarbert grid as before.



whatey

as

s in

ll

ed to

We now have a grid which is representative of the data. It has been someextrapolated in certain areas, and the fault zones have been blanked. If wwere only creating structure maps using limited extrapolation, we might sathat the map is finished.

In this class, however, our workflow extends all the way to volumetrics, andthe instructor has explained, this will require us to fill in the fault zones foreach horizon in the structural envelope so that we do not end up with holethe isochore grids

Filling in Fault Zones for Tarbert Horizon

There are actually several ways to fill in fault zones, but the one presentedhere is the most direct and requires the least amount of extra data. We wisimply use the grid itself as “data” to re-grid the entire horizonwithout thefaults, since the fault blocks have already been very well defined. The gridnodes 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 neto fill in the blank areas. When we re-grid in this manner, we’ll also choosedo a little more extrapolation on the fault blocks towards the East, as well.

1. From theSingle Surface Gridding dialog box, re-grid the Tarberthorizon as follows:

• UnderData, select the Tarbert grid as the onlyData set.



fine

ill

• ToggleFault andPolygonto gray.

• SelectConvergent from theAlgorithm pop-up list, and set theInitial Interval to 200. This is the approximately half the largesthorizontal displacement exhibited by the fault patterns in thishorizon. It is the largest distance between data points which dethe “holes” in this data.

• Click theAdvanced button, and verify thatNumber of Nodes tosnap to is 16. and select theDeterministic weight function andModerate damping.

• Click OK to return to theSingle Surface Gridding dialog box.

• UnderSurface, selectTarbert again.

• Click OK to start the gridding, replacing theTarbert grid with anew version.

Because we created this version of the gridwithoutusing the fault boundaries,the grid willnot be automatically associated with a fault set. Therefore, weforce the association before we contour.

11. ClickUtilities > Sets > Associate_Set_With_Grid. Identify theTarbert grid and its associated fault set,mm_Tarbert , then clickOK .

12.Erase the screen, and click onDisplay > Contours and contour theTarbert surface.



ny,
If you like, you can color-shade this new grid to verify that there a few, if aareas which are not defined.


the

ed

e

areust

ural

Grid the Ness Horizon

Using the same procedures as for the Tarbert, create a smoothed grid of Ness horizon where the fault zones are filled in and the grid has beenextrapolated all the way to the edges of the map. The seismic data is nammm_Ness_Depth_intrp, the well data ismm_NESS_Depth_wmrkr, and thefault boundaries aremm_Ness. Fault subsets 1 and 8 should be deleted in thmm_Ness fault set before gridding. Try aStarting Grid Interval of 400 forthis data set. Note that the well data and the seismic data in this data set not calibrated, and so you may want to use only the seismic for gridding, jto get a smoother overall map for the class.

When finished, your map should be namedNess, and should resemble the oneshown below:

We now have three of the several components we need to build the structenvelope for the lithozone between the Tarbert and the Ness horizons. Inparticular, we have the unconformity grid,Bunnkritt , and the two horizongrids below it- theTarbert and theNess.



re
We’ll take a break from modeling activities for a moment to learn a little moabout Basemapping and ASCII file input in the next exercises.



Chapter 14Contouring, Colorshading, and More

• • • • • •Basemapping

Overview

In this chapter we will look at more options available for basemapping. Wewill introduce you to colorshading, and demonstrate many of the graphicparameters which we did not take the time to discuss during the gridding.


Contouring, Colorshading, and More Basemapping Schlumberger

ny

e

y are

ap

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 othe screen will depend on the scale defined for the currently active Displaenvironment.

During screen display,CPS-3 first creates all graphics in a manner and scalappropriate to the size of the plot you have specified in your Displayenvironment. It then renders a smaller version of this on your workstationscreen.

Thus, rendering of character sizes, symbol sizes, and even contour qualita function of thephysical size of the plot you specify when you scale yourDisplay environment. There are three modes by which you may set the mscale –Ratio, Direct, or NoScale.

You specify the plot to be this big andpick graphic sizes appropriate to this

CPS-3 then “miniaturizes” this

picture and puts it on your screen.

PlotSize


Schlumberger Contouring, Colorshading, and More Basemapping

ds forthe

on the

rspect

h or

in

es,

ller

e theh

When you select eitherRatio, orDirect scaling methods, you have the abilityto define a plot size of your own choosing, for example, 18 inches for X an22 inches for Y. This means that if you select a text size of, say, .25 inchecontour labels, then they will be .25 inches high when the map is plotted atspecified size. On your screen, the text will be smaller since the workstatiscreen always presents a miniature version of your scaled map, except inrare case when you specify a plot size which is actually smaller than yourworkstation screen.

When you selectNo Scale, CPS-3simply assumes a default maximum plottesize of 12 inches by 12 inches, then scales everything and maintains the aratio accordingly.

English and Metric Units

Even though your sets inCPS-3 are stored in meters or feet, you have maychoose to specify character sizes and other graphic dimensioning in EnglisMetric notation. This is determined by theGeoGraphic Distance attribute inthe GeoFrame Display Units which is managed from theProject Managerdialog.

When you select a particularGeoFrame Display Units definition in metricunits, for example, then graphic sizing and scale specification will be donemetric units.

Rendering

No matter how you actually specify the size of your paper plot,text sizing,andsymbol sizing, will be relative to that plot size, as shown in the previousdiagram. Stated another way - if you set a posting symbol size of .25 inchthe symbol will be .25 inches high on the final map, not .25 inches on theworkstation screen.

When you selectcontour quality, the system attempts to tie the selectedquality specification to a measurable result on the physical plot. This isaccomplished by refining the contoured grid to levels which will cause smaand smaller contour line segments. If time permits, the instructor mightprovide a basic description of the contouring algorithm at this point., but thbasic fact is that refining the grid before generating contour loci will causeindividual contour line segments to become smaller. Below is a table whicmaps Contour Quality to Refine Grid Cell Size ininches.



s

nd

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 of0 will cause contouring of the grid with no refinement.

Note that in later versions of the software, this feature may work slightlydifferently, but the on-line Help is always available for current details.

Time of Execution for Contour Generation

The contouring algorithm inCPS-3is both fast and accurate; however, factorwhich 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 amore contours are slower)

• Contour Quality (higher quality is slower)

Map Size

• For a given grid and a given Contour Quality, smaller plot sizes willcontour quicker than larger ones.



nes

the

Guidelines to Optimize Contouring Speed• During interactive sessions not involving hard-copy plots, specify a

scale for your Display environment which yields aplot size that fitswithin a 12x12 inch space.

• When contouring, begin with a Quality ofZero. Your grid may be fineenough so that Zero Quality provides adequately smooth contour liwithout having to resort to refinement.

• Try contouringwithout labels for modeling work. They tend toobscure the shape of the structure in some cases, and you can putlabels on later, when you want to generate presentation maps.

• Use aContour Increment which is reasonable. Extremely finecontour increments can generate contour displays which sometimeappear to “sculpture” the surface, but take a long time to generate.



the

ExerciseExercise

Understanding Graphic Size Parameters

In this exercise, we will learn how plot size affect the size of characters onscreen. The assumption is that theGeoFrame Display Units are stillMetric/Charisma .

1. Click theSelect Environmenticon. This opens theSelectEnvironment dialog box.

• Verify that theGullFaks_Gridding Display environment is stillactive, highlight it, and clickEdit Current under theDisplayEnvironment panel.

Changing Map Scale Mode

• In theHorizontal Scalesection, setMap Scaleto 650 Direct(m/cm). The computed plot size should be 9.1 x 11.7 cm.

• Click OK , returning to theMain menu.

2. Erase the screen, and clickDisplay > Contours

• SelectNess as theSurface.

• ToggleDisplay Line Contours to red and clickSet 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.



d inasler

y

s

g

Placing a border on the plot shows the physical size of the Displayenvironment as rendered on the screen. It should be very close to 9.1 by11.7cm, or about 3.6 by 4.6 inches, which corresponds to the size specifiethe Display environment. In this case, text size on the screen is the same what you have specified in the parameters because the “plot size” is smalthan the screen, and the system does not have to shrink it.

4. Now, return to theSelect Environment dialog and again edit theGullFaks_Gridding Display environment.

• Change theHorizontal Map Scale Mode to beDirect, and theScaleto be120meters/cm. Striking the <Return> key will cause anew Resulting Map Size to be displayed. This should be 49.2 b63.3 cm.

• Click OK back to theMain menu, discarding any existing graphicon the screen.

5. Contour the Ness grid as before, not changing any of the contourinparameters.

About 3.6 inches on the screen

Text is about1/4 inch high



ort

on

Two things have happened simply by changing map scale:

1. The physical size of the plot no longer fits in the workstation viewpand so the system has shrunk it to fit.

2. The same text size (.5cm) has been rendered to show how it wouldlook on the plot with the specified size, therefore, it appears smallerthe workstation screen.

• Now return again to theEnvironment dialogs and change the mapscale for theGullFaks_gridding Display environment to250meters/cm.

• Recontour theNess grid, changing the following contourparameters:

— Distance to First Label = 1

Text is about1/16 inch high

About 6 1/4 inches on the screen



— Distance Between Labels = 20

— Contour Label Size =.35.



f the

ExerciseExercise

Contouring a Single Z-value

1. Erase the scrren and contour theNess grid as follows

— setStart contour level= 1800— set Increment between contours = 1— set Number of contours = 1— setMap quality = 0— setLine width for normal (non-bold) contours = #3— toggleNo bolding to red

— toggle No blanking to red

— toggle No labeling to red, and clickOK .

This shows the locus of the 1800m contour lines against the background ofault patterns.

• Now bring up the contour menu again, and clickHelp. Point toseveral parameter fields and make sure you understand themeaning of the parameters.

• Experiment with the other contouring parameters, such asBoldingrate, Contour label rate, andDistance to first label.



Color Shaded Contours

1. Erase the screen, and clickDisplay > Contours.

• SelectNess for Surface.

• ToggleDisplay Line Contoursoff

• Toggleon Display a Shaded Grid, and clickSet Parameters.This opens the followingParameters for Color Shaded Contoursdialog box.

— Set the first three parameters toComputed.

— SetX and Y Resolution to .25 andGrid Refinement to .2

— Make sure thatColor palette is set toRainbow.

— SetInvert palette to Yes.— Click OK to close the dialog box.



• ToggleonDisplay Faults and clickSet Parameters. This opens theParameters for Displaying Faults dialog box.

— SetLine color = black

— SetSymbol Size to 0.

— SetAnnotate Names andAnnotate Z-values to No

— SetFault polygon fill method = No Fill— Click OK back to theMain menu to start the color-shading.

• Go toDisplay > Basemap to setBorders and Labelsaround the map.



X
This is a medium-to-high resolution shaded contour map. By reducing theand Y resolutions and the Faulted Cell resolution, quicker maps can begenerated.
Make Room for a Color Bar

1. Click Display > Display Functions > Set General DisplayParameters to open theGeneral Display Parametersdialog box.

2. In theSet Screen Display Marginsection, set theLeft margin to 6and theRight margin to 2, and then clickOK.



e

Display the Color Bar

1. Click Display > Color-shading Palette to open theDisplay ColorTable dialog box.

— SetMethod of positioning color table to Use cursor.— SetLabel text size to .3.

— SetLabel text color to black.

— SetLabel text font to 5.

— Set Label text quality to Filled, and clickOK . UseMB1 to placethe color bar next to your map display. Click and hold to define threctangle, then click again to verify.

2. Put a bold, black border around the map, but no labels.

3. Save as a new map set calledNess_shade, and erase the screen.



ping

ExerciseExercise

More Basemapping

We will finish this exercise by creating a map using some of the basemaptools which we have yet not tried.

Return to GullFaks_Overview Display Environment

1. Go toDisplay > Display Functions > Set General DisplayParameters,— setLeft margin to 1— setRight margin to 4— click OK to return CPS-3 Main Module

2. Go to theSelect Environment dialog and activate theBetter_GullFaks_Overview display environment.

3. Click theDisplay basemap icon to open theBasemap Displaydialogbox.

• ToggleonMap Set and selectNess_shade from Pick Sets.

• Click Apply to display the map.

• Toggle onBorder.

• ToggleonLabels and clickSet Parameters.— SetX: label size andY: label size to .2.— SetX: label increment andY: label increment to 5000 .

— Click OK .

• ToggleonMap Title and clickSet 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 .



cs

• Set Additional Parameters

— ToggleonX,Y Grid Lines and Tics and click SetParameters.

— 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 .

• ToggleLat/Lon Lines and Labels and click Set Parameters.— Set first six parameters toComputed— 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 theBasemap Displaydialog box. Your display shouldlook similar to the following figure, which shows some of the graphioff the workstation screen. We will remedy this in a minute.



5. Back in theBasemap dialog, toggleonExtended Data and post the2D seismic location set,mm_2d_gullfaks_shtpt, just as we did for theprevious basemap. ClickOK .

6. Click theReveal all graphics icon to expand the x,y box.

7. Click onUser/Show_Environment to bring up the project location.Swipe the path to the project and stick it into an Xterm.

8. Click theDisplay basemap icon again.

• ToggleonTitle Block and click Set Parameters to open thedialog box. Set the following parameters:

— Caption justification point = Lower left of display window— X andY offset from justification point - toggleon Position

with cursor— Caption scale factor =.5— Click Select file, then blank out theFilter text field, and

replace it with the path to yourCPS dsl swiped from the Xterm

— Add “/*.cst ” to the end of the path and press <Return>.

— Choose the caption fileschlum_title.cst, and clickOK .



— Click Enter title block field values at the bottom of theCaption Information dialog to open theDraw a Title Blockdialog box.

In the following figure, you see theinformation in the title blockfields which you want displayed on your map.

In the next figure, you see thenames of the fieldswhere you enter theinformation for each of the locations in the title block.

— In theDraw a Title Block dialog box, enter the appropriateinformation in the text entry fields. For example, in theAuthortext entry field, enter your name; in theMap Title text entryfield, enter Top Of Ness , and clickOK .

— Click OK again, and clickApply.

Top of Ness

Depth/M



— When the cursor becomes a“+” , position the title block to theright of the lower right border corner, even with the lowerborder. UseMB1 to position the block, then click it again toaccept the location. If you want to reposition, click therightbutton and start again.

9. In theBasemap Display dialog box, selectProjection Block, andclick Set Parameters.Set the following parameters:

— Caption justification point = Lower left of display window— X andY offset from justification point - toggleon Position with

cursor— Caption scale factor = .5— Click OK .

— Click OK to close theBasemap Display dialog box.

10. Position the projection block similarly to the title block, in a locationof your choice.

11. Add ascale bar as before.

Your display should now resemble the one below.



12. Click theSave currently displayed mapicon, and save the display toa new map set calledNess_Overview .


ion”

’ll

Chapter 15Demonstrate Inverse Interpolation and

• • • • • •Control Point Arithmetic

Overview

The purpose of this chapter is to demonstrate the use of “inverse interpolatand “control point arithmetic”. The workflow will involve computing theerror , if any, in the Ness structure grid at certain marker locations which weload from an ASCII file shown below. The file containsWell Name, SymbolCode, and Symbol Color information as well asX, Y, Z data.


Demonstrate Inverse Interpolation and Control Point Arithmetic Schlumberger

ode

ate.

Display Ness_tops

1. Clear the screen and go toDisplay > Select Environment to verifythat the activeDisplay environment is GullFaks_Gridding .

2. Click Display > Basemapand toggle on Extended Data.

3. SelectNess_tops, and clickSet Parameters.

4. Click Set Parameters, and set the parameters shown below:

• ToggleSymbol Parameters to red

• Click theSymbol code icon which reveals the symbol code tableshown below.

Note that the symbol you pick in this case represents only thedefaultsymbolbecause the symbol codes were already loaded in thisparticular data set. However, in case a well did not have a symbol cin 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 appropri


Schlumberger Demonstrate Inverse Interpolation and Control Point Arithmetic

6. Toggle theText1 field to red. This will be the well name. Chooseappropriate parameter values.

7. When finished with theparameters dialog box, clickOK to close it

8. Click OK again to begin the display.

9. When the wells appear on the screen, use theRubberband zoom-inicon to view details of a few of the wells.

10. Click theUn-zoom icon , and return to the full area of interest.



e

t

ExerciseExercise

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. Wwill now learn something aboutinverse interpolation as we see how differentthe Ness grid is from the Ness_tops Data set.

1. Click onOperations > Control Point > Interpolate from Grid toData, to open theCompute data from a Grid dialog box.

• SelectNess as theGrid . Notice that the correct Fault boundary seautomatically appears.

• TogglePolygon to null .

• SelectNess_tops as theData set, and clickOK .

2. In the ensuing dialog box, toggleonResults to new Z Field, and typein grid_value in theSelection box.


Schlumberger Demonstrate Inverse Interpolation and Control Point Arithmetic

t.ee

le

3. Click OK to begin the calculation.

This operation will create a second z-field in the Ness_tops data seFor each well in the data set, the second z-field represents the valufrom the Ness grid, while the first z-field represents the original valu(pick) from the ASCII file.

After execution, note the statistics in theCPS-3 Status Informationwindow, and note the z-range of the second z-field,grid_value.

4. Now clickUtilities > Sets > View_Contents_Statistics.At the top ofthe next dialog, clickList Contents, toggleData to red, then select thedata setNess_top, and clickOK .

5. In theCPS-3 Status Information window, down near the bottom,click the cursor in the long white box labelledEnter Response.Leaving the cursor in the box, type the number: 100 .

What you see is a listing of all stored data for the data setNess_tops.Across the page you see sequence number, X, Y, original Z, grid Z(which we just calculated), symbol code, symbol color, and borehoname for each well.

Note that some of the grid Z values are null (INDT ). These are wellswhich fall outside the area of the grid, and a value could not becomputed.



a

Use Control Point Arithmetic to Compute Difference

6. Click onOperations > Control Point > Control Point Math.

7. SelectNess_tops as theData set, and clickOK .

• For theAlgebraic expression enter @z2-@z1

• ToggleonResults to new Z Field

• Enter the nameerror in theSelection text entry field, and clickOK .

8. Look at the statistics which appear in theStatus Information windowagain, and see therange of the error.

Note that this error can be mapped and its distribution displayed. There issystem macro for this purpose called Show_Error.mac.


tical.

nted

elow.

Chapter 16

• • • • • •Fault Surface Operations

Overview

In this chapter, we will turn our attention to another step in the workflowwhose culmination will be the computation of oil in place in a reservoir

Figure 16.1 Sealing Faults

In those cases where a reservoir is bounded by sealing faults, it will benecessary to make grids of the fault surfaces, unless they are actually ver

We have already discussed the importance of defining the fault zones whevolumetrics is the workflow focus, and we should have already accommodathis requirement when gridding the top and base structures as depicted b

Fault A Fault B

O/W


Fault Surface Operations Schlumberger

ultssedhesopot

lingbase

ereno be

We are careful when creating grids to be used in volumetrics to define all fazones in each horizon. There are many techniques for doing this as discuin a previous chapter, and not all of them require an actual fault surface. Tdefinition, during gridding, of all fault zones should be done for volumetricwhether there are any sealing faults or not. It simply guarantees that the tand base envelope will be continuous and that the resulting isochore will nhave any holes in it due to undefined fault zones

Creating Fault Surfaces

In this chapter, we continue with modeling requirements in the case of seafaults, where one or more fault surfaces must be integrated into the top orenvelope, or both.

The technique is to simply define the fault surface as well as possible withwhatever 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 thare when gridding any data. One of the differences between typical horizointerpretation data and fault interpretation data is that the fault data tends tsparser and of a lower quality. For this reason, it is not always possible toobtain a good model of the fault on the first iteration.

Horizon 1

Horizon 2FaultZones


Schlumberger Fault Surface Operations

ou you

d

re isen

tie

all

ces

so

h,

ut it

Try the Convergent algorithm first, or any other algorithm you choose. If ylike the resulting grid and it honors the data, then that’s probably as far asneed to go.

In the GeoQuest modeling system called Framework 3D, faults are griddemany at a time, and a specific algorithm is used there which has a highprobability of creating a good grid on the first try. This algorithm can be“duplicated” by several CPS-3 procedures and embodied in a macro. Theanother algorithm which has already been put into a macro which uses evanother technique. Both of these are discussed below.

Both of these techniques work well for. Be aware the output grid may not to all of the data points, but it works well for fault input data which is eithervery 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 forfault data sets, but which is a very useful alternative toConvergent gridding.The origin of this gridding technique is the realization that most fault surfahave strong linear components in the direction of dip. With typically sparsedata, strong linear trends are not always honored by theConvergentalgorithm, nor ingrained in the fault cut data set.

This particular technique is directly available in the CPS-3 set of Systemmacros. It’s called “GridFault”. Here is an outline of how it works:

• Create an initial 2nd orderTrend grid from the fault data points.

• At all data point locations, compute thedifference between theTrendsurface and the z-value in the data point.

• Subtract the two values, creating a new z-field calledError .

• Create a grid of theError andadd it to the initialTrend grid, givingthe final grid which contains a strong fault-like trend downdip, but alties to the observed data.

• Display thecontours for the fault grid

• Display the originaldata points for the grid.

Slope Method

In FW3D, a new fault gridding algorithm for GF4.0 has been installed whicin most cases, gives better results than theTrend Method. It may not be in theCPS-3 set of System Macros, depending of the version of your software, bworks like this:



ntd

nal

• Use the data you have to create a fault surface using the Convergegridding algorithm for a grid which is 4 times a coarse as the desirefinal grid size.

• Use the Control Point operations to compute slopes at all controlpoints so that you have an augmented control point set containingX,Y,Z,dZ/dX, dZ/dY.

• Use the augmented control point set to create the fault grid at the figrid size.



ond

ththe

umed

Now, let’s review the geometry of the Gullfaks faults and horizons, decide the location of the reservoir to model, and grid those fault surfaces we neefor incorporation into the structural envelopes.

GullFaks Fault Patterns

In general, the Gullfaks horizons are tilted fault blocks having fault zonesrunning North/South. Higher horizons contain numerous erosion zones wicorresponding lack of data. Below are some representative fault patterns inarea we are mapping.

In the figure below, we see a schematic East-West section through an assreservoir area.



other

For the volumetric exercises, we will focus on the interval between theTarbert and theNessbetweenFault 2 andFault 4, which we will assume aresealing faults. Notice that the top envelope of the reservoir is defined by bthe Tarbert and, in its erosion zones, by the Bunkritt unconformity. In a latchapter, we will also introduce the oil/water contact.

In this exercise, we will create the grids for Faults 2 and 4.

BunnkrittUnconformity

Fault 2 Fault 4

Tarbert

Ness



r

” and

ExerciseExercise

Load Fault Segments (Cuts)

1. In theCPS-3 Main Menu, click on theGeoFrame Link icon:

.

2. Click Controls, and highlight all surveys.

3. Click Data Types. In the next dialog, underContainers, selectFaults,and underRepresentations, selectFault Cut Sets, and clickOK .

4. Click GeoFrame Data,and in the next dialog, set theVerticalDomain to Depth.

5. In the left panel, select theF2 fault. You may see several items appeaunder theRepresentations panel on the right, buthighlight only therow sayingFault Cut Set.

6. Click F4 in the left panel and on the right, highlight the row sayingFault Cut Set, then clickOK .

7. Back in theGeoFrame Link dialog,highlight both of the items in theright panel, and then clickRun.

These sets will be stored in the CPS-3 dsl as data sets named “F2_Depth“F4_Depth”.



youe

lts

ExerciseExercise

Inspect Fault Data Points and Create Fault Grids

1. If you like, display the fault cuts for the F2 and F4 faults. As seenbelow against the background of the three surveys we have used, can see that each runs North/South with F2 on the left and F4 on thright. It is not necessary to replicate this figure, only display the fauin your currentDisplay environment.

Creating the fault grids

At this point, we will introduce you to the concept ofmacros in CPS-3. Wewill grid these two faults using apredefined macrowhich embodies the faultgridding technique which was discussed in the reference material for thistopic.



antted

.

In a later chapter, you will learn how to create macros. Here, we simply wto introduce you to how they can be used. The macro you will run was creain CPS-3, then modified by addingMacro Command Language, whichallows prompting, substitution, and other useful features inside of macros



iss

ExerciseExercise

Run the Fault Gridding Macro

1. Click theSelect environment icon, and set both theModeling andDisplay Environments to gullfaks_gridding.

2. AnswerDiscard andDo not clip to the change of environmentmessage.

3. Delete the data set namedmacwork, if it exists.

4. Click Macros > Execute and toggleonShow System Macros.

5. Click on the list widget next to it, and selectFault Gridding . This willcause the macro namedGridFault.mac to appear under theMacrospanel. Highlight it, and you will see the description of the macro. Thmacro represents one of several methods for gridding fault surfaceand seems to work well with the data we have.

6. Click OK to start the macro

7. When theSelect a Data Set dialog pops up, select the data setF2_depth, and then clickOK .

8. When theType output surface name dialog pops up, type in thename: F2_fault .

9. When theEnter an slm... dialog pops up, enter2500.00, andthe macro will begin execution. When finished, it will display thecontours for the fault grid and the data points as below.



t the
This is a reasonable-looking fault surface and so we’ll continue and repeamacro for the second faultF4_depth. Specify an output name ofF4_fault ,and anslm of 2500 .
F2_fault

F4-fault



e. Ite

Establishing Set Attributes for the Fault Surfaces

Macros do not always establish the set attributes for grids which they creatis up to the macro’s author whether or not it is done, and the macro that wused to create these surfaces does not. This will give us the opportunity toshow how to set attributes in theSet Managerdialog.

1. Click onUtilities > Sets > List_Manage_Sets, and set the filter so thatonly grids are listed.

2. Highlight theF2_fault grid, and click on the “i” icon (information)which also allows editing of set attributes.

3. ToggleonReplace All at the top

4. ChangeSurface from Unknown to Fault

5. Pick theSurface Name “F2” from the list

6. SetProperty Code to Depth

7. SetZ-Unit to meters, and then clickOK .



8. Repeat this process for theF4_fault surface, but chooseF4 as theSurface Name




toip

s

Chapter 17Visualizing Relationships Among

• • • • • •Surfaces with Cross-Sections

Overview

In this chapter, we will continue with our modeling work and introduce youa simple quality control tool which is useful for understanding the relationshbetween two surfaces.

We will discover something about the Ness and Tarbert horizons, and willhave to make some adjustments in the Ness.

We will also discuss the procedure for generating traditional cross sectionusingCPS-3, which are useful when trying to understand the spatialrelationships among many surfaces.


Visualizing Relationships Among Surfaces with Cross-Sections Schlumberger

very

k of

as theny

aterid

.

ExerciseExercise

Determine If the Ness and Tarbert Surfaces Cross

Geologically, the Tarbert and the Ness are separate events and their gridsshould not cross. We worry about this for two reasons:

1. Relative to their grid spacing (50m.), the Ness and Tarbert are not far apart (about 100m), and have many faults.

2. Both horizons have missing data areas caused by erosion, or by lacseismic definition.

We want to see if theextrapolation which occured during gridding in thosemissing data areas is reasonable, Since we intend to use these horizons basis for the top and base of our reservoir envelope, we want to remove aareas which might cross.

To begin this quality-control procedure, simply subtract the two grids to crean isochore. Then color-shade only the negative portion of the isochore gwhich, if we subtract the Tarbert from the Ness, will reveal where the Nessdeviatedabove the Tarbert.

Use Multiple Surface Arithmetic Operations to Subtractthe Grids, then Display Overlapping Areas

1. Click Operations > Grid > Multiple_Grids > C=A–B— For grid C, create a new set calledDiff

— For grid A, select theNess grid

— For grid B, select theTarbert grid

— Click OK

2. Click Display > Contours— Select theDiff grid

— Un-selectFaults— ToggleonDisplay a Shaded Grid, and un-select all other options

3. Click Parameters besideDisplay a Shaded Grid


Schlumberger Visualizing Relationships Among Surfaces with Cross-Sections

elow.

uld.

adeltlackate

— setStart Contour Level = 0.

— setIncrement = –10— setNumber of Contours = Computed, and then clickOK .

After displaying a border and labels, your msp should resemble the one b

Note that most crossings occur where the fault zones of the two horizonsoverlap. This is an indication that the interpretation along these zones shoprobably be improved, since these horizons are already so close togetherWhen horizons are so close, this is also an indication that a more rigorousmethod of filling in the faults zones might be required.

The larger crossings in the corners of the map occurred even though we muse of some digitized contours to control the Tarbert horizon, which we fewas diving too steeply to the Southeast. These crossings are all caused byof data in one or the other of the horizons and might be mitigated somewhby more careful interpretation, some data editing, and some changes in thgridding parameters.

In order to move along quickly, we can apply aglobal type of remediation tothis problem which is already available in a macro.



llerd to

:

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 wherethe lower grid is above the upper.

This macro was designed to remove discrepancies which were much smathan the ones we have, but in this training environment, the data is designedemonstrate principles of operation.

Conform the Ness Grid to the Tarbert Grid Where TheyOverlap

1. Click Macros, and toggleonShow System Macros

2. Select the macroConform_to_Upper.mac, and clickOK .

— Pick Upper Surface = Tarbert

— Pick Lower Surface = Ness

— Pick newOutput Surface = Ness_conformed

— Pick newOutput Boundary = Ness_overlaps

When finished, you’ll see a display of theNess_overlaps boundary set, aswell as a color shaded map of theNess_conformed.

After finishing with this macro, we’ll use the dialog inUtilities/Sets/Associate_Set_with_Gridto associate the fault set,mm_Nesswith the gridNess_conformed.

One final step remains, and that is to give theoutput grid a finalsmoothing.This is recommended, but it is not part of the macro we ran.

3. Click Operations > Grid > Smooth,and set the following parameters

— SetInput Grid = Ness_conformed— SetFaults = mm_Ness— SetPolygon = null— SetOutput Grid = null— Smoothing Operator = Biharmonic— Max # Passes = 1, and then clickOK to start the smoothing.

The output grid should resemble the one shown below.



We will leave it you to verify that the overlap zones have diminishedconsiderably by inspecting the z-range of thediff grid which you canrecompute by subtracting theNess_conformed grid from theTarbert .

4. Now delete theNess grid, and rename theNess_conformed grid toNess.



ExerciseExercise

Examine Relationships among Horizons and SealingFaults

We would like to inspect the interrelationships among theBunnkritt , theTarbert , and theNess horizons, as well as the two sealing faults,F2 andF4.By using profiles baselines which cut the map area at the top, bottom, andalong a diagonal, we should be able to get a good idea of the spatialrelationships among these grids.

Digitize Profile Baselines

1. Erase the screen and from theCPS-3 Main Module, click Display >Select Environment.

2. Select theGullFaks_Gridding environment.

3. Clear the screen and display aBorder with Labels. Use a labelincrement of2000.

4. Display themm_Tarbert Fault set.

5. Click Digitize > Polygon— ToggleonScreen digitizingand clickNew.

— EnterBaselines as a newPolygonsetName. SetSurface Typeto Unknown

— ToggleAppend off

— Set theEcho color to Black, and clickOK .

6. Click No to Close polygon?, and then clickOK .

7. TypeUpper_EW for the polygon name, and clickOK .

8. UsingMB1, click the first point in the polyline on the left border atapproximatelyY = 6790150.Click the second point at the same y-location on the right border. If you need to delete a point, clickMB3,



.

, the

then clickDelete on the menu. Repeat as many times as necessaryAfter the second point has been successfully digitized, clickMB3,thenFinish in the dialog which appears.

9. AnswerYes to Create another subset? Give the second polyline thename Lower_EW, and in a similar fashion as above, digitize a linefrom left to right at approximatelyY = 6786200.

10. AnswerYes to Create another subset? Call it UL_to_LR , and in asimilar fashion, digitize a baseline from the upper left corner of themap to the lower right corner as shown in the map below.

12. AnswerNo to Create another subset? to stop the digitizing.

13. Erase the screen, display the fault setmm_Tarbert , and the polygonsetBaselines.

Note that when these baselines are used in the profiling procedureleft side of the profiles corresponds with thefirst point digitized.

Y = 6790150

Y = 6786200



Establish Z-scale Attributes in the Display Environment

Before we move on to the2D XSectiondialog boxes, we will first make surethat the x,y scaling and z-scaling is set up properly in the current Displayenvironment, or we will never see our cross sections.

1. Bring up the Display environmentGullFaks_Gridding for editing.

Below, you can see which fields in this dialog will affect our profiledisplay:

2. For theX-section horizontal scale, enter100.0 Direct scale

3. For theX-section vertical scale, enter50.0 Direct scale.

4. Click OK back to theMain menu.

This is how you set the horizontalscale along the baseline for yourcross sections.

This is how you set the Z-scalingfor your cross sections. ExaggeratedHorizontal is a linear multiplier of thebaseline scale above, left.



ll

he

Create Profile Displays

Now, we will return to theCPS-3 Main Moduleand set up for the crosssection displays.

1. Click onDisplay > 2D XSectionto open the dialog box.

— ToggleXSection Method = Quick

— Pick thePolygon/Baseline set = Baselines

— ToggleExtract Method = Normal baseline

— Click on SimpleBaseline Method.

— Click onSelect All, which selects all baselines in the set, and wicause 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 canAdd each grid separately, or highlight all at once by using t<Control> key as you pick.

4. Click Secondary Option.— ToggleXSection Type = Normal/Structural— ToggleXSection Mode = Prohibit: Clip...— ToggleInvert Z-Axis = On



e

— Click onSet General Display Parametersand set theLarge TextSize =2.,Small Text Size =.1, andSymbol Size =.2 ClickOK .

— Click onVertical Profile Limits and set theAxis Limitation to“XSections”, thenOK .

— Click Primary Options to return to the top dialog.

1. Click OK to start the profile display, and clickNo to Save Graphics?

Your display should resemble the one above.

7. Click Zoom Profile in the small dialog associated with the profiledisplay, and zoom into upper right corner, and other parts of thedisplay.

8. Click Do Next Profile to see the profile for the next baseline, then thnext, and clickClose to exit.

9. Restart the profile display

— UnderSecondary Options, click Vertical Profile Limits , and settheAxis Limitation to Manual, typingZ-minimum = 1000 andZ-maximum = 3000.

— Click OK , thenPrimary Options, thenOK again to redisplay theprofiles.






ptness

ustast

te an

oil

pe. of

Chapter 18

• • • • • •Creating a Volumetric Envelope

Overview

The first step in computing oil in place within an interval is to define the toand the base of the oil-bearing rock. If the top and base horizons were flasurfaces, cleanly defined across the entire area, then the gross rock thickcould be computed by simply subtracting the two surfaces. However, we mconsider the common case where both of these surfaces intersect, or at leonlap or baselap an unconformity or other bounding strata. In addition, wewill also consider the common condition where a fault surface seals theenvelope along one of its boundaries as well. These surface-to-surfaceinteractions mean that we must perform other mapping operations to creaenvelope which surrounds only the oil-bearing rock in this interval.

Since we must also account for the presence of water and gas within thestructural envelope, one of the last steps will be the integration of the gas/and oil/water contacts into the final envelope.

Here, we will outline all the steps required to compute a volumetric enveloThese steps should also work for any reservoir that you encounter outsideclass.


Creating a Volumetric Envelope Schlumberger

ation

d to

rge

Recommended Sequence for Computing an Isochore forVolumetrics

The following steps may be taken when computing an oil-only isochorebetween two horizons. This procedure is designed to preserve the true locof the zero line in the isochore. Refer to“Location of the Zero-Line inIsochores”which follows.

Assumptions:

• Z-units are assumed to be indepth

• Fault zones associated with the top and base structure are assumebe completely gridded and integrated in the structure grid.

The goal of this operations is to end up with a top envelope and a baseenvelope whichcleanly intersect along their edges, butdo not overlap (arenot 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 becomputed.

2. If the top is truncated by any unconformity, or a sealing feature, methe two grids, retaining thedeeper portions of both.

3. If the top intersects a gas/oil contact, merge the two, retaining thedeeper portions of both.

Create the Base Envelope:

4. Identify the base of the interval for which the isochore is to becomputed

5. If the base is truncated by anylower surface, including sealing faults,merge the two, retaining theshallower portions of both

6. Merge the result ofstep 5with the oil/water contact, if any, retainingtheshallower portions of both

7. Subtract the top envelope, the result of step 3, from the base envelope,the result ofstep 6, which will give a final positive isochore in thereservoir and a negative isochore everywhere else.


Schlumberger Creating a Volumetric Envelope

lues

the

dero

of

Location of the Zero Line in Isochores

Isochores, created for the purpose of contouring or volumetrics, shouldpreserve the location of the zero line in the grid by containing negative vaon the other side of the zero line. This does not have to be artificiallyintroduced, since it can be a natural by-product of the process of creatingstructural envelopes. If the isochores are leftclipped to zero, as can happenwhen surfaces are prematurely truncated, it effectivelymoves the zero contourline, shrinking the perimeter of the positive isochore. The contouring andvolumetrics algorithms will both do a much better job when isochores arenotclipped. You should, however, clip isochores to zero when using them forsurface operations, such as adding them to a top or base structure.

A visual symptom of isochores which have been clipped to zero are raggecontours along the zero line. See example below which exhibits a wobbly zcontour in the north.

Figure 18.1 Isochore clipped to zero displaying ragged contour along zeroline

In this example, the clipping was not explicitly performed. It was the resultpremature merging or truncation of surfaces, as is explained below.



ee ontion.ons

est

uld

How Did the Top and Base Envelope Become Coincident?

The profile below shows a top envelope and a base envelope which are thorigin of the isochore contoured above. There is a section along the profilthe left where both surfaces are coincident. This is what is causing the flazero area in the isochore, and the loss of the true location of the intersectThe coincidence in the envelopes was caused when the two original horizwere truncated along an unconformity at some step along the way. Whilethese envelopes are geologically correct, they are not formed to gain the bresults from volumetric calculations.

Figure 18.2 Top envelope and base envelope of isochore in Figure 18.1

If the precedingPreferred Sequence of Operations had been followed, thisloss of volume would not have happened, because the base envelope wonot have been merged with the upper unconformity. Only the top envelopeinteracts with the upper unconformity.



me is

e

toets

ult

Accounting for Non-vertical Fault Discontinuities in theVolumetric Isochore

For the most accurate results involving faulted horizons, an extra step isneeded for the preparation of the fault boundary sets used during the volucalculations. Thinning of the isochore is the reason for this extra step, andshown in the following figure.A is the location of the upthrown side of thefault boundary for the Top.B is the location of the downthrown side.C andDare 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 twofaulted structure grids, is, itself, faulted, or at least discontinuous in z in thfault zones. It requires the boundary sets of both of the structure grids toseparate one discontinuous zone from another, and to allow the algorithmcompute the most accurate results. For this reason, we will prepare fault sto use during the volume calculations for both intervals. Each prepared faset will be the combination of the fault traces for the top and bottom of theassociated envelope. We will do this below with a simpleCopy/Mergeoperation for each isochore.

It should be noted that if the fault zones are large, fault surfaces shouldnormally be used as part of the structural envelope, if available, and if thefaults are sealing.



ical

we thee

illingne

s

0

e

Example of Creating a Structural Envelope

We use an example from the GullFaks field. Below is the diagram of a typsection through a reservoir. Our job at the moment is to identify thosestructural components which contribute to the TOP of the reservoir. First, recognize that the F-2 fault will become the Western edge of the BASE ofenvelope, and so this gives us a convenient starting place for identifying thtop of the envelope.

Starting just to the right of the sealing F-2 fault, at the Tarbert horizon, we wexamine each intersection which occurs, noting which of the two intersectgrids is the stratigraphicly LOWEST at the right of the intersection. That owhich is lower then becomes the upper boundary. For example the firstintersection with the Tarbert is along the 2100 g/o contact. Moving to theright, the g/o contact then intersects the Unconformity, which now becomethe boundary. Continuing on in this manner we can see that, excluding thefaults, the top of the reservoir is formed by sections of the Tarbert, the 210o/w contact, the Unconformity, and the F-4 fault.

Therefore, it is these four grids which we must merge to form the top.

Merging takes place two grids at a time, using a CPS-3 logical operationwhich will take the stratigraphicly lower value of the two grids at each nodlocation. 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, notGEOLOGICALLY. This means that you must consider theZ-units of thegrids which you are manipulating. If your units are in elevation, rather thandepth, then your choice of operation from the table below will be different.

F-2 F-4

U

Tarbert

Ness

2100

2200



ingpth,

eer:

The operation highlighted in the dialog above is the one we want for mergthe top envelope components, since we are in depth. When units are in dethe lower component will have thehigher depth values.

Luckily, it does not matter which order in which these operations occur, thresult will be the same. Let’s merge these components in the following ord

• Merge theTarbert with theUnconformity

• Merge the result with theG/O contact

• Merge the result with theF_4 fault

See each result below



F-2 F-4

U

Tarbert2100

F-2 F-4

U

Tarbert2100

F-2 F-4

U

Tarbert2100



he

gicalo

se

Now for the bottom of the envelope. We can see that its components are tF_2 fault, the Ness horizon, and the O/W contact.

In the same manner we can merge these components, using a different looperation, one that takes the minimum (higher values in depth) from the twgrids at each step. We’ll merge in this order:

• MergeF_2 fault withNess, giving the result below

• Merge result withO/W contact.

The next step, of course, is to make sure that the top envelope and the baenvelope cross at the edges, so that their subtraction will result in positiveisochore, where needed, as well as negative isochore where needed.

F-2 F-4

Ness

2200

F-2 F-4

Ness

2200



risticsthe

ir.

hem.

Below, we have superimposed the top and base envelopes.

We see that top and base envelopes cross well, but we see some charactewhich may not be what we want. We note the small negative component inisochore in the middle of the map, but realize that this will not cause anyproblems and can be disregarded. However, the top and the base of theisochore havethree areas where they arecoincident.We would like to avoidthis, if possible. Therefore, when the isochore map is created, we mustexamine the extent of these resultingflat zero areas. They may be small andinsignificant, but it is also possible that the isochore may need some repa

Let’s see how these coincident areas occurred and what we can do about t

F-2 F-4

U

Tarbert

Ness

2100

2200

Isochore

(+) (+) (-)(-)(-)

0.0



ase

all zeroe tont,

edituts

In the case of a bounding fault grid which forms one side of the reservoir, potential problem exists in the isochore. If the Fault is merged with the Bato form the bottom envelope, and the Top is left by itself to form the topenvelope as in Case A, then when they are subtracted, there will be a smzone where the top envelope and bottom envelope overlap, causing a flatarea in the isochore grid, where, instead, there should be an abrupt changnegative values. In many cases, these areas are very small and insignificabut, in others, must be addressed. One way to address this problem is to the top envelope so that it does not coincide with the base envelope, but ccleanly across it, as in Case B.

Top

Base

Top

Base

Fault

A B

CoincidentZone




er T

Chapter 19Prepare the Tarbert/Ness Envelopes

• • • • • •and Create the Gross Isochore

Overview

In this chapter, we will make use of theCPS-3 arithmetic and logical surfaceoperations to prepare the volumetric envelope for theTarbert/Ness interval.The reservoir is limited horizontally by the two sealing faults Fault_2 andFault_4. It is limited vertically by the base horizon Ness and top horizonTarbert, which is also truncated by the Bunnkritt unconformity. The oil/watcontact is at 2200m and the gas/oil contact is at 2100 m. as shown below.

Figure 19.1 Tarbert/Ness interval with gas/oil/water contacts.

Fault_2 Fault_4

2100 g/o

2200 o/w


Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore Schlumberger

hisllscesthe

dw,d.

d.

We can get some idea of the shape of the bottom of the reservoir bycontouring the base surface, Ness, at the depth of the oil/water contact. Tcontour line is shown in the figure below. We also know that the reservoir fabetween the two sealing faults, Fault 2 and Fault 4. Until we put all the pietogether, it is not clear whether the reservoir will close in the South within map boundaries.

Figure 19.2 Relationship of base of reservoir with sealing faults.

In preparation for volumetrics, the instructor should have already discussethe proper way to create a structural isochore. In the exercises which followe’ll decide which components will be used for the top of the envelope, anwhich 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 theseexercises, so that you will understand why certain operations are performeRefer to the lecture materials for this chapter.

Fault 2

Fault 4


Schlumberger Prepare the Tarbert/Ness Envelopes and Create the Gross Isochore

ids

hich

ExerciseExercise

Create Top of Envelope for Tarbert/Ness Interval

First, let’s create the contact surfaces.

Create 2200m and 2100 m Fluid Contact Grids

1. In theCPS-3 Main Module, click Modeling > Single Surfacetoopen theSingle Surface Gridding dialog box.

— Disregard the inputData text entry fields and select theConstantZ Value algorithm.

— Set theZ Value to 2200 .

— In theSurface section, clickNew.— Name the output surfaceow_2200.— Associate it with theUnknown container name, and clickOK .

— Click OK to return to theCPS-3 Main Module.— In the same manner, create the grid namedgo_2100at a depth of

2100 meters.

Create Top Envelope

Taking the lead presented in the lecture material we’ll merge these four grtogether to form the top of the envelope.

Tarbert

Bunnkritt Unconformity

Gas/Oil Contact (go_2100)

F4 Fault

We will not make direct use of theCPS-3 Logical Surface Operations as inthe lecture notes. Instead, we’ll use some easier-to-understand macros wwere designed for this purpose.



as a

ontion

Merge Tarbert with Bunnkritt using Toplap Macro

1. Click Macros > Execute, then toggleShow System Macros to red.

2. Select theToplap.mac macro in theMacros panel and read thedescription, then clickOK to start the macro running.

— SelectHorizon = Tarbert

— SelectUnconformity = Bunnkritt

— SelectOutput Grid = Tarbert-Bunnkritt; create a new grid nameand select an “unknown” Surface Type

— SelectBoundary = Tarbert-Bunnkritt; create a new boundaryname and select an “unknown” Surface Type.

3. The macro should produce a color-shade map of the result as wellrendering 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 correlatiof the eroded zones (boundaries created by macro) and the distribuof the interpretation.



Merge Result with Gas/Oil Contact

5. As before, bring up the macroExecute dialog and then select theSystemmacro calledClipTOP_at_GO.mac,which will clip the resultfrom the first macro to the Gas/Oil contact.

— SetTop Envelope = Tarbert_Bunnkritt

— SetGOC grid = go_2100

— SetOutput grid = Tarbert_Bunnkritt_2100 (Surface Type =unknown)

— SetBoundary = Tarbert_Bunnkritt_2100 (Surface Type =unknown)

The macro will generate a map similar to the one below. The whiteline close to the boundaries can be eliminated by increasing thecolorshade resolution in the macro.

Merge Result with F-4 Fault

6. As before, bring up the macroExecute dialog then select theUsermacro calleda_SealTop.mac, which will seal the top envelope with afault surface.

— SetTop Envelope = Tarbert_Bunnkritt_2100

— SetFault grid = F4_fault



y

— SetOutput grid = Tarbert_Bunnkritt_2100_F4 (Surface Type =unknown)

— SetBoundary = Tarbert_Bunnkritt_2100_F4 (Surface Type =unknown)

The deep portions of the fault surface dominate the colors in thisdisplay. Those of you who wish, can verify the accuracy of this grid bdisplaying across-section using the same baselines we used earlier.Remove the other grids from the profile except the contact grids.



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 macroExecute dialog and then select theSystem macro calledClipBASE_at_OW.mac, which will clip theNess horizon to theGas/Oil contact.

— SetBase Envelope = Ness

— SetOWC grid = ow_2200

— SetOutput grid = Ness_2200 (Surface Type = unknown)

— SetBoundary = Ness_2200 (Surface Type = unknown)



see

Merge Result with F_2 Fault

2. As before, bring up the macroExecute dialog and then select theProject macro calleda_SealBase.mac which will merge the sealingfault F_2 with the result from the first macro.

— SetFault grid = F2_fault

— SetHorizon or Base = Ness_2200

— SetOutput grid = Ness_2200_F2 (Surface Type = unknown)

— SetBoundary = Ness_2200_F2 (Surface Type = unknown)

Compute the Isochore

Now, we can simply subtract the base envelope from the top envelope to what the isochore looks like

3. Click Operations/Grid/Multiple_Grids/C=A-B— SetC = new grid named Gross_Isochore

— SetA = Ness_2200_F2

— SetB = Tarbert_Bunnkritt_2100_F4, then clickOK .

4. Color-shade theGross_Isochore grid, but only values above zero, anduse an increment of 5.0.

5. Click onDisplay > Color-shading-Palette to show the color bar.



6. Click onUtilities > Sets > Statistics and view the Basic statistics fortheGross_Isochore grid, in particular, the z-range



when ith

Prepare the Fault Traces for the Gross Thickness Grid

It is sometimes desirable to use fault traces for both the top and the base computing volumes, since the isochore, itself, has many discontinuities inwhen there are non-vertical faults present. If you want to maintain as mucaccuracy as possible, here’s how to merge these two sets.

Merging mm_Ness and mm_Tarbert Fault Boundaries

Sets are merged with theCopy Setscommand on theUtilities menu. Below ishow to merge the fault sets for theTarbert andNess into a single set.

1. Click Utilities > Sets > Copy, and toggleonFault [F] and click theFilter button.

2. Selectmm_Ness,then mm_Tarbert (holding down the <Control>key), then clickOK

3. Click New, and create a new fault set namedNess_Tarbert .

4. Associate it with theUnknown container name, and clickOK .

5. Click OK in theCopy the Set dialog box.

6. When the dialog appears again, clickPick Set, and pick theNess_Tarbert set, then back in theCopying a Setdialog, toggleonAppend To Set and clickOK .

The system copies (appends) the setTarbert to the fault setNess_Tarbert.

7. Display the fault setNess_Tarbert to see what the result looks like.






g

nd

the

Chapter 20Applying Reservoir Properties to the

• • • • • •Gross_Isochore for Oil in Place

Overview

In this chapter we will learn how to gain access to the necessaryreservoirproperty data fromGeoFrame so that we can compute oil in place accordinto this simple formula:

Oil in Place = Gross Isochore Volume* Net/Gross * Porosity * Saturation

We’ll discuss the origins of the Zone properties, as stored in GeoFrame, ademonstrate the calculation of each of theproperty grids, as well as theseries ofvolumetric grids:

• Net Isochore

• Net Pore Volume

• Net Pay

Finally, we’ll demonstrate the use of the volumetric procedure and discussreport which it produces.


Applying Reservoir Properties to the Gross_Isochore for Oil in Place Schlumberger

y of

ogs.

edn.e.

),r

d

r a

d Yne,

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 manthe reservoir properties such asporosity andsaturation. In GeoFrame, thetools required to do this are found on the Geology and Petrophysics catalApplications such asBoreView, PetroViewPlus, WellPix, Geology Office,and ResSumall help to define these property values.

Ultimately, average property values are computed byResSum for propertiesin eachlithozone. There can be many “versions” of these averagecalculations, and so they are grouped and categorized byZone Version. Whenwe compute volumes in CPS-3 for a particular interval, or lithozone, we neto make sure and extract the property values from the proper Zone VersioZone Versions allow different interpretations to exist for the same lithozonFor each property calculation within a specific Zone Version, ResSumprovides accumulations of the value based on different geometries - forexample, according to True Vertical Thickness (TVT), Measured Depth (MDand others. Where available, TVT orTVD computations should be chosen fovolumetrics.

Let’s assume that we wish to compute Oil in Place between two horizonsnamed Jakarta and Kobe. A typical GeoFrame workflow for computing therequired properties in ResSum is:

• Load the appropriatewell logs

• Create the geologicalmarkers for the Jakarta and the Kobe, either inWellPix or by loading them with theGeneral Ascii Loader

• In Well Pix, define a lithozone between the Jakarta and the Kobe anestablish aZone Version.

• In ResSum, calculate theratios and propertyaverages for the layer.

When imported into CPS-3 via the GeoFrame link, each property value foparticular Zone Version will take on the characteristics similar to aset ofmarkers; that is, a set of scatter points based on the well paths. The X anvalues for these property values do not sit at the top or base of the lithozobut, rather, in the middle of it as seen below, depending on the particularcomputational geometry chosen (TVT, MD, ...).


Schlumberger Applying Reservoir Properties to the Gross_Isochore for Oil in Place

e

Zone Property Values and Grid Calculations

Typically, the following ResSum properties are the ones used in thevolumetric equation for CPS-3:

Net Thickness,Gross Thickness,Net Porosity, andNet Pay Water Saturation.

Each is retrieved as ascatter set from the GeoFrame data base with theGFLink . and then gridded. These property grids can then be applied to thgross isochore with CPS-3 grid arithmetic operations.

Lithozone

Approximateproperty “marker”locations



nly a

tria

ing

re.

,

Quality and Characteristics of Property Grids

In the example shown, note that the gross isochore (shaded area) covers oportion of ourArea of Interest (AOI ). When we look at the quality of eachproperty grid we create, we will not be concerned with areas which are nowithin this pay zone. Within the pay zone, however, there are certain critewhich must be met:

• Porosity andSaturation values must remain between 0. and 1.0.This means that we may have to change parameters, or even griddalgorithms if too much slope is introduced into the grids by thealgorithm.

• The gridsmust be completely definedwithin the pay zone. No holesin the grid are allowed, otherwise, no volume can be calculated the

• As with other grids, the grid valuesmust honor the values in thewells.

• The grids should be relatively smooth between the well data pointsand shouldnot contain sharp discontinuitieswhich are notassociated with the existing fault boundaries, if used.



ter

,

nd

thehe

ionus

nt

Typical Difficulties When Gridding Properties

1. Faulting can affect property values during deposition, as well as afdeposition. In some reservoirs, thefault boundaries for either thetopof zone orbase of zone are used during property gridding to helpprovide discrete ranges of the property value in certain fault blockswhere appropriate.

2. Good property data for all lithozones is typically hard to come by adata from the wells is usuallysparse. This type of data can bechallenging to model adequately. We see that in the example below,data points for which we have property values barely reaches into treservoir area.

If seismic attributes exist for which it can be shown that there is a correlatwith property data, then interval property grids can be improved with variotechniques including the use of the applicationLog Property Mapping(LPM) which can extend the accurate extent of property grids beyond thelateral limits imposed by the well data.

Gridding Guidelines

With sparse data, we will probably get the best results using the Convergealgorithm. When gridding property data, it is almost invariable thatextrapolation will be required.



al the

the

isy

ase

ute

toe

The only other issue to worry about is the value for the Starting Grid Intervwhen using the Convergent algorithm. The rules of thumb we discussed inearlier 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 ofpay zone.

Remember, this number is not critical to determine the very first time. If it too small (pay zone not fully defined, or holes in the grid), then we’ll simplre-grid and make it bigger the next time.

Continuing with the OIP Equation

Once the individualproperty grids exist, the following series of grids arenormally 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 inboldfaceare the individual property grids. TheGross_Isochoreis thestructural envelope thickness, which is simply the difference of the top andbase structural envelopes. The final Net Pay grid becomes the input to theVolumetrics operation, along with any associated fault polygons and the lepolygons.

All operations involve onlygrid arithmetic when applying the properties.When we created the structural envelope, we used primarilygrid logicaloperations.

Using the Formula Processor for a Shortcut

Instead of computing the grids above independently, it is possible to comptheNet Pay grid from theGross_Isochore and the individualproperty gridsin asingle operation. In the exercises for this chapter, we’ll show you how solve the OIP equation at the beginning of the chapter in one step from thdialog under OPERATIONS/FORMULA.



pe,d,

ir

this

yies

ce. A

Note on Arithmetic and Logical Operations

In all the logical operations which we have performed to shape the enveloand all the grid arithmetic we have performed to compute the Net_Pay griwe have not used thefault boundaries (traces) at all. The reason for this isthat the CPS-3 logical operations and grid arithmetic functions perform thecalculations node-by-node,vertically, on corresponding grid nodes of theinput grids.

Computing Oil in Place with Volumetrics

We use the CPS-3 Volumetrics procedure to calculate oil in place. Thisprocedure has the ability to performnumerical integration between a gridand a base plane. It accumulates volume grid cell by grid cell and has theability to differentiate the volumes on either side of a fault or lease polylinewhen a cell is dissected by the line. Refer to the on-line documentation forprocedure for an summary of its operation.

If the volumetric input grid were a gross isochore, the results would simplbe volume of rock. However, having applied all of the required rock propertto the thickness grid, thevolumetric input grid is no longer in a simplethickness domain, and the result on the volumetrics report will be oil in plaWe have an option to report the results in barrels or other units, if desired.separate report for each lease polygon is generated.

The inputs to theVolumetric procedure are:

• singleNet_Pay grid which we have just calculated.

• set of combined top and basefault boundaries

• leasepolygons

The output from theVolumetric procedure is a report such as the exampleshown below.



lat

ove

nbe

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 thebase plane. The area of thepolygon (lease) is also a flat area.

Surface area is the curvilinear area of that portion of the grid ABOVE orBELOW the base plane and should always be equal or greater than the FArea.

For aNet_Pay volumetric grid which is based on an isochore, and whosevalues of interest should be positive, we are only interested in numbers abzero, and so we need only to look at theIntegrated Results ABOVE theHorizontal Reference Planein the report. The other sections are useful whethe volumetric grid is a structural model and Civil Engineering issues are tostudied, such as cut and fill for highway design.



id

in

Exercises for Oil in Place Calculations

In this chapter we will fetch the necessaryreservoir property data from theGeoFrame database so that we can compute oil in place according to thissimple formula:

Oil in Place = Gross Isochore Volume * Net/Gross * Porosity * Saturation

Once these data are accessible, we will grid them inCPS-3 to create one gridper property, then apply each to the Gross Isochore grid using Multiple GrArithmetic 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 fallingthis lithozone are computed byResSum, and are similar to geologicalmarkers. For example, the porosity is a set ofX,Y,Z points, where the Z-valueis anaverage porosity value in each borehole for the interval. Similarly, thesaturation and net/gross are sets of X,Y,Z points originating from theboreholes, containing average values.X,Y locations of the strat markers willfall along the borehole, midway between the geological markers.

You will recall that zone property values fromResSum are available inMD ,TVT , TVD , andTST form. For our purposes, we can use either theTVT orTVD . We’ll start by accessing the property data fromGeoFrame.



y

se

ExerciseExercise

Load Zone Properties (Net/Gross, Porosity, and WaterSaturation) from GeoFrame

As mentioned in the reference discussions, these zone properties arecalculated inResSum. When the “scatter set” switch is set during thesecalculations, a scatter set for each property calculated will be created andstored inGeoFrame. In this case, these properties can be accessed directlfrom CPS-3.

In this project, however, the “scatter set” switch was not set, and the purpoof this exercise is to show you how to use theGeoFrame Link to obtainaccess to these property scatter sets in CPS-3

1. Click onTools > GeoFrame Link.

2. Click on theLoad from GeoFrame tab, then clickZones to openGeoFrame Zone Interval Properties, then clickZone VersionandselectFormation, and then clickOK .

3. In theLithologic Layers section, highlightTarbert .

4. In theModel Name section, highlightCPS3_Intro.

5. In theProperty Versions section, highlightResSum_Output_3.

6. Highlight theNet/Gross_Thickness_Ratio, Net_Reservoir_Porosity,and Net_Pay_Water_Saturationproperties, and then underIndexhighlightTVD , and clickOK.

7. Highlight all threeCPS-3 Output Sets, and clickRun.

This will load three data sets in theCPS-3 DSL, one for each property.When finished, clickExit to return to theCPS-3 Main Module.

• • • • • •

Note: In early versions of the training project, the output sets may be empty.



ee
8. If the sets are not empty, go toUtilities > Sets > View
Contents/Statistics to display the statistics for the data created, to sif 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 toUtilities/Sets/List-Manage-Sets and edit their attributes such thatSurface = “Rock Feature”,Surface Name is “Tarbert”, and theProperty Code is appropriate for the set, for example, “Net PayPorosity”, etc.



forthe

ExerciseExercise

Create Property Grids

Determine Initial Grid Interval and Gridding Algorithm

1. Contour theGross Isochore.

2. Display themm_TARBERT_NESS_Porosity data set with largesymbols.

3. Go to Utilities > System > Set Toggle Switchesand make sure thatthe toggleShow graphic entities when z is null is off.

If time permits, it is recommended toskip the next section called “QuickProperty Gridding”, and to go instead to the procedure titled “A TechniqueObtaining Better Property Grids”. If, however, time is of the essence, use quick gridding.



ng

re

esl be.

Quick Property Gridding

Do this section only if you are going to skip the better technique, “...ObtainiBetter Property Grids” due to lack of time. This exercise will create thepropery grids needed to continue on to the volumetrics, but if possible motime 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 theMoving AverageSingle Surface gridding algorithm.

— Do not use the faults during gridding

— Use all default parameters, except for those below

— SetExtrapolation distance= 3000 m.

— SetSearch Radius = 3000 m.

— In Advanced parameters, setZ-minimum to 0.0 andReset Modeto “Blank”.

— Name the output grids “Netgross”, “Porosity”, and “Saturation”,respectively.

This will guarantee to create useable grids where the property valuexist everywhere that the reservoir exists. However, these grids wilrelatively simplistic, with the typical tight bullseyes around the wells

2. Go directly to the exercise titled “Apply Property Grids to GrossIsochore”.



e,

the

see

use

of

s:

he

are

ay

The Sparse Data Problem - A Technique for ObtainingBetter Property Grids

Property data is typically available only at the wells. Judging from thedistribution of the well data points relative to the pay zone in the map abovwe have what might be called a better-than-average amount of data withwhich to define the property grids. We only must define these grids withinpay zone. It is not always necessary to extrapolate to the edge of the mapwhen developing the property grids.

Even so, however, when the Ness_Tarbert fault set is displayed, you can that the reservoir extends across three fault blocks, and the data is stillsparsewhen compared to seismic distributions. Someextrapolation will still benecessary even with this relatively good data distribution.

Now the question is which gridding algorithm to use. Recall that theConvergent algorithm provides the best extrapolator available, we should it. The lecture notes give a good general procedure to follow, but we willdepart from it here because we actually have fairly numerous data inside our fault blocks.

We will define atwo-step gridding technique where we use the Convergentalgorithm to define accurate property valuesclose to the data, and use it againwith different parameter settings to “damp”unrelated data values whencompleting the grid in the extrapolated areas. We accomplish this as follow

1) Using a very small initial grid size in the first grid, we take advantage of tConvergent’s slope projection, but only closely around the data points. Wewill use the faults in the first gridding to make sure that these initial valuesnot tainted by data from different fault blocks.

2) Copy the first grid as “data” for a second gridding where we’ll produce a“weighted average” solution in extrapolated areas, instead of projectingvalues. We won’t use the faults in this gridding.

Overall, this will give a better-behaved property grid from sparse data forwhich the fault blocks have been taken into consideration.

No matter how we grid the property, it must be defined in all areas of the pzone. We’ll store a map set of the pay zone for comparative purposes:

3) Erase your screen and display only line contours for theGross_Isochore.Use alight blue contours.

4) Save the display as a map set calledPayZone.





)

,

ts

Grid the Property Data

1. Click onModeling > Single Surface and useConvergent gridding tocreate a grid for each property.

• Pick Data = mm_TARBERT_NESS_Porosity

• SetAlgorithm to Convergent.

• Pick Fault = Ness_Tarbert.

• Toggle OFFPolygon.

• SetInitial Interval to 250 .

• Click onAdvanced parameters, and

— SetOrder of Projection to First (This uses linear slope projection

— SetWeight Function to Statistical (This tends to spread theweights fairly evenly)

— SetZ_Limiting_Mode = “Smooth Clip”

— SetZ_min. = .1

— SetZ_max. = .8.

• Let the name of the output griddefault to the name of the data setmm_TARBERT_NESS_Porosity

• Click OK .

2. Use Fast Color-shadingto render the grid, then display the data poinon top. You should see a grid similar to the one below:



t ack

payext

ot

The advantage of using the fault boundaries during gridding is that we gemuch more accurate model. Luckily, there is enough data in each fault bloto define almost all of the blocks.

The one exception is the small block in the North which is included in the zone, but not defined in the property grid. This will become defined in the nproperty gridding step. Note how the grid is tightly defined only around thedata. We controlled this with a small Initial Grid Interval.

Let’s now continue with the second gridding for the final property grid.

3. Copy the property grid,mm_TARBERT_NESS_Porosity to a dataset calledPorosity

4. Create another grid called Porosity with the Convergent algorithmusing the same parameters except the following:

— UsePorosity as the input data.

— Don’t use any fault boundaries during gridding

— Set theInitial Grid Interval to about 500 m.

— SetOrder of Projection to Zero— SetWeight Function to Uniform

5. Color-shade the resulting grid, using the faults for contouring, but nfor display, and display the map setPayZone on top.



be

on

This final porosity grid covers the area of the pay zone and looks toOK.

6. Now repeat this process for the net/gross data set and the saturatidata setsmm_TARBERT_NESS_net-gross andmm_TARBERT_NESS_WSat_, creating a similar grid for each, onecalledNetGross, the other calledSaturation

The initial and final grids for each are shown below.





entids

ss

d

d. In

his

ExerciseExercise

Apply Property Grids to Gross_Isochore

As outlined in the lecture notes, we’ll now use theCPS-3 multiple gridoperations to create the volumetric grids. We could use the multiple-gridformula processor inCPS-3 to compute the final volumetric grid in oneprocess, but for sensitivity studies and for investigating results using differZone Versions for properties, we’ll calculate the traditional intermediate grone at a time.

Quality Control Considerations for the Property Grids

At this point, the most important things to verify about our three propertygrids are:

1. Make sure that all three grids are defined within the area of the groisochore.

2. Make sure that none of the grids have flat, zero areas, or negativeareas. It’s OK to be blank outside of the gross isochore, but noproperty grid should not be negative anywhere.

If the property grids do not fit these requirements, they should be regriddewith different parameters until they do.

Quality Control Considerations for the Intermediate VolumetricGrids

For the grids we will be creating in this exercise,

• Make sure that the shape of the reservoir is maintained in each griother words, the “zero line” of all of these grids should be the same

• Ensure that false positive features are not introduced in the grids. Tmeans that no new positive areas should show up outside of theoriginal “zero line”. This can happen if any of the property grids areallowed to go below zero.



Compute Net_Isochore Grid

1. Click Operations > Grid > Multiple Grids and selectC = A * B.

2. For C, create a new set namedNet_Isochore, and clickOK .

3. For A, selectGross_Isochore.

4. For B, selectNetGross.

5. Click OK . Use the statistics tool to check the Z-range of the outputgrid. 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



Compute Net Pore Volume Grid

1. Click Operations > Grid > Multiple Grid and selectC = 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 andcolor-shade the output grid as above



tg

Compute Net Pay Grid

For theNet_Paygrid, we will use theCPS-3 Formula Processerto finish thecalculations. So far, we have calculated:

Gross_Thickness * Net_to_Gross * Porosity.

The remaining term in the equation is(1.0 - Water_Saturation)and it willgive us the desired grid,Net_Pay, from which to compute oil in place.

1. Click onOperations > Grid > Formula.

2. EnterC=A*(1.0-B) under theFormula Editor .

3. Click theScan button (below the formula field) and asemicolonshould appear at the end of the formula. If it does not, you will seeSyntax error in theStatus text field - this means the formula was noentered correctly. Try again until the semicolon appears after clickinScan.

4. HighlightC (NULL) in theFormula Variable Definition section, andtypeNet_Pay in the bottom text entry field.



x

5. PressReturn.

6. HighlightA (NULL) in theFormula Variable Definition section.

7. Scroll through theSurface Set list, and highlightNet_Pore_Volume.Click Associate.

8. HighlightB (NULL) in theFormula Variable Definition section, andin a similar manner as above,associate B with the gridSaturation.

9. Click Calc and answerNo to Conformal Limiting .

10. After the calculation is finished, clickSave and provide the name of afile in which to save the formula. (Don’t forget to specify the file suffiof .frm .)

11. ClickDismiss.

12.Erase the screen and display contours for theNet_Pay grid, whichshould resemble the map below.



me

y

ansor

Verify Net Pay Grid

In this particular reservoir, we know that there should be only positive volueverywhere within its boundary as shown above.

1. Verify that this final grid is positive everywhere within its boundary bdoing the following:

— Erase the screen

— Contour the Zero Line of theNet Pay grid.

— Color shade theNet Pay grid, but color shade values onlybeginning at 0.0 using a contour interval of -10.

If any color-shaded contours appear within the reservoir boundary, this methat one of the previous operations did not work as intended. The instructwill help you determine which step of the procedure caused the problem.



pe,

s that

Fault Boundaries and Grid-to-grid operations

In all the logical operations which we have performed to shape the enveloand all the grid arithmetic we have performed to compute theNet_Pay grid,we have not used the fault boundaries (traces) at all. The reason for this itheCPS-3 logical operations and grid arithmetic functions perform theircalculations node-by-node, vertically, on corresponding grid nodes of theinput grids.

For these operations, the fault boundaries are not needed.



illd

ur to

me ines.

ExerciseExercise

Lease Blocks from ASCII Files

Since volumetrics is typically computed within specific lease blocks, we wload an ASCII file containing four leases and then compute OIP associatewith each.

Here are twoASCII files, each containing the same basic information for olease polygons. The first file contains subset markers with the lease namemark the beginning of each subset. The second file contains the lease naevery record, andCPS-3can tell the end of one lease when the name changUse either format you like for loading polygons.

This file which we will actually use today is the file named“mm_north_leases.ply”, which is to be found in yourCPS-3 dsl. It resemblesthe first file above, in that it containsCPS-3 subset markers to identify eachlease polygon.

k_leases_a.ply k_leases_b.ply



Load the Polygon File of Leases

1. Click File > Import > ASCII > Polygon.

2. Select “mm_north_leases.ply” from theFile Selection Dialog. (Thisopens theInput a Polygon File dialog box.)

3. Click New to create aPolygon set calledLeases as theOutput Set.

4. Click OK to return to theInput a Polygon File dialog box. Click onAssign Input/Output Parameters to open theRead/Write an ASCIIFile 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 theCPS-3 Main Module.



Display the Polygons

1. Go toDisplay > Basemap.

• ToggleBorder andLabelson.

• Set your own parameters, and clickOK .

• TogglePolygonson, and pickLeases.

• In Parameters, select a thick black line and clickOK .

2. Click OK in Basemap Display dialog box.

Note that portions of some of the polygons falloutside the border oftheDisplay environment. This will not affect the volumetriccalculations.

3. Go toDisplay > Basemap again.

4. TogglePolygonson, ensureLeases is selected, and clickSetParameters.

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



— Polygon fill method = Solid Fill— Click OK .

6. Click Apply in theBasemap Display dialog box.

7. Display the polygon set again, but make the following settings:

— Line color = red— First polygon of set to use = 2


— Line color = yellow— First polygon of set to use = 3


— Line color = light blue— First polygon of set to use = 4

10. Now display the whole polygon again with a black line, settingFirstPolygon = 1,Number of Polygons = All , andPolygon Fill Method =NoFill .

11. ClickOK to close the parameter dialog box.

12. ToggleMap Set to red, and select theLease_Names map set fordisplay.

13. ClickOK to close theBasemap Display dialog box.





e. It

edm

ExerciseExercise

Computing Oil In Place

TheCPS-3 Volumetrics procedure is used to calculate oil in place. Thisprocedure performs numerical integration between a grid and a base plancalculates volume – grid cell by grid cell, and has the ability to differentiatethe volume on either side of a fault or lease line whenever a cell is dissectby it. The instructor should provide a discussion of the volumetrics algorithbased on theon-line documentation for this procedure. In particular, therefinement parameter should be discussed.

Follow these steps to compute the oil in place from the Net_Pay grid.

1. In theCPS-3 Main Module, Click onOperations>Volumetrics.

2. Select the inputGrid asNet_Pay.

3. ToggleonFaults and selectNess_Tarbert.

4. ToggleonPolygon and selectNorth_Leases. Click OK .

North_LeasesPolygon Set



— SetVolume algorithm to Full Refinement.— SetReference plane elevation (Z units) to 0.0 .

— SetScale factor for all area results to meter^2 => acres.— SetScale factor for all volume resultsto m^2*m => MMBL .

— ToggleonDon’t do slice volumes.— Make sure thatFirst Polygon is 1 andNumber to Use is All— Click OK .

Looking at theCPS-3 Status Information window, the report for the lastpolygon,End_o_Rainbow,should be visible.



enl in

a bit

We are only interested in the first section of numbers:

Integrated Results ABOVE the Horizontal Reference Planein the report.

The other sections are useful only if your volumetric grid represents astructural model (topography) and you want to compute differences betwevolumes above a certain elevation and below that elevation which is usefuearth movement applications.

Note that theVolume reported, 42.1967 is inMMBL , and allAreas reportedare inacres. Your results will probably be slightly different due to themultitude of steps required to get to this point.

Had we used something other thanFull Refinement for the volume algorithm,the results might have been somewhat less accurate, but would have run faster. When accuracy is the main consideration, use Full Refinement.

MyPart


ng

ndedhen

Chapter 21

• • • • • •Editing Exercises

Overview

The purpose of this chapter is to introduce students to the interactive edititools available inCPS-3:

• Model Editor

• Color Palette Editor

• Map Editor

The exercises suggested here are relatively unstructured and the recommeprocedure is for the instructor to present the lecture notes for each topic, tdemonstrate the facilities, and then let the students follow suit after eachdemonstration. Student experimentation is encouraged with help from theinstructor.

GeoFrame Introduction to CPS-3 Chapter 21 - 1

Editing Exercises Schlumberger

are

the

uge

Model Editor Overview

Figure 21.1 CPS-3 Model Editor displaying its Pan/Zoom feature

TheCPS3 Model Editor is a powerful tool that lets you edit gridded surfacemodels, along with data, faults, polylines, and cultural features. Surfaces edited thoughmanipulation of contour lines and/or data values and faultlocations. After the edits are complete, the surface is then regridded usingchanged contours and/or data.

You may also change a grid by simply editing the node values directly in avariety of ways.

TheModel Editor gives you greater control during modeling, and allows yoto focus in specific areas for modification. It lets you integrate your knowledand interpretation into the modeling process.

Aside from editing the gridded model itself, the Model Editor has manyprovisions for making changes to yourData sets,Fault sets, andPolygonsets.

Chapter 21 - 2 GeoFrame Introduction to CPS-3

Schlumberger Editing Exercises

up,

en

Starting the Model Editor

There are four locations at which theModel Editor may be launched. Thereare also two modes in which launching occurs: independent mode and openmode.

Independent Mode

When launched inindependent mode, theModel Editor makes noassumptions regarding the sets which you may wish to edit. After it comesyou load each set you want by clickingFile > Load as below.

Figure 21.1 CPS-3 Model Editor displaying its load features

TheModel Editor is launched inindependent mode from the following twotwo locations:

• In theGeoFrame Visualization Catalog, click onModel Editor.— At the bottom, designate on which monitor you want theModel

Editor to be launched.

— < machine_name>:0.0 will launch it on theleft monitor, :0.1 willlaunch to theright .

— Click OK .

• In the CPS-3 Main Module, click Tools > Model Editor.

Open Set Mode

When launched inopen set mode, theModel Editor assumes that you want itto load those sets which are currently open in yourCPS-3 session. Look atyour CPS-3 Status Information window and it will show you the currentlyopen sets at the top of the window. The following dialog box appears in opset mode, and you can change any of the set names before theModel Editorlaunches and loads them.



Figure 21.1 Link to Model Editor dialog box

TheModel Editor is launched inopen set mode in the following twomethods:

• In theCPS-3 Main Module, click Operations > Surface/ModelEditor .

• Click on theModel Editor icon.



ere,

in

most

Model Editor functions

TheModel Editor has many features within its icons and menus, and thereare many ways to actually modify a grid, based on personal preference. Hwe refer you to the on-lineCPS-3 User’s Guidewhich containsmenu-by-menu and icon-by-icon documentation of every feature includedtheModel Editor .

We recommend that you read this documentation if you intend to use theModel Editor to any degree.

In this chapter, however, we want to go through examples of some of the common editing tasks using theModel Editor , rather than recite the functionof each menu and icon. which is well done in the document above.

Typical Editor session• LaunchModel 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 nodevalues, if the regridding reached the desired results.

• Repeat Step 2 - 6, as needed, until you are satisfied with the entiresurface.

• Save your edits.



s

he

d.

r

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 thiway you are able to recreate the grid at any time, as long as theoriginal data is available.

• If your surface requires editing in large areas, do not try to do it in tModel Editor. TheModel Editor was not designed to do regionaledits, but is most useful in small local edits to simply clean up a gri

• 3. Edit each area independently, zooming into the smallest areapossible, and setting the smallest regridding area possible.

• 4. Save your grid often; use theSave Asto retain intermediate versionsso that you do not lose your work.

• 5. Try to finish all your data and fault edits before moving on to yousurface edits.



n

ExerciseExercise

Model Editor

After presentation of the lecture notes (Topic 23 - Model Editor), theseexercises 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, theregrid, 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 newclosed polygon, delete points inside polygon.



eir

g

as

ize,h

ed in

Overview of the CPS-3 Map Editor

TheCPS-3 Map Editor lets you perform simple graphic editing on savedmap sets. Map sets are saved during sessions in theCPS-3 Main Module andcontain graphic objects and their attributes. Map sets are identifiable by thUNIX file extension,.mcps. TheMap Editor is not a substitute for a full-featuredCAD program. It does, however, provide a number of useful editinfeatures.

• 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 line color, style, thickness.

• View and edit map subsets.

• Combine up to five map sets into a composite map.

• • • • • •

Tip: TheMap Editor performs only graphic editing, and is limited to moving andcreating simple objects and modifying their attributes, such as color, font, sline style, width. The main use of this application is to clean up maps whichave already been created. TheMap Editor is NOT designed for editingcontours, data sets, fault sets, polygon sets, or grids. These should be edittheCPS-3 Model Editor. Changes made in the Map Editor will only bereflected in theCPS-3 Map set.



Starting the Map Editor

There are two ways to start theMap Editor .

• GeoFrame Application Manager> Visualization icon >Visualization Catalog— Click on theCPS-3 folder

— Click once onMap 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,underTools. (The target screen is controlled at the bottom of theVisualization Catalog.

Figure 21.1 CPS-3 Map Editor main menu



e of

es

u

Pull-down menus

The pull-down menus -File, Activate, Mode, View andOptions are locatedacross the top of theMap Editor window. Most of the functions under thepull-down menus are also available as icons in the tool bar. Here are somthe 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 loadedmap sets (up to 5 sets), only one of them isactive. If not picked here,the last one loaded to the session will be the active map set, which isthe one on display.

• Editable Layers: same as the icon(ACTIVATE:) E Layers . Allelements/subsets of the active map set are listed here as separatelayers. You may turn ON and OFF any of them to allow selected onto be edited. The layers you turn off may NOT be edited.

• Viewable Layers:same as the icon(ACTIVATE:) V Layers . Allelements/subsets of the active map set are listed here as separatelayers. You may turn off certain layers to hide them temporarily if yodo not want them to be on display.

Mode

UnderMode, you will see three groups of functions,Select, Add andComposite. Functions under each group are also iconized in the tool bar.

Figure 21.1 CPS-3 Map Editor bar menu



a

ill

of

gmep.,

d

Select Mode

• Browse: This function displays the x,y location of the cursor as youclick the mouse button.

• Move: This function allows you to move an object. Click on theMovebutton, and click on the object that you want to move. You will see white frame enclosing the object you just picked. Leave the cursorinside the white frame and click the mouse button again to pick thewhite frame up and drop to the place you want to move to. You canonly move one object at a time.

• Delete: This function allows you to delete an object. Click on theDeletebutton, and click on the object that you want to delete. You wsee a white frame enclosing the object you just picked. Leave thecursor inside the white frame and click the mouse button again todelete the object. You can only delete one object at a time.

• Copy: This function allows you to copy an object. Click on theCopybutton, and click on the object that you want to copy. You will see awhite frame enclosing the object you just picked. Leave the cursorinside the white frame and click the mouse button again to pick thewhite frame up and drop to the place you want to copy to. You canonly copy one object at a time.

• Attribute : This function allows you to change the graphic attributesan object. To change attributes, click on theAttr button, and click onthe object you want to change. You will see a white frame enclosinthe object that you just picked. Leave the cursor inside the white fraand click the mouse button again, an attribute dialog box will pop uIf the object you picked istext, you can change the text content, sizerotation angle, font, color, quality and justification. If it is asymbol,you will be able to select a different symbol, along with size, color anrotation angle. If it is a line, you may change the line style, width,color and smoothness. After you input the new attributes, click onApply button. The changes will display on screen. You can onlychange attributes on one object at a time.

• • • • • •

Note: Changing of text font will not show up in the Map Editor display.



t

tlay

it.

l

d

u

N

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 dialogbox which allows you to specify text attributes. After setting the texattributes, click on theApply button. Then move the cursor to theMapEditor window, a white frame will appear. Locate the white frame awhere you want the text to be, click the mouse button again to dispit.

• Symbol: To add a symbol, click on the(ADD:) Symbol button,displaying a dialog box which allows to you pick a symbol from thelibrary and specify its attributes. After setting the symbol attributes,click on theApply button. Then move the cursor to theMap Editorwindow, a white frame will appear. Locate the white frame at whereyou want the symbol to be, click on mouse button again to display

Composite Mode

Composite functions allow you to combine up to five map sets to make asingle, composite map.

• Base: This provides you with a blank canvas on which you can sizeand arrange the active map set, leaving space for pasting additionamap sets. IfGrid is turned ON, the canvas will show grid marks. If theSnap to Grid function is ON, the size of the map set will be snappeto the nearest grid mark.

• Paste: Other than the active map set, all additional map sets loadedinto the session (up to four sets) can be pasted onto the canvas. Yocan resize and rearrange these map sets. TheGrid andSnap functionworks the same way as inBase mode.

• Frame: This function allows you to enlarge the border of yourcomposite map set.

• Grid : This function allows you to turn the grid mark on the canvas Oand OFF, turnSnap to Grid function ON and OFF, and define the sizeof the grid on the canvas.

View

• Refresh - redraws the contents of the screen.

• Zoom - provides zoom functions -In , Out, Extents



s

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 canva

• Set Line Edit On - edits a line

• Set Point Edit On - edits a single point

• Set Quick Screen Repair - sets quick refresh



ises

ExerciseExercise

Map Editor

After presentation of the lecture notes (Topic 25, Map Editor), these exercare suggested:

1. Import a map

2. Move characters, change colors

3. Save map.



n is

ofo

rs

lor

p,

ExerciseExercise

Color Palette Editor

Basic Facts - 127 and 256 Color Limits

Each application, which runs on aUNIX workstation, uses up a certainnumber of the256 maximum colors per color map currently allowed at thistime byUNIX .

Sometimes 256 colors is insufficient, and it may be necessary to shut dowcertain applications known to be “color hogs” in your work environment. Italso possible to invoke the version ofCPS-3 which uses aprivate color map.This will provide a separate 256-colorUNIX color map for theCPS-3applications. The only drawback to the private color map is the annoyancecolor flashing which occurs as you move the cursor from one application tanother.

In this exercise, we will define less than 30 colors, so we should not beaffected by the lack of colors in theUNIX color map. Note that regardless ofhow many colors are available in theUNIX color map, the 127-color limit fortheColor Palette Editor will still remain. If you do have palettes with morethan 127 colors, use theStarting color index in the upper left of the menu toestablish the first of the 127 colors you wish to see. For example, theCPS-3Rainbow palette has 171 colors. If you want to work with the last 127 coloin this palette, then set theStarting color to 43 .

1. Create a simple palette for use in error mapping. Color 1 = red, Co2 = White, and Color 3 = blue.

2. Create a distributed 100-color palette with Yellow at the top, Blue inthe middle, and White at the end. Assign a z-value of 1000 to the to2000 to the middle and 2500 to the bottom.




form.

ere

nd

Chapter 22

• • • • • •CPS-3 Macros

Overview

One of the most useful features in a mapping package is the ability to pera series of predefined steps at different times or under different conditionsCPS-3 has had the ability to make macros for some time, but macroextensibility has not been generally possible. Recently, however, macros wmade much more powerful with the introduction of a flexiblemacrocommand language, which are an addition to the current macro structure, aallow prompting, variable substitution, and other features to make macrosmore 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 project’s CPS-3 dsl.

3. User macros - stored in user-specified location


CPS-3 Macros Schlumberger

hout it

he

you

Basic Macro Format

A macro is a simpleASCII file that contains a series of CPS-3 nativemapping commands.Native commands are documented in theReferenceManual, which is available on-line underTools in theCPS-3 Main Module.You donot need to know native commands in order to use macros. Those wrun macros frequently become knowledgeable about native commands, bis not necessary to begin using them. Being stored inASCII files, macros areeasily transported and edited. A portion of anASCII macro file is shownbelow as seen from the Unix “TextEdit: file editor.

Creating Macros

Macros are built, one command at a time, interactively in theCPS-3 MainModule, as you step through the dialog boxes performing the actions whicyou want to be stored in the macro. You can choose to only “go through thmotions” when creating a macro, or you can literally execute the steps as


Schlumberger CPS-3 Macros

us

l

ou

rlesks

used

ut

, and

ts

/.

create it. By executing the steps as you go, you can catch errors which yowould not see if you only “go through the motions”, however, both methodhave their uses.

Once created, the macro is placed in theProject macro directory, which is theproject’s CPS-3 dsl.

Macro Grouping

For all your macros, you have the option to organize them into meaningfugroups. Read how to do this in theonline CPS-3 User Manual. You candefine group names in a simple file, and assign each macro to a differentgroup. As you access the Macro functions from the Main Module menu, ythen 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, o“in the background” while you continue other mapping tasks. Macros enabyou to automate common, repetitive mapping tasks, as well as mapping tathat take a long time to complete.

Making a Macro Universally Useful

As created from CPS-3, macros contain the actual set names which werefor input and output as the macro was created. This limits the flexibility ofmacros, and this is why themacro command language was added to thesystem - to be able to transform thefixed-name initial macro into a universaltool which itself is able to prompt the user for the names of input and outpsets. Themacro command language also adds other capabilities to macrosbesides prompting such as executing loops, executing system commandscalling other macros.

Below, you’ll see how to modify a fixed-name macro into one which prompfor input.

Besides theProject macros, this version of CPS-3 supports access to anexisting library of macros calledSystem macroswhich are found in theGeoFrame installation directory under the sub-directory .../cps3_run_mac



nish.

to

The New Macro Language Abilities

The new language provides you with a variety of abilities within any macroyou create with CPS-3. These abilities are listed below.

• Establishnamed variables in a macro for your own purposes.Variables can contain characters, numbers, set names, or colors.

• Performarithmetic and logical operations between variables.

• Control theflow of the macro with these operators:

— While statement

— If - Then - Else

• Add interactive prompting inside the macro to establish variablevalues.

• Performsubstitution operations on set names and parameter valuesbefore the macro is run.

• Spawn detached processes, or spawn a process and wait for it to fi

• • • • • •

Note: For detailed descriptions of each of these language facilities, please refer the chapter about Macros in theCPS-3 User’s Manual.



of a

s of

Basic Facts about Macro Syntax and Organization

• Every line in the macro which starts with an exclamation point is acomment.

• Every line in the macro which starts with a six-letter commandbeginning withF, such asF1SWIT is aparameter-setting command.

• Each value following a parameter-setting command sets the value specific parameter. Some commands contain only one parameter,others contain many more parameters.

• Every line in the macro which starts with a six-letter commandbeginning withM , such asM1OPEN, is anoperation command.

• Some operation commands rely onprevious parameter-settingcommands to establish how the command will be executed, such aMSTRN1. Others rely on parameters which occur on the same linethe operation, such asM1OPEN.

• All parameter-setting commands and operation commands aredocumented in detail in theCPS-3 Reference Manual, which can befound underTools in theCPS-3 Main Module.



ll

abeers

ero the

Typical Prompting Language Added to a Macro

Below, you see some typicalmacro commands relating to promptingcomponents which are added to macros. These commands are in a file cak_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 forData set, and an output Surface set name. As you can see, this file could used as simple template and you can change the names, or even add othsets to be prompted for. Refer to the on-line User’s 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 singledialog

“prompt ” activates a single prompt line in the dialog for one variable

In general, variables should be declared asset, if they will be used for theselection of existing input sets. Variables declared asstring are set by the useronly by typed response.

Substituting Fixed Set Names with Variable Names

The next phase in making a macro universally useful is to find all places lowin the macro where the fixed-name sets are specified, and change them tappropriate variable name. For example, if the original unedited macrocontained the line



et

ableich

to

M1OPEN “DA” “mysetname” “UNKNOWN”

which opens a Data set named mysetname, we should replace the fixed sname (including double quotes) with the variable name $DATA1 (includingthe Dollar sign):

M1OPEN “DA” $DATA 1“UNKNOWN”

After all fixed set names have been replaced as shown with the proper variname, the macro will have been converted into a universally useful tool whcan 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 use it. Use the MACROS/SCAN features



on

nt-

ust

are.ssion

y to

Current Constraints: Macro Execution and Environments

1. At present, no information is written to a macro during Macro Creatiduring Environmentselection, creation, or editing.

2. At present, there is no macro command language tocreate newenvironments oredit existing environments

3. At present, when a macro executes, it assumes that thecurrentlyactive display and modeling environments are to be used. You canchange this, as will be shown below, by inserting various environmerelated commands in the macro.

Getting Around the Constraints

Future releases may improve upon these constraints, but until then, we muse whatever tools are available to help us manage environments withinmacros. Below, we document what is available in this release of the softwThese capabilities exist because environments are stored in the CPS-3 sefiles.

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

wheren is an environment number in the current session file. The only wadeterminen 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

wheren is an environment number in the current session file.



e

nged,

are

nning

ngthe

To save the currently defined modeling environments to a sessionfile when in CPS-3:

Although not specifically applicableinside of a macro, this function is runfrom the CPS-3 Main Moduleand is useful in preparing a session file for amacro to use. In theCPS-3 Status Informationwindow, enter the followingcommand at the bottom of the dialog box in the field labeledCPS-3Command. This command can be done at any time, but should probably bdone 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 chaolder macros must be converted to the current macro format before beingexecuted. The rules for pre-GF3.5 macros are as follows:

The macro is read and then converted to a6.0 macro, having a namingconvention ofCPS60_<old name>. During this process, oldernativecommands such asF1WINE , F1GINC, F1ZTYP, F1UNIT, andF1VSCL,which were previously used to establish a primitive mapping environment,commented out.

After a macro has been converted, it contains a header record at the begiof the file which looks like

!CPS_VERSION_6.0 T=98

which means that CPS-3 will read and execute the macro without assumithat it needs conversion. All macros created in GF3.5 and later will containsame header, so that no conversion will be attempted.

Managing Macros - Enhancements for GF4.0

Please refer to the Lecture DocumentI40_c05_Newfor40 which describesnew capabilities for macros regarding their organization, description, andselection.




ehe

Chapter 23

• • • • • •Graphic Operations in CPS-3

Overview

In this chapter, you will be introduced to many concepts inCPS-3associatedwith the creation, storage, modification, clipping, viewing, and plotting ofgraphic displays. In earlier chapters, we talked about mappingenvironmentsand how the X,Y box is the most visible of environment attributes. Here, wwill show how graphic objects are classified and how each interacts with tX,Y box of the changingDisplay environments during yourCPS-3 session.

Graphic Display in CPS

Whenever anything is displayed on the screen in CPS-3, it is recorded inscreen memory,which is actually a hiddenCPS-3map set used to refresh thescreen quickly.


Graphic Operations in CPS-3 Schlumberger

s. Intputmap

are

If a permanentcopy of the screen contents is desired, use theSave currentlydisplayed mapicon to write screen memory to a permanentCPS-3mapset.

Saved map sets retain all displayed graphic components and their attributeaddition, subset markers are written into the map set so that the graphic ouof one process can be distinguished from another. These layers of a savedset can bedeleted, or rearranged, if desired. Use theManipulate currentmap layers icon to invoke theMap Layer Manager.

We will perform an exercise later in the course to illustrate how map layersrearranged and deleted.

Honoring the Active Display Environment

Before anything is actually stored in screen memory, the active displayenvironment determines if any type of transformation is required. Inparticular, the displayed data may be:

• transformed to the activeGeographic Coordinate System

• scaledto the active scale

• converted to the active horizontal and vertical units

• clipped by the activeVolume of Interest (VOI )


Schlumberger Graphic Operations in CPS-3

, or

t be

It is the last operation,clipping, which provides the main focus for thischapter. We will discuss conditions when graphic displays become clippedwhen they are merely hidden.

• • • • • •

Note: The basic 2D clipping rectangle is defined by the X and Y extents of theVolume of Interest. However, these can be enlarged by the temporaryspecification of aTop, Bottom, Right, andLeft margin, if desired.

When Are Graphic Objects Clipped?

Two Display Classes

For clipping purposes, objects to be displayed inCPS-3fall into one of twoclasses -Inside objects andOutside objects.

Inside

Inside objects (see the following) areclipped to theVolume of Interestduring display.

• Data

• Faults

• Polygons

• Surfaces

• Maps (optional)

Any graphic manifestations of theCPS-3set types shown above, such as poindisplay, polylines, data value display, or contouring, are also considered toInside objects, and any graphics generated outside the X,Y box will bediscarded.

Upon displaying aMap set, you will be given the choice of treating it as anInside or Outside object, as desired.

Outside

Outside objects areNOT clipped during display. The following areconsideredOutside objects:

• Maps (optional)

• Borders,

• Labels


Graphic Operations in CPS-3 Schlumberger

to

and

ghn

ion

rust

the

• Title blocks

• North arrows

• In general, graphic output from allBasemap dialog boxes, exceptDisplay SetandLines and Annotationsections, is consideredOutside graphic objects.

Clipping During Graphic Display

WhenInside objects are displayed on the screen, they are clipped exactlythe activeVolume of Interest, and then stored inScreen Memory. Thisoccurs whether the user is zoomed in or not.

WhenOutside objects are displayed on the screen, they are NOT clipped, are stored in their entirety inScreen Memory, even though they may not bevisible. Again, this occurs whether or not the user is zoomed in. Even thouOutside graphics may not fall within the visible area of the display, they cabe made visible by creating and activating aDisplay environment whosedisplay volume is large enough to include the data.

Alternatively, clicking theReveal all graphics icon, will show allgraphic elements currently in screen memory.

TheReveal all graphics icon is activated when the current display does notshow all graphic components stored inScreen Memory. An example might bea title block which was placed at some x and y offset from the lower leftcorner of the map, but which fell outside the current viewing area.

• • • • • •

Note: There was no mention of the current zoom window in the previous discussconcerning clipping. Since there is now only one clipping window, which isdefined by the X, Y limits of the currently activeDisplay environment, and themargins,display of data while zoomed in will NOT cause the data to beclipped to the zoom window.This means that when you zoom out again aftehaving displayed some data, you will see all of it inside the X, Y limits, not ja piece of it, as in earlier versions.

In the exercises which follow, we will demonstrate the concept of graphicclipping, and the difference betweenInside andOutside graphic objects.

The exercises for this chapter will provide the opportunity to demonstrate principles discussed here.


ic

tion

Chapter 24

• • • • • •CPS-3 Ascii Loader

Overview

TheCPS-3 ASCII Data Loader is invoked from theCPS-3 Main Modulemenu bar and offers a very wide variety of data loading features.

Click onFile > Import > ASCII to see that you can load any of the five basset types in CPS-3 from ASCII files.

Figure 27.1 Available ASCII file types

TheExtended Datatype at the bottom is an enhanced method of loadingData sets when it contains textual information or graphic symbology in thefile. This will be explained later.

While theCPS-3 ASCII Data Loaderis very flexible and can load manydifferent file formats, there are certain conventions, regarding the organizaof these files, which are outlined in this chapter.


CPS-3 Ascii Loader Schlumberger

,

f

and

he

ing

General Requirements/Options

In general, each physical record in a data file representsone data pointorvertex in CPS-3.

All information associated withone point must be on the same physicalrecord.

There is a storage limit of50 z-attributes per data point. That is, a data pointcan have up to 50 z-values, each representing a measurement.

You can skip any number of records at the beginning of a file, but youCANNOT skip any at the end. Trailer records, which are not data recordsmust be physically deleted from the end of the file before loading.

Comments, prefaced with a “!” in column 1 of a record, can be embedded inany of theASCII file types, and will be ignored.

Theorder 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 theOrdered Input/Output loading method because thesystem expects data fields to occur in this order: x, y, z1, z2,...zn.

Each x, y, z, text, and symbology field must bejustified to the same column ineach record.

Defining Subsets During Loading

There are three ways to maintain the integrity of line-oriented data whenloading into CPS-3 fromASCII files. These methods apply to the loading oData, Fault, andPolygon 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 “differencethreshold” criteria will be initiated byCPS-3while loading the pointsto help it identify separate lines. The threshold works like this:

— Let D1 be the distance between the current point being loaded the previous point loaded.

— Let D2 be the distance between the previous point loaded and tpoint before it.

— If D1/D2 is greater than the threshold, then the current point beloaded is considered to be the beginning of a new line.


Schlumberger CPS-3 Ascii Loader

s

nts

rore

ASCII Data Loading Menu

Most of the parameters on the following menu are self-explanatory, such atheNumber of Z fields parameter.File Type andFormat, however, may needsome 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 conteof the data fields in theASCII file. These options apply toData, Fault,Polygon, Surface, andMap set loading.

1. Fortran Format Specification

In earlier versions ofCPS-3, you could actually specify aFortran formatstatement to be used byCPS-3 when loading the different fields in yourASCII data file. You can still do this by typing in the format in the menu, oby including the format statement as the first record in the file. However, mconvenient methods are available as alternative choices in the menu.



ach

ut

lly

aching. Ifset,

2. Ordered Input/Output

This method causes the system to read data in the following order from erecord without the user having to specify a format:

x, y, z1 ....zn

Each field must be separated by acomma and/or at leastone space.

3. Point to Fields

This option provides you with a special menu on which your data file isdisplayed so that you can pick the column limits for each field you want toread intoCPS-3.

File Types

There are almost no limits to the way in whichASCII data can be organized.However, these predefined formats are simplistic enough to cover just aboany kind of data which is loaded intoCPS-3.

1. X,Y,Z Only

This file format contains only x,y,z values in each data record and is typicaread 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 erecord. This type is typically read using non-extended mode. All points havthe same name field will be grouped into the same subset with that namethe name field is a unique well name, then each well becomes its own suband 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

. . .



s atrted inrded

ese

ual

3. CPS-3 ASCII Format

Unlike other formats, this one incorporates the setting of parameter valuethe top of the file and uses subset markers to define subsets. When expothis format, the parameters associated with the set are automatically recoby the system. This can be an advantage when transferring sets from onenetwork node to another while still retaining certain set characteristicsembodied in the parameters. It is not common practice to load data with thparameters unless reloading one which was exported fromCPS-3. The mainadvantage of this format is the use of the subset markers to define individlines and polylines. As with the other set formats, multiple z-fields may bepresent.

! comments

! comments

...

native parameter command 1



...

->subset 1 name

x1 y1 z1 . . .

x2 y2 z2 . . .

x3 y3 z3 . . .

->subset 2 name

x4 y4 z4 . . .

x5 y5 z5 . . .

x6 y6 z6 . . .

...



ual

the

d

use

p.

4. X,Y,Z with Text Fields and Symbology

In this format, multiple text fields exist in each record, as well as symbolcodes or other graphic attributes which are to be associated with the individdata 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 withExtended Data loader, so that all fields and symbology can be stored andused.

x1 y1 z1 . . . Text1.1, 1.2 . . . Attribute1.1, 1.2 . . .



Extended and Non-Extended Data Sets

When loadingData sets, there are two loaders to choose from as mentionepreviously - the standardData loader and theExtended Data loader.

Load data intonon-extended data sets if it does not contain, or you do notwish to use, textual or symbology fields. For example, if yourASCII data filecontains a well name and a well symbol code, but you do not plan to makeof them, load just the x,y,z portion into a non-extended data set, ignoring theother fields in the record.

Load data intoextended data sets if theASCII file contains text, numerics, orsymbology fields which you wish to display, or make use of, on a base ma

• 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 wellsymbol color



e

Examples of File Formats

Data Files

Here is an example of anX,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 ofX,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 inX,Y,Z Plus Name Fieldformat with a wellname:

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 thefields are separated only by commas. This file can be read by selecting thOrdered 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



code,

Here is an example of simple 2D seismic dataCPS-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 ofX,Y,Z with Text Fields and Symbologywith somecomments at the top, three z-fields, a well name, operator name, symbol and a symbol color associated with each well location.TheExtended Dataloader 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



se a

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 todefine the separate fault traces for each named fault. It is valid for faultvertices to contain z-values to aid in the gridding process. We would choofault attribute ofx,y only and a file type ofCPS-3 format for loading thisdata.

->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



mes.We

subset

Next is an example showing the same fault traces, but having the fault naencoded on each vertex record, removing the need for the subset markerwould choose the attribute x,y only attribute, and theX,Y Plus Name Fieldfile type to load these faults.

6101.402 2260.635 Northwest_vertical







6398.598 3401.793 Southern_Green_A








Polygon Files

Here is an example of a polygon lease file with lease names used as the 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



Data Transformations

As ASCII data is imported or exported fromCPS-3, transforms can beapplied to the data to move it, rotate it, scale it, or perform other arithmeticoperations. The transformation menu is shown below

Figure 27.3 Data Transforms dialog box



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


y a

Chapter 25

• • • • • •Convergent Algorithm Overview

Overview

TheConvergent gridding algorithm has proven to be a very reliable andpredictable general-purpose gridding algorithm. Its innovative methodologhas clearly set a standard for the industry. In this chapter, we will give youbrief overview of the mechanics of its operation, so that you can use theinformation to your advantage.

Figure 28.1 Internal surface refinement in Convergent gridding


Convergent Algorithm Overview Schlumberger

esgrid

ll

s

eme

rgeery

butrid

o

Iterative Procedure

Convergent gridding gets its name from a process whereby grid node valuare converged upon by iteratively assigning control point values to nearbynodes. The process starts with a large grid cell size, theStarting Interval , inthe first iteration, and the process ends when the grid cell size reaches itsdesired size, theFinal Interval. The grid is refined to smaller and smaller cesizes between each iteration. At each iteration, each control point value isassigned to a certain number of theclosest grid nodes, specified by theparameterNumber of Nodes to snap to. Thus, the most important parameterassociated with theConvergent 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:

• assignsor interpolates control point values to nearby nodes. (In thecase of nodes already having a values, implement the blending schdescribed in the followingBlending Algorithm section.)

• smoothsthe grid

• refines the grid

Through all iterations, the following becomesmaller:— The grid cell size

— TheNumber of Nodes to snap to parameter (1 on the lastiteration)

As you can see, in the early iterations, each control point contributes to a lageographic area, but in the final iterations, each control point is tied to a vsmall area. The result of theConvergent gridding technique is that areasoutside of the data have been modeled with a smooth, trend-like solution,yet in the middle of the data, the grid ties the data as closely as the final gsize will allow.

In the case of faulted surfaces, theConvergent algorithm applies the standardvisibility criteria when determining if a particular data point is appropriate tuse in the computation of grid node values.


Schlumberger Convergent Algorithm Overview

grid The

an

the

ried

t

Blending Algorithm

Multiple weighted Z values assigned by several control points to the samenode are mathematically merged using a sophisticated blending function.function is based on theTaylor Series, which allows the prediction of a shapeat any point “x” by knowing the behavior of the shape at several points “a”.

“X” is the grid node location, and “a” are the data point locations.

TheConvergent process involves multiple iterations of interpolation,smoothing and refining to achieve a trend like surface in extrapolation andaccurate fit in the presence of data. It starts with course grid interval whichcontrols the extrapolation and ends with a fine grid interval approximatingdata density, therefore controlling the accuracy of the model.

Slope and curvature information is calculated on the first iteration and carfrom 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 thecontrol points.

We will not explicitly discuss these options in class, but you can read abouthem in the on-lineUser’s Guide.

To help you see how theConvergent algorithm computes the final grid, thefollowing schematics of several iterations illustrate the process.

f x( ) f a( ) f ′ a( ) x a–( ) f″ a( )( )2!

----------------- x a–( )2+ +=



ata

ofd by

Figure 28.1 Convergent gridding: first iteration

At the beginning of the first iteration, the grid is null, and all control pointswill contribute, to some degree, to all grid node values. The effect of each dpoint depends upon its distance to the grid node. At the end of the firstiteration, the grid is essentially a weighted average. Note that the amountoverall extrapolation desired around the edge of the data can be controllethe Initial grid interval.

X

X

X

X

X

X

X

X

XINC = YINC = 2200mNumber of Nodes to snap to = 16 (max. possible)

XINC

YIN

C

1 2 3

4 5 6

7 8 9


Schlumberger Convergent Algorithm Overview

andthe 8.

nt ofing

Figure 28.1 Convergent gridding: second iteration

In this iteration, the grid starts with the refined values of the first iteration, the area affected by each control point has become smaller. For example,closest nodes for the upper left control point are 1, 2, 6, 7, 11, 12, 8, and 3Because the grid starts with existing values in this iteration, the assignmecontrol point values now becomes the projection of control point values usthe slopes and curvature computed from the grid.

X

X

X

X

X

X

X

X

YIN

C

XINCXINC = YINC = 1100m

Number of Nodes to snap to = 8

1 2 3 4 5

6 7 8 9 10

11 12 13 14 15

16 17 18 19

21 22 23 24

20

25



aller.elldt

Figure 28.1 Convergent gridding: third iteration

In this iteration, the grid begins with the refined values from the seconditeration, and the area affected by each control point has become even smEach control point in this iteration will change only the four nodes of the cin which it falls, but the overall trend in the grid is retained. The change anreadjustment of the four nodes continues as the projection of control poinvalues along the slopes and curvature computed from the grid.

X

X

X

X

X

X

X

X

Number of Nodes to snap to = 4XINC = YINC = 550m


n

hics.

s.ject.

ro)s

is

l

Chapter 26

• • • • • •Glossary of Mapping Terms

Overview

anisotropic: Having properties that differ according to the direction ofmeasurement. Least-Squares gridding allows for directional bias based ouser-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-3models data, performs data and surface operations and displays 2-D grapThe AOI boundaries are defined by the minimum and maximum, X and Yengineering coordinates. (See also engineering window.)

audit trail: When activated, the audit trail records all parameters andoperations used to create or modify data, grids, faults, polygons and mapThe user can request an audit report for a specific set or all sets in the pro

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 (macas a background computer process without user intervention. This mode iuseful when immediate results are not necessary or when cup intensivemapping tasks are to be run in offbeat computer load periods. This mode also used when hardcopy graphics are required.

bathymetric data: x,y,z data sets describing the depth of large bodies ofwater

biharmonic filter: See smoothing.

blanking: A procedure for setting the value of selected grid nodes to a nul(indeterminate) value. Nodes are usually selected by enclosing them inpolygons.


Glossary of Mapping Terms Schlumberger

r iss

of

userutoff

cetheur

g

nts

iner

r

bulls-eye: A contour pattern consisting of tightly spaced concentric circulacontours which stand out as an anomalous area on the map. This patterngenerally the result of a bad data point, seismic misties, or data that variegreatly, in relation to the contour interval, within a small distance.

cell: The base unit of the grid; bounded by four grid nodes. The dimensionsa cell are defined by the x- and y-increment.

clipping: There are two types of clipping.1.Surface clipping--Surfaceoperations can be used to ensure a surface is not greater than/less than aspecified cutoff value. All areas of the surface greater than/less than the cwill 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 oroutside user specified polygons.

color-shade contours:A user specified color palette is used to color the spabetween contour intervals. A single color from the palette is used to paint area of the surface falling within a defined contour interval. Adjacent contointervals are painted with adjacent colors from the color palette.

column: Within a computed grid, all nodes with equal X locations, butdifferent Y locations comprises a single grid column

command: A single word entered at the command line to invoke a mappinfunction 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 createdsurface. The surface limits can be controlled by either user defined constaor surfaces.

container: A named collection of information in GeoFrame. For example, asurface container holds various versions of gridded models for a specifichorizon and the fault traces which are associated with them; a data contaholds various versions of data points or scatter points for a particularhorizon.A container has no intrinsic data except as a holding tank for othecollections 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. Orthogonalcontours--These are generally drawn perpendicular to normal contours toindicate direction of flow.

contour interval: The difference between z-values of adjacent normalcontours (see contours).

contour-to-grid: See gridding.


Schlumberger Glossary of Mapping Terms

ndlue

ehas

st beher

nd

g

s

ts

control points: A point on a map represented as X,Y,Z1,Z2...Zn where X aY determine the location of the point on the map and Zn represents the vaof surface n at that point.

convergent gridding: See gridding.

coordinate system:A means of spatially locating X and Y data on a flat plansuch as a map. It may be a simple XY coordinate system in which the areabeen defined by a minimum to maximum X and Y values. If the data islocated by another means such as latitude and longitude, the X,Y axes mudefined with those coordinates. Latitude/Longitude may transformed to otcoordinate systems via different projections (UTM, Lambert, etc).

cultural data: Any information, such as political boundaries, roads, rivers alease boundaries used as reference points on a map.

data transformation: Any function that can be performed on the data durinit's import/export into CPS-3. System functions include scaling, shifting theorigin, rotation, or converting from latitude/longitude to X,Y.

default (default value): A software supplied answer to a question posed bythe program. Most default values represent a typical situation. The defaultvalue may be changed or left as is.

density gridding: See gridding.

deterministic data: Control points with very precise Z-values, such as welldata.

digitize: Method of directly entering new data into CPS-3 via a mouseattached 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 degreefrom horizontal.

distance gridding: See gridding.

edge effect: Term used to describe undesirable gridding (contouring) resulbeyond the edge of the data limits. This is due to erroneous extrapolationoutside 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.



. The

ly.

nd

).lt

eted

X, by

an

eult

as, awell, a

engineering window: A three dimensional geographic area in which CPS-3models data, performs data and surface operations and displays graphicsboundaries are defined by the minimum and maximum X, Y and Zengineering coordinates. The Z limits are used for 3-D graphic displays on(see also area of interest).

extrapolation: The process of projecting, extending, or expanding slope agradient information from known data into an unknown area. CPS-3 usesextrapolation during the gridding process.

fault boundaries: These are equivalent to polygonal fault traces (see belowIn IESX, fault boundaries can be digitized directly, or initialized from the faucontacts (see below).

fault contacts: Those points computed in IESX which are the actual orprojected intersection of an interpreted fault surface and a specific interprhorizon along a seismic line. Viewed in plan view, the fault contacts for aparticular horizon and fault approximate the fault boundaries which, in IEScan be derived from the contacts. Fault contacts in IESX can be identifiedhorizon, by fault, and by upthrown or downthrown side. Typically, the faultcontacts are used as a guide to digitize or initialize the fault boundaries(polygons).

fault cuts or fault segments: Seismic interpretation of a fault surface alongone or more seismic lines. The collection of fault cuts for a particular fault cbe used as data points to create a gridded model of the surface.

fault intersections: These are equivalent tofault boundaries, fault traces,andfault polygons.

fault trace (fault): A line marking any discontinuity (abrupt change inelevation or slope) in a surface model. Typically a fault trace marks theintersection of a fault surface with the modelled surface as viewed from thtop. Fault traces are minimally defined by X,Y vertices. A more complete fadefinition can include elevation (Z) and vertical throw (T) in the format of(X,Y,Z,T). Non-vertical faults are represented by closed polygons (faulttraces) and vertical faults are represented by lines.

field: Within an ASCII data file, a field contains one item of information in computer record (a record may have one or more fields). In multiple recordgiven field should always contain the same type of data. An example is a record in which one field stores the well name, an X-field contains latitudeY field contains longitude and the Z-field contains a formation top.



to, is

h

d al.

ew are

therr

t

ny

ce.larding

filter: There are two types of filters within CPS-3. 1.File filter--The graphicalinterface allows the user to limit the file list when dealing with files externalCPS-3. Ex. When importing ascii fault files into CPS-3, the user, by defaultallowed to select the file from a list of all existing.flt files. If the users file hasa different extension (.dat), the filter can be changed to.dat. The user willthen be allowed to select the correct file.2.Smoothing Filter--There are twotypes of filters which may be used during the smoothing process:a. Thebiharmonic filter is a converging filter requiring one or more passes througthe surface to converge on the final smoothed surface model. This filterminimizes curvature without affecting local slopes. This is usually thepreferred filter and is always used during snap or convergent gridding.b. Thering convolution filter is a non-converging filter that passes through the griuser-specified number of times to create the final smoothed surface modeThis filter reduces both slope and curvature. (see also smoothing).

fishnet isometric: A common method of representing a surface in threedimensions. The user specifies an azimuth and elevation from which to vithe surface. The surface is represented by a grid lattice where grid nodesplaced at their correct grid elevation revealing the peaks and valleys of themodel. 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 whethey would be obscured from the users view because they fall behind othefeatures of the surface.2.Hidden Line Removal (Isometric)--Grid latticesegments which fall behind portions of the surface being displayed are nodisplayed.

graphic displays: Two or three-dimensional map view representations of adata, cultural information, faults, surfaces, etc.

grid: A model showing the distribution of a user defined attribute such asdepth, porosity or contaminant concentration. Often referred to as a surfaThe grid consists of a set of ordered Z (attribute)-values occurring at reguintervals of rows and columns usually calculated from a set of user-defineattributes at irregular X,Y locations. As a verb, grid is the process of creatthe 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.



re

grid row: See row.

gridding: The basic computer mapping process for transforming user x,y,zdata into a regularly distributed x,y,z data set referred to as a grid. There aseveral algorithms within CPS-3 for creating grids.

contour-to-grid--Modified convergent gridding algorithm usedfor creating grids from digitized contour data.

convergent--Iterative gridding process which begins with a verycoarse grid increment which continually refines and reties data tothe grid until the final grid increment is reached. Excellentalgorithm for all common data type Minimizes edge effectsproducing a model more closely resembling a hand drawn contourmap.

density--Grid node values are set to the number of valid controlpoints within the search limit radius.

distance--Grid node values are set to the distance between thegrid node and nearest control point.

isopach--Specialized gridding for data sets where a zero valueindicates the modelled attribute is not present at that location.Commonly used for gridding isopach data. Uses a datapreprocessor to project a proper zero line and assign theappropriate negative number to the zero data value beforegridding takes place. Can be used with both convergent and leastsquares gridding techniques.

least squares--One of the oldest methods of computing grids. Canbe used for all types of data except digitized contours. Should notbe used where extrapolation across large areas is required due toundesirable edge effects.Can use dip and azimuth information atcontrol points if available. Allows for anisotropic weighting of thedata.

moving average--Does not consider slope or curvatureinformation when creating the grid. Performs a weighted averageon data within the Search Limit Radius to calculate the grid nodevalue. Not recommended for most data types. Produces acceptableresults 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 valuegrid is created by setting C1 to the constant value and C2-C10 to0.



is as a

ode,DT.

s

s

idel

wo

gridding (continued)...

snap--A single iteration of convergent gridding. Data is tied to thenodes of a new or existing surface. Excellent for quick lookgridding (especially 3-D seismic).Also used to tie an existingsurface to new or modified data.

step--Grid node values are set to the value of the closest controlpoint.

trend--Used to generate regional trend and residual maps. Anapproximation of the data model which reveals gross features onlyand hides local data variations.

horizon: A particular stratigraphic geologic sequence. In most instances thmay also be referred to as a grid or surface. FFMS uses the horizon namekey word for naming the surfaces and faults it calculates.

increment (interval): This is the basic measuring unit of a grid. Itcorresponds to the X, Y dimensions of a grid cell and determines theresolution of the map or model.

indeterminate value (INDT): A value used to indicate a null condition suchas the absence of data at a particular location. When assigned to a grid nthe surface is undefined in that area. The abbreviation used by CPS-3 is INThe value is internally stored as 1.0E+30.

interactive execution: The processing mode in which the software performoperations immediately upon command of the user. Graphic output isnormally sent to a terminal for immediate viewing. This mode is sometimereferred to as foreground execution. (see also batch execution).

interpolation: A process used during gridding to estimate values that liebetween two known values.

inverse interpolation: A process that back-interpolates a z-value from a grat a given xy location or cursor location as in the browse facility in the modeditor.

isochore: A surface which represents the true vertical thickness between tother surfaces. Often the result of subtracting two surfaces.

isometric display: See fishnet isometric



ness.e the

ach

ordbuilt

yed

ay

isopach: Literally it is the true stratigraphic thickness between two othersurfaces. This surface is always greater than or equal to the isochore thickCPS-3 does not calculate true isopach surfaces. However, many people usterm isopach synonymously with isochore, particularly when the bed dipangle is negligible.

isopleth: A grid representing the spatial distribution of some property orattribute.

isotropic: Having equal properties in any direction of measurement. Mostgridding assumes isotropic properties. (see also anisotropic).

lattice: The wire-mesh figure created by drawing line segments through ecolumn and row in a grid.

least squares gridding: See gridding

macro: A text file consisting of one or more commands which perform onemore mapping tasks. These can be built interactively using the macro builcommand within CPS-3 and recording your commands or macros can be using the macro builder under the CPS-3 Application Manager.

map: The entire graphic image generated by CPS-3. Maps may be displaon the screen or sent to plotters for hardcopy output.

menu: A list of options presented to the user for selection. Menu choices minvoke mapping functions or lead to other menus.

moving average gridding: See gridding

multiple surface operations: Algebraic or logical operations which can beperformed between two surfaces.

native commands: Low-level commands underlying CPS-3 that provideaccess 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



forming

mse

ee

,

as ay

to

ave

t

htheing

parameter: User- or system-specified values that a procedure uses to pera task. For example, the native command FSGRID is a parameter specifythe initial grid interval for gridding. The naming convention for CPSparameters 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 mnemonicdescriptor. (See also procedure.)

plotting units: The units of measure used to define the size of graphical iteposted on the plot or the size of the plot itself. The default units of measurare inches but can be changed to centimeters.

plotting window: A rectangle which positions the engineering window on thplotting device (screen or plotter). If a map scale is not set, displays will bcreated to fit within the specified treated as a temporary work file orpermanent archive from session to session. It stores data, faults, surfacesmaps. The project file will be obsolete from CPS-3 v4.0 onward.

projection: Used to convert data defining a three-dimensional body, such sphere, into a two-dimensional drawing (a flat plane). In cartography, mandifferent 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 grida different (larger/smaller) X- and Y-increment by resampling the existinggrid.

report file: During each interactive CPS-3 mapping session a file calledproject_name.rep is created. This file contains a summary of all thecommands and parameters used during that session.

response file: A text file that stores all the user responses made duringcreation of a macro within the Macro Builder Module. The response file isused to edit a macro previously created with the module. Response files han.rsp extension.

ring convolution filter: See filter.

row: Within a computed grid, all nodes with equal Y locations, but differenX-locations comprises a single grid row.

search limit (SLM): The length of the radius used to describe a circle whiccontains all control point data used to calculate a value for a grid node at center of the circle. A search limit radius is used in least squares and movaverage gridding algorithms.



ceheresee

ed as

es

d

rs

olfaultl.much

tolled

d

single surface operations: Algebraic or logical operations which can beperformed on an existing surface.

smoothing: A procedure performed on a surface (grid) to reduce the surfacurvature and produce a surface that is smooth and free of irregularities. Tare two types of filters which may be used by the smoothing process. (alsofilters).

snap gridding (snapping): See gridding.

statistical data: Control points with relatively imprecise Z-values, such asmagnetometer and seismic data. Statistical data is not meant to be honorstrictly as deterministic data.

step gridding: See gridding.

strike: The direction of a line formed by the intersection of a fault with asurface. In the CPS-3 FFMS module, by default, this is measured in degrepositively counter-clockwise from north.

subroutine library: The core of the CPS-3 system. The library is compriseof a set of highly organized subroutines for performing all of the mappingfunctions available with the software.

surface: See grid.

surface strike: The direction normal to the dip of a surface. Normal contoufollow surface strike.

switch: See toggle switch

symbol code: A numeric code used by CPS-3 to post the appropriate symbat a particular location. Numbers 1-65 represent stroked symbols. The desymbols and codes are shown in Appendix C of the CPS-3 User's manuaSymbol numbers 1001 and greater are machine symbols and are posted quicker.

throw: The amount of vertical separation across a fault trace.

toggle (switch):To change the status of a parameter or other item from ONOFF or vice versa. CPS-3 provides a number of global parameters (also ca“switches”) that can be turned ON or OFF. Example.INDT is a switch whichwhen ON displays all graphic items. When it is OFF, only items with a valiz-value are displayed.

transformation sequence: The order in which X,Y and/or Z values aremanipulated during CPS-3 input/output. (See data transformation.)



ger

ute

ls

trend gridding: See gridding.

unconformity: A surface of erosion or non deposition that separates younstrata 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 compthe volumes within an enclosed area.

X-increment: The length of a grid cell along the x-axis measured inengineering units. The distance between grid columns.

Y-increment: The length of a grid cell along the y-axis measured inengineering units. The distance between grid rows.

Z-value: Value of any attribute to be modeled at a specific location. Typicaattributes are depth, porosity and saturation values. Data points, grid nodeand fault vertices can all contain z-values.




Documents

Introduction to CPS-3 - pudn.comread.pudn.com/downloads130/doc/556189/train/train/GF4_IntroCPS3... · Introduction to CPS-3 GeoFrame 4.031 November 6, ... Training Workflow ... Computing