Flog Ug

ECLIPSE* reservoir simulation software
Version 2010.1
User Guide
Proprietary notice
Copyright © Schlumberger. All rights reserved. Reproduction or alteration without prior written permission is prohibited, except as allowed
under applicable law.
Use of this product is governed by the License Agreement. Schlumberger makes no warranties, express, implied, or statutory, with respect
to the product described herein and disclaims without limitations any warranties of merchantability or fitness for a particular purpose.
Trademarks & service marks

"Schlumberger," the Schlumberger logotype, and other words or symbols used to identify the products and services described herein are
either trademarks, trade names, or service marks of Schlumberger and its licensors, or are the property of their respective owners. These
marks may not be copied, imitated, or used, in whole or in part, without the express prior written permission of their owners. In addition,
covers, page headers, custom graphics, icons, and other design elements may be service marks, trademarks, and/or trade dress of
Schlumberger and may not be copied, imitated, or used, in whole or in part, without the express prior written permission of Schlumberger.
Table of Contents
List of Figures ..... ...................................................................................................................................................................9
List of Tables ...... .................................................................................................................................................................12
Chapter 1 - New developments ..................................................................................................... 13

Developments in 2007.1 .......................................................................................................................................................13
Developments in FloGrid 2006.1 ..........................................................................................................................................14
Chapter 2 - Introduction ................................................................................................................. 15

Overview............. .................................................................................................................................................................15
FloGrid Tools ...... .................................................................................................................................................................17
Create a Model .. .................................................................................................................................................................26
Typical Workflows.................................................................................................................................................................30
Main Window ...... .................................................................................................................................................................35
Chapter 3 - Getting started............................................................................................................. 37

Starting FloGrid .. .................................................................................................................................................................37
Chapter 4 - Short Tutorials............................................................................................................. 39

Introduction ......... .................................................................................................................................................................39
Building a simulation model from maps ................................................................................................................................42
Building a simulation model from a RESCUE model ............................................................................................................46
Building a simulation model by upgridding another model and comparing volumetrics .......................................................48
Building an unstructured simulation model ...........................................................................................................................51
Planning New Wells..............................................................................................................................................................53
Updating a simulation model and building a derived model .................................................................................................56
Deriving Fault Transmissibility Multipliers for Simulation......................................................................................................59
Generating geostatistical properties .....................................................................................................................................61
Running a Streamline Simulation with Multiple Realizations ................................................................................................66
Generating Structure and Properties from 2D Mapping .......................................................................................................70
Chapter 5 - User Interface .............................................................................................................. 75

Introduction ......... .................................................................................................................................................................75
Windows and Panels ............................................................................................................................................................76
Data Tables ........ .................................................................................................................................................................83
Window Items ..... .................................................................................................................................................................84
Common options .................................................................................................................................................................87
Preferences Menu ................................................................................................................................................................94
Chapter 6 - Save and Restore ........................................................................................................ 97

Workspace save and restore ................................................................................................................................................97
The workspace - technical background ................................................................................................................................98
File menu options .................................................................................................................................................................99
Chapter 7 - Commands................................................................................................................. 101

Commands ......... ...............................................................................................................................................................101
Chapter 8 - 3D Viewer ................................................................................................................... 107

Introduction ......... ...............................................................................................................................................................107
File Menu ............ ...............................................................................................................................................................109
Edit Menu ........... ...............................................................................................................................................................112
FloGrid User Guide 3

Table of Contents
View menu .......... ...............................................................................................................................................................130
Tools menu ......... ...............................................................................................................................................................140
Scene Menu........ ...............................................................................................................................................................144
Chapter 9 - Structural Framework ............................................................................................... 175

Introduction ......... ...............................................................................................................................................................175
Creating and deleting models .............................................................................................................................................177
Displaying model status ......................................................................................................................................................178
Creating and displaying boundaries....................................................................................................................................179
Specifying units .. ...............................................................................................................................................................182
Fault block splitting .............................................................................................................................................................186
Creating FloGrid data models .............................................................................................................................................190
Chapter 10 - Fault framework editor ........................................................................................... 191

Introduction ......... ...............................................................................................................................................................191
Selecting faults/gridding controls for display.......................................................................................................................192
Editors................. ...............................................................................................................................................................193
Editing lines and vertices ....................................................................................................................................................195
Editing faults/gridding controls ............................................................................................................................................199
Fault block splitting .............................................................................................................................................................209
Chapter 11 - Geological Property model .................................................................................... 215

Introduction ......... ...............................................................................................................................................................215
Creating and deleting models .............................................................................................................................................217
Importing data ..... ...............................................................................................................................................................218
External model .... ...............................................................................................................................................................220
External properties..............................................................................................................................................................221
Scenarios ............ ...............................................................................................................................................................222
Creating and editing model properties ................................................................................................................................223
Creating property maps ......................................................................................................................................................228
Property data model ...........................................................................................................................................................229
Chapter 12 - Property population................................................................................................ 231

Introduction ......... ...............................................................................................................................................................231
File menu ............ ...............................................................................................................................................................233
Population Parameter Set...................................................................................................................................................234
Primary Input ...... ...............................................................................................................................................................236
Lumping .............. ...............................................................................................................................................................240
Secondary Input.. ...............................................................................................................................................................242
Algorithm............. ...............................................................................................................................................................243
Realizations ........ ...............................................................................................................................................................262
Proportions (Global, Vertical and Secondary Data Weights) ..............................................................................................264
Search ................ ...............................................................................................................................................................266
Output Mask ....... ...............................................................................................................................................................268
Current Property Grid..........................................................................................................................................................270
Creating and specifying data ..............................................................................................................................................272
Property Population menu ..................................................................................................................................................280
Indicator Classification ........................................................................................................................................................284
Property Population Data Analysis .....................................................................................................................................288
Data Analysis ...... ...............................................................................................................................................................292
Histogram Settings..............................................................................................................................................................297
Univariate Statistics ............................................................................................................................................................298
Bivariate Statistics...............................................................................................................................................................300
Variogram Specification ......................................................................................................................................................302
4 FloGrid User Guide

Table of Contents
Chapter 13 - Creating a structured grid ...................................................................................... 309
Structured Gridder Module .................................................................................................................................................309
Corner point gridding ..........................................................................................................................................................311
Rectangular gridding ..........................................................................................................................................................330
Chapter 14 - Data tree................................................................................................................... 333

Introduction ......... ...............................................................................................................................................................333
Using the data tree .............................................................................................................................................................334
Surfaces Data .... ...............................................................................................................................................................341
Faults Data ........ ...............................................................................................................................................................360
Wells Data ......... ...............................................................................................................................................................374
Well Markers Data .............................................................................................................................................................383
Well Logs Data ... ...............................................................................................................................................................386
Boundaries Data ...............................................................................................................................................................390
Structural Frameworks Data ..............................................................................................................................................393
FloGrid Models Data ..........................................................................................................................................................396
Chapter 15 - LGRs, Resizing, Aquifers and NNCs ..................................................................... 407

Introduction ......... ...............................................................................................................................................................407
Refining a structured grid ...................................................................................................................................................408
Resizing a structured grid ...................................................................................................................................................412
Region multipliers ...............................................................................................................................................................417
Aquifers .............. ...............................................................................................................................................................419
NNCs .................. ...............................................................................................................................................................421
Chapter 16 - Structured gridder properties ................................................................................ 427

Structured gridder properties/Upscaler ..............................................................................................................................427
File: Import, Export and Status ...........................................................................................................................................430
Phase folders...... ...............................................................................................................................................................434
Property editor tree .............................................................................................................................................................435
1 Phase .............. ...............................................................................................................................................................451
2 Phase .............. ...............................................................................................................................................................453
Multilevel upscaling ............................................................................................................................................................459
Diagnostics ......... ...............................................................................................................................................................461
Upscaling and diagnostics ..................................................................................................................................................463
Upscaling relative permeability ...........................................................................................................................................479
Statistical diagnostics .........................................................................................................................................................484
Building the micro grid in a grid block .................................................................................................................................485
Single phase flow equations in curvilinear coordinates ......................................................................................................486
Chapter 17 - Upgridder ................................................................................................................. 487

Introduction ......... ...............................................................................................................................................................487
Upgridding Folder ...............................................................................................................................................................488
Upgridder - Technical Description ......................................................................................................................................493
Generating and using fluxes for Upgridding .......................................................................................................................496
Chapter 18 - Generating an unstructured grid ........................................................................... 499

Unstructured Gridder module .............................................................................................................................................499
Creating and editing unstructured grid................................................................................................................................501
Gridding order..... ...............................................................................................................................................................524
Generating a grid ...............................................................................................................................................................525
Gridding Preferences..........................................................................................................................................................532
Chapter 19 - LGRs, Aquifers and Properties for an unstructured grid.................................... 535

Introduction ......... ...............................................................................................................................................................535

Table of Contents
LGR... ................. ...............................................................................................................................................................536
Aquifers............... ...............................................................................................................................................................540
Property .............. ...............................................................................................................................................................542
Chapter 20 - Fault Property Calculator ....................................................................................... 551

Introduction ......... ...............................................................................................................................................................551
Faults Tab ........... ...............................................................................................................................................................553
Derived Multiplier Folder .....................................................................................................................................................555
Fault Export folder ..............................................................................................................................................................558
Fault Property Calculator - technical background ...............................................................................................................559
Chapter 21 - Volumetrics.............................................................................................................. 569

Volumetrics ......... ...............................................................................................................................................................569
Measurements .... ...............................................................................................................................................................570
Reporting options ...............................................................................................................................................................573
Volumetric run definitions....................................................................................................................................................574
Using contact sets with volumetrics ....................................................................................................................................575
Single run operation............................................................................................................................................................576
Multiple realization operation ..............................................................................................................................................577
Chapter 22 - Contact Sets ............................................................................................................ 579

Introduction ......... ...............................................................................................................................................................579
The ContactRegion property...............................................................................................................................................580
Defining a contact set .........................................................................................................................................................581
Displaying a contact set ......................................................................................................................................................582
Using a contact set .............................................................................................................................................................583
Chapter 23 - Streamline Simulation ............................................................................................ 585

Introduction ......... ...............................................................................................................................................................585
Simulation Setup. ...............................................................................................................................................................587
Simulation Manager (Volumetrics Graphics) ......................................................................................................................595
File menu ............ ...............................................................................................................................................................596
Graphics Window ...............................................................................................................................................................603
Management Options .........................................................................................................................................................605
Schedule section keyword generation ................................................................................................................................611
Black Oil correlations ..........................................................................................................................................................613
Calculation of Kh and connection factor .............................................................................................................................617
Orthogonalization of vectors ...............................................................................................................................................620
Chapter 24 - Multiple Realizations .............................................................................................. 623

Introduction ......... ...............................................................................................................................................................623
Realizations Dialog (Volumetrics) .......................................................................................................................................625
Executing Realizations........................................................................................................................................................628
Multiple Realizations for FrontSim simulations ...................................................................................................................629
The Realizations Dialog (Simulation)..................................................................................................................................630
Chapter 25 - Well Planning........................................................................................................... 631

Introduction ......... ...............................................................................................................................................................631
Wells node .......... ...............................................................................................................................................................632
Well node ............ ...............................................................................................................................................................637
Chapter 26 - Core Analysis .......................................................................................................... 645

Core .................... ...............................................................................................................................................................645

Table of Contents
Chapter 27 - 2D Mapping Canvas ................................................................................................ 647
Introduction ......... ...............................................................................................................................................................647
Edit menu ........... ...............................................................................................................................................................653
Display menu ...... ...............................................................................................................................................................654
Options menu ..... ...............................................................................................................................................................658
Others menu ....... ...............................................................................................................................................................659
2D Viewer ........... ...............................................................................................................................................................660
2D Viewer options ..............................................................................................................................................................669
2D Viewer Editors ...............................................................................................................................................................671
Common Workflows............................................................................................................................................................674
Chapter 28 - 2D Well Log Correlation Canvas............................................................................ 679

Introduction ......... ...............................................................................................................................................................679
Selecting data for display ...................................................................................................................................................680
Removing data from display ...............................................................................................................................................682
Color shading the well logs.................................................................................................................................................685
Chapter 29 - Expression Calculator ............................................................................................ 687

Introduction ......... ...............................................................................................................................................................687
Common features ...............................................................................................................................................................688
Multi-Apply Calculator.........................................................................................................................................................690
Expression calculator language..........................................................................................................................................695
Appendix A - Calculator Language ............................................................................................. 701

Introduction ......... ...............................................................................................................................................................701
Language definition ............................................................................................................................................................702
Keywords ............ ...............................................................................................................................................................705
Built-in constants ...............................................................................................................................................................710
Built-in functions . ...............................................................................................................................................................711
Operators............ ...............................................................................................................................................................713
Symbol functions ...............................................................................................................................................................714
Unit support ........ ...............................................................................................................................................................717
Special variables ...............................................................................................................................................................727
Calculator utilities ...............................................................................................................................................................729
Startup files......... ...............................................................................................................................................................731
Debugging .......... ...............................................................................................................................................................732
Appendix B - Configuring FloGrid............................................................................................... 735

Configuring on-line help......................................................................................................................................................735
FloGrid License Features ...................................................................................................................................................756
Appendix C - Construction of Units and Horizons from Mesh Maps ....................................... 757
Introduction ......... ...............................................................................................................................................................757
Appendix D - Corner point gridding............................................................................................ 761

Introduction ......... ...............................................................................................................................................................761
Corner point grids ...............................................................................................................................................................762
Building a corner point grid .................................................................................................................................................764
Further remarks on the user specified parameters, and user choices................................................................................769
Appendix E - Input file formats .................................................................................................... 773

Input file formats . ...............................................................................................................................................................773
Contour Map Control files ...................................................................................................................................................774
Mesh Map Data .. ...............................................................................................................................................................781

Table of Contents
Scatter sets data . ...............................................................................................................................................................783
Faults .................. ...............................................................................................................................................................784
Wells ................... ...............................................................................................................................................................791
Property model input formats..............................................................................................................................................798
Geolith / Chears input format ..............................................................................................................................................799
Appendix F - Importing Data From GeoFrame ........................................................................... 803

Introduction ......... ...............................................................................................................................................................803
Appendix G - Unstructured Gridder files.................................................................................... 805

Import files .......... ...............................................................................................................................................................805
Export files .......... ...............................................................................................................................................................808
Converting old dual porosity files command files................................................................................................................811
Appendix H - Property Population Glossary.............................................................................. 813

Introduction ......... ...............................................................................................................................................................813
Appendix I - Reference Tutorials ................................................................................................. 823

Introduction ......... ...............................................................................................................................................................823
Fault trace handling ............................................................................................................................................................824
Appendix J - Mapping Packages................................................................................................. 839

Introduction ......... ...............................................................................................................................................................839
Convergent Gridder ............................................................................................................................................................840
Conpac ............... ...............................................................................................................................................................847
Contouring .......... ...............................................................................................................................................................850
Appendix K - Printing images...................................................................................................... 853

Saving Images as Print Files ..............................................................................................................................................853
Related information for supported file save formats ...........................................................................................................857
Appendix L - History of developments ....................................................................................... 859

Developments in FloGrid 2004A_1 .....................................................................................................................................859
Developments in FloGrid 2004A .........................................................................................................................................860
Developments in FloGrid 99B .............................................................................................................................................891
Developments for FloGrid 98B............................................................................................................................................899
Appendix M - Bibliography .......................................................................................................... 905
Appendix N - Index ....................................................................................................................... 909

Table of Contents
List of Figures
Figure 5.1 .......... Tile 3D Windows panel ...........................................................................................................................77
Figure 5.2 .......... Example of tiling 2 viewers in one row....................................................................................................78
Figure 5.3 .......... Example of tiling 3 viewers in two rows ..................................................................................................78
Figure 5.4 .......... The Text Editor window ..........................................................................................................................79
Figure 5.5 .......... Example of a modal panel ......................................................................................................................80
Figure 5.6 .......... Example of a modeless panel.................................................................................................................81
Figure 5.7 .......... Example window items ...........................................................................................................................85
Figure 8.1 .......... Print Setup panel ..................................................................................................................................109
Figure 8.2 .......... Edit Boundaries panel...........................................................................................................................113
Figure 8.3 .......... Map Editor Controls panel ....................................................................................................................117
Figure 8.4 .......... The Edit NNC Values panel..................................................................................................................120
Figure 8.5 .......... The Create New NNC panel .................................................................................................................121
Figure 8.6 .......... The Animate Time panel.......................................................................................................................131
Figure 8.7 .......... The timestep control buttons ................................................................................................................131
Figure 8.8 .......... The Animate Time Options panel .........................................................................................................132
Figure 8.9 .......... Object Appearance panel .....................................................................................................................132
Figure 8.10 ........ Normalization panel .............................................................................................................................133
Figure 8.11 ........ Object Rotation panel ...........................................................................................................................136
Figure 8.12 ........ Lighting panel .......................................................................................................................................137
Figure 8.13 ........ Stereo Panel .........................................................................................................................................137
Figure 8.14 ........ Property Display panel..........................................................................................................................146
Figure 8.15 ........ Cell Probe panel ...................................................................................................................................147
Figure 8.16 ........ Threshold Properties ............................................................................................................................148
Figure 8.17 ........ Integer Threshold panel........................................................................................................................149
Figure 8.18 ........ Real Threshold panel............................................................................................................................149
Figure 8.19 ........ IJK Slicer panel.....................................................................................................................................151
Figure 8.20 ........ VOI Grid Cells panel .............................................................................................................................152
Figure 8.21 ........ VOI Domain Selection panel.................................................................................................................153
Figure 8.22 ........ Create VOI From Boundary panel ........................................................................................................154
Figure 8.23 ........ The Cell Face Selection panel ..............................................................................................................159
Figure 8.24 ........ Integer Threshold panel........................................................................................................................163
Figure 8.25 ........ Real Threshold panel............................................................................................................................164
Figure 8.26 ........ Wells panel ...........................................................................................................................................165
Figure 8.27 ........ Ternary legend......................................................................................................................................167
Figure 8.28 ........ Color legend .........................................................................................................................................168
Figure 8.29 ........ Color legend .........................................................................................................................................168
Figure 8.30 ........ Object Appearance panel .....................................................................................................................171
Figure 8.31 ........ Edit Titles panel ....................................................................................................................................172
Figure 8.32 ........ Axes panel ............................................................................................................................................173
Figure 10.1 ........ Two intersecting faults ..........................................................................................................................192
Figure 10.2 ........ A fault in the process of being edited by moving the vertices...............................................................193
Figure 10.3 ........ Magnification Controls dialog................................................................................................................198
Figure 10.4 ........ Intersecting faults following selection of a position along the major fault (shown in yellow) .................200
Figure 10.5 ........ The same faults, after selecting a section of the major fault (shown in yellow) ....................................200
Figure 10.6 ........ Potentially ambiguous multiple intersections between pairs of faults/gridding controls (areal view) ....201
Figure 10.7 ........ Digitize New Control dialog...................................................................................................................203
Figure 10.8 ........ Digitizing an extension to the top line of an existing gridding control ...................................................205
Figure 10.9 ........ The same control after digitizing the extension to the bottom line ........................................................205
Figure 10.10 ...... The same control after extension .........................................................................................................206
Figure 10.11 ...... Rescue model fault with incorrectly specified top (magenta) and bottom (cyan) edges .......................206
Figure 10.12 ...... The same fault after placing the four beads to define the correct top and bottom edges .....................207
Figure 10.13 ...... The corrected fault................................................................................................................................208
Figure 10.14 ...... How FloGrid analyzes and orders faults ...............................................................................................210
Figure 10.15 ...... Faults with a cyclic set of major-minor relationships.............................................................................211

List of Figures
Figure 10.16 ....... How FloGrid splits fault blocks with a cyclic set of major-minor fault relationships...............................211
Figure 10.17 ....... How FloGrid creates new mesh maps for each block and horizon .......................................................212
Figure 10.18 ....... How FloGrid applies re-samples of the 2D fault traces to the new block unit horizons ........................212
Figure 12.1 ......... Algorithm Decision Tree........................................................................................................................260
Figure 12.2 ......... Facies Property Population ...................................................................................................................260
Figure 12.3 ......... Petrophysical Property Population .......................................................................................................261
Figure 12.4 ......... Features of a variogram ........................................................................................................................295
Figure 13.1 ......... Top conforming (offlap) sub-unit layering to a user-specified surface ..................................................326
Figure 13.2 ......... Bottom conforming (onlap) sub-unit layering to a user-specified surface .............................................326
Figure 14.1 ......... Areal view of the fault traces for three horizon maps ............................................................................362
Figure 14.2 ......... Areal view of the splitting traces for all three fault traces ......................................................................362
Figure 14.3 ......... Three model fault traces demonstrating digitizing of splitting trace ......................................................363
Figure 14.4 ......... The splitting trace concept seen in cross section. ................................................................................363
Figure 14.5 ......... A listric fault seen in cross section ........................................................................................................364
Figure 14.6 ......... The original and replacement fault surface seen in cross section ........................................................364
Figure 14.7 ......... The replacement fault trace seen in cross section................................................................................365
Figure 15.1 ......... Splitting a selected existing layer of grid cells into two new sub layers (side view). .............................414
Figure 15.2 ......... As Figure 15.1, but splitting the upper sub-layer into three sub-layers, and the lower sub-layer into two...
415
Figure 15.3 ......... Adding a new layer above the existing grid (side view) ........................................................................416
Figure 15.4 ......... The Create Transmissibilities and NNCs panel. ...................................................................................422
Figure 15.5 ......... The Vertical Pinchout tab......................................................................................................................424
Figure 15.6 ......... The Areal Pinchout tab .........................................................................................................................424
Figure 15.7 ......... The Advanced Options tab ...................................................................................................................425
Figure 16.1 ......... Property to edit or create panel.............................................................................................................436
Figure 16.2 ......... Create Property Type panel ..................................................................................................................437
Figure 16.3 ......... Property creation parameters section ...................................................................................................438
Figure 16.4 ......... Edit scope section.................................................................................................................................438
Figure 16.5 ......... Generate by section..............................................................................................................................439
Figure 16.6 ......... Expression Builder panel ......................................................................................................................441
Figure 16.7 ......... Calculator folder ....................................................................................................................................444
Figure 16.8 ......... Run Differencing folder .........................................................................................................................444
Figure 16.9 ......... Boundary interpolation .........................................................................................................................445
Figure 16.10 ....... Points Interpolation ..............................................................................................................................445
Figure 16.11 ....... Control buttons......................................................................................................................................446
Figure 16.12 ....... Grid block boundaries do not follow the detailed fine grid ....................................................................465
Figure 16.13 ....... Logical coordinate interpolation property assignment honors layers ....................................................465
Figure 16.14 ....... Determining the saturation given a capillary pressure value.................................................................477
Figure 16.15 ....... Relative permeability curves .................................................................................................................480
Figure 16.16 ....... Determining the saturation given a fractional flow value.......................................................................482
Figure 16.17 ....... Point labels on the reference cube and the grid block ..........................................................................485
Figure 16.18 ....... Interpolating a 2x1x3 fine grid in a grid block........................................................................................485
Figure 18.1 ......... Vertical fractured well grid, showing well control parameters ...............................................................506
Figure 18.2 ......... Horizontal fractured well, showing well controls parameters ................................................................507
Figure 20.1 ......... Example of determining the component weightings across an I fault ...................................................562
Figure 20.2 ......... Illustration of fault thickness calculation incorporating rock types brittleness .......................................563
Figure 20.3 ......... After Yielding et al, 1997.......................................................................................................................564
Figure 20.4 ......... A schematic diagram of two cells separated by a fault .........................................................................566
Figure D.1 .......... An example of a structured grid of quadrilaterals .................................................................................762
Figure D.2 .......... The coordinate tube with coordinate lines as edges.............................................................................763
Figure D.3 .......... Grid blocks obtained by slicing coordinate tubes..................................................................................763
Figure D.4 .......... A boundary, two i-faults and a single j-fault ..........................................................................................765
Figure D.5 .......... Smooth extensions of faults to the boundary .......................................................................................766
Figure D.6 .......... Control lines with some additional lines - zero smoothness..................................................................767
Figure D.7 .......... Control lines with some additional lines - with smoothness ..................................................................767
Figure D.8 .......... Fig. 5. An example of isotropic gridding between two faults .................................................................770
Figure D.9 .......... Fig. 6. An example of anisotropic gridding between two faults .............................................................770
Figure D.10 ........ An example where FAULTS keyword cannot fully represent simulation grid location ..........................771
Figure H.1 .......... Pairs used in an experimental variogram calculation............................................................................816

List of Figures
Figure H.2 .......... Octant search .......................................................................................................................................817
Figure H.3 .......... Super block search ...............................................................................................................................821
Figure I.1 ........... 3D Viewer in Digitize mode...................................................................................................................830
Figure I.2 ........... Digitized sloping fault............................................................................................................................831
Figure I.3 ........... Invalid fault polygon ..............................................................................................................................834
Figure I.4 ........... Valid fault polygon ................................................................................................................................834
Figure I.5 ........... Digitizing a bounding polygon...............................................................................................................836
Figure J.1 ........... Convergent Gridding.............................................................................................................................840
Figure J.2 ........... Convergent Gridding: First Iteration......................................................................................................841
Figure J.3 ........... Convergent Gridding: Second Iteration ................................................................................................842
Figure J.4 ........... Convergent Gridding: Third Iteration ....................................................................................................843
Figure J.5 ........... Convergent Gridding: Fourth Iteration ..................................................................................................844
Figure J.6 ........... Faulted Surface from Convergent Gridding ..........................................................................................845
Figure K.1 .......... PostScript panel....................................................................................................................................853
Figure K.2 .......... Write Image panel.................................................................................................................................855

List of Figures
List of Tables
Table 2.1 Type of operations allowed on FloGrid models........................................................................................28
Table 5.1 The default push button action.................................................................................................................80
Table 5.2 Panel interaction ......................................................................................................................................82
Table 5.3 Table navigation.......................................................................................................................................83
Table 5.4 Window items...........................................................................................................................................84
Table 5.5 Interaction with a dropdown list box .........................................................................................................85
Table 5.6 Open Inventor settings .............................................................................................................................95
Table 5.7 OIFloViz Settings .....................................................................................................................................96
Table 5.8 GeoFrame settings ..................................................................................................................................96
Table 5.9 RTView settings .......................................................................................................................................96
Table 12.1 Algorithms available for selection in the algorithm tab ...........................................................................243
Table 15.1 Effects of the PINCH keyword arguments .............................................................................................425
Table 16.1 Examples of operands and property types ............................................................................................439
Table 16.2 Arithmetic operators grouped by precedence, highest at top ................................................................442
Table 16.3 Relative and combinational operators in order of precedence...............................................................443
Table 17.1 Upgridding methods ...............................................................................................................................489
Table 25.1 Event names and associated event related data ...................................................................................634
Table 25.2 Event file UNITS keywords ....................................................................................................................635
Table 25.3 Recognized event file length UNITS (units) ...........................................................................................635
Table 27.1 Nodes available in the 2D tree ...............................................................................................................650
Table 29.1 Expression Calculator standard operators .............................................................................................697
Table 29.2 Expression Calculator relational operators ............................................................................................697
Table 29.3 Expression Calculator functions.............................................................................................................697
Table 29.4 NULL handling rules ..............................................................................................................................698
Table A.1 Standard Calculator keyword descriptions.............................................................................................705
Table A.2 Built-in constants....................................................................................................................................710
Table A.3 Built-in functions.....................................................................................................................................711
Table A.4 Supported operators ..............................................................................................................................713
Table A.5 Symbol functions....................................................................................................................................714
Table A.6 Variables defined when simulation property editing...............................................................................727
Table A.7 Variables defined when editing Property Model properties....................................................................728
Table A.8 Simulation Property Editor example scripts ...........................................................................................734
Table A.9 Property Model Property Editor example scripts....................................................................................734
Table B.1 FloGrid License Features.......................................................................................................................756
Table E.1 Geolith keywords supported by FloGrid .................................................................................................801
Table F.1 Data types and methods of I/O ..............................................................................................................803
Table G.1 Property names......................................................................................................................................811
Table I.1 Mouse controls for digitizing using pick points .......................................................................................837
Table K.1 Configuration file settings.......................................................................................................................855

List of Tables
New developments
Chapter 1
Developments in 2007.1
Maintenance of this application is continuing until further notice.
FloGrid User Guide New developments 13

Developments in 2007.1
Developments in FloGrid 2006.1
Seismic data handling is no longer supported in FloGrid. We recommend use of Petrel for the
complete workflow from seismic data to reservoir simulation. Please contact your local support
organization for further information.
14 New developments FloGrid User Guide

Developments in FloGrid 2006.1
Introduction
Chapter 2
Overview
FloGrid is an interactive application designed to build high quality reservoir models from
interpreted geological and geophysical data for reserves estimation, fluid flow simulation using
ECLIPSE, and reservoir development planning. The core 3D structured corner point gridding
and upscaling technology employed is recognized to be one of the most advanced, robust and
reliable in the engineering and petroleum industry for the construction of reservoir simulation
models.
This is augmented by advanced geostatistical property population methods, detailed fault
transmissibility computation, and a simulator interface for the creation, conditioning and
calibration of reservoir models. Drillable wells and laterals can be easily located and quickly
simulated to evaluate reservoir development options.
FloGrid has basic structural modeling capabilities that are complemented by the ability to
interface with external geological modeling packages. FloGrid receives 3D geological models
delivered in the POSC standard RESCUE format from all vendors that are able to export in this
format. Traditional 2D workflows are also supported through the mapping canvas.
Multiphase and multilevel upscaling techniques are available for generating relative
permeability and capillary pressure curves that are strongly coupled to the underlying
geological model. Unstructured grids can be generated and properties upscaled for simulation
of both full field and detailed well models.
Major Features
• Comprehensive 3D visualization of all input and generated data (maps, well paths,
completions, logs, markers, scatter sets, contours, faults traces/surfaces, RESCUE
geological models, simulation models, streamlines, line graphs).
• 2D mapping canvas
• Structural framework construction
FloGrid User Guide Introduction 15

Overview
• Geological and simulation model creation
• Structured grid generation
• 2D well log correlation canvas
• Geostatistical property population and data analysis
• Volumetrics
• Fault property calculation
• Streamline simulation setup and management
• Well planning
• Multiple realization generation and statistical analysis tools
• Unstructured grid generation
• A command language for recording and replaying all activities.
• Interactive and programmable calculators
The above functionality is presented to you using a data tree, a 3D Viewer, a set of 2D viewers
and application modules. Tool bars and drop-down menus on data tree nodes provide access to
most frequently used features.
16 Introduction FloGrid User Guide

Overview
FloGrid Tools
New Workflow
In previous versions of FloGrid, the workflow was essentially:
• Load maps, fault traces, wells
• Build the Structural Model
• Build the Property Model
• Build the simulation grid
• Upscale
• Export grids, properties, well trajectories to ECLIPSE.
Or, when a 3D property model was available from an external application, for example
RESCUE, the workflow was:
• Load wells, property model (RESCUE, SGM, GeoLith)
• Build the simulation grid
• Upscale and Export
The inclusion of the Property Population feature in version 2002A has resulted in a change to
this workflow. Note that a corner point grid is used for both property modeling and simulation.
Therefore, gridding is performed immediately after building structure. A Fault Framework is
built when creating the wireframe structure and this combination is now called a Structural
Framework; it replaces the old Structural Model.
The new workflow is:
• Load maps, fault, traces, wells
• Build the Structural Framework
• Build the corner point grid
• Populate grid with properties to create the property model.
• The rest of the workflow follows as before.
The new features and enhancements to existing features mean that the number of possible
workflows is immense. A special module, Create Model, has been designed to aid you in
managing the various workflows. The old workflows are still supported.
Tasks in a common modeling workflow

1 Set preferred units system.
2 Load data, visualize and perform quality and consistency checks.
3 Define the surface model.
4 Construct depth structure and thickness maps or import from external application.
5 Build structural framework from maps and faults.
6 Create model for geological property population.

FloGrid Tools
7 Build 3D structured corner point grid on the Structural Framework.
8 Populate 3D grid with properties.
9 Run volumetrics and assess reserves.
10 Compute fault properties.
11 Run streamline simulation.
12 Create simulation grid on ‘best’ geological model, upscale and export to ECLIPSE Office.
A number of loops and iterations are possible based around this fundament workflow, especially
the analysis of uncertainty through multiple realizations, and well planning tasks. For more
examples on possible workflows see "Typical Workflows" on page 30.
Data Loading
The first task in the model construction workflow is the loading of basic data into the
application. A variety of generic loaders and formatted loaders for available data types are
provided to make data loading an efficient process.
As FloGrid works, data loading commands are being automatically saved to a command file.
This file can be played back at the start of any session to quickly reload all data back into the
system. Alternatively, a workspace of the entire project can be saved at anytime and restored
later.
Structural Framework
The Structural Framework module supports the creation of 3D Structural Frameworks from
surface maps and fault traces. It creates unit surfaces (horizons) from maps using surface type
(horizon/unconformity) and topology (above/below). These units are split into block units using
fault centre lines and the user defined boundary. The collection of the outlines/edges of the
block units forms what is known as the wireframe of the Structural Framework.
The 3D Fault Framework is automatically created by constructing fault planes using up and
down thrown fault traces. You can now visualize the entire fault system in 3D and correct fault
slopes and fault-fault intersection errors. The intersection of two faults is represented by a
common coordinate line.
The block split model is used to sample depth structure during 3D grid construction. The Fault
Framework is the source for a gridding control framework which is used by both the Structured
and the Unstructured Gridders. The slope of the 3D grid coordinate lines is entirely dependent
on the gridding control framework and controls the shape of a grid around faults. The Fault
Framework / Gridding Controls Editor module, is launched using the Edit menu on a fault
framework or from the gridding controls node.
The gridding control framework can be edited to custom design the 3D grid. In edit mode you
can visualize the possible orientation of the 3D grid coordinate lines. Changing the shape of the
gridding controls only affects the grid, the original Fault Framework is untouched.
Importing a RESCUE model automatically creates a wireframe and an editable Fault
Framework. ECLIPSE corner point grid geometry files can be imported and the Structural
Framework reverse engineered. The faults are extracted by analyzing the split node information
and the simulation layers are assigned to a single unit.

FloGrid Tools
Model Creation
A FloGrid model is a 3D model with structure and properties. They are central to FloGrid and
all the major workflows and tools operate on FloGrid models. The structure of these models are
defined either by structured corner point grids, implicit grid geometry, or unstructured grids.
This gridded structure is based on the Structural Framework model. The pre-2002A map based
property model is an example of a FloGrid model with implicit geometry. In the new workflow
geological models have a structured corner point grid. RESCUE 3D geological models can have
either implicit or corner point geometry depending on the vendor implementation. Simulation
models are either structured corner point or unstructured. The underlying principal is that all of
them have structure and properties.
The Model Creation module is the starting point in the FloGrid Model construction workflow.
You can choose either to build a new grid, import a model or create a map-based model.
Depending on your intent the following options are provided for you to choose the basis;
structural framework, the grid type or the filename of the model to import.
You can choose to derive another model by upgridding an existing FloGrid Model. This is a
scientific way of quickly producing a coarsened model from a fine scale geological model. Such
a model can sometimes provide better upscaled properties for fluid flow simulation.
Existing ECLIPSE models can be imported and used a FloGrid Model or edited, updated with
LGRs and globally refined or coarsened.
Structured gridder
The Structured Gridder module is used to build structured corner-point grids and properties
using the Fault Framework. For each FloGrid Model the basic Fault Framework is copied to
create a gridding controls. This gridding controls control the areal shape of the grid and the slope
of coordinate lines. The gridding control framework can be edited to produce a grid that
adequately represents complex geometry and/or is suitable for flow simulation.
You can choose individual gridding control parameters; to distort the grid to conform to faults
in the I and J directions, zigzag faults, slope to a fault, ignore the fault slope and slope-snap to
a fault. Ignore implies that the gridding control is not used in the slope control the corresponding
fault is not verticalized but coordinate lines along the fault align with the local slope. The slope-
snap option applies to zigzag faults and snaps the grid corners to the closest point on the
gridding control plane.
Note Gridding from frameworks is new in FloGrid 2002A and uses a revised algorithm. The
old workflow using control lines is still available. However, the control line workflow
does not provide the flexibility of specifying individual slope controls for faults.
Three gridding approaches are supported:

FloGrid Tools
Corner point gridding
This option allows you to specify a flexible gridding boundary and to control areal and vertical
grid size and quality. Areal Grid control parameters include global Nx, Ny or Dx and DY,
orthogonality, and smoothness factors. Sub gridding Nx and Ny parameters fine control the
distribution of i- and j-rows and columns in different areas of the grid. Coordinate lines may be
sloped or vertical. Vertical layering is based on the reservoir units with common and advanced
options for subdividing units into layers.
Cartesian and radial local grid refinement is supported. Cartesian local grid refinements can be
structure sampled to include a high amount of detail.
Faults can be vertically zigzagged using the IJK Faults option. This allows you to model
complex geometry with minimal interaction provided the FloGrid Model has the appropriate
structural representation. The flow across such fault is controlled by generating MULTNUM
regions and transmissibility modifiers.
Rectangular gridding
This allows you to specify a rectangular boundary with constant or variable dx and dy spacing.
The coordinate lines are restricted to vertical. Similar vertical layering, local grid refinement
options, and fault modeling options are available as in the corner point approach.
Upgridding
This approach constructs simulation grids by combining rows, columns and layers of a
geological model into coarser simulation cells. Upgridding allows significant geological
features such as high permeability streaks or large contrasts in properties between geological
layers to be captured more accurately in the resulting simulation grid. Algorithmic (flow based
and variability) and manual upgridding techniques are supported.
Note This option can only be used to construct a simulation model from a single block unit
of a geological model, except in the case of geological models that have an underlying
single grid. For this case only the Global grid can be used for variability based
upgridding. A further restriction on upgridded Flogrid models is that the simulation
model boundary matches the block unit boundary.
Flow based upgridding is restricted to GEOLITH and SGM models without inactive cells. The
variation method is available on all types of model, with or without inactive cells.
The Structured Gridder module can be used to import ECLIPSE / FrontSim initial and
recurrent properties and display streamlines. Imported simulation properties can be back
populated onto the fine scale model from which the simulation model was generated. This
allows simulation properties to be used in the modeling of the static geological model.
Using an imported grid

This option, in the Structured Gridder, allows you to import, visualize and edit an existing
structured simulation grid from a file. The grid file can be in GRID or EGRID format. The grid
can contain LGRs, but these must all be structured LGRs. An imported grid is not built from a
property model, so properties can not be upscaled on it. The Simulation Property Editor can
be used on an imported grid.

FloGrid Tools
GRDECL import
You can read the grid and properties from an ECLIPSE keywords file in ASCII format
(GRDECL file). This includes LGRs. Property types found in the file are assigned to the correct
FloGrid property type whenever possible.
Property Population
Property Population provides the ability to populate 3D structured grids with facies and
petrophysical properties. Fluvial channel systems can be realized using object simulation
techniques. The module contains integrated data analysis tools.
The Property Population dialog allows you to select the geological units to populate, specify
the primary and secondary input data, select population algorithms and specify output masks to
select specific zones within the units for population. Population parameters can be saved in
parameter sets and the model populated in batch mode using multiple parameter sets.
The following input data types are supported: Well Logs, Property Maps, 3D Property Grids,
and Scatter Sets.
The following property population algorithms are available: Distance To Nearest Neighbor,
Constant Assignment, Nearest Neighbor, Inverse Distance, Ordinary Kriging, Simple
Kriging, Collocated Cokriging, Sequential Indicator Simulation, Sequential Gaussian
Simulation, Sequential Gaussian Cosimulation, Truncated Gaussian Simulation, Fluvial
Object Simulation.
Volumetrics
The Volumetrics module is launched on a FloGrid Model to produce volumetric parameters
and summations for estimating reserves. Porosity and net-to-gross parameters are provided as
arrays or constants. You can define equilibration regions using units, block or the property
editor. Fluid contact sets can are assigned to the various equilibration regions. Saturations
maybe derived from contacts, arrays or input as constants.
Volumetrics can be performed on the entire model or a selected potion of the model. Reporting
by equilibration regions, block, units or any user defined integer property array is possible.
Reports can be displayed in tabular form, graphed or saved to spread-sheet compatible files.
Volumetrics on multiple realizations can be performed and the result analyzed using statistical
tools.
Upscaling
The Structured Gridder Properties module allows you to generate single and multi-phase
properties for structured grids using a suite of upscaling and editing tools. Upscaling is normally
done from the source FloGrid Model that was the basis for the creation of the target model.
However, you could choose to upscale from another FloGrid Model provided the two models
are structurally consistent.

FloGrid Tools
A variety of upscaling, averaging and cell geometrical attribute computation methods are
available. Upscaling is done on a cell by cell process involves rigorous sampling of the fine
scale model. Permeability upscaling can be done using statistical, flow based algebraic, and
pressure solver methods with complex boundary conditions. An adjoint method is available for
high speed flow based upscaling. Strictly, upscaling should be validated by flow simulations on
fine and coarse scale models however one could use the statistical diagnostics properties for
preliminary analyses. In addition half block permeability can be upscaled to check that variance
in permeability with a grid block is acceptable.
Upscaling methods can be applied selectively to different areas of the model. The fine scale
permeability distribution may provide clues to the optimal usage of the different upscaling
methods in different regions of the model.
Multiphase and multilevel upscaling methods are available for computing relative permeability
and capillary pressure curves for use in simulation models. The multiphase upscaling module
requires that the core level data has been loaded after launching the SCAL module. The main
methods for computation of relative permeability involve the pressure solver upscaling method
with the assumptions of capillary equilibrium (segregated flow) or constant fractional flow
(diffused flow). In addition there are simpler methods assuming constant saturation or using a
majority vote.
The Multi-level option provides the functionality required to pass data between models which
are typically built at different scales. This is done by loading selected upscaled properties from
one model into SCAL records and then using the data in the SCAL records to create new
properties on the fine scale representation of the other (typically, the next level up) model.
Fault Property Calculation

The Fault Property Calculator module allows you to systematically calculate fluid flow
properties and sealing potential for faults in a structured corner point FloGrid model. The first
objective is to describe the thickness and permeability of the fault zone. Since the fault zone is
not explicitly modeled in the grid the effect of the fault is communicated to the simulator using
transmissibility modifiers on cell faces on either side of the fault.
The module uses geological parameters such as Vshale, fault displacements, and the rock types
on both sides of the fault to estimate fault zone thickness, permeability, and sealing potential.
Cell face transmissibility are computed and exported as keywords for use by the ECLIPSE and
FrontSim simulators.
The Fault Property Calculator module also enables you to assign blanket modifiers to
completely or partially seal a fault and define threshold pressures that control when flow is
allowed to occur depending on the pressure differential across the fault. All calculated fault
properties may be visualized as Allen Diagram type displays in the 3D Viewer.
Simulation Interface
The Streamline Simulation module is intended to assist you to quickly set up and run simple
simulation models using FrontSim or ECLIPSE, for the purpose of dynamic conditioning, tracer
analysis, well placement analysis, waterflood pattern optimization, ranking geological models,
etc. Basic simulations can be set up with minimal user input for PVT, equilibration, and
saturation tables. Quickly define constant well production and injection rates and the length and
number of simulation timesteps. The wells trajectory locations are automatically computed for

FloGrid Tools
the current 3D grid. Select options for producing various outputs (including streamlines from
FrontSim), write out the simulation deck, add the run to a queue and start the run. When the run
finishes summary results are automatically loaded. Streamlines are loaded on demand and
displayed on the 3D Viewer along with the model and other data, for example wells, simulation
grid, fault properties or property model slices.
The module comprises two windows, the Simulation Manager and the Simulation Setup.
The Simulation Manager is for viewing graphical output from the simulator and for managing
and running queued simulation data sets.
Multiple realizations of porosity and permeability for the current model can be used to generate
multiple runs. Runs for other models can be generated and queued as well. The queue can be
started when all possible realizations from one or several models are ready.
The Simulation Manager provides the statistical tools for analyzing multiple realization from
both simulation and volumetric runs.
Well Planning
The Well Planning tool is a collection of features that allow the creation and placement of well
paths within the reservoir. Well paths can be edited in the 3D Viewer and constrained to honor
drilling constraints while passing through target points. Well paths can be constrained to follow
a geological unit, layer or surface. A quick and easy way of defining vertical wells to target
remaining hydrocarbon areas is provided. Wells can be auto completed to lie within units or
completion ranges can be edited interactively on the well bore in the 3D Viewer. When a well
path is satisfactorily placed the target points or the deviation points can be transferred to the
Drilling Office application for defining the complete drilling plan.
Special Core Analysis

This module provides integrated core, relative permeability and capillary pressure functionality
for use when doing multiphase and / or multilevel upscaling within FloGrid. The module is also
available as stand alone application.
The module has facilities to store SCAL data on a core plug basis. Core plug defined attributes
can be used to organize this data, for example, data from cores of a certain rock type and
different porosity range can be grouped / sub grouped. This data can then be averaged, smoothed
and fitted to standard relative permeability models and capillary pressure converted to J-
functions.
Saturation logs can be used to create saturation versus height relationships.
Capillary pressure and relatively permeability curves are merged into tables with consistent
end-points. The tables are output in a format for input into ECLIPSE and FrontSim simulators.
The tables are assigned to each cell in the simulation model according to specified criteria, for
example, rocktype and porosity.
The module can be used for direct creation of saturation tables and region distributions without
performing multiphase upscaling.

FloGrid Tools
Mapping
The 2D Mapping Canvas module is used to generate mesh maps and to display contour and
color filled maps. The canvas has its own data tree which duplicates the tree in the associated
with the 3D Viewer with relevant items. All items can be viewed on the 2D canvas. Mesh maps
can be generated using proprietary interpolation algorithms and a choice of input data; scatter,
markers, fault traces, user defined contours, simulation properties, and input mesh maps.
Generated contours can be saved and viewed in the 3D overlaid on surfaces.
An option exists to quickly create thickness scatter sets from well markers. Scatter data,
contours and fault traces can be created by digitalization using a mouse. A mesh map calculator
is available to perform arithmetic and logical operations to derive new mesh maps or update
existing maps.
You can lump initial 3D grid properties across multiple layers. Lumped or single layer
properties can be used to generate and display contours to show trends. and back contour
simulation grids. You can compute a new map from another map using the Mesh Map
Calculator panel.
2D Well Log Correlation Canvas

The Well Log Correlation Canvas is intended to display well log curves, markers, and marker
correlation in a 2D view for the purposes of visual inspection of input logs, correlations, lumped
logs used for property population and synthetic logs. Logs for multiple wells can be displayed
and flattened or hung from a selected marker to check correlations. Multiple logs can be
displayed per well. The canvas also allows creation and editing of markers.
Unstructured gridder
The Unstructured Gridder generates simulation grids, cell properties, and well connections for
simulation using geological model definitions from the "Structural Framework" on page 175
and "Geological Property model" on page 215. It can generate prismatic PEBI and triangular
grids with vertical or piece wise linear (segmented) coordinate lines as well as handle cross-
sections of models.
All reservoir data must be imported and structural or property models must be built before
creating a model within the Unstructured Gridder module. If any changes are subsequently
made to the reservoir data they may not be correctly reflected in the gridder.
Open the Unstructured Gridder window using Tools | Old Workflows | Unstructured
Gridder.... This window has a menu bar from which various menu options can be selected that
allow you to create and edit unstructured grid models and a display area.

FloGrid Tools
Multiple Realizations
The Multiple Realization facility allows you to generate realizations based on combinations of
properties that exist on structured grid models. Model property realizations can be generated by
geostatistical simulation algorithms in the Property Population module. In addition, you could
construct different 3D grid model on the same reservoir, for example, fine and coarse scaled
models. The Volumetrics and Simulation modules can process these multiple realizations; and
the results are viewed in the Simulation Manager.
A single realization can only contain one property of any given type. For example, only one
Porosity property or PermX property is allowed. If a model has two Porosity properties defined
(called Poro1 and Poro2, say) and three Perm properties defined (perm1, perm2, perm3), then
six realizations of the model (2 x 3) can be generated which use these property combinations:
Poro1 , Perm1
Poro2 , Perm1
Poro1 , Perm2
Poro2 , Perm2
Poro1 , Perm3
Poro2 , Perm3
If there are many variations of properties existing on a model then many realizations can be
generated. You can choose to use a selected subset of the generated realizations for processing
by omitting invalid combinations.

FloGrid Tools
Create a Model
A FloGrid model is a 3D object with structure and properties. They are central to FloGrid and
all the major workflows and tools operate on FloGrid models. They can be map based, multi-
block with a grid for each block, corner point or unstructured grid based. The underlying
principle is that all of them have structure and properties. For models built in FloGrid, the
properties are created in a second step using upscaling or geostatistical techniques. For imported
models, both structure and properties can be imported as one unit.
This section contains information on the following options:
• "Model creation" on page 26.
• "Options" on page 26.
• "Confirmation dialogs" on page 28.
Model creation
The Model Creation module gives you a set of options for three major aspects of model
creation - the how to build it option, the structural basis for the model and the grid type.
The how to build it option specifies the process by which the new model is to be created. The
structural basis option allows you to choose between different structures (already loaded into
FloGrid) on which you can base the new model. Last, you must select the type of grid
(structured or unstructured) that you wish to create.
The intent text box always shows what workflow options are available to you for any
combination of choices.
Options
This section contains information on:
• "Name" on page 26.
• "How to build it" on page 26.
• "Structural basis" on page 27.
• "Grid type" on page 27.
• "Data Selections" on page 27.
Name
This is the name of the new model.
How to build it
These options allow you to choose how to build the model.
Build new grid

A new 3D grid is to be constructed.

Create a Model
Import model
The 3D grid structure is to be imported.
Map-based property model

A map-based model has direct assignment of property maps to the block units in a map based
structural framework.
Note If the file is an ECLIPSE grid, you have choose whether to create a structured or an
unstructured model and it is possible to optionally create a Structural Framework for
further model creation.
Structural basis
The Structural Basis of the new model is one of:
The new model’s grid structure is to be based on the faults and surfaces in a Structural
Framework.
A Structural Framework is either built in FloGrid or “back populated” from an imported
model (for example an ECLIPSE grid or a RESCUE model).
Existing FloGrid Model

The new model’s grid structure is to be based on the grids inside the chosen existing FloGrid
model. For example, a new model can be created by upgridding a corner point grid inside an
existing FloGrid model.
Imported file
The new model’s grid structure is to be taken directly from an imported model.
This can be an ECLIPSE grid, RESCUE, OpenSGM or Geolith.
Grid type
You may select the grid type of the model.
Structured
Unstructured
Unstructured (dual source)

The dual source option allows a grid to be built from one Structural Framework and the
properties to be upscaled from a model based on another Structural Framework.
Data Selections
Existing Structural Frameworks
A selection list box with existing Structural Frameworks.

Create a Model
Existing FloGrid Models
A selection list box with existing FloGrid models
File to import
A file selection dialog.
Table 2.1 Type of operations allowed on FloGrid models
Map based 2D
Structural Basis Build New Grid Import File
Model
Create rectangular, Create a property model
corner point or by assigning property
Structural unstructured grid, maps to a structural
Framework usable for property framework
population or upscaling
from another model
Existing FloGrid Create new grid by
Model upgridding
Refine, coarsen, add Import and visualize.

LGRs, edit cell Subsequently, edit or
geometry and create derived models.
properties. Also, you Also, you can create a
Imported file:
can create a structural structural framework
ECLIPSE grid framework from which from which you can
you can create new create new structured or
structured or unstructured grids
unstructured grids
Create rectangular, Import and visualize.
Imported file: corner point or Subsequently, edit or
RESCUE unstructured grid or create derived models.
upgrid
OpenSGM unstructured grid or create derived models.
upgrid
Geolith unstructured grid or create derived models.
upgrid
Confirmation dialogs
When you have chosen how to build the new model, its structural basis and grid type, you may
be presented with further sub-options dependent on your initial choices.
• "More detailed grid types" on page 29
• "Gridding controls" on page 29.
• "Dual Porosity" on page 29.

Create a Model
• "Grid conversion" on page 29.
More detailed grid types

Structured
Corner Point Grid

Allows you to create a corner point grid with sloping coordinate lines.
Vertical Rectangular
Allows you to create a rectangular areal grid with vertical coordinate lines.
Upgridded
Allows you to build a model whose structure is based directly on the 3D grid inside an imported
geological model.
Gridding controls
This allows you to choose to control your areal grid and slope on either the new (2002A or later)
Fault Framework or the older (2001A) Control lines.
ECLIPSE grid use

You can choose to create a Structural Framework (an automatic geological interpretation of
the imported ECLIPSE grid) or you can choose to modify the imported grid by adding LGRs or
refining or coarsening the grid.
.GRID format options

If you have chosen to import a .GRID file then you can have it converted during the import to
EGRID (corner point) format.
If it is converted to EGRID format then you can take advantage of the Structural Framework
creation, the Grid Editor and the Refine and Coarsening options.
Note If the grid has curved coordinate lines they are made straight during the conversion.
Dual Porosity
Certain grid import formats (for example .GRID) do not carry the information about whether
they are to be treated as dual porosity models or not. In these cases the confirmation dialog
allows you to choose how the grid (and subsequently imported properties) are to be treated.
Grid conversion
You can choose to convert your structured grid to an unstructured data structure on import. Use
this option if you want to generate multi-point transmissibility using the Multi-point Flux
option.

Create a Model
Typical Workflows
FloGrid has a multitude of entry and exit points, and a large set of tools or application modules.
Hence, the total number of distinct workflows is quite significant. This section provides an
overview of some typical workflows, whilst covering most of the major modules. Your own
workflow may involve a part of one of the workflows here or an amalgamation of several.
Building a simulation model from maps

The input data is a set of mesh maps and fault traces generated in an external mapping package;
and well deviation surveys. The output is a simulation grid and cell properties. The workflow
steps are:
• Creating a structural framework, a property model, a simulation grid and upscaling
properties.
• Set the unit system in which you wish to work, using menu option Preferences | Set
External Units. Import mesh maps (see "Data tree" on page 333), fault traces (see "Fault
trace import" on page 365) and well deviation surveys (see "Import well deviation surveys"
on page 376) using the File Import menu or the drop-down menus from the respective
parent nodes on the data tree.
• View the imported data by ticking the selection boxes on the data tree and edit and clean up
any data item using the appropriate editor (see "Edit Menu" on page 112) launched using
the drop-down menus on the tree nodes.
• Once the data is acceptable, create a Structural Framework (see "Structural Framework"
on page 175) using the module launched from the tool bar or the tools menu. The Fault
Framework may be edited (see "Fault framework editor" on page 191), intersections
redefined prior to model building.
The model building for this workflow has two stages. The first stage is building a map based
property model. The second stage is to build a 3D cellular model for simulation.
• A map based model is built with the Create Model tool (see "Create a Model" on page 26).
On the panel the build method should be set to Map-based Property Model and the
structural basis is Structural Framework. This opens the Map Based Property Model
Builder (see "Geological Property model" on page 215). The appropriate properties should
be dragged and dropped on to each unit.
• At the second stage, a 3D cellular model is built with the Create Model tool. On the panel
the build method should be set to Build New Grid, the structural basis is Structural
Framework and the grid type is Structured. This launches the Structured Gridder (see
"LGRs, Resizing, Aquifers and NNCs" on page 407), on which the boundary, gridding
controls, areal grid and vertical gridding must be defined and a 3D grid should be built.
• The cell properties on the structured grid are generated using the Upscaling tool (see
"Structured gridder properties" on page 427). The upscaling is from the map based
model to the cell based simulation model.
• Once the properties have been upscaled, launch the Structured Gridder on the
simulation model using the edit option on the drop-down menu. Note that the edit
option on a FloGrid model opens the model editor appropriate to the type of model.
• Export the grid, cell properties and well data using the File | Export option on the
Structured Gridder module.

Typical Workflows
Building a simulation model from a RESCUE
model
The input data is a RESCUE model created in an external modelling product. The output is a
simulation grid and cell properties. The workflow steps are; creating a simulation grid,
upscaling properties.
• Import a RESCUE model (see "Importing data" on page 218) using File | Import or the
drop-down menu from the model node on the data tree.
• View the model and the structural framework in the 3D Viewer. Use model slice controls
to interrogate the model.
• Open the Create Model tool (see "Create a Model" on page 26) and set the build method
to Build New Grid, the structural basis to Structural Framework and the grid type to
Structured.
This opens the Structured Gridder module (see "LGRs, Resizing, Aquifers and NNCs" on
page 407), which should be used to build a grid.
• Generate cell properties using the Upscaler (see "Structured gridder properties" on
page 427) tool and export the grid and properties using the File | Export option in the
Structured Gridder.
Building a simulation model by upgridding

another model
The input data is an existing FloGrid model. This could be an imported RESCUE model, an
imported corner point model or one built in FloGrid. The output is a simulation grid and cell
properties. The workflow steps are:
• Creating a simulation grid using the Upgridder ("Structured Gridder Module" on
page 309), upscaling properties, running volumetrics on input and output models.
• Ensure there is a FloGrid model, for instance by importing a RESCUE model (see
"Importing data" on page 218).
to Build New Grid, the structural basis to Existing FloGrid Model and the grid type to
Structured.
This opens the Upgridder module (see "LGRs, Resizing, Aquifers and NNCs" on
page 407), which should be used to build a grid. Note that if the parent model is not a corner
point model, for example from a fault block based RESCUE model, the Upgridder is
restricted to create a simulation model only for a single fault block at a time.
• Generate cell properties using the Upscaler (see "Structured gridder properties" on
page 427) tool.
• Open the Volumetrics tool (see "Volumetrics" on page 569), select the parent model, set
Output, Properties, Contacts, Volume of Interest Reporting and perform a single
volumetrics run.
• Repeat for the upgridded model and compare volumes.

Typical Workflows
Building an unstructured simulation model
The input data is a FloGrid Model and well deviation surveys. The model can be an imported
RESCUE model, built from maps or an existing structured grid. The output is an unstructured
simulation grid, cell properties and well connections. The workflow steps are:
• Creating a simulation grid using the Unstructured Gridder), and then generating cell
properties and well connections.
• Ensure there is a FloGrid model, for instance by importing a RESCUE model (see
"Geological Property model" on page 215).
to Build New Grid, the structural basis to Structural Framework and the grid type to
Unstructured (normal).
This opens the Unstructured Gridder.
• Set well, fault, bulk and layer gridding controls using the Edit menus.
• Generate a grid, generate properties and connect wells using Grid, Property and Wells
menus. Export all simulation data using the File | Export options.
Planning new wells

The input data is an existing FloGrid Model, for instance a corner point grid (see "FloGrid
Models Data" on page 396). The output is a well trajectory file for the Schedule program and a
well target file for Drilling Office. The workflow steps are:
• Defining well heads, creating well targets, using drilling constraints and creating well
deviations. These are performed using the Well Planning tool (see "Well Planning" on
page 631).
• Once well paths have been defined, perforation intervals can be defined and synthetic logs
can be created by launching panels using the drop-down menu on selected wells (see "Wells
Data" on page 374).
• A table of targets can be exported using the drop-down menu on a well path table and a
trajectory file can be exported using the Structured or Unstructured Gridder module File
| Export menus.
Updating a simulation model and building a

derived model
The input data is an ECLIPSE grid and properties (see "ECLIPSE grid use" on page 29). The
output is an updated simulation model or a new one. The workflow steps are; open the Create
Model tool (see "Create a Model" on page 26), set build option to Use grid from imported file,
structural basis to Imported file: Eclipse grid, grid type to Structured. View the model. Add
LGRs, refine or coarsen the model using the Structured Gridder (see "LGRs, Resizing,
Aquifers and NNCs" on page 407) launched using the model Edit menu. Edit the grid nodes
using the Edit grid option on the main window. Export the modified simulation model from the
Structured Gridder.
In another scenario, instead of modifying the imported model, build a derived new model. The
workflow steps are:

Typical Workflows
• Create the imported model as before, but use the Create Structural Framework option on
the pop up panel.
• Edit the structural framework. Create a new derived model using the Create Model tool
with build type Build new grid, structural basis Structural Framework, grid type
Unstructured.
This opens the Unstructured Gridder using which a new grid and cell properties can be
created, viewed and exported.
Deriving fault transmissibility multipliers for

simulation
The input data is a RESCUE model. The output is simulator keywords defining the
transmissibility multipliers. The workflow steps are:
• Generate a structured grid. Open the Fault Property Calculator (see "Fault Property
Calculator" on page 551).
• Execute Faults, Derived Multiplier and Fault Export tabs.
This calculates fault displacement, fault thickness, shale gouge ratio, fault permeability and
fault transmissibility.
Generating and assigning relative permeability

and capillary pressure curves for simulation
The input data is a structured or unstructured FloGrid model with a simulation grid and
properties and laboratory SCAL data. The output is simulator keywords for the PROPS and
REGIONS sections defining the relative permeability and capillary pressure curves and their
assigned regions. The workflow steps are:
• Launch SCAL from the toolbar, see "Core Analysis" on page 645.
• Import lab data into it, prepare curves, average as required, generate SATNUM property for
the 3D model based on lithotypes or other derived criterion for assigning the tables.
• Export the tables and the SATNUM property.
Generating geostatistical properties

The input data is a structural framework, well logs, and markers. The structure may be imported
using a RESCUE model or built within FloGrid using map and fault data. The other data may
be imported as flat files. The output is a geological scale corner point model with geostatistical
properties. The workflow steps are:
• Create a geological scale corner point grid using the Structured Gridder,
• Determine the layering scheme for the vertical gridding by investigating the property logs
in the Well Correlation Canvas (see "2D Mapping Canvas" on page 647), opened using
the well drop-down menu.
• Open the Property Population tool (see "Property population" on page 231) and set up
primary input, lumping, algorithms, search parameters and populate porosity.

Typical Workflows
• Use the data analysis tools throughout the process.
Running a streamline simulation with multiple

realizations
The input data is a set of FloGrid models with corner point grids and multiple properties and a
set of well paths. The multiple models may be due to different layering schemes or fault
realizations and multiple properties may be due to multiple geostatistical realizations or history
matching scenarios. The output is a production profile report from a streamline simulation. The
workflow steps are:
• Open the Streamline Simulation tool (see "Streamline Simulation" on page 585) and
define the initial conditions, well targets and data set file names in the Simulation Setup
panel (see "Simulation Setup" on page 587).
• Launch the Multiple Realization Manager (see "Multiple Realizations" on page 623)
from the Simulation Setup panel, run realizations, view production profiles graphically
and export report.
Generating structure and properties from 2D

mapping
The input data is markers, contours, scatter sets and fault traces, imported using File | Import.
The output is a map based FloGrid model with structure and properties, ready for 3D gridding.
The workflow steps are:
• Open the 2D Mapping Canvas tool, see "2D Mapping Canvas" on page 647.
• Create structural and property mesh maps using the Create Mesh Map panel using the raw
data.
• Once the maps are of sufficient quality, use the Structural Framework tool to create a
structural framework and the Create Model tool to create a model using the Map-based
Property Model build type.

Typical Workflows
Main Window
The main window consists of a data tree, a 3D Viewer and a small log window. The main menus
are:
• "File Menu" on page 109
• "Edit Menu" on page 112
• "View menu" on page 130.
• "Tools menu" on page 140
• "Scene Menu" on page 144
• "Preferences Menu" on page 94
• "Window Items" on page 84
• and Help.
There are also a set of toolbars, to launch the major tools and to control the 3D Viewer.
Data Tree
The data tree displays all data items in FloGrid. Imported raw data is ordered towards the top of
the tree and derived data is ordered at the bottom of the tree. The nodes can be expanded or
collapsed as required by double clicking on the squares to left of the nodes. Data items can be
displayed on the 3D Viewer using the check boxes to the right of the nodes. Dropdown menus
launched by right mouse button clicks over the nodes provide the most frequently used features.
The tree contains the following data types:
• Surface, see "Surfaces Data" on page 341.
• Faults, see "Faults Data" on page 360.
• Wells, see "Wells Data" on page 374.
• Well Markers, see "Well Markers Data" on page 383.
• Well Logs, see "Well Logs Data" on page 386.
• Boundaries, see "Boundaries Data" on page 390.
• Structural Frameworks, see "Structural Frameworks Data" on page 393.
• FloGrid Models, see "FloGrid Models Data" on page 396.

Main Window
Main Window
Getting started
Chapter 3
Starting FloGrid
FloGrid can be started in three ways.
Using the ECLIPSE Launcher

This is available on Windows platforms. After successful installation of the SIS Simulation
Software, a program icon/short-cut is installed on the machine.
1 To start the ECLIPSE Launcher select the program short-cut from the taskbar or click on
the icon.
2 To start FloGrid program click on the FloGrid button on the launcher, select a start-up
directory when the FloGrid Launcher panel appears by browsing through the directory
tree, and click on the Run button.
Starting FloGrid on UNIX

1 Typing the @flogrid command at the prompt on the selected start-up directory in UNIX
platforms to run the start-up macro.
FloGrid User Guide Getting started 37

Starting FloGrid
38 Getting started FloGrid User Guide
Starting FloGrid
Short Tutorials
Chapter 4
Introduction
This section provides a set of short tutorials, which take you through the major workflows of
the program. It is strongly advised that you run the appropriate short tutorial prior to attempting
to using your own data and scenario. Your own workflow may involve a part of one of the
workflows here or an amalgamation of several.
Note that all tutorials require the basic FloGrid license features. Additional license feature
requirements are noted below. See "FloGrid License Features" on page 756 for more
information on licensing.
The available tutorials are:
1 "Building a simulation model from maps" on page 42.
2 "Building a simulation model from a RESCUE model" on page 46.
3 "Building a simulation model by upgridding another model and comparing volumetrics" on
page 48. (Requires gf_fg_analysis license feature.)
4 "Building an unstructured simulation model" on page 51. (Requires gf_petragrid
license feature.)
5 "Planning New Wells" on page 53. (Requires gf_fg_analysis license feature.)
6 "Updating a simulation model and building a derived model" on page 56. (Requires
gf_petragrid license feature for unstructured gridding at end.)
7 "Deriving Fault Transmissibility Multipliers for Simulation" on page 59. (Requires
gf_fg_populate license feature.)
8 "Generating geostatistical properties" on page 61. (Requires gf_fg_populate license
feature.)
9 "Running a Streamline Simulation with Multiple Realizations" on page 66. (Requires
gf_fg_analysis and gf_fg_populate license features.)
10 "Generating Structure and Properties from 2D Mapping" on page 70.
FloGrid User Guide Short Tutorials 39

Introduction
How to interact with the 3D Viewer
Note For the 2004A release we switched the underlying graphics libraries to OpenInventor,
giving greatly improved graphics performance. We took this opportunity to adopt the
OpenInventor standard mouse interactions, giving us consistency with other
OpenInventor applications such as Petrel.
The 3D Viewer has 2 distinct modes of operation: 'viewing' and 'picking'. The 3D Viewer is by
default in 'view' mode (the default cursor is a hand ), which means that you can use the
mouse buttons to rotate, translate and zoom the display. To pick on objects in the display you
must select the 'pick' mode (the cursor changes to an arrow ). In pick mode you cannot
change the orientation of the display, just pick on objects in the display.
To change mode you can either:
• use the hand and arrow button on the top left toolbar,
• use the 'P' (pick) and 'V' (view) keys,
• or use the <Esc> key to toggle between modes.
View mode
When in 'view' mode, interaction is as follows:
Rotate
Press the left mouse button and move the mouse to rotate about the model.
Translate
Press the middle mouse button and move the mouse to pan from side to side.
Zoom
Press both the Ctrl key and the middle mouse button (or left and middle mouse buttons
simultaneously) and move the mouse to zoom the display.
Note Note that the 3D Viewer displays a Perspective view by default.
Other buttons of interest on the left hand toolbar are:
Normalize Returns the model to the middle of the window.
Seek to Point Select this button and then click on a point on the model. The
3D Viewer zooms to the selected point. The ’S’ key provides a
short cut to this button.
Perspective Toggles between Perspective and Orthogonal views of the
model.
40 Short Tutorials FloGrid User Guide

Introduction
User View Returns the view to its orientation prior to a fixed view being
set (with the Set View buttons below).
Set View These 6 buttons align the view with each of the primary axes.

Introduction
Introduction
The input data are a set of mesh maps and fault traces, generated in an external mapping
package, and well deviation surveys. The output is a simulation grid and cell properties. The
workflow steps are; creating a structural framework, a property model, a simulation grid and
upscaling properties.
The files for this tutorial are in the directory flogrid/tutorials/grainne.
Hint A pre-recording of the entire tutorial can be found in the command file
_sim_from_maps.cmd.
1 Start FloGrid in the above directory or if already running select File | New
Workspace…(this clears any existing data from FloGrid).
Importing data
1 Set the unit system for the model to metric by selecting Preferences | Set External
Units... and choosing ECLIPSE-METRIC.
2 Right-click on the Surfaces data tree node to reach the drop-down menu and select Import
Mesh Maps | CPS3....
3 Select maps:
• TOPS1.SVS, TOPS2.SVS, TOPS3.SVS, TOPS4.SVS, TOPS5.SVS
• PORO1.SVS, PORO2.SVS, PORO3.SVS, PORO4.SVS, PORO5.SVS
• PERMX1.SVS, PERMX2.SVS, PERMX3.SVS, PERMX4.SVS, PERMX5.SVS
4 On the pop-up dialog with the table of maps to import, press button Create Surface.
5 On the next pop-up dialog set number of surfaces to 5 and number them top to bottom. On
the next pop-up dialog, accept the default surface names.
6 Back on the Mesh Map Import dialog, set the Surface names for the tops, porosity and
permeability maps.
• Set TOPS1, PORO1 and PERMX1 to Surface1 etc.
• Set the property of the horizon maps to Horizon,
• Set the property of porosity maps to Porosity and permeability maps to Perm.
• Press Edit and set the Vertical Unit to FEET.
7 Back on the Mesh Map Import dialog, click on OK.
8 Expand the Surfaces node on the data tree and check all the horizon nodes to display them
on the 3D Viewer.
Hint You may want to increase the vertical exaggeration and change the angle of
display to obtain a better view.

9 Use the drop-down menu on the Faults data tree node and select Import Fault Traces |
Generic....
10 Select file ID.FLT and accept defaults, press OK.
11 Check the Faults node to display all fault traces in the 3D Viewer.
12 Use the drop-down menu on the Wells data tree node and select Import Well Deviation
Surveys | GRID....
13 Select file _wells.ctl.
14 Check the Wells node to display all wells in the 3D Viewer.
Using a thickness map to define the bottom

surface
1 For each unit (layer) in the structural model, data are needed to define the top and bottom
surface. The maps imported so far define 5 surfaces and associated properties, which can
be used to build a model with 4 units. The following steps describe how to define the
bottom surface by adding a thickness map, which will result in a model with 5 units. (You
may omit these steps and build a model with 4 units.)
2 Use the drop-down menu on the Surfaces data tree node, select Import Mesh Maps |
CPS3... and select the thickness map DZ5.SVS
3 Press Edit and set the Vertical Unit to FEET.
4 Back on the Mesh Map Import dialog, set the property to Thickness and press OK.
5 Note that the imported map is listed under Unassigned Maps.
6 From the drop-down menu on the Surfaces data tree node, select Surface Table... and
press the Add Below button to add a surface representing the bottom of the reservoir.
7 On the data tree, select the Thickness - DZ5 map, drag and drop it onto the node for
Surface6
8 Return to the Surface Table and set the Thickness Reference to Surface5 (in the column
headed Th. Reference). This indicates that DZ5 represents the thickness between
Surface5 and Surface6.
9 Close the Surface Table panel.
Building a structural framework

1 Launch Structural Framework Builder from the toolbar by pressing the Structural
Framework Creation button, .
2 Create a framework, using File | Create Structural Framework... on the Structural

Framework module.
• Accept the defaults.
3 On the Boundary folder, set the boundary to Use Map Extents.
4 On the Units folder, build units using all the defaults by pressing press Build Units.
5 On the Faults folder, create fault block units using all the defaults by pressing Auto Split
Into Blocks & Block Units.

6 View the fault framework and the wireframe.
Building a map based property model

1 Launch the Create Model module from the toolbar by pressing the Create Models button,
.
2 Give the model a name and set the build type to Map-based property model.
3 Set the structural basis to Structural Framework, select the framework from the list and
press OK.
This creates a model and opens the Property Model dialog, from which you can create and
edit property models. You can close it without any actions.
Building a structured grid

1 Launch the Create Model module from the toolbar, .
2 Give the model a name and set the build type to Build new grid.
3 Set the structural basis to Structural Framework and select one from the list.
4 Set the Grid Type to Structured and press OK.
5 On the pop-up dialog, select Corner Point grid type and Fault Framework gridding
controls.
6 On the Boundary folder of the Structured Gridder, press Create, Copy... to create a new
boundary. Press Create... on the pop-up dialog and select Polygon, projection plane XY
and Top.
7 Add a horizon map to the 3D Viewer to locate the valid area of the model.
8 Digitize a boundary within the valid area of the map with four major points and any number
of minor points.
Hint The first point is major by default and the subsequent points are minor unless Ctrl is
pressed while digitizing.
9 Define an approximate quadrilateral boundary, since we are building a structured grid and
commit the edit by pressing the tickmark button. And close the Create or edit model
boundary dialog
10 On the Gridding Controls folder, of the Structured Gridder, set the type of control ID1
to J Line, ID2 to I Line, ID3 to I Line and press Apply.
Note If the fault crosses the new boundary it may not be possible to change the type.
11 On the Areal Grid folder, enter the Total Nx and Total Ny (40, 30) and build an areal grid,
by pressing Build.
12 On the Vertical Grid folder, accept the default layering and press Set Layering.
13 On the 3D Grid section, press Build..Click “continue” on the message box

14 Display the grid.
Upscaling properties
1 Launch the Upscaling module from the toolbar by clicking on the Upscaling button .
2 For the Upscale from model select the map based model and for the Upscale to model
select the structured grid.
3 Accept the default properties of porosity and permeability to upscale using the default
methods and press Upscale.
4 Expand the Properties node on the data tree and view required properties.
Exporting the upscaled model for simulation

1 Launch the Export Data dialog using the drop-down menu Export | Model item on the
corresponding FloGrid Models node, on the data tree.
2 Set the following:
• output format to GRDECL (Eclipse.GRDECL keywords),
• select Grid by checking the box in the Geometry section, then press Set Location,
enter a file name and Save
• select Well Trajectories and set file location
• select Grid Properties.
3 Press Export to export all files.
Hint When you press Save on the file name dialog, this saves the name of the file to be
created. You must press Export to write out the data.
Note For the wells defined in the file _wells.dev, WELL_4 and WELL_8 do not
intersect the grid.

Building a simulation model from a RESCUE model
Introduction
The input data are loaded from a RESCUE model created in an external modeling product. The
output is a simulation grid and cell properties. The workflow steps are; creating a simulation
grid, upscaling properties.
• The files for this tutorial are in the directory
flogrid/tutorials/RESCUE/cloudspin.
_sim_from_rescue.cmd.
1 Start FloGrid in the above directory or if already running select File | New Workspace…
(this clears any existing data from FloGrid).
Importing data
1 Use the right mouse button floating menu on the FloGrid Models tree node and select
Import Model | RESCUE... Select the file cloudspin.bin. The Set External
Property Types dialog appears. Press OK.
2 Display model on the 3D Viewer by checking the Rescue model node on the tree.
3 Expand the Properties node on the tree and select a property to view and use the IJK
buttons and the video buttons on the 3D
Viewer toolbar to view slices through the model.
4 Use the floating menu on the Wells tree node and select Import Well Deviation Surveys
| GRID....
• Select file _wells.ctl.
5 Display the wells on the 3D Viewer by checking the Wells node.

4 Set the grid type to Structured and click on OK.
5 On the pop-up dialog, select Corner Point grid type and Fault Framework (New
Workflow) for Gridding Controls.
6 On the Boundary folder of the Structured Gridder, click on Create from Structural
Framework Boundary.
7 On the Gridding Controls folder accept the default controls and click on Apply.

by clicking on Build.
9 On the Vertical Grid folder, set Layers Per Unit to 10.
10 On the 3D Grid section, select Set Layering and then Build.Click “continue” on the
message box.
11 Dismiss the Structured Gridder and display the grid.
Upscaling properties
1 Launch the Upscaling module from the toolbar, .
2 Set the Upscale from model to the RESCUE model and the Upscale to model to the
structured grid.
3 Accept the default properties of porosity and permeability to upscale using the default
methods and click on Upscale.
Exporting the model for simulation

1 Launch the Export Data using the drop-down menu Export | Model item on the
corresponding FloGrid Model node, in the data tree.
2 Set the following:
• output format to GRDECL (Eclipse.GRDECL keywords),
• select Grid by checking the box in Geometry section and set the file name and
location,
• select Well Trajectories and set file location,
• select Grid Properties.
3 Press Export to export all files.

Building a simulation model by upgridding another model
and comparing volumetrics
Introduction
The input data are loaded from an existing FloGrid model. This could be an imported RESCUE
model, an imported corner point model or one built in FloGrid. The output is a simulation grid
and cell properties. The workflow steps are; creating a simulation grid using the Upgridder,
upscaling properties, running volumetrics on input and output models.
• This tutorial requires the gf_fg_analysis license feature.
_upgrid_volumetrics.cmd.
Importing Data
1 Use the drop-down menu on the FloGrid Models tree node and select Import Model |
RESCUE.... Select the file cloudspin.bin. The Set External Property Types dialog
appears. Press OK.
3 Expand the Properties node on the tree and select a property to view.
4 Use the IJK buttons, , , , and the video buttons, , , , , ,
, on the 3D Viewer toolbar to view slices through the model.

5 Use the drop-down menu on the Wells tree node and select Import Well Deviation
Surveys | GRID....

2 Give the model name Fine and set the build type to Build new grid.
4 Set the grid type to Structured and press OK.

Building a simulation model by upgridding another model and comparing volumetrics
5 On the pop-up dialog, select Corner Point grid type and Fault Framework Gridding
Controls.
6 On the Boundary folder of the Structured Gridder, press Create from Structural
Framework Boundary.
7 On the Gridding Controls folder accept the default controls and press Apply.
by pressing Build.
9 On the Vertical Grid folder, set Layers Per Unit to 10.
10 On the 3D Grid section, press Set Layering and then press Build. Click “continue” on
the message box.
11 Display the grid.
Upscaling properties on the fine grid

2 Set the Upscale from model to Rescue cloudspin and the Upscale to model to Fine.
3 Select Porosity, Perm and CellVolume to upscale using the default methods and press
Upscale, and close the Structured Gridder Properties dialog.
Building a structured grid by upgridding

2 Give the model name Coarse and set the build type to Build new grid.
3 Set the structural basis to Existing FloGrid Model, select Fine from the list and press OK.
4 On the Upgridding folder of the Structured Gridder, set the Select fine BUG to Global
grid and press Options.
5 On the Var Upgridding Controls panel, enable the I, J and K options and select
Porosity_v0 as the upgridding property in each group on IJK directions and press OK.
6 Press Create to create the upgridded BUG and press Convert to Sim Grid to create a 3D
grid.
7 Display the grid and close the Structured Gridder.
Upscaling properties on the coarse grid

2 Set the Upscale from model to Fine and the Upscale to model to Coarse.
3 Select Porosity, PermX, PermY and PermZ, and CellVolume to upscale using the
default methods and press Upscale and close the Structured Gridder Properties dialog.
4 Expand the Properties node on the data tree and view the required properties.

Running volumetrics on fine and coarse models
1 Launch the Volumetrics module from the toolbar, .
2 Set a report name and select model Fine.

3 On the Output folder, set all outputs to On and Source to Calculate....
4 On the Properties folder:
• For the NTG property use a constant value of 0.5
• Set the Porosity property to the available porosity property array.
• For Oil Saturation use a constant value of 0.5.
• For Gas Saturation use a constant value of 0.25
• For Water Saturation set to Calculate....
5 In the Reporting folder set the level of details to Totals only, and the output units for Rock
volume to ft^3, Liquid volume to bbl and Gas volume to ft^3.
6 Press Single Run.
7 Repeat the process for model Coarse and compare the results reported to the Log Window.

Introduction
The input data are a FloGrid Model and well deviation surveys. The model can be an imported
RESCUE model, built from maps or an existing structured grid. The output is an unstructured
simulation grid, cell properties and well connections. The workflow steps are; creating a
simulation grid using the Unstructured Gridder, generating cell properties and well
connections.
• This tutorial requires the gf_petragrid license feature.
_unstr_sim.cmd.
Importing data
1 Use the drop-down menu on the FloGrid Models tree node and select Import Model |
RESCUE.... Select the file cloudspin.bin. The Set External Property Types dialog
appears. Press OK.
3 Expand the Properties node on the tree and select a property to view.
4 Use the IJK buttons, , , , and the video buttons, , , , , ,
, on the 3D Viewer toolbar to view slices through the model.

5 Use the drop-down menu on the Wells tree node and select Import Well Deviation
Surveys | GRID....
Building an unstructured grid

4 Set the grid type to Unstructured (normal) and press OK.

5 On the pop-up dialog, select Fault Framework Gridding Controls.
6 On the Unstructured Gridder, inspect the well gridding controls and the fault gridding
controls using Edit | Well Controls... and Edit | Fault Controls....
• And close both dialogs.
7 On the Edit Bulk Controls panel, launched with Edit | Bulk Controls..., set the Cells in J
to 40 and Apply, and close this dialog.
8 On the Edit Layer Controls panel, launched with Edit | Layer Controls..., set the
Number of layers per unit to 10,
9 Press Refine Selected BlockUnit(s) button, accept the default weights and press OK.
10 Press OK on the Edit Layer Controls panel.
11 Generate a grid using Grid | Generate menu, on the Unstructured Gridder, and inspect
the grid using the IJK Slicer.
Upscaling properties and connecting wells

1 Generate cell properties and transmissibilities using Property | Generate Real... on the
Unstructured Gridder module and accept the defaults.
2 Inspect the properties in the 3D Viewer.
3 Generate well connections using Wells | Auto Connect....
Exporting the model for simulation

1 Export a grid file for ECLIPSE using File | Export Grid Keywords... and accept all the
defaults on the Export Grid Keywords panel.
2 Export a well completions file for ECLIPSE using File | Export Well Keywords....
3 Export a well trajectory file for Schedule using File | Export Well Trajectory....

Planning New Wells
Introduction
The input data are loaded from an existing FloGrid Model, for instance a corner point grid. The
output is a well trajectory file for the Schedule program and a well target file for Drilling Office.
The workflow steps are; defining well heads, creating well targets, using drilling constraints and
creating well deviations are performed using the Well Planning tool. Once well paths have been
defined, perforation intervals can be defined and synthetic logs can be created. A table of targets
can be exported using the drop-down menu on a well path table and a trajectory file can be
exported using the Structured or Unstructured Gridder module.
• The files for this tutorial are in the directory -
• This tutorial requires the gf_fg_analysis license feature.
_plan_wells.cmd.
Importing data and building a structured grid and

upscaling
This part of the tutorial is already documented in a previous tutorial, "Building a simulation
model from a RESCUE model" on page 46.
1 Please run that tutorial or its command file, _sim_from_rescue.cmd, first.
Plan Wells
1 Display all the existing wells by checking the Wells node.
2 Launch the Well Planning module from the toolbar, .
3 Enter well name New1 on the empty last row of the table.
New1 will be a new horizontal well.
4 Switch on the Pick New Wellhead Locations option and click on the 3D Viewer to define
a location for the well head. Press Apply to create the well.
5 Expand the Wells node on the data tree and find New1. Right-mouse click on the node for
New1 and select Edit Wellpath... from the drop-down menu.
6 On the Edit Wellpath panel, select as Constraint, Structural Framework “Rescue
cloudspin (sm)” and the default Constraint Option to Center in “Houston”.
This constrains the horizontal well track, to be digitized in the center of unit Houston.

Planning New Wells
7 Switch on the Apply drilling constraints to generate trajectory option.
8 Digitize a set of points on the 3D Viewer as targets for a horizontal well and press OK.
Note The points seen on the 3D Viewer are projected normal to the view to center in the unit
Houston.
9 Back on the Well Planning panel in the new empty last row, enter New2 as a well name.
New2 will be a new vertical well.
10 Tick Pick New Wellhead Locations toggle and click on the 3D Viewer to define a
location for the well head. Press Apply to create the well.
11 Select Edit Well Path... from the drop-down menu for New2. On the Edit Wellpath panel
press Make Vertical From WellHead. Click Yes on the warning message box stating the
existing well deviation will be lost.
12 Click "continue" on the message box. Then click on OK.
This creates a vertical well path.
Exporting targets and trajectory

1 The next step is to output a set of targets as a table for Drilling Office.
2 Select Edit Well Path... from the drop-down menu for New1.
This re-launches the Edit Wellpath panel for New1.
3 Use the right mouse button drop-down menu on the table to export it into a file. Having
exported a file Cancel the panel.
4 Launch the Export Data panel using the drop-down menu Export | Model item on the
FloGrid Model node for the structured grid struct.
5 Select only Well Trajectories for export, set the file name and location, and Export.
6 Close the Export Data and Well Planning dialogs.
Creating synthetic logs

1 Expand the Wells node, use the Create Synthetic Well Logs... item from the drop-down
menu on well New1.
2 Select Porosity_v0 as the Property Grid and press OK.
3 Repeat the process for well New2.
4 Expand the Well Logs node and check Porosity.
5 Remove the FloGrid Models from display to see the logs better in the 3D Viewer.
6 Use the drop-down menu on wells New1 and New2 to add them to the Well Correlation
Canvas.
7 Use the drop-down menu on the Porosity logs to add the logs to the Well Correlation
Canvas. Inspect the logs in the correlation canvas.

Planning New Wells
Note The Well Correlation Canvas functionality is supported in the Sun Solaris 8 and
Windows 2000 PC 32-bit platforms only.

Planning New Wells
Updating a simulation model and building a derived
model
Introduction
The input data are an ECLIPSE grid and properties. The output is an updated simulation model
or a new one. The workflow steps are:
• Create a structured grid based on an imported ECLIPSE grid. Add LGRs, refine or coarsen
the model.
• Edit the grid nodes, and export the modified simulation model from the Structured
Gridder.
In another scenario, instead of modifying the imported model, build a derived new model. The
workflow steps are create the imported model as before, but use the Create Structural
Framework option. Edit the structural framework and create a new derived model, with the
Unstructured Gridder.
• The files for this tutorial are in the directory flogrid/tutorials/brilld.
• This tutorial requires the gf_petragrid license feature for use of the unstructured
gridder at the end of the tutorial
_update_derive_model.cmd.
1 Start FloGrid in the above directory or if already running use File | New
Importing a model and updating it

2 Set the following parameters

• model name,
• build type to Import model,
• structural basis to Imported file: ECLIPSE grid and
• grid type to Structured,
• select BRILLD.EGRID as the file to import
• and press OK.
3 On the pop-up Grid Use panel select the Refine, coarsen or add LGRs option.
4 From the drop-down menu on the model node use Import | Properties | ECLIPSE... and
import BRILLD.INIT file to import the static properties. View the grid and properties.
5 Launch the Structured Gridder panel by selecting the Edit... item from the drop-down
menu on the model node.

Updating a simulation model and building a derived model
6 Select the Resize folder, and to refine the last two grid columns set I1 to 19 and, I2 to 20,
and the I Factor to 4. Leave J1, J2, K1, K2 and the corresponding J and K factors set to
1. Then press Refine.
7 To coarsen the last 8 columns back to 2 set I1 to 19, and I2 to 26, and I Factor to 4. (Other
parameters should be set to 1 as before.) Then, press Coarsen.
This coarsens 8 columns by a factor of 4 to 2 columns.
8 Select the LGRs folder and give the LGR a name.
9 Click on a cell in the 3D Viewer to set the StartIJ.
10 Select the EndIJ toggle on the LGR folder and click on a cell in the 3D Viewer to set the
end IJ.
11 Use the default values for NXFIN, NYFIN and NZFIN to refine by a factor of 2 in the I and
J directions only.
12 Press Save LGR and then Update 3DGrid.
13 Launch the Export Data dialog from the File | Export... menu on the gridder.
14 Set the following parameters:
• output format to Eclipse.GRDECL keywords,
• select Grid, LGR Grids in the Geometry section and set file location,
15 In the Properties section, select Grid Properties and LGR Properties and select
Property Types: NTG, PermX, PermY, PermZ, and Porosity to export.
16 In the Well Trajectories section toggle off the option to export Well Trajectories.
17 Press Export to export the file.
18 Close the Export Data dialog and the Structured Gridder panel.
Importing a model and deriving a new model

2 Set the following parameters

• model name,
• build type to Import model,
• structural basis to Imported File ECLIPSE grid and
• grid type to Structured,
• select BRILLD.EGRID as the file to import
• and press OK.
3 On the pop-up Please Select Grid Use panel select the Create structural framework
option.
4 From the drop-down menu on the model node use Import | Properties | ECLIPSE... and
import BRILLD.INIT file to import the static properties. View the grid and properties.
5 Remove the grid from the view and add the Fault Framework to the view.

Hint The Fault Framework node is under the corresponding Structural Framework node
in the data tree.
6 Use the drop-down menu and the item Edit on the Fault Framework node to open the
Framework Editor.
This editor can be used to clean up imperfections in a Fault Framework. We will now perform
a dummy edit as an example.
7 Rotate the model and zoom as necessary to access the fault data in the 3D window.
8 Double-click on the major fault on the 3D Viewer to make that particular fault editable.
You should see the top and bottom lines turn into tubes and white vertical control lines
appear.
Click on the top line to make it editable.
You should see yellow cube handles and a 3D cursor appear. Drag the 3D cursor slightly in
away from the minor fault to give the major fault a slope.
9 Cancel the edit by clicking .
Note When editing it is important to move the bottom line in the symmetrically opposite
direction and line up the red center line of the Fault Framework item with its
wireframe representation. This ensures the throw in the grid coincides with the Fault
Framework item.
10 Build a new unstructured (normal) gridding model in the Create Model module using the
edited Structural Framework. In the Please Select Gridding Option dialog select the
Gridding Controls to Fault Framework (New Workflow) option.
11 In the Unstructured Gridder, use the Edit | Layer Controls... option to set the layering
for the new grid.
12 Set Number of layers per unit to 7 and set the Layering method to Use property
model.
13 Press Refine Selected BlockUnit(s).
14 Accept defaults, press OK on the Refinement panel and on the Layering panel.
15 Generate a grid using, Grid | Generate and generate properties using Property |
Generate Real... and accept the defaults.
16 View the resulting grid and properties.

Deriving Fault Transmissibility Multipliers for Simulation
Introduction
The input data are loaded from a RESCUE model. The output is simulator keywords defining
the transmissibility multipliers. The workflow steps are:
• generate a structured grid.
• use the Fault Property Calculator to determine fault displacement, thickness, shale
gouge ratio, fault permeability and transmissibility.
• The files for this tutorial are in the directory -
• This tutorial requires the gf_fg_populate license feature
_fault_trans.cmd.
Importing data and building a structured grid and

upscaling
This part of the tutorial is already documented in a previous tutorial: "Building a simulation
model from a RESCUE model" on page 46.
1 Please run that tutorial or its command file, _sim_from_rescue.cmd, first.
Calculating Fault Properties

1 Launch the Fault Property Calculator from the toolbar.
2 On the Faults folder, use the radio button to set the Style for all faults to Derived.
Now, we will calculate the transmissibility based on fault throw, shale gouge ratio and fault
permeability.
3 Select the Derived Multiplier folder.
On the Thickness folder, choose the default thickness calculation formula based on a
constant brittleness factor. Select Calculate Fault Displacement and Thickness. Accept
the pop-up dialog on calculating IJKFAULTMULTNUM.
4 In the Shale folder, set a constant value of 0.2 as the Shale Content and select Set Shale
Content=Constant.
5 Calculate Shale Gouge Ratio to perform calculation.

6 On the Perm folder, select the permeability function to be
log kf = ( – A1 × SGR ) – ( A2 × log(D) × ( 1 – SGR ) **A3 ) and Calculate Fault Permeability.
7 On the Trans folder, press Calculate Cross Fault Transmissibility to perform

calculation.
Inspect the fault properties in the 3D Viewer using the steps below.
1 Display the 3D Grid and in the Properties node, select the face-based property
Faultid_Face.
2 Launch the thresholding dialog using menu Scene | Grid | Threshold....
3 Select values 1-4 as the values to be displayed.
Apply.
This culls out faces with index 0, leaving only the fault faces on display.
4 On the tree, select properties Displacement_Face, Thickness_Face,
Permeability_Face and TransM_Face to display in sequence and inspect their values.
5 Go to the Fault Export folder on the Fault Property Calculator.
Select all keywords to export.
Export Keywords for Faults.
6 Set file name to faults_grid.grdecl for the GRID keywords and
faults_edit.grdecl for the EDIT keywords on the respective file selection dialogs
that pop up to export the files.

Introduction
The input data are a structural framework, well logs, and markers. The structure may be
imported using a RESCUE model or built within FloGrid using map and fault data. The other
data may be imported as flat files. The output is a geological scale corner point model with
petrophysical properties that have been distributed using a geostatisical method. The workflow
steps are:
• create a geological scale corner point grid using the Structured Gridder,
• determine the layering scheme for the vertical gridding by investigating the property
logs in the Well Correlation Canvas,
• populate a grid with porosity values using a geostatistical algorithm
• use the data analysis tools throughout the process.
• The files for this tutorial are in the directory flogrid/tutorials/cloudspin-by-
maps.
• This tutorial requires the gf_fg_populate license feature
_geostats.cmd.
Importing data from a file

1 Confirm the unit system for the model is field units, using Preferences | Set External
Units... and choose ECLIPSE-FIELD.
2 Use drop-down menu on the Surfaces data tree node and select Import Mesh Maps |
CPS3....
3 From the Horizons directory select the following maps:
• houston.svs and base.svs.
4 On the Mesh Map Import pop-up dialog select Create Surface.
5 On the next pop-up dialog set Number Of Surface(s) Required to 2 and select Number
surfaces from top to bottom.
6 On the next pop-up dialog, set the surface names to houston and base, for Surfaces 1 and
2 respectively.
7 Back on the Mesh Map Import dialog:
• associate surfaces, names and files using the drop-downs in the Surface cells and set
the Property type to Horizon
• select OK.

8 Display the surfaces in the 3D Viewer by checking the tree node.
CPS....
• From the Faults directory, select houston.flt.
• In the Fault Trace Import dialog, using the drop-down selection option on the
Surface column, set all to Splitter. OK.
Note The assignment of traces as splitter is very important at this stage since this aids in the
definition and construction of the Structural Framework.
10 Check the Faults node to display them on the 3D Viewer.

11 From the drop-down menu on the Wells node, select Import Well Deviation Surveys |
CPS...
• From the Deviation directory select wells.dat.
12 Check the Wells node to display them on the 3D Viewer.
13 Use the drop-down menu on the Well Markers node and select Import Well Markers |
Generic....
• From the Horizons directory select marker.dat.
14 Check to ensure that the column headings match the input file and press Review Marker
Assignments.
15 Confirm the surfaces and wells are properly referenced in the Markers assignments to
wells and surfaces dialog and click on OK.
Then OK on the Generic Well Marker Import panel. Check Well Markers node on the
tree to display markers.
16 Use the drop-down menu on the Well Logs node and select Import Well Logs | LAS....
• From the Logs directory select all the log files.
Accept all the defaults by clicking on OK.
Notice that not all the loaded wells have log data.
17 Expand the Well Logs node, use the drop-down menu on Porosity logs and Set Display
Type to Line-1. Similarly, set the Display Type of VCLAY to Line-2.
• Toggle the Surfaces tree nodes off and check the tree nodes to display all logs.
18 On the Wells node, using the drop-down menus select Add All Wells to Well Correlation
Canvas.
19 Similarly, using the Well Markers node and the Well Logs nodes, add all markers and logs
to the Well Correlation Canvas.
20 Use the zone zoom option on the canvas and drag a rectangle over the valid log area
and zoom repeatedly.
21 Remove all items displayed in the 3D Viewer, and close the Well Correlation Canvas.

Building the structural framework
1 Launch Structural Framework Creation module from the toolbar.
2 Create a new Structural Framework using File | Create Structural Framework...
OK to accept the defaults.
3 On the Boundary folder: Use Map Extents to set the boundary extents to those defined
by the map extents.
4 On the Units folder, build the units using all the defaults, by clicking on Build Units.
5 On the Faults folder, create fault block units using all the defaults by clicking on Auto Split
Into Blocks & Block Units.
6 View the Fault Framework and the Wireframe by selecting them from the Structural
Frameworks node.

1 Launch the Create Model module from the toolbar.
2 Give the model a name and set the build type to Build New Grid.
4 Set the grid type to Structured and click on OK.
5 On the pop-up dialog, select Corner Point as the Grid Type and Fault Framework as the
Gridding Controls.
6 On the Boundary folder of the Structured Gridder panel, select Create from Structural
Framework Boundary.
7 On the Gridding Controls folder accept the default controls: Apply.
8 On the Areal Grid folder, enter the Average Dx and Average Dy (250, 250) and Build
an Areal Grid.
The given grid size should result in Total Nx = 54, Total Ny = 60.
9 On the Vertical Grid folder, set Layer Type to Bottom Conforming, and Max Unit
Thickness/Layers Per Unit to 5.
• Click on Set Layering.
• Click on Build.
This layering scheme will result in 33 layers per unit.
10 Continue in the FloGrid pop-up information dialog.
11 Close the Structured Gridder and display the grid.
Populating properties using geostatistics

1 Launch the Property Population module from the toolbar.
2 Create a Population Parameter Set by clicking on Create Parameter Set... in the top
row.

Give a name for the parameters and click on OK.
3 Create a Property Grid by clicking on the Create... button on the next row.
Give the new property a name and select Porosity as the property type. OK.
4 Unit... to select Unit 1.
5 On the Primary Input folder: in the Primary Data section, select Well Logs.
Compute Borehole/Surface Intersections....
6 Inspect the Intersection MD, Marker MD and Difference columns.
OK to accept the default settings.
7 Select property type Porosity.
8 Click on Load.
This loads the selected well log data, stretching and squeezing as defined in the
Borehole/Surface Intersection dialog.
9 Inspect the newly created primary logs and original logs in the Well Correlation Canvas
by using the drop-down menu options on the Wells, Well Markers and Well Logs. The
logs created here are available under the Property Population node on the data tree.
10 Click on the “Histogram” button next to Load to inspect the histogram of the primary
data.
11 On the Lumping folder, click on Lump. Add lumped logs to the Well Correlation Canvas
and inspect. Inspect the histogram of the lumped data.
Note The Primary and Lumped logs can be accessed as Well Logs on the data tree under the
Property Population node, while the Property Population window is open, with the
relevant parameter set loaded. After closing the window, or running a command file to
create these logs, you can restore the logs by re-opening the Property Population
dialog and using Load Parameter Set.
12 Go to Algorithm folder, select Sequential Gaussian Simulation from the drop-down

algorithm option and click on the variogram tool .
13 On the Variogram Specifications panel, click on Compute Experimental.

14 Adjust the variogram in the Variogram Specifications panel and/or by setting values in
the Data Analysis graphical window:
• Model Type: Spherical
• Nugget: 0.0005
• Toggle Areal Major or Minor ON
• Uncheck the option to Constrain to major sill. Note that if this is checked then all sill
values will be set equal.
• Set the Major Range value to 4200 and the Major Sill value to 0.0075.
• Set the Minor Range value to 2100 and the Minor Sill value to 0.0075.
• Set the Vertical Range value to 35 and the Vertical Sill value to 0.005.
• Set Azimuth to 0.
• Give the model a name in the field next to Output Variogram Model.
• Press Save.
• Close the Variogram Specifications panel.
Note Variogram Range, Sill and Nugget can be adjusted graphically in the Data Analysis
dialog by dragging (Range, Sill) point and Nugget points (click and drag on the
points).
15 On the Property Population panel, in the Algorithm folder, set Realization Number to
3 and click on Save Parameter Set & Populate.
16 Inspect the 3 Porosity properties in the 3D Viewer by viewing different K slices.
Notice that most of the upper layers have large amounts of null values. This is because the
layering scheme is Bottom Conforming and many of the cells in the upper layer have zero
cell volumes.
17 Expand the Wells node.
18 Use the drop-down menu on a selected set of wells and Create Synthetic Well Logs from
the populated Porosity grids, which you previously generated.
19 On the Create Synthetic Well Logs pop-up panel, choose the Property as Porosity.
Set the Grid to one of the realizations, or set the Grid to Unspecified, to generate
synthetic logs for all realizations.
20 Expand the Well Logs node on the data tree and find the synthetic logs under the node for
Porosity logs. Add the synthetic logs to the Well Correlation Canvas and compare the
synthetic logs with the original logs, for those cases that have original Porosity logs.

Running a Streamline Simulation with Multiple
Realizations
Introduction
The input data are a set of FloGrid models with corner point grids and multiple properties and
a set of well paths. The multiple models may be due to different layering schemes or fault
realizations and multiple properties may be due to multiple geostatistical realizations or history
matching scenarios. The output is a production profile report from a streamline simulation. The
workflow steps are; launch the Streamline Simulation tool ("Streamline Simulation" on
page 585) and define the initial conditions, well targets and data set file names in the
Simulation Setup panel ("Simulation Setup" on page 587). Launch the Multiple Realization
Manager ("Multiple Realizations" on page 623) from the Simulation Setup panel, run
realizations, view production profiles graphically and export report.
• The files for this tutorial are in the directory tutorials/cloudspin-by-maps.
• This tutorial requires the gf_fg_analysis and gf_fg_populate license features.
_mult_sim.cmd.
1 Start FloGrid in the above directory or if already running use File | New Workspace…
Creating a model and properties

This part of the tutorial is already documented in a previous tutorial: "Generating geostatistical
properties" on page 61).
1 Please run that tutorial or its command file (_geostats.cmd) first.
Creating multiple properties

1 Generate VCLAY values on the new grid using the same procedure as for the Porosity
property in the previous tutorial:
• Choose 3 realizations of Sequential Gaussian Simulations, for simplicity use the
same variogram model.
• Display the properties.
• On the top of the model, you will see large areas of NULL values. They are pinched
out cells, which are not populated for efficiency.

Running a Streamline Simulation with Multiple Realizations
Preparing properties for simulation
1 Expand the Porosity Property Node on the Geostats model and select all porosity
properties using Shift-click.
2 Using the drop-down menu on the selected node, replace NULL values by 0.0.
3 Do the same for the VCLAY property, this time replace the NULL values with 1.0.
4 Launch the Property Calculator from the same drop-down menu.
5 Press Create Property to create a property of name PermX_r1 and type PermX.
6 Using the Calculator buttons, create the equation:
PermX_r1=0.4 * EXP(22* porosity_r1)
Hint Select the correct name of the first porosity realization from the list at the lower right
of the calculator.
7 Press the Multi-Apply button and in the Multi-Apply Calculator panel press OK.
8 Using the Property Calculator, create PermY_r1 of type PermY that equates to PermX_r1.
Use Multi-Apply so that the other PermY_r2 and PermY_r3 are also generated.
9 Create PermZ_r1 of type Perm Z using:
PermZ_r1 = If (VCLAY_r1>0.75) THEN 1 ELSE (250 * EXP(-3*VCLAY_r1))
ENDIF
10 Use Multi-Apply to create 3 realizations of Perm Z.
Setting up simulation data and running multiple

realizations
Before running the simulation it is necessary to identify what kinds of wells are present so that
the simulator can assign group injection and production rates automatically.
1 Select all the wells in the data tree and with the right hand mouse button menu select Set
Type of Selected Wells to | Producer. This is because almost all the wells are producers
and only a few are injectors.
2 Then set the injectors using the right hand mouse button selection as Injector. The wells to
set to injector are: Citrine-1, Jasper-D1, Amethyst-3, Calcite-32, Diamond-14 and Copper-
6.
3 One well should not be simulated: Albite-F1. You can prevent it by using the right hand
mouse menu to set its type to Unknown.
Hint To see which wells are Producers and which are Injectors, right-mouse click on the
Wells node and select Color Wells | by Well Type
Now we can run the simulator.
1 Launch the Simulation Setup module from the toolbar, .

2 On the General folder, toggle on the option Graphics Files (Streamlines & RESTART)
required for 3D views, which is in the section Output Files to generate, and click on
Apply.
3 On the Setup | 2 Phase folder, set Pressure @ OWC to 6000 psia and click on Apply
to accept the other defaults.
4 On the Setup | Rates folder, set Maximum Injection BHP to 6000 psia and click on
Apply to accept the other defaults.
5 On the Run | Multiple folder click on Multiple Realizations to open the Simulation
Realizations panel.
6 Inspect the list of existing models and properties.
7 To decrease the number of realizations click on Guess Groups.
• Or alternatively type r1, r2, r3, in the Group Name column next to the
corresponding permeability realization in the Existing Models and Properties table.
8 Click on Apply to start the simulations.
Viewing results using the Graphical Simulation

Manager
1 Launch the graphical Simulation Manager by pressing the Display Graphics button on
the Multiple Realization Manager or the Simulation Manager button at the bottom of
the Simulation Setup panel.
Hint This can be done while simulations are in progress.
2 View the vector results from the simulation runs.

• The display consists of three linked plots:
• Data value versus time.
• Histogram of the data values at a particular time
• Graph of accumulated mean and standard deviation versus realizations.
• In the table to the top left of the panel, you can see the status of all the simulations. As each
simulation is completed, its results are added to the graphical displays.
• You can manage the simulations using the buttons above and below the table listing the
simulations. You may interrupt a simulation by pressing Stop Queue and delete runs by
selecting a row and using the Delete button.
• You can select the results vector to analyze using the lists at the bottom left corner. You can
select field, group or well data.
• You can move the horizontal and vertical analysis lines to analyze the data at a particular
time, percentile or realization. The selected values are also shown on the middle left slider
display.
• You can print a plot using the buttons at the top of the display area.
Hint Double-click OR drag and drop one of the smaller plots to make it the active large plot.

Note The vector mnemonics used for the simulation output are described in the simulator
reference manuals (see SUMMARY section).
3 View 3D simulation results and streamlines from a FrontSim run. Select the required
simulation in the table and click the Load3D button
Note The button activation depends on whether the current active table column is the first
or second column. The second column (cyan selections) is required for the Load3D
operation, because this column applies only to runs that have completed. The first
column (magenta selections) applies to all simulations.
4 The streamline display appears in the main window. The display can be changed by
clicking on the “Streamline” button, ,on the right of the 3D display, to open the
Streamline Display window. This allows selection of attributes, filtering and thresholding.
Available streamline properties include:
• SWAT - water saturation
• SOIL - oil saturation
• ID_BEG - streamline source (formerly STRTWELL)
• ID_END - streamline sump (formerly ENDWELL)
5 Display the 3D grid and select recurrent properties (for example, pressure, water saturation)
from the property nodes on the data tree. Use the buttons at the top right for viewing
different timesteps and different I, J, K planes.

Generating Structure and Properties from 2D Mapping
Introduction
The input data are markers, contours, scatter sets and fault traces, imported using the File |
Import. The output is a map based FloGrid model with structure and properties, ready for 3D
gridding. The workflow steps are; launch the 2D Mapping Canvas ("2D Mapping Canvas" on
page 647), create structural and property mesh maps on the Create Mesh Map panel using the
raw data. Once the maps are of sufficient quality, use the Structural Framework tool to create
a structural framework and the Create Model tool to create a model using the Map-based
Property Model build type.
• The files for this tutorial are in the directory tutorials/cloudspin-by-maps.
_mapping.cmd.
Importing data from a file

1 Set the unit system for the model to feet by selecting Preferences | Set External Units...
and ECLIPSE-FIELD.
2 Import horizons. Use the drop-down menu on the Surfaces Data tree node and item
Import Mesh Maps | CPS3.
3 From the Horizons directory select the following maps:
• houston.svs and base.svs.
4 On the pop-up dialog with the table of maps to import, press Create Surface.
5 On the next pop-up dialog set number of surfaces to 3 and number them top to bottom.
6 On the next pop-up dialog, set the Surface Names to houston, base, and salt for surfaces
1 to 3.
7 Back on the Mesh Map Import dialog:
• associate surfaces, names and files using the drop-down in the Surface cells
• accept the default Property Type of Horizon
• press OK to load the data.
8 Display the surfaces in the 3D Viewer by checking the tree node.
CPS....
• From the Faults directory, select houston.flt.
• In the Fault Trace Import dialog, using the drop-down selection option on the
Surface column, set all to Splitter. And press OK.

10 Check the Faults node to display on the 3D Viewer.
11 Use menu File | Import | Scatter Sets| Generic to import the data.
• From the Horizons directory, select salt-contour.dat.
12 On the Generic Scatter Set Import panel, set column 3 to property type Unconformity,
click on Scatter Settings and set the Surface to salt on the pop-up Scatter Set Info
panel.
13 Press OK and ignore the message about the coordinate system.
14 Display the houston horizon and the salt scatter data in 3D.
Hint You can change the color settings for individual surfaces, by using the drop-down
menu from the main Surfaces node to edit the Surface Table. You can also change
the appearance of individual maps, by selecting Visualization Settings... from the
map node.
Generating horizon maps

1 Launch the 2D Mapping Canvas from the toolbar, .
2 Expand the Surfaces node and the salt and houston surface nodes on data tree for the 2D
Mapping Canvas.
3 Display the salt scatter data.
4 Open the Create Mesh Map panel using Create | Mesh Map.
• Set the Mesh map name to salt1, Property to Unconformity, Surface to salt.
5 Set the Map Geometry.
• Press Use Existing Map Geometry.
• On the 2D canvas data tree, click on the map name houston under the Surfaces node.
On the Create Mesh Map panel, this sets all the geometry parameters to those of
houston.
6 On the Scatters folder, select salt-contour-1.
7 On the Interpolate folder, view the default parameters.
• Press Apply on the panel, to generate the mesh map.
8 View the map in the 2D and 3D Viewer and close the Create Mesh Map panel.
9 Access the Display Controls for the salt map, using the right mouse button drop-down
menus on the 2D Mapping Canvas and on the 2D canvas data tree. Change the contour
intervals, render mode and labelling.
10 Inspect the options available from the drop-down menus and also inspect the menus on the
top menubar of the 2D Mapping Canvas module.
11 Close the 2D Mapping Canvas module.

Note The mesh map interpolation controls can be modified after the map is created, by using
the drop-down menu and selecting Interpolation. By default, the Convergent gridder
algorithm is selected. Open the Interpolate folder on the panel to test alternative
methods and parameter settings.
Editing mesh maps

The Salt surface defines a non-reservoir area in the west of the field. However it is not necessary
to build a thick unit between the base and salt surfaces in the east part of the field.
1 Expand the Surfaces nodes on the data tree of the 3D window and right-mouse click on a
map node (or right-mouse click on a map displayed in the 3D window). Select Mesh Map
Calculator... from the drop-down menu.
2 Create a thickness map by selecting Create Mesh Map, filling in a name and setting Use
Parameters from salt1.
• Press OK.
3 In the Expression Calculator, use the list at the bottom right to create the following
equation for the new thickness map and apply:
base - salt1
4 Repeat the steps to create a mesh map called salt_final and fill in the equation using the
Expression calculator buttons and apply:
IF (thickness >=50) THEN ‘salt1’
ELSE (base + 50)
ENDIF
5 Assign the salt_final map to the salt surface by dragging and clicking.
6 View the various maps in 3D.
Building a structural framework

1 Open the Structural Framework Builder from the toolbar, .
2 In the Structural Framework Builder, select File | Create Structural Framework and
accept the defaults.
3 On the Boundary folder, set the boundary to Use Map Extents.
4 On the Units folder, ensure the map for the salt surface is salt_final.
5 Build units using all the remaining defaults by pressing Build Units.
6 On the Faults folder, create fault block units using all the defaults by pressing Auto Split
Into Block & Block Units.
7 View the fault framework and the wireframe.

Creating property maps and FloGrid models
• Property maps can be created by following exactly the same procedure as for structure
maps described in the sections above.
• FloGrid Models can be created from mesh maps by following the procedure in "Building a
map based property model" on page 44 and "Building a structured grid" on page 44 in
"Building a simulation model from maps" on page 42.

User Interface
Chapter 5
Introduction
FloGrid has an overall modular structure. The main FloGrid window consists of a data tree (see
"Data tree" on page 333), and the 3D Viewer (see "3D Viewer" on page 107).
The 3D Viewer allows comprehensive 3D visualization of all input and generated data, It also
allows you to access the individual modules such as the 2D Mapping Canvas or the Well
Correlation Canvas.
The size, orientation and position of the objects viewed can be manipulated directly with the
mouse as described under "Preferences Menu" on page 94 later in this chapter.
Many menu options in the 3D Viewer have associated dialog panels. Panels that have an OK
button must be filled in and confirmed before continuing. Panels with an Apply button allow to
repeated changes to update the view. These panels remain open until they are explicitly closed.
Where appropriate it is also possible to make these panels automatically apply changes as soon
as they are made. This is done using a pop-up menu that appears when the right mouse button
is held down over the panel.
This chapter contains information on the following:
• "Windows and Panels" on page 76.
• "Data Tables" on page 83.
• "Window Items" on page 84.
• "Common options" on page 87.
• "Preferences Menu" on page 94.
FloGrid User Guide User Interface 75

Introduction
Windows and Panels
Window management
This section describes facilities to manage the principal windows making up the application.
Window menu
The window menu contains the following standard items:
Cascade
The windows are rearranged so that they are the same size and overlap but are offset downwards
and to the right so the title areas are still visible. The main window is repositioned first at the
top left. Data entry panels are brought to the front.
Message Area
This hides and shows the message area. Hiding the message area is useful if the application is
generating too many distracting messages. The message area is incorporated into the lower
section of the main window (see "Log window" on page 79).
Minimize Children
All top level windows apart from the main window are minimized. It is useful if the screen is
getting full and you temporarily want to use a different application.
Restore Children
Any minimized windows belonging to the application are restored to their previous positions.
Window List
The remaining options correspond to top level windows in the application. Selecting one of
these causes the window to be brought to the front (and restored if it was minimized). This is
useful if the desired window has been hidden behind other windows.
Instance numbers
If the application shows more than one window of a certain type then the different windows are
identified by numbers on their title bars. For example “Editor:1” and “Editor:2”.
Tile 3D Windows...
This menu item brings up a dialog panel where various parameters for tiling the 3D windows
are entered.
76 User Interface FloGrid User Guide

Windows and Panels
Figure 5.1 Tile 3D Windows panel
The slider allows the width of the reserved area to be entered. The reserved area is defined to
the left of the screen, and are not used for tiling the 3D windows. If you do not require a reserved
area, then either set the width of the reserved area to 0, or the uncheck the Use Reserved Area
box.
The screen size shown in Current Situation is for information only, and cannot be altered.
Similarly Number of Viewers is for information only - this is a count of the Master Viewer
and all its slave viewers that are currently active.
Number of Rows can be used to select different tiling methods.
For example, suppose 1 row has been selected for the tiling, an area of 336 pixels reserved, and
a Master Viewer and a single Slave Viewer are present. After tiling the display looks
something like this:

Windows and Panels
Figure 5.2 Example of tiling 2 viewers in one row
As a second example, suppose 2 rows have been selected for the tiling and a second Slave
Viewer added. After tiling the display looks something like this:
Figure 5.3 Example of tiling 3 viewers in two rows

Windows and Panels
Note that the tiling always places the Master Viewer in the top left corner of the non-reserved
area. If no reserved area is selected, the 3D windows fill the display area.
Note Tiling attempts to resize the windows to fit the space as appropriate. It cannot reduce
the windows below their minimum size, so some overlap of the windows will be seen.
You can reduce the minimum size by removing the toolbar icons with menu option
Preferences | Toolbars | Toggle On/Off.
Special windows
Log window
A special window called the “Log Window” to where the application sends informational
messages such as warnings and errors. The application may also echo the contents of the log
window to a file. The Log window can be deactivated using either the Window menu of the
main window or the pop up window of the Log window.
Text editor
The standard text editor window is used in a variety of contexts. It provides generic text editing
capabilities along with a status line and a tool bar. Here is an example the Text Editor display.
Figure 5.4 The Text Editor window
The tool bar buttons correspond to File | Open, File | Save, Edit | Copy, Edit | Cut and Edit
| Paste.
The Edit menu also contains items to find text, replace text and to go to a specific line.

Windows and Panels
Text may be cut, copied and pasted to the clipboard using the menus, toolbar or keyboard in the
normal way.
Panels
Data entry panels are divided into two types, modal (Figure 5.5) and modeless (Figure 5.6).
Modal panels need to be completed and responded to before any other operation within the
application can resume. Only one copy of a particular Modal panel can be displayed at a time.
Modeless panels are generally used where you wish the panel to remain on the screen after
applying a change. More than one copy of a Modeless panel can be displayed at a time.
Modal Panels
These normally have the OK, Cancel and Help buttons. They are used in situations where you
must supply data before an action or calculation can be made. Once visible the panel can be
relocated on the screen, any other activity within the application is not possible.
You are able to work with other applications even when a modal panel is displayed. The bottom
of a panel often displays helpful information describing either the widget you are on, how data
should be entered, or a validation message.
Figure 5.5 Example of a modal panel
Table 5.1 The default push button action
Push button Action

OK Calls validation checks and if successful loads the data displayed into the
internal data structures, then removes the panel.

Windows and Panels
Table 5.1 The default push button action
Push button Action

Apply Calls validation checks and if successful loads the data displayed into the
internal data structures
Cancel Removes the panel. Changes to data, since the last apply, within the panel
are lost.
Help Produces help information.
Modeless panel
These normally have the OK, Apply, Cancel and Help buttons as shown in Figure 5.6. They
are used in situations where you are able to interact with the data in a number of ways for
example, simultaneous graphical or tabular editing. When a modeless panel is displayed you are
allowed to perform other application specific tasks.
To remove a modeless panel select Cancel.
Figure 5.6 Example of a modeless panel

Windows and Panels
Interaction with a panel
This is achieved using either the mouse or following key strokes.
Table 5.2 Panel interaction
Keystroke Effect
Tab Move focus to next window item. If focus is within a table tab will move
focus to the next cell. To move focus out of a table you must use the mouse.
Shift Tab Same as above but in opposite direction.
Down arrow If focus is within a table, moves focus to the cell below see Table 5.3. If in
radio button moves to next button (tab to next field). If in drop-down list box
see Table 5.5.
Up arrow If focus is within a table, moves focus to the cell above see Table 5.3.
If within a drop-down list, will move focus to the item above in the list see
Table 5.5.
Left arrow Move one character to the left within the same cell/edit field. See Table 5.3
Right arrow Move one character to the right within the same cell/edit field. Table 5.3
Enter Same as pressing OK on modal panels, or Apply on Modeless panels.
Otherwise simulates pressing an application specific “update/process data”
button (the exception is when focus is within a drop-down list box). Or
chooses button with focus.
Escape Same as pressing Cancel button. Otherwise simulates pressing an application
specific “Cancel/Remove” panel button.
Space Toggles checkbox, set radio button, or simulates a button press.
F11 Moves onto next table or field / off current table / field
F12 Moves onto previous table or field / off current table or field
Active and passive units

Panels support passive units that is changing the unit does not alter a displayed value. For
example: If we enter a value into the field seen in Figure 5.5, and change the unit via the
dropdown list box, the displayed value of the field is not converted.
Active units would imply a change to the unit field would convert the displayed value. For
example, if we had a field displaying 10 meters and changed the units to feet the displayed value
would update to show 32.8.

Windows and Panels
Data Tables
Tables are supplied with their own vertical and horizontal scroll bars. The order of the table
columns can be temporarily changed by picking up the column header with the mouse and
dropping it at the new location in the table; the cursor changes to a hand during this operation.
Columns can be temporarily resized by dragging a column’s divider, situated within the table
heading.
Table 5.3 Table navigation
Keystroke Effect
tab Moves focus to next cell on same row. If in last cell move to first cell in next
row. If in last cell in table stay there.
shift tab As above but move backwards.
up/down arrows Move to cell above/below
left/right arrows Move character left/right, remain in same cell.
Shift & down arrows Displays drop-down list bow for text choice cells
Ctrl d Delete current row.
Ctrl n * Insert row below current. Move focus to new row.
Ctrl shift n Insert row above current row. Move focus to new row.
Ctrl u† Undo last edit. Message "Undone" or "Nothing to undo" displayed.
F9‡ Copy current cell contents into cell below, move to that cell
*. The “Plus button” in the top right corner of the table is an alternative to Ctrl N for inserting rows
†. Ctrl U will undo the table edits one at a time until the last time data was “consolidated”. Tables are
always consolidated by Apply.
‡. The F9 cell repeat facility is currently only used on the Record merger and the Record Associator panels.
While editing tabular data use the Undo key (see Table 5.3) to undo the changes in reverse
order. You can undo up to the last time the panel loaded the panel data into the internal data
structures (that is when OK or Apply were pressed).
Restrictions
Currently it is not possible to modify the column units specified in the column header. It is also
not possible to tab into or out of a data table.

Data Tables
Window Items
Window items, widgets and fields are generally synonymous, although sometimes a field
implies a composite widget (group of widgets) that represents a more useful construct for
example a named floating point value with associated units (scalar).
This section describes the different window items, and how they are used. For examples of the
window items listed here see Figure 5.7
Table 5.4 Window items
Window item Behavior

Scalar - Floating point edit field Alphabetic characters will be rejected as input (unless part of
preceded by text scientific notation). Input will also be checked against the range
for the field. Extra validation may have enforced.
Scalar - Floating point edit field This field has a drop-down list box attached which shows
preceded by text, with a units drop- alternate units for this item. The user may choose to display/input
down list box. the value in different units.
Slider Scalar A slider representation of a standard scalar.
Integer edit field preceded by text Input is automatically checked for range.
Slider Integer A slider representation of a standard integer.
Checkbox When a checkbox is checked it is deemed to be true.
Radio Buttons A radio button can represent a number of states. A radio button
can only represent one particular state at an one time.
Static text A piece of text or description which can not be edited or gain
focus.
String edit field A string edit field allows data entry. An alphanumeric characters
can be entered.
drop-down list box Clicking on the dropdown button displays a list of options. To
make a selection click on one of the entries in the list. The list
may be editable (that is the values not in the list may be entered).
Table Generally a table will appear with scroll bars, and display several
columns of data. A table can be navigated as specified in Table
5.3. If a particular column or cell is disabled it will appear grayed
out and will not accept focus. A table cell may display a
dropdown button, in this case a selection from a choice can be
made. This is similar in operation to a “drop-down list box”
described above.

Window Items
Figure 5.7 Example window items
Checkboxes Scalar fields with

unit drop-down
Integer field
Radio
buttons
Table
String
field
Push button
Interaction with drop-down list box

Drop-downs are associated with a number of different window items, for example scalar units
and table cells. As well as using the mouse, drop-downs can be navigated using the following
keystrokes once focus is within the drop-down edit field:
Table 5.5 Interaction with a dropdown list box
Keystroke Effect
Shift and down arrow Display list box
Down arrow Move down the list
Up arrow Move up the list

Window Items
Table 5.5 Interaction with a dropdown list box (Continued)
Keystroke Effect
Enter Make selection from list
Space Make selection from list
Letter Move to item in list starting with letter

Window Items
Common options
The menus, dialogs and panels that make up FloGrid’s user interface contain many common
options. This section details these options and their standard actions.
Note Any options that do not obey this standard behavior are described in detail later in the
User Guide.

• "Data tree common options" on page 87.
• "Module common options" on page 88.
Data tree common options

The menus accessed from the data tree nodes contain several common options that produce
standard actions.
Add to view
Adds the selected data item (s) (for example a mesh map) to the 3D Viewer.
Apply/Autoapply
Applies and saves the current settings.
Create
Opens a panel and allows you to create new data (for example a well) or a new file.
Copy
Copies selected existing data.
Close
Closes a dialog or a panel. You may be asked if you wish to apply changes.
Delete
Deletes the selected data or value(s).
Edit
Edits the selected data or value(s).

Common options
Export
Opens a file browser and allows you to export selected data to a specified file.
Hide
This option hides the selected nodes to avoid them cluttering up the view. This is useful if they
are not needed for the current workflow.
Import
Opens a file browser and allows you to import data from a file.
Remove from view

Removes the selected data item (s) (for example a mesh map) from the 3D Viewer.
Reset
Restores the initial default settings (that is not the settings before the last Apply).
Visualization settings
This option can be used to alter the way data is displayed in the 3D Viewer. Note that at least
one of the data type (for example a control line) must be displayed in the 3D Viewer before you
can use this option.
Module common options

The modules, panels and dialogs contain several common options that produce standard actions.
Add New Graph...

This option adds an empty graph placeholder to the main workspace.
Add to view/ +view

Adds the selected data item (s) (for example a mesh map) to the 3D Viewer.
Apply
Applies and saves the current settings.
Autoapply
If AutoApply is on, then changes to the panel take place immediately; if AutoApply is off, then
changes made in the panel do not happen until Apply is chosen. When AutoApply is on, the
Apply button is disabled (grayed out).
The status of AutoApply can be altered from the drop-down menu accessible with the right
mouse button; releasing the button over the AutoApply option changes the state of AutoApply.

Common options
Cancel
Closes the panel or dialog without saving your changes.
Cancel Edit
Cancels the current edit operation, and disables the editor.
Clear
Removes the current changes.
Clear Edit
Removes the current edits.
Close
Closes a dialog or a panel. You may be asked if you wish to apply changes.
Commit Edit
The current edit operation is committed, and the editor is disabled.
Create
Opens a panel and allows you to create new data (for example a well) or a new file.
Copy
Copies selected existing data.
Copy to Clipboard
Main Graph
On a PC, this copies the main workspace image to the clipboard, and you can paste this into any
suitable application (for example Word, PowerPoint, etc.).
Active Graph
On a PC, this copies the active graph to the clipboard.
The active graph is the one usually highlighted by a yellow border, if there is more than one
graph in the main workspace.
Whole Picture
On a PC, this copies the whole of the graphics window to the clipboard. Navigation graphs,
small graphs, legend and caption windows are included in the saved picture
Delete / Delete
Deletes the selected data or value(s).

Common options
Delete All
Deletes all applicable data.
Edit
Opens a data specific editing panel.
Exit
Closes all windows and exits the program.
Export
Opens a file browser and allows you to export selected data to a specified file.
Graph Legend Style...

Opens the Graph Legend Configuration panel, which you can use to control the appearance
of the legend at the top of the active graph, or even whether it is present.
Help
Opens the relevant on-line help page(s).
OK
Closes a dialog or a panel and saves your changes.
Import
Opens a file browser and allows you to import data from a file.
Invert
Inverts the color scheme of the graph window so that, for example, dark foreground graph colors
on a light background become light on a dark background.
Main Title Settings...

This displays the Main Graph Title Settings panel for the main graph or workspace.
Use this option to modify the attributes of the title bar font, size, background and foreground
color.
Modify graph title...

This opens a simple panel in which you can edit the title of the main graph active at the time.

Common options
Plot style settings...
Opens the Data Style panel for the currently active plot. You can modify various style settings
for the appearance of the data (line, marker style and color) through this panel.
Print
Print Window
Print Window prints all the contents of the plot window, that is the main graph plus all
information windows and small graphs.
Print Graph
Print Graph prints just the contents of the main plot window.
Print Pictures
Print Pictures prints the contents of the main plot window and of each of the small graphs, on
separate sheets.
Print Preview...
This opens a preview window showing approximately the final appearance of the printer output
using the current settings. As the printing, it has two modes, one where just the main workspace
is printed, and one where all of the window is printed.
Print Setup...(PC only)

This is the standard Windows setup panel, allowing selection of the default printer and also
paper orientation.
Print Layout...
This opens the Print Layout panel, which is used to specify various aspects of the print output,
especially the date stamp appearance. There are also controls for aspect ratio and scaling of
fonts.
Print Type...
This opens the Printer Drivers panel, which allows selection of the type of printer or driver the
graphics image is sent to. The various output options are specified in the ECL.CFG file.
Read / Read...
Opens a file dialog and allows you to read a list of data.
Refresh
Forces a redraw of the window.

Common options
Remove from view / - view
Removes the selected data item (s) (for example a mesh map) from the 3D Viewer.
Remove Active Graph

This option deletes the selected graph in the main workspace.
This option is only available when there is more than one graph in the workspace.
Reset
Reset Edit
Resets the current feature to its state before editing began.
Rubberband Zoom In
Zoom into the current plot using a dragged box. To use this, select the menu option, place the
cursor (which changes into a magnifying glass symbol) over the grid, click on one corner of
your desired zoomed area, and drag the mouse with the button held down to the opposite corner
of the area.
Selected or Active Graph

Only one graph is active or selected in the main workspace. The selected graph is outlined in
yellow. To select a graph, click on one of the graph plot titles in the legend above the graph grid.
Menu selections are often based on the currently selected graph.
Small Title Settings...

This displays the Small Graph Title Settings panel for the rest of the frames on the window,
small graphs, captions, etc. Use this option to modify the title base attributes, as with the main
settings.
Swap with main

The main workspace is the active workspace, but you can swap a small workspace with the main
workspace by clicking on the right mouse button in the small workspace and selecting this
option.
Trash Bin
The trash bin is used for drag and drop deletions. A graph in the main workspace can be dragged
to the trash bin for deletion unless it is the last graph in the workspace. A small workspace can
be dragged to the trash bin for deletion. This deletes all of the graphs that are in the small
workspace.
Unzoom Completely
Completely unzoom the plot. This displays the complete data range on the main graph.

Common options
Write
Opens a file browser dialog and allows you to write a file containing the selected data.
Zoom in
Zooms in one step into the center of the plot area. The size of the zoom depends on the settings
in the Zoom Preferences panel. Plots may also be zoomed and panned using the zoom box on
the navigation graph.
Zoom Out
Unzoom the complete plot area into a rectangular portion of the plot. The zoom goes out one
step for each time the button is pressed, or the menu item selected, the size of the step being
adjustable through the Zoom Preferences panel.
Zoom Preferences...
Opens the Zoom Preferences panel, from where the default zoom in and out behavior can be
changed.

Common options
Preferences Menu
This menu contains the following options:
• "Set External Units" on page 94.
• "Toolbars" on page 94.
• "Graphics options" on page 94.
• "Rotation style" on page 94.
• "Rotation caching" on page 95.
• "Mouse buttons" on page 95.
• "Outline control..." on page 96.
Set External Units

This panel allows you to change the unit system with which data values are displayed. The unit
system can be switched between Field, Metric and Laboratory. Property units, axes and data
values on other panels are automatically updated to reflect the unit system change.
Toolbars
This option shows or hides the toolbars.
Graphics options
There is a choice between two renderers:
• The hardware renderer uses the workstation platform’s native graphics libraries and
hardware to draw objects on the screen.
• The software renderer implements its own graphics model, drawing objects into an X
Window System image.
In general, the hardware renderer is faster. However, the native graphics facilities on many
workstations do not support all rendering features. If the hardware renderer does not support a
rendering feature such as lights, switch to Software Renderer.
The software render may be slower to draw, but it implements more rendering features than all
but the most expensive color graphics workstations. On some platforms, such as a simple color
X terminal, the software renderer may be the only renderer available.
Rotation style
While you are translating, rotating and/or zooming objects in the 3D Viewer, you can use
different methods to display the object before the final display. The less processing done during
these operations, the faster they are executed.
Unchanged
All objects in the 3D Viewer are displayed and moved during translating, rotating and/or
zooming. No objects are hidden. Cell outlines are especially time-consuming to translate, rotate
and zoom in the Unchanged mode.

Preferences Menu
Wire frame
Rather than displaying and moving all objects in the 3D Viewer, wire frames for each grid are
displayed during translation, rotation and zooming. Wells are displayed as simple lines without
well labels. The Wire frame option is less demanding on the software than the Unchanged
mode.
Bounding box
All objects are hidden from view during translation except for a bounding box around each grid.
This is the least demanding style.
Rotation caching
When enabled, this option stores an image of the model in RAM during translation, rotation and
zooming. This provides much smoother movement of the model during manipulation in the 3D
Viewer.
Mouse buttons
The Mouse Buttons option allows you to select a mode of interaction with the 3D Viewer that
suits the way in which you work. Options are OpenInventor (default), OIFloViz,
GeoFrame and RTView. All are described in detail below. Primarily, these options just set
which mouse buttons control picking, rotation, translation and zooming. The one exception is
OpenInventor, which has two distinct modes for picking and viewing.
Slave viewers use the same mode as the master viewer.
For continuous rotation, keep the mouse moving when releasing the appropriate mouse button.
Note A 2-button mouse is no longer supported.
The following tables give details of which mouse buttons do what in each mode.
Table 5.6 Open Inventor settings
Interaction Mouse / key combination

Select (Picking) LEFT (only in pick mode)
Rotate LEFT (only in view mode)
Translate MIDDLE (only in view mode)
Zoom <CTRL>MIDDLE (only in view
mode)
When in pick mode, the model cannot be moved. Only picking is available. To toggle between
modes, either use the buttons at the top left corner of the viewer (hand and arrow), select with
the P and V keys, or toggle using the <Esc> key.

Preferences Menu
In viewing mode, the left mouse button rotates the model, the middle button translates, and
<Ctrl> key with the middle mouse button zooms.
Table 5.7 OIFloViz Settings
Interaction Mouse / key combination

Select (Picking) LEFT
Rotate LEFT and move mouse
Translate MIDDLE
Zoom <CTRL>MIDDLE
OIFloViz is similar to Open Inventor except that there is only one mode. A pick is registered by
a left mouse button click. If the mouse button is depressed and the mouse is moved, the pick
turns into a rotate. In this way, both modes are available at once using the mouse.
Table 5.8 GeoFrame settings
Mouse / key combination

Rotate MIDDLE
Translate RIGHT
Zoom LEFT and move mouse
A pick is registered by a left mouse button click. If the mouse button is depressed and the mouse
is moved, the pick turns into a zoom.
Table 5.9 RTView settings
Mouse / key combination

Rotate MIDDLE
Translate RIGHT
Zoom <SHIFT>MIDDLE
These settings are the same as the SIS program RTView.

To zoom into an object (make it appear bigger), keep the appropriate button depressed and move
the mouse upwards or to the right.
Outline control...
When cell outlines are displayed, the lines are lifted slightly above the surface towards the eye
point to make them visible. If, however, the model contains very thin cells, some lines may show
through from the bottom surface. This option allows you to control a scale factor for the lift.
Using a smaller value reduces the tendency for lines to show through, although the lines may
then appear dashed when viewed at an oblique angle.

Preferences Menu
Save and Restore
Chapter 6
Workspace save and restore

This chapter contains information on the Workspace save and restore options in FloGrid.
• "The workspace - technical background" on page 98.
• "File menu options" on page 99.
FloGrid User Guide Save and Restore 97

Workspace save and restore
The workspace - technical background
Introduction
The Workspace options on the File menu in the main FloGrid window provide a facility to save
and restore all model data and relationships associated with a session. Saved workspace files
work across all machines of the same type (for example SGI, Sun) and the same program
version.
To upgrade from one release to the next, FloGrid restores and plays a command file embedded
within the Workspace file. Workspace files, which are loaded on a different machine type
(for example saved on SGI, then opened on Sun) attempt to restore the saved workspace using
the original embedded command file.
If the workspace cannot be restored (for example, if the paths to data files in the command file
are not replicated on the new machine, the embedded command file is saved in the working
directory as a file called RECOVERY.CMDLOG.
The New Workspace option clears all existing data from the program.
Warning Please note that FloGrid workspaces are intended only for temporary
backups of your current work. For long term storage of your project, keep
copies of your input data and command files.
Replaying the embedded command file

If FloGrid cannot load a Workspace file it attempts to restore a session by replaying the
command file embedded in the workspace file. It is therefore imperative that the input data (map
data, well data, fault data) is kept available, against this eventuality.
Save and restore memory usage

FloGrid uses a special area of memory called the persistent heap in which to place objects that
are saved. This heap’s low fragmentation algorithm uses more memory than the normal
(transient) memory storage.
In cases where memory is limited you can choose to turn off the save and restore facility and
thus make more memory available. To turn off save and restore you must set an environment
variable (ECL_UTSR_HEAP) to a particular value (PROCESS).
The command to achieve this is located in the @eclrc file (on unix) or $eclrc.bat file (on
PC). Edit the file and locate the following line:
:SET ECL_UTSR_HEAP=PROCESS
When this line is commented out (starts with a colon) then Save & Restore is enabled. To turn
off Save & Restore, delete the leading colon. The change will apply next time you restart
FloGrid.
98 Save and Restore FloGrid User Guide

The workspace - technical background
File menu options
Workspace options
New Workspace
This option deletes all application data from the program and closes all the application windows
except the main window. You are prompted if you wish to save the current workspace before
proceeding.
Save Workspace
This option allows you to save the current state of the application data to a workspace file.
Depending on the amount of data to be saved this process can take anywhere from a few seconds
to a few minutes.
Note FloGrid does not prompt you if you select File | Save Workspace and you have
previously saved a workspace file. The program saves the current workspace state to a
file with the previously saved workspace filename and overwrites the original
workspace file. To save workspace files at key stages of grid model building, use the
menu option File | Save Workspace As.
If you have not previously performed a save during the current FloGrid session, you are
prompted, using the file browser, to select a filename for the workspace. If no file extension is
entered, FloGrid appends.WORKSPACE to the filename.
The workspace file has 3 parts: a version header, a section containing a full record of the
commands used, and a binary image representing the current state of the application data.
Whenever a new workspace is saved or an old workspace is restored, a new version of a
command file called FloGrid.WORKSPACESTART is created. The first line of this file
contains a command to restore the recently saved (or restored) workspace file. All commands
processed thereafter are recorded in this command file, as well as FloGrid.CMDLOG, until
either the program is exited or a new workspace is saved or restored at which point the process
is repeated. This mechanism ensures that the file FloGrid.WORKSPACESTART contains the
minimum necessary commands to restore the program back to its current state.
Note The FloGrid WORKSPACESTART file has the following known limitation. When the
WORKSPACESTART file is run, firstly all windows are closed. This is due to the
RestoreWorkspace command at the beginning of the file. If there are subsequent
3D Viewer commands that occur before the next 3D Viewer open command (that is
the Display3DGrid command or the OpenWindow command) these commands
fail and the run terminates.
A workaround is to add a 3D Viewer open command in the second line of the
WORKSPACESTART file (after the RestoreWorkspace command).
FloGrid User Guide Save and Restore 99

File menu options
Save Workspace As...
This option allows you to save a workspace into a new workspace file. You are prompted, using
the file browser, to select a filename for the workspace. If no file extension is entered, FloGrid
appends.WORKSPACE to the filename.
Restore Workspace
This option allows you to restore a previous FloGrid session by selecting a saved workspace file
using the file browser. Restoring a workspace deletes all existing application data from the
program, close all the application windows except the main window and restore the saved
application data from the workspace file.
If the workspace file was created by the same executable, for example the SGI 2000A version,
the workspace is recovered by using the binary image portion of the workspace file.
If the workspace was written by any other version of the program other than the one being run,
FloGrid attempts to recover the program state by playing the commands recorded in the
workspace file.
If, for any reason, this process fails, FloGrid writes out the commands stored within the
workspace file to the current working directory, as a command file called
RECOVERY.CMDLOG. This allows you to then make any edits necessary to the command file
(RECOVERY.CMDLOG) such as resetting the paths to the current file locations and recover the
session by using the Play Commands option. (See "Play/Save Commands Settings..." on
page 101.)
100 Save and Restore FloGrid User Guide

File menu options
Commands
Chapter 7
Commands
This chapter contains information on the commands system in FloGrid.
File menu command options

Play Commands...
A log of your operations is written to a command file with the suffix .CMDLOG. These files can
be replayed to restore the program to a previous state.
The file from the previous run is renamed to <application_name>_prev_run.CMD and
can be replayed using the Play Commands option. Alternatively, command log files can be
renamed as required with the suffix .CMD, and then replayed in future sessions. If a command
file is renamed <application_name>.startup, or appended to the command line with
the -play option, it is run automatically on startup.
Save Commands as...

This option allows you to save the generated commands into a user selected file.
Note Although renaming the <application name>.cmdlog is sufficient to produce

a command file that restores the application state, a Save Commands As... is
required to ensure that the generated command file benefits from the selections placed
in the Play/Save Commands Settings panel described in the next section.
Play/Save Commands Settings...

It is possible to optimize the way that commands are played, saved or executed by selecting the
appropriate options in the Play/Save Commands Settings panel. A detailed description of
the options available can be found in "Play/Save Commands Settings" on page 102.
FloGrid User Guide Commands 101

Commands
Record 3D Position
This option writes commands containing details of the current 3D position of the object in the
view. The 3D position may be recorded in this way at any time.
Add Pause Commands...

The Add Pause dialog allows you to write a Pause command into the current log file. You
may enter a text message of your choice that is associated with the Pause command.
When the command file is played back the Pause command interrupts execution of the
program and displays a panel containing the text message. Three possibilities are then available:
Continue
Process all commands until the next Pause when another panel appears.
Continue to End
Process all commands until the end of the command file. If any further Pause commands are
found, they do not generate a panel.
Cancel
Immediately stop all processing of the command file.
Play/Save Commands Settings

Commands management can be made more efficient at various stages of the workflow.
During playing of a command file

• deferring windows/graphics refresh until the command files to be played terminates
• avoiding execution of unnecessary commands
Note Unnecessary commands are those commands whose execution does not have any side
effect and therefore their omission does not impair the restoration of the application
state.
• replacing the execution of lengthy, time consuming operations with previously cached
results (when available).
Examples of unnecessary commands

• displaying objects and removing objects from displaying in the 3D Viewer
• Pause commands
• 3D Viewer settings (such as, exaggeration, rotation
During the saving the log of commands (using Save Commands As...)
• exporting only a subset of the available command history
• filtering out unnecessary commands (see "Examples of unnecessary commands" on
page 102) so that they do not appear in the saved file
102 Commands FloGrid User Guide

Commands
• saving (together with the command file) the auxiliary files containing cached results from
lengthy, time consuming operations. These files can be (optionally) used when commands
are replayed (this speeds up their execution)
During ordinary interactive workflow

• caching results to be reused as described above.
Hint Fly-by help is available on all options: hover for a few seconds with the mouse pointer
over the corresponding widget to bring up a brief description of the option.
Play/Save Commands Mode

You can toggle between the original and the new enhanced style of executing commands.
Enhanced
Enables selection of all available options.
Old Style
All options are disabled. All commands contained in a command file are executed and all
commands generated during interactive usage of the application are saved by doing a Save
Commands As....
Defer update
For efficiency reasons it is always better to defer any time consuming User Interface updates
until a whole batch of operations is performed.
Main data tree

When this box is checked the main data tree is updated only after the execution of a command
file terminates (or aborts).
3D Viewer
When this box is checked the 3D Viewer is refreshed only after the execution of a command
file terminates (or aborts).
Note Enabling the 3D Viewer option is particularly convenient when FloGrid is running on
a remote host with the display set on the local machine.
Note The undeferred update of the 3D Viewer may still be needed in order to visualize
partial results when executing a Pause command.
Suppress Commands when playing

There are categories of commands whose execution is not required to restore the model state of
the application. If these commands are present in a command file, they can be ignored. The
supported categories are:

Commands
Open Windows
When enabled, no windows pop up during command file execution
Pause Commands
When enabled, all Pause commands are ignored and the execution continue until the successful
end of the run
Display Objects in 3D Viewer

When enabled certain objects (such as Wells and Grids) are not displayed in the 3D Viewer.
3D Viewer Settings
The 3D settings commands, such as change in perspective, rotation, translation, normalization
of the view, etc., are ignored.
Commands history to save

When saving a command file it is possible to export only a portion of the entire command
history (that is the complete log of generated commands since the application is started).
Until last restore

When enabled, the list of commands since start-up and until the last Restore Workspace...
operation is exported
After last restore

When enabled, commands generated from the last Restore Workspace... operation onwards
are exported
Note When both boxes are checked, the entire command history is exported.
Caution Be aware that if none of the boxes are checked, no command is exported.
Suppress Commands when saving

There are categories of commands that do not need to be replayed to restore the model state of
the application. These commands can be ignored when saving using Save Commands As....
These commands fall into any of the following supported categories:
Open windows
When enabled, no Open Window commands are saved in a command file
Pause Commands
When enabled, no Pause commands are saved in a command file
Display objects in 3D Viewer

When enabled, any commands responsible for displaying/not displaying objects in the 3D
Viewer are not saved in a command file.

Commands
3D Viewer settings
When enabled, any commands that alter the 3D Viewer settings are not exported.
Upscaled property cache

Upscaling is notoriously a complex, time-consuming operation with direct impact on the state
of a model, consequently, its successful execution results in the generation of commands. When
these commands are saved and later replayed, the upscaling operations are re-executed. In order
to optimize this workflow, you can decide to cache the results from an upscaling operation and
use the cache in place of the upscaling calculation when the command is executed.
When this facility is enabled and an upscale operation is successfully performed, a cache file is
created. This cache file is stored in a user-defined temporary directory. This directory can be
changed at any time while the application is running.
Note When the temporary area is changed, the content of the previously designated area is
not copied into the new area. This optimizes the total available disk space because the
cache can be distributed across different partitions/machines.
Enable creation
When this box is checked, upscale cache files are created in the location specified in the field
below.
Note The directory path can be entered using slashes in any style (that is UNIX style forward
slashes/ or Windows style back slashes\) they are amended to the appropriate platform
during validation.
After you specify the location press the TAB key to validate the path.
Use cache when playing

Uses the referenced cache files.
Use cache when saving

Copies the cache files referenced in the saved command from the temporary location to the
cache subdirectory.
Notes
Performing a Save Commands As... with the Use Cache When Saving option enabled,
creates a new subdirectory is created in the location where the command file . All the upscale
cache files relevant to the saved commands are copied in this subdirectory.
If you select Play Commands... with the Use Cache When Playing option enabled, the
content of any file referenced by an upscale command is used instead of the re-executing the
upscale calculations. FloGrid expects the file to be in the cache subdirectory where the
command file was saved.
The naming convention currently adopted for the cache files and their subdirectory is:
• cache files containing the upscale results (initially located in the temporary area) are
named: UPSnnnnn.dat where nnnnn is a 5-digit integer

Commands
• the saved cache subdirectory is named stem_cache where stem is the stem of the saved
command file. For example, if FloGrid_project.cmdlog is the saved command file,
the cache subdirectory is called FloGrid_project_cache.
Whenever a problem is encountered while accessing a cache file while playing commands, you
are given the following options:
• Retry - gives you the chance to relocate misplaced files,
• Upscale - performs a full upscale,
• Abort - terminates the command file execution.
Note When the application is shut down, all temporary locations specified since start up are
cleared.
The Reset To Default button resets all options as they were at application start-up.
Note Once options are set, this configuration persists both when the panel is closed and also
after a New Workspace... operation.

Commands
3D Viewer
Chapter 8
Introduction
The main FloGrid window consists of a data tree, see "Data tree" on page 333, and the 3D
Viewer.
The 3D Viewer allows comprehensive 3D visualization of all input and generated data (maps,
well deviations, logs, markers, RESCUE geological models, simulation models, simulation
input data, simulation results). For further information on the general user interface of the
program see "User Interface" on page 75.
Note Please note that any menu options that require additional explanation beyond the
general summary in "User Interface" on page 75 are described in this chapter.
For information on the following:

• Workspace save and restore, printing, importing and command file options see "File Menu"
on page 109.
• Editing options see, "Edit Menu" on page 112.
• Timesteps, Object Appearance, Normalize, Center of Zoom, Perspective etc., see"View
menu" on page 130.
• Tools such as the Fault Property Calculator, Volumetrics, Property Population are available
through the "Tools menu" on page 140. You can also create of Structural Frameworks and
Models using options on this menu.
• Modifying the display of Structural Frameworks, Model Slice Controls, Upgridded
Models, Grids, Wells etc. see "Scene Menu" on page 144.
The 3D Viewer also contains the following menus:
• Preferences Menu, for further information see "Preferences Menu" on page 94.
FloGrid User Guide 3D Viewer 107

Introduction
• Window Menu, for further information see:
• the node tree, see "Docking/UnDocking Data Tree" on page 337
• and on windows and panels, see "Windows and Panels" on page 76.
108 3D Viewer FloGrid User Guide

Introduction
File Menu
• "Workspace save and restore" on page 97.
• "Commands" on page 101.
• "Saving Images as Print Files" on page 853.
• "Print Setup" on page 109.
• "Import" on page 110.
Print Setup
This menu item opens a dialog panel to enable the setting of options for printing. These options
are used whenever a Print button is pressed in a dialog.
Figure 8.1 Print Setup panel
Printer
Select the required printer from the drop down. Information about the selected printer is
displayed below the drop-down.
Properties
Brings up a printer-specific dialog for adjustment of printing setting. The exact dialog depends
on the hardware and drivers that are installed.
Paper
Select the size of paper that will be loaded into your printer as well as the paper tray from which
the printer will take the paper.

File Menu
Orientation
Specify portrait or landscape orientation for printing
Network
This option opens up a network selection dialog enabling the selection of network printers that
do not appear in the Printer drop-down.
OK
Select this option to close the dialog and save your changes to the print settings.
Cancel
Select this option to close the dialog without saving any change you may have made.
Import
Property Model
This option allows you to import property model data. For further information see "Importing
data" on page 218.
Framework3D Model
This item is present if the config file option F3D_IMPORT has been set TRUE. The option
appears in the GEOMODELS subsection of the FLOGRID section of CONFIG.ECL. By default
it is not present. It allows you to import fault and horizon data exported from aFramework3D
model using Geoframe 4.04.
Mesh Maps
"Importing mesh maps" on page 343.
Contour Maps
"Contour map data options" on page 352.
Scatter Sets
"Scatter Sets" on page 353.
Fault Traces
"Fault trace import" on page 365.
Fault Surfaces
"Fault surfaces" on page 366.

File Menu
Well Deviation Surveys
"Import well deviation surveys" on page 376.
Well Logs
"Well Logs Data" on page 386.
Well Markers
"Well Markers Data" on page 383.
Well Events
"Import Well Events" on page 633.

File Menu
Edit Menu
• Advanced Property Calculator, see "Fault Property Calculator" on page 551.
• "Text Editor" on page 113.
• "Boundaries..." on page 113.
• "Control lines" on page 115.
• "Fault trace" on page 115.
• "Mesh Map" on page 116.
• "Fault framework editor" on page 191.
• "Non-Neighbor Connection Editor" on page 119.
• "Grid" on page 122.
• "Digitize" on page 126.
• "Select/Move" on page 127.
• "Delete" on page 127.
• "Set Major/Minor" on page 128.
• "Select Pick Items" on page 128.
• "Pick Points" on page 128.
• "Close Line" on page 129.
• "Edit On" on page 129.
• "Export" on page 129.
• "Clear Edit" on page 129.
• "Reset Edit" on page 129.
The Edit menu contains options for editing objects such as boundaries (either generic or
attached to particular objects), fault traces, control lines and simulation grids.
The Edit menu is divided into four sections:
• The first section contains options for creating or editing these objects.
• The second section contains the editing modes such as digitizing new points or moving and
deleting existing ones. Once an object is selected for editing, the relevant edit modes are
enabled.
• The third section contains options which influence the action of the edit modes. For
example, when digitizing or moving points the editor can move the points to lie on other
objects included in the editor as Pick Items. These options only become active if the
feature being edited and the current edit mode both support the options.
• The fourth section of the Edit menu contains options that apply to all objects and edit
modes. These options mainly serve to control the edit process.

Edit Menu
Text Editor
Opens a simple text editor. You can open, edit and save ASCII files. There are facilities to cut,
copy and paste text to and from the clipboard, to go to a specified line and to find and replace
specific text strings.
Boundaries...
Boundaries are 2D polygons or rectangles that are used to define 3D volumes. This option
displays an editing panel, which lists the currently defined boundaries and allows boundaries to
be created, copied, edited or deleted.
Boundaries may be added to a variety of groups that are listed in the Boundary list. Different
groups are relevant to different Schlumberger applications and so the list varies from a single
item (all boundaries are added to this ’group’) to many groups representing structural models,
structured grids, and unstructured grids. A boundary used for a specific kind of group, like
structural models, must be in the structural model list. A boundary from one group may be
copied into any other group’s list.
Figure 8.2 Edit Boundaries panel
Boundary list
The list of Boundary groups given by this list varies between applications. Some have just one
entry and so all boundaries are added to this one list. Other applications may have various lists
such as Structural Model Boundaries, Structured Gridder Boundaries, or Unstructured
Grid Boundaries. Each list has its own set of boundaries.
If any boundaries have been created for the chosen list, they are listed in the table below.
Create
This opens the Create Boundary panel to allow you to create a new boundary.
Boundary name
This text box allows you to enter a name for the new boundary.

Edit Menu
Boundary type
These radio buttons allow you to select the boundary type (polygon or rectangle).
Projection plane
These radio buttons allow you to set the orientation of the boundary.
Selecting OK puts the 3D Viewer into Edit mode allowing nodes to be digitized, moved and
deleted.
Copy
This opens the Copy Boundary panel to allow you to select an existing boundary as a template
for the new boundary.
Boundary name
This text box allows you to enter a name for the new boundary.
Boundary type
These radio buttons allow you to choose the boundary type (polygon or rectangle).
Projection plane
These radio buttons allow you to set the orientation of the boundary.
Copy From
This opens the Select Boundary to Copy panel and allows you to select both the boundary list
to copy from and the specific boundary to be copied.
Edit
This opens the Edit Boundary panel and allows you to edit a selected existing boundary. The
options on this panel are the same as for Create, and Copy above. The 3D Viewer changes to
Edit mode allowing nodes to be moved, deleted or added. See the section on Editor Toolbar
Buttons for more information.
Delete
This option allows you to delete an existing boundary by highlighting it then clicking on
Delete.
Import
This option opens a file browser to allow you to import a boundary from a file.
Export
This option opens a file browser to allow you to export a selected boundary to a specified file.
+ View
This option allows you to add a selected boundary to the 3D Viewer for viewing.
- View
This option allows you to remove a selected boundary from the 3D Viewer.

Edit Menu
Copying and editing a boundary are similar to creating one, except that you must first highlight
the boundary to act on before choosing the Copy or Edit buttons. When the editor is enabled,
the existing polygon or rectangle appears, ready for editing.
It is not possible to change the plane in which the boundary is defined when copying or editing
a boundary. It is, however, possible to change the viewing direction and convert polygons into
rectangles and vice-versa.
When digitizing boundaries for structural models or grids, four corners, or major points, are
required. Major points are used to indicate corners and minor points are used for points on the
segments between them.
When it comes to gridding, the boundary is split into segments so that a boundary/boundary
intersection occurs a each corner. This ensures that the corner point is honored exactly. Minor
points along the boundary segments are not honored exactly.
Import and Export read and write boundary information from and to ASCII files.
Close
Select this option to close the dialog.
Control lines
Control lines are used to control the positions of areal grid lines and the slope of coordinate lines
if sloping coordinate line gridding is enabled.
The editor provides access to the following functionality:
Sample Z-Value
When this option is enabled, Z values for newly digitized points on control lines are sampled on
the underlying structural framework.
Swap Up/Down
Swap Up/Down allows to swap the nomination of upthrown and downthrown for the control
line being edited.
Fault trace
Edit traces
Opens the Edit Fault Traces panel.
Create
When a trace is created from this panel, a new fault is also created with which the trace is then
associated. Currently, the name of the fault is automatically generated. If this name is
unacceptable, an alternative fault can be generated and named using the pop-up menu available
from the Faults node of the Fault Tree. Traces can then be associated with this new fault.

Edit Menu
Trace name
Enter a name for the trace in the text box.
Line/Polygon
Specify whether the trace is vertical with a single trace line or sloping with a polygon.
Set map
Opens a panel for the selection of a map to which the fault trace is attached. If a trace is attached
to a map, z values for the trace are calculated by sampling each X Y point vertically onto the
map.
Copy
The options on this panel are similar to those for "Create" on page 115.
Edit
The options on this panel are similar to those for "Create" on page 115.
Set Up/Down
Set the upthrown and downthrown sides of a fault polygon. The first line in the polygon is set
to be the upthrown side, the second line is set to be the downthrown side. Once the upthrown
status is set it can be swapped using the Swap Up/Down option. This option should be used
when a first analysis of the Z values of a fault polygon does not correctly determine which is the
upthrown side.
Reset Up/Down
Resets the upthrown / downthrown status of a fault polygon to unknown and allows FloGrid to
calculate which side of the fault is the upthrown one based on the average height of each side.
Swap Up/Down
Swap Up/Down allows you to swap the nomination of upthrown and downthrown for the fault
polygon being edited.
Reset Z-Values
Deletes existing Z values for the trace. If the trace is currently associated with a map, this option
is unavailable.
Mesh Map
The Mesh Map Editor offers the ability to modify imported mesh maps, useful for fixing
isolated erroneous “spike” values, or for nulling out regions of the map in which data values are
unreliable and need to be interpolated from surrounding values.
The Mesh Map Editor can be launched on any map by selecting the corresponding entry in the
data tree, right-clicking and selecting the Edit option. (If the map is not currently displayed, it
is first added to the 3D Viewer window). An edit session may also be launched on any map in
the display from the Mesh Map Editor Controls panel.

Edit Menu
The Mesh Map Editor allows you to select a node or set of nodes on the edited map and then
to modify the value at these nodes, either to a preset value (which may be picked from elsewhere
on the map) or to a NULL value, indicating that no data is available for these nodes or that the
data there is regarded as unreliable.
The selection of map nodes can be made in one of three ways:
• by selecting individual nodes or combinations of nodes;
• by selecting one or more regions of nodes each bounded by a convex boundary;
• by selecting all nodes within a previously-defined boundary.
Controls...
Opens the Map Editor Controls panel.
Figure 8.3 Map Editor Controls panel
Displayed maps
Selects the map to be edited. Only maps that are currently on the display are listed.

Edit Menu
Start edit
Starts an edit session on the currently selected map. The title of the panel changes to reflect the
name of the map being edited. If an edit session is currently underway, this button will be
unavailable.
Boundaries
Select from the various categories of boundary defined within the system. The list below it
displays currently defined boundaries belonging to the currently selected category, and allows
a particular boundary to be selected.
Select Boundary
Selects all the nodes of the mesh map currently being edited which fall within the currently
selected boundary. If no map is currently being edited, or no boundary is currently selected, this
button will be unavailable.
Invert Selection
Inverts the current selection, with all unselected nodes becoming selected and vice versa. This
function is duplicated by the Invert Selection menu option and by the button on the toolbar. If
no map is currently being edited, this button is unavailable.
Edit Method
Specifies whether you wish to set the value at the selected nodes to NULL, corresponding to an
undefined value, or to a particular value. In this case, the value is entered in the box either
directly, or by using the Pick Values edit mode to copy the value from another location on the
map (see below). Pressing Apply commits the change.
Select Nodes
Places the editor into the Select Nodes edit mode. This mode allows selection of individual
nodes. A single click selects the node and clears any previous selection. Holding down Ctrl
while clicking allows selection of multiple nodes, preventing the previous selection being
cleared. Holding down Shift and Ctrl while clicking toggles the state of the clicked node
from selected to unselected and vice versa.
Select Region
Places the editor into the Select Region edit mode. This mode allows selection of regions of
nodes. Drag the cursor in a loop around the region to be selected. When the mouse button is
released, all nodes within the loop will be selected. Holding down the Ctrl key prevents the
previous selection being cleared when definition of a new region is started, allowing you to
define multiple regions of selected nodes.
Clear Selection
Deselects all the selected nodes.

Edit Menu
Invert Selection
Inverts the current selection, with all unselected nodes becoming selected and vice versa.
Pick Value
Places the editor into the Pick Value edit mode. This mode allows values to be picked from
existing nodes of the map. The picked value appears in the New Value box on the Mesh Map
Editor Control panel, and can subsequently be used to change the values of nodes in the
selection.
Non-Neighbor Connection Editor

The Non-Neighbor Connection Editor allows editing of the transmissibility values associated
with non-neighbor connections (NNCs) between pairs of cells. Such non-neighbor connections
can arise in several ways:
• across displacement faults
• due to pinchout of very small or very thin cells
• due to the presence of LGRs
You can launch the Non-Neighbor Connection Editor on a particular set of NNCs by right-
clicking on the corresponding node in the data tree and selecting the Edit... option. Within the
editor, selection of individual NNCs is made by left-clicking on them (selected NNCs are
displayed in white to distinguish them from unselected NNCs). Hold down Ctrl to add
individual NNCs to the selection. To select multiple NNCs at once, lasso them by dragging a
loop around them; all NNCs for which both ends lie within the loop are added to the selection.
The following menu options are available from within an edit session.
Edit NNC values...

This option opens a panel (Figure 8.4) that allows you to specify the new transmissibility values
for the selected NNCs, either as an absolute transmissibility value or by applying a multiplying
factor to the current value.

Edit Menu
Figure 8.4 The Edit NNC Values panel
Create NNCs...
Opens the Create new NNC panel (Figure 8.5), which allows you to generate a new NNC
between a pair of cells, either in the same domain or different domains. Each cell of the pair can
be picked independently, controlled by the radio buttons at the top of the panel. You can enter
the data for each cell by hand, or by picking on the cell in the display. Once valid data for both
cells have been specified together with the transmissibility, the NNC can be created by pressing
the Create NNC button.
Note Note that it is not possible to create an NNC from a cell to itself, or to an adjoining cell
in the same structured domain; this would create a neighbor connection. Nor is it
possible to create a new NNC between a pair of cells if a NNC already exists between
them.

Edit Menu
Figure 8.5 The Create New NNC panel
Display style...
Changes the display style of selected NNCs. NNCs may be displayed as lines or tubes with
capped ends. Lines are efficient to render but may be hard to see if the NNC is very short in
length. Tubes are slower to render, but since the width can be changed, they remain visible even
with zero length.
Lines
Displays selected NNCs as lines.
Tubes
Displays selected NNCs as tubes.
Display cell outlines

Toggles the display of the cell outlines for displayed NNCs. This option is useful as a means of
locating very short NNCs.
Hide unselected NNCs

Hides from the display all NNCs other than those currently selected. Once hidden in this way,
NNCs remain hidden until the effects are reversed using the Show all NNCs option.
Show all NNCs

Reverses the effects of the previous option.

Edit Menu
Visualization settings...
Controls the display of the NNCs. Currently you can only change the width of NNCs displayed
as tubes using a slider control.
Grid
The Grid Editor offers lateral (horizontal) editing, vertical (along the coordinate line) editing,
fault creation and fault healing functionality for corner point structured grids.
Note Structured grid editing is only applicable to newly-created grids, or to grids imported
from .EGRID format files.
The editor has three modes: Select Nodes, Lateral Edit and Vertical Edit.
The editing workflow starts with the selection of the nodes, optional fault creation or fault
healing, followed by horizontal and/or vertical editing, and then saving the edits performed. You
can switch between these modes either by selecting these options from the pull down menu, or
by clicking on their buttons displayed in the horizontal tool bar or by using the navigational left
and right arrow keys or by pressing the hot keys for these modes.
Working with Named Faults

You can optionally associate names with created grid faults. These names are recorded if you
commit the edit. Named grid faults are accessible in the Fault Property Calculator. You can also
heal named faults that existed in the grid at the start of the edit session. The grid editor has only
one level of Undo, and so you are recommended to create or delete named faults in separate edit
sessions, otherwise you may find yourself unintentionally undoing edits that you wish to keep.
Edit Active Grid

Starts the Grid Editor session on the active grid and takes you to the Select Nodes mode. It
also inserts the editor buttons in the horizontal tool bar of the 3D Viewer window.
Select Nodes
This mode allows the selection of nodes, that is coordinate lines for editing. A pyramid shaped
object is placed at the top and the bottom of each coordinate line for selection. The number of
faces of each pyramid is determined by the number of cells joining that coordinate line. Each
face of the pyramid represents a possible I or J split that may exist along that coordinate line.
Every face of the pyramid is selectable. In the case of non-split coordinate lines, selecting any
face selects all the faces of the pyramid, thereby indicating selection of all the corners of the
coordinate line. For split coordinate lines, only the faces sharing the split with the selected face
is shown as selected. Non-selected faces are shown in green, or in yellow if the coordinate line
is split. Selected faces are shown in magenta. Shift can be used to select multiple nodes and
Ctrl can be used to toggle the selection state of any node.
Note If Shift is used and the node selected is a split node, then only that face is selected
for all the coordinate lines selected by this operation.
The hot key for this mode is “S” or “s”.

Edit Menu
Select All Nodes
Selects all the nodes, that is coordinate lines, which are currently on display, for editing. It
appends the selection made by this operation to any existing selection. In case of split nodes,
only the pyramid faces representing the cells that are on display are selected.
Clear Node Selection

Deselects all the selected nodes, irrespective of whether they are on display or not.
Split Ordered Selection

Introduces a new fault directly into the grid. The path to be taken by the fault through the grid
must first be entered by selecting coordinate lines in order, using Ctrl to select the second and
subsequent points. For split coordinate lines only one of the pyramid faces needs to be selected
(and it does not matter which one). Activating the option introduces a split across the selected
path and automatically selects the pyramid faces on one side of the fault. Activating the option
a second time switches the selection to the other side of the fault. The two sides of the fault can
then be moved apart vertically by switching to the vertical edit mode. If this option is selected
for a single coordinate line it is split in both I and J directions.
Create a Named Fault

If you have picked Split Ordered Selection (above) and a split takes place (as opposed to a
toggle) then you are prompted to enter a fault name. If you enter a name and press OK, the split
that you subsequently create and commit appears in the Fault Property Calculator with that
name and you are able to export related keywords to the Simulator. You must have selected at
least 2 connected nodes using Ctrl as described above. Faults created by splitting an isolated
(single) node are ignored as far as naming and the FPC are concerned. Nodes are connected if
they are neighbors on the same I or J line. Two nodes that are diagonally opposed on the same
cell are NOT connected.
It is possible in one selection to select a set of I J nodes that are not connected. In this case each
connected component containing at least 2 nodes is recorded as a grid fault and given a name
based on the name you have entered but with an integer suffix to distinguish each connected
component.
If, at the name prompt, you press Cancel, then the split proceeds as usual but no information is
recorded for use by the Fault Property Calculator.
You do not necessarily have to perform a vertical edit in conjunction with a split. This case is
considered to be a fault with zero throw.
Heal Ordered Selection

This option is similar to the Split Ordered Selection option but removes any vertical split
across the path of the selected points.
Delete a named fault

Heals all the coordinate lines, which correspond to a named fault. You are presented with a
selection box containing the names of the faults, if any. When you select a name in the box, the
corresponding coordinate lines are selected and highlighted in the display. If you press Heal,
the fault is healed.

Edit Menu
Note The Reset and Cancel buttons presented in the Delete Named Faults dialog resets
all edits for the current edit session, and not just for changes made after the dialog is
launched. To ensure that your deletions are committed to the grid, you must press OK
and commit the edits for the edit session.
Heal Selection
Removes any vertical splits between the selected pyramid faces. It does not require coordinate
lines to be selected in order and it only acts on the selected pyramid faces.
Lateral Edit
This mode allows lateral editing of all the selected nodes in a constant Z plane by pressing down
the left mouse button and dragging the mouse. Upon pressing the left mouse button, rubber band
lines are drawn to display the coordinate lines, with an x (cross) symbol marking the top of the
coordinate line and a + (plus) symbol marking the bottom. The coordinate lines can also be
swivelled around their tops or bottoms by pressing Shift or Ctrl, respectively, during this
edit operation. Esc can be used while dragging to undo the drag. The hot key for this mode is
“H” or “h”.
Lateral Edit Controls...

Opens the Horizontal Edit Control panel. This panel allows typing in explicitly, either in
absolute or relative, top and bottom X and Y distances by which all the selected coordinate lines
are moved. The absolute option is represented by the radio button X and Y and the relative
option is represented by the DX and DY radio button.
Vertical Edit
This mode allows editing of nodes along the coordinate line by pressing down the left mouse
button and dragging it. Upon pressing the left mouse button, rubber band lines are drawn to
display the coordinate lines, with an x (cross) symbol marking the top of the coordinate line and
tick marks showing each node along that coordinate line. Control over the range of the nodes to
move along the coordinate line is provided using the Vertical Edit Control panel. In case of split
nodes, only the split sides selected are edited. Dragging the mouse results in all the K points
within the specified K range moving by an equal DZ along the coordinate line. Proportional
editing can be performed by anchoring either the top or the bottom of the specified K range by
using Ctrl or Shift respectively during the drag operation. This results in all the K points
within the specified K range moving in proportion, maintaining their cell thickness ratio. Esc
can be used while dragging to undo the drag. The hot key for this mode is “V” or “v”.
Vertical Edit Controls...

Sets of the K range that is the range of nodes along the coordinate line that are edited. The
minimum and the maximum range is displayed on the left of the text entry fields. In addition, it
allows explicit entry, in either absolute or relative form, the Z distances by which the selected
nodes are edited, and selection of how the vertical editing is applied. These features are
represented by the Edit Mode radio buttons:

Edit Menu
Set Z and K Range
Specifies the absolute Z distance and the K range of the nodes along the coordinate line, which
are edited. A K range greater than 1 results in collapsing of the cells; therefore, a confirmation
message is displayed in such a case when OK or Apply is pressed.
Set DZ and K Range

Specifies the relative Z distance and the K range of the nodes along the coordinate line, which
are edited.
Set K Range:
Specifies the top and the bottom K values of the nodes along the coordinate line, which are
edited. By default, the K Range is the K extent of the grid being edited.
Edit Type controls how the vertical editing is performed. The options are:
Constant
All the K points on the coordinate line, within the specified K range, are moved by Z or DZ.
Proportional, Top Anchored

The Bottom K Range point is moved by Z or DZ and all the K points on the coordinate line,
within the specified K range, move proportionately, maintaining the cell thickness ratio.
Proportional, Bottom Anchored

The Top K Range point is moved by Z or DZ and all the K points on the coordinate line, within
the specified K range, move proportionately, maintaining the cell thickness ratio.
Note IJK slicing performed on the 3D Viewer does not automatically modify the K range
on this panel.
Save Edit Session

Saves the edits that have been performed to the simulation grid, leaving the node selection as is.
It marks an important milestone during the edit session, as any undo operation during an edit
session reverts the grid back to its last saved state. The simulation grid is updated whenever a
save is performed. The option is duplicated with the button on the horizontal toolbar.
Toggle Pyramids Display

This option is available only from the horizontal tool bar button. It toggles the display state of
the pyramid shaped selectable objects, which allow the selection of the coordinate lines. In case
the pyramids are hidden and the Select Nodes option is chosen, the pyramids are displayed
automatically.
Reset Edit
Reverts the grid to its last saved state. However, it leaves the node selection unchanged to help
in continuing further edits.

Edit Menu
Clear Edit
Same as Reset Edit.
Digitize
When an object is created, Digitize is the default mode. Points forming the object (or nodes) are
created by clicking on the left mouse button.
Digitizing major and minor points

Digitized points can be major or minor. Major points are points with special significance. For
example, when digitizing a structured grid boundary, major points are used to identify the four
corners of the boundary. Similarly, when digitizing a fault polygon, major points identify the
ends of upthrown and downthrown sections.
(Minor points, marked by smaller squares, are digitized by simply clicking the left mouse
button. Major points, marked by bigger squares, are digitized by holding down Shift while
clicking on the left mouse button. It is not possible to commit an edit unless at least two major
points exist in a polygon.
Note When creating a polygon the first point digitized defaults to major, irrespective of the
Shift key position.
Note When the creation of an object does not require any distinction between major and
minor points (that is vertical fault traces, rectangular boundaries and so on) all
digitized points are visualized as major, displayed as bigger squares.
Digitizing new points on an existing line or polygon

In order to digitize one or more new points on an existing line or polygon, you must first select
a line segment to which the new points are to be added. This is done by clicking with the middle
mouse button over the desired line segment. The selected segment is highlighted. Once a
segment is highlighted, further picks with the left mouse button digitize new points. Each time
a point is digitized, the display is updated to indicate the new active segment to which the next
digitized point is added.
Digitizing new points at the end of an existing line or open polygon

To extend an already digitized open line (that is to add a point past either end of an open line)
you must first select the end point to which new points are to be connected. This is done by
clicking with the middle button beyond the end of the line. The selected point is highlighted.
Once a point is highlighted, further picks with the left mouse button digitize new points. Each
time a point is digitized, the display is updated to mark the new point as the active point to which
the next digitized point is connected.
Z values of digitized points

If digitized points are added to an existing line or polygon, Z values for new points are
determined as follows:

Edit Menu
• If the line or polygon was imported with Z values set, Z values for new intermediate points
are interpolated from the Z values of the selected line segment end points. Interpolation is
not done between different sides of a fault polygon. Similarly, Z values for new end points
are set to the Z value of the previous end point.
• If the line or polygon is a fault and has been associated with a map, Z values of new points
are also computed from the map.
Z values of moved points

Z values of any moved points are left unchanged unless the line or polygon is a fault and has
been associated with a map. In this case Z values of moved points are recomputed from the map
when the edit is committed.
Deleting points while digitizing

The Backspace (or Delete key) deletes the currently selected point. This can be done in and
out of Digitize mode.
Note As the most recently digitized point is typically highlighted, successive digitized
points can be deleted (undone) using Backspace or the Delete key.
Select/Move
When an edit session of a pre-existing object starts, this is the default mode.
Nodes and segments of an object can be repositioned by selecting and dragging the nodes or
segments with the mouse holding the left button down.
Note By dragging with the middle mouse button held down and the Ctrl key pressed, the
whole object being edited moves in a rigid translation.
When editing a rectangle, for example, the left mouse button selects either a corner of the
rectangle or a side. By dragging the mouse with the left button held down, the corner or side can
be moved. By dragging with the middle mouse button held down, the whole rectangle can be
moved and repositioned.
Delete
When the editor is in this mode, you can delete points by clicking on them with the left mouse
button. By holding down the Shift key as the mouse is clicked, all points between the last
deleted point and the current point are deleted.
When deleting points from a closed polygon, the choice of which points to delete when Shift
is used is ambiguous. This is because points could be deleted in the clockwise or anti-clockwise
directions. In this case, the section with the fewest points is deleted.
Hint The Delete key (or Backspace) can be used to delete the currently selected point.

Edit Menu
Set Major/Minor
When this mode is active, points can be toggled between major and minor by clicking on them
with the left mouse button. Minor points are marked by smaller squares. Major points are
marked by bigger squares. Major points are points with special significance. It is not possible
to commit an edit unless at least two major points exist in a polygon.
Boundary major and minor points

When digitizing a structured grid or structural framework boundary, major points are used to
identify the four corners of the boundary.
Fault polygon major and minor points

When digitizing a fault polygon, major points identify the ends of upthrown and downthrown
sections. A fault polygon may have as many as four major points. A fault polygon requires two
major points at an end if the end of the fault has been truncated by the model / map boundary or
by another fault (that is it has a non zero throw at the end) or if the fault is a splitting trace made
up from sections of fault polygons from different maps. Minor points cannot be set or digitized
between consecutive major points marking the end of a fault polygon.
Details on how fault traces are colored can be found in "Fault trace coloring and interaction with
3D Viewer" on page 372.
Select Pick Items

When creating or editing objects in Digitize mode, it may be useful to include points from other
objects in the new object. This can be done by selecting objects, known as pick items, which
are added to the display as pick guides when digitizing. Pick guides appear as small dots (pick
points), joined by white lines.
Boundaries, Fault Traces, Control Lines and Contour Lines (that is elements of Contour
Maps) can all be selected as pick items to create pick guides. The selection of objects to use as
pick items is made from the cascade menu Select Pick Items. Several objects (and of different
types) can be selected for an edit session.
Note A pick guide is not fully updated in the current 3D Viewer session. If the object which
formed the pick guide is edited, the pick guide still represents the original points of the
pick item. Deselecting and reselecting the object as pick items updates the XY values
of the pick guide. However, to correctly update the Z values of pick guides that
represent items with edited Z values, you must shut down and restart the 3D Viewer.
Pick Points
This is an option that can be used when in digitize mode. When active (checked entry) any point
digitized in the proximity of a point from a pickable object is snapped to that point.
Digitizing using multiple pick points

To insert consecutive points from a single pickable object, select the first pick point to be added
with the left mouse button and then the last point with Shift held down. This adds all the
selected pick points as minor points to the object being digitized.

Edit Menu
Shift selection of pick points cannot be done across different pickable objects. To add pick
points from multiple pickable objects in a single operation, select or Shift select the desired
pick points from one pickable object, then select the first desired pick point on the next pickable
object, then Shift select the remaining desired pick points on the second pickable object (and
so on).
Setting major points when using pick points

If Ctrl is held down, the selected pick point is added as a major point. If the Ctrl and Shift
keys are held down, the last selected pick point is added as a major point.
Close Line
The option closes an open polygon. Alternatively, a polygon can be closed by double-clicking
when adding a point.
Edit On
Once you have enabled the editor, this option allows you to toggle between editing mode and
normal 3D viewing.
Export
This allows the polygon or rectangle currently being edited to be exported to an ASCII file.
The Export Feature panel allows you to export the file in one of two formats:
Export XY
Opens a file browser that allows the file to be exported with only XY coordinates.
Export XYZ
Opens a file browser that allows the file to be exported with XYZ coordinates.
Clear Edit
This option removes all points from the current feature, including previously digitized and
saved points.
Reset Edit
This option resets the current feature to the state it was in before editing began. The default edit
mode, Digitize, is reselected.

Edit Menu
View menu
• "Timesteps" on page 130.
• "Object Appearance..." on page 132.
• "Normalize" on page 133.
• "Perspective" on page 134.
• "Set View" on page 134.
• "Rubber Band Zoom" on page 135.
• "Object Rotation..." on page 136.
• "Lights..." on page 136.
• "XYZ Exaggerate..." on page 137.
• "Stereo..." on page 137.
• "Refresh View" on page 138.
• "Hardcopy Colors" on page 139.
Timesteps
Note All timesteps for all time varying objects in the view are listed. It is possible therefore
for you to select a timestep for which there is no data for one of these objects. If this
happens, you are warned and the object’s closest previous timestep used.
Individual timesteps can be chosen to display from a list showing sequence number, timestep
and date. Animation of the timesteps is controlled with buttons similar to those on a video
recorder.

View menu
Figure 8.6 The Animate Time panel
The timesteps can also be chosen from the timestep buttons on the 3D Viewer’s toolbar.
The animation buttons let you single step forwards, single step backwards, stop the animation
and play the animation from current step to the end. Additional buttons on the 3D Viewer’s
toolbar let you snap directly to the first (rewind) or last (fast forward) timestep.
On the Animate Time panel it is possible to select timesteps directly from the list, so the panel
does not have the icons for first/last timesteps.
The Circular Animation button sets the Play Mode to loop continuously. When Play is pressed
and the last step is reached we return to the first step where the animation starts again. By default
the loop is played 99 times before stopping automatically. This may be configured through the
use of the MAX_CONTINUOUS entry in the config file.
Figure 8.7 The timestep control buttons
First Timestep Last Timestep
Previous Timestep Next Timestep
Stop Play
Select Options... to define the minimum and maximum timesteps, the timestep interval, and the
delay between timesteps.

View menu
Figure 8.8 The Animate Time Options panel
Object Appearance...
This opens the Object Appearance panel, which contains a list of all objects that have been
requested for display in the 3D Viewer. On this panel you can select which objects to view at
any one time.
Figure 8.9 Object Appearance panel
Objects
This column displays the names of the objects that have been sent to the viewer.
Visibility
The drop-down menus in this column allow you to either Hide or Show the object.
Render mode
The drop-down menus in this column allow you to select how the objects are visualized in the
viewer. The choices are dependent on the type of objects. Most objects have the following
options:
• Lines - This shows the objects as a framework of lines.
• Surfaces - This shows the objects as solid surfaces.
• Cell outlines - This shows the objects with the cell outlines superimposed on the surfaces.
Other objects have more specific options; for example, wells have the following:
• Wells - This shows the wells without well labels.

View menu
• Wells and labels - This shows both the wells and the well labels.
Level of detail
The drop-down menus in this column allow you to specify the level of detail required in the
viewer. If Level of Detail is not applicable for a given object, the entry only shows All.
View/Picking mode
These radio buttons reflect the current 3D Viewer mode of operation. With the Open Inventor
mouse buttons you can be in one of two modes - viewing or picking.
• Selecting the arrow changes the view into pick mode.
• Selecting the hand changes to viewing mode.
Hint The mode can be toggled by pressing the <Esc> key, or by pressing the V key for view
mode or the P key for pick mode.
If you use any other mouse button settings (OIFloViz, RTView or GeoFrame, see the
Preferences | Mouse Buttons menu option), the View/Picking buttons simply reflect the
current viewer mode since view/pick mode is determined by which mouse button is depressed.
Normalize
The View | Normalize... menu item opens a dialog allowing various parameters for
normalization to be entered.
Figure 8.10 Normalization panel
The first button Normalize View is a push-button and performs normalization (using the values
of the other parameters) once only.
AutoNormalize turns normalization on continuously. It can be useful when selecting individual
slices of a model to ensure each slice fills the 3D Viewer. With this option turned on, the
contents of the view are automatically scaled to fill the window. This happens every time the
contents of the view changes. With this option off, no rescaling takes place when the view
contents change.
Note that rotation is always about the center of the screen.

View menu
Seek to point
This option interactively zooms and centers the model on a point you pick. Click on the Seek
to point button (the cursor changes to a Target) and then click on a point of interest on the
model. The view interactively zooms by a factor of 2 so that the picked point is in the center of
the screen. You can repeatedly pick on the model during the zoom operation. Each time you pick
the zoom continues from the new pick point.
Note The S key provides a short cut to the Seek to point button
Note You must pick a point on the model for the seek mechanism to work. Streamlines can
be picked more easily by displaying them as Tubes (Scene | Streamlines |
Streamline Display..., then refer to the Line Display section of the Attributes folder).
Picking on the viewer background will simply turn off the Seek to point behavior.
Perspective
This option toggles the perspective projection on and off.
Set View
This option allows a choice from a list of six predefined viewpoints of the model.
Hint The button colors correspond to the display colors of the axes.
User
This view is defined as the last view of the model defined by the mouse. The default is 30
degrees above the horizontal, 60 degrees to the left and with the model rotated 8 degrees around
the Z axis.
Top
A view from above the model in the negative Z direction.
Bottom
A view from below the model in the positive Z direction.
Front
A view of the model from the front or positive Y direction.
Back
A view of the model from the back or negative Y direction.
Left
A view of the model in the left or positive X direction.

View menu
Right
A view of the model in the right or negative X direction.
Freeze
This option, available only from the toolbar button, allows several changes to be made before
re-rendering (such as a change of IJK slice as well as a change of timestep). Only one button is
visible, and when you click on it, it changes to the other type.
When Freeze is ON the button changes to the red traffic light symbol and the mouse cursor
changes to the "busy" cursor (an hourglass). The mouse cursor change only happens when the
mouse is positioned over the 3D Viewer window. A message VIEW FROZEN appears in the
middle of the 3D Viewer, and most objects are removed from the view. Rotation, scaling and
translation have no effect when the view is frozen. However, it is still possible to bring up new
dialogs, change settings on the dialogs, run commands, add new objects to the view, etc.
Although most objects are removed, the axes and the axis bounding box (if present) are retained.
This is considered much better than having a completely empty view. Furthermore since they
are only lines, they are quick to re-render if an expose event occurs (an expose event can be
caused by another window appearing on top of the 3D window and then being closed or moved).
Note that if the Axes Extents are set to Displayed, the axes continue to resize if IJK slicing
and/or thresholding is changed.
The 3D Viewer remains empty until the toolbar button is pressed again. The message
disappears from the 3D Viewer, and all objects are added back to the view (but only rendered
once). The toolbar button changes to the green traffic light symbol, and the mouse cursor
changes to the idle symbol, a pointer. Rotation, scaling and translation are then possible again.
Rubber Band Zoom

This option allows an area of the 3D Viewer to be "lassoed" with the mouse in order to zoom
in on a particular area.
When Rubber Band Zoom is invoked, the mouse cursor changes to a magnifying glass; you
define the first corner of the zoom box by clicking and holding the mouse down, and then
dragging the mouse to define the other corner. You can perform further rubber band zooms if
you wish. To exit rubber band zoom mode, click on the toolbar button again or re-select the
menu item Rubber Band Zoom.
Each zoom is stored in a list, and you can undo the zooms one at a time – click on the second
toolbar button, or select the Undo Rubber Band Zoom menu item – or completely – click on
the third toolbar button, or select the Reset Rubber Band Zoom menu item. Undo and Reset
are available during a zoom, as well as when zoom mode has finished.
In Rubber Band Zoom mode some functions are disabled, such as Cell picking, Set View,
Normalization, etc. However, rotation and translation are still possible.

View menu
Object Rotation...
This panel allows the object to be rotated about the center of rotation in the 3D Viewer. Use the
buttons in the single step box to rotate the object horizontally or vertically by the rotation angle
you specify. Use the buttons in the animation box to rotate the object through 360 degrees, using
the number of iterations you specify.
Note When one or more slave viewer is active, only the models in one viewer can be set in
continuous rotation (using the mouse) at any one time.
Object rotation is not the same as camera rotation performed with the camera rotation panel.
Firstly, object rotation is always about the center of rotation/zoom and not the center of the
object. Secondly, when an object is rotated it continues to be lit from the front.
Figure 8.11 Object Rotation panel
Lights...
Turns directional lights on or off. Lighting the model with several lights "shining" from different
directions produces highlights and shadows, creating a more realistic view and emphasizing
topological features such as faults. Ambient lighting is always on.
Caution The use of lighting can increase the time taken to display the model. This decrease
in performance can be very significant when working with large models.
The Lighting panel controls the directional lights. The directional lights are arranged relative to
the viewing position at Top Left, Top Right, Bottom Left and Bottom Right. Turning on for
example the Bottom Right light illuminates the bottom and right hand sides of the model, which
may help in viewing points of interest in that area.
The display becomes brighter as more lights are turned on.

View menu
Figure 8.12 Lighting panel
XYZ Exaggerate...
This option allows you to apply a scale factor to the X, Y, and Z (height) directions. Vertical
exaggeration can be quickly applied to the model by clicking on the “Vertical Stretch” and
“Vertical Shrink” buttons in the toolbar.
Stereo...
This option opens a dialog panel to give you extra control over the stereoscopic viewing
parameters.
Figure 8.13 Stereo Panel

View menu
Check the Stereo On box to turn stereo mode on.
Various different stereo modes exist to suit the available hardware. To define the stereo mode,
set the OIV_STEREO_TYPE environment variable to the appropriate mode.
• For Red/Green glasses:
ANAGLYPH_RED_CYAN (default)
ANAGLYPH_GREEN_MAGENTA
ANAGLYPH_BLUE_YELLOW
Each view is rendered using the given colors.
• For systems employing mirror glasses (that show one half of the screen to one eye and the
other half to the other eye):
HALF_SCREEN_OVERUNDER_FILL
HALF_SCREEN_OVERUNDER
HALF_SCREEN_SIDEBYSIDE_FILL
HALF_SCREEN_SIDEBYSIDE
• For systems using light polarizing glasses. RAW uses OpenGL stereo and requires a
graphics card that supports quad buffered stereo.
INTERLACED_HORIZONTAL_BEST
INTERLACED_VERTICAL_BEST
INTERLACED_HORIZONTAL_FAST
INTERLACED_VERTICAL_FAST
RAW
The Balance control determines how much an object appears to protrude in front of the screen,
versus how much it appears behind the screen ("negative parallax"). At 1, the object should be
behind the screen, and at 0 (the default) it should be in front of the screen. The slider provides
a range from 0 to 2.
The Separation Offset controls how strong the stereo effect is. As the value gets higher, the
images appear farther apart. The default value is 1, and a value of 0 produces no stereo effect.
The slider allows a range from 0 to 4.
The stereo effect alternatively displays the left and right images. To view these it is necessary
to use a system such as StereoGraphics’ CrystalEyes. This consists of glasses containing LCD
shutters and an infra-red transmitter to synchronize the opening and closing of the individual
lenses with the image.
Refresh View
If the image does not rotate when it should or the screen goes black, select
View | Refresh View to update the image. This is to overcome problems with some Graphics
cards and their drivers. If problems continue please ensure the latest graphics drivers are
installed on your machine.
Note Note that this command has no effect if VIEW FROZEN has been selected.

View menu
Hardcopy Colors
There is no dialog panel associated with this option.
This menu item switches colors between black and white for various objects, and is primarily
intended for switching between screen colors and hard copy.
If the menu option is selected (that is, hardcopy colors are requested), then the background color
is set to white and the foreground color is set to black. If the option is not selected (or screen
colors are selected) then the background color is set to black and the foreground color is set to
white.
The various objects changed are as follows:-
• The background of the 3D window changes to the background color.
• Cell outlines change to the foreground color.
• Text used for Wells, Axes, Titles, Color Legend and 3D Text changes to the foreground
color.
Flip X axis
This option reverses the X axis. It should only be used for non-ECLIPSE grids with a different
origin.
Flip Y axis
This option reverses the Y axis. It should only be used for non-ECLIPSE grids with a different
origin.

View menu
Tools menu
This menu allows you to access the following options:
• "Structural Framework" on page 175.
• "Create a Model" on page 26.
• "Property population" on page 231.
• "Volumetrics" on page 569.
• Upscaling, see "Structured gridder properties" on page 427.
• "Fault Property Calculator" on page 551.
• "Streamline Simulation" on page 585.
• "Well Planning" on page 631.
• "Property type management" on page 140.
• "Core Analysis" on page 645.
• "Old Workflows" on page 142.
• "Programming Calculator" on page 142
• "Geological Property model" on page 215.
• "LGRs, Resizing, Aquifers and NNCs" on page 407.
• "Generating an unstructured grid" on page 499.
• "Programming Calculator" on page 142.
• "Aliases" on page 143.
• "2D Mapping Canvas" on page 647.
• "2D Well Log Correlation Canvas" on page 679.
• "Aliases" on page 143.
Property type management

This group of menu items provides options for creating new types of properties. Once created,
these property types can be deleted (removed) or assigned to a family. A family is a group of
associated property types. FloGrid has three default families; Maps, Initial and Recurrent. A
property type should be added to the Maps family if it is to be used in any of the geological
modules. If a property type is to be used only on a simulation model it should be added to either
the Initial or Recurrent families.
Create...
Opens the Create Property Type panel.

Tools menu
Create Property type panel
Property Type Name

Specifies the name of the new property type.
Select quantity
Selects what type of quantity a property type is (for example, area, length etc.). The choice of
quantity dictates which units are used with a property type.
Information
Provide additional information about the property type.
Select families
Defines which property families the created property type belongs to. This list contains the
default list of FloGrid families and any families created by you.
Remove...
Opens the Remove property panel.
Remove property panel

A multiple selection list for deleting property types that are not required.
Associate with family...

Opens the Set Property Type Families panel.
Set property type families panel
Family names
Select which property types to add or remove from an active family.
Prop types to add

A multiple selection list of property types. Double-click on the menu entry, or select it then click
on the >> button, to add the selected property type to the family and display it in the list on the
right. Multiple selections may be made.
Prop types in family

A multiple selection list displaying the current set of property types in the family. Select
property types in the list and click on the << button to remove them from the family and re-
display them in the list on the left.
Create family...
Opens the Create Property Type Family panel.
Create property type family panel
Family name
Specifies the name of the new family.

Tools menu
Info
Describe the family.
Select property types

A multiple selection list for selecting the property types to include in the newly created family.
After selection click on Apply to create the new family.
Remove family...
Opens the Remove Property Type Families panel.
Remove property type families panel
Select families
A multiple selection list for selecting which families to remove. Only select families that you
have created yourself.
Old Workflows
This option gives you access to workflow tools that were available in previous versions of
FloGrid.
• Property Calculator
This opens the Simulation Property Editor panel. For further information see
"Simulation Property Editor panel" on page 436.
• "Geological Property model" on page 215.
• "LGRs, Resizing, Aquifers and NNCs" on page 407.
• "Generating an unstructured grid" on page 499.
Programming Calculator
Calculator log
Prints the current contents of the calculator log file (OUTPUT.PRT) to the message area. If any
problems occur when running the calculator, examine this output for help in diagnosing the
problem.
Calculator show
View different Calculator variables within a text window, including a listing of all the
commands within the program.
Calculator reset
Clears all variables from the Calculator. It is recommended when running one Calculator
program after another, to avoid clashes of persistent variables.
For further information see "Calculator Language" on page 701.

Tools menu
Aliases
Certain simulators, including ECLIPSE and FrontSim, restrict all names to less than or equal to
eight characters, and require names to be unique and valid. This menu item allows you to open
panels that control the global aliasing of names to be used when passing data directly to the
simulator.
Wells
Opens the Well Aliases panel.
Enable
Enforces well aliasing. All well names greater than eight characters are truncated to eight
characters. Once any truncation has been done, names are checked to see if they are valid and
unique. If any names are not valid or not unique, simple but unique and valid names are
generated in any exports to the simulator along with comments giving the original non-aliased
names.
To override or set the aliased names, import a file with the desired aliases.
Read...
Aliases specified in this file are merged with the current list.
Faults
Opens the Fault Aliases panel.
Enable
Enforces fault aliasing. All fault names greater than eight characters are truncated to eight
characters. Once any truncation has been done, names are checked to see if they are valid and
unique. If any names are not valid or are not unique, simple but unique and valid names are
generated in any exports to the simulator along with comments giving the original non-aliased
names.
To override or set the aliased names, import a file with the desired aliases.
Read...
Aliases specified in this file are merged with the current list.
Write...
Sets fault aliases. For further information see "Alias" on page 553.

Tools menu
Scene Menu
• "Structural Frameworks..." on page 144.
• Model Slice Controls, see "Display" on page 224.
• "Upgridded models" on page 145.
• "Grid" on page 146.
• "Streamlines" on page 161.
• "Color Legend" on page 167.
• Wells..., see "Well Display Options dialog" on page 379.
• "Show Titles" on page 172.
• "Axes..." on page 172.
Structural Frameworks...
Opens the Structural Frameworks dialog and allows you to modify the appearance of the
displayed structural framework.
Select framework
Selects the structural framework to view. Only structural frameworks that have been added to
the 3D Viewer from the Structural Framework window are available.
Select units / Select blocks

Control the selection of which units and blocks (block units) are affected using the viewing
controls in this dialog. If all units or all blocks are selected from the lists, display choices
supersede previous selections made for individual blocks and units.
Show block unit edges

Displays the wireframe of the selected block unit(s).
Show block unit faces as surfaces

Displays the top and bottom surfaces of the selected block unit(s) as colored surfaces. Surfaces
are colored based on the currently selected block unit color, which can be set from the Select
block unit Color... option on this panel.
Show block unit faces as lines

Displays the top and bottom surfaces of the selected block unit(s) as a gridded set of lines.

Scene Menu
Select block unit color...
Sets the color to be used when the currently selected block unit surfaces are displayed. The
button displays a Color Selector dialog containing a table of colors. To set a new color, select
a color from the table, pick it and press the Apply button. This then updates the legend in the
display dialog.
Upgridded models
The upgridded model is initially displayed by clicking on the View button in the Upgridding
folder of the Structured Gridder window. The panel shows the following options:
IJK slice...
Opens the Upgridding: IJK Slicing panel in the 3D Viewer and offers a selection of different
kinds of views in the I, J, and K directions.
Select slice object

Selects the object to view in the 3D Viewer for slicing. There are three folders that control the
slicing.
IJ slicing
I-Direction/Every Nth/ Apply

Shows the number of layers in the I direction and allows selection of the slices to be displayed.
The arrow buttons move the selections up or down. The Reset button resets the choice to every
layer. Slices can also be selected by entering the name directly in the type-in box; use a comma
to separate multiple entries and a dash to represent a range of selections.
J-Direction/Every Nth/ Apply

Shows the number of layers in the J direction and allows selection of the slices to be displayed.
layer. Slices can also be selected by entering its name directly in the type-in box; use a comma
K-Slicing
K-Direction/Every Nth/ Apply

Shows the number of layers in the K direction and allows selection of the slices to be displayed.
layer. Slices can also be selected by entering its name directly in the type-in box; use a comma
Honor IJ slicing
Honors any IJ slicing selected.
Multiple IJK numbers can be chosen by pressing the Ctrl key while selecting the appropriate
numbers. Several numbers in a row can be chosen by highlighting the first value then holding
the Shift key and highlighting the last value. All numbers in between are highlighted. Use
Every Nth to choose regularly spaced row or layer numbers.

Scene Menu
IJK extents
Sets the extent of the IJK layers to be shown in the 3D Viewer, by adjusting the bar sliders.
Selections in Upgridding: IJK Slice panel are not normally not applied until you click on
Apply.
Display property...
Opens the Upgridding: Display Property panel.
Select view object

Selects the object to view in the 3D Viewer.
Select property
Selects the property to view in the 3D Viewer. Any properties generated by upgridding in the
Structured Gridder window can be chosen and viewed here.
Grid
These options apply only to the grid selected in Set Active Grid.
Property
Opens the Property Display panel, which is used to select the simulation property to color the
cells of the active grid. Initial and Recurrent properties are grouped into two families. Only one
of these is shown in the list at a time. If both are available, selection may be toggled from one
to the other by use of the radio buttons.
Figure 8.14 Property Display panel
If water, oil and gas saturations are available, a Ternary property is created. This property exists
at all timesteps where the three saturations are available. The Ternary property is found in the
list of Recurrent properties and is available for display just like any other property.

Scene Menu
Cell probe
The Cell Probe allows you to investigate a cell’s properties. The cell is selected by clicking on
it in the 3D Viewer with the left mouse button. If the Paint Cell option is on, the cell is painted
white. By default the I, J, K location of the cell, and the grid it belongs to, are reported.
To examine the cell’s property values select a property from the All Properties list and transfer
it to the Probe Properties by either double-clicking on the property or by selecting the property
and clicking on the button. The property name and the corresponding cell value are then
shown in the Cell Properties box. More properties may be selected in the same way.
To remove a property from the Probe Properties either double-click on the property name in
the list or select it and click on the button.
Figure 8.15 Cell Probe panel
The cell values update as you animate the simulation through time. Also note that the probe can
be used in sweep mode by holding the left mouse button down and moving the pointer over the
grid. The effect is to get a continuous trail of property values for the cells that have been swept
by the mouse cursor.
The Cell Geometry option displays the coordinates of the corners and the center of the
currently selected cell. The nodes are listed in an anti-clockwise direction, top face first
followed by the bottom face. For Cartesian cells we list from the top back left node, for radials
from the min. r - min. theta node.
The Always On Top option can be used to prevent the cell probe panel from being hidden by
the 3D Viewer if the two windows are overlapping.
The Print button prints the contents of the text window to your default printer.

Scene Menu
Threshold
The Threshold panel allows you to limit the cells displayed to those that have a property value
inside a given range. You can threshold on multiple properties, so that the cells displayed are
those whose property values are within the intersection of the supplied ranges. As you animate
through time different cells fall into and outside of this property range so giving a visual
indication of fluid flow.
Figure 8.16 Threshold Properties
The list of properties featured in the All Properties list can be toggled between the Initial
and Recurrent property list by the buttons at the top of the panel.
Select properties for thresholding from the All Properties list either by double-clicking on
them, or by single-clicking them and then clicking on the button. Selected properties are
then listed in the Active Properties list. The details of the currently selected property are listed
on the folder below. The layout of the folder differs for integer and real properties - the integer
thresholding folder allows multiple discrete ranges to be selected whereas the real threshold
folder allows just one floating point range to be set per property. Selecting a property from the
Active Properties list displays the details of that property on the folder below. A properties
may be removed from the Active Properties list (and have its threshold range reset) either by
double-clicking on it or by single-clicking on it and clicking on the button.
The following two sections describe the different interfaces presented for integer and real
properties.
Integer properties
The Integer properties interface is as follows:

Scene Menu
Figure 8.17 Integer Threshold panel
Select values
The Select Values list allows multiple selection of integer values to be included in the
threshold range. The selected ranges are listed in the Edit Selection field below. This text list
may be edited directly. To select more than one individual integer from the list, press the Ctrl
key while selecting values with the mouse button; to select a continuous range select the first in
range with the mouse, scroll to the last in range and press the Shift button while selecting it
with the mouse.
Move selection
This increments or decrements all selected values by the given amount. Selected values wrap
from the end of the list to the beginning and vice-versa.
Edit Selection
The complete selection is shown in this field. You can also edit it here.
Disable
When selected, this temporarily disables the selected property’s threshold range.
Reset
Resets the selected properties threshold ranges.
Real properties
Figure 8.18 Real Threshold panel

Scene Menu
Threshold range
Allows selection of a min. and max value that delimit the property values. Only cells with
property values within these limits are displayed.
Move range
Allows the min. and max. range values to be incremented or decremented by the given amount.
The icons are only available when there is sufficient range to move the range values without
ending up outside the property min. and max. values.
Disable
When selected, temporarily disables the selected property’s threshold range.
Reset
Color from Range

The Color from Range button applies the range min. and max. to the property’s colour legend,
so the entire legend spectrum is applied to the selected cells.
IJK Slice
Note This option applies only to the grid selected in Set Active Grid.
The IJK Slicer panel allows you to view restricted slices or blocks of the grid based on the grid’s
IJK structure. Structured grids have a single global domain and domains for each LGR created.
LGRs can be sliced independently of the global cells.
Unstructured grids are made up from several domains around features like wells, faults and
boundaries. Each of these domains has its own IJK structure and can be sliced independently.
There is also a top level, or global domain that does not have an explicit IJK structure. It is an
internally constructed, virtual IJK grid that can be used to view the unstructured grid in a more
conventional manner.
The Global domain is sliced by default. To slice a particular domain, either select it from the
Select Domain drop-down list box or simply pick on the domain in the 3D Viewer with the
left mouse button. This automatically selects the chosen grid for slicing. Existing slicings of
other domains are remembered.

Scene Menu
Figure 8.19 IJK Slicer panel
Note When slicing sub-domains, it may be useful to display only the cells in that particular
sub-domain. Use Grid | Volume of Interest | Domains to limit the domains viewed.
The effects of slicing are cumulative in that the global domain and any or all sub-domains can
be sliced at the same time. The union of the slices is displayed. The buttons Reset Domain and
Reset All Domains can be used to cancel slicing if it is not desired.
The rest of the IJK Slice panel provides three folders for controlling the slicing. The IJ Slicing
folder allows a selection of rows and columns to be displayed. These rows can be combined with
a selection of K layers set in the K Slicing folder. The Honor IJ Slicing check-box on the K
Slice folder toggles the combination between union and intersection with the IJ slices. The IJK
Extents folder allows the range of I,J and K cells displayed to be restricted to a smaller block.
Several numbers in a row can be chosen by highlighting the first value then holding the Shift
key and highlighting the last value. All numbers in between are highlighted. Multiple IJK
numbers can be chosen by pressing the Ctrl key while selecting the appropriate numbers -
using the Ctrl key on an already selected row deselects it. The full combination of selected
rows is shown in the horizontal box in a short-hand form such as “1-7,13,15-20”. This box can
be edited.
Use Every Nth to choose regularly spaced row or layer numbers.

Scene Menu
If AutoApply is on, then changes take place immediately; if AutoApply is off then changes
made in the panel do not happen until you click on Apply. When AutoApply is on, the Apply
button is disabled (grayed out).
mouse button - releasing the button over the AutoApply option changes the state of AutoApply.
The drop-down menu only changes the status of AutoApply on the currently selected folder, so
each folder can be set as required.
Volume of Interest
Note This option applies only to the grid selected in Set Active Grid.
Grid Cells...
This option restricts the volume of the displayed model. Only cells in the new restricted range
will be available to the IJK Slicer. Volume of Interest may only be set on the global grid.
Changes made to the Volume of Interest panel are applied automatically. The AutoApply
option can be toggled off by pressing the right mouse button anywhere in the window and
clicking on AutoApply is On.
Figure 8.20 VOI Grid Cells panel
Domain Selection...
A domain is a named group of cells within the grid. Structured grids have a global domain and
a sub-domain for any available LGRs.

Scene Menu
In unstructured grids, reservoir features such as wells, faults and regions are grouped into
individual domains. Each domain has an independent IJK numbering system. (This collection
of IJK numbers is mapped to a single, regular IJK grid for ECLIPSE internally by the
unstructured gridder.) There is also an unstructured global domain that does not have an explicit
IJK structure. It is a virtual IJK grid created by the unstructured gridder that allows the model
to be displayed and sliced in a more conventional manner.
From the Domain Selection window one or more domains can be chosen for display.
Choices made in Domain Selection are not applied until Apply is chosen. The AutoApply
option can be toggled on by pressing the right mouse button anywhere in the window and
clicking on AutoApply is Off.
Figure 8.21 VOI Domain Selection panel
Boundaries...
Boundaries are used to define areal limits for structural models and grids. They can also be used
to assign properties and aquifers to particular sections of the grid. Boundaries can be created in
Edit | Boundaries. Boundary boxes may be displayed or removed from the viewer in Edit |
Boundaries.
The window Create VOI From Boundary allows you to select cells inside or outside of a
boundary for display.

Scene Menu
Figure 8.22 Create VOI From Boundary panel
The Union and Intersection buttons display the union or intersection respectively of the cells
defined by the boundary with the cells currently selected in the 3D Viewer.
When assigning properties or creating aquifers in the 3D Viewer, this option offers a method to
define which cells are used for assigning the new property or aquifer.
Iso Cell Selection

An Iso Cell Selection is a collection of cells through which a surface of constant value (isovalue)
passes. This may be useful for investigating property distribution and the movement of fronts
through time. Being a collection of cells, they can be used to create new properties through use
of the 3D viewer selected cells option on the Simulation Property Editor panel.
This feature differs from Property Thresholding by the way in which cells are selected.
Property Thresholding selects all cells whose property value is between two values. With Iso
Cell selection, the cell based property values are interpolated on to shared cell faces and nodes.
In this way, a property range is computed for each cell. Cells whose range encompasses the
given isovalue are selected.
Create Iso Cell Selection Panel

This panel is launched from the Iso Cell Selection panel using the Create Iso-Cell Selection
button.
Select Values from Cell Pick

When selected, the panel is updated with the property and value of the next picked cell. Click
Apply to generate the iso cell selection.
IsoCells Selection
The text in the box represents the name that will be given to the next created iso cell selection.
You can change this if you wish.

Scene Menu
Initial or Recurrent
These buttons toggle the property list between the Initial and Recurrent list.
IsoValue
This slider represents the range of values for the selected property. The selected value will be
used as the IsoValue in the generation of the iso cell selected cells.
Apply
Applies all changes made to the panel. Not available if AutoApply is on (see below).
Close
Closes this panel. You are asked whether you wish to Apply any un-applied changes.
Help
Opens the on-line help pages.
Autoapply
The status of AutoApply can be altered using the right mouse button drop-down menu: release
the button over the AutoApply option to change the state of AutoApply.
Other functions on the main IsoCell Selection panel are:
Edit IsoCell Selection

Allows the isovalue of the selected isocell to be edited. The property name and its units (if any)
are also displayed.
Existing IsoCell Selections

Lists any existing isocell selections. If highlighted the selection may be edited, deleted, or
included or removed from the view.
Union / Intersection
These buttons toggle the way in which the isocells interact with other cell selections in the
display. Individual isocell selections always union with each other.
Delete All
Deletes all isocell selections.
Delete
Deletes the selected isocell selection.
Enable
The default. The selected isocell selection is included in the 3D Viewer. The display status of
each selection is appended to its description in the list above.

Scene Menu
Disable
The selected isocell selection is removed from the 3D Viewer. If it is the only cell selection, the
display reverts to displaying all cells. The display status of each selection is appended to its
description in the list above.
Apply
Applies all changes made to the panel. Not available if AutoApply is on.
Close
Closes this panel. You are asked whether you wish to Apply changes not yet applied.
Help
Autoapply
The status of AutoApply using the right mouse button drop-down menu: releasing the button
over the AutoApply option changes the state of AutoApply.
Plane Slicer...
The Plane Slicer allows you to digitize a line or select a predefined line (such as a well
trajectory) to define a cutting poly-plane for cell selection. The plane may be oriented in both
the horizontal and vertical axes for greater flexibility. The plane is extended in each direction to
cover the whole model extents. The plane may be used to select all cells whose center is ’above’
(to one side of) the plane or all cells that ’straddle’ the plane.
Note When the Straddle option is selected, the Show Slice option colors the slice plane by
the cells it cuts. To see this slice, turn off the display of the grid cells with the and
buttons.
Plane Lists
Collections of lines. The Digitized collection is always available and is the collection to which
all digitized lines are added. Other collections may contain lines defined by existing grid objects
such as wells and faults.
Digitize Plane
This button sets the 3D Viewer into digitizing mode. If the edit was successful, the 3D Viewer
returns to normal view and the line’s name appears in the list of planes. The plane is displayed
as a translucent grey poly-plane following your digitized line. An additional plane segment is
appended to each end to ensure that the whole model extents are covered.
Plane Name
The ’type in’ next to the Digitize Plane box defines the default name that is given to the
digitized plane. You may give a plane any name providing it is unique.

Scene Menu
Edit Plane
Puts the 3D Viewer into digitizing mode and allows the currently selected plane’s line to be
edited. See the Editor Toolbar Buttons section for more information on toolbar buttons and
digitizing options.
Delete Plane
Deletes currently selected plane.
Delete All
Deletes all planes in the collection.
Plane List
Lists all planes in the selected collection. Select a plane from the list to make it the ’active’
plane.
Above
All cells whose center lies to one side of the plane are selected. Rotates plane through 180
degrees to select cells on the opposite side.
Straddle
Selects all cells that have at least one node on either side of the plane.
Show Slice
Only available with the Straddle option, the Show Slice option displays the cut cells on the
plane. Turn off cell display and the digitized plane to see the slice plane clearly. Note that the
slice plane is unavailable within unstructured domains.
Angle of Plane Extensions

This rotates the plane extensions about their join with the digitized plane. This allows you to
customize the bisection of the grid as required.
Angle from Vertical

Change the angle used to define the plane in the vertical (in degrees). This angle is measured to
the two plane extensions as they are the only two segments that are guaranteed to be parallel and
can be freely adjusted. See Angle of Plane Extensions above.
Show Plane
Toggles the display of the plane.
Reset Selection
Undo the affects of applying the plane.
Apply
Close
Closes this panel. You are asked whether you wish to Apply any changes not applied.
Help

Scene Menu
AutoApply
any changes made in the panel do not happen until Apply is chosen. When AutoApply is on, the
Distortion
This panel allows the reservoir cells to be artificially ‘thickened’ or the whole reservoir to be
‘flattened’. Cells of very thin reservoirs may be artificially ‘thickened’ to make the cells more
visible, and steeply dipping reservoirs may be flattened to facilitate property distribution
visualization. The Thickening Factor varies the amount of cell thickening applied.
Note Note that artificially ‘thickening’ or ‘flattening’ the reservoir changes the perceived
orientation of features such as Oil-Water and Gas-Oil cuts as well as distorting
perceived gravity effects.
Note Boundaries created in the XZ or YZ plane do not behave as expected with thickening
or flattening as the boundaries themselves are not affected by the distortion.
This distortion also renders the axes values useless and so the axes ticks and bounding box are
disabled when Grid Thickening is in use.
The process of thickening relies on sampling points from a top surface. This sampling can give
incorrect results on and around discontinuities (faults) and may show up as spikes or troughs
around the faults. The sampling can also be quite slow, particularly with unstructured (PEBI)
grids.
The thickening process works by stretching the reservoir in dz using the function
z = zSurf + γ ( z – z Surf )
where γ is the thickening factor. Flattening normalizes the top layer of the reservoir to an xy
datum plane defined at top reservoir depth.
made in the panel do not happen until Apply is chosen. When AutoApply is on, the Apply
Show
Cells
This option allows the display of the cells to be toggled.
Outlines
This option allows the display of the cell outlines to be toggled. Along with the Cells option
this enables four different display modes, from cells with outlines (good for checking
geometry), to no cells or outlines for viewing the wells.

Scene Menu
Note These buttons affect all grids in the display, not just the currently active one. Use the
Object Appearance panel to set the visual characteristics of individual grids.
Faces...
This option opens the Cell Face Selection panel, which gives you control over which faces of
the cells are displayed and which are not displayed. This is useful for visualizing the grid, with
the wells in situ at the same time, gaining insight into the fluid flow through the interior, and
viewing the exterior of the model.
Figure 8.23 The Cell Face Selection panel
• You can turn the I, J and K + and - faces on or off using the check boxes.
• The Clear button removes all selections and the Reset button selects all faces.
Note Note that with all six faces selected, the model behaves as it does by default, by only
displaying the external faces of the model (since the interior faces are no longer
visible).
Caution Note that displaying many faces at once dramatically increases the number of
polygons to be displayed, and will therefore have a marked effect on the speed of
your display. It is unwise to display back-to-back faces at the same time.
Cell face selection can of course be used in conjunction with any other display option, but is
particularly effective when used with IJK slicing.
Inactive cells
By default, inactive cells are only shown if the displayed property has data for active cells. This
option allows you to show the inactive cells even if the displayed property has no data for them.
The inactive cells are colored according to the color set using the Scene | Grid | Inactive Cell
Color... menu option.
Displaying inactive cells can be useful for highlighting shale breaks, pinch-outs or just generally
checking the grid quality.

Scene Menu
Display Shale Breaks
This option turns off the display of cell faces adjacent to inactive layers. Take for example a
shale break that is represented by a layer of impermeable cells. Assuming these cells are
inactive, they are not displayed with the majority of simulation properties. This means that your
model may be full of thin layers that are not displayed; each layer will have cell faces above and
below it, the faces of the active cells above and below. If these layers are very thin, these faces
are unnecessary to the point of being invisible when internal to the model. By turning off Shale
Breaks, you turn off the display of these potentially invisible faces. This reduces the amount of
geometry to be displayed and so can dramatically speed up interaction with the model.
Note Where these inactive layers meet the exterior of the model, you may see ’holes’
through which you can see inside the reservoir.
Inactive cell color...

This option displays a color selector dialog for selecting the color to use when coloring the
inactive cells.
Transparency...
The Grid Transparency panel allows you to change the opacity of the displayed grid so that
you can see the wells in position. A value of 1.0 makes the grid fully transparent, a value of 0.0
fully opaque.
Set Active Grid...

This option allows the selection of an active grid from all of the grids currently on display in the
3D Viewer. This includes grids that are hidden by the Appearance panel. All Grid menu
panels only affect the currently active grid. The option is grayed out until two or more grids are
available for viewing.
Edit aquifers...
Note This option applies only to the grid selected in Set Active Grid and only to
unstructured grids.
Opens the Edit Aquifer panel. Aquifers are defined visually in the 3D Viewer. A single cell is
created in the unstructured grid with connections to all the reservoir cell faces that have been
selected for connection. The aquifer is connected to all cells that are currently displayed in the
3D Viewer and that have cell faces pointing directly out of the screen or within 30 degrees of
a perpendicular out of the screen. A selection of cells for display can be made using the display
direction buttons, the domain selector, the IJK Slicer, the property thresholder, or a user-defined
boundary.
Create
Opens the Create Aquifer panel.
Aquifer name
Give the aquifer an unique name.

Scene Menu
Connection direction
Specifies the direction in which the aquifer connects to the cells. The Get View Direction
button will display the direction of the current view in the 3D Viewer.
Aquifer properties
The Edit Properties button opens the Aquifer Properties panel. This panel is used to define
the new aquifer by supplying data for:
• Cross sectional area
• Length
• Depth
• Porosity
• Permeability
• Transmissibility.
Connected cells
When the Connect Cells button is selected the aquifer is connected to the grid cells depending
on the data supplied.
Aquifers can be attached in only one direction. Multiple aquifers can be created if necessary but
only one aquifer may be attached to any particular cell face.
Copy
A panel appears, similar to the one described for "Create" on page 160.
Edit
A panel appears, similar to the one described for "Create" on page 160.
Streamlines
Show Streamlines
The Show Streamlines option simply toggles on or off the display of streamlines in the 3D
Viewer.
Streamline Display
The Streamline Display dialog allows you to affect the way streamlines are displayed and
filtered. Filtering can apply both to whole streamlines and to individual streamline segments.
For example, filtering by wells filters out whole streamlines that do not originate or terminate
at the selected wells, whereas property thresholding selects just streamline segments whose
property value falls between the selected values.
The dialog is organized into three panels or folders, namely Attributes (line coloring and
display style), Filtering (by wells, by selected cells) and Thresholding (by property range).
The panels are described as follows:

Scene Menu
Attributes
Select color...
Allows selection of a color with which to color the streamlines. Choose the Edit Color... to
bring up the Color Selector dialog. Select the required color from this dialog and then click on
Apply or OK to confirm.
Color by property
This option toggles the coloring of the streamlines between using the fixed color defined by the
Select Color... option and coloring by the property selected in the list below. To ensure the
legend relates to the streamline property, click with the left mouse button over the color legend
and select the streamlines legend from the pop-up menu.
Line Display
The Line Display group allows you to tailor how the streamlines are displayed. By default the
streamlines are displayed As Lines - these are fast to render and give a good overall picture but
are not affected by directional lighting. Switching to display As Tubes enables the rest of the
buttons in the group and displays the streamlines as thin tubes. These take longer to render but
are affected by directional lighting so improve the visual feedback. The Low, Med and High
radio buttons allow setting of tube resolution (4-, 8- or 16-sided tubes) while the Tube Radius
can be altered with the slider bar. Line Display can also be set using the Display | Object
Appearance menu option and is configurable by using the config file.
Filtering
Every Nth
Use this option to reduce the number of displayed streamlines. The default is to display every
streamline; a factor of 2 would display 1 in 2, and so on.
By Selected Wells
Select one or more wells. Streamlines that originate or terminate at least one of the selected
wells will be displayed.
Select All Wells

A quick way to select all wells from the above list.
By Selected Cells
With this option selected, only segments of streamlines that pass through the currently selected
grid cells are displayed. This option is not available when Select Penetrated Cells is selected.
Select Penetrated Cells

This option adds to the display all cells that are penetrated by the currently selected streamline
segments. This option is not available when By Selected Cells is selected.
Thresholding
The Property Thresholding folder allows you to limit the streamline segments displayed to
those that have a property value inside the given range. You can threshold on multiple
properties, so that the displayed segments are those whose property values are within the
intersection of the supplied ranges. As you animate through time different streamline segments
fall into and outside of this property range so giving a visual indication of fluid flow.

Scene Menu
Select properties for thresholding from the Streamline Properties list either by double-
clicking on them or by single-clicking and then clicking on the [>] button. Selected properties
are then listed in the Selected Properties list. The details of the currently selected property are
listed on the folder below. The layout of the folder differs for integer and real properties - the
integer thresholding folder allows multiple discrete ranges to be selected, whereas the real
threshold folder allows just one floating point range to be set per property. Selecting a property
from the Selected Properties list displays its details on the folder below. Properties may be
removed from the Selected Properties list (and have their threshold range reset) either by
double clicking on them or by selecting them and then clicking on the [<] button.
The following two sections describe the different interfaces presented for integer and real
properties.
Integer properties
Figure 8.24 Integer Threshold panel
Select values
The Select Values list allows multiple selection of integer values to be included in the
threshold range. The selected ranges are listed in the Edit Selection field below. This text list
may be edited directly. To select more than one individual integer from the list press the Ctrl
key whilst selecting values with the mouse button; to select a continuous range select the first
in range with the mouse, scroll to the last in range and press the Shift button whilst selecting
it with the mouse.
Move selection
Increments or decrements all selected values by the given amount. Selected values wrap from
the end of the list to the beginning and vice-versa.
Disable
When selected, temporarily disables the selected property’s threshold range.
Reset

Scene Menu
Real properties
Figure 8.25 Real Threshold panel
Threshold range
Allows selection of a min. and max. value that delimit the property values. Only streamline
segments with property values within these limits are displayed.
Move range
Allows the min. and max. range values to be incremented or decremented by the given amount.
The and buttons are only available when there is sufficient range to move the range
values without ending up outside the property min. and max. values.
Disable
When selected, temporarily disables the threshold range of the selected property.
Reset
Resets the threshold ranges of the selected properties.
Disable all
Disables all active threshold ranges.
Enable all
Enables all active threshold ranges.
Reset all
Resets all active threshold ranges.
Apply
Close
Closes this panel. You are asked whether you wish to Apply any changes not applied.
Help

Scene Menu
AutoApply
any changes made in the panel do not happen until Apply is chosen. When AutoApply is on, the
Wells...
The Wells panel allows you to modify the appearance of the wells. The height of the well stem
and the well width may be changed using the Height and Width sliders. The Display radio
buttons toggle what is displayed between no wells, just the wells, and the wells and their labels.
Figure 8.26 Wells panel
The Connections check-box toggles the display of the simulation to well connections. These
are represented by spheres at the center of cells that the well is connected to and may be green
(open) or red (closed) depending on their current status.
The Status check-box toggles the display of the well’s status. This is represented by an icon that
appears at the top of the well stem. The icon is either:
1 An upwards pointing cone indicating the well is currently producing. The cone is colored
purple.
2 A downwards pointing cone indicating the well is currently being used as an injector. The
cone is colored according to the colors associated with the saturations by the
TERNARY_LEGEND ORDER config file entry (by default red for gas, green for oil, blue
for water).
3 Two opposing cones indicate that the well is closed.
4 A flat gray disk indicates the well is shut in.
The Show All Wells check-box toggles between displaying all wells and just those connected
to the currently displayed cells.

Scene Menu
The Level Of Detail radio buttons allow selection of low, medium or high resolution. The
higher the level of detail the better the wells look, but they take longer to draw.
Note Changes in the Display state of the wells is reflected on the Object Appearance
panel.
The Connections check-box toggles the display of the simulation to well connections. These
are represented by spheres at the centers of cells that the well is connected to and may be green
(open) or red (closed) depending on their current status.
Note Unless the ECLIPSE keyword COMPORD was set to INPUT, ECLIPSE computes the
order in which the connections occur along the well bore. This can generate strange
results culminating in the ’zigzagging’ of the wells in the 3D Viewer. If this occurs,
either rerun the simulation with COMPORD set to INPUT or set the CONFIG option
USE_ECLIPSE_CONNECTION_ORDERING (SECTION 3D, SUBSECT WELLS)
to FALSE.
The Status check-box toggles the display of the well’s status. This is represented by an icon that
appears at the top of the well stem. The icon is either:
1 An upwards pointing cone indicating the well is currently producing. The cone is colored
purple.
2 A downwards pointing cone indicating the well is currently being used as an injector. The
cone is colored according to the colors associated with the saturations by the
TERNARY_LEGEND ORDER config file entry (by default red for gas, green for oil, blue
for water).
3 Two opposing cones indicate that the well is closed.
4 A flat gray disk indicates the well is shut in.
Font Options
The Font Options panel is a generic panel used to tailor font representations for a variety of
text styles within the 3D Viewer.
Font family
Provides a list of fonts to choose from. The fonts available depend on the host computer’s
operating system.
Height
Allows the font height to be set in pixels. The sizes available depend on the host computer’s
operating system.
Statistics...
This panel displays information about objects currently in the 3D Viewer in three folders:
Property
This panel displays statistical information about the currently displayed property. Information
from the sum of the selected cells to the mean, median and standard deviation are given. All data
is for the current report step only.

Scene Menu
Note Use the Scene | Grid | Property... menu option to change the displayed property.
Note Information can be shown for the whole model or just for the currently selected cells
by selecting either the Whole Model or the Current Selection buttons.
Grid
This panel displays information about the numbers of selected grid cells.
Note With Whole Model selected the information displayed includes the global, LGR and
LGR host cells.
Note With Current Selection selected you can identify inactive cells by turning on the
Scene | Grid | Show | Inactive Cells option. The information then lists the number
of cells displayed (inactive + active) and the number of these that are active.
Wells
This panel displays information about the grid wells at the current date. Information includes
how many wells are connected to the selected cells and of those open, which are producers and
which are injectors. The number of connections attached to the selected cells is also given.
Note Information can be shown for the whole model or just for the currently selected cells
by selecting either the Whole Model or the Current Selection buttons.
Color Legend
These options control the appearance of the color legend. Switching between the normal
horizontal legend and the ternary legend is automatic as you choose the property to display.
Figure 8.27 Ternary legend

Scene Menu
Figure 8.28 Color legend
Figure 8.29 Color legend
Show Color Legend

This option toggles the color legend on or off.
Color legend editor

The Color Legend Editor allows you to edit the position and size of the legend and also allows
access to the individual property Color Map Editors. These allow editing of the colors, markers
and method used to generate the colormap and are discussed in detail later.
Horizontal position
Slider moves the color legend horizontally across the screen.
Vertical position
Slider moves the color legend vertically across the screen.
Ternary legend size

Sets the size of the Ternary property legend.
Length of legend
Sets the length of the color legend on the screen.
The Color Map to Edit list allows selection of the property type color map to be edited. Simply
select the property type and then click on Edit...
Hint Click on the Color Legend in the 3D Viewer to display a pop up menu. Select Edit
to open the color map editor for the current Property Type.
You are presented with one of the following editors depending on the property data type:
Integer color map editor

The Integer Color Map Editor provides controls for editing the color map used for a particular
integer property type. The color map may be continuous or discrete.

Scene Menu
Min./Max. override
Normally the minimum and maximum values for a property type are calculated over all objects
in the view and all timesteps containing the property. The Min./Max. Override allows these
values to be changed. If the minimum and/or maximum values are set inside the calculated
values, then a light gray color is used for the underflows (values less than the min. value set)
and a dark gray color is used for the overflows (values greater than the max. value set).
Overriding the Min./Max. can be useful for:
1 Highlighting small property variations by reducing the coloration range to values close to
the variations.
2 Pinpointing data anomalies by reducing coloration range to show cells that are outside the
normal range for that property.
3 Identifying groups of cells that fall inside or outside a particular range of interest, especially
whilst animating that property through time.
Continuous color map

A continuous color map is shown as a smooth gradation of colors from the start to the end. The
Edit Color... button may be used to change the color for the start and/or end and the
interpolation method used to change the way the gradation occurs.
RGB interpolation works by providing a smooth gradation between the red, green and blue
components of the Start and End colors. RGB interpolation is useful for providing color maps
from light to dark blue, etc.
HSV interpolation works by providing a smooth gradation between the hue, saturation and
value components of the Start and End colors. HSV interpolation is useful for providing
rainbow color maps.
Discrete color maps

Discrete color maps may have from 2 to 16 steps. If the integer property has 16 or fewer values,
the default color map is discrete.
The number of steps may be altered. If there are fewer steps than values, then several values are
shown together. For example, if JINDEX ranges from 1 to 20 and four steps are chosen, then
the steps contain values of 1-5, 6-10, 11-15, and 16-20 respectively.
The color and bounds of each step may be altered. Clicking on the Edit Color... button displays
a new panel with 48 predefined colors that may be used to change the color of the selected step.
The bounds may be altered using the Lower Bound and Upper Bound sliders, and these
automatically change the adjacent step.
Real color map editor

The Color Map Editor provides controls for editing the color map used for a particular floating
point property type. The color map may be continuous, discrete, logarithmic or reverse
logarithmic.
Min./Max. override
Normally the minimum and maximum values for a property type are calculated over all objects
in the view and all timesteps containing the property. The Min./Max. Override allows these
values to be changed. If the minimum and/or maximum values are set inside the calculated
values, then a light gray color are used for the underflows (values less than the minimum value
set) and a dark gray color are used for the overflows (values greater than the maximum value
set). Overriding the Min./Max. can be useful for:

Scene Menu
1 Highlighting small property variations by reducing the coloration range to values close to
the variations.
2 Pinpointing data anomalies by reducing coloration range to show cells that are outside the
normal range for that property.
3 Identifying groups of cells that fall inside or outside a particular range of interest, especially
whilst animating that property through time.
Continuous color map

A continuous color map is shown as a smooth graduation of colors from the start to the end. The
Edit Color... button may be used to change the color for the Start and/or End, and the
interpolation method used to change the way the gradation occurs.
RGB interpolation works by providing a smooth graduation between the red, green and blue
components of the start and end colors. RGB interpolation is useful for providing color maps
from light to dark blue, etc.
HSV interpolation works by providing a smooth graduation between the hue, saturation and
value components of the start and end colors. HSV interpolation is useful for providing rainbow
color maps.
Discrete color maps

Discrete color maps may have from 2 to 16 steps. The number of steps, the color and the bounds
of each step may be altered.
Clicking on the Edit Color... button opens a new panel with 48 predefined colors that may be
used to change the color of the selected step. The bounds may be altered using the Lower
Bound and Upper Bound sliders, and these automatically change the adjacent step.
Logarithmic and reverse log. color maps

Selecting either of these options creates discrete color maps, but instead of the steps being
evenly spaced, they default to a logarithmic spacing. Logarithmic color maps have smaller steps
at the start of the range, and reverse log. color maps have smaller steps at the end of the range.
The number of steps, the color and bounds of each step may be altered as for discrete color
maps.
Ternary Color Map Editor

The Ternary Color Map Editor presents you with the three components and their Min./Max.
values that will be used to generate the Ternary diagram. Ternary cell colors are derived by
applying amounts of red, green and blue coloration according to the percentage of each
component within the cell. The first component (usually GasSat) is red, the second (usually
OilSat) is green and the third (usually WaterSat) is blue.
By default we override the components’ real Min./Max. and assume that each component
occupies 0 - 100% of a cell somewhere in the model, in other words that their Min./Max.
saturations are 0 to 1. This gives a balanced view of the percentage of each component within
each cell, but can make it hard to see small amounts of gas in the reservoir, for example. The
Override switch can therefore be used to toggle between this and using the Min./Max. of the
individual components.

Scene Menu
Object Appearance...
This opens the Object Appearance panel, which contains a list of all objects that have been
requested for display in the 3D Viewer. On this panel you can select which objects to view at
any one time.
Figure 8.30 Object Appearance panel
Objects
This column displays the names of the objects that have been sent to the viewer.
Visibility
The drop-down menus in this column allow you to either Hide or Show the object.
Render mode
The drop-down menus in this column allow you to select how the objects are visualized in the
viewer. The choices are dependent on the type of objects. Most objects have the following
options:
• Lines - This shows the objects as a framework of lines.
• Surfaces - This shows the objects as solid surfaces.
• Cell outlines - This shows the objects with the cell outlines superimposed on the surfaces.
Other objects have more specific options; for example, wells have the following:
• Wells - This shows the wells without well labels.
• Wells and labels - This shows both the wells and the well labels.
Level of detail
The drop-down menus in this column allow you to specify the level of detail required in the
viewer. If Level of Detail is not applicable for a given object, the entry only shows All.
Titles
Edit Titles...
This option allows you to add titles and annotation to your 3D view. You may add as many titles
as you like by using the Add Title button. The currently selected title may also be removed by
pressing the Delete Title button.
The position, size and alignment to start position for the currently selected title may be changed
using the Position, Font and Align Text to Position sections respectively. The position sliders
have extents of -1.0 to 1.0. Fonts and text heights may be machine-dependent.
The Contents section displays the selected title text. The contents of the title may be edited by
simply typing into the text box. The drop-down list holds keywords that are translated on screen
to the value they represent. Select an entry point in the title text with the cursor and select a
keyword to add it to the title.

Scene Menu
Titles may be defined in advance within the config file. See the section on configuring the
application for more details.
Figure 8.31 Edit Titles panel
made in the panel do not happen until Apply is chosen. When AutoApply is on, the Apply
mouse button: release the button over the AutoApply option to change the state of AutoApply.
Show Titles
This option toggles the titles on or off.
Axes...
The Axes panel allows you to configure the display of model axes in the 3D Viewer.
The axes displayed around the model have their origin at (0,0,0) in the grid model coordinate
system. You can set the axes to be colored and labeled using the Axes check boxes. The axes
colors directly correspond to the colors on the View buttons found on the left side of the 3D
Viewer, namely red for the X axis, green for the Y axis and blue for the Z axis. A full model
Bounding Box can be turned on, which fully contains the grid and axes.

Scene Menu
Figure 8.32 Axes panel
The axes locations can be set to the Bounding Box limits with the Position radio buttons.
The Axes Extents option allows you to toggle the axes extents between that of the current
selection and the whole model. The axes update as the selected extent changes, for example by
changing threshold or slicer values.
Tick Marks and Tick Labels can be placed on the axes using the check boxes and tick mark
folders. Primary and Secondary Tick Marks can be set at defined intervals on each axis from
drop-down menus. Tick Labels can be displayed at regular intervals along the Primary Tick
Marks, set with the Label Every: drop-down menu. Control of the number of decimal places,
and whether to use scientific notation, is also possible.
The Primary Tick Marks can be extended to cover the full extent of the model by selecting the
Grid Lines box. Grid line color can be changed with the Grid Color... option. The Grid and
Primary Tick Marks positions are affected by the Position radio buttons.
The Axes settings can be applied to the model view automatically. This can be set by clicking
anywhere within the Axes panel area with the right mouse button, then releasing the mouse
button on the AutoApply is Off button. The Apply button is then grayed out and any edits in the
Axes panel are immediately reflected in the model view. To turn the automatic axes settings off,
click in the Axes panel area with the right mouse button then release the mouse button on the
AutoApply is On button.
Axes AutoApply options can be preset on or off at program startup by editing the 3D section
of the CONFIG.ECL configuration file, or its local copies ECL.CFG or ECL.CFA.

Scene Menu
Scene Menu
Chapter 9
Introduction
The Structural Framework module is where selected data from the Reservoir Data Tree is
used to construct consistent 3D Structural Frameworks from which simulation models can be
built.
The construction of a suitable Structural Framework is typically a computationally-intensive
task, often requiring large areas of surfaces to be computed or re-computed. Surfaces may need
to be computed for a variety of reasons. These include interpolating or extrapolating across
areas of nulls, computing new surfaces from thickness data, re-computing surfaces in the
vicinity of faults to correct bad surfaces, and providing extrapolated surfaces for sampling on
the wrong side of the fault.
The construction of a Structural Framework involves three main steps: boundary definition,
unit creation and fault block splitting.
This chapter contains information on the following options:
• "Creating and deleting models" on page 177.
• "Displaying model status" on page 178.
• "Creating and displaying boundaries" on page 179.
• "Specifying units" on page 182.
• "Fault block splitting" on page 186.
• "Creating FloGrid data models" on page 190.
Boundary definition
Excludes irrelevant portions of the maps, such as non hydrocarbon bearing zones or any large
areas of nulls around the perimeter, from the subsequent model clean-up and construction steps.
FloGrid User Guide Structural Framework 175

Introduction
Unit creation
Builds reservoir units from selected surfaces and surface representations stored in the main
window tree. Automated mesh map operations compute units based on the given order of
surfaces, and erode any overlapping surfaces according to their respective surface types.
Fault block splitting (FBS)

This step completes the model construction process and provides a robust solution to the
difficult problem of how to sample surfaces (and subsequent properties) in the vicinity of faults
and layer boundaries. Fault block splitting first divides the model into a set of fault blocks,
extrapolating faults where necessary. Next, each block is further subdivided into block units,
using the units created earlier. Finally, block unit surfaces are repaired and extrapolated to
produce a model that supports rigorous sampling, including sampling values from the wrong
side of the fault.
Note The Structural Framework Module is also used to store and visualize structural fault
surface and block unit data from imported property models. Imported property models
can be accessed from the structural framework drop-down list box. Once the model is
selected, property model fault surfaces and block units may be added and removed
from the 3D Viewer by selecting and deselecting nodes in the appropriate tree and
selecting and deselecting the 3D Viewer button. See "Fault block splitting" on
page 186 for more details on visualizing faults and block units.
The Structural Framework module can be opened using Tools | Structural Framework
Creation...
This window has a menu bar from which various menu options can be selected and allows you
to create and edit structural frameworks. There is also a model and mode selection area, and
a display area that contains three folders. See "Creating and displaying boundaries" on
page 179, "Specifying units" on page 182 and "Fault block splitting" on page 186.
176 Structural Framework FloGrid User Guide

Introduction
Creating and deleting models
File
• "Create model" on page 177.
• "Delete model" on page 177.
Create model
Opens the Create Structural Framework panel, which allows you to enter a name for the new
Structural Framework. Alternatively you can accept the default name.
Three check boxes offer you the chance to:
• Auto build boundary using map extents.
• Auto build units using available maps.
• Auto build block units using available faults.
If these are not selected, the boundary, units and blocks must be manually defined.
Note When a structural framework is created it effectively takes a copy of the data in the
main window tree. If changes are subsequently made to faults or surfaces in the main
window tree these changes are not reflected in structural models already created.
Delete model
Opens the Delete Structural Framework panel, which contains a list of structural models. To
delete a model, select one of the models in the list and confirm with OK. Cancel aborts the
operation and no models are deleted.
Note A model can only be deleted if no property models exist in the system.

Displaying model status
This section contains information on the following:
• "Current model" on page 178.
• "Model status" on page 178.
• "Display model" on page 178.
Current model
The Current Model drop-down list shows the currently selected structural framework. Details
displayed in the "Creating and displaying boundaries" on page 179, "Specifying units" on
page 182 and "Fault block splitting" on page 186 apply only to the current model. When a
different Structural Framework is chosen, the details shown in the folders change to reflect the
new choice of current model.
Note This drop-down is also used to select structural models back-populated from imported
property models.
Model status
The Model Status buttons show how far you have progressed in building the current model.
• When boundary has been selected or created for this model, the first button lights up.
• When the units have been created the second button lights up.
• When the block units have been created the third button lights up.
• When the model is complete and ready for a property model to be built, the “GO” button
is highlighted.
Display model
Visualizes the completed structural framework in the 3D Viewer. (See "3D Viewer" on
page 107 for details on how to manipulate the 3D view of the structural framework.)
Note The Display Model button is grayed out until the Structural Framework is complete.

Displaying model status
Creating and displaying boundaries
Introduction
The Boundary folder allows you to create or select a 2D areal boundary representing the area
of interest of the model. This area of interest applies throughout the vertical extent of the model
to create a volume of interest.
See "Fault block splitting" on page 209 for a fuller discussion of this subject.
• "Select boundary" on page 179
• "Use map extents" on page 179
• "Create, copy..." on page 179
• 3D edit... puts you into editing mode in the 3D Viewer allowing the existing boundary to
be modified if necessary. See "Boundaries..." on page 113 for more detail on the Boundary
Editor.
• "Table edit..." on page 180.
Select boundary
Shows the currently selected boundary for the current model. You can choose from a list of all
the structural framework boundaries that exist in the model.
Use map extents

Instructs the Structural Framework to take the extents of all system maps as its boundary. If
the maps all have the same extents, a boundary is created using this common extent. If any of
the maps have differing extents, the right side of the window opens showing a table detailing all
the different maps and their extents. You can select one or more of the maps in the table (the
second column of the table) and may then choose to:
• Use the selected map to build the boundary
• Use a combination of the selected maps to build the boundary
• Use the union of all maps to build the boundary
• Cancel (and decide, for example, to edit the boundary manually).
Create, copy...
Opens the Create or edit model boundary panel to allow you to start up a boundary
creation/editing session in the 3D Viewer.

Boundary list
Lists all the existing boundaries.
Create
Opens the Create Boundary panel.
Boundary name
Enter a name for the new boundary.
Boundary type
Selects the boundary type (polygon or rectangle).
Projection Plane
Sets the orientation of the boundary.
Copy
Opens the Copy Boundary panel.
Boundary name
Boundary type
Projection plane
Copy from...
Opens the Select Boundary to Copy panel to allow you to select another (Global, structural
framework or Structured Gridder) category of boundary from a drop-down list.
Hint See "Boundaries..." on page 113 for more detail on the Boundary Editor.
Table edit...
Once created, you may decide to edit the boundary by modifying the X-Y coordinates of its
points. The Table Edit button displays the Boundary Edit table on the right side of the
Boundary folder; this allows the edit.
Boundary edit
Displays the name of the boundary being edited.

Reference coordinate system
Selects the reference coordinate system used to view and edit the X-Y coordinates of points in
a boundary.
Point
Number indicating the position of the point in the boundary.
X and Y coordinates
The second and third columns of the table show the X and Y coordinates of the boundary points.
Values can be edited.
Corner
The last column shows whether the point is a Corner node of the boundary. This is a major point
in the terminology of the Boundary Editor. A single click of the mouse on any cell in this last
column switches the point between major (Y) and minor (N) (corner or non-corner).
The Apply button makes the required changes to the boundary. The Close button reverts to the
normal folder view.

Specifying units
Introduction
The Units folder allows you to specify and construct structural framework units.
Units are constructed from a sequence of selected maps as described in "Construction of Units
and Horizons from Mesh Maps" on page 757. Operations are based on whether maps are
classified as horizons, unconformities or thickness maps.
The initial sequence and classification of surfaces is taken from the current state of the surfaces
in the main window tree. The Options table provides the opportunity to inspect and modify this
sequence and classification of surfaces and then inspect the resulting units.
• "Unit/horizon table" on page 182.
• "OPTIONS table" on page 183.
Unit/horizon table
The Unit table on the left side of the Units folder describes the results of the unit building
process, that is the units and the maps that define them.
Unit
This column gives the name of the unit and may be edited.
Top/3D
The Top column gives the name of the resulting tops horizon for each unit. The accompanying
3D column determines whether this tops map is to be visualized or not (a click on this column
places the surface in the 3D Viewer or removes it from the 3D Viewer).
Bottom/3D
The Bottom column gives the name of the resulting base horizon for each unit (that is the tops
map of the unit below). The accompanying 3D column determines whether that base map is to
be visualized or not (a click on this column places the surface in the 3D Viewer or removes it
from the 3D Viewer).
Visualizing units
The “Visualization” button, , to be found at the top right corner of the units table, controls
the visualization of the tops and base surfaces. When it is depressed, the selected surfaces are
shown in the 3D Viewer. You select the surfaces using the 3D column in the Unit/Horizon
table.

Specifying units
Build units
Builds the units for the Structural Framework. It uses the current definition of the sequence of
surfaces (to be found on the right table of the Units folder) and applies the mesh map operations
based on the appropriate rules for this sequence of surfaces. See "Construction of Units and
Horizons from Mesh Maps" on page 757.
You can click on this button repeatedly in order to experiment with modifications to the
sequence or definitions of surfaces from the table. This process of unit creation can be repeated
until the definition of the units is committed by the creation of the block units inside the fault
blocks. See the description in "Fault block splitting" on page 186.
Note The block units themselves can be deleted by use of the Undo Block Units button (see
the description in "Undo block units" on page 188).
OPTIONS table
The OPTIONS table on the right side of the units folder shows the current sequence of surfaces
and types that go to make up the units when the Build Units button is applied.
3D
Determines whether the surface is to be shown in the 3D Viewer. A mouse click in this column
toggles the surface on and off in the 3D Viewer.
Surface
Shows the name of the surface (as defined in the main window tree). A mouse click over this
column highlights this surface for the purpose of reordering it relative to the others in the table
(see the "Move up/down" on page 184).
Select
Shows whether the surface is to be included in the unit construction (when the "Build units" on
page 183 button is selected). By default all surfaces in the main window surface tree are
assumed by FloGrid to be used in the unit building - you may elect to ignore certain surfaces
(and thereby create fewer units).
Map
Displays which of the maps belong to a surface (in the main window surface tree) and which
one is to be used in the mesh map operations. The default map is the first one in the list, but you
may use the drop-down menu to select a different map.
Th. Reference
If thickness maps are used to define surfaces, FloGrid (by default) calculates the Z-position of
the layer with reference to the layer immediately above it. This assumes that the Z-values
represent only the thickness of a particular layer. If instead, the Z-values represent the
cumulative total thickness from a layer somewhere above and including the current layer, then
you must identify an appropriate thickness reference.

Specifying units
The Th. Reference column allows you to specify the reference surface that is used to calculate
the position of a thickness map.
Type
The Type of surface refers to the Horizon-Unconformity rule that is applied when surfaces are
combined to form layers. A Type is either a Horizon or an Unconformity and is defined when
you specify the property type in the main window surface tree. Property types horizon and
thickness are assigned the horizon rule, and the property type unconformity is assigned the
unconformity rule.
The rules are as follows:
• The Horizon rule stipulates that map values from a lower surface are honored in preference
to map values from an upper surface. If the lower surface value is higher in elevation than
the upper surface value, the upper surface value is moved up to drape over the lower surface
value.
• The Unconformity rule honors the upper surface in preference to the lower surface. In this
case if the upper map intersects the lower map, the lower map values are truncated by the
upper map values.
If a surface has a null value and is added to a surface with a non-null value, the non-null value
always dominates the null value. The non-null value is not moved up in space or truncated by
the interpolation of a null value, no matter which rule is applied.
You can reassign rules in the Units table to change the preference for honoring map data.
Specifying a rule in the Structural Framework’s Units table does not change the property
definition in the Surface table of the Maps tab of the main window surface table. Changes
made to a property type in the main window surface tree after Units have been generated are
only reflected in the Units table when the Reset button in the structural framework is chosen.
You can thus have different versions of a structural framework, which compare the Horizon rule
to the Unconformity rule for a given horizon.
Visualizing surfaces
The “Visualization” button, , at the top right corner of the OPTIONS table controls the
visualization of the surfaces. When it is depressed the selected surfaces are shown in the 3D
Viewer. You select the surfaces in the 3D column in the table.
The relative order of the surfaces defines in which order the surfaces make up the tops and bases
of the units, and these can be set in the following ways:
Move up/down
When a particular surface is highlighted on the panel (by clicking on the Surface column) the
Move Up button moves the surface up one place (to a younger position in the list). The Move
Down button moves it down one place (to an older position in the list).
Reset
Returns the list to the default ordering (as defined by the surface order in the main window
surface tree).

Specifying units
Note If one surface completely obliterates another during the mesh-map operations a
warning appears in the Log window. This is so that you know when a unit has been
constructed with zero thickness. This may happen, for example, when an
nonconformity or horizon is physically lower at every point than an older surface (that
is a surface below it in the surface sequence).

Specifying units
Fault block splitting
Introduction
The Faults folder allows you to perform fault block splitting, thus enabling the simulation grid
cells to be positioned correctly with respect to faults. See "Fault block splitting" on page 209 for
a fuller discussion of this subject.
The Faults folder provides three tree views.
• The two Fault trees on the left show the faults in the system and enable you to visualize
and select the faults for inclusion or exclusion from the model. See "Select faults for
splitting" on page 186.
• The Options tree on the right shows in detail how far the splitting has progressed. It
provides facilities for editing the splitting and for visualization of intermediate stages in the
splitting. See "OPTIONS" on page 187.
Note This folder is also used to visualize fault surfaces and block units back-populated from
imported property models.
Select faults for splitting

The left side of the Faults folder shows two trees: the available faults and the unavailable faults.
These trees list all the faults in the system that can be used in fault block splitting. For example,
a fault that is created in the main window fault tree containing one or more fault traces can be
used in the splitting. However a fault in the fault tree that has no fault trace associated with it
cannot be used and does not appear in the fault trees.
You can select any of the faults that are available to be included in the splitting. By default all
faults are available for inclusion, but you can select and drag faults from the Available Faults
tree to the Unavailable Faults tree and back again as desired.
Note When a structural framework has been completed the two trees have slightly modified
headings. They become the Used Faults tree and the Unused Faults tree, to show
which faults were actually used in the splitting.
Auto split into blocks and block units

Once you have completed the selection of faults available for splitting the next stage is to create
the splitting and its associated block units. In general you can rely on FloGrid to calculate the
near-optimal (least number of blocks) splitting.
The Auto Split Into Blocks & Block Units button activates the three stages of fault block
splitting. For a full description of the three stages (analysis of faults, splitting into volumes and
the creation of block units) see "Fault block splitting" on page 209.

Visualizing faults
The “Visualizing” button, , which is in the top right corner of the Fault Trees panel,
controls whether the faults are placed into the 3D Viewer (see "3D Viewer" on page 107) or not.
When this button is pressed all selected faults (available and unavailable) are placed into the 3D
Viewer. Available faults are colored yellow and unavailable faults are colored blue. A selected
fault is colored red.
Note 3D picking of faults is supported. If you wish to identify a fault from its visualization
in the viewer, click on the visualized fault (with the mouse). It turns red and is similarly
highlighted in the Fault trees. A fault cannot be deselected from the 3D Viewer - it can
only be deselected from the fault tree (by using Ctrl-click in the normal way).
OPTIONS
The OPTIONS tree shows the progress and structure of the splitting. It enables you to build and
inspect the splitting in detail.
The tree is rooted at the volume of interest (shown as Volume of Interest). The volume of
interest is the area defined by the model boundary and dropped vertically through the vertical
extent of the model.
The volume of interest is split into two sub-volumes by the first fault in the chosen ordering (the
name of the fault is indicated on the tree). The sub-volumes are shown as branches (or children)
of the volume of interest. A sub-volume may itself be further split into two sub-sub-volumes
that are shown as its children.
When the splitting is complete and there are no more faults available to split any more volumes,
the volumes of the tree with no children (leaf volumes) can be designated as Blocks. These
blocks can themselves then be split into block units by the horizons bounding the units. The
name of designated blocks and number of block units they contain are shown on Volume tree.
Sometimes you may wish to experiment and see how a fault splits a volume into two. In this
case you can drag an available fault and drop it on the volume concerned. If the volume has
children the algorithm searches the children (and the children’s children and so on) to find a
suitable leaf volume to split with this fault.
The fault then splits the leaf volume into two. This process can be visualized using the
“Visualize blocks” button ("Visualizing blocks and block units" on page 187).
Visualizing blocks and block units

The “Visualize selected blocks” button, , is on the top right corner of the OPTIONS panel.
When this button is depressed any volume, block or block unit that is selected in the tree is
placed into the 3D Viewer (see "3D Viewer" on page 107). Block unit nodes are displayed in
the tree by double-clicking on the parent block. Double-clicking on a parent node when block
units are displayed below it collapses the tree back to the parent node level.
To select a volume, block or block unit, click on it with the mouse. It will turn dark blue.

Re-order available faults
The first stage in the automatic splitting algorithm is to order the major faults before the minor
faults to minimize the number of blocks that are created. See "Fault block splitting (FBS)" on
page 176 for a fuller discussion of this subject.
Even if you have elected to split the model manually it may still be useful to have the auto-
splitting algorithm begin by re-ordering the faults in the proposed major - minor ordering. You
can then inspect and possibly modify that ordering if it is unsatisfactory.
The Re-Order Available Faults button gives you the ability to do this. When this button is
pressed the auto-splitting algorithm orders the faults but then stops and does not proceed to split
the Volume of Interest into sub-volumes.
Build block units

The creation of blocks and block units is the last stage of the auto-splitting algorithm, and is
normally performed automatically. However, if you have decided to perform the splitting
manually, this last step must not be activated until after you have finished splitting the volumes
and sub-volumes.
When you are satisfied that all necessary faults are represented in the splitting, you can create
the blocks and block units by clicking on Build Block Units.
Sequential split into volumes

If you have decided on ordering of faults (for example, some variation of the major-minor
ordering provided by Re-Order Available Faults) the volumes may be created by dragging
and dropping each fault, in order, on the volume of interest or on a leaf volume.
However, Sequentially Split Into Volumes provides you with the facility to do this
automatically: it drops each fault sequentially on the volume of interest and then tries to work
out into which volume that fault falls.
Note Sequentially Split Into Volumes deals with each fault individually and in a fixed
(user-defined) ordering. As a result it does not have the flexibility of the auto splitting
algorithm to find the best way of inserting the faults into the volumes. A consequence
of this is that it may suffer some failures when you attempt to insert faults.
Undo block units

You may find a particular splitting unsatisfactory. For example, a small fault may be deemed
unworthy of inclusion in the splitting or a fault may have been left out (made unavailable) as an
experiment. When this happens you have the option of re-doing the entire splitting process.
You achieve this by undoing each stage of the splitting process in turn. The last stage (creation
of block units) must be undone first. This facility is supplied by Undo Block Units which.
When you click on this the model is returned to the stage just before the block and block unit
creation. This means that, although blocks and block units cease to exist in this model, the
volume splitting is still present.
Volume splitting can then be modified as required by inserting new faults or removing faults
that were included in the splitting. Volume splitting can be removed in part or entirely, if
required, by dragging the appropriate volume back to the fault tree.

Note The blocks and block units may be deleted until a property model (see "Geological
Property model" on page 215) has been created based on the completed structural
framework. Once a property model exists the underlying structural framework cannot
be edited further.

Creating FloGrid data models
Introduction
FloGrid uses POSC terminology to describe its data model.
The three key areas in the data model are:
• "Structural data model" on page 190
• "Property data model" on page 229
• "Property scenarios" on page 229.
Structural data model

The structural framework is made up of units, blocks and block units.
Units
Units are geological layers defined by two structural framework horizons, one above and one
below.
Horizons
Horizons in the structural framework are defined from the Reservoir Data Store by horizons,
nonconformities and thickness maps. They are made up from collections of block unit horizons.
Blocks
Blocks are created by fault splitting through the volume of interest (VOI).
Block units
Block Units are the intersection of a block and a unit. A block unit is bounded above and below
by a block unit horizon.
Block unit horizon

A Block Unit Horizon is the part of a horizon corresponding to a particular block.

Creating FloGrid data models
Fault framework editor
Chapter 10
Introduction
The Fault Framework module forms a part of the structural framework. It contains the
definitions of the fault intersection geometry used as a basis for constructing the Gridding
Control Framework, which can then be used by the Structured Gridder and Unstructured
Gridder to generate simulation grids that conform to the geometry of the faults in the model.
Note The Fault Framework and Gridding Control Framework modules are very similar
from an editing point of view. The principal distinction is that gridding controls can be
created, modified and deleted, while faults may only be modified, not created or
deleted.
This chapter contains the following:

• "Selecting faults/gridding controls for display" on page 192.
• "Editors" on page 193.
• "Editing lines and vertices" on page 195.
• "Editing faults/gridding controls" on page 199.
• "Fault block splitting" on page 209.
FloGrid User Guide Fault framework editor 191

Introduction
Selecting faults/gridding controls for display
The Fault Framework node for a structural framework appears in the data tree under the
corresponding Structural Framework node . Below this are individual subnodes
corresponding to each of the faults. The Gridding Control Framework node for a
gridding model appears in the data tree under the node for the corresponding model.
Faults and gridding controls can be added to or removed from the display by checking or
unchecking the corresponding node in the data tree. Faults and gridding controls are normally
displayed as a translucent ribbon surface, bounded by upper and lower lines color-coded in
magenta and cyan to represent the top and bottom edges respectively; optionally the average
line may also be displayed in red (Figure 10.1).
Figure 10.1 Two intersecting faults
Changing the way that fault/gridding control

nodes are shown in the Data Tree
Beneath the parent node representing the fault/gridding control framework, the nodes
representing individual faults or gridding controls are organized by default as a flat list, allowing
you to show and hide faults or gridding controls individually. You can change this organization
if desired, to reflect the presence of intersections. Right-click on the parent node for the fault
framework/gridding control framework in the data tree, and select the Show intersection
subnodes... option. This opens a dialog that allows you to specify whether you wish to display
subnodes for:
• minor intersecting faults only
• major intersecting faults only
• all intersecting faults.
Select the desired mode and click on OK.
192 Fault framework editor FloGrid User Guide

Selecting faults/gridding controls for display
Editors
• "Starting the editors" on page 193.
• "Using the editors" on page 193.
Starting the editors

To start an edit session, select the node in the data tree corresponding to the fault
framework/gridding control framework to be edited, right-click and select Edit from the popup
menu. (You may also start the edit by right-clicking on an individual node corresponding to a
specific fault or gridding control that you wish to edit; the editor opens with the selected fault
or gridding control already present in the display).
Using the editors

In order to manipulate a fault/gridding control in the editor, you must first add it to the display
in an editable form. Within the editor, you can make faults/controls editable by picking on the
ribbon surface. Editable faults and controls are displayed with the top and bottom lines of the
fault (together with any intervening lines) shown as tubes (Figure 10.2). The lines are defined
by a sequence of vertices, which are displayed as cubes along the line.
Note For optimum display of the control vertices and the editor cursor, ensure that lighting
is turned on while editing. Use the button for this.
Figure 10.2 A fault in the process of being edited by moving the vertices

Editors
The functionality of the editors can be divided for the purposes of description into two parts.
• The first part comprises those functions concerned with detailed editing of the lines
that comprise a fault or gridding control, by means of adding, moving and deleting
individual vertices.
• The second part comprises those functions concerned with manipulating the
faults/gridding controls as a whole, for example, by allowing selection of sections of a
fault/control for subsequent copying or deletion, extension of existing faults/controls,
splitting of faults/controls in two, merging together of pairs of faults/controls to form
a single entity, and so on.
The editors support multi-level undo, so that the results of an individual edit operation can be
reversed within an edit session without invalidating previous edit operations. To undo an
operation, select the button from the toolbar.
Note The editors rely on the use of 3D picking to function correctly. In practice this means
that in order to manipulate any entity within the editor, you must be able to pick on it.
Picking does not work if the object that you wish to pick (line, vertex or cursor) is
obscured by another object in front of it at the pick position. If this is the case, consider
either rotating the viewpoint to a position from which you obtain an unobstructed view
of the object you wish to pick, or removing the obscuring object from the display.

Editors
Editing lines and vertices
This section includes information on the following options:
• "Cursor Move" on page 195.
• "Snap Move" on page 196.
• "Change Cursor Type" on page 196.
• "Magnification Controls..." on page 197.
Cursor Move
Places the editor into Cursor Move mode. (In 2002A this was referred to as Select Vertices
mode.) In this mode, you can first select a single vertex or set of vertices, and then use the cursor
to move them. The editor maintains the concept of a current selected set of vertices, which are
displayed in a different color used for highlighting (yellow).
Selecting single vertices

Picking on a vertex selects it. This is signaled by a change in color to the highlight color, and
the cursor moves to the selected vertex. Usually any previously existing selection is cleared
first.
Selecting multiple vertices

Multiple vertices may be selected by holding down the Ctrl key while picking subsequent
vertices, to prevent the current selection from being cleared.
Selecting groups of vertices

To select groups of vertices along a line, pick the vertex at one end of the group and hold down
the Shift key while picking the vertex at the other end of the group. As before, holding down
the Ctrl key prevents the current selection from being cleared.
Selecting all vertices along a line

To select all vertices along a line, pick the line itself. The cursor moves to the position of the
pick along the line, and all vertices along the line are selected.
Deleting selected vertices

Pressing the Delete key while in Cursor Move mode deletes the currently selected vertex or
vertices.
Moving the selected vertices with the cursor

Click on part of the cursor to start the move, and you can then drag the selected vertices to a new
position. All the selected vertices move in parallel. The nature of the movement depends on the
cursor type and the part of the cursor that was picked (see below).

Snap Move
Places the editor in Snap Move mode. In this mode, the selected vertex or vertices can be
moved or “snapped” to the position of an existing 3D object on the display.
Selecting and moving a single vertex

Click on the vertex to be moved, and drag to the new location. The vertex is selected and you
will see a red line connecting the mouse pointer to the dragged vertex. When the mouse pointer
is over another pickable object in the display (indicated by the red line turning white), releasing
the mouse causes the selected vertex to snap to the picked location. If the mouse button is
released while the pointer is not over a pickable object, no movement takes place.
Selecting and moving multiple vertices

Selection of the vertices to be moved is identical to the mode "Cursor Move" on page 195. Once
the desired selection has been made, hold the Ctrl key down (to prevent the selection being
cleared), click on one of the selected vertices, and drag to the new location as described above.
When the mouse button is released over a pickable object, all the selected vertices move in
parallel.
Deleting selected vertices

Pressing Delete while in Snap Move mode deletes the currently selected vertex or vertices.
As with all editor actions, you can reverse the effect of the snap movement by clicking on Undo
.
Insert Vertices
Places the editor in Insert Vertices Mode. In this mode, you can insert new vertices in an
existing line. Pick on the line at the position where each new vertex is to be inserted.
Delete Vertices
Deletes the currently selected vertex or vertices. Selecting this option has the same effect as
pressing the Delete key while in Cursor Move or Snap Move modes.
Note You are not allowed to delete the end vertices of a line; you may only delete the interior
vertices.
Change Cursor Type

Selects the cursor type, which in turn determines the constraints on the movements that may be
made. Each cursor type consists of a number of bars and/or a flattened cuboid. By picking and
dragging on one of the bars, you can move the current selection constrained along the direction
of the bar; by picking and dragging on the flattened cuboid, you can move the current selection
freely in a plane.

Constrain X, Y, Z
Constrains movement of the current selection along each of the X, Y and Z axes.
Constrain Z, Free X, Y
Constrains movement of the current selection up and down the Z axis, or freely in the X-Y
plane.
Constrain by Line
Constrains movement of the current selection in a direction determined by the last selected
vertex. There are two possible orientations. You can toggle between them by clicking on the
Constrain By Line button.
Movement constrained by the line

The cursor is oriented tangentially to the line at the position of the last selected vertex.
Movement constrained by the fault/gridding control

The cursor orientation depends on the position of the last picked vertex relative to the fault or
gridding control. Picking one of the end vertices orients the cursor along the corresponding end
coordinate line of the fault/gridding control. Picking one of the other vertices orients the cursor
normal to the line tangent at the picked vertex, along the local direction of slope of the
fault/gridding control surface.
Note With all cursor types, movement is not allowed if the current viewpoint does not afford
a good perspective on the selected axis (that is, the drag axis makes an angle of less
than 30 degrees with the view normal). If this is the case you are alerted with a message
in the status bar prompting you to rotate the view to a better viewpoint for the drag.
Magnification Controls...
Opens the Magnification Controls dialog (Figure 10.3). This allows you to control the sizes of
the different visual elements of the 3D Editor on the display. The Lines slider controls the width
of lines displayed as tubes, the Markers slider controls the size of the vertex markers, and the
Cursor slider controls the size of the cursor. These may be controlled individually if desired.
You can control the size of all three elements simultaneously by checking the Link Together
checkbox.

Figure 10.3 Magnification Controls dialog

Editing faults/gridding controls
• "Select Fault/Control Section" on page 199
• "Build Intersection" on page 201
• "Copy Section" on page 201
• "Delete Section" on page 201
• "Split Control" on page 202
• "Merge Controls" on page 202
• "Toggle Spline" on page 202
• "Digitize New/Extended Control..." on page 202
• "Edit Loop" on page 206.
Select Fault/Control Section

Places the editor in Select Fault/Control Section mode. In this mode
• you can select positions along a fault or gridding control (for example to define the
position at which a gridding control is to be split in two)
• you can define sections of a gridding control (for example, for subsequent deletion or
copying), or
• you can select the entire length of the fault or gridding control (for example, to change
the interpolation type).
Selecting a position along a fault or gridding control

With the editor in Select Fault/Control Section mode, pick on the gridding control you wish
to select. A yellow line appears showing the position of the pick; this line lies on the surface of
the gridding control and passes through the position of the pick (Figure 10.4). You can also pick
on the top or bottom lines of the gridding control, or on one of the control vertices of the top or
bottom lines.

Figure 10.4 Intersecting faults following selection of a position along the major fault (shown in yellow)
Selecting a section of a fault/gridding control

With the editor in Select Fault/Control Section mode, select the position on the fault/gridding
control corresponding to one end of the section, as above. A yellow line appears showing the
position of the pick. Holding down the Shift key, select the position corresponding to the
other end of the section. The selected section of the fault or gridding control is highlighted
(Figure 10.5).
Figure 10.5 The same faults, after selecting a section of the major fault (shown in yellow)
Selecting the entire fault/gridding control

With the editor in Select Fault/Control Section mode, double-click on the fault/gridding
control. The entire fault/gridding control becomes selected and is displayed in the highlight
color.

Build Intersection
This allows you to build an intersection between two selected faults/gridding controls.
Normally, this option is dimmed. Select the two faults/gridding controls which are to be
intersected (for example by double-clicking on them as described above). The Build
Intersection option is enabled. Pressing this button builds an intersection between the two
selected faults/gridding controls.
Where two intersections are possible between the selected faults/gridding controls, ambiguity
exists as to which intersection should be built (for example, in the cases shown in Figure 10.6).
You can indicate which of the intersections should be built by making the selection on the minor
fault/gridding control close to the desired intersection; this intersection is then built in
preference to the other one.
Figure 10.6 Potentially ambiguous multiple intersections between pairs of faults/gridding controls (areal view)
Copy Section
Creates a new gridding control by copying a section of an existing one. Normally, this option is
dimmed. Select the section of an existing gridding control that you wish to copy, as described
above. The Copy Section option becomes enabled. Click on this button, and a dialog opens
asking you to enter a name for the new gridding control. Enter a unique name and click on OK,
and the new gridding control is created and added to the display.
Delete Section
Deletes all or a section of an existing gridding control. Normally, this option is dimmed. Select
the section of an existing gridding control that you wish to delete, as described above. The
Delete Section option becomes enabled. Click on it to delete the selected section of the
gridding control. If the entire gridding control was selected, rather than just a section of it, this
action removes the control entirely.
If the section of the gridding control selected for deletion does not include one of the ends,
deleting it splits the original gridding control into two parts. The two parts have the same name
as the original gridding control, but with the suffices “:1” and “:2” appended.

Split Control
Splits an existing gridding control in two. Normally, this option is dimmed. Select the position
at which you wish to split the gridding control, as described above. The Split Control option
becomes enabled. Click on it to split the gridding control into two parts at the selected position.
The two parts have the same name as the original gridding control, but with the suffices “:1”
and “:2” appended.
Merge Controls
Merges together two existing gridding controls. Normally, this option is dimmed. Select the pair
of gridding controls that you wish to merge. The Merge Controls option becomes enabled.
Click on it to delete the two selected gridding controls and replace them by one gridding control
formed by merging them (joining together the two closest ends).
You are asked to specify the name to be used for the new control: a default name is suggested
based on concatenating the names of the constituent controls.
Toggle Spline
Changes the interpolation type of a fault or gridding control. Normally this option is dimmed.
Select the gridding control or controls for which you want to change the interpolation style (for
example by double-clicking on them with the editor in Select Fault/Control Section mode).
The Toggle Spline option becomes enabled. Click on it to specify whether you wish to use
spline interpolation for the selected fault/control.
Digitize New/Extended Control...

Sets the editor into Digitize Mode and brings up the Digitize New/Extended Control dialog
(Figure 10.7). In this mode, you can digitize a set of control lines for a new gridding control, or
alternatively digitize an extension to an existing fault or control. Note that if you are editing a
fault framework, as opposed to a gridding control framework, the Create Control option is
unavailable.

Figure 10.7 Digitize New Control dialog
Digitizing lines
A single click starts digitizing a new line. The new line is displayed in red. Successive clicks
add new vertices to the line, while pressing Delete removes the last vertex to have been added.
Double-click or press Return to finish digitizing the line. You can then digitize further lines
in the same way.
Removing digitized lines

You can remove the last line to have been digitized if desired by clicking on the Clear last line
button on the Digitize New/Extended Control dialog. Clicking on the Clear all lines button
allows you to start digitizing lines again from scratch.
Changing the line interpolation strategy

The checkbox Use spline interpolation controls whether or not the digitized points should be
connected by spline-interpolated lines. If this box is unchecked, the digitized points are
connected by straight-line segments.
Picking from existing lines

Existing lines may be used to define the vertices of the new line being digitized. Picking on a
vertex of an existing line adds it to the new line. You can select a contiguous group of vertices
from an existing line by picking on the first vertex of the group, then holding Shift down
while selecting the last vertex of the group; all intervening vertices are added as well. Picking
on the line itself adds a vertex that lies on the line.

Picking from pick guides
Pick guides may be used in the same way as existing lines to define vertices to be added. Display
the pick guides to be used from the Edit | Select Pick Items menu.
Picking from other objects in the display

Other displayed objects, for instance maps and surfaces, may also be used for defining the
positions of new vertices. Picking on these objects defines a new vertex at the location of the
pick.
Note Where the digitized position does not result from a pick of another object, the 3D
position of the newly created vertex lies on the “edit plane”, an XY plane passing
through the framework. The Z location of this edit plane initially lies at the top of the
fault/gridding control framework, but is changed following a 3D pick on an existing
object in the display.
Generating a new gridding control

You must specify the name of the new control to be created in the type-in box on the dialog. At
least one complete line is required in order to generate the new gridding control. Once the
required number of lines have been digitized, press Create Control on the dialog to generate
the new control. (If the dialog has become hidden, click on the Digitize New/Extended
Control... toolbar button to bring it to the front of the display again.)
Note If only one line has been digitized, this is projected in Z on to the top and bottom planes
of the gridding control framework in order to generate the top and bottom lines of the
gridding control. If two or more lines have been digitized, these are used directly to
generate the new control without the need for any projection.
Extending an existing fault or gridding control

To extend an existing fault or gridding control, ensure that the first vertex of the digitized line
or lines is coincident with the end of the fault or gridding control to be extended. This is best
achieved by making sure that the vertices on the control to be extended are visible, and picking
on the end vertex to define the position of the first vertex for the extension (Figure 10.8).
Note The drop-down list giving the choice of which fault/control to extend is not enabled
until the first extension line is completed (by double clicking). This is so that only
relevant faults/controls are offered for extension.

Figure 10.8 Digitizing an extension to the top line of an existing gridding control
When you have finished digitizing the extension line, the Digitize New/Extended Control
dialog shows the name of all faults or gridding controls that you can choose to extend. Select
the fault/gridding control that you wish to extend, and click on Extend to extend the selected
fault/gridding control.
If only one extension line has been digitized, this is copied as many times as necessary to define
the extensions for each of the lines of the fault/gridding control. You may if you wish define
separate extension lines for each of the lines of the fault/gridding control (Figure 10.9).
Figure 10.9 The same control after digitizing the extension to the bottom line

Figure 10.10 The same control after extension
Edit Loop
Sets the editor into the Edit Loop edit mode. The purpose of this mode is to allow correction of
faults imported from Rescue models for which the top and bottom edges are incorrectly
specified (for example Figure 10.11). You can indicate which portions of the loop should be the
top and bottom edges respectively and rebuild the fault.
The top and bottom edges are indicated by placing “beads” around the loop. There are two
magenta beads that define either end of the top edge, and two cyan beads that define either end
of the bottom edge. Once all four beads have been placed, the fault can be rebuilt.
Figure 10.11 Rescue model fault with incorrectly specified top (magenta) and bottom (cyan) edges
Defining the top edge

With the Edit Loop edit mode selected, pick the fault to be corrected at one end of the top edge.
The fault is added to the view in editable form if it is not present, and a magenta bead should
appear on the loop at this point. (If necessary use the Magnification Controls dialog to make it
large enough to see easily).

Next, pick on the fault at the other end of the top edge. A second magenta bead should appear
on the loop. The two magenta spheres define the ends of the top edge.
Defining the bottom edge

The bottom edge is defined similarly by picking on the fault at the position where the ends of
the bottom edge are to be placed. Each pick places a cyan bead on the loop near the pick
position. The two cyan beads define the ends of the bottom edge (Figure 10.12).
Figure 10.12 The same fault after placing the four beads to define the correct top and bottom edges
Correcting the position of the beads

You can slide beads around the loop by picking on them and dragging them to the new position.
Pressing Delete deletes the last bead to have been added, allowing it to be replaced in a
different position. If all four beads are deleted, they can be replaced around a different fault.
Rebuilding the fault

Once all four beads are correctly in place, you can rebuild the fault by double-clicking or
pressing Return (Figure 10.13). Note that it is possible to form invalid arrangements of the
four beads, in which magenta and cyan beads alternate around the loop; if this is the case you
are warned, and the fault is not rebuilt. Edit the beads as necessary to form a valid arrangement
and try again.

Figure 10.13 The corrected fault

Introduction
The structural framework analyzes and stores information about faults so that a suitable throw
(consisting of split nodes) can be put between two simulation grid cells that straddle a fault. This
is achieved through fault block splitting.
Fault block splitting entails dividing the volume of interest (VOI) into blocks each of which
contains no faults. This means that the faults all occur at the boundaries of the blocks.
Once these blocks have been created it is a simple matter to construct block unit horizons which
represent a particular horizon within one block. Because a block contains no faults a block unit
horizon may be represented by a single mesh map containing no holes or regions defined in
multiple ways.
This means that when a simulation grid is being built, all that remains to do is to decide into
which block a coordinate tube (column of simulation grid cells) falls. After this decision is
made, the heights of the nodes for any cell can be calculated by sampling from the block unit
horizons for that block.
Fault block splitting is considered under the following headings:
• "Splitting the model into fault blocks" on page 209
• "Fault analysis and ordering" on page 210
• "Recursive volume splitting (with a final forced splitting)" on page 210
• "Creating block units and sampling fault traces" on page 211
• "Manual fault block splitting" on page 212
• "Limitations of the fault block splitting algorithm" on page 213.
Splitting the model into fault blocks

The prerequisites for fault block splitting are:
• an area of interest has been created (the structural framework boundary)
• faults have been selected as candidates for the splitting
The “splitting” fault trace belonging to a fault (in the main window tree) is the one that
governs the splitting.
• horizons have been created (see "Construction of Units and Horizons from Mesh Maps" on
page 757 for more details).
The three steps involved in splitting the model into fault blocks are:
1 Fault analysis and ordering
2 Recursive volume splitting (with a final forced splitting)
3 Block unit creation and sampling of fault traces.

Fault analysis and ordering
Each fault is processed by the splitting algorithm, either as a single fault trace or as a fault trace
polygon (the first or primary trace in the main window fault tree list of fault traces belonging to
that fault).
The first step in splitting up the volume of interest is to split up the area of interest. To do this
the algorithm requires a single 2D (poly) line representing each fault. For this reason fault
polygons are averaged (from up- and down-thrown traces) to establish a single splitting line.
Once the algorithm has created a single 2D line for each fault, extensions are then added so that
each fault either intersects another fault or extends beyond the area of interest. Any fault that
lies completely outside the area of interest is rejected, as is any fault that intersects the area of
interest boundary more than twice.
The algorithm now minimizes the number of blocks that it needs to create, by selecting major
faults before minor faults when used for splitting. See Figure 10.14.
Figure 10.14 How FloGrid analyzes and orders faults
Extension to Fault C
Fault C (minor to Fault B)
Fault B
Fault A (minor to Fault A)
(major fault)
(major to Fault C)
Recursive volume splitting (with a final forced splitting)

The faults are now taken in order, major before minor, and sequentially placed into the Area of
Interest (the AOI is taken from the structural framework boundary). The first fault splits the AOI
into two sub-areas. The next fault splits one of the two sub-areas into two further sub-areas. As
each fault is placed into an area it splits the area into two sub-areas. Because of the major-minor
ordering of the faults, each fault normally splits just one sub-area into two.
Sometimes it is not possible to order a set of faults because they have a cyclic major minor
relationship. This is shown in Figure 10.15.

Figure 10.15 Faults with a cyclic set of major-minor relationships
In this case the faults are ordered arbitrarily and at least one fault ends up splitting more than
one volume. See Figure 10.16.
Figure 10.16 How FloGrid splits fault blocks with a cyclic set of major-minor fault relationships
First fault Second fault

(splits AOI into two) (divides one block)
Third fault
Area of Interest
(divides two blocks)
Once all faults have been placed into the area of interest, the blocks are created.
The volume of interest (which is made up of the area of interest extended vertically through all
the maps in the system) is now split vertically in the same order as the area of interest. The
volumes created have vertical sides and have area profiles the same as the sub areas created by
the 2D fault lines.
Volumes that are not themselves split are known as blocks.
Creating block units and sampling fault traces

Now that the blocks have been created, the next stage is to build up stacks of block unit horizons
for each block.
This is done by creating new mesh maps for each block and for each horizon. The maps are then
nulled out in parts and re-interpolated in order to establish correctly the throw across the fault.
Finally all the maps are made to conform with all other maps for that block. For details about
how the map is re-interpolated and made to conform, see "Construction of Units and Horizons
from Mesh Maps" on page 757.

All these maps are then allowed to intersect with the blocks to create a set of block units for each
block.
The last stage is to apply resampling of the 2D fault traces to the new block unit horizons so that
the simulation grid coordinate lines can be deviated to lie on the fault (for unstructured grids).
See Figure 10.17 and Figure 10.18
Figure 10.17 How FloGrid creates new mesh maps for each block and horizon
Cross-section Upthrown Downthrown

Fault Trace Fault Trace
Horizon
Splitting Line
(Block Boundary) Block Unit Horizon
Re-interpolated Extension
Figure 10.18 How FloGrid applies re-samples of the 2D fault traces to the new block unit horizons
Cross-section Resampled Resampled

Upthrown Downthrown
Fault Trace Fault Trace
Splitting Line
(Block Boundary) Block Unit Horizon
Re-interpolated Extension
Manual fault block splitting

In some cases you may decide that the split obtained by the automatic splitting algorithm is not
optimal. The structural framework window lets you manually split the VOI.
In the structural framework window you can drag and drop faults on to blocks. When a fault is
dropped on to a block the structural framework determines which of the sub-blocks of that block
is the best candidate for a split by that fault. Once that block has been determined (it may be the
original block if that had no sub-blocks) it is split into two sub-blocks.
The process can be viewed graphically on the 3D Viewer by enabling the 3D view of each tree
(by clicking on the 3D view icons at the top right corner of each tree in the structural framework
window).

If you elect to split the model manually you must complete the process (of building the block
units and sampling the fault traces) by clicking on Build Block Units (below the block tree).
Note You can run the ordering for only part of the automatic splitting by pressing the Re-
Order Available Faults button below the block tree. This orders the faults into a
major/minor hierarchy. The Sequentially Split Into Volumes button allows you to try
and use the existing fault ordering or your own defined ordering, to split the entire
model into volumes.
Limitations of the fault block splitting algorithm

The splitting algorithm splits areas (and projected volumes) into sub-areas (and projected sub-
volumes) with a minimum of three sides. This means that a fault is not allowed to split the side
of a block more than once.
Occasionally this occurs in the automatic algorithm. The algorithm then proceeds by splitting
the fault itself in two, and inserting the two pieces of the fault into the block one after the other
as if there were two faults.
In the event that a fault splits one side of the structural boundary more than once, the remedy is
to change the major/minor status of the boundary’s digitized points (using the boundary editor),
thus moving one corner of the boundary so that the fault now straddles two sides of the
boundary.

Geological Property model
Chapter 11
Introduction
• "Creating and deleting models" on page 217.
• "Importing data" on page 218.
• "External model" on page 220.
• "External properties" on page 221.
• "Scenarios" on page 222,
• "Creating and editing model properties" on page 223.
• "Creating property maps" on page 228.
• "Property data model" on page 229
The Property Model module combines map-based and 3D geological modeling approaches.
This provides a consistent 3D structural and property representation from which to build
simulation grids. The module has the following major functions:
• Importing 3D geological models. FloGrid supports a number of proprietary formats
including the RESCUE standard.
• Assigning maps to units created in the structural framework (see "Structural Framework"
on page 175). If you have not assigned property maps to apply above or below a given
surface in the Surface node this allows you to directly assign the maps to units.
• Creating additional properties for a property model. Properties can be defined in three
ways: with simple arithmetic expressions as simple functions of two or fewer existing
properties, with complex conditional expressions using any existing properties, or with user
defined functions using the Calculator. (See"Calculator Language" on page 701 for
details.)
• Exporting static or dynamic properties from FloGrid back to the geological model.
• Managing Property Scenarios. (See "Property scenarios" on page 229 for details.)
FloGrid User Guide Geological Property model 215

Introduction
The Property Model window can be opened using Tools | Property Model...
This window has a menu bar from which various menu options can be selected that allow you
to create and edit property models. There is also a model and mode selection area, and a display
area that contains a folder called "Creating property maps" on page 228.
216 Geological Property model FloGrid User Guide

Introduction
File menu
Create model...
Opens the Create Property Model panel, which allows you to select a structural framework
(see "Structural Framework" on page 175) from a list of the existing models, to use as a basis
of your property model. It also allows you to enter a name for the new property model.
Note When a property model is created any property maps belonging to surfaces are
automatically assigned to the units built from those surfaces.
Delete model
Opens the Delete Property Model panel, which contains a list of property models. A model
can only be deleted if no simulation models derive from that property model.

Importing data
Property model
Imports data directly into the property model. There are three geological model formats that
may be imported to create a property model:
• Geolith
• RESCUE (Versions 9 - 35)
• Stratamodel (SGM 5).
For a complete description of these input formats please refer to "Property model input formats"
on page 798.
Geolith...
Select the required Geolith file. This format is a useful way of importing structurally simple,
3D models that can be defined using a regular dx, dy grid with varying z values. Input is in
ASCII format.
RESCUE
Select the required RESCUE file. The RESCUE format is the preferred way of importing
geological models from most geological modeling applications.
Note FloGrid supports RESCUE models exported using Versions 9 to 35.1 of the RESCUE
class library. The RESCUE participants have agreed that all commercial releases of
geological modeling applications supporting RESCUE will ensure that they export
models in this range.
RESCUE models exported with Version 12 and above are now a set of files rather than a single
file. This is to support several new features, notably load on call, which allows applications
accessing the RESCUE model to only load parts of the model as they require it. This makes
FloGrid much more memory efficient.
Note To reduce storage in the workspace file (which is still significant), FloGrid does not
duplicate the RESCUE file contents in the Workspace file if a session is saved. This
means you must retain the RESCUE file when using Save and Restore.
Note FloGrid allows you to edit the faults imported from RESCUE.
Stratamodel...
Select the required Stratamodel model. Models are read using OpenSGM libraries to allow the
native Stratamodel project files to be accessed.

Importing data
Hint This means that it should not matter which of the Stratamodel files is picked to import;
OpenSGM ascertains the associated project. If in doubt, we recommend you select the
file with type .amd.
Note This option can only be used for reading unfaulted Stratamodel models built using
SGM 5.0. If a faulted Stratamodel model is to be read into FloGrid it should be
exported from Stratamodel using RESCUE.
When you import a property model from an external geological model, a suitable structural
framework (see "Structural Framework" on page 175) is first constructed and then block unit
grids are built to cover the block units. Finally, property arrays are loaded for these grids.
When such a property array is loaded it may be that FloGrid does not recognize the external
name of the property as relating to one of its internal property types. If this happens, the property
is assigned the unknown property type and the Set External Property Types panel appears to
prompt you to match this and any other unknown imported properties with FloGrid internal
property types. See the description of the Set External Property Types panel in "External
properties" on page 221.
Property type mapping files

If models with similar or identical property type mappings are to be used regularly it is
recommended that they are entered into a property type mappings file, the location of which can
be set in the config file. Separate property mapping files can be set up for Geolith, RESCUE
and Stratamodel.
Each file consists of a series of rows, each with two character strings. The first column gives the
third-party property type name, the second gives the equivalent FloGrid property type.
Note Multiple third-party property types can map onto the same FloGrid property type.

Importing data
External model
Note This functionality is only available for RESCUE models. It is intended primarily for
use in releases where geological modeling applications are capable of one or more of
the following: reading properties created on a RESCUE files, supporting property
scenarios, supporting partial / real-time RESCUE model updates. (See "Property
scenarios" on page 229 for details.)
Export new properties to external model...

Exports to the external representation of the current property model any new Property Model
properties that have been created in FloGrid in the current modeling scenario.
For RESCUE models, the properties are written to the existing RESCUE file in a new scenario.
Caution This option uses a lot of memory, as all properties to be exported are loaded into
memory at once. It is therefore strongly recommended that only a few properties
are exported. This can be achieved by deleting properties from the current
scenario using the Property Model Property Editor.
Resynchronize with modified external model...

Forces FloGrid to re-read the current RESCUE model files to take account of any changes to
properties in the RESCUE model since it was originally read.
Caution This option cannot be used if the RESCUE model structure has changed.

External model
External properties
Set external property types...

Opens the Set External Property Types panel. This allows you to assign properties on the
imported property model to FloGrid property types. This panel can be used when importing a
property model or subsequently to set or reset assignments.
The Set External Property Types panel contains a table with two columns. The External
Property column shows the external description of the property as it was imported from the
external geological model. The FloGrid Property column contains a drop-down menu for each
row, allowing you to select the appropriate internal FloGrid property type for this property array.
Note FloGrid supports only one property of each type per model, unless the model has
Property Scenarios defined in the RESCUE model by the geological modeling package
that created it. If you attempt to assign two imported properties to the same FloGrid
internal property type, only the first property of that type is available in the property
model when upscaling or visualizing the model. (See "Property scenarios" on page 229
for details.)

External properties
Scenarios
Note This functionality is only available for RESCUE models. It is intended primarily for
use in releases where geological modeling applications are capable of one or more of
the following: reading properties created on a RESCUE files, supporting property
scenarios, supporting partial / real-time RESCUE model updates. (See "Property
scenarios" on page 229 for details.)
Set modeling property scenario...

Select the currently active scenario from the list of available scenarios. This scenario is used in
places where there is no user interface to select a scenario.

Scenarios
Creating and editing model properties
• "Current model" on page 223.
• "Create properties" on page 223.
• "Property model property editor" on page 223.
• "Display" on page 224.
Current model
Displays the currently selected property model. This currently selected model is the one whose
details are shown in the Property Map folder below.
The drop-down list at the side of the text box shows all the models available. If you select a
different property model from this drop-down list, the details shown in the folder below change
to reflect the new choice of current model.
Create properties
Opens the Property Model Property Editor panel.
Property model property editor

Current model
Sets the current model in which the properties can be created or edited.
Property scenario
Set the property scenario on the current model in which the properties can be created or edited.
Property
Selects the property to be created or edited. A * next to a property shows that it is an existing
property to be edited.
As FloGrid only supports one version of a property type in a property scenario, properties are
selected using their property type names. If you wish to create new property types, use the
Property Types menu item in the main window Tools menu.
Defining properties
You can define the properties in three different ways:
• Use simple expressions involving constants and/or one or two other properties.
• Use complex conditional expressions using any existing properties.

• Use the Expression Calculator (see "Expression Calculator" on page 687).
The Property Editor exports variables for use in a Calculator script (see "Property model
property editor commands" on page 719) and runs the script once for each block unit.
Generate by
The three methods of defining properties in the Property Model Property Editor panel are
selected by the two Generate by radio buttons:
Expression
When you choose this option you enter an expression in the next 2 lines of the window. This
involves
• typing in a constant or selecting a property/property scenario on which to base the new or
edited property (from the first pair of drop-down lists);
• (optional) selecting an arithmetic function from the second drop-down list;
• (optional) selecting a second property/property scenario or constant from the third pair of
drop-down lists.
When you select a property, you must also select the property scenario containing the property
from the drop-down list. Note that all properties selected must be from compatible scenarios;
this means from scenarios that exist on the same set of Block Unit Grids.
Advanced Expression
When this option is chosen a separate panel is created, the Expression Builder. This is the
panel where the advanced expression is typed in, or edited, and validated. When a valid
expression is applied, the advanced expression window on the Property Model Property
Editor panel is updated with that expression. Note that all properties used in the advanced
expression must be from the same scenario.
Calculator
When this option is chosen you can enter the location of a calculator script file in the Calculator
file text entry field.
OK
OK applies the edit and closes the Property Model Property Editor panel (or simply closes
the window if the edit has already been applied).
Note This means that the current edit is applied before closing the pane, even if that edit has
already been applied.
Display
Opens the 3D Viewer and allows you to visualize the currently selected property model in the
3D Viewer. The panel provides a selection of different kinds of displays, properties, and views
in I, J, and K directions. The default view contains only the hull edges and looks exactly like the
default view of the structural model (see "Structural Framework" on page 175). The panel
provides the following options:

Select model
Selects the model to view. Only models that have been added to the 3D Viewer from the
Property Model window are available.
Select scenario
Selects the property scenario from which the property to be viewed is to be selected.
Select property
Selects which property to display from those available for the currently selected model and
model property scenario. Properties are displayed if the Show Property option is selected and
I, J or K slices are selected.
Select units and blocks

Controls the selection of which units and blocks (block units) are affected using the viewing
controls in this dialog. If all units or all blocks are selected from the lists, display choices
supersede previous selections made for individual blocks and units.
Show block unit edges

When this box is checked the wireframe of the selected block unit(s) is displayed.
Show block unit faces

When this box is checked the top and bottom surfaces of the selected block unit(s) are displayed
as colored surfaces. Surface color can be selected from the Select block unit Color... option
on this panel.
Show property
When this box is checked the selected property is displayed in the 3D Viewer according to the
slicing options below.
Select block unit color...

Sets the color to be used when the currently selected block unit surfaces are displayed. The
button displays a Color Selector dialog containing a table of colors. To set a new color pick it
in the table and click on Apply. This will update the legend in the Display dialog.
I, J and K Slicing
Displays multiple I, J and K slices from the selected block unit grids. The property to display is
selected from the Select Property list. Enable Show property to display the selected slices.

Exactly how I, J or K slices are labeled (numbered) in the lists can depend on the type of
property model being displayed. By default, I, J labeling corresponds to the I, J numbering of
the property model grid, and K labels are constructed from the unit name and the layer number
within that unit. This labeling can be overwritten if the property model is a RESCUE model and
I, J or K labeling information (sometimes referred to as layer or IJK equivalency) has been
supplied by the geological modeling application that generated the model. In this situation,
FloGrid labels the slices using the supplied labeling scheme.
Note Once slices are in the display, they can be probed by picking on individual cells.
Information about the picked cell such as the block, unit and IJK numbers is displayed
in the message area at the bottom of the 3D Viewer.
I-Direction/Every Nth/ Apply

Displays how many layers there are in the I direction and allows the selection of which slices
are displayed. The arrow buttons move the selections up or down. The Reset button resets the
choice to every layer. You can also select slices by entering the name directly in the type-in box;
use a comma to separate multiple entries and a dash to represent a range of selections.
J-Direction/Every Nth/ Apply

Displays the number of layers in the J direction and allows the selection of the slices to be
displayed. The arrow buttons move the selections up or down. The Reset button resets the
K-Direction/Every Nth/ Apply

Displays the number of layers in the K direction and allows the selection of the slices to be
displayed. The arrow buttons move the selections up or down. The Reset button resets the
Increment
Use Increment to move the property down through the block using K Slicing or across the
block using I, J Slicing.
Several I, J slices can be selected for display from the Property Models panel by using Ctrl.
To select several slice numbers in a row, highlight the first slice number, hold down the Shift
key, and choose the last number in the row required. All slice numbers in between are
highlighted. You can deselect a highlighted selection by pressing the Ctrl key while clicking
the mouse over the layer.
Hint I, J Slicing can be used to display fence diagrams.
Commit the new parameters by clicking on Apply after every change in the window.

Property model decimation
When working with large models, it can sometimes take a long time to display multiple IJK
slices through a property model. To speed up the display it is useful to define a coarser view of
the property model in the configuration file. You can do this as shown below, by specifying
alternative levels of detail to be made available to you in the Object Appearance panel. The
example below defines two display levels when viewing IJ slices and three additional levels
when viewing K layers. When rows, columns and layers are grouped, the geometry of the
coarsened cell is taken from the corners of the grouped cells. The property displayed is the
property of the first cell, not an average. You can define as many display levels as you wish.
SUBSECT PROPERTY_MODEL_VISUALISATION_COARSENING
-- Coarsening for property model visualisation.
-- Set up level of detail options for coarsening
-- property model visualisation (options appear
-- in object appearance panel).
-- Default IJ row coarsening:

DEFAULT_NUMBER_OF_IJ_ROWS_TO_VIEW_AS_SINGLE_ROW 1
-- Possible IJ row coarsening options:

NUMBER_OF_IJ_ROWS_TO_VIEW_AS_SINGLE_ROW_OPTION1 5
-- Default K layer coarsening:

DEFAULT_NUMBER_OF_K_LAYERS_TO_VIEW_AS_SINGLE_LAYER 1
-- Possible K layer coarsening options:

NUMBER_OF_K_LAYERS_TO_VIEW_AS_SINGLE_LAYER_OPTION1 2

Creating property maps
Introduction
The Property Maps folder allows you to build up a property model from 2D property maps by
assigning maps to each unit constructed in the structural modeling process. A property is fully
defined on the property model when a map of a given type has been assigned to each unit in the
model.
This folder is intended for use only with map based models, not imported 3D geological files.
The Property Maps folder is divided into two sections.
Unit tree
The Unit Tree shows the units and properties for the model selected in the Current Model box
above. Units are listed in depositional order (as constructed in the structural framework, see
"Structural Framework" on page 175). Each unit may have one or more property maps
associated with it. The property maps are generally imported into the main window surfaces
tree, although they can be created using the Property Editor.
Property map tree

The Property Map Tree shows all property maps in the system that have not been assigned to
a unit.
Dragging and dropping property maps

Any unassigned property map can be assigned by dragging it on to the Unit Tree and dropping
it on any unit. Similarly, a property map can be dragged from one unit to another or can be
unassigned by dragging it from the Unit Tree to the Property Map Tree.
Note In map based models, properties are only available to be visualized, edited or upscaled
when they are defined in all units of the model. FloGrid supports only one property of
each type per unit. If you attempt to assign two property maps of the same type to the
same unit, only the first one is available.

Creating property maps
Property data model
Introduction
The property data model inherits its structural properties from the structural framework to which
it then adds properties. These properties are in the form of (geological scale) grids known as
block unit grids that have the following constraints:
• Each block unit may have one or more block unit grids
• Each block unit grid may have one or more attached property arrays
• A property array may be attached to more than one block unit grid.
(For example, in the case of a map-based property the property is attached to all the
map block unit grids in a single unit.)
When a particular property type is represented in the block unit grid of every block unit the
whole model is said to bear this property. In this situation the property can be:
• viewed using the Property Model Viewer
• upscaled using the Upscaler
• edited using the Property Model Editor.
When two or more properties of the same type exist with the same block unit the first assigned
is taken as the representative property.
Property scenarios
A property scenario is a grouping of block unit properties with the following characteristics.
A scenario does not have to cover the whole property model. This means, for example, that a
scenario may contain properties for a subset of all the units in the model. However, all properties
in a scenario must cover the same set of block units.
A scenario contains at most one property of any given type. This means, for example, that a
scenario named version 1 properties might contain porosity and permeability and
another scenario named version 2 properties might contain only porosity. However,
the version 1 properties scenario cannot contain two versions of porosity.
Note In 2001A the following additional restriction applies: any two properties in the same
scenario must use the same block unit grid structures.
How property scenarios are created

There are three ways that scenarios are created.
1 Some RESCUE model writers (notably Property3D) can create scenarios. If they conform
to the restrictions above they will be imported into FloGrid.
2 If a property model has properties which do not belong to any imported scenario then
FloGrid places them in a default scenario called the FloGrid Default Scenario.

Property data model
Note This scenario obeys the additional rule that all its properties must cover the whole
model. This is compatible with earlier FloGrid releases.
3 FloGrid creates a scenario when it makes simulation model properties available on the
geological model. This is called "back posting" or "downscaling" and is accessible from the
Structured Gridder panel, using the File | Create Fine Model View menu option. The
scenario is given the same name as the simulation model. Note that, if two versions of the
same property type exist on a simulation model, only the first is placed in the scenario.
The current modeling scenario

Many FloGrid operations now depend on your choice of scenario. The most important example
is the choice of which scenarios' properties to upscale into the simulation grid. In many places,
on the user interface, FloGrid presents you with a drop-down menu to choose the scenario for
each operation.
However, there are cases of scenario-dependent operations where you are not given the choice
of scenario. The most significant example is when you are running command files generated
from earlier versions of FloGrid. Other examples include upgridding and the choice of target
scenario to determine the backposting block unit grids. In these cases FloGrid uses the current
modeling scenario as the users choice.
You can set the current modeling scenario from the Scenarios menu in the Property Model
panel. The current modeling scenario defaults to the FloGrid default scenario, if it exists.

Property data model
Property population
Chapter 12
Introduction
Property Population provides the ability to populate 3D structural models, using varying kind
of data that has been loaded in FloGrid. It provides integrated data analysis functions to
investigate input data and output property grids.
You can open the Property Population dialog using Tools | Property Population Models...
or from the workflow window Property Modeling | Property Population.
Property Population dialog

The Property Population dialog allows you to select the population focus, specify the input
data for the property grids, select the algorithms with which they are processed and specify the
output masks to control the population output. It allows saving of all the population parameters
in a population parameter set either for immediate population or population in batch.
This chapter contains information on:
• Creating, loading and deleting parameter sets: see "File menu" on page 233.
• Collecting parameters for generating a property grid: see "Population Parameter Set" on
page 234.
• Selecting primary data for property generation: see "Primary Input" on page 236.
• Lumping data to match the layers specified in your correlation scheme: see "Lumping" on
page 240.
• Selecting secondary data for property generation: see "Secondary Input" on page 242.
• Selecting the algorithm with which you wish to process your data: see "Algorithm" on
page 243.
• Specifying the number of realizations to generate: see "Realizations" on page 262.
• Specifying the distributions to honor when populating a grid: see "Proportions (Global,
Vertical and Secondary Data Weights)" on page 264.
FloGrid User Guide Property population 231

Introduction
• Adjusting the range and quantity of data to select for property population: see "Search" on
page 266.
• Specifying the parameters for the populated output grids: see "Output Mask" on page 268.
• Overwriting specified values for the current population grid: see "Current Property Grid"
on page 270.
• Creating and specifying parameters: see "Creating and specifying data" on page 272.
• Creating and using indicator classes: see "Indicator Classification" on page 284.
• Analyzing property population data: see "Property Population Data Analysis" on page 288.
Hint For explanations of the terms used, see "Property Population Glossary" on page 813.
232 Property population FloGrid User Guide

Introduction
File menu
Introduction
This first group of menu items is for Population Parameter Sets. The Population
Parameter Set is a collection of all the parameters chosen for property grid generation. See
"Population Parameter Set" on page 234 for more details.
This section contains the following options:
• "Create Parameter Set..." on page 280.
• "Load Parameter Set..." on page 280.
• "Save Parameter Set" on page 233.
• "Save Parameter Set As..." on page 233.
• Delete Parameter Set...: see "Delete parameter set..." on page 280
• Create Property Grid: see "Create..." on page 278.
• "Setting the property population focus" on page 233
Save Parameter Set

Saves the property population parameter set. In case the name of the set has not been specified,
a dialog opens to query for the name.
Note Only parameter sets that have not been used for populating a grid and, therefore, are
allowed to be edited, can be saved.
Save Parameter Set As...

Saves the property population parameter set using a different name than the one currently being
used.
Setting the property population focus

There are two ways to set the property population focus. You can either start by selecting the
model, the property grid, the property type and the units for population or by loading an existing
population parameter set.

File menu
Population Parameter Set
Introduction
The Population Parameter Set is a collection of all the parameters chosen for property grid
generation. It includes the population focus, that is, the property model, the units, the property
grid name and the property type, the input data, the algorithm to apply to the input data, the
search options for the algorithm, and the output masks to control the output of the properties
into the property grid.
To preserve the property grid’s population history, the Population Parameter Set is locked,
that is, made read-only once the parameter set has been used for the grid property population.
No further edits are allowed to this parameter set. To make edits or a variation of this parameter
set, a new parameter set can be created as its clone and edited. See "Create Parameter Set..." on
page 280.
The text field displays the name of the current Property Population Parameter Set. This text
is read only.
• "Create Parameter Set..." on page 280.
• "Load Parameter Set..." on page 280.
• "Coordinate Correlation" on page 234.
• "Model" on page 235.
• "Property Grid" on page 235.
• "Type" on page 235.
• "Create..." on page 278.
• "Unit..." on page 279.
• "Histogram button" on page 235.
• "Delete parameter set..." on page 280.
Coordinate Correlation
Specifies the type of spatial correlation to use in property population. Computed distances
between data supports and output locations vary depending on this selection, leading to different
data weights and thus different property distributions. The coordinate correlation types and
appropriate uses are described below.
By IJK
Data weights are computed based on a function of the structured grids IJK geometry. This
correlation option is the default, and is appropriate for use with rectangular structured grids.
This correlation is also appropriate for non-rectangular grids, when it is desired to have the
property distribution follow a specified non-linear direction (such as properties distributed in a
channel complex).

By XYK
Data weights are computed based on a function of the horizontal X and Y coordinates, along
with the vertical K layering scheme of the structured grid. This correlation is appropriate for use
when a rectangular or corner-point structured grid is created, and the vertical K layering scheme
used in the structured grid corresponds to a depositional environment.
By XYZ
Data weights are computed based on a function of the model’s geographic coordinates, X, Y and
Z. This option is useful only in certain special cases, when a layer-cake or flat property
distribution is desired and nothing is known about the depositional environment. In general, one
should use the XYK or IJK correlation option.
Model
Sets the model in which the property grids are generated. By default, the current model is shown
as the selected model.
Property Grid
Select an existing property grid to be populated. You can create a new property grid by clicking
on the Create... button after the Property Type display field.
Type
Displays the property type of the selected property grid. This text is read only.
Histogram button
Opens the Property Population Data Analysis tool and displays the histogram for the output
property grid. In case the output grid has multiple realizations, the histogram is displayed for
the first realization.
See "Property Population Data Analysis" on page 288.

Primary Input
You can select the primary data and threshold it for property generation in this tab.
• "Primary Data" on page 236.
• "Borehole/Surface Intersection button" on page 236.
• "Resampling" on page 237.
• "Property Type..." on page 280.
• "Select..." on page 237.
• "Load..." on page 238
• Histogram button .
This button opens the Property Population Data Analysis tool.

• "Threshold" on page 238.
Primary Data
Four types of primary data are supported for property generation. These can be selected from
the drop-down menu. The types of data are:
• Well Logs
• Property Maps
• 3D Property Grids
• Scatter Set.
Borehole/Surface Intersection button

If Well Logs are selected as primary data, the first operation to be performed is borehole surface
intersection calculation. When you click on this button, it automatically computes the
intersections between each of the wells, or well section (in case of multi-section well) you have
loaded, and the start and end depths of all surfaces encountered by the well/well section. It then
opens the Borehole/Surface Intersections panel. This presents the computed results about the
intersections of the wells/well sections with the surfaces and also allows you to redo the
borehole surface intersection calculation.
See "Borehole/Surface Intersections" on page 277.

Primary Input
Resampling
The Resampling option menus in the primary, discriminator thresholding and secondary data
frames specify the interpolation algorithm you can use on the data. For well log data, this
resampling occurs when loading the data; log data gets implicitly loaded at a sampling rate of
0.5 feet. For other data types, resampling occurs when using constant assignment for primary
data or when co-locating the secondary or discriminator data to either the primary data or the
output data locations.
The resampling operations supported for the various data types are:
Well Logs
• Continuous
• Discrete
• Upper Gate
• Lower Gate.
For well log data, you can load explicitly sampled logs that represent interpreted facies types.
You select the Upper Gate option when you want the data sample to apply to all points beneath
the data sample, until the next data sample point. You select the Lower Gate option when you
want a data sample to apply to all data locations above the data location.
All other types

Continuous
You choose the Continuous resampling option when the property type represents a continuous
quantity. Linear, bilinear or trilinear resampling is performed.
Discrete
You choose the Discrete resampling option when the property type represents a discrete (or
integer) property. Closest-point resampling is performed.
Select...
Opens the data selector for the data type selected. Once the selection is made, it is displayed in
the text area opposite this button. The different kind of data selectors for the data types are:
Well Logs
See "Well Logs Data Selector" on page 281.
Property Maps
"2D Property Maps Data Selector" on page 281.
3D Property Grids
"3D Property Grid Selector" on page 282.

Primary Input
Scatter Set
"Scatter Sets Data Selector" on page 282.
Load...
Loads the data for the selected data type.
If the data type selected is Well Logs, synthetic well logs are created with the loaded data. These
well log names are appended with the string [Pop_Primary].
Threshold
The Threshold portion of the Input tab allows you to limit the data you use in modeling. You
can:
• Set upper and lower thresholds outside of which values are discarded.
• Set upper and lower thresholds inside of which values are discarded (inverse thresholding).
There are a variety of situations in which you may find thresholding your data useful. Perhaps
the input data exceeds the physical bounds of the property type, as when you discover (probably
from the histogram) that you have water saturation values that are <0. Or you may find
thresholding useful in identifying and eliminating out-lying or otherwise errant values. You may
combine the two thresholding methods to grid “mixed” lithologies.
There are two methods of thresholding:
Basic
You simply set a maximum and a minimum for values to include or (if you are doing inverse
thresholding) to exclude.
Setting a basic threshold

• From the Type radio box, select Basic (default).
• Toggle Inverse Thresholding ON or OFF (default).
• ON: Values between the Minimum and Maximum are excluded from the data.
• OFF: Values less than the Minimum and greater than the Maximum are excluded from the
data.
• Set a Minimum value using the parameter tool.
• Set a Maximum value using the parameter tool.
• To initiate thresholding, click on Threshold.
The “Histogram” button, , becomes active.
• To view a histogram of the thresholded data, click on .
Hint If your input data is well logs, go on to the discussion of the Lump tab. Otherwise, go
to Algorithm .

Primary Input
Advanced
You can use an indicator classification to limit the data values used. This classification can be
applied either to the original data selected or to a second set of user-selected data that is used to
“mask” the original data selected.
Setting an advanced threshold

• From the Type radio box, select Advanced.
The Basic thresholding parameters are replaced by two parameter input areas:
Discriminator (OFF by default)
[Indicator classification] (ON by default).
• Toggle Inverse Thresholding ON or OFF (default).
ON: Values represented by the advanced data are excluded from the data.
OFF: Values corresponding to those of the advanced data become the data limits.
• Click on Classification.
The Indicator Classification Selector opens.
• When you have selected or created and selected an indicator classification, click on
Previous Topic to return to this discussion. Classes is now active.
• Click on Classes.
The Indicator Classes Selector opens.
• Select one or more classes (that represent user-defined data ranges) to use to limit the values
used.
If you are not going to establish a Discriminator set of data, these classes function as
masks to include data or (if Inverse Threshold is toggled ON) to exclude data.
If you are going to establish a Discriminator set of data, these classes function as
selectors for data in the Discriminator set to be used to mask the input data.
• Click on Threshold to threshold the original input data directly with the Indicator classes
selected.
Or
• Go to Discriminator.
Selecting a data set for masking
Note In establishing a Discriminator data set, you must select the same Source and
Property as you selected for the original data.
• Toggle Discriminator ON.

• Select Source.
• Set Resampling.
• Select Property Type.
• Select specific data.
• Load the selected data.
• Click on Threshold.

Primary Input
Lumping
Introduction
Lumps your data to match the layers you specified in the Correlation Scheme. That is, you are
able to manipulate data value ranges to come up with a single value for each of the physical
divisions of the unit for which you are generating a model. You are given a choice of algorithms
by which this set of values is calculated.
The values are those of cells through which a borehole passes as we are using data from well
logs.
For example, assume that a borehole that passes through a cell contains a well log with property
values of 1, 2 and 3 respectively. If you chose the Arithmetic Averaging algorithm, the node in
the cell is assigned the value ( 1 + 2 + 3 ) ⁄ 3 , or 2 .
The result is a series of depth-ordered samples or composites, positioned along the borehole
path, each of which commonly spans a single chronostratigraphic layer. The resampling is
controlled by the resolution (number of layers) defined in the correlation scheme.
• "Input Data" on page 240.
• "Method" on page 240.
• "Lump" on page 241.
• Histogram button .
Opens the Property Population Data Analysis tool.

Input Data
At Data Used, select either Original or (if active) Thresholded.
Original
The lumping algorithm is applied to your original data as loaded at the Input tab. This option is
always active.
Thresholded
The lumping algorithm is applied to your data as it exists after thresholding. This option is active
only if you have thresholded your original data.
Method
Select the algorithm you wish to use.

Lumping
Only the following methods are normally used for lumping. The others are useful for quality
control.
Mode
Suitable for discrete properties such as facies code, rock type, and lithology type.
Median
Better than Arithmetic Average if the distribution is skewed. Also used for discrete properties
when there is an odd number of data points.
Arithmetic Average
Suitable for properties that are additive variables, such as porosity, net-to-gross, and water
saturation.
Harmonic Average
Produces the effective vertical permeability if the reservoir is layered with a constant
permeability in each layer. Accepts only values > 0 . Threshold data to remove values ≤ 0 .
Geometric Average
Typically used for properties that are log-normally distributed, such as permeability. Accepts
only values > 0 . Threshold data to remove values ≤ 0 .
Power Average
Normally used for permeability. Requires you to supply a value for ω power. Power average
results are the same as Arithmetic Average when power=1 and the same as Harmonic
Average when power=−1.
Random
Produces a randomly selected data value from the data samples in the property grid cell.
Minimum
Produces the minimum data value located in the property grid cell.
Maximum
Produces the maximum data value located in the property grid cell.
Lump
Initiates lumping.

Lumping
Secondary Input
You can select the secondary data for property generation in this tab.
• "Secondary Data" on page 242.
• "Resampling" on page 237.
• "Property Type..." on page 280.
• "Select..." on page 237.
• Load and Collocate... button
Loads the data for the selected data type by collocating against the input data source
selected in the Algorithm folder. See "Algorithm" on page 243.
• Histogram button
Opens the Property Population Data Analysis tool. See "Property Population Data
Analysis" on page 288.
• "Cross Plot button" on page 242.
Secondary Data
The following data type are supported for property generation. These can be selected from the
drop-down menu. The types of data are:
• Property Maps
• 3D Property Grids
Cross Plot button

Opens the Property Population Data Analysis tool. The data source (either Original,
Thresholded or Lumped) selected in the Algorithm tab is the primary data for the cross plot.

Secondary Input
Algorithm
Introduction
Algorithms available for selection in the Algorithm tab are based on the property type (discrete
or continuous) of the output property grid and on the coordinate correlation system selected, as
shown in this table:
Table 12.1 Algorithms available for selection in the algorithm tab
Coordinate
Algorithm Correlation Continuous Discrete
System
Distance to Nearest Neighbor IJK, XYK, XYZ YES YES
Constant Assignment IJK, XYK, XYZ YES YES
Nearest Neighbor IJK, XYK, XYZ YES YES
Inverse Distance IJK, XYK, XYZ YES NO
Ordinary Kriging IJK, XYK, XYZ YES NO
Simple Kriging IJK, XYK, XYZ YES NO
Collocated Cokriging IJK, XYK, XYZ YES NO
Sequential Indicator Simulation IJK NO YES
Sequential Gaussian Simulation IJK YES NO
Sequential Gaussian Cosimulation IJK YES NO
Truncated Gaussian Simulation IJK NO YES
Fluvial Object Simulation IJK NO YES
Either the Original, Thresholded or Lumped data can be selected as the input data for
population.
• "Segregate Data By" on page 244.
• "Distance to nearest neighbor parameters" on page 244.
• "Constant assignment parameters" on page 245.
• "Nearest neighbor" on page 245.
• "Inverse distance parameters" on page 246.
• "Ordinary Kriging parameters" on page 247.
• "Simple Kriging Parameters" on page 249.
• "Collocated Cokriging Parameters" on page 250.
• "Sequential Indicator Simulation Parameters" on page 251.
• "Sequential Gaussian Simulation Parameters" on page 252.
• "Sequential Gaussian Co-simulation Parameters" on page 253.
• "Truncated Gaussian Simulation parameters" on page 255

Algorithm
• "Fluvial Object Simulation parameters" on page 256.
• "Algorithm decision tree" on page 259.
Segregate Data By
Specifies how the input data is to be shared in the population run. Data can be used across all
units, blocks and block units in the structured grid, or can be used only in the particular
structural volume it is located in. Data segregation is an option for all the non-simulation
algorithms. For the simulation algorithms, this option is not available; the default is to share data
across structural boundaries for the simulation algorithms. The following options exist for data
segregation.
None
No data segregation is done. This is the default. The effect is that the data will be shared across
all structural boundaries and used everywhere population is desired.
Block Unit
Data is segregated by block unit when populating. This means that data will only be used to
populate grid cells located in the same block unit as the data sample.
Unit
Data is segregated by unit when populating. This means that data is only used to populate grid
cells located in the same unit as the data sample.
Block
Data is segregated by block when populating. This means that data is only used to populate grid
cells located in the same block as the data sample.
Distance to nearest neighbor parameters

Criteria
• You need to quantify the distance from each grid cell to a single data source or a set of
nearest data locations.
• The actual data values associated with the input data are not important.
Notes
• The distance between the nearest input data sample and the grid node to be populated is
calculated.
Parameters
• No parameters are required for this algorithm.

Algorithm
Limitations
This algorithm:
• is rarely appropriate in generating final rock or fluid property grids.
• may be useful when a discriminator grid is required to restrict processing. For example, you
might limit the computation of reserves to a user-specified drainage radius around a
borehole.
• may be useful in generating an intermediate grid used in obtaining a final grid.
Constant assignment parameters

Criteria
• A single constant value is sufficient to describe the desired property values for all property
grid cells involved.
• Data from well logs, scatter sets or 2D property maps needs to be assigned to a 3D property
grid.
Notes
• The Constant Assignment algorithm creates a grid containing a single value for each cell,
if a constant value is specified. Selective population criteria may be set to control which
property grid cells get the
• When Constant Assignment is used to assign values to a 3D grid containing two or more
layers using 2D data, the same value is assigned to each cell at any given areal position (for
example, [I, J]-location). This value, which is evaluated from the input 2D grid, is used for
all cell layers at any (X, Y)-location. The direct assignment method is useful in loading 2D
grid of property distributions so that these values may be visualized in 3D canvas in the
context of the Structural Framework.
• For 3D data, the data is assigned to the appropriate property grid cell.
Parameters
Value to be assigned to the grid.
Nearest neighbor
Criteria
• You are using input data that represents a discrete property.
• A simple polygonal region of influence surrounding each data point is sufficient for your
purposes.
• You are using this algorithm as a preliminary screen of data values.

Algorithm
Notes
• The Nearest Neighbor algorithm creates a grid containing a single value for each cell.
This value is obtained from the single data point nearest to the cell to be populated.
Nearest Neighbor is useful as a quality control tool in reviewing data values. It is rarely
used to produce final distributions of rock or fluid properties.
• This algorithm is traditionally used with discrete data, but may be useful in representing
data density when clustered data are present.
Parameters
• No parameters are required for this algorithm.
Limitations
This algorithm:
• produces simplistic results based only on the input data values
• exhibits polygonal regions surrounding each input data point. Within each polygonal
region, a constant value is present that is equal to the input data point’s value.
• performs no interpolation. As a result, the output grid contains only values present in the
input data.
Inverse distance parameters

Criteria
• Data density is sufficient to allow interpolation between data locations. That is, you are
willing to correlate the property values between neighboring data locations.
• A relatively simple distribution of interpolated property values is adequate.
• The input data exhibit little or no clustering with respect to the block unit volumes being
populated.
• The correlation of data values as a function of distance is fairly simplistic. That is, no short-
range phenomenon is present that would impact the correlation of data values at distances
less than the minimum data spacing.
Notes
• The Inverse Distance algorithm creates a grid containing a single value for each cell. Each
value represents a weighted average of the neighboring data samples. The weight for each
neighboring data sample is derived from a simple inverse distance formula.
• The closer a sample to the node to be populated, the more weight its value is given. The
further a sample from the node to be populated, the less weight its value is given. The
weight is calculated as the inverse of the distance from the node raised to a user-specified
power.

Algorithm
Parameters
Power
The power parameter is used in the computation of data sample weights. At a power near a value
of 0, all weights are nearly equal, and the result is a simple arithmetic average of all values
within the search neighborhood of a given grid cell.
The greater the power, the greater the variation in weighting among samples.
Examples:
• 1 = inverse distance
• 2 = the inverse square of the distance
• 3 = the inverse cube of the distance, etc...
Tolerance
The tolerance parameter lets you ensure that when a data point lies within a close proximity to
the cell to be estimated, the cell is assigned the value from the nearest data point. In effect, this
parameter indicates the minimum distance from grid cell to neighboring data within which a
simple nearest- neighbor approach is used instead of a weighted average.
Limitations
This algorithm:
• interpolates between neighboring data samples
• is rarely appropriate for use with discrete properties
• tends to a produce values that are global means of neighboring data at grid locations beyond
the extent of available data.
Ordinary Kriging parameters

Criteria
• Data density is sufficient to allow interpolation between data locations. That is, you are
unwilling to correlate the property values between neighboring data locations.
• The input data may exhibit clustering with respect to the block unit volumes being
populated.
• A trend is present in the input data and must be modeled independently from the data
values, or a trend model is available and you wish to incorporate this trend into a property
grid representation.
• A correlation of data values as a function of distance is present. In other words, a short
range phenomenon is present that impacts the correlation of data values at distances less
than the minimum data spacing.

Algorithm
Notes
• The Ordinary Kriging algorithm creates a grid containing a single value for each cell. This
algorithm assumes that the local mean is constant but unknown in the search window. It
allows the local mean to vary in each search window. Ordinary Kriging uses a local mean,
while simple kriging uses a universal mean. Thus Ordinary Kriging has lower estimated
values in low-value areas and higher estimated values in high-value areas.
• A single primary source of data serves as input to this algorithm. As with any kriging-based
algorithm, a corresponding variogram is also required. This variogram quantifies the spatial
correlation associated with the primary input data.
• Ordinary Kriging also supports the quantitative estimation of trend, a geostatistical
technique often referred to as trend kriging. You may either perform the kriging to take a
trend into account or compute the trend alone for subsequent use.
• If a trend has been identified and computed, you also can use this secondary data during the
kriging computation. This is commonly known as kriging with external drift.
Parameters
If you select this algorithm, the following additional parameters appear on the Algorithm tab,
requiring you to provide additional input:
Ordinary toggle
If you select this toggle, Ordinary Kriging is done, with no trend or external drift.
Trend toggle
If you select this toggle, Ordinary Kriging with Trend is done.
The Trend parameters enable you to specify up to 9 trend terms. If the Krige with Trend toggle
is ON, the resulting property grid contains the computed trend; if this toggle is OFF, the
estimation results are written out to the property grid.
With Secondary Drift toggle

If you select this toggle, Ordinary Kriging with External Drift is done. Secondary data is
required for this option.
Variograms
See "Select Variogram Model" on page 262.
Save Kriging Variance Grid

Writes the kriging variance to a Variance property grid, with a name <name>_Variance, where
<name> is the output property grid name.
Limitations
• As a kriging process, this algorithm sometimes assigns negative weights to the input data
within the search window screen effect. The resulting estimated value may be slightly
outside the range expected in light of the input values (for example, negative porosity). The
populations algorithms do not attempt to correct for unrealistic estimated values. You are
expected to review the grid and use the appropriate grid operations to influence the output
grid.

Algorithm
Simple Kriging Parameters
Criteria
• Data density is sufficient to allow interpolation between data locations. In other words, you
are unwilling to correlate the property values between neighboring data locations.
populated.
• A global mean value is either known or should be honored.
Notes
• The Simple Kriging algorithm creates a grid containing a single value for each cell. The
kriging system of equations relates the covariance among all the samples (obtained from
the variogram), the covariance between each sample to the location to be estimated, and the
unknown weights.
• A single primary source of data along with a global mean serves as input to this algorithm.
As with any kriging-based algorithm, a corresponding variogram is also required. This
variogram quantifies the spatial correlation associated with the primary input data.
• As the location to be estimated becomes farther away, the surrounding data points carry less
information; hence the weights decrease. Consequently, the weight on the mean increases
and the estimate becomes closer to the mean.
Parameters
Mean
This is by default the data’s arithmetic average. You may modify this to specify a different
global mean to use.
Variograms

Limitations
This algorithm:

Algorithm
• does not adapt to local trends in the data since it relies on the mean value, assumed known
and constant throughout the area. Consequently, Simple Kriging is rarely used for direct
estimation.
• as a kriging process, sometimes assigns negative weights to the input data within the
Search Window (screen effect). The resulting estimated value may be slightly outside the
range expected in light of the input values (for example, negative porosity). The
grid.
Collocated Cokriging Parameters

Criteria
• Data density is not sufficient to allow interpolation between data locations. In other words,
you are unwilling to correlate the property values between neighboring data locations.
populated.
• A correlated secondary attribute representation is available. This representation is more
densely sampled than the primary input data and reflects the variation present in the
distribution of data values between the primary data locations.
Notes
• The Collocated Cokriging algorithm creates a grid containing a single value for each cell.
This algorithm requires both a primary and secondary source of input data. As with all other
kriging-based algorithms, a variogram model is also required. However, a variogram model
is only required for the primary input data. No variogram model associated with the
secondary data is used.
Parameters
Correlation Coefficient
This is by default the correlation coefficient between primary and secondary data. A -1 signifies
an inverse relationship. A +1 represents a direct relationship. A 0 indicates no relationship
between primary and secondary data.
Variograms


Algorithm
Limitations
• As a kriging process, this algorithm sometimes assigns negative weights to the input data
within the search window (screen effect). The resulting estimated value may be slightly
outside the range expected in light of the input values (for example, negative porosity). The
grid.
Sequential Indicator Simulation Parameters

Criteria
• No interpolation is desired or required (that is, you are using a discrete property)
• In order to quantify uncertainty, multiple realizations are required that reflect the range of
equi-probable property value distributions.
Notes
• The Sequential Indicator Simulation algorithm may be used to create grids from discrete
sets of data values (frequently referred to as “indicators”). This mapping of input values to
indicators allows you to perform spatial data analysis (variogram computation and
modeling) on such data values.
• All variogram analysis must be conducted using the indicator semi-variogram calculation.
This requires selection of a single category or indicator class for analysis. All values
corresponding to the selected class are treated as “true” and temporarily assigned a value
of 1. All other values are treated as “false” and temporarily assigned a value of 0. The actual
variogram computation is performed on the 1/0 values rather than the original data values.
(See "Guidelines for creating indicator classes" on page 287.)
Note Gaussian variogram models are not available for use in Indicator Simulation.
You have a choice of two versions of Indicator Simulation:

• In the Full IK Function, each indicator class has its own variogram that is used in
computation. This approach addresses the situation in which differences exist in spatial
correlation (trend) among the indicator classes.
• In the Median IK Function, a single class is selected for variogram modeling. This median
indicator controls which data values are assigned a true-state value of 1 and which are
considered false and assigned a value of 0. This approach can be useful when no clear
trending emerges from the data; that is, all data values being simulated share the same
spatial correlation model (variogram). If this is not the case, then you must exclude the data
that exhibit uncommon behavior through the use of some form of thresholding or use Full
IK Function.

Algorithm
Parameters
If you select the Sequential Indicator Simulation algorithm, the following additional
parameters appear on the Algorithm tab, requiring you to provide additional input:
Indicator Classification
"Guidelines for creating indicator classes" on page 287.
Realizations
"Realizations" on page 262.
Indicator Kriging Type

This is either Full IK or Median IK.
Indicator Variograms
"Indicator Variogram Selection" on page 262.
Proportions
"Proportions (Global, Vertical and Secondary Data Weights)" on page 264.
Simulated Nodes to Use

"Simulated Nodes to Use" on page 262.
Limitations
This algorithm:
• is capable of reproducing proportions based on either global estimates, vertical proportions,
or secondary data proportions. This facilitates the generation of discrete grid
representations in which the relative percentage of each class of values can be user-
controlled.
• can be controlled by selecting secondary input data, such as hand-drawn interpretation
incorporated into a grid.
• computes more slowly when you use Full IK Function.
Sequential Gaussian Simulation Parameters

Criteria
populated.

Algorithm
Notes
• The Sequential Gaussian Simulation (SGS) algorithm may be used to create a grid
containing multiple values at each cell. It supports a single source of input data. A
variogram model quantifying the spatial correlation associated with the input data must
also be supplied.
• The Sequential Gaussian Simulation algorithm assumes that the input data are normally
distributed. To ensure this, a transformation is automatically applied to the input data that
is used for simulation. A histogram allows you to verify that the transformed data meet this
requirement.
• All variogram analysis and computations are performed on the transformed data. Only after
grid values have been simulated are the values back-transformed to reflect the original
distribution. Many implementations of Sequential Gaussian Simulation require you to
manually conduct such transformations. This is built in to the Sequential Gaussian
Simulation algorithm in Property Population.
Unconditional Simulation
If Unconditional Simulation is toggled ON in the input folder, the transformed data is only
used for the back transform as the desired transformation table and not for the actual
calculations. If you do not select input data and transform the data to create a transformation
table, the normal space is scaled using the back transformation minimum and maximum values
to give a distribution within those ranges while maintaining the normal distribution.
Parameters
Realizations
Variograms
"Select Variogram Model" on page 262.

Sequential Gaussian Co-simulation Parameters

Criteria
• Property distribution is not characterized by a constant value, nor can an existing 2D grid
be resampled to provide an adequate representation.

Algorithm
• A correlation of data values as a function of distance is present. In other words, a short-
• A correlated secondary attribute representation is available. This representation is more
densely sampled than the primary input data and reflects the variation present in the
distribution of data values between the primary data locations.
Notes
• The Sequential Gaussian Co-simulation (SGCS) algorithm may be used to create a grid
containing multiple values at each cell. It supports a single source of input data. A
variogram model quantifying the spatial correlation associated with the input data must
also be supplied.
• The Sequential Gaussian Simulation algorithm assumes that the input data are normally
distributed. To ensure this, a transformation is automatically applied to the input data that
is used for simulation. A histogram allows you to verify that the transformed data meet this
requirement. All variogram analysis and computations are performed on the transformed
data. Only after grid values have been simulated are the values back-transformed to reflect
the original distribution. Many implementations of Sequential Gaussian Simulation
require you to manually conduct such transformations. This is built into the Sequential
Gaussian Simulation algorithm in Property Population.
Unconditional Simulation
If Unconditional Simulation is toggled ON in the input folder, the transformed data is only
used for the back transform as the desired transformation table and not for the actual
calculations. If you do not select input data and transform the data to create a transformation
table, the normal space is scaled using the back transformation minimum and maximum values
to give a distribution within those ranges while maintaining the normal distribution.
Parameters
Realizations
Variograms
Simulated Nodes to Use.


Algorithm
Limitations
This algorithm uses Ordinary Kriging in its calculations.
Truncated Gaussian Simulation parameters

Criteria
• Property to be modeled is discrete, such as lithology.
• In order to quantify uncertainty, multiple realizations are required that will reflect the range
of equi-probable property value distributions.
Notes
• The Truncated Gaussian Simulation algorithm may be used to create grids from discrete
sets of data values (frequently referred to as “indicators”). This mapping of input values to
indicators allows you to perform spatial data analysis (variogram computation and
modeling) on such data values.
• All variogram analysis and computation are performed on the transformed data. This is
built in to the Truncated Gaussian Simulation algorithm in Property Population.
Parameters
Realizations
Variograms

Note The indicator classification ranges
Limitations
• The defined facies must be contiguous.

Algorithm
Fluvial Object Simulation parameters
Criteria
• You wish to model fluvial objects (channels, levees, point bars, splays).
• Property to be modeled is discrete, such as lithology.
• Data input comes from well log data.
Notes
• The Fluvial Object Simulation algorithm may be used to model fluvial objects from input
data, embedding them into a background as part of reservoir simulation.
You may model the following objects:
• Background (typically shale)
• Channels or a channel complex
• Levees
• Splays
• Point bars.
• You can control the generation and display of each type of object by setting specific
parameters.
• You may further affect the population output by setting parameters for vertical weights and
for global proportions.
• The Fluvial Object Simulation algorithm also allows the generation of multiple
realizations.
Note You can save a grid containing the IDs of any created objects at the Output tab.
Parameters
If you select the Fluvial Object Simulation algorithm, the following additional frames appear
on the Algorithm tab, requiring you to provide additional input:
Objects to model
"Objects to model" on page 257.
Realizations

Algorithm
Proportions
"Proportions (Global, Vertical and Secondary Data Weights)" on page 264.
Objects to model
You are allowed to select any or all of the objects available for modeling and to assign an
indicator class to each. Once you have chosen the features you wish to use, you may modify
various physical parameters for any feature (except Background) from the Fluvial Object
Simulation parameters dialog.
Note If you are re-gridding a previously-populated grid and toggle Background OFF, newly-
created fluvial objects replace the values of original grid.
You can model either channels or a channel complex--you cannot model both. To select an
object for modeling:
• Toggle the selected feature ON.
Note In the Channels/Complex radio box, toggle ON which of the two you wish to select.
• The Set button next to the feature label becomes active.

• Click on Set.
• The Categories selector dialog opens, listing the available indicator classes in the
selected classification set.
• Click on the category you wish to assign to the selected feature. OK.
• The selected category is displayed in the text box next to the feature label. When the output
grid is populated, the color and values associated with this category are applied to the
feature.
• You may review the categories for the classification set in use by going up to the Indicator
Classification area of the Property Population Manager and clicking on Select. From
the resulting dialog, click on the classification set you are currently using, then on the i
button. The Indicator Classification Editor opens, with the individual classes presented in
spreadsheet form.
Note You cannot make a selection from the Categories Selector dialog box until both the
Indicator Classification Editor and the Indicator Classification Selector are closed.
• Continue with each desired feature, assigning a classification to each.

Each time you open the Categories Selector, any classification previously used in the
current action has been removed from the list. A classification can be assigned to only one
feature in a simulation.
• To clear all current indicator class assignments, click on Clear.
To modify the parameters for modeled features:

• You may modify specific parameters for each feature (except Background) you have
selected by clicking on Parameters and opening the Fluvial Simulation Parameters
dialog box.

Algorithm
This dialog consists of two tabs:
• Channel/Complex
• Others
A tab is active only if you have selected that feature (toggled it ON) in the Algorithm tab of the
Property Population Manager.
Each tab lists a variety of parameters for its feature. These can be modified by using the
Parameter tools associated with them. The parameters and the objects to which they are
applicable are as follows:
Channels/Channel Complex
Note that channels are generated to go only through their assigned facies and to avoid all other
facies. A channel complex, although guided by the assigned facies, does not avoid other facies.
You are therefore required to select the wells through which you wish a channel complex to
pass. To do this, select the well logs for the specific wells of interest in the Input tab. The top
of the channel complex is set to correspond to the top of the highest sand interval (or
corresponding category assigned to the channel complex feature) among the wells you specify.
Other dimensions are manually set.
Note The intersection of a channel complex and the wells depends on well distribution and
on the parameter settings for the channel complex. Therefore a case may arise that does
not permit the intersection of the channel complex with all the selected wells.
Channels
If you are modeling channels, multiple channels are possible. Channels are generated until the
proportion of channel reaches the value set for the channel facies at Global Proportion.
Channel or channel complex

The following list of parameters applies to channels; many of them also apply to a channel
complex. However, if you are modeling a channel complex, you are creating a single (usually
large) object. As a result, proportional settings are irrelevant and appear grayed-out.
Orientation - Average:
Average angle of channel orientation in degrees clockwise from North. Angle drawn from
triangular distribution.
Orientation - Deviation:
Tolerance in degrees from average within which channel orientation can move. The deviation
range defines the range of triangular distribution.
Thickness - Average:
Average thickness of created channel. Value drawn from triangular distribution. Unit depends
on the unit set in your project. Typically meters or feet.
Thickness - Deviation:
Tolerance from average within which channel thickness can vary. The deviation range defines
the range of triangular distribution. Unit same as Thickness - Average.

Algorithm
Width/Thickness - Average:
The average ratio of a channel’s width to its thickness. Value drawn from triangular distribution.
Width/Thickness - Deviation:
Tolerance from average within which Width/Thickness can vary. The deviation range defines
the range of triangular distribution
Amplitude - Average:
Average distance within which a channel can vary from its axis. Unit depends on the unit set in
your project. Typically meters or feet
Wavelength - Average:
Average wavelength if channels were assumed to be perfectly sinusoidal. Unit depends on the
unit set in your project. Typically meters or feet.
Relative width variation:

Tolerance from average within which channel width can vary. Expressed as a ratio to the
average width. For example, a value of 0.3 would allow the width to vary to as much as 30%
wider or 30% narrower than the average channel width.
Levee
Width/Thickness:
The relative height of the levee in relation to channel thickness. A value of 0.3, for example, sets
levee height at 30% that of channel thickness.
Splay
Width/Thickness:
The ratio of a splay’s width to its thickness. Value drawn from triangular distribution.
Point bar
Relative width:
The size of the point bar as a multiple of channel width. If the channel is 50 feet wide at the point
where a point bar is created, for example, and Width is set to 3, the point bar is 150 feet wide.
Algorithm decision tree

The following decision tree can aid in selecting an appropriate algorithm for your data and
purpose.

Algorithm
Figure 12.1 Algorithm Decision Tree
YES
Constant or
Constant Assignment Assignment?
NO
YES
Distance to Nearest Distance?
Neighbor
NO
Discrete
YES property?
NO
Facies Petrophysical
Algorithm Algorithm
Figure 12.2 Facies Property Population
YES
Nearest Neighbor Data Density?
NO
YES
Fluvial Object FluvialObjects?
Simulation
NO
NO
Differing degrees
YES of Anisotropy?
OR
Sequential Indicator Sequential Indicator Truncated Gaussian

Simulation (Full IK) Simulation (Median IK) Simulation

Algorithm
Figure 12.3 Petrophysical Property Population
YES NO
Deterministic?
Estimation Simulation
NO
YES Clustering?
Secondary
Attribute?
Inverse Distance YES NO
Global Mean?
YES NO
Trend/ Sequential Gaussian

Secondary YES CoSimulation
Simple Kriging
attribute?
NO
Ordinary Kriging Sequential Gaussian
(Trend or Drift) Simulation
OR
Ordinary Collocated
Kriging CoKriging

Algorithm
Realizations
Introduction
The Realizations panel specifies how many realizations to simulate.
Note If the number of realizations is greater than 1, property grids are generated with names
of the format <name>_r<num>, where <name> is the output property grid name
specified and <num> is the current realization number.

• "Simulated Nodes to Use" on page 262.
• "Select Variogram Model" on page 262.
• "Indicator Variogram Selection" on page 262.

The Simulated Nodes to Use panel specifies how many previously simulated nodes to use in
the estimation of the current node. The higher this number, the smoother the results.
Select Variogram Model

The Select Variogram Model dialog selects a variogram model to use in property population.
One variogram model can be selected at a time from the list box.
Indicator Variogram Selection

Sequential Indicator Simulation supports both Median IK and Full IK. With Median IK, only
one variogram model is required. With Full IK, one variogram model per indicator class is
required. The Indicator Variogram dialog displays a table of one row for Median IK, where the
indicator class name is the name of the Median IK class selected. The dialog box displays a table
with one row per used indicator class if Full IK is selected.
Select...
Opens the Select Variogram Model selection dialog. The selection applies to the indicator class
currently in focus in the table. See "Select Variogram Model" on page 262.
Variogram
Opens the Variogram Data Analysis tool with the appropriate class and data focus.
Table (Class Name and Variogram Model)

Table displaying Class Name and Variogram Model Name.
• To select a variogram model, click the left mouse button in the Variogram Model cell for
the appropriate class, then click on Select....

Realizations
• To create or view a variogram model, click the left mouse button in the Variogram Model
cell for the appropriate class, then click on .

Realizations
Proportions (Global, Vertical and Secondary Data
Weights)
Introduction
This area provides facilities for you to specify distributions to honor when populating using
Sequential Indicator Simulation or Fluvial Object Simulation. By default, global proportions are
honored. You may choose to honor vertical and/or secondary data weights (for Sequential
Indicator Simulation) proportions as well. If the vertical proportions or secondary data weights
toggle is toggled on, the program attempts to honor the global, using the vertical proportions
and/or secondary data weights to specify trends in the results.
• "Global Proportions" on page 264.
• "Vertical Proportions" on page 264.
• "Secondary Data Weights" on page 265.
Global Proportions
The Global Proportions dialog provides facilities to modify the global proportions for each
selected indicator class to honor. By default, the proportions computed from the primary input
data are displayed. To change the global proportions, type in the value desired into the
appropriate grid cell next to the indicator class name.
Note When property population is done in Sequential Indicator Simulation, normalization

occurs to ensure the global proportions sum to 1.0. In Fluvial Object Simulation, no
normalization occurs; the result honors the total for the proportions of the fluvial
objects, with the remaining proportion set as background. If the sum of proportions in
Fluvial Object Simulation is greater than 0.9, the resulting proportions are reduced
by an appropriate amount.
Set Default
Sets the global proportions to the calculated defaults, based on the primary input data.
Vertical Proportions
When this toggle is on, the program attempts to honor vertical proportions distribution from the
primary data, while maintaining the global proportions specified in the Global Proportions
dialog.

Proportions (Global, Vertical and Secondary Data Weights)
Secondary Data Weights
The Secondary Data Weights dialog is used in Sequential Indicator Simulation by using the
secondary input data to guide the results. If the toggle is on, the program uses the resulting
transformed secondary data to guide the trends in X and Y direction, while maintaining the
global proportions specified in the Global Proportions dialog. This functionality takes the
secondary input data and transforms the data into zones; one can think of them as pay or non-
pay zones.
Use Secondary Data Weights

Toggle whether to use secondary data weights (on) or not (off).
Note To use this option in Sequential Indicator Simulation, secondary input data must first
be loaded.
Classes...
Indicator class selector. The selected class(es) represent similar classes. The data weights get
divided into two zones, then subdivided into individual classes, based on the secondary input
data. This is a multi-select dialog. See "Selecting classes" on page 287.
Crossplot
Displays a crossplot of the secondary input data versus the data weights proportions in the
selected class(es).

Proportions (Global, Vertical and Secondary Data Weights)
Search
Introduction
The Search folder contains parameter settings to adjust the range and quantity of data to select
for property population. Under normal circumstances, you should not need to adjust these
parameters; reasonable defaults exist to provide decent results. You can modify these
parameters given special cases, however.
• "Algorithm" on page 266.
• "Search Parameters" on page 267.
• "Sector Search" on page 267.
Algorithm
Property Population allows you to choose from among three search algorithms. They differ in
how the search window is explored during the search.
Superblock
This approach speeds up the search and selection process. In it, as a part of pre-processing the
application superimposes a grid of blocks over the grid nodes that approximate the search
window as you define it. Each “superblock” is assigned an ID and each value within the
superblock is associated with that ID. The data is in effect “batched” before the search and
populating begin.
During the population process the data is accessed in batches and the search conditions and
population algorithm applied to each batch, rather than to every node.
This algorithm is especially useful when your input data is dense but not uniformly distributed,
as, for example, when it consists of numerous well logs.
Spiral
In this approach, the search spirals out around the node to be estimated accumulating values
from data points it encounters until it reaches the maximum specified in the search parameters.
If the search reaches the boundaries of the current Search window without encountering the
minimum number of samples specified in the search parameters, it assigns a null value to the
node.
This algorithm is especially useful when your input data tends to be uniformly distributed in a
grid pattern.
Sector
In this approach, you are able to take into account redundancy of nearby samples. The Search
window is divided into a user-specified number of sectors. The search in each sector is halted
when it has encountered the maximum number of data points specified in the search parameters.

Search
Search Parameters
Min. Samples
Min. Samples represents the minimum number of data samples to use in property estimation.
If the search algorithm finds fewer data samples, no estimation is done in this cell.
Max. Samples
Max. Samples represents the maximum number of data samples to search for using the
Superblock or Spiral search algorithms. If more data samples exist in the search range than
specified, only the closest data samples are used for property estimation, up to the maximum
specified value.
Thickness
Thickness represents the maximum vertical search thickness to search for data samples.
Radius
Radius represents the maximum horizontal radius to search for data samples.
Azimuth (deg.)
Angle represents the major search direction, measured in degrees clockwise relative to North.
The range of acceptable values goes from -180 degrees to +180 degrees.
Anisotropy
Anisotropy represents the horizontal ratio for the minor versus major search directions. This
defines the ellipse shape. Acceptable values go from 0.0 to 1.0. The minor direction is
perpendicular to the major direction.
Sector Search
The Sector search algorithm does not use the Max. Samples parameter. The following three
parameters are used:
Points/Sector
Points/Sector represents the maximum number of data samples per sector to use in property
estimation.
Number Sectors
Number of Sectors represents the number of sectors to break the search region into. This is
analogous to deciding how many slices of pizza to cut.
Allowable Empty Sectors

Allowable Empty Sectors represents the number of sectors that can have no data samples in
it. If more empty sectors exist than specified, no property estimation is done. By default, this
number is one less than the number of sectors, since at least one sector requires data for property
estimation.

Search
Output Mask
At the Output tab of the Property Population Dialog you are able to specify the parameters
for the populated output grid. These parameters include a number of (optional) ways to
selectively populate the output grid.
• "Populating an output grid" on page 268.
• "Filtering options" on page 268.
Populating an output grid

• Click on Output Mask.
• Select the populate output grid using check boxes as required, and describe the
parameters.
• Click on Populate.
The output grid is populated with the values you have established in the Property
Population Dialog.
Filtering options
Property Population allows you to modify output by any or all of six filtering options:
Current Property Grid

Allows you to overwrite specified values in the current property grid.
Template Property Grid

Allows you to overlay on the output property grid the values you have arrived at in another grid,
that acts as a template, and (optionally) to specify additional constraints on the population.
K Layers
Allows you to specify two layers; you can populate either between the two layers or outside the
two layers.
Surfaces
Allows you to use surface(s) as population guides; you can populate above or below a specified
surface, between two surfaces, or outside two surfaces.
Displayed Cells
Allows you to populate according to selected cells of the output grid in the 3D Viewer.
You can use these modifiers after you first create a grid, or you can use them in re-gridding.
They offer great flexibility in managing and controlling the population distribution in your
property grids.
They work in a logical AND relationship. For example, if you decide to populate only between
two surfaces AND only between 3D displayed cells, the population occurs only in those cells
that fall between the two surfaces AND are included in the display.

Output Mask
Restrictions
Note the following restrictions:
• You cannot populate (the Populate button is inactive) if you have toggled ON a population
option that contains no data or for which you have selected no data.
• You can set an option or combination of options so that NO cells can be populated.
• You can set an option or combination of options so that ALL cells are populated.
• If you are repopulating an output grid using the selective population options, only the cells
included by your selections in these options are overwritten; earlier values are unchanged.

Output Mask
In the current property grid for population, you can choose to overwrite specified values in any
of five ways.
Hint Because one of your options is to use classes as inclusive or exclusive features, you
may want to review "Indicator Classes" on page 287.
This section includes information on the following:

• "Overwrite" on page 270.
• "Notes" on page 270.
Overwrite
At Overwrite, make a selection from the five options on the drop-down menu:
NULLS:
Overwrites any nulls in the existing output grid with the corresponding values from the current
grid.
Range:
Overwrites any values in the existing output range that fall between user-specified minimum
and maximum with the corresponding values from the current grid. That is, only cells whose
existing output grid values lie within the minimum and maximum values are included during
the population process. See note 1.
Exclude Range:
Overwrites any values in the existing output range that are smaller than the user-specified
minimum or larger than the user-specified maximum with the corresponding values from the
current grid. That is, only cells whose existing output grid values are greater than the maximum
and less than the minimum values are included during the population process. See note 1.
Classes:
Overwrites any value in the user-specified classes with the corresponding value from the current
grid. That is, only cells whose existing output grid values correspond to the class values are
included in the population process. See note 2.
Exclude Classes:
Overwrites any value not in the user-specified classes with the corresponding value from the
current grid. That is, only cells whose existing output grid values do not correspond to the class
values are included in the population process. See note 2.
Notes
1 If you selected Range or Exclude Range, use the Min and Max text fields to set Min and
Max values.
2 If you selected Classes or Exclude classes, click on Indicator.

An Object Selector opens, listing available indicator classifications.
3 Select the desired Indicator Classification.
4 Click on Classes.
An Object Selector opens listing the available classes associated with the indicator.
5 Select the class(es) you wish to limit population to or to exclude from population.
6 Select another option at Selective Population.
Or
Note If you are using the Indicator Simulation algorithm and have set global proportions
to equal more or less than 1.0, a warning panel opens. You may either return to the
Proportions portion of the Algorithm tab and readjust the values, or you may choose
(by selecting Yes) to have the program recompute the proportions to equal 1.0.

Creating and specifying data
• Creating template property grids, see "Template Property Grid" on page 272
• Creating K- Layers, see "K Layers" on page 274
• Specifying surfaces, see "Surfaces" on page 275
• Calculating borehole/surface intersections, see "Borehole/Surface Intersections" on
page 277
• Creating property grids, see "Create..." on page 278
• Selecting units, see "Unit..." on page 279
• "Create Parameter Set..." on page 280
• "Load Parameter Set..." on page 280
• Deleting parameters sets, see "Delete parameter set..." on page 280
• Selecting property type data, see "Property Type..." on page 280
• "Well Logs Data Selector" on page 281
• "2D Property Maps Data Selector" on page 281
• "3D Property Grid Selector" on page 282
• "Scatter Sets Data Selector" on page 282
• "Property Population Parameters Selection" on page 283
Template Property Grid

Once you have created a grid, you probably do additional manipulations with the data and
eventually want to repopulate that grid. There are a number of features in this process to make
it simpler and more productive. The Selective Population toggle gives you access to a
Template option, which allows you to overlay on an existing output grid the values you have
arrived at and (optionally) to specify additional constraints on the population. The assumption
is that the template grid you select has at least some points in common with the current grid.
Hint Because one of your options is to use classes as inclusive or exclusive features, you
may want to review "Indicator Classes" on page 287.
Notes
• If you have no grids to use as templates or you do not select a template, you must be sure
that Template is toggled OFF. Otherwise you cannot populate (the Populate button is not
active).
• If you have created a channel complex using the Fluvial Simulation algorithm, you can use
that structure as a template.
Creating a template property grid

1 Toggle Template Property Grid ON.

The Template tab becomes active and available for input. This tab not only allows you to
select a grid to overlay on the output grid, but also allows you to specify where the output
grid nodes are computed.
2 Click on Property Type.
An Input Data Property Selector opens, listing all available property types. You cannot
create or delete from this interface, only select.
• Select a property type.
See "Property Type..." on page 280.
3 Select a single or multiple realization to use.
4 Click on Template.
The 3D Property Grid Selector opens, listing all available 3D grids. You cannot create or
delete from this interface, only select.
See "3D Property Grid Selector" on page 282.
Note As you are using a selected grid as a template, when you specify one of them as the
Template Grid, its locations and values are used to create the final output grid, but the
Template Grid itself is not (indeed cannot be) overwritten.
5 Go to the 3D Property Grid Selector.

• When you are finished, click on Previous Topic to return.
The Load Template button on the Template tab becomes active.
6 Click on Load Template.
The selected grid is loaded, and the “Histogram” button and following options become
active. Note that if multiple realization is selected, data for only the first realization of the
selected template property grid is loaded.
7 (Optional) To see a histogram of the data in the template grid, click on “Histogram” .
Note that if multiple realization is selected, the histogram for data of only the first
realization of the selected template property grid is displayed.
8 In Overwrite, make a selection from the five options on the drop-down menu:
• NULLS:
Overwrite any nulls in the template grid with the corresponding values from the current
grid. Go to step 12.
• Range:
Overwrite any values in the template range that fall between user-specified minimum
and maximum with the corresponding values from the current grid. That is, only cells
whose template grid values lie within the minimum and maximum values are included
during the population process. Go to step 9.
• Exclude Range:

Overwrite any values in the template range that are smaller than the user-specified
minimum or larger than the user-specified maximum with the corresponding values
from the current grid. That is, only cells whose template grid values are greater than
the maximum and less than the minimum values are included during the population
process. Go to step 9.
• Classes:
Overwrite any value in the user-specified classes with the corresponding value from
the current grid. That is, only cells whose template grid values correspond to the class
values are included in the population process. Go to step 10.
• Exclude Classes:
Overwrite any value not in the user-specified classes with the corresponding value
from the current grid. That is, only cells whose template grid values do not correspond
to the class values are included in the population process. Go to step 10.
9 If you selected Range or Exclude Range, use the Min and Max text fields to set Min and
Max values.
10 If you selected Classes or Exclude classes, click on Indicator.
An Object Selector opens, listing available indicator classifications.
11 Select the desired indicator classification.
12 Click on Classes.
An Object Selector opens listing the available classes associated with the indicator.
13 Select the class(es) you wish to limit population to or to exclude from population.
Or
Note If you are using the Indicator Simulation algorithm and have set global proportions
to equal more or less than 1.0, a warning panel opens. You may either return to the
Proportions portion of the Algorithm tab and readjust the values, or you may choose
(by selecting Yes) to have the program recompute the proportions to equal 1.0.
K Layers
When you created the property grid you are using in populating, you also created K layers. This
option allows you to specify one or more K layers between which to populate or outside which
to populate.
Note If you do not select Two Layer, you must be sure that Layers is toggled OFF.
Otherwise you cannot populate (the Populate button is not active).
Specifying K Layers
1 Check K Layers ON.

The K Layers tab becomes active and available for input. This tab allows you to select two
K layers to be used in populating the output grid.
2 From the drop-down menu at Populate, select how you want the input to be used:
• Between and Including:
Population occurs inside the specified layers and in all layers between them.
• Outside and Excluding:
Population occurs only outside the layers.
3 Use the K Layer text fields to select the two layers you wish to use.
Hint You can limit population to a single layer by selecting the same layer in both places.

Or
Surfaces
Specifies a surface above or below which population is to occur. Or you can specify select two
grids or constants (or a mix) and restrict population to between or outside them.
Note If you do not select a surface, you must be sure that Surface is toggled OFF.
This section includes information on:

• "Specifying Surfaces" on page 275.
• "Displayed Cells" on page 276.
Specifying Surfaces
1 Check Surfaces ON.
The Surfaces tab becomes active and available for input. This tab allows you to select
grids or to specify constants to be used in populating the output grid.
2 From the drop-down menu, select how you want the input to be used:
• Above:
Population occurs only above the specified grid or constant. Upper Surface... is
inactive.
• Below:
Population occurs only below the specified grid or constant. Lower Surface... is
inactive.
• Between:
Population occurs only between the specified grids or constants. Both selection areas
are active.
• Outside:

Population occurs only outside the specified grids or constants. Both selection areas
are active.
Note If you selected Between or Outside, you may use two surfaces.
3 Click on Upper Surface or Lower Surface as applicable.

If you selected surface, a 2D Property Maps Data Selector opens, listing all available
Horizons. See "2D Property Maps Data Selector" on page 281.
Select the surface you wish to use and click on OK.
The Data Selector closes, and the name of the surface you selected is displayed in the text
box on the surface.
4 Select another option, or click on Populate.
Displayed Cells
You can limit population by displayed cells in 3D display in which to populate.
Note If you do not wish to populate, you must be sure that Displayed Cells is toggled OFF.
1 Toggle Displayed Cells ON.

2 On the 3D Display, select Grid Cells.
Or
Save Parameter Set

Saves the property population parameter set. In case the name of the set has not been specified,
a dialog is displayed to query for the name. Only parameter sets that have not been used for
population and, therefore, are allowed to be edited, can be saved.
Save Parameter Set As...

Saves the property population parameter set using a different name than the one currently being
used.
Save Parameter Set and Populate

Save the property population parameter set and runs the population operation using this
parameter set. A warning is displayed if the property population parameter set specification is
incomplete. After the population operation has been completed, the parameter set is locked for
editing, to preserve the grid population history.
Populate Multiple...
Runs the population operation on multiple parameter sets in the specified sequence. See
“"Property Population Parameters Selection" on page 283. After the population operation has
been completed, all the parameter sets used in the population operation are locked for editing,
to preserve the grid population history.

Borehole/Surface Intersections
When you click on the Borehole Surface Intersection button on the Primary Input tab, if
Well Logs has been selected, it computes the intersections between each well/well section and
the start and end depths of all surfaces encountered by that well/well section, and the
intersection information is presented in this Borehole/surface Intersection panel.
The computation results are in a list of intervals along the path of the well trajectory (defined
by the corresponding deviation survey). An intersection is paired with any marker that
corresponds to that intersection if there is mark data available for the intersection.
Note The computed intersection may not always correspond with the interpreted position.
Such a divergence is an indication that you may want to do some stretching or
squeezing of the data before proceeding with property population.
The intersection information is presented in spreadsheet form on the Borehole/surface

Intersection panel. This panel is divided into three areas:
• "Table Setup" on page 277.
• "Borehole/Surface Intersection Information" on page 277.
• "Control buttons" on page 278.
Table Setup
Customizes the contents and sorting of your spreadsheet display. The spreadsheet table can be
sorted by Borehole Name, Surface Name, Intersection Measured Depth, Marker
Measured Depth, the Difference of the Depth Values, Selected Intersection, Depth
Value to Use, Marker Name, Intersection Tvd or Marker TVD value in either the ascending
or descending order.
It can also sort the table with a secondary attribute if you toggle Secondary Sort ON and select
the attribute and either ascending or descending order.
Borehole/Surface Intersection Information

The spreadsheet area, presenting information about the intersections of wells/well sections with
surfaces. The information is presented in following columns:
• Borehole Name
• Surface Name
• Computed Intersection Measured Depth Value
• Marker Measured Depth Value
• Difference Of The Two Depth Values
• Selected Intersection Type
• Depth Value To Use
• Marker Name
• Computed Intersection TVD Value
• Maker TVD Value.

Here you can select to use computed intersection measured depth value or marker depth value
by selecting from the drop-down list in the Selected Intersection column, or type in a depth
value of your own. For the following property population, by default, when marker depth value
is available for an intersection, the marker depth value is selected.
• You can set to use Intersection Depth values or Marker Depth values for all intersections
by clicking on the Set to Marker or Set to Intersection buttons under the spreadsheet.
Control buttons
Recalculate...
Selects some or all of the wells/well sections to recompute the intersection values. It opens a
pop-up panel listing all the wells/well sections loaded, from which you can select the wells/well
sections that you want to be computed.
After you click on OK to close the popup panel, the intersections for the selected wells/well
sections are recomputed and the spreadsheet table is refreshed to reflect the new results.
Recalculate All
Redo the borehole surface intersection computation on all of the wells/well sections loaded and
refresh the spreadsheet with the new results.
Set to Marker
Sets the Selected Intersection column to Marker and the Depth Value to Use column to the
corresponding Marker Depth Values for all the intersections.
Set to Intersection
Sets the Selected Intersection column to Intersection and the Depth Value to Use column
to the corresponding Computed Intersection Depth value for all the intersections.
Reset
Resets the spreadsheet table to its initial state. That is, sorted by borehole names in ascending
order, Selected Intersection column and Depth Value to Use column to marker and marker
depth value respectively if the marker for the intersection is available, otherwise to Intersection
and Computed Intersection depth values respectively.
Note Your settings for the Borehole Surface Intersection panel are not restored in a
workspace restore. The borehole surface intersection values are recalculated the first
time you open the Borehole Surface Intersection panel from the Property
Population dialog after you have restored the workspace.
Create...
Name
Provides the new name for the property grid.

Type
Select the property type for this grid from the drop-down menu. Only the property types that can
be populated are available for selection.
Create Property Type...

See "Property Type..." on page 280.
Unit...
Selects the units for the selected model. Only the units that have been selected are populated.
The units in this property model are displayed in a multi-selection list. Any number of
contiguous items can be chosen from this list.

Property Population menu
Create Parameter Set...

Name
Provide the new name for the Population Parameter Set. This name should be unique.
Clone Of
Select this option to clone an existing population parameter set. The existing population
parameter sets are displayed in a single select list. When you select a parameter from this list,
textual information about the parameter is shown in the read-only text window on the right side
of the dialog. Whenever a new item is selected, the old information is replaced with information
on the new parameter.
Load Parameter Set...

Selects a Property Population Parameter Set to display it in the Property Population panel.
A single select list of all the population parameter sets is displayed for selection on the left side
of the dialog. When you select a parameter from this list, textual information about the
parameter is displayed in the read-only text window on the right. Whenever a new item is
selected, the old information is replaced with the information from the new parameter.
Save parameter set

Saves the currently active set.
Save parameter set as...

Opens a dialog for you to enter the new name.
Delete parameter set...

Deletes Property Population Parameter Sets. A multiple select list of all the population
parameter sets is displayed for selection.
Property Type...
Selects the Property Type for the data.

All the available property types for the selected data type is displayed in a single select list.
Selected property type is used as a filter for the selection of the data which is made from the
Select... panel.
Well Logs Data Selector

Selects well log data for input into property population.
Property
Displays the Property Type of the data in a read only text field.
Available: Well Logs (Well Section)

Displays all the well logs of the selected property type.
Note Well logs of only those wells that have had their borehole surface intersection
calculated are available for selection.
Well log names are displayed by appending the name of their well section to their names. You
can select one or more well logs either by double clicking on the name or by use of the move
arrow buttons.
Selected Well Logs

Displays all the well logs that have been selected as input data. You can deselect data either by
double clicking on the name or by the use of selection and move arrow buttons.
OK
Sets the data selected as the current data selection. It also displays the selected data in the
Property Population panel and removes the panel.
Apply
Property Population panel.
2D Property Maps Data Selector

Selects 2D property map data for input into property population. It displays the names of all the
property maps in FloGrid that matches the selected property type in a single select list, with the
current selection highlighted.
Property

OK
Apply
3D Property Grid Selector

Selects 3D property grids data for input into property population. The panel is divided into 3
single select lists.
The left most list displays all the models. Selection of any model results in the display of all the
property grids in that model which are of the selected property type in the middle list. Selecting
any property grid results in the display of all the realizations of that property grid.
Property
OK
Apply
Scatter Sets Data Selector

Selects scatter sets data for input into property population. It displays the names of all the scatter
sets in FloGrid that matches the selected property type in a single select list, with the current
selection highlighted.
Note Voxel picks, in depth domain, can be exported from GeoViz as 3D scatter data (x, y, z,
property) and imported into FloGrid using File | Import | Scatter Sets. You can use
the Property Population tool, to populate the grid with the scatter set data by selecting
it as primary input data for either direct assignment or inverse distance algorithm, with
a small search radius. You can then use the populated 3D grid to aid further population,
say as a template grid. To generate channel bodies you can use the FluvSim algorithm.
Property

OK
Apply
Property Population Parameters Selection

Selects multiple property population parameter sets and modify their selection order.
Parameter to select
Displays all the property population parameter sets that are available for population operation.
Parameter selected
Displays all the property population parameter sets selected for the population operation. Up
and down arrow buttons allow you to change the order of the selected parameter sets.
OK
Starts population operation on the Property Population Parameter Sets in the order selected
and removes the panel.

This section describes how to use indicator classification in FloGrid property population and the
guidelines to create indicator classes.
To select an Indicator Classification:
• Select Classification button from Advanced Thresholding in the Primary Input tab.
or
• Click on Indicator for Current Property Grid and Template Property Grid in Output
Mask tab.
The Object Selector panel opens.
• "Indicator Classifications" on page 284.
• "Creating and editing an indicator classification" on page 284.
• "Defining classes" on page 285.
• "Guidelines for creating indicator classes" on page 287.
Indicator Classifications
A list box to show all the existing classifications for the property type.
New
Creates a new indicator classification by bring up the Indicator Classification Editor panel.
Selection
Displays the currently selected indicator classification (read-only field).
Creating and editing an indicator classification

To create/edit an indicator classification:
• Select New from the Object Selector,
• or the Edit button in the Sequential Indicator Simulation
• or Fluvial Object Simulation in the Algorithm tab,
the Indicator Classification Editor panel opens.
• Alternatively you can select Edit from the Object Selector to bring up the Indicator
Classification Editor in editing mode.
• Use the interface to specify the parameters for the new indicator classification.
Hint You may want to review the guidelines (see "Guidelines for creating indicator classes"
on page 287) for creating classes before beginning.

The indicator classification editor consists of three areas:
Indication Classification:
Set the basic parameters for the new object (name, description and type).
Classes:
Set the classes and their parameters.
Command bar:
Consists of OK, Cancel, Help buttons.
To create the indicator classification:
• Enter the Name under which you wish to save the indicator classification.
Note Note, if you are editing an existing classification by clicking on Edit button from the
Object Selector, the name is read-only.
• Enter an optional Description of the indicator classification.

• Property Type shows the property type of the current property and is a read-only field.
Defining classes
Individual classes are defined using a spreadsheet structure. The fields include:
Index
Automatically generated index numbers, starting from 0, which are used to represent the
indicator class in the populated grid. These numbers cannot be modified.
Name
Name for the class.
Minimum
Minimum property value for the current class.
Maximum
Maximum property value for the current class.
Note Minimum and Maximum values are used for continuous properties. For categorical
properties, they are replaced by Category.

Color
Sets the color in which class is to be displayed in the 3D Viewer when the simulation is
completed and viewed.
Delete Row
Note You cannot delete the existing classes in the classifications from the Algorithm tab
since they are read-only, but the min/max values (category values for categorical
properties) can be changed, if the min/max values are set to -1/-1 (category values set
to -1), then the corresponding classes are set to unused. Review the guidelines for
creating classes, see "Guidelines for creating indicator classes" on page 287.
Toggle Usage
Toggles on/off the current row. After the row is toggled off, it is not used in the following
calculation.
When an indicator classification is first created, the Indicator Classification Editor checks for
the classes which are already defined for the property type in 3D Viewer’s Color Map Editor,
if there are any classes, the Editor displays these classes with the minimum and maximum
values set to -1. If there is no any classes existing for the property type, the Editor does not
display an entry. When an indicator classification exists, the Editor displays the existing classes
in the classification.
Note If you open the Indicator Classification Editor from Algorithm tab, the existing
classes are in read-only mode. You can only adjust the Minimum and Maximum
values (Category values for categorical properties) or create more classes in the
classification.
To define a class
• Use the Add Row to add one or more rows in the spreadsheet.
• Enter a name in the Name field of each class you are creating. The name can be typed into
the cell or selected from pre-defined common class names from the drop-down list.
• Enter a Minimum and a Maximum value (or Category values in case of categorical
properties) for each class you are creating. For Category values, the user can enter multiple
integral values for a class by connecting the integral values by comma (,) or dash (-). For
example, ‘1-3’, ‘4-6, 8’. For Minimum values, if the user enter the Minimum value for the
current class, and the Maximum value for the previous class is -1.0, then the -1.0 will be
automatically replaced by the Minimum value of the current class.
Note Please refer to "Guidelines for creating indicator classes" on page 287 regarding how
to set the minimum and maximum values.
• Select a color from each class you are creating from the dropdown Colour field.

Selecting classes
When you select:
• the Classes button for Advanced Thresholding in the Primary Input tab
• the Set button for Fluvial Object Simulation in the Algorithm tab
• or the Indicator button for Current Property Grid and Template Property Grid in the
Output Mask tab
the Indicator Class Selector panel opens. It consists of the following areas:
Query From
Name of the classification to select from.
Indicator Classes
Displays all the existing classes for the classification.
Selection
Displays the currently selected indicator classes. This field is read-only.
Guidelines for creating indicator classes

In defining an indicator set, the following rules apply:
1 The data falls in a specified class if min < value <= max, where min and max are the
Minimum and Maximum, respectively, for the indicator, and value is the data value for
continuous properties.
2 One class must have a Minimum and Maximum value (or Category value).
3 If the Minimum and the Maximum value equal -1 (the Category value equals -1 for
categorical properties), the class is set to unused.

Property Population Data Analysis
Property Population offers graphical plotting tools to assist you in your data analysis. Each
graph plot type can be displayed by selecting data and clicking on a button on the Property
Population Manager. This opens the Data Analysis tool with the plotted data and plot type.
• saving graphs as bitmaps: see "File" on page 288.
• editing data: see "Edit" on page 289.
• Standard View menu options: see "Module common options" on page 88.
• Analysis options: see "Analysis" on page 290.
• Analyzing data: see "Data Analysis" on page 292.
• Modifying histograms: see "Histogram Settings" on page 297.
• Displaying univariate statistics: see "Univariate Statistics" on page 298.
• Displaying univariate and bivariate statistics: see "Bivariate Statistics" on page 300.
• "Variogram Specification" on page 302.
Plot Types
Histogram
Bar graph of data frequency distribution.
Variogram
Plot of data spatial correlation.
Crossplot
Bivariate plot in which the components of a data pair are plotted against each other.
Vertical Proportion Curve Data

Bar graph of indicator class distribution by layer. Note this is available only for algorithms
supporting indicator classification.
Bar Chart
Bar graph where the data is binned into independent bars.
File
All the file options are contained in this menu. The standard options are detailed in "Module
common options" on page 88.

Note Note that some do not exist for the Data Analysis tool and are switched off as shown
by the menu items.
Save to Bitmap
Graph...
Saves the main graph to a bitmap file.
Active Graph...
Saves the active graph to a bitmap file.
Whole Picture...
Saves all pictures including small graphs to a bitmap file.
Edit
This menu contains all the options for editing data.
Note Note if the edit options exist in the application, but the current plot consists of data that
is non-editable, then the options are switched off. This is shown by the menu items,
and toolbar buttons being grayed out.
Remove Active Graph

Deletes the selected graph in the main workspace. This option is only available when there is
more than one graph in the workspace.
Add New Graph...

Adds an empty graph placeholder to the main workspace.
Remove Stale Data

Removes any graphs that are labeled as Stale Data. A graph is labeled as Stale Data when the
same plot selection type is graphed in the Data Analysis window and the data is different.
Remove All Data

Removes all of the graphs from all of the workspaces.
Do Not Add Stale Data

Indicates that stale data is not kept in a workspace when the same plot selection type is graphed
with different data. Any graphs that are currently labeled as stale data are not removed. Only
from the time that the selection is made is stale data not kept. To remove any current stale data
graphs, select the Remove Stale Data selection under the Edit menu.

Analysis
Apply Original Data
Note The Data Analysis tool does not use these options and so they are switched off as
shown by the grayed out menu items.
Options
The standard menu options are detailed in "Module common options" on page 88.
Add/Remove Components...
Displays the Graph Configuration panel for the Data Analysis window. You can modify the
visible and hidden layout and window components from here.
Graph Legend Style...

Opens the Graph Legend Configuration panel, which you can use to control the appearance
of the legend at the top of the active graph, or even whether it is present.
Plot style settings...

Opens the Data Style panel for the currently active plot. You can modify various style settings
for the appearance of the data (line, marker style and color) through this panel.
X/Y Axis Settings...

Opens the Axis Property Editing panel for the axis displaying the current active data, either X
or Y, depending on menu option chosen. You can modify the many axis style attributes from this
panel.
Grid Settings...
Opens the Grid Property Editing panel. The grid has a small number of settings, mostly related
to the visibility of the grid itself, and the current point, if defined.
Histogram Settings...
Opens the Histogram Editing panel. You can use the panel settings to modify the selected
histogram in the main workspace. See "Histogram Settings" on page 297.
Bar Chart Settings...

Opens the Bar Chart Editing panel. You can use the panel settings to modify the selected bar
chart in the main workspace. The available settings allow you to display the bar chart showing
the frequency or percentage along the y-axis.

Vertical Proportion Settings...
Opens the Vertical Proportion Editing panel. You can use the panel settings to modify the
selected vertical proportion in the main workspace. The available settings allow you to display
the vertical proportion showing the frequency or proportion along the x-axis.
Original Data Table...

Opens the Original Vector Data panel. This table shows the data in the main workspace before
it is analyzed. You cannot edit the data at present. Each column in the table represents a vector
of data that is used in the data analysis.
Table...
Opens the Active plot vector data panel. This table shows the selected histogram, cross-plot,
or variogram data that is plotted after the data is analyzed. The first column shows the data along
the x-axis, and the second column shows the data along the y-axis. You cannot edit the data.
If there is more than one data plot on a graph, the data in the table is shown for the currently
selected plot. The currently selected plot is highlighted in yellow in the legend above the graph
grid.
Bar Chart Table...

Opens the Bar Chart Data panel. This table shows the selected bar chart data that is plotted
after the data is analyzed. It shows the frequency or percentage for each property type. The color
that represents the property type is shown next to the property type name.
Vertical Proportion Table...

Opens the Vertical Proportion Data panel. This table shows the selected vertical proportion
data that is plotted after the data is analyzed. For each K Layer, it shows the frequency or
proportion value of each property type. The color that represents the property type is shown
below the property name on the table.

Data Analysis
The Data Analysis window is divided into a main workspace and small workspaces. Each
workspace can display graphs of a particular set of data. You select the data and graphs that are
displayed in the Property Population panel, see "Geological Property model" on page 215.
The Data Analysis window is limited to ten small workspaces and one main workspace.
When you display data using the Property Population panel, the current graphs in the main
workspace move to a small workspace. If all workspaces have data, then the next time data is
displayed by the Property Population panel, the data in one of the workspaces labeled Stale
Data is automatically removed.
Note A graph is labeled as Stale Data when the same plot selection type is graphed in the
Data Analysis window and the data is different.
Hint You can set a flag set in the CONFIG.ECL file so that you are prompted with a
confirmation popup before the Stale Data workspace is removed. The default is not
to prompt with a confirmation popup.

• Main Data Analysis "Options" on page 292.
• "Histogram Plots" on page 292.
• "Cross Plots" on page 293.
• "Variograms" on page 294.
• "Vertical Proportions" on page 295.
• "Bar Charts" on page 296.
Options
The standard menu options are detailed in "Module common options" on page 88.
Histogram Plots
A histogram is a graphical representation of frequency of data occurrence; that is, how often a
value occurs in the data set. You can generate a histogram of your data set by selecting data and
clicking on the histogram button on the property population manager.
Hint Histograms are not useful for Constant data, all of which has exactly the same value.
There is no distribution and therefore no way to provide a meaningful graph of
distribution.

Data Analysis
Viewing a histogram can tell you many things about your data, including whether it might be
useful to threshold your data and/or to lump it. For example, if the property you are modeling
is porosity and the histogram shows a number of 0 values, you probably want to threshold the
data to exclude 0 (non-porous) values. In addition, several lumping algorithms do not accept 0
values.
You can use the Histogram Editing panel to modify the selected histogram in the main
workspace. See "Histogram Settings" on page 297.
If the data to be plotted is discrete data, then a bar chart is plotted when the histogram button is
clicked. This occurs if there are 100 or less discrete bins; otherwise, a histogram is plotted. See
"Bar Charts" on page 296
Popup Menu
You have a choice of three styles of histograms, which you can select on the popup menu. You
access the menu by clicking with the right mouse button in a histogram graph in the main
workspace.
You also can select the Univariate Statistics panel box from the popup menu.
Display histogram plot

Displays a graph of the data as a histogram.
Display cumulative plot

Displays a graph of the data as a cumulative histogram.
Display inverse cumulative plot

Displays a graph of the data as an inverse cumulative histogram.
Show Univariate Statistics

Opens the Univariate Statistics panel. This panel displays univariate statistics on the data that
is graphed in the main workspace. Once the panel is displayed, it stays displayed until it is
closed so that multiple univariate statistics can be displayed at the same time. See "Univariate
Statistics" on page 298.
Cross Plots
A crossplot allows you to examine the cross-dependency between measurements of different
attributes. You need this functionality when you are dealing with algorithms that require
primary and secondary input. These are typically kriging-type algorithms.
Popup Menu
You have a choice of three styles of crossplot that you can select on the popup menu. You access
the menu by clicking with the right mouse button in a cross plot graph in the main workspace.
Display Scatter Cross Plot

Displays a bivariate plot where the components of data pairs are plotted against each other. It
allows you to observe three basic patterns of correlation:

Data Analysis
Positive:
Large values of one variable are associated with large values of the other variable.
Negative:
Large values of one variable are associated with small values of the other variable.
Non-correlated:
No association of value size of one variable with value size of the other variable.
Display QQ Cross Plot

Displays a plot of matching quantities. A straight line suggests that the distributions of the two
variables are similar. If the straight line is other than x=y (regression), the distributions of the
two variables are similar in shape but have different locations and spreads.
When you are using as your variables the input data and the output grid produced by an
algorithm, a Q-Q plot tends to illustrate any problems in the centers of the distributions
Display PP Cross Plot

Displays a plot of matching cumulative probabilities (scaled from 0 to 1). A straight line
suggests that the distributions of the two variables are similar.
When you are using as your variables the input data and the output grid produced by an
algorithm, a P-P plot tends to illustrate any problems in the tails of the distributions
Display Primary Collocated Histogram Plot, Display Secondary

Collocated Histogram Plot
Displays the histograms that are available for Primary Collocated Data and for Secondary
Collocated Data.
Note Be aware that the histograms produced from these selections are not the same as a
histogram on the Property Population. The Secondary Collocated Data histogram,
for example, displays secondary collocated with primary data in the crossplot, rather
than all secondary values. This limited set corresponds to values resampled from the
Secondary Collocated Data set at the primary data location. Also, note that if any
primary or secondary collocated data values are null, that data pair is removed from
the data.
Show Bivariate Statistics

Displays a mostly read-only listing of the univariate and bivariate values comprising the data.
The only values you can change are for Linear Regression. See"Bivariate Statistics" on
page 300.
Variograms
A variogram is a graphical tool for examining spatial correlations among data. This is important
because data values tend to become more dissimilar as the distance between them increases.
Thus before populating your model you may want to perform a variogram analysis of the data.
Several of the property population algorithms require the use of one or more variogram models
during the population process.

Data Analysis
Features of a variogram
Figure 12.4 Features of a variogram
= Semivariogram
Value
Gamma Range
Sill
Nugget
Lag Distances
The range is the distance at which the variogram reaches a plateau--the distance at which
increased separation between data pairs causes no further dissimilarity.
The sill is the plateau formed when the distance between data pairs causes no further
dissimilarity.
The nugget effect occurs when the semi variogram value does not tend to 0 when the separation
vector value does.
Popup Menu
You access the popup menu by right-clicking in a variogram graph in the main workspace.
Show Variogram Specification

Opens the Variogram Specification, which can be used for creating, selecting, or editing
variogram models or computing experimental variograms. See "Variogram Specification" on
page 302.
Vertical Proportions
The Vertical Proportion plot is a special type of horizontal bar chart where the x-axis contains
the frequency or proportion (0.0 to 1.0) for a particular bin and y-axis shows the depth of K
layer. This plot is useful for viewing the data trends vertically. It is available only for algorithms
utilizing indicator classification; it keys its display to the parameters of the indicator
classification you have selected for use.
This tool allows you to review the proportion of facies type per layer quickly, typically to see if
a trend exists that makes the imposition of vertical proportions useful.
If data is missing for a layer, the display shows a white gap.
You can use the Vertical Proportion Editing panel to modify the selected vertical proportion
in the main workspace by selecting Vertical Proportion Settings... under Options. The
available setting allows the vertical proportion to be displayed showing the frequency or
proportion along the x-axis.

Data Analysis
Popup Menu
You can access the popup menu by right-clicking in a vertical proportion graph in the main
workspace.
Toggle Frequency/Percentage
Toggles the vertical proportion display to show frequency or proportion along the x-axis.
Bar Charts
The Bar Chart plot displays a series of bars (bins) with independent labels along the x-axis and
with a common unit of measurement along the y-axis. Bar charts are similar to histogram plots,
but the data is not in a continuous range; the data are binned into independent bars.
You can use the Bar Chart Editing panel to modify the selected bar chart in the main workspace
by selecting Bar Chart Settings... under Options. The available setting allows the bar chart to
be displayed showing the frequency or percentage along the y-axis.
Bar charts are also used to display discrete histogram data if there are 100 or less discrete bins.
Popup Menu
You can access the popup menu by right-clicking in a bar chart graph in the main workspace.
Toggle Frequency/Percentage
This selection toggles the bar chart display to show frequency or percentage along the y-axis.

Data Analysis
Histogram Settings
This panel contains options that you can use to modify the histogram that is selected in the main
workspace.
Bin Setting
Sets the histogram to be displayed using the number of bins or a bin width when the data is
analyzed.
Number of Bins
If the bin setting is Number of Bins, then the binning analysis is based on this number.
Bin Width
If the bin setting is Bin Width, then the binning analysis is based on this width.
Display Style
Displays the histogram showing the frequency or percentage along the y-axis.
Data Range Min, Data Range Max

Sets the data range that is to be used in the binning analysis.

Histogram Settings
Univariate Statistics
This folder displays univariate statistics on the data that is graphed in the main workspace.
Options
Measure of Location
Sample Size
Number of valid data samples in the data set
Null Size
Number of invalid data samples in the data set
Minimum
Minimum value in the data set
Maximum
Maximum value in the data set
Mean
Arithmetic mean of the data set
Median
Median value in the data set
Percentile
Given a percentile value (for example, P90), the data value that exists in the cumulative
distribution
Measure of Spread
IQR
The inter-quartile range (IQR) describes the range of data values between the 75th and the 25th
percentiles.
Variance
The variance describes the variation of the data as a squared function of the differences between
the data samples and the arithmetic mean.
Ave. Dev.
The average deviation is a function of the differences between the data samples and the
arithmetic mean.

Std. Dev.
The standard deviation is the square root of the variance.
Measure of Shape
Skew
The skew describes how the data distribution behaves. If there is no skew, the data distribution
is symmetric about the mean. If a positive skew exists, the tail is longer to the right. If a negative
skew exists, the tail is longer to the left.
Kurtosis
The kurtosis describes the size of the tails. A normal distribution yields a kurtosis of 0, and is
termed mesokurtic. A positive kurtosis signifies larger tails, and is termed a leptokurtic
distribution. A negative kurtosis signifies smaller tails, and is termed platykurtic.
COV
The coefficient of variation is a ratio of the standard deviation to the mean, and is a measurement
of reliability. The smaller the coefficient of variation, the more reproducible the results will be.
Chi-square
The Chi-square distribution measures the goodness to fit of the data distribution to a normal (or
other) distribution. This value, along with the degrees of freedom, can be used to test whether
the data fits the normal distribution or not.
Degrees of Freedom
The degrees of freedom is part of the Chi-square test, and is related to the number of bins used
to test the goodness to fit.

Bivariate Statistics
This folder displays univariate and bivariate statistics on the data that is graphed in the main
workspace.
Options
Univariate Measure
Minimum
Minimum value in the data set
Maximum
Maximum value in the data set
Arithmetic Mean
Arithmetic mean of the data set
Standard Deviation
The standard deviation is the square root of the variance
Bivariate Measure
Number
The number of valid data sample pairs collocated with each other
Covariance
The covariance describes the relationship between the two variables. A covariance of 0 signifies
no dependence between the primary and secondary data. A positive covariance signifies a direct
relationship; as the primary values increase, the secondary values also increase. A negative
covariance signifies an inverse relationship; as the primary values increase, the secondary
values decrease.
Correlation Coefficient
The correlation coefficient is similar to the covariance measure, only goes from -1 (inversely
related) to +1. The closer the correlation coefficient is to 0, the less correlated the primary and
secondary data are.
Rank Correlation Coefficient

Similar to the correlation coefficient, only the rank correlation coefficient is computed on the
data ranks, not the actual data values. This is considered a more robust measure than the
correlation coefficient itself.

Linear Regression
These are used to plot the linear regression line on the graph in the workspace.
• Slope
• Intercept
• Secondary Primary

Variogram Specification
This folder contains options for the experimental variogram and the variogram model. The
loaded data that is used in the analysis is listed on the title bar of the panel and in each directional
graph that is displayed. The major, minor, and vertical direction graphs are displayed in the
Data Analysis window.
• "Experimental Parameters" on page 302.
• "Model Parameters" on page 304.
• "Interactive Graphs" on page 306.
• "Azimuth" on page 306.
• "Output Variogram Model" on page 307.
Experimental Parameters
This area contains options to calculate the experimental variogram measure. Experimental
variograms are based on data as originally loaded (well logs or grids) or on data derived from
the originally-loaded data: data that has been thresholded or lumped, for example, or grids
output from other Property Population actions.
Spatial Equations
Select from the drop-down Spatial Equations menu the type of correlation you wish to use.
Note Only those algorithms appropriate for the population algorithm selected and the data
type are listed. For example, if the algorithm selected is Sequential Indicator
Simulation, only Indicator Semivariogram is an option.
The available Spatial Equations are:

• Semivariogram
• Covariance
• Correlogram
• General Relative Semivariogram
• Pairwise Relative Semivariogram
• Semivariogram of Logarithms
• Semirodogram
• Semimadogram
• Indicator Semivariogram

Search Distances
Lag, Maximum Lag
These two parameters together determine the number of lags, which is equal to the maximum
lag divided by the lag length. There is a built-in overlap for a lag distance equal to one-half the
value set for the lag. This distance is added to either side of the lag to ensure coverage of all
points. The maximum lag value must be greater than the lag value.
Decimation
Decimation controls are used to decimate the data. Decimating the data reduces the data size
and declusters the data based to the bin size specified.
Half Angle
This is the angle from the direction vector that is used for the data pair search.
Bandwidth
This is the max distance perpendicular to the direction vector that is used for the data pair search.
Angle Increments, Start Direction

The start direction is the initial azimuthal angle for calculating the directional experimental semi
variogram. The angle increments specifies the increment to use in calculating further directional
experimental Semivariogram.
Experimental and Cloud Buttons

Compute experimental
Computes the experimental variogram measure and plots the experimental variogram results in
each of the directional graphs. If this is clicked and no values have changed since the last
computation, a warning message will pop up.
Clear experimental
Removes the experimental variogram from each of the directional graphs.
Display cloud
Displays the cloud plot in each of the graphs. The cloud is made by plotting each data pair’s
separation distance versus the semi variogram measure. This button is desensitized until the
experimental has been computed at least once.
Note The first time this button is selected for a new variogram display, a popup message
suggests you clear the cloud data when it is not in use to prevent refresh delays.
Hint If the cloud data gets covered by another window and does not refresh, use View |
Refresh.
Clear cloud
Removes the cloud plots from each of the directional graphs.

Model Parameters
This area contains options for creating, selecting, or editing variogram models. Variogram
models are used for geostatistical and simulation algorithms to determine the spatial variation
for the data set.
Changing the values on the panel automatically updates the directional graphs in the Data
Analysis window.
You can also update the values on the panel interactively on each of the directional graphs.
Input Variogram Model

You can select a saved variogram model by clicking on the drop-down menu. When a model is
selected, the panel updates the model values. The major, minor, and vertical graphs in the Data
Analysis window also update with the values. A model selection of None shows default values
for the selected data.
Model Type
You have three model choices:
Spherical
Has a linear behavior near the origin but flattens at longer distances.
Exponential
Has a linear behavior near the origin and reaches its sill asymptotically
Gaussian
Has a parabolic behavior at the origin and reaches its sill asymptotically
Nugget
The nugget effect occurs when the semi variogram value does not tend to 0 when the separation
vector value does.
• To update the Nugget Value, move the Nugget Slider, which also updates the nugget
value on all directional graphs.
• To update the Nugget Value interactively from the graph, press the left mouse button down
just right of the y-axis of the graph near the origin and move the cursor up or down the y-
axis. The cursor should change to an up and down arrow. The Nugget Value is the same
for all the variogram directions, so all graphs update as well. To refine the value, the slider
should be used.
Note When selecting the origin to update the Nugget Value, press the left mouse button
down on the right side of the y-axis close to the origin. (Pressing on the left side will
show a red line which will move the entire y-axis.)

Note The Nugget Value must not be greater than the minimum sill value, and the slider and
graphs do not update past this value. They also do not update when the value is out of
the minimum or maximum value range. A message in the one-line help area will warn
you when the limits have been reached.
Variogram Direction
In variogram modeling, selecting a direction allows you to specify the anisotropy for the model
variogram. Anisotropy occurs when the spatial variability of a phenomenon changes with
direction.
You have four options that apply to the model:
Omnidirectional
Analyzes both the horizontal major and the horizontal minor at the same time.
Horizontal Major
Analyzes anisotropy in the principal (or major) axis direction. The major axis is the plane of
greatest continuity and is defined using the azimuth angle.
Horizontal Minor
Analyzes anisotropy at 90 degrees to the major axis as viewed in the x, y plane. The minor axis
occurs at the intersection of the major plane and the horizontal plane.
Vertical
Analyzes anisotropy at an angle that is perpendicular to the directions of both the minor axis and
the major axis. The vertical axis occurs at 90 degrees from both axes.
Areal Omnidirectional and Areal Major or Minor

When the Areal Omnidirectional button is selected, the major and minor values are the same
and any changes to the range or sill change both the horizontal major and the horizontal minor
values.
When the Areal Major or Minor button is selected, the major and minor values are independent
of each other and the range and sill values can be changed separately.
The exception to this is if the Constrain to major sill is checked on.
Constrain to major sill

When the Constrain to major sill is checked on, all sill values are set to the major sill value
and all values change the same whenever any of the sill values is changed. The default is for this
to be checked on.
Range
The range is the distance at which the variogram reaches a plateau--the distance at which
increased separation between data pairs causes no further dissimilarity.

• To update the range value for a direction, move the Range Slider next to that direction.
This also updates the range value on the selected directional graph.
• To update the range value interactively from the graph, press the left mouse button down
on the marker intersection of the range-sill lines and move the cursor to the right or left.
Only the range value for the direction type of the graph updates except in the following
case:
• If the omnidirectional option is selected, the range for both the major and minor
directions update.
Note The major range must not be less than the minor range value, and the major or minor
slider and graphs do not update past this value. They also do not update when the value
is out of the minimum or maximum value range. A message in the on-line help area
warns you when the limits have been reached.
Sill
The sill is the plateau formed when the distance between data pairs causes no further
dissimilarity.
• To update the sill value for a direction, move the Sill Slider next to that direction. This also
updates the sill value on the selected directional graph.
• To update the sill value interactively from the graph, press the left mouse button down on
the marker intersection of the range-sill lines and move the cursor up or down. Only the sill
value for the direction type of the graph is updated except in the following cases:
• If the omnidirectional option is selected, the sill for both the major and minor
directions updates.
• If the Constrain to major sill is checked on, all sill values update the same.
Note The sill value must not be less than the nugget value, and the slider and graphs do not
update past this value. They also do not update when the value is out of the minimum
or maximum value range. A message in the on-line help area warns you when the
limits have been reached.
Interactive Graphs
Each of the graphs is interactive and can be used to set range or sill values on the Variogram
Specification panel. The graph must first be selected to move the limit lines or nugget in it.
Select the graph by clicking on one of its graph plot titles in the legend above the graph grid.
Azimuth
The azimuth angle is used in defining the major axis direction.

Output Variogram Model
Save
Saves the model parameters. If the model is representing stale data (which is shown in the dialog
title), this button is desensitized.
If the model has already been used for population, it cannot be edited and saved. In this case, a
message opens to say that it cannot be edited.

Creating a structured grid
Chapter 13
Structured Gridder Module

This chapter details how to create a structured grid from a structured framework. You create a
structured grid using corner point gridding.
• "Corner point gridding" on page 311
• "Defining and editing boundaries" on page 311
• "Gridding Controls" on page 313
• "Areal gridding" on page 318
• "Vertical gridding" on page 321
• "Rectangular gridding" on page 330
For further information on how to create a structured framework see "Structural Framework" on
page 18 and "Model Creation" on page 19. Once you have created a structured grid you can
refine and resize it; see "LGRs, Resizing, Aquifers and NNCs" on page 407.
When a grid has been created, and if necessary refined and resized, properties may be assigned
to it by:
• creating them interactively using the Simulation Property Editor
• using Calculator scripts
• importing properties
• upscaling from a property model.
Property functionality is normally accessed using the Structured Gridder Properties option
or the 3D Viewer. You can also use the Upgridder to group layers in a geological model into
coarser simulation layers; see "Upgridder" on page 487.
Generated grids and properties can be exported from either of the gridding modules or the
Structured Gridder Properties window For further information see "Structured gridder
properties" on page 427.
FloGrid User Guide Creating a structured grid 309

The Structured Gridder module is used primarily to build structured corner point and
rectangular fluid-flow grids, and properties that honor selected features of a given property
model.
You can open the Structured Gridder window either by right-clicking on a structured grid
FloGrid model node in the tree and selecting Edit from the pop-up menu, or by selecting Tools
| Old Workflows | Structured Gridder... in the main window.
This window has a menu bar from which options can be selected that allow you to copy and edit
structured grid models. There is also a model and mode selection area, and a display area that
contains folders. The folders displayed depend upon what type of structured grid you are
building.
To create a new structured grid model from which to build a structured grid you first need to use
Create Flogrid Model panel accessed either using the FloGrid Models node’s pop-up menu,
the Tools menu or the main window buttons.
310 Creating a structured grid FloGrid User Guide

You create a structured grid using corner point gridding. To build a structured grid you should
first specify a grid boundary and then define an areal (coordinate) corner point grid. The final
stage is define the vertical grid. "Corner point gridding" on page 761 contains technical
information on corner point gridding.
An important feature of the Structured Gridder is the option to align I- and J-grid lines with
gridding controls. Faults or parts of faults that do not correspond to gridding controls are
zigzagged. Gridding parameters include global Nx, Ny and Nz, orthogonality, smoothness and
sub-grid Nx and Ny distribution to control the distribution of I- and J-rows and columns in
different areas of the grid. Cartesian and radial local grid refinement is supported. Coordinate
lines may be sloping or vertical. Vertical layering is based on the reservoir units with options for
subdividing units.
• The first stage of building a corner point grid is defining the grid boundaries; see "Defining
and editing boundaries" on page 311.
• After you have defined the grid boundaries you should select the gridding controls you wish
to be gridded; see "Gridding Controls" on page 313.
• Once you have set up the boundaries and gridding controls you can define the areal corner
point grid; see "Areal gridding controls" on page 314.
• The final stage is defining the vertical grid; see "Vertical gridding" on page 321.
Defining and editing boundaries

The Boundary folder allows you to define and edit corner point grid boundaries.
Select boundary
Shows the currently selected boundary for the current model. You can choose from a list of all
the structured grid model boundaries that exist in the model.
Create from Structural Framework boundary

Forces the simulation grid boundary to match the structural framework boundary. When this
option is used, a copy of the original structural framework boundary is taken. This allows edits
to be made to the grid boundary without invalidating the original structural framework.
If boundary has already been created using this for a given simulation grid, the option is grayed
out.
Create, copy, edit...

Opens the Create or Edit Model Boundary panel to allow you to start up a boundary
creation/editing session in the 3D Viewer (see "3D Viewer" on page 107).
Boundary list
Lists all existing structural grid models. The drop-down lists the boundaries that exist in that
model.

Create...
Opens the Create Boundary panel.
Boundary name
Boundary type
Projection plane
Copy...
Opens the Copy Boundary panel to allow you to select an existing boundary as a template for
the new boundary.
Copy from...
Opens the Select Boundary to Copy panel to allow you to select another (Global, structural
framework or Structured Gridder) category of boundary from a drop-down list.
Edit...
Opens the Edit Boundary panel to allow you to edit an existing boundary.
Delete
Deletes the selected boundary from the list, but not from the file it was imported from.
Import...
Opens a browser for you to select an existing boundary to import.
Export...
Opens a browser for you to select an existing boundary to export.
+ View/- View
Adds or removes a selected boundary from the 3D Viewer.
See "Boundaries..." on page 113 for more detail of the boundary editor.
3D edit
Activates the digitizing mode in the 3D Viewer. This enables a new boundary to be digitized or
an existing one to be edited. This option requires that at least one item is present in the viewer.
See "Digitize" on page 126 for more details.
Table edit
Once a boundary has been created you may decide to edit it by modifying the X-Y coordinates
of the points in the boundary. The Table Edit button displays the Boundary Edit table on the
right side of the Boundary folder. This allows you to edit the current boundary.

Reference coordinate system
Displays a drop-down list containing the structural framework and a list of the structural maps
in the system. By default, the reference coordinate system is set to be the one used by the
structural framework. In the event that different maps have different coordinate systems,
selecting one of these maps causes the points in the table below to be displayed in the new
coordinate system.
X and Y coordinates
The second and third columns of the table show the X and Y coordinates of the boundary points
which you may edit.
Corner
The last column shows the corner of the boundary. This is a major point in the terminology of
the Boundary Editor. A single click of the mouse on any cell in this last column switches the
point between major (Y) and minor (N) (corner or non-corner).
Gridding Controls
After you have defined the grid boundaries you should select the gridding controls you wish to
be gridded.
The Gridding Controls folder contains options for creating, editing and deleting gridding
controls for corner point grids.
• "Areal gridding controls" on page 314
• "Sloping grids" on page 314
• "Boundary deviation" on page 315
• "Gridding control table" on page 315
• "Show gridding controls" on page 316
• "Editing gridding controls" on page 317.
Gridding controls are used to control the positions of areal grid lines and the slope of coordinate
lines if sloping coordinate line gridding is enabled.
Two types of gridding controls are supported: control surfaces and control lines. Control
surfaces were introduced in 2002A and are based on the Fault Framework. You can select
which type of gridding control is to be used when the gridding model is created. Control lines
are always used when running command files created by previous versions of FloGrid prior to
2002A.
It is expected that you will need to edit the default set of gridding controls in nearly all cases.
Typical edits involve:
• Creating a new control that corresponds to part of an original fault, for the purpose of
aligning that part of the fault with an I- or J- line.
• Creating a zigzag control that corresponds to part of an original fault, to ensure that the
slope of the grid corresponds to the slope of the fault in that region.
• Creating a new control to merge two faults (or parts of faults) that you want to place on the
same I- or J- line.
• Creating a new control, for the purpose of controlling the grid construction in that region.

This might be because there are wells in the region, or because the slope of the grid needs
to be controlled near the boundary, or because you need to create additional grid sub regions
within which local Nx and Ny values can be set.
Typical edits applicable only to control lines are:
• Deleting the original control line corresponding to a fault when new Control Lines have
been created to model portions of the fault. This ensures that the Structured Gridder is not
supplied with multiple slope control information in the same area of the grid. With Control
Surfaces it is possible to split an existing control into two or more portions in a single
operation.
• Deleting the original control line corresponding to a fault when the slope of the fault proves
impossible to honor when a grid is constructed. This might be because the fault has a very
complex shape or because other faults nearby make it impossible to create a sloping
coordinate line grid with straight coordinate lines that honor all slopes without the
coordinate lines crossing. With Control Surfaces you can select the controls used to slope
the grid individually, so you can easily turn off any problem controls without deleting them.
Control Lines can be created as either vertical lines or as polygons. Vertical lines are used in
areal gridding only. Polygons are used in areal gridding and when sloping the grid. When
sloping grids are generated all polygons are used, even if they are of type zigzag.
Areal gridding controls

Gridding controls of type I- or J- are used to control areal gridding. You can use these controls
to honor faults exactly. You can also influence the density of the areal grid in different regions
by introducing controls that split the grid into separate sub-grid regions where Nx and Ny values
can be set
When the areal grid is generated from Control Surfaces the gridding lines are taken from the
average lines. Average lines are shown in red in the 3D Viewer. When the areal grid is generated
from control line polygons the gridding line is taken midway between the upthrown and
downthrown lines. The Structured Gridder ensures that a line in the areal grid with a constant
I value is aligned with the gridding line for controls of type I-. The same applies for J- lines.
If you wish to ignore a particular control in the areal grid then set the type to zigzag. These
controls can then be used to slope the grid or they can be ignored completely.
Sloping grids
With control surfaces you can easily switch on and off the controls that are used to slope the
grid. If a control is enabled the grid is sloped so that coordinate lines lie on the surface. If a
control is ignored then the slope of the grid near the control is based on the slopes of the
surrounding controls.
With control lines you must create polygons if you wish to slope the grid. If you do not want a
control to influence the slope you must create it as a vertical line.
If a control line polygon has been auto-generated from a fault, Z values for the control polygon
are taken directly from the fault if these have been explicitly provided (X Y Z values read in or
using Rescue). If the Z values do not already exist, they are calculated by projecting the control
lines onto the surface of the structural framework. Any control polygon that is edited has its Z
values recomputed by projecting the new polygon onto the Structural Framework.

Note Care must be taken when creating or editing control line polygons to ensure that the
end points of the upthrown line and the end points of the downthrown line are
positioned consistently with any other slope information nearby. If this is not done, it
is possible to create grids where conflicting slope controls cause co-ordinate lines to
cross.
Boundary deviation
As an aid to classification, the areal alignment of each gridding control is compared to the
alignment of the I and J axes and reported in a table. Deviation angles are calculated by
comparing the best straight-line fit through each gridding control to the best straight-line fit
through each boundary.
The Boundary Deviation option allows you to classify gridding controls based on user-defined
maximum acceptable deviation angles. Gridding controls with I or J deviation angles that fall
below these maximum angles are made into either an I- or J- control as appropriate.
Note It is strongly recommended that automatically classifying gridding controls using

deviation angles is not done, as in general it leads to poor quality grids. Instead, it is
recommended that gridding controls are visually inspected and interactively classified
as I-, J- or zigzag controls using either the Type table drop-down or the pop-up menus
accessible from the Fault Gridding Controls nodes on the tree, linked with the 3D
Viewer (see "3D Viewer" on page 107).
I line angle
Defines the maximum acceptable deviation angle for I-lines. Gridding controls with I deviations
below this angle are only set to be I controls when you click on Apply.
J line angle
Defines the maximum acceptable deviation angle for J-lines. Gridding controls with J
deviations below this angle are only set to be J controls when you click on Apply.
Apply
Reclassifies control lines. This resets any previous control line classifications.
Gridding control table

3D
Indicates with a ## symbol which gridding control has been selected in the 3D Viewer.
Name
Lists the names of the gridding controls.
Type
Selects the gridding control type from Zigzag, I Line and J Line options. However, if a
gridding control crosses a boundary, the I or J Line options may not be available.

I angle
Displays the angle between the best fit lines going through the gridding control and the J
boundary. A small angle indicates a gridding control is well aligned with the J boundary and
hence is suitable for gridding to a grid line of constant I.
J angle
Displays the angle between the best fit lines going through the gridding control and the I
boundary. A small angle indicates a gridding control is well aligned with the I boundary and
hence is suitable for gridding to a grid line of constant J.
Slope
Displays how the gridding control is used if sloping coordinate line gridding is enabled in the
Vertical gridding folder. For control surfaces it is possible to choose between Ignore and
Slope. If the type is Zigzag it is also possible to select Slope+Snap, in which the corners of
the cells nearest the control surface are moved onto the surface. For control lines this column is
used to indicate whether vertical lines or polygons were set.
Show gridding controls

The Display button adds gridding controls to the 3D Viewer (see "3D Viewer" on page 107)
according to the selection criteria set in the Select By Type check-boxes.
Note Each time the status of a check box is changed the list of viewable gridding controls is
rebuilt, overriding any selections previously made.
Control surface coloration

Control Surfaces are displayed in the 3D Viewer using the color of the fault upon which they
are based. New controls not based on any fault are drawn in cyan. Lines along the top and
bottom of the surface are drawn in magenta and cyan, respectively, and the average line is drawn
in red.
Control line coloration

Control Lines are displayed in the 3D Viewer using a color convention that identifies the
control line type.
Note Although a control line always consists of a top line and a bottom line (for example,
corresponding respectively to the upper upthrown and the lower downthrown side of a
fault), if the control line is vertical only the top line is displayed.
The top line color of a control line is

• Yellow: if the control line belongs to the Default Set
• White: if the control line lies outside the grid boundaries
• Plum: if the control line is of type I
• Green: if the control line is of type J
• Brown: if the control line is of type zigzag.
The bottom line (when drawn) is always colored in Cyan.

When a control line is selected it appears in the 3D Viewer with its colors dashed with a red line.
Editing gridding controls

Once in the 3D Viewer, gridding controls can be interactively classified as I, J or zigzag control
lines from the 3D Viewer by enabling the Set Type Via 3D Selection check-box and then
picking on the desired control line type. For control surfaces it is also possible to set the slope
option by enabling the Set Slope Via 3D Selection check-box.
Gridding controls can then be classified simply by picking on them in the 3D Viewer. In
addition to highlighting the selected control, a ## in the 3D column of the gridding control table
denotes the picked control.
The Set All button sets the type or slope of all gridding controls.
To finish classifying gridding controls, disable the Set Type Via 3D Selection and Set Slope
Via 3D Selection check-boxes.
An alternative way of setting the type and slope of control surfaces is to use the node tree.
The Edit button either enables the control surfaces editor (see "Fault framework editor" on
page 191) or displays the Edit control lines panel.
Edit control lines

Displays a list of the available control lines and offers the following options:
Control line list

Selects the set of control lines to be edited. One set exists for each gridding model. There is an
additional default set that can be used to store control lines not associated with any particular
gridding model.
Create
Opens the Create Control Line panel. This allows you to define a new control line for the
active (selected) control line set.
• Line/polygon
Select whether the control line to be created is vertical or sloping. If the control line is
vertical it is normally defined by a single line. If it is to be sloping, it is defined by a
polygon. Note that a polygon can be used to define a vertical control line. This can occur
when a polygon is used in conjunction with the Vertical Gridding option. In this scenario,
a center line is constructed from the average of the two sides of the polygon.
When you click on OK, an Edit session is started in the 3D Viewer to allow you to
interactively define the new control line.
Copy
You must select a control line before choosing this option, which then opens the Copy Control
Line panel. The options on this panel are identical to those for Create above.
When you click on OK, an Edit session is started in the 3D Viewer to allow you to interactively
define the new control line.
Copy from
Copies a control line from a different set of control lines, typically corresponding to another
gridding model. This option displays the Select Control Line to Copy panel. Select the
required control line set from the list and then select the required control line from that set.

Once a control line to be copied has been selected, the options and steps are identical to those
for Copy above.
Edit
You must select a control line before choosing the option which then opens the Edit Control
Line panel.
• Line/polygon
These buttons control whether the control line is to be edited as a line or as a polygon. The
buttons default to the existing status of the control line and should normally be left
unchanged.
If you change the line type from a polygon to a line, the Edit session uses the first line of
the polygon and deletes remaining points. If you change the line type from a line to a
polygon, the existing line is defaulted to be the first line of the new polygon.
When you click on OK, an Edit session is started in the 3D Viewer to allow you to
interactively define the new control line.
Copy full set

Copies a full set of control lines from a different set of control lines, typically corresponding to
another gridding model. This option opens the Select Source Control Line List panel. Select
the required control line set from the list.
Import
The file format required is based on the CPS3 fault file format.
Export
The file format used for exported control lines is based on the CPS3 fault file format.
Areal gridding
The Areal Grid folder allows you to define an areal (coordinate line) corner point grid with
options to control grid quality and density.
Before constructing an areal grid you should define a grid boundary and select which gridding
controls are to be gridded.
Set global Nx/Ny

This option is enabled when a grid is constructed for the first time. The values set for Total Nx
and Total Ny are used with other grid parameters to construct an Nx * Ny grid that fits the
boundary defined in the Select boundary folder, and that honors the I and J gridding controls
selected in the Gridding Controls folder.
When a grid is built with this option, grids are effectively subdivided into a set of sub-grid
regions by the extended lines that honor each I and J gridding control.
In a grid where all gridding controls are zigzagged there is only one sub-grid.
Set sub-grid Nx/Ny

Varies the number of grid lines between gridded gridding controls. It is only available after an
initial areal grid has been constructed.

The number and shape of sub-grid regions are determined by which gridding controls are
selected as I and J gridding controls in the Gridding Controls folder. When this option is active,
you can specify the number of cells in each sub-grid in the associated table. This table is linked
to the displayed 2D grid.
Row
This is an information field numbering the sub-grids in the I and the J directions.
Subgrid
A ## symbol in this field indicates that this sub-grid has been picked in the 2D grid displayed
in the 3D Viewer.
Nx’s
Sets or indicates the number of x (I) rows in the sub-grid.
Ny’s
Sets or indicates the number of y (J) rows in the sub-grid.
Total Nx
Defines the total number of grid cells in the x (I) direction. If this number is set less than the
number of I gridding controls plus 1, the Structured Gridder automatically increases this value.
Total Ny
Defines the total number of grid cells in the y (J) direction. If this number is set less than the
number of J gridding controls plus 1, the Structured Gridder automatically increases this
value.
Average Dx
Provides an indication of the average grid cell size in the x (I) direction at the model boundaries.
The Average Dx field is updated when you set the Total Nx value. You can also type a value
into this field to define the grid cell size required. The Total Nx value is then updated to give a
grid cell size as close as possible to the value set.
Average Dy
Provides an indication of the average grid cell size in the y (J) direction at the model boundaries.
The Average Dx field is updated when you set the Total Ny value. You can type a value into
this field to define the grid cell size required. The Total Ny value is then updated to give a grid
cell size as close as possible to the value set.
Gridding parameters
Smoothness
Determines how much the distribution of grid lines in one sub-grid is affected by grid line
spacings in neighboring sub-grids. A value of zero results in sub-grids being treated
independently. A high value (towards 1) results in grid line spacings that change more smoothly
across each adjacent sub-grid. For more details see "Smoothness" on page 769.

Orthogonality
Controls the orthogonality of the grid by changing the shape of the control line extensions that
grid to selected gridding controls. A high value (towards 1) produces a more orthogonal set of
grid lines. Any non-zero value causes the gridder to take much longer. For more details see
"Orthogonality" on page 769.
Gridding method
Selects Isotropic or Anisotropic gridding.
The primary difference between the two methods is in how the grid lines that lie on gridding
controls are extended (control line extensions). In many situations the difference between grids
computed with the two methods is very small. As isotropic gridding is faster, it is chosen as the
default. For more details on these gridding methods see "Isotropic and anisotropic gridding" on
page 769.
Fault ends
Automatically creates additional control lines at each end of the user-defined control lines. This
might be used to try and ensure that all the ends of faults modeled by control lines are honored
by grid cell corners. For example, if this option is used, each gridded I control line ultimately
produces 3 control lines, one along the control line and one at each end of the control line.
Note It is strongly recommended that this option is not used. If it is tried, extreme caution
should be exercised when evaluating the resulting grid as it can result in excessive
numbers of control lines being generated that are too close together. The tolerance field
merges control lines generated by this option if they are within the specified tolerance
distance.
Areal grid
Build
Initiates the Structured Gridder using the currently selected gridding parameters. In certain
cases grid regeneration can be very fast. This depends on which parameters are changed.
Edit
Opens the Areal Grid Editor. Make sure a reference object such as a map is in the view before
editing.
The Areal Grid Editor contains options for moving areal grid nodes and for probing the grid to
get X Y values. There is also an undo facility, which can be used to progressively undo grid node
edits made up until the last time the edit session was committed.
All editor modes and actions are selected by using the editor buttons. By default the editor
comes up in Grid Probe mode.
Display
Displays the current areal grid in the 3D Viewer (see "3D Viewer" on page 107). In
circumstances where the Structured Gridder has failed, the displayed grid may be distorted or
incomplete.

Vertical gridding
Defining a vertical grid is the final stage of creating a corner point grid.
The Vertical Grid folder allows you to define the vertical grid of a model whose areal grid has
been defined in the Areal Grid folder (see "Areal gridding" on page 318) or the Rectangular
Grid folder. By default, one simulation layer is created for each unit in the property model. If
additional simulation layers are required within a given unit they can be specified in the table
or by using the Advanced Layering option.
You can:
• create sloping or vertical coordinate line grids
• decide how faults are modeled and represented in the simulation grid
• determine how simulation layers are constructed within geological units.
Unit layering table

Creates additional simulation layers within a unit. Layers can be created directly in the table
when the required layering is simple to define or by using the Advanced Layering options that
allow you to specify more complex layering, including using the property model layers as
simulation layers.
Note By default, layer thicknesses are calculated and displayed the first time that the Set
Layering button is pressed. This speeds up areal gridding iterations when working
with large models. You may opt to pre-calculate unit thicknesses in the future
whenever the areal grid is regenerated (the 2001A behavior) by clicking the checkbox
Unit Thicknesses Pre-calculation, which is found below the Unit layering table.
Note The average layer thickness values displayed in this table are also useful when using
the Advanced Layering options, Top Conforming and Bottom Conforming to set
varying fixed thickness layers within a unit (using Refine Selected BlockUnit).
These values help you determine precisely how many layers are required.
Number of layers
Indicates the total number of simulation layers defined in the model.
Note If any changes are made to layering parameters in the unit layering table, the Set
Layering button must be hit for changes to take effect when building LGRs and 3D
grids. If there are LGRs already defined in the grid, then their vertical extent and
refinements are set to the default values of one refined layer in each layer of the parent
grid.
Unit
Displays the name of the geological unit. This field is read only.
Layer type
Select the desired vertical gridding scheme for each unit.

By default each unit in the structural / property model is represented in the simulation grid by a
single simulation layer. This can be changed on a unit-by-unit basis by selecting the desired type
of simulation layering and specifying the appropriate parameters for that layering scheme.
Proportional
This is the default layering option. When this option is chosen the unit is subdivided into the
number of layers specified in the Layers Per Unit field.
Bottom conforming (offlap)

When this option is chosen, fixed thickness simulation layers are constructed upwards from the
lower surface of the unit. The desired thickness of each simulation layer should be specified in
the Layer Thickness field.
The following approach is used:
1 Calculate the maximum vertical thickness in the unit.
2 Calculate the maximum number of layers required from step 1.
3 For each coordinate line, place the number of nodes just calculated along the coordinate
line at fixed intervals. Move any nodes that are placed above the top of the unit to the top
of the unit.
This approach means that there are often large areas of the grid where the uppermost grid cells
are pinched out with zero or small thickness.
Top conforming (onlap)

When this option is chosen, fixed thickness simulation layers are constructed downwards from
the upper surface of the unit. The desired thickness of each simulation layer should be specified
in the Layer Thickness field.
The following approach is used:
1 Calculate the maximum vertical thickness in the unit.
2 Calculate the maximum number of layers required from step 1.
3 For each coordinate line, place the number of nodes just calculated along the coordinate
line at fixed intervals. Move any nodes that are placed below the bottom of the unit to the
bottom of the unit.
This approach means that there are often large areas of the grid where the lowest grid cells are
pinched out with zero or small thickness.
Use property model

Indicates when you have specified that a unit has additional simulation layering based on the
property model layering within that unit.
Hint It also provides an alternative method of opening the Edit Layer Controls panel,
which provides advanced layering options.
Layers per unit

Defines the number of simulation layers within the geological unit when constructing
simulation layers using proportional spacing.

If fixed thickness onlap or offlap gridding is selected this field is read-only, and reports back the
estimated maximum number of layers required to grid the unit given the requested layer
thickness.
Max unit thickness / Layers per unit

Defines the desired thickness of simulation layers when using onlap or offlap gridding.
If proportional gridding is used this field is read-only, and reports back the maximum thickness
of the simulation layer within the unit.
Note If any changes are made to layering parameters in the unit layering table, the set
layering button must be pressed for changes to take effect when building LGRs and 3D
grids.
Note The associated Build option must still be selected to compute associated grid
geometry.
Advanced layering
Opens the Edit Layer Controls panel for defining more complex layering schemes, such as
• layering that varies between blocks within a unit
• weighted proportional layering
• conforming layers of varying thicknesses
• layering that conforms to a selected surface or pair of surfaces, rather than the top and
bottom of the unit.
Edit layer controls...

Opens the Edit Layer Controls panel. The layer controls determine the vertical gridding within
units. The number of units was determined in the structural model, and the vertical gridding
always honors the horizons between each unit. You can control the number and gridding style
of layers (refinements):
• within each unit
• within each individual block-unit.
Three of the five gridding styles (Proportional, Top conforming and Bottom conforming)
make use of a pair of reference surfaces to control the layering, referred to hereafter as the upper
and lower surfaces. By default, the upper surface is taken to correspond to the upper surface of
the selected unit, and similarly the lower surface is taken to be the lower surface of the selected
unit. If you wish, you may alter these and select a surface from the Reservoir Data Store instead.
Layering basis
You toggle this radio button between Unit-wide controls and Block-unit controls. If you choose
Unit-wide controls, then you can specify the layering for each unit as a whole. If you choose
Block-unit controls, then you can specify the layering individually for each block-unit.
When you change between the two options you are warned that the existing settings of layering
methods, and the refinement parameters, are reset. You given the option to say No to changing
the option.

If you say Yes, and change from Unit-wide to Block-Unit, the current settings for each unit are
copied for each block in that unit.
If you say Yes, and change from Block-unit to Unit-wide, the settings for the first block in each
unit are applied to the whole unit.
Number of layers per unit

The number of layers within a given unit are the same for all its block-units. You can set the
number of layers in the selected unit in the drop-down menu item Unit (top down numbering)
using this field. You can also change the number of layers in the unit when entering the
refinement parameters from one of the panels opened from the menu item Refine Selected
Block Unit(s).
Unit (top down numbering)

You select the unit for which to define the vertical gridding from this drop-down. The units are
listed in top down order by name.
Block(s)
If you are doing Block-unit based layering you select, from this drop-down, the block within the
unit for which to define the vertical gridding. The blocks are listed by name. If Unit-based
layering has been chosen, this drop-down is disabled.
Layering method
You have five different vertical gridding styles to choose from in this drop-down.
Proportional
The thickness of each layer within the (block) unit is a proportion of the total thickness at each
location (that is the distance between the upper and lower surfaces at that location). The relative
thickness of each layer is determined by weights.
By default, the upper surface corresponds to the upper horizon of the unit, and the lower surface
corresponds to the lower horizon of the unit. You may change both these if desired.
Top conforming (offlap)

The absolute thickness of each layer is specified, and each layer is defined relative to the base
of the layer above. The base of the topmost layer is formed by applying the specified thickness
of the topmost layer as an offset from the selected reference surface. The default for the
reference surface is the upper horizon of the unit; you may change this if desired. The lower
surface is not used.
Bottom conforming (onlap)

The absolute thickness of each layer is specified, and each layer is defined relative to the top of
the layer below. The top of the bottommost layer is formed by applying the specified thickness
of the bottommost layer as an offset from the selected reference surface. The default for the
reference surface is the lower horizon of the unit; you may change this if desired. The upper
surface is not used.
Use property model

This option allows you to specify the vertical gridding in terms of the property model layers (if
any) within the (block) unit ("Geological Property model" on page 215). The base of each layer
is defined as the base of a property model layer.

The upper and lower reference surfaces are not used by this gridding style.
Use property model parameters

This option is the same as Use Property Model, see above. If the FloGrid model is an
unstructured grid then Use Property Model Parameters is significant and different to Use
Property Model ("Generating a grid" on page 525)
Upper reference surface

If the proportional or top-conforming gridding styles have been selected, this dropdown allows
you to select the upper reference surface. For the default behavior (using the upper horizon of
the unit), leave this set to Default (top of unit).
Lower reference surface

If the proportional or bottom-conforming gridding styles have been selected, this dropdown
allows you to select the lower reference surface. For the default behavior (using the lower
horizon of the unit), leave this set to Default (bottom of unit).
Property model / scenario

If there are multiple property models or multiple scenarios, and if Use property model layering
is selected, this lets you select a property model and scenario.
Refine selected block unit(s)

Opens the panel UnitName AllBlocks (Unit-wide layering) or UnitName BlockName
(Block-unit layering) in which you define the vertical gridding parameters. The panel contains
information on the layering method and a table in which you enter the parameters. The contents
of the table corresponds to your selection of layering method.
All methods
To add a layer to the table, highlight the layer below which you want the new layer and type
Ctrl n.
To delete a layer, highlight the layer and type Ctrl d.
Refinements may also be added by clicking on the + symbol in the right corner of the panel.
Proportional
The table contains the weights for the relative thickness of each simulation layer within the
(block-)unit. The layers are listed in top down order. The thickness of an individual layer is
given by:
thickness = unit thickness * (weight / sum of weights)

In general, each layer in a top-conforming layered unit has a constant thickness. The table
contains the absolute thicknesses of each layer, again listed top down within the (block-)unit.
Since absolute thicknesses are specified, it is possible that parts of a unit are thinner than the
total thickness of all layers, or alternatively are thicker than the total thickness of all layers. If
the unit is thinner, then the simulation layers are truncated at the base of the unit. If the unit is
thicker, the program ensures that the specified number of layers fills the unit by extending the
lowest layer to the base of the unit. The latter case means that the thickness of the lowest layer
is not used within the program, and is read-only in the panel. However the full number of layers
must be present in the table for consistency.

Note A complication arises if a different upper surface has been selected in preference to the
default surface (the upper horizon of the unit). The upper surface of the topmost layer
of the generated sub layering conforms to the actual upper horizon of the unit, while
the lower surface of the topmost layer lies on the selected upper surface (if a thickness
of zero has been entered for the topmost layer) or the specified distance below it (if a
positive layer thickness has been entered for this layer) (Figure 13.1). If the selected
upper surface lies above the actual upper surface of the unit, the topmost layer is
truncated against the top of the unit.

This table is similar to the top conforming case. Simulation layers are still listed in top-down
order. However, since this option represents bottom-conforming stratigraphy, the layers are
truncated or extended if required at the top of the unit, and the first layer in the table is read-only.
Note Similar remarks apply in the case of a different lower surface having been selected in
preference to the default surface (lower surface of the unit): the upper surface of the
bottommost layer will conform to the selected lower surface (if a thickness of zero has
been entered for this layer) or lie the specified distance above it (if a positive thickness
has been entered for this layer) (Figure 13.2). If the selected lower surface lies below
the actual lower surface of the unit, the bottommost layer will be truncated against the
bottom of the unit.
Figure 13.1 Top conforming (offlap) sub-unit layering to a user-specified surface
Figure 13.2 Bottom conforming (onlap) sub-unit layering to a user-specified surface
Use property model

You enter the layer IDs of the property model layers that you want to use to define for each
simulation layer in the table. The simulation layers are listed in top down order. The base of the
selected property model forms the base of the simulation layer. The layer IDs are the unit-wide
equivalent layer IDs for the unit.

Note They are in the same order as the 3D Viewer (see "Property Model" on page 110).
Individual block-units within a unit may not contain all of the unit-wide equivalent
layer IDs. If such a layer ID is selected, then the simulation layer is pinched out in that
block-unit.
Above the table, you find some information on the layering within this (block-)unit in the
property model. For a single block property model the layering method is reported. For all
property models, the number of layers within the (block-)unit, and the ranges of valid layer IDs
for the (block-)unit are reported. You can also examine the property model in the 3D Viewer
while this panel is open, and identify which layer IDs you want to use by picking them within
the 3D Viewer.

Like the Use Property Model option, you enter the layer IDs of the property model layers that
you want to use to define for each simulation layer in the table.
Unit Thicknesses Pre-calculation

This checkbox is off by default. If you turn it on, then FloGrid reverts to the 2001A behavior,
where the unit thickness calculation is run as soon as the areal grid is regenerated.
Faults
Select how faults are to be modeled in the simulation grid:
I and J faces
Models faults as only existing between adjacent I and J grid cell faces.
If this option is selected, all grid cells within any given column (tube) are modeled as lying in
the same fault block (that is they all lie on the same side of a fault). In areas of the grid close to
faults it is not always obvious which side of the fault the column should lie. This decision is
determined by evaluating the intersections of each nearby block unit with the column to decide
which block is dominant.
This method is the default option and must always be used when building simulation grids from
maps.
It is probably not an appropriate method to use when gridding geological models with complex
structures such as those with Y faults or channel sands represented as block units.
I, J and K faces
Models faults as existing between adjacent I, J and K grid cell faces.
If this option is selected, cells within any given column are no longer constrained to all lie in the
same fault block.
This option allows you to model:
• a sloping fault on a vertical coordinate line grid by vertically zigzagging the fault
• a Y fault.
In this case you may chose to slope the coordinate lines to agree with part of the Y fault, or
zigzag the entire fault.

It is recommended that this method is used when building simulation grids from geological
models with complex structures such as those with Y faults or channel sands represented as
block units.
The ECLIPSE MULTREGT keyword must be used to export the fault location and to set
transmissibility multipliers. To do this, a MULTNUM property that defines the fault location is
required together with a table defining the valid pairs of MULTNUM regions that define each fault
(see "Autogenerate IJK fault location table" on page 418 for how to generate the table).
Coordinate lines
Controls how the slopes of the coordinate lines are constructed. The following options are
provided:
All vertical
If this option is selected, all the coordinate lines in the grid are constrained to be vertical.
Vertical boundary
Note This option is not available for fault framework-based gridding.
For control-line based gridding, all coordinate lines that do not lie on the grid boundary are
allowed to slope, based on the control line slopes defined in the Control Lines section.
Coordinate lines on the boundary are constrained to be vertical unless nearby control lines make
this impossible.
All sloping
All coordinate lines slope based on the slopes defined in the Gridding Controls section.
Note In FloGrid, rectangular grids are constrained to have vertical coordinate lines.
3D Grid
Set layering
Applies the layering defined in the layering table and creates a list of global simulation layers,
and default LGRs that apply to the entire model.
Build
Creates the geometry for the 3D global and local grids. It can be a time-consuming process.
Once a grid has been built, LGRs can be changed and the grid updated quickly from the LGR
panel (see "LGRs" on page 408). That is, the LGR grids can be added, altered and removed
without rebuilding the global grid geometry. The boundary, the control lines or the areal grid
can be changed once a grid has been built, but the grid would then have to be rebuilt to bring
everything back into a consistent state.

Note If the BLOCK property has been edited, then subsequent grid building operations
attempt to respect your choice of block for the columnar block assignment. This can
be useful if you need to move the logical location of a fault in the grid. Note that your
choice of blocks persists until the next time the areal grid is built; it is then reset. You
can force a reset by deleting the BLOCK property.

Rectangular gridding is an alternative method of creating an areal grid. Once you have created
an areal grid using this method you can use it as a basis for defining a vertical grid. See "Vertical
gridding" on page 321.
The Rectangular Gridding folder allows you to specify and edit areal rectangular grids with
constant or variable dx and dy spacing. Cartesian local grid refinement is supported. Vertical
layering is based on the reservoir units with options for subdividing units.
Grids can be defined using the fields within the folder or by using a linked editor in the 3D
Viewer.
Note Rectangular grids are constrained to have vertical coordinate lines.
Grid location
X origin, Y origin
X Y positions of the grid origin specified in the coordinate system of the property model.
Rotation angle
Angle through which the grid is rotated.
Grid boundary
I length, J length
Length of the grid along the I and J axes.
Grid dimensions
Nx, Ny
The number of grid cells along the I and J axes.
Grid spacing
Dx, Dy
Grid spacing along the I and J axes. If Variable Dx & Dy Gridding is selected, these fields show
the average Dx and Dy grid spacing.
Gridding method
For building an areal rectangular grid, three methods can be used. These are described below.
I & J length
Specifies the boundary using the grid location and grid boundary parameters, and places cells
at regular intervals using the Nx and Ny grid dimensions.

Constant Dx & Dy
Specifies the grid origin and axes rotation using the grid location parameters. Construct the grid
with Nx rows in the I axis direction each with Dx width and Ny rows in the J axis direction each
with Dy width.
Dx & Dy array
Specifies the grid origin and axes rotation using the grid location parameters. Construct the grid
with Nx rows in the I axis direction and Ny rows in the J axis direction each with Dy width. Use
the values in the Dx & Dy table to define the size of each row.
Note When an areal grid has been built using one method, it is normally possible to switch
to another gridding method. For example, a grid may be defined using variable Dx &
Dy Array spacing and subsequently switched to Constant Dx & Dy. In this case,
average values for Dx and Dy are computed, honoring the original boundary.
Areal grid
Build
Builds (or updates) the areal grid based on the parameters set in this folder. When gridding
parameters are changed, you must press this button, or the commit button in the 3D Editor, to
ensure that the changes are taken into account when the software builds the 3D grid.
Reset
Resets the areal (rectangular) grid and associated parameters, to the state they were in the last
time the edit was committed using the Build Areal Grid option.
Edit
Opens the Areal Grid Editor in the 3D Viewer.
If no areal grid has been defined when this option is selected, the Editor starts up in digitize
mode. Use the left mouse button to pick points. The first pick defines one corner of the grid, the
second pick defines a second corner along one of the axes, and the third pick defines the extent
of the model and completes the definition of a rectangular grid. The decisions on where the
origin of the grid is, and which boundaries correspond to the I and J axes, are based on the
rotation angle of the defined rectangle and the preferred position for the simulator origin (top
left or bottom left).
The Editor is controlled by a set of buttons that provide the following functionality.
Rotate Grid
Use the left mouse button to rotate the grid around the origin that is marked by a small black
square.
Translate Grid
Use the left mouse button to translate the grid.
Insert I Line
Use the left mouse button to pick an area of the grid between two existing I lines where a new
I line is required. The inserted I line is placed midway between the existing I lines.

Insert J Line
Use the left mouse button to pick an area of the grid between two existing J lines where a new
J line is required. The inserted J line is placed midway between the existing J lines.
Move Line
Use the left mouse button to select the I or a J line to be moved. Hold the mouse button down
and drag the line to the new position. A line cannot be dragged across another line in the same
direction.
Delete Line
Use the left mouse button to select the I or a J line to be deleted. If the last I line or the last J line
is deleted, the boundary shrinks accordingly.
Digitize Grid
If no areal grid has been defined when this option is selected, the editor starts up in digitize
mode. If this option is selected when an areal grid already exists, the previous areal grid will be
deleted, a new boundary is created, and gridding parameters are re-initialized.
Use the left mouse button to pick points. The first pick defines one corner of the grid, the second
pick defines a second corner along one of the axes, and the third pick defines the extent of the
model and completes the definition of a rectangular grid. The decisions on where the origin of
the grid is, and which boundaries correspond to the I and J axes, are based on the rotation angle
of the defined rectangle and the preferred position for the simulator origin (top left or bottom
left).

Data tree
Chapter 14
Introduction
You import reservoir data information into FloGrid in the form of data files. The imported data
can be grouped together and examined using the Data Tree interface. Editing of the input data
is currently not fully supported.
For further information on using the data tree see "Using the data tree" on page 334.
The data tree is displayed on the left of the main window. It displays data items and allows you
view and manipulate them. The data tree consists of a series of nodes, which represent the types
of data you can load in to FloGrid.
The data types are:
• Surfaces, see "Surfaces Data" on page 341
• and maps, see "Maps" on page 342.
• Faults, see "Faults Data" on page 360
• Wells, see "Wells Data" on page 374.
• Markers, see "Well Markers Data" on page 383.
• Logs, see "Well Logs Data" on page 386.
• Boundaries, see "Boundaries Data" on page 390.
• "Structural Frameworks Data" on page 393.
The data tree also allows you to view FloGrid Model data:
• "FloGrid Models Data" on page 396
FloGrid User Guide Data tree 333

Introduction
Using the data tree
• You can access display options and data specific functions if you click, with the right mouse
button, on any of the nodes within the data tree.
• You can open the node search tool if you right mouse click in the white space, see "Finding
Nodes" on page 338.
• You can use the +/- buttons to expand and contract the nodes.
Controlling the views

Split view
You can split the tree into two halves, each half showing its own view of the same data. This is
very useful if you want to view two parts of the tree without constantly having to scroll up and
down. You can also drag objects from one half of the tree to the other.
• To split the tree into two, click with the mouse on the little box immediately above the
tree’s vertical scrollbar. The cursor changes shape when you move the mouse over the box.
When you click on the box a horizontal line appears spanning the width of the tree, move
the mouse to the desired split point and release the mouse. The tree redraws in two halves.
• To adjust the split position click anywhere on the resize bar if on a PC or on the little box
if on Motif. Drag the mouse to the new location and release the mouse.
• To combine two split halves back into a single tree drag the resize bar to either the top or
bottom of the tree.
Hiding tree nodes

Sometimes you may wish to hide certain nodes in the tree. This allows you to remove the clutter
from the tree so that you can concentrate on only those nodes that are important for the current
task.
• To hide a node open the nodes popup menu, and choose the Hide menu option.
A new special node is created at the same level called Hidden Items as below:
Note One of these special nodes is created at each level in the tree where at least one node
has been hidden.
• To hide other nodes either select the Hide menu option as above or drag the node onto any
existing Hidden Items nodes.
If several nodes have been selected then they all get hidden.
Note It is not possible to drag a Hidden Items node onto another Hidden Items node!
334 Data tree FloGrid User Guide

Using the data tree
• To restore those nodes either double click on the Hidden Items node or open the pop-up
menu and select the Show all hidden menu option.
Navigation, selection and configuration of the tree

Keyboard navigation of tree
In general use the <UP ARROW> and <DOWN ARROW> keys to move up and down through the
tree.
Note You can only navigate through those nodes that are visible.
To expand a node with children:

• press the <RETURN> key whilst over the node or
• press the <+> key whilst over the node or
• press the <RIGHT ARROW> key whilst over the node.
To collapse a node with children:
• press the <RETURN> key whilst over the node or
• press the <-> key whilst over the node or
• press the <LEFT ARROW> key whilst over the node.
To move down a level in the tree off an expanded parent node onto the first child node:
• press the <DOWN ARROW> key or
• press the <RIGHT ARROW> key.
To move up a level in the tree off a child node up to its parent:
• press the <UP ARROW> key off the first child node or
• press the <RIGHT ARROW> key off any of the children.
To expand all of a nodes children:
• press the <*> key whilst over a node with children.
To collapse all of a nodes children:
• press the </> key whilst over a node with children.
To tick/untick a node:
• press the <SPACE> key whilst over the node.
Multiple selection of nodes

To select a single node click with the left mouse button over the node (but not over the tickbox
or expand/collapse box). All other selections are lost.
To add to, or remove from, a selection hold down the <Ctrl> key whilst clicking with the left
mouse button. This toggles the selected state of the node under the mouse.

Using the data tree
To select a group of nodes hold down the <Shift> key whilst clicking with the left mouse
button. This selects all nodes between the previously selected node and the node under the
mouse.
Note The <Shift> modifier only works on nodes at the same depth in the tree. If you want
to select multiple nodes at different depths in the tree then the only way to do this is by
using the <Ctrl> modifier as described above.
Note Selecting multiple nodes can only be performed with the mouse and not the keyboard.
Adding/Removing Objects to/from the View

Those objects that can be displayed in the view have a tickbox displayed next to the node.
There are three ways of adding objects to the view:
• Click with the mouse over the tickbox. A tick should appear to show that the object is in
the view .
• To remove the object from the view click again over the tickbox.
• Select the nodes you want to add into the view and then open one of these node’s pop-up
menu. There should be two menu items, Add to view and Remove from view. Select the
appropriate menu option.
• Select the nodes you want to add into the view and then click on one of these nodes and
drag it into the 3D Viewer.
Note the following:
• At all times the ticked state of each nodes tickbox should reflect whether the object
associated with the node is displayed in the view.
Ticking on a parent node adds/removes all its children to/from the view.
If the children of a parent node are not all in the same state (ticked or unticked) then the
parent nodes tickbox is drawn with a highlighted background. If the child nodes are
collapsed, this allows you to see, by looking at the parent node, whether all the children are
all added to the view , all removed from the view or only some in the view .
• Some nodes’ tickboxes are displayed with rounded edges . This indicates that this node
and its siblings are acting like a radio button group. Only one of the nodes may be selected
and thus added into the view at any one time. The currently selected node is show by having
a circle in the middle of it .
• Some tickboxes are shown with a border drawn in the disabled color. This means that,
although you can switch off the node thus removing its items from the view, you cannot
switch the node on. These types of tickboxes are usually used where it does not make sense
to be able to add all the children of a node to the view in one go. The Add to view menu
item of the nodes popup menu are also disabled and it is not possible to drag the node into
the 3D Viewer.
• To remove all the objects from the view in one go click on the button in the top right
toolbar.

Using the data tree
Configuring the visual appearance of objects in
the view
Each object in the view represented by a node in the tree has a Visualization Settings option
on its pop up menu. Provided the object has been added to the view this option opens a modeless
panel containing two lists and a checkbox.
• Use the Render Mode and Level of detail lists to change the way the object is displayed.
You can only select one entry in each list.
The checkbox determines whether the object is hidden or visible. The panel automatically
closes if the object it refers to is removed from the view.
Selecting nodes in the tree using the 3D Viewer

If you click using the left mouse button in the 3D Viewer whilst over any object the associated
node in the tree should be selected. Multiple selections can be made by holding down the
<Ctrl> key whilst clicking with the left mouse button in the 3D Viewer. This toggles the
selection of the associated tree node.
Holding down the <Ctrl> key whilst clicking with the right mouse button in the 3D Viewer
not only selects the associated node in the tree but displays its popup menu at the current mouse
position. This is an extremely useful way of performing operations on objects in the 3D Viewer.
However it is not very intuitive to hold down the <Ctrl> key whilst clicking with the right
mouse button since the normal way to invoke pop up menus is to simply right click. This
possesses problems in the 3D Viewer though as right clicks have already been reserved for
translate operations. The code has thus been written such that it intelligently determines whether
you want to translate the object or invoke its pop up menu. If this intelligent behavior causes
problems then it can be switched off using the following configuration file setting:
SECTION FLOGRID
SUBSECT TREE
ENHANCED3DPICK FALSE
Note The associated node is selected but the tree does not automatically scroll the selected
node into view.
Docking/UnDocking Data Tree

The data tree can be docked/undocked from the main FloGrid window by one of:
• Selecting the Node Tree Docked option from the Window menu of the main window.
• Clicking on the button in the top right toolbar.

The advantages of undocking the data tree are that it can now be sized independently of the main
window. It can also be minimized if not needed. However this operation really comes into it’s
own on a dual head machine. The data tree can be placed onto one of the screens and the main
window containing the 3D Viewer can be placed in the other.

Using the data tree
When the tree is undocked for the first time it attempts to position itself to the left of the main
window. If the main window is maximized then the tree is positioned on the left hand side of
the screen. Its height remains same as the main window and its width is preserved. When it is
subsequently re-docked its width inside the main window is preserved. When the tree is docked
its undocked position and size is remembered for the next time it is undocked.
Note The data tree automatically re-docks if a new workspace is requested.
Finding Nodes
The data tree can contain a large amount of data and it is sometimes difficult to locate the node
that you want. A node search facility has been written to allow you to select or move to nodes
matching a pattern based on the nodes labels. Use one of the two following to invoke the node
search facility:
• Select Find Node from the Data Tree’s pop up menu.
Hint If the mouse is over a node then use Ctrl-right-click, otherwise you open the node’s
pop up menu instead.
• Click on the button in the top right toolbar.

The Node Finder consists of the following options:
• an edit field for typing the search pattern matching the node labels to be located;
• a set of check boxes to determine the search behavior.
• two radio buttons to determine the selection behavior.
• a status counter indicating the number of nodes found (the nodes whose label matches the
search pattern);
• a table listing the labels of the located nodes (one entry per node);
• a set of control buttons.
Search Pattern
The search pattern consists of a string containing plain text and any number of instances of the
following special characters:
• ‘*’ to indicate zero or more instances of any ASCII character
• ‘?’ to indicate exactly one instance of any ASCII character.
Search Pattern Edit field

The Search Pattern Edit field maintains a history of all patterns searched for. You can display
this list using the drop-down button on the right side of the edit field. This enables you to repeat
old searches, possibly modifying them first.

Using the data tree
Check Boxes
There are two check boxes on the dialog. The first one, if ticked, sets the search to be case
sensitive. The second one, if ticked, sets whether the search results are alphabetically sorted.
Radio Buttons
There are two radio buttons on the dialog. They determine what happens when you select
something from the list underneath.
Move to node
• If the radio button is set to Move to node then the selected node is brought into view.
Parent nodes are expanded if necessary. The current selection is unaffected.
Select node(s)
• If the radio button is set to Select node(s) then the node is only selected. The current
expanded/collapsed state of the node tree is unaffected. It therefore may be the case that
you do not actually see the selection even though it has taken place.
Status counter
The Status Counter shows, at all times, the number of nodes found. It also indicates the
number of entries in the table underneath.
Control buttons
• To search the node tree for nodes matching the pattern press the Search button. The search
can be carried out in two modes: AutoSearch On and AutoSearch Off.
Hint It is possible to toggle between the two modes from the pop-up menu displayed from
the right mouse button.
AutoSearch On
When AutoSearch is On the Search button is disabled and a new search automatically takes
place whenever the content of the edit field is modified.
Autosearch Off
If AutoSearch is Off the Search button is active and a search is started only after the button is
pressed with the left mouse button.
Clearing searches
• To clear the search pattern in the edit field and clear all the search results press the Reset
button.
Retrieving a node
• To retrieve a node, click on the table entry containing its label. The tree’s behavior is
determined by the state of the radio buttons.

Using the data tree
When two or more nodes (in the same search context) carry the same label, the table
contains one entry for each node: all duplicate labels have the tag (press n) (with n = 2, 3,
4...) appended to their corresponding entry.
Clicking on a different tagged entry causes the retrieval of a different node.

Using the data tree
Surfaces Data
Introduction
Two distinct categories of maps can be imported into the surfaces tree: mesh maps and contour
maps.
Data editing facilities are also provided. These options are currently restricted to creating and
editing: mesh maps, fault traces and polygons in the 3D Viewer.
The Surfaces node contains several menu options to import various formats of scatter sets,
mesh maps and contour maps.
• "Surface Data" on page 341.
• "Maps" on page 342.
• "Mesh Map Data" on page 347.
• "Contour maps" on page 350.
• "Contour Map Data" on page 352.
• "Scatter Sets" on page 353.
• "Unassigned Maps Node" on page 355.
• "Surface table" on page 356.
• "Create Simple Mesh Map" on page 357.
• "Export as Generic" on page 359.
Surface Data
The Surface node contains one or more map nodes. Surfaces are always ordered depositionally,
with the most recently formed geological surface at the top.
Different functionality is available at different levels in the tree. It is accessed by selecting one
or more of the nodes and then using the right mouse button to bring up an appropriate pop-up
menu.
Surface options
You can display the Surface Options pop-up menu by holding the right mouse button down
over one of the selected nodes: this includes facility for surface visualization (that is visualizing
mesh and contour maps associated to that surface) and for the selections of associated well
markers.

Surfaces Data
Maps
The Surface tree provides facilities for visualizing, classifying and managing contour map,
mesh map and surface data. Information entered in this folder is used to help automate the
process of building structural and property models from which simulation models are then built.
Most functions are available using pop-up menu options on the Surface and Map nodes.
Certain functions are also available using the Surface Table.
One of the main roles of the map and surface trees is to provide a quick way to assign maps to
a given surface. Maps may be assigned to a given surface by selecting the node which represents
them and dragging the mouse onto the required surface node.
Pop-up functionality (in most cases) and the assignment of maps to surfaces using drag and drop
can be applied to multiple nodes in one operation. This is done by selecting multiple nodes using
either Ctrl or Shift selection as required.
Note The Unassigned Maps node is populated with both mesh and contour map nodes that
have not yet been assigned to any surface. Nodes corresponding to contour maps are
labeled with the tag [Contour]: prepended to the map property and name. Unless
differently specified, any reference to a Map Node is intended as a reference to a node
representing either a mesh or a contour map.
Note Mesh maps, Contour Maps and Scatter Sets can be imported into FloGrid either from
the popup menu of the Surfaces Tree or by selecting the appropriate entry in the
cascade pull-down File | Import from the main window.
Mesh maps
A mesh map file contains data values represented on a regular grid mesh.
Mesh map attributes and formats

Each map has a set of attributes that describe how the data are organized. Map attributes and
input file formats are described in "Mesh Map Data" on page 781.
Mesh map types

Maps are divided into three basic types - surface, thickness, and property.
Surface and thickness maps define structure. Surface maps can be horizons or unconformities.
For further information on the interaction of mesh nodes and surfaces see "Construction of Units
and Horizons from Mesh Maps" on page 757.
Surface map
A surface map is a 2-D array of depth/height values. Surface maps are used primarily in the
construction of structural models from which property models and ultimately simulation models
are constructed.

Surfaces Data
Thickness map
A thickness map contains thickness values that are added to a reference grid surface to produce
a new surface. The reference surface used in the process is called Th. Reference.
Note A thickness map surface can be defined based on another thickness map as long as the
reference eventually resolves to a surface map.
Property map
A property map describes the property values of a unit.
Property maps can be assigned explicitly to units in the Property Model module. When
property maps are assigned to units in the property model, the process must be repeated each
time a new property model is created.
Alternatively, property maps can be assigned to surfaces in the main window surfaces tree.
Where surfaces have been created and numbered from top to bottom, property maps assigned
to a surface represent the properties immediately below that surface (that is properties in the unit
bounded above by that surface). Similarly, for a bottom up model, property maps assigned to a
surface represent properties above that surface. Properties assigned in this way are available in
all map-based property models.
Importing mesh maps

To import mesh maps of a given type, select the appropriate menu option. This opens a multi-
file selection dialog. One or more mesh maps can be imported by navigating to the desired
directory and selecting the required mesh map files using the appropriate use of Shift / Ctrl
selections.
The supported mesh map file formats are described below.
Generic
This is a formatted text file containing the mesh map dimensions (nx, ny) and nx*ny values,
where nx represents the number of columns and ny the number of rows (see Set Import control
panel for details). There can only be one structural or property map per file.
CPS1 (SAVE)
This is a binary SAVE file from the CPS mapping program. This format requires additional
control file information such as map dimensions and null value. See "Set import controls panel"
on page 346. There can only be only one structural or property map per file.
CPS3 (SVS)
This is a binary file in CPS-3 (SVS) format. There can only be one structural or property map
per file. All information except map units is stored in the binary file. If units are not specified
in Set Import Controls, FloGrid uses the current External Units System defined in
Preferences | Set External Units.

Surfaces Data
IRAP
This is a binary file exported from IRAP containing multiple mesh maps. This format is referred
to as the Binary Irap Classic multi grid format. Normally, this file has an extension of .lay.
This is not mandatory.
Each kind of mesh map (structure, porosity, permeability, etc.) must be loaded as a separate file.
A suitable null value must be defined in Set Import Controls.
Note It is strongly recommended that all structure maps for a model are imported in a single
file. If this is done, FloGrid can be requested to automatically define the correct
number of surfaces and assign structure mesh maps to the correct surfaces. Similarly,
all the property maps of a given type should be loaded in a single file, once structure
maps have been imported and surfaces created. If this is done, FloGrid can be
requested to automatically assign property maps to appropriate surfaces.
The following information has been supplied by Roxar to assist users wishing to export a Binary
Irap Classic multi grid file from IRAP. The instructions cover how to export a set of horizons.
Note You need a set of horizons in RMS, so you need at least one horizon in your horizon
container.
1 Export the horizons to Binary Irap Classic multi grid.

2 Click on the Horizons icon menu | Export | Binary Irap Classic multi grid...
3 Enter a name and click OK.
Note Note that all available horizons are exported, that is all horizons in the horizons
container; it is not possible to make a selection.
4 To quality control the exported file, you can import the file back into RMS. Use the
following option: Horizons button menu | Import | Binary Irap Classic multi grid...
ZMAP
This is an ASCII export file from the ZMAP mapping program.
Once the selection phase is over, by choosing OK all the selected property maps populates the
Mesh Map Import panel (common to all mesh map formats supported by FloGrid) described
below.
Mesh map import panel

Once one or more files have been chosen, a panel labeled Mesh Map Import appears with a list
of mesh maps selected for importing. The data are not loaded until the OK button is chosen. This
panel gives you several options.
Another file
This button opens the file selection window again to allow more maps to be loaded.

Surfaces Data
Create surface
This option allows you to define the structural surfaces that are to be modeled in the main
window tree. Surfaces can be represented by horizon, thickness and unconformity maps. See
"Construction of Units and Horizons from Mesh Maps" on page 757 for more information about
the different kinds of surface maps.
Selecting the Create Surface button displays the Surfaces to Create panel.
Surfaces to create
Number of surfaces required

This integer defines the number of distinct surfaces to be modeled. Typically it is one greater
than the number of units to be modeled. If there are alternative map representations for any
surface, such as different horizon maps for a given surface, the surface should only be counted
once and both maps should be assigned to the same surface.
Note When you construct a structural framework you can select one, and only one,
representation of each surface.
Number surfaces from bottom to top or from top to bottom

Surfaces may be numbered and created from top to bottom or from bottom to top. When
property maps are assigned to a model numbered from the top to bottom, property maps
assigned to a surface represent the properties immediately below that surface (that is properties
in the unit bounded above by that surface). Similarly, for a bottom up model, property maps
assigned to a surface represent properties above that surface.
Confirmation (OK) displays a further panel called Surface Names. This panel contains a table
with a list of default surface names and options to create further surfaces and delete existing
ones. Default names can be over-written by typing over the default names.
Mesh map import panel table

The Mesh Map Import panel contains a table with the following columns:
Location (1st column left)

For map data resident on flat files, this shows the path name of the map files to be imported.
Name
Map names are taken from the imported file name. This name may be changed by typing a new
one in the column labeled Name.
Note It is possible to import copies of a mesh map in one single import transaction by re-
loading the same file using the Another File button and changing the map name in the
Name column.
Surface
Surfaces are first created with the Create Surface option. To assign imported maps to a
surface, use the drop-down fields under Surface. Several maps can be assigned to the same
surface.

Surfaces Data
Property
Use the Property drop-down field to select a FloGrid property type for the map
Note It is easier to assign surfaces and properties to maps using the Surface and Map Trees
in the main window once the maps have already been loaded. This is explained below.
Th. Reference
When thickness maps are assigned to a surface, Z values for that surface are computed by
default by adding or subtracting the map thickness values to the computed Z values of the
surface immediately above or below depending on whether the model is built top down or
bottom up. If this logic is not appropriate, for example all thickness maps define a thickness
from a single surface, the Th. Reference field should be used to select which surface the
thickness map should be added to or subtracted from.
Import?
If a map is unintentionally selected for import or it is part of a set of maps selected in a single
transaction, it can be de-selected by setting the corresponding field under Import? to No.
Edit
The Edit button opens the Set Import Controls panel to allow customizing of the import
parameters before reading a data file. This option can affect a single map or all maps selected
for import. Use the selection box labeled Map controls to edit to choose the maps to use in Set
Import Controls.
Set import controls panel

Sets one or more map import options. Because each file format has different amounts of
information in the header you have to enter different types of information for each map format.
This ranges from specifying the null value to which way the axes are defined and where the
origin is. Depending on which import format is chosen, some of the entries for control
parameters are disabled. Disabled entries indicate that these values are defined in the header (or
not needed).
Note The entries shown in the panel when it is first displayed are default values and are not
based on data in the file(s). This is because the file has not yet been read so these values
are unknown.
Read/Write
When parameters are defined for import controls, they may be saved to an external disk file with
the Write button. The file can be used later to import other maps with the Read button.
Number of X, Y nodes
These parameters specify the number of nodes in the X and Y dimension.
Null value
This is the value used to identify null numbers in the map file. When using the Generic, CPS1,
and IRAP map formats the null value needs to be defined.

Surfaces Data
Hint In some cases you may not know the null value. A handy trick is to import the map
without specifying the null value and examine the range of imported data values using
the Show Information pop up menu option on the Map Tree to display the minimum
and maximum values for that map. The null value is typically the largest number in the
range. The map can then be deleted and reloaded using the correct null value.
IJ origin
This parameter defines how the data are organized in the file. Top Left indicates that the first
point in the file represents the top left corner of the map. Bottom Left indicates that the first
point in the file represents the bottom left corner of the map. The position of the map’s second
point is defined by the parameter Row or Column Major.
Row or column major

This specifies whether the map values are organized in rows or columns (for example, j or i
values varying fastest).
• If Column Major is selected, the second point in the disk file represents a point down the
first column (if Top Left is selected) or up the first column (if Bottom Left is selected) of
the map.
• If Row Major is selected, the second point in the disk file represents a point along the first
row of the map.
Axis template
The axis orientation is specified by selecting one of the eight corners of the cube.
Z rotation
Use the angle slide bar to specify the Z-axis rotation.
Areal, vertical unit

These parameters specify the aereal and vertical map units. By default these units are set to the
current external unit system set from the main FloGrid window under Preferences | Set
External Units.
X, Y origin
This defines the X and Y location of the map origin.
X, Y maximum
This defines the maximum X and Y extents of the map data.
OK
After all the map files are selected, use this button to start the import process.
Mesh Map Data

Most map options, activated from the popup menu, can be applied to multiple maps.

Surfaces Data
Caution Some only make sense for a single map. If multiple maps are selected for a single
map option such as Show Map Information, an error message is displayed.
The chosen operation from the Map Option is applied to all selected nodes. Some options are
different or not applicable depending on whether the option is applied to a mesh map or a
contour map.
Mesh map data options

Show Information
This option displays the Map Information panel. It can be used to check if a mesh map has
been imported properly. The map parameters displayed are:
• Number of X, Y nodes.
• Null value.
• Minimum, and maximum values in each dimension, X, Y, Z.
Values are displayed in the external units that were active when the panel was opened.
• Raw Z value at node.
This is the value stored in the original map file at the X Y node selected using the slider
bars beneath.
Note Raw Z values are not converted to external units.
Visualization Settings
Note This option applies to one map at a time.
This panel allows you to change the way the selected mesh maps are rendered in the 3D Viewer.
The Render Mode affects the map appearance and consists of a combination of these modes:
• Surface
The map appears colored according to the property it represents (if enabled, a color legend
appears in the 3D Viewer).
• Lines
The map is rendered as a white mesh.
• Solid Colored Surface
The map appears in the same color as the node of the surface to which the map is assigned.
If the map is Unassigned the default Peach color is used.
The Level Of Detail affects the accuracy of the map visualization.
• By choosing all the entire set of available data is used.
• Any other value decimates the data prior to rendering (the higher the value, the lower the
decimation - hence the higher the quality).
It is also possible to hide/show the mesh map using the Visible check-box.

Surfaces Data
Edit
Note This option applies to one map at a time.
Mesh maps can be edited in the 3D Viewer

See "Mesh Maps" on page 110
Change coord system

This option displays the Edit Coordinate System panel.
It is used to specify the Z rotation, the orientation and the units of the axes, and the mesh map
origin.
Set property
Displays the Set Map Property panel.
It is used to set the property type of the selected mesh maps. It can be used to classify structural
mesh maps as horizons, unconformities or thickness maps and to classify property mesh maps
according to the type of property they are representing (porosity, permeability, etc.). Choose a
property type from the selections provided in the list.
Set property unit

Displays the Set Map Unit panel.
It is used to change the Z value (property) units of the map.
Note It does not change the X and Y units for the mesh map.
Set null intepretation
Note This option can only be invoked on thickness mesh maps.
It displays the Interpret Map Null dialog and allows the null interpretation be set to one of two
ways:
• treats null values as zero,
• searches for the nearest non-null value whenever a null value is encountered.
Hint The pre-processing of the mesh maps alleviates the problem of having to actually
perform a search during a run.
Mesh Map Calculator

See "Expression Calculator" on page 687 for details.
Export Selected Maps as Generic...

A mesh map, irrespective of its format when it was originally imported/created, can always be
exported in generic format. See "Export as Generic" on page 359 for details.

Surfaces Data
Contour maps
Contour maps consist of a set of scalar values represented on lines in space.
Contour map attributes

A contour map is characterized by a geometry and a property.
A contour geometry consists of a set of contour lines (2D or 3D lines, either open or closed)
with a unique scalar property value associated to each line.
Units of measurement for both the contour geometry and its property must be present in the
contour data file (irrespective of its format).
Other parameters such as:
• Angle of rotation (decimal degrees, anticlockwise, positive from X-axis)
• Position of origin
• Axis template (orientation of the axes (X, Y, Z), top, bottom, left or right)
are defaulted.
Contour map formats

Currently, contour maps can only be imported using the Generic option, which uses a control
file approach to define the format and location of the contour files to be imported. See "Import
Contour Maps" on page 351.
Contour map visualization

Contour maps can represent structural or property information. Typically, contour maps consist
of sets of XY lines and a structure or property value for each line. 3D contour maps consist of
sets of XYZ lines and a structure or, more often, a property value for each line.
How a contour map is visualized depends on whether it is a structure or property map and
whether the contours are 2D or 3D lines.
Visualization of 2D structural contours

2D structural contours are displayed in the 3D Viewer as 3D lines with Z values equal to the
contour value for that line. Lines are colored according to the value of the contour.
Visualization of 2D property contours

2D property contours are displayed in the 3D Viewer as 2D lines drawn at the visualization
datum plane. Lines are colored according to the value of the contour.
Visualization of 3D structural and property contours

3D structural and property contours are displayed in the 3D Viewer as 3D lines using the XYZ
values of points on each line. Lines are colored according to the value of the contour.
This data is subsequently used in downstream modules. Options include:
• assigning maps to be of a specific type (for example, porosity, permeability, horizon)
• setting or changing map units and coordinate systems

Surfaces Data
• creating simple mesh maps
• creating surfaces representing top, bottom and intermediate layers and placing them in
geological order
Note Use of this information is critical in the automation of the construction of reservoir
units (strata) and a subsequent 3D structural framework.
• assigning maps to a particular surface (for example, stating which maps represent top,
bottom and intermediate layers)
• assigning thickness mesh maps to the surfaces which they represent
• assigning fault traces to particular surfaces.
Note Although it is possible to assign contour maps to a surface, contours do not take part
in the determination of reservoir units (strata) used in the construction of a 3D
structural framework. FloGrid supports contours either for visualization purposes or
for digitizing fault traces, boundaries and control lines.
Import Contour Maps

The Import | Contour Maps option provides a method to import contour map files into
FloGrid. Currently, contour maps can only be imported using the Generic option, which uses a
control file approach to define the format and location of the contours to be imported. You can
select in the browser the control file, which describes the format (Control file approach) or try
to define the format in a interactive way (Interactive approach) by selecting the data file.
Note Although the interactive approach offers a more immediate workflow there are formats
that can only be imported with the aid of a control file.
Interactive approach
You need to have data organized in 3 or 4 columns with no text between contours. If a file is
readable by this approach FloGrid loads a panel that allows you to define the format you want
to use.
This option supports column formatted text files in which each column represents a property or
an identifier and each line defines one element of the contour. Typically, column 1 and 2
represents the x, y location of the contour point column 3 represents a property measured at that
location. For example:
X Y Property1
--------------------------------------------------------------------
79.0247 6500 3016
100 6489.12 3016
200 6431.25 3016
245.326 6400 3016
300 6352.73 3016
352.508 6300 3016
To properly read the file format you need to specify:

Surfaces Data
• the number of header lines, these are lines with relevant information but not part of the data
set, that is, comment or description lines.
• the property defined by each column, these are pull down list from which the user can select
what each column represents, (that is column 1 contains the x coordinate, column 2 the y
coordinate, column 3 the porosity measured at that location, etc.).
• whether there is a separator between each contour line.
• if a column serves as contour identifier by setting it to ID Value.
• in the Contour Set Information table the name of the contour, the measured property units,
the surface associated with the contour and whether to load the set or not can be specified.
Upon pressing OK the contours are loaded in FloGrid.
Note The following values are not valid property values: Ignore, X (Structure), Y
(Structure), Z (Structure) and ID Value - if any is selected, import is refused.
Control file approach

Contour map files are imported through the selection of control files. A control file is a text file
(typically created in a text editor) that describes the format and locations of contour map files.
For further information see "Contour Map Control files" on page 774.
Contour Map Data

Most map options, activated from the popup menu, can be applied to multiple maps. Some only
make sense for a single map. If multiple maps are selected for a single map option such as Show
Map Information, an error message is displayed.
The chosen operation from the Map Option is applied to all selected nodes. Some options are
different or not applicable depending on whether the option is applied to a mesh map or a
contour map.
Contour map data options

Show information
Displays the Map Information panel. It can be used to check if a contour map has been
imported properly. The map parameters displayed are:
• Number of contour lines.
• Minimum, and maximum values in each dimension, (X, Y for 2D contour maps and X, Y,
Z for 3D contour maps).
Values are displayed in the External Units which were active when the panel was brought
up.
• Minimum and maximum value of the property associated to the contour map (Level
Value).
• Raw Contour Line Value.
This is the property value associated to the n-th contour line (as loaded from the contour
map file) selected using the slider bar beneath (Contour Line Number).

Surfaces Data
Note Values are not converted to external units.
Change coord system

Displays the Edit Coordinate System panel.
It is used to specify the Z rotation, the orientation and the units of the axes, and the contour map
origin.
Set property
Displays the Set Map Property panel. It is used to set the property type of the selected contour
maps. It can be used to classify structural contour maps as horizons or unconformities and to
classify property contour maps according to the type of property they are representing (porosity,
permeability, etc.). Choose a property type from the selections provided in the list.
Set property unit

Displays the Set Map Unit panel. It is used to change the property units of the contour map.
Note It does not change the geometry units of the contour map.
Set null intepretation
Note This option is not applicable on contour maps (as the Thickness property is not
supported).
Export Selected Maps as Generic...

A contour map, irrespective of how it was originally imported, can always be exported in
generic format - See "Export as Generic" on page 359 for details.
Scatter Sets
You can import Scatter sets into FloGrid in a generic ASCII format, by selecting the File |
Import | Scatter Sets. You can select multiple files for import, for further information see
"Scatter sets data" on page 783.
This option supports column formatted text files in which each column represents a property
and each line defines one element of the scatter. Typically, column 1, 2 and 3 represent the x, y
and z location of the scatter point and columns 4 and above represent a property measured at
that location.
Scatter Settings
Opens the Scatter Set Information dialog in which you can specify the name of the scatter, the
property measured, the units, the surface associated with the scatter and whether to load the
scatter.

Surfaces Data
Edit
You can set the coordinate system and distance units by pressing the Edit button.
3D/4D
Allows you to specify the dimension of your scatter. FloGrid cannot import scatter with an other
dimension.
OK
Pressing OK loads the scatter set(s) in FloGrid.
Notes
• For 4D scatter: The following values are not valid property values: Ignore, X (Structure),
Y (Structure), Z (Structure), if any are selected, import is refused.
• For 3D scatter: The following values are not valid property values: Ignore, X (Structure),
Y (Structure), if any are selected, import is refused. Z (Structure) is converted into the
Horizon property.
• A file that contains columns of textual identifiers (that is similar to well markers) is
considered as invalid: only numerical columns (below the header) are permitted.
• OK is disabled until the scatter settings are set.
Scatter set data options
Show information
Displays the Scatter Set Information panel and can be used to check if a scatter set has been
properly imported. The scatter set parameters displayed are:
• Number of scatter points.
• Minimum, and maximum values in each dimension, (X, Y and Z).
Values are displayed in the External Units which were active when the panel was brought
up.
• Minimum and maximum value of the property associated to the scatter set
Set property
Displays the Set Map Property panel. It is used to set the property type of the selected scatter
sets. It can be used to classify structural scatter sets as horizons or unconformities and to classify
property scatter sets according to the type of property they are representing (porosity,
permeability, etc.). Choose a property type from the selections provided in the list.
Set property unit

Displays the Set Map Unit panel. It is used to change the property units of the scatter set.
Note It does not change the geometry units of the scatter set.

Surfaces Data
Export Selected Scatter as Generic...
Scatter sets can be exported in generic format.
See "Export as Generic" on page 359 for details.
Unassigned Maps Node

This node collects each unassigned map, either mesh, scatter or contour.
The functionality available under this tree from the map nodes pop-up menu is identical to that
available from map nodes when they populate the Surface node.
All imported maps that have not yet been assigned to a surface are grouped together under this
node. Each mesh map is labeled with its property type and the name given at import. A scatter
set carries the tag [Scatter]: prepended to its property and name whereas a contour map carries
the tag [Contour]: in a similar position. A property type of Unknown indicates that no property
type has yet been defined for the map.
Hint Mesh map nodes precede contour map nodes, which in turn proceed scatter set nodes
in the Unassigned Maps node.
Assigning maps to a surface

To assign one or more maps (either contour, scatter or mesh) to a surface, select the required
map nodes and drag them onto the node representing the desired surface in the Surface node.
in the determination of reservoir units (strata) used in the construction of a 3D
structural framework. FloGrid supports contours either for visualization purposes or
for digitizing fault traces, boundaries and control lines.
Data editing facilities are also provided:

• Dragging a map from the Unassigned Maps to a surface assigns that map to the surface.
If the map is a structural mesh map (horizon, unconformity or thickness) it is used to
construct the appropriate surfaces in the structural framework and ultimately the simulation
model.
If the mesh map is a property map (that is porosity, permeability and so on) it is used in the
property model and ultimately the simulation model to define property values above or
below that surface until a new surface and set of property maps is encountered. Property
values apply below the surface if surfaces are created top down and above the surface if
surfaces are created bottom up.
• Dragging a map from one surface to another surface re-assigns the map to the destination
surface.
• Dragging from a surface to the Unassigned Maps unassigns the map.
Hint Multiple maps can be chosen and dragged at the same time. To choose multiple maps,
click on the first map then hold the Ctrl key down on the keyboard and click on the
required maps to highlight them.

Surfaces Data
When several maps are highlighted, they can all be moved or manipulated together.
Alternatively if the maps to be assigned are adjacent in the tree, they can be selected by picking
the first map node and then the last node using Shift select. This selects all nodes between.
Surface table
The Surface Table (accessed from the popup menu of the Surfaces node) provides the
following facilities for manipulating surfaces:
• creating, deleting and renaming surfaces
• setting the property types of maps
• assigning reference surfaces to which thickness mesh maps should be added to construct
new surfaces.
• creating simple mesh maps
Surfaces in the table are in depositional order, with the youngest (shallowest) surface at the top
of the list and the oldest (deepest) one at the bottom of the list.
Multiple structure maps assigned to a surface

Multiple alternative structure maps can be assigned to any surface in the surface tree. However,
when a structural framework is constructed, only one structure map can be used. The choice can
be different for each structural framework and it can be made prior to building units.
in the determination of reservoir units (strata) used in the construction of 3D structural
framework. Currently, FloGrid supports contours for visualization purposes only.
Surface ordering
A surface can either be above or below another surface. Above means it is depositionally
younger, below means it is older. The main window surface tree displays surfaces in
depositional order.
A top-down model means that surface n is younger than surface n+1. A bottom-up model means
that surface n is older than surface n+1. The surface table allows a surface to be numbered
according to whether a top-down or a bottom-up model is defined.
Map display / datum plane

Surface maps can be visualized in the 3D Viewer using the 3D values of the map. However,
there are no Z values associated with thickness and property maps. Therefore, they can only be
visualized by projecting them onto a Z plane. The Z plane created by the program for this
purpose is called the datum plane. It is defined at 10% above the highest surface map. The datum
plane is updated automatically as each surface map is imported to (or removed from) the
program.
Select
Select a surface to be deleted or to select a position below or above which a new surface is to
be added. Surfaces are numbered in depositional order, starting with the oldest surface.
• Highlight the Select number to select a surface.

Surfaces Data
Surface
Displays the surface name. Type over the name to change the name of the surface.
Color
Changes the color associated to the Surface (that is the color of the surface node)
Map
Displays the maps assigned to the surface.
Property
Displays the map property type. Change the type by selecting a different entry from the drop-
down menu.
Th. Reference
Note This only applies to thickness mesh maps.
Location
Displays the path name of the imported map file.
Vendor
Displays which map format was selected for the input file.
Add above
Adds a surface above the highlighted Select value. If no entry is selected, the surface is added
to the top.
Add below
Adds a surface below the highlighted Select value. If no entry is selected, the surface is added
to the bottom.
Create map
Opens the Create Simple Mesh Map panel where you can generate simple mesh maps. See
"Create Simple Mesh Map" on page 357.
Create Simple Mesh Map

The Create Simple Mesh Map panel provides facilities to generate simple mesh maps from a
user supplied matrix.

Surfaces Data
Map details
This section allows you to specify the map name, property and units.
Map name
A default map name is suggested, of the form mapXXX, where XXX is a number that makes the
map name unique among the existing maps. You are free to enter a different name; if the name
of an existing map is entered then the new map overwrites the existing map of the same name
(you are prompted to confirm this action though).
Property type
You can select the property type associated to the map.
Units
You can select the units associated with the new map; the numbers entered in the matrix are
assumed to be in these units.
Data organization
Specifies how the mesh map data is arranged.
Number of X nodes
Specifies the X-dimension of the nodes matrix.
Number of Y nodes
Specifies the Y-dimension of the nodes matrix.
Note The X and Y dimensions are limited to between 2 and 100. If you want to enter a larger
matrix than this then you should think about importing the data from an external
source. A mesh map requires a minimum of four nodes (to define the map corners)
hence the requirement for a minimum of 2 nodes in each dimension.
Map controls
Opens the Set Import Controls panel where you can specify such attributes as the orientation,
origin and extents of the mesh map. It is the very similar to the Set Import Controls panel used
when importing external mesh maps. See "Set import controls panel" on page 346.
Set all to value

You can enter a value here and then click the Apply button to initialize the nodes matrix to a
constant value.
Caution This feature overwrites any existing values you may have entered in the Nodes
table.

Surfaces Data
Map data
Specifies the actual Z-values of the nodes used to create the mesh map. The organization of the
data depends on the settings in the Set Import Controls panel (see "Map controls" on
page 358).
• if the data organization is Column Major (the default) then Y-indices are defined by the
columns and X-indices are defined by the rows; if the data organization is Row Major then
the meaning of the rows and columns is reversed.
• if the data organization specifies Top Left IJ Origin then the row indices increase from top
to bottom; for Bottom Left the row indices are reversed.
Create
The Create button generates a mesh map using the data specified in the panel. The new map
appears under the Unassigned Maps section of the surfaces tree and can then be used in the
same way as any other mesh map.
The Create Simple Mesh Map panel remains open to allow you to quickly create a new map
by just modifying the data already entered; to close the panel press the Cancel button.
Hint If you override the default map name with some other name, then they can quickly
develop their maps by repeatedly modifying the data, pressing Create and confirming
the prompt to overwrite the previous map.
Export as Generic
Scatter set, mesh and contour map data can be exported in generic format (irrespective of the
format when the data were originally imported) by choosing the appropriate option from the
node popup menu.
You are prompted for an output location and the name entered is used as a stem for the
generation of two output files:
• XXX.gct and XXX.ctl for mesh maps
• XXX.dat and XXX.ctl for contours and scatter sets
where XXX is the name entered.
The .gct/.dat file contains the exported data and .ctl the controls to be used when re-
importing the exported data (obviously by choosing the data type specific Import option and
Generic... format from the Surfaces top node).
When re-importing the data, the .gct/.dat file is selected first and, if the operation is
successful,- the type specific import panel is shown. At this stage the Edit button displays the
Set Import Controls panel and instead of manually entering the control information, you can
read the exported .ctl file by choosing the Read... button on the left of the upper part of the
panel.

Surfaces Data
Faults Data
This section covers the following menu options:
• "Fault trace formats" on page 365.
• "Fault trace import" on page 365.
• "Fault surfaces" on page 366.
• "Fault table" on page 367.
• "Faults" on page 368.
• "Fault Data" on page 369.
• "Unassigned Fault Traces Data" on page 370.
• "Unassigned Fault Surfaces Data" on page 370.
• "Fault Trace Data" on page 370.
Introduction
Faults can be imported as surfaces and as sets of one or more fault traces.
Fault surfaces are used for visualization only and are defined using gridded surfaces.
Fault traces are used to model faults in the structural framework and ultimately in the simulation
model. Fault traces are defined by lines with XY or XYZ values. A fault trace may be a single
line or a pair of lines which represents the two sides of a fault and the area within.
A trace that is defined by a pair of areally distinct lines is often referred to as a fault polygon.
One or both ends of a fault polygon may be explicitly joined. If an end is explicitly joined this
indicates that the throw on the fault has gone to zero at this point. Any ends that are not joined
explicitly are connected by FloGrid to ensure that all polygons define a closed region.
A special kind of fault trace is the splitting trace. This is the trace used in the fault block
splitting phase of the structural framework construction. It is also the trace used to determine if
and how maps are nulled out in the vicinity of a fault. By default, the first fault trace assigned
to a fault is treated as the splitting trace. This can be changed from the fault trace option pop-up
menu.
• If the splitting trace is vertical its XY trace is used during fault block splitting.
• If the splitting trace is a polygon, a line is constructed for the purpose of fault block splitting
that lies midway between the two sides of the polygon. A polygon used for splitting is
normally constructed from the upthrown trace on the uppermost surface in the model and
the downthrown trace on the lowest surface where the fault exists.
• If the splitting trace is a polygon, the area within the polygon is nulled out and re-
interpolated for all maps in the model.
Splitting trace
This is a special kind of fault trace. This trace represents the overall shape and extent of the fault
and is not associated with a particular surface. It is normally constructed from the upthrown
trace on the uppermost surface in the model and the downthrown trace on the lowest surface
where the fault exists.

Faults Data
The splitting trace is used in the fault block splitting phase of the structural framework
construction and is also used to determine if and how maps are nulled out in the vicinity of a
fault. If the splitting trace is a single line it is used directly during fault block splitting. If the
splitting trace is a polygon, a line is constructed for the purpose of fault block splitting which
lies midway between the two sides of the polygon. If the splitting trace is a polygon, the area
within the polygon is nulled out and re-interpolated for all maps in the model.
Simulation grid faults

The Structured Gridder and Unstructured Gridder approximate curved fault surfaces with
locally planar surfaces. The shapes of these planes are determined by the fault polygon data. In
the Structured Gridder a curved fault surface is approximated by joining straight lines between
the upthrown fault trace on the uppermost surface map and the downthrown fault trace on the
lowest surface map. The Unstructured Gridder uses the same approach unless the
Segmented Coordinate Line option is being used. In this case, the curved fault surface is
approximated by piece wise linear lines determined by fault polygon information at
intermediate horizons.
If traces are not assigned to maps, splitting traces are also used to control the slope and position
of simulation grid faults. This is done by taking the two sections of a splitting trace and selecting
one to represent the upthrown trace of the uppermost fault and the other to represent the
downthrown trace of the lowermost fault. Z values for the splitting trace are then determined by
sampling the two sides onto the structural framework.
Note A key point from above is that although the splitting trace is normally constructed from
the uppermost upthrown trace and lowermost downthrown trace, the program allows
you to define these differently. This means that under unusual circumstances, you can
null out additional areas using the splitting polygon without moving the areal location
of the fault or without changing the slope of the simulation grid fault, which are
determined by the traces assigned to surfaces.
Defining splitting traces for sloping faults

Faults are often defined on a layer by layer basis by providing fault polygons on individual
horizon maps. These fault polygons define approximate fault surfaces and throws at the horizon
fault intersections.
The following section on defining splitting traces is based around the normal situation where a
splitting trace is constructed from fault polygons which have been associated with individual
maps.
Figure 14.1 shows three pairs of upthrown (Top1, Top2, Top3) and downthrown (Base1, Base2,
Base3) fault traces associated with three horizons.

Faults Data
Figure 14.1 Areal view of the fault traces for three horizon maps
Figure 14.2 shows the splitting fault trace constructed from the upthrown fault trace on horizon
map 1and the downthrown fault trace on horizon map 3.
Figure 14.2 Areal view of the splitting traces for all three fault traces
Figure 14.3 shows an idealized areal view of a digitized splitting trace with major points set to
the ends of the uppermost and lowest faults, and minor points set to the pick points on the
upthrown fault trace on horizon map 1 to the downthrown fault trace on horizon map 3. The fault
information between these user-picked limits is discarded.

Faults Data
Figure 14.3 Three model fault traces demonstrating digitizing of splitting trace
Figure 14.4 The splitting trace concept seen in cross section.
Figure 14.4 shows one side of a cross section of a listric fault surface defined by three sets of
fault traces, at the top and base of each layer. The replacement or simulation grid fault profile is
the dashed line between the uppermost and lowest fault traces.
Figure 14.5 shows both sides of a listric fault surface in cross section. We now discuss how
FloGrid deals with faults.

Faults Data
Figure 14.5 A listric fault seen in cross section
FloGrid nulls out the elevation information within the splitting polygon, in this case between
the upthrown fault trace on the uppermost horizon map and the downthrown fault trace on the
lowest horizon map, constructs a replacement fault profile / surface between the upthrown and
downthrown fault traces then extrapolates the existing horizon information out to the
replacement fault surface as seen in Figure 14.6. The original fault surface is ignored.
Figure 14.6 The original and replacement fault surface seen in cross section
Figure 14.7 shows the replacement fault in cross section.

Faults Data
Figure 14.7 The replacement fault trace seen in cross section
Fault trace formats

Fault traces can be imported into FloGrid in Generic, CPS or IRAP ASCII formats.
Generic...
Opens a file browser from which you can select a generic fault file. This format can be used to
import fault traces exported from CPS in X, Y, ID format. However, it is recommended that the
more comprehensive CPS fault format is used.
Four types of ASCII formats are supported, for further information see "Generic..." on
page 784.
CPS...
Opens a file browser to select an ASCII file in CPS format. This format allows multiple fault
traces in one file. Each fault trace section is started with “->”, followed by the fault name. For
further information see "CPS..." on page 785.
IRAP...
Opens a file browser from which you can select an ASCII file in IRAP format. This allows
multiple fault traces in one file. For further information see "IRAP..." on page 786.
Fault trace import

When a file is chosen from the file selection window, the Fault Trace Import window appears
with a list of one or more fault traces contained in the file selected for importing.

Faults Data
Another file
Opens the file selection window again to allow more fault traces to be loaded.
Fault traces to import

This table lists the traces in the selected file available for import.
Vendor
Displays which fault format was selected for the input file.
Location
Displays the path name of the imported file (and the specific format in the Generic case).
Trace
Displays the name FloGrid has assigned to the fault trace about to be imported. Names of fault
traces imported from the IRAP, Generic-ID or Generic-marker formats are generated using the
name of the disk file name. For example, if the disk file containing four fault traces is called
fourflts.dat, the fault traces in FloGrid are labeled fourflts1, fourflts2,
fourflts3, and fourflts4. As fault trace names cannot be changed once loaded, it is
recommended that the imported file is given a name which is appropriate for the faults.
Names of fault traces imported from CPS and Generic-name formats are read from the imported
file.
Fault
Specifies which fault the fault trace is to be assigned to. The drop-down list contains any faults
created by you in the Fault Tree, additional ones autogenerated from the imported fault trace
file and an entry called Unknown meaning that the fault trace is not to be assigned to any fault.
Import?
If a fault trace is unintentionally selected for import, it can be de-selected by changing the
corresponding field under Import? to No.
Import Z values? (IRAP only)

IRAP and CPS fault traces typically come as collections of (X, Y, Z) points. However, selecting
No in this field causes Z values to be ignored: the fault trace is therefore modeled using (X, Y)
values only.
Fault surfaces
The Fault Surface Import option provides a method to import external fault surface files into
FloGrid for visualization purposes only. A fault surface file contains data values represented on
a grid mesh. Supported fault surface options are listed next.
Fault surfaces
Fault surfaces are mainly used for visualization and are defined using gridded surfaces.
Supported fault surface options are listed next.

Faults Data
Importing fault surfaces
• To import fault surfaces of a given type, select the appropriate menu option.
A multi-file selection dialog opens.
• You can import one or more fault files by navigating to the desired directory and selecting
the required files. Selections are made by building up a list of files in the selection list. To
do this use Shift / Ctrl selection to pick multiple files and press the Add button or by
double-clicking on individual file names.
• Press the OK button to proceed with importing the selected files.
CPS1 (SAVE)
This is a binary SAVE file from the CPS mapping program. This format requires additional
control file information such as fault surface dimensions and a null value. See "Set import
controls panel" on page 346.
CPS3 (SVS)
This is a binary file in CPS-3 (SVS) format. There should be only one fault surface per file. All
information except fault surface units is stored in the binary file. If units are not specified in Set
Import Controls, FloGrid uses the currently defined External Unit System defined in
Preferences | Set External Units.
Fault table
The faults in the faults tree are listed in this table.
Select
This column is used to select a fault to be deleted. Faults are listed and numbered in the order
in which they are imported.
• Highlight the Select number to select a fault to delete.
Fault
The name of a fault may be changed by typing over the entry in Fault.
Trace
This shows the traces assigned to each fault. One trace association is shown in each row.
Surface
Associates a trace with a surface. Associations made using this option are used to determine the
uppermost and lowermost surfaces that a given trace cuts and hence can be used to specify faults
that die out in the reservoir.

Faults Data
If a trace is associated with a surface, Z values for the trace are computed after the build units
phase of the structural framework building process, once the Z values for the surface have been
computed, unless the trace is also assigned to a map, in which case Z values are taken from the
map.
Plane
Displays the fault surfaces associated with each fault. One surface association is shown in each
row.
Location
Displays the path name of the imported fault file.
Vendor
Displays which fault format was selected for the input file.
Create
Adds a fault to the main window faults tree. Faults are added to the bottom of the fault table.
Faults
The Faults tree, in conjunction with the 3D Viewer, provides facilities for visualizing, editing,
classifying and managing fault data. Information entered in this folder is used to help automate
the process of building structural and property models from which simulation models are then
built. Most functions are available using pop-up menu options on Fault Tree nodes. Certain
functions are also available using the Fault Table.
Fault tree
The fault tree has three top level nodes - Faults, Unassigned Fault Traces and Unassigned
Fault Surfaces.
Different functionality is available at different levels in the tree. It is accessed by selecting one
or more of the nodes and then using the right mouse button to bring up an appropriate pop-up
menu.
Pop-up functionality (in most cases) and the assignment of traces and surfaces to faults using
drag and drop can be applied to multiple nodes in one operation. This is done by selecting
multiple nodes using either control or shift selection as required.
Faults
Faults defined in this section of the tree are used whenever a structural framework is
constructed.
The top level Faults Node is connected to nodes representing each defined fault. Each fault
node can have one or more fault trace nodes connected to it.
Each Fault Trace Node can have a map node connected to it. This indicates that the map
represented by the map node has been used to compute Z values for the fault trace by sampling
the XY-trace from the underlying map.

Faults Data
Fault Data
This node is parented to the Faults Node. Each Fault node can have one or more Fault Traces
nodes connected to it. Faults defined in this section of the tree are used whenever a structural
framework is constructed.
Fault data options

Assign all traces to map
Assigns all traces for the selected fault(s) with a selected map. This option opens a panel to
allow you to select which map is to be used. When a trace is assigned to a map using this option,
Z values for the fault trace are derived from the map and if it is a fault polygon, a computation
is made to determine likely upthrown and downthrown sides.
Add all traces to view

Adds all fault traces assigned to the selected fault(s) to the 3D Viewer.
Add non-splitting traces to view

Adds all non-splitting fault traces assigned to the selected fault(s) to the 3D Viewer.
Add splitting traces to view

Adds the splitting fault trace assigned to the selected fault(s) to the 3D Viewer.
Add map-assigned traces to view

Adds all fault traces assigned to the selected map(s) and fault(s) to the 3D Viewer. This option
opens a panel to allow you to select which maps are to be used.
Create trace/polygon
Opens the Create Fault Trace panel. This allows you to define a new fault trace for the
selected fault and create and edit it in the 3D Viewer.
Trace name
Enter a name for the trace in the text box.
Line/Polygon
You are prompted to specify whether the trace is vertical (in this case you digitize a single trace
line) or sloping: in the second case the entire areal polygon can be defined.
Set Map
Opens a panel where you can select a map to which the fault trace is attached. If a trace is
attached to a map, Z values for the trace are calculated by projecting each XY point vertically
onto the map.
Auto create 2D / 3D splitter trace

Builds a default splitter trace for a fault if upthrown and downthrown traces have been assigned
to one or more surfaces. The default splitter trace is constructed from the uppermost upthrown
trace and the lowermost downthrown trace.

Faults Data
If the 3D option is chosen then the splitter trace has the same Z-values as the uppermost
upthrown and lowermost downthrown traces. If the 2D option is chosen the splitter trace does
not have any Z-values (the Z-values are sampled later, during the construction of the structural
framework).
Delete
Note Any traces that are assigned to the deleted fault(s) are unassigned.
Unassigned Fault Traces Data

This node represents unassigned fault traces. Unassigned traces are not used in the construction
of a structural framework.
Assign a fault trace to a fault

Fault traces may be assigned or unassigned as follows:
• Drag a fault trace from the Unassigned Fault Traces to a fault to assign that fault trace
to the fault.
• Drag a fault trace from one fault to another to re-assign the trace to the destination fault.
• Drag from a fault to the Unassigned Fault Traces to unassign the trace.
Unassigned Fault Surfaces Data

This node represents unassigned fault surfaces.
Note It is currently recommended that all imported fault surfaces are left as unassigned since
they can only be used for visualization. Fault surfaces are not used in the construction
of a structural framework.
This node represents unassigned fault surfaces.
Note Only a limited number of Options are available from a Fault Surface node - please refer
to the "Fault trace formats" on page 365 for a description.
Fault Trace Data

The Fault Trace Options pop-up menu allows fault traces to be edited, visualized and deleted.
Editing options change one or more attributes of a fault trace. Several of the editing functions
open the Fault Trace Editor, which can also be accessed from the Edit menu.
Each fault trace node can have a map node connected to it. This indicates that the map
represented by the map node has been used to compute Z values for the fault trace by sampling
the XY-trace from the underlying map.

Faults Data
Most fault trace options can be applied to multiple traces. Some only make sense for a single
trace. If multiple traces are selected for a single trace option, such as edit coordinate system, an
error message is displayed.
Fault trace display

Fault traces can have XY or XYZ information. Fault traces which only have XY information
are displayed at the datum plane, a flat surface just above the top of the reservoir.
Fault traces are colored to indicate:
• if a trace consists of one or two lines *
• if a trace has z values set (by importing XYZ values or sampling onto a map)
• if a polygon has been split into upthrown and downthrown sides.
Single line trace

z values are unknown: line = white
z values are known: line = cyan
Two line trace (vertical or polygon)

if the upthrown/downthrown status is set then if
z values are known: upthrown line = magenta, downthrown line = cyan
z values are unknown: upthrown line = magenta, downthrown line = yellow
if the upthrown/downthrown status is not set then if
z values are known: first line = green, second line = cyan
z values are unknown: first line = white, second line = yellow
Selecting a trace in the 3D Viewer selects the node corresponding to that trace in the fault tree.
Any trace in the 3D Viewer that is selected in the tree has its colors dashed with a red line.
When a trace is selected in the 3D Viewer the trace is added to the list of nodes already selected.
To deselect items in the 3D Viewer, the corresponding nodes must be deselected in the tree.
Fault Trace data options

Change Coord Sys...
Opens the Edit Coordinate System panel to specify the Z rotation, the orientation and units of
the axes, and the fault origin.
Copy...
Opens the Copy Fault Trace panel.
This allows you to create a new fault trace as a copy of the selected trace, to name it, to define
it to be a vertical line or polygon, to optionally assign it to a map and to edit it. The new trace is
assigned to the same fault as the trace that was copied.
Edit...
Opens the Edit Fault Trace panel.
*. A one-line trace is always vertical whereas a two-line trace can be either vertical or a polygon: it is a
polygon if it consists of two areally distinct lines.

Faults Data
This allows you to redefine whether the fault trace is vertical or a polygon, to optionally assign
it to a map and to edit it in the 3D Viewer.
Assign Selected Traces to Map...

This option displays a list of the structural maps available in the surfaces tree. The chosen map
is assigned to the selected fault trace(s).
Hint Choosing the None (unset) option, causes the selected fault trace(s) to be unassigned
from any map.
Notes
• Fault trace Z values sampled on a previously associated map persist after the map is
unassigned from the trace. However, Z values can be erased while editing the fault trace by
selecting Reset Z-Values in the appropriate menu.
• If a vertical fault trace is assigned to a map the single line is made into a polygon with up-
and downthrown lines. The points on the upthrown line are sampled from the highest points
in their map cells and those on the downthrown line are sampled from the lowest points in
their map cells. When the Editor is launched on such a fault the nodes on the single 2D line
are available for editing.
The fault trace’s map is explicitly marked in the fault trace node label. Additionally, a map
button is appended to the fault trace node while the assignment is in place.
Associate Selected Traces to Surfaces...

Displays the list of surfaces available in the surfaces tree: the chosen surface are associated with
the selected fault trace(s).
Associations made using this option are used to determine the uppermost and lowermost
surfaces that a given trace belongs to, and hence can be used to specify faults that die out in the
reservoir.
If a trace is associated with a surface, Z values for the trace are computed after the build units
phase of the structural framework building process, when the Z values for the surface have been
computed. If the trace is also assigned to a map, Z values are taken from the map.
Hint Choosing the None (unset) option, causes the selected fault trace(s) to be
disassociated from any surface.
The associated fault trace surface is explicitly marked in the Fault Trace Node label.
Export Selected Traces as CPS...

Exports one or more fault traces in a CPS compatible format.
Set as Splitting Trace...

Sets which fault trace is used as the splitting trace. See "Scatter Sets" on page 353 for a
description of the roles of the splitting trace.
Fault trace coloring and interaction with 3D Viewer

Fault trace nodes are colored to indicate:
• if a trace consists of one or two lines *

Faults Data
• if a trace has Z values set (by importing XYZ values or sampling onto a map)
• if a polygon has been split into upthrown and downthrown sides.
Node colors match those used to display the trace in the 3D Viewer.
Single line trace

Z values are unknown: line = white
Z values are known: line = cyan.
Two line trace (vertical or polygon)

If the upthrown/downthrown status is set, then if
• Z values are known: upthrown line = magenta, downthrown line = cyan
• Z values are unknown: upthrown line = magenta, downthrown line = yellow
If the upthrown/downthrown status is not set, then if
• Z values are known: first line = green, second line = cyan
• Z values are unknown: first line = white, second line = yellow.
A red border indicates that the node is selected, and is acted on if a fault trace pop-up menu
function is invoked.
Selecting a trace in the 3D Viewer selects the node corresponding to that trace in the tree. Any
trace in the 3D Viewer that is selected in the tree has its colors dashed with a red line.
You can make selections from the 3D Viewer in two different ways:
• Clicking on the trace with the left mouse button selects that trace.
All previously selected traces are deselected.
• Holding down the Ctrl key and clicking on the trace with the left mouse button selects
that trace if it was not before, or it deselects the trace if already selected.
All other selections remain unchanged.
Note Selection in the list of fault traces of the Edit Fault Traces panel (accessed from the
Edit menu) is always synchronized with the set of selections in the 3D Viewer and in
the trees. Furthermore, it is possible to make selections from the list of fault traces on
the Edit Fault Traces panel.
*. A one-line trace is always vertical whereas a two-line trace can be either vertical or a polygon: it is a
polygon if it consists of two areally distinct lines.

Faults Data
Wells Data
Introduction
This section documents some of the menus available by right clicking on the wells base node in
the node tree.
The following options are covered:
• "Create Wells..." on page 375
• Advanced vertical well planning..., see "Well Planning" on page 631.
Note You need the appropriate licence feature to use this option.
• "Import well deviation surveys" on page 376.

• Import well events, see "Well Planning" on page 631.
• Export well deviations, see "Well Planning" on page 631.
• Export well events, see "Well Planning" on page 631.
• "Select Wells of Type" on page 378.

• "Color Wells" on page 378.
• "Well Data" on page 378.
• "Visualization settings" on page 378.
• "Change well’s coordinate system..." on page 380.
• "Add lateral..." on page 380.
• "Add lateral..." on page 380.
• Edit Wellpath..., see "Well Planning" on page 631.
• Edit events, see "Well Planning" on page 631.
• "Properties..." on page 381.

Wells Data
• "Select Wells of Type" on page 381.
• "Set Type of Selected Wells To" on page 382.
• "Color Wells" on page 382.
• "Create synthetic well logs from 3D property grids..." on page 382.
Note Note that the generic Hide option is not documented here.
Create Wells...
Opens the Wells dialog.
Well dialog
Specifies well names and the location of each wellhead.
Wellhead Location
The Wellhead Location is important to allow deviation files containing entries specified as
offsets to be read.
Hint Wellhead Locations can either be entered manually, from file or the clipboard (right
click in the table to select these options), or by picking on features in the 3D Viewer.
The Wellhead Reference Height is (optionally) used to correct any TVD read from deviation
files to TVDSS, ensuring that the well is correctly positioned with respect to other geological
features.
Laterals, branches or sidetracks can also be specified in this dialog. Each should be named, and
then the row number of the parent well specified (FloGrid does not enforce unique names
throughout the model; the child’s name must only be unique to the parent well). You should also
specify the kick off point on the parent. If the parent has its deviation loaded then the appropriate
measured depth limits are indicated in a prompt above the location table.
To create a new well type in the well name into the table, then either enter a surface X, Y
location or pick the point on the 3D Viewer. Finally enter the Kelly Bushing or reference depth
in specified units. To change the units click with the right mouse button anywhere on the table
to access the pop up menu and select the Change Units... option. Alternatively, to create a well,
load the well head information from a text file by clicking with the right mouse button anywhere
on the table to access the pop up menu and select the Table Import... option.
To export well head information to a file or clipboard click with the right mouse button
anywhere on the table to select the pop up menu. From the resulting menu select the Table
Export... option.
Pick New Well Locations

Clicking Pick New Well Locations results in a new entry being added to the table following
each click in the 3D Viewer.

Wells Data
Show Well Head Locations
Clicking Show Well Head Locations results in a sphere representing each well head location
being displayed in the 3D Viewer.
Hint It is possible to associate (and disassociate) wells and laterals using this dialog, simply
by specifying that a well has a parent and entering an appropriate kick off point. This
may be desirable should the deviations of a well and a lateral have been read separately,
without having first defined their relationship.
Note Note that it is not necessary to enter wellhead data here if the information can be loaded
from the deviation survey file.
Note Note that deviated well paths can be edited (subject to the appropriate license feature)
by using the Edit Wellpath... dialog. You can access this dialog from the drop-down
menu for the well, after creating the well here. See "Well Planning" on page 631.
Well track display

Well tracks are displayed using their 3D values. For the purpose of display, they are clipped by
the datum plane from above to prevent possible Z exaggeration problems caused by the length
of the tracks being much longer than the thickness of all of the maps combined.
Import well deviation surveys

FloGrid can import well deviation surveys stored in either generic or proprietary GRID
formats.
Generic...
You are first asked for the locations of the files to be read. Several can be selected, to be read in
one operation—this should be done if the files are in the same format, as it is then not necessary
to specify the format more than once.
Once the files are specified, the Associate Deviation Files To Wells dialog opens.
Associate deviation files to wells

Lists all the files selected, together with the well to which the file’s information should be
associated. FloGrid attempts to default the associations based upon the names of the wells and
the files, but you should check that the associations are correct before continuing.
Clicking on an associated well entry enables you to change the association:
Note Note that any multilateral wells have their laterals specified in Schedule encoded
format, with a “%” character separating the parent well name from the lateral name.

Wells Data
None (Create New Well)
Selecting None (Create New Well) creates a new well rather than associating the deviation to
any previously defined well. The disk file name is used for the well’s name, although this can
later be changed, either in the Properties... dialog or in the Create Wells... dialog.
Hint Note that in this case the location of the wellhead of the new well is defaulted, which
may result in the well being incorrectly positioned. Changing the defaulted values in
the Create Wells... dialog repositions the well accordingly.
None (Ignore file)

Disregards the selected deviation file. This file is skipped during the deviation loading.
On clicking OK, the Specify Deviation File Format dialog appears, asking for the format of
the first file to be read.
Specify Deviation File Format

Displays the first fifty lines of the specified deviation file, and requires you to select the data
columns to be read, and their formats. You must specify the fields containing X, Y, and Z data
for each data point. X and Y data can either be absolute positions, or offset from the defined
wellhead (in this case select dX and dY). If no measured depth field is specified these data are
calculated assuming piece wise linear sections.
The specified number of header rows is ignored.
Hint Note that if the height reference is specified as RKB then the wellhead’s defined
reference height is subtracted from the Z data on read. Select reference MSL to prevent
this processing.
Once the format has been entered, clicking OK results in the format of the next file being
requested. Once all formats are specified the deviation files are loaded. Alternatively, clicking
OK (all files) results in the last specified format being used for all remaining file to be read.
Clicking Cancel causes the file whose format is currently being specified to be skipped by the
reader. Clicking Cancel (all files) instructs the reader to ignore all remaining files to be read.
GRID...
The GRID format consists of a control file that contains text information describing the
parameters to be read from an ASCII well deviation survey file. The actual well deviation
survey data file is specified in this control file. Such a control file can be exported from FloGrid
(subject to the correct feature licence), Schedule, GRID, or created in any text editor.
On selecting the option to import deviations using this format, specify the location of the control
file to be read.
Note The input description control file should be selected rather than the actual file
containing the deviation data.
For further information see "GRID" on page 791.

Wells Data
CPS...
A CPS ASCII file contains one or more well deviation surveys.
Caution At present, FloGrid assumes that the depth data are in the same units as the
horizontal data. If a file in mixed units has been read, the Edit Coordinate
System dialog can be used to correct the units of the data.
On selecting the option to import deviations using this format, specify the location of the data
file to be read.
Note If the CPS file qualifies the well name with a borehole name, it is the borehole name
that will be used in FloGrid. Each borehole will be treated as a separate well.
For further information see "CPS" on page 793.
Select Wells of Type

A type can be associated with a well in FloGrid. These types are either Injectors, Producers or
Unknown. This menu option allows you to select all the wells of a particular type on which you
can then perform a group operation. A simple example might be to add all the producers to the
3D Viewer.
Color Wells
Wells may be colored either uniquely or by well type. This menu option allows you to switch
between the two. The color of the well nodes and the wells in the 3D Viewer change to reflect
the current selection. If wells are colored by type then Injectors are colored Blue, Producers are
Red and Unknowns are Thistle (pale mauve).
Well Data
This section documents the menus available by right clicking on the node representing a well in
the node tree. Some choices allow the operation to be carried out on all selected wells.
Note Some operations can only be carried out on one well (or well branch) at a time: in case
of multiple node selections these options will be grayed out.
Visualization settings
Opens the Well Display Options dialog, controlling the well visualization settings.

Wells Data
Well Display Options dialog
This dialog contains several controls, specifying how wells are visualized in the 3D Viewer.
The settings apply to all wells in the 3D Viewer.
Display
Tickboxes exist for wells, well labels, well head and well events. Ticking the appropriate tick
box makes the corresponding object visible, unticking the tick box hides the object. The Well
Labels option shows the well name at the top and bottom of each well. It is not possible to show
the well labels without also showing the well.
Level Of Detail
Increasing the level of detail increases the number of sides on the cylinders used to render wells,
well events and well heads in the 3D Viewer.
Clip Tops/Bottoms
By default well paths are not shown all the way to the surface, but instead are clipped to the
volume of interest, automatically defined by the other geological features in the model. This
default can be changed using these check boxes.
Label Font...
This option opens a dialog allowing you to specify the font used for drawing well labels
specified.
Well Width
The well width slider controls the radius of the tubes used to render wells, well events and well
heads in the 3D Viewer.
Event Opacity
The event opacity can be varied from 0% (completely transparent) to 100% (opaque).
Hint It is possible to just render well events in the 3D Viewer. Switch off the Wells, Labels
and Well Heads tick boxes and switch on the Events tickbox. You can optionally,
increase the event opacity to 100%. This may make it easier to see the important
completed regions in complex models with large numbers of wells.
Open Event Color

By default, open events (perforation and barefoot) are rendered as partially opaque green tubes
around the tube representing the well path. This color may be changed by selecting a new color
using this drop-down.
Closed Event Color

By default, closed events (squeeze and plug) are rendered as partially opaque red tubes around
the tube representing the well path. This color may be changed by selecting a new color using
this drop-down.

Wells Data
Well Head Width
Well heads are displayed as spheres. The well head width slider is used to increase or decrease
the width of the well heads in relation to the widths of the tubes representing the well paths. A
value of 1.0, the default, means that the well head has the same radius as the well tube. The well
head can be increased to twice the size or reduced to a quarter of the size of the well tube.
Well Head Color

By default, well heads are rendered as yellow spheres. This color may be changed by selecting
a new color using this drop-down.
Change well’s coordinate system...

The option - only applicable to one well (or well branch) at a time - opens the Edit Coordinate
System dialog. This specifies the Z rotation, the orientation, and units of the axes, and the well
deviation origin.
Add lateral...
Note This option is only applicable to one well (or well branch) at a time.
Opens the Add Lateral dialog, which is used to add a lateral to a parent well. The parent well
is the well from which this dialog was invoked.
Parent
Displays the name of the parent well and is used purely as visual feedback that you are creating
the lateral on the correct well.
Range of parent’s MD
Displays the range of the parent wells measured depth and the units. This should be used as a
guide for the kick off point of the lateral well.
Name
Use this field to enter the name of the lateral.
KO Point
Enter the kick off point for the lateral. The units are displayed but cannot be changed. Checks
are made to ensure that the kick off point is within the measured depth range of the parent.
Pick KO Point in 3D Viewer

By selecting this tickbox you can click on the parent well in the 3D Viewer to specify the kick
off point. The value is displayed in the appropriate field of the dialog.

Wells Data
Properties...
Note This option is only applicable to one well (or well branch) at a time.
Opens the Well Properties dialog.
Well properties
Name
Allows the name of the well to be changed.
Parent (only present if applicable)

Displays the name of the parent well.
Wellhead Location (only present if applicable)

Displays the location of the wellhead; this value can be changed in the Well dialog.
Deviation (only present if applicable)

Displays the nodes on the well’s deviation, if any.
Deviation Processing (only present if applicable)
Note This option is available if you have the appropriate feature licence.
Controls how the well path is visualized in the 3D Viewer. The original deviation is saved,
allowing a change in the processing option to be reversed.
The Sample mode discards unnecessary points on the deviation, controlled by the threshold
angle. A point is discarded if the angle that the line joining the point to its predecessor makes
with the adjoining line is less that this threshold angle.
The Constrain mode generates a well trajectory using the deviation points as control points.
The entered dog leg severity and kick off limit is used to constrain the generated deviation. Note
that selecting this mode results in measured depths being recalculated.
Hint If deviations are exported it is the visual representation, as tabulated on this dialog that
will appear in the output files. If the original target points are required, switch the
deviation processing to None before exporting the deviation files.
Select Wells of Type

A type can be associated with a well in FloGrid. These types are either Injectors, Producers
or Unknown. This option allows you to select all the wells of a particular type on which you
can then perform a group operation. A simple example might be to add all the producers to the
3D Viewer.

Wells Data
Set Type of Selected Wells To
To use this menu option select a group of wells that you want to set to a particular type. The
types known about by FloGrid are Injectors, Producers or Unknown. If the coloration of wells
has been set to color by type then you will see the selected wells in the node tree and 3D Viewer
change color to reflect their type.
Color Wells
Wells may be colored either uniquely or by well type. This menu option allows you to switch
between the two. The color of the well nodes and the wells in the 3D Viewer change to reflect
the current selection. If wells are colored by type then Injectors are colored Blue, Producers are
Red and Unknowns are Thistle (pale mauve).
Create synthetic well logs from 3D property

grids...
Opens the Synthetic Well Log Creation panel. The panel allows you to select a property
model, and a property grid in the selected property model to generate synthetic well logs from
the property grid for the selected wells.
The synthetic well logs are computed by sampling the property grid along the well tracks of the
selected wells, and a Well Log Node is generated in the well log tree for each synthetic well
log along with the original well logs.
The panel has two drop-down lists to allow you to select a property model and a property grid
of the selected model, by default, the current property model and the first property grid of the
current property model are selected. The panel also contains a text field to show the property
type of the selected property grid.

Wells Data
Well Markers Data
Introduction
Well markers can be imported into FloGrid in Generic format.
This section covers the following options:
• "Well Marker Table" on page 385.
Import
Marker data are stored in column formatted ASCII files. An example and further information is
given "Well Markers Data Formats" on page 794. You select the Import | Generic... from the
Well Markers node in the data tree option to select the file location.
Note Only one marker file can be imported in a single operation.
Generic Well Marker Import panel

In its central part the top 50 lines of the marker file are shown and these can be a useful guide
during the initialization of the rest of the panel.
The read-only field Marker File Name contains the selected marker file location and the edit
field Number of Header Lines is used to enter the number of header lines at the top of the file
- lines that are ignored during import.

Well Markers Data
The 9 drop-down fields (numbered from 1 to 9) underneath the Column caption are used to
describe the content of the corresponding column in the marker file. Possible values are:
• Surface: name of the surface to which the marker is associated (for example, a marker
representing a well borehole/surface intersection).
• Well: name of the well borehole to which the marker is associated (for example, a
marker representing a well borehole/surface intersection).
• X: areal X-coordinate of the marker.
• Y: areal Y-coordinate of the marker.
• TVD (True Vertical Depth): areal Z-coordinate of the marker - usually referenced to
the Kelly Bushing.
• TVDSS (True Vertical Depth Sub Sea): areal Z-coordinate of the marker - usually
referenced to sea level
• MD: measured depth along the well to which the marker is associated (for example, a
marker representing a well borehole/surface intersection).
• Dip: dip-angle of the surface to which the marker is associated (for example, a marker
representing a well borehole/surface intersection).
• Azimuth: azimuth-angle of the surface to which the marker is associated (for example,
a marker representing a well borehole/surface intersection).
• NONE: the column is missing/ignored.
The Units drop-down field is used to set the units of the values described above.
The Review Marker Assignments button opens a panel where the associations marker-
surface-well can be reviewed.
Review Marker Assignment panel

(Re-)defines marker-surface and marker-borehole associations.
The panel tries to guess to which surface/borehole already present in the system each marker is
associated and if no guess is possible NONE appears in the field. The initial guess can be
overridden from the drop-down field - where all the existing surfaces/boreholes are listed.
Note The OK button on Generic Well Marker Import panel is enabled only after
reviewing and OK-ing the marker associations.
The upper part of the panel is used to (re-)define marker-surface association whereas the lower
part plays a similar role in the marker-borehole association.
It is possible to exclude from import sets of markers that are associated to a certain surface
and/or borehole by changing the value in the Load column of the appropriate section (that is the
surface/borehole) from YES to NO.
Note The Depth Correction column has no effect as the corresponding feature has not yet
been fully implemented.

Well Markers Data
Well Marker Table
The Marker Table option from the popup menu of the Well Markers top node displays a
summary of all markers available in the system. The read-only field Depth Units indicates in
which units the information is presented.
The drop-down field Sort by allows the marker table to be sorted according to:
• Surface: the list of the available surfaces
• Well: the list of the available wells

Well Markers Data
Well Logs Data
Introduction
You can import Well logs into FloGrid in the following formats:
• Generic, see "Generic" on page 386.
• LAS format, see "LAS" on page 386.
The section also contains information on the following options:
• "LAS log export" on page 389.
Generic
Only one file can be selected for input. For further information on the data format see "Well
Logs Data Formats" on page 795.
LAS
For further information on the data format see "Well Logs Data Formats" on page 795.
Note Note there may be multiple wells in one LAS file and you can select multiple LAS files
for input.
In the pop-up dialog you set up the Well Log input.

• In the first table you can associate wells in LAS file to the Well Sections in FloGrid. You
can choose not to load wells.
• In the second table you can select Well Log Types for the well log (s) in the LAS file.
Note Note if there are no well logs loaded into FloGrid then the list only shows new well
logs. Otherwise all log types are listed.
• You can associate log with a property type from FloGrid list of property types.
• Units read from the file are displayed in the fourth column of the table. You can change
them.
• In the fifth column you can choose whether to load each individual log.
There is a depth correction parameter that applies to all logs, NULL value and choice depth
units. Only meters and feet are in the list.
The text window at the bottom displays the LAS file that is being processed.

Well Logs Data
Select Color Legend...
Right-clicking on the Well Log node and choosing Select Color Legend... opens the Select
Well Log Property for... dialog. This allows you to set the properties indicated by the Color
Legend for Well Logs displayed in the 3D Viewer.
Note This option is active only if the color legend is enabled (that is Scene | Color Legend
| Show Color Legend is ticked) and the Object For Color Legend is set to Wells.
Hint You can set Object for Color Legend using Scene | Color Legend | Object for
Color Legend....
Select Color Legend Property

This is a drop-down list containing all the log properties currently displayed in the 3D Viewer.
You can select a property for the color legend from this list. When you select a property the
associated table contains the list of visualized logs of that property.
<select>
The list also contains an extra entry <select>. Clicking on this option displays a list of all the
logs visualized by means of color (either borehole or log line coloration) in the associated table.
Hint If you click on a log entry in the table, prior to selecting a property for the color legend,
the name of the property the log represents appears at the bottom of the panel beneath
the table.
Display Settings...
When a well log is associated with a well (or well section, in case of multilateral wells), you can
display it in the 3D Viewer either by coloring the borehole of the well, or by plotting a log line
along the borehole - up to two log lines (to which we refer as Line-1 and Line-2), representing
two different logs, can be displayed at the same time.
Right-clicking on the Well Log node and choosing Display Settings... opens the Well Log
Display Settings... dialog. This allows you to customize the well log representation in the 3D
Viewer.
Note Any setting selected in this panel applies to all well logs.
Decimation (Borehole Coloration, Line-1, Line-2)
Apply
When you enable the Apply check-box, the raw well log data goes through a process of
decimation, before they are used to determine the well coloration or the log line points.
Factor
Use the Factor slide-bar to vary the tolerance that drives the numerical algorithm used for
decimating, that is the higher the tolerance, the "fewer" log samples that are used.

Well Logs Data
The tolerance used is given by the chosen factor multiplied by the difference between the
magnitude of the maximum and the minimum value of the log property.
Choose Factor Upper Limit

Allows you to set the upper limit for the decimation factor. The scroll-bar varies the value used
from 0 to the set upper limit.
Log Samples Used

The percentage of the log samples used in the representation and an indication of the effect of
decimation (that is 100% means no decimation.)
Scale (Borehole Coloration)
Note The Borehole Coloration is currently insensitive to the chosen scale; a linear scale is
always used.
Scale (Line-1, Line-2)
Linear
The log samples are plotted on a linear scale.
Logarithmic
The log samples (after decimation) are plotted on a logarithmic scale.
Geometry (Line-1, Line-2)

This group of settings is used to vary the geometry of the plotted log lines.
Width
Determines the extension of the log line in terms of "times the borehole radius". For example,
using a Width of 3 means that all log lines (of type 1 or 2) are plotted on an XY plane cross-
sectional to the borehole and within an extension of 3 times the borehole radius.
Thickness
Sets the thickness of the lines:1 is thinnest, 10 is thickest.
Note It is not possible to independently vary the thickness of Line-1 and Line-2 log lines.
Any value set either in the Line-1 or Line-2 section applies to all log lines.
Plane
Changes the 2D plane on which the log lines are drawn. Values of 0 and 360 refer to the XY
plane.
Hint By choosing a displacement of 180deg in the Plane angle between Line-1 and Line-
2, it is possible to overlap the log line plot for two logs.

Well Logs Data
Color Scheme (Line-1, Line-2)
Property
When Property is selected, the log line is colored according to the property it represents. In this
mode it is also possible to obtain a color legend for that particular property.
Hint You can select color legend for the property by choosing Select Color Legend... from
the pop-up menu of the Well Log node.
Monochrome
Monochrome mode allows you to choose a specific color for Line-1 and/or Line-2. The name
of the selected color appears in the message window after any selection.
Reset
LAS log export

It is possible to export logs in the LAS format. This option is available in the menu for each well
log when you press the right mouse button. You can select several logs and then export them. A
separate file is created for each log. You can specify sampling interval, file name modifier and
directory where files will be written. The file name consists of the well name of the log, its
property name and file name modifier that you specify.

Well Logs Data
Boundaries Data
Introduction
This is the top level node for the boundaries. It contains a boundary child node for each
boundary created.
• "Boundaries data options" on page 390.
• Child boundary nodes, see "Boundary Data" on page 390.
Boundaries data options

Import...
Opens a dialog from which you can select the custodian, or boundary list, into which you wish
to import boundaries. Selecting one of the lists and pressing OK opens a file browser from
which you can select a file that defines one or more boundaries. If an imported boundary has the
same name as one already in FloGrid, you are offered the options of importing the boundary
with a modified name or not proceeding with the import.
Create, Copy, Edit...

This option allows you to create a new boundary by digitizing it or by copying an existing
boundary and then editing the copy.
To create a new boundary by digitizing it choose the boundary list to which your new boundary
will belong from the drop-down then press the Create button. This opens another dialog where
you can enter the boundary name. Select the type and projection plane then press OK. You can
now digitize the new boundary inside the 3D Viewer.
To create a new boundary by copying it, select the boundary to copy using the drop-down to
select the boundary list and highlighting the boundary in the list of boundaries beneath, then
press the Copy button. This opens another dialog where you can enter the new boundary name.
Select the type and projection plane then press OK. You can now edit the new copy boundary
inside the 3D Viewer.
Boundary Data
One of these nodes is created for each boundary that has been created.
Note When displayed under the Boundaries Node the name of the boundary is displayed
and the type of boundary is displayed in brackets. However when displayed under the
FloGrid Model Node it is the boundary name that is placed in brackets.

Boundaries Data
Boundary data options
Export...
The boundaries are exported in an ASCII format file.
Visualization Settings...
Once a boundary has been added to the view this option can be used to alter the way the
boundary is displayed.
Copy...
Copies one boundary to another. A dialog is displayed that allows you to change the
automatically generated name for the new boundary. Once you press OK on this panel you can
edit the copied boundary in the 3D Viewer.
3D Edit...
Edits the boundary using the 3D Viewer. A warning message appears if the boundary is used
by a FloGrid model that has had 2D or 3D grids generated already. An error message appears
and you are not able to edit a boundary that shared by more than one FloGrid model or which
is used by a Structural Framework.
Table Edit...
Edits the boundary using a table containing the X, Y points representing the boundary edges. A
warning message appears if the boundary is used by a FloGrid model that has had 2D or 3D
grids generated already. An error message appears and you are not able to edit a boundary that
shared by more than one FloGrid model or which is used by a Structural Framework.
Delete
An error message appears and the boundary is not deleted if the boundary is shared by more than
one FloGrid model, or if, when selecting this option on a node displayed under the Boundaries
Node, any FloGrid model is using this boundary.
Caution Be very careful with this option, as there is currently no confirmation dialog for
boundary deletion.
Note When displayed under the FloGrid Model Node the next three options appear above
Hide. When displayed under the Boundaries Node these do not appear.
Create a new boundary from structural framework

Forces the simulation grid boundary to match the structural framework boundary. When this
option is used, a copy of the original structural framework boundary is taken. This allows edits
to be made to the grid boundary without invalidating the original structural framework.
Create a new model boundary...

Opens a dialog where you can enter the boundary name. Select the type and projection plane
then press OK. You can now digitize the new boundary inside the 3D Viewer.

Boundaries Data
Select a new boundary for this model....
Opens a panel displaying a list of any other boundaries in the Structured Gridder Boundaries
control from which you can select a new boundary.

Boundaries Data
Structural Frameworks Data
Introduction
This is a top level node containing a child node for each structural framework that has been
created. Initially the node is expanded to show each of the structural framework nodes. However
you can collapse the node if this is not required.
• "Structural Frameworks data options" on page 393.
• Child structural framework nodes, see "Structural Framework Data" on page 393.
• "Fault Framework Data" on page 394.
• "Fault within Framework Data" on page 394.
• "Wireframe Data" on page 395.
Structural Frameworks data options

Add To View
This option is disabled to prevent you accidentally adding all the structural frameworks into the
3D Viewer in one go since this may take a long time. It is not something that you normally want
to do. If you really want to see all the structural frameworks in the view at the same time then
add them individually using the structural framework nodes.
Structural Framework Data

One of these is created for each structural framework and placed under the Structural
Frameworks Node. It contains two child nodes, one for the fault framework and one for the
wireframe.
Structural Framework data options

Edit...
Opens the Structural Framework panel with the current structural framework set to the one
represented by this node.
Delete
Caution Be very careful with this option as there is currently no confirmation dialog.

Fault Framework Data
This node represents the faults in the structural framework and contains one child node per fault.
Fault Framework data options

Edit
This allows you to edit the fault framework, though you are warned that major modifications
can invalidate the structural framework and that you should consider editing fault traces and
rebuilding the structural framework instead.
Set editor selection

When an edit session is running, this options enables you to select which faults are being edited.
If the fault selected is not already in the viewer it is added.
Show intersection subnodes...

Opens a dialog that allows you to change the way the fault framework nodes are displayed based
on the intersections between one another.
Export...
Opens a dialog listing all the faults from which you can select some or all for export. The
Browse button on this dialog opens a file browser from which you can choose the file to which
to export.
Import...
Once you select the file to import the dialog lists the gridding controls within that file. You can
then select which gridding controls to import, and what to do with any gridding controls already
in the Structural Framework.
Fault within Framework Data

This node represents a single fault.
Fault within Framework data options

Once at least one fault has been added to the view this option can be used to alter the way the
gridding controls are displayed.
Edit
This option allows you to edit the fault, though you are warned that major modifications can
invalidate the structural framework and that you should consider editing fault traces and
rebuilding the structural framework instead. The fault will automatically be added into the 3D
Viewer.

When an edit session is running, this options enables you to select which faults are being edited.
If the fault(s) selected is not already in the 3D Viewer it is added.
Export...
Selecting Export on the fault node popup menu opens the Export dialog listing all the faults
with those faults selected in the tree pre-selected in the dialog.
Wireframe Data
This node represents the structural framework’s wireframe.
Wireframe data options

Once the wireframe has been added to the view this option can be used to alter the way the
wireframe is displayed.

FloGrid Models Data
Introduction
The top level FloGrid Models data contains a child node for each model created in this
workspace. Initially the node is expanded to show each of the FloGrid Model nodes. However
you can collapse the node if this is not required.
This section contains information on the following options and nodes:
• "FloGrid Models data options" on page 396.
• "FloGrid Model Data" on page 397.
• "Boundary Data" on page 390.
• "Fault Gridding Controls Data" on page 398.
• "Gridding Control Data" on page 398.
• "Control Lines Data" on page 399.
• "Control Data" on page 400.
• "Areal Grid Data" on page 400.
• "3D Grid Data" on page 400.
• "Properties Data" on page 401.
• ",Property Type Data" on page 402.
• "Property Data" on page 402.
• "Slicing Data" on page 403.
• "Slice Node" on page 404.
• "Contact Sets Data" on page 404.
• "Aquifers Data" on page 405.
• "NNCs" on page 405.
FloGrid Models data options

Import
This option lists various types of models that you can import.
Add To View
Note This option is disabled to prevent you accidentally adding all the FloGrid Models into
the 3D Viewer in one go since this may take a long time and is not something that you
normally want to do. If you really want to see all the FloGrid Models in the view at the
same time then add them individually using the FloGrid Model nodes.

FloGrid Models Data
FloGrid Model Data
Each model created is represented by one of these nodes. If the label of the node is in bold it
indicates that this node is the current model. If a new model is created it automatically becomes
the current model. Under this node in the tree are a variety of child nodes depending on the type
of model created.
FloGrid Model data options

Import
The options under this menu allow you to import properties, well trajectories or streamlines.
You can import properties from ECLIPSE (INIT and RESTART) or generic AVS format files.
Well trajectories can be imported from ECLIPSE RESTART files, and are converted to well
deviations on import so that you can do further work on them. You can import files generated
by the FrontSim simulator that contain the streamline geometry and data.
Export
This option allows the INIT and RESTART files associated with model’s simulation grid to be
written out.
For FloGrid models that have been created as structured grid models, there is a second sub-
option under this option to export the model. Selecting Export | Model... opens the export panel
from the Structured Gridder.
Add To View
Adds all the various components making up the FloGrid Model into the 3D Viewer.
Remove From View

Removes all the various components making up the FloGrid Model from the 3D Viewer.
Set as current model

Sets the model represented by this node to be the current one. The nodes label changes to bold
to indicate this.
Copy...
Copies the selected model. A modal dialog opens allowing you to enter the name you wish the
copied model to be known as.
Rename...
Renames the selected model. A modal dialog opens allowing you to enter the new name you
wish this model to be known as
Edit...
Opens the appropriate panel to allow you to edit the model.

FloGrid Models Data
Fault Gridding Controls Data
This node contains all the gridding controls for the FloGrid model. By default, on model
creation, all the faults from the structural framework are added as gridding controls.
Fault gridding controls data options

Show controls by type...
This options allows you to add or remove all gridding controls that match the selected control
type (I, J, Zig-zag or Outside boundary) to or from the 3D Viewer. Types that are ticked are
in the view; types that have no tick next to them are not.
Show controls by slope setting...

This options allows you to add or remove all gridding controls that match the selected slope
option setting (Ignore, Slope, or Slope+Snap) to or from the 3D Viewer. Options that are
ticked are in the view; options that have no tick next to them are not.
Edit...
Starts the Gridding Controls Editor in the 3D Viewer.

When an edit session is running, this options enables you to select which gridding controls are
being edited. If the gridding control selected is not already in the 3D Viewer it is added.
Show intersection subnodes...

Opens a panel from which you can select for which type of intersection subnodes are shown.
Export...
Opens a dialog listing all the gridding controls from which you can select some or all gridding
controls for export. The Browse button on this dialog opens a file browser from which you can
choose the file to which to export.
Import...
Opens an import panel from which you can Browse to select a file containing gridding controls.
Once selected the gridding controls within that files are listed and you can select which gridding
controls to import, and what to do with any gridding controls already in the FloGrid model.
Gridding Control Data

There is one nodes of these per gridding control in the FloGrid model. The icon shows the
control type and slope option set for that gridding control as follows:
I Line, slope ignored by grid
I line, grid slopes to control
J line, slope ignore by grid
J line, grid slopes to fault

FloGrid Models Data
Grid zigzags along control and slope ignored
Grid zigzags along but slopes to control
Grid zigzags along fault with nodes snapped to the control, and grid slopes to control.
Gridding control data options

Once at least one gridding control has been added to the view this option can be used to alter
the way the gridding controls are displayed.
Set control type...

This options allows you to set the control type (I, J, or Zig-zag) for the selected gridding
control(s). If a type is invalid for a particular gridding control, an error message appears and the
type of that gridding control is not changed.
Set slope option...

This options allows you to set the slope option (Ignore, Slope, or Slope+Snap) for the
selected gridding control(s). If the option is invalid for a particular gridding control, an error
message appears and the slope option for that gridding control is not changed.
Edit
Opens the Gridding Controls Editor in the 3D Viewer.

When an edit session is running, this options enables you to select which gridding controls are
being edited. If the gridding control selected is not already in the 3D Viewer it is added.
Caution Be very careful with this option as there is currently no confirmation dialog.
Export...
Selecting Export on the fault node popup menu opens the export dialog listing all the faults with
those faults selected in the tree pre-selected in the dialog.
Control Lines Data

This allows you to add/remove from the display the various types of gridding controls used by
the Structured Gridder to build the model. The node contains four child nodes, one for each of
I, J, ZigZag and OutsideBoundaries.
Control Lines data options

Once at least one control line has been added to the view this option can be used to alter the way
the control lines are displayed.

FloGrid Models Data
Edit...
Opens the Control Lines Edit dialog. This dialog allows you to import, export, create, edit,
delete and copy control lines.
Control Data
A Control Line Node is created for each of the I, J, ZigZag and Outside Boundaries control
line types. This allows you to independently view each of the control line types.
Areal Grid Data

This allows you to add/remove from the display the 2D grid used by the Structured Gridder.
Areal Grid data options

Once the Areal Grid has been added to the view this option can be used to alter the way the Areal
grid is displayed.
Edit...
This option allows the Areal Grid to be edited using the 3D Viewer.
3D Grid Data
This allows you to add/remove from the display the 3D grid generated by the Structured
Gridder.
3D Grid node options

Once the 3D Grid has been added to the view this option can be used to alter the way the 3D
Grid is displayed.
Add To View
If a property has been set using the Properties Node then this is the property that is displayed
on the 3D Grid. If no property is set in the Properties Node then the grid is displayed using the
last property used for this 3D Grid and the Properties Node updates to show this as the current
property.
Edit...
This option allows the 3D Grid to be edited using the 3D Viewer.

FloGrid Models Data
Properties Data
The Properties node allows you to select the property displayed in both the 3D Grid and the
Property Model. It contains child nodes for each property type and each of these contains a child
node for each property of that type.
Properties node options

Add To View
The property used to display the Property Model is the first property under the first property
type node.
Select 3D Grid property

This option, if checked, causes the 3D grid to be updated when the currently selected property
is changed.
Note The 3D grid must be added to the view for it to display the property, this is not done
automatically for you.
Select Slicing property

This option, if checked, causes the Property Model to be updated when the currently selected
property is changed.
Property calculator...
Opens the Property Calculator for the current model.
Create Depth, Tops, DX/Y/Z, Volume

Opens a list box that allows you to select which geometric properties to create.
The properties offered are Depth (depth of cell center), Tops (depth of cell top face center), DX,
DY (distance between center points of X or Y faces projected onto the XY plane), DZ (distance
between top and bottom cell centers) and Cell Volume (exact volume defined by bilinear
surfaces, see "Geometric upscalers" on page 467).
By default only properties that do not already exist are created. You can opt to create any
combination of the above six geometric properties.
Note Only properties created in this way are overwritten by this facility. Properties that were
created by other parts of the program or were imported are not overwritten.
Create Transmissibilities and NNCs...

Opens the Create Transmissibilities And NNCs panel (see "NNCs" on page 421).
For further information on NNCs see "NNCs" on page 405 and "Edit NNC values..." on
page 119.

FloGrid Models Data
,Property Type Data
One of these nodes is created under the Properties Node for each property type found in either
the Property Model or the 3D Grid. Each of these nodes contains children representing
properties of this type. The name of the node is the name of the property type.
Property Type data options

Add To View
Selecting this option can have several different results:
• If a 3D Grid has been added to the 3D Viewer then this option changes the property
displayed in the 3D Grid (provided the Select 3D Grid property menu option on the
Properties Node has been checked).
• If a Property Model has been added to the 3D Viewer then this option changes the property
displayed in the property model (provided the Select Slicing property menu option on
the Properties Node has been checked).
• If neither a 3D Grid nor a Property Model have been added to the 3D Viewer then this
option adds the property model into the 3D Viewer. The property represented by this node
will then be used to display the property model (provided the Select Slicing property
menu option on the Properties Node has been checked).
The property used is the property represented by the first child node.
Delete...
Note If all properties of a type are successfully removed then this Property Type Node is
also removed.
Property Data
One of these nodes is created under the Property Type Node for each property in both the
Property Model and the 3D Grid. The preferred properties are shown in bold. There may be
several nodes listed for the same property type however they have unique names. Once a node
is added to the view it becomes a preferred property.
Selecting a property selects it in both the property model and the 3D grid.
Note The property nodes shown are a combination a both the properties found in the
Property Model and those found in the 3D grid. Therefore it is possible that the
selected property only exists in one or the other. You should see a warning message if
one of these nodes is selected as the object in the 3D Viewer may not update.
Property data options

Add to View
Selecting this option can have several different results:

FloGrid Models Data
• If a 3D Grid has been added to the 3D Viewer then this option changes the property
displayed in the 3D Grid (provided the Select 3D Grid property menu option on the
Properties Node has been checked).
• If a Property Model has been added to the 3D Viewer then this option changes the property
displayed in the Property Model (provided the Select Slicing property menu option on
the Properties Node has been checked).
• If neither a 3D Grid nor a Property Model have been added to the 3D Viewer then this
option adds the Property Model into the 3D Viewer. The property represented by this node
is then used to display the Property Model (provided the Select Slicing property menu
option on the Properties Node has been checked).
Property Calculator...
Opens the Property Calculator for the selected property node.
Rename...
Renames the property. A dialog opens asking you for the new name for the property.
Note Not all properties can be renamed.
Delete...
Note Not all properties can be deleted.
Replace Nulls...
Displays a dialog allowing you to enter the value that nulls are to be replaced with.
Slicing Data
This contains three child nodes for the I, J and K planes. This node controls only the Property
Model slicing and not the 3D Grid slicing. When a slice is added to the 3D Viewer the Property
Model is automatically added. However when all the slices are removed from the 3D Viewer
the Property Model is not automatically removed from the view. This allows other operations
to be performed on the Property Model using the Full Slicing dialog which do not involve
slices.
Slicing data options

Once the Property Model has been added to the view this option can be used to alter the way the
Property Model is displayed.
Add To View
If the Property Model is not already in the view it is added and the property displayed is that
which is currently selected in the property node tree.

FloGrid Models Data
Slice Controls...
Displays the Full Slicing dialog. The dialog allows much more complicated slicing operations
than simply incrementing or decrementing the current slice, which is all that the popup menus
provide.
Slice Node
One of these is created for each I, J and K slice plane. The numbers displayed in brackets after
the slice name is the current slice, or list of slices that is displayed for that plane.
Slice data options

Add To View
This option displays the particular slice in the 3D Viewer. If the Property Model is not already
in the view it will be added and the property displayed will be that which is currently selected
in the property node tree.
Increment Slice
This option increments the slice of the particular I, J or K slice represented by the node.
Reaching the limit in one direction returns you to the start.
Decrement Slice
This option decrements the slice of the particular I, J or K slice represented by the node.
Reaching the limit in one direction returns you to the start.
Contact Sets Data

This node contains nodes for each contact set defined on the model. Until you define a contact
set, the node has no child nodes.
Contact Sets data options

Create...
Opens a panel that enables you to define oil-water, gas-oil and / or gas-water contact sets using
a contact region property and a contact depth.
Contact Set Data

One of these nodes exists for each contact set that you have defined for a Flogrid model.
Contact Set data options

Edit...
Opens the Contact Set Definition panel to enable you to edit the definition.

FloGrid Models Data
Aquifers Data
This node contains nodes for each aquifer defined on the model. Until you define a aquifer, the
node has no child nodes.
Aquifers data options

Create...
Opens a panel that enables you to create a new aquifer. You define the cells and faces of the grid
that are connected to your aquifer, and the properties of the aquifer. The panel is described in
"Create, Edit, Delete Aquifer..." on page 419.
Aquifer Data
One of these nodes exists for each aquifer that you have defined for a FloGrid model. Ticking
an analytical aquifer node’s tickbox displays the Aquifer Connections property on the 3D
Grid. Ticking a numerical aquifer displays the Aquifer Cells property. If the 3D grid is not in
the 3D Viewer the aquifer properties cannot be displayed.
Aquifer data options

Add aquifer connections to view
This item only appears for numerical aquifers. It allows you to display the Aquifer
Connections property for that aquifer.
Add to view
This items displays the Aquifer Connections property on the 3D Grid for an analytical aquifer,
and the Aquifer Cells property for a numerical aquifer.
Copy...
This opens the aquifer definition panel (described in "Create, Edit, Delete Aquifer..." on
page 419) to enable you to define a new aquifer as a copy of the currently selected one. The
parameter values in the panel and the cell selection are copied from the current aquifer. You can
change these if you so wish.
Edit...
This opens a aquifer definition panel for the current aquifer from which you can edit the aquifer
properties or connections.
NNCs
Subnodes for all non-neighbor connections (NNC) properties for the parent grid are contained
under this node. Until you create or import NNC data, this node has no child nodes.

FloGrid Models Data
The subnodes each represent an NNC property type, the most important of which is the
Transmissibility property type. Beneath each property type node are stored all the NNC
properties of that type, each represented by a separate NNC property node.
NNC properties are displayed as a set of lines joining the centers of the grid cells that are
connected by each NNC. Since the actual property values are displayed as colors applied to
these lines, only one NNC property may be displayed at any one time for a particular grid.
NNC node options

Add to view
This adds the first NNC property found for the parent grid to the view (the subnodes are
automatically expanded so that you can see which property has been displayed).
Remove from view

This removes all displayed NNC properties for the parent grid from the view.
Threshold...
This displays the Threshold panel. With this panel you can specify a range of property values to
display for the currently displayed NNC property. NNCs for which the property values lie
outside the selected range are not displayed.
NNC property node options

Edit...
Launches an edit session on the selected NNC property. You can change the property values
associated with selected NNCs; and add and delete NNCs.
Copy...
Copies the selected NNC property. The name you give the copied NNC property must not be
empty or identical to an existing name.
Rename...
Renames the selected NNC property. The name you give the copied NNC property must not be
empty or identical to an existing name.
Delete
Deletes the selected NNC property. The system asks you to confirm the action before deleting
the property.

FloGrid Models Data
LGRs, Resizing, Aquifers and
NNCs Chapter 15
Introduction
After creating a structured grid, the Structured Gridder module can be used to refine, resize
and edit the simulation grid. For further information on creating the grid, see "Creating a
structured grid" on page 309.
The following facilities are described in this chapter:
• Local grid refinement (LGRs) - see "Refining a structured grid" on page 408.
• Refining and coarsening the global grid, and adding layers to an existing grid - see "Region
multipliers" on page 417.
• Defining region multipliers - see "Autogenerate IJK fault location table" on page 418
• Defining aquifers - see "Aquifers" on page 419.
• Creating NNCs and transmissibilities - see "NNCs" on page 421.
You can also use the Structured Gridder module to import and display streamlines (see
"Streamlines" on page 161) to import and edit an existing simulation grid and to back-populate
simulation properties onto the fine scale / property model from which it was generated (see
"Create fine model view" on page 461).
FloGrid User Guide LGRs, Resizing, Aquifers and NNCs 407

Introduction
Refining a structured grid
LGRs
The LGRs folder allows you to specify the style and the areal and vertical dimensions of locally
refined grids (LGRs). It is only operational either once an areal grid has been created or once a
grid has been imported. It can be used before or after a 3D grid has been built. LGRs can be
defined on the global grid and for certain simulators on previously defined local grids
(domains). Previously-defined LGRs can be selected and modified.
Select domain for LGR

Selects which grid level (domain) to refine. All domains in the model are listed with indentation
used to indicate nesting of LGRs / domains.
Note If any level other than the global grid is selected, you should check that the target
simulator supports nested LGRs.
LGR name in this domain

Specifies a name for the LGR to be created in the domain / grid selected in the field above. In
addition, existing LGRs can be selected using the drop-down list to examine their details.
LGR Style
Below the LGR name field is a set of radio buttons, which you can use to specify the style of
the refinement. The four options are
• Cartesian
• Cart refine
• Radial 1 col
• Radial 4 col
The default style is Cartesian. In this style, and in the Cart refine (Cartesian refine) style, you
specify a set of host cells using the LGR Location fields (see below). The host cells are each
subdivided into a cartesian grid of NXFIN by NYFIN by NZFIN refined cells. The Cart refine
style is a simple trilinear sub-division or refinement of the host cell (this was the only Cartesian
option before 2002A). The new Cartesian style builds the LGR cells by sampling the property
model structure, just as is done to generate the parent grid. These LGRs can honour the geology
at the LGR areal and vertical resolution and hence more closely model horizon undulations and
fault locations.
Radial LGRs have a polar geometry: that is, in an areal view their cells form a series of NRFIN
concentric annuli divided into NTFIN wedges, and in a vertical plane they subdivide host cells
into layers. There are two radial LGR options. The first places the radial LGR within a single
column of host cells (Radial 1 col), with the centre of the radial grid being placed at the centre
of the host cell. the second (Radial 4 col) places the radial LGR within a two by two set of four
host cell columns, with the centre of the radial grid being along the common coordinate line of
the four columns.
408 LGRs, Resizing, Aquifers and NNCs FloGrid User Guide

LGR Location
This group of options allows you to specify the I, J and K extents of the parent grid within which
an LGR is required, the default number of refinements in each direction within each host cell,
and, for radial LGRs, the inner and outer radius of the LGR. The names of the fields adapt to
the style of the LGR being defined.
The extent of the LGR can be specified by typing in the values into the two rows of 3 fields Start
Cell i, j and k and End Cell i, j and k. The two k fields can be filled in once the I-J extent of the
LGR has been defined. By default the K extent is set to all grid layers currently defined.
The I,J and K extents can also be set interactively by picking on the appropriate cells in the
simulation grid in the 3D Viewer. Five picking options are available:
• Start IJ
• End IJ
• Start K
• End K
• Pick IJK
When Start IJ or End IJ is active, selecting a simulation grid cell in the 3D Viewer (see "3D
Viewer" on page 107) sets the appropriate fields to the selected cell’s I and J values. When Start
K or End K is active, selecting a simulation grid cell in the 3D Viewer sets the appropriate fields
to the selected cell’s K value. The host cells for the new LGR are painted white in the 3D
Viewer. For radial LGRs you only need to set one of StartIJ or EndIJ locations; the extent of
the LGR in the host grid is then automatically completed for you.
Note If all the simulation grid cells are in the view and the LGR’s host cells do not touch the
boundary of the grid, the selected cells will not be visible. They can always be
uncovered by slicing through the grid.
When Pick IJK is active, selecting a 3D grid cell within the current LGR causes the appropriate
rows of the LGR refinements tables to be labeled by a ## in the first column.
You can set the default number of refinements per host cell by typing into the third row of three
fields. For Cartesian LGRs these are labeled NXFIN, NYFIN and NZFIN. For Radial LGRS
these are labeled NRFIN, NTFIN and NZFIN. NTFIN can take the values 1 or 4 for the one
column style, or 4 or 8 for the four column radial style.
Note The NRFIN specified for radial LGRs includes the outer ring of cells which extend to
the host cell boundaries. The generated LGR therefore appears as NRFIN-1 annuli in
the middle of the host cells.
2D grid option
If the simulation grid has yet to be built, the 2D grid option allows the IJ extents to be set, by
picking the start and end cell on the areal grid in the 3D Viewer.
When Start IJ or End IJ is active, selecting a 2D areal grid cell on the 3D Viewer (see "3D
Viewer" on page 107) sets the appropriate fields to the selected cell’s I and J values. When Pick
IJK is selected, selecting a 2D areal grid cell within the current LGR (once the IJ extent has been
defined) causes the appropriate rows of the LGR refinements tables to be labeled by a # in the
3D column.

Note When using the 2D grid option, parent cells within the requested LGR region are
colored according to which fault block they are in. This is done to give you some
indication that an LGR is crossing a fault or a fault extension (see "Fault block
splitting" on page 209 for more details on fault blocks).
Inner radius, Outer radius, Minimum DeltaR

These fields are only active when a radial LGR is being defined. The default values are an inner
radius of one foot, an outer radius of one-third of the radius of the largest circle that can fit
within the host cell(s), and a minimum annular width of five feet. Set the outer radius to a value
of zero to use the default value. If you specify a value for the outer radius that is larger than that
of the largest circle that can fit within the host cell(s), this value is used during gridding and
message sent to the Log Window.
When you save the LGR (click the Save LGR button), the values in these fields are updated.
The fields display the newly calculated default values if you have not entered your own values,
and display values that have been adjusted to be valid if you have entered a set that is invalid,
for example with a specified outer radius that is too big to fit inside the host cell(s), or with
default values that are invalid for your grid. The Log Window displays an explanatory warning
message in these cases.
Use refined layer geometry at resampled LGR boundaries

This option enables the user to build the LGR based on the underlying geological model
layering. In certain cases this option can provide improved LGR definition compared with the
default sampling method.
By default this option is unchecked, in which case the global geometry is used at the LGR
boundary.
LGR Refinements
Three tables are displayed in this group. For cartesian LGRs they list the I, J and K rows in the
parent grid that are to be refined. Each table has three columns:
• the first column gives the host I, J or K row, or displays ## to indicate that host cell has been
selected in the 3D Viewer
• the second column gives number of refinements per host cell;
• the third column displays either Default, or WeightsSet depending on whether default or
non-default weights have been set; it contains on its right a button that gives you a drop-
down menu with the two options UseDefault and UseWeights that you use to define the
weights.
When the IJ location of the LGR has been completely specified, the rows of the first two tables
are filled in with the chosen default number of refinements and default weights. Once the K
location of the LGR has been defined, the third table’s rows are filled in with the default number
of K refinements per host cell and default weights.
Once a table has been filled out by FloGrid you can vary the refinement in each cell by entering
new values for the Nx, Ny or Nz in the parent rows. A ## in the I, J or K column indicates that
this row has been selected in the 3D Viewer. To define default equally weighted refinements
for the cell, select Default from the drop-down. To set non-uniform weights select
UseWeights. A panel Refinement Weights for Host... pops up. This contains a table in which
you can type the weighting given to each LGR cell within the host cell. Press OK to confirm
your weights, or Cancel to dismiss the panel without making changes.

For radial LGRs, the middle (Ny) table is not used, and is grayed out. The first table is labeled
Nr, and its first row is used to define the weighting given to each annulus within the LGR. The
third (Nz) table is used as for Cartesian LGRs to define refinements in the vertical direction.
Note For radial LGRs the default radial refinement are geometrically increasing radii. If you
want uniformly weighted annuli, select SetWeights and define a set of equal numbers.
Save LGR
Creates and saves the LGR using the specified start and end cell locations and the refinements
you have made in the tables. An areal LGR is created, and is displayed in the 3D Viewer as part
of the areal grid. Any existing 3D grid is not altered until you either click Update 3D Grid on
this panel or Build Grid on the vertical gridding panel.
Delete LGRs
Deletes previously created LGRs. If selected this button displays a list of LGRs to select from.
If you select an LGR that has LGRs defined within it (child LGRs), then you are offered the
options to cancel the delete, or to delete the child LGRs first.
Update 3D Grid
This option is available if you have already built a vertical grid (simulation grid). LGRs that
have been saved since the grid was built or last updated are added to it. LGRs that have been
deleted are removed from the grid. LGRs whose location or refinements have been changed are
rebuilt. Since the LGR grid cells are refinements of the host cells, updating an existing 3D grid
after making changes to the model’s LGRs is much faster than rebuilding the whole grid.
When the grid is updated, existing properties are preserved. New and edited LGRs have
property values taken from their host cells.

Resizing a structured grid
The Resize folder allows you to perform operations that affect the geometry of the whole grid,
with reasonable property values being assigned to new cells. These operations are
• Refining part of the grid in I, J and/or K
• Coarsening part of the grid in I, J and/or K
• Insertion of additional K-layers into the grid within an existing layer
• Addition of extra K-layers above or below the existing grid.
All these operations change the size of the grid after it has already been built.
The folder contains two sub folders, Refine/Coarsen and Add Layers To Grid. These will be
described in turn.
Refine/Coarsen
The region of the grid to be refined or coarsened can be selected with the mouse. The first cell
selected defines one corner of the selected region, while the second cell selected defines the
other corner. Alternatively, the IJK box values can be entered manually in the first two columns.
The third column contains the (integer) factors by which you want the selected region of the grid
refined or coarsened. A factor of 1 leaves the cells unaltered (in that direction). If all three
factors are 1, no refinement or coarsening will take place, and the grid will be unchanged. Note
that in the case of coarsening, the coarsening factor in each dimension must exactly divide the
size of the coarsened region in that dimension.
Once the desired region and the refinement/coarsening factors have been specified, click on
Refine or Coarsen to refine or coarsen as desired.
Note The operation cannot be undone, so it should be used with care.
Effect of refinement/coarsening on LGRs

Any LGRs that are affected by the refinement or coarsening are discarded. LGRs that do not
intersect the refined/coarsened region are preserved.
Refine
Any existing faults are honored. Cell based properties are copied from the host cell of the grid
prior to refinement. The PORV property if defined is recalculated. Advanced geometrical
properties (CellVolume, AspectRatio, Jacobian etc.) if defined are recalculated.
The refinement is not an LGR, and extends to the edge of the grid.

Coarsen
The PORO and NTG properties are calculated using a volume-weighted average of the values
in the host cells of the grid prior to coarsening. PERM* properties are calculated using a pore-
volume weighted average. The PORV property if defined is recalculated. Advanced geometrical
properties (CellVolume, AspectRatio, Jacobian etc.) if defined are recalculated. Note that the
coarsening does not do a complete “upscaling” of all existing properties: in particular,
permeabilities are not harmonically/directionally weighted.
The coarsening does not produce an ECLIPSE coarsened region. It coarsens a selected box, and
the coarsened cells extend out in the selected direction(s) to the edge of the grid. If a coarse cell
spans a fault, the coarse cell effectively heals the fault joining cells which were previously split.
Effect of coarsening on unit boundaries

A complication arises if the grid is coarsened in the K dimension, when the region selected for
coarsening spans across two or more adjacent units. If this is the case, it may be that the
coarsening operation causes layers from adjacent units to be merged. If this happens, the merged
layer(s) are assigned unit numbers in a manner that maintains the boundaries between units as
close to their original positions as possible, in terms of their logical position in the grid. This
may potentially result in one or more layers becoming pinched out.
Add Layers to Grid

The Add Layers To Grid feature allows you either to split an existing layer of grid cells into
two new sub layers (each of which may be further subdivided if desired), or to insert new layers
of cells above or below the existing grid. In both cases, the new layers of cells will conform to
a selected horizon (this is different from a global grid refinement in K, which is restricted to
generating new refinement layers by proportionally spacing them within an existing K layer).
In the case of splitting an existing layer in two, the boundary between the two new sub-layers
will conform to the selected horizon, except in places where the horizon lies above or below the
layer of cells to be split; in this case one or other of the sub-layers will be pinched out (Figure
15.1, Figure 15.2).
In the case of adding extra layer(s) above the grid, the top of the extra layer(s) will conform to
the selected horizon, except in the case where the horizon passes below the top of the existing
grid; in this case, the extra layer(s) will become pinched out at this point in order to avoid
generating inside-out cells (Figure 15.3). Similar remarks pertain to the adding of extra layers
below the existing grid.
Effect of adding layers on LGRs

If the extra layers are generated by splitting an existing layer, any LGRs that intersect the layer
that is split are discarded. All other LGRs are preserved.
Adding layers above or below the grid preserves all LGRs.
Effect of adding layers on properties

If the extra layers are generated by splitting an existing layer, then cell-based properties are
copied from the host cell of the grid prior to refinement. If the extra layers are added above or
below the grid, then cell-based properties are propagated from the top or bottom layer of the
existing grid as appropriate. The PORV property if defined is recalculated. Advanced
geometrical properties (CellVolume, AspectRatio, Jacobian etc.), if defined, are
recalculated.

Using the Add Layers To Grid feature
Adding layers within the grid
Select the horizon to be used from the Horizon Surface list (on the left of the Add New Layers
To Grid folder). Under Add new layers, select the At grid layer option. You can now enter the
index of the k-layer that you wish to split in the Layer box (or you can pick a cell in the desired
layer from the 3D Viewer, whereupon the whole of that layer will be highlighted).
Select the number of layers that you wish to create above and below the horizon surface. At least
one layer above and one layer below will be created, although you may split these into further
sub-layers if desired. The Extend coordinate lines control will be disabled: since the new layer
will lie entirely within the existing grid, no extension takes place and this control is irrelevant.
When you are ready, click on Create New Layers to add the new layers.
Figure 15.1 Splitting a selected existing layer of grid cells into two new sub layers (side view).

Figure 15.2 As Figure 15.1, but splitting the upper sub-layer into three sub-layers, and the lower sub-layer into two.
Adding new layers above the grid

Select the horizon to be used from the Horizon Surface list. This should lie above the top of
the existing grid, or the extra layer created will have zero volume. Under Add new layers,
select the Above grid option. Select the number of layers that you wish to create below the
horizon surface; these layer(s) will lie between the horizon surface and the top of the existing
grid. No extra layers may be created above the horizon surface. The coordinate lines will be
extended straight until they meet the horizon surface (Figure 15.3). Beware: the horizon surface
should lie just above the grid; if the coordinate lines are extended straight for too far, there is a
risk that they will cross and inside-out cells will be generated.
When you are ready, click on Create New Layers to add the new layers.
Adding new layers below the grid

Adding new layers below the grid is analogous to adding new layers above the grid, except that
under Add new layers, you should select the Below grid option.

Figure 15.3 Adding a new layer above the existing grid (side view)

Region multipliers
Opens the MULTREGT Keyword Editor panel. It is used to define transmissibility multipliers
to be applied between regions of the simulation grid based on MULTNUM values in adjacent
cells.
Note Multipliers entered in this panel and the corresponding MULTNUM array must be
exported from the Grid and Properties Export panel and processed in the simulator,
as the Structured Gridder does not compute transmissibilities.
MULTREGT keyword
Defines transmissibility multipliers to be applied between regions of the simulation grid based
on MULTNUM values in adjacent simulation cells.
The panel provides a table for entering pairs of MULTNUM values, and associated multipliers and
options, to generate MULTNUM values on the simulation model and fill the table with valid
MULTNUM pairs.
From region
An integer MULTNUM region number.
To region
An integer MULTNUM region number.
Trans. multiplier
The transmissibility multiplier to be used by the simulator whenever simulation cells with a
MULTNUM equal to that specified in the From Region are connected to simulation cells with a
MULTNUM equal to that specified in the To region column.
Directions
The directions in which the transmissibility multiplier should be applied.
NNCs
Specifies if the transmissibility multiplier should be applied to all connections between the
specified regions, just the NNC connections, or standard connections excluding NNC
connections.
Fault/label
Annotates the rows in the MULTREGT. Text entered here is exported as a comment after the end
of the row in the exported table.

Region multipliers
Update table from MULTNUM property
Creates a list of valid pairs of connected MULTNUM regions based on normal and non-neighbor
(NNC) simulation grid block connections and fills in the table. If a MULTNUM property is not
defined on the simulation model, you are offered the option to compute a default MULTNUM
property based on the block unit number associated with the grid block. As block unit
numbering is zero based and MULTNUM is 1 based, the generated MULTNUM property is
computed by adding one to the block unit number.
Autogenerate IJK fault location table

Creates a special MULTNUM property called IJKFAULTMULTNUM, creates a list of valid pairs
and fills in the table. This table can be exported to define the location of IJK faults within the
grid for export to the simulator.
The IJKFAULTMULTNUM property in a given simulation grid cell is also based on the block
unit number (for maximum flexibility in use). Cells that have a connection to another cell across
a fault have the value one greater than the block unit number. All other cells have the value one
greater than the total number of block units (this is the non-fault value). Such cells include cells
situated away from a fault, cells that lie next to a fault that has a throw greater than the model
thickness and so are disconnected from their neighbor across the fault, and cells that lie on a
block unit boundary but that are outside the extent of the fault.
Pairs that include the non-fault value MULTNUM region are automatically excluded from the
table. Each row in the table is labeled by the name(s) of the fault(s) that divide those MULTNUM
regions. The table rows are sorted by the fault/label field, so all rows pertaining to a single fault
can be found together.
Note Computing these tables can be a lengthy process as it involves computing all valid
connections.
Preserve additional rows

If this option is checked, any region multipliers that have been added since the last time the
Update table from MULTNUM property option was selected is preserved when the table is
next updated.

Region multipliers
Aquifers
Create, Edit, Delete Aquifer...
Opens a panel that contains a list box with any aquifers already defined upon the model, and
buttons to Create, Copy, Edit or Delete an aquifer for a structured grid. Create, Copy, Edit
each open the aquifer definitions panel Create Aquifer or Copy Aquifer <name> or Edit
Aquifer <name.
Aquifer name
If you are creating or copying an aquifer you need to type in the aquifer name or accept the
default name provided.
Connected cells
You define the aquifer connections, that is those faces of reservoir cells to which the aquifer will
be connected, by selecting the connected cells and the cell-faces (I-, J-, K-, I+, J+ or K+) through
which the aquifer is connected. You select the cells by using the 3D viewer to display the
required cells, and then clicking on Select New Cells to Connect. You select the faces by
checking one or more of the connection directions I-, J-, K-, I+, J+ and K+. The aquifer will be
connected to the external faces in each of the connection directions of all the cells that form the
bounding box in IJK of the connected cells selection.
For an existing aquifer (that you are editing or have just created) you may define additional IJK
boxes of cells and associated faces through which the aquifer is connected. A radio button gives
you the option to either Add to current connections, or to Replace current connections
when you click on Select New Cells to Connect. If you choose Replace current
connections, all existing connections for that aquifer are deleted and replaced by your new
connected cells and faces.
Note You can add new boxes of connected cells to an aquifer definition, but you cannot
delete or edit individual boxes that are already defined. You can only replace all
connected cells by a fresh definition
To see a table of the current connections for the aquifer, click on List Boxes of Cells
Connected to this Aquifer. The table that pops up shows the IJK bounds of each connected
box of cells, and through which of the (external) I-, J-, K-, I+, J+ and K+ cell-faces the aquifer
is connected.
Once the aquifer is created, you can visualize the aquifer connections by displaying its
AquConnections property (see Apply below)
Aquifer properties
The aquifer may be analytical or numerical. You control which type of aquifer you define by
selecting the appropriate properties.
Click on Analytical Aquifer to define an analytical aquifer. A second panel opens that contains
radio buttons to select the aquifer type - Fetkovich, Carter Tracy or Constant Flux - and edit
fields in which you type the parameter values. Defaults are provided where available.
Parameters that are not applicable to the analytical model chosen are disabled.

Aquifers
Click on Numerical Aquifer to define a numerical aquifer. A new panel opens that contains
some transmissibility calculation parameters, and a table. You define the properties of, and the
grid cell that is to be used for, each numerical aquifer cell in this table. You can type in a value
for the Grid Cell, but the easier method is to pick a suitable cell from the 3D Viewer. First, in
the Properties panel, click on the row that you want to fill in the table, then click on the grid
cell in the 3D Viewer. The Grid Cell column of that row will be filled in with the picked grid
cell ID. You should pick a zero-volume or other inactive grid cell for use as an aquifer cell.
ECLIPSE connects the aquifer cells within a numerical aquifer in the order that they are listed
in the table.
If the aquifer is newly created, its aquifer properties are created and appear under the
Properties node of the main tree. For all aquifers, an AquConnections property is created, one
per aquifer, to show which reservoir cells are connected to the aquifer. The connected cells have
the value of the aquiferID of that aquifer (that is used in the ECLIPSE keywords). The faces of
those cells that will be connected to the aquifer are defined by your choice of connection
direction. For numerical aquifers, its aquiferID is used to identify those grid cells that are used
for the numerical aquifer cells. There is one AquiferCells property that shows the cells used for
all the numerical aquifers you have defined.

Aquifers
NNCs
For further information on NNCs see "NNCs" on page 405. You can find further information on
editing and creating NNCs in"Create NNCs..." on page 120 and "Edit NNC values..." on
page 119.
Create Transmissibilities and NNCs...

Opens the Create Transmissibilities and NNCs panel (Figure 15.4), which creates a named set
of transmissibility data for the grid. The data consists of transmissibility properties with
associated non-neighbor connections (NNCs).
Once generated, the neighbor connection transmissibilities are stored as TRANX, TRANY and
TRANZ cell-based properties (these are given names of the form TransX_xxxx,
TransY_xxxx and TransZ_xxxx respectively, where xxxx is the output transmissibility name
that you specify). The non-neighbor connections are stored with the same name under the
Transmissibility subnode of the NNC node; these comprise
• NNCs across faults
• NNCs across vertically pinched-out layers of cells
• NNCs across areally pinched out layers of cells
• NNCs arising due to the presence of LGRs.

NNCs
Figure 15.4 The Create Transmissibilities and NNCs panel.
In order to generate transmissibilities, at least the following properties must be defined:

• permeability
• either pore volume or porosity.
Other properties required can be either calculated on the fly or defaulted to 1.0. The
transmissibility calculation is identical to that performed by ECLIPSE.
Model
Selects the model for which you wish to generate the transmissibility data.

NNCs
Output transmissibility name
Denotes the name that is used to refer to the set of transmissibility data that is generated, both
neighbor and non-neighbor connections. You can select the name of an existing set of
transmissibility data, in which case it is overwritten when the transmissibilities are recalculated.
Alternatively you can enter the name to create a new set of transmissibility data.
Note Selecting the name of a previously calculated set of transmissibility data causes the
panel to display the options used when calculating that set of transmissibility data. This
allows you to regenerate it if required (for example, following edits to the grid), or to
generate a second set by modifying the parameters used for an existing set.
Input properties
Select the permeability properties to be used in the X, Y and Z directions in calculating the
transmissibilities, together with the net-to-gross (NTG) ratio. If no NTG property exists, the
NTG ratio defaults to 1.0 .
Transmissibility multipliers
Select properties that should be used as transmissibility multipliers in the X, Y and Z directions;
otherwise, or if no such properties exist, the transmissibility multipliers default to 1.0.
Pore volume property

Specifies how the initial pore volume property is to be obtained. If a pore volume property
already exists, this may be selected; otherwise, the pore volume is calculated on the fly as
porosity * cell volume * net-to-gross ratio, and used to create a pore volume property on the fly.
Note If an existing pore volume property is used, the NTG property used, if defined, must
be the same one that was used in generating this pore volume property. If you wish to
specify a different NTG property, you should select the option to recalculate the pore
volume on the fly using this NTG property, rather than using a pre-existing pore
volume property.
Pinchout criteria
Sets the criteria for detection of pinched-out cells. Cells are pinched out if their pore volume is
below a threshold pore volume value. Where a contiguous sequence of one or more pinched-out
cells exists in a column with an active (that is unpinched) cell above and below, the potential
exists for generation of a vertical pinchout NNC to replace the flow which would otherwise have
occurred through the pinched cells. Whether an NNC is actually generated depends on the
vertical thickness threshold specified and the details of the pinch criteria applied. Similarly for
areal pinchouts, an NNC is generated only if the gap between the active cells either side of the
row of areally pinched-out cells is less than the specified areal thickness threshold.
The Pore Volume tab (seen in Figure 15.4) allows setting a threshold criterion on the cell’s pore
volume, either using a constant value, or using a minimum pore volume property if one exists.
A cell is pinched out and made inactive if its pore volume is below the threshold pore volume.
(This threshold corresponds to the ECLIPSE MINPORV keyword).

NNCs
The Vertical Pinchout tab (Figure 15.5) sets a threshold criterion on the total vertical thickness
of the pinched-out column of cells, either using a constant value or using a minimum thickness
property, if one exists. You may choose whether to define the cell thickness using a pre-
calculated thickness property if one exists; otherwise, cell thickness is calculated on the fly.
In general, a vertical NNC is only generated if the total vertical thickness of the column of
pinched-out cells is less than the threshold thickness; however, the precise effects of the
thickness threshold criterion depend on the options set in the Advanced Options tab. (This
threshold corresponds to the first parameter of the ECLIPSE PINCH keyword).
Figure 15.5 The Vertical Pinchout tab
The Areal Pinchout tab (Figure 15.6) sets threshold thickness criteria that determine whether
an NNC is generated between a pair of cells separated in the X or Y directions by a row of one
or more pinched-out cells. An NNC is only generated if the total thickness across the row of
pinched-out cells is less than the threshold thickness. The thresholds can be set separately for
the X and Y directions. (These thresholds correspond to the values specified by the ECLIPSE
PINCHXY keyword).
Figure 15.6 The Areal Pinchout tab
The Advanced Options tab (Figure 15.7) allows detailed control of the options pertaining to
the generation of vertical pinchout NNCs.

NNCs
Figure 15.7 The Advanced Options tab
This tab has drop-downs corresponding to arguments 2 to 5 of the ECLIPSE PINCH keyword
(argument 1 is the vertical pinchout threshold, which is set using the Vertical Pinchout tab as
previously described). The other four arguments behave as follows:
Table 15.1 Effects of the PINCH keyword arguments
PINCH
keyword Meaning
argument
Argument 2 GAP An NNC is generated across a column of pinched-out cells between the
active cells at either end, even if the total thickness thus spanned exceeds
the threshold thickness, provided that no individual pinched-out cell in the
column exceeds the threshold thickness.
(The thickness of a column of cells is defined as the maximum absolute Z-
displacement found between corners of the topmost face of the topmost
cell, and the corresponding corners of the bottom-most face of the bottom-
most cell.)
NOGAP An NNC is only generated across the column of pinched-out cells
between the active cells at either end if the total thickness of the column,
calculated as described above, does not exceed the threshold thickness.
Argument 3 This option controls the total allowed gap between all pairs of adjacent cells in the
column. (The gap between a pair of cells adjacent in Z is defined as the minimum
absolute Z-displacement found between corners of the bottom face of the upper cell, and
the corresponding corners of the top face of the lower cell.)
If the total gap summed over all pairs of adjacent cells in the column exceeds the
specified value, then no pinchout NNC is formed. By default, this is set to an extremely
large value 1.0E20, implying that NNCs are not suppressed from this cause.
Argument 4 TOPBOT The NNC transmissibility is calculated between the active cells at either
end of the column of pinched-out cells only; the intervening cells are
ignored.
ALL The NNC transmissibility is calculated as the harmonic average of the
transmissibilities between all pairs of adjacent cells in the column of
pinched-out cells.

NNCs
Table 15.1 Effects of the PINCH keyword arguments
PINCH
keyword Meaning
argument
(The following option only has an effect if the preceding option is set to TOPBOT)
The transmissibility multiplier used in calculating the
TOP
transmissibility is taken from the topmost active cell only.
Argument 5 The transmissibility multiplier used in calculating the
transmissibility is taken from the minimum of the MULTZ values
ALL
across the topmost active cell and all pinched-out cells in the
column.
Aggregate pore volume option

Specifies what should be done with the existing pore volume of cells pinched out by the vertical
pinchout criteria specified above. There are five options:
• to ignore it (this is the ECLIPSE behavior); the pore volume is then effectively lost from
the reservoir
• to aggregate it with the pore volume of the uppermost of the NNC cells
• to aggregate it with the pore volume of the lowermost of the NNC cells
• to aggregate it with the pore volume of whichever of the NNC cells has the larger pore
volume
• to aggregate it with the pore volume of whichever of the NNC cells has the smaller pore
volume (the default).
In all cases, the pore volume of the pinched-out cells is set to zero.

NNCs
Structured gridder properties
Chapter 16
Structured gridder properties/Upscaler

• Importing and exporting grid and properties, see "File: Import, Export and Status" on
page 430.
• Types of upscaling, see "Phase folders" on page 434.
• Using the property editor tree, see "Property editor tree" on page 435.
• Using single phase upscaling, see "1 Phase" on page 451.
• Using two and three phase upscaling, see "2 Phase" on page 453.
• Using multilevel upscaling, see "Multilevel upscaling" on page 459.
• Exploring microgrid statistics, see "Diagnostics" on page 461.
The second half of the chapter contains technical background information on the algorithms
used by:
• "Upscaling and diagnostics" on page 463.
• "Upscaling relative permeability" on page 479.
• "Statistical diagnostics" on page 484.
• "Building the micro grid in a grid block" on page 485.
• "Single phase flow equations in curvilinear coordinates" on page 486.
Introduction
The Structured Gridder Properties window, formerly the Upscaler window, provides
facilities for creating, visualizing and editing simulation properties for structured grids. Options
include:
FloGrid User Guide Structured gridder properties 427

• Single phase upscaling methods, available for sampling and averaging geological
properties stored on the property model;
• Editing simulation grid properties;
• Importing properties generated by running an ECLIPSE simulation;
• Exporting grid geometries, properties and well trajectories.
The Structured Gridder Properties window can be opened using Tools | Upscaling..., which
is enabled when at least one structured grid exists within FloGrid.
The Structured Gridder Properties window has various menu options that can be selected,
and drop-downs that display the current structured grid and the current property scenario. A
Property Editor tree displays the initial properties that belong to the current grid, and the 1
Phase folder provides the interface to the single phase upscaling methods.
Note FloGrid supports property versioning for grid properties. This means that different
versions of, for example, permeability, can be upscaled to, edited and then compared,
for the same grid. The Property Editor tree displays the versions that exist for each
property type. Each version must have a unique name.
In the Structured Gridder Properties window, the 1 Phase folder has a table with a column
of PM Properties that can be upscaled from, and a column of Grid Properties that they can
be upscaled to. The table has one row for each property, for example, porosity or Permx,
permy, permz, that can be upscaled from.
If your model being upscaled from has more than one version of a property, it is the preferred
property that is used. The preferred property is the one that is highlighted in the main window
tree. You can set a different preferred property by selecting the appropriate property node for
the appropriate model in the main window tree.
The following upscaling methods are provided in FloGrid for the different properties.
Porosity
• Volume weighted average.
Absolute permeability, Kx, Ky, Kz

(For a technical explanation of the meaning of Kx, Ky, Kz on the fine and coarse scales see "The
meaning of Kx, Ky, Kz on the fine and coarse scale" on page 470.)
• Single phase 3D flow solution:
• no flow boundary conditions
• linear boundary conditions
• adjoint technique (a faster version of the linear boundary condition method)
428 Structured gridder properties FloGrid User Guide

• Algebraic averaging:
• harmonic arithmetic
• arithmetic harmonic
• arithmetic
• harmonic
• geometric
• power.
Known integer properties

Properties that are known to be integer quantities - rock type, saturation number (PVTNUM,
FIPNUM, EQLNUM) may be upscaled using the histogram method. The value on the geological
model with the largest volume within the simulation grid block is chosen. This value may be
output as an integer property on the simulation grid.
Other properties
All other properties are available for upscaling using the real number upscaling methods that all
offer the option to upscale with or without volume weighting. The following averaging methods
are available:
• arithmetic
• harmonic
• geometric
• power.
Note FloGrid does not use finescale net-to-gross information when upscaling. If data are
net-to-gross, they need to be used in the Property Model BUG Property Editor (see
"Geological Property model" on page 215) to create appropriate finescale gross
properties from finescale net property and net-to-gross data prior to upscaling.
Simulation net-to-gross data can be upscaled independently and used to create
simulation net properties using the Simulation Property Editor panel. If this is done
you need to export net properties and net-to-gross. Otherwise, there is no need to
output net-to-gross, as the upscaled properties are gross properties with an effective
net-to-gross of 1.
Grid diagnostics
In addition to the Property Model properties that can be upscaled, additional properties are
included in the list. These provide diagnostic information on the quality of the current grid:
• grid cell volume
• grid cell orthogonality
• grid cell inside out
• linear size - dx, dy, dz and tops.
A detailed explanation of each algorithm can be found in "Upscaling and diagnostics" on
page 463.

File: Import, Export and Status
The File menu contains the following options:
• "Import properties..." on page 430.
• "Export..." on page 430.
• "Status bar" on page 433.
Import properties...
Imports simulation results for the current upscaling framework.
ECLIPSE...
Imports files in the ECLIPSE format.
Generic (AVS)...
Imports files in the Generic (AVS) format.
Note If the simulation results data has inactive cells that do not match the current property
data within FloGrid, then you should read the initial file containing pore volume to
define which cells are active, before the restart files.
Eclipse .GRDECL...
Imports files in the .GRDECL and .GEC formats.
Export...
Opens the Export Data panel from which you can export grid geometries, grid properties and
well trajectories. Grid properties can also be exported from the Structured Gridder (see
"LGRs, Resizing, Aquifers and NNCs" on page 407).
Select output format

Displays the options available to export your current model. The ECLIPSE.GRDECL option
writes out the grid keywords for ECLIPSE input (COORD and ZCORN...). The ECLIPSE
.FEGRID and .EGRID options write out formatted and unformatted files respectively that
contain the grid geometry in an extensible format. The ECLIPSE .FGRID option writes out a
.FGRID file containing the corner point geometry only.
Select grid model

Selects the grid model to be exported.

Geometry
Each checked box indicates that the grid, LGR grids or faults are to be exported to the files
specified using the Set Location buttons.
Grid | Set location

Exports the current grid geometry.
Grid | Match host cell corners to resampled LGRs

This checkbox is ticked by default. It fixes an import problem in ECLIPSE when ECLIPSE
imports a grid that includes resampled cartesian LGRs, the cells of which protrude beyond their
host cells. It should generally be left ticked, though the host cell geometry will be distorted if
the exported grid is then read back into FloGrid and only the parent domain visualized.
Grid | Export grid geometry in map coordinate system

When the checkbox is unticked (the default), the grid geometry is exported with the xyz values
defined in the external units relative to the grid coordinate system. The grid coordinate system
is the one defined relative to the reference map coordinate system by the MAPUNITS and
MAPAXES keywords. When the check box is ticked, the grid geometry is exported with the xyz
values defined in the external units relative to the reference map coordinate system. The
GRIDUNITS keyword is exported with its second item set to “MAP” or “MAPFT” depending
on the external unit system.
LGR grid | Set location

Exports any LGRs in the current grid geometry.
Faults | Set location

Exports any I J faults in the current grid geometry. The ECLIPSE FAULTS keyword is exported,
which defines the faults in the model so that their transmissibilities can be modified using the
MULTFLT keyword.
Note This option is intended for use when faults are represented in the simulation grid with
the same I J pattern in all layers of the grid. If faults are modeled using the I J K Faces
option in the Vertical Gridding panel, no faults are exported using this option. The
MULTREGT keyword should be used instead.
MULTREGT | Set location

Exports the MULTREGT keyword. It is used to define transmissibility multipliers to be applied
between regions of the simulation grid based on MULTNUM values in adjacent cells.
Note This option may be used to define fault locations and transmissibility multipliers
across faults when the faults are modeled using the I J K Faces option in the Vertical
Gridding panel. The IJKFAULTMULTNUM property should be exported as the
appropriate MULTNUM property.

Properties
Selects the grid properties to be exported, optionally including the data for any LGRs. This area
is active when the Eclipse.GRDECL output format has been selected. Use the Set Location
button to name a destination file.
Grid properties | Set location

Exports the properties of the current grid mode.
LGR properties | Set location

Exports the properties of any LGRs in the current grid geometry.
Dual System
Select which simulation system you wish to export. There are three options - No dual
Properties, Dual Porosity and Dual Porosity/Permeability. The two dual options have the
same effect on the keywords exported. The changes make the exported GRID keyword section
consistent with a dual system simulation run.
The DPGRID keyword is exported and the number of grid layers doubled in the SPECGRID and
LGR (CARFIN or RADFIN) keywords. BOX keywords around each output property restrict the
property either the upper half of this doubled grid (single/matrix properties) or to the lower part
(fracture properties).
Properties Table
Available property types and versions are listed in the table. If a property type has more than
one version associated with it, these are displayed using the drop-down in the Version column.
You can choose which properties are exported by clicking in the Export? column.
If Dual Porosity or Dual Porosity/Permeability system has been selected, then any fracture
versions (that exist) of those properties whose Export? setting is Yes by default are also
exported by default. If No dual Properties is selected, then no fracture/matrix properties are
exported by default.
NNCs
Export Global NNCs | Set location
Exports the global NNCs of the current model.
Export LGR NNCs

Exports LGR NNCs. Where applicable, Trans. gives a choice of Transmissibilities.
Well trajectories
Exports any well trajectories for input into Schedule. The well trajectory file holds geometrical
information about how the wells intersect the selected grid model, and property information for
the intersected grid blocks.
Export well trajectories/set location

Exports any well trajectories in the current grid model. Use the Set Location button to name a
destination file.

Exporting Aquifers
In the Aquifers area of the Export Data panel, a selection of any aquifers defined on the model
can be exported. The Aquifers area options are activated when you select the GRDECL output
format. By default the Location is the same as that for the grid geometry. However some of the
aquifer keywords exported belong in different sections of the ECLIPSE deck from the GRID
section to which belong the other keywords written on export, so you may wish to specify a
different filename. The table contains a list of all aquifers in the FloGrid model that have
connections defined (that is those that have at least one cell in its cell selection and at least one
connection direction). Toggle the second column to YES for those aquifers you wish to export.
Note You cannot mix analytical aquifer types within an ECLIPSE run. However you can
export a mix of numerical and one type of analytical aquifer. You can also define
analytical aquifers of different types on a FloGrid model, and, when you export your
model, select a subset of these aquifers of the same type that you want to use in you
ECLIPSE run.
FloGrid exports the AQUDIMS keyword, an AQUANCON keyword with records for all the
exported analytical aquifers and AQUCON keyword with records for all the exported numerical
aquifers. It also exports the appropriate aquifer definition keywords for each of the exported
aquifers. The AQUDIMS keyword belongs in the RUNSPEC section. The connections keyword
AQUANCON and aquifer definition keywords AQUCT, AQUFETP and AQUFLUX belong in the
SOLUTION section. The AQUCON and AQUNUM keywords belong in the GRID section. The
exported file has comments in front of the keywords that state where the keywords belong. The
simulator link when writing the ECLIPSE deck inserts the appropriate keywords in the
appropriate section.
When all required selections have been made in the 5 panels, click on Export to export the data.
Status bar
Current model
Shows the currently-selected Structured Gridding Model for which the property information
is displayed. The contents of the window change to reflect a new choice of current model. The
text box to the right of the Current Model drop-down indicates which property model is being
upscaled from.
Property scenario
Shows the currently selected Property Scenario for which property model property
information is displayed. The list allows selection of any scenario on the same property model
from which the Current Model was built. The contents of the window change to reflect a new
choice of scenario.

Phase folders
There are four folders in the Structured Gridder Properties panel.
The 1 Phase folder allows you to select the properties from the Property Model for upscaling
and to choose a method of single phase upscaling. Depending on the selected upscaling method,
additional parameters may need to be specified, such as power values in the x, y and z directions
for power averaging.
The 2 Phase folder provides two and three phase upscaling functionality.
The Multilevel upscaling folder provides the functionality required to pass data between models
built at different scales. This is done by loading selected upscaled properties from one level into
SCAL records and then using the data in the SCAL records to create new properties on the fine
scale representation of the next level up.
The Diagnostics folder provides access to techniques for exploring microgrid property statistics
in individual coarse grid blocks. The algorithms are explained in the technical description - see
"Upscaling and diagnostics" on page 463.
Note The Upscaler must work with a consistent set of property data on the property model
(see "Geological Property model" on page 215). If more than one set of property data
exists on the property model, such as two porosity maps for one unit, the data from the
currently selected Property Scenario is used.
You can upscale the selected properties using different upscaling methods and create separate
versions of the upscaled simulation properties. Each version name must be unique. The
"Property editor tree" on page 435 displays the property type and versions that exist for the
current grid.

Phase folders
Property editor tree
Note This section describes the Property Editor tree on the left hand side of the Upscaler
panel (Structured Gridder Properties).
A more straightforward interface for creating and editing properties can be found in
the Property/Expression calculator.
To use the Property/Expression calculator, right-click on the Properties node of a
FloGrid model in the FloGrid main window or use the calculator icon at the top right
of the FloGrid main window.
Introduction
The Property Editor tree displays the initial property types and versions that exist in the current
structured grid.
The tree contains three types of node.
• The root node is called the Properties node and is the top level which holds all of the initial
properties belonging to the current structured grid.
• Below the root node are Property Type nodes, which group the initial properties according
to their property type name.
• The leaf nodes in the tree are Property Version nodes, which represent the initial property
versions which exist in the current structured grid.
Different functionality is available at different levels in the tree. Select one or more of the nodes
and use the right mouse button to bring up a pop-up menu. The different pop-up menus and their
options are described below.
• "Properties options" on page 435.
• "Simulation Property Editor panel" on page 436.
• "Property type options" on page 446.
• "Property information panel" on page 447.
• "Apply scope" on page 448.
Properties options
The Properties Options pop-up menu is displayed by selecting the Properties node in the
Property Editor tree and holding the right mouse button down over the selected node.
Create
Opens the Simulation Property Editor panel or brings it to the front if it is already on display.

Simulation Property Editor panel
The Simulation Property Editor panel allows you to manipulate simulation properties.
Simulation properties can be created, edited and deleted. It is also possible to run the Calculator
from this panel; special variables are made available to the Calculator when it is run in this
context.
Note Property Types are placeholders for their individual properties and property versions.
The idea is that many versions of the same property may exist and all be grouped under
one Property Type umbrella. All properties (versions) must be associated with a
Property Type, and the min. and max. values used to color these properties are taken
from all properties associated with a Property Type.
Properties can be both Initial and Recurrent, that is they can exist with the same name
to describe both the initial state and their changes through time. The family (Initial or
Recurrent) of the property to be edited or created is ascertained from the expression to be
evaluated, or assumed to be initial when running a calculator script.
Property to edit or create

The Property to edit section of the Simulation Property Editor panel holds the details of the
property to which the changes are to be applied.
Figure 16.1 Property to edit or create panel
Type
Lists the property type of the property to be edited. Property Types with existing property
versions are first in the list and indicated by an asterisk.
Version
Holds the names of the property versions corresponding to the property type displayed in the
Type drop-down. If no versions of the Property Type currently exist, (none) is displayed.
Note that property versions read from the simulator output are not editable. This is to guard
against the concept of altering simulator output values directly. To edit these properties first
make a copy of the property and then edit the copy.
Property type creation parameters

Sets the creation details for a property and is active when a new property is to be created. New
properties take their data type (Integer or Real) from their Property Type; the Real and Integer
radio buttons are not selectable, and simply indicate the type of the currently selected Property
Type.

Create Property Type panel
This dialog opens when you click on Create Property Type... to provide you with type
creation options. Once created, these property types are available for the creation of new
properties.
Figure 16.2 Create Property Type panel
Note Property Types are placeholders for their individual properties and property versions.
The idea is that many versions of the same property may exist and all be grouped in
one Property Type. All properties (versions) must be associated with a Property
Type, and the min. and max. values used to color these properties are taken from all
properties associated with a Property Type.
Property type name

Specifies the name of the new property type.
Select quantity
Selects what type of quantity a property type is (for example, area, length, ratio, etc.). The
choice of quantity dictates which units are used with a property type.
Integer or Real radio buttons

Select Integer or Real to determine the type of the data to be associated with this property type.
Info
This text box allows additional information to be provided about the property type.
Select families
Defines which property families the created property type belongs to. Families are not currently
used by this product so this field can be ignored.

Figure 16.3 Property creation parameters section
New property
When checked, creates a new property. The type of the property to be created is ascertained from
the expression to be evaluated or assumed to be initial when running a Calculator script.
The property must be specified with the radio buttons as being Cell-based or Face-based.
Inactive cells
Stores values for inactive cells.
LGRs
Stores values for local grid refinements.
Edit scope
Specifies which cells the edit is to be applied to.
Figure 16.4 Edit scope section
All cells
Applies the edit to all the cells that exist for the property.
Selected cells
Applies the edit to the cells selected by being currently on display on the 3D Viewer.
Generate by
The Generate by section of the Simulation Property Editor panel defines the method to
compute the property being edited. Four methods are available:

Figure 16.5 Generate by section
Expression
The Expression folder allows you to specify a constant or arithmetic expression with which to
calculate the property. Two operand drop-down lists contain the names of all available
Initial and Recurrent properties, separated by an operator list. You may select a property
or enter a constant value into either of these fields. The operator list contains available
arithmetic operators plus two difference operators, ‘T+1-T’ and ‘T-T0’ which operate only
on the recurrent property specified by the first operand field. The second operand is only
available when an arithmetic operator is selected.
Expressions mixing Initial and Recurrent properties are allowed, as is specifying a
particular report step with which to operate.
When you click on Apply, the expression is evaluated to discern the type (Initial or
Recurrent) of property to be created and / or edited. If a new property is being created, a
property of this type with this name must not already exist. Likewise, if an existing property is
being edited, an editable property of the required type and name must already exist.
The following criteria describe the type of property required for different expressions:
Table 16.1 Examples of operands and property types
operand 1 operator operand2 Resultant property type

Constant Initial
Constant * Constant Initial
PORV Initial
PRESSURE Recurrent
Constant * PORV Initial
Constant * SOIL(1) Recurrent valid only at step 1
Constant * SOIL Recurrent valid at all SOIL steps
DX * PORV Initial
SOIL(1) * PORV Recurrent valid only at step 1
SOIL * PORV Recurrent valid at all SOIL steps
SOIL(1) * PRESSURE(1) Recurrent valid only at step 1
SOIL * PRESSURE(1) Recurrent valid at all SOIL steps
SOIL(I) * PRESSURE(1) Recurrent valid only at step 1
SOIL(I) * PRESSURE Recurrent valid at all PRESSURE steps
SOIL * PRESSURE Recurrent valid at all common steps

Table 16.1 Examples of operands and property types (Continued)
operand 1 operator operand2 Resultant property type

SOIL(6) - SOIL(2) Recurrent valid only at step 2
SOIL T+1-T Recurrent valid at nSOIL-1 steps
SOIL T-T0 Recurrent valid at all SOIL steps
Notes
1 Property name qualifiers must be in brackets ‘( )’. Valid qualifiers are integer values
(depicting a particular report step), the letter ‘I’ to force the use of the Initial version
of a property or ‘R’ to force the use of the Recurrent version.
2 In this table, ‘*’ is used as an example and can be replaced by any arithmetic operator in
the list. PORV and DX are used as example Initial properties and PRESSURE and SOIL
as example Recurrent properties.
3 All expressions are transposable.
Advanced Expression
Use the Advanced Expression folder when you want to edit or create properties using a more
complex single arithmetic expression than is provided for in the basic expression folder, yet
without programming the calculator. The expression can include conditions, so different editing
algorithms can be applied to different sectors of the model.
When you click on this folder tab another panel appears: the Expression Builder, in which you
type and edit your expression. When you click on Apply on the Expression Builder, the
expression is analyzed for correct syntax; if validated, it is passed through to this folder.

Expression Builder panel
Figure 16.6 Expression Builder panel
This is the panel where the advanced expression is typed in or edited, and validated.
Available properties
Available operations
These fields are provided for reference. They list all the properties and operators that are known
and can be used in the expression.
Enter expression here

This window is where you type in your expression. As with a program, it can be spread over
several lines. Comments can be inserted too.
Load expression
Save expression
If a particular expression is likely to be used many times it can be saved to, and loaded from, a
file.

Default value
This field allows you to enter a fixed value to be assigned to the output property for cells which
do not meet any of the conditions in the expression. It is the same as using ELSE with a fixed
value.
Error value
This field allows you to enter a fixed value to be assigned to the output property in cells where
the expression could not be evaluated, perhaps because of errors in the property or in your
expression. An example of such a situation would be if the expression contained LOG (PERMX),
and PERMX was 0.0 in a cell.
Clicking on Apply validates the expression. If valid the expression is passed on to the
Simulation Property Editor, where it can be applied.
Expression syntax
Expressions may span as many lines as is necessary, and comment lines may be inserted
anywhere in the text by including “--” at the start of the line.
There are several types of expression. These are:
1 Single-value arithmetic expression
Standard engineering expressions that evaluate to a single value use the normal
mathematical rules of operator precedence. These can be overridden using parentheses to
bracket operations.
Example: 0.314 * SQRT(PERMX / PORO)
The full list of operators that can be used in arithmetic expressions is given in the following
table.
Table 16.2 Arithmetic operators grouped by precedence, highest at top
Operator symbol Operation name

SIN sine
COS cosine
TAN tangent
ASIN arc-sine
ACOS arc-cosine
ATAN arc-tangent
SQRT square root
LOG log to base 10
ALOG antilog to base 10
LN log to base e
EXP exponential
ABS absolute (positive) value
INT integer value
** raise to power
* multiply
/ divide

Table 16.2 Arithmetic operators grouped by precedence, highest at top

% modulo
+ plus
- minus
2 Relative conditions
Conditions are expressed by simply joining single-value expressions together using
relational operators. In turn they can be joined using combinational operators to make
complex conditions. Conditions cannot be used on their own - they can only be used as part
of a conditional expression.
Example: PORO > 0.25 AND (PERMX > 500 OR PERMY > 500)
The list of these operators is given in the following table.
Table 16.3 Relative and combinational operators in order of precedence

GT, > Greater than
GE, >= Greater than or equal to
LT, < Less than
LE, <= Less than or equal to
EQ, = Equal
NE, <>, != Not equal
AND and
OR or
3 Conditional expression
A full conditional expression is written using a simple IF-THEN-ELSE (or ELSEIF)
structure.
Note Because only single expressions are processed here, this means that any conditional
expressions must begin with an IF.
The syntax for a conditional expression is:

IF (relative condition 1) THEN value expression 1
ELSEIF (relative condition 2) THEN value expression 2
ELSE value expression 3
The ELSEIF and ELSE statements are optional. You can have as many ELSEIF
statements as you like.
Example:
IF (SQRT(PERMX/PORO) > 150) THEN 1
ELSEIF (PORO>0.2) THEN 2

ELSE 3
Properties
You can use any Recurrent or Initial properties in the formulation of your expression,
and each may appear in the expression as many times as you want. You cannot specify
individual timesteps to be used for a Recurrent property.
Because more than two properties may be used, the Initial/Recurrent status of the output
property has been simplified from that in the simple expressions. If the expression you create
uses only Initial properties (or numerical values) the resulting property is an Initial
property too. If however you use any Recurrent properties in your expression the expression
is evaluated at every timestep, and your resulting property is Recurrent.
Calculator
Figure 16.7 Calculator folder
With this folder selected, you can enter (or select using the browser ) the location of a
Calculator script in the Calculator file text entry field. The Calculator script is run within the
context of the Simulation Property Editor; this panel allows a number of special variables to
be made available for optional use within the Calculator script. These include many of the
values set interactively on the Simulation Property Editor panel. For more details see the
section on simulation property editing in the Calculator appendix.
All calculator parameters including those set by this panel may be reset prior to execution of the
calculator script by checking the Reset Calculator prior to execution check box.
Run Differencing
Figure 16.8 Run Differencing folder

The Run Differencing folder allows you to compute properties that are the difference in a
property between simulation runs. The Import File button presents you with a file browser with
which to select an ECLIPSE INIT or Restart, or AVS format file to difference with.
Properties common to the current model and the selected file are displayed in the Subtract...
drop-down list. Select a property to be differenced from this list; the property read from the file
is subtracted from the model’s property to create the new property given by the Property Type
and Version fields.
Note Importing a new file clears the previous file and its available properties.
Boundary Interpretation
Figure 16.9 Boundary interpolation
Lists all polygon boundaries created. The interpolation takes place between the values defined
by those polygons.
Points Interpolation
Figure 16.10 Points Interpolation

Interpolation takes place between the vertices of the boundary polygons defined.
Figure 16.11 Control buttons
Delete
The Delete button displays a question box asking if you are sure you wish to delete the selected
property. If the property exists as both Initial and Recurrent you are given the option to
delete one or the other or both. Deleting a property removes it from the application permanently.
Property type options

The Property Type Options pop-up menu is displayed by selecting a single Property Type
node in the Property Editor tree and holding the right mouse button down over the selected
node.
Note Property Type options only apply to a single selected property type.
Property type information

Opens an information panel displaying details common to all property versions of the selected
property type:
• Units - the units for the property type.
• Minimum value - the global minimum for all properties of the selected type in the
application.
• Maximum value - the global maximum for all properties of the selected type in the
application.
Create
Opens the Simulation Property Editor panel (see "Simulation Property Editor panel" on
page 436) or brings it to the front if it is already on display.
Property version options

The Property Version Options pop-up menu is displayed by selecting a Property Version
node in the Property Editor tree and holding the right mouse button down over the selected
node.
Note The Property Version Options can only be applied to single selections. If multiple
versions are selected, an error message is displayed.
Property information
Opens the Property Information panel displaying details for the selected property version.

Property information panel
Displays details for the selected property version, including information about the way the
property values have been generated.
For the property version, the following information is displayed:
Property name
The name of the selected version. The name cannot be changed here; this must be done using
the Rename option from the Property Version Options pop-up menu.
Property Information
Statistics
Min
The minimum value of the property version.
Max
The maximum value of the property version.
Property edit records

Displays a list of property edit records, in order of their creation. Edit records are created when
certain operations are performed which create or change the property values. These operations
are:
Edit by expression
Creates property values using a mathematical expression. Edits of this type initially have the
name Expression edit x, where x is a number uniquely identifying the edit operation.
Edit by calculator
Creates property values using a calculator script. Edits of this type initially have the name
Calculator edit x, where x is a number uniquely identifying the edit operation.
Edit from within calculator script

Commands within a calculator script or a command log can be used to change the values of a
property. An edit of this type initially has the name Calculator script edit x, where x is a
number uniquely identifying the edit operation.
Upscaling
Both single-phase and two-phase upscaling runs generate new property values. These edit
records initially have the name Upscaling run x, where x is a number uniquely identifying the
upscaling run.
You can select a record from the list, to display further information about the edit record in the
Record Details area of the panel.

Record details
Displays information about the property edit record currently selected in the Property Edit
Records list.
Name
This is the name by which the edit record is identified in the Property Edit Records list.
Initially, the name is set according to the nature of the operation that created it (see above), but
a new name can by typed into this field. The name of the edit is changed to the new name when
another edit is selected from the list, or when the Apply button is clicked.
Operation information
Information about the operation used to change the property values is displayed. This
information includes:
• Date and time the edit record was created (that is when the operation was performed).
• For edits by expression - the mathematical expression used to change the property values.
• For edits by calculator - the name and path of the Calculator script used to change the
property values.
For upscaling run edit records, the information stored about the method includes the parameters
used for the upscaling:
• Method - the upscaling method used to create the selected property version.
• PM property - which property was upscaled from the Property Model.
• Additional Data - details of any extra user-defined data that was specified.
For two-phase upscaling runs, the following information is also present:
• SCAL group - the name of the SCAL record group created by this run.
• Single-phase permeability - the name of the upscaled permeability property used in the
upscaling run.
Edit scope information

Information about the selection of cells on which the operation was performed is also displayed.
When the Simulation Property Editor is used to change property values the user can choose
whether to perform the edit on all cells, or only to those cells which are selected in the 3D
Viewer. You can also make this choice when an upscaling run is performed. The choice of cells
to which the operation is applied is the Edit Scope. This area of the panel gives information
about the methods by which cells were selected.
Comments
Displays comments about the record. These can be added or modified by typing into the text
area. The comments are added to the record when another edit is selected from the list, or when
the Apply button is clicked.
Apply scope
As detailed above, a property edit can be applied either to the entire grid or to the cells which
are selected in the 3D Viewer. Information about the Edit Scope is stored with the record of
that edit. When one of these edit records is selected from the Property Edits list, then a button
Apply Scope is present on the panel.

When you click on this button, the selection of cells (that is the Edit Scope) used for the edit
on the original grid is reproduced as far as is possible on the grid which is currently active on
the 3D Viewer. This does not necessarily have to be the same grid to which the edit was
originally made - the Edit Scope is interpreted in such a way that the selection is made on the
currently active grid. This allows you to replicate on a new grid a set of cell selection criteria
that were found to be useful for performing property edits on a different grid.
The exact behavior depends on the choice of Edit Scope for the edit:
All cells
If the edit was applied to all cells in the grid, then the button causes the entire grid to be selected
in the 3D Viewer. Any selection criteria set by you are removed.
3D selected cells
Selections in the 3D Viewer are made using the various types of cell selection criteria, using
different menu options. If the edit was applied to the cells selected in the 3D Viewer, then the
Edit Scope contains a list of the criteria used to select those cells. Those criteria are used to
select cells on the currently active grid, as far as is possible. Any cell selections previously made
on the active grid are removed. The different types of cell selection criteria are detailed in the
documentation for the 3D - see "3D Viewer" on page 107.
Since the currently active grid may differ from the grid to which the edit was originally applied
(the original grid) in its structure, dimensions, properties and other details, not all the criteria
may be applicable to the currently active grid. In general, if the parameters used for the selection
criteria are completely appropriate to the currently active grid, then the criteria are applied. If
the parameters are partly appropriate to the current grid, then only that part that is applicable is
used. If the parameters are entirely inappropriate to the current grid, then the selection criteria
are ignored. This is explained in detail for each type of selection criterion.
Domains
Domains exist on a grid in a hierarchy. If a domain exists on the active grid in an equivalent
place in the hierarchy to that of the selected domain on the original grid, then that domain is
selected in the current grid. Otherwise, the selection criteria are ignored.
This is also true for criteria of any other type that apply to specific domains. If there is no domain
on the active grid in an equivalent position to the domain for a criterion, then that criterion is
ignored.
Note Note that a Global domain exists on all grids. A Global domain selection, or any other
selection specified for the Global domain, always has an appropriate domain on the
active grid.
Property threshold
If the property for which a threshold was set does not exist on the active grid, then the criteria
are ignored. The property must be of the same type (initial or recurrent) and contain data of the
same type (integer or real). If the property does exist on the active grid, then those cells on the
active grid whose property value lies within the specified range are selected.
If the threshold was set to be ignored on the original grid, then it is set to be ignored on the active
grid.

IJK slice
If the original grid had larger I, J or K dimensions than the active grid, then it is possible that
some of the slices selected on the original grid will be for I, J or K values that do not exist on
the active grid. In this case, those slices are ignored; only slices for I, J and K values that do exist
on the active grid are selected. If the Honor IJ Slicing option was selected for the criteria on
the original grid, then it is also applied to the active grid.
IJK slices are specified for a particular domain. If an equivalent domain does not exist on the
active grid, then the criterion is ignored (see "Property threshold" on page 449).
IJK extents
the block of cells selected on the original grid includes cells with I, J or K values that do not
exist on the active grid. In this case, only those values that exist on the active grid are used; all
others are ignored.
IJK extents are specified for a particular domain. If an equivalent domain does not exist on the
active grid, then the criterion is ignored (see "Property threshold" on page 449).
Volume of interest (grid cells)

the block of cells selected on the original grid includes cells with I, J or K values that do not
exist on the active grid. In this case, only those values that exist on the active grid are used; all
others are ignored.
Grid cell volumes of interest apply only to the global domain, which exists on all grids.
Volume of interest (boundaries)

Several lists of boundaries are maintained by the application. If a boundary of the same name
exists within the same list, then the selection criterion is applied to the active grid. Otherwise,
the criterion is ignored.
Copy
page 436) or brings it to the front if it is already on display. The editor panel is configured to
reflect the property type and version of the selected node to be copied.
Edit
page 436) or brings it to the front if it is already on display. The Editor panel is configured to
reflect the property type and version of the selected node to be edited.
Rename
Opens the Property Renamer panel in which a new name for the selected version can be
entered.

1 Phase
This folder provides the single phase upscaling functionality. It contains a table listing the
Property Model properties in the current Property Scenario that can be upscaled for the
current model, an Upscale button and a panel that may contain additional data required for the
currently selected upscaling method and buttons to choose the scope of the upscaling run.
This folder contains the following options:
• "PM properties" on page 451.
• "Method" on page 451.
• "Upscale" on page 451.
• "Grid properties" on page 451.
• "Additional data panel" on page 451.
• "Edit scope" on page 452.
• "Upscale" on page 452.
PM properties
Lists the properties that can be upscaled from the current Property Scenario on the Property
Model associated with the current grid.
Method
Lists the methods available for upscaling the property. The drop-down list allows you to choose
the method of upscaling. If the method requires extra user-defined information, appropriate
fields will appear in the additional data panel. Several methods are available that are described
in detail in the technical description. See "Upscaling and diagnostics" on page 463.
Upscale
Selects which property to use for upscaling. From the drop-down list you choose either YES or
NO. The default selection is YES.
Grid properties
Displays the name of the upscaled simulation property version that is to be created. A default
name is provided, which can be overridden. All simulation property version names must be
unique, regardless of what property type they belong to.
Additional data panel

This panel holds extra fields for upscaling methods requiring additional user-defined data. The
contents of the panel either inform you that the currently selected Property Model property and
upscaling method do not require additional data or the appropriate data entry fields are
displayed.

1 Phase
Edit scope
These buttons allow you to choose to upscale properties onto all cells on the grid, or only onto
the cells that are selected in the 3D Viewer.
Upscale
Runs the upscaling algorithms for the selected properties. If the specified property version
already exists on the simulation grid, it is overwritten; otherwise a new property version is
created and displayed in the Property Editor tree. A summary of the upscaling run is output to
the Log Window.

1 Phase
2 Phase
This folder provides two and three phase upscaling functionality. Before two- or three-phase
upscaling is possible the following minimum requirements must be met:
1 Porosity must exist on the fine scale.
2 Permeability must exist on the fine scale.
3 A SATNUM property must exist on the fine scale.
4 An upscaled permeability must exist on the coarse scale.
5 A SCAL group of records containing kr curves corresponding to the fine scale SATNUM
must exist for the desired phase combinations.
• "Phase combination" on page 453.
• "Upscaling method" on page 453.
• "Input SCAL group" on page 454.
• "Upscaled permeability" on page 454.
• "Root name" on page 455.
• "Output curves" on page 455.
• "Output group" on page 455.
• "Record prefix" on page 455.
• "Binning" on page 456.
• "2-phase upscaling options" on page 456.
• "Edit scope" on page 457.
Phase combination
The choices are Oil-Water, Oil-Gas, Gas-Water and Oil-Water-Gas. The program checks
that the input group of SCAL records contains curves for the appropriate phase combination.
For the 3-phase case, the SCAL records for the fine scale must be associated to link the oil-water
and oil-gas data. See the "SCAL User Guide" for more details.
Upscaling method
Four methods are currently available. They are described in detail in the technical appendices.
The methods are:
Majority vote
The curve for the coarse cell is taken to be the first one occupying the greatest volume in the
microcells inside the coarse cell.
Constant saturation
This method assumes the saturations are the same in each microcell.

2 Phase
Capillary equilibrium
This method assumes the same capillary pressure in each microcell. It is appropriate to use when
the flow rates are small. The saturation in each microcell can then be determined from the fine
scale pc curves. To use this method the SCAL records must contain pc data as well as kr.
Constant fractional flow

This method assumes the fractional flows are the same in each microcell. It is appropriate to use
when the flow rates are high. The saturation in each microcell can then be determined from the
fine scale fractional flow curves. In order to calculate the fractional flow the viscosities of the
phases are required. These must be specified in the first record of the input SCAL group. The
data should be entered using the SCAL Record Editor in the Properties panel. The same
viscosity ratio is assumed throughout the region to be upscaled.
Capillary pressure is upscaled using a capillary equilibrium method when Kr is calculated either
by the capillary equilibrium method or by the constant fractional flow method. When the
constant saturation method is used, upscaled Pc is calculated as a pore volume weighted average
of the fine scale Pcs. When the majority vote method is used, upscaled Pc is calculated as a
volume weighted vote on the fine scale Pcs.
The set of upscaled properties varies according to the upscaling method, the directionality and
whether binning is active. The index into the list of tables is always created (SATNUM, KRNUMX
etc.). The saturation end point scaling limits (SWL, SWU, SWLX etc.) are always calculated
unless binning without normalisation is active. If binning with normalization the vertical end
point scaling properties (KRW, KRGX, PCW etc.) are also created.
In the oil-water-gas case two sets of upscaling are done, first for the phase combination in the
input SCAL group and then for the phase combination in the associated records. The upscaled
oil-water and oil-gas curves are then associated. If necessary the oil-gas curves are renormalized
to have consistent Swi values with the oil-water curves. The association is done in the direction
specified by the input SCAL group, that is, if the input SCAL group is oil-gas then the output
oil-gas curves are associated with the output oil-water curves. In this case when outputting the
curves the oil-gas group should be specified.
Input SCAL group

This is the name of the SCAL group to which the fine scale SATNUM property refers. The
records in the SCAL group must contain Kr data. In addition Pc, J-function and viscosity data
may be required. If oil-water-gas systems are to be upscaled the records in the group must be
associated, to provide the linkage between the oil-water and oil-gas data. Only non-root groups
appear in the list. This is to avoid mistakes when using a root group and upscaling, which adds
more records onto the root group, and then accidentally reusing the group.
Upscaled permeability
This is the coarse scale permeability used to rescale the effective mobilities generated for each
point on the upscaled curves. The list contains an entry for each upscaled permeability that has
X, Y and Z components. The name in the list corresponds to the name of the X component with
the X removed.
Note Permeabilities read from a file or created by the Property Editor are not available.

2 Phase
The upscaling method used to calculate the effective mobilities is the same as the method used
for the upscaled permeability. The method can be found on the Property Information panel by
using the right mouse button menu on the property tree.
Root name
This name is prepended to the name of each of the coarse properties created during a 2-phase
upscaling run. For example if the root name is trial1 then properties with names such as
trial1_SATNUM_v2 and trial1_SWL_v4 are created. The root name may be blank.
Output curves
Upscaled curves are created with the Kr and Pc merged and the oil-water and oil-gas records
associated for the 3 phase case ready for direct output to the simulator. Curves may be written
from the SCAL Keyword Generator panel. The upscaled curves should be specified as the
Assignment group. See the "SCAL User Guide" for more details.
It is important to retain the correspondence between the SATNUM type property and the group
of tables it applies to, especially as the two quantities are exported from different panels. The
Property Information panel (right mouse button on property tree) gives the SCAL group for
the two-phase properties.
Output group
This is the name of the SCAL group into which the upscaled records are put. It is always
required. The group must be unique, as there should be a one to one correspondence between
the upscaled curves and the generated SATNUM property. For the 3 phase case two output groups
are created, one for the oil-water upscaled curves and one for the oil-gas. These groups have
_OW or _OG appended to the specified output group name.
The records in the output group are always new except when using the majority vote method
where the records are merely pointers into the set specified as the input group.
Record prefix
The string specified here is prepended to the name (SAMPLENAME attribute) of the upscaled
record. The name of the upscaled record is constructed in different ways depending on the
upscaling method and if binning is active. The rules are as follows. In these examples assume a
record prefix of T1 has been specified:
Majority vote method

Names are taken from the names of records in the input SCAL group. No new records are
created.
No binning, 2 phases, all other methods

Names are of the form T1_UP_NN, where the NN is the cell index of the coarse cell on the
simulation grid.
Binning, 2 or 3 phases, all other methods

Names are of the form T1KRREC PCREC where KRREC is the name of the record in the input
group whose Kr was closest to the upscaled curve and PCREC is the name of the record in the
input group whose Pc was closest to the upscaled curve.

2 Phase
No binning, 3 phases
Names are of the form T1_OW_UP_NN, T1_OG_UP_NN.
Binning
Bin curves
If this box is checked then the upscaled curve is compared with the curves in the binning
template group and the closest curve in the template group is selected. The comparison is done
by a least-squares method. The Kr and Pc are done separately and the selected Kr and Pc are
merged into a new record that is added to the output group. Because of this there may be up to
twice as many records in the output group as in the template group. However, there are typically
many fewer than this.
If this box is not checked, that is binning is off, two supplemental attributes are created in the
new SCAL records. These are SCALE and DIRECTION.
• SCALE gives an indication of the scale at which the upscaling was done. It is calculated
from the coarse grid dimensions and the nx, ny, nz and given to one significant figure. It is
a useful indicator when doing multilevel upscaling.
• DIRECTION is a text attribute with the value Average, X, Y or Z according to whether
directional curves are being calculated and the actual direction of the curve in the record.
Use normalization
If this box is checked then both the upscaled curves and the template curves are normalized
before being compared. If normalization is used then additional upscaled end point scaling
properties such as KRW, PCW are produced and these should be used along with the curves in the
output group when performing the simulation. If normalisation is off then the assumption is that
the template curves show sufficient variation that they may be used directly in the simulation.
Group to bin to
This is the SCAL group containing the records to which the upscaled curves are compared. It is
also known as the template group. In the 3-phase case these records must be associated to give
the oil-water oil-gas linkage.
Note Kr and Pc data are copied from records in this group and remerged into records in the
output group.
Options...
Displays the 2-Phase Upscaling Options panel.
2-phase upscaling options

Use J
If this box is checked then the capillary pressures required during upscaling are calculated by
using J-function scaling.

2 Phase
If J-function upscaling is required then additional data is required. Both porosity and
permeability must be available on the fine scale. In addition, the parameters required to convert
from J-function to Pc must be set in the first SCAL record of the input SCAL group. The
required data are interfacial tension and contact angle. If unset, the contact angle defaults to 0
degrees. The SCAL records in the input group must contain J function tables (for example
JPCOW etc.) instead of or as well as the usual Pc data. The "SCAL User Guide" gives full details
on how to convert Pc to J.
When the J-function option is used the Pc on the fine scale is calculated from the J-function for
the fine cell and the porosity and permeability for the fine cell.
Directional output
Calculates directional Krs. The appropriate directional index and end point scaling properties
are also calculated.
Note that the directional versions of the SATNUM property are KRNUMX, KRNUMY and KRNUMZ.
If the box is unchecked then the three directional relative permeabilities are arithmetically
averaged before being exported into the output group.
For both the directional and non-directional case a single output group of curves is created. In
the directional case with no binning three times as many curves are created. The first three
curves are for the first upscaled cell and correspond to the X, Y and Z directions respectively.
The next three curves are for the next coarse cell, and so on. Hence the numbering in the
KRNUMX property is 1, 4, 7, …, and for KRNUMY 2, 5, 8 etc.
Target saturation increment

This number is the minimum number of points on the upscaled curves. The actual number of
points may be up to twice the specified number in order to get better definition of the upscaled
curve. The algorithm to calculate the point placement on the curves is described in the technical
appendices. The time taken to do the upscaling varies linearly with this number.
Min sat separation

This number, called Alpha1 in the command files, prevents the saturation interval between
average saturation values on upscaled capillary or fractional flow curves from going lower than
Alpha1.
Min sat separation on merge

This number, called Alpha2 in the command files, prevents the saturation interval between
average saturation values on merged upscaled relative permeability and capillary pressure
curves from falling below Alpha2.
Edit scope
These buttons allow you to choose to upscale properties onto all cells on the grid, or only onto
the cells that are selected in the 3D Viewer.

2 Phase
Caution The two-phase Upscaler does not check that the cell selection for two-phase
upscaling is identical to that of the single-phase upscaling that must be performed
in advance. You must ensure that the cell selection on the two-phase run is
identical to that used for the corresponding single-phase property used to
normalize the two-phase relative permeabilities. Failure to make identical
selections creates meaningless results.

2 Phase
Multilevel upscaling
This folder provides the functionality required to pass data between models built at different
scales. This is done by loading selected upscaled properties from one level into SCAL records
and then using the data in the SCAL records to create new properties on the fine scale
representation of the next level up.
Properties are typically created by setting range information in the SCAL record and using the
Property Model Property Editor to create the property using the SCAL records option.
Note that the porosity and permeability properties are automatically loaded into the SCAL
records created during 2-phase upscaling.
Note Only initial properties can be loaded into SCAL records. Recurrent properties are not
recognized.

• "Record prefix" on page 459.
• "Group to load" on page 459.
• "Sub group / parent" on page 459.
• "Property table" on page 459.
• "Load SCAL" on page 460.
Record prefix
A SCAL record is created for each cell on the coarse model. The record is given the name
prefix_NN where NN is the index of the coarse cell.
Group to load
This is the SCAL group into which the new records containing the upscaled values are placed.
If it does not exist it is created.
Sub group / parent

The new group may optionally be a sub group of an existing group. These fields control that
option.
Property table
The table contains a row for each property type in the current model. If there is more than one
version of the property then the required version may be specified using the drop-down choices
in the Version column. Data is extracted into the SCAL record if Yes is specified in the Load
column. Several items of data may be extracted into each SCAL record at the same time.

Load SCAL
This option loads the selected property data into the designated SCAL records. If the property
type of a selected property is a known SCAL record attribute, for example porosity or
permeability, the value will be loaded directly into the appropriate SCAL record attribute
(PORO, XPERMEABILITY, YPERMEABILITY, ZPERMEABILITY). Otherwise a
supplemental attribute of the appropriate type (integer or real) will be created. The supplemental
attribute is given the same name as the property version.
One SCAL record is created for each coarse cell - confirmation is required if more than 100
records are being created. When records are created by 2 phase upscaling a SCALE supplement
is automatically created.

Diagnostics
This folder provides access to techniques for exploring microgrid property statistics in
individual coarse grid blocks. A choice of up to four methods is presented in the drop-down
menus obtained by selecting items in the Method column. Each of these items requires extra
information. The algorithms are explained in "Upscaling and diagnostics" on page 463.
• "Standard deviation" on page 461.
• "Prob outside [av - scale, av + scale]" on page 461.
• "One-point probability" on page 461.
• "Two-point probability" on page 461.
Standard deviation
A check box appears enabling you to cancel the use of relative dispersion to normalise the
standard deviations in the grid blocks.
Prob outside [av - scale, av + scale]

A numerical entry box appears where the value of scale may be typed. This requires previous
examination of the data set, to choose a suitable value.
One-point probability
Two numerical entry boxes appear where the min. and max. values of an interval may be typed.
The value is the fraction of microcell values in the grid block that fall within the specified
interval.
Two-point probability
The first three integer entry boxes, I-direction, J-direction and K-direction allow the definition
of the I, J and K increments for the separation vector. This is in terms of numbers of microcells.
The next four numerical entry boxes, First Min, First Max, Second Min and Second Max
define the two intervals used in the calculation. The final entry is the Cutoff Increment.
The meaning of the two-point probability calculation is given in "Upscaling and diagnostics"
on page 463.
Create fine model view

This option, on the Structured Gridder File menu, makes all the simulation properties
associated with the current gridding model, including all results data, available on the property
model from which it was generated. This can take some time if upscaling has not already been
performed for a particular simulation model.

Diagnostics
Properties are generated on the property model in a new property scenario with a scenario name
corresponding to the current gridding model. These properties are then viewable on the fine
scale property model the next time the Property Model Viewer dialog is reopened by selecting
the new scenario and the appropriate back populated simulation property. Back populated
properties are also available to be exported back onto the external model representation from
which the model was built (this option is only supported for Rescue models).
There is only one option for making simulation properties available on property models. This is
a back population algorithm that simply assigns to each geological cell the ID of the simulation
cell to which the geological cell contributes during upscaling. All simulation cell properties are
then transparently made available through reference to this ID (GeoSimCellIndex). Back-
populated property model properties are therefore constant in each simulation cell. Property
model cells that do not lie within the simulation grid are given null values.
Note This technique for accessing simulation properties minimizes the amount of memory
required to make the simulation properties available on the property model.
Note The back population option is only available for 3D property models.

Diagnostics
Upscaling and diagnostics
Introduction
In the following section we introduce upscaling and describe the algorithms used by the FloGrid
upscalers and grid block diagnostic methods. This covers both single and two-phase upscaling.
This section contains technical background information on the following:
• "Constructing the micro grid" on page 464.
• "Sampling the properties" on page 464.
• "Geometric upscalers" on page 467.
• "Upscaling non-dimensional real properties" on page 468.
• "Upscaling porosity" on page 470.
• "Upscaling absolute permeability" on page 470.
• "Upscaling SATNUM" on page 476.
• "Upscaling capillary pressure" on page 476.
Definition of upscaling
Upscaling is a process of approximating one model by another.
We call these models the input model and the output model. Each model comprises grids of cells
or blocks with associated properties. The blocks on one grid overlap those on the other, and so
an averaging procedure is required that defines a property on the output model in terms of the
properties on the input model. Generally the input model is a geological model and the output
model is a reservoir simulation model, but other combinations are possible.
Generally the input model has many more grid cells than the output model, but again this is not
necessarily so. Nevertheless, for definiteness in the following, we refer to the input model as the
fine model and the output model as the coarse model.
Note on net-to-gross
The Upscalers assume that the properties are gross. It is assumed that any net-to-gross
corrections have been made to the properties prior to upscaling. This can be done in the
Property Editor.
Note FloGrid does not use finescale net-to-gross information when upscaling. If you have
net-to-gross data, this needs to be used in the Property Model BUG Property Editor
(see "Geological Property model" on page 215) to create appropriate fine scale gross
properties from finescale net property and net-to-gross data prior to upscaling.
Simulation net-to-gross data can be upscaled independently and used to create
simulation net properties using the Simulation Property Editor panel. If this is done
you need to export net properties and net-to-gross. Otherwise, there is no need to
output net-to-gross as the upscaled properties are gross properties with an effective
net-to-gross of 1.

Note on terminology
For clarity we refer to fine cells on the fine (or input) model, and to grid blocks on the coarse
(or output) model. To enable the various calculations we need to subdivide the grid blocks into
smaller parts - we refer to these as microcells. Microcells are not generally the same as fine
cells, but are approximately the same size as nearby fine cells.
Applicability
Upscaling usually involves a reduction in the number of degrees of freedom in a model. Like
any summary this involves a loss of information or detail and so the design of the underlying
fine model, the design of the coarse grid and the choice of upscaling methods used to coarsen
the model, must be made with a view to the purpose of the modeling activity. Unfortunately
there are no general guidelines as to the best way to proceed. However, it is recommended that
one explores the input data, and compares results from different upscaling methods.
Sometimes one can perform local studies where the predictions of the coarse grid with upscaled
properties can be compared against the results from a coarse grid with a much finer resolution
(ideally even finer than that of the fine model). Such studies are of particular value.
Basic structure of an upscaler

Except for geometric methods, upscaling involves the following steps:
1 You select a set of coarse grid blocks for property assignment by upscaling.
2 FloGrid builds a micro grid inside the grid block.
Note that the micro grid is not usually the same as part of the fine model.
3 FloGrid determines the properties to be associated with each microcell.
Note this involves processing designed to avoid large sampling errors.
4 You choose an averaging method and FloGrid then averages the micro grid properties, to
calculate a corresponding coarse grid property for the coarse model block. The averaging
may involve a single phase flow simulation, using a linear solver.
Upscaled values only depend upon the fine model properties associated with a single grid block,
and are not influenced by the properties associated with other grid blocks.
Constructing the micro grid

Each grid block is assumed defined by its eight corner points. An Nx by Ny by Nz micro grid
is constructed inside the block using an interpolation formula. See "Building the micro grid in
a grid block" on page 485 for further details of the micro grid construction. The aim of this step
is to determine a structured grid (for speed of upscaling) that approximates a possibly
complicated fine model structure.
Sampling the properties

The coarse grid block construction method determines which block unit grid on the fine model
is related to the coarse grid. We first observe that each block unit grid has two coordinate
systems. The first is the usual x ,y ,z system where the coordinates are actual values in a reference
Cartesian frame. The second are the logical coordinates which can be used to determine the cell
index by taking the integer part of the logical coordinates. By subtracting the cell index from
the logical coordinates we determine the fraction of the block unit grid fine cell that is traversed
by a point to be placed in the fine model.

To sample the properties on this block unit grid we go through the following steps (more detail
follows this summary):
1 Determine the logical coordinates of each corner of the coarse block.
2 Determine the Nx , Ny , Nz of the micro grid to be constructed.
3 Interpolate the logical coordinates of the corners onto the center of each of the microcells
inside the coarse grid block.
4 Determine the integer part of the logical value at the center of each microcell.
5 Look up the properties at the calculated integer values.
Figure 16.12 Grid block boundaries do not follow the detailed fine grid
Figure 16.13 Logical coordinate interpolation property assignment honors layers

This procedure has two advantages. One is speed; we only need to do a search for the coarse
grid block corners. The microcell properties are fast array lookups. The second advantage is
accuracy; layering patterns are often honored, even when the fine model layers of the block unit
grid are outside the conventional boundary of the coarse grid block. If this seems paradoxical
think of the procedure as a definition of the fine model grid cells that are associated with a
particular coarse grid block. Note that although the pattern of the fine model properties is
honored we may not honor the geometry. This is inevitable as we cannot exactly honor a general
grid with a structured grid. See Figure 16.12 for an illustration of the property assignment
method using logical coordinate interpolation.
We now provide further information about stages 1-3 of sampling the properties.
Determining the logical coordinates of the block corners

Given a particular coarse grid block, each corner of the coarse block is tested against the block
unit grid to determine the fine grid cell that is occupied by the corner. Denote this fine cell by
( i, j, k ) . Each fine grid cell can be mapped onto the reference unit cube, of the same orientation.
The reference cube has a local coordinate system, with points labelled by ( a, b, c ) where a, b and
c take on the values 0 or 1 at the corners. Assuming that the reference cube is mapped onto the
fine grid cell using a trilinear mapping (see"Building the micro grid in a grid block" on
page 485) we determine the value of ( a, b, c ) that is at the same point as the corner on the coarse
grid block. We then add this to the ( i, j, k ) value to provide the value ( ξ, η, ζ ) , where ξ = i + a ,
η = j + b and ζ = k + c .
Examples
1 If the coarse grid block is at the center of fine grid cell (2,4,3) the ( ξ, η, ζ ) value would be
(2.5, 4.5, 3.5).
2 If the corner happens to be areally in the center of fine grid cell (2,1,3) and three-quarters
of the way into the fine cell in the k-direction the ( α, β, γ ) the values are (2.5, 1.5, 3.75).
Determining the dimensions of the micro grid

With reference to Figure 16.17, to determine Nx , Ny and Nz we set:
Nx = 1 + max (|ξ 2 – ξ 1 |,|ξ 4 – ξ 3 |, |ξ 6 – ξ 5 |, |ξ 8 – ξ 7 |)
Ny = 1 + max (|η3 – η 1 |,|η 4 – η 2 |, |η7 – η5 |, |η 8 – η 6 |)
Nz = 1 + max (|ζ1 – ζ 5 |,|ζ2 – ζ 6 |, |ζ 3 – ζ 7 |, |ζ 4 – ζ 8 |) [EQ 16.1]
Note that these values can be modified using options available in the Configuration file. Grid
blocks are classified as non-truncated if the zeta values of all points on the top of the grid block
are identical to a single zeta value and the zeta values on the bottom of the grid block are also
identical to a single value, otherwise the block is ’truncated’. Through the configuration option,
one can specify that the Nx, Ny, Nz values are to be multiplied by specified numbers or set equal
to the specified numbers. These operations can be applied separately to the truncated or non-
truncated cells. Thus it is possible to increase the sampling density in truncated blocks so that
the connectivity is better captured. Since the sampling is performed in the logical coordinates
of the fine cells the default settings described in the previous equation are usually adequate. By
choosing the values in the configuration file to be absolute, and setting their values to unity, one
may specify that FloGrid samples at a single point that is at the grid block center. See Appendix
B for further details.

Interpolating the corner point logical values
ξ ( α, β, γ ) = { [ ξ 1 ( 1 – α ) + ξ 2 α ] ( 1 – β ) + [ ξ 3 ( 1 – β ) + ξ 4 α ]β } ( 1 – γ )+
{ [ ξ 5 ( 1 – α ) + ξ 6 α ] ( 1 – β ) + [ ξ 7 ( 1 – α ) + ξ 8 α ]β }γ
η ( α, β, γ ) = { [ η 1 ( 1 – α ) + η2 α ] ( 1 – β ) + [ η 3 ( 1 – β ) + η 4 α ]β } ( 1 – γ )+
{ [ η 5 ( 1 – α ) + η6 α ] ( 1 – β ) + [ η 7 ( 1 – α ) + η 8 α ]β }γ
ζ ( α, β, γ ) = { [ ζ 1 ( 1 – α ) + ζ 2 α ] ( 1 – β ) + [ ζ 3 ( 1 – β ) + ζ 4 α ]β } ( 1 – γ )+
{ [ ζ 5 ( 1 – α ) + ζ 6 α ] ( 1 – β ) + [ ζ 7 ( 1 – α ) + ζ 8 α ]β }γ [EQ 16.2]
where ( α, β, γ ) are the logical coordinates in the grid block. ( α, β, γ ) each range from 0 to 1.
Geometric upscalers
Linear size
dx , dy , dz , tops
The dx, dy, dz Upscaler provides a summary of the linear size of a grid block.
The value of dx is calculated by finding the mid-points of the opposing i -faces of a grid block
and computing the length of the projection of this onto a constant z datum plane. Similarly, to
calculate dy , we find the mid-points of the opposing j -faces of the grid block, and find the
length of the projection. In contrast we compute the value of dz by finding the z -coordinate of
the mid-point of the top and bottom faces of the block - in the k -direction - and taking the
absolute value of the difference of these two values.
This upscaler also calculates tops values. The value for a cell is 0.25 times the sum of the z
values of the four top corner nodes of the cell.
Simulation grid block volumes

The exact, geometric, volume of the block is calculated assuming the block to be defined by the
eight corners, and assuming bilinear surfaces. This uses the approach of Dukowicz, [Ref. 9] and
is consistent with the ECLIPSE method.
Test for inside-out cells

To measure the quality of the simulation grid block geometry, FloGrid uses a temporary fine
grid of microcells. (These are not the same as the microcells used for sampling.)
Assuming that the temporary microgrid cells are defined by a trilinear mapping, FloGrid
calculates the Jacobian at the eight corners and at the center points of the microcells. You are
able to specify the resolution of this micro grid by an integer, M say, which is then used to
construct an M by M by M grid inside each simulation grid block. The total number of times
that the Jacobian is negative is then reported. When the grid is good, the result is zero, or 8 + M 3 .
In most cases, the values are all, or almost all zeros. Only when an inverted coordinate system
has been used at the start, will the larger number be the result. A grid is not good when the result
is different in different grid blocks. There is no known rigorous test for inside-out hexahedra
with bilinear surfaces. See Knupp, [Ref. 26], for a discussion. Larger values of M make the test
increasingly rigorous.

Even if none of the cells are inside-out, many of them can be very distorted. This is to be
expected, depending on the input data. The converse may happen, when a cell is flagged as
inside-out but does not appear to be so. In these cases, however, the Jacobian will still have
changed sign, somewhere inside the grid block. If the total grid block volume is of the correct
sign then this may not affect the ability of the simulator to solve the flow equations, however,
we recommend that you investigate the causes of any inside-out cells. Inside-out cells occur
because there is too much distortion in some of the input data, or one or more control lines are
incorrectly classified as i -lines when they should be j -lines, and vice-versa.
Departure from orthogonality

The angles, in degrees, are calculated at the eight corners on the top and the base of each grid
block. In other words, we do not consider any of the angles on the sides of the grid blocks. The
absolute difference from 90 degrees is then calculated, and the maximum over the eight corners
is reported. This gives a measure of departure from orthogonality. A value of zero everywhere
corresponds to a perfectly orthogonal projection of the grid onto a flat datum plane.
Upscaling non-dimensional real properties

Properties, whose units are not that of permeability, are assumed to be arrays of dimensionless
real numbers. The coarse scale average in each coarse grid block is defined to be a weighted
average over the microcells. The weights can be chosen as either unity or the microcell volumes.
In the following formulae, P b and v b are the property and volume respectively in the b -th
microcell. P B is the upscaled value in the coarse block. The total number of microcells in the
simulation block is denoted by N, equal to the product, NxNyNz .
Arithmetic averaging with volume weighting
∑ vb Pb
b
PB = ------------------
- [EQ 16.3]
∑ vb
b
Arithmetic averaging without volume weighting
∑ Pb
b -
PB = ------------ [EQ 16.4]
N
Geometric averaging with volume weighting
∑ vblnPb
b
lnP B = -----------------------
- [EQ 16.5]
∑ vb
b

Geometric averaging without volume weighting
∑ lnPb
b
lnP B = -----------------
- [EQ 16.6]
N
Harmonic averaging with volume weighting

1
∑ vb -----
Pb
-
1- = ------------------
----- b - [EQ 16.7]
PB
∑ vb
b
Harmonic averaging without volume weighting

1
∑ P-----b-
1- = ------------
----- b - [EQ 16.8]
PB N
Power averaging with volume weighting

ω
ω
∑ vb Pb
b
PB = -------------------
- [EQ 16.9]
∑ vb
b
Power averaging without volume weighting

ω
∑ Pb
ω b
PB = -------------
- [EQ 16.10]
N
Note When the absolute value of ω is very small the power averaging method gives results
similar to that of geometric averaging. As ω tends closer to zero the result from power
averaging, as implemented using the above formula, tends to unity. If the geometric
average is required, one should use the explicit geometric averaging method. (In the
limit that ω tends to zero, in theory power averaging is exactly the same as geometric
averaging. As a result of essential numerical approximations in the compiler
implementations of the power function this limit is not obtained. Hence, the inclusion
of a specific geometric method.)
Caution FloGrid ignores any negative or zero property data when doing geometric,
harmonic or power averaging.

Upscaling porosity
Porosity is averaged using the microcell volumes as weights. Thus:
∑ vb ϕb
b
ϕB = ------------------
- [EQ 16.11]
∑ vb
b
Upscaling absolute permeability

The meaning of Kx, Ky, Kz on the fine and coarse scale
The convention adopted by the Structured Gridder Upscaler regarding the meaning of the
directional permeabilities, Kx, Ky and Kz is described in this subsection. Each structured
simulation grid has four principal corners. That corner closest to the x-y origin of the reference
fine grid is taken as the I-J origin of the coarse (simulation) grid. The pair of opposing sides of
the areal coarse grid that are most closely aligned with the x-axis of the reference fine model are
taken as the direction of the logical I-axis of the coarse model. The pair of opposing sides of the
areal coarse grid that are most closely aligned with the y-axis of the reference fine model are
taken as the direction of the logical J-axis of the coarse model. Kx on the coarse model is in the
I-direction, the direction of increasing I-index. Kx on the coarse model corresponds to Kx on the
fine model. Ky on the coarse model is in the J-direction, the direction of increasing J-index. Ky
on the coarse model corresponds to Ky on the fine model. Kz on the coarse model corresponds
to Kz on the fine model. The z-direction on the coarse model is broadly in the direction of z on
the fine model, remembering that we may have sloping coordinate lines. No tensor rotations are
performed.
In other words the fine scale permeabilities are assumed to be in the coordinate system defined
by the simulation grid blocks. When there is no anisotropy in the x and y-directions no particular
attention need be paid to the orientation of the simulation grid. If anisotropy is present, then for
consistent results, it is important that the coarse (simulation) grid be aligned with the directions
of the fine grid areal permeability anisotropy. This is compatible with traditional practice as
incorporated in the GRID application and in the use of the PERMX, PERMY and PERMZ
keywords in ECLIPSE.
Overview of permeability upscaling

Three classes of Single Phase Upscaler are provided. The simple averaging methods are
included for completeness, and have no basis in physics. The composite 1-D solutions are based
on physical arguments, are often of sufficient accuracy and are robust and fast. The flow based
methods are of greatest accuracy (if the length scales are well-separated) but can be
considerable slower than the composite methods.
If the connectivity pattern of the heterogeneity is aligned with increasing i, j, or k then the
arithmetic-harmonic and harmonic-arithmetic methods provide reasonable approximations for
the upscaled permeability. When the pattern of heterogeneity is random, with high or low
permeability paths meandering through the grid blocks, then the flow based methods are much
more accurate than the algebraic methods.

The arithmetic-harmonic method provides upper bounds, and the harmonic-arithmetic lower
bounds. If the kV/kH ratio is very small (that is the permeability in the z-direction is much
smaller than the permeabilities in the x and y-directions) then it is advisable to use results from
harmonic-arithmetic upscaling in the x and y-directions, and to use the results from arithmetic-
harmonic upscaling for the z-direction. This can be done when sending the final results to the
simulator. This particular way of working is important when performing two-phase upscaling
where directional effects in the mobility can lead to very small kV/kH values on the mobility.
We only present the formulae for upscaling the I-direction permeability. The other directions
have the same form. "Single phase flow equations in curvilinear coordinates" on page 486 states
the single phase flow equations in a general trilinear coordinate system. Study of these equations
may help readers who wish to derive the harmonic-arithmetic and arithmetic-harmonic
methods. The methods are derived from the solution of the discrete form of the flow equations.
Approximations are required, but these lead to analytical upscaling methods. The discretization
proceeds by transforming the equations and then discretizing in the normal way.
Note that simulators do not transform the equations before the discretization. The prior
transformation simplifies the equations and leads to faster methods. The transformation is not
possible when there are non-neighbor connections. The micro grids that we use never have
internal non-neighbor connections.
The following formulae are implemented in FloGrid, where KI is the upscaled absolute
permeability in the I-direction, V ijk is an estimate of the volume of the cell, dI ijk an estimate of
the length of the microcell in the I-direction and kIijk is the absolute permeability in the
microcell in the I-direction, for microcell (i,j,k).
Simple averaging
In a simple averaging method we do not justify the averaging formula by reference to an
approximate flow solution. In the case of arithmetic and harmonic averaging we weight the
permeabilities with geometric factors so that in a truly 1-D case, where the method is similar to
a flow based method, we arrive at the same answer as the no-side-flow boundary condition
method. This amounts to taking into consideration the cross-sectional area and length of each
microcell. This is equivalent to using the volume and squared length.
Arithmetic averaging
V ijk V ijk kI ijk
KI ∑ ------------
dI
- = ∑ --------------------
2
dI
2
[EQ 16.12]
ijk ijk
where the summation is over all microcells. Arithmetic averaging is equivalent to assuming all
the microcells are in parallel.
Harmonic averaging
2 2
1- dI ijk dI ijk
-----
KI ∑ ----------
V ijk
= ∑ -------------------
Vijk kIijk
- [EQ 16.13]
where the summation is over all microcells. Harmonic averaging is equivalent to assuming all
the microcells are in series.
Geometric averaging
N ln KI = ∑ ln kIijk [EQ 16.14]

where the summation is over all microcells.
Note that there is no volume weighting. This is for consistency with the limit of a zero valued
power in the power averaging method for upscaling permeability.
Power averaging
⎛ V ijk kI ijk⎞ ω
∑
⎜ -------------------
⎝ dI 2ijk ⎠
-⎟
ω
KI = ------------------------------------ [EQ 16.15]
⎛ V ijk ⎞ ω
∑
⎜ ----------
⎝ dI 2ijk⎠
⎟
where the summation is over all microcells. The above equation is derived by applying a non-
weighted power averaging method to the permeabilities after transformation to logical
coordinates.
Note When the absolute value of ω is very small the power averaging method gives results
similar to that of geometric averaging. As ω tends closer to zero the result from power
averaging, as implemented using the above formula, tends to unity. If the geometric
average is required, one should use the explicit geometric averaging method. (In the
limit that ω tends to zero, in theory power averaging is exactly the same as geometric
averaging. As a result of essential numerical approximations in the compiler
implementations of the power function this limit is not obtained. Hence, the inclusion
of a specific geometric method.)
Composite 1-D solutions

In these methods we carve the micro grid into an array of tubes and ignore cross-flow between
the tubes, or we carve the micro grid into a linear array of slabs and ignore cross-flow within
each slab. In the following we assume that the viscosity is unity. This simplifies the equations
with no loss of generality and without affecting the upscaled values of permeability.
Harmonic-arithmetic averaging
In the first case we calculate the flux, uIjk, through each tube (j,k) separately. By integrating the
flow equations along the tube, assuming the geometric factors and permeability are piece wise
constant, we obtain
2
dI ijk
uIjk ∑ - = Δp
-------------------
Vijk kIijk
[EQ 16.16]
The total flux through the grid block is then obtained by summing uIjk , the flux through micro
tube ( j, k ) over j and k.
We then calculate the upscaled permeability from
1 1
∑ --------------------------
2
dI ijk
- = KI ∑ ------------------
dI ijk
2
[EQ 16.17]
∑ VijkkIijk ∑ Vijk
j ,k -------------------
- j ,k ----------
i i

Arithmetic-harmonic averaging
In this case we assume a pressure drop of δpi across the i-th slab. By incompressibility the flux
through all slabs is the same. This flux is given by the formula
V ijk
u = δp i ∑ ----------
dI
2
kI ijk [EQ 16.18]
j ,k ijk
This formula for the flux through each microcell is deduced from the discrete version of the flow
equations.
Now summing the pressure drops over the slabs, we obtain:
1
∑ δpi = p0 – pL = u ∑ --------------------------
V ijk kIijk
- [EQ 16.19]
i i
∑ dI2 -------------------
-
j ,k ijk
where p 0 is the inlet pressure and p L the outlet pressure.

Equating the pressure drop to the similar expression with constant KI , the upscaled
permeability, we obtain the final expression
1
∑ -----------------
V ijk
-
i
∑ dI2 ----------
j ,k ijk -
KI = ---------------------------------- [EQ 16.20]
1
∑--------------------------
V ijk kI ijk
-
i
∑ -------------------
2
-
j ,k dI ijk
Full 3-D solutions

The full, flow based, 3-D numerical solutions, are the most computationally intensive single-
phase upscaling options. They are implemented with a choice of no-flow boundary conditions
on the block sides, linear boundary conditions and the adjoint method. There is also an option
to compute half-block upscaled permeabilities for use as a diagnostic. The half-block method
uses linear boundary conditions. The linear boundary condition and half-block methods have an
option for you to provide face multipliers.
The no-side-flow boundary condition method

No-side-flow boundary conditions impose a constant pressure on one face of the block, and a
different constant pressure on the opposing face. The other four sides of the block are subject to
no-flow boundary conditions. There are three different ways of applying these boundary
conditions, providing three independent numerical experiments for the components of a
diagonal permeability tensor.
We compute the total flux through the block in the direction of the pressure drop, joining the
mid-points of the block faces in the direction of flow. The effective permeability is then
estimated by solving the same problem with constant permeabilities chosen to give the same
flux. For the no-side-flow boundary conditions, this constant permeability problem is solved
using harmonic-arithmetic averaging. An error is introduced by this, unless the grid blocks are
rectangular. The use of the linear boundary conditions removes the need for this approximation.

The no-side-flow boundary condition method uses the fine model geometry for the microgrid
when upgridding has been done and the fine model has a rectangular grid with regular dx and
dy spacing ( dx is constant for a given y, and dy is constant for a given x). In other cases the
microgrid is obtained by interpolating the block corners. In many cases the sampling uses the
exact fine grid as explained earlier.
The no-side-flow boundary condition method transforms the problem into an equivalent
problem on a cube. The Jacobians and length-scale factors are evaluated at the cell centers. The
transmissibilities, on irregular grids, are slightly different between this approach and the
NEWTRAN method used in the ECLIPSE simulator.
The results are different from the similar calculation performed with a zero face multiplier but
using the linear boundary condition method because (i) the geometry of the fine grid may be
different (ii) a different method is used to back-out the upscaled values and (iii) the
transmissibilities between the fine grid cells are calculated differently.
The linear boundary condition method

Linear boundary conditions are imposed by choosing a direction vector along the normal to a
surface that divides the grid block into two parts. This dividing surface is the arithmetic average
of the two opposing faces modeled as bilinear patches. This can be done in three ways, leading
to three numerical experiments; one for each component of a diagonal permeability tensor. The
pressure at points on the external faces is given by the scalar product of the direction vector with
the coordinates at those points.
The total flux through the system is calculated in the direction joining the mid-points of the two
grid block faces in the direction of flow. This is also the direction of the pressure drop. The
diagonal upscaled permeability tensor is then defined to be that constant diagonal tensor that
would give rise to the same fluxes if we use identical boundary conditions.
In all cases, even if upgridding has been performed, the linear boundary condition method uses
the microgrid geometry; not the fine model geometry. However, in simpler cases the geometries
can coincide.
The transmissibilities are calculated in the same way as in the ECLIPSE simulator, using the
NEWTRAN method.
There is an option to apply a multiplier (between 0 and 1) to the side faces in each of the three
numerical experiments. When the multiplier is zero we have a version of the no-side-flow
boundary condition method. Thus in an I -direction flow experiment, we apply the J and K face
multipliers to the side-faces.
In the default multiplier option the multipliers on all six faces are calculated by the code. The
normal at the center of each face is found, and the multiplier for that face is the magnitude of
the dot product of the normal with the direction of the imposed pressure gradient.
The multiplier can be used to investigate the presence of permeability barriers in a grid block.
If the barriers are extensive, intersecting several blocks, then a low value of the multiplier is
suggested. If the barriers only pass through a block and part of its neighbor then a multiplier
value near one is appropriate.
The linear boundary condition method has been discussed by Madsen, [Ref. 30],and King et al,
[Ref. 24]. King et al introduced the concept of the face multipliers.

The adjoint method
Each flow-based upscaler needs (i) boundary conditions (ii) a flow solver (iii) a diagnostic
function. This last requirement reduces to the provision of a vector, c , and a fixed number, a ,
so that a measure, q , of the total flux is given by q = p ⋅ c + a where p is the vector of pressures
obtained from the numerical solution. Normally one would use a different vector, c , and
number, a , for each flow direction. The vector and the number are both functions of the chosen
boundary conditions and the permeability in the microcells adjacent to the grid block surface.
In the adjoint method we choose the diagnostic function by first finding the total flux through
each face of the grid block in the direction of increasing x, increasing y and increasing z and
then taking the sum of these fluxes. (If we take the sum of the fluxes in the direction of the
outward pointing normal then, of course, the sum would be zero.) Thus we can use the same
vector c in the diagnostic functions. The constant, a , is different in each experiment. In the
adjoint method we use linear boundary conditions, and the constant a , depends on the direction
of the pressure gradient in each numerical experiment.
Thus we can use the adjoint method of solving a sequence of linear equation problems, where
only the right hand sides are different, and we only wish to evaluate a fixed linear diagnostic
function. We therefore only need to solve the linear system once and we can find the total fluxes
by evaluating three dot products. In the adjoint method we use the same matrix as in the normal
approach. We can do this because the matrix is symmetric. The right side in the adjoint method
is the vector c and we solve for a vector v . The flux is then given by q = v ⋅ b + a where b is
the usual right side. We only need solve for v once, and then we can compute the three values
of q using the three right hand sides.
The adjoint method has the potential to be nearly three times as fast as the standard linear
boundary method. If we use face multipliers we destroy the feature of constancy in c . For this
reason the Face Multiplier option is not available on the adjoint method.
The adjoint method does not give the same upscaled permeabilities as the linear boundary
condition method with unit multipliers. However, the results are almost the same.
The half-grid block method

The Upscalers described so far have used all of the properties within a block to calculate the
effective permeability. This accords with the usual way that upscaling is performed. For
validation purposes it is useful to investigate the effect of upscaling on a different sized region.
If the results are markedly different then the fine model needs further study.
To calculate upscaled permeability on a different sized region, we divide the grid blocks into
two pieces (using the average bilinear surface between two opposing faces.) This can be done
in three different ways. For each way we apply the linear boundary condition method in each
half-grid block. This results in six values of permeability. Each half-block permeability
depending only on the permeabilities in its half block. For further discussion on the use of half-
block permeabilities see King et al, [Ref. 24].
In the half-block method there is an option to apply transmissibility multipliers to each side face.

Note All the flow based Upscalers use a conjugate gradient method with an incomplete
Cholesky preconditioner. The preconditioner has the same sparsity pattern as the
original matrix and preserves the column sum. Symmetry of the matrix implies
preservation of the row sum. In the CONFIG file you may set the maximum number of
iterations and the magnitude of the mean square residual below which the solver
terminates. The default settings are very tight. Some data sets cause ill-conditioning in
the flow matrix, with layers of near zero permeability; hence the conservative defaults.
It can be worth experimenting with the defaults. In some cases the pre-conditioner is
sufficient to give upscaled permeabilities within a few percent of the converged values.
The action of the preconditioner alone is obtained when the default maximum number
of iterations is set to zero.
Upscaling SATNUM
The saturation table indices, known as SATNUM from the ECLIPSE keyword, are obtained by
taking a volume weighted majority vote. This is called the histogram method when it appears in
the single phase upscaler, and the majority vote method in the two-phase upscaler. The SATNUM
assigned to the grid block is the SATNUM that occupies the largest volume of microcells. In the
event of a tie, the smallest SATNUM in the tie is assigned to the grid block.
Upscaling capillary pressure

In practice FloGrid only upscales capillary pressure data at the same time as corresponding
relative permeability data. In general different sets of saturation points are used for capillary and
relative permeability so that their values must be merged after upscaling.
A capillary equilibrium method is used to upscale the capillary pressure functions associated
with the microgrid cells. This method is used to upscale the capillary pressures in the capillary
equilibrium and constant fractional flow two-phase upscalers. The capillary equilibrium and
constant fractional flow two-phase upscalers differ in their treatment of the relative
permeability. The constant saturation two-phase upscaler uses a microcell pore volume
weighted average of the capillary pressure curves. The Majority Vote Two-phase Upscaler
uses a microcell volume weighted vote. In the majority vote method the pore volume weighted
endpoints are calculated for subsequent export for a simulation using end point scaling.
Capillary pressure upscaling is based on the assumption of equilibrium of an incompressible
two-phase system with negligible gravity effects (thin layer approximation).
To apply this assumption the code selects a monotonic sequence of capillary pressures. Then for
each of these capillary pressures the saturation in the microcells is determined by looking for
the saturation corresponding to that capillary pressure defined by the SATNUM in the microcell.
The upscaled capillary pressure, Pc ( SA ) , which is a function of the upscaled phase- A saturation,
is thus constructed with the prescribed value of the capillary pressure:
Pc ( S A ) = P AB [EQ 16.21]
and the coarse block saturation given by:
∑ S Ab V b ϕ b
S A = ----------------------------- [EQ 16.22]
∑ Vb ϕb

where S Ab is the phase- A saturation in microcell- b and P cb ( S ab ) = PAB .
This is illustrated in Figure 16.14.

Figure 16.14 Determining the saturation given a capillary pressure value
Pc
The pore volume average of the saturation is used to define the average saturation for the grid
block.
To compute the capillary pressures at which to determine the average saturations we first
determine the maximum of the minimum capillary pressure over the fine cells. Then we find the
minimum of the maximum values. The average value of the saturations is then found for the
minimum and maximum capillary pressures. These average saturations define the range of
possible saturations for which an upscaled capillary pressure is required.
You will have set the desired number of sample points. The number of sample points is a target
value, and the resulting number of sample points may be smaller or larger. You also have the
opportunity to set two tolerance values called Min sat separation and Min sat separation on
merge on the user interface. In the command files the Min sat separation control is called
Alpha1 and the Min sat separation on merge control is called Alpha2. The merge control
comes into operation when capillary curves are merged with corresponding upscaled relative
permeability curves.
The algorithm for determining the capillary pressures at which to upscale is as follows:
1 Divide the saturation axis into the requested number of intervals. These intervals are
equally spaced.
2 Determine the pore volume averaged capillary pressure at the equally spaced saturation
values.
3 Determine the true pore volume averaged saturation corresponding to the capillary
pressure. This is done by looking up the saturation on the capillary pressure curve in each
microcell. This determines the initial capillary pressure curve.
4 Equidistribute, in arc length, the required number of points along the initial capillary
pressure curve. Include the first and last points, and then any other points in the final
capillary pressure curve if they are less than Alpha1 (Min sat separation control) from
any points already included.

To perform the above steps the Capillary Pressure Upscaler needs to calculate the saturations
in the microcells, for a given value of capillary pressure, and the value of capillary pressure
given a saturation. To speed this process the microcell capillary curves are grouped, so that if J-
functions are not used, and there are only two curves, for example, there will only be two values
to look up. However, if J-functions are in operation then the saturation could be different in each
microcell. Thus the capillary upscaling with J-functions can be much slower than without J-
functions.
Note Data regarding the surface tension and contact angle are passed to the capillary
pressure upscaler (and the capillary equilibrium upscaler) via the SATNUM property
on the fine grid. In other words the surface tensions and contact angles are obtained by
looking up the values of surface tension and contact angle in the J-function record
corresponding to the SATNUM on the fine cells. (Thus any data relating to surface
tension and contact angle that are explicitly present as properties on the fine grid are
not used in the upscalers.)

Upscaling relative permeability
Introduction
This section contains technical background information on the following:
• "Phase saturations" on page 479.
• "Constant saturation method" on page 481.
• "Capillary equilibrium method" on page 481.
• "Constant fractional flow method" on page 481.
Phase saturations
In the following we assume incompressible, steady state, two phase flow.
If we knew the phase saturations we could upscale mobility (the product of absolute
permeability with relative permeability, divided by viscosity) using a single phase upscaler. This
leads to an upscaled mobility, which, after normalization using the ratio of the upscaled absolute
permeability to the viscosity, gives an upscaled relative permeability.
The mobilities of phases A and B are given by the expressions:
I
I k k rA ( S A )
λ A = ----------------------
- [EQ 16.23]
μA
I
I k k rB ( S A )
λ B = ----------------------
- [EQ 16.24]
μB
where λ A and λ B are the phase- A and phase- B mobilities, kI the absolute permeability in the
I -direction, k rA and k rB are the relative permeabilities of phase- A and phase- B , μ A and μ B are
the phase viscosities. The relative permeabilities are assumed to be functions of the phase- A
saturation, S A . There is an option to use, as input, directional relative permeabilities; this leads
to a superscript, I , on krA and k rB in the two previous equations.
The relative permeabilities are functions of the phase- A saturation and have the shapes shown
in the Figure 16.15:

Figure 16.15 Relative permeability curves
The Darcy-Muskat law for two-phase flow, in the absence of gravity effects, introduces the
equations:
u A = – λ A ∇p A [EQ 16.25]
u B = – λ B ∇P B [EQ 16.26]
pB – p A = p c ( sA ) [EQ 16.27]
for the phase fluxes, u A and u B where p c ( s A ) is the capillary pressure, a function of the phase-
A saturation.
We assume steady-state incompressible flow so we have the conservation equations:

∇.u A = 0 [EQ 16.28]
∇.u B = 0 [EQ 16.29]
As boundary conditions we assume a hexahedral domain with either no-side-flow or linear

boundary conditions. In the no-side-flow case we specify a phase- A pressure at the inlet, and a
zero value at the outlet. The phase- B pressure is set to the phase- A pressure plus a constant. On
the remaining sides we specify zero flux. In the linear boundary condition case we specify the
phase- A pressure to be a given linear function on the boundary of the domain. The phase- B
pressure, on the boundary, is set equal to the phase- A pressure plus a constant.
If we suppose we know the phase saturation S A , then we can dispense with the capillary
function, and solve two equations for p A and pB , as if the phases A and B were independent.
We then can pass the mobilities to one of the single phase upscalers, as if they were
permeabilities. This delivers the upscaled mobilities, Λ IA and Λ IB . We then obtain the upscaled
relative permeabilities in the I-direction, K IrA and K IrB from the definitions:
I
I Λ rA μ A
K rA = ---------------
- [EQ 16.30]
I
K
I
I Λ rB μ B
K rB = ---------------
- [EQ 16.31]
I
K
The result of upscaling is either the directional upscaled relative permeabilities that we have just
defined or the scalar relative permeability as obtained from an arithmetic average of the three
directional relative permeabilities.

Different methods of upscaling relative permeability are then obtained depending upon how we
approximate the phase saturations.
We consider three methods for determining such phase saturations: The methods of capillary
equilibrium and constant fractional flow upscaling were introduced and their limits of validity
discussed by Smith. A relevant discussion may also be found in Dale et al, [Ref. 6]. The constant
saturation method is very similar in character to the capillary equilibrium and fractional flow
methods.
A fourth method is available, the majority vote method, this is the same as the SATNUM
histogram method described earlier and does not require approximate phase saturations.
Constant saturation method

A set of saturation values between the minimum and the maximum are defined. These are then
assigned to each of the microcells. If the saturation so defined falls outside the interval defined
by the minimum and maximum saturation in the microcell the local fine grid block saturation is
clipped to the appropriate bound.
The method then proceeds as described above.
Capillary equilibrium method

Capillary equilibrium upscaling is based on the theorem:
If the situation is one of two-phase, incompressible, steady-state flow, in which gravity
effects are negligible (thin layer case) and the capillary pressure is constant over the surface
of a grid block then the capillary pressure is equal to that constant throughout the grid block
in the limit of zero flow rate.
The method works by first upscaling the capillary pressure as described earlier. The upscaler
then divides the average saturation range into equal intervals according to the requested number.
For each value of the required average saturation the upscaled capillary pressure curve is
scanned to find a pair of capillary pressure values whose true pore volume weighted average
saturations bound the required average saturation. The microcell saturations are assigned by
linear interpolation of the microcell saturations corresponding to the bounding capillary
pressures. The relative permeabilities are then upscaled using these microcell saturations using
the method described above.
Constant fractional flow method

In this method we choose a sequence of fractional flow values from zero to one. We then assume
that the fractional flow is the same in each of the microgrid blocks. The fractional flow curve in
each of the microcells is then used to determine the saturation value which would give that value
of fractional flow.
The algorithm for choosing the fractional flow values is as follows:
1 Divide the saturation axis into the requested number of intervals. These intervals are of
equal length. Call the saturation points defining the intervals the ’target saturations’.
2 Determine the pore volume weighted fractional flow at each target saturation value.

3 Determine the true pore volume weighted saturation corresponding to each of the
previously calculated fractional flow values. This determines the initial fractional flow
curve.
4 Equidistribute, in arc length, the requisite number of points along the initial fractional flow
curve. Call this the secondary fractional flow curve.
5 Construct the final fractional flow curve by starting with the first and last values of the
secondary curve. Then add the other values provided that they are more than the min. sat
separation from points already on the final curve. For each target saturation locate the
fractional flow values on the final fractional flow curve whose true pore volume weighted
average saturations provide an upper and lower bound for the target saturation. Linearly
interpolate the microcell saturations corresponding to the lower and upper bounds so that
the resulting microcell saturations have a pore volume weighted average equal to the target.
The interpolated microcell saturations are then used in the previously described method for
upscaling relative permeability.
After upscaling the relative permeabilities merge the saturation values on the upscaled capillary
pressure curve with those on the upscaled relative permeability curves. The capillary pressure
saturation values (and corresponding capillary pressure) are only included in the result if the
capillary pressure saturations are more than Min sat separation on merge from any other
points on the curve.
In the command files the Min sat separation is called Alpha1 and the Min sat separation
on merge is called Alpha2.
The fractional flow of phase- A is defined by the formula:
λA ( SA )
fA = ---------------------------------------
- [EQ 16.32]
λA ( SA ) + λB ( SB )
and is a monotonic increasing function on [0,1] with values on [0,1].

This is illustrated in Figure 16.16.
Figure 16.16 Determining the saturation given a fractional flow value
The fractional flow method can be proved exact in the limit as the flow rate goes to infinity, or
equivalently in the singular limit that the capillary pressure is zero.

Note In the Fractional Flow Upscaler the capillary pressure is upscaled using the capillary
equilibrium method. The saturation points obtained for the relative permeabilities and
the capillary pressure are generally different. The upscaled capillary pressure curve
saturation values are merged with the upscaled relative permeability saturation values,
thus leading to final upscaled curves with up to twice as many points as originally
requested. If these merged saturations are nearer than Min sat separation on merge,
(Alpha2 in the command files) then the capillary pressure point is not included in the
merged curves. Although merging increases the total number of points by up to a factor
of two, it does not markedly increase the execution time, and greatly improves the
accuracy of the final results. At the merged points the corresponding function values
are obtained by linear interpolation on the original upscaled curves. In the case that the
saturation range for the upscaled capillary pressure extends beyond that of the upscaled
relative permeabilities, the upscaled relative permeabilities are extended using linear
extrapolation to unity at the larger saturation value. At the lower values of relative
permeability extra zero values are inserted where needed.

Statistical diagnostics
These all compute coarse grid block properties using only the data on the microgrid within each
coarse grid block.
Standard deviation
This is the square root of the average square difference of each microcell value and its average.
That is, the usual biased standard deviation.
If the relative dispersion option is selected, the standard deviation is divided by the average, if
the average is non-zero. (When the average is zero the division is not performed.)
Probability outside [av - scale, av + scale]

First the average is computed. We then define an interval either side of this average. The result
is the probability that a cell chosen at random is outside this interval.
One-point probability
This is the probability that a cell chosen at random (within the coarse grid block) has a value
inside the specified interval [min., max].
Two-point probability
This is the probability that a pair of cells, chosen at random within the coarse grid block, and
with the two cell centers separated by the vector ( I -direction, J -direction, K -direction) have:
a the first value inside the interval [first min., first max]
b the second value inside the interval [second min., second max] and
c the absolute difference between the values less than the specified increment.
So, for example, if we specify the direction (1,0,0), and the intervals (0.3, 0.9), (2.1, 2.7) and
the increment 0.95, we will find the fraction of all possible pairs of cells, separated by the vector
(1,0,0), that are next to each other in the I -direction, such that the first cell has a value in (0.3,
0.9), the second cell has a value in (2.1, 2.7) and the two values have an absolute difference less
than 0.95.
If the increment is set to a very large value, then the probability is the fraction of all possible
pairs of cells, separated by the vector (1,0,0), that are next to each other in the I -direction, such
that the first cell has a value in (0.3, 0.9) and the second cell has a value in (2.1, 2.7).

Statistical diagnostics
Building the micro grid in a grid block
Having selected our grid block we divide the block into a set of Nx by Ny by Nz microcells. We
do this using trilinear interpolation from the corner values. One way of thinking about this is to
imagine that the grid block is a deformed version of a unit cube. On a unit cube we can introduce
a coordinate system ( α, β, γ ) , where each of the variables lies between 0 and 1.
We then define the deformation of the unit cube to the actual grid block by the trilinear
interpolation formula:
x ( ξ, η, ζ ) = { [ x1 ( 1 – ζ ) + x2 ζ ] ( 1 – η ) + [ x3 ( 1 – ζ ) + x4 ζ ]η } ( 1 – ζ )+
{ [ x5 ( 1 – ζ ) + x6 ζ ] ( 1 – η ) + [ x7 ( 1 – ζ ) + x8 ζ ]η }ζ [EQ 16.33]
Points 1-4 are on the top, points 4-8 on the base. These labels are as shown in Figure 16.17.
We define a microgrid of rectangular grid blocks, all of the same shape and size inside the
reference block. The transformation then deforms all these reference microcells into deformed
microcells.
Figure 16.17 Point labels on the reference cube and the grid block
Figure 16.18 Interpolating a 2x1x3 fine grid in a grid block

Building the micro grid in a grid block
Single phase flow equations in curvilinear coordinates
The derivation of the flow equations in general coordinates is most easily done using the
machinery of tensor analysis. A good summary of this is provided by Spiegel). We assume, in
the normal way, that the trilinear coordinate system is orthogonal, even when this is manifestly
not the case.
For incompressible flow the mass balance law is:
∂ i
∑ ∂ξi gu = 0 [EQ 16.34]
i
i
where ξ is the i -th curvilinear coordinate ( α, β, γ ) for i = 1, 2, 3 respectively. g is the square
root of the determinant of the metric tensor and is the volume of physical space per unit volume
of computational space at ( α, β, γ ) .
Darcy’s law reads:
i
i k ∂p
u = – ------ -------i [EQ 16.35]
g ii ∂ξ
where ki is the physical component of the permeability tensor in the i-th direction. The
orthogonality approximation occurs when we ignore the off-diagonal terms of the transformed
permeability tensor in the trilinear coordinates. gii is the i-th component of the metric tensor,
and is the squared length of physical space per unit squared length of computational space at
( α, β, γ ) in the i-th direction. In our calculations we approximate the metric tensor as a constant
in each grid block equal to the value at the block center given by ( α, β, γ ) = (0.5, 0.5, 0.5). In this
way the equations in the curvilinear system are of the same form as an equivalent system in
rectangular coordinates but with differently varying permeabilities.

Single phase flow equations in curvilinear coordinates
Upgridder
Chapter 17
Introduction
The Upgridder is used to group layers in a geological model into coarser simulation layers. The
main methods are variability based, flow based and manual upgridding.
The interfaces to the variability and flow based methods have been designed to be very similar,
even though the underlying algorithms are different. The main options are described in the
following sections of this chapter.
• Creating upgridded models, see "Upgridding Folder" on page 488.
• Setting upgridding controls, see "Options" on page 489.
• Manual upgridding, see "Edit" on page 491.
• I J K Slicing of upgridded models, see "Generating and using fluxes for Upgridding" on
page 496.
• Displaying upgridded properties, see "Upgridding Display Property" on page 491.
The technical background to the upgridding facility is described further in "Upgridder -
Technical Description" on page 493.
Use of FrontSim for generating fluxes for upgridding is described in "Generating and using
fluxes for Upgridding" on page 496.
FloGrid User Guide Upgridder 487

Introduction
Upgridding Folder
The Upgridding folder allows you to construct simulation grids by coarsening the geometry of
an existing grid or geological model. The upgridding process seeks to construct a grid that
represents the underlying property variations in the fine model.
Two types of upgridding algorithms are provided, Variability based and Flow based.
• Variability based upgridding places simulation grid cell boundaries where there are big
changes in a selected property between rows, columns or layers of the geological grid.
• Flow based upgridding places simulation grid cell boundaries such that high permeability
rows, columns or layers in the geological model are retained.
Note 3D manual upgridding is also supported. Manual upgridding can be done either in
isolation or after an algorithm has been used, to modify the grid.
The original flow-based upgridding options (available prior to FloGrid 2004A) are restricted to
input geological models that are in GEOLITH or SGM (.amd) format and that have no inactive
cells.
The Simulation Flux Output Based option, developed for the 2004A release, allows you to
apply flow based upgridding to a wider range of geological models. It requires the geological
model to contain FrontSim fluxes, which implies that the geological model must itself have been
created as a FloGrid model. You can create a fine FloGrid model from an imported RESCUE
model or imported ECLIPSE grid, run FrontSim to generate the required fluxes, and then apply
the upgridder to the fine FloGrid model (see "Generating and using fluxes for Upgridding" on
page 496).
Flow-based upgridding methods can only be applied to a single block unit of the fine model.
The Variability method, which is much faster, is available for all input fine models and is not
restricted to a single block unit grid.
Refer to "Upgridder - Technical Description" on page 493 for more details of the algorithms
behind the two methods.
Select Fine BUG

Selects the source block unit grid (BUG) to be upgridded.
If the Variability method is selected, and the source fine grid has a global grid, that is also be
selected from the list of available input fine BUGs. Global grids are present in corner point grids
created within FloGrid or imported geological models (RESCUE) containing corner point grids.
488 Upgridder FloGrid User Guide

Upgridding Folder
Coarse BUG
Select the upgridding algorithm from one of the methods shown in the following table:
Table 17.1 Upgridding methods
Abs Perm Flow Based

In this approach we solve two single phase, incompressible, flow problems on a selected block
unit grid, from left to right, and from the back to the front. We refer to these experiments as
the I and the J experiments.
PermXY, PermZ Flow Based / Tensor Perm Flow Based
These options are variations of the Abs Perm Flow Based method, that use the respective
permeability properties when calculating the fluxes.
Variability
Adjusts the simulation grid block corners so that the variance of some user selected property
is equally distributed under the constraint of a specified total number of grid blocks.
Simulation Flux Output Based
This option instructs the Upgridder to use pre-existing FrontSim fluxes in I, J experiments in
the same way that the fluxes calculated in the flow-based options are used. Fluxes for the
current time step are used.
Options
Options opens the Upgridding Control panel for the currently selected upgridding algorithm.
The panel is the same for all the flow-based or simulation flux-based upgridders, and very
similar for the variation-based upgridder. On the panel there are three areas for adding data, one
each for grouping in rows, columns and layers.
Flux based upgridder options

For the Flux-Based Upgridder options, the area for defining Layer (Z Controls) is at the top
of the panel, then come the I and J areas.
Group by layer | I Row | J Column

This check box allows the Upgridder to group layer, rows or columns. When this box is
checked the controls in the area below it are active, and upgridding is performed in that
direction.
Percentage of Maximum flux

You can set the maximum allowed flux through any coarse layer, specified as a percentage of
the maximum average flux in any of the fine grid layers.
Maximum number of fine layers to group

This option allows you to set the maximum number of contiguous fine grid layers that can be
grouped in any simulation layer.

Upgridding Folder
Maximum number of fine layers to retain
This parameter controls the number of fine layers that must be retained as individual layers after
coarsening. The layers retained are those with the most flux through them.
Variability based upgridder options

For the Variability-based Upgridder, the options panel shows the I, J and K areas in that order.
There are some additional controls that are not used for flux-based upgridding.
Group [I][J][K]
These check boxes allows the Upgridder to group layers, rows or columns. When this box is
checked the controls in the area below it are active, and upgridding will be performed in that
direction.
Percentage of Maximum Var

For the selected property, you can set the maximum variability allowed within any coarse layer,
specified as a percentage of the maximum average variability in any of the fine grid layers.
Maximum Num of Fine Layers to Group

As in the Flux- Based Upgridder, this option allows you to set the maximum number of
contiguous fine grid layers which can be grouped in any simulation layer.
Maximum Num of Fine Layers to Retain

As in the Flux- Based Upgridder, this option controls the number of fine layers that must be
retained as individual layers after coarsening. The layers retained are those with the highest
variability.
Select Property
This is a drop-down list for selecting which property should be used when grouping layers.
Guide Layers
This table only appears in the K grouping area. It displays the guide layers for the currently
selected fine BUG. Guide layers are the K indices of the fine BUG layer interfaces that are to
be retained in the upgridding process. The surface below the given layer index is retained. The
Guide Layers are defaulted to the unit boundaries. When the Coarse BUG has been created,
you can edit or delete these guide layers.
Create (Modify)
Applies the selected Upgridder with input data. This process can take many minutes to run.
This button is renamed to Modify after the Upgridder has been run once.
View
Adds the upgridded model to the 3D Viewer (see "3D Viewer" on page 107). The object
displayed shows the fine grid properties with lines denoting the coarsened geometry.
The view of the upgridded model can be controlled using the following options from the Scene
menu at the top of the main window.

Upgridding Folder
Upgridding IJK Slice
This dialog is opened using Scene | Upgridded Models | IJK Slice. It allows the visualization
control of the intermediate upgridding model. Ranges of I J K slices may be selected with this
panel.
Upgridding Display Property

This dialog is opened using Scene | Upgridded Models | Display Property. This allows you
to select the model, the property type and the property to view in the 3D Viewer.
Edit
Opens the Coarse BUG Editor panel for manual upgridding and adds the upgridded, coarse
block unit grid model to the 3D Viewer if it is not already present.
This panel provides options for interactively (manually) grouping layers of the Block Unit Grid
(BUG).
Editing direction
Selects the direction in which grouping is to be done.
Editing type
Switches modes between grouping and splitting layers. The two modes are:
Merge coarse layers (/rows/columns)

When coarse layers are merged, coarse grid layer boundaries are removed from within the group
of adjoining merged coarse layers.
Merge fine layers (/rows/columns)

When fine layers are merged, coarse grid boundaries (and hence layers) are created at the top
and bottom of the set of adjoining merged fine layers.
Selection
This area provides textual information indicating which layers are selected. There is also a
check box for requesting that the selected layers are highlighted in a single color.
Simulation grid
Convert to Sim Grid
Converts the upgridded (coarse) geological grid into a simulation grid, calculating the node
locations for each cell. This simulation grid can then be displayed on the 3D Viewer by clicking
on the Display Grid button.
Note When creating a simulation grid, the K numbering of the simulation grid is always top
down regardless of the numbering scheme in the geological model.

Upgridding Folder
Hint The direct conversion of an upgridded model to a simulation grid is only reliable if
there are no missing (inactive) cells. If direct conversion cannot be used, the
recommended workflow is to refer to the Upgridder reports in the FloGrid log file for
guidance. Then build a new model from the geological model and assign the layer
grouping in each block, using the advanced layering feature in the Structured Corner
Point Vertical Gridder.

Upgridding Folder
Upgridder - Technical Description
Variability based upgridding

This method has been developed to improve the efficiency of previously described variance
based upgridding methods, [Ref. 24] and [Ref. 27]. These methods adjust the simulation grid
block corners so that the variance of some user selected property is equally distributed under the
constraint of a specified total number of grid blocks. The technique can work well. However, in
full generality (when we group geological cells into simulation cells) it is slow - mainly because
of the sampling needed. In the special case that the simulation grid layers correspond to an exact
group of geological layers the algorithm is much faster. However, it still requires the solution
of a difficult combinatorial optimization problem and needs obscure input. The difficulty arises
from the non-additive nature of variance. If we add a high variance layer to a low variance layer
the total variance can decrease.
We therefore introduce the notion of variability or variation, which is strictly increasing.
Consider a block unit grid with N g layers and define the variation of a property, p , between a
layer and the cells above the layer by the expression:
1
a k = -----∑ p –p †
nk c ∈ k c c
[EQ 17.1]
aNg = 0
where c† is the cell above cell c and p c is the value of the property in the geological cell. The
summation is over all the active cells in the kth layer. The cells c† are not necessarily all in the
same layer since layers can pinch out.
The normalization factor n k is either the total number of cells in the kth layer (including
inactives) or the total number of active cells. This choice is set in the Configuration file using
the keyword EXTEND_PINCHED_OUT_LAYERS. The default is to include all the inactive
cells in the normalization factor. If the inactive cells are dispersed throughout the layer, then this
is appropriate. If the inactive cells are together and caused by, for example, an unconformity,
then it is perhaps better to use the normalization that ignores all inactive cells.
A similar formula to that for the a k is used to define the variation, b k , of each layer with the
cells below the layer.
To obtain a measure of the total variation in the selected block unit grid, we define the total
variation, to be the sum of the variations of the layers with the cells below, that is the sum of
the ak values. This is the same as the sum of the b k values.
We define a Ng and b0 for convenience in defining the two-way variation.
The total variation of the whole model is defined by the sum of the variations between the
layers.
The two-way variation of a layer is defined by the expression:
tk = 0.5 ( a k + b k ) [EQ 17.2]

We order the two-way variations of the geological model layers and then assign a variation
index equal to the order. Thus, if the variation index of a fine layer is equal to n, this layer is the
layer with the n’th largest two-way variation.
If the geological layers are grouped, consecutively, into simulation layers, we define the
variation in any coarse layer according to
vs = ∑ bk
k∈s
[EQ 17.3]
where the summation is over all the geological layer boundaries inside the simulation layer.
You are responsible for choosing values for the following parameters:
• An upper bound on the simulation layer variation, expressed as a percentage of the total
variation of the model.
• An upper bound on the number of geological layers that can be grouped into a simulation
layer.
• The number of layers to be retained as single layers. That is, specific geological layers are
designated to remain as simulation layers. If you specify R layers are to be retained as
single layers, these R layers are those with the R highest variation indices.
The grouping starts at the base of the model, so that the last group of layers, at the top, may have
a variation considerably smaller than your specified maximum.
Flow based upgridding

Flux calculation
There are two options for calculating the fluxes between cells in the geological model. In both
cases, after the fluxes have been obtained, the upgridder carries out the layer grouping operation
as described in the next subsection.
To upgrid imported GEOLITH or SGM (.amd) format geological models that have no inactive
cells, the upgridder can perform the calculation of fluxes. The algorithm is an implementation
of the work of Durlofsky [Ref. 10], and is described in this subsection below.
Alternatively you can run a FrontSim simulation on a fine FloGrid model, then import the fluxes
from the RESTART file output by the simulation (see "Generating and using fluxes for
Upgridding" on page 496).
In the Durlofsky approach we solve two single phase, incompressible, flow problems on a
selected block unit grid, from left to right, and from the back to the front. We refer to these
experiments as the I and the J experiments.
In the experiments we impose constant pressure boundary conditions on two opposing vertical
faces of the reservoir. The pressure on one face is set to unity, and on the opposing face is set to
zero. The other four faces are given zero flow boundary conditions. Without loss of generality,
we set the viscosity to unity.
The flow calculations are performed in a composite manner by setting the transmissibilities
transverse to the pressure drop direction to zero. This greatly speeds the calculations.
Once the flow calculations are performed the geological model layer fluxes are calculated by
accumulating the volumetric flux, independently for each layer, through each face between all
pairs of grid blocks and all exterior faces of the layer. Note that the layer fluxes include the
contributions of both the I and the J experiments.

Grouping the layers
Once these layer fluxes are found, we order the layer fluxes to obtain the flux index for each
layer. The maximum flux is defined to be the flux in the layer with flux index equal to unity, in
other words the flux in the layer with the maximum flux amongst the layers.
You are then required to set three parameters:
• An upper bound on the simulation layer total flux, expressed as a percentage of the
maximum flux.
• An upper bound on the number of geological layers that may be grouped into a simulation
layer.
• The number of layers to be retained as single layers. That is, specific geological layers are
designated to remain as simulation layers. If you specify R layers are to be retained as
single layers, these R layers are those with the R highest flux indices.
Again the grouping is started at the base of the reservoir.
Note Note that when grouping rows or columns, instead of a layer flux we have a row or
column flux. These fluxes still use the I and the J experiments, described above. The
row flux (grouping rows of cells of constant J) uses only the I experiment fluxes. The
column flux (grouping columns of cells of constant I) uses only the I experiment
fluxes.

Generating and using fluxes for Upgridding
The Simulation Flux Output Based option requires the fine BUG to already contain FrontSim
fluxes. This implies that the geological model must itself have been created as a FloGrid model.
You can create a FloGrid model from an imported RESCUE model or imported ECLIPSE grid,
generate properties and fluxes on it, and then upgrid it to create your final simulation model
grid. We shall refer to this existing FloGrid model as the “finescale model” in the descriptions
below.
To generate fluxes for the finescale model, you can either run FrontSim from within FloGrid, or
export the grid and properties, then set up and run FrontSim independently. Using FrontSim
from outside FloGrid allows you to access the full functionality of FrontSim, but requires you
to set up the input decks using ECLIPSE Office or a text editor. For simple cases it is easier to
use the simulation interface (see"Simulation Setup" on page 587), and run FrontSim from
FloGrid.
When running FrontSim from within FloGrid, you must define the well source and sink terms
required for the current flow experiment. Note that the resulting fluxes may vary depending on
the well positions selected.
Alternatively, FrontSim can be run with constant pressure or flux boundary conditions instead
of wells. This means that you can mimic the flow experiments used in the other flow based
upscaling options and described in "Flux calculation" on page 494. The FrontSim keywords
FLUXSIDE and PSIDE can be used to set boundary conditions over a specified area. However,
these keywords are not currently available from within the FloGrid simulator link.
To obtain flux output, the keyword RPTRST must be used with the option FLOWTOT in the
SCHEDULE section of your simulator run. If you are using the FloGrid simulator link, this is
obtained by ticking the output option Graphics Files/Streamlines and RESTART.
Once the FrontSim run has been completed, you need to import the INIT and RESTART files
into your finescale model. You should find six flux properties have been imported called
• FLUXLEFT (the I- fluxes),
• FLUXRIGHT (the I+ fluxes),
• FLUXBACK (the J- fluxes),
• FLUXFRONT (the J+ fluxes),
• FLUXUP (the K- fluxes), and
• FLUXDOWN (the K+ fluxes).
Note These properties are actually flows (reservoir volumes over time). The FloGrid
Upgridder correctly converts them to fluxes when performing the upgridding
calculations.
Note The imported fluxes are those between I J K neighbors. No account is taken in this (or
the other flow-based upgridding algorithms) of non-neighbor connections (NNCs).

You can now create your new coarse scale simulation model by selecting the Existing FloGrid
model option for the Structural basis on the FloGrid creation panel. Then select your finescale
model from the list in Existing FloGrid models. When you proceed with creating the new grid,
the Upgridder panel opens and you can see that the Simulation flux output based radio button
option is enabled for the coarse BUG.
Select Simulation flux output based upgridding: the Options panel has the same options as
the other flow based upgridding choices.

Generating an unstructured grid
Chapter 18
Unstructured Gridder module

The Unstructured Gridder generates simulation grids, cell properties, and well connections for
simulation using geological model definitions from the "Structural Framework" on page 175
and "Geological Property model" on page 215. It can generate prismatic PEBI and triangular
grids with vertical or piecewise linear (segmented) coordinate lines as well as handle cross-
sections of models.
Note You must import all reservoir data and you must build a structural framework before
you can create an unstructured gridding model. If any changes are subsequently made
to the reservoir data they may not be correctly reflected in the Unstructured Gridder.
The Unstructured Gridder window can also be opened for an existing model from the menu
obtained by right-clicking on the model node.
The module has a menu bar from which various menu options can be selected that allow you to
create and edit unstructured grid models.
In order to create an unstructured grid:
• "Creating and editing unstructured grid" on page 501.
• "Gridding order..." on page 524.
• "Generating a grid" on page 525.
• "Gridding Preferences" on page 532.
There are two main types of model: single source and dual source. A single source gridding
model uses structural information from the structural framework to construct the unstructured
grid and derives property values from a property model based on the same structural framework.
A dual source gridding model allows you to derive property values from a property model based
on a different structural framework. The primary use envisaged occurs when an externally
generated geological property model is imported into FloGrid. The geological model, as
imported, may not contain all the structural features that you require, for example faults.
However you may wish to use the imported property data to populate a grid based on an
FloGrid User Guide Generating an unstructured grid 499

enhanced structural framework that you create within FloGrid using additional structural data.
Additionally you may wish your grid to honor a non-structural surface such as the oil-water
contact. You could create a new structural framework with this surface and your original
property model and then create a dual source unstructured grid model based on this new
structural framework and your original property model. There are no restrictions imposed at this
stage on which pairs of structural and property models may be combined in a dual source
gridding model. However the two models chosen should be related in order that the spatial
property value distribution makes sense on the final grid.
You can also add LGRs, Aquifers and Properties to an unstructured grid, for further information
see "LGRs, Aquifers and Properties for an unstructured grid" on page 535.
500 Generating an unstructured grid FloGrid User Guide

Creating and editing unstructured grid
Creating an unstructured grid

You can create an unstructured gridding model using the Create Model module (see "Create a
Model" on page 26).
Alternatively you create a new gridding model with the initial gridding parameters copied from
an existing model. You can then create a new grid as a modification of an existing grid. To do
this, select File | Copy model.... The grid itself is not copied since it is expected that you will
make some changes to the gridding parameters before the grid is regenerated. The new model
uses the same property model and, if it is a dual source model, the same structural framework.
If you have defined any LGR parameters this information is also copied.
You can also rename an existing model. If a grid has been generated for the gridding model, then
the grid is also renamed to match the new gridding model name.
Grid parameters
It is best to create a new model for importing grids using the Create Models module (see
"Create a Model" on page 26). However you can import gridding parameters including
geometry using a series of import files.
Any existing grid is overwritten if the file is imported to an existing gridding model. Also, since
the gridding parameters are not reset when the grid is imported, they are generally inconsistent
with those used to generate the grid.
You can also export grid parameters using a series of files; for further information see "Export
files" on page 808.
• "Boundaries" on page 501.
• "Cell centers" on page 502.
• "Wells" on page 502.
• "Gridding parameters for wells" on page 504.
• "Bulk areas" on page 513.
• "Layer controls" on page 518.
• "Cross section..." on page 521.
Boundaries
Boundaries are used to define the extent of the structural framework, structured and
unstructured grids, and regions. A boundary created in another part of the software may be
exported and imported later in another section or for a different project. You can import
boundaries using File | Import regions... from the Tools | Old Workflows | Unstructured
Gridder... option.

Boundaries may be either rectangles or polygons. The file format for either type is the same
except for the keyword REGION and the necessity to mark major points in a polygon boundary.
The polygon is completed internally by the program, by linking the first and the last points.
For information on the file formats see "Boundary file formats" on page 805.
You can also export boundaries to ASCII files using File | Export regions....
Cell centers
Cell centers and cell vertices help to define the structure of PEBI and tetrahedral grids
respectively. You can import sets of points (from an ASCII file) that define the position of cell
centers or vertices, using File | Import points... or File | 2D points. This allows you to generate
a customized grid, rather than letting the Unstructured Gridder automatically generate cell
centers and vertices in the main bulk.
The imported points are used in addition to points generated automatically for model features
like wells and faults. There is no restriction on the density or randomness of the imported points.
For further information on the files you can use to import gridding parameters see "Import files"
on page 805.
Wells
The main Wells menu in the Unstructured Gridder contains the following options:
Auto connect...
Automatically generates well connection factors for the grid and all selected well tracks. A list
of all available wells is presented with all wells initially selected. You can accept the default
selection or choose a subset of the wells. A grid must be generated and permeability sampled
before calculating the well connections. Any existing well connections are cleared by this
option.
The Log Window reports how many connections were made for each well. If any imported wells
do not intersect the grid, a message is returned saying
Unconnected wells present
The Log window also reports which wells did not have connections.
When the well connections have been made, a new property in the 3D Viewer is created called
WellConnection. Each well is given a unique integer value, depending on the order in
which it was imported into FloGrid. Cells with a WellConnection value of zero are cells
without connections. The WellConnection value 1 is assigned to the first well imported in
the Structural Framework. Use Scene | Grid | Property | Threshold to hide all cells, which
have a WellConnection value of zero, leaving in the display only cells that have
connections to well tracks.
Note If more than one well passes through a single cell, the last well takes precedence when
selecting the cell color in the WellConnection property.
The grid dependent trajectory data for Schedule and the COMPDAT data for ECLIPSE can be
exported using File | Export Trajectory/COMPDAT Keywords.

Manual connect...
Opens the Manual Well Connection panel, which provides a greater degree of control over the
generation of well connection factors.
Well
Selects the well of interest.
Cell
Selects the grid cell of interest. This can be done by selecting the domain and entering the IJK
numbers of the cell, or if Pick Cell is enabled, the cell can be selected in the 3D Viewer. The
cell is highlighted if Paint Cell is enabled.
Connections
• Add single cell
Calculates the connection factor for the selected cell only, provided that the well passes through
the cell.
• Trace cells
Starts from the selected cell and traces along the well track in both forward and backward
directions to locate further cells. Tracing stops when the end of the well track is reached or when
the well track exits the grid. Connection factors are calculated for all cells found.
Note Manual well connections and automatic well connections for imported grids are
always generated by tracing along the well track within the grid. This is in contrast to
the automatic procedure for generated grids, which includes special treatments for
certain well gridding styles. This means that the two procedures can produce different
results if a well has been gridded to and if the grid does not honor the well track exactly.
This is especially true for algebraic gridding where the original well track can pass
outside one of the very small central cells within the cell length.
Upscale Connections (Advanced)...

Opens the Well Connection Upscaling panel, which enables well connection transmissibility
factors to be made more accurate by incorporating results from a fine grid. With the coarse grid
selected as the current gridding model, both coarse and fine grid summary files must be
imported (File | Import Summary File) before upscaling can be performed. The well
connections must be generated first in the standard way with Well | Generate Connections.
The resulting transmissibility factors are then overwritten by the upscaling operation.
First report step

Sets the number of the first report step for which upscaling is to be performed.
Last report step

Sets the number of the last report step for which upscaling is to be performed. If more than one
report step is specified an average is taken.
Well Connection Factor Upscaling

Well connection upscaling is performed by running local single phase simulations on the
original coarse grid and a fine grid. All wells must be run at a representative rate. The run time
must be long enough to feel boundaries and any other wells of interest.

The upscaled well connection factor is calculated as
c c c
CD θ k h
T = -----------------------
-
c
r0
ln ----- + S
rw
where
c c c c
r CD θ k h c
- ( P0 – P fw )
ln ----0- = -----------------------
rw c c c
q B μ
C D Darcy’s constant
c
θ completion angle (set to 2π )
c
k permeability (taken from the grid)
c
h thickness (taken from the grid)
c
q flow rate (COFR in the coarse grid summary file)
c
B formation volume factor
c
μ viscosity (BOVIS in the coarse grid summary file)
c
P0 pressure (BPR in the coarse grid summary file)
f
Pw bottom hole pressure (WBHP in the fine grid summary file)
The final connection factor is set to be the mean over the specified report steps of the magnitude
of the vector T (evaluated for the permeability and thickness in the x, y, and z directions)
Formation volume factor

Sets a value for the formation volume factor to be used in the calculation.
Selecting OK initiates the upscaling operation and results are reported to the Log Window.
Gridding parameters for wells

The following options on the Edit menu allow you to define the gridding parameters used for
wells.
Well controls...
Opens the Edit Well Controls panel. The parameters defined in this panel apply to only a single
well, unless the M-Apply option is used.
Well
Selects which well to use as the current well from the drop-down list. All subsequent parameter
choices apply to this well.
Grid to well
Set whether or not the well chosen above is honored during gridding.

Slope to well
This checkbox is only enabled for fault framework based gridding when a vertical grid style has
been selected. It allows you to control which wells are to be honored when sloping the grid when
grid deviation is enabled. For non fault framework based gridding all wells with a vertical grid
style that have Grid To Well enabled are used to slope the grid.
Grid style
From this drop-down list a number of gridding styles are available for applying to the wells.
Vert: single cell (bulk size)

The well is honored by a single cell placed at the well’s end point. This option is intended for
gridding vertical wells (or horizontal wells in cross section gridding). The size of the cell is
controlled by the spacing of the background bulk grid and the number of sides of the cell is
controlled by the Azimuthal Divisions field.
Vert: single cell (fixed size)

The gridding is as forVert: single cell (bulk size), except that the size of the cell is controlled
by the Cell Length field.
Vert: radial
The well is honored by a radial grid centered on the last point of the well track. This option is
intended for gridding of vertical wells (or horizontal wells in cross section gridding). The radial
grid can be defined using automatic or custom settings. For both options, the absolute size of
the cells is set by the Well Radius and Outer Radius fields.
For the automatic option, the number of cells in the radial grid is set by the radial Divisions and
Azimuthal Divisions fields. The size of the cells increases logarithmically outwards from the
well radius to the outer radius. Hence:
r(0) = rWell
r(n+1) = r(n) * dr (n = 0, rDivisions-1)
dr = (rOuter/rWell)**(1/rDivisions)
The cell sizes are uniform in the azimuthal direction.

For the custom option, you can control the relative size of cells by activating the Use Custom
Azimuthal Divisions and the Use Custom Radial Divisions toggles, and then opening the
Azimuthal Divisions Controls and Radial Divisions Controls panels (see "Set azimuthal
divisions" on page 510and "Apply inner radius" on page 509).
Vert: fractured
This generates a grid representing a fracture with a radial like section around the well and two
linear sections along the fracture (see Figure 18.1).

Figure 18.1 Vertical fractured well grid, showing well control parameters
fracture
width cell length
radial divisions = 2
azimuthal divisions = 14
fracture half length
outer radius fracture orientation
well radius
The number of radial divisions in the radial section is given by the Radial Divisions field. The
absolute size of the cells is set by the Well Radius and Outer Radius fields, and cell sizes
increase logarithmically outwards from the well radius to the outer radius in the same way as
the vertical radial grid style. The number of azimuthal divisions is controlled by the Azimuthal
Divisions and is equal to 6+4n, where n is an integer, such that the total is less than or equal to
the Azimuthal Divisions.
The fracture is defined using the Fracture Controls panel (see "Set Fracture controls" on
page 510). The size of cells along the fracture sections is given by the Cell Length field.
Horz: (bulk spaced)

Rectangular cells are generated along the well track. The number of cells along the well track
is derived from the background bulk grid. The number and size of cells across the well track are
set by the Inner Radius, Outer Radius and Radial Divisions fields. There will be n cells
between inner and outer radii with logarithmic growth outwards from the inner radius, where n
is the number of radial divisions.
Horz: (fixed spaced)

The gridding will be as for the bulk space horizontal well style above, except that the number
of cells along the well track is controlled by the Cell Length field.
This is the only available well type for 3D local grid refinements (LGRs). For 3D gridding, the
number and size of cells across the well track are set by the Inner Radius, Outer Radius and
Radial Divisions fields. The number of divisions around the well track is set by the Azimuthal
Divisions field.
Horz: algebraic (bulk spaced)

This grid style produces a similar looking grid to Horz: (bulk spaced), and is controlled by the
same fields, but uses a different algorithm used for the gridding. It generates well domains
algebraically, allowing fine resolution around wells and sharp bends in well tracks, but it is
limited to gridding complete domains.

Horz: algebraic (fixed spaced)
The gridding will be as for the algebraic bulk spaced horizontal well style, except that the
number of cells along the well track is controlled by the Cell Length.
Horz: fractured (bulk spaced)

This generates a grid representing a horizontal or sloping well intersected by fractures, which
can be oriented along (parallel fracture) or across (perpendicular fracture) the well track. The
algebraic gridding algorithm is similar to that used for the Horz: algebraic (bulk spaced) well
style, but adapts the radial cell sizes so as to honor the fractures (see Figure 18.2).
Local refined zones are inserted into the grid around perpendicular fractures. The target cell
sizes are set using the Inner Radius, Outer Radius, Radial Divisions fields and the
background bulk grid. The fractures and refined zone cell sizes are defined using the Fracture
Controls panel (see "Set Fracture controls" on page 510).
Figure 18.2 Horizontal fractured well, showing well controls parameters
Perpendicular fracture F1
Parallel fracture F2
F1 MD cell length
F2 MD outer
radius
F1 half
length
inner
radius
F1 zone half width

F2 half length
F1 width
F1 num divs = 1
radial divisions = 2
Horz: fractured (fixed spaced)

The gridding is as for Horz: fractured (bulk spaced), except that the number of cells along the
well track is controlled by the Cell Length field.
Horz: 2D/3D (fixed spaced)

This creates composite well domains with a 2D part and a 3D part. The two outermost sets of
cells are of 2D type and the remaining cells are of 3D type. You specify the cell lengths along
the track in both 2D and 3D parts in the Cell Length field. The 3D part extends from the well
bore surface (well radius) to the start of the 2D part. The 2D part extends from the end of the
3D part to the outer radius. The cell size in the 3D part increases outwards from the well radius
in the same way as the Vert: radial well style. The cell size in the 2D part then continues to
increase at the same multiplicative rate dr.

The number of divisions used by the 2D part is controlled by the config file entry
NUMBER_OF_2D3D_WELL_2D_RADIAL_DIVISIONS, which is defaulted to 2. If this value
is changed to 0, the outer radius applies to the end of the 3D region and the number of radial
divisions applies to the 3D region. Hence, the total well grid extends to a region larger than the
outer radius, by two 2D cells.
Note This is considered to be a 2D well style because it can only be used in 2D grids. The
3D well style Horz: (fixed spaced) must be used for 3D local grid refinements
(LGRs).
If there are problems fitting the well domain, try increasing the number of radial divisions to 8
and the number of theta divisions to 8. This reduces the value of dr for the 3D PEBI region
around a well, which results in a lower overall size required to fit the well.
Well radius / Well skin

These should reflect the radius and skin of the well bore. A well radius is typically 0.3-0.7 feet.
The skin is a dimensionless quantity that reflects the wellbore damage. The default value for
skin is zero, indicating no damage. Typical values range from zero to two. The well radius is
used in radial gridding and both radius and skin are used in well connection factor calculations.
Cell length
Defines the length of cells along a well track when a fixed space well style is used.
Radial Style
Logarithmic
The radii grow logarithmically from the wellbore radius. The outer radius of the innermost cells
may be fixed or be controlled by a minimum value.
r(0) = well radius

r(1) = if (Apply Inner Radius) rInner else r(0) * dr(0)
r(i+1) = r(i) * dr(i) where i=[1,nr-1]
dr(i) = (rOuter/r(i))**(1/nr-i)
Note Using the logarithmic radial style without applying an inner radius limit can lead to
small cells next to the wellbore leading to poor simulator convergence.
Geometric
The radial cell sizes grow by a constant factor from the inner radius to the outer radius.
r(0) = well radius

r(1) = rInner
r(i+1) = r(i) + a * (r(i)-r(i-1)) where i=[1,nr-2], a is constant
r(nr) = rOuter

Linear
The radial cell sizes are constant between the wellbore radius and the outer radius. The outer
r(0) = rWell (not used in horizontal grids)

r(1) = if ( rInner > rWell ) rInner else (rOuter - r(O))/nr
r(i+1) = r(i) + (rOuter - r(i))/(nr-i) where i=[1,nr-1]
radius of the innermost cells may be fixed or be controlled by a minimum value.
Custom
This enables the use of customized specification of the number and size of cells in a radial well
domain in the R direction (radial). When enabled the program ignores the value in the Radial
Divisions field and uses the table displayed by the Set Radial Divisions button.
Apply inner radius
Ignore
This does not apply any inner radius constraints.
Minimum
This uses the inner radius value as a minimum limit during radial division calculations. It
applies to the outer radius of the innermost cells.
Fix
This uses the inner radius value as fixed required value during radial division calculations. It
applies to the outer radius of the innermost cells.
Set radial divisions

This button opens the Radial Divisions Controls panel. The panel contains a table that
specifies the number and sizes of radial divisions, for customized use. The number of rows in
the table specifies the number of divisions and the weights specify the relative size of the
divisions. The division number increases outwards from the well bore and the radial size of an
individual division is given by:
(rOuter-well radius) * weight / sum of weights
Inner radius
For tetrahedral grids this is the distance from a well track to the edges of the innermost cells in
a horizontal well domain. For PEBI grids this is the distance from a well track to the center of
the innermost cells.
Outer radius
For tetrahedral grids this is the distance from a well track to the edges of the outermost cells in
a horizontal well domain. For PEBI grids this is the distance from a well track to the center of
the outermost cells.
Radial divisions
For a radial well this defines the number of cells in the R direction (radial). For a horizontal well
domain this defines the number of cells normal to the track.

Use custom azimuthal divisions
This enables the use of customized specification of the number and angle of cells in a radial well
domain in the theta direction (angular). When enabled the program ignores the value in the
Azimuthal Divisions field and use the table opened by the Set Azimuthal Divisions button.
Set azimuthal divisions

This button opens the Azimuthal Divisions Controls panel. The panel contains a table that
specifies the number and angles of azimuthal divisions, for customized use. The number of rows
in the table specifies the number of divisions and the weights specify the relative angles of the
divisions. Theta Origin, measured clockwise from the gridding model coordinate systems’s x-
axis, defines the axis from which the azimuthal division definitions start. Divisions are
numbered clockwise from this starting axis, and the angle of an individual division is given by:
360 degrees * weight / sum of weights
Note When there are many wells in a project, it is important to keep the cell size around the
wells small enough to prevent neighboring well-cells from interfering with each other.
If the cell sizes are too big, some of the cells around wells, which lie close to each other,
may not be centered around the well. It is recommended that the well-cell size should
be a quarter of the distance between wells when there are many wells clustered
together.
Azimuthal divisions
This specifies the number of cells in a radial well domain in the theta direction (angular). For
3D gridding it specifies the number of divisions around the well track.
Set Fracture controls

Opens the Fracture Controls panel, used to set special parameters for the vertical and
horizontal fracture gridding styles. Depending on the well style selected, a different panel will
be opened.
For the Vert: fractured well style (Figure 18.1), the panel contains the following fields:
Fracture half length

This is the length of each of the two linear sections.
Fracture width
This sets the width of the fracture cells. It must be less than the inner radius value set on the
main panel.
Fracture orientation
This sets the rotation angle of the fracture line. The angle is measured clockwise relative to the
x -axis of the gridding model coordinate system.
Fracture top and fracture bottom

These two fields set the absolute vertical extent of the fracture. The values are relative to the
gridding model coordinate system, that is Z positive and increasing downwards. The fracture
grid domain extends the full depth of the model grid, but the fracture porosity and permeability
is only applied within these vertical limits.

Fracture porosity
This sets the porosity value for the fracture cells. This value takes precedence over sampled
porosity during property generation within the fracture top and bottom limits.
Fracture permeability
This sets the permeability value for the fracture cells. This value takes precedence over sampled
permeability during property generation within the fracture top and bottom limits.
For the Horz: fractured (bulk spaced) and Horz: fractured (fixed spaced) well styles
(Figure 18.2), the panel contains a table with one row per fracture and the following columns:
MD
This sets the measured depth along the well track at which the fracture is located. For
perpendicular fractures this is the position at which the center of the fracture intersects the well
track. For parallel fractures, that is fractures that lie along the well track, this is the position of
the center of the fracture. Fractures must be added to the table in order of increasing measured
depth. Fractures must not overlap and there must be sufficient space between them to contain
the refinements (Zone Half Width) for individual perpendicular fractures.
H.length
This is half the length of the fracture, that is the length of the fracture either side of the measured
depth value set above. For perpendicular fractures, this defines the radial distance away from
the well track. For parallel fractures, this defines a distance along the well track.
Width
This parameter only applies to perpendicular fractures. It sets the width of the fracture cells, that
is the central row of cells perpendicular to the well track within the refined zone. The fracture
width must be less than the fracture zone width (that is twice the fracture Zone Half Width).
DZ above and DZ below

These set the distance above and below the well track for which fracture properties are applied
during property generation. The fracture grid domain extends the full depth of the model grid,
but the fracture porosity and permeability is only applied within these vertical limits.
Zone H.width
The Zone Half Width parameter only applies to perpendicular fractures. It sets the distance
from the fracture center (the measured depth value) to the edge of the zone of refined grid cells
either side of that fracture. The Zone Half Width is therefore a distance along the well track. It
must be less that the cell length (if known).
Num div
This parameter also only applies to perpendicular fractures. It sets the number of divisions in
the refined zone either side of a fracture. Cells within the refined zone increase in thickness
logarithmically outwards from the fracture, from the fracture width. Thus:
r(n+1) = r(n) * dr
dr = (ZoneHalfWidth/Width)**(1/NumDiv)
where r is the distance along the well track from the fracture measured depth.
Orient’n
The orientation of a fracture can be chosen from Parallel and Perpendicular.

Parallel fractures represent fractures that are oriented along the well track and that intersect the
well. The well grid honors the ends of the fracture, using the Half Length parameter, but does
not explicitly represent the fracture width. A parallel fracture’s properties are applied to all
central cells of the well domain that lie between the fracture ends, and that lie between the
vertical limits set by DZ above and DZ below.
Perpendicular fractures represent fractures that are oriented perpendicular to the well track and
that intersect the well. The well grid inserts refined zones perpendicular to the well track,
centered on the fracture measured depth, and extending outwards from the well track for the
fracture Half Length distance. A perpendicular fractures’s properties are applied to the central
cells of the refined zone.
Fractures that intersect a well at intermediate angles must be assigned by you to one of the two
fracture types.
Porosity
This sets the fracture porosity at the center of the fracture
Tip por.
This sets the fracture porosity at the outer ends of the fracture. Fracture porosity values for each
cell are interpolated linearly between the center porosity and tip porosity values.
Perm
This sets the fracture permeability at the center of the fractures.
Tip Perm.
This sets the fracture permeability at the outer ends of the fractures. The permeability values are
interpolated linearly between the center and tip values for each fracture cell.
M-Apply
When M-Apply is chosen the Multiple Apply panel appears. The list on the left side of the panel
allows you to choose which wells the parameters apply to. The right side of the panel shows the
values entered for the controls. Clicking on OK applies the value of the parameters selected in
the list on the right to all the wells selected in the list on the left rather than defining parameters
for every individual well.
Faults
The fault control options are available from the Edit menu.
Fault controls...
Opens the Edit Fault Grid panel. The parameters defined in this panel apply to only a single
fault unless the M-Apply option is used.
For fault framework based gridding fault controls are made available for each of the control
surfaces. Control surfaces may represent real faults or they may be introduced to guide the grid.
Fault
Selects which fault to use as the current fault from the drop-down list, and all subsequent
parameter choices apply to this fault.
Grid to fault
Sets whether or not the fault chosen above is honored during gridding.

Slope to fault
This checkbox is only enabled for fault framework based gridding. It allows you to control
which faults are to be honored when sloping the grid when grid deviation is enabled. For non
fault framework based gridding all faults that have Grid To Fault enabled are used to slope the
grid.
Grid style
From this drop-down list two gridding styles are available for applying to the faults.
Fixed spaced
A grid with dimensions 2 x n is produced along the line of the fault in each K-layer, where n is
the number of cells along the fault. The number and size of cells along the fault is controlled
with the Cell Length field. The size of cells across the fault are controlled by the Cell width
field.
Bulk spaced
Gridding is as above, except the size of the cells is derived from the varying size of the
background bulk grid.
Cell length
Defines the length of cells along a fault.
Cell width
Defines the length of cells across a fault.
Transmissibility multiplier
For fault framework based gridding transmissibility multipliers are only available for controls
corresponding to faults in the Fault Framework. If there are multiple controls associated with
a single fault then care should be taken to only set the multiplier on one control.
Apply multiplier
This applies a multiplier to the transmissibilities across the fault. The locate faults option (see
"Locate faults" on page 526) must be enabled in the Grid Generation Options panel if
multipliers are to be used. The multiplier can be changed after the grid has been generated and
this takes effect next time transmissibilities are calculated.
Multiplier
This is the selected value of the multiplier. The multiplier is applied to all layers and to faces
between cells that lie on either side of the fault. The fault may be completely honored during
gridding, partially honored or not selected for gridding.
Bulk areas
The bulk of the model contains the cells not included around the wells and faults. Normally the
gridding parameters for the bulk apply to the whole area of the bulk. However, smaller bulk
areas may be created to allow different gridding parameters to be applied to different areas of
the model. For example, you may wish to refine an area of high permeability or an area with a
high well density.
To define gridding parameters for bulk areas select Edit | Bulk controls... .

Bulk controls...
Opens the Edit Bulk Controls panel.
Bulk
Selects which bulk to use as the current bulk from the drop-down list, and all subsequent
parameter choices apply to this bulk.
Grid to bulk
Sets whether or not the bulk chosen above is honored during gridding. If the main bulk is not
selected, points inside the bulk are not used to generate the grid.
Note Even if the Main Bulk is deactivated, the grid is still generated to the extent of the main
bulk’s boundary. The extent of the simulation grid’s boundary is determined by the
Clipping Boundary, which can be found in Grid | Options | Grid Generation.
Bulk boundary
This is the boundary defining the area in the selected bulk.
Grid to boundary
Sets whether or not the boundary chosen above is honored during gridding. If the boundary is a
geological feature it should be used in the generation of grid cells. For example, cells around
faults should honor the fault positions and lie exactly along the fault.
If a bulk region is created around a group of wells for further refinement, it would not be
appropriate to insist that grid cells follow that boundary. The refined cells are generated within
the region but should not honor what is really an artificial boundary.
To ensure that a smooth grid is created along the outer edges of the grid, you should enable Grid
to Boundary for the Main Bulk.
Note For PEBI gridding, the main bulk boundary is always honored, regardless of the switch
set for Grid to Boundary.
Create new bulk

Opens the Add New Bulk Region panel. A new bulk region may lie directly inside the main
bulk or inside another bulk region.
Note For LGR models in which multiple LGRs have been defined, the new bulk is set for
the same LGR as the currently selected bulk.
New bulk name

Enter the name of the new bulk.
Bulk boundary
Choose a bulk boundary. Initially, no bulk boundaries are available to choose from.

Derive new boundary
Create new boundaries that surround an existing gridded feature - bulk, fault or well. You can
use this option when creating any new bulk, but it is particularly useful when creating a
transition bulk (see "Transition" on page 516).
• Use bulk / Use fault / Use well
Select which type of feature to derive your boundary from with this radio button. The radio
button is initially be set at the first of these options that actually has features to derive from, or
to Use Bulk.
Note If there are no features within your unstructured grid model from which to derive a
boundary, then the three drop-downs described next are all disabled.
• Bulk
The list of bulks from which you can derive a boundary. If there are none, that is only the
main bulk exists, then this drop-down cannot be enabled. Otherwise, enable it by selecting
UseBulk in the radio button, and select the bulk.
• Fault
The list of faults from which you can derive a boundary. If there are faults to choose from,
you can enable the drop-down by selecting Use Fault and selecting the appropriate fault.
• Well
This drop-down contains the list of wells. If there are wells to choose from, you can enable
the drop-down by selecting Use Well and selecting the appropriate well. You can only
derive a boundary from a sloping or horizontal well, though vertical wells appear in this
list. A message appears on the panel if you select a vertical well and click OK create the
boundary.
• Absolute distance from feature and Relative distance from feature
You set the distance of the derived boundary away from the feature with these two fields.
The relative distance is the fraction of the feature size - the length of a fault, or length in the
horizontal plane of a well, or the longest horizontal dimension of a bulk. The distance of
the derived boundary from the feature is then given by
dist = absDist + relDist * featureSize.
Edit boundaries
Creates new boundaries or to copies existing boundaries.
For a fuller description of the options available on this panel see "Defining and editing
boundaries" on page 311.
• Boundary list
There are a limited variety of boundary lists available - Structural Framework
Boundaries, Structured Gridder Boundaries, or Unstructured Grid Boundaries. Each
list has its own set of boundaries.
If any boundaries have been created for the chosen list, they are listed in the table below.
• Create
Opens the Create Boundary window, allowing you to digitize a rectangle or polygon for
the boundary.
• Copy from

Copies a boundary from some other Boundary List.
From the window Select Boundary to Copy, choose the Boundary List to copy from and
highlight the particular boundary to copy. Choose OK and enter a new name in the Copy
Boundary panel or use the default name supplied. See "3D Viewer" on page 107 for further
details on digitizing and editing boundaries.
Grid style
There are five styles of gridding you can choose from for the background bulk.
Rectangular
A rectangular grid has cells with six faces, and all vertical faces are at right angles to each other.
The cells have a constant size. This is defined as a regular hexahedral grid.
Hexagonal/Triangular
Generates a regular grid of hexagonal or triangular cells, depending on whether PEBI or
Tetrahedral gridding is chosen. The cells have a constant size.
Radial
Primarily used for single well studies. In a radial grid the bulk cells are radially distributed
around a well and grow logarithmically from the well. The well around which gridding is
defined in the Radial/Elliptic bulk well option. The maximum cell size is defined by the Set
cell size limits panel.
Elliptic
Primarily used for horizontal or fractured vertical single well studies. In an elliptic grid the bulk
cells are symmertically distributed around a well and grow logarithmically from the well. The
well around which gridding is defined in the Radial/Elliptic bulk well option. The growth rate
and theta divisions of the cell distributions are fixed to match those of the well. The maximum
cell size is defined by the Set cell size limits panel.
Variable
Generates a variable density grid in which the cell sizes grow from each well up to a maximum
value. Cell sizes along boundaries take the local background size. The maximum cell size is
defined by the Set cell size limitspanel.
Transition
Provides a linear decrease of cell size from a maximum at the boundary to a minimum at a user-
specified distance inwards from it. The cell size further away from the boundary, that is further
within the transition bulk, remains constant. You can create these regions by digitizing arbitrary
boundaries (see "Edit boundaries" on page 515) or by deriving boundaries from existing
features (see "Derive new boundary" on page 515). In the latter case the transition bulk forms a
buffer zone between the feature and the background, providing a smooth cell size growth.
Grid smoothing is recommended with this style. The cell sizes and transition zone width are set
from the Set cell size limits panel.
Radial/Elliptic bulk well

When the grid style is Radial, cells radiate from a single well within each bulk and grow in size
logarithmically from the well. By default the chosen well is the first well within the bulk region.
It can be overridden by selecting a specific well from this drop-down list of wells.

Smoothing iterations
Moves the nodes of triangles or tetrahedra towards the averages of their neighbors in order to
smooth the resulting grid. The smoothing iteration number should be zero for rectangular bulk
regions, because smoothing destroys right angled triangles. There is a re-triangulation following
each smoothing iteration.
Grid refinement
The number of grid cells to use in the bulk grid can be determined by specifying the Number
of Cells in each I- and J-direction or by specifying the Cell Size in map units.
Use number of cells/Use cell size

You can toggle between these options to indicate either the use of cell numbers or of cell sizes
to define the bulk area.
Cells in I / Cells in J
Specifies the number of cells in either the I-direction or the J-direction when defining the bulk.
Cell size in I / Cell size in J

Specifies the size of the cells in either the I-direction or the J-direction when defining the bulk.
Set IJK directions

Opens the IJK Direction panel.
Bulk alignment
There are three options for aligning the grid: Maps, Grid Boundary, and Custom.
If Boundary or Maps is chosen for the orientation, the bulk grid is aligned with the first major
segment of the boundary or the first tops map. In both cases the angle between the axes is
restricted to 90 degrees, creating orthogonal axes.
For Custom orientation:
• Axes Rotation Angle
Specifies an angle relative to the orientation of the default X Y axis.
• Angle Between Axes
Specifies the angle between the two axes.
Snap to point
Snap to Point is designed to ensure that a grid is centered around a particular well location.
You enter an X Y position for the grid to snap to, in the Snap Point table below, and when the
grid is generated, the nearest cell center or cell vertex is moved to the X Y position, and the grid
is shifted accordingly. The cell center is moved for a PEBI grid, and the cell vertex is moved for
a tetrahedral grid.
Set cell size limits

Opens the Cell Size Limits panel for setting the minimum and maximum cell sizes for Radial,
Elliptic, Variable and Transition bulk gridding. The minimum (and maximum) cell size within
the region is given by:
Cell_Size = Absolute_size + Relative_size * Model_Size

The Cell Size Limits panel is also used to set the transition zone width for transition bulk
gridding. The width is the distance inward from the bulk boundary over which the cell size
varies linearly from the outer maximum to inner minimum cell size. It is given by:
Width - Absolute_width + Relative_width * Model_Size
Layer controls
The layer controls determine the vertical gridding within units. The number of units was
determined in the structural model, and the vertical gridding always honors the horizons
between each unit. You can control the number and style of layers (refinements) within each
unit, or alternatively within each individual block-unit.
Note For unstructured LGR models, the Edit Layer Controls panel is opened from the Edit
LGR panel.
Edit layer controls...

Opens the Edit Layer Controls panel.
Layering basis
You toggle this radio button between Unit-wide controls and Block-unit controls. If you choose
Unit-wide controls, then you can specify the layering for each unit as a whole. If you choose
Block-unit controls, then you can specify the layering individually for each block-unit.
When you change between the two options you are warned that the existing settings of layering
methods, and the refinement parameters, are reset. You given the option to say No to changing
the option.
If you say Yes, and change from Unit-wide to Block-Unit, the current settings for each unit are
copied for each block in that unit.
If you say Yes, and change from Block-unit to Unit-wide, the settings for the first block in each
unit are applied to the whole unit.
Number of layers per unit

The number of layers within a given unit are the same for all its block-units. You can set the
number of layers in the selected unit in the drop-down menu item Unit (top down numbering)
using this field. You can also change the number of layers in the unit when entering the
refinement parameters from one of the panels opened from the menu item Refine Selected
Block Unit(s).
Unit (top down numbering)

Selects the unit for which to define the vertical gridding from this drop-down. The units are
listed in top down order by name.
Block(s)
If you are doing Block-unit based layering, you select the block within the unit for which to
define the vertical gridding from this drop-down. The blocks are listed by name. If Unit-based
layering has been chosen, this drop-down is disabled.

Layering method
You have five different vertical gridding styles to choose from in this drop-down.
Proportional
The thicknesses of each layer within the (block) unit is a proportion of the total unit thickness
at each location. The relative thickness of each layer is determined by weights.

The absolute thickness of each layer is specified, and each layer is defined relative to the base
of the layer above or the upper horizon of the unit.

The absolute thickness of each layer is specified, and each layer is defined relative to the top of
the layer below or the lower horizon of the unit.
Use property model

This option allows you to specify the vertical gridding in terms of the property model layers (if
any) within the (block) unit ("Geological Property model" on page 215). The base of each layer
is defined as the base of a property model layer.

This option is usually the same as Use Property Model. There is a difference for dual source
unstructured grid models, which have been built over a property model whose layers are defined
implicitly (for example as eighty proportional layers, or thirty top-conforming layers each of
100 m thickness). In that case, the simulation layers are defined using those parameters rather
than the actual property model layer surfaces. This can help if improve the simulation grid near
faults if the property model does not explicitly contain the faults and so the property model
layers are sloped across the fault, whilst the structural model contains a throw across the fault.
Upper reference surface

If the proportional or top-conforming gridding styles have been selected, this dropdown allows
you to select the upper reference surface. For the default behavior (using the upper horizon of
the unit), leave this set to “Default (top of unit)”.
Lower reference surface

If the proportional or bottom-conforming gridding styles have been selected, this dropdown
allows you to select the lower reference surface. For the default behavior (using the lower
horizon of the unit), leave this set to “Default (bottom of unit)”.
Property model / scenario

If there are multiple property models or multiple scenarios and if Use property model layering
is selected, this lets you select a property model and scenario.
Refine Selected Block Unit(s)

Clicking on this button opens the panel UnitName AllBlocks (Unit wide layering) or
UnitName BlockName (Block-unit layering) in which you define the vertical gridding
parameters. The panel contains information on the layering method and a table in which you
enter the parameters. The contents of the table corresponds to your selection of layering method.

All methods
To add a layer to the table, highlight the layer below which you want the new layer and type
Ctrl-n or click on the + at the top right of the table.
To delete a layer, highlight the layer and type Ctrl-d or make a selection from the right mouse
button drop-down menu.
Proportional
The table contains the weights for the relative thickness of each simulation layer within the
(block-)unit. The layers are listed in top down order. The thickness of an individual layer is
given by:
thickness = unit thickness * (weight / sum of weights)

Each layer in a top conforming layered unit has a constant thickness. The table contains the
absolute thicknesses of each layer, again listed top down within the (block-)unit. Since absolute
thicknesses are specified, it is possible that parts of a unit are thinner than the total thickness of
all layers, or alternatively are thicker than the total thickness of all layers. If the unit is thinner,
then the simulation layers are truncated at the base of the unit. If the unit is thicker, the program
ensures that the specified number of layers fills the unit by extending the lowest layer to the base
of the unit. The latter case means that the thickness of the lowest layer is not used within the
program, and is read-only in the panel. However the full number of layers must be present in
the table for consistency.

This table is similar to the top conforming case. Simulation layers are still listed in top down
order. However, since this option represents bottom conforming stratigraphy, the layers are
truncated or extended if required at the top of the unit, and the first layer in the table is read-only.
Use property model

You enter the layer IDs of the property model layers that you want to use to define for each
simulation layer in the table. The simulation layers are listed in top down order. The base of the
property model selected forms the base of the simulation layer. The layer IDs are the unit-wide
equivalent layer IDs for the unit.
Note They are in the same order as the 3D Viewer (see "Property Model" on page 110).
Individual block-units within a unit may not contain all of the unit-wide equivalent
layer IDs. If such a layer ID is selected, then the simulation layer is pinched out in that
block-unit.
Above the table, you find some information on the layering within this (block-)unit in the
property model. For a single block property model the layering method is reported. For all
property models, the number of layers within the (block-)unit, and the ranges of valid layer IDs
for the (block-)unit are reported. You can also examine the property model in the 3D Viewer
while this panel is open, and identify which layer IDs you want to use by picking them within
the 3D Viewer.

Like the Use Property Model option, you enter the layer IDs of the property model layers that
you want to use to define for each simulation layer in the table.
Cross section...
A grid through a cross section of the structural framework can be created at a position defined
by you. The Edit Cross Section Controls panel allows you to define the cross section
parameters.
Note To create a cross section rather than a full grid, the option Grid cross section must be
enabled in the Grid Generation Options panel using Grid | Options | Grid
Generation.
Cross section end points

Specifies the end points of the cross section line in the areal view. The first row refers to the start
of the line and the second row refers to the end of the line.
Note For anisotropic permeability, the x and y components are resolved along and across the
cross section line, respectively. The permeability is interpreted in the same directions
as for normal gridding if the cross section line is parallel to the x-axis.
Thickness
Defines thickness of the cross section. The drop-down menu allows you to specify which units
are used.
Cross section position

Specifies whether the cross section is centered on the areal line or to the right or left of the line.
Refine thickness
Opens the Thickness Refinement panel, which allows you to enter subdivisions and weights
for the cross section.
• To add a refinement, type Ctrl-n to add a new row.
• To delete a refinement, type Ctrl-d to delete a row.
Refinements may also be added by clicking on the + symbol in the top right corner of the
panel or by making a selection from the right mouse button drop-down menu.
Weights must be greater than or equal to 0 and less than or equal to 1. The cross section is
proportionally subdivided according to the weight list. If all subdivisions have a weight of 1,
they are divided into equal parts.

Well Ranges...
This panel controls how wells are presented to the Unstructured Gridder. You can add new
wells imported after the gridding model was created, and you can control which parts of the
wells are to be honored by the Unstructured Gridder. Several sections of a well may be chosen
to be honored—in this dialog each is referred to as a well range. Throughout the rest of the
Unstructured Gridder each is treated as though it were a separate well.
The top section of the dialog shows a list of the well ranges in the reservoir model. The initial
list is automatically-generated when the gridding model was created. You can choose to modify
those wells that are known by the Unstructured Gridder by choosing one of the following
options:
Add (create default range)

Select from the list of available well sections those wells to be added to the Unstructured
Gridder. For each parent well section selected, a new well range is created, extending from the
start of the first well event to the end of the last, should events (for example perforations) be
defined, or the whole length of the well, should no events be defined.
This operation may be useful if new wells have been imported into FloGrid after the gridding
model was created.
Hint On first opening this dialog, should wells be defined in FloGrid that are not present in
the gridding model, these new wells are automatically selected. You are notified of this
fact; click OK to add these wells to the gridding model. This option provides the
functionality of the Add New Wells option in previous releases of FloGrid.
Add (customized range)

Selects the parent well section. Enter a name to identify the range (useful if multiple ranges have
been generated from the same parent well), and the start and end measured depths of the range.
The dropdowns on the right can be used to initialize the start and end points.
Hint This operation may be useful to prevent the Unstructured Gridder honoring the
whole well, which may cause problems with intersecting features, when it is only
necessary to honor the region of interest.
Modify
Selects the range to be modified. You can then change the name and end points of the range.
Delete
Selects the ranges to be deleted. Each is removed from the gridding model.
Caution Do not delete a well from the gridding model simply to prevent the well from
being honored by the Unstructured Gridder, as then no connection factors are
generated for this well. Instead use the Grid To Well option in the Well Controls
dialog to instruct the Unstructured Gridder not to honor the well.

LGR...
See "LGR..." on page 536.
Auto Set Controls

See "Auto set controls" on page 539.

Gridding order...
This panel controls the order in which objects are gridded. If one object is chosen to be gridded
before a second one, any points in the second object that would disrupt the first object’s points
are ignored in the gridding process.
For example, it is generally not desirable for points from the background grid to disrupt the
regions of the grid that honor the faults and wells. For this reason, the bulk is the last object to
be gridded, and only the points that do not disrupt the other objects are added to the grid.
To ensure that grid cells are centered around well locations, it is recommended that wells are
gridded before faults.
The order of objects is edited by making a selection in the left list and then using one of the
action buttons on the right to move the selection relative to the rest of the objects. It is possible
to move multiple selections as well as single selections.
Intersections...
Controls which intersections are honored during the gridding process. By default the
Unstructured Gridder attempts to improve the grid in regions where two objects intersect by
generating a local grid that honors both objects. This is not always required. By disabling the
intersection, the first object to be gridded takes precedence over the second.
The panel has two lists: enabled intersections on the left and disabled intersections on the right.
An intersection can be disabled by selecting it in the list on the left and clicking on the >> button
to move it into the other list. Alternatively, you can simply double click on the intersection.
Intersections can be enabled by moving them in the opposite direction using the << button.
At present, actions which cause the internal gridding model to be updated cause the current state
of intersections to be lost as intersections are recalculated. These actions include:
• editing the gridding boundary
• changing an object’s gridding style
• changing to and from isotropic/anisotropic gridding
• cross-section gridding.

Gridding order...
Generating a grid
The Grid menu contains grid generating options.
Generate
Generates a grid using the current settings. If a grid has already been created for the current grid,
a message warns you that the existing grid will be lost. To continue and overwrite the grid, press
OK.
Hint To preserve the settings of the current grid, create a new grid under File | Copy Model
and define the new parameters in the new model.
Note If the BLOCK property has been edited, then subsequent grid generation operations
attempt to respect your choice of block for the columnar block assignment. This can
be useful if you need to move the logical location of a fault in the grid. Note that your
choice of blocks persists until the number of cells changes. You can force a reset by
deleting the BLOCK property.
Whenever the BLOCK property has been edited it is regenerated at every subsequent
grid generation.
Options
Grid generation...
Opens the Grid Generation Option panel. These parameters apply to the overall grid.
Grid type
This option allows you to choose one of two types of grid:
• 2D PEBI
• 2D Tetrahedral.
Bulk regions
This option can be toggled on or off to specify whether or not the bulk regions are to be gridded.
When this option is disabled, the parameters in Edit | Bulk Controls | Grid to Bulk are
overridden.
Faults
This option can be toggled on or off to specify whether or not faults should be used in gridding.
When this option is disabled, the parameters in Edit | Fault Controls | Grid to Fault are
overridden.

Generating a grid
Wells
This option can be toggled on or off to specify whether or not wells should be used in gridding.
When this option is disabled, the parameters in Edit | Well Controls | Grid to Well are
overridden.
Points
This option can be toggled on or off to specify whether or not user supplied points are to be
gridded.
Clipping boundary
Cells generated outside this boundary are clipped. By default, this is the boundary of the main
bulk. Other boundaries, such as that mark user-defined bulks may also be selected as the
Clipping Boundary from the drop-down list.
Grid cross section

Creates a cross section rather than a full grid when the grid is generated. The parameters for the
cross section are defined in Edit | Cross Section. It may be useful to use Scale To Anisotropy
when creating a cross section.
Scale to anisotropy
The Unstructured Gridder performs K-orthogonal gridding by scaling the geometry with the
permeability tensor. Use this option only when areal anisotropy is important or when generating
cross section grids.
Deviate grid
Enable this option to use sloping or segmented coordinate lines when expanding the 2D grid into
3-dimensions. If disabled, vertical coordinate lines are used. See Grid | Options | Grid
Deviation for more information. This option must be enabled for LGR models if the parent grid
contains non vertical coordinate lines.
Zigzag faults vertically

This option is only available for gridding models based on Rescue models. Enable this option
to zigzag faults vertically within the grid.
Locate faults
This option, which is usually enabled, controls whether fault multipliers and fault properties
(FaceFaultIndex and MULTNUM) can be generated. It may be disabled for performance
reasons in large grids with many faults.
Renumbering algorithm
In this drop-down list you can specify the algorithm for numbering cells into an external IJK
grid for submitting to simulators.
Line sweep method

In the Line Sweep Method, unstructured domains are gathered together and numbered with
lines that sweep in I and J directions. This is the Unstructured Gridder’s default renumbering
method.

Generating a grid
Stacking method
The Stacking Method stacks unstructured domains as a direct line of cells, which can generate
a large fraction of non-neighbor connections.
Input point method

The Input Point Method numbers cells in the order the points were generated, as a one
dimensional string. This option is not recommended for general applications.
SOLVNUM method
This method creates an integer property named SOLVNUM, which contains the cell indices for
the Line Sweep method for ECLIPSE. It also reduces the size of the ECLIPSE keyword file by
generating them only for active cells. The SOLVNUM property must be exported and supplied to
ECLIPSE with the other keywords.
Note For LGR models the Grid Type is set from the Edit LGR panel and the clipping
boundary, cross-section gridding and anisotropic gridding options are not available.
Cell generation...
Opens the Cell Generation Options panel. The cell generation parameters influence the way
cells are generated.
Grid to algebraic domains

For radial, horizontal and fractured well grids, the Unstructured Gridder uses algebraically
generated cells to improve accuracy. If disabled the Unstructured Gridder does not generate
refinements inside these domains. The option is enabled by default.
Divide grid cells into domains

By default cells of the grid are sorted into sub-domains according to which object (for example
boundary, fault, well or bulk) caused them to be generated. This allows grid structure to be
exploited to give each domain an IJK structure. If this box is not checked all cells are placed in
a single domain with no structure.
Aggregate triangles which lie in a structured grid cell

This option ensures that triangles that lie in the same logical grid cell are unconditionally
aggregated regardless of the distance between their circumcenters. The option may be disabled
if a purely triangular grid is required.
Triangle center aggregation tolerance

This value is a fractional tolerance of the distance between triangle circumcenters used for
determining whether or not to aggregate the triangles into a single composite cell. The fraction
is relative to the aggregated cell length along the line of the centers.
Aggregate PEBI nodes which lie at the center of a structured grid cell
This option, not enabled by default, determines whether vertices that lie at the center of a logical
grid cell are unconditionally aggregated regardless of the distance between them.

Generating a grid
PEBI node aggregation tolerance
When the above option is enabled, this fractional tolerance of the distance between vertices of
PEBI cells is used for determining whether to aggregate them into a single vertex. The fraction
is relative to the aggregated cell length along the line of the centers.
Grid deviation...
Non-vertical faults and wells can be honored in an unstructured grid by creating sloping or
segmented coordinate lines when expanding the 2D grid into three dimensions.
For fault framework based gridding only the faults and wells with Slope To Fault or Slope to
Well options enabled in the fault and well control panels are considered when sloping the grid.
For non fault framework based gridding all faults with Grid To Fault or Grid to Well options
enabled are used to slope the grid. In this case, non-vertical faults can be imported or created as
fault polygons, or imported as fault traces defining the up- and down-thrown sides.
The deviation for each grid point is calculated on a number of horizontal planes as a Laplace
solution in which the areal positions of the faults and wells are fixed. By default two planes are
used, one above and one below the model, and simple sloping coordinate lines are generated.
Segmented coordinate lines can be generated by increasing the number of horizontal planes.
These planes are defined by dividing the full height of the model into a number of weighted
refinements, in a similar manner to the way in which geological units are refined under Edit |
Bulk Controls | Refine Unit.
Deviation refinement
Type Ctrl-n to add a refinement or Ctrl-d to delete a refinement.
Refinements may also be added by clicking on the + symbol in the right hand corner of the
panel. Weights must be greater then 0 and less than or equal to 1.
For example, for a model extending between depths of 2000m and 2500m, weights of 0.25 and
1.0 result in horizontal planes at 2000m, 2100m and 2500m.
Absolute / Relative extrapolation threshold

These options only apply when sloping to faults in non fault framework based gridding and
when sloping 2D LGRs.
In general, faults do not extend across the full height of the model. Positions are obtained on
planes above and below these objects by extrapolating from the top or bottom two fault traces.
If the input data is noisy and the two traces are vertically close then this can have the effect of
amplifying noise. The extrapolation threshold is the minimum vertical distance between two
points for which extrapolation is used. If the top (or bottom) two traces do not satisfy this limit,
a pair is formed between the top (or bottom) trace and the next trace in. If no suitable pair of
traces can be found, this point is not used for deviating the grid. The extrapolation threshold is
calculated as
Threshold = Absolute + Relative * Model_Height
For wells, extrapolation uses a representative length of the well track and the extrapolation
threshold is not used.
Projection of boundary and horizontal wells

This option controls how the grid boundary and horizontal wells are projected into 3-
dimensions.

Generating a grid
Free boundary, horizontal wells projected vertically
The slope of the boundary is allowed to follow the local slope of the grid (determined from
faults and non-horizontal wells) and horizontal wells are projected vertically.
Boundary and horizontal wells projected vertically
Boundary and horizontal wells sloping

A constant slope determined from the average slope over the whole grid is imposed on both the
boundary and horizontal wells.
Displacement calculation
This option controls when the displacements for all points in the grid are to be calculated.
Calculate during each grid generation

This specifies that the displacements are to be calculated whenever the grid is regenerated using
the same gridding controls as for the grid.
Calculate now and use for subsequent grid generation

This specifies that the displacements are to be calculated when either OK or Apply is pressed
and these displacements are used whenever the grid is regenerated. For non fault framework
based gridding it can be useful to use different gridding controls for the displacements and for
the grid by changing the controls after the displacements have been calculated. This option is
not available for LGR models.
Edit Cell Centers

Opens the Cell Center Editor for 2D PEBI grids, which allows you to make modifications to
the points used to construct the PEBI cells. Cell center editing is not normally required but it
can be used to make adjustments to the grid in complex regions where there are several close or
intersecting features. New points can also be inserted to increase the cell density in a precise
manner. Editing takes place in the 3D Viewer and a reference object must be in the view before
editing can commence. The current grid can serve as a convenient reference object but this does
not show the effect of the current set of edits until the grid is regenerated. The Cell Center
Editor can also be used to modify the points used to define the vertices of cells in 2D tetrahedral
grids.
A set of edits describes modifications to the automatically-generated points as well as new user-
defined points. Modifications, either moves or deletions, continue to be applied until they are
cleared or until the gridding controls for the particular object change significantly. Cells
generated from user-defined points are placed in an Edit Points domain, similar to the Point
Set domain created from imported points (see "Cell centers" on page 502).
The Cell Center Editor works in a similar manner to the Boundary Editor (see "Edit Menu"
on page 112). Points are displayed as small crosses: original points are white, moved points are
green, deleted points are red, and user-defined points are cyan. Three editing modes are
available: Digitize, Select/Move and Delete. The edit mode is selected by clicking on the
horizontal tool bar or from the 3D Viewer Edit menu. The initial editing mode is Select/Move.
The meanings of the edit control options –Export, Clear Edit, Reset Edit, Cancel Edit,
Commit Edit – in the context of the cell centre editor, are described below. Cell center editor
specific operations – Reset Selected Points and Merge Selected Points – are available from
the Edit | Cell Centers menu and are also described below.

Generating a grid
Digitize
User-defined points, displayed in cyan, are added by clicking the left mouse button.
Select/Move
Single points are selected by clicking with the left mouse button. Once a point is selected it is
highlighted and a description is displayed in the bottom left message area of the 3D Viewer
window. If the description is followed by text of the form “point 1 of 3” this indicates that there
are several points with the same coordinates. This happens at a corner, for example. If the mouse
is kept in the same position each successive click with the left button selects the next point in
the list.
Single points can be added to an existing selection by clicking the left mouse button with the
Shift key pressed. A point can be removed from the existing selection or added if it is not
already in the selection by clicking the left mouse button with the Ctrl key pressed. A set of
points can be selected by dragging with the center mouse button until the required points are
within the resulting rectangle. If this is done with the Ctrl key pressed points that were already
selected are deselected and points that were not selected are added to the selection. Drag select
is a convenient way of selecting several closely spaced or coincident points.
A single point can be moved by dragging with the left mouse button. Once moved, an
automatically-generated point is displayed in green, a user-defined point remains cyan. The
selected set of points can be moved either by dragging from the last select action, or more
conveniently, by moving the mouse to an area where there are no points and then, with either
Shift or Ctrl pressed, dragging with the left mouse button.
The selected set of points can be deleted by pressing the Delete (or Backspace) key.
Delete
Points are deleted by clicking with the left mouse button. Deleting an automatically-generated
point turns it red; deleting the point a second time reintroduces the point. When a user-defined
point is deleted it is removed from the list of points.
Reset Selected Points

This option, available under Edit | Cell Centers, undeletes and restores the selected set of
automatically-generated points to their original positions. User-defined points are not affected.
Merge Selected Points

This option, available under Edit | Cell Centers, calculates the average position of the selected
points and moves them all to the same location.
Export
Writes the coordinates of any user-defined points to a file. This file can then be used to import
the points as a point set (see "Cell centers" on page 502).
Clear Edit
Undeletes and restores all automatically-generated points to their original positions, and deletes
all user-defined points.
Commit Edit
The current edit operation is committed, and the Cell Center Editor is disabled. Any edits take
effect the next time the grid is generated.

Generating a grid
Info...
Simulation IJK...
The IJK cell numbering in the Unstructured Gridder is a collection of IJK based systems
around reservoir features; that is the wells, faults, and regions. Each of the features belongs to
a domain with an independent IJK numbering system.
Note This collection of IJK numbers must be mapped to a single, regular IJK grid for
ECLIPSE. This mapping is done internally by the Unstructured Gridder.
This option opens the Cell Information panel which provides a method for you to map between
a cell in simulation IJK space and the Unstructured Gridder’s IJK space.
Enter the appropriate simulation IJK numbers in the Simulation IJK area of the panel and select
Apply. The corresponding domain and IJK in the Unstructured Gridder is identified in the
lower Domain IJK area of the panel. This IJK value and domain can then be used in IJK Slice
to visualize the cell.
The requirement for the simulation grid to be regular in shape makes it necessary to create extra
cells in the simulation grid that do not correspond to data in the unstructured grid. These extra
cells are marked inactive. So it is possible to choose IJK numbers in the top part of the
Simulation IJK area of the panel that do not have corresponding domains and IJK numbers in
the unstructured grid. The message Missing Cell appears if an extra, inactive cell is chosen
from the simulation IJK numbering.
The reverse procedure is also valid. An Unstructured Gridder IJK number may be entered in
the lower Domain IJK area to find the corresponding IJK number in the Simulation IJK area.
As an alternative to entering IJK numbers, if Pick Cell is enabled then the cell can be selected
by clicking on it in the 3D Viewer. If Paint Cell is enabled then the selected cell is highlighted.
Note When the domain and IJK cell number are identified, use Grid | Volume of Interest |
Domains to limit the display to only cells in that domain. In the IJK Slice panel, select
the appropriate domain again and enter the IJK numbers you have obtained from Info
| Simulation IJK.
LGR...
See "LGR..." on page 536.
Aquifers
See "Aquifers" on page 540.
Property
See "Property" on page 542.

Generating a grid
Gridding Preferences
The Preferences menu contains the initialization controls and methods and it also allows you
to control the message display in the Unstructured Gridder.
Initial controls...
Opens the Gridding Control Initialization panel, which allows you to set how the gridding
controls are initialized when a new gridding model is created and how the controls are modified
when the Edit | Auto Set Controls option is selected.
Gridding Control Initialisation

Two initialization methods are available.
99B
For wells, a horizontal or vertical gridding style is selected using the well track and the gridding
parameters are calculated from the well radius and the distance to the nearest feature (for
example another well or a fault). Fault and bulk controls are reset to their default state and any
user-defined bulk controls are deleted. For LGR models, the 99B method is identical to the 98B
method.
98B
This method is provided for compatibility with previous versions of the program. It is the same
as the 99B method except that well gridding parameters are set to a default state and are not
determined by the well radius or the distance to other features.
Play commands
Controls how gridding controls are initialized for new gridding models when playing a
command file.
Use this initialization method

Specifies that the above method should take precedence over the method specified in the
command file. A command file generated with a previous version of the program may produce
a slightly different grid if you had not modified the initial gridding parameters.
Use initialization method specified in command file

Specifies that the method requested in the command file should take precedence. Use this option
when you want to play a command file generated with a previous version of the program and
you want an identical grid to be produced.

Message preferences...
Opens the Message Preferences panel, which controls what messages are sent to the Log
Window.
• The Message Group drop-down enables you to select what action you wish with the
following options.
• It is possible to enable or disable messages depending upon their severity (informational,
error or warning).
• Warning messages can also be promoted to error messages or error messages can be
demoted to warning messages. Error messages are reported in a panel that must be cleared
by you; warning messages are reported silently to the Log Window.

LGRs, Aquifers and Properties
for an unstructured grid Chapter 19
Introduction
You can also add, LGRS, Aquifers and Properties to an unstructured grid model. Before refining
an unstructured grid in this way you should first generate your unstructured grid. For further
information see "Generating an unstructured grid" on page 499.
• "LGR..." on page 536.
• "Aquifers" on page 540.
• "Property" on page 542.
FloGrid User Guide LGRs, Aquifers and Properties for an unstructured grid 535
Introduction
LGR...
This panel allows local grid refinements (LGRs) to be defined. An LGR definition encapsulates
an LGR name, a set of cells in the parent grid (the host cells) and a set of features to be gridded.
A LGR gridding model must be created before any LGRs can be defined. For further details on
creating an LGR model, see "Edit LGR Definition..." on page 536.
The sets of host cells for all LGRs are obtained from a special LGRIndex property. This
property is created when the LGR gridding model is created and it exists for all global cells.
Each LGR definition is assigned a unique integer value which is used to denote whether a
particular global cell is to be a host cell for that definition. The LGRIndex property can be
edited just like any other property (select Property | Edit Properties) and any changes take
effect when the LGRs are regridded.
Separate gridding controls are used for each LGR and these are created as needed. Single lists
of well, fault and bulk controls are presented for all LGRs with the well, fault or bulk name
preceded by the LGR name.
• "LGR name" on page 537.
• "LGR index" on page 537.
• "New LGR" on page 537.
• "Delete LGR" on page 537.
• "Gridding" on page 537.
• "Grid type" on page 537.
• "Layer controls" on page 518. Vertical gridding can be set independently for each LGR.
• "Automatic selection of host cells" on page 538.
• "Auto set controls" on page 539.
Edit LGR Definition...

Opens the Edit LGR Definition panel. This allows you to create a gridding model for inserting
local grid refinements (LGRs) into an existing grid. The LGR model is built over an existing
unstructured gridding model containing the parent grid. The parent model must be created first
and must be selected as the current model before creating the LGR model. The panel allows you
to select the structural framework on which the LGR model is based. This is usually be the same
as that used for the parent model but it can be different. The initial selection is the parent’s
structural framework. If the parent model is not based on a structural framework, a grid based
model can be created in which sampling is performed on the parent grid. A grid based model
cannot be created until the parent grid has been imported and the parent grid cannot be changed
once it is used by a grid based model. Only one LGR model can be created for each parent model
but any number of LGRs can be defined within it.
An LGR model is always associated with a parent gridding model. The grid is shared by the two
models but operations on the parent model act on global cells and operations on the LGR model
act on local cells. The LGR model has an independent set of gridding parameters to the parent
model. The LGR Gridding button can be used to toggle between the parent and LGR models.
536 LGRs, Aquifers and Properties for an unstructured grid FloGrid User Guide
LGR...
LGR name
Selects the LGR definition that you wish to edit. Select the New LGR option if no LGRs have
been defined.
LGR index
Displays the value used to identify host cells in the LGRIndex property.
New LGR
Opens the New LGR Definition panel, which allows you to set the LGR Name and the LGR
Index. Both the LGR Name and LGR Index must be unique and they cannot be changed once
the new definition is created.
Default bulk controls are created automatically when a new LGR is defined. can create extra
bulk regions from the Edit Bulk Controls panel.
Delete LGR
Deletes the current LGR definition. Any host cells are removed from the LGR Index property.
This change does not affect the grid until it is regenerated.
Gridding
Selects which of the LGRs are to be gridded when the Grid | Generate option is selected. All
existing LGRs are removed from the grid before new LGRs are created.
Enable all LGRs

All LGRs are gridded together.
Enable this LGR only

Only this LGR is gridded.
Hint Select this option if you want to repeatedly grid an LGR in order to optimize the
gridding parameters. Once this LGR meets your needs, the grid can be regenerated
with all LGRs enabled.
Enable another LGR only

This is used to indicate that another LGR has been selected for gridding and that this LGR is not
gridded.
Grid type
Selects one of two types of grid:
• 2D PEBI
• 3D PEBI
3D PEBI well refinements are fitted within selected cells, and as a result the outermost faces of
the outermost cells are in general not PEBI.
LGR...
If there are problems fitting the well domain using the 3D PEBI option, try increasing the
number of radial divisions to 8, the number of theta divisions to 8 and making the radial style
linear. This reduces the cell growth rate for the 3D PEBI region around a well, which results in
a lower overall size required to fit the well.
Wells
A list of all available wells is shown on the left and a list of the wells to be gridded in this LGR
is shown on the right. Wells can be moved between the two lists by either selecting and clicking
on the >> or << buttons, or simply by double-clicking on the well name. New gridding controls
are created for wells added to the LGR.
Faults
A list of all available faults is shown in the left and a list of the faults to be gridded in the LGR
is shown on the right. Faults can be moved between the two lists by either selecting and clicking
on the >> or << buttons, or simply by double-clicking on the fault name. New gridding controls
are created for faults added to the LGR.
Automatic selection of host cells

Sets how host cells are set within the LGRIndex property.
No automatic selection
Select this option if you want to edit the LGRIndex property to set the host cells manually. The
3D Viewer can be used to display a restricted set of cells, which can then be marked as host
cells with the Property Editor.
Set from well controls when LGR is gridded

Creates a set of host cells around the well track based on the outer well radius set in the well
controls. This is done at the time of gridding so that it takes into account the most recent value.
Set from well controls now

Creates a set of host cells around the well track based on the outer well radius set in the well
controls. This is done at the moment OK or Apply is pressed. Select this option if you want to
modify the automatic selection by editing the LGRIndex property or if you want to set a
different outer well radius for gridding.
Set using distance from well now

Selects all cells within a given distance of the well track.
Note 3D LGRs are restricted to a single well, and bulk cells and fault gridding are not
available. This option offers more flexibility for 3D gridding of wells than is available
with the composite 2D/3D well type ("Horz: 2D/3D (fixed spaced)" on page 507).
However, any number of 2D/3D wells can be placed within a 2D LGR, just as with any
other style of well gridding.
LGR...
Auto set controls
Partially restores the gridding controls to the state they were in when the model was created, or
to automatically set more appropriate well controls depending on well radii. Typical use would
be to create the gridding model, set well radii in the well controls and then auto set the controls.
It could also be used after importing new wells with the Auto set controls option. Care must
be taken because user data is overwritten by this option. For more details on how the controls
are set, see "Initial controls..." on page 532.
LGR...
Aquifers
For gridding purposes, a (numerical) aquifer definition encapsulates an aquifer name, a set of
unstructured grid cell faces to which the aquifer is to be connected, and a set of properties for
the aquifer cells. An aquifer may have any number of contiguous cells, of which the first cell is
connected to the reservoir. A grid must exist before an aquifer is defined in order to set the faces.
The aquifer must then be explicitly connected to the grid. Aquifer definitions persist if the grid
is regenerated but faces must be reselected.
• "Edit..." on page 540.
• "Connect..." on page 541.
Edit...
Opens the Grid Aquifers panel to show a list of the currently defined aquifers. This panel allows
you to create a new aquifer, create a new aquifer by copying an existing aquifer, edit an
existing aquifer, or delete an existing aquifer.
Aquifers are defined visually using the 3D Viewer (see "3D Viewer" on page 107). To do this,
the grid must be oriented in the 3D Viewer to display only the faces to which the aquifer is to
be connected.
Create Aquifer panel

This panel opens when you click on Create. It requests first an Aquifer Name.
Select Cells to Connect

This takes all cells visible in the 3D Viewer as the current set of cells.
Get view direction

This takes the current direction from the 3D Viewer. Alternatively, the direction can be entered
explicitly. The aquifer is connected to faces on the outside of the cell selection that have normals
within 30 degrees of the given direction.
Edit properties
Opens the Aquifer Properties panel.
Transmissibility option
Sets the method for calculating the transmissibility between the unstructured grid and the first
aquifer cell.
• Aquifer area
For the Aquifer Area option, the transmissibility is calculated from the area specified for the
first aquifer cell.
• Cell face area
For the Cell Face Area option, the transmissibility is calculated from the face area of the
corresponding unstructured grid cell.
Aquifers
Apply multiplier
If enabled, a transmissibility multiplier is applied on all faces connecting the unstructured grid
to the first aquifer cell.
Multiplier
The value of the transmissibility multiplier.
Aquifer cell properties

The properties of each aquifer cell are specified in a table.
• Type Ctrl-n to add a cell.
Cells can also be added by clicking on the + symbol in the top right corner of the table. Cell
1 connects the aquifer to the unstructured grid and it must always be specified.
• Type Ctrl-d to delete a cell.
Connect...
This option allows one or more aquifers to be connected to the grid. This must be done whenever
the grid is regenerated.
Note Aquifers cannot be defined or connected within LGR models. Global cell aquifers
must be connected in the parent model before any LGRs are defined. Any connections
between external LGR cells and the global cell aquifers are made automatically when
the LGR is gridded.
Aquifers
Property
• "Generate real..." on page 542.
• "Generate integer..." on page 542.
Generate real... and Generate integer... calculate real and integer properties, respectively,
from the property model data, for the simulation grid. Both options display a list of available
properties to be calculated. By default all properties that have not already been generated are
selected. Once generated, property values can be visualized in the 3D Viewer (see "3D Viewer"
on page 107) or exported to an ASCII file for simulation.
• "Generate face angle" on page 543.
• "Edit properties" on page 544.
• "Transmissibility multipliers" on page 544.
• "Options..." on page 545.
Generate real...
Opens the Generate Real Properties panel. It lets you select a property model or scenario,
and lets you select a set of properties for generation.
In versions prior to 2001A, transmissibilities were generated by selecting TransXYZ (or
Fracture TransXYZ) to produce cell based properties TransX, TransY, TransZ (or
Fracture TransX, Fracture TransY, Fracture TransZ) and a set of (invisible)
non-neighbor connections. A new option Trans is now available in which transmissibilities
are shown on the cell faces. This allows you to visualize and edit all transmissibilities including
non-neighbor connections. The face-based transmissibilities are converted to ECLIPSE
transmissibility and non-neighbor connection keywords on export (see "Grid keywords" on
page 808). The TransXYZ option is still available, for example if you need to inspect or edit
TransX, but is not selected by default; and it is recommended that it is not used for new
models. If the ECLIPSE transmissibility properties exist at the time of export then they are used
in preference to the face-based transmissibility. ECLIPSE transmissibilities are derived from the
face-based property and these are generated automatically (overwriting any existing property)
whenever TransXYZ is selected. Note that for input point and SOLVNUM renumbering
schemes (see "SOLVNUM method" on page 527) only non-neighbor connections are generated
and the cell based transmissibilities are not relevant and cannot be generated.
Generate integer...
Opens the Generate Integer Properties panel. It lets you select a property model or scenario,
and lets you select a set of properties for generation.
Several special integer properties are available:
BlockUnitID, PropBlockUnitID
The block unit ID is a positive or zero number used internally to identify the block unit for
sampling. BlockUnitID is concerned with sampling the structural framework to define the
grid and PropBlockUnitID is concerned with property sampling. BlockUnitID and
PropBlockUnitID are different for dual source models.
Property
UNIT, BLOCK, BUNIT, PROPUNIT, PROPBLOCK, PROPBUNIT
These properties refer to the unit, block and block unit IDs in the structural and property models.
The BLOCK property can be edited to change the block assignment used in subsequent grid
generation.
EulerCount
In the unlikely event that a corrupt grid is produced (for example, due to inappropriate gridding
parameters) this property can be used to identify the bad cells. A non-zero value indicates that
there is a problem. A warning is issued during grid generation if this property should be
generated and inspected.
SOLVNUM
This property contains cell numbers for the linear solver. It is generated automatically if the
SOLVNUM renumbering method is selected (see "Renumbering algorithm" on page 526).
FaceFaultIndex
This face-based property marks internal faces lying on faults with a positive value. For faces
associated with a single fault this value corresponds to the position of the fault in the fault
controls list. For faces associated with more than one fault a value one greater than the number
of faults is set. This property allow you to visualize where fault multipliers are applied. It is also
possible to modify transmissibilities across faults directly in the 3D Viewer by thresholding on
FaceFaultIndex and editing the face-based Trans property. The locate faults option must
be enabled if FaultFaceIndex is to be generated (see "Faults" on page 512).
MultNum
This property identifies cells on either side of faults with values derived from the structural
framework block unit IDs (as used for the BUNIT property). The actual values used are 1 +
block unit ID at the faults and 1 + maximum block unit ID for all other cells. By exporting this
property and the MULTREGT keyword you can define transmissibility multipliers that can be
changed outside of FloGrid (see "Write MULTREGT" on page 810 and "Transmissibility
multipliers" on page 544). You can edit the property to make small adjustments to the faces to
which the multipliers are applied or you can define completely new regions between which new
multipliers can be specified. The locate faults option must be enabled for this property to be
generated (see "Faults" on page 512).
ColumnID
This property has a unique value on each column of cells in the grid.
VirtualIJKIndices
Selecting this option creates three properties VirtualIIndex, VirtualJIndex and VirtualKIndex,
which take the values of the I, J and K indices used to slice the global domain.
Generate face angle

Creates or updates the face-based FaceAngle property in which each face in the current cell
selection in the 3D Viewer is assigned a value given by the angle between the face normal and
the current view direction. By thresholding on this property you can select a suitable set of faces
for editing face-based transmissibilities. Faces at the front of the cell selection have angles in
the range 0° to 90° and faces at the back have angles at 90° to 180°.
Property
All Faces
Generates the FaceAngle property with internal faces having values in the range 0° to 90°.
External Faces
Generates the FaceAngle property with internal faces set to a value of 360°. By suitable
thresholding in the range 0° to 90° this allows you to select only the front faces and not any of
the parallel faces between cells further back in the selection.
Edit properties
Opens the Simulation Property Editor panel which allows properties to be edited explicitly.
For more information see "Simulation Property Editor panel" on page 436.
Transmissibility multipliers
Note There are three approaches for defining transmissibility multipliers on unstructured
grids. The first approach is to apply a multiplier at a fault (see "Transmissibility
multiplier" on page 513). The second approach is to set a multiplier to a selected set of
faces, as described by the remainder of this section. The third approach, which is also
the most flexible, is to use ECLIPSE keywords MULTNUM and MULTREGT (see
"MultNum" on page 543 and "Transmissibility multipliers" on page 544). Using this
approach you can assign a multiplier to the boundary between any pair of regions. You
can perform this without needing to return to FloGrid, as the multipliers are applied
directly in the simulator. Hence, we recommend this approach in preference to the first
two.
This opens the Transmissibility Multiplier panel to show a list of previously set transmissibility
multiplier definitions. A transmissibility multiplier definition encapsulates a name, a set of
faces, and a value for the multiplier. The panel allows you to create a new definition, create a
new definition by copying an existing definition, edit an existing definition, or delete an existing
definition. If several multipliers are specified on the same face the effects are cumulative.
Transmissibility multiplier definitions persist if the grid is regenerated but the faces must be
reselected.
Note The transmissibility property (Trans) must be regenerated whenever changes are
made to transmissibility multipliers.
The set of faces for a transmissibility definition is set visually using the "3D Viewer" on
page 107. To do this, the grid must be orientated in the 3D Viewer to display only the faces to
which the multiplier is to be applied.
Select cells
Takes all cells visible in the 3D Viewer as the current set of cells.
Get view direction

Takes the current direction from the 3D Viewer. Alternatively, the direction can be entered
explicitly. The set of faces is calculated from cell faces on the outside of the cell selection that
have normals within 30 degrees of the given direction.
Property
Transmissibility multiplier
Sets the value of the multiplier.
Options...
Opens the Property Generation Options panel.
Pinchout folder
Minimum pore volume
Here you can set the minimum pore volume as a number or select a minimum pore volume
property which can vary from cell to cell. If a cell pore volume is smaller than the limit for that
cell, the pore volume is set to zero.
If you type in a number, you specify a single value to be used across the whole model. If you
select a property name from the drop-down, then the values in that property for a given cell
define the minimum pore volume for that cell. When you click on Apply or OK the property is
created if it does not already exist. It has a uniform value across the whole grid. You can then
edit that property using the Simulation Property Editor (see "Edit properties" on page 544).
This enables you to vary the minimum pore volume criteria by unit or k-layer for example. You
are offered the property name MinPoreVolume by default, but you can type in other names
to create alternative minimum pore volume properties.
Connect cells across removed cells

If this option is enabled, cells that have been removed because of the pore volume limit are
connected (subject to the connection porosity and permeability limits) by non-neighbor
connections. These are created by connecting the two cells with the highest face areas.
Pinch-out thickness limit

Here you can set the minimum pinch-out thickness as a number or select a minimum pinch-out
thickness property that can vary from cell to cell. If a cell thickness is smaller than the limit for
that cell, the pore volume is set to zero. You create and edit the pinchout thickness property in
the same fashion as the minimum pore volume property (see above).
Connect cells across removed cells

If this option is enabled, cells that have been removed because of the pinch-out thickness limit
are connected (subject to the connection porosity and permeability limits) by non-neighbor
connections. These are created by connecting the two cells with the highest face areas.
Aggregate pore volume from removed cells

You have five options for dealing with the pore volume of cells whose pore volume has been set
to zero due to minimum pore volume or thickness criteria:
• Discard,
• Above,
• Below,
• Largest, and
• Smallest.
Property
The 2001A behavior was to discard the pore volume. The remaining four options describe to
which neighbor in the same I J column of cells the removed pore volume is added. If the
immediate neighbor is also pinched out, then the volume is added to nearest non-pinched out
neighbor. Thus Above adds the pore volume to the first non-pinched out cell above the cell,
Below adds it to the first non-pinched out cell below the cell, Largest adds it to the larger of
the neighbors above and below, and Smallest adds it to the smaller of the neighbors above and
below.
Connection porosity limit

The connections across cells removed by the minimum pore volume limit or by the pinchout
limit are not made if the porosity of the removed cells fall below this limit.
Connection permeability limit

The connections across cells removed by the minimum pore volume limit or by the pinchout
limit is not made if the x, y, or z permeabilities of the removed cells fall below this limit.
Trans and Perm folder

Dual system
This drop-down box controls the dual porosity/permeability option for simulating highly
fractured reservoirs. It affects the calculation of well connection factors and the default set of
properties to be exported under File | Export GRID | EDIT | REGIONS Keywords.
No dual properties
If set to No Dual Properties, fracture cell properties are not used.
Dual Porosity
If set to Dual Porosity, flow takes place between neighboring fracture cells and between
corresponding fracture and matrix cells.
Dual Porosity/Permeability
If set to Dual Porosity/Permeability, flow can also take place between neighboring matrix
cells.
Fracture cell properties (Fracture Porosity, Fracture PoreVolume, Fracture
Perm, Fracture TransXYZ) can be generated from Properties | Generate Real,
regardless of the Dual System setting, provided that Fracture Porosity and Fracture
Perm (or Fracture PermX, Fracture PermY, Fracture PermZ) exist in the
underlying property model. Fracture cell properties must be generated before calculating well
connections, or before property export, if Dual System is set to Dual Porosity or Dual
Porosity / Permeability.
To use dual porosity/permeability in an ECLIPSE simulation, the number of layers entered in
item 3 of the DIMENS keyword in the RUNSPEC section must be twice the number of actual
layers in the grid; the value given for NZ at the top of exported GRID section must be doubled.
Fracture cell properties are written in the second half of this virtual grid, in the way expected by
ECLIPSE.
For further information see "Converting old dual porosity files command files" on page 811.
Property
Multi-point flux
This drop-down box controls the calculation of coefficients for simulations based on multi-point
fluxes, in which the flow across a cell face is a function of more than two pressure values.
None
If set to None, only standard two-point transmissibilities are generated.
O-Method
If set to O-Method, multi-point flux transmissibilities are also generated for any faces
containing a K-orthogonality error above a user-specified limit. The integer property MPFANUM
can be used to restrict the multi-point flux calculation to part of the grid. If the property exists,
multi-point flux transmissibilities are only generated if the values for the cells on both sides of
a face are greater than 0. If the property does not exist, the calculation is applied over the whole
grid.
Both two-point and multi-point transmissibilities are generated when the TransXYZ property
is selected from Property | Generate Real. It is necessary to regenerate TransXYZ whenever
the multi-point flux option or the MPFA ortho error limit changes. Multi-point transmissibilities
can be exported in the standard way from File | Export GRID | EDIT | REGIONS Keywords,
under control of the Write MPF NNCs check box, and are written with the keyword MPFNNC.
When multi-point transmissibilities are generated, the face-based transmissibility property is
displayed as zero for those faces.
MPFA ortho error limit

Sets the K-orthogonality error limit for the O-Method multi-point flux option.
Permeability directions (tensor permeability handling)

Controls the interpretation of the directions of the cell properties PermX, PermY and PermZ.
The flexibility provided in this option enables handling any symmetric positive definite tensor
permeability description. A positive definite tensor can be transformed into a diagonal tensor in
its principal directions, which are mutually orthogonal. Simulation cell PermX, PermY and
PermZ are taken to be values in these principal directions. This option enables you to define
the principal directions, which may vary spatially.
Along XYZ
Directions of PermX, PermY and PermZ are taken to be in X, Y and Z directions, respectively.
Along strata
The directions of PermX and PermY are on a plane along the strata, implied by the direction
of PermZ. The direction of PermZ is taken to be in the direction of the average of the normals
of the top and bottom faces of the simulation cell. The direction of PermX is on a vertical plane
through the x-axis.
Along strata and permX

The directions of PermX and PermY are on a plane along the strata, implied by the direction
of PermZ. The direction of PermZ is taken to be in the direction of the average of the normals
of the top and bottom faces of the simulation cell. The angle between a vertical plane through
the direction of PermX and a vertical plane through the x-axis is given by the value of the cell
property PermxAngle. PermxAngle is in degrees and is measured clockwise from the x-
axis.
Property
Dip and azimuth
The plane on which PermX and PermY sit is defined by the cell property values
AzimuthAngle and DipAngle. The line of intersection between the X Y plane and the
PermX-PermY plane is known as the strike. The angle between the strike and the x-axis is the
AzimuthAngle. The angle between the X Y plane and the PermX-PermY plane is the
DipAngle. The AzimuthAngle is measured clockwise from the x-axis and both angles are
in degrees. The direction of PermZ is orthogonal to the PermX-PermY plane. The direction of
PermX is on a vertical plane through the x-axis.
Dip, Azimuth and PermX

The plane on which PermX and PermY sit is defined by the cell property values
AzimuthAngle and DipAngle. The line of intersection between the X Y plane and the
PermX-PermY plane is known as the strike. The angle between the strike and the x-axis is the
AzimuthAngle. The angle between the X Y plane and the PermX-PermY plane is the
DipAngle. The AzimuthAngle is measured clockwise from the x-axis and both angles are
in degrees. The direction of PermZ is orthogonal to the PermX-PermY plane. The angle
between a vertical plane through the direction of PermX and a vertical plane through the x-axis
is given by the value of the cell property PermxAngle. PermxAngle is in degrees and is
measured clockwise from the x-axis.
Cell properties PermxAngle, AzimuthAngle and DipAngle can be specified using maps
or using the Property Edit dialog.
Upscaling folder
Sample zero outside model
Zero is returned when sampling properties outside of the valid extent of the property model.
Upscale
If this option is enabled, then the methods specified in the next four drop-downs can be used to
upscale the fine scale data.
• Porosity upscale method
• Permeability upscale method
• Other real properties upscale method
• Integer properties upscale method
If it is not enabled, then these properties are generated by sampling the property model at the
center of each simulation cell. Derived properties such as Transmissibility and PORV are
calculated after the upscaling process using the upscaled grid cell property values.
The algorithms for each upscaling method are described in "Upscaling non-dimensional real
properties" on page 468 and in the following sections.
Note The Unstructured Gridder generates the fine grid within each cell using a different
method from that used in the Structured Gridder, see "LGRs, Resizing, Aquifers and
NNCs" on page 407.
Property
The fine grid for each unstructured cell follows the block-unit grid within the property model.
Those block-unit grid cells that fall within the simulation cell are included in the fine grid. When
calculating which block-unit grid cells are contained in the simulation cell, for 2.5D simulation
grid cells, the upper and lower surface of the simulation cell are assumed to follow the block-
unit grid layering. The side faces of 2.5D simulation grid cells, and all 3D simulation grid cell
faces are assumed to be planar.
Different properties may be defined on different block-unit grids. The calculation of the fine
grid for a cell may therefore have to be repeated for different properties during the generation
of all upscaleable properties.
Porosity upscale method

You can choose between
• Volume weighted arithmetic average (default)
• Cell center sampling
The second option effectively turns off upscaling for porosity. By choosing Cell center
sampling for one or more of the four property groups you can individually control which
properties are upscaled.
Permeability upscale method

You can choose between five algebraic upscaling methods for absolute permeability within the
Unstructured Gridder. The Cell Center Sampling option is also available.
• Harmonic-arithmetic upscaling (default)
• Volume weighted Arithmetic average
• Volume weighted Geometric average
• Volume weighted Harmonic average
• Arithmetic-harmonic upscaling.
Other real properties upscale method

You can choose between six algebraic upscaling methods, or cell center sampling.
The upscaling methods are unweighted and volume weighted versions of:
• Arithmetic average
• Geometric average
• Harmonic average
The unweighted versions take no account of the relative size of cells within the fine grid
generated on each simulation cell when forming the average values.
Integer properties upscale method

Three integer property upscaling methods are available:
• Cell center sampling
• Volume weighted mode
• Unweighted mode.
Property
Properties that are known to be integer quantities may be upscaled using the histogram method.
The value from the geological model with the largest volume within the simulation cell is
chosen. The unweighted version chooses the value with the largest number of fine grid cells
within the simulation cell.
Property
Fault Property Calculator
Chapter 20
Introduction
The Fault Property Calculator allows you to systematically calculate fluid flow
properties and sealing potential for faults in a geocellular model. Its technical basis is described
in "Fault Property Calculator - technical background" on page 559.
The method uses geologic parameters present in or calculable from a geocellular model such as
fault displacements and the lithologies on both sides of the fault, to estimate fault zone
thickness, permeability, and sealing potential using a limited set of global parameters for sets of
similar faults. From the fault’s permeability and thickness, transmissibility multipliers are
calculated for each cell that lies adjacent to a fault. These properties can be exported as
ECLIPSE keywords.
Caution The calculation of derived transmissibility multipliers is designed for normal I, J

or zig-zag faults only. It can be used with I J K faults to give an indication of fault
properties but the fault displacement may not be calculated accurately in these
cases.

• Calculating properties and values for Faults, see "Faults Tab" on page 553.
• Selecting values for derived multipliers, see "Derived Multiplier Folder" on page 555.
• Exporting faults, see "Fault Export folder" on page 558.
Functions
The Fault Property Calculator has the following major functions:
FloGrid User Guide Fault Property Calculator 551

Introduction
• Create data objects that are associated with each cell adjacent to a fault. These data objects
contain properties (for example, displacement, thickness, shale gouge ratio, permeability,
transmissibility multiplier) and inherit their geometry from their parent cells.
• Export fault keywords such as FAULTS, MULTFLT, THPRESFT, and transmissibility
multipliers in the form of MULTIPLY TRANX, MULTIPLY TRANY, and EDITNNC.
Assumptions
• The Fault Property Calculator assumes that you have a model that contains faults and is
populated with geological properties on a structured property grid. A structured property
grid is necessary to calculate fault displacement. You may require a lithology indicator to
be populated through the model (for example, limestone, shale, sandy shale, cemented
sandstone, etc.).
• A key property to have populated through the geocellular model is the fraction of shale in
each cell or an equivalent approximation, typically called Vshale or Vclay. Another
property necessary to run the Fault Property Calculator is the IJKFAULTNUM property,
which can be created from the Structured Gridder | Region Multipliers panel (see "LGRs,
Resizing, Aquifers and NNCs" on page 407) by generating an IJK Fault Location table.
Starting the Fault Property Calculator

You can launch the Fault Property Calculator using Tools | Fault Property Calculator…
This calculates properties for all faults in the model.
To select individual faults, you may expand the Faults node from the main tree, highlight the
desired faults and launch the Fault Property Calculator using a right-mouse click.
552 Fault Property Calculator FloGrid User Guide

Introduction
Faults Tab
This is the folder that opens when you launch the Fault Property Calculator. It contains a table
with the following columns:
Faults
Select those faults on which you wish to calculate the properties.
Hint The selection should be done with consideration of which faults were formed under
similar geologic conditions and consequently have a similar geologic basis for their
properties.
Alias
The Fault Alias that you wish to use in the exported keywords.
Note The Fault Alias should be eight characters long if the exported keywords are to be used
in ECLIPSE.
You can set fault aliases using Tools | Aliases | Faults.
Styles
For each fault, select the style of properties to assign to the fault from a drop-down list:
Default
The cross-fault grid cell transmissibility calculations are performed using the transmissibility
calculations in ECLIPSE.
Sealing
calculations in ECLIPSE, but the transmissibility multiplier for the fault (MULTFLT) is set to 0.
Constant Multiplier
calculations in ECLIPSE, but the transmissibility multiplier for the fault (MULTFLT) is set to
the user-defined constant, entered in the Trans Multiplier column.
Derived Multiplier
A geology-based cross-fault transmissibility multiplier is calculated for each pair of fault-
juxtaposed grid cells, using the parameters defined under the Derived Multiplier Tab, (see
"Derived Multiplier Folder" on page 555).

Faults Tab
Trans multiplier
You can only enter a value in this column if the Fault Style is Constant Multiplier. This
constant is the transmissibility multiplier for the entire fault and is exported as the MULTFLT
keyword.
Threshold pressure
This is the fault’s threshold pressure that is exported as the THPRESFT keyword.
Hint A quick way to set the style for all faults is to click the radio button with the required
style below the table; this changes the Styles column. Default is the default style.

Faults Tab
Derived Multiplier Folder
This folder can only be accessed if you select a Derived Multiplier fault style. There are four
tabs associated with it:
• "Thickness tab" on page 555
• "Shale tab" on page 555.
• "Perm tab" on page 556.
• "Trans tab" on page 557.
Thickness tab
This calculates the displacements and thickness for all faults selected with the Derived
Multiplier style. You should enter constants defining the relationship between fault
displacement and fault thickness. Three different calculation methods are available:
Linear thickness-displacement relation

Thickness is linearly related to displacement through a single constant value (b0) for all rock
types. This is the default option. The constant is initially set equal to 0.01 but you can modify it.
Logarithmic thickness-displacement relation

Thickness is related to displacement through a log-log relationship with a single constant value
(b0) for all rock types. The constant is initially set equal to 0.01 but you can modify it.
Lithology dependent
You enter different thickness constants (bi) for each rock type based on a lithology indicator.
You selects the Lithology Indicator for the Lithology Table from a list of available integer
FloGrid properties. When you select the Lithology Indicator, the Lithology column is
populated with all unique values of that lithology.
You can assign different thickness constant terms for each lithology in the Variable bi column
to be used in the displacement-thickness relationship. The button Set variable bi=b0 allows
you to populate the Variable bi column in the Lithology table with the constant term b0.
Performing the Calculation

• Calculate Fault Displacement and Thickness to perform the calculation.
The face-based properties Displacement_Face and Thickness_Face are created and
can be visualized in the 3D Viewer.
Shale tab
You calculate the Shale Gouge Ratio (SGR) for all faults selected with a Derived Multiplier
style. SGR is a function of the shale content of all cells that have slid past a particular location
on the fault. This property may be used later in the calculation of fault permeability.

Calculating the property
• To calculate this property, at least one of the following properties must exist for each grid
cell in the property model: V Shale , VClay or NTG. If one or more instances of these properties
is available, then you can select the appropriate one from a drop-down list. Otherwise you
must enter a Shale Content for each lithology on the Lithology table.
• Use Set Shale Content=Constant to populate the Shale Content column in the
Lithology table with the Constant term.

• Click on Calculate Shale Gouge Ratio to perform the calculation. The face-based
property of SGR_Face is created and can be visualized in the 3D Viewer.
Perm tab
You have four options for calculating the fault permeability for all faults selected with the
Derived Multiplier style. The fault permeability is required for the calculation of cross-fault
transmissibility. You should select one of the following functions for the calculation:
Lithology Table - Displacement weighted arithmetic

average
The fault permeability is calculated using the displacement-weighted arithmetic average of the
Perm Factor values entered in the Lithology table.
Lithology Table – Displacement weighted harmonic

average.
The fault permeability is calculated using the displacement -weighted harmonic average of the
Perm Factor values entered in the Lithology table.
Juxtaposition-based permeability
Each pair of lithologies that may be juxtaposed by faulting has a fault permeability taken from
the Permeability look-up table. You select the lithologies for juxtaposition from the Lithology
Indicator. The Permeability look-up table may be populated with properties derived from core,
outcrop, or other appropriate analogy. The Juxtaposition Permeability table is a symmetric
matrix; permeability values are only therefore entered on and below the matrix diagonal. When
you click on the Calculate Fault Permeability button is pressed, the upper half of the matrix
is populated.
log kf = -A1 ¥ SGR – A2 ¥ log(d) ¥ (1-SGR)A3

Fault permeability is calculated from a mathematical function that relates it to SGR and
displacement. You can modify the constants A1, A2 and A3. SGR(MAX) and D(MAX) are the
threshold shale gouge ratios and displacements. If a faulted cell face’s SGR or displacement
exceeds either of these values, then the cell face permeability is set to zero.

If you use either of the Lithology table methods for calculating fault permeability, Set Perm
Factor=Constant populates the Perm Factor column in the lithology table with the Constant
term.
If the Juxtaposition-based Permeability method is used for calculating fault permeability,
Set Perm Factor=Constant populates the lower half of the Permeability look-up table.

• Click on Calculate Fault Permeability to calculate permeability for each cell face
adjacent to a fault.
The face-based property of Permeability_Face is created and can be visualized in the 3D
Viewer.
Trans tab
From the calculated fault thickness and permeability, you can directly calculate the
transmissibility multipliers to be applied to each cell face pair that is juxtaposed across a fault.
In this way, the fault properties are explicitly dealt with in a manner that is amenable to
incorporation into an ECLIPSE simulation.
Note At least one permeability property should exist in the model before performing the
calculation.
• Select the appropriate permeability property for each direction, X, Y, and Z.

• Click on Calculate Cross Fault Transmissibility to perform the calculation.
The face-based property of TransM_Face is created and can be visualized in the 3D
Viewer.

Fault Export folder
This exports ECLIPSE keywords related to the fault geometry and properties. The exported
keywords are sent to two files, one for the GRID section keywords and another for the EDIT
sections keywords. For more details about the ECLIPSE keywords, see the "ECLIPSE
Reference Manual". The following keywords may be exported:
• FAULTS keyword to the GRID section file.
• MULTFLT keyword to the GRID section file.
• THPRESFT keyword to the GRID section file.
• Cell to cell transmissibility multipliers to the EDIT section file. The MULTIPLY keyword
is used in conjunction with TRANX and TRANY.
• EDITNNC keyword to the EDIT section file.
Note The THPRESFT keyword is not available in ECLIPSE 300.

Fault Export folder
Fault Property Calculator - technical background
Overview
The Fault Property Calculator module allows you to systematically calculate fluid flow
properties and sealing potential for faults in a geocellular model. The module uses geologic
parameters present in or calculable from a geocellular model such as fault displacements and
the rock types on both sides of the fault to estimate fault zone thickness, permeability, and
sealing potential using a limited set of global parameters for sets of similar faults. From the fault
zone permeability and thickness, transmissibility multipliers are calculated for each cell that lies
adjacent to a fault. The Fault Property Calculator module also enables you to assign basic
properties to a fault such as a uniform transmissibility multiplier and threshold pressure. Fault
properties can be visualized in the 3D Viewer and exported as keywords for use in the
ECLIPSE simulator.
This section contains technical background information on:
• "Fault Property Calculator workflow" on page 559.
• "Fault Property Calculator – Faults tab" on page 560.
• "Fault Property Calculator – Derived Multiplier tab" on page 561.
• "Fault Property Calculator – Fault Export tab" on page 567.
Fault Property Calculator workflow

The first step of the workflow is for you to select a set of faults on which to calculate properties.
The selection should be done with consideration of which faults were formed under similar
geologic conditions and consequently have a similar geologic basis for their properties. Fisher
and Knipe ([Ref. 12]) proposed one classification scheme that uses the shale content of the host
rocks and lithification state at the time of faulting. Other factors affecting which faults to include
in a set might include the geologic conditions during and after the time of faulting (stress state,
temperature, hydrothermal fluids, etc.), the type of faulting (normal, reverse, strike-slip, or
combination), and whether the faults have experienced a complex motion history with multiple
episodes of displacement under different conditions. Based on each fault’s geologic history, you
define a fault style: default, sealing, partially sealing, or variably sealing along its length. You
may also specify the threshold pressure that the fault can maintain before it permits flow to
occur.
If you have identified any faults as variably sealing, then the fault transmissibility must be
calculated. You define the parameters that relate the fault thickness to other geologic variables,
such as fault displacement and lithologies of the rock units cut by the fault. Once these
parameters are defined, the Fault Property Calculator calculates fault displacement and
thickness for each fault-adjacent grid cell face using the structured grid and the user-defined
thickness-displacement relationship. You may visualize the calculated displacement and
thickness in the 3D Viewer. A visual examination of the displacement of units on a fault plane
(that is, an Allan diagram) helps you validate framework geometries.

The next step of the workflow for calculating properties of variably sealing faults is to calculate
proxy-properties (for example, shale gouge ratio) along the fault plane that is used to estimate
fluid flow properties. You select the property stored in the structural grid that quantifies the
shale content in each grid cell. The Fault Property Calculator uses this property and the fault
displacement to calculate the shale gouge ratio for each fault-adjacent grid cell face. You can
visualize the calculated shale gouge ratio in the 3D Viewer. Visualization helps you identify
which parts of the fault are more likely to act as significant seals or baffles and which are likely
to permit flow.
You then select the parameters that relate the fault’s permeability to displacement, lithologies,
and proxy-properties (for example the shale gouge ratio). This is the most complex relationship
as many factors in the geologic history of a fault may give rise to its fluid flow properties. You
may choose to calculate the permeability as a function of the displacement-weighted rock
properties of the cells that have moved past a particular location on the fault, construct a
permeability table that assigns a permeability to each distinct rock type juxtaposition, or use a
simple equation with modifiable constant terms. The Fault Property Calculator calculates the
permeability perpendicular to the fault zone based on the selected approach. The fault’s
permeability and thickness are then used to calculate the transmissibility multipliers for each
fault-adjacent grid cell. Properties calculated for each fault-adjacent cell faces may be
visualized in the 3D Viewer.
The last step of the workflow is to export the calculated fault properties to files that can be
included in an ECLIPSE simulation deck. You can export two files, one file with fault
information for the GRID section and one file for the EDIT section. The GRID section file
contains the FAULTS, MULTFLT, and THPRESFT keywords defining geometry and properties
of the fault. The EDIT section contains the MULTIPLY keyword modifying the TRANX and
TRANY keywords for normally connected, fault-adjacent cells and the EDITNNC keyword
modifying the transmissibility for non-neighbor fault-adjacent cells.
Note An EDIT section is only required if fault transmissibility multipliers are calculated.
After completing the workflow for a set of faults that formed under similar conditions, you may
chose to select a separate set of faults for property calculation. The workflow is repeated for
these faults.
Fault Property Calculator – Faults tab

On the Faults tab, you can assign one of four different approaches to calculating the properties
of the faults in the model: Default, Sealing, Constant or Derived. You can also assign a
threshold pressure that must be exceeded for flow to occur across a fault. This threshold
pressure corresponds to the THPRESFT keyword.
• Default leaves the calculation of transmissibility across the fault to ECLIPSE using the
permeabilities of the adjacent grid cells and information about their geometry and overlap.
See "Transmissibility Calculations" in the "ECLIPSE Technical Description" for further
information.
• Sealing sets the keyword MULTFLT equal to 0 for the fault, allowing no flow to cross the
fault. This option is available for I, J, zigzag faults, and IJK faults.
• Constant assigns a single value to MULTFLT for the entire fault plane. This option is
available for I, J, zigzag faults, and IJK faults.

• Derived calculates geology-based transmissibility multipliers for all cells adjacent to the
fault. These multipliers are based on the thickness and permeability of the fault zone, which
are calculated by the Fault Property Calculator module. This option is available for I, J,
and zigzag faults, but not to IJK faults
Fault Property Calculator – Derived Multiplier tab

Fault Displacement and Thickness
The calculations within the Fault Property Calculator rely on an existing structured simulation
grid. An IJK Fault Location table must exist for the model. It can be automatically generated
under Structured Gridder | Region Multipliers.
The fault displacement calculation determines which cells have been offset across a fault and
calculates the distance between the cell face centers across the fault. Displacement on a cell face
is determined by finding the distance to the corresponding cell face on the opposite side of the
fault. For a structured grid without any K faults, the corresponding cells are Cell (I, J, K) and
Cell (I+1,J,K) for an I fault, and Cell (I, J, K) and Cell(I,J+1,K) for a J fault. The displacement
magnitude across the a fault between cell A and cell B is
2 2 2
d AB = ( xA – xB ) + ( yA – yB ) + ( zA – zB ) [EQ 20.1]
where (xA, yA, zA) are the coordinates of the face center on cell A adjacent to the fault and (xB,
yB, zB) are the coordinates of the face center on cell B adjacent to the fault. The face center on
a grid cell is calculated as the average location of the four corners of the face:
x A1 + x A2 + x A3 + x A4 y A1 + y A2 + y A3 + y A4 z A1 + z A2 + z A3 + z A4⎞
( x A ,y A ,z A ) = ⎛⎝ ---------------------------------------------------
- ,---------------------------------------------------- ,--------------------------------------------------
⎠ [EQ 20.2]
4 4 4
In several of the calculations described below, it is necessary to calculate the displacement-

weighted contribution of each cell that been displaced against a particular cell face. In this
approach, each cell displaced past a cell face contributes to the structure and properties of the
fault zone.
An example of the algorithm for determining the component weightings across an I fault is
described below. Consider Cell (I, J, K1) whose face center is juxtaposed against Cell(I+1,J,K2)
as shown in Figure 20.1. In the algorithm, hK,I is the apparent height of cell (I, J, K) measured
parallel to the fault displacement vector.

Figure 20.1 Example of determining the component weightings across an I fault
If K 1 = K2 , then the cell is self juxtaposed and the only unit contributing to properties on the I
face is unit K 1 (equal to K 2 ).
d K1 = Cell face center distance
If K1 > K2 , then the I side is up-thrown with respect to I + 1
d K1 = 0.5 × h K1, I + 1
for K = K 1 – 1 to K 2 + 1 step ( – 1 )
d K = h K, I + 1
d K2 = distance from face base Cell ( I + 1, J, K 2 ) to face center Cell ( I, J, K 1 ) .
If K1 < K2 , then the I side is down-thrown with respect to I + 1
d K1 = 0.5 × h K1, I + 1
for K = K 1 + 1 to K 2 – 1 step ( 1 ) step (1)
d K = h K, I + 1
d K2 = distance from face top Cell ( I + 1, J, K 2 ) to face center Cell ( I, J, K 1 ) .
Fault Thickness
Outcrop studies of faults reveal that there is a relationship between fault displacement and fault
thickness. Depending on the scale of observation, this relationship may be linear:
tf = b0 × d [EQ 20.3]
or logarithmic: log t f = b 0 × log d [EQ 20.4]

In these equations, t f is the fault thickness, d is the fault displacement, and b 0 is an empirical
constant fit to observed data, typically derived from outcrop or core. Both thickness-
displacement relations are available in the Fault Property Calculator. In actual practice, it is
best to apply a unique constant factor that is appropriate for the local field, play, or basin.
Detailed observations of faulted outcrops often reveal that the thickness of the fault zone is often
highly dependent on the mechanical strength of the rocks at the time of deformation (for
example, Foxford et al., Hull, [Ref. 13]; and Knott et al., [Ref. 26]). For example, interbedded
sands and highly ductile shales are likely to produce thinner fault zones than thick, well-lithified
sandstones. For this reason, a lithology-based “brittleness” weighting factor can be introduced
into the Fault Property Calculator’s calculation for the fault thickness. These variable bi
values are entered on the Lithology Table for each different lithology. This brittleness factor is
applied to all rock units that have slid past a given point on the fault as a weighting factor to
calculate the fault thickness. For a given location on a fault, the fault thickness is calculated as:
tf = ∑ ( bi × di ) [EQ 20.5]
i
where b i is the brittleness factor of lithologyi that has moved past the location, and d i is the
displacement-parallel apparent thickness of lithologyi that has moved past the location. The
displacement calculations on a per-cell basis are described above. Values for the brittleness of
units can be derived from empirical observations, geomechanical analogs, or estimations of
relative rock brittleness. Typically, each different lithology displaced by the fault has a distinct
brittleness weighting factor. If all weighting factors are set equal to the same value, [EQ 20.5])
reduces to [EQ 20.3]. In practice, the values used for brittleness should be those for the rock
units at the time of faulting. Figure 20.2 is a cartoon block diagram that illustrates the
calculation of the fault thickness incorporating the brittleness of the different rock types. The
fault’s thickness varies spatially because different rock units have moved past each point on the
fault plane.
Figure 20.2 Illustration of fault thickness calculation incorporating rock types brittleness

Shale Gouge Ratio
Numerous authors have published semi-quantitative approaches to predicting fault seal
behavior based on different measures of shale or clay that have slid past a particular reservoir
horizon (Fulljames et al., [Ref. 15]; Lindsay et al., [Ref. 29] Yielding et al., [Ref. 39]). In the
petroleum industry, the most commonly applied of these is the shale gouge ratio (SGR),
proposed by Yielding et al., see Figure 20.3. The value for SGR for a single cell face can be
found by summing up the effects of all other cells that have slid past that particular cell during
the fault’s displacement:
∑
V sh,i × d i
SGR = ------------------------------ [EQ 20.6]
∑ di
where V sh,i is the volume of shale (as a fraction) in grid cell i and di is the distance of the fault
transport vector that crosses unit i .
Figure 20.3 After Yielding et al, 1997
In the Fault Property Calculator, you specify which grid property corresponds to Vshale or
Vclay. If these properties do not exist within the model, it is also possible to use the Net-to-
Gross ratio for each grid cell assuming that all rock volume in a cell that is not “Net” is shale.
Alternatively, you may assign Shale Content in the Lithology Table for each lithology indicator
(for example, Rock Type or K-Index) that exists within the model.
Fault Permeability
The Fault Property Calculator provides four options for assigning the permeability to a fault:
two based on the integrated contribution of the rock types that have been transported along the
fault plane, a juxtaposition-table based approach, and a simple equation relating fault
permeability to displacement and shale gouge ratio.
The first two approaches to calculating fault permeability use a displacement weighted Perm
Factor from the Lithology Table for each fault-adjacent cell. These Perm Factors are
averaged to give the permeability at a particular location on the fault. Averaging can be either
arithmetic or harmonic, which emphasize the mean Perm Factor or the minimum Perm
Factor, respectively. If averaging is arithmetic, the fault permeability is:

∑ PermFactor i × d i
k f = ----------------------------------------------------- [EQ 20.7]
∑ di
If averaging is harmonic, fault permeability is:

d
kf = ∑ di ⁄ ∑ ----------------------------------
PermFactor i
i
[EQ 20.8]
Another approach to calculating permeability is by rock-type juxtaposition ([Ref. 12]). In this

approach, each pair of rock types juxtaposed by faulting has a distinct fault rock type and
permeability. This approach could incorporate a variety of different fault rock types including
disaggregation faults, cataclastic faults, phyllosilicate-framework faults, and clay smear faults.
Using the Permeability look-up table provided in the Fault Property Calculator, you can enter
fault rock properties derived from core and outcrop for each of the different potential rock type
juxtapositions. Because the juxtaposition permeability table is a symmetric matrix, permeability
values are only entered on and below the diagonal.
A fourth method to calculate fault permeability relies on a simple equation relating fault
permeability to displacement and shale gouge ratio (Manzocchi et al. (1999, see [Ref. 31]):[EQ 20.9]
A3
log k f = A 1 × SGR-A 2 × log ( d ) × ( 1 – SGR ) [EQ 20.10]
A 1, A 2 and A 3 are empirical constants fit to observed data, typically derived from outcrop and
core data. In actual practice, it would be best to apply constant factors that are appropriate for
the local field, play, or basin. Manzocchi et al. (1999, see [Ref. 31]) suggest values for
A 1, A 2 and A 3 of 4, 0.25, and 5 respectively. The Fault Property Calculator uses these values by
default.
In the permeability equation, the first term ( A1 ) reflects permeability loss due to shale smear
along the fault plane. The second term ( A2 ) reflects permeability reduction due to non-smearing
behavior (that is, for lithologies with low shale content). By modifying the constant terms,
appropriate relations can be obtained that treat a variety of fault behaviors. For example, if fault
permeability depends only on offset, then A1 and A 3 are set equal to zero.
Using the Grid Property Editor, it is possible to make further modifications to the fault
permeability property based on manipulations of the other face-based properties. In this way,
you may calculate fault permeability based on proprietary algorithms, increasing the flexibility
of the Fault Property Calculator module. The user-modified fault permeability is then used by
the Fault Property Calculator to calculate cell based transmissibility multipliers.
Transmissibility Multipliers
From the fault thickness and permeability, it is possible to directly calculate the transmissibility
multipliers that are to be applied to each cell face that lies adjacent to a fault. The
transmissibility multiplier equals the ratio of the transmissibility between two cells with the
fault present to the transmissibility without the fault:
T 12f
TMULT = --------
- [EQ 20.11]
T 12
In this way, the fault properties are explicitly dealt with in a manner that is amenable to
incorporation into an ECLIPSE simulation. This approach is similar to that described by
Manzocchi et al. (1999) except it takes into account intra-cell geometric factors described in the
"Transmissibility Calculations" in the "ECLIPSE Technical Description".

Figure 20.4 A schematic diagram of two cells separated by a fault
Figure 20.4 shows a schematic diagram of two cells separated by a fault. Fault thickness and
permeability are tf and kf, respectively and d1 and d2 are normal distances from the cell centers
to the center of the area of cell intersection, A. Without the fault, transmissibility between the
two blocks can be calculated using the corner point transmissibility calculation:
T 12 = TMULT × CDARCY
---------------------------------------------------- [EQ 20.12]
1 + -----
----- 1
T1 T2
where TMULT and CDARCY are defined in the "ECLIPSE Technical Description" and:
p . p
A di
T i = k i × NTG i × --------------------- [EQ 20.13]
p p
.
di di
TMULT × CDARCY [EQ 20.14]

Thetransmissibilitybetweenthetwoblockswiththefaultpresentis:T 12f = ----------------------------------------------------
--1- + --1-
T 1f T 2f
where T 1f and T 2f are the transmissibilities of each cell incorporating half of the fault thickness
and are calculated as:
T if = a i T i [EQ 20.15]
where a i is calculated by attributing half of the fault’s thickness to each cell and calculating the
harmonic average permeability across the merged cell and fault:
di
a i = --------------------------------------------- [EQ 20.16]
⎛ d – --t-f⎞ ⁄ k + --t-f ⁄ k
⎝ i 2⎠ i 2 f
---------------------------------------------
ki
which simplifies to:
tf ⎛ ki ⎞ –1
a i = 1 + ------- ---- – 1
2d i ⎝ k f ⎠
[EQ 20.17]
Combining [EQ 20.11], [EQ 20.12], [EQ 20.14], and [EQ 20.15] yields an equation for the
transmissibility multiplier between two fault-juxtaposed cells:

T1 + T2
TMULT = ------------------------------------
- [EQ 20.18]
T1 ⁄ a2 + T2 ⁄ a1
Transmissibility multipliers must be calculated for all grid cells that lie adjacent to faults. The
multipliers are applied to the cell face that is adjacent to the fault using the MULTIPLY keyword
with the TRANX and TRANY keyword for normally connected cells and the EDITNNC keyword
for the non-neighbor connections caused by the fault offset. For more details, see the TRANX,
TRANY, and EDITNNC keywords in the "ECLIPSE Reference Manual" and "Transmissibility
Calculations" in the "ECLIPSE Technical Description".
Fault Property Calculator – Fault Export tab

The last step of the Fault Property Calculator workflow is to export the calculated fault
properties to files that may be included as a part of an ECLIPSE input deck. This part of the
workflow is implemented under the Fault Export tab. Two files may be export, one file with
fault information for the GRID section and one file for the EDIT section. Fault names and IJK
extents (FAULTS keyword) and the values entered on the Faults tab for the MULTFLT and
THPRESFT keyword are exported to the GRID section file. The exported fault names are the
fault alias name, limited in ECLIPSE to eight characters. The EDIT section file contains the
MULTIPLY keyword modifying the TRANX and TRANY keywords for normally connected,
fault-adjacent cells. It also contains the EDITNNC keyword modifying the transmissibility for
non-neighbor fault-adjacent cells.
Note An EDIT section file is only required if derived fault transmissibility multipliers were
calculated.

Volumetrics
Chapter 21
Volumetrics
Introduction
The Volumetrics module is used to measure some commonly-requested volumetric
quantities (for example, Oil volume) for gridded models.
• Measuring volumetric quantities (see "Measurements" on page 570).
• Creating a report (see "Reporting options" on page 573).
• Repeating measurements (see "Volumetric run definitions" on page 574).
• Using Contact Sets (see "Using contact sets with volumetrics" on page 575).
• Performing a volumetrics run (see "Single run operation" on page 576).
• Analyzing various realizations of model (see "Multiple realization operation" on page 577).
Limitations
• Gridded models only.
FloGrid User Guide Volumetrics 569

Volumetrics
Measurements
Measurement quantities
Any combination of the following quantities can be measured.
Bulk volume
The physical volume occupied by the grid cells
Net volume
The volume occupied by permeable rock
Pore volume
The volume occupied by pores within the rock
Oil volume
The volume of oil in the pore space
Gas volume
The volume of gas in the pore space
Hydrocarbon volume
The volume of gas or oil in the pore space
How these quantities are measured

These raw data used to calculate these quantities are the properties and contact sets that are
defined for the particular grid model. In each case except Bulk Volume a volume grid property
is created for the appropriate measurement. The quantity is then measured by simply summing
the cell values.
Bulk Volume is exceptional because it is always calculated by simply summing the cell volume
property on the grid. If there is no cell volume property you must create one using the
Upscaling panel.
The property for each measurement is obtained in the following ways:
Net volume
Either use an existing net volume property directly, or calculate one by multiplying the bulk
volume by either a net-to-gross property (if one exists) or a fixed net-to-gross value.
Pore volume
Either use an existing Pore Volume property directly, or calculate one by multiplying the net
volume property (obtained as above) by either a porosity property (if one exists) or a fixed
porosity value.
570 Volumetrics FloGrid User Guide

Measurements
Oil volume
Either use an existing Oil Volume property directly, or calculate one by multiplying the pore
volume property by the oil saturation. The pore volume property is obtained as above. The oil
saturation can either be specified as an existing property, as a constant value in each cell, or left
to be calculated from the Gas and Water saturations (using the equation So = 1 – Sw – S g )
Gas volume
Calculated in a similar manner to Oil Volume - by multiplying the pore volume by the gas
saturation, which in turn can be a known property, a value or inferred from the Oil and Water
saturation data.
Hydrocarbon volume
Calculated by multiplying the Pore Volume by the Non-Water saturation. The Non-Water
saturation is deduced from either the Water saturation ( 1 – S w ) or the Oil and Gas saturations
( S 0 + S g ) , depending on which saturations are defined.
Use of Contact Sets

You can also use Contact Sets instead of or in addition to using saturation properties to define
the location and quantity of each fluid. Contact Sets allow you to specify fluid contact depths
for different areas of the reservoir. See "Contact Sets" on page 579. For more details about how
Contact Sets are used see “"Using contact sets with volumetrics" on page 575.
Using contact sets with Volumetrics

The prime method for specifying the location and quantity of each fluid within the reservoir is
by fluid saturations properties. However, realistic saturation properties are not always available
and constant saturation values may be inappropriate. In this situation you can use a Contact Set
to define depth constraints for the fluids, which modifies or defines those saturations.
Note Defined Saturations take precedence over Contact Sets. If any saturations are
defined Volumetrics uses those to define or derive any saturations it needs over the
whole model. If a Contact Set is specified in addition, it will be used to restrict those
saturations by depth. Only if no saturations are defined are the Contact Sets used to
directly define the saturations to be used in the volumetric calculations.
There are 3 cases of using Contact Sets to consider:
When no saturation properties exist

If no saturation properties are known Contact Sets provide the only way to estimate fluid
volumes.
• From the Volumetrics module you should select the Contacts folder and choose the
Contact Set to use.
When insufficient saturation properties are defined

If you want to measure a fluid volume for which no saturation property exists, and only one of
the other properties is known, a Contact Set can enable Volumetrics to separate the other
fluids.

Measurements
For example, you are trying to measure oil volume but only have a water saturation property (no
oil or gas saturation).
• On the Properties folder you would:
• Set the Water Saturation property to the correct property,
• Check the Oil Saturation property is set to Calculate....
• Check the Gas Saturation property is set to Calculate....
• On the Contacts folder you would select the Contact Set (containing an Oil contact) to use.
Note When run the Volumetrics module first calculates the Oil Saturation as being (1.0 -
the defined water saturation) for all cells in the model. This would then be truncated at
the relevant contact boundary by the Contact Set.
When sufficient saturation properties are already defined

Volumetric analysis on the fluids in a model can be performed whenever there is enough
information defined to enable the saturations of the measured fluids to be known throughout the
model. If this information is already present in the form of defined saturations, there is little
value in using a Contact Set since it probably leads to different saturations.
Note If your defined saturation properties do not have saturation depth profiles identical to
those in the Contact Set some saturation (and therefore volume) will be “lost” when
the Contact Depths are used to truncate the saturation properties. They are most
likely quite different, in which case you should consider this option carefully.
Volume of interest
You can restrict the measurement to the cells displayed in the 3D Viewer. This gives you ample
scope for analyzing volumes in individual units, blocks, rock types, lease boundaries, or
disconnected parts of the same reservoir.

Measurements
Reporting options
Report structure
The simplest type of result for any quantity is a total value. This may suffice but you may prefer
to see the result broken down into sub-totals such as geological unit or rock type, or even by
both units and blocks.
Consequently the Volumetrics module allows three levels of detail in a report:
Total
One value per measurement
Column
A column of values per measurement; one row for each value of a specified indicator property.
Table
A table of values per measurement, each row and column representing values of two indicator
properties.
Note You can use any discrete properties as indicator properties. For example, UNIT,
ROCKTYPE, SATNUM, etc.
Report units
You can select the particular units the result is to be reported in.
Rock Volume Unit

Bulk and Net volumes
Liquid Volume Unit

Pore, Oil and Hydrocarbon volumes
Gas Volume Unit

Gas volumes.
Report output
You can output the volumetrics report can be output to:
• the screen
The results are reported to the Log Window.
• a user-defined file
This file is formatted for direct import into a spreadsheet package.
The results are also automatically stored internally for analysis using the Multiple Realization
Graphics.

Reporting options
Volumetric run definitions
You may want to repeat a particular measurement to see the effect of any edits. To accommodate
this you can save your selections on the Volumetrics panel as a Volumetric Run Definition.
• You must give a name for each run definition before running.
• You can reselect particular run definition from the Volumetrics panel, if you wish to repeat
a set of measurements.
Note Volumetrics Run Definitions are stored while the program is running but are not
saved when the program is closed.
• You can also use Volumetric Run Definitions as a basis for Multiple Realization runs.

Volumetric run definitions
Using contact sets with volumetrics
Contact Sets can be used by the Volumetrics module to truncate the user-specified saturations
above/below the contact depths.
Note This means that if the contact depths within a Contact Set do not agree with the
saturation/depth pattern shown in the saturation property, that some saturation (and
therefore volume) will be lost from the calculations.
If you have no saturation properties you still need to supply some constant saturations. Normally
saturations defined this way need to add up to 1.0, but if you are using a contact set this rule can
be broken since the fluid saturations are truncated and cannot overlap.
For example, if you are interested in finding the pore-volumes in each fluid zone you should set
each of the fluid saturations to 1.0 and report the Gas volume, Oil volume, and Water
volume.
See "Contact Sets" on page 579.

Using contact sets with volumetrics
Single run operation
• To perform a volumetrics run you need to select the desired options on the panel, ensure the
run has a name (this is used as the Volumetrics Run Definition), and click the Single Run
button.
The result is written directly to the selected destination.

Single run operation
Multiple realization operation
• To analyze various realizations of a model by comparing volumetric measurements on
those realizations you must select the desired options and ensure the run has a name as for
the single run, then click the Multiple Realization button.
This opens up the Multiple Realization Volumetrics panel (see "Multiple Realizations"
on page 623).
This panel allows you to define which realizations to use and then to make volumetrics
measurements using the specified volumetrics run definition for all those realizations. In
addition to screen and file output another output option is provided here. You can plot the
totals or sub-totals for any measurement to provide an analysis of the range and distribution
across the realizations. See "Multiple Realizations for Volumetrics" on page 624.

Contact Sets
Chapter 22
Introduction
A Contact Set defines the height of particular fluid contacts within the gridded model.
They are used by the Volumetrics module to determine what proportion of each cell contains
each fluid type. They may be used instead of or in combination with saturation properties.
Fluid contacts can each be one of three types: Gas-Oil, Oil-Water and Gas-Water. Often there
is only one fluid contact in a Contact Set, but it is also possible to have both Gas-Oil and Oil-
Water contacts within a Contact Set.
FloGrid models fluid contacts by splitting the grid into regions in which the contact depth is
constant, and storing a separate contact depth for each of those regions.
The regions are defined using a special grid property ContactRegion, explained in detail later.
• Creating ContactRegion properties, see "The ContactRegion property" on page 580
• Creating contact sets, see "Defining a contact set" on page 581.
• "Displaying a contact set" on page 582.
• "Using a contact set" on page 583.
FloGrid User Guide Contact Sets 579

Introduction
The ContactRegion property
This grid property breaks the model up into regions in which any contact depths are constant.
Like other index properties (for example UNITNUM) it exists as a value for every grid cell. This
means you can edit it to ensure it matches your requirements.
This property is created automatically by FloGrid when you start to define a contact set (if it
does not already exist). FloGrid offers the following basic options as starting points:
1 Define only one contact region, spanning the entire model
2 Make each BLOCK a separate contact region
3 Open the Property Calculator so you can define it with an expression.
If these are sufficient you can continue to create the contact set, or you can re-edit the property
until satisfied.
Note There is only one ContactRegion property per model. This means that every contact
set you define on the model applies to the same contact regions. Similarly this contact
region definition is used for all fluid contact types.
This property appears on the Property node tree under the EQLNum property type, because it is
closely related to equilibration region properties used in ECLIPSE.
580 Contact Sets FloGrid User Guide

The ContactRegion property
Defining a contact set
After the ContactRegion property has been created you can define your contact set.
The Contact Sets panel has check-boxes indicating what types of fluid contact are in the
contact set, and a table in which to enter the contact depths by region number and fluid contact
type.
A Contact Set name needs to be defined. Different models may have contact sets with the
same name.
When OK or Apply is clicked on the panel FloGrid calculates grid cell properties representing
the volume fraction of each cell above the fluid contact(s). Any cells that are intersected by a
contact depth are truncated to ensure this calculation is accurate, this may take some time.
The Volume Fraction Properties are used later by the Volumetrics module. You should not
edit these, but you can view them to get an understanding of where the fluids are in the reservoir.
They appear under the Cell volume fraction property type in the Property tree.

Defining a contact set
Displaying a contact set
Contact Sets cannot be viewed directly. The simplest way is to examine the Cell volume
fraction properties.
Hint If you have gas-oil and oil-water contacts, the oil zone can be quickly picked out by
using the Property Calculator to create a new “oilzone” property equal to the above-
oil-water-fraction minus the above-oil-gas-fraction.

Displaying a contact set
Using a contact set
In the Volumetrics module you can select a Contact Set to use from the model.
The effect of using a Contact Set is to truncate fluid saturation properties at the fluid contact
boundaries.
See "Using contact sets with Volumetrics" on page 571 for further information.

Using a contact set
Using a contact set
Streamline Simulation
Chapter 23
Introduction
The Streamline Simulation module consists of two windows, the Simulation Manager
and the Simulation Setup. The Simulation Manager is for viewing graphics output from the
simulator and the management and running of queued simulation data sets.
• Setting up streamline simulations, "Simulation Setup" on page 587.
• Displaying volumetric graphics, "Simulation Manager (Volumetrics Graphics)" on
page 595.
• Loading data, setting report, display and default options, "File menu" on page 596.
• Displaying plots, "Graphics Window" on page 603.
• Managing simulations, "Management Options" on page 605.
• Generating simulator keywords, "Schedule section keyword generation" on page 611.
And technical background information on:
• Calculation of oil, gas and water volume factors and viscosities, "Black Oil correlations"
on page 613.
• Calculation of well connections factors, "Calculation of Kh and connection factor" on
page 617.
• Calculation of well connection factors for distorted cartesian grids, "Orthogonalization of
vectors" on page 620.
Overview
The Simulation Manager is opened using the button with that name at the bottom of the
Streamline Simulation window.
FloGrid User Guide Streamline Simulation 585

Introduction
The Simulation Setup window is where you enter the parameters to run the Simulator. You can
set up a simple 2 phase (oil and water) simulation in the Setup folder.
The first panel you see is the General folder, which allows setting of various items (note these
may be left unchanged in most cases). You may wish however to change the simulation file
names for the files written out to run the simulator in the Simulator File Names box.
To run a simulation, first go to the Setup folder in Simulation Setup and change some of the
default values if desired in the 2 Phase and Rates folders; all data in these folders has reasonable
defaults calculated from the size of the grid. In order for the wells to operate however it is
necessary to set which wells are injectors and which producers on the data items tree in the main
FloGrid window. Once this has been done you proceed to the Run folder to either perform a
single run or a multiple run of the simulation as described in "Running the Simulation" on
page 591.
The panels are designed so the default settings result in a simulation that runs in most cases.
However it can occur that the pressure in the reservoir requires increasing in order to get the
wells to flow (see NoData status in the Simulation Manager | Management Options table
below). In that case the pressure at the oil water contact is the relevant value to increase.
Note Wells are assumed to be open hole and fully connected to the grid, if no well events
have been defined. If a well event is detected, all the wells are shut and then the
connections are opened by applying perforation events. In this case any well that does
not have an event is shut.
586 Streamline Simulation FloGrid User Guide

Introduction
Simulation Setup
Introduction
The Simulation Setup folder is where the simulation data is entered that is used to create a file
for passing to FrontSim or ECLIPSE to run. This file is hidden from the user and need not
concern the novice.
The default model built for the simulators is 2 Phase (oil and water) with the well rates specified
at the group level. That is, wells are assigned to two groups as to whether they are producers or
injectors, and the rates specified for each group.
A more complex well control can be specified in the Advanced Features section and here well
rates are set on an individual basis. Thus, for example, a history match can be performed if
history has been imported into the Simulation Manager using Simulation Manager: Files |
Import | History Data. For this type of run it is usual to set the option on the Simulation
Manager, (Simulation Manager: Options | Well Connection Factor | Calculate), to obtain
accurate connections for the well flows from the grid.
Note In the Simulation Setup folder a command is written out reflecting the state of the
viewed folder whenever the Apply button is pressed.

• "Restored Data" on page 587.
• "Property Selections" on page 588.
• "Setup" on page 589.
• "Connection Factor Calculation" on page 592.
• "Aquifer Simulation" on page 592.
• "Setup (Advanced Features)" on page 592.
Restored Data
This box refers to the Simulation Manager module, which stores all the data for any simulation
added to it. This data can be recovered from the Simulation Manager and examined in these
panels. The Root, Grid and Prop are shortened versions of the headings in the Simulator File
Names box on the General folder. The Previous and Next buttons in the Restored Data box
also allow you to step through data in the Simulation Manager.
Note As the data to be viewed is loaded back into the folders a warning popup appears if you
have pressed the Apply button prior to requesting a reload of data. This occurs to
prevent the inadvertent loss of edited data. If the load is accepted the check is not
performed again.

Simulation Setup
Once data has been restored into the Simulation Setup it can be altered and a new simulation
created or multiple simulations created from it. Thus multiple realizations can easily be built up
on properties other than those under control of the Multiple Realizations panel such as the well
rates or oil properties.
Note After simulation data has been restored the Restored Data box becomes blank when
the Apply button is pressed. This is because at this point the panel is dealing with a new
simulation different from one that is stored in the Simulation Manager. A good way
to envisage the Simulation Setup is as an editor that copies its state out to the
Simulation Manager and may have its state copied back from the Simulation
Manager. The simulation data in the Simulation Manager cannot be edited only the
copy of it. The only exception to this is the Notes folder in the Simulation Manager
itself (see below).
Property Selections
These fields display the currently selected Flogrid Model, Contact set, Porosity and
Permeability. You can select different permutations of these for particular Single simulations.
Note All permutations are automatically selected when the Multiple Runs are performed
through the Multiple Realizations panel. However the Contact Set is not altered in
a multiple run. The contact depth taken from it is fixed throughout the multiple
realizations.
These fields are set to 'none' if there are no properties present for them. The existence of
properties is detected automatically and the panel updated with the properties present.
Hint If the panel has not automatically detected the presence of a model or property then to
refresh it with Apply.
Well information
The Simulation Setup automatically builds well information required for the simulator. If it
has failed to do so when well data is imported or altered, the window title will report that the
panels require a refresh. Click on Apply to update the panels.
General
The Simulation Title and Simulation Start Date are defaulted and you can alter them if you
wish. The simulation title appears on simulation output files. The Run folder outputs various
files to run the simulator and the names of these can be set in the Simulator File Names box:
Simulation Root
The Simulation Root is the directory location and files name without extension to be used as
the basis for all files generated, see "Running the Simulation" on page 591.

Simulation Setup
Grid Include file
This is the name of a file that FloGrid writes out with the currently selected grid as shown at the
top of the window under Flogrid Model.
Property Include file

This is the name of a file that FloGrid writes out with the currently selected properties shown at
the top of the window (Porosity, Permeability), or in the Multiple case for the permutation of
the different property sets.
Output files to generate

You have three options. First whether to write out graphics files, necessary for viewing
streamlines or properties like oil saturation on the grid. You can import these back into FloGrid
through the Simulation Manager - see "Table" on page 573. This option is switched off by
default as these file can be very large.
Hint On a large model when you have the output from multiple runs you can select one in
the Simulation Manager and reload the data (See Restore Data above). Change the
graphics output setting and run this simulation again as a single run to get graphics files
for it.
The second option sets formatted or unformatted files and the third whether the simulator should
write separate files for each time step it takes.
Below this there are some minimum pore volume specifications and some settings to run
FrontSim fast but less stable or slower and more stable.
Note The default setup is to run FrontSim with tuning such that it runs quickly. This however
makes for a less stable simulation and runs are more prone to fail or stop prematurely.
By unchecking the FAST option a much slower but more stable run can be achieved.
Setup
At the top of this folder is a statement about the current type of simulation setting in use. To the
right of this is a check box allowing the switching on of Advanced Features. These allow the
setting of individual well rates and if this is done the statement will change to indicate the
simulation is in individual well control rather than Field rate control mode.
2 Phase
Specifies the time steps and Oil and Water properties. Suitable defaults are present on start-up.
Other properties and tables required to run the simulator are generated using correlations with
these values as input, and can only be accessed in the Advanced Features.
Calculate pressure
You can use this to get an approximate default pressure for the reservoir if one is unknown.

Simulation Setup
Incompressible Frontsim Simulation
This tells the Simulation Setup to output a data set that can only run in FrontSim with
incompressible oil and water. Such a simulation is very fast and stable.
Note By default a value in the Reservoir Conditions box for Pressure @ OWC is set, but
if the Contact Set drop-down is changed at the top of the window then this default
may be inappropriate. The Calculate Pressure button recalculates it at the contact set
value.
Rates
This folder sets the rates for the Field of wells as a whole. Individual well rates are under the
control of the simulator to match these settings. The required input is the third field (Produced
Oil Rate from Reservoir). Initially the default is obtained by calculating the volume of oil in
the reservoir given the oil-water contact specified in the 2 Phase folder, the volume is
multiplied by the first field (Produced Oil Fraction of Reservoir) and this volume is entered
into the third field. If you click on Compute Rates then this process is performed on the current
settings.
RUN
There are two options on the panel called Single and Multiple, referring to whether you wish
to submit multiple simulations under FloGrid control or to manually construct the simulations.
Single
There are two boxes enclosing buttons that must be used in a single simulation case:
• Simulator Sections to Write
• Running the Simulation
Simulator Sections to Write

The check boxes refer to the files to write with the Simulation Root as specified in the General
folder, see "General" on page 588.
For example, given a root file name of FRONTSIM, the following files are generated when the
Write Sections button is used:
FRONTSIM.DATA contains the dimensions and phases etc.

FRONTSIM_GRID.INC the grid geometry data from FloGrid
FRONTSIM_PROP.INC the properties from FloGrid
FRONTSIM_PVT.INC the PVT properties from the Simulation Setup panel.
FRONTSIM_SCAL.INC the saturation data from the Simulation Setup panel.
FRONTSIM_SCH.INC the well data from the Simulation Setup panel.
FRONTSIM_SOL.INC equilibrium data from the Simulation Setup panel.
FRONTSIM_SUM.INC a list of summary properties (currently unused).

Simulation Setup
Use the check boxes to write these out. This allows you to have alternative versions on disk with
their own properties. You can write out only those sections you wish to change and reuse the
files from a previous run.
If aquifers are detected then extra files are present. The extra files depend on the type of aquifer
present. The files are:
FRONTSIM_GRID_AQU.INC
FRONTSIM_SOL_AQU.INC
Note The Simulation Root file with the extension DATA is always written as it contains the
names of the other files within it, which may have changed.
Running the Simulation

You can use the Add Simulation button to add simulations to the Simulation Manager, the
data for these are stored and can be recovered using the table (column 1/magenta selection) in
the Simulation Manager (see "Simulation Setup" on page 587).
Below these are two include options which can pick up files created in the Fault Property
Calculator - see "Fault Property Calculator" on page 551.
Multiple
Creating and Running a Multiple Simulation
Use the button Multiple Realizations... to open the Multiple Realizations option (see
"Multiple Realizations" on page 623). You can generate multiple realizations from there and
they start running automatically in the Simulation Manager.
Note When the multiple runs are generated the Simulation Root has an '_' and the number
of the case appended to the root name for each of the realizations that are automatically
generated. These files can be seen in the Simulation Manager.
Using an Existing Simulation File

If the Simulation Root file (.DATA) already exists on disk, there is an option on the Multiple
folder to use it for the data set rather then the files being generated from the Simulation Setup.
In this case the Simulation Root file is copied to a file with the '_n' and only the Grid and
Property files are overwritten for each run.
If the option on the General folder on the Simulation Setup panel is set to ‘Simulation File
Names set equal to FloGrid Model name’ then the copy is taken from a file with the name
equal to the FloGrid Model name (which may change if there is more than one) and the file
copied to has the name of the FloGrid Model with the ‘_n’ added to that.

Simulation Setup
Connection Factor Calculation
If the Simulation Manager: Options | Well Connection Factor | Calculate option is used
(this setting can be made the default by setting WELL_CONNECTION_FACTOR to TRUE in
the config file) then the connection factors are calculated from the Peaceman formula as
specified in the Calculation of Kh and connection factor section, which takes into account
the direction of the well and partial penetration. The following simplifications apply:
• there is only one diameter and skin for a particular connection factor calculation
• the diameter and skin is the value from the last event in the time step within cell
• net to gross is not used.
In FloGrid 2003A_1 and later versions, the calculation of the connection factor has been
improved for distorted cartesian grids. You can choose the method for defining the directions in
which PERMX, PERMY and PERMZ arrays are to be interpreted. The algorithm is described in
"Calculation of Kh and connection factor" on page 617.
Aquifer Simulation
If aquifers have been created in FloGrid (see "Aquifer Data" on page 405) then all active
aquifers for a given model will be attached to the appropriate simulation.
Setup (Advanced Features)

When the Advanced Features check box is used, five more folders become available and the
2 Phase folder is disabled. You can now simulate gas as well as water and oil together with
time-varying wells, which may have historical rates imported for history matching.
Hint Its a good idea to set the time steps in the 2 Phase folder before going on to the
advanced folders. This is because although the time steps can be edited in the advanced
Wells | General (+History) folder, they can only be created one at a time. This could
be a slow process if you have many time steps. Setting them in advance makes things
easier in the Advanced Wells folder.
The advanced folders are:
Wells
Prediction
These rates are the reservoir rates produced/injected for the well. Filling in a value for a well in
the Oil, Water or Gas column specifies that well as a producer, and overrides the setting in the
data tree. Similarly for InjWat and InjGas, which specify injection.

Simulation Setup
Note You can use the Quick Set function below the well table to quickly set a constant value
into different cells, use BHP or RESV (case insensitive) for the Mode column or
OPEN/SHUT for the state. Fill in a value and then click on the cell into which you
want the value to be entered.
Alternatively entire columns or parts thereof can be set by clicking on them when the
other check boxes are used. The most useful feature of this is when you can identify
the injector and producer wells through a naming convention. Then all the wells
matching a given string can be set by clicking on a column. Use the ‘not’ operator (an
exclamation mark: ‘!’) in front of a Wells Matching Expression to match all the wells
that do not satisfy the rest of the expression.
General (+History)
Allows detailed editing of the wells possibly created in the Prediction folder or for a history
matching simulation to be set up if history has been imported into the Simulation Manager
(File | Import | History Data). With the history data present, click on the Map History button
at the bottom left of the panel to fill in the data for the wells on the specified time steps.
The Type column in a history match case is set to H to indicate that WCONHIST keywords will
be exported to the Simulator. The table can be edited to change these to P, in which case a
WCONPROD keyword is exported. For injectors the keyword is always WCONINJE. The table
always sets all to H prior to an edited date and all to P after that date automatically.
You can edit the time steps in detail here. Note that the date at the top right of this folder is the
date range for the selected time step in the Days column.
Filling in a value for a well in the Oil, Water or Gas column specifies that well as a producer
and overrides the setting in the data tree, similarly for InjWat and InjGas which specify
injection. Thus it is possible to switch a single well between production and injection through
time.
Note In the third table the connections listed are those which apply on the date selected in
the middle table. The dates on which the connections apply is indicated above this
table. This table should only be edited for single simulation runs and is only for
viewing in the multiple runs case. This is because the multiple runs case needs to
recalculate all data when setting up each of the multiple runs.
Note For history matching when historical data has been imported and mapped onto the
wells, it is advisable to set Simulation Manager: Options | Well Connection Factor
| Calculate to ON. This gives more realistic connections of the wells to the grid,
particularly in deviated wells, and therefore a better result for history matching.
Phases
Changes the phases present. Notice that when Dissolved Gas is selected the option to specify
an amount of dissolved gas is removed. This is because the dissolved gas ratio is then generated
from the tables in the PVT folder.

Simulation Setup
Initial
Details the initial equilibrium conditions of the reservoir. The pressure in the first field must be
specified at the Datum Depth or one of the contact depths depending on the phases selected in
the Phases folder. The depth that the pressure should be for is the first enabled depth in the
folder.
PVT
Details the Surface and Reservoir properties. It also allows examination of the properties
generated through the correlations and the variation of the oil properties through variation of F1
to F7 (FO1 to FO7 in "Black Oil correlations" on page 613).
Click on Apply to update this table. This calculates the table entries from the correlations taking
into account the settings on the other folders (density, phases present, etc.)
SCAL
Allows detailed control over the saturation functions. The folders present depend on the phases
selected in the Phases folder.
Click on Apply to update this table to use correlations to determine more realistic relative
permeability curves.
Hint The settings in these tables can be reset to their simple 2 Phase values by switching
off the Advanced Features followed by clicking on Apply on the 2 Phase and
Rates folders.
Note A particular Advanced folder ill only update the advanced settings when the Apply
button is clicked on that particular advanced folder. Otherwise that part of the model
remains with its simple 2 Phase values.

Simulation Setup
Simulation Manager (Volumetrics Graphics)
• The left of the panel contains the simulation and graphics Management Options
• The right of the panel shows the Graphics window.
The module has two modes, shown in the title bar: you can switch mode in the Display Mode
menu item with options Simulation (title: Simulation Manager) and Volumetrics (title:
Volumetrics Graphics).

Simulation Manager (Volumetrics Graphics)
File menu
• "External" on page 596.
• "Export" on page 597.
• "View" on page 597.
• "History" on page 597.
• "Display Mode" on page 597.
• "Group" on page 598.
• "Options" on page 600.
• "Defaults for Options menu" on page 602.
External
Simulation Data
Reads in file names for simulation data that is prepared either in the Simulation Manager or
externally to FloGrid. The data is not imported back into the Simulation Setup panel. The files
are listed in the Table and can be run using Start; the summary output is viewed in the graphics
only after the run. 3D graphics cannot be viewed automatically as this information is only
available for a simulation created in FloGrid.
Import
Summary Files
Import summary files from previous simulations or from simulations run externally to FloGrid.
They are plotted automatically in the graphics window.
History Data
Import production history in Production Analyst or Oil Field Manager format as normally
imported into the Schedule program.
Load 3D Files
Import the currently selected graphics (cyan) simulation 3D streamlines and properties into the
3D Viewer.

File menu
Export
Report
Writes out a hard copy of the data displayed in the plots including the mean, median and
standard deviation for the current selection.
View
Properties
Displays the number of points, mean and standard deviation of each of the histograms.
History
Actual data
Displays all the history available from the start date of the simulation onwards.
Averaged on time steps

Maps the history data onto the time steps in the simulation output over the range of the currently
loaded simulations.
Clear All History Data
Display Mode
Simulation
Displays the simulation data
Volumetrics
Displays the volumetrics data. In Volumetrics mode the panel function is similar to the mode
for simulation, but there is no graphics display for data versus time, and no concept of Starting
or Killing simulations; these buttons at the top left are disabled.
Simulation
View Status
This allows you to monitor the currently running simulation for problems, warnings, etc.
In the Status column the color coding is as follows:
• simulation progress is blue

File menu
• reports are in green and appear each time the simulation advances to the next time step
• errors are reported in red
• warnings are orange
• problems are yellow
• messages and other information are pale blue.
The check boxes at the top allow you to suppress the various outputs. For example if there is a
lot of output and you only want to see the problems that occurred, uncheck everything but the
problems.
Show Running Simulation/Show Loaded Simulation allows the panel to show the output
for the running simulation or to show the result of a simulation that has previously run.
Note When Show Loaded Simulation is selected the simulation is the one shown at the top
left of the Simulation Setup window in Restored Data.
Edit Notes
Add your own notes to be kept with the simulation through the Save and Restore mechanism.
Use ‘CTRL-n’ to add new lines or the ‘+’ at the top right of the table, and ‘CTRL-d’ to delete
lines. Type text into the lines and select the type of the line from the Type drop-down in the
table.
• When you run a multiple realization the table is copied to each of the runs. You can then
edit the table for each after the simulations have run. This allows you to write general notes
on all the runs plus particular notes on how each performed.
Note The simulation being edited is the one indicated in the Restored Data box in the
Simulation Manager window.
Simulation Setup
Opens the Simulation Setup panel.
Group
Cycle
This cycles different histograms to the front to account for histograms overlapping and therefore
difficult to see.
Green
• Grid
• Poro
• PermX
• PermY

File menu
• PermZ
• Contact
Each of these will, when one realization has been moved to a different histogram with the
specified color, move all other realizations which share the same Grid, Poro, PermX, etc. with
the realization already selected. If more than one realization has been selected the first
encountered is used.
Name
Selects a range of realizations, and adds to the green selection if one or more has already been
selected.
• If one name has been selected, the last part of the name beginning with an underscore is
removed. All realizations that share the remaining root name are added to the green group.
• If more than one realization is selected, the first two are examined to find a root part of the
two names that they have in common. This is applied in the selection as before.
Range
Selects a range of realizations and add to the green selection if one or more has already been
selected. If only one has been selected the selection is continued to the end of the list; if two
have been selected the selection includes those between the selections.
Enable
Disable
Enable/disable all the green realizations.
Magenta
• Grid
• Poro
• PermX
• PermY
• PermZ
• Contact
Each of these will, when one realization has been moved to a different histogram with the
specified color, move all other realizations that share the same Grid, Poro, PermX etc. with the
realization already selected. If more than one realization has been selected the first encountered
is used.
Name
Selects a range of realizations, and adds to the green selection if one or more has already been
selected.
• If one name has been selected, the last part of the name beginning with an underscore is
removed. All realizations that share the remaining root name are added to the green group.
• If more than one realization is selected, the first two are examined to find a root part of the
two names that they have in common. This is applied in the selection as before.

File menu
Range
Selects a range of realizations and add to the magenta selection if one or more has already been
selected. If only one has been selected the selection is continued to the end of the list, if two
have been selected the selection includes those between the selections.
• Enable
• Disable
Enables/disables all the magenta realizations.
Blue
• Enable
• Disable
Enables/disables the remainder (unselected realizations). That is those that have the blue
histogram and a white background in the table.
Clear
Clears all the grouping of histograms back to the initial setting (all data in one histogram).
Options
Summary Data
Keep in memory
Specifies whether the summary data, which can take up a large amount of memory, should be
stored in memory or re-read from disk whenever a graphics change occurred. If not in memory,
when a property type is changed a slight delay may be experienced.
Graphics Selection
Locked to Simulation Setup (Restore)
With this selected the magenta and cyan (column 1 and 2) in the table are locked together. This
means that the Simulation Setup panels are updated with the selected simulation automatically
as a graphics selection is made. This is ‘off’ by default as this slows the graphics down and
interfere with user editing of the Simulation Setup.
Table jumps to graphics selection

Locks the cyan (column 2) selection to the current active selected cell in the table. When a
selection is made using the graphics features the cyan selection is moved to the simulation
associated with that data point. But if the table is very large this may result in the cyan selection
being outside the displayed portion of the table. This mode causes the cyan selection to jump
into view in the table.
3D files to Load
• INIT and RESTART (Cell Properties)
• FrontSim Streamlines

File menu
• Simulation wells (‘off’ by default)
Select each of these to be imported in the File | Import | Load 3D Files menu option.
Note Simulation wells do not respond to the Wells tick box on the main window data tree
and interfere with the viewing of deviation surveys. It may be necessary to use Scene
| Wells in the main FloGrid window to manipulate the simulation wells. The option
below (Simulation Wells) is required to remove the Simulation Wells from the view
and restore normal well view functionality.
Simulation Wells
Show in 3D Viewer
Adds or removes all the simulation wells and their data to or from the 3D window. In adding the
wells on their own to the view the well data will be imported from the graphics files. This option
is ‘off’ by default.
Histogram
Full data range (all times)
The range of the histogram axis is usually calculated from the full range of the data throughout
all times. But the histogram is only a section through the data at a specific time and this can
result in a large part of the axis being unused. Unchecking this option will cause the range of
the axis to be the range of the data at the particular time step selected.
Well Connection Factor

Calculate
Causes the connection factor and Kh to be calculated and written out to the simulation files. See
"Calculation of Kh and connection factor" on page 617.
Simulator
Simulator to run
Changes the simulator that the Simulation Manager is using to run on the realizations
(FrontSim or ECLIPSE), and a remote simulation to be performed on a different machine.
The remote simulation uses rsh and rcp to carry out its operations. Thus it is essential that these
work properly for the simulation to run. This may require you to have the file ‘.rhosts’ in
your home directory on the target machine properly configured to give you and the simulator
access to that machine. Also, the files created locally that are copied out to the target machine
is configured according to the setup on your local machine (using the ECL.CFG settings). Thus
it is essential that the target machine is configured in a similar manner, otherwise the simulator
may report that the file to run could not be found; for example, because the CASE or SUFFIX
setting in the ECL.CFG files are different.
Hint If the simulator could not be found on the target machine then this could be because it
is not listed in the PATH variable on that machine.

File menu
Defaults for Options menu
The default settings for some of the options menus can be set in the ECL.CFG file.
The options that can be set are:
Options | Summary Data | Keep in memory:

Config entry: KEEP_SUMMARY_IN_MEMORY TRUE (default) or FALSE
Options | Well Connection Factor | Calculate

Config entry: WELL_CONNECTION_FACTOR FALSE (default) or TRUE
Options | Graphics Selection | Lock to Simulation Setup

(Restore)
Config entry: TABLE_LOCK_COLUMN_MAGENTA_CYAN FALSE (default) or TRUE
Options | Graphics Selection | Table jumps to current

selection
Config entry: TABLE_KEEP_SELECTION_IN_VIEW FALSE (default) or TRUE

File menu
Graphics Window
Double-click on a small “thumbnail” plot to make it change places with the main plot.
Histogram and CFD

The plot consist of a Histogram and Cumulative Distribution Function. The histogram is
calculated with the currently-selected bin size. This can be altered using the Number of Bins
slider on the left. In simulation mode the histogram can be considered to be a cross section
through the Single data curves on the date selected by the Simulation Days slider on the left.
The vertical cover line indicates the selected date for this section on the ‘Single data vs. Time
(envelope+history)’ plot.
Hint The CFD can be used to obtain the probability that, say, the FOPT (or any other
selected type) is greater than some particular value by setting the vertical cover line to
that value (or the nearest point). The horizontal cover line then gives the probability
for a value less than the selected value. 1 minus this gives the probability for a value
created than the selected value.
It is possible to put data from the blue histogram into a green or magenta one by using the Select
button under the table on the left. The first click on Select puts the realization into the green the
second click puts it into the magenta and a third click put it back into the original blue. Quick
grouping for a particular grid or property can be done through the menu Group | Green | Poro,
etc.
Note The histogram or CFD is effectively a ranking of the data in ascending order. When
used on derived history types it is a ranking of the difference from the historical data.
Accumulated data (AV and STD)

An Accumulation of the runs versus the run number. Also on this plot are the running mean and
standard deviation plotted above and below the mean.
Note The horizontal cover line in the Accumulated data (AV and STD) graph jumps to
the nearest point when released. This can be used to find the point nearest the mean or
one standard deviation above or below the mean by aligning it with the end point of
the mean or standard deviation curves and letting go. It jumps to the nearest point and
the simulation is also selected in the Simulation table.
Single data versus Time (envelope+history)

In Volumetrics Graphics mode the plot is empty.

Graphics Window
In Simulation Manager mode the selected summary type against time for all of the runs is
displayed. This graph shows all the simulations superimposed (by default in blue) and the single
currently selected one (by default in cyan). There are also gray dashed outer curves which are
the curves with the maximum and minimum value of all the curves at the current location of the
time slice cover line.
Note Notice that the multiple plots will be colored according to the color of the Histogram
associated with it as described above in Histogram and CFD.
You can alter the current selection using the cover lines in any of the other graphs or by selection
from the Management sliders on the left.
For example, you can use the cover line in the Single data vs. Time (envelope+history) plot
to select the Simulation Day on which the Histogram and Accumulation plots are drawn.
The curves in this plot are color coded with the multiple histograms specified by using the Select
button.
Note If the current point selected by the slider is the last one to come in from the simulator
then the selection automatically advances to the next one when the next simulation
finishes. If the selection is made from the percentile slider or the selected point is not
the last one then it is not automatically advanced.
In the case of the Histogram and CFD display, when you move the horizontal cover line, the
vertical line constantly moves to the point below. The percentile slider and the selected
simulation in the table on the left are also updated.
Note When making a column 1/magenta selection the information about the simulation is
loaded back into the Simulation Setup panel. The properties being passed to the
simulator on a selection are indicated above the table in the Simulate field. For other
properties for the simulation the individual folders have to be examined. For a
simulation the entire data is reloaded into all panels, for volumetrics only the contact
set and porosity are loaded.

Graphics Window
Management Options
There are four panel areas:
• "Simulation run control options" on page 605.
• "Table" on page 605.
• "Table (Volumetrics Mode)" on page 605.
• "Table (Simulation Mode)" on page 605.
This section also contains information on:
• "Table (Buttons)" on page 606.
• "Table column selections" on page 607.
• "Graphics control sliders" on page 607.
• "Type controls" on page 608.
• "Simulation Types (Type of data in the graph)" on page 609.
Simulation run control options

This allows you to start the simulation queue or stop it running.
• Start Queue: Starts the queued simulations.
• Kill Running: Stops the current simulation.
• Clear Table: Removes all the simulations and/or volumetrics that were added, and
consequently everything from the graphics panels.
Table
The table display is different between Volumetrics and Simulation (see below).
Above the table is the Simulate field, which shows the properties available to the simulator
when a selection is made from column 1, Status, of the table. There is also a field giving the
state of the queue in Simulation Mode. Below the table there are five buttons that apply to
operations on the rows of the table.
Table (Volumetrics Mode)

The table Status (column 1) is set to Volume and the Realization Data (column 2) lists the
properties used for this calculation.
Table (Simulation Mode)

Status (column 1 in the table) shows the state of the loaded simulations and Realization Data
(column 2) lists the root file name for the simulation (without the directory path).
Status takes settings that change according to the state of the simulation:

Management Options
• Queued: Shows the simulations that are waiting to run.
• Finished: Shows the simulations that have successfully completed.
Note Simulations that were imported as SUMMARY files have a status of Finished even if
there are no simulation DATA files which could be used to run the simulator associated
for them.
• Failed: Signifies the simulations that failed to start running due to bad data supplied to
FrontSim or ECLIPSE. This condition is generated by FrontSim or ECLIPSE.
• Killed: Indicates that you stopped the job running by pressing the Kill button.
• No Data: Lists the simulations that ran but produced no output. This usually occurs because
it stopped on the first time step or ran without the wells producing anything. One reason for
this may be because all the wells are shut in (possibly because there was not enough
pressure in the reservoir to cause flow): Try increasing the pressure at the oil water contact
in the Simulation Setup: General|2 Phase folder. Alternatively the data set may have
been incomplete in some way.
• No File: Indicates that the input simulation could not be found at the point of running the
simulation. This could happen if the files were deleted externally to FloGrid.
• No Exe: Indicates that FloGrid could not find FrontSim or ECLIPSE in order to run the
simulation.
• Can’t Run: Indicates that FloGrid failed to generate the grid geometry or property file
correctly for the simulation. This may occur in a Multiple Realization case when you
deleted a grid or property from FloGrid before the Simulation Manager wrote out the data
for it. This can occur as the files are only written out just prior to each simulation running.
Note For any condition blue indicates success, red failure. For more details, click on the
relevant Status in column 1, select menu option Simulation | View Status in the
Simulation Manager, and examine the Simulation Status panel that opens.
Table (Buttons)
Below the table on the same panel, there are five buttons. Some of the buttons apply to both
Volumetrics and Simulation modes. Buttons may be disabled, depending on the current
column in the table and the state of the simulation in the currently selected cell in the table.
The buttons are:
• Enable/Disable
• For Volumetrics, enables or disables the contribution of this selection to the graphics.
• For Simulation, if the simulation is queued then you can disable it so that it is skipped
when running the simulations. After a simulation has finished you can switch on and
off that simulation's contribution to the graphics. The option is context sensitive
dependent on the state of simulation at the row selected.
• Reset (Simulation only): Use this option to reset a Finished simulation to Queued.
• Delete: Deletes a finished simulation/volumetrics from the graphics. This frees up memory
but does not delete any files associated with the simulation.

Management Options
Note Delete applies to the Status selection, not to the Realization Data selection.
• Load3D (Simulation only): Plots the current selection from table column 2 in the 3D
Viewer.
• Select (Simulation only): Switches the color of individual plots in the ‘Single data vs.
Time’ plot and also changes the color of the background in the table to match.
The realization is moved into a different histogram:
• The first click changes it to a green histogram
• The second click changes it to a magenta one.
• A third click resets it back to the original blue.
This allows you to track selected curves between different types, for example, FOPT,
FWCT etc. selected in the Types Controls panel. And it allows you to identify groups
of curves with shared properties. The selections can be cleared with Group | Clear.
See menu selections above for various actions that can be performed with multiple
histograms.
Table column selections

• Click on the Realization Data name (column 2) to select the graphics point for the sliders
and cover lines.
• Click on the Status (column 1) to set the state of the Simulation Setup window (Restored
Data) for the simulation selected; the data that is passed to the simulation is indicated above
the table (Simulate) as a string of the properties separated by commas.
This way you can examine the properties and status for a simulation that has run in the Setup,
Status or Run folders in the Simulation Setup window.
You can also regenerate a particular data set grid and property file in the Simulation Setup
window by going to the Run folder there, selecting the Single folder and clicking on the Write
Sections button.
Note External Simulations which are imported through the menu selection Simulation
Manager: File | External | Simulation Data do not have the Grid Include file or
Property Include file set shown at the top left in Restored Data in the Simulation
Setup window. This is because only the file name is known; the file is not parsed to
determine its contents, and the grid and properties are not regenerated inside FloGrid.
Graphics control sliders

There are four sliders linked to the graphics cover lines and table selection.
• Percentile: You can select a simulation/volumetrics by setting a percentile.
In the case when there are multiple histograms and CFDs the slider will not be able to reach
all realizations because there is an ambiguity over which CFD to apply to. To reach all
realizations in this case, uncheck the box: ‘Percentile Slider uses Multiple Cases’.
• Display Index: You can select the simulation/volumetrics by index in the list.

Management Options
• Simulation Days (Simulation only): Selects the date that the histogram and accumulated
data are calculated.
• Number of Bins: Change the Bin Size for the Histogram here.
Type controls
The fourth panel selects the type of data to display in the graphics. There are two table lists side
by side. The lists depends on whether the mode is set to volumetrics or simulation.
Left Table: Summary type/Volumetrics type

For simulation the default is FOPT. It shows all the summary vectors available from the
simulation run.
In the volumetrics case it shows the quantities being measured.
There are derived types added to the bottom of the list from the summary data in the simulation
case. These have a prefix with an underscore (‘_’) in them. The ‘Break Through’ field refers
to the TIM_ type of these and specifies a value that if the curve for the specified quantity through
time rises above that value then the time for that to occur is plotted.
The prefixes are:
For FIELD types

• MAX_ = the plots are the maximum value encountered through time.
• MIN_ = the plots are the minimum value encountered through time.
• TIM_ = the time at which the Break Through value is reached.
• D_HIS_ = the difference from the historical data.
• S_HIS_ = root average square difference from the historical data (constant).
For Well types

• W_MAX_ = the plots are the maximum value encountered through time.
• W_MIN_ = the plots are the minimum value encountered through time.
• W_TIM_ = the time at which the Break Through value is reached.
• W_D_HIS_ = the difference from the historical data.
• W_S_HIS_ = root average square difference from the historical data (constant).
• W_P_MAX_ = the plot for the well that contains the maximum value.
• W_P_MIN_ = the plot for the well that contains the minimum value.
In the case of wells the quantities are obtained by examining only those wells that are selected
from the Right table (see below). For the W_ well types the well name that correspond to the
currently selected curve is indicated in the status bar at the bottom of the main graphics window.

Management Options
Right table: Well name/Volumetrics breakdown
For simulation, if a well property is chosen (for example WOPT) then the wells are listed. You
can select multiple wells, in which case the summary data from them is summed together to
produce single plots (except for some of the W_ derived properties). For volumetrics the
breakdown is always listed. Multiple selection is allowed and the data from each is added to
produce single plots.
Note If summary data from different simulations is loaded with different wells in each, then
the list at the bottom on the left is an accumulation of all the wells. The view does not
automatically select different wells when a simulation is clicked on.
Simulation Types (Type of data in the graph)

For the left table the following code is used:
• First Letter:
• F = Field
• G = Group
• W = Well
• M = Material Balance Error(%)
• FM = Field Number of
• Subsequent letters:
• O = Oil
• W = water
• G = Gas
• P = Production
• I = Injection
• IN = Injection currently flowing
• IA = Injection abandoned
• T = Total
• R = Surface Rate
• Q = Reservoir Rate
• WI = Well Index
• IP = In Place
• BHP = Bottom Hole Pressure
• PR = Pressure
• WCT = Water Cut (Water oil ratio)
• GOR = Gas Oil ratio
• WGR = Water Gas ratio

Management Options
Above the type list there is a filter string that allows the selection of types that match any string.
The match string may begin and end with a ‘*’ representing any characters. The ‘!’ character
(not) in front of a string matches all strings that do not match the following characters. The same
convention applies to the list of wells/volumetrics breakdown.
Note FrontSim aborts, by default, if the Material Balance Error (MT) becomes greater then
2%.

Management Options
Schedule section keyword generation
This section describes the generation of the simulator keywords for the SCHEDULE section and
is of interest only to those familiar with keyword input to the simulator.
The following keywords are generated:
• "WELSPECS"
• "WELOPEN"
• "WELOPEN"
• "WCONPROD"
• "WCONHIST"
• "WCONINJE"
• "COMPDAT"
• "TSTEP" .
There is no generation of LGR connections.
WELSPECS
Identifies the well. In Field mode the main window data tree is used to determine if the well is
injecting water or producing oil. In Well mode the preferred phase is determined by examining
the oil, water and gas specifications for the well. If oil and water are specified, the preferred
phase is LIQ.
The phase is used by the simulator in determining the worst offending well for GCONPROD and
GCONPRI keywords, which are not output in this simple case.
WELOPEN
If the connections in the well change, this shuts the well at the beginning of the time step
immediately prior to opening the new connections on the current date, using COMPDAT
(below).
WCONPROD
Specifies the production targets for the well. In Field mode the keyword will be generated if the
well is a producer as specified in the main window wells data tree, and then only the BHP target
is set. In Well mode the keyword will generated if the well is found to be a producer, by
examination of the production columns (Oil, Water and Gas) and injection column
(InjWat/InjGas). Injection dominates if there is an ambiguity, in which case production is lost
and the keyword is not generated. If the state of the well is not SHUT then the keyword is
generated.
WCONHIST
Only output in Well mode. Specifies the production targets for the well. The simulator
determines whether to generate the production keyword by examining the production columns
(Oil, Water and Gas) and injection column (InjWat/InjGas). Injection dominates if there is an
ambiguity, in which case production is lost and the keyword in not generated. If the state of the
well is not SHUT then the keyword is generated.

WCONINJE
Specifies the injection rate for the well. In Field mode the keyword will be generated if the well
is an injector as specified in the main window wells data tree, and then only the BHP target is
set. In Well mode the simulator determines whether to generate the injection keyword, by
examining the production columns (Oil, Water and Gas) and injection column
(InjWat/InjGas). Injection dominates if there is an ambiguity, in which case production is lost
as this keyword will be generated.
COMPDAT
Specifies the completions for the well. The simulator calculates the direction of the connection
to the grid cell from how the deviation survey enters the grid cell in question. If there are events
present these are used to define the cells that appear in the IJK list.
The well connection factor (and Kh) can be accurately calculated and output in this keyword by
setting the Simulation Manager: Options | Well Connection Factor | Calculate or by
setting the default for this option in the Config file setting WELL_CONNECTION_FACTOR to
TRUE.
The connection factors and Kh are calculated from the Peaceman formula (as specified in the
"Calculation of Kh and connection factor" on page 617, which takes into account the direction
of the well and partial penetration. The following simplifications apply:
• There is only one diameter and skin for a particular connection factor calculation
• The diameter and skin is the value from the last event in the time step within cell
• Net to gross is not used.
TSTEP
Advances the simulation the specified number of days.

Black Oil correlations
Introduction
The Oil formation volume factors and viscosities are calculated using the Black Oil correlations
given in this section. The Gas and Water formation volume factors and viscosities, together with
the water compressibility, are calculated using correlations given in this section. For further
information see:
• "Oil formation volume factor and solution gas-oil ratio" on page 613.
• "Oil viscosity" on page 614.
• "Gas formation volume factor" on page 615.
• "Gas viscosity" on page 616.
• "Water formation volume factor" on page 616.
• "Water viscosity" on page 616.
and
• "Calculation of Kh and connection factor" on page 617.
Oil formation volume factor and solution gas-oil ratio

The solution gas-oil ratio of saturated oil (Rssat scf/stb) is calculated from Standing’s
correlation, [Ref. 37]:
( 0.0125API – 0.00091T ) ( 1 ⁄ 0.83 )
10 P
R ssat = SPG g --------------------------------------------------------- [EQ 23.1]
18 ⋅ FO 1
where:
SPGg is the gas specific gravity (relative to air)

P is the pressure in psia
API is the oil gravity in °API
T is the temperature in °F
FO1 is a property tuning factor (see above).
The API gravity of oil is related to its specific gravity relative to water ( SPGo ) by:
141.5- – 131.5
API = ------------ [EQ 23.2]
SPGo
If the oil is saturated (producing GOR > Rssat ), the formation volume factor ( FVFo rbl/stb) is
calculated from the relation given by Frick, [Ref. 14]:
1.175
FVF o = 0.972 ⋅ FO 2 + 0.000147 ⋅ FO 3 ⋅ F [EQ 23.3]
where FO2 and FO3 are property tuning factors, and:
⎛ SPG ⎞ 0.5
F = R ssat ⎜ ------------g-⎟ + 1.25 ⋅ T [EQ 23.4]
⎝ SPG o⎠

If the oil is under-saturated (producing GOR < Rssat ), the bubble-point pressure (PBUB) is first
calculated as:
GOR 0.83
PBUB = 18 ⋅ FO 1 ⋅ ⎛⎝ -------------⎞⎠
( 0.00091T – 0.0125API )
⋅ 10 [EQ 23.5]
SPG g
where:
GOR is the producing gas-oil ratio in scf/stb.
The formation volume factor is obtained from a compressibility relationship:

FVF o = FVF ob exp [ C o ( PBUB – P ) ] [EQ 23.6]
FVFob is the formation volume factor of saturated oil at the pressure PBUB.
The oil compressibility Co is obtained from the correlation of Vazquez and Beggs [Ref. 38]:
– 1433 + 5 ⋅ GOR + 17.2 ⋅ T – ( 1180 ⋅ SPGS g ) + 12.61 ⋅ API
C o = FO 4 -------------------------------------------------------------------------------------------------------------------------------------------------
- [EQ 23.7]
5
10 P
where:
FO4 is a property tuning factor.

SPGSg is the gas gravity that would result from a separator at 100 psig.
Vazquez and Beggs [Ref. 38] provide a correction for other values of the separator pressure
(PSEP psia):
PSEP
SPGS g = SPGg 1 + 5.912 ⋅ 10 SPG o ⋅ TSEP ⋅ log ⎛⎝ -------------⎞⎠
–5
[EQ 23.8]
114.7
where:
TSEP is the separator temperature in °F.
VFPi applies this equation with PSEP and TSEP at standard surface conditions.
Oil viscosity
The viscosity of saturated oil (in cP) is obtained from the correlation of Beggs and Robinson, as
reported by Brown and Beggs [Ref. 3]. The viscosity of dead (gas-free) oil is first determined
from the equation:
x
VISC od = 10 – 1 [EQ 23.9]
where:
y – 1.163
x = 10 T
y = 3.0324 – 0.02023API
This is transformed into the saturated oil viscosity (VISCo) by:

( FO 6 B )
VISC o = A ⋅ FO 5 ⋅ VISC od [EQ 23.10]
where:
FO5 and FO6 are property tuning factors, and
– 0.515
A = 10.715 ( R s + 100 )

– 0.338
B = 5.44 ( R s + 150 )
If the oil is under-saturated, the viscosity of oil at the bubble point pressure (VISCob) is
calculated as given above, and then transformed using Standing’s fit ([Ref. 37]) to Beal’s curve
for under-saturated oil:
VISC o = VISC ob + X ( P – PBUB ) [EQ 23.11]
where:
1.6 0.56
[ 2.4 ( VISC ob ) + 3.8 ( VISC ob ) ]
X = FO 7 --------------------------------------------------------------------------------------
-
5
10
FO7 is a property tuning factor.
Internally, the viscosity is required in units of lbm/ft-sec. The viscosity in cP is transformed into
these units by dividing by 1488.
Gas formation volume factor

The built-in correlations relate to the properties of dry gas. The program can take account of oil
drop-out and re-vaporization in gas condensate wells, but the PVT properties of wet gas must
be supplied in the input data tables.
The gas formation volume factor (FVFg rcf/scf) is related to the Z-factor by:
P surf ⋅ TR well
FVF g = Z ------------------------------
- [EQ 23.12]
P well ⋅ TR surf
where:
TR represents the temperature in degrees R (= T °F + 460), and

the subscripts “well” and “surf” relate to the local well bore conditions and
standard surface conditions respectively.
The Z-factor is calculated from the Hall-Yarborough [Ref. 19] correlation, as reported by Dake
[Ref. 5]:
0.06125P 2
Z = -------------------------r t ⋅ exp [ – 1.2 ( 1 – t ) ] [EQ 23.13]
y
y is the “reduced density” which is calculated by Newton iteration from the relationship:
2 ⎛ y + y 2 + y 3 – y 4⎞
– 0.06125 P r t ⋅ exp [ – 1.2 ( 1 – t ) ] + ⎜ ------------------------------------⎟ [EQ 23.14]
⎝ 3 ⎠
(1 – y)
2 3 2 2 3 ( 2.18 + 2.82t )
– ( 14.76t – 9.76t + 4.58t )y + ( 90.7t – 242.2t + 42.4t )y = 0
where
Pr is the “pseudo reduced pressure”, P / Pcrit, and

t is the “reciprocal pseudo reduced temperature”, TRcrit / TR.
The values of the critical pressure and temperature are obtained from Katz’s [Ref. 23] curves
for miscellaneous or “California” gases, as reported by Standing [Ref. 37]:
2
P crit = 677 + 15 ⋅ SPG g – 37.5 ( SPG g ) [EQ 23.15]

2
T crit = 168 + 325 ⋅ SPG g – 12.5 ( SPG g ) [EQ 23.16]
Gas viscosity
The gas viscosity (VISCg cP) is calculated from the correlation of Lee et al. [Ref. 28]
y
VISC g = 0.0001K ⋅ exp { x ( DLG ) } [EQ 23.17]
where
DLG is the local density of the gas in g/cm3, and

1.5
K = (----------------------------------------------------
9.4 + 0.02M ) ( TR ) -
209 + 19M + TR
986
x = 3.5 + ⎛⎝ ---------⎞⎠ + 0.01M
TR
y = 2.4 – 0.2x
M is the molecular weight of the gas, which is calculated from the gas gravity:
M = 28.966 SPGg
The viscosity is transformed internally into units of lbm/ft-sec by dividing by 1488.
Water formation volume factor

The water formation volume factor (FVFw rb/stb) is calculated by assuming a compressibility
of 3x10–6 psi-1, and fitting thermal expansion coefficients to match approximately the
temperature dependence curves given by Frick [Ref. 14] for pure water,
–4 –7 2 –6
FVF w = ( 1 + 1.25x10 DT + 9.88x10 DT ) ( 1 – 3x10 DP ) [EQ 23.18]
where:
DT = T - Tsurf in °F and
DP = P - Psurf in psi.
Water viscosity
The water viscosity (VISCw cP) is calculated from Beal’s correlation as reported by Brown and
Beggs [Ref. 3]:
–5 2
VISC w = exp [ 1.003 – 0.01479 ⋅ T + 1.982x10 T ] [EQ 23.19]
The viscosity is transformed internally into units of lbm/ft-sec by dividing by 1488.
Above a percentage of 60-70%, the emulsion inverts and brine becomes the continuous phase.
The viscosity of the emulsion then can be approximated by the brine viscosity. However, near
the inversion point, extremely high viscosities can be attained.

Calculation of Kh and connection factor
When the WELL_CONNECTION_FACTOR option in the ECL.CFG is used FloGrid calculates
the connection factors for the well. You can also set this option in the Simulation Manager
under Options | Well Connection Factor | Calculate.
Grid connections are affected by events, and the connections affected by a particular event are
determined by the measured depth of the event. When any event affects a completion,
calculates a connection factor.
The connection factor calculated by is based on a three-part Peaceman formula which takes into
account the following factors:
• the orientationof the well
• the permeabilities of the grid block
• the portion of the grid block which is perforated
• the effective wellbore diameter in each of the orthogonal X, Y and Z directions
In addition, you may specify damage skins.
This approach allows to accurately model situations, such as deviated wells, partially
penetrating wells, and multiple perforations within a given cell, by directly incorporating these
effects into the connection factor (due to the full vector representation). Many simulators just
model these effects by adjusting the skin value.
Cell entry and exit points are supplied through the well trajectory data. Schedule uses this
information to define a trajectory vector that represents the straight line between the entry and
exit points. The perforation length is defined in the event file, so the measured depth of the start
and end of the perforation are known. With these two pieces of information, the length of the
perforation within each grid block that lies along the trajectory vector is known.
The trajectory vector is split into its three components in the local X, Y, and Z directions, and
scaled to the measured perforation length. In effect, the local X, Y, and Z directions define the
directions in which the PERMX, PERMY and PERMZ arrays are to be interpreted.
The algorithm to calculate the local x, y, z unit vectors is as follows:
Let i and j be the vectors joining the centroids of opposing faces in the i and j directions local
to a cell. The z unit vector is then calculated as the normal to the plan defined by the i and j
vectors.
Note If the PERMX direction is assumed to be vertical (option 2 above) then i and j are
projected on to the horizontal plane by setting iz=0 and jz=0.
We now want to calculate the x and y vectors as two orthogonal vectors in the plane given by i
and j that are as closely aligned with i and j as possible. When i and j are not orthogonal to each
other, as in general they are not, we want the resultant vectors to line up more closely with the
longer of i and j, this can be achieved by rotating one of the vectors through 90 degrees in the
plane defined by i and j and adding it to the other. This defines the first unit vector in the plane.
The second unit vector is orthogonal to this one.
Mathematically we can describe the above as:
z = i×j [EQ 23.20]

x = i + j × ẑ [EQ 23.21]
y = j + i × ẑ [EQ 23.22]
where
ẑ = z ⁄ z [EQ 23.23]
Each of these vectors is then normalized to give unit vectors.
Using the above equations we can state the following properties for the x, y and z unit vectors.
1 x, y and z are guaranteed to be orthogonal.
2 If i and j are orthogonal then x̂ = î and ŷ = ĵ
3 As i → 0 then ŷ → ĵ
4 As j → 0 then x̂ → î
5 If i = j then the axis is equally displaced from i and j.
Thus, defining
h x as the magnitude of the perforation vector in the local x direction.
Dx as the magnitude of the local x vector.

Kh in the X direction becomes:
K h x = ( Ky × Kz ) × hx [EQ 23.24]
and the Peaceman radius in the X direction is:
K K
D z2 ⎛⎝ -----y-⎞⎠ + D y2 ⎛⎝ -----z-⎞⎠
Kz Ky
r ox = 0.28 ⋅ -------------------------------------------------------- [EQ 23.25]
⎛ K y⎞ ⎛ K z⎞
⎝ 4 ----- - + ------
K z⎠ ⎝ 4 K y⎠
Similarly for the Y and Z directions.

Thus:
cθKh x
Tx = --------------------------
- [EQ 23.26]
⎛ r ox⎞
------
ln ⎝ ⎠ + S -
rw
where
Tx is the connection transmissibility in the X direction
S is the damage skin
θ equals 2π
c is 0.001127 in field units, 0.008527 in metric units
The cell connection factor (CCF, and Kh, that are output to the COMPDAT statement) are defined
by:

CCF = Tx2 + T y2 + T z2 [EQ 23.27]
2 2 2
Kh = Kh x + Kh y + Kh z [EQ 23.28]
Note FloGrid ignores the net-to-gross term.

Orthogonalization of vectors
Introduction
In FloGrid 2003A_1 and later versions, the calculation of the connection factor was improved
for distorted cartesian grids. The method used to define the direction of the three unit vectors x ,
y and z onto which the trajectory vector is projected can be changed by defining
WELL_CONNECTION_METHOD in the configuration file. In effect this means defining the
directions in which the PERMX, PERMY and PERMZ arrays are to be interpreted.
There are three options for WELL_CONNECTION_METHOD.
0 Old method cell-aligned well connection factor (as used before 2003A_1).
1 Improved Well Connection Calculation with PERMZ aligned (orthogonal) to the
bedding plane.
2 Improved Well Connection Calculation with PERMZ aligned with the vertical (Z)
direction.
Well connection factor

To activate the WELL_CONNECTION_METHOD set the WELL_CONNECTION_FACTOR
parameter to TRUE.
Note If you do not specify a WELL_CONNECTION_METHOD, method 1 is used by default.
Having defined how PERMZ is treated, the PERMX and PERMY directions are calculated by
orthogonalization of the vectors as described below.
Orthogonalization of the vectors

Let i and j be the vectors joining the centroids of opposing faces in the i and j directions local
to a cell. The z unit vector is then calculated as the normal to the plane defined by the i and j
vectors.
Note If the PERMZ direction is assumed to be vertical then i and j are projected onto the
horizontal plane by setting i z = 0 and j z = 0 .
We now want to calculate the x and y vectors as two orthogonal vectors in the plane given by
i and j that are as closely aligned with i and j as possible. When i and j are not orthogonal to
each other, as in general they are not, we want the resultant vectors to line up more closely with
the longer of i and j , this can be achieved by rotating one of the vectors through 90 degrees in
the plane defined by i and j and adding it to the other. This defines the first unit vector in the
plane. The second unit vector is orthogonal to this one.
Mathematically we can describe the above as:
z = i×j
x = i + j × ẑ

where
ẑ = z ⁄ z
Each of these vectors is then normalized to give unit vectors.

Using the above equations we can state the following properties for the x , y and z unit vectors.
1 x, y and z are guaranteed to be orthogonal.
2 If i and j are orthogonal then x̂ = î and ŷ = ĵ
3 As i → 0 then ŷ → ĵ
4 As j → 0 then x̂ → î
If i = j then the axis is equally displaced from i and j .

Chapter 24
Introduction
The Multiple Realization facility allows you to generate realizations based on combinations of
all the properties that exist on gridded models. The generated realizations can be used to make
volumetric measurements or perform streamline simulations.
This chapter contains the following information:
• Viewing volumetric reports and selecting properties, etc. for realizations (see "Realizations
Dialog (Volumetrics)" on page 625).
• Creating realizations (see "Executing Realizations" on page 628).
• Creating multiple realizations for FrontSim (see "Multiple Realizations for FrontSim
simulations" on page 629).
• Viewing simulation reports and selecting properties etc. for realizations (see "The
Realizations Dialog (Simulation)" on page 630).
Overview
A single realization can only contain one property of any given type. For example, only one
Porosity property or PermX property is allowed. If a model has two Porosity properties defined
(called Poro1 and Poro2, say) and three PermX properties defined (perm1, perm2, perm3), six
realizations of the model (2 x 3) are generated that use these property combinations:
Poro1 , PermX
Poro2 , PermX
Poro1 , PermY
Poro2 , PermY
Poro1 , PermZ
Poro2 , PermZ
If there are many variations of properties existing on a model, many realizations are generated.
You can choose to use a selected subset of the generated realizations for processing.
FloGrid User Guide Multiple Realizations 623

Introduction
The results of the processing stage can be viewed directly in the Graphics Display panel.
Multiple Realizations for Volumetrics

Access to multiple realizations for volumetrics processing is through the Volumetrics dialog.
See "Volumetrics" on page 569 for the details of how to specify and make volumetric
measurements on a gridded model.
The volumetrics workflow allows you to create one or more named Volumetrics Reports. Each
report specifies one or more measurements to be made on a selected model and where the results
of the calculation are placed (file, screen, statistics package). To access Multiple Realizations:
• create at least one named report
• click on Multiple Realizations.
The Volumetric Realizations dialog then opens.
624 Multiple Realizations FloGrid User Guide

Introduction
Realizations Dialog (Volumetrics)
Using this dialog you can see all the models and their properties that are relevant to the
volumetrics reports that you have created; you can:
• see all the possible realizations that can be used for your reports
• see what reports cannot be made because the properties needed to make the measurements
do not exist on the model(s)
• select a subset of realizations to be used to make measurements
• make the measurements on the selected realizations.
The dialog consists of three tables.
• "Existing Models Table" on page 625
• "Possible Realizations Table" on page 627
• "Impossible Realizations" on page 627.
Existing Models Table

The Existing Models and Properties table displays all the relevant models and their
properties. A model is displayed only if it possesses at least one property whose type is needed
to make some volumetrics measurement.
Note If a model does not possess any of the properties needed to satisfy a report, it will never
appear in this or any of the other tables.
The first column lists the model name. The second column lists the property type names, and
the third column lists the existing properties of those types. All the properties listed are existing
property grids. You cannot change the content of these columns.
The fourth column is used to define constraining groups.
You can change how the realizations are generated by changing whether models and properties
are used and by imposing grouping to constrain which properties are allowed to be used with
each other.
Changing Usage
You can choose whether you want a particular model, properties, or all properties of a given type
to be used to generate realizations, by selecting with the left mouse button and then clicking on
the Toggle Usage button. Selections are highlighted with a RED background. You can select:
• a model name in column 1 - this selects all of the properties for the model.
• a property type name in column 2 - this selects all of the properties for that type and model.
• a single property (one mode click) or a contiguous set of properties (2 mouse clicks) in
column 3. The selection always uses the last 2 mouse clicks to define the range of
selections. You can reset the selection by clicking on the Deselect button.
When the Toggle Usage button is pressed, the usage of the selected items is inverted (on-off,
off-on). If you change the usage from off to on, all of the related items to the right are turned on.
If you change the usage from on to off, all the items to the left are changed if this is appropriate.

Note the following:
• Items that are being used are displayed as black text on a white background.
• Items that are not being used are displayed as black text on a gray background.
• Only models and properties that are select for use are used to generate realizations.
• The effect of toggling the usage is immediately reflected in the possible realizations table.
Grouping properties by hand

You can further constrain how realizations are generated by specifying that certain properties
must always occur together in any realization. To force two or more properties to be used
together, you type the same name into the group column for each property in the group. The
name is quite arbitrary and serves only to bind the properties together, for the purpose of
ensuring that they always appear together in any realization. These grouping constraints are then
applied when realizations are generated.
Note the following:
• You cannot use the same name for properties of the same type within a model, because
properties of the same type are not allowed in a single realization
• The name must consist only of letters, digits, dashes or underscores, for example “g1”,
“123”, “AAx”. Spaces are not allowed.
Note The group names that you type are arbitrary and are unrelated to any other form of
property grouping that occurs in FloGrid.
Auto-grouping of properties
When there are many properties on a model, typing in grouping constraints can be tedious. The
Guess Groups button applies an algorithm based on the property names to generate groupings,
as follows:
• If the name is of the form XXXX-rNN where N is a digit, a group name of model--NN is
generated. For example, if the model is called fred and it has properties ntg-r1, ntg-
r2, poro-r1, they are given group names fred--1, fred--2 and fred--1
respectively. This means that ntg-r1 and poro-r1 must appear together in any
realization. This name convention is based on the names generated by property population
algorithms when multiple properties are calculated.
• If the property name is of the form XXXX-NN or XXXXNN, a group name model--NN is
generated.
All of the group names can be erased by selecting the Clear Groups button.
The effect of guessing group names is reflected immediately in the realizations table. It may
eliminate all realizations, in which case you can edit individual group names as appropriate.
Caution If you hit the Clear Groups button, all existing group names that you may have
entered are lost.

Possible Realizations Table
The Realizations using Existing Models and Properties table lists all of the possible
realizations, if any. The list is based on all relevant models and all the volumetric reports that
you have defined using the Volumetrics dialog. The content of this table reflects all the usage
and group settings that you may have made in the Existing Models and Properties table.
The first column shows the Volumetrics Report name. At the time you created the report, you
had to specify a particular model and a specific set of properties to use. Now, however, all the
measurements specified in a report are made, using the model and properties shown in the other
columns of the table for each realization case.
The Possible Realizations table can be empty for a number of reasons:
• you have not specified any named report definitions
• there are no models loaded that possess any properties that are relevant to making
measurements (or running simulations, see "The Realizations Dialog (Simulation)" on
page 630)
• you have turned off the usage for all relevant properties
• you have set groupings that eliminate all the combinations.
Display limitations
It is possible in some cases for many thousands of realizations to be generated, and so the
number visualized in this table is limited, by default, to 1000. If the number of possible
realizations is less than this limit, all are displayed. If the number is greater, only the first 500
and last 500 are displayed. The limit is a configurable option. To change it, edit your
configuration file (ECL.CFG) entry for:
SECTION FLOGRID, SUBSECT MULTIPLE_REALIZATIONS:
MAX_DISPLAYED 1000
Note If you set this value to a large number (25,000 say) and more than 10,000 realizations
are generated, display update may be unacceptably slow.
Impossible Realizations
The Requests Unsatisfied by Existing Models table lists the models that possess some, but
not all, of the property types needed to make the measurements specified in a named report. For
each relevant report and model, the missing property types are shown in the third column.
Note If a model does not possess any of the properties needed to satisfy a report, it does not
appear in this or any of the other tables.

Executing Realizations
When you are satisfied with the set of realizations that have been listed, click on the OK or
Apply button to execute them. The results of the execution (the report outputs) go to wherever
you specified when you created the report specification.
If you click on OK, the dialog closes after execution and the current settings are recorded and
can be saved as part of the workspace. If you click on Apply, the dialog remains open.
All results go to a graphics display. You can view this display by clicking on the Display
Graphics button in the Results box. See "Graphics Window" on page 603.
Cancel and Continue

You may interrupt the execution of Volumetrics Multiple Realization execution by clicking
on the Cancel button in the progress bar. After an interruption, when you click on OK or Apply
you are presented with a choice to continue from where execution left off, or to start again and
re-execute from the beginning. However, if you have made any changes to the usage or group
constraint settings, you are only allowed to execute from the beginning, because the set of
possible realizations will have been re-computed and may have changed.

Executing Realizations
Multiple Realizations for FrontSim simulations
You can access multiple realizations for simulations processing using the Simulation Setup
dialog. See "Streamline Simulation" on page 585 for the details of how to specify simulation
runs.
The simulations workflow allows you to create a simulation run based on a selected model and
properties.
To access Multiple Realizations, you have to
• set up a simulation run
• click on the Multiple Realizations button in the Multiple folder in the Setup/Run panel.
The Simulation Realizations dialog opens.

Multiple Realizations for FrontSim simulations
The Realizations Dialog (Simulation)
The functionality of this dialog is identical to that of the Realizations dialog for Volumetrics
(see "Realizations Dialog (Volumetrics)" on page 625). For models that contain permeabilities
and porosities, you can see the models and possible realizations displayed. You can control
which models and property combinations are used to make realizations using the usage and
grouping features in the same way as for Volumetrics. To execute the simulations, you click on
the Apply button. Simulation results are automatically sent to the graphics display and to the 3D
Viewer.
There are, however, some differences in what you see displayed compared with the
Volumetrics case:
• the simulation setup workflow does not allow you to explicitly set up more than one
simulation “report”, so when you enter the Multiple Realizations panel you only see a
single name in the Report Name column of the tables. That name is always
“Simulation”.
• when you click on Apply to execute the simulations, all the realizations are sent in one
batch to the Simulation Manager for execution. The execution of the simulations takes
place simultaneously with that of FloGrid itself. This means that you could change the
content of the Realizations panel and send a new batch for execution before the previous
batch of simulations has finished executing.
In the Volumetrics case, the realizations are sent and executed one at a time. You cannot
make changes in the Realizations panel until execution of the batch of realizations has
completed.

The Realizations Dialog (Simulation)
Well Planning
Chapter 25
Introduction
The well planning feature (requiring a separate license) enables the following FloGrid
options:
• Editing of well paths:
• constraining target points by geological features (layers, surfaces, etc.)
• generation of wellpath from target points, honoring drilling constraints.
• Import, display, modification, and export of well events (for example, perforations)
• Generating vertical wells in areas identified by property thresholding techniques.
For further information on these options see "Well node" on page 637.
• Export of well deviations.
For further information on this option, other export and import options and advanced well
planning options see "Wells node" on page 632.
These options aid the creation of wells for the purposes of screening.
FloGrid User Guide Well Planning 631

Introduction
Wells node
The Wells Node section documents some of the menus available by right-clicking on the
wells base node in the node tree. Those options not requiring a well planning license feature are
documented in "Wells Data" on page 374.
Advanced Vertical Well Planning

Opens the Advanced Vertical Well Planning dialog, which allows the creation of several
planned vertical wells simultaneously.
Targets can be initialized by way of clicks in the 3D Viewer, from file, or from the cell centers
of currently displayed cells (allowing targets to be positioned according to user-defined
thresholding criteria).
Advanced Vertical Well Planning dialog

Displays the areal target locations of the planned wells to be created. At least one well name
must be provided; if a planned well is not named then it takes its name from the last named well
above. Target locations can be read from file by selecting the Table Import option in the right
mouse button pop-up menu.
Note that it is not possible to edit target well locations in the 3D Viewer, but you can edit these
positions manually in the data table. Once wells have been created their locations are removed
from the data table; you can then edit the wells using the Edit Wellpath dialog.
From Current Pick

Adds a new target location at the last picked location (information on this location is given in
the text window). In order to optimize this process for many picks, check the Auto Select Pick
option; if this option is checked, subsequent 3D Viewer pick locations are automatically added
to the table.
From Displayed Cells

Adds new entries into the data table, each corresponding to the center of a cell displayed in the
active grid. This option is intended to be used in conjunction with appropriate thresholding
techniques. You are asked to confirm this operation if it results in the creation of more than
twenty new wells.
Vertically Position
Sets the vertical extents of the wells manually. Note that if other geological features are
present—defining a volume of interest—the extents can be taken from this volume.
632 Well Planning FloGrid User Guide

Wells node
Auto. Completion
Requests that the new wells are automatically completed upon creation. If this option is selected
you need to enter the completions’ event date (Schedule symbolic dates are allowed in addition
to normal dates), together with the completions’ diameter and skin values. If the complete By
Depth option is chosen, you also need to enter the depths at which the completions should
occur. A completion is added to each newly-created well; if additional completions are required,
or you need to change the completion parameters, this can be done using the Edit Events
dialog.
Import Well Events

FloGrid can import well events in the proprietary Schedule format. Perforation, barefoot,
squeeze and plug events are interpreted.
Note Any ECLIPSE keywords in the event file are ignored.
Schedule
Specifies the location of the Schedule format event file.
Well event file format

You can list well events in any date order within the input ASCII file; FloGrid re-orders the
dates as necessary. Wells can also appear in any order in the input file. It is recommended that,
for each well, the event data are grouped together, and in date order, to make the ASCII file
more readable.
A group of events for a well is introduced by the WELLNAME keyword, which is followed by a
name for the well. The events for the well should follow the WELLNAME keyword with each
event specified on a single line. The format for the event specification is:
DATE EVENT-NAME EVENT-RELATED-DATA
This format repeats for all events relating to the well. Blank lines are allowed at any point, and
lines that have '--' as the first two characters are ignored. See "Example 1" on page 636, which
shows this format.
Well event names may be in either upper or lower case (or mixed). However, if any entry has
been made for a layer constraint (for example SAND_1), this name is case sensitive. Note that
layer names must be contained in brackets (see "Example 2" on page 636).
As in Schedule, you may use symbolic dates in place of actual dates. These are preserved with
the event, allowing the symbol’s meaning to be interpreted if the events are exported and read
back into Schedule. The allowable symbolic dates are:
• SPH (Start of Production History)
Represents the first data where production history occurs.
• EPH (End of Production History)
Represents the last data where production history occurs.
• SOH (Start of History)

Wells node
Represents the date associated with the Schedule symbol SOH (in Schedule this defaults to
the start of production history [SPH]).
• EOH (End of History)
Represents the date associated with the Schedule symbol EOH (in Schedule this defaults to
the start of the prediction period, minus 1 day).
• SOP (Start of Prediction)
Represents the date associated with the Schedule symbol SOP (in Schedule this defaults to
the last date where production history is recorded, minus 1 month).
• EOP (End of Prediction)
Represents the date associated with the Schedule symbol EOP (in Schedule this defaults to
the start of the prediction period, plus 1 year).
• SOS or INITIAL (Start of Simulation)
Represents the first defined date available (in Schedule this is defined by the first row of
the time framework table).
• EOS or FINAL (End of Simulation)
Represents the last date available (in Schedule this is defined by the first row of the time
framework table).
Event related data must also be provided in a specified order that is determined by the event
name.
Event shifting in time can be specified in the file if the event shift direction is different from the
default. The event time shift direction is specified after the layer name within the brackets, and
has the form:
(LAYER shift=-) or (LAYER shift=0) or (LAYER shift=+).
The layer name “LAYER” may be omitted.
Event names that are recognized by FloGrid (a subset of those recognized by Schedule), and the
event related data, are shown in Table 25.1:
Table 25.1 Event names and associated event related data

Measured
Measured
Diameter
Wellbore
Number
Bottom
Depth
Depth
Table
BHP
Skin
Top
Kh
perforation • • • •
barefoot • • •
squeeze • •
plug •
Perforation
Opens the well to flow within a certain specified measured depth range.
Barefoot
Opens the well to flow from a given measured depth to the bottom of the well.

Wells node
Squeeze
Closes the well to flow within a certain specified measured depth range.
Plug
Closes the well to flow from a given measured depth to the bottom of the well.
Event file UNITS keywords
Table 25.2 Event file UNITS keywords

UNITS FIELD This keyword allows the events data to be input in FIELD units. These
units need not be the same as the units used within the project.
UNITS METRIC This keyword allows the events data to be input in METRIC units.
These units need not be the same as the units used within the project.
UNITS DEPTH units This keyword sets the input units for depth information. See
table Table 25.3 for recognized length units.
UNITS DIAMETER units This keyword sets the input units for the well diameters. See table
Table 25.3 for recognized length units.
The UNITS DIAMETER keyword take precedence over the UNITS keyword. If UNITS
DIAMETER is not set, the units set with the UNITS keyword are applied to the data.
Note The use of upper and lower case is important for the units symbol.
Table 25.3 Recognized event file length UNITS (units)
Recognized length Conversion Factor from

Name of length unit
units units to meters
m 1.0000E+00 metre
METRES 1.0000E+00 metre
dm 1.0000E-01 decimeter
cm 1.0000E-02 centimeter
CM 1.0000E-02 centimeter
mm 1.0000E-03 millimeter
km 1.0000E+03 kilo metre
mi 1.6093E+03 mile
NauMi 1.8520E+03 nautical mile
yd 9.1440E-01 yard
ft 3.0480E-01 foot
FEET 3.0480E-01 feet
in 2.5400E-02 inch

Wells node
Examples
Example 1
-- This is a comment line

UNITS FIELD
WELLNAME WELL-1
01/01/1990 perforation 4000 4020 .5 0
01/11/1992 perforation 4100 4200 .5 0
WELLNAME WELL-2
01/01/1990 barefoot 3790
Example 2
-- Next line is also a comment line

-- DD.MM.YYYY WELLNAME EVENT DEPTH1 DEPTH2 DIAM SKIN
01.08.1992 Q13 perforation (SAND_1) 10 30 .5 0
01.09.1992 Q13 perforation 30 500 .5 0
Export well deviation surveys

FloGrid can export well events in the proprietary GRID format. In this way edits to wellpaths
made in FloGrid can be saved to file.
GRID
Specify the location of the GRID format control file to be created. A file of the same root name
with the extension .dev is also created to hold the actual deviation data referenced by the
control file.
Hint If deviations are exported it is the visual representation that appear in the output files.
If the original target points of a planned well are required, switch the deviation
processing to None (using the Properties dialog) before exporting the deviation files.
Export Well Events

FloGrid can export well events in the proprietary Schedule format. In this way edits to events
made in FloGrid can be saved to file.
Schedule
Specify the location of the Schedule format event file to be created.

Wells node
Well node
This section lists the menus available by right-clicking on the node representing a well in the
node tree. Those options not requiring a well planning license feature are documented in "Wells
Data" on page 374.
Edit Wellpath
Opens the Well Editor, which enables you to modify the points making up the wellpath. The
Edit Wellpath panel also opens. Editing behavior is controlled by options under the Edit menu,
by toolbar buttons around the 3D Viewer, and by options on the dialog.
Caution Editing the points making up the wellpath changes the measured depths associated
with the points. This causes logs and markers to be repositioned, affecting any
resultant property population. You should normally only consider editing the
target points for planned wells.
When digitizing points on the wellpath the frame of reference is determined by the objects you
are picking upon. The Well Editor automatically takes the pick location to be on a picked object,
if any. If it is necessary to digitize points in space, rather than on objects in the 3D Viewer, it is
recommended that the 3D Viewer is locked into either a top or side view, as this can help to
remove the confusion as to the point’s location.
The location of a picked target point can be moved vertically away from the picked point by
specifying depth constraints, based upon chosen geological features, before making the pick. In
this manner target points can be constrained to lie, for example, in the middle of a geological
layer.
If the well being edited is a lateral, the first point (the connection point on the parent well) is
treated specially. The point is constrained to lie on the parent well section.
The following editor modes are used to control interaction with the Well Editor through the 3D
Viewer. These modes can be selected from the main window’s Edit menu, or by selecting the
appropriate toolbar button.
Digitize
New points forming the wellpath are created clicking with the left mouse button in the 3D
Viewer. This mode is the default mode if no well deviation is yet defined.
As described above, it is recommended that you click on visible objects in the 3D Viewer (for
example, surfaces, grid cells) to avoid ambiguity as to the location of the pick—picking in space
may result in the point being offset in the third dimension (orthogonal to the viewing plane)
requiring the point to be later moved.
The new point may be vertically offset from the picked location if a new target point depth
constraint is specified in the Edit Wellpath dialog. If such a constraint is selected, picks in space
are not allowed. In some cases the final target point location may be ambiguous when using the
specified constraint (for example, specifying to constrain the point to the middle of a geological
layer in the vicinity of a reverse fault). In this case you are asked to resolve the ambiguity, and
presented with a list of possible locations. You are also told if it is not possible to use the
constraint with the current pick.

Well node
Digitizing new points on an existing wellpath
In order to digitize one or more new points on an existing line or polygon, you must first select
a line segment to which the new points are to be added. This is done by changing to Select mode
and then clicking over the desired line segment, whereupon the selected segment is highlighted.
Once a segment is highlighted, further picks in Digitize mode add new points in between the
points delimiting the highlighted section. Each time a point is digitized, the display is updated
to indicate the new active segment to which the next digitized point is added.
Digitizing new points at the end of an existing wellpath

To extend an already digitized wellpath you must first select the last point. You do this by
changing to Select mode and then clicking on the last point, whereupon it is highlighted. Once
a point is highlighted, further picks digitize new points. Each time a point is digitized, the
display is updated to mark the new point as the active point to which the next digitized point is
connected.
Hint As an alternative to switching to and from Select mode, to select points or line
segments as described above you can perform the same operation by using the right
mouse button, while holding down the Ctrl modifier.
Deleting points while digitizing

The Backspace (or Delete key) deletes the currently selected point. This can be done in and
out of Digitize mode.
Hint As the most recently digitized point is typically highlighted, successively digitized
points can be deleted (undone) using the Backspace (or the Delete key).
Select / Move
Nodes of the wellpath can be repositioned by selecting and dragging the nodes with the mouse.
If a well deviation is already defined, this is the default mode when the edit session starts.
Hint Use of the constrained drag mode is recommended to reduce the confusion as to the
final location of the point being moved. Alternatively it is recommended that the 3D
Viewer be locked into either a top or side view.
You can move the whole wellpath being edited in a rigid translation, by dragging using the right
mouse button with the Ctrl modifier held down. Note that if you are editing a lateral, the
constraint on the first data point being on the parent wellpath still applies, so the wellpath snaps
to the closest available permissible location when this operation is complete.
Delete
When the Well Editor is in this mode, you can delete points by clicking on them. If both the
Ctrl and Shift modifiers are held down as the mouse is clicked, all points between the last
deleted point and the current point, inclusive, are deleted.
Hint The Delete key (or Backspace) can be used to delete the currently selected point
when in Digitize or Select/Move mode.

Well node
Constrain Drag
If this option is checked (with the Well Editor enabled) dragging of nodes is constrained to be
done along one of the three major axes (the drag cursor reflects this mode). Once a drag has been
started, movement is only allowed in the chosen direction.
To change the direction of movement, return the cursor to the original location of the node. It
should then be possible to start movement along a different axis.
Hint Once dragging is under way in the chosen direction, move the cursor away from the
point being dragged. This avoids accidentally changing the direction of constrained
movement if the mouse passes over the original data point.
Edit On
Once the Well Editor has been enabled, this option allows you to toggle between editing mode
and normal 3D viewing.
Edit | Export
Exports the wellpath currently being edited to an ASCII file.
Note No measured depths are exported using these options. Use of the Export Well
Deviations Surveys option from the drop-down menu (obtained by right-clicking on
the wells base node in the node tree) is recommended.
Export XY
Exports a file with only XY coordinates.
Export XYZ
Exports a file with XYZ coordinates.
Cancel Edit
This has the same effect as clicking Cancel on the Edit Wellpath panel.
Commit Edit
This has the same effect as clicking OK on the Edit Wellpath panel.
Edit Wellpath panel

The panel shows the nodes making up the wellpath in tabular format.

Well node
Note Note that if you are editing a lateral, the first data point is constrained to be on its
parent’s deviation, you are not able to edit the x, y, or z co-ordinates of this point, but
you can change the measured depth of the connection point. Following manual
changes to the data table, click on Apply to update the 3D Viewer edit line; if this is
not done these changes are lost if any edit is made using the 3D Viewer.
Clicking on OK in the panel commits the edit. Clicking on Cancel cancels the edit. Both
operations close the panel.
New Target Point Depth Constraint

The panel also allows control over the depth constraint of newly-inserted data points. By
default, if no constraint is selected, new target points are added at the pick location. Selecting a
constraint moves this pick point vertically according to the chosen constraint.
Constraint
Select a constraint from the drop-down list. This can be a structural framework, a simulation
grid, or a surface.
Option
If appropriate (dependent on the chosen constraint), select the option to identify how the
constraint should be applied. For example, if the constraint is a structural framework, the
options allow you to choose to center the target point in the center of the chosen geological layer.
Offset
The final position of the target point can be offset from the calculated location by the amount
chosen. This depth offset can be positive or negative.
Note When you choose to constrain new picked target points, you need to pick on an object.
Drilling Constraints
If you choose the option to apply drilling constraints, the well deviation is calculated from the
target points. The requested maximum dog-leg severity and kick off limit is used to generate the
wellpath.
Note This causes measured depths to be recalculated (the depth shown in the table is that of
the closest point on the calculated trajectory to the target point). The calculation is
carried out when you click on Apply or OK. When you click on OK the edit is
committed and the 3D Viewer updates to show the calculated wellpath. The calculated
wellpath can only be seen after the edit is committed.
Dog Leg Severity

Enter the maximum permitted curvature of the wellpath, in degrees per 100 feet. Note that this
is just a requested maximum.
Kick Off Limit

Enter the maximum permitted offset of the start of the calculated wellpath from the first target
point.

Well node
Note The Well Properties dialog can also be used to switch the processing applied to the
points making up the wellpath.
Vertical Well Generation

Two buttons are provided to aid the generation of new vertical wells during digitizing.
Make Vertical From Wellhead

Uses the well’s defined wellhead location and initialize the table’s data points accordingly.
Make Vertical From 1st Point

Uses the data in the first row of the table as the wells location.
In both cases the well starts just above, and ends just below, the volume of interest.
Note If no geological features are present, the volume of interest is undefined, and you need
to enter the well top and bottom yourself.
In both cases you are warned if existing data points are discarded. These operations are
inappropriate for laterals, when the options are disabled.
Well Event Manager

Select the wells in either the node tree or the 3D Viewer whose events you are interested in, and
select the Edit Events... option. The Well Events Manager panel is displayed showing all the
selected wells under a Chosen Wells list.
If a well is selected from the Chosen Wells list then the events associated with this well are
shown in chronological order (events using symbolic dates are listed last) in the Events for
Selected Well list.
There are three ways of selecting a well. The well can also be selected using the 3D Viewer, the
node tree or from the list in the dialog. Whichever mechanism is used, the other two views
update to reflect the selection. This makes it very easy to select the correct well.
Note If more than one well is selected in either the 3D Viewer or the node tree then the
current selection in the Well Event Manager panel is lost.
Once a well has been selected in the Well Event Manager panel the Add… button is enabled
allowing events to be added to the well.
If a well event is selected from the Events for Selected Well list then both the Edit... and
Delete... buttons are enabled.
Delete... allows you to delete the selected event. You are asked to confirm this operation.
Edit... allows you to edit the selected event using the Edit Event dialog.
If a well is deleted whilst the Well Event Manager panel is being displayed, it is removed from
the Chosen Wells list and any panels being used to edit the events are closed down.

Well node
To change the chosen set of wells, choose a new selection using either the 3D Viewer or the
node tree, and choose the Edit Events… menu option. The Well Event Manager panel should
be refreshed with the new set of wells.
Create Event panel

Creates a new event. A panel appears, asking you to select the type of event and the event start
date. The date may be chosen as a Schedule symbolic date; a list of valid dates is given. Once
these values have been entered, click on OK to create the new event. You will automatically be
taken to the Edit Event panel to define the remaining event parameters, as described below.
Edit Event panel

Modifies the selected event. The fields shown on the panel vary dependent on the type of event
(perforation, barefoot, squeeze, plug) chosen:
Date
The date on which the event occurred. This may either be a normal date, or a Schedule symbolic
date.
Comment
An optional comment to be associated with the event.
Shift
Used when aligning event dates to simulation dates. If Earlier is chosen then the well event date
is shifted to the first earlier simulation date. If Later is chosen then the well event date is shifted
to the first later simulation date. If Ignore is chosen then the event is shifted to the closest
simulation date.
Note The shifting only affects the way the well events are displayed in the 3D Viewer and
does not directly affect the well event date.
Start MD
The measured depth at which the event is located on the selected well.
End MD
The measured depth at which the event finishes (not applicable for a barefoot or plug event).
Diameter
The diameter of the completion (not applicable for a squeeze or plug event).
Skin
The skin associated with the completion (not applicable for a squeeze or plug event).
Note that if the Pick Start/End Points option is checked, you are asked to click on the well in
the 3D Viewer in order to define the completion extent.

Well node
Animating Events
Use the Well Events Manager dialog described above to select the well whose events you wish
to animate. On the dialog are a set of video controls that are enabled once you select a well with
associated events.
The video controls in the Well Events Manager dialog can be used to animate over only those
timesteps associated with that particular well's events.
Note These controls are different from the video controls in the 3D Viewer and in the
Timestep panel, as these animate over all timesteps.
When an event is selected in the Well Events Manager the model in the 3D Viewer is moved
to that timestep. This is reflected in the Timestep panel, if it is displayed.

Well node
Well node
Core Analysis
Chapter 26
Core
The Core Analysis option launches the SCAL module to provide integrated core, relative
permeability and capillary pressure functionality for use when doing multi-phase and or multi-
level upscaling (FloGeo). For more information on SCAL see the "SCAL User Guide".
The module has facilities to:
• import laboratory data
• perform quality control (such as curve smoothing)
• group data according to lithological parameters and end-point values
• transform the laboratory data into rock curves suitable for input to simulators such as
ECLIPSE
• automatically assign these curves to grid cells (according to a set of user defined rules, for
example as a function of porosity, permeability or lithological parameters).
A key use of the SCAL module in FloGrid or FloGeo is to process SCAL records that handle
the data generated or used during multi-phase and multi-level upscaling.
FloGrid User Guide Core Analysis 645

Core
646 Core Analysis FloGrid User Guide
Core
2D Mapping Canvas
Chapter 27
Introduction
The 2D Mapping Canvas module is a 2D mapping module. Its primary purpose is to
compute and display a two-dimensional regular mesh. You can also use it as another way of
representing reservoir data (especially a map or a grid) as it allows contour computation for any
kind of grid. Common workflows in the module are outlined in "Common Workflows" on
page 674. This chapter also contains information on the following:
• Data types, data management and the 2D Tree (see "Basic functionality" on page 648 and
"Tree" on page 649)
• Displaying maps, contour lines, scatter sets, fault traces, markers, wells, simulation grid
properties and boundaries (see"2D Viewer" on page 660). You can also control the
appearance of the displayed data (see "2D Viewer options" on page 669).
• Creating data such as Mesh Maps (see "Create Mesh Map or Interpolate Map" on
page 661.), Scatter Sets (see "Create Scatter Set" on page 663), Contour Maps (see "Create
Contour Map" on page 663)and Fault Traces (see "Create Fault Trace" on page 663). You
can also edit already existing data (see "2D Viewer Editors" on page 671).
• Digitizing (see "Edit menu" on page 653)
• The standard View menu options are detailed in "Module common options" on page 88.
You can also set your zoom preferences (see "Zoom Preferences" on page 660). Note the
scope of zoom has no effect in the 2D Mapping Canvas.
• Setting pen styles and editing axis properties for graphs (see"Display menu" on page 654).
• Controlling the appearance of the graph window (see "Options menu" on page 658).
• Translate mode (see "Others menu" on page 659).
• And technical background information on the mapping packages used (see "Mapping
Packages" on page 839).
FloGrid User Guide 2D Mapping Canvas 647

Introduction
Basic functionality
This section covers the basic functionality available in the module.
Data management
The 2D Mapping Canvas module is notified each time a new model is imported or created in
the 3D Viewer. The 2D Mapping Canvas module informs the 3D Viewer each time a change
occurs. In the 2D Mapping Canvas module you can manage your data association as well as
exporting all the data that can be generated or updated.
Except boundaries all the data that can be updated or created can be exported in a file. For
further information see "Map" on page 651.
Data types
Note Well markers, well deviations, 3D property grid, boundaries are not editable in the 2D
Viewer, but the functionality is available in the 3D Viewer (wells, 3D property grid,
boundaries) and the Log Canvas (markers).
Regular Mesh Maps

• You can display mesh maps by coloring the node values or by contouring the node values.
• You can create and update mesh maps, without interpolation, using Mesh Map Calculator
and with interpolation using the Create Map panel.
For a mesh interpolation your input data can be a mesh, a selection of K Layers from a
structured or unstructured property grid, a contour, a scatter, and some fault traces.
You can mix the different data types together, except for mesh and K Layers.
Note Mesh map editing is not supported by the 2D Mapping Canvas module but is
available in the 3D Viewer.
Markers
Markers are displayed as 2D points.
• You can display them with or without their values.
Wells
Wells are displayed as 2D spline lines with a top projection.
Scatter sets
Scatter sets are displayed as 2D points. You can display them with or without their values.
• You can create or update scatter sets using the editor. Alternatively you can create them by
generating a Thickness scatter set between two surfaces using the well markers.
Fault Traces
You can display fault traces as 2D lines or polygons.
648 2D Mapping Canvas FloGrid User Guide

Introduction
• You can create or update fault traces using the editor.
Contour lines
You can display contour lines as 2D lines (closed or open) or 2D points.
• You can display them with or without their values.
You can create and update contour lines by editing existing ones or by extracting the data from
a map.
Structured and unstructured property grids

• You can display property grids by coloring each cell with its center values or by contouring
the cell center values.
Boundaries
Boundaries are displayed as 2D polygons. Boundaries must be rectangular.
Tree
The tree gives you a good representation of the organization of your data (name, number, type,
dependencies). It is also a good place to setup specific items.
Note The 2D Tree behaves in a very similar fashion to the 3D Tree. See "Using the data tree"
on page 334. There are some differences, which are described in this section.
Note Drag and drop from tree to 3D Viewer is not supported by the 2D Mapping Canvas.
A right-click on each node displays the main popup menu. The options unless otherwise noted
are:
• Show information
• Edit
• Change Coord system...
• Set Property...
• Set Property Unit...
• Add to view
• Remove from view
Shift right-click on each node displays a specific popup menu.
Note All the root nodes, the surface nodes and the simulation grid nodes do not have a right-
click popup menu
Note Fault traces have a Shift right-click popup menu, which allows you to set the
transmissibility for each of them. This feature is only used in Conpac, the mapping
package (see "Conpac" on page 847).

Introduction
Available nodes
The following data nodes are available in the 2D tree:
Table 27.1 Nodes available in the 2D tree
Notes on Pop-up Menu

Data Node
options
Unassociated Surface
data Surfaces root node
Unassociated Map data Export Map data (generic

Maps root node ASCII file)
See "Map" on page 657.
Unassociated Contour Edit opens the Contour Lines
Lines Contour Lines root node Editor.
Export Contour lines data
(generic ASCII file).
Unassociated Scatter Edit opens the Scatter Lines
Sets Scatter set root node Editor.
Unassociated Fault Edit opens the Fault Traces
Trace Fault traces root node Editor.
Export Fault traces (CPS ASCII
file)
Unassociated Well data Add to view and Remove from
Wells root node view.
Unassociated Well Add to view and Remove from
Markers Well markers root node view.
Unassociated The Show information,
Boundaries Boundaries root node Change Coord system..., Set
Property..., and Set Property
Unit... options are not available.
Unassociated FloGrid
Models (Simulation FloGrid Models root node
Grid)
Surface and its The Horizon node has a Create
associated data. Surface node or Horizon node Thickness Scatter Set option,
which opens the appropriate
panel.
Map and its associated Map node. Export map data (generic
data. The bitmap reflects its property ASCII file)
See "Map" on page 657.
Contour. Contour Lines node. Export contour lines data
There is no associated The bitmap reflects its property (generic ASCII file).
data
Scatter set. Scatter set node. Export scatter sets (generic
There is no associated The bitmap reflects its property. ASCII file)
data.

Introduction
Table 27.1 Nodes available in the 2D tree (Continued)
Notes on Pop-up Menu

Data Node
options
Fault trace. Edit opens the Fault Trace Editor.
Fault trace node
There is no associated Export Fault traces (CPS
data ASCII file)
The Show information,
Change Coord system... , Set
Property... , and Set Property
Well. Add to view and Remove from
Well node view.
There is no associated
data.
Well marker. Add to view and Remove from
Well marker node
There is no associated view.
data.
Boundary and its The Show information,
associated data. Boundary node Change Coord system..., Set
Property..., and Set Property
3D property grid. See "3D Grid" on page 657.
Simulation Grid Node
The associated data are
the grid properties.
3D grid property. Simulation Grid Property Node. Add to view and Remove from
The bitmap reflects its property. view.
Map
Tick the node to display this menu.
• "Contour Display Controls" on page 663.
• Generate Contours - Computes and extracts contours from the current map.
• "Interpolate Mesh Map" on page 665.
3D Grid
Tick the node to display this menu.
• "Select K Layer" on page 666.
• "Select Time Step" on page 666.
Drag, drop and dependencies

The drag and drop mechanism is used to manage data associations in the application. The tree
reflects the dependencies. If a data node contains other data it is a parent node and its dependent
data nodes are children.

Introduction
You can change association between nodes easily by using drag and drop. Drag and drop is only
permitted if the association is correct. Dependencies between items are specified by the data
type of each item.
The permitted dependencies are:
• Surface nodes can contain map, contour lines and scatter set nodes.
• Map nodes can contain fault traces.
• Contour lines can be associated to a map but note that they do not become a child of the
map.
• Horizon nodes can contain well markers
• If data is unassigned its node belongs to its type root node. For example, surface data belong
to Surfaces root node, map data to Map root nodes, etc. The exception is that there are
markers that belong to the Unknown Horizon.
Note Each 3D simulation grid model node contains one node with all the continuous real
properties of this grid.

Introduction
Edit menu
Note No options are available in normal mode.
In Digitize mode the following options are available:

• "2D Viewer options" on page 669
• "Select/Move" on page 671.

Edit menu
Display menu
Styles
Styles allow you to specify the pen style for each type of display item. Each style item on the
menu opens an associated panel. For further information see the descriptions of the setting
panels on pages 665 to 666.
Axis Property Editing panel

There are several ways to open this panel for a particular axis:
• Double-click on the required axis.
• Click on the axis with the Shift key held down.
• Right-click on the axis, and choose the Show Edit Box option.
• Use the X Axis Settings or Y Axis Settings under the Display menu option, if available.
This will bring up the appropriate axis panel for the active (highlighted) plot.
Each axis has its own set of properties that you can set individually using one of these panels.
The options are separated onto five tabs, each dealing with one aspect of axis appearance. A
sample axis, showing approximately what the axis would look like with the current settings is
present to the right of the tabs for vertical axes, and below the tabs for horizontal axes.
Axis labels
You can control how the axis title and units appear using this tab.
Title
Edits the title of the axis.
Units
Selecting a different unit changes the units displayed on the axis, and transforms the data.
Labels, show title / Labels, show unit

Switches the display of the axis title or units on and off.
Labels, axis sizes...

You can set the sizing individually per axis, or set to be the same for all axes.
Axis plots
Displays the plots attached to the axis you are editing. You can also open the Data Style panel
for these plots; select the required plot, and click on Edit Selected Plot.

Display menu
Axis ticks
Controls the appearance of the ticks on the axis, and their associated labels at major intervals.
Note Note that the major (heavier) ticks are those displayed at the longer intervals. The
minor (lighter) ticks are displayed at the shorter intervals. The appearance of ticks also
affects the appearance of the grid, if the grid lines are visible. So, for example,
switching the minor ticks off would also remove the closely spaced grid lines
associated with these ticks.
There are two versions of this tab, one for normal numerical data, and one for dates. The
common elements are described below, followed by the different settings for numeric and date
axes.
Common options
Label the ticks
Displays numerical labels on the major ticks.
Show major
Displays the major ticks.
Show minor
Displays the minor ticks.
Note All three of the above selections are usually defaulted to ON.
Elements seen only in numeric panels

Major spacing
Sets the spacing of the major ticks. It is set automatically by default . Only sensible values are
accepted; for example, if the setting would result in too many tick marks, it is rejected.
Format
Alters the appearance of the numbers labeling the ticks. You can choose between normal and
scientific notation (that is including an exponent). You can also set the number of decimal places
shown by using the up and down buttons controlling the number. A sample format is shown
below the option selection area.
Elements seen in date panels

Time format
Displays seconds and selects the separator used between hours, minutes and seconds.
Note Time is only shown for times varying over less than a day.

Display menu
Date format
Varies the format of the date using this set of drop-down selections. The final format is of the
form xx:xx:xx where each of the xx’s can be day, month or year in several formats, and the
separator can also be one of several options. Each field can also be blank to allow shortened
dates (for example 11/9’, ‘Sept, 99’ or ‘1999’).
Axis range
Controls the range shown by the axis and some other related properties, such as its
linear/logarithmic setting. You can override the various automatic ranging options by typing the
required range into the Visible Range text boxes.
The settings are:
• Round range - rounds the range down at the bottom and up at the top. Normally the range
is set at the exact data cut-off.
• Limit range - limits the data range (allowing for rounding if set). However, if the data
changes to include data points outside the original range, then the limit also changes to
match.
• Log - switches the axis between log and linear display. In log display, data at or below zero
is ignored.
• Invert - inverts from the usual left/right and bottom top convention of increasing data.
• Margin - forces the axis range to allow a margin around the actual data range.
Note The ranging options only apply when you have not applied some other ranging device
to the plot, such as explicitly typing the range, or using one of the zoom options. To
return to the automatic behavior select Unzoom Completely from the View menu.
Axis style
Color
Affects all of the elements of the axis - labels, title, and tick marks.
Grid lines
Removes the grid lines associated with the ticks for this axis.
Note The Grid Panel option switches off X and Y grid lines at once.
Bar
Displays the axis line.
Endbars
Controls the appearance of the end of the axis line, which you can see best if the major ticks are
off.
Border
Draws a border round the complete axis.

Display menu
Map
These options are available only if a map is displayed inside the 2D Viewer.
• Generate Contours - computes and extracts contours from the current map.
3D Grid
• "Select Time Step" on page 666.
• "Extent panel" on page 667.
• Move K Layer Up / Move K Layer Down - moves to the K Layer above or

below the current one.
• Clear Screen - clears the 2D Viewer.

Display menu
Options menu
Add/Remove Components...
Controls the overall look of the graph window, and which layout and behavior components it
contains. Behavior components mostly control whether the menu and tool bar options appear,
but also more fundamental parts of the window, such as the status bar.
There are two tabs to this panel, one for the layout (Layout Components) and one for the
behavior (Window Components).
Layout components
Small graphs, legends etc. can be displayed or hidden using this tab. Simply select the item that
is going to be changed, and click on the appropriate Show or Hide button. Note that multiple
selection by Shift or Ctrl clicking is possible in the standard manner. Changes are
immediately reflected in the window layout without the need for applying the changes.
Window components
Again a simple selection and Show / Hide mechanism is used to adjust the properties of the
window. The majority of the options control Tool Bar and Menu options. Others include
Cursors, which controls the way the cursor changes shape, Resize Bars, which switches on
the bars between frames which can be adjusted by dragging, and also Status Bar and Tool
Bars, which can be used to switch these features on and off.

Options menu
Others menu
Translate
Puts the mouse into Translate mode. In this mode all the displayed items can be translated inside
the drawing area by clicking with the left mouse button
Normalize
Resets the extent so that it encompasses the displayed items only.

Others menu
2D Viewer
The 2D Viewer can display maps, contour lines, scatter sets, fault traces, markers, wells,
simulation grid properties and boundaries.
• "Popup menu" on page 660.
• "Panels" on page 660.
Popup menu
A right-click in the plotting area displays a popup menu, with the following options:
Map
• Generate Contours - computes and extracts contours from the current map.
3D Grid
This menu is available only if a simulation grid property is displayed inside the 2D Viewer.
• "Extent panel" on page 667.
• Select Time Step - opens the Select Time Step panel.

• Clear Screen - clears the 2D Viewer.
Layout
Note You cannot customize the layout.
The default layout is composed of a plotting area bounded by 4 axes. The left axis represents Y
and the bottom axis X. A color legend appears below if you are displaying a map or a grid
property.
Panels
Zoom Preferences
Allows you to fix the zoom step.

2D Viewer
Note Scope of zoom has no effect in the 2D Mapping Canvas.
Create Mesh Map or Interpolate Map

You can open this panel in Create mode or in Interpolate mode.
Hint The best way to enter all the parameters is to scan the panels from left to right.
The 2D Viewer displays the mesh map after you generate it.
Output
Note This tab is displayed in Create mode only.
Hint When a mesh map has been generated this panel is disabled. To enable it and create a
new map click on the New Map button.
Enter the map details first. Set a Map Name, a Property Type, a Surface (if necessary) and a
Property Unit. Once these are set, they filter the input data for you.
You must set the map geometry; there are four options.
Manual
Enter the following data:
• Areal Unit,
• Null value,
• X and Y Origin,
• Delta X and Y,
• Width and Height,
• Nx and Ny,
• Rotation Angle, if necessary.
• The Z axis orientation.
Boundary
Enter a boundary in Use Boundary popup menu. This retrieves X and Y Origin, Rotation
Angle, Width and Height from the boundary. All you need do then is enter Delta X, Delta Y,
Null Value and Areal Unit.
Current display
Use the current display. This retrieves X and Y Origin, Width and Height from the current
display. All you need do then is enter Delta X, Delta Y, Null Value and Areal Unit.
Existing map geometry

Use existing map geometry. To do this select a map node in the tree; this sets all the values using
the data from the selected map.

2D Viewer
Markers
Displays the available markers.
Attach to surface markers

The surface is specified in the Output panel.
Unassigned
These markers are not assigned to any surface.
If the selection remains blank, you either have no markers, or your markers do not match the
property log. Note that the property is the one defined in the Output panel.
Scatters
Note You can only select one scatter at a time .
Displays the available scatter sets. These options are similar to the options for the markers list,
(see "Markers" on page 662).
If the selection remains blank, you either have no scatter sets, or your scatter sets do not match
the property. Note that the property is the one defined in the Output panel.
You can select the unknown property scatters by clicking on Show Unknown Property Type.
Fault traces
Displays the available Fault Traces. These options are similar to the options for the markers
list, (see "Markers" on page 662).
Hint When you grid a structure map you can choose to use the fault’s values.
Contours
Note You can select one contour a time.
Displays the available contours. These options are similar to the options for the scatter sets, see
("Scatters" on page 662).
Grids
2D Grid
Select a map name. The list displays the map that matches the property and the surface you have
selected in the Output panel.
3D Grid
Select a Simulation Grid model and select properties for gridding.
If the selected model has a property that matches your map the program displays a list of K
Layers. You can select the K Layers you want to use for gridding.
If this property is a recurrent one, a list of Time Steps is also available. You can select a Time
Step for gridding.

2D Viewer
Note It is possible to Sum or Average different K Layers or Time Steps.
Note The new dummy property ZCORN has been added to the list of properties.
Unchecking domain mismatch displays all the current simulation grid properties. They must
be continuous and real. If you check this button the property displayed matches your output
property name. This toggle button is unchecked by default.
Interpolate
Sets the interpolation algorithms and settings. There are two interpolation packages; Conpac
and CPS Convergent Gridder.
Note It is impossible to have good default parameters that handle most of the cases.
Resetting interpolation when the data selection changes lets the program compute the
interpolation settings for you. Different input data types need different parameters. If
you want to use your own parameters uncheck this box.
Conpac is the mapping package used in GRID. For more information see "Conpac" on
page 847. The Convergent Gridder is the CPS one. For more information see "Convergent
Gridder" on page 840.
Create Scatter Set

Specifies a Name, a Property and a Type for the scatter set. You can also enter a coordinate
system by clicking on Scatter Control.
Hint If you do not use this option a warning message informs you that you have not set
scatter controls. You can ignore it because the program automatically assigns the
FloGrid external coordinate system to your scatter set unless you specify otherwise.
When you press Create, the program creates an empty set and loads the Scatter Editor.
Create Contour Map

This option is similar to "Create Scatter Set" on page 663.
Create Fault Trace

Specifies a Name, and a Type (Sloping or Vertical) for a fault trace. You can also associate
your fault with a map using Set Map popup menu. When you click on OK, the program creates
an empty fault and loads the Fault Editor.
Contour Display Controls

Sets contouring parameters for mesh maps and 3D property grids. The contours are computed
from the mesh map nodes or from the 3D property grid cell centers. The contouring computation
is done by Conpac. For further information see "Contouring" on page 850.
At the top of the panel a comment displays the plotting units and the property unit.

2D Viewer
• The Property Unit is the one used to set major contour intervals and base contour.
• Contour spacing, label height, space between labels, and minimum contour spacing are
shown in plotting units.
Generation
Sets contouring parameters.
Major intervals
Sets the interval between major contours.
Min. spacing
Specifies the minimum gradient or spacing between contours.
Note Conpac draws two successive contours only if their normal distance is superior to the
Min. Spacing value.
Subdivisions
Defines the number by which the Major Interval is divided. This is an integer value.
For example if the Major Interval is 100 meters and the Subdivision 5, the minor interval is 20.
Base contour
Defines the start value for contouring.
For example, if you have a elevation map with no values under 1000 meters ,you can start to
contour from 1000 meters.
Contour quality
Increases the quality of the contour display by smoothing sharp angles. You can give an integer
value between 1 and 10.
Note This option also increases the computation time. It is not always necessary to set it to
maximum, because after a certain point the quality may not improve noticeably. It is
up to you to find the correct compromise between computation time and quality.
Use Fault
Uses the fault geometry to contour.
Note For contouring, unlike interpolation, the fault elevation is not taken into account. Only
x and y apply.
Draw box
Select what you want to display.
• Mesh Color Fill - displays the mesh map without any contours.
• Color Fill Contour - colors the intervals between contour lines.
• Contours - draws the contour lines.

2D Viewer
Labels
There are two Label Setting options, one for major labels and one minor labels. This allows
you to have a different layout for both at the same time.
Draw label
Displays or hides the labels. By default they are hidden.
Label height
Specifies the height of the contour.
Space between labels

Defines the distance between labels in a contour line.
Min. contour spacing

Defines the normal distance between two neighboring labels of two different contour lines. This
distance is the minimum allowed value to enable the label to be drawn.
Decimals
Sets the number of decimals you want to display. For example, it is useful to draw labels for
properties with value between 0 and 1.
Interpolate Mesh Map

This is similar to the Create Map panel, (see "Create Mesh Map or Interpolate Map" on
page 661).
Map contours settings panel

Specifies the map contour pen styles for major and minor contours.
3D grid contours settings panel

Specifies the 3D grid contours pen styles for major and minor contours.
Contours settings panel

Specifies the pen styles for digitized or extracted contours. You can choose whether or not you
wish to display labels and to specify their height and spacing. You can choose the maximum
number of decimal places you want to display.
Note Force label drawing forces the drawing of contours for each label. This means that
the intersection criteria are decreased and that the spacing between labels is increased.
Scatters settings panel

Specifies the Scatters pen styles and is similar to the "Contours settings panel" on page 665.

2D Viewer
Note For scatters with more than the max value the settings are not taken into account. This
maximum value, by default 500, is editable. It allows you to make a distinction
between small scatters and large one.
Fault traces settings panel

Specifies the Fault traces pen styles. You can customize the color fill inside sloping faults.
Hint Select NONE in the Color Fill drop-down menu to disable this option.
Markers settings panel

Specifies the Markers pen styles and is similar to the "Contours settings panel" on page 665.
Wells settings panel

Specifies the Wells pen styles.
Boundaries settings panel

Specifies the Boundaries pen styles.
Select K Layer
Selects the 3D Grid K Layer for display.
Select Time Step

Selects the 3D Grid Time Step you wish to display in the 2D Viewer.
• Time steps are only available for recurrent properties.
Contour value panel

Specifies the Contour Z values.
• First, Next, Previous, Last allows you to swap from one contour line to another.
• You can close or open the current contour.
• You can also set a delta value, which is added to or subtracted from the last current value
to generate the new one. Only contour line values that are undefined can be computed by
this way.
• A read only table give you the X and Y positions for each point of the current contour line.
Note The current contour is highlighted in the 2D Viewer.
This panel is linked to the Contour Editor, and its behavior changes with the Editor mode. In
Digitize mode all the contours lines are in the buffer. In Select/Move mode only the selected
one are in the buffer. This option is not available in Delete mode.

2D Viewer
Note This panel displays the coordinate system in which you are working. Only the Horizon
and Unconformity properties are affected by the Z Axis orientation.
Scatter value panel

Specifies the Z values of the Scatters. A table gives you X, Y and Value for each scatter. X and
Y are read only. You can only edit the Value column.
This panel is linked to the Scatter Editor; its behavior changes with the Editor mode. In
Digitize mode all the scatters are in the buffer. In Select/Move mode only the selected one is
in the buffer. This option is not available in Delete mode.
Note This panel displays the coordinate system in which you are working. Only the Horizon
and Unconformity properties are affected by the Z Axis orientation.
Create thickness scatter panel

Creates a thickness scatter set between two horizons. You load this panel from the top horizon.
The base horizon is automatically selected by the program and the name automatically
generated. However, you can change these settings in this panel.
Extent panel
Customizes the 2D Viewer extent. You can also set whether or not you want to work in
elevation or in depth. The scope defines the default behavior of the 2D Viewer extent. Three
types of extent scope are available.
Global
The default plotting area is the extent of all the data you have loaded into the application.
Normalize
The default plotting area is the extent of all the data displayed in the 2D Viewer.
User defined
Defines the default plotting area. It is useful when you are working in a special area of your
reservoir and you do not want to retrieve it each time you unzoom, remove model from the 2D
Viewer etc.
Hint If however you have, by translation or/and zoom, defined an area you wish to return
to, you can use the Actual Display Extent to save it as your work area.
Fault traces parameters panel

Specifies a fault trace behavior.

2D Viewer
Note These settings are important for the Conpac gridding algorithm only. For further
information see "Conpac" on page 847.
Transparency
Indicates the transparency of the feature. You can enter a value between 0.0 and 1.0.
0.0 means total opacity and 1.0 total transparency.
Check domain
Indicates whether the transparency is use or not, or whether the segment between two points
crosses the fault an odd number of times.
Not contour inside

Switches off the computation of contours inside for a sloping fault.

2D Viewer
2D Viewer options
This section covers data display in the 2D Viewer. Items that can be displayed are:
• "Maps" on page 669
• "Contour lines" on page 669
• "Fault traces" on page 670
• Scatter sets are sets of 3D points. See "Scatter value panel" on page 667. You can display
only one scatter set a time.
• Markers are sets of 3D points with a name. They cannot be edited in the 2D Viewer. See
"Markers settings panel" on page 666.
• Wells are set of 3D lines. They cannot be edited in the 2D Viewer. See "Wells settings
panel" on page 666.
• "Simulation grids (3D property grid)" on page 670.
• "Boundaries" on page 670.
Maps
Each time a 2D grid is displayed a new tool bar appears, which allows you to change the contour
display controls, load the interpolation panel or extract contour from map.
You can display a map in 4 render modes, each of which compute contours from the grid node
values, with the exception of the Mesh map color filled mode.
• The Contour lines and Contour color filled and contour lines options draw contours.
The Contour color filled and Contour color filled and contour lines options color inside
the contour lines between major contours.
You can specify the contouring settings. For more details see "Mapping Packages" on
page 839.
• The Mesh map color filled option draws the mesh map nodes in a color that corresponds
to their value.
Note You can display only one map at a time.
Contour lines
The Contour Lines are sets of 2D lines. They can be open or closed. You can edit them; and
display their values in the 2D Viewer. For more details see "Contour value panel" on page 666.
Note You can display only one contour map at a time.

2D Viewer options
Fault traces
The Fault Traces are sets of 3D lines. They can be single lines (vertical) or a polygon (sloping).
You can edit them.
Simulation grids (3D property grid)

Each time a 2D grid is displayed a new tool bar appears, which allows you to change the contour
display controls, or load the Interpolation panel.
The simulation grids are sets of 2D grid properties sorted by K Layers. You can display them
as a property grid. This property grid behaves as a mesh map, therefore you can display it in four
render modes, see "Maps" on page 669.
Note You can display only one grid property a time
Note You can customize the display by opening the 3D Grid contours dialog (see "3D grid
contours settings panel" on page 665).
Boundaries
Boundaries are sets of 2D lines; boundaries can only be rectangular. You can edit them in the
3D Viewer. You can use them to fix a window of interest when mapping.

2D Viewer options
2D Viewer Editors
When you create new data you are automatically in edit mode.
Note You cannot undo a command with 2D Mapping Canvas Editors.
Editors
The following editors are available :
• "Contour lines editor" on page 672.
• "Fault traces editor" on page 673.
• "Scatter sets editor" on page 673.
This section also contains information on the following:
• "Common Editor commands" on page 671
• "Toolbar" on page 672.
Common Editor commands

All the editors use the following commands unless otherwise noted:
Digitize
Keyboard and mouse button events:
• Left button - adds a point in the line.
• Left button (Double click) - adds a point and opens the line.
• Middle button - selects a contour segment or a point. Allows you to append point in line
• Right button- displays a popup menu
Select/Move
• Left button - selects a point, or a line. Deselects the current selection.
• Shift Left button - selects a point, or a line and keeps the current selection.
• Ctrl Left button - selects or deselects a point, or a line. Deselects the current selection.
• Right button - displays a popup menu
• Left mouse button, down and move (Shift, Ctrl, or whiteout) drags the current
selection
• Left mouse button up after move (Shift, Ctrl, or whiteout) crops the current selection
• Delete - deletes the current selection
Delete

2D Viewer Editors
• Left: Deletes a point, or a line.
Toolbar
Each editor has a toolbar with the following options:
Grid canvas show and Hide a Grid Canvas can help you to digitize.
Grid canvas show displays the cursor position in the status bar.
Grid Canvas
Allows you to add points, lines, etc.
See "Common Editor commands" on page 671.
Digitize
Allows you to select a point on a segment or a line. When one of these
is selected you can display a popup menu. This enables you to edit the
Select/Move selection, to move it or to delete it.
Hint When you want to delete a point in a line it is better to use the
Select/Move option. It is easy to delete the full line by mistake
with the Delete option.

This option is available for contours and scatters editors only.
Allows you to edit contour and scatter set values.
Edit Value Dialog
The values are stored in coordinate system of the model but edited in the
2D Viewer’s coordinate system. That means that if you type a Z value
in a 2D editor, this value must match the system you are working with.
• If the 2D Mapping Canvas module is set to work in meters, the
values you give must be in meters.
• If 2D Mapping Canvas is set to work with the Z axis in elevation,
Z must be entered (positive if above sea level, and negative if below
sea level).
• If 2D Mapping Canvas is working in depth, the Z value must be
given (positive if below sea level, and negative if above sea level).
See "Scatter value panel" on page 667 and "Contour value panel" on
page 666.
Contour lines editor

Digitize Popup menu

• Edit Value - see "Contour value panel" on page 666.
• Close Contour - closes the current contour line.
• End Contour - completes the current contour line edit.
Select/Move Popup menu

• Close contour - closes the contour lines selected

2D Viewer Editors
• Open contour - opens the contour lines selected
• Delete - deletes the current selection
• Edit - see "Contour value panel" on page 666.
Fault traces editor

This editor behaves almost like the 3D Viewer Fault Trace Editor (see "Fault Trace Data" on
page 370). In 3D a sloping fault trace has minor and major points, because it is represented as
upthrown trace and downthrown trace. Major points are used as delimiters for fault traces. A
trace becomes, in this case, the line between two major points.
Note As the 2D Viewer displays vertical fault traces as open lines and sloping fault traces
as polygons, minor and major points are not required. To commit a vertical fault trace
you need one major point that gives the position of the end of the first line. You can set
it by Ctrl-click or by using Edit | Set Minor/Major. In the 2D Viewer if you do not
specify any major point we take by default the middle of the polygon. To avoid the
minor and major problems we recommend that you use the 3D Viewer Fault Trace
Editor to edit sloping faults.
Digitize
• Left button - adds a minor point in the line.
• Ctrl-Left button - adds a major point in the line.
• Left button (double click) - adds a major point in the line, and for polygons closes the line.
• Middle button - selects a fault trace segment. This allows you to append a point in the line.
Scatter sets editor

Digitize
• Left button - adds a point.
• Left button (double click) - adds a point and opens the "Scatter value panel" on page 667.
Select/Move Popup menu:

• Edit - see "Scatter value panel" on page 667.

2D Viewer Editors
Common Workflows
Outlined below are some common workflows in the 2D Mapping Canvas module to assist you
in either model assembly or map generation for reporting purposes
Note The sections below give ‘high level’ descriptions of the workflows, not click-by-click
detail, but sufficient information is included to enable you to complete the process.
• "Creating isochores using well markers" on page 674.

• "Creating Scatter sets" on page 675.
• "Creating contour maps" on page 676.
• "Creating 2D Maps from 3D Models and Recurrent properties" on page 676.
Creating isochores using well markers

Background
One method of building a map based model in FloGrid is to start with a top or base surface and
build the remaining required surfaces using isochores (see "Building a simulation model from
maps" on page 42).
Care should be taken to ensure the isochore map is attached to the correct surface and referenced
to the correct surface when building a model
Isochores may be generated in FloGrid using loaded well marker data as follows:
1 Open the 2D Mapping Canvas using the button in the top toolbar or from the Tools
menu.
2 Expand the Well Markers node to see a list of the loaded well markers. Right mouse click
on the selected node to open the Create thickness scatter set panel.
3 In the Create Thickness Scatter set panel, provide a name or accept the default. From
the pull-down menu, select the required Base Horizon and click on OK. This creates a
thickness scatter set under the Surface node of the top horizon, (expand the Surfaces node
and the horizon node).
• If necessary the scatter set may be edited as described in "Creating Scatter sets" on
page 675.
4 At this point you can use Create | Mesh map to create a thickness mesh map.
5 Select Create | Mesh Map from the menu bar. Provide a name for the map and a Property
from the pull-down menu. Click on the pull-down menu then type ‘t’. This takes you to
the first property that begins with the letter t, in this case thickness. This functionality works
throughout FloGrid.
6 Select the surface to attach the map to and if appropriate, change the Property unit.
7 To set the Map Geometry, click on Use existing map geometry, which brings the 2D
canvas forward. Click on an appropriate map from the tree under the Surfaces node, to fill
in the map geometry, nodes and any rotation embedded in the map.
8 Click on the Scatters tab and select the scatter set.

Common Workflows
9 This is all the information required, so click on OK to create the mesh map.
The map is located under the surface node in the 2D canvas and in the tree in the main
FloGrid window.
Creating Scatter sets

Background
Scatter sets may be created in the 2D Mapping Canvas with any of the properties available
from the pull down menu. The scatter sets may then be gridded and used in the creation of a
structural framework, property creation or other appropriate workflow.
1 Click on Create | Scatter set in the top menu bar. In the resulting dialog, provide a name,
property and unit for the data set. Accept all the defaults.
2 Select the Digitize button in the top toolbar. Click points in the 2D Mapping Canvas.
All will have the null value of -1e+019 to start with.
3 Proceed as for Editing scatter data below.
Editing scatter data

1 Right mouse click on the Scatter Set node in the 2D Mapping Canvas tree. Select Edit...
from the drop-down menu. The 2D Mapping Canvas goes into edit mode.
2 Select the Select/Move button, in the toolbar at the top.
3 Click on one of the scatter points. It should turn red. Click with the right mouse button and
select the Edit Value option. Enter a new value in the panel and click on OK. The Delete
option deletes the scatter point.
4 If you have many points to edit, click on the Edit Value Dialog button to open the Set
Scatter Value panel. Clicking on a scatter point in the 2D Mapping Canvas module puts
the X, Y, and Z value in the Set Scatter Dialog box. Change the value and click on Apply.
Continue with other values.
Adding additional scatter points

1 Right mouse click on the scatter set node in the 2D Mapping Canvas tree. Select Edit...
from the drop-down menu. The 2D Mapping Canvas module goes into edit mode. Select
the Digitize button in the toolbar at the top.
2 Click in the canvas to create scatter points. All will have the null value of -1e+019 to start
with.
3 Once points have been created, click the Select/Move button, in the toolbar at the top
and proceed as for Editing scatter data.

Common Workflows
Creating contour maps
Background
Contours may be created and/or edited in the 2D Mapping Canvas and used as input to
creating mesh maps or to control extrapolation of a property away from existing control points.
This workflow concentrates on adding contours to a thickness scatter set to control extrapolation
1 Click on Create | Contour Map from the top menu bar. In the dialog, give the map a name,
property and a unit. There is no need to adjust Contour Controls.
2 Click on Create. The toolbar at the top of the 2D Mapping Canvas will have some new
buttons for use in digitizing contours.
3 Click on the pencil button, , (Digitize). Start to digitize with left mouse button clicks.
A double click ends digitizing and shows the Set Contour Values panel. Provide a contour
value and click on OK. You may also close the contour from here.
4 To edit a contour point, click the Select/Move button, in the toolbar, click on a point
and drag it to a new location. To delete an entire contour, click on the line between the
points; the entire contour should turn red. Click with the right mouse button and select
Delete from the pop-up menu.
5 Once digitizing is complete, click on the green tick button to save the new contours.
6 The contours may be incorporated in mesh map generation by selecting them from the
Contour tab in the Create | Mesh Map panel.
Creating 2D Maps from 3D Models and Recurrent

properties
Background
The 2D Mapping Canvas may be used to create 2D mesh maps of 3D properties present in a
FloGrid model. These maps be exported for use in report writing or presentations. Additionally,
since a Surface must be identified during mesh map creation, the map may be used for
subsequent model building in the FloGrid main window.
You may choose to map one or more K Layers, In the case of many K Layers, different
methods exist to sum or average the layers.
If FrontSim or ECLIPSE has been run on the model and INIT and RESTART files have been
loaded to FloGrid from the Simulation Manager, then recurrent properties (OilSat, WaterSat,
Pressure etc.) may be mapped for selected time steps for selected layers.
Displaying 3D property data in the 2D window

1 In the 2D Mapping Canvas, expand the FloGrid Models node to receive a list of the
properties in a model.
2 Click on one of the properties. Initially very little might display.

Common Workflows
3 Click on the K button, in the top toolbar to receive a list of the K Layers in the model.
Select one and click on Apply or OK. Use the blue triangles in the toolbar to play up and
down the K Layer list.
4 The button to the left of the K Layer button is the Display Controls button. Click on this
to set the display style of the map from the resulting dialog. At the very least, under Render
Mode, use the pull-down menu to select Color filled. Click on Apply.
Creating Mesh Maps from 3D or Recurrent properties

Follow Displaying 3D property data in the 2D window to review the properties in the 2D
Mapping Canvas.
1 Click on Create | Mesh Map. Provide a Mesh map name, Property, associated Surface and
if appropriate, Property unit.
2 Set the map geometry using either Existing Map Geometry or Using Current Display
(see "Creating isochores using well markers" on page 674).
3 If a boundary is required, make one in the 3D Viewer and apply it under Map Geometry.
4 Go to the Grids tab. Toggle on 3D Grid. Select the FloGrid model to use and the Property.
• If the property is a 3D property, (porosity, permeability, etc.), you may select one of
the K Layers from the list (or many, using a combination of Shift and Ctrl.
• If the property is a recurrent property, then a timesteps list is available in the bottom
panel. Once again, select one or several timesteps as outlined above.

Common Workflows
Common Workflows
2D Well Log Correlation Canvas
Chapter 28
Introduction
The Well Log Correlation Canvas is used to display well log curves, markers, and
marker correlation in a 2D view. Data are displayed along vertical measured-depth tracks,
grouped by wells. Multiple logs can be displayed. Each log is displayed in separate tracks. The
canvas also allows creation and editing of markers.
• "Selecting data for display" on page 680.
• "Removing data from display" on page 682.
• "Color shading the well logs" on page 685.
FloGrid User Guide 2D Well Log Correlation Canvas 679

Introduction
Selecting data for display
All data to be displayed in the Well Log Correlation Canvas are selected using the data tree
in the main FloGrid window.
Displaying wells
Select one or more wells in the data tree and select Add to Well Correlation Canvas from the
right-click popup menu.
Alternatively, select Add All Wells to Well Correlation Canvas from the Well root node
popup menu in order to display all wells.
Displaying well logs

Select one or more well logs in the data tree and select Add to Well Correlation Canvas from
the right-click popup menu. The logs are displayed and grouped by their corresponding wells.
Within each well group, the logs are ordered by property type and log type (that is, Original,
Primary, Lumped, Thresholded, or Synthetics).
Alternatively, select one or more well log property types and then select Add to Well
Correlation Canvas from the popup menu. In this case, all well logs assigned to the selected
properties are selected for display. Or select Add All Logs to Well Correlation Canvas from
the Well Logs root node popup menu in order to select all logs for display.
Note If well logs are selected for display before their wells are displayed, the logs are not
displayed in the canvas. However, the logs are automatically displayed when the wells
are later displayed.
Displaying well markers

Select one or more well markers in the data tree and select Add to Well Correlation Canvas
from the right-click popup menu. The markers are displayed and grouped by their
corresponding wells.
Alternatively, select one or more well marker surfaces and then select Add to Well Correlation
Canvas in the popup menu. In this case, all well markers assigned to the selected marker
surfaces are selected for display. Or select Add All Markers to Well Correlation Canvas from
the Well Markers root node popup menu in order to select all markers for display.
680 2D Well Log Correlation Canvas FloGrid User Guide

Note If well markers are selected for display before their wells are displayed, the markers
are not displayed in the canvas. However, the markers are automatically displayed
when the wells are later displayed.
Displaying well marker correlation

Well marker correlations are automatically displayed to correlate markers in neighboring wells.
The correlation is determined from the surface to which markers are assigned.
Note No correlations are displayed for unassigned markers (that is, markers that are assigned
to the Unknown surface).

Removing data from display
All data removals are done using the data tree in FloGrid’s main window.
Removing wells
In the data tree, select the wells to be removed and press Remove from Well Correlation
Canvas in the right-click popup menu.
Alternatively, select Remove All Wells from Well Correlation Canvas in the Wells root node
in order to remove all wells.
The selected wells, along with their well logs and markers, are removed from the canvas.
Removing well logs

In the data tree, select the well logs to be removed and select Remove from Well Correlation
Canvas from the right-click popup menu.
Alternatively, select the log property types and select Remove from Well Correlation Canvas
from the popup menu. In this case, all well logs assigned to the selected property types are
removed from the canvas. Or select Remove All Logs from Well Correlation Canvas on the
Well Logs root node popup menu in order to remove all logs.
Removing well markers

In the data tree, select the well markers to be removed and select Remove from Well
Correlation Canvas on the right-click popup menu.
Alternatively, select the marker surfaces and select Remove from Well Correlation Canvas
from the popup menu. In this case, all well markers assigned to the selected marker surfaces are
removed from the canvas. Or select Remove All Markers from Well Correlation Canvas in
the Well Markers root node popup menu to remove all markers.
Removing well marker correlations

Marker correlations are automatically removed from the canvas when their markers are
removed.
Zoom in/out
Select to zoom the view by a factor of 2.
Select to zoom out by a factor of 2.
Select to graphically define a depth range to zoom in.

Marker flattening
• To flatten the depth along a marker select , and then select the marker. All markers that
are assigned to the same surface as the selected marker are centered in the canvas.
Note When the view is flattened, the depth scale of the wells are no longer aligned.
• To revert to normal view select .
Creating markers
• Select to open the Create Marker window.
• In order to create assigned markers, select a surface in the surface list. If no surface is
selected, the new markers are unassigned (and are placed in the Unknown group within the
marker data tree).
• Then specify how the new marker(s) are named. Each marker name in FloGrid must be
unique. Several ways of generating marker names are provided in order to facilitate this:
• Select the Generate unique marker name Automatically option and leave the
Marker Name field empty.
This is the default setting. Unique marker names are generated automatically by
appending a unique number to the name of the selected surface. If no surface has been
selected, the text marker_ is used as the prefix.
• Select the Automatic option selected and enter text in the Marker Name field. Unique
marker names are generated automatically by appending a unique number to the
specified text.
• Deselect the Automatic option and enter an unique name in the Marker Name field.
An error dialog is shown if the field is empty or the specified name is already used for
an existing marker.
• Create the marker by clicking the mouse while the pointer is in the desired well track and
depth.
Note When an assigned marker is being created, a warning dialog is shown if there is an
existing marker, in the same well, assigned to the same surface. Answer Yes to this
dialog to continue creating the new marker. There are then multiple markers in that
well assigned to the same surface.
Note The depth and log value indicator shown in the status bar at the bottom of the canvas
can be used to guide the marker positioning.

Editing markers
• Select to edit marker depths.
• Click and drag the marker to the new position.
Notes
• A marker must first be displayed in the canvas for it to be possible to edit it.
• The depth and log value indicator shown in the status bar at the bottom of the canvas can
be used to guide the marker positioning.
Undoing marker edits

Marker edits can be undone one at a time by pressing the “Undo previous marker edit” toolbar
button. Pressing the “Undo all marker edits” toolbar button undoes all changes in the edit
history.
Notes
• The marker edit history is cleared whenever the Correlation Canvas is closed.
• The “Undo” and “Undo All” toolbar buttons are grayed out when no editing has been done
since the last time the canvas is opened.

Color shading the well logs
• Select to color shade the area left of the log curves.
This is the default color shading option.
• Select to color shade the area right of the log curves.
• Select to color shade both sides of the log curves.
• Select to display only the log curves.

The colors used for the color shading are selected from the color map associated with log
curve’s property type. This color map is the same as the one used for log display in the 3D
Viewer.

Expression Calculator
Chapter 29
Introduction
The Expression Calculator (distinct from the Programming Calculator) is an advanced
expression-based editor for properties (both fine scale and gridded) and mesh maps. It provides
a simple and consistent user interface for manipulating your data.
The calculator is accessed by selecting the object (mesh map or property) you wish to edit in the
data tree and picking Calculator... from the popup menu that appears when you right-click on
the object.
The remainder of this section is split into the common functions of the calculator and afterwards
the object-specific features are detailed ('object' here refers to either a fine-scale or gridded
property or to a mesh map, depending on what you are editing). Following that is a description
of the expression calculator language.
• "Common features" on page 688
• "Multi-Apply Calculator" on page 690
• "Expression calculator language" on page 695.
FloGrid User Guide Expression Calculator 687

Introduction
Common features
The Expression Calculator consists of the following areas:
• The two drop-down boxes in the top left corner select which object is to be edited.
• The button below this is used to create a new object.
It opens a panel where the attributes of the new object can be set. This panel, naturally,
depends on the type of object you are working with.
• Below this is the Edit Scope box.
This allows you to select whether the editing applies to the whole of the object, or just the
part that has been selected in the 3D Viewer (if this is possible with the selected type of
object).
• Below this is an Options box.
• The first option is the Default value. This is used with an IF expression. See "IF
statement" on page 696 for more details.
• The second option is the Error value. This value is substituted whenever an error
occurs in evaluating the expression. For example, if you entered the expression
1/Porosity the error value would be substituted wherever Porosity was zero.
• There is also an Advanced Options button. This is used to open a panel where object-
specific options can be set.
The expression is just saved • In the top right corner there are two buttons: Save Expression and Load Expression.
as simple plain text, so can These open a file selection panel where you can select a file to either save the expression
be edited later with any or load a previously saved expression into the expression box, respectively.
plain text editor.
• Below this is the Expression Box, where you type the actual expression.
The expression is evaluated to change the values in the object selected on the left. See
"Expression calculator language" on page 695 for the details of what constitutes a valid
expression.
• Below the Expression Box are a number of tools to help you build up expressions more
easily and quickly. When you click on the buttons or select an item from the lists, text is
inserted in the expression box at the current cursor location; alternatively, if some text is
selected in the expression box, this text is replaced by the new text.
• The large group of buttons contains numbers arranged in a calculator style and some
common operators and special syntax (IF, ELSE, etc.) When the buttons are pressed
they generally insert the text or symbol that is printed on the button face. However,
some buttons are ‘smart’ and insert additional characters and move the cursor into a
more convenient location so you can continue typing easily.
• The middle box contains a list of available functions. See "Function reference" on
page 697 for a description of each function. Just select a function from the list and it is
inserted into the expression box.
• The right-hand box contains a list of object names (variables) that are available for use
in your expression. This is generally a list of all the objects of the same type and in the
same model as the one you are editing.
688 Expression Calculator FloGrid User Guide

Common features
To use the Expression Calculator you select the object you wish to edit (or create a new one
with the Create button) and enter an expression describing the new contents of the object. When
you click on the Apply button the changes are made. Note that the panel remains open for you
to make additional changes if you so wish.
Hint If you are developing a new expression or are unsure as to what effect you expression
will have, you can create a new temporary object and modify that, without modifying
your existing data.
The Multi-Apply button allows you to apply the expression a number of times, using different
input and output data. This is most useful when dealing with multiple realizations, where similar
calculations must be performed a large number of times. See "Multi-Apply Calculator" on
page 690 for more details.

Common features
Multi-Apply Calculator
The Multi-Apply Calculator is an additional panel. It enables an expression to be evaluated a
number of times, using different input and output variables on each occasion. Use the Multi-
Apply button to open it.
• "Making life easier" on page 690.
• "Fill Pattern Match" on page 691.
• "RESCUE property editor features" on page 692.
• "Gridded property editor features" on page 694.
• "Mesh map editor features" on page 694.
The Multi-Apply Calculator parses the expression entered in the main Calculator and extracts
from it all the input variables, and the output variable taken from the second drop-down box on
the main Calculator window.
The Multi-Apply Calculator displays a table containing the following columns:
• The first column contains the output variable.
• The subsequent columns contain the input variables, one for each variable used in the
expression entered in the main calculator window.
Each row in the table contains the substitutions that are made in the expression for each
evaluation of the expression. The input substitutions can be either variable names or numbers.
The output substitutions must be variable names (which may or may not exist).
Hint If you wish to vary some constant in your expression, use a ‘dummy’ variable as a
placeholder in the expression for the constant; then substitute this variable with your
constants in each row.
When you click on OK, the expression is evaluated for each row in the table with the
substitutions specified in each row. If an output variable does not exist, it is automatically
created, using the output variable in the row above as a template. For example, if the first output
variable was Poro_r1 (which exists) and in the second row was Poro_r2 (which does not exist)
the Poro_r2 is created with exactly the same parameters (property type, extents etc.) as Poro_r1.
Note The first output variable must already exist, as otherwise there would be no reference
for how to create it.
Making life easier

Clearly it would be very tedious to enter all the substitutions if you were trying to create 100
realizations of a property, so the Multi-Apply Calculator has some features to speed up filling
out the substitution table.
• Firstly, when the Multi-Apply Calculator opens, it analyzes the input and output variable
names and the list of available variables, and it fills the table with a guess of what you
would like to do. You can then modify the table as you see fit.

Hint The Multi-Apply Calculator looks for variable names ending in a number (for
example, PermX_r1, TOPS23 etc.) and tries to fill the table with similar variables
with different numbers. This might be useful to bear in mind when naming objects.
• The Fill Pattern Match feature allows you to find variables that match some pattern and
fill them in the table. See "Fill Pattern Match" on page 691 for details.
• The Fill Series feature allows you to generate a sequence of variable names or numbers
and fill them in the table. See "Fill Series" on page 691 for details.
• The contents of the table can be exported to a file or the system clipboard (from where it
could be loaded into, say, a spreadsheet) and then it can be imported back into the table after
it has been modified. Simply use the Import Table... and Export Table... buttons.
• Each cell in the substitution table and the pattern boxes contains a drop-down list of all the
available variables, for easy reference.
Fill Pattern Match

In the Fill Pattern Match section you can enter a pattern in the Pattern field using wildcards
(similar to those used by file systems for matching files). When you click on Find all the
variables that match the given pattern are filled down the table in the column containing the
highlighted cell, starting at the highlighted cell.
For example, if you entered Perm?_r* as the pattern, the highlighted cell and the cells below
it could be filled with the variables:
PermX_r1, PermX_r2, PermX_r3... PermX_r10, PermY_r1, PermY_r2, PermY_r3...
PermY_r10, PermZ_r1, PermZ_r2, PermZ_r3... PermZ_r10 (assuming these variables
exist).
The wildcards allowed are:
• *
Matches any characters, any number of times. For example, “a*b” matches anything
beginning with an “a” and ending in a “b”.
• ?
This matches any single character once. For example, “a?b” matches three-letter words
beginning with “a” and ending in “b”.
• [chars]
This matches any single character in chars, where chars is a list of characters or a range of
characters. For example, a[A-Z0-9_]b matches three letter words beginning with “a”
followed by any capital letter, number or underscore, followed by “b”.
Fill Series
The start, end and step In the Fill Series section you can specify an arithmetic series by specifying a start value, an
values can be integer or end value and a step value and a pattern (normally containing a placeholder for the value).
real numbers. The end When you click on Fill, each value in the series in substituted for the placeholder in the pattern
value can be less than the and the resulting text is filled down the table in the column containing the highlighted cell,
start value if the step value
starting at the highlighted cell.
is negative.

For normal use the placeholder %g can be used in the pattern where the series value should be
substituted. For example, the pattern Poro_r %g generates the text Poro_r1, Poro_r2...
Poro_r10 with the default start, end and step values of 1, 10 and 1, respectively. The pattern %g
on its own simply generates the numerical series specified. Alternatively, a pattern without the
placeholder fills down the same text for as many times as the length of the series.
Note To use a literal % character in the generated text, use %% in the pattern.
The %g placeholder can be used in most circumstances, but an advanced form of this
placeholder can be used to control the exact format of the numbers generated.
The format of the placeholder is:
%[flag][width][.precision][char]
• where flag is one of the following:
- Left justify the field; default is right-justified.

+ Always prefix a sign value (+ or −).
space Reserve a space at the start of the string for the sign character (+ or −).
# Force the decimal point to be displayed, even if no characters follow it.
0 Pad values with leading zeros to fill the width.
• width is the minimum width of the output field. If the converted value is shorter than
width it is padded with spaces or zeros.
• precision is the number of digits printed to the right of the decimal point.
• The conversion character char can be one of the following:
E Produce a number in scientific notation, for example, 1.5E6

e Produce a number in scientific notation, for example, 1.5e6
f Produce a number in floating-point format, for example, 150000
g Produce a number in the shorter of e and f, suppressing insignificant zeros.
G Produce a number in the shorter of E and F, suppressing insignificant zeros.
% Produce a percent sign only.
Hint If you have used the UNIX printf command this should be familiar. See the
printf manual for more details.
Example
• To produce a set of properties named Poro_r001 to Poro_r100 you can use the
patterns Poro_r%03g or Poro_r%03f.
RESCUE property editor features

The specific features of the Expression Calculator that relate to editing fine scale properties
are:

• Fine-scale models can have only one instance of a property per property type and the name
of that instance is the same as the property type. For example, there can only be one instance
of a Porosity type property and it is called “Porosity”. Additional instances of a
property may be calculated using the workflow outlined below.
In summary, you cannot use another property of the same type as the one being created or
edited in the Expression Calculator, that is you cannot create a porosity property that is
half the value of another porosity directly. You must use a dummy property as an
intermediate step.
Workflow Example
To create a porosity property that is x2 the values of a current porosity property.
1 From the Properties node of the RESCUE model select Property Calculator... from the
drop-down menu.
2 In the Expression Calculator click on Create Property... to open the Create fine scale
property dialog.
3 Select a property from the drop-down list that does not appear in the RESCUE model
property list - any one will do.
Back in the Expression Calculator, the new property should appear in the Property pull-
down on the left.
4 Complete the expression by selecting Porosity from the list of properties on the right and
then type in *2. Click on Apply.
The new property should appear in the tree and be selectable in the 3D Viewer.
5 Check the min./max. of the property in the 3D Viewer by selecting Scene | Statistics.
6 To transfer the ‘dummy property’ to a porosity property, in the Expression Calculator
click on Create Property... and select Porosity from the drop-down list in the Create fine
scale property dialog and click on OK.
This creates a porosity property called Porosity_1 in the Properties tree.
7 In the Expression Calculator complete the expression by selecting the property you
created in step 2. Click on Apply.
This populates the new porosity property. Note that the color scale changes but the legend
reflects the min./max. values of the Porosity property, not each ‘realization’.
8 Check the statistics using Scene | Statistics.
• The Create Fine Scale Property panel (open by clicking on Create Property on the
Expression Calculator) presents a list of all the available property types. You select one
of these and click on OK to create a property of that type and name. The Create Property
Type button can be used to create a new property types.
• The Edit Scope option only allows All cells to be edited. To edit only particular
blocks/units an expression can be used. For example, to set only block 1 to the value 0.5
use the expression:
IF (AutoBlock = 1) THEN
0.5
ENDIF

Gridded property editor features
The specific features of the Expression Calculator that relate to editing gridded properties are:
• Simulation models can have multiple instances of each property type, as long as the names
are unique. For example, you can have two Porosity type properties, called “Poro_1” and
“Poro_2”, respectively.
• The Create Simulation Property (launched by clicking on Create Property on the
Expression Calculator) prompts for a name for the new property and you can select the
property type from the list. You can also create new property types using Create Property
Type. The options allow you to select whether the new property is cell-based or face-based,
and whether it supports inactive cells or local grid refinements (these can be turned off to
conserve memory).
• The Edit Scope option allows you to select whether the editing applies to the whole
property or just to the cells selected (for the property being edited) in the 3D Viewer.
Mesh map editor features

The specific features of the Expression Calculator that relate to editing mesh maps are:
• Mesh maps are not part of any model, so the Model selection list in the top left corner is
not available. All loaded mesh maps appear in the list below that.
• The Create Mesh Map panel (opened by clicking on Create Mesh Map on the
calculator) prompts for a name for the new mesh map. You are required to select an existing
map from where to copy the origin, extents, resolution and property type from. (These
details are shown for the selected map.)
• The Edit Scope option only allows All cells to be edited, as it is not possible to select part
of a mesh map in the 3D Viewer.
• You are warned if you try to create an expression that uses maps with different extents or
resolution from the map being edited. If you choose to ignore this warning, a simple
straight-line interpolation is used to match points in the expression to points on the map
being edited.
Pseudo-variables
There are four extra “pseudo-variables” that can be used in composing advanced mesh map
expressions. The pseudo-variables I and J are the zero-based node indices along the i and j
directions respectively, while the pseudo-variables X and Y are the areal coordinates of the node
in the external coordinate system. If a map already exists in the system with the same name as
one of the pseudo-variables, it overrides that pseudo-variable (FloGrid warns you that this is
happening).
Hint You can use the 2D Mapping Canvas to do more complex mapping operations, such
as converting from one resolution to another.

Expression calculator language
The Expression Calculator uses a subset of the Programming Calculator language. This
section describes the parts of the language that the Expression Calculator uses.
Comments
Comments can be useful if Comments can be used anywhere in the expression. As with the Programming Calculator, a
you wish to save an comment starts with a double-dash (--) and continues to the end of the line, for example:
expression for later use.
-- This is a comment and will be ignored

1/Poro -- description of this expression
Expressions
The Expression Calculator requires an expression to evaluate. An expression consists of
literal values (for example 1.25), the special value NULL, or variables, possibly combined with
standard operators or functions (see "Standard operator reference" on page 697 and "Function
reference" on page 697). Brackets can also be used to group sub-expressions.
Example expressions
0.34 -- a literal value

1.03e-10 -- a literal value in scientific notation
NULL -- the null value
Porosity -- a variable
'GasFlowI+' -- a variable with an unusual name
Porosity / 2 -- a variable, an operator and a literal value
PermX + log(PermY) -- a variable, an operator and a function taking
-- another variable
(Poro + 0.1) * 2 -- Grouping using brackets
• Literal values are integers, floating point numbers or numbers in standard scientific
notation.
• The NULL value represents a ‘no valid data’ value. If it is used anywhere in an expression,
then the whole expression evaluates to NULL. It is usually useful when used in an IF
statement. See "IF statement" on page 696 and also "NULL handling caveats" on page 698.
• Variables are defined by the context in which the expression is being evaluated. All
available variables are listed in the bottom right corner of the Expression Calculator. If
variables have any non-alphabetic characters or spaces in them, they should be quoted
using single quotes, for example, 'Fracture WaterFlowI+'.

IF statement
The Expression Calculator also supports conditional expressions. Given a condition or a
number of conditions, it selects an expression to use. Conditions use the relational operators (see
"Relational operator reference" on page 697) to select which expression to use, and can also use
the standard operators and functions in their sub-expressions. This is best illustrated by
example:
-- Set expression to NULL where Poro is less than 0.1

IF (Poro < 0.1) THEN
NULL
ENDIF
Note that if the condition fails (that is in this case where Poro is >= 0.1) then the default
value is returned instead. Normally the default value is empty, which means the original object
is unchanged where the condition fails.
To use a different expression when the condition fails, use an ELSE clause:
-- Set expression to NULL where Poro is less than 0.1,

-- otherwise set to the value of Poro
IF (Poro < 0.1) THEN
NULL
ELSE
Poro
ENDIF
You can include further conditions to refine the expression:
-- Set expression to Poro / 2, unless Poro is NULL or less than 0.1

-- in which case set it to 0.0, or Poro is greater then 1.0, in
-- which case set it to 1.0
IF (Poro = NULL OR Poro < 0.1) THEN
0.0
ELSEIF (Poro > 1.0) THEN
1.0
ELSE
Poro / 2
ENDIF
Note Note that there a some points to watch out for when using NULL values. See "NULL
handling caveats" on page 698.

Standard operator reference
Table 29.1 Expression Calculator standard operators
Operation Returns
+X X
-X X negated
X + Y X plus Y
X - Y Y subtracted from X
X * Y X multiplied by Y
X / Y X divided by Y
X % Y remainder of X divided by Y
X ** Y X raised to the power of Y
Relational operator reference
Table 29.2 Expression Calculator relational operators
Operation Alternate Form Alternate Form Returns

X = Y X eq Y X equals Y
X != Y X ne Y X <> Y X not equal to Y
X < Y X lt Y X less than Y
X > Y X gt Y X greater than Y
X <= Y X le Y X less than or equal to Y
X >= Y X ge Y X greater than or equal to Y
A and B both A and B are true
A or B either A or B is true
Function reference
Table 29.3 Expression Calculator functions
Function Returns
sin(X) sine of X*
cos(X) cosine of X
tan(X) tangent of X
asin(X) inverse sine of X
acos(X) inverse cosine of X
atan(X) inverse tangent of X
log(X) 10-base logarithm of X
alog(X) 10-base anti-logarithm of X
ln(X) natural logarithm of X
exp(X) exponential e to the power of X

Table 29.3 Expression Calculator functions (Continued)
Function Returns
sqrt(X) square root of X
abs(X) absolute value of X
int(X) integer portion of X
*. X is expected in radians and the returned

value is in radians for all trigonometric
functions
NULL handling caveats

The presence of NULL values in data or in expressions introduces some subtle changes to what
would be regarded as the normal rules of arithmetic.
• Firstly, as previously noted, any expression using functions or the standard operators will
be evaluated to NULL if any of the operands or function arguments are NULL. For example:
NULL * 0 -- returns NULL

sin(NULL) + 5 -- returns NULL
1 / Poro -- returns NULL wherever Poro is NULL
• The relational operators = and != (and their aliases) can be used to test for NULL values,
for example:
IF (Poro = NULL)
0.0 -- returns 0.0 wherever Poro is NULL
ENDIF
• The other relational operators (<, >, <= and >=) behave differently when used with NULL
values, according to these rules:
Table 29.4 NULL handling rules
Expression Result
x < NULL false: ∀x
x > NULL false: ∀x
x <= NULL false: ∀x, x ≠ NULL
NULL <= NULL true
x >= NULL false: ∀x, x ≠ NULL
NULL >= NULL true
x = NULL false: ∀x, x ≠ NULL
NULL = NULL true
x != NULL true: ∀x, x ≠ NULL
NULL != NULL false

Normally these rules should not interfere with the ‘natural’ way of writing expressions.
However, one case that should be noted is the following expression:
IF (Poro < 0.1)

0.0 -- Poro is < 0.1
ELSE
1.0 -- Poro is >= 0.1 or Poro = NULL
ENDIF
In this example, any NULL values in Poro are mapped to the value 1.0, along with values of
Poro that are less than 0.1. This may not have been what was desired; instead, the following
expression should probably have been used:
IF (Poro < 0.1)

0.0 -- Poro is < 0.1
ELSEIF (Poro >= 0.1)
1.0 -- Poro is >= 0.1
ENDIF
-- Else use default value
The key point to remember is that for any expression that can contain NULL values you should
not rely on ELSE - use ELSEIF to explicitly state the condition and leave out the final ELSE
altogether, using the default instead.

Calculator Language
Appendix A
Introduction
The Calculator is a general purpose, easy to use, interpreted programming language. You can
write your own programs in a language similar to BASIC, C or FORTRAN. Calculator
programs can be executed from a file or in an interactive environment. Applications that run
Calculator programs from a file write any output to a *.PRT file (usually OUTPUT.PRT).
The Calculator language is a free format language supporting all major programming constructs
such as variables and arrays, and high level constructs such as if, while and function calls. It also
understands units, and has a large number of built-in functions.
Applications can tailor the Calculator to their needs in three ways:
• by publishing internal variables so the Calculator (and hence you) can access them
• by installing “commands”, which enable the Calculator to instruct the application to do
various application specific tasks
• by calling the Calculator at well-defined points in the application to run calculator
programs to perform certain tasks. These programs can be made available to you giving you
the ability to modify or extend the default processing.
It is not expected large programs will be written using the Calculator, rather that it is used to
calculate useful expressions and transformations. You can build up your own library of small
routines.
The Calculator may be encountered in an application in various guises, for instance as a
standalone top level window, or for executing startup or run files, or as a means of extending
the capabilities of an application by supplying program files for the application to execute.
FloGrid User Guide Calculator Language 701

Introduction
Language definition
Syntax
This section briefly describes the definition of the programming language; but it can be easier
to learn by example. You can study the example (*.CAL) files for examples of the language
constructs.
Statements
The Calculator language consists of statements. There is one statement per line. Statements can
continue over more than one line by finishing the line with a continuation character (&).
Comments
Comments are introduced by --. Text following the -- but on the same line is ignored.
Structure
The language is block structured. if statements must be paired with endif, while with
endwhile etc.
Strings
Text strings are specified using double quotes ("").
User defined procedures and functions

User defined procedures and functions are supported. They must be defined before they are
called.
White space
White space may be freely used to enhance readability (for example blank lines and indentation
are recommended).
Case sensitivity
The language is case sensitive. Language keywords may be in upper or lower case. Other
elements (variables, functions, constants, units) must be specified exactly as described in this
document.
Variables
The following types of variables are supported:
• Floating point numbers (double precision).
• Built in floating point constants (double precision).
702 Calculator Language FloGrid User Guide

Language definition
• String constants.
• Floating point variables (scalars - double precision).
• String variables.
• Floating point vectors (single and double precision).
All variables have global scope apart from function and procedure arguments. This means that
the same variable can be accessed from anywhere in a Calculator program, even from other
functions.
Variables exist from the time they are first used until the application closes down or the
Calculator is reset. Consequently, variables from previous runs exist with their old values. This
is to enable exchange of information between the Calculator and an application.
All variables in the Calculator except strings are floating point: there are no integer or logical
variables. Floating point variables are also known as scalars. Floating point arrays are known as
vectors. Both scalars and vectors may have units attached to them.
String and floating point variables are created when they are encountered. However vectors
must be declared before use and variables with particular units must also be declared.
Strings may optionally be declared before use by using the string keyword. This syntax is
required if the first use of a string is as an argument to a command.
Strings may be concatenated using “+”. They may be read and written to files. Strings may be
used as function arguments and as file names in read, write and include statements.
Singly dimensioned vectors are supported. The lengths must be specified when they are
declared. The lengths may be changed at run time using the vresize function.
Variables are initialized to UNDEFINED. (See Built-in constants.)
The following program illustrates various aspects of Calculator variables:
-- set variables to a constant

a = 1
b = 1 ft
c = "Hello"
print "a=",a," b=",b," c=",c
-- declare a vector, set it
vector v1[3]
vset(v1,1.0)
print "v1[0]=",v1[0]
-- specify units for a variable
d : cm
vector v2[3] : in
d = 1 ft
vset(v2,2m)
print "d=",d," v2[0]=",v2[0]
-- undefined variables
e
vector v3[3]
print "e=",e," v3[0]=",v3[0]
-- strings
s1 = "Concatenated "
s2 = "string"
s3 = s1 + s2
print s1," ",s2," ",s3

Language definition
It gives the following output:
a= 1 b= 0.3048 m c=Hello
v1[0]= 1
d= 30.48 cm v2[0]= 78.7402 in
e= -1e+037 v3[0]= -1e+037
Concatenated string Concatenated string
Example
Here is a simple Calculator program to calculate some values in different units.
proc conv()
print "Distance conversion"
print "==================="
ht = 100 ft
print "ht in cm = ",ht cm
print "ht in in = ",ht in
print "Rate Conversion"
print "==============="
q = 100 stb/day
print "q in ft3/day = ",q ft^3/day
print "q in m3/s = ",q m^3/s
print "q in ft3/mnth = ",q ft^3/mnth
endproc
--main program starts here
conv()
stop
Syntax / run time errors

Processing by the Calculator happens in two stages. First the program is “compiled”, that is the
language is checked and translated into an executable form. During this phase the Calculator
displays the message “Processing program...”. If the compilation is successful the
calculator displays the message “Running program...” and runs the compiled program.
If the program finishes successfully the message “Program finished ok” is written.
When compiling, if the Calculator does not recognize a particular language construct it prints
an error message that includes the line that was in error. The message is as informative as
possible but often the necessary information is not available and the message “Syntax error
File... line...” is displayed.
Checks are also made at run time. For example array bounds errors and dimensionally incorrect
assignments are trapped and reported.

Language definition
Keywords
The language consists of the following keywords. This list can be generated using the Options
| Show | Keywords menu option in the interactive Calculator. Keywords may be specified in
upper or lower case. By convention this document always uses lower case.
Table A.1 Standard Calculator keyword descriptions
Keyword Description Notes

break Break out of a while loop (7)
close Close (rewind) file (4)
else Else statement (1)
endfunc End of function definition (2)
endif Endif statement (1)
endproc End of procedure statement (2)
endwhile End of while loop (7)
func Function definition (2)
if If statement (1)
include Include another source file (5)
print Print statement (3)
printnr Print on same line (3)
proc Procedure definition (2)
read Read vectors and scalars from file (4)
return Return from func or proc (2)
stop Stop execution (optional) (6)
string Define a string variable (9)
usertype Define a user variable (10)
vector Define a vector (array): vector vec[10] (8)
vreadcol Read vectors from file in column format (4)
vwritecol Write vectors to file in column format (4)
while while loop (7)
write write vectors and scalars to file (4)
Notes
1 The set of statements in the if and else block must be terminated by an endif
statement. For example:
if ( i < iMax )
sum = sum + i
prod = prod * i
else
print "Error: i out of range ",i
endif

Keywords
The condition in () is deemed to be TRUE if non zero, FALSE if zero
2 Functions return a value, procedures do not. Function and procedure definitions begin with
the name followed by empty brackets. Procedures end with the endproc statement.
Functions end with an endfunc statement. Multiple returns within a function or
procedure are allowed. Values are returned from a function using the return statement.
Within the definition arguments are referred to as $1 for the first argument, $2 for the
second etc. Functions must be defined before they are called. Function calls may be nested.
They are invoked by specifying the name followed by any arguments in brackets. For
example:
proc error()
print "A fatal error has occurred. Execution terminated."
stop
endproc
func invert_sum()
temp = $1 + $2
if ( abs(temp) < 0.0001)
error()
endif
return 1/temp
endfunc
--main program
a = 1.0
b = 2.0
print "1/(a+b) = ",invert_sum(a,b)
stop
3 Strings and variables may be displayed on the output window using the print statement.
The print statement always starts a new line. To print on the same line as before use
printnr. Several items may be printed in one statement, each separated by a comma.
Variables are printed into fields 8 characters wide. If a variable has associated units these
are automatically printed according to the rules described in the Units Support section.
All output produced using print statements is echoed to the file OUTPUT.PRT. This
provides a convenient record of a calculation which can then be included into other work,
for example a spreadsheet.
4 Reading and writing to files is supported. The file name is specified on the keyword. Note
that on the PC, any backslashes to indicate directories must be put in twice. If the file is not
already open it is opened automatically.
The read and write keywords write vectors, strings and scalars from and to files.
Vectors are written 6 per line. When reading strings are delimited by spaces.
When reading or writing scalars or strings the variable must be prefixed with & to indicate
that the contents may be updated.
The vreadcol and vwritecol keywords write vectors in columns, one column per
vector. This is useful for interfacing with other programs.
Files are closed when the Calculator program terminates or the close keyword is
encountered.

Keywords
Here is some example code for I/O.
--write, read, close

vector vwrita[5]
vector vwritb[6]
vinclog(vwrita,1,1e+4)
vset(vwritb,1e+5)
writc = 1e+5
write("writeto.cal",vwrita,vwritb,&writc)
close("writeto.cal")
vector vreada[6]
vector vreadb[6]
print "error message coming up "
read("writeto.cal", vreada,vreadb,&readc)
while(i<6)
if(vreada[i]!=10^i || vreadb[i]!=1e+5)
stopmsg("write/read test failed")
endif
i = i + 1
endwhile
if(readc!=0)
stopmsg("write/read test failed")
endif
close("writeto.cal")
-vwritecol, vreadcol, close
vector vwcola[6]
vector vwcolb[6]
i = 0
while(i<6)
vwcola[i] = i
vwcolb[i] = 10*i
i = i + 1
endwhile
vwritecol("vwriteto.cal",vwcola,vwcolb)
close("vwriteto.cal")
vector vrcola[6]
vector vrcolb[6]
vreadcol("vwriteto.cal",vrcola,vrcolb)
i = 0
while(i<6)
if(vrcola[i]!=i || vrcolb[i]!=10*i)
stopmsg("vwritecol/vreadcol test failed")
endif
i = i + 1
endwhile

Keywords
5 Other Calculator functions, procedures and code may be embedded using the include
statement. For example:
-- include library of useful routines

include( "mylib.cal")
-- make use of the include file
a = 10
b = 3
c = 22
d = 5.4
area = calcarea(a,b,c,d)
6 Execution stops when a stop statement is encountered. A stop statement at the end of
the main program is optional. The message STOP is written to the output window.
7 Program loops are accomplished using the while statement. The statements between the
while and endwhile are repeatedly executed until the expression inside the () becomes
false. while loops can be exited using the break statement. Remember to increment the
loop counter inside the loop. For example:
print "Table of sines"

deg = 0.0
while ( TRUE )
print "sin(",deg,") = ",sin(deg/DEG)
deg = deg + 1.0
if ( deg > 90.0 )
break
endif
endwhile
print "Finished"
8 Vectors, also known as arrays are declared using the vector keyword. Only singly
dimensioned arrays are supported. Individual elements are accessed using square bracket
notation []. Vectors start at element 0 and range up to element N-1 where N is the declared
size. Vectors must be declared before use. They are given a size when they are declared,
this size can be changed at run time using the vresize() symbol function (see later).
Vector variables may be given preferred units as for scalar variables. For example:
vector speeds[10] : mi/h;

Keywords
9 The string keyword is only required when the first encountered usage of the variable is
as an argument to a command. In this case it is not possible to ascertain from the context
what the correct type of the variable is and a hint is required from the user. For example:
string message
proc AskTOContinue()
if ( Question( Question=message ) )
stop
endif
endproc
message = ‘Carry on?’

AskToContinue()
-- do further processing
10 The usertype keyword is only required when the first encountered usage of the variable
is as an argument to a command. In this case it is not possible to ascertain from the context
what the correct type of the variable is and a hint is required from the user. User types are
used infrequently. Certain commands may return a user type, such as a simulation grid. The
only use of this returned variable is as an argument to another command. This facility
allows a set of commands to be defined to process specialized objects efficiently.

Keywords
Built-in constants
The table shows the various constants that are predefined in the Calculator.
Table A.2 Built-in constants
Name Value Description

DEG 5.72958e+01 degrees to radians conversion factor
EPSILON 1.0e-04 precision test
EXP 2.71828e+00 e - base of natural logarithms
FALSE 0 Logical false
GAMMA 5.77216e-01 Euler-Mascheroni constant
LN10 2.30259e+00 natural log of 10
LN2 6.93147e-01 natural log of 2
LOG10E 4.34294e-01 log (base 10) of e
LOG2E 1.44270e+00 log (base 2) of e
ONE_DIV_PI 3.18310e-01 reciprocal of pi
ONE_DIV_SQRT2 7.07107e-01 reciprocal of square root of 2
ONE_DIV_SQRTPI 5.64190e-01 reciprocal of square root of pi
PHI 1.61803e+00 golden ratio
PI 3.14159e+00 pi
PI_DIV_2 1.57080e+00 pi divided by 2
PI_DIV_4 7.85398e-01 pi divided by 4
SQRT2 1.41421e+00 square root of 2
TRUE 1.0 Logical TRUE
TWO_DIV_PI 6.36620e-01 twice reciprocal of pi
TWO_DIV_SQRTPI 1.12838e+00 twice reciprocal of square root of pi
UNDEFINED -1.0e33 variable initialized to this value

Built-in constants
Built-in functions
The table shows the wide range of built-in functions that the Calculator supports.
Table A.3 Built-in functions
Name No. args Description Notes

abs 1 absolute value
acos 1 inverse cosine (1)
antilog10 1 Anti logarithm base 10
asin 1 inverse sine (1)
atan 1 inverse tangent (1)
cos 1 cosine (2)
cosh 1 hyperbolic cosine (2)
ei 1 exponential integral (1 argument)
erf 1 error function
erfc 1 Complementary error function
exp 1 exponential function e
expn 2 exponential integral (2 arguments) (3)
factorial 1 factorial
gamma 1 gamma function
i0 1 Modified Bessel function of order zero
i0e 1 i0(x)*exp(-x)
i1 1 Modified Bessel function of order one
i1e 1 i1(x)*exp(-x)
igamma 2 Incomplete gamma function
igammac 2 Complementary Incomplete gamma function
int 1 Truncate towards zero
j0 1 Bessel function of order zero
j1 1 Bessel function of order one
k0 1 Modified Bessel func, third kind, order zero
k0e 1 k1(x)*exp(x)
k1 1 Modified Bessel function, third kind, order one
k1e 1 k1(x)*exp(-x)
log 1 Logarithim base e
log10 1 Logarithm base 10
rand 1 Random number between 0 and 1 (6)
sin 1 Sine (2)
sinh 1 Hyperbolic sine (2)
sqrt 1 Square root
srand 1 Initialize random number sequence (6)
tan 1 Tangent (2)

Built-in functions
Table A.3 Built-in functions (Continued)
Name No. args Description Notes

tanh 1 Hyperbolic tangent (2)
user 2 Developer defined function user (a,b) (4)
yn 2 Bessel function of second kind of integer order (5)
Notes
1 Value returned in radians. Use built in constant DEG to convert to degrees.
2 Argument in radians. Use built in constant DEG to convert to degrees.
3 Usage is a = exp ( n, x ) where
∞
( – xt ) n
exp ( n, x ) = ∫e dt ⁄ t [EQ A.1]
1
4 The user function is only available to programmers using the Calculator as a part of their
own programs.
5 Usage is b = yn(n,x) where n is a (possibly negative) integer.
6 rand() returns a random number between 0 and 1. The argument is required but ignored.
Successive calls to rand() return different random numbers from a given sequence. The
sequence can be altered by calling srand (seed) where seed represents a position in the
random number sequence. The same sequence of random numbers can be regenerated by
reinitializing with the same seed. The srand seed also affects the sequence of numbers
generated for vrandomfill.

Built-in functions
Operators
The table shows the operators supported by the Calculator.
Table A.4 Supported operators
Symbol Description
+ Add
- Subtract (or negate)
* Multiply
/ Divide
^ Raise to power
< Less than
> Greater than
<= Less than or equal
>= Greater than or equal
!= Not equal (logical expression)
== Equals (logical expression)
= Assignment
|| Logical OR
! Logical NOT
&& Logical AND
() Brackets - evaluate first
: Assign units when declaring variable
[] Access vector elements
& Continuation character if last on a line

Operators
Symbol functions
A wide range of built in functions are provided that operate on vectors and some manipulate
scalars. These functions make many data processing tasks extremely simple.
Functions operating on vectors have names that begin with “v”. Many of the functions return a
value indicating success or failure, these values are denoted by “ierr” in the table below. For
these functions 1 (TRUE) indicates success, 0 (FALSE) failure.
The vlen() and vresize() functions are particularly useful as they allow the Calculator to
respond to different run time data, for example the size of a simulation grid.
Using the vector based functions is much more efficient that explicitly processing the data using
the while loop. Whenever large arrays are processed vector functions should be used.
Note Optional arguments are in [], is and ie correspond to the start and end indices of the
vector. Non vector arguments that are updated by the function are preceded by “&”.
Table A.5 Symbol functions
Name Description
cubic Solve cubic eqn ax**3+bx**2+cx+d=0: nroot = cubic(&x1,&x2,&x3,a,b,c,d)
presval Present value: res = presval (rate,nper,pmt,fv,type)
quad Solve quadratic eqn. ax^2+bx+c=0: nroot = quad(&x1,&x2,a,b,c)
raw Dimensionless value after conversion to unit:
res = raw (x,unit)
swap Swap values: ierr = Swap (&a,&b)
vabs Make elements positive: ierr = vabs(v,[is],[ie])
vadd Add v2 to v1: ierr = vadd(v1,v2,[is],[ie])
vaverage Average vector: av = vaverage(v,[is],[ie])
vceiling Replace values in v that are greater than x by x: ierr = vceiling(v,x,[is],[ie])
vcopy Copy v2 onto v1: ierr = vcopy(v1,v2,[is],[ie])
vcopyconv Copy v2 onto v1 with unit conversion:
ierr = vcopyconv(v1,v2,[is],[ie])
vcopyraw Copy dimless v2 after conv onto v1 with unit conv:
ierr = vcopyraw(v1,v2,[is],[ie])
vdelete Delete element ierr = vdelete(v,i)
vderivpoly Evaluate as a differentiated polynomial:
res = vderivpoly(v,x,[is],[ie])
vdivide Divide v1 by v2 element by element: ierr = vdivide(v1,v2,[is],[ie])
vexpon Raise element in v1 to power in corresponding element in v2:
ierr = vexpon(v1,v2,[is],[ie])
vfloor Replace values in v that are less than x by x: ierr = vfloor(v,x,[is],[ie])
vfft Fast Fourier transform vector: ierr = vfft(v,npts,isign)

Symbol functions
Table A.5 Symbol functions (Continued)
Name Description
vinc Set elements to incremented interval:
ierr = vinc(v,xl,xu,[is],[ie])
vinclog Set elems to log incremented interval:
ierr = vinclog(v,xl,xu,[is],[ie])
vinsert Insert element with value x at i: ierr = vinsert(v,x,i)
vintegrpoly Evaluate as an integrated polynomial:
res = vintegrpoly(v,x,[is],[ie])
vintegrtrap Trapezoidal rule integration:
res = vintegrtrap(v,xstep,[is],[ie])
vinterp Return y corresponding to x using linear interpolation:
y = vinterp(vx,vy,x,[is],[ie])
vlaplace Laplace transform of vector: res = vlaplace(v,n,tau,sr)
vlen Return length of a vector: res = vlen(v)
vlog Take natural logarithm of each element of a vector: ierr = vlog(v,[is],[ie])
vlsqfit Fit vectors to y=a+bx, also calculate variances in the result. Can optionally
specify the fit range for the independent vector:
ierr = vlsqfit(vx,vy,&a,&b,&avar,&bvar,[fl],[fu])
vmax Maximum value of vector: maxval = vmax(v,[is],[ie])
vmaxdiff Maximum difference between elements:
maxd = vmaxdiff(v,[is],[ie])
vmedian Median value of vector: med =vmedian(v,[is],[ie])
vmin Minimum value of vector: minval = vmin(v,[is],[ie])
vmindiff Minimum absolute difference between elements:
mind = vmindiff(v,[is],[ie])
vminus Make elements negative, v[i] = -abs(v[i]):
ierr = vminus(v,[is],[ie])
vmultipy Multiply v1 by v2 element by element:
ierr = vmultiply(v1,v2,[is],[ie])
vnearest Index of element nearest to value:
near = vnearest(v,fval,[is],[ie])
vnegate Invert sign of elements: ierr = vnegate(v,[is],[ie])
vpow Raise each element of v to power x: ierr = vpow(v,x,[is],[ie])
vnpv Net Present Value: amount = vnpv(v,time,rate)
vpolynom Valuate as a polynomial: res = vpolynom(v,x,[is],[ie])
vrandomfill Fill with random numbers between fl and fu:
ierr = vrandomfill(v,fl,fu,[is],[ie])
vresize Change length of vector: ierr = vresize(v,newsize)
vscale Scale vector: ierr = vscale(v,amount,[is],[ie])
vscprod Scalar product of v1 and v2:
ierr = vscprod(v1,v2,[is],[ie])

Symbol functions
Table A.5 Symbol functions (Continued)
Name Description
vset Set elements of vector to val: ierr = vset(v,val,[is],[ie])
vshift Shift vector: ierr = vshift(v,amount,[is],[ie])
vsmooth Smooth vector: ierr = vsmooth(v,nsm,[is],[ie])
vsolvematrix Solve 2x2 matrix: ierr = vsolvematrix(va,vb,vc,n)
vsort Sort vector, uses heapsort - efficient:
ierr = vsort(v,increasing,[is],[ie])
vsubtract Subtract v2 from v1: ierr = vsubtract(v1,v2,[is],[ie])
vsum Sum vector: sum = vsum(v,[is],[ie])
vsumsqr Sum of squares of vector: sumsq = vsumsqr(v,[is],[ie])

Symbol functions
Unit support
Calculator units are defined by the application. If no units are specified, the default is the SI unit
system. The complete list may be obtained by using Show | Variable | Units from the
interactive Calculator. The conversion factors are to the SI unit system.
Composite units are generated by forming expressions using the base units above. The
expressions are evaluated from left to right, brackets are not supported. Unit powers are
specified using the ^, inverse units by using the /. For example, momentum is kg m^2 /s^2.
Internally all variables are stored in SI units. Variables may be given preferred units by declaring
them using the colon (:) notation.
If a variable has preferred units then these units are assumed during assignment and used in print
statements. Units must always be specified explicitly in expressions whether preferred units are
in force or not that is:
today : day
tomorrow : day
today = 1.0
tomorrow = today + 1.0 -- illegal
tomorrow = today + 1.0 day -- ok
tomorrow = today + 24.0 hr -- ok
If a variable has units these will be displayed when it is printed. Alternatively the units to be
used in printing may be specified explicitly. For example:
-- specify preferred units

d_cm : cm
d_mm : mm
d_cm = 10 -- stored internally as 0.1
d_mm = 20 cm -- preferred units overridden
d_km = 1 km -- no preferred units will be printed in metres
d_dim = 10 -- dimensionless variable
print "Variables without explicit units"
print "d_cm = ",d_cm
print "d_mm = ",d_mm
print "d_km = ",d_km
print "d_dim = ",d_dim
print "Variables with explicit units"
print "d_cm = ",d_cm m
print "d_mm = ",d_mm mm
print "d_km = ",d_km km
print "d_dim = ",raw(d_dim,ft) m
stop

Unit support
This program prints the following output:
Variables without explicit units

d_cm = 10 cm
d_mm = 200 mm
d_km = 1000 m
d_dim = 10
Variables with explicit units
d_cm = 0.1 m
d_mm = 200 mm
d_km = 1 km
d_dim = 10 m
STOP
Notice the use of the raw() function to override the dimensionality of the d_dim variable in the
print statement.
Conversion factors may be easily obtained by setting the variable to 1. For example:
q = 1.0 stb/d
print q stb/d, " ", q m^3/s, " ", q ft^3/mnth
Note There are strict checks for dimensional consistency. For example you may not add a
dimensionless quantity to a quantity with dimensions.
The units associated with a variable can be overridden using the raw() symbol function. This
converts the supplied variable using the supplied units and then strips the units and returns the
dimensionless value. For example the following program:
a = 2 ft
b = 1 in
b = raw(a,in) cm
print a, raw(a), raw(a,in), raw(a,in) cm, b
produces the following output:
0.6096 m 0.6096 24 2400 cm 0.24 m
The first output value is 2 feet converted into meters; the second is 2 feet converted to the default
SI unit (meters) then output as a dimensionless value; the third is 2 feet converted to inches and
output as a dimensionless value; the fourth is 2 feet converted to inches then to SI units (meters)
and output as centimeters. Finally, the last value is 24 centimeters expressed as meters.

Unit support
This facility is useful when implementing formulae that assume certain units. The vcopyraw()
function is similar but does not convert using an intermediate unit. vcopyconv() is used to
copy vectors with different units but the same dimensionality. vcopy() is used when the vectors
have the same units. The following example should make this clearer:
vector a[3] :m
vector b[3] :g
vector c[3] :cm
vector d[3] :m
vset(a,1 ft) -- initialise a
vcopyraw(b,a) -- copy onto vector with different dimensions
vcopyconv(c,a) -- copy onto vector with different units
vcopy(d,a) -- copy onto vector with same dimensions
print a[0],b[0],c[0],d[0]
This program produces the following output:
0.3048 m 0.3048 g 30.48 cm 0.3048 m
Units bind to expressions with the same precedence as “+” and “-”. Thus the statement c = 1.0
m * 2.0 in is illegal but d = 1.0 m + 2.0 in is ok. The first statement should be c = (1.0 m) + (2.0
in). The example file UASSOC.CAL gives some more examples.
Property model property editor commands

The following list of commands may be used to manipulate Property Model properties. These
commands are normally used by running a Calculator script from within the Property Model
Property Editor panel. (See the section the Property Model Editor in this manual.)
For commands which require a property type string, a list of available property types can be
found in the Property drop-down in the Property Model Property Editor panel. It is also
possible to create new property types. (See the section on property types in this manual.)
BUGPropToVec()
This command copies data for the specified property type and block unit grid (BUG) into a
Calculator vector. Note that if more than one property version for the type exists for a block unit
grid, the first is used.
• Returns:
1 if ok, else 0.
• Arguments:
Model (string) - name of the property model.
Scenario (string) - name of the property scenario on the model.
BUGNumber (scalar) - number of the BUG to be accessed within the scenario.
PropertyType (string) - property type to be accessed.
Vector (vector) - vector to copy the property data into. The vector is resized to hold the
data.
• Argument combinations:

Unit support
All arguments must be specified, except Scenario, which defaults to the current
geological scenario on the model.
• Example:
BUGPropToVec(Model = PropertyModelName, Scenario =
PropertyScenarioName, BUGNumber = BUGNumber, PropertyType =
BUGPropertyType, Vector = vecToCopyInto)
Note that all the arguments are set to Calculator variable names that are made available
from within the context of the Property Model Property Editor panel.
VecToBUGProp()
This command will copy data from a Calculator vector into the specified property type and
block unit grid (BUG). The property must exist within the application, else an error is returned.
Note that if more than one property version for the type exists for a block unit grid, the first is
used.
• Returns:
1 if ok, else 0.
• Arguments:
PropertyType (string) - property type to be accessed.
Vector (vector) - vector to copy the property data from.
• Example:
VecToBUGProp(Model = PropertyModelName, Scenario = PropertyScenarioName,
BUGNumber = BUGNumber, PropertyType = BUGPropertyType, Vector =
vecToCopyFrom)
Note that all the arguments are set to the Calculator variable names that are made available
from within the context of the Property Model Property Editor panel.
GetNumOfBUGs()
This command returns the number of block unit grids in a property scenario on a property
model.
• Returns:
Number of block unit grids in the scenario.
• Arguments:
Scenario (string) - name of the property scenario on the model
Model argument must be specified. Scenario defaults to the current geological scenario
on the model.

Unit support
• Example:
GetNumOfBUGs(Model = “PropertyModel1”, Scenario = “PropertyScenario1”)
GetBUGSize()
This command returns the dimension of a block unit grid within a property model.
• Returns:
Size of the block unit grid in the specified dimension.
• Arguments:
Dimension (string) - one of “Nx”, “Ny”, or “Nz”.
• Example:
GetBUGSize(Model = “PropertyModel1”, Dimension = “Nx”, Scenario =
“PropertyScenario1”, BUGNumber = BUGNumber)
Note that the BUGNumber argument is set to the Calculator variable name that is made
available from within the context of the Property Model Property Editor panel.
Simulation Property Editor commands

The following commands provide access to manipulate simulation properties. It is possible to
edit and create both initial and recurrent properties of a simulation grid. These commands are
usually used by running the Calculator from within the Simulation Property Editor but can be
called from anywhere within the application, where appropriate.
Most of the commands require a property type string. The list of available property types can be
found from the Type field in the Simulation Property Editor. It is also possible to create
property types.
SimCellIDToIndex()
This command loads a list of indices into a Calculator vector. These correspond to indices into
the property vector for each cellID (natural cell index, from 1 to number of cells, including any
LGRs).
• Returns:
1 if ok, else 0.
• Arguments:
PropType (string) - name of the property type to be created.
PropName (string) - name of the property version to be created.
GridName (string) - name of simulation grid.
PropManager (string) - name of property manager.

Unit support
Vector (vector) - vector to copy the indices into. The vector is resized to hold the data.
CurrentSelection (string) - name of current 3D cell selection. If none is specified
from the Simulation Property Editor, a warning is reported and all cells are used.
ReportStep (integer) - must be an existing report step.
PropType, PropName and Vector must all be specified. If only one simulation grid
and property manager exist in the application, the arguments GridName and
PropManager need not be specified. The remaining arguments are optional.
• Example:
SimCellIDToIndex (PropType = “PoreVolume”, PropName = “PORV”,
GridName = SimGridName, Vector = idToIndexVec,CurrentSelection =
SimCellSelectionName)
Note that the GridName and CurrentSelection arguments are set to Calculator
variable names that are made available from within the context of the Simulation Property
Editor.
SimCreateEmptyProperty()
Used to create a new initial or recurrent simulation property. A new initial property is created
by the Simulation Property Editor when the New property box is checked, so this command
is unlikely to be required to create initial properties. However, it is the only way to create
recurrent properties.
• Returns:
1 if ok, else 0.
• Arguments:
PropBasis (string) - property basis: “Cell-based” (the default) or “Face-based”.
DataType (string) - type of property data. Either Integer or Real.
InactiveData (boolean) - flag to indicate if there are inactive cells. Default is
“FALSE”.
LGRData (boolean) - flag to indicate that property includes data for any LGRs in the grid.
Default is “FALSE”.
External (boolean) - flag to indicate if the grid has external renumbering. Default is
“FALSE”.
Value (scalar) - initial value. If not specified, default is 0.
PropType, PropName, and DataType must all be specified. If only one simulation
grid and property manager exist in the application, the arguments GridName and
• Example:

Unit support
SimCreateEmptyProperty (PropType = “OilSat”, PropName = “os1”,
GridName = “Grid1”, PropManager = “PropManager1”, DataType = “Real”,
ReportStep = 1)
SimGetPropReportSteps()
This command loads the report steps that exist for the specified property into a Calculator
vector.
• Returns:
1 if ok, else 0.
• Arguments:
Vector (vector) - vector to copy the report steps into. The vector is resized to hold the
data.
PropType, PropName and Vector must all be specified. If PropManager is not
given, the first property manager in the system is used.
• Example:
SimGetPropReportSteps (PropType = “OilSat”, PropName = “SOIL”,
PropManager = SimPropManager, Vector = rptStepVec)
Note that the PropManager argument is set to a Calculator variable name that is made
available from within the context of the Simulation Property Editor.
SimIndexToCellID()
This command loads a vector of cellIDs into a Calculator vector corresponding to the cellID of
each element in the property vector.
• Returns:
1 if ok, else 0.
• Arguments:
Vector (vector) - vector to copy the cellIDs into. The vector is resized to hold the data.

Unit support
• Example:
SimIndexToCellID (PropType = “PoreVolume”, PropName = “PORV”,
GridName = SimGridName, Vector = indexToCellIDVec, CurrentSelection =
Editor.
SimPropToVec()
This command loads data for the specified property into a Calculator vector.
• Returns:
1 if ok, else 0.
• Arguments:
Vector (vector) - vector to copy the property data into. The vector is resized to hold the
data.
and property manager exists in the application, the arguments GridName and
• Example:
SimPropToVec (PropType = “Porosity”, PropName = “poro1”, GridName =
SimGridName, Vector = vecToCopyInto, CurrentSelection =
Editor.
SimVecToProp()
This command loads data from a Calculator vector into the application’s internal representation
of the specified property. The property must exist within the application, else an error is
returned.
• Returns:
1 if ok, else 0.

Unit support
• Arguments:
PropType (string) - name of the property type.
PropName (string) - name of the property version into which the data is to be
copied.
Vector (vector) - vector containing the property data to copy from.
• Example:
SimVecToProp (PropType = SimPropType, PropName = SimPropName,
GridName = SimGridName, Vector = vecToCopyFrom, CurrentSelection =
Note that all the arguments are set to Calculator variable names that are made available
from within the context of the Simulation Property Editor.
SimCellPropToFaceID()
This command loads a set of face IDs into a Calculator vector for each face that joins cells with
the specified property values. This is useful if you are editing a face based property and you
want to identify a subset of the selected faces using a cell based property.
• Returns:
1 if ok, else 0.
• Arguments:
PropType (string) - name of the (cell based) property type.
PropName (string) - name of the (cell based) property version to be queried.
Vector (vector) - vector to copy the face IDs into. The vector is resized to hold the data.
Value1 (integer) - requested property value for one of the face cells.
Value2 (integer) - requested property value for the other face cell.
PropType, PropName, Vector, Value1 and Value2 must all be specified. If only
one simulation grid exists in the application, the argument GridName need not be
specified. The remaining arguments are optional.
• Example:

Unit support
SimCellPropToFaceID(PropType="BUNIT", PropName="BUNIT", GridName
= SimGridName, Vector=faceVec, Value1=2, Value2=3)
This will identify the set of faces that connect cells with BUNIT values of 2 and 3. Note
that the GridName argument is set to a Calculator variable name that is made available
from within the context of the Simulation Property Editor. Within this context the
SimCellIDToIndexVector can then be used to index into a face based property
vector.
Note When operating on face based properties (for example, transmissibility in the
unstructured gridder) commands and the special variables made available within the
context of the Simulation Property Editor work with face IDs rather than cell IDs.

Unit support
Special variables
The Calculator can be run as a general utility from a stand alone top level window or it may be
called at well defined points from within an application. This section describes special variables
that can be used in Calculator scripts to be run at particular places in an application. The values
of variables depend on the data you have entered in the panel from which the Calculator is to be
run. This means that the variables can be used, rather than specific names, to write a general
Calculator script that can be applied to the user selected data.
Care should be taken that user defined variables do not clash with these names.
Simulation property editing

If the Calculator is run from the Simulation Property Editor panel, the following special
variables are made available for use.
Table A.6 Variables defined when simulation property editing
Name Type Usage

SimGridName string The name of the current simulation grid.
SimPropManager string The name of the current property manager.
SimPropType string The property type.
SimPropName string The version name of the property.
SimPropBasis string The property basis: “Cell-based” or “Face-based”.
SimPropLength scalar The length of the property vector. This will either be
for all cells or for the selection in the 3D Viewer,
depending on the panel configuration.
SimCellSelectionName string The name of the selection in the 3D Viewer, or
“unset_name” if this option is inactive.
SimCellIDToIndexVector vector Vector holding the indices into the property vector,
SimPropVector, corresponding to cellID. If data for a
cellID is not present, the index = -1.
SimIndexToCellIDVector vector Vector holding the cellIDs for each of the values held in
the property vector, SimPropVector.
SimPropVector vector Vector holding the data for the property. Either all the
available data or for the selection in the 3D viewer.
SimSelCellIdsVector vector Vector holding the cellIDs for the cells that have been
selected in the 3D Viewer. If the selection option is
inactive, vector holds all the cellIDs for the property.
Property model property editing

If the Calculator is run from the Property Model Property Editor panel, the following special
variables are made available for use.

Special variables
The Calculator script is run once for each block unit in the property model.
Table A.7 Variables defined when editing Property Model properties
Name Type Usage

PropertyModelName string Property Model name
PropertyScenarioName string Property Scenario name
BUGPropertyType string Property type
BUGNumber scalar Number of BUG within the
scenario (counting all BUGs in
each unit starting from the
bottom up)
BUGPropertyLength scalar Length of the complete array laid
out as a one dimensional
property vector (with I the fastest
varying index, J the next index
and K the last index)
BUGPropertyNx, scalar Dimensions nx, ny and nz of the
BUGPropertyNy, array where:
BUGPropertyNz I varies from 1 to nx,

J varies from 1 to ny,
K varies from 1 to nz
BUGPropertyVector vector The BUG data itself laid out as a
vector
BUGActiveCellVector vector Vector spanning the BUG
indicating whether the associated
cell is active or not. Active cells
have value 1; inactive cells have
value 0.

Special variables
Calculator utilities
The Calculator utilities are accessible from the Main Window | Utilities menu by selecting the
Calculator Show option. Selection of one of the menu items opens a window in which a list of
variables corresponding to the selection and available for use within a Calculator script is
displayed. The window provides a search facility and its contents can be saved to a file.
Scalars
Selection of the Calculator Show | Scalars menu item displays all current floating point
variables that exist for use within the Calculator.
Vectors
Selection of the Calculator Show | Vectors menu item displays all current vectors that exist for
use within the Calculator.
Strings
Selection of the Calculator Show | Strings menu item displays all current string variables that
exist for use within the Calculator.
Units
Selection of the Calculator Show | Units menu item displays all units that exist for use within
the Calculator. Conversion factors are to the SI unit system.
Built in functions
Selection of the Calculator Show | Built in functions menu item displays the built in functions
that the Calculator supports.
Symbol functions
Selection of the Calculator Show | Symbol functions menu item displays the symbol functions
that operate on vectors (and some scalars) supported by the Calculator.
Keywords
Selection of the Calculator Show | Keywords menu item displays the list of reserved keywords
defined by the Calculator.
Operators
Selection of the Calculator Show | Operators menu item displays the operators that can be
used within a Calculator script.

Commands
Selection of the Calculator Show | Commands menu item displays the list of commands that
exist within the application. This includes commands used for logging and replaying progress
through the application in addition to commands used to provide access to the internal data
within the application for use in Calculator scripts.
Constants
Selection of the Calculator Show | Constants menu item displays the constants that are defined
within the Calculator.
All of above
Selection of the Calculator Show | Constants menu item lists all the above information at
once.

Startup files
When an application starts it may search for a calculator file and run it. This file may create
variables for use later in the application, for example it could set a user name to be later
embedded in a report, or it may fire application specific commands or menu picks to restore an
application to a previous state.
By default the startup file is called PROFILE.CAL and is looked for in the working directory.
This can be altered using the ECL.CFG configuration file as shown:
----------------------------------------
SECTION APPLNAME
----------------------------------------
SUBSECT CALC
PROFILEDIR /project/study1/mydata
PROFILE MYPROF.CAL
The section keyword is the specific application name for example SCHEDULE or WELTEST.
An example startup file that loads data into the Weltest 200 program is shown below:
caAutoRun = 1
caAutoFileName = "demo.db"
caAutoDirName = "/project/study1/mydata"
MenuPick(Window = "W200",Pick = "Open...")

MenuPick(Window = "W200",Pick = "Import...")
MenuPick(Window = "W200",Pick = "Close")
MenuPick(Window = "W200 - Analyse",Pick = "Add Line...")
caAutoRun = 0
stop
In this example the caAutoRun flag is a built in variable that, if non zero informs the
application that data panels should be bypassed. The caAutoFileName variable contains the
names of input files that will be needed when options such as opening a file are invoked.
caAutoDirName contains the directory where the files reside
The MenuPick() command takes two arguments and fires off the appropriate menu option.
The first parameter is the window name, while the second is the menu option. It is important to
get these names exactly right (case is important).

Startup files
Debugging
Examining variables
There is no explicit debugging facility in the Calculator. However print statements can be
used as required to show the value of variables and
stop statements may be used as breakpoints. Variables may then be interrogated using the
Calculator Show utilities menu. Remember variables are global and exist until the calculator
is closed or reset.
Common problems
Name conflicts
This comes from three sources and can give rise to unexpected syntax or run time errors.
1 Name clashes with built in names or (especially) units. Certain names are reserved for
keywords, built in constants or functions, or units. A list of the names in use can be obtained
from the Calculator Show utilities menu. Clashes with unit names are especially common
as many units have short names likely to be chosen as variables (for example h, g, m etc.).
2 All variables are global so it is possible to inadvertently use the same variable in different
functions. This may give a compilation error (inconsistent units) or run time error, but may
just give misleading results. Variables must be global so that program as well as user
variables can be accessed. If in doubt use the Calculator Reset menu option.
3 Variables from previous runs still exist when the run has finished. This can give unexpected
errors when a new function is run which uses an old variable in a new way. Persistence of
variables is necessary so that program variables may be accessed. The namespace can be
cleared using the Calculator Reset menu. It is also good practise to initialize all variables
the first time they are used.
Never ending while loops

If using the while loop as a FORTRAN type DO loop or a c type for or while loop then do
not forget to initialize the counter and increment it inside the body of the loop. This example
will loop until stopped by the user.
iCount = 0
while (iCount<10) --loops forever
a[iCount] = 0.0
endwhile
Stack overflow
This message can occur if the statement(s) following an if or while construct are not finished
with an endif or endwhile.

Debugging
Syntax error signalled on a valid line
The preceding line may be at fault. You may have forgotten to close a quoted string. Sometimes
exact information about where an error occurred is not available. In these cases the Calculator
gives a nearby line number and highlights that line. To help locate the problem the next few
characters after the error are written.
Using quantities with fractional dimensions

The code:
a = 4.0 m
b = sqrt(a)
print "",b," ",(b*b)
incorrectly prints "2.0 m 4.0m^2", rather than "2.0 m^0.5 4.0 m".
Non fractional dimensions are treated correctly, that is the code:
a = 4.0 m^2
b = sqrt(a)
print "",b," ",(b*b)
correctly prints "2.0 m 4.0 m^2".
Printing expressions
Expressions involving “*” or “/” may give a syntax error when used in a print statement. If this
happens enclose the expression in () or use an intermediate variable for example.
a = 2
-- the following line would give a syntax error

--print a*a
-- so do it like this ...

b = a*a
print b
-- or this ...
print (a*a)
Slow execution
In the interactive Calculator sometimes the speed of program execution is limited by the time
taken to write the output text to the output window. Often shrinking the output window or
reducing the program output can dramatically speed up the Calculator.

Debugging
Simulation Property Editor examples
The following Calculator scripts work on recurrent simulation property data and should be run
from within the context of the Simulation Property Editor. These files do not perform any
manipulation of initial properties, which may be accessed through the Simulation Property
Editor. Therefore, there is no need to check the box in the panel to create a new property: the
selection of an existing property suffices since no editing of that property results from running
the scripts. The filenames all have the file name suffix .CAL.
Table A.8 Simulation Property Editor example scripts
File Description
OIP Calculates the oil in place for each column of cells and posts this value to
each cell in the column.
DTPLUS1MINUST Calculates the difference in the specified property between successive
timesteps.
DTMINUST0 Calculates the difference in the specified property between each timestep
and the first timestep.
Property model property editor examples

The following Calculator scripts work on Property Model property data and should be run
from within the context of the Property Model Property Editor. The filenames all end .CAL.
Table A.9 Property Model Property Editor example scripts
File Description
PM_VARS Prints the special variables available in the Property Model Property
Editor. Also shows use of GetNumOfBUGs() and GetBUGSize().
PM_SQRTPOROPERM Sets the selected property equal to the square root of permeability divided
by porosity.

Debugging
Configuring FloGrid
Appendix B
Configuring on-line help

In the current version of FloGrid on-line help accesses the appropriate pages of the reference
section of the user guide.
----------------------------------------
SECTION HELP
----------------------------------------
FLOGRID $ECLARCH/2000a/flogrid/flog_ug/
SHARED $ECLARCH/2000a/resource/help/
FloGrid User Guide Configuring FloGrid 735

Configuring External Units
----------------------------------------
SECTION FLOGRID
----------------------------------------
SUBSECT EXTERNAL_UNITS
-- Force external unit selection at startup

ASK TRUE
Configuring the Property Model

SUBSECT MAP_DECIMATION
-- The MAP_DECIMATION controls what map decimation

-- options appear in the object appearance panel.
-- When decimation is active for a particular map
-- that map will be displayed as an NxN node map (or
-- as near to NxN as possible).
DEFAULT_DECIMATION_LEVEL 50
DECIMATION_LEVEL1 50
Configuring the Fault Framework

SUBSECT FAULT_FRAMEWORK
-- Control whether a fault framework is created for a new style

-- (2002a onwards) Flogrid model. It may be necessary to turn
-- off the fault framework build (BUILD FALSE) for efficiency or if
-- there are problems building the framework for a particular model
BUILD TRUE
736 Configuring FloGrid FloGrid User Guide

Configuring Geomodel Property Cache
SUBSECT GEOMODELS
-- The FULL_PROPERTY_CACHE_SIZE governs the size of

-- the (RESCUE and SGM) geomodel property cache.
-- This is an in-memory cache of properties that
-- are not currently in use by the user (eg. for visualisation
-- or upscaling).
-- The number FULL_PROPERTY_CACHE_SIZE is the maximum
-- number of such model-wide properties to be cached
-- in memory for possible future use.
-- It replaces the 98B option below.
FULL_PROPERTY_CACHE_SIZE 5
-- 98B and earlier:

-- The SGM_ATTRIBUTE_CACHE_SIZE is the maximum
-- number of unused SGM attributes to be cached
-- in memory for possible future use.
-- SGM_ATTRIBUTE_CACHE_SIZE 4

Coarsening for property model visualization
SUBSECT PROPERTY_MODEL_VISUALISATION_COARSENING
-- Coarsening for property model visualisation.

-- Set up level of detail options for coarsening
-- property model visualisation (options appear
-- in object appearance panel).
-- Default IJ row coarsening:
DEFAULT_NUMBER_OF_IJ_ROWS_TO_VIEW_AS_SINGLE_ROW 1
-- Possible IJ row coarsening options:
-- Default K layer coarsening:
DEFAULT_NUMBER_OF_K_LAYERS_TO_VIEW_AS_SINGLE_LAYER 1
-- Possible K layer coarsening options:
SUBSECT LOG_WINDOW
LOG_IN_MAIN_WINDOW TRUE

Configuring RESCUE model handling
SUBSECT RESCUE
-- Rescue version 26 (2001A) supports the global rotation of

-- geological models. However some rescue model writers may
-- not have this latest version. If a rotation of a
-- pre-version 26 rescue model is required then the following
-- option may be used to rotate the model on loading.
-- The parameter is number of degrees (counter clockwise)
-- from the x-axis.
-- ROTATE_MODEL 25
-- Some RESCUE models do not have the units set up correctly

-- the following configuration settings allow the FloGrid
-- reader to establish the necessary settings.
-- FORCE_X_UNITS m
-- FORCE_Y_UNITS m
-- FORCE_Z_UNITS ft
-- Some RESCUE models (notably early gOCad models) have incorrect

-- settings in the axis template. You can change the axis directions
-- to be X plus or minus, Y plus or minus, Z plus or minus
-- eg. typical gOcad settings:
-- FORCE_AXIS PX_PY_MZ
-- If a corner point RESCUE model is to be loaded but without faults

-- then the sampling may fall back to the horizons.
-- If you wich to force the sampling to be based on the grid (e.g. for
-- unfaulted RMS / gOcad models) the following setting can be used.
-- FORCE_CORNER_POINT_LOAD TRUE
-- It is possible to view the RESCUE gridded surfaces individually

-- via the main tree. This can be useful when editing
-- fault traces. Use the following option:
-- BACK_POPULATE_RDS_HORIZONS TRUE

Property map files
PROPERTY_MAP_FILE $ECLARCH/$ECLVER/resource/rescue_property_map.dat
-- Specify whether to base the RESCUE IRAP RMS model depth sampling on:
-- a) the exported horizon maps cut up and resampled (setting TRUE) or
-- b) the 3d geological grid cell tops (setting FALSE)
-- the default setting is FALSE (98B functionality corresponds to TRUE)
--
-- IRAP_SAMPLE_HORIZONS FALSE
--SUBSECT SGM
--PROPERTY_MAP_FILE $ECLARCH/$ECLVER/resource/sgm_property_map.dat
--SUBSECT GEOLITH
--
PROPERTY_MAP_FILE $ECLARCH/$ECLVER/resource/geolith_property_map.dat
SUBSECT BLOCK_UNIT_HORIZONS
-- Possible choices for map based block unit horizon extrapolation
-- are LAPLACE or BRIGGS:
-- LAPLACE is faster and extends horizontally (average of neighbours)
-- BRIGGS is slower and minimises surface curvature
-- BRIGGS is the default
EXTRAPOLATION_CHOICE BRIGGS
-- FloGrid can switch on a more refined global surface extrapolation

-- if it detects that the fault polygons cause a distant extrapolation.
-- This can be slow. The user can switch this off or limit the amount of
-- extra refinement. The defaults are given below:
-- SLOW_GLOBAL_EXTRAPOLATION_IF_REQUIRED TRUE
-- MAXIMUM_GLOBAL_EXTRAPOLATION_REFINEMENT 40

Configuring the Structured Gridder
SUBSECT STRUCT_GRIDDER
-- Specify the type of gridding to be done after the control lines are
-- constructed. TRANSFINITE_INTERPOLATION, WINSLOW or
AREA_ORTHOGONALITY
-- are the choices
STRUCTURED_GRIDDING_FLEXIBLE_GRIDDER TRANSFINITE_INTERPOLATION
-- Controls how flat the faults are allowed to go in the sloping grids
MINIMUM_SLOPE_ANGLE_DEGREES_FROM_HORIZONTAL 10
-- Significant internal changes in the structured gridder in 2001a.

-- If it is essential to replicate the 2000A behaviour then the
following
-- options can be used.
-- Suppress the new algorithm which tries to ensure that no throws

-- happen across extensions even when faults are ill-defined.
-- EARLY_ZIPUP_ABORT FALSE
-- Suppress the use of the new corner point grid data structure.
-- Note - certain options, eg grid editing, are available only
-- with the new corner point grid data structure.
-- USE_CORNER_POINT_DOMAIN FALSE
Configuring the Upgridder

SUBSECT UPGRIDDER
-- Specify the maximum number of iterations to be allowed in the

-- flow based upgridding linear solver and the tolerance for residual
-- convergence
MAX_ITS_FLOW_BASED_UPGRIDDER 500
TOLERANCE_FLOW_BASED_UPGRIDDER 1.0E-18
-- Weight variations between fine layers or slices

-- with the actual number of connections, ignoring inactive cells.
-- The default is to weight with total number of cells in the layers,
-- including inactives. Set EXTEND_PINCHED_OUT_LAYERS = FALSE for the
-- default.
EXTEND_PINCHED_OUT_LAYERS FALSE

Configuring the Upscaler for Structured Grids
SUBSECT UPSCALER
MAX_ITS_FLOW_BASED_UPSCALER 500
TOLERANCE_FLOW_BASED_UPSCALER 1.0E-20
-- IJKSAMPLING flag. Default is to use fast ijk sampling. For backwards

-- compatibility 98b and previous, set to FALSE
IJKSAMPLING TRUE
-- NON_TRUNCATED_GRID_BLOCKS_MULTIPLIER set to TRUE means that

-- the grid used for sampling before upscaling in all grid blocks that
-- are not truncated by horizons or other surfaces is the value
-- calculated by FloGrid (from the number of layers etc) multiplied
-- by NON_TRUNC_NX etc.
-- NON_TRUNCATED_GRID_BLOCKS_MULTIPLIER set to FALSE means that all
-- non-truncated blocks are subrefined to a NON_TRUNC_NX
-- by NON_TRUNC_NY by NON_TRUNC_NZ grid for sampling before upscaling
NON_TRUNCATED_GRID_BLOCKS_MULTIPLIER TRUE
NON_TRUNC_NX 1
NON_TRUNC_NY 1
NON_TRUNC_NZ 1
-- TRUNCATED_GRID_BLOCKS_MULTIPLIER set to TRUE means that

-- the grid used for sampling before upscaling in all grid blocks that
-- are truncated by horizons or other surfaces is the value
-- calculated by FloGrid (from the number of layers etc) multipled
-- by TRUNC_NX etc.
-- TRUNCATED_GRID_BLOCKS_MULTIPLIER set to FALSE means that all
-- truncated blocks are subrefined to a TRUNC_NX
-- by TRUNC_NY by TRUNC_NZ grid for sampling before upscaling
TRUNCATED_GRID_BLOCKS_MULTIPLIER TRUE
TRUNC_NX 1
TRUNC_NY 1
TRUNC_NZ 1

Configuring Save and Restore
SUBSECT SAVE_AND_RESTORE
-- FloGrid - Windows NT4.0 - Graphics Hardware Compatibility Problem

--
-- Some PC Windows NT 4.0 graphics card drivers are incompatible
-- with FloGrid 2000A default settings. This incompatibility can
-- manifest itself in a number of ways. The 3D viewer may work
-- only in software mode, may not launch at all or the user may see
-- messages stating that DDRAW.DLL did not initialise correctly.
--
-- This problem has been observed with a number of graphics card
-- drivers (Matrox, Nvidia / GeForce, ATI, Intel). It appears to be
-- caused by FloGrid making prior use of memory that the graphics
-- card driver expects to be able to use. FloGrid’s save & restore
-- facility reserves (but does not commit) a large amount of virtual
-- memory on start up.
--
-- The preferred fix is to upgrade the graphics card drivers so
-- that they do not conflict with FloGrid.
--
-- If no working graphics card driver can be found, the next
-- option is to reconfigure the FloGrid save & restore settings
-- so that they avoid any potential conflict.
--
-- To modify the save & restore settings, uncomment the following
-- lines.
--
-- FORCE_PERSISTENT_HEAP_LOCATION 0x10200000
-- FORCE_PERSISTENT_HEAP_SIZE 0x31E00000
--
-- On UNIX, by default, swap space is used to back the save & restore
-- persistent heap. The USE_SWAP_MEMORY (FALSE) setting can be used
-- to make a hidden file be used instead (as in 99B).
-- With this option the MEMORY_MAP_FILE_LOCATION variable allows
-- the user to control the location of the memory backing file used.
-- This file can grow very large. When the variable is
-- absent the memory backing file is placed in the startup directory.
-- Note this is UNIX only - PC version always uses swap space.
--
-- USE_SWAP_MEMORY TRUE
-- MEMORY_MAP_FILE_LOCATION /somewritabledirectory

Configuring Names
SUBSECT NAMES
-- Shortening names to 8 characters for Eclipse

-- Well/fault aliasing initial state.
WELL_ALIAS TRUE
FAULT_ALIAS TRUE
-- Name checking when creating a new LGR.
LGR_CHECK TRUE
Configuring the Unstructured Gridder

The configuration options listed below reflect the default settings used in the Unstructured
Gridder. Therefore, the program would still behave the same, if all of them are removed from
the configuration file.
However, if you want the program to behave different, modify the configuration options as
described below.
----------------------------------------
SECTION PETRAGRID
----------------------------------------
-- Default feature priority (boundary has top priority)
You may change this priority order to honor some features in preference to others. For example
if WELL_PRIORITY = 3 and FAULT_PRIORITY = 2, faults will be gridded in preference
to wells at intersections. Feature priorities can be set precisely in the program.
BNDRY_PRIORITY 1
WELL_PRIORITY 2
FAULT_PRIORITY 3
LAYER_PRIORITY 4
BULK_PRIORITY 5
-- Default feature intersection treatment
All line (boundary, fault, layer) intersections are handled specially and well intersections are
ignored. Although this special well/line intersection handling exists it is not recommended.
Intersection handling can be set precisely in the program.
For 2D/3D wells it is possible to control the number of 2D refinements to be included inside the
outer radius. A value of 0 means that the outer radius sets the size of the 3D radial part only.

It is possible to use extended portion of the well track (deviation) for well tracing when
BNDRY_BNDRY_X TRUE
BNDRY_LAYER_X TRUE
BNDRY_FAULT_X TRUE
BNDRY_WELL_X FALSE
FAULT_LAYER_X TRUE
FAULT_FAULT_X TRUE
FAULT_WELL_X FALSE
LAYER_WELL_X FALSE
-- Controls how flat the faults are allowed to go when sloping the
-- grid in fault framework based models
MINIMUM_SLOPE_ANGLE_DEGREES_FROM_HORIZONTAL 10
-- For 2D/3D wells this is the number of 2D refinements to be included

-- inside the outer radius. A value of 0 means that the outer radius
-- sets the size of the 3D radial part only.
NUMBER_OF_2D3D_WELL_2D_RADIAL_DIVISIONS 2
--Well tracks are clipped to the outer reservoir horizons in Petragrid.

--In models with undulating reservoir hosionz at the top or base of
--the model, there may be small unavoidable mismatches between the grid
--surface and the reservoir horizon surface if, as is likely, they are
--defined at different resolutions. If there are very thin layers in
--the grid at the top or base of the model, wells may not then be
--completed in all the grid layers expected. Extending the clipped well
--track slightly beyond the reservoir bounds can improve the well
- tracing calculation in this case
EXTEND_CLIPPED_WELL_FOR_TRACING FALSE
generating well completions.

Configuring the calculator
The Calculator can be configured to either allow or disallow system events to be processed
while a Calculator script is running. The default is to disallow event processing, as this improves
the speed of Calculator runs. However, this has a detrimental effect on the appearance of the
application while the Calculator is running. The display, including the progress bar, is updated
infrequently for Property Model Property Editor runs, and there are no updates at all while
running a Simulation Property Editor Calculator script. Changing the configuration to allow
event processing results in the application being refreshed more frequently, but causes
calculator scripts to take longer to run.
----------------------------------------
SECTION CALCULATOR
----------------------------------------
-- Whether to process system events while
-- running script
PROCESS_EVENTS_WHILE_RUNNING FALSE
Configuring layout
This configuration option is currently not used.
----------------------------------------
SECTION LAYOUT
----------------------------------------
DIRECTORY C:\ecl/$ECLVER/flogrid/grtfg_layout

Configuring the 3D Viewer
SECTION 3D
----------------------------------------
--RENDERER SOFTWARE
RENDERER HARDWARE
-- Switch between software and hardware model rendering.
--AUTONORMALISE TRUE
-- Sets autonormalise state TRUE/FALSE at Viewer startup.
-- N.B. When the first model is read into the Main Viewer,
-- it is automatically normalised. The function of
-- AUTONORMALISE TRUE is to turn on the autonormalise facility
-- for subsequent slicing etc.
--BACKGROUND_COLOR WHITE
-- Set background color to either BLACK (default) or WHITE
--MAX_CONTINUOUS 5
-- sets number of loops(5) of continous play of
-- the circular animation of the timesteps panel
LIGHTING OFF
--LIGHTING ON
-- Sets lighting ON/OFF at Main Viewer startup.
TIMER ON
--When set ON, the time for each complete time animation
--is reported in the status bar.
--If continuous animation is selected, it also gives
--the average time.
--COLOUR_LEGEND OFF
COLOUR_LEGEND ON
-- Sets color legend ON/OFF at Main Viewer startup.

FLIP_X_AXIS FALSE
FLIP_Y_AXIS FALSE
-- Sets axes flip TRUE/FALSE at Viewer startup.
ROTATION_STYLE UNCHANGED
-- Sets the rotation style at viewer startup. Choices are
-- uncganged (default), wireframe or bounds.
ROTATION_CACHING OFF
-- Sets rotation caching ON/OFF at Main Viewer startup.
-- Rotation caching holds an image of the model in the
-- platforms memory. This makes model rotation appear
-- smoother.
OUTLINE_LIFT 0.7
--To avoid cell outlines being drawn co-incident with
--their surfaces, the outlines are lifted a small amount
--above the surface. With thin cells this may cause lines
--from cells below to come through. Reducing the lift
--scale reduces this effect, but may make the lines
--appear dashed when viewed at a low angle.
--Can be redefined via the
--Preferences | Outline Control panel.
TITLES ON
--TITLE Version $ECLVER
--The first entry determines whether titles are to
--appear in the Main Viewer upon startup.
--It can be redefined via DISPLAY | TITLES | Show Titles.
--The second entry sets the contents of the title.
--It can be edited via DISPLAY | TITLES | Edit Titles.
--The default depends on the application.

Stereo support
--STEREO TRUE
--This option adds stereo support to a Main Viewer for Silicon Graphics
--platforms only
--On other platforms the option is disabled.
--
--Only the SSI and Infinite Reality graphics accelerators support
--"stereo in a window" (because they are the only ones with quad-buffered
--support). For all other SG graphics accelerators, it is necessary to first
--make the viewer fill the BOTTOM HALF of the screen.
--
--The stereo effect alternatively displays the left & right images. To view
--these it is necessary to use a system such as CrystalEyes (TM). This
--consists of glasses containing LCD shutters and an infra-red transmitter to
--synchronise the opening & closing of the individual lenses with the display.
TEXT_HEIGHT 12
--This sets the font height used for text in the Main Viewer. It is used for
--the text used in the title, color legend, axis & axis tick marks, well
--labels etc.
--It can only be altered interactively at present for the titles.
--This entry is useful if, for some reason, the system does not support
--scaled fonts. In this case it may be necessary to start a Main Viewer, add
--a title and adjust the font height until the text is visible, then set the
--TEXT_HEIGHT to this value before re-running the application.
Mouse settings
--MOUSE_BUTTONS 3
--Determines the number of mouse buttons to be used. Valid values are 2 or 3.
--An attempt is made on PC's to determine this value from the system metrics,
--but this has proven unreliable. Cannot be redefined, defaults to system given
--metrics on PC, default to 3 on UNIX.
--Note that this setting is useful when running remote applications. If a
--program is being run on a UNIX workstation, but being viewed via an xterm on
--a PC, then the program will expect a 3 button mouse, unless MOUSE_BUTTONS is
--set to 2..
--MOUSE_SETTINGS RTVIEW
--Determines the settings of mouse buttons. Can be RTVIEW or GEOFRAME. If
--present this overrides any 2BUTTON_MOUSE or 3BUTTON_MOUSE subsections. Can
--be redefined interactively.

--SUBSECT 2BUTTON_MOUSE
--PICK LEFT
--ROTATE RIGHT
--TRANSLATE <SHIFT>LEFT
--SCALE <SHIFT>RIGHT
--Z_TRANSLATE <CTRL>LEFT
--Determines the mouse settings for a 2 button mouse. These settings can be made
--independent of whether a 2 or 3 button mouse is used - the settings used will
--depend on MOUSE_BUTTONS. This subsection is optional, if not present the
--default settings will be chosen. Cannot be set interactively.
--The first four settings must be given, Z_TRANSLATE is optional and if not
--given there will be no functionality for this. Settings must not be duplicated
--(i.e. <SHIFT>LEFT if defined, must be used only once in this subsection). If
--a modifier is given it must be either "<SHIFT>" or "<CTRL>". The button to be
--used must be either "LEFT" or "RIGHT" and must come immediately after the
--modifier. If an error is found when decoding this subsection the default
--settings (as shown) will be used.
--SUBSECT 3BUTTON_MOUSE
--PICK LEFT
--ROTATE MIDDLE
--TRANSLATE RIGHT
--SCALE <SHIFT>MIDDLE
--Z_TRANSLATE <SHIFT>RIGHT
--Determines the mouse settings for a 3 button mouse. These settings can be made
--independent of whether a 2 or 3 button mouse is used - the settings used will
--depend on MOUSE_BUTTONS. This subsection is optional, if not present the
--default settings will be chosen. Cannot be set interactively.
--The first four settings must be given, Z_TRANSLATE is optional and if not
--given there will be no functionality for this. Settings must not be duplicated
--(i.e. <SHIFT>LEFT if defined, must be used only once in this subsection). If
--a modifier is given it must be either "<SHIFT>" or "<CTRL>". The button to be
--used must be either "LEFT", "MIDDLE" or "RIGHT" and must come immediately
--after the modifier. If an error is found when decoding this subsection the
--default settings (as shown) will be used.

Viewers
SUBSECT MASTER_VIEWER
X_START 0
Y_START 100
WIDTH 600
HEIGHT 420
SUBSECT SLAVE_VIEWER
X_START 640
Y_START 100
WIDTH 600
HEIGHT 420
-- You may set the initial location and size of the master and slave viewers.
-- These options may be especially useful on small screens where the default
-- settings may be too large for the screen itself.
SUBSECT AUTOAPPLY
ANIMATION OFF
AXES OFF
DOMAIN_SELECTION OFF
EXAGGERATE OFF
IJK_SLICING ON
LIGHTING ON
THRESHOLD OFF
COLOUR_LEGEND_EDITOR ON
-- These settings can be redefined on the relevant panel
-- using the right mouse button click drop down menu.
-- These options can also be set in the program(s) via
-- Preferences | Autoapply
SUBSECT ANIMATION
DELAY 0.0
-- Determines the number of seconds delay
-- between animation timesteps
-- This can be redefined via the Grid | Timesteps |
-- Timestep Options panel.

Wells, ternary legend, grid, decimation level
display
SUBSECT WELLS
--RADIUS 10
-- The grid X and Y dimensions are used to compute a sensible well radius.
-- However, sometimes unusual dimensions can cause a strange well radius to be
-- computed. Use this option to override this value if required
--SUBSECT TERNARY_LEGEND
--XPOSITION 0.4
--YPOSITION -0.75
--HEIGHT 0.2
--ORDER RGB
--This overrides the appearance and location of the ternary legend.
--The ORDER defines the mapping of the 3 saturations,
--Gas, Oil & Water in that order to the colours Red,
--Green & Blue in the example.
SUBSECT GRID
CONVERT2CORNER FALSE
-- The CONVERT2CORNER flag is used to convert the image -
-- of a block-centred grid into a smoothed grid for the
-- purposes of display.
-- It should not be used on a corner point grid.
--DEFAULT_DECIMATION_LEVEL 10000
DEFAULT_DECIMATION_LEVEL ALL
-- The DECIMATION_LEVEL entries define the
-- level of detail for the display of a grid in terms
-- of the number of cells to be displayed.
-- Any number of levels can be defined.
-- These will then be displayed on the “Object Appearance
-- panel” “Level of Detail” drop down menu.
-- The DEFAULT_DECIMATION_LEVEL can be set to ALL
-- or a number.
-- option.

Cell display defaults
DISPLAY_CELLS ON
DISPLAY_CELL_OUTLINES ON
-- The "DISPLAY_CELLS" entry determines if a grid\222s cells should be

-- drawn when first displayed. By default the cells are displayed.
-- This can be redefined interactively by the Grid/Display/Cells
-- option and the associated toolbar icon.
IFACE+ ON
JFACE+ ON
KFACE+ ON
IFACE- ON
JFACE- ON
KFACE- ON
-- The "DISPLAY_CELL_OUTLINES" entry sets if a grid\222s cell outlines
-- should be drawn when first displayed. By default the outlines are
-- not displayed. This can be redefined interactively by the
-- Grid/Display/Outlines option and the associated toolbar icon.
-- "IFACE+" through to "KFACE-" indicate if the relevant cell face
-- should be displayed. Note that if all faces are set to ON, then
-- faces interior to the model will not be displayed. Setting all
-- faces to OFF (default) has the same effect as turning them all
-- ON. These can be set interactively by the Grid/Display/Faces
Streamlines
SUBSECT STREAMLINES
--LEVEL_OF_DETAIL Line
-- Sets the initial level of detail with which the streamlines are first
-- displayed. This is settable interactively from the Object Appearance panel.
-- Valid values are Low, Medium High and Line. Default is Line.
--TUBE_RADIUS 1.0
-- Sets the radius of the streamlines when displayed as tubes (with levels of
-- detail Low, Medium and High). Tubes take longer to draw but give a better
-- visual effect particularly with lighting turned on. Default is 0.5.

PostScript output files defaults
SUBSECT POSTSCRIPT
FILENAME grtframe.ps
SIZE A4
WIDTH 120.0
HEIGHT 160.0
ORIENTATION LANDSCAPE
COLOUR_MODE COLOR
-- This subsection defines default values for the production of hard

-- copy via vector Postscript.
-- All the values can be changed interactivly via the File/Save
-- As/Postscript option.
--
-- The FILENAME will be the name of the file created (note - if a
-- name is entered without .ps, this will be added automatically).
-- If no FILENAME entry is present, the default will be as set by
-- the application (e.g. floviz.ps). If TMPDIR is not set, the
-- directory used for the file will be the start-up directory
--
-- The size can be any one of 5 values. It defaults to A4 if not
-- set.
--
-- EPS (Encapsulated Postscript, any
-- size)
--
-- A (US letter size, 280x216 mm.)
-- B (US ledger size, 432x280 mm.)
-- A4 (ISO A4, 297x210 mm.)
-- A3 (ISO A3, 420x297 mm.)
--
-- The width & height are only used for Encapsulated Postscript. For
-- this they default to 120x160 mm. Encapsulated Postscript is used
-- to embed documents in word processing and desk-top publishing
-- packages.
--
-- Changing the orientation between Landscape and Portrait
-- effectively rotates the image. If not set this defaults to
-- Landscape.
--
-- The COLOUR_MODE can be COLOR or GREYSCALE (the spelling
-- GRAYSCALE is also accepted). Although COLOR can be used on a
-- monochrome printer, using GREYSCALE may result in a smaller file.
-- The default, if not set, is COLOR.

Image output defaults and Editor defaults
SUBSECT WRITE_IMAGE
FILENAME grtframe.jpg
FILETYPE JPEG
-- This subsection defines default values for the production of image files
-- which can be used in word processors, web pages etc.
-- All the values can be changed interactivly via the File/Save As/ option.
--
-- The FILENAME will be the name of the file created (note - if a
-- name is entered without a suffix, this will be added automatically).
-- If no FILENAME entry is present, the default will be as set by
-- the application (e.g. floviz.jpg). If TMPDIR is not set, the
-- directory used for the file will be the start-up directory
--
-- Three different filetypes are supported JPEG, TIFF and PBM (Portable
-- Bit Map). JPG & TIF are also accepted.
SUBSECT EDITOR
-- This subsection configures the Main Viewer's editor.
-- ALLOWPCHARDWARE TRUE
-- This switch controls whether the hardware renderer is allowed during
-- editing on the PC. The default is TRUE but experience has shown that there
-- can be problems with the lines drawn over the 3D view during editing. With
-- the switch set to TRUE the hardware renderer is allowed (for greater speed)
-- but the screen will flash black the first time it is used to attempt to fix
-- the display problem. FALSE will simply use software rendering which has
-- proved slow but reliable

FloGrid License Features
Table B.1 FloGrid License Features
Module License Options

FloGrid gf_flogrid 3D Structured Gridder
2D Mapping
Upscaling / Upgridding
Local Grid Refinement
Visualization gf_floviz 3D Visualization
FloGrid Properties gf_fg_populate Well Correlation
Cell Population
Fault Property Calculation
FloGrid Reservoir Analysis gf_fg_analysis Volumetrics
Well Planning
Simulation Link
(Uncertainty)
Unstructured Gridding gf_petragrid Unstructured Gridder
FloGeo gf_flogeo, gf_scal Multiphase upscaling
The table above shows which license features are required for the various options within
FloGrid.
The gf_flogrid license feature covers the basic features of FloGrid, including the structured
gridder, 2D mapping and upscaling/upgridding; the gf_floviz license feature enables the 3D
visualization features.
The property population options such as cell and fault property calculation, and the well
correlation option are covered by the gf_fg_populate license feature.
The reservoir analysis options, which include the volumetrics, well planning, simulator link and
uncertainty functionality are covered by the gf_fg_analysis license feature.
Advanced FloGrid options such as the unstructured gridder and multiphase upscaling
functionality have their individual license features gf_petragrid, gf_flogeo and gf_scal.
Note The license features described here are sold in license bundles, consisting of a group
of license features. For example, the gf_fg_populate and gf_fg_analysis features are
sold as a single bundle. Contact your account manager for details of FloGrid license
bundles and pricing.

FloGrid License Features
Construction of Units and
Horizons from Mesh Maps Appendix C
Introduction
There are two stages in the creation of the surfaces (Block Unit Horizons) that bound each unit
within each block in FloGrid.
• "Construction of units and horizons" on page 757
(using the selection of maps from the main window surface tree).
• "Construction of block unit horizons" on page 758
(using the blocks from the block splitting algorithm).
The first stage allows you to specify how maps and thicknesses are combined to define the
layers in the model. In the second stage FloGrid ensures that the horizons can be sampled while
still respecting any fault-throws correctly.
Construction of units and horizons

The pre-condition for this stage of the construction is that you have
• imported two or more maps into the main window surface tree
• specified that each map is a horizon, a thickness or a nonconformity
• assigned each chosen map to a surface in depth ordered.
A suitable resolution and extent must be determined for the model (that is an X Y-origin, a DX,
a DY, an NX and an NY). This is done by taking the union of all the extents, of all the chosen
input maps, and choosing the finest resolution in the X and the Y direction from all the chosen
maps.
Often all the maps have the same resolution and extent and this is chosen as the resolution and
extent of all the structural framework horizons (SM-horizons) so that all the maps have identical
resolution and extent.
FloGrid User Guide Construction of Units and Horizons from Mesh Maps 757
Introduction
Then the number of units is determined and one mesh map is created for the top of each unit
plus one for the base of the bottom unit. These maps become the structural framework horizons
(SM-horizons) above and below each unit.
The maps are either created by sampling the relevant map directly or by sampling the relevant
thickness map and adding it (recursively if necessary) to the reference map. There are, however,
a number of rules for this sampling and addition:
1 If the extent of the map is less than that of the SM-horizon, the nearest value on the edge of
the map is taken.
2 All nulls in horizons or nonconformities are passed into the SM-horizons as nulls, that is,
if a map cell has any non-null nodes then a bilinear interpolation is taken, or else null is
posted to the target SM-horizon node.
3 All nulls in thickness maps are either interpolated away by replacing them with the nearest
non-null value, or interpreted as zero. This takes place prior to any addition. This usually
results in nulls being treated as zeros, as thickness maps often taper off to zero thickness
before introducing nulls. It also avoids spikes developing in the holes in the thickness maps
(surrounded by non-zero values), (for an example see the grainne data set). The option
to switch to Null Interpretation may be needed if a thickness map tapers away to almost
zero but not quite. A menu item on the right mouse button drop-down menu of the maps
allows this choice to be made.
4 If a thickness non-null value is added to a null value sampled from a map then the resulting
value is null.
Horizon-Nonconformity rules
Starting from the bottom map the standard Horizon-Nonconformity rules are now applied to
create a set of conforming SM-horizons. The Horizon-Nonconformity rules are:
1 A horizon deposits on any lower surface; that is the lower surface value dominates.
2 A nonconformity erodes any lower surface; that is the lower surface value is dominated by
the nonconformity.
3 If the surface being added has a null, it remains null.
4 If a surface is non-null and is being compared with a null, it always dominates the null.
Construction of block unit horizons

The pre-condition for this stage is that a list of conforming SM-horizons has been defined and
that fault block splitting has been performed. Fault block splitting divides the structural
framework region (area of interest, AOI) into areas (blocks) whose boundaries consist of
portions of actual fault trace and portions of fault trace extensions.
For every block in the splitting, the following sequence of steps is repeated:
Creating mesh surfaces

Create a new mesh surface (a block unit horizon) for every SM-horizon in this block.
The extents of this new mesh surface are just enough to completely cover the block and the
resolution of the surface matches exactly that of the SM-horizon, that is the nodes correspond
exactly. These surfaces are the block unit horizons (BU-horizons).
758 Construction of Units and Horizons from Mesh Maps FloGrid User Guide
Introduction
Sampling across block boundaries
Ensure that sampling across block boundaries respects the fault throws (but is zero across an
extension) by performing the following operations:
1 Make every node on the surface null if is more than four grid cells away from the block
boundary.
2 Make every node null if it is within one cell of an actual fault trace.
3 Make every node null if it lies within a fault trace polygon. (This is in addition to any nulls
that have come through from the copied SM-horizon.)
4 Record every null node. (They will receive special treatment after extrapolation.)
Extrapolate and smooth away all the null nodes

1 Make an initial guess as to the value the surface modeler will converge on (fill in all nulls
with the nearest non-null value).
2 Now use the Laplacian Surface Modeler to extrapolate/interpolate all nodes that were
null and are within four grid cells of the boundary. (Ignore all nodes further away while
extrapolating.)
3 Re-nullify all nodes more than two grid cells from the boundary and replace these nodes
with the nearest non-null node.
This achieves sufficient surface smoothness and speed.
Surface limiting rules

Apply the surface limiting rules to these surfaces to ensure that they conform.
The surface limiting rule is:
• Starting from the top, each BU-horizon node dominates all nodes below it, except if the
node was once null and the one below it was never null (in that case the one below
dominates).
This rule when applied to every column of nodes achieves a conforming set of BU-horizons
where original null data never dominates real surface data.
Inserting horizon definitions

Insert the BU-horizon definitions into the wireframe description of the blocks to create the block
units.
FloGrid User Guide Construction of Units and Horizons from Mesh Maps 759
Introduction
760 Construction of Units and Horizons from Mesh Maps FloGrid User Guide
Introduction
Appendix D
Introduction
In this section we first define the concept of a corner point grid and then outline the main stages
that are performed by FloGrid to build a corner point grid. Finally we give some detailed
information on some of the options. These topics are set out in the following sections:
• "Corner point grids" on page 762
• "Building a corner point grid" on page 764
• "Further remarks on the user specified parameters, and user choices" on page 769.
FloGrid User Guide Corner point gridding 761

Introduction
Corner point grids
The main components of a corner point grid are:
• Coordinate lines
• Coordinate tubes
(which have coordinate lines as their edges)
• Grid blocks
(obtained by slicing the coordinate tubes with the horizons).
Coordinate lines
These are parallel, vertical or sloping, straight lines drawn downwards from the corners of the
quadrilaterals in a structured areal grid.
An example of a structured areal grid of quadrilaterals is shown in Figure D.1. From each of the
corners of the quadrilaterals coordinate lines extend vertically downwards, or in this case, into
the page.
Figure D.1 An example of a structured grid of quadrilaterals
Coordinate tubes
A 3D view of a coordinate tube is shown in Figure D.2. These coordinate tubes are the vertical
extensions of the quadrilaterals of the structured areal grid, as outlined by the coordinate lines.
762 Corner point gridding FloGrid User Guide

Corner point grids
Figure D.2 The coordinate tube with coordinate lines as edges
Areal Grid Projected

onto the Tops Map
Co-ordinate
Line
Co-ordinate Tube
Grid blocks
The coordinate tube is sliced into grid blocks by placing points on each coordinate line, where
it is sliced by the horizons and using the four points to define four of the corner points of the
grid block. If there are n+1 horizons cutting each tube then there are n grid blocks in the
coordinate tube. This is illustrated in Figure D.3 for n = 1.
Figure D.3 Grid blocks obtained by slicing coordinate tubes
Corner Point
Grid Block

Corner point grids
Building a corner point grid
The Areal (Coordinate Line) Gridder builds a set of coordinate lines which form an Nx by Ny
coordinate tube grid. This grid honors the boundary, and selected i- and j-control lines.
Coordinate lines that are not constrained to lie on a boundary or control line are positioned
according to controlled gridding parameters.
The Vertical (Block) Gridder divides the coordinate tubes into grid blocks using the horizons
and the specified simulation layering options in each geological layer.
The construction of a corner point grid is done in two parts.
1 Areal gridding which involves six steps:
• Specifying a boundary and selecting control lines to honor.
• Building an internal irregular triangulation which honors the selected control lines and
boundary.
• Constructing i- and j- vector fields.
• Extrapolating the gridded control lines using the vector fields.
• Distributing coordinate lines along the control lines and the boundary.
• Distributing the remaining coordinate lines.
2 Vertical gridding:
• Construct sloping or vertical coordinate lines. Sloping coordinate lines use slopes from
I, J and zigzag control lines.
• Construct simulation layers.
More details about each of the steps are provided below.
Areal gridding
In the following sections, the description of areal gridding is occasionally simplified by
referring to I and J control lines as I and J faults. In situations where faults are complex and / or
change direction, it is more likely that you will construct I and J control lines from sections of
faults.
Stage 1
You are required to define a boundary so that it is either a rectangle or an irregular rectangle. A
good boundary follows the trend of the faults that you wish to honor in the simulation grid. See
Figure D.4.

Figure D.4 A boundary, two i-faults and a single j-fault
Corners j-fault
Boundary
i-fault
The faults are then classified by you as i-faults, j-faults or zigzag faults.
• I-faults are those faults that have a constant i value in the generated simulation grid (for
example an i-fault could lie on the i = 3 line).
• J-faults will lie on grid lines of constant j.
• The zigzag faults are those which do not line up with the boundary, or are too distorted.
These are not handled by the areal gridder.
Stage two
The software builds an irregular grid of triangles that honors the boundary and all the selected
faults. This is done by sequentially modifying the starting triangulation and adding each line-
segment from the boundary or the faults in turn. This stage is invisible to the user.
Stage three
FloGrid constructs two vector fields with vectors calculated for each node of the triangular grid.
Nodes lying on the boundary or a fault have vectors which are forced to honor the tangents to
the boundary of faults. Vectors on the remaining nodes are interpolated.
As a result of this, one set of field lines follows the i-lines and one set follows the j-lines.
The interpolation is either isotropic or anisotropic. There is also an orthogonality control,
which biases the vector fields towards mutually orthogonality (refer to "Orthogonality" on
page 769).
• Isotropic interpolation reduces the influence of sharp bends in the faults or boundary.
• Anisotropic interpolation causes such discontinuities to be exaggerated further.
We illustrate the effect of this choice a little later. See "Isotropic and anisotropic gridding" on
page 769 for more details.

Stage four
Integral curves are constructed away from the two ends of each fault. These integral curves are
the lines which, if you have made a good classification of the faults, and provided a suitable
boundary, partitions the area inside the boundary into regions (sub-grids), which can be
continuously distorted into a rectangular grid.
Figure D.5 Smooth extensions of faults to the boundary
Smooth Fault
Extension
Stage five
Now points are distributed along the extended control lines, between the points at which the i-
lines intersect the j-lines.
The number of points to be distributed is controlled either globally or locally:
• Globally, whereby an overall Nx and Ny is specified, and FloGrid decides the distribution.
• Locally, by specifying the Nx between any pair of i-lines or Ny between any pair of j-lines.
The smoothness parameter controls how this is done. When set to zero the points are placed
equidistant between the intersections. If the smoothness is increased, to a maximum of one, the
points are distributed in a more smooth way, so that the distance between successive pairs only
changes gradually (refer to "Smoothness" on page 769). This is illustrated in Figure D.6 and
Figure D.7 where one of the lines is moved markedly to the right because the adjacent sub-grid
has a higher density of grid lines.
Stage six
The final grid of coordinate lines is constructed by interpolating the boundary points of each
sub-grid using the transfinite interpolation method.

Figure D.6 Control lines with some additional lines - zero smoothness
Figure D.7 Control lines with some additional lines - with smoothness
The slopes of the coordinate lines built by the areal gridder are determined by which vertical
gridding options are used.
If vertical coordinate lines are requested, the coordinate lines used in the corner point grid are
obtained by dropping straight lines, vertically, from the nodes of the areal grid.
If sloping coordinate line grids are requested the slopes of the coordinate lines are determined
by the slopes of all I, J and zigzag control lines.
Vertical gridding
In this section we use the notion of a fault block (more correctly a block, but we wish to
emphasize the difference between a block in the structural framework and a grid block in a
simulation grid).

The software assigns each coordinate tube to one or more fault blocks, on the basis of how the
coordinate tube intersects the block units in the vicinity of the tube and depending on whether
you have specified that a tube can represent multiple blocks.
You have the option at this stage of specifying how many simulation layers are to be placed
inside each unit and whether these additional layers are constructed using a proportional
layering scheme or by using fixed thickness layers conforming to the upper or lower surface.
The horizons inside the fault block are used to slice the coordinate tube into grid blocks by
locating the intersections of the coordinate lines with each horizon, and using the four points to
define four of the corner points of the grid block.
If the geological layer is to become the simulation layer then the two horizons (top and bottom)
of the geological layer, slicing the coordinate tube, define the eight corner points for a single
simulation grid block.
If, however, the geological layer is to be divided into a given number of simulation layers then
each of the segments of line between consecutive points on the coordinate lines are divided
according to whether proportional or fixed thickness layers are required.

Further remarks on the user specified parameters, and
user choices
Orthogonality
Orthogonality is a weight factor between zero and 1 that biases the vector fields, and also the
control lines, towards mutual orthogonality. If the weight is zero the lines tend to follow the
boundaries or their respective control lines. If the weight is set to 1 the field lines will try to cross
at right-angles to one another. If the boundary or the control lines are not themselves mutually
orthogonal, then the vectors are not exactly orthogonal. In this case the program calculates the
best values of orthogonality, which are somewhere in between these values. A little
experimentation may be necessary to create a grid meeting your specification.
If the boundary or control lines contain any very sharp corners, then the application of some
orthogonality is essential if inside-out grids are to be avoided. Sometimes a control line cannot
be characterized as an i- or j-line and is best treated as a zigzag control line. Similarly, if the
boundary is too complicated this can also lead to inside-out grids.
The Structured Gridder is based on the idea that the grid is a distorted rectangular grid. If the
target lines are too distorted from a rectangular grid it causes an error. The software will alert
you to this and you will then have to adjust the boundary or change the control line
classification.
Smoothness
The smoothness of the simulation grid is controlled by the spacing of the points on the extended
control lines you have specified. If the smoothness is set to zero then the points along the control
line extensions are equally spaced for all control lines. Thus the distance between pairs of points
can show a distinct jump as one moves between the control line regions. If the smoothness is set
to 1.0 then the distance between points will be varied smoothly between the different control
lines. This control is achieved with a non-linear tension spline algorithm.
Isotropic and anisotropic gridding

The main options in areal gridding are isotropic and anisotropic interpolation of the vector
fields.
In isotropic gridding, the Gridder sets the i-vector at the corner of a triangle to the weighted
average of, the vector that is orthogonal to the j-vector at that corner and the arithmetic average
of the i-vectors at the corners of any triangles sharing the first corner. This requires an iterative
process, and is the main cause for the time required by the Gridder to accomplish its tasks. The
j-field is constructed in a similar way.
In anisotropic gridding the arithmetic average is replaced by a distance weighted average. This
takes longer to compute, and is the reason for the increased creation time for this type of grid.

Further remarks on the user specified parameters, and user choices
The difference between the two types of gridding is best illustrated by the result obtained from
running both methods with the same data. In many cases isotropic and anisotropic gridding
produce very similar results. However, in some circumstances, such as illustrated in the
following illustrations, the grids are markedly different.
In the illustrations, the fine lines show the original faults, and the bold lines show the extensions
added.
Figure D.8 Fig. 5. An example of isotropic gridding between two faults
Figure D.9 Fig. 6. An example of anisotropic gridding between two faults
Performance and quality

The Gridder runs fastest if isotropic gridding without orthogonality is used.
The Gridder produces the best quality grid with high orthogonality and smoothness weightings.
However, quality is a subjective concept and so some experimentation is suggested.

Export of IJK Faults
If the I, J and K faces option is selected in the vertical gridder, a fault location may be
represented by partial cell faces. This happens when there is the combination of K-zigzagging
of one fault and of split grid block faces at a second fault. The split faces result from a throw
across a fault along which the grid has been sloped. For example, near the intersection of the
two parts of a Y fault, as shown below the zigzagged fault is located within in the grid between
the two gray grid blocks, but only exists on part of the face of each block. The ECLIPSE
FAULTS keyword defines the grid fault location within the simulation grid in terms of complete
cell faces only, and so the alternative fault location export method using MULTNUM and
MULTREGT must be used
Figure D.10 An example where FAULTS keyword cannot fully represent simulation grid location

Input file formats
Appendix E
Input file formats

This appendix details the formats for FloGrid’s input data files. It contains information on the
following:
• "Contour Map Control files" on page 774.
• "Mesh Map Data" on page 781.
• "Scatter sets data" on page 783.
• "Well Markers Data Formats" on page 794.
• "Well Logs Data Formats" on page 795.
• "Property model input formats" on page 798.
• "Geolith / Chears input format" on page 799.
FloGrid User Guide Input file formats 773

Input file formats
Contour Map Control files
Control file format

A control file is organized as a list of one or more control sections.
A control section consists of a format description and data location information.
A control section is not delimited by any specific keyword but it is automatically recognized
once a valid format and a list of data file locations are specified.
A typical control file probably contains a single format description and one or more data
locations.
Hint As a control file can contain several control sections, reading multiple contour maps
with different formats can be done using a single control file.
Control section keywords

Control sections in contour control files are specified using a set of keywords.
Keywords are followed by parameters (also known as data items) that determine the meanings
of the keywords.
A keyword and its parameters can extend (or be broken) across several lines (that is putting line
breaks), as long as each line (before the last) is terminated by the continuation line character ’\’.
Blank lines are ignored.
Control files can contain comments by starting each comment line with a double hyphen ’--’.
Hint For consistency with other types of control files (for example Wells in GRID format -
used throughout FloGrid) the terminating END keyword (at the end of the control file)
is allowed, although not required.
Data format keywords

It is assumed that contour map data are organized as consecutive chunks of data, each chunk
representing a contour line. Each contour line data chunk may begin with header lines (that is
lines carrying some extra information, not part of the contour line data).
The following declarations are used to define data formats.
HEADER
This keyword can be used for two different purposes: either to ignore contour line headers or to
retrieve relevant information from them.
774 Input file formats FloGrid User Guide

The former usage requires the syntax:
HEADER n
where n is a positive integer. The effect is to skip n header lines before each contour line.
The syntax for the latter usage is:
HEADER n POSITION m MARKER
or
HEADER n POSITION m LEVEL
where n and m, both positive integers, indicate, respectively, the header line number and the
field position where the information is stored.
MARKER indicates that the value in the field m on the header line n is used to determine the end
of a contour line data chunk, whereas the LEVEL states that the value in the field m on the header
line n is the property value associated with the contour line to be read.
MARKER
This keyword is used to set a global value (that is throughout all contour lines) to be interpreted
as the end of a contour line data chunk.
Its syntax is:
MARKER value
where value is a real number.
LEVEL
This keyword is used to set a global value (that is throughout all contour lines) to be interpreted
as the property value associated with all contour lines to be read.
Its syntax is:
LEVEL value
where value is a real number.
ATTRIBUTE
The keyword ATTRIBUTE describes the meaning of the fields forming the Contour line data
(which begins after the header - if any)
Its syntax is:
ATTRIBUTE name POSITION n UNITS units
where:
• name is one of the following quantities: ID, X, Y, Z, LEVEL
• n is a positive integer value indicating the field position where the quantity name is stored

• units indicates in which units of measurement the quantity name is expressed. The value
NONE can be entered.
Note The attribute Z does not relate to the property value associated to a contour line, but
represents the Z-coordinate when importing a 3D contour.
Note Currently, only the quantities X, Y, Z, ID, LEVEL are recognized. If, accidentally,
another string is input, a warning message is issued and the operation continues (that
is the whole keyword is ignored).
START
This keyword is used to skip an initial chunk of lines in the Contour Map data file.
Its syntax is:
START n
where n is a positive integer.

The presence of this keyword implies that the first n lines of the data file are to be ignored
(starting on the n+1-th line). If this keyword is not present, a default value of 0 is used.
Data location keywords

FILE
The FILE keyword is used to specify the location of contour map files.
It takes an arbitrary number of file locations:
FILE location1 [location2...]
Note All contour maps located by the FILE keyword must be in the same format.
A file location can continue on subsequent lines provided that each line before the last is ’\’
terminated (that is the line-feed/carriage-return is escaped). If a location contains spaces, the
string needs to be delimited by the double-quote ’"’ characters.
Note If a location consists of a file name without an absolute path (that is either there is a
relative path or there is no path at all) the location of the file is considered to be relative
to the location of the control file.

Examples
In order to illustrate the information above, a series of known contour map formats are
considered and example control sections provided.
Example 1 - Z-MAP Plus Format (Landmark)

Contour maps can be exported from Z-MAP Plus in a range of equivalent formats. One possible
format is
ZNON ZNON
Level Continuation Flag
X Y
... ...
... ...
-ZNON -ZNON (optional)
where the -ZNON, if present, delimits the end of the entire contour map (and not a contour line).
For example:
0.1000E+31 0.1000E+31
9500 1.2
1200 826.1
1400 832.2
0.1000E+31 0.1000E+31
9600 1.4
1522 1000
1568 1200
1578 1400
-0.1000E+31 -0.1000E+31
represents a contour map with 2 contour lines:

the first consisting of 2 2D points and a property value of 9500,
the second consisting of 3 2D points and a property value of 9600.
Note The continuation flag (2 decimal-point separated integers) is not used in FloGrid (and
is, therefore, ignored).
The Control Section becomes:
-- Data Format
HEADER 1 POSITION 1 MARKER
-- alternatively HEADER 1 POSITION 2 MARKER
HEADER 2 POSITION 1 LEVEL
ATTRIBUTE X POSITION 1 UNITS FEET
ATTRIBUTE Y POSITION 2 UNITS FEET
-- Data Location
FILE ../contour.dat

Example 2 - GRID Format (SIS)
The SIS GRID application can export contour maps in this format:
*
X Y Z
... ... ...
Marker Marker Marker
X Y Z
... ... ...
X Y Z
... ... ...
The initial ’*’ character is just a place holder and carries no information.
Unlike Z-MAP Plus formats, here the marker is placed at the end of a contour line (rather than
at the beginning) and therefore cannot be read in a contour line header but must be declared
globally.
The previous contour map becomes:
*
1200 826.1 9500
1400 832.2 9500
0.1000E+31 0.1000E+31 0.1000E+31
1522 1000 9600
1568 1200 9600
1578 1400 9600
0.1000E+31 0.1000E+31 0.1000E+31
The data format can be described as follows:
HEADER 1
START 1
MARKER 0.1000E+31
ATTRIBUTE LEVEL POSITION 3 UNITS FEET
-- and the data location as in previous examples
FILE ../contour.dat

Example 3- Identifier format
Most of the contour maps are imported with a identifier for each contour line. One possible
format is
# X Y SEG_ID ELEVATION
3680.432780000 33.87013000000 1 180.0000000000
3893.349107000 143.9480520000 1 180.0000000000
4033.590076000 220.1558440000 1 180.0000000000
4227.920473000 320.0727270000 1 180.0000000000
4488.123494000 462.3272730000 1 180.0000000000
4577.654726000 523.3428710000 1 180.0000000000
4702.642282000 630.2238060000 1 180.0000000000
4785.334121000 723.5158430000 1 180.0000000000
4889.936035000 850.7270960000 1 180.0000000000
5018.030579000 1047.459190000 1 180.0000000000
5093.832092000 1178.042761000 1 180.0000000000
5178.058931000 1322.193803000 1 180.0000000000
5206.721948000 1362.898362000 1 180.0000000000
5257.184076000 1473.122690000 1 180.0000000000
5300.898545000 1574.866411000 1 180.0000000000
5342.850803000 1698.647498000 1 180.0000000000
3307.445977000 179.5116880000 2 170.0000000000
3425.708884000 247.2519480000 2 170.0000000000
3587.903291000 338.7012990000 2 170.0000000000
3755.164348000 433.5376620000 2 170.0000000000
3934.276322000 528.3740260000 2 170.0000000000
4101.562005000 616.4363640000 2 170.0000000000
4273.949336000 704.5444140000 2 170.0000000000
The data format can be described as follows:
START 1
ATTRIBUTE ID POSITION 3 UNITS NONE
ATTRIBUTE LEVEL POSITION 4 UNITS FEET
-- and the data location as in previous examples
FILE ../contour.dat
Example 4- 3D contours
As explained earlier, a 3D contour map can be considered as a collection of 3D surfaces, with a
scalar property value associated to each.
Note In previous examples, Z indicated the property value associated to a particular contour
line. In this section Z indicates the third coordinate of the 3D points defining a surface.
The scalar property value associated to the surface is indicated with P.

The format layout is:
*
X Y Z P
... ... ... ...
Marker Marker Marker Marker
X Y Z P
... ... ... ...
X Y Z P
... ... ... ...
In the example contour map used above, let’s consider the level values as Z coordinates and
associate a property value of 0.6 to the first surface and 0.8 to the second.
The data file becomes:
*
1200 826.1 9500 0.6
1400 832.2 9500 0.6
0.1000E+31
1522 1000 9600 0.8
1568 1200 9600 0.8
1578 1400 9600 0.8
0.1000E+31
Hint The marker value need not be repeated for each column of data.
The description of the format is:
START 1
HEADER 1
MARKER 0.1000E+31
ATTRIBUTE Z POSITION 3 UNITS FEET
ATTRIBUTE LEVEL POSITION 4 UNITS dimensionless
-- and the rest as in previous examples

Mesh Map Data
Mesh Map Attributes

Map attributes may be supplied as part of the map header. This depends on the type (format) of
map.
NROW - Number of mesh rows

NCOL - Number of mesh columns
XMIN - Minimum X value
YMIN - Minimum Y value
XMAX - Maximum X value
YMAX - Maximum Y value
NULL - Null value used for data in the file
ANGLE - Angle of rotation of mesh (decimal degrees, anticlockwise,
positive from the X-axis)
ORIGIN - Position of mesh origin (at row=1, column=1)
AXIS TEMPLATE - Orientation of the axes (X, Y, Z), top, bottom, left or right
UNITS - Horizontal (X, Y) unit, and vertical (Z) or property unit.
Mesh map formats

FloGrid supports the following formats:
Generic
This is a formatted text file containing the mesh map dimensions (nx, ny) and nx*ny values,
where nx represents the number of columns and ny the number of rows (see Set Import control
panel for details). Only one structural or property map is allowed per file.
CPS1 (Save)
These are binary SAVE files. These require additional control file information such as map
dimensions and null values. Only one structural or property map is allowed per file.
CPS3 (SVS)
These are binary files in CPS-3 (SVS) format. Only one structural or property map is allowed
per file.

Mesh Map Data
IRAP
This is a binary file exported from IRAP containing multiple mesh maps. This format is referred
to as the Binary Irap Classic Multi Grid format. Normally, this file has an extension of.lay.
This is not mandatory.
Each kind of mesh map (structure, porosity, permeability, etc.) must be loaded as a separate file
and have a suitable null value.
Note It is strongly recommended that all structure maps for a model are imported in a single
file. If this is done, FloGrid can be requested to automatically define the correct
number of surfaces and assign structure mesh maps to the correct surfaces. Similarly,
all the property maps of a given type should be loaded in a single file, once structure
maps have been imported and surfaces created. If this is done, FloGrid can be
requested to automatically assign property maps to appropriate surfaces.
The following information has been supplied by Roxar to assist people wishing to export a
Binary Irap Classic Multi Grid file from IRAP. The instructions cover how to export a set of
horizons.
1 You need a set of horizons in RMS, that is you need at least one horizon in your horizon
container.
2 Export the horizons to Binary Irap Classic Multi Grid. Horizons icon menu | Export |
Binary Irap Classic multi grid...
3 Give a name and click OK.
Note that all available horizons are exported, that is all horizons in the horizons container, it is
not possible to make a selection.
4 To quality control the exported file, you can import the file back into RMS. Use the
following option: Horizons icon menu | Import | Binary Irap Classic multi grid...
ZMap
These are ASCII export files from ZMAP.

Mesh Map Data
Scatter sets data
This supports column formatted text files in which each column represents a property and each
line defines one element of the scatter. Typically, column 1, 2 and 3 represent the x, y and z
location of the scatter point and columns 4 and above represent a property measured at that
location. For example:
X Y Z Property1 Property2 Property3 Property4.....

--------------------------------------------------------------------
3040.00 3990.30 4345.50 .02 1.34 104.54 .1
3065.00 4130.30 4347.50 .07 1.23 123.45 .23
3086.00 4090.30 4349.50 .08 1.17 112.43 .17
3094.00 4080.30 4335.50 .01 1.09 118.23 .21
You need to specify:

• the number of header lines (that is, lines with information complementary to - but not part
of - the data set; for example, comments/description lines);
• the property defined in each column (using the pull down lists from each column field - for
example, column 1 contains the x coordinate, column 2 the y coordinate, column 3 the z
coordinate, column 4 the porosity measured at that location);
• whether there is a separator between each scatter set group, this generates multiple scatter
sets.
Note A file that contains columns of textual identifiers (that is similar to well markers) is
considered as invalid: only numerical columns (below the header) are permitted.

Scatter sets data
Faults
Generic...
This option opens a file browser from which you can select a generic fault file. This format can
be used to import fault traces exported from CPS in X, Y, ID format. However, it is
recommended that the more comprehensive CPS fault format is used.
Four types of ASCII formats are supported:
Faults defined by ID number

Each fault must have a unique integer ID number. FloGrid recognizes a new fault by the change
in ID number.
X-location Y-location Fault-ID

253900.21800 335572.68700 1
265840.65600 323167.68700 1
278604.34300 309494.71800 1
636141.68700 227020.06200 2
617731.75000 229109.53100 2
595155.50000 232837.46800 2
Fault defined by marker

Two REAL numbers are expected on each record, and a marker card is used to separate different
fault trace. The marker must be 1.00E+20.
X-location Y-location
1.00000002E+20 1.00000002E+20
253900.21800 335572.68700
265840.65600 323167.68700
278604.34300 309494.71800
1.00000002E+20 1.00000002E+20
636141.68700 227020.06200
617731.75000 229109.53100
595155.50000 232837.46800
Fault defined by a name

The fault name can be enclosed in single quotes.
X-location Y-location Fault-name

253900.21800 335572.68700 ‘Fault-A’
265840.65600 323167.68700 ‘Fault-A’
278604.34300 309494.71800 ‘Fault-A’
636141.68700 227020.06200 ‘Fault-B’
617731.75000 229109.53100 ‘Fault-B’
595155.50000 232837.46800 ‘Fault-B’

Faults
Fault defined by XY pairs
A new fault trace is started whenever the X2,Y2 coordinate of one record differs from the X1,Y1
coordinate of the next record.
X1-location Y1-location X2-location Y2-location

218649.03100 387929.34300 230555.53100 366823.09300
230555.53100 366823.09300 240717.20300 350704.71800
240717.20300 350704.71800 253900.21800 335572.68700
253900.21800 335572.68700 265840.65600 323167.68700
265840.65600 323167.68700 278604.34300 309494.71800
FloGrid automatically determines which of the above formats to use from the file contents.
CPS...
This option opens a file browser to select an ASCII file in CPS format. This format allows
multiple fault traces in one file. Each fault trace section is started with “->”, followed by the
fault name.
Even when there are two sections with the same name, no decision is made on which one is the
upthrown and which is the downthrown: this is because in the CPS format it is not possible to
distinguish between upthrown and downthrown traces. However, the upthrown, downthrown
sections can be set (and swapped once set) using the appropriate options in the 3D Viewer.
The points on both sections must be ordered starting from the same end and going in the same
direction of the fault. If there are more than two sections only the last section is considered.
Note Each record can be X, Y or X, Y, Z determining whether the fault trace is 2D or 3D.

Faults
Any value greater than 1.00E+11 or smaller than -1.00E+11 is assumed to be absent or null.
->Top1Fault 1
555319.2500 6809983.500
555170.5625 6809576.000
555021.8750 6809169.000
554873.1875 6808761.500
554724.5000 6808354.500
->Top1Fault 1
556311.8125 6809965.500
556418.5000 6809594.000
556525.2500 6809222.500
556715.3125 6808666.500
556844.8125 6808287.500
->Top1Fault 2
556311.8125 6809965.500
556418.5000 6809594.000
556525.2500 6809222.500
556715.3125 6808666.500
556844.8125 6808287.500
->Top1Fault 2
558169.3125 6803937.500
558200.5000 6804113.500
558221.3125 6804582.000
558200.5000 6804868.000
558179.7500 6805153.500
In the example above, there are four fault trace sections defining two fault traces Top1Fault
1 and Top1Fault 2. Note that spaces can be included in the names.
IRAP...
This option opens a file browser from which you can select an ASCII file in IRAP format. This
allows multiple fault traces in one file.

Faults
The fault traces are named based on the file name, starting from 1. Three REAL numbers are
expected on each record, and a marker card is used to separate different fault traces. The marker
must be 999.
441054.600098 6797760.000000 3021.385185

441141.800049 6797795.000000 3013.727966
441203.000000 6797818.000000 3008.413956
441264.699951 6797838.000000 3003.124883
441345.199951 6797859.000000 2994.857433
999.000000 999.000000 999.000000
441052.399902 6797763.000000 3021.564619
441149.000000 6797807.000000 3012.774086
441206.399902 6797826.000000 3007.741681
441302.199951 6797856.000000 2999.124284
441400.899902 6797877.000000 2987.976742
999.000000 999.000000 999.000000
Fault Trace Formats

FloGrid supports the following fault trace formats:
Generic (ASCII)
Four types of ASCII formats are supported:
X, Y
Multiple fault traces are supported in one file. The marker 1E+20 must be used to separate the
different traces within a single file.
X-location Y-location
1.00000002E+20 1.00000002E+20
253900.21800 335572.68700
265840.65600 323167.68700
278604.34300 309494.71800
290488.53100 296790.87500
298255.37500 285674.28100
306982.78100 272687.03100
1.00000002E+20 1.00000002E+20
636141.68700 227020.06200
617731.75000 229109.53100
595155.50000 232837.46800
573246.87500 237401.62500
553058.50000 240528.90600
533424.25000 243844.68700

Faults
X, Y, ID
Multiple fault traces are supported in one file. Different traces are differentiated by ID. Note this
format can be used to import CPS faults exported in X, Y, ID format. However, it is
recommended that the CPS format is used.
X-location Y-location Fault-ID

253900.21800 335572.68700 1
265840.65600 323167.68700 1
278604.34300 309494.71800 1
290488.53100 296790.87500 1
298255.37500 285674.28100 1
306982.78100 272687.03100 1
636141.68700 227020.06200 2
617731.75000 229109.53100 2
595155.50000 232837.46800 2
573246.87500 237401.62500 2
553058.50000 240528.90600 2
X, Y, Name
Multiple fault traces in one file. Different traces are differentiated by Name.
X-location Y-location Fault-name

253900.21800 335572.68700 ‘Fault-A’
265840.65600 323167.68700 ‘Fault-A’
278604.34300 309494.71800 ‘Fault-A’
290488.53100 296790.87500 ‘Fault-A’
298255.37500 285674.28100 ‘Fault-A’
306982.78100 272687.03100 ‘Fault-A’
636141.68700 227020.06200 ‘Fault-B’
617731.75000 229109.53100 ‘Fault-B’
595155.50000 232837.46800 ‘Fault-B’
573246.87500 237401.62500 ‘Fault-B’
553058.50000 240528.90600 ‘Fault-B’
X1, Y1, X2, Y2

Multiple fault traces are supported in one file. A new trace is started whenever the X2, Y2 of
one record differs from the X1, Y1 of the next record.
X1-location Y1-location X2-location Y2-location

218649.03100 387929.34300 230555.53100 366823.09300
230555.53100 366823.09300 240717.20300 350704.71800
240717.20300 350704.71800 253900.21800 335572.68700
253900.21800 335572.68700 265840.65600 323167.68700
265840.65600 323167.68700 278604.34300 309494.71800
278604.34300 309494.71800 290488.53100 296790.87500
290488.53100 296790.87500 298255.37500 285674.28100
298255.37500 285674.28100 306982.78100 272687.03100
FloGrid automatically determines the correct ASCII file format from file contents.

Faults
CPS
This option allows importing an ASCII file in CPS format. This format allows multiple fault
traces in one file. Each fault trace section is started with “->”, followed by the fault name.
Even when there are two sections with the same name, no decision is made on which one is the
upthrown and which is the downthrown: this is because in the CPS format it is not possible to
distinguish between upthrown and downthrown traces. However, the upthrown, downthrown,
sections can be set (and swapped once set) using the appropriate options in the Main Viewer.
The points on both sections of the fault must be ordered starting from the same end and going
in the same direction. If there are more than two sections only the last section is considered.
Note Each record can be X, Y or X, Y, Z determining whether the fault trace is 2D or 3D.
Any value greater than 1.00E+11 or smaller than -1.00E+11 is assumed to be absent or null.
->Top1Fault 1
555319.2500 6809983.500
555170.5625 6809576.000
555021.8750 6809169.000
554873.1875 6808761.500
554724.5000 6808354.500
->Top1Fault 1
556311.8125 6809965.500
556418.5000 6809594.000
556525.2500 6809222.500
556715.3125 6808666.500
556844.8125 6808287.500
->Top1Fault 2
556311.8125 6809965.500
556418.5000 6809594.000
556525.2500 6809222.500
556715.3125 6808666.500
556844.8125 6808287.500
->Top1Fault 2
558169.3125 6803937.500
558200.5000 6804113.500
558221.3125 6804582.000
558200.5000 6804868.000
558179.7500 6805153.500
In the example above, there are four fault trace sections defining two fault traces Top1Fault
1 and Top1Fault 2. Note that spaces can be included in the names.

Faults
IRAP
These are ASCII files in IRAP format. Multiple fault traces are supported in one file. The fault
traces are named based on the file name, starting from 1. Three REAL numbers are expected on
each record, and a marker card is used to separate different fault traces. The marker must be 999.
441054.600098 6797760.000000 3021.385185

441141.800049 6797795.000000 3013.727966
441203.000000 6797818.000000 3008.413956
441264.699951 6797838.000000 3003.124883
441345.199951 6797859.000000 2994.857433
999.000000 999.000000 999.000000
441052.399902 6797763.000000 3021.564619
441149.000000 6797807.000000 3012.774086
441206.399902 6797826.000000 3007.741681
441302.199951 6797856.000000 2999.124284
441400.899902 6797877.000000 2987.976742
999.000000 999.000000 999.000000

Faults
Wells
Well Deviation Surveys

Well deviation surveys can be imported into FloGrid in Generic or GRID format.
Generic (ASCII)
Three types of formatted text files:
• X, Y, Z
• X, Y, MD, TVD
• MD, TVD, X, Y.
The marker 1E+20 must be used to separate different deviation surveys within a single file.
GRID
The GRID format consists of a file that contains text information describing the parameters in
an ASCII well deviation survey file. This control file can be exported from the GRID program
or created in any text editor.
Note To use the GRID format, an input description file must already be defined. Choose the
input description file when prompted for the input file. The actual well deviation
survey data file is specified in the input description.
Below is an example of a GRID data file with the corresponding input description.
Data file called WELL.DAT
name
WELL1
--
--
X loc Y loc MD TVD
592555 5950648 9400 9400
592555 5950648 9600 9600
593361 5951135 9600 9600
593361 5951135 9670 9670

Wells
Input description file:
FILETYPE SINGLEWELL
XYUNITS FEET
XYOFFSET NO
START 6
WELLNAME HEADER LINE 2 ITEM 1
FILETYPE SINGLEWELL
TOPX DEFAULT
TOPY DEFAULT
REFDEPTH DEFAULT
-- Attributes in well data file

ATTRIBUTE TVD POSITION 4 UNITS FEET
ATTRIBUTE MD POSITION 3 UNITS FEET
ATTRIBUTE XPOS POSITION 1 UNITS FEET
ATTRIBUTE YPOS POSITION 2 UNITS FEET
-- List of input files

FILE WELL.DAT
END
The parameters used in the input description file are as follows:
FILETYPE
MULTIWELL or SINGLEWELL
• Use MULTIWELL to load several wells in one file.
• Use SINGLEWELL to load one well from the file.
XYUNITS
FEET or METRES
XYOFFSET
YES or NO
• Choose YES to if X, Y positions in the deviation survey are offsets from the wellhead
position.
• Choose NO if the X, Y positions are absolute values.
START
• Position of the first line of data (number of lines from the top of file or from the start
of the current well).
ENDPOINT MARKER
• For MULTIWELL files the last data point for each well must be followed by a MARKER
value. This is an indicator that this is the end of the data for the current well and any
data that follow belongs to the next well.
• The marker may be any value.
• Do not use a value that may appear in the data record.

Wells
WELLNAME
• For MULTIWELL files, the name of the well is read from the file HEADER (the user
specifies LINE and ITEM position).
• For SINGLEWELL files, the user may choose to enter the well name or enter a default
name root.
TOPX, TOPY
HEADER LINE n ITEM m or specific numeric value
• X, Y positions of the wellhead.
• These may be read from the file HEADER, entered as actual positions (for
SINGLEWELL files), or defaulted to the first X, Y position read from the file.
REFDEPTH
REFDEPTH HEADER LINE n ITEM m or REFDEPTH specific numeric value
or REFDEPTH DEFAULT
• Reference depth for depth values. This may be read from the file HEADER or defaulted
to zero.
ATTRIBUTE
Attributes can be defined in the following manner:
ATTRIBUTE name POSITION n UNITS unit or
ATTRIBUTE name CALCULATE UNITS units
• Variables used for the calculation may include input data attributes and also the
keyword REFDEPTH. For example:
CALCULATE TVD BY DEPTH - REFDEPTH
FILE
• You must enter a list of input files to be loaded. If these are SINGLEWELL files, they
should all be in the same format.
CPS
A CPS ASCII file contains one or more well deviation surveys. The file consists of a header
(where information concerning the units of the data can be found), followed by data tables
giving X, Y, TVDSS, and MD data points for a number of wells. The data for each well are
preceded by the well name, prefixed by “->”.
Caution At present, FloGrid assumes that the depth data are in the same units as the
horizontal data. If a file in mixed units has been read, the Edit Coordinate
System dialog can be used to correct the units of the data.

Wells
Below is an example of a CPS file (data columns have wrapped):
FDASCI 0 2 "Computed" 0 1E30 0

FDATTR 8 2 1 0
FDATNM 1 "TVDSS" "real"
FDATNM 2 "m.MD" "real"
!Coordinate System:
! Secondary Horizontal: Units: m Per/Meter: 1.000000000000
! Geodetic Datum: ED50 Ellipsoid: INT24
! Projection Mode: UTM: Zone=31 Hemisphere: North
! Projection Method: UTM
! Projection Method: Gauss Krueger TM
! Central Meridian: 3.00000000000
! Base Parallel: 0.0
! Scale Factor: 0.999600000000
! False Easting: 500000.000000 m
! False Northing: 0.0 m
! User Horizontal: Units: m Per/Secondary: 1.000000000000
(4D25.16)
->7/21A-A9MD
0.4757814899999183E+06 0.7988856320999652E+07
-0.4629999923706055E+02 0.0000000000000000E+00
0.4757875680861473E+06 0.7988852811807632E+07 0.1635435485839
844E+03 0.2100000000000000E+03
0.4758309747390747E+06 0.7988827750913620E+07 0.7500567626953
125E+03 0.6000000000000000E+03
0.4758924077224731E+06 0.7988792282485962E+07 0.8414320678710
938E+03 0.9000000000000000E+03
0.4759776282806396E+06 0.7988743080268860E+07 0.1124713134765
625E+04 0.1200000000000000E+04
Well Markers Data Formats

Generic
Marker data are stored in column formatted ASCII files. An example is:
[1]Borehole Name [2]Surface Name [3] X (m) [4] Y (m)

[5]MD (m) [6]TVDSS (m
--------------------------------------------------------------------
2 AEO 373055.986 5989613.685 3133.39 3089.35
5 AEO 377253.529 5990616.994 3118.38 3082.75
6 AEO 378666.468 5987621.138 3124.26 3090.04
G1 AEO 376055.151 5990678.221 3693.31 3062.22
G2 AEO 375321.927 5987429.198 3646.71 3113.71
G3 AEO 373338.491 5988776.696 4197.19 3060.32
where the header describes the meaning of each column and the number of rows (below the
header) corresponds to the number of markers contained in the file.

Wells
Note The marker header contained in the file is not used by the Import mechanism and you
can modify the default column description offered (as described below).
You select the Import | Generic... from the Well Markers node in the data tree option to select
the file location, see "Generic Well Marker Import panel" on page 383.
Note Only one marker file can be imported in a single operation.
Well Logs Data Formats

Generic
This option supports the following formatted text files:
MD Prop1 Prop2 Prop3 Prop4 Prop5 Prop6

ft - - - - - -
7000 10.0 -999.25 55.5 100.0 -999.25 15.5
7029.52 20.0 -999.25 75.5 80.0 -999.25 25.5
7169.91 30.5 -999.25 95.5 90.0 -999.25 35.5
7211.39 40.0 80.0 44.5 60.0 -999.25 45.5
7251.28 60.5 80.0 33.5 65.0 59.25 55.5
7411.72 55.6 120.0 40.6 70.0 59.25 65.5
7427.66 50.5 140.0 55.0 75.0 59.25 95.5
7462.11 74.9 170.0 80.5 80.0 59.25 155.5
7503.26 66.1 -999.25 75.5 60.0 59.25 125.5
7611.75 66.1 -999.25 95.5 10.0 -999.25 140.5
7713.85 66.1 95.5 110.7 10.0 -999.25 110.5
7761.34 66.1 115.25 -999.25 110.0 99.25 125.5
7811.41 70.0 110.5 -999.25 120.0 99.25 105.5
LAS
The LAS format has the following sections:

Wells
Version information
~Version Information
VERS . 2.0 :CWLS Log Ascii
Standard - Version 2.0
WRAP . NO :One line per depth step
Well information block

~Well Information Block
#MNEM.UNIT Data Type Information
#--------- --------- ------------------
-------------
STRT .M 4029.91300 :START DEPTH
STOP .M 3940.30180 :STOP DEPTH
STEP .M -0.15240 :INCREMENT
NULL . -999.25 :NULL DATA VALUE
COMP . BP Exploration :COMPANY
WELL . 9/34A-G11 :WELL
FLD . YORK :FIELD
LOC . :LOCATION
PROV . :PROVINCE
STAT . :STATE
CNTY . :COUNTY
CTRY . :COUNTRY
DATE . :DATE
UWI . G11 :UNIQUE WELL UWI
LIC . :LICENSE NUMBER
API . :API NUMBER
SRVC . :SERVICE COMPANY
Parameter Information Block

~Parameter Information Block
#MNEM.UNIT Value Description
#--------- --------- -------------
LONG .DEG 1.103629 :Well Surface Location
LATI .DEG 54.031971 :Well Surface Location
XWELL .M 375790.000000 :X-coordinate of Well Head
YWELL .M 5988871.000000 :Y-coordinate of Well Head
Curve Information Block

~Curve Information Block
#MNEM.UNIT API Code Curve Description
#-------- -------------- ----- -------------------
DEPT .M :0 Index
PHIE .V/V :1 Effective Porosity
SW .V/V :2 Water Saturation
VCL1 .V/V :3 Volume of Clay 1 Relative
to Total Volume

Wells
ASCII data section
~Ascii Data Section
4029.91300 0.06557 0.18485 0.33185
4029.76060 0.07560 0.13231 0.24525
4029.60820 0.07537 0.13273 0.22677
4029.45580 0.07052 0.14211 0.24663
4029.30340 0.05890 0.17257 0.27742
4029.15100 0.04011 0.26649 0.31371

Wells
Property model input formats
Introduction
There are currently three input formats available for the property model.
Geolith
This format is a useful way of importing structurally simple, 3D models that can be defined
using a regular dx, dy grid with varying z values. Input is in ASCII format. See "Geolith /
Chears input format" on page 799
Rescue
The Rescue format is the preferred way of importing geological models from most geological
modeling applications.
FloGrid supports Rescue models exported using Versions 9 to 35 of the Rescue class library.
The Rescue participants have agreed that all commercial releases of geological modeling
applications supporting Rescue will ensure that they export models in this range.
Rescue models exported with Version 12 and above are now a set of files rather than a single
file. This is to support several new features, notably load on call, which allows applications
accessing the Rescue model to only load parts of the model as they require it. This makes
FloGrid 99B and later versions much more memory efficient.
Note To reduce storage in the Workspace file (which is still significant), FloGrid does not
duplicate the RESCUE file contents in the Workspace file if a session is saved. This
means you must retain the RESCUE file when using Save and Restore.
For a description of the publicly available Rescue exchange format, please see the POSC web
site for more information.
Stratamodel...
This format only supports unfaulted Stratamodel models built using SGM 5.0. If a faulted
Stratamodel model is to be read into FloGrid it should be exported from Stratamodel using
Rescue. Models are read using OpenSGM libraries to allow the native Stratamodel project files
to be accessed.

Property model input formats
Geolith / Chears input format
Geolith data file structure

The Geolith input format is an ASCII format containing the following information*:
• Grid and structure.
• Top depth data for layer 1.
• Gross thickness for each layer.
• Data arrays containing property data for layers 1 to n.
(that is porosity, permeability, etc.).
Grid and structure

This first section defines the model size:
* === Start of Grid and Structure Section === *

* nx = 10 ny = 10 nz = 2
MODELSIZE 10 5 2
*
The next section defines the cell DX and DY (note that DX and DY are constant for all cells):
DX
100.0
*
DY
50.0
Tops depth section

This section gives the surface data for the top surface:
* The CELLS keyword specifies mini, maxi, minj, maxj, mink, maxk
*
* === Top Depth Section === *
* Contains depth data for surface 1
*
TDEPTH
CELLS 1 10 1 5 1 1 =
100.0 100.0 100.0 200.0 100.0 100.0 100.0 100.0 100.0 100.0
100.0 100.0 100.0 100.0 100.0 100.0 100.0 100.0 100.0 100.0
100.0 100.0 100.0 100.0 100.0 100.0 100.0 100.0 100.0 100.0
100.0 100.0 100.0 100.0 100.0 100.0 100.0 100.0 100.0 100.0
100.0 100.0 100.0 100.0 100.0 100.0 100.0 100.0 100.0 100.0
*. Chears is Chevron Texaco’s inhouse simulator.

Gross thickness section
This section gives the cell depths for all layers:
*
* === Gross Thickness Section === *
*
GROSS
CELLS 1 10 1 5 1 2 =
1.763 1.721 1.689 1.658 1.627 1.594 1.558 1.531 1.471 1.441
1.787 1.752 1.700 1.673 1.648 1.621 1.590 1.553 1.499 1.472
1.768 1.729 1.700 1.672 1.647 1.628 1.605 1.581 1.553 1.526
1.798 1.743 1.735 1.697 1.661 1.633 1.608 1.578 1.547 1.516
1.821 1.774 1.751 1.712 1.669 1.634 1.607 1.623 1.591 1.553
1.843 1.794 1.794 1.758 1.721 1.682 1.651 1.678 1.645 1.600
1.927 1.880 1.858 1.824 1.794 1.768 1.738 1.725 1.696 1.659
1.936 1.896 1.842 1.807 1.779 1.759 1.742 1.725 1.712 1.674
1.922 1.882 1.829 1.794 1.779 1.762 1.740 1.732 1.711 1.678
1.903 1.866 1.812 1.782 1.770 1.754 1.734 1.726 1.697 1.662
Example property section

This section is an example property section giving the cell values for the property.
*
* === XPERM Section === *
*
XPERM
CELLS 1 10 1 5 1 2 =
11.992 23.045 29.493 1.363 18.610 14.998 44.855 184.391 57.665 0.141
0.057 1.005 0.179 9.589 1.522 7.901 11.393 15.002 30.981 0.119
0.038 0.017 0.695 0.347 1.007 1.323 0.251 0.273 0.417 0.066
0.031 0.011 0.148 0.042 0.868 0.480 0.359 1.281 0.324 0.269
0.020 0.087 0.050 0.201 0.200 0.255 0.006 1.583 0.633 5.609
0.002 0.116 0.034 0.385 0.184 0.026 0.109 0.087 0.200 0.058
0.015 0.026 0.015 0.034 0.040 0.057 0.092 0.021 0.107 0.062
0.046 0.077 0.271 0.037 0.020 0.051 0.410 0.021 1.607 0.282
0.040 0.101 0.044 0.050 0.020 0.018 0.422 0.216 0.091 0.424
0.054 0.025 0.033 0.207 0.046 0.032 0.033 0.466 0.098 0.498

Supported properties
This table shows the Geolith property keywords that are supported and their FloGrid properties
equivalents:
Table E.1 Geolith keywords supported by FloGrid
Keyword FloGrid Property Description

POROSITY Porosity Porosity
XPERM PermX X-permeability
YPERM PermY Y-permeability
ZPERM PermZ Z-permeability
SWIR SWL
NETGROSS NTG NetToGross
KRREGION SATNum SatNum
ACTIVE ExtActive External active flag

Importing Data From GeoFrame
Appendix F
Introduction
This section outlines the options for importing data from GeoFrame The recommended method
is the first method for each data type.
Table F.1 Data types and methods of I/O
Data Type GeoFrame Export FloGrid Import

CPS: File | Export | Binary | Grid. Identify Surfaces Node | Import Mesh
Mesh Maps proper surface. Maps | CPS3
CPS: File | Export | Binary | Grid. Identify Faults Node | Import Fault
Fault Surfaces proper surface. Surfaces | CPS3
CPS: File | Export | Ascii | Fault. Identify Faults Node | Import Fault Traces
Fault Traces proper trace, set type as CPS-3 (trace is | CPS3
best for sloping faults).
CPS: File | Export | Ascii | Data. Identify File | Import | Contour Maps |
Contours Contour data set, set type as CPS3. Generic
CPS: File | Export | Ascii | Data. Identify File | Import | Scatter Sets |
Scatter Scatter data set, set type as XYZ-Only. Generic
CPS: File | Export | Ascii | Data. Identify Wells Node | Import Well
Well Deviations Borehole data set, set type as CPS3. Deviation Surveys | CPS.
Individual well export from GeoFrame Wells Node | Import Well
data exporter. Deviation Surveys | Generic
Data Management | Data Store | ASCII | Well Markers| Import Well
Well Markers Markers. Use standard control file. Markers| Generic
FloGrid User Guide Importing Data From GeoFrame 803

Introduction
Table F.1 Data types and methods of I/O (Continued)
Data Type GeoFrame Export FloGrid Import

Data Management | Data Store | ASCII | Well Logs Node | Import Well
Well Logs LAS. Use standard LAS format. Logs | LAS
Structural Fault block split structural models FloGrid Models Node | Import
Frameworks exported from P3D via RESCUE export Models | RESCUE
P3D RESCUE export FloGrid Models Node | Import
FloGrid Models Models | RESCUE
804 Importing Data From GeoFrame FloGrid User Guide

Introduction
Unstructured Gridder files
Appendix G
Import files
Boundary file formats

Polygon file format:
BOUNDARY ‘Polygon 1’ 2D_Polygon
UNITS ft ft ft
ORIGIN 0 0 0
AXIS PX_PY_PZ
POINTS XY
x1 y1 *
x2 y2
x3 y3
x4 y4 *
x5 y5
x6 y6 *
x7 y7
x8 y8 *
If this file is imported, it would appear in the list of available boundaries as Polygon 1. The
word 2D_Polygon in the file indicates that the boundary is a polygon. The asterisk after points
1, 4, 6 and 8 indicate that these are major points. See "Boundaries..." on page 113 for more
information on major and minor points.
FloGrid User Guide Unstructured Gridder files 805

Import files
Rectangle file format:
BOUNDARY ‘Rectangle 2’ 2D_Rectangle
UNITS ft ft ft
ORIGIN 0 0 0
AXIS PX_PY_PZ
POINTS XY
x1 y1
x2 y2
x3 y3
x4 y4
This boundary would appear in the list of boundaries as Rectangle 2. Asterisks are not
necessary to mark major points, because there are only four points needed to define the
rectangle and they are all major points by definition.
Grid geometry import files

You can import grid geometry files into the Unstructured Gridder using File | Import grid
geometry.... The following options are available:
Unstructured/structured
Imports an unstructured grid in EGRID or PGRID format, or a structured grid in EGRID or
GRID format. This is the most frequently used option.
Dual Porosity Structured

Imports and splits a dual porosity structured grid. It is only necessary to use this option for GRID
format files; the previous option can be used for dual porosity EGRID files because the split
information is stored in the file.
Convert Structured
Imports a structured grid in EGRID or GRID format, which is then converted internally into the
unstructured grid file format. Use this option if you want to generate multi-point transmissibility
using the Multi-point Flux option.
Convert Dual Porosity Structured

Imports, converts and splits a dual porosity structured grid in GRID format.
Results/props import files

You can imports simulation results for the current model’s grid into the unstructured gridder
using File | Import Results/props.... There are two property input file options available:
806 Unstructured Gridder files FloGrid User Guide

Import files
Eclipse...
Opens a file browser, Select GRT Property File and imports files in the ECLIPSE format.
Generic (AVS)...
Opens a file browser, Select AVS File, and imports files in the Generic format.
The grid corresponding to the simulation results must be generated or imported before executing
this option.
Summary file
You can imports simulation results for the current model’s grid into the unstructured gridder
using File | Import summary file....
Imports simulation results from an ECLIPSE SUMMARY file. These results are used for well
connection upscaling, in which well connection transmissibility factors are made more accurate
by incorporating results from a fine grid. The coarse grid should be selected as the current
gridding model. Both coarse and fine grid summary files must be imported before upscaling can
be performed.
The standard extensions for unified SUMMARY files are.FUNSMR (formatted) and.UNSMRY
(unformatted). Report steps must be set at the same times in both simulations. Mini steps are
ignored since it is unlikely that time values from the coarse and fine grid simulations would
coincide. If there is a mismatch between the well names in the SUMMARY file and the well names
in the gridding model, a mapping is set automatically and this is reported to the Log window.
The imported data persists as long as the gridding model, unless it is overwritten by importing
another file.
Coarse grid...
Opens a file browser Open Coarse Grid Summary File, and imports a SUMMARY file for the
current (coarse) grid. Results for well bottom hole pressure (WBHP), well connection flow rate
(COFR) and cell oil viscosity (BOVIS) are required. Cell specific data is not checked until
upscaling is performed, since the well connections may not exist at the time the file is read.
Fine grid...
Opens a file browser, Open Fine Grid Summary File, and imports a SUMMARY file for the
fine grid. Results for well bottom hole pressure (WBHP) are required.

Import files
Export files
Grid geometry files

File | Export grid geometry... opens a file browser, Grid Geometry File. If the grid contains
local grid refinements (LGRs) you can select whether to output the grid with LGRs or to just
output the global cells.
Unstructured grids are stored in a different format from the standard ECLIPSE Grid Geometry
file. The extensible grid file format (EGRID) can be used for both structured and unstructured
grids, both with and without LGRs. These files can be imported into FloViz and Schedule
for visualization purposes. For backwards compatibility, the old PGRID format files can also be
written but these can only be used for purely unstructured grids.
Both formatted (ASCII text) and unformatted (binary) files are supported. The default file
extensions are.fegrid and.egrid, respectively for EGRID format files and .fpgrid and
.pgrid for PGRID format files.
Note ECLIPSE cannot create an EGRID file from the input data for an unstructured grid.
You MUST write out an EGRID file from your FloGrid session and keep it for future
uses, (for example visualization).
Grid keywords
File | Export grid keywords... opens the Export Grid Keywords panel, and exports ECLIPSE
keywords to an ASCII file. Properties should have been previously generated.
The panel has a table listing all the previously generated properties. The initial selection is based
on the keywords required in the GRID and EDIT sections for ECLIPSE. You may deselect or
select other properties as required.
Select OK and a file browser, Keyword File (.grdecl), opens to allow you to enter an
appropriate file name for the exported file. The convention in ECLIPSE is to give this file an
extension .grdecl, .regecl or .solecl, depending on the section, but any name and
extension may be used.
For GRID/EDIT section files, the NX, NY and NZ values of the ECLIPSE grid into which the
unstructured grid has been mapped are given under the SPECGRID keyword. These NX, NY and
NZ values must be entered manually by you into the RUNSPEC section of the.DATA file.
The selected cell properties are written to the file one subset of cells at a time using the BOX
keyword.
Note Note that the VE option and fine grid equilibration cannot be run in ECLIPSE when
using an unstructured grid.
GRID/EDIT sections
Writes keywords for the GRID and EDIT sections. A warning is issued if the minimum set of
properties required to successfully run ECLIPSE has not been generated.

Export files
REGIONS section
Writes keywords for the REGIONS section. You must select only the properties that are
appropriate for this section.
SOLUTION section
Writes keywords for the SOLUTION section. You must select only the properties that are
appropriate for this section.
Write global grid

This option is available if an LGR model has been created. Check this box to output global cell
data.
Write LGRs
This option is available if an LGR model has been created. Check this box to output LGR cell
data.
Write GRID section keyword

Check this box to export the GRID section header keyword.
Write EDIT section keyword

Check this box to export the EDIT section header keyword.
Write REGIONS section keyword

Check this box to export the REGIONS section header keyword.
Write SOLUTION section keyword

Check this box to export the SOLUTION section header keyword.
Sometimes you may not want to write these keywords if the exported file is to be an INCLUDE
file because in this case the keywords may already be in the main data file.
Write NNCs
Check this box to export non-neighbor connection information when exporting to the
GRID/EDIT sections.
Write MPF NNCs

Check this box to export non-neighbor connections for multi-point fluxes when exporting to the
GRID/EDIT sections.

Export files
Write MULTREGT
This option is available if the MULTNUM property has been generated. Check this box to export
pairs of region numbers lying on faults. The transmissibility multiplier values can then be edited
as required.
Well trajectory
File | Export well trajectory opens a file browser, Trajectory File (.trj), which allows you to
export grid dependent data for the Schedule program. Schedule expects the file extension .trj,
but any file name and extension may be entered. The exported file contains time independent
well connection data to enable Schedule to generate ECLIPSE keywords incorporating time
dependent quantities. The option Wells | Auto Connect or Wells | Manual Connect must be
executed prior to exporting trajectory data.
Well keywords
File | Export well keywords opens a file browser, SCHEDULE Keyword File (.schecl),
which allows you to export the grid dependent data for ECLIPSE COMPDAT and WELSPECS
keywords. The convention for the file extension is by default.schecl. The file contains the
following for each connection:
Well_Name I J K1 K2 OPEN 1* Well_Connection_Factor
Diameter Kh Skin_Factor 2* Equil_Rad /
Data following item 8 are output for information only; they are ignored by ECLIPSE since the
well connection factor is given explicitly.
The option Wells | Auto Connect or Wells | Manual Connect must be executed prior to
exporting the COMPDAT and WELSPECS keywords.

Export files
Converting old dual porosity files command files
Note Any pre-99B command files for dual porosity/permeability models need to be
converted by making the following changes. Also note that dual porosity/permeability
LGR is not supported with pre-2000A ECLIPSE.
Commands and property names

Remove CreatePropType commands where the PropType argument is an old style
fracture property name.
Substitute new-style property names for old-style names in the following commands:
• ImportMap - argument PropType
• SelectProp - argument PropName
• SimEditPropertyByExpr - argument PropName
• GetThreshSC - argument PropName
• GenerateProperties - argument Properties
• ExportGridKeywords - argument Properties.
Old and new property names
Table G.1 Property names
Old property name New property name

FracPorosity Fracture Porosity
FracPerm Fracture Perm
FracPermX Fracture PermX
FracPermY Fracture PermY
FracPermZ Fracture PermZ
FracPermXYZ Fracture PermXYZ
FracPorVol Fracture PoreVolume
FracTransX Fracture TransX
FracTransY Fracture TransY
FracTransZ Fracture TransZ
FracTransXYZ Fracture TransXYZ

Property Population Glossary
Appendix H
Introduction
This appendix contains a glossary of terms used in Property Population.
Glossary
Bivariate statistics
Statistical measures calculated from a pair of variables or attributes of a population of sample
data points. These various bivariate statistical measures describe the relationship between the
two variables of the population.
Coefficient of skewness
⎛ n ⎞
⎜ ( x – m )3⎟ ⁄ n
⎜ ∑ i ⎟
⎝ i ⎠
= ---------------------------------------- [EQ H.1]
3
σ
The coefficient of skewness is used to capture the symmetry of a distribution. Since this
calculation also suffers from erratic high values, it is sometimes only used to describe the sign
of the symmetry and not the magnitude. A positively skewed histogram has a long tail of high
values to the right, making the median less than the mean. If there is a long tail of small values
to the left and the median is greater than the mean, the histogram is negatively skewed, [Ref.
22].
FloGrid User Guide Property Population Glossary 813

Introduction
Coefficient of variation
σ-
CV = --- [EQ H.2]
m
If this ratio is > 1, the coefficient indicates that the distribution contains some erratic high
sample values that could have a significant impact on other estimates [Ref. 22].
Collocated Cokriging
n1
ẐCOK ( u ) = ∑ λα1 ( u )Z ( u α1 ) + λ'Y ( u ) [EQ H.3]

α1 = 1
Collocated cokriging requires that the secondary variable be defined at every estimation
location (practically speaking, that it be a grid). This technique requires the primary covariance
just as in cokriging. However, since the secondary variable is defined at every estimation
location, the secondary covariance is not needed. The cross covariance is still required,
however, GSLIB approximates this behind the scenes using a Markov-type hypothesis. Thus,
the real advantage of collocated cokriging is that it requires a variogram of only the primary
variable. The matrix is also simpler and runs faster. It does not, however, provide as much
variability in the final estimate as a pure cokriging technique. This is basically due to the fact
that λ'Y ( u ) is a weighted residual of the secondary attribute that is added to the primary, [Ref.
8].
Correlation coefficient
⎛ n ⎞
⎜ ( x – m ) ( y – m )⎟ ⁄ n
⎜ ∑ i x i y ⎟
⎝ i ⎠
ρ = ------------------------------------------------------------- [EQ H.4]
σx σy
The Pearson correlation coefficient is the statistic most commonly used to summarize the linear
relationship between two variables. It ranges between -1 and 1 where -1 represents a very strong
inverse relationship and +1 represents a very strong positive relationship. If 0, no linear
relationship exists, [Ref. 4].
Correlogram
C ( h )-
ρ ( h ) = -------------- [EQ H.5]
σ–h σh
C(h) = covariance of the data (see [EQ H.5])

σ–h σ h = the standard deviation of the tail and head values respectively.
When x and y refer to different attributes, the expression identifies the sample cross correlogram
[[Ref. 8]].
814 Property Population Glossary FloGrid User Guide

Introduction
Covariance
N( h)
1
C ( h ) = ----------- •
N(h) ∑ xi yi – m–h mh [EQ H.6]
i=1
m-h = the mean of the tail values

mh = the mean of the head values
This measure, also called the non-ergodic covariance, is the traditional covariance commonly
used in statistics. If x and y refer to two different attributes, the sample cross covariance is
identified [Ref. 22], [Ref. 8].
Cumulative frequency
Cumulative frequency plots should provide the same level of interactivity as the histograms.
This plot is also known as the cumulative distribution function or cdf.
Exponential model
ϒ ( h ) = c • 1.0 – exp ⎛⎝ – h
---⎞⎠ [EQ H.7]
a
where:
a = effective range 3a [Ref. 8]
Theoretical semi variogram model used for representing the structural behavior of the spatial
variances in a data set. Used in kriging methods.
Gaussian model
⎛ 2⎞
ϒ ( h ) = c • 1.0 – exp ⎜ – h-----⎟ [EQ H.8]
⎝ a 2⎠
where:
a = effective range a 3 [Ref. 8]

Gaussian simulations
A stochastic imaging technique designed for generating equally probable, alternative
realizations of data that exhibit a normal distribution.
General relative semi variogram

ϒ(h) -
ϒGR ( h ) = ----------------------------- [EQ H.9]
m 2
– h + m h⎞
⎛ ----------------------
⎝ 2 ⎠

Introduction
The semi variogram as calculated above is used as the numerator in this equation. The
expression in the denominator is used to standardize the squared mean of the data used for each
lag, [Ref. 8].
Head / Tail
The head and tail are terms used to describe the pairs used in an experimental variogram
calculation.
Figure H.1 Pairs used in an experimental variogram calculation.
data pt. A data pt. B
Tail Head
Histograms
Histogram plotting can be fairly basic. You should be able to determine the number of classes
but also be able to rely on a default calculation of classes if he/she so chooses.
Interquartile range
IQR = Q3 – Q1 [EQ H.10]
The IQR is the difference between the upper and lower quartiles of the data, or the value below
which 75% of the data lie, minus the value below which 25% of the data lie. It does not use the
mean as the center of the distribution. Thus, it is often used if a few erratically high values exist
which strongly influence the mean, [Ref. 22].
Kurtosis
(Coefficient of Excess)
⎛ n ⎞
⎜ ( x – m )4⎟ ⁄ n
⎜ ∑ i ⎟
⎝ i ⎠
= ---------------------------------------- – 3 [EQ H.11]
4
σ
This coefficient measures the sharpness of the peak on the curve of a probability density
function. A distribution with an excess coefficient > 0 is said to be leptokurtic, zero is
mesokurtic and < 0 is platykurtic [Ref. 8].
Location
Statistical measures which describe the variable values such as Minimum and Maximum,
Range, Mean, Median, and Mode.
Moving window statistics

The calculation of a statistical property within multiple windows or subregions throughout an
area of interest.

Introduction
Nested structures
The mathematical combination of multiple variogram models to summarize a variogram cross
plot.
Nugget effect
A discontinuity at the origin of the variogram. The vertical separation from the value of 0 at the
origin to the value of the variogram at extremely small separation distances is called the nugget
effect.
Octant Search
A relatively common data search method employed by a variety of grid-based algorithms. For
most gridding algorithms, only a limited number of data points are considered in the estimation
of any given grid node value. In an octant search, the neighboring region (a search ellipse
centered on the grid node and up to the search radius in diameter) surrounding a grid node is
divided into eight sectors (octants). This partitioning is illustrated below. Controls are often
provided which limit the total maximum number of data points that are considered within the
defined search neighborhood, the minimum number of points which are required in order to
proceed with the computation, and the maximum number of data points which will be allowed
for any single octant. Occasionally, a parameter that defines the maximum number of empty
octant that will be tolerated is also provided. Collectively, these controls attempt to insure that
data are considered from “all sides” of the point being estimated. If too few data or consecutive
octants, etc. are available, the node is not estimated and instead, left “uninformed” (that is,
assigned a NULL, missing, or indeterminate value):
Figure H.2 Octant search
Ordinary Kriging
n n
ẐOK ( u ) = ∑ λα( u )Z ( uα ) + 1– ∑ λα ( u ) m̂ ( u ) [EQ H.12]

α=1 α=1
where:
m̂ ( u ) = the location-dependent estimate of the mean.

Introduction
Ordinary kriging (OK) filters the mean from the SK estimator by requiring that the kriging
weights sum to one. OK amounts to re-estimating, at each new location u, the mean m as used
in the SK expression, [Ref. 8].
Pairwise relative semi variogram

N(h) 2
1 ( xi – yi )
ϒPR ( h ) = --------------- •
2N ( h ) ∑ ---------------------
⎛ x i + y i⎞ 2
- [EQ H.13]
i = 1 --------------
⎝ 2 ⎠
Both the pairwise relative and general relative sample variograms are resistant to data sparsity
and outliers when applied to positively skewed sample distributions. They sometimes reveal
spatial structure and anisotropy that could not be detected otherwise.
Caution However, because of the divisors in both expressions, the general relative pairwise
variograms should only be used for strictly positive variables [Ref. 8].
Proportional effects
A measure of the local average versus the local variability. This measure helps to determine
those areas of the map where local variability could have an impact on the accuracy of estimates.
In areas with very uniform values, the prospects for accurate estimates are quite good. On the
other hand, if the data values fluctuate wildly our chances of accurate local estimates are poor.
Quantiles
The general name for the values of a variable which divide its distribution into equal groups.
Four equal parts are quartiles. Ten equal parts are deciles, etc.
Rank correlation coefficient

⎛ n ⎞
⎜ ( R – m ) ( R – m )⎟ ⁄ n
⎜ ∑ xi Rx yi Ry ⎟
⎝ i ⎠
ρ rank = ----------------------------------------------------------------------- [EQ H.14]
σRx σR y
where:
Rxi = Rank of xi among all x values
Ryi = Rank of yi among all y values
m Rx = mean of ranks R xi ... R xn
m Ry = mean of ranks R yi ... R yn
n = total number of values ranked

σRx σ Ry = standard deviation of x rank and y ranks

Introduction
If the relationship between two variables is not linear, the correlation coefficient may be a very
poor summary statistic. It is often useful to supplement the linear correlation coefficient with
another measure of the strength of the relationship, the rank correlation coefficient (Spearmans
in this case). The rank correlation coefficient is based on sorted values. The lowest on the sorted
list of x values would receive a rank of 1; the highest would receive a rank of n. The same for
the y variable [Ref. 22], [Ref. 7].
Semimadogram
N(h)
1
ϒM ( h ) = --------------- •
2N ( h ) ∑ xi – yi [EQ H.15]
i=1
This measure is similar to the traditional variogram; instead of squaring the difference between
xi and yi, the absolute difference is used.
Caution Madograms and rodograms are particularly useful for establishing large scale
structures (range and anisotropy). However, they should not be used for modeling
the nugget variance of semi variograms [Ref. 8].
Semirodogram
N(h)
1
ϒR ( h ) = --------------- •
2N ( h ) ∑ xi – yi [EQ H.16]
i=1
This measure is similar to the traditional variogram; instead of squaring the difference between
xi and yi, the square root of the absolute difference is used [Ref. 8].
Semi variogram
N(h)
1 2
ϒ ( h ) = --------------- •
2N ( h ) ∑ ( xi – yi ) [EQ H.17]
i=1
where:
N(h) = number of pairs
xi = value at the start or tail of the pair
yi = value at the end or head of the pair
h = the separation vector
The semi variogram is the traditional measure and defined as half the average squared difference
between two attribute values approximately separated by vector h [Ref. 8].
Semi variogram of logarithms

N (h )
1 2
ϒL ( h ) = --------------- •
2N ( h ) ∑ [ ln ( xi ) – ln ( yi ) ] [EQ H.18]
i=1

Introduction
The semi variogram is computed on the natural logarithms of the original variables (provided
that they are positive) [Ref. 8].
Shape
Statistical measures which describe the shape of a population of variable values such as
Skewness, and Kurtosis.
Simple Kriging
n n
ẐSK ( u ) = ∑ λα ( u )Z( uα ) + 1– ∑ λα ( u ) m [EQ H.19]

α=1 α=1
where:
ẐSK ( u ) = the estimated value at location u.
λ α u = the calculated weights at each location based on the solution from the simple kriging
matrix.
Z ( uα ) = the property values being collected for each of the estimation locations.
m = the mean value for the entire data set.

Simple kriging (SK) does not adapt to local trends in the data since it relies on the mean value
m, assumed known and constant throughout the area. Consequently, SK is rarely used directly
for mapping the z-values [Ref. 8].
Spherical model
h h 3
ϒ ( h ) = c • 1.5 --- – 0.5 ⎛⎝ ---⎞⎠
a a
where:
if h ≤ a
ϒ ( h ) = c , if h > a [EQ H.20]

a = range
c = sill or positive variance contribution
h = lag spacing [3]
Spread
Statistical measures that describe the variability of values such as Standard Deviation, Variance,
and Interquartile range.

Introduction
Standard deviation
2
( xi – m )
σ = ∑ ---------------------
n
[EQ H.21]
i
The standard deviation is the square root of the variance and is often used instead of the variance
since its units are the same as the units of the variable being described.
Super-block Search
An alternative data search strategy which provides an efficient mechanism in cases where many
nodes are to be estimated (that is, large 2-D and 3-D grids). Unlike a basic octant-search, a
coarse grid of blocks is superimposed over the pattern of grid node locations. Source data point
preprocessing classifies and sorts each point according to parent block. Subsequently, during
grid node estimation, the entire input pool of data values can quickly be screened or filtered by
limiting the neighborhood to the set of blocks which overlap with the search ellipse (that is, the
current super-block). As with octant-based data searches, the super-block search method allows,
only a limited number of data points are considered in the estimation of any given grid node
value. This super-block partitioning is illustrated below. Controls are then provided which limit
the total maximum number of data points that are considered within the defined search
neighborhood, the minimum number of points which are required in order to proceed with the
computation.
Figure H.3 Super block search
Trend Kriging and External Drift

n
ẐKT ( u ) = ∑ λα ( u )Z ( uα ) [EQ H.22]

α=1
The λ weights are derived from a system involving the residual covariance and a polynomial
trend model. In the case of the external drift variable, the system involves a smoothly varying
surface related to the primary variable. Optionally, the algorithm may estimate a trend from the
data and save this as a grid file.

Introduction
Univariate statistics
Statistical measures calculated from a single variable or attribute of a population of sample data
points. These various univariate statistical measures describe location, spread, and shape of the
population with respect to the test variable.
Variogram cloud
The cloud is made by plotting each squared difference ( vi – vj )2 versus the separation distance
hij . The cloud formed by these points may reveal extreme outlying points that dominate the
estimation of the sample variogram. It may also reveal that the distribution of the ( vi – v j )2 for
any one lag is severely skewed, in which case the arithmetic average of ( vi – v j )2 may provide a
poor estimate of the sample variogram for that lag.
Variance
2
=σ [EQ H.23]
The variance offers a measure of the data spread. It is sensitive, however, to erratic high values
since it involves squared differences from the mean.
Variogram model
nst
ϒ ( h ) = c0 + ∑ ci • f (h,ai) [EQ H.24]

i
nst = number of non-nugget structures

c0 = nugget value
ci = sill contribution for structure i
ai = range associated with structure i
A set of mathematical structures that describe the spatial correlation of a given attribute as a
function of separation distance. Any given model may contain a nugget values and zero or more
structures. The structures that are supported by this application are: spherical, exponential,
gaussian, and power. In addition to a nugget value, the use of up to four structures is supported.
However, models of three or more structures are rare.

Introduction
Reference Tutorials
Appendix I
Introduction
This section provides a reference tutorial, which provides technical information on specialized
aspects of using FloGrid.
• "Fault trace handling" on page 824.
FloGrid User Guide Reference Tutorials 823

Introduction
Fault trace handling
Introduction
Geological faults are an essential part of the reservoir description and must be represented at all
stages of the modeling process. This tutorial deals with the import, creation, edit and export of
vertical and sloping faults using the Fault Tree facilities in the main window.
Stages
This tutorial contains the following sections:
• "Importing fault data" on page 824.
• "Working with the Fault Tree and table" on page 825.
• "Displaying and identifying faults in the 3D Viewer" on page 827.
• "Digitizing and editing fault traces" on page 828.
• "Creating 3D fault traces" on page 831.
• "Editing an existing fault trace" on page 832.
• "Validating an incorrect fault polygon" on page 833.
• "Creating a bounding polygon or splitting trace for a sloping fault" on page 835.
Before you start

1 Copy all files from flogrid/tutorials/Grainne to your working directory.
2 Select File | Play Commands... _load_data.cmd.
This loads structure and property maps and well deviation surveys for the Grainne field.
Importing fault data

Faults are defined by their traces on structure contour maps. The trace points are either
projections on a datum plane (2D lines in X, Y coordinates) or full 3D drapes (X, Y and Z
coordinates). The ASCII file formats that FloGrid recognizes are classified into three types:
Generic, CPS and IRAP. Details of these formats are provided in "Input file formats" on
page 773.
The Generic format is a collection of four different formats. The CPS and IRAP formats allow
for 3D trace information. The CPS format has the additional advantage of being able to
distinguish between upthrown and downthrown traces. The name of the fault trace can be
provided when using one of the generic formats and the CPS format. In all other cases the trace
name defaults to the file name prefix. For files with multiple traces a sequence number starting
with 1 is added to the filename to create a unique trace name.
FloGrid assigns a fault with the same name as the fault trace name by default. The fault name
or assignment can be changed on import or later.
824 Reference Tutorials FloGrid User Guide

During import the data are interpreted as being in the Preferred Units system.
1 Open the files ID.FLT, MARKER.FLT and NAME.FLT in a text editor and examine the
generic formats used.
All generic formats only allow 2D traces in X, Y coordinates. The file ID.FLT contains
trace IDs that are appended to the filename to create trace names. The MARKER.FLT uses
the number 1.00E+20 as a marker to separate traces. The NAME.FLT uses trace names.
2 Open and examine the files IRAP.FLT (IRAP format) and POLYGON.CPS (CPS format).
Note the use of Z values and the 999 delimiter for the IRAP format. Traces are named using
the filename as a prefix. Observe how the CPS format allows names and separate entries
for upthrown (Line 1) and downthrown (Line 2) traces.
3 Confirm that the preferred units system is METRIC. Select FloGrid: Preferences | Set
External Units | ECLIPSE METRIC.
4 Select File | Import | Fault Traces | Generic...
5 Select the file ID.FLT. This opens the Fault Trace Import panel.
6 Review the information provided and the drop-down options that can be selected on the
table.
Note the default fault names that FloGrid has provided for each trace.
Note Ensure that the fault trace information is in the same coordinate system and units as the
maps. It is recommended not to use mixed units for importing fault traces, for example
the X, Y coordinates in meters and the Z coordinate in feet. If the data are indeed in
one system for the areal coordinates and another for the vertical, then resample the Z
values on structure maps as described later in this tutorial.
If the areal units are relative to a different origin from the maps then the coordinate
frame of reference can be moved by editing the coordinate system.
7 Select OK to load the fault traces update the Fault Tree and Table.
Working with the Fault Tree and table

The Fault Tree is composed of three main branches - Faults, Unassigned Fault Traces and
Unassigned Fault Surfaces. Each Fault node can have one or more fault trace and fault
surface nodes assigned. Fault trace nodes are colored to indicate their type (vertical/polygon)
and status (throw and z-values).
1 Select the Trace node ID2 (Splitter) on the Fault Tree.
Notice that the fault button border turns red to indicate that it is active.
2 With mouse cursor over the Fault trace node, click the right mouse button to open a pop-
menu of options that apply to operations on traces.
3 Select Change Coord Sys...
This opens the Edit Coordinate System panel.
4 Review the units, coordinate system orientation and the origin information. The units for
the X, Y and Z should be the same as the preferred units system. Close the panel.

Selecting and assigning traces to faults
1 Drag Trace node ID2 and drop it on Fault node ID1.
The cursor changes to (+) when over a valid dropping point. Trace ID2 now belongs to
Fault ID1 in both the Fault Tree and the Fault Table.
Splitting the fault tree panel

1 Move the cursor over to the small horizontal line on top of the scroll bar on the right side
of the Fault Tree panel. The mouse cursor changes to a (=) sign. Click on the line and drag
it down to split the Fault Tree panel into two parts.
The two panes can be independently scrolled, and drag-and-drop operations can performed
from one pane to the other.
2 Scroll the top pane to bring the Trace Node ID2 into view. Similarly, scroll the bottom
pane to bring the Unassigned Fault Traces node into view.
• Drag the fault trace ID2 and drop it on the Unassigned Fault Trace node.
• Drag and drop trace ID2 back onto Fault ID2.
3 Drag the bottom bar of the top pane and move it to the top to restore the single pane Fault
Tree.
Reducing the tree by hiding fault trace nodes

1 Double-click on fault node ID2 to collapse the branch and hide the Fault trace node.
2 Double-click on the fault node ID2 to expand the branch again.
You can also click on the + or - symbol in a small square to expand or collapse a branch.
Fast Find on Node Trees

1 Press Ctrl and right-click within the Fault Tree panel to bring up the RDS Node Search
panel.
2 Enter *3 in the Type Search Pattern field and click on Search.
The list table below is updated with the "hit" ID3.
3 Click on (highlight) the ID3 on the list produced by the RDS Node Search panel. The
Fault Tree scrolls automatically to the fault ID3 and highlights the fault node.
4 Close the RDS Node Search panel.
Note In the Structural Framework panel, when selecting the Faults folder, two instances
of the Node Finder are available: one for the Available/Unavailable Fault Trees
and one for the Volume of Interest tree.
Creating, deleting and renaming faults using the fault

table
1 In the Fault Table, click in the Select column next to fault ID2. The entire row is
highlighted in yellow.
2 Click on the Delete button.

The fault ID2 is deleted from both the table and the tree. The trace ID2 is moved to the
Unassigned Fault Trace node.
3 Click on Create on the Fault Table and select OK in the Create Fault panel.
A new fault with a default name appears in both tree and table.
4 Edit the name of the fault to ID2 in the table and press Return.
5 Drag and drop the trace ID2 from the Unassigned Fault Traces node to the fault ID2 in
the Faults branch.
Note You can also create and delete faults using pop-up menu options. The pop up menu for
creating faults is activated by a right mouse-button click with the cursor over the root
Faults Node. To delete a fault, select a Fault Node, click the right mouse button over
it, and select Delete.
Displaying and identifying faults in the 3D Viewer

1 Select the top Fault node ID1 and Shift-click the Fault node ID4 on the Faults branch.
All the fault nodes between ID1 and ID4 are selected and highlighted in red.
2 Right-click on any Fault node and select Add All Traces to View.
All traces belonging to the selected faults are displayed in the 3D Viewer.
3 Drag the Fault Trace node ID2 and drop it in the 3D Viewer to display.
Selecting fault traces in the 3D Viewer

Often you receive all the fault data in individual files, or in one large file with no distinguishing
names for the loaded fault traces. Fault traces can be selected on the 3D Viewer and various tree
operations can be done on the selected Fault Trace nodes, such as drag-and-drop for grouping
and merging traces belonging to a single fault, export to file, etc.
1 With the mouse cursor over the root node Faults right-click to open a pop-up menu.
2 Select Create Fault(s) to open the Create Faults panel.
3 Edit the fault name and call it ID5. Click on OK.
The Fault Tree is updated with a new fault node for ID5.
4 Click on any fault trace in the 3D Viewer.
The trace is highlighted, the name of the trace is displayed in the 3D Viewer status bar
(bottom left) and the trace node is highlighted in the Fault Tree.
5 Ctrl-click on another fault in the 3D Viewer and observe how the status bar and the fault
tree are updated.
6 In the Fault Tree drag and drop the selected traces on the fault node ID5. This is an
example of how you can group traces belonging to a fault.
Exporting Fault Traces

1 Right-click on any Fault Trace node.
2 Select Export Selected Traces as CPS...
3 Enter the filename to which you want to export the selected traces and click on Save.

4 Open the file in a text editor (or use Edit | Text Editor | File | Open) and analyze contents.
To restore our original fault tree do the following:
1 Right-click on the Fault node ID5 and select Delete.
The fault is deleted and all the traces are moved to the Unassigned Fault Trace node.
2 Drag each fault trace from the Unassigned Fault Trace node to its respective Fault node,
for example trace ID1 to fault ID1, and so on.
Removing faults from the 3D Viewer

3 Select a single trace or multiple traces in the 3D Viewer as shown above. Confirm that the
selected trace nodes are highlighted on the Fault Tree.
4 Click the right mouse button on any active trace node and select Remove from View on
the pop-up menu.
Digitizing and editing fault traces

A vertical fault can be defined by a single trace. A sloping fault has separate upthrown and
downthrown traces, forming a polygon, for each horizon. The collection of polygons on each
horizon defines the entire fault.
A fault trace or polygon is defined by a set of X Y or X Y Z points. In order to differentiate the
upthrown and downthrown traces, points are labeled as major or minor. Major points are used
to define the ends or corners of the upthrown and downthrown traces. All other points are
labeled as minor. The lines joining the corresponding upthrown and downthrown major points
are straight and cannot include any minor points. Major pick points are seen in the 3D Viewer
as large squares and minor pick points are seen as small squares.
A hinge fault that has some displacement at one end and no displacement at the other has three
major points or corners. A fault that is displaced at either end within the model has four major
points.
Displaying a reference map

Editing faults requires that a reference object is displayed in the 3D Viewer, add a TOPS1 to
the view from the Surfaces node.
Digitizing a vertical fault

Create a new fault as follows:
1 Right-click on the root Faults node and select Create Fault(s).
This opens the Create Fault(s) panel with a default Fault Name.
2 Edit the fault name and call it MYFAULT and press OK.
This creates a new fault called MYFAULT and updates the Fault Tree.
3 Select the fault MYFAULT and right-click on any fault node and select Create
Trace/Polygon from the pop-up menu.
This opens the Create Fault Trace panel.
4 Type in the trace name as MYTRACE and select Vertical line(s) and press OK.

Note Instead of the procedure above you can create a fault by selecting Edit | Fault Trace
| Edit traces... to define a new trace. The only difference is that FloGrid creates a new
fault with a default name for you.
5 Clicking on OK puts the 3D Viewer in Digitize Mode.

Notice that the cursor position is continually reported at the bottom right and status
messages are given at the bottom left of the 3D Viewer. Digitizing tools now occupy the
border at top left.
6 Digitize a vertical fault similar to that:
a Position the cursor at the point where you wish the trace to begin and digitize points
using the left mouse button.
Note You can delete points in reverse by using the Backspace or Delete key.
You can also delete points by selecting the Delete button and clicking the on the
points. The nearest point to the cursor is deleted.
You can then continue digitizing points after selecting Digitize .
b To cancel the edit completely click on Cancel Edit . To reset the edit click on
Reset Edit .
c When ready to accept the new trace click on the Commit Edit button or double-
click the last digitized point.
To re-enter Edit mode after committing an edit, select Edit | Fault Trace | Edit
Traces..., click on the name of the trace you wish to edit, and click on Edit. The 3D
Viewer enters Edit mode.
7 Rotate the view and increase vertical exaggeration and observe that the fault trace is
displayed at a default Z-plane above the top surface.
The fault trace is a 2D X Y polyline without any Z values; it represents the projection of
the intersection trace of the fault surface and horizon surface on a datum plane.
Note As long as the button is visible on the 3D Viewer FloGrid is in Edit mode. You
may need to click on this button to make the tools reappear.
You must either commit the current edit with or cancel it with before you
can proceed with another edit operation.

Figure I.1 3D Viewer in Digitize mode
Digitizing a sloping fault

1 Remove MYTRACE from the 3D Viewer.
2 Select Edit | Fault Trace | Edit traces...
The Edit Fault Traces panel appears.
3 Select Create.
Select Sloping polygon on the Create Fault Trace panel.
4 Enter the name MYPOLYGON for the new trace and click on OK.
This puts the 3D Viewer into Digitize mode.
5 Digitize a sloping fault similar to that Figure I.2.
a Click where you wish your trace to start. (defaults to a major point).
b Digitize as required along the first edge by clicking with the left mouse button.
c At the end of the first side set a major point at the corner using a Ctrl-click.
d Ctrl-click to set another major point at the start of the second edge.
e Digitize points along the second edge and Ctrl-click the last point to create a polygon
with four major points.
6 Edit | Close Line.
Notice now that the polygon is not only closed but its structure is now displayed by coloring
the four sides.
The lines are colored gray and yellow to represent the first and second lines respectively.
7 Select Edit | Fault Trace | Set Up/Down.
This sets the first line as the upthrown side and the second line as the downthrown side. The
upthrown side is colored magenta and the downthrown side yellow.

Figure I.2 Digitized sloping fault.
8 Click on Commit Edit .

• Rotate the view and observe that the polygon is displayed above the top surface as a
2D projection of the actual traces on a datum plane.
9 Close the Edit Fault Traces panel.
Note If during edit of a fault in the 3D Viewer with maps displayed, the fault edit symbols
and lines seem to disappear, click on the map with the right mouse button. The fault is
then brought to the 3D Viewer foreground.
Creating 3D fault traces

Fault traces in 2D do not provide a definition of the slope of the fault plane. Traces need to be
assigned to maps over which they drape in order to correctly model faults.
By default a sloping fault defined by an upthrown trace and a downthrown trace will be assumed
to intersect all the structural framework units. Therefore the upthrown trace is sampled on the
top horizon and the downthrown trace sampled on the bottom horizon for Z values.
Faults that die out can be assigned interactively to intermediate horizons.
1 Right-click on the MYPOLYGON trace and select Sample Z values from Map...
This opens the Select Surface Map panel.
2 Select the TOPS1 map and click on OK.
The Fault Tree is updated to show the Z values assigned.
3 In the 3D Viewer observe that the trace color pattern has changed and the trace now drapes
the map surface.
4 Right-click on the MYPOLYGON trace and select Associate Selected Traces to Surface....

Select Surface1 from the Select Surface list and click OK.
This opens the Select Surface panel.
The Fault Tree updates to the show the Surface assignment.
Note Traces may not exactly drape the surface when visualized. This is because the
procedure for sampling irregular points on a regular gridded surface results in a high
an low value for each point. For polygons the high values are taken for the upthrown
side, and low values are taken for the downthrown side. When a vertical trace is
assigned to a map, the trace is then displayed as a vertical polygon and may appear
confusing.
Traces can also be assigned to surfaces. In that case the sampling of Z-values is
deferred until the structural framework horizons are built.
Editing an existing fault trace

1 Select the trace node MYTRACE.
2 Right-click on any trace node and select Copy on the pop-up menu.
This opens the Copy Fault Trace panel.
3 Enter the trace name as COPYOFMYTRACE.
• Check that Vertical line(s) is selected, and click on OK.
The viewer enters Edit mode and places a copy of the trace showing the major and
minor points.
4 By default the editor is in select/move mode, which allows you to select and move a point
clicking and dragging. Experiment with moving a few points.
Hint The entire trace can be moved as a whole by shift-clicking and dragging.
5 Insert new points:
a Choose Select/Move mode on the 3D Viewer and select a line segment by

clicking on the line between two points.
One of the points and the line segment is highlighted.
b Choose Digitize mode and click within the line segment to digitize points.
6 Extend a line:
a Choose Select/Move mode.
Select the last point on the line by clicking slightly beyond the point.
b Change to Digitize mode and click to digitize new points that extend the line.
7 Delete points:
• Choose Delete mode and click on the point to be deleted.

Alternatively, you can use the Delete or Backspace key to delete a highlighted
point.

Hint The type of a trace can be changed from Vertical line(s) to Sloping polygon and vice-
versa in the Edit Fault Trace panel. This is useful for creating vertical fault polygon
information for use by the gridders.
a Choose Clear Edit . This clears the object ready to start digitizing the entire object
afresh.
Note that abandoning the edit after this still restores the original object.
b Choose Reset Edit . This restores the object to its state at the beginning of the
edit.
8 Commit or cancel your edit and remove the trace from the 3D Viewer.
Validating an incorrect fault polygon

None of the fault input formats, except for the CPS format, distinguishes between upthrown and
downthrown sides of the fault polygon. FloGrid attempts to define the two sides by labeling
major and minor points. This may not work as desired, so manual editing will be required. The
following example loads a polygon for a fault where the ends of the upthrown and downthrown
edges are incorrectly defined.
Note It is strongly recommended that fault polygons imported using either Generic or IRAP
format are checked in the viewer by analyzing the colored sections (white and yellow
or green and cyan if Z values are known) to make sure that the upthrown and
downthrown sides are correctly interpreted.
1 RM click on the Faults node and select Import | Fault Traces | IRAP...
In the file browser select BADPOLY.FLT and open it. The Fault Trace Import panel is
displayed.
2 Click on OK.
3 In the Fault Tree add the fault trace BADPOLY1 to the 3D Viewer view.
• You will notice that the FloGrid box extends downwards to incorporate the new fault
trace. This is because the z values on the fault trace are in feet and FloGrid is presently
set as ECLIPSE-METRIC. The solution to this is as follows:
4 Right click on the fault trace node BADPOLY1 and select Associate Selected Traces to
Surface...
5 Select Surface1 and click OK
6 Right click on the fault trace node BADPOLY1 again and select Sample Z values from
map...
7 Select TOPS1 and click OK
8 Toggle the fault trace node BADPOLY1 off and on in the data tree. It should now lie on
Surface1
9 Select Edit | Fault Traces | Edit Traces...
• Select BADPOLY1 from the Edit Fault Traces panel and click on Edit.

10 Select Edit Fault Trace: Sloping Polygon | OK.
This displays the major and minor points for the trace as interpreted by FloGrid. Observe
that there are only two major points, which indicates that the fault separation is zero at the
ends. The correct interpretation, however, is that there is separation at the ends.
Figure I.3 Invalid fault polygon
11 Select Edit | Set Major/Minor.

12 Click on the two corresponding corner points adjacent to the existing major points to make
the polygon valid.
Figure I.4 Valid fault polygon
13 Commit the edit .

14 Close the Edit Fault Traces panel.
15 Remove the trace from the 3D Viewer.

Creating a bounding polygon or splitting trace for
a sloping fault
Sloping faults are often defined by providing fault polygons on each horizon that the fault
intersects. These fault polygons define approximate fault surfaces and throws at the horizon
intersections.
For the purposes of structural framework construction and simulation grid generation from 2D
map data, FloGrid approximates the fault surface defined by these polygons and replaces them
by a single planar surface. This surface is defined by the upthrown trace on the topmost horizon
that the fault intersects and the downthrown trace on the bottommost intersected horizon.
Note When simulation grids are created for RESCUE-based 3D models the complete fault
surface information provided is used in simulation grid construction.
1 Create a new fault node called POLYGON using the Create Fault(s) pop up panel from
the Faults node.
2 Select File | Import | Fault Traces | CPS.
3 Select the fault trace POLYGON.CPS in the file browser window.
4 Click on OPEN (PC) or OK (UNIX).
5 On the Fault Trace Import panel go to the Fault column and select the fault POLYGON for
each Trace.
6 Select OK on the Fault Trace Import panel.
The imported fault traces should all appear under the fault POLYGON in the Fault Tree.
7 Select the fault POLYGON and add the five faults to the 3D Viewer using the option Add
All Traces to View on the right mouse button pop-up menu.
The upthrown trace of the polygon POLYGON_1 on the TOPS1 horizon and the downthrown
trace on the polygon POLYGON_5 define the bounding polygon
Automatic generation of 2D and 3D splitter traces

1 Right-click on trace node POLYGON_1 and select Associate Selected Traces to
Surface....
This opens the Select Surface menu.
2 Click on Surface1 on the list provided. Click on OK.
3 Similarly, assign the trace POLYGON_5 to the Surface5 map.
4 Highlight the fault POLYGON node and right-click to open the pop-up menu.
5 Select Auto Create 3D Splitter Trace.
The trace Splitter_trace-POLYGON is automatically generated and set to Splitter.
Note You can also create a 2D Splitter trace which will be a projection of the 3D Splitter
trace. The Z-values needed to define the 3D trace will be sampled from the structural
framework horizons later.

Manual creation by snapping to existing traces
1 Select the fault node POLYGON, RM click and select Create Trace/Polygon.
a Enter the fault name as Polygon-Slope
b Set the fault trace type as Sloping Polygon
c Ignore the Set Map button as we wish to z values of our new trace to correspond
exactly to those loaded from the file.
d Click on OK, the 3D viewer will go into Edit mode.
2 Prior to clicking in the 3D viewer, select Edit | Select Pick Items | Fault Traces.
a Select POLYGON_1+POLYGON
b Click OK
c Ensure that Edit | Pick Points is checked and notice light grey points defining
Polygon_1
3 To create the upthrown trace of the splitter, Ctrl+Click on the first point and then
Ctrl+Shift+Click on the last point of the upthrown trace to select all intermediate
points. This way the top trace is defined. If you do not receive a large white square using
Ctrl+Shift+Click, hit Delete on the keyboard and try again.
4 Select Edit | Select Pick Items | Fault Traces...
5 Select POLYGON_5+POLYGON
6 Create the downthrown trace of the splitter. Remember to start with Ctrl+Click and
finish with Ctrl+Shift+Click on the last point of the downthrown trace. You should
have a picture similar to that in Figure I.8.
7 Click on the Commit button when you have finished (green check mark).
8 Display only the trace you have just created. It should have a green upper trace and cyan
lower trace. This color combination indicates ‘Two lines of a fault polygon with z values’.
Figure I.5 Digitizing a bounding polygon

Hint In a closed loop, such as a polygon, the points that can be selected between the first
point and the last point (Shift and Click) can be ambiguous, as the selection can
be done clockwise or counter-clockwise. FloGrid internal logic, in most cases, selects
the most probable path. If this not correct then you have to guide the editor by clicking
on the first point along the required edge. In this example, if the edited line was not
correct then you would have to click on the next point along the upper edge of fault
trace POLYGON_1.
Hint If you make a mistake whilst digitizing a trace you can step back through your digitized
points to the last good point or the first point using the Delete key on your keyboard.
Note When you have selected faults as pick items, you can edit new faults using the picked
faults as templates. Toggle the selection in Edit | Pick Points as and when you wish
snap to existing points. The digitizing controls are summarized below.
Table I.1 Mouse controls for digitizing using pick points

Click with left mouse Shift - Click with Ctrl - Click with left Shift + Ctrl - Click
User action button left mouse button mouse button with left mouse button
Sets or selects the point Selects all points Sets a major point at the Selects all points
at mouse cursor between the last pick cursor location between the last pick
Set or selection
point and the current point and the current
action point major point at the cursor
location
Snaps to nearest pick Snaps to nearest pick Snaps to nearest pick Snaps to nearest pick
Snap action point if within snap point if within snap point if within snap point if within snap
range range range range
9 Set the fault trace Polygon-Slope to be the splitting trace for the fault POLYGON. Use
the right mouse button click over the Polygon-Slope trace node and select Set as
Splitting Trace from the pop-up menu.
The word Splitter (in brackets) adjacent to the splitting fault trace node appears. The
splitting trace is used during structural framework creation.
10 Exit FloGrid.

Mapping Packages
Appendix J
Introduction
FloGrid uses two different mapping packages (Conpac and CPS Convergent Gridder). Their
results are very different. For instance if the Convergent Gridder appears to be the better one in
95% of cases then Conpac could the best for the rest.
The main difference between them is that the Convergent Gridder snaps scattered data points
to nearby grid node values and iterates until it achieves a converged solution. Conpac mostly
uses the Least Squares algorithms.
Note A potential drawback to using the Convergent Gridder is that it always extrapolates
beyond data unless additional controls are specified. If extrapolation is undesirable, the
Least Squares algorithm (Conpac) may be a better choice.
This section contains technical background information on:

• "Convergent Gridder" on page 840.
• "Conpac" on page 847.
• "Contouring" on page 850.
FloGrid User Guide Mapping Packages 839

Introduction
Convergent Gridder
Overview
The Convergent Gridder uses a general-purpose gridding algorithm that can model any type
of single-valued surface. Convergent gridding does a particularly good job with line-ordered
data, such as digitized contours. It is also a very stable algorithm for modeling random or
clustered data. If you are uncertain which algorithm is appropriate, we recommend that you use
the Convergent Gridder.
The speed at which the gridding process completes has increased significantly. The results of
the extrapolation and interpolation process can differ from the previous version of convergent
gridding. You can now specify the contribution (or weight) of each data set used for generating
the Convergent grid. This provides you with greater control. In addition, you can use both dip
and azimuth data in computing the model.
Note A potential drawback to using the Convergent Gridder is that it always extrapolates
beyond data unless additional controls are specified. If extrapolation is undesirable, the
Least Squares (Conpac) algorithm may be a better choice.
The convergent gridding algorithm calculates grid node values by one or more iterations, or
passes, of snapping scattered data points to nearby nodes to produce a converged solution.
Figure J.1 illustrates the process with scatter data point A, B, C, and D, and node w. The Z values
for the scattered data points are snapped to grid node w using a distance-weighting technique so
that scattered data points closer to the node have a greater effect on the node value.
Figure J.1 Convergent Gridding
Grid Plane
Control point Grid node
Sometimes collisions occur between the weighted Z values provided by each scatter data point
when several scattered data points are snapped to the same grid node. To overcome this
problem, the convergent gridding algorithm uses a blending function to average the scatter data
point Z values. Thus, multiple scattered data points are weighted and averaged into a single
node value.
840 Mapping Packages FloGrid User Guide

Convergent Gridder
The convergent gridding algorithm performs several steps during each iteration. In the first
iteration, which uses a coarse grid, each scatter data point is snapped to many (typically sixteen)
surrounding nodes. The grid is then smoothed and tied to the data with a biharmonic filter. In
the next iteration, the grid is refined by a factor of two, and again the scattered data points are
snapped to grid nodes. In this iteration, however, each scatter data point is snapped only to the
nearest eight (or fewer) nodes. Again, the grid is smoothed and tied to the data. Two more
iterations occur, where the grid is refined by a factor of two and each scatter data point is
snapped to fewer nodes. In the last iteration, each scatter data point is snapped only to the
nearest node. The grid is then smoothed and tied to the data a final time. During each iteration
the goodness-of-fit between grid and data is monitored to determine if more iterations are
necessary.
The effect of multiple iterations is several-fold. In areas where data is sparse or nonexistent, a
trend-like surface results due to the coarse interval in the first pass. In the vicinity of data,
however, the grid represents data accurately due to the final pass, which snaps each scatter data
point to the single nearest node. Since slope and curvature of the grid are carried from one
iteration to the next, the final surface projects trends that may exist between widely scattered
data points. The figures that follow show the result of each iteration.
In Figure J.2, the first iteration produces a coarse grid (grid lines shown), with each scattered
data point snapped to the nearest sixteen grid nodes. The result is a trend-like grid.
Figure J.2 Convergent Gridding: First Iteration
Figure J.3 shows the next iteration. The grid is refined by a factor of two, which doubles the
number of grid rows and columns compared with Figure J.2. Scattered data points are snapped
to the nearest eight nodes. Node values from the previous iteration are blended with the newly
computed node values.

Convergent Gridder
Figure J.3 Convergent Gridding: Second Iteration
In Figure J.4, the grid is refined again by a factor of two, and scattered data points are snapped
to the nearest four nodes. The grid begins to take on much more curvature than in the previous
two iterations.

Convergent Gridder
Figure J.4 Convergent Gridding: Third Iteration
Figure J.5 shows the results from the fourth (and final) iteration. In the vicinity of data, the grid
reflects the elevation of the data accurately. In extrapolated areas, the grid has a trend-like
appearance. Slope and curvature are used to project the surface between widely scattered scatter
data points.

Convergent Gridder
Figure J.5 Convergent Gridding: Fourth Iteration
In the presence of faults, the convergent algorithm behaves in much the same way as described
above. The difference is that the faults are introduced to reflect discontinuities local to the fault
trace. Convergent gridding can ignore faults in early iterations. This allows trends associated
with data to extend across faults, while forcing the grid to honor surface discontinuities in the
vicinity of faults. Alternatively, faults may be used during all iterations of convergent gridding.
Note The presence of faults can increase computation time significantly.
Figure J.6 shows a faulted surface created with convergent gridding.

Convergent Gridder
Figure J.6 Faulted Surface from Convergent Gridding
Setting Parameters
Initial grid interval
Grid interval of first pass.

This is the size of the grid interval during the first pass of convergent gridding. Each successive
gridding pass divides the grid interval by 2 until the desired final resolution is achieved. This
setting and the final grid interval determine the number of gridding passes required to converge
to a final grid solution. It also affects the level of data extrapolation. Data is extrapolated
approximately twice the initial grid interval, assuming Number of Nodes to Snap is set to 16.
Values less than 16 result in less extrapolation.
Set to the system null value for a computed solution by setting the value to zero. This computed
solution gives you the best result but does not really guarantee that the computation time is the
lowest you can have.
For a faster interpolation check the Reset interpolation on data selection change box to
compute the settings each time input data or output geometry change in such a way that they
match the computation you want (Interpolation or Extrapolation) but also take as constraint
the time computation. In those cases a fully-defined model is produced. (In some cases, uneven
data distributions for faulted surfaces can lead to a less than fully-defined model.).
Set to any other positive value for faster runtimes or more limited extrapolation.

Convergent Gridder
The Initial Grid Interval defines a square grid cell if the final grid cell is square, or a rectangular
grid cell if the final grid cell is a rectangle. That is, the aspect ratio (Yinc/Xinc) of the initial grid
cell is always the same as the aspect ratio of the final grid cell. The cell aspect ratio affects the
level of isotropy (square cells) or anisotropic (rectangular cells), such as directional correlation
of data, during the modeling process. When the final grid cell is rectangular, the initial grid
interval sets the dimension in X, with the Y-dimension computed to give the same aspect ratio.
Number of nodes to snap

During each pass, data are projected to 1-16 nearest grid nodes. For the first gridding pass,
which is the coarse gridding phase, this value may be controlled. After that, the gridder takes
control.
• Set to 16 for maximum extrapolation, or smaller values for less extrapolation and faster
runtimes.
• Set to 1 or 2 when gridding grid data, for example for data that occur at or near grid
locations.
Order of projection
This setting controls the method used when snapping data to grid nodes. It affects how the
model is shaped in extrapolated areas and applies to the initial (coarse) gridding pass only. After
that, the gridder takes control of the projection.
• Set to linear for more linear shaping
• Set to quadratic for more curvature in extrapolated areas.
The default selection is linear.
Number of final smoothing passes

This smoothing is applied at the final grid resolution after convergent iterations are complete. It
has no effect on prior Convergent Gridding passes or how smoothing may be applied there.
This smoothing is most effective on data other than point data as they are smoothed using this
feature. Point data (such as scatter data and marker data) are not smoothed (for example, the
model is constrained at these locations). Smoothing may be any positive number of passes.
Some typical settings are:
• 0 = No smoothing (default)
• 1 = Low smoothing
• 2 = Medium smoothing
• 4 = High smoothing
• 8 = Very high smoothing
This is a biharmonic smoothing process, which minimizes surface curvature while preserving
any linear trends in the surface.

Convergent Gridder
Conpac
Conpac is the mapping package in used in Grid. See the "GRID Reference Manual" for further
information. Inside FloGrid it is limited to:
• Mesh map interpolation
• Contouring.
Mesh map interpolation

Conpac uses mostly Least Square algorithms. Some other minor algorithms are provided as
well (Distance weighted average of points in search circle, Search radius for this point, The
number of point in search circle) for limited purposes.
Interpolation algorithms
There are six interpolation methods available in Conpac.
• Distance weighted average of points in search circle.
• Search radius for this point.
• The number of points in search circle.
• Least squares fit of reduced parabolic surface: Value = a + bx + cy + d ( x∗ x + y∗ y )
• Least squares fit for plane surface: Value = a + bx + cy
• Least squares fit of parabolic surface: Value = a + bx + cy + d ( x∗ x ) + e ( y∗ y ) + f ( xy ) .
For each you have a weighting function, which can be:
• Increase weight with distance: W1 = ( ( S – R )∗ ( S – R ) ) ⁄ ( R∗ R + ES )
• Equal distance everywhere: W2 = 1
• Decrease weight with distance: W3 = 1 ⁄ W1 .
Search Circle Definition

Fix Search Radius
You should set this value so that a representative selection of control points are within this
distance of the interpolation points. It may be set to some fixed value or it may allowed to vary
automatically over the map area. The process is quite sensitive to this parameter and it is
important to get it right.
When the Search Radius is set to Optimize the program computes it for you. Some times it is
possible that the distribution of points does not give you a good interpolation. You can then edit
new points and re-interpolate or decide to fix the Search Radius yourself.
Variable Search Radius

In this case Conpac makes a statistical best estimate of the mean search radius (Sm) required
to include points from Number of data to encompass groups on average and then permits
limited excursions away from this value during processing. The maximum excursion of the
search radius above the estimated mean value is given by: Smax = ABS ( S )Sm (where S=
Search radius and Sm = mean search radius).

Conpac
This limit is necessary to inhibit attempted interpolation when the interpolation point is well
outside the data area.
While this facility gives generally better results more economically than the Fixed Search
Radius you still have to supply the data in a reasonably uniform coverage of the area, digitizing
extra intermediate contours in complicated or low gradient regions. It become less reliable when
the number of discontinuities increases.
Note When data density varies dramatically over the map area it may be advisable to employ
a method which increases density.
The present Variable Search Radius system does not take account of faults so that, in this
presence of high fault densities, the chosen search radius may not be always have sufficient non-
zero-weight control points to obtain an interpolation. Indeed, since the faults normally behave
as barriers, it may not be possible to obtain enough data simply by increasing the search radius.
Note It is essential when using this mode to supply suitable data.
Octants
This is a further safeguard against poor interpolation. The search circle is divided into octants.
Octants gives the number of adjacent octants that may be empty of control points before
interpolation is rejected. Values greater than five are likely to result in poor values in some areas
(negative rather than running null values).
Note High values of Octants should not be used without using local interval truncation
(see"Local interval truncation" on page 849).
Number of data to encompass

It gives the number of distinct groups (lines or digitized contours) that are to contribute control
points to the interpolation search circle average. Suitable values range from 3 to 6 with higher
values being used when the spacing of the lines is very variable. For general purposes use 4 or 5.
For contours you should chose at least four different digitized contours and not more than ten.
For scattered data the absolute minimum is four points, but in practise this is not usually enough
because the distribution of the points is also important.
Other parameters
The following parameters allow you to improve the computation:
The damping factor

This is a smoothing parameter with value between 0.001 and 10.0 for light and heavy smoothing
effect respectively.
Note Smoothing is obtained at the expense of failing to honor the data points but the method
is effective for removing noise.

Conpac
Local interval truncation
Select this option if you require an exponential damping of local highs and lows. This is
particularly useful when working with digitized contours where the absence of an inner contour
usually implies that the surface does not pass through that level. The resulting surface is
smoothly curved but does not extend further than the specified tolerance (the Local Interval
Truncation value).
This value is the permissible extension Ztol of interpolated z-values above or below local highs
or lows or “floor” and “Ceiling” values. The value is normally of the same order as the contour
interval in use, and should be equal to about 0.7 to 0.8 of the digitized contour interval when it
is required to suppress values beyond un-digitized value in the results (unsteady interpolations
near critical values).
Global floor value

Select this option if exponential damping is required below some global minimum value. Use
this when a “clean” transition is required through a base value.
Local ceiling value

Select this option if exponential damping is required above some global maximum value. Use
this when a “clean” transition is required through a top value.
Grid quality
You can specify the grid quality. It is an integer between 1 and 10. This allows you to increase
the quality of the grid interpolation but it also increases the computation time. It not always
necessary to set it to maximum, because the quality of the grid interpolation may not improve
even you increase the value.
It is up to you to find the correct compromise between computation time and quality. Basically
grid quality subdivides the grid, so if you have a 10 by 10 grid with a quality of 10 you
interpolate a grid of 1000 by 1000.
Fault
You can also use fault for the computation. The fault can be Opaque, Transparent or in
between. That specifies the behavior of each fault when interpolating.

Conpac
Contouring
You can contour any 2D grid (3D property simulation grids, and mesh maps).
Conpac contours using the node value of your grid. There are two kinds of operation you can
do with Conpac:
• Manage the contouring parameters
• Manage the contouring layout.
Contouring parameters
Contour intervals
You can specify the Major Contour Interval, the Minor Contour Interval and the Base
Contour. All these values are in the property unit.
Contour Quality
You can also specify the Contour Quality. It is an integer between 1 and 10. It permits you to
increase the quality of the contour displayed by smoothing sharp angles. It increases the
computation time. It is not always necessary to set it to maximum, because at one step the
quality stays the same. It is up to you to find the correct compromise between computation time
and quality. Basically contour quality subdivides the grid, so if you have a 10 by 10 grid with a
quality of 10 you contour a grid of 1000 by 1000.
Gradient Control Value

You can set separately for minor and major contours a Gradient Control Value in plotting
units. It defines whether a contour line should be drawn or not. Conpac draws a contour only
if the normal distance is superior to the Min.Spacing Value.
Fault
You can also use Fault for the computation. The fault can be Opaque, Transparent or in
between. You can specify the behavior of each fault when interpolating. With a sloping fault
trace you have can contour or not inside it.
Note For contouring, contrary to interpolation, the fault elevation is not taken in account.
Only x and y apply.
Contouring layout
You can draw contours without color filled, or color filled contours, without drawing them or
color fill contours and draw them.
Labels
You can also decide whether or not you want to display labels. You can define separately for
minor and major contours, the label layout by specifying: the following options.
Label height
Specifies the height of the label in the plotting units.

Contouring
Space between labels
Defines the distance in plotting units between labels in a contour line.
Min. contour spacing

Defines the normal minimum distance value (in plotting units between two neighbor labels of
two different contour lines) to allow the label to be drawn.
Decimals
Sets the number of decimals you want to display. It is useful to contour some properties with a
value between 0 and 1 for example.

Contouring
Contouring
Printing images
Appendix K
Saving Images as Print Files

PostScript...
Creates a vector PostScript file of the current image.
Figure K.1 PostScript panel
As well as allowing a choice between Landscape and Portrait and Color and Grayscale, you
can choose between Default Quality and High Quality. The difference between these options
is the way a decision is made to see if an object is in front of, or behind, another object.
The default quality option produces Postscript at the screen resolution, high quality at twice this.
FloGrid User Guide Printing images 853

The Width and Height may only be entered for encapsulated PostScript. For the other sizes,
these sliders are disabled and are used to show the page size selected.
When you click on Write Postscript File, a check is first made to see if the aspect ratio of the
3D window matches the aspect ratio of the output. If it does not match, you are presented with
three choices:
Resize
An attempt is made to reduce the 3D window to match the aspect ratio, or to increase the 3D
window if the reduction would make it smaller than the minimum size. The output file is then
created.
Create
No change of window size is made, and the output file is created.
Cancel
The process is stopped and no output file is created.
Note The program may be unable to resize the window correctly if it is near to its minimum
size. If this occurs, you are asked to resize the window manually.
The next stage is to check if the directory entered here (or from the config.file) exists. If
not, you are asked if the current working directory should be substituted instead, in which case
the file is not written.
The last stage is to check if the requested filename already exists. You may either overwrite the
file or cancel the operation. If, however, the filename is the default filename, this check does not
take place.
Limitations
• If the aspect ratio of the 3D window and the PostScript output are not the same, the image
is centered on the page.
• The center triangle of the ternary color legend is colored gray.
• The appearance of cell outlines may not be the same as on screen, and may also differ from
one printer to another.
• Transparency is a not a supported feature of PostScript, therefore all surfaces appear
opaque.
Image File...
This menu item allows the 3D image to be saved in various file formats.
854 Printing images FloGrid User Guide

Figure K.2 Write Image panel
The quality of the JPEG image can be changed; a higher quality (higher value) is likely to mean
larger file sizes. This parameter has no effect for the other formats.
When you click on the Write Image button, a check is made to see if the requested file name
already exists. You may either overwrite the file or cancel the operation. If, however, the
filename is the default filename, this check does not take place.
Table K.1 Configuration file settings
SECTION 3D
SUBSECTION WRITE_IMAGE
FILENAME $TMPDIRgrtframe.jpg
FILETYPE JPEG
WIDTH 500
HEIGHT 500
SUBSECTION WRITE_IMAGE
FILENAME is the name of the file entered on the dialog panel (note that if a name is entered
without a suffix this is added automatically). The config. file name does not alter the
default file name.
FILETYPE determines the type of image selected. Choices are:
• JPEG (JPG is also accepted)
• TIFF (TIF is also accepted)
FILETYPE determines the 3-letter suffix that is automatically added to the file name.

Choice of type of image
The advantage of JPEG over TIFF is the size of the files, due to the compression techniques
used. However JPEG is better suited to photographic images than to computer generated
images. TIFF files as generated here use the lossless run-length encoding method; the
compression used for JPEG is a lossy compression.

Related information for supported file save formats
PostScript file save format

Postscript format print files can be printed on a PostScript format printer using the Ghostscript
GSview utility provided in the tools directory of your Installation CD on both UNIX and PC, or
the UNIX lpr or lp print command.
Bitmap format files can be created in GSview on the PC using the File | Print option, then
checking the Print to File printbox on the Printer Setup panel, with one of the bitmap devices
(that is bmp16, bmp256 or bmp16m) selected in the Device field. You can write the bitmap file
to your work area, then embed it into your documents. A similar program called Ghostview
exists for X11 on UNIX.
The GSview program also has the option to create a bitmap for previewing the file within word
processors such as Word. The option is "Add EPS Preview" under "Edit", and allows the file to
be saved under a different name when a format is chosen (such as Windows Metafile for Word).
Note that when printed on a PostScript printer, both files will be the same - the bitmap is only
used to preview the picture within Word. This only works, however, if the file has been saved
in EPS format.
Additional information
To obtain the latest release of Aladdin or GNU Ghostscript consult the Ghostscript World Wide
Web home page at http://www.cs.wisc.edu/~ghost/.
To obtain a CD-ROM of Ghostview, contact Russell Lang at Ghostgum Software Pty Ltd, 218
Gallaghers Rd, GLEN WAVERLEY, VIC 3150, AUSTRALIA,
email: gsview@ghostgum.com.au.

History of developments
Appendix L
Developments in FloGrid 2004A_1

• The Well Correlation Canvas has now been restored and works as normal.
• An issue with incorrect values being reported for RESCUE or map-based property models
has been fixed. This occurred when a user clicked on such a model in the 3D viewer and
received incorrect cell position and property values.
• An issue with a RESCUE model being overwritten if the property values were edited and
a workspace or command file saved and replayed has been fixed.
RESCUE
• FloGrid 2004A uses the RESCUE version 33 libraries. Please refer to "Known Issues" in
the "GSS Software Release Notes" for more information on this.
FloGrid User Guide History of developments 859

Developments in FloGrid 2004A
General
3D Viewer
We now use the OpenInventor graphics library from TGS for our 3D Viewer. This improves
graphics performance whilst requiring less memory for visualization.
We have taken this opportunity to adopt the OpenInventor standard mouse interactions, giving
us consistency with other OpenInventor applications such as Petrel. If required, the mouse
buttons can be reset to behave as in previous FloGrid releases using the drop-down menu
Preferences | Mouse Buttons (from the top of the main window).
See "How to interact with the 3D Viewer" on page 40 for more information.
External units
When FloGrid is launched, a pop-up panel appears in which you can set the initial choice of
external units (Field by default). You can still set the external units via the main menu at any
time after.
If you wish to prevent this panel appearing on start-up, edit the Config file and change the
following setting:
----------------------------------------
SECTION FLOGRID
----------------------------------------
SUBSECT EXTERNAL_UNITS
-- Force external unit selection at startup
ASK TRUE
Commands
FloGrid 2004A includes further enhancements to the commands system. See "Play/Save
Commands Settings" on page 102 for more information.
Data import
RESCUE
FloGrid 2004A uses the RESCUE version 35.1 libraries.
OpenSpirit Link
The OpenSpirit link is no longer available in FloGrid. The recommended workflow for this
functionality can be found in Petrel.
860 History of developments FloGrid User Guide

Structured gridder
Transmissibilities and Non Neighbor Connections
FloGrid now has the ability to calculate transmissibility values for a structured grid, including
non-neighbor connection (NNC) transmissibilities within the global structured grid and
cartesian sub-domains, arising from faults, layer pinchouts and LGRs. The NNCs can be
displayed as sticks (lines or tubes) connecting the cell centers, colored according to the
calculated transmissibility; multiple transmissibility realizations can be stored if desired using
different generation options. The transmissibilities of associated neighbor connections are
stored as TRANX/TRANY/TRANZ cell-based properties.
NNCs generated by ECLIPSE may be imported and visualized from INIT files, and NNCs may
be exported as a component of a GRDECL file using the NNC and EDITNNCR keywords.
An editor allows the NNC transmissibility values to be changed. NNCs can be removed by
setting their transmissibilities to zero, and new NNCs can be introduced into the grid, with user-
specified transmissibilities between selected pairs of cells. For further information see "Non-
Neighbor Connection Editor" on page 119.
Flux-based upgridding
Flow based upgridding is now available for simulation models that contain FrontSim Flux data.
This facility allows flow based upgridding to be applied to a wider range of models than in
previous versions of FloGrid. See "Upgridding Folder" on page 488
Export
You can optionally export the structured grid geometry in map coordinates. See "Export..." on
page 430

General
Command handling
FloGrid now offers a new set of controls for playing command files. You can choose to skip
commands that only affect the user interface. In many cases this results in much quicker replay
of the command file. There are also options for how command files are saved. Command file
options can be set using the menu selection File | Commands | Play/Save Commands
Settings....
Documentation
This manual has been restructured. The contents have been regrouped into sections
corresponding to major functional areas of FloGrid.
Licensing for wells and well menus

A problem occurs when using the 2003A release. If the license feature gf_fg_analysis is
not present, FloGrid issues spurious error messages whenever a well is displayed, or a well
menu is accessed. Only the well planning options should be controlled by this license feature.
The problem is resolved in patch release 2003A_0.1 and in the full 2003A_1 release.
RESCUE models
Multiple properties of the same type
FloGrid can now import multiple properties of the same property type from RESCUE files. On
import, the properties are named uniquely, if required, and displayed under the appropriate
property type node on the FloGrid model tree. For upscaling and other workflows that identify
properties only by type, the active property can be selected using the tree.
Memory improvements (slab load)
FloGrid now uses the RESCUE "slab load facility" to reduce the memory requirements for
loading a property from a RESCUE file. When FloGrid accesses properties from a RESCUE
model with large block unit grids, this development allows partial loading, in slabs of a size
controlled by the CONFIG file parameter SLAB_SIZE_MEGABYTES (default 50MB).
Structured gridder
GRDECL import
FloGrid can now read the grid and properties from an ECLIPSE keywords file in ASCII format
(GRDECL file). This includes LGRs. Property types found in the file are assigned to the correct
FloGrid property type whenever possible.
Sub-unit layering based on user-defined surfaces

The user can now choose to base the implicit (sub-unit) layering of the grid on an arbitrary
surface. Proportional, top-conforming or bottom-conforming layering can be based on reference
surfaces loaded into the FloGrid surface tree, instead of using the default upper and lower
horizons of a unit.
Overburden / subsurface gridding
The Structured Gridder now allows you to add new layers to an existing grid. The new layers
can be placed between any pair of k-surfaces in the grid or above or below the grid. The shape
of the surfaces is based on a selected surface from the surface tree.
Simulator interface
Well connection factors
The well connection factor calculation has been modified to give more accurate results in non-
orthogonal cells. The new method is compatible with changes in Schedule and Near Wellbore
Modeling.

General
Pop up menus in 3D viewer
In FloGrid 2003A, it is easier to invoke drop-down menus for objects displayed in the 3D
Viewer, via a right mouse click, without using the Ctrl modifier. The menus correspond to the
menus available on the object nodes of the 3D tree.
Note Normally the right mouse button in the FloGrid 3D Viewer is used for translation. In
FloGrid 2003A, the software determines what you want to do and selects the
appropriate behavior.
RESCUE models
FloGrid supports the latest version of the RESCUE library (version 32). Older RESCUE files
can also be loaded (version 9 and later).
OpenSpirit interface
Use of the OpenSpirit interface is now controlled by a separate license feature. The client
installation is no longer supplied as part of the SIS Simulation Software release and must be
obtained direct from OpenSpirit. FloGrid 2003A requires OpenSpirit 2.4 (available for SGI,
Sun and PC installations). A new option is available with this release, to import 2D horizon data
derived from seismic interpretation.
Wells
Well creation and well planning
The options for creating and planning wells have been reorganized. The following options are
available:
• The Create Wells... option allows the specification of well names and well head locations.
This option can be used to define wells before importing deviation survey data specified as
offsets, or to create wells before editing the wellpaths. This option is available from the icon
on the top bar of the main window, or from the drop-down menu on the Wells node of the
data tree.
• The Advanced Vertical Well Planning option provides facilities for selecting target
locations for multiple vertical wells. This option is available from the drop-down menu on
the Wells node of the data tree, subject to licensing.
• The Edit Wellpath... option is for creation or editing of wellpaths, subject to drilling
constraints. This option is available from the drop-down menu for selected wells on the data
tree, subject to licensing

Creating a lateral
The facilities for creating a lateral well have been improved, to guide the user through the
process. When the Add Lateral... menu option is chosen on the well node, a small dialog box
is displayed asking for the name of the lateral and the KO point. You can enter a KO point by
typing it in or select it in the 3D Viewer.
Wellhead visualization
Wellheads can now be displayed in the 3D Viewer using options on the Well Creation panel
and the Well Display Options dialog. Their color, size and visibility can be modified.
Well event management

The Well Event Management panel has been re-written to make it easier to work on events
for groups of wells. New event types of plug and squeeze have been added.
Well event animation

It is now possible to animate the well events over time. The event dates are added to the global
time line for use with the animation controls on the 3D Viewer. Similar animation buttons exist
on the Event Management panel, to allow animation to be performed only for the dates of
events for a particular well.
Well logs
Synthetic well log generation for recurrent properties
Recurrent properties can now be used as input for synthetic well log generation. In addition, the
generation panel has been redesigned to enhance its usability.
Synthetic well log fitting
Synthetic well log generation has been enhanced by adding the capability to fit the well log to
the model, that is reverse the stretch and squeeze that was performed as part of the property
population operation.
Well log export
Well logs can be exported to LAS files. Single or multiple well logs can be exported, but a
separate file will be created for each log.
2D Mapping
Back interpolating structural data
Corner point Z-values from a grid can be back interpolated to create 2D structure maps.
Time dependent properties

Recurrent simulation properties can be now used with 2D mapping.

Interrupt facility
Time-consuming interpolation processes can now be interrupted via a Cancel button on the
progress bar.
Property Population
Grid population history
Property Population parameter sets are preserved to track the Property Grid’s population history.
This enables you to recreate a property grid or to review its generation history.
LGR population
For models containing LGRs, FloGrid populates the global domain cells as well as the LGR
cells when the population operation is performed.
Coordinate correlation
New spatial correlations X Y K and X Y Z have been added to handle different kinds of
depositional environment in distorted corner point grids. Different coordinate correlation leads
to different computed distances between the data supports and the output location, leading to
different data weights and therefore, different property distributions.
Data segregation
The deterministic property population algorithms have been enhanced to provide the ability to
control the input data used in the population. Data can be used across all the units, block units,
or the blocks in the structured grid, or in the particular structural volume where it is located.
Variograms
Variogram specification dialog has been redesigned to enhance its usability. Experimental
variogram calculation performance has been improved for regular grids.
Indicator classification
The following changes and improvements have been made:
• Toggle button to control the inclusion of an Indicator Class.
• drop-down class name selection to select commonly used indicator class names.
• Multiple valued Indicator Classes.
• Auto filling of Indicator Class range.
• Preserving Indicator Classes that have been utilized for Property Grid population.
Usability
Behavior of the frequently used panels in the property population parameter specification
workflow have been modified to be non-modal. This enables easier and simultaneous
interaction with multiple property population parameter set panels.

Data analysis
The following changes and improvements have been made:
• Discrete data histogram will be displayed as bar charts.
• Vertical proportions display now include frequency.
• Option for stale data removal from the workspace.
• Multiple Univariate Statistics dialogs can be viewed simultaneously.
Structured Gridders
Boundary and fault controls accessible using the tree
Additional functionality is now accessible from the Boundary and Fault Gridding Controls
nodes of a structured grid FloGrid Model node on the tree. The new menu items include
creation of model boundaries and setting of fault gridding control types and slope options.
Aquifers for structured grid models

You can define analytical or numerical aquifers and attach them to selected faces of a structured
grid. The three analytical models supported by ECLIPSE are available. You can select the grid
cells to be used for numerical aquifers by picking them in the 3D Viewer. The aquifer
connections and aquifer cells (for numerical aquifers) are visualized by new Aquifer Cells and
Aquifer Connections grid properties. Appropriate keywords are written for the selected
aquifers when you export the model.
Copy 3D grid with structured grid model

When you create a new structured grid model by copying another structured grid model, by
default any 3D grid and initial properties in the source model is now also copied. You can
choose not to copy the 3D grid.
Global grid manipulations

The previously existing functionality allowing a selected region of an imported grid to be
globally refined or coarsened has been extended to apply to corner-point grids constructed
within FloGrid. The refinement/coarsening now attempts to preserve existing LGRs, except
where these intersect the refined/coarsened region.
LGR folder enhancements

The way that you specify weightings for the LGR refinements in host cells has been made
clearer. The LGR Refinements tables now contain drop-down buttons that you use to either set
default equal weights or to pop-up another panel in which you can enter the weights you want.
The NXFIN/NYFIN/NZFIN fields have be moved below the start and end cell fields to better
match a typical workflow.

Creating an unstructured model from a structured grid
An unstructured model can now be created from an existing structured grid using Create
Model. This is equivalent to exporting a structured grid and importing the data into a new
unstructured model. Unstructured LGRs can then be inserted into the full field model.
Grid Faults
IJ grid faults in imported grids
When a grid is imported, using Create Model | Import, any IJ grid faults present in the grid are
auto-detected. These faults now appear in the Fault Property Calculator so that fault
properties can be calculated and FAULT keywords exported for them.
IJ grid faults in edited grids

On an existing grid, the Grid Editor allows you to create sets of split nodes with an optional
throw. If you do this, you are now prompted for a name and the named selection appears in the
Fault Property Calculator.
Simulator Interface
Set-up options
The simulation set-up panels have been reorganized. There are two main options:
• 2 phase - the default model is 2 Phase (oil and water) with the well rates specified at the
group level. Wells are assigned to two groups according to well type (producers or
injectors), and rates can be specified for each group. The user can also choose to run
FrontSim with incompressible fluids.
• Advanced - by selecting Advanced Features the user can access additional set-up panels
where well rates are set on an individual basis. Multi-phase runs can be set up, with PVT
and Scal data supplied by the user or calculated from correlations.
Simulator selection
Selection of FrontSim or ECLIPSE is now available via the Simulation Manager panel, using
the menu option Options | Simulator | Simulator to Run... This also allows the user to specify
remote simulation on a different machine.
Aquifer simulation
If aquifers have been created for a given model, the active aquifers, selected on the data tree,
will be used for simulation.
Historical production data

In the Advanced set-up option, the production schedule can optionally be defined from loaded
historical production data.

Results analysis
For analysis of results from multiple realizations, the Group menu can be used from the
Simulation Manager. This provides options to select simulation runs by criteria such as
porosity or permeability realization or by name, and add to different histogram groups. Up to
three histograms can be displayed separately or together.

General
Fault trace import from CPS
The option to import fault traces in CPS format has been enhanced, and the association of fault
traces with surfaces has been automated.
Well deviation survey import
The options for importing data using OpenSpirit have been extended to include well deviation
surveys.
Well visualization
Wells can be classified by type as producer, injector or unknown. In the 3D display, wells can
be displayed using unique colors or colored by well type.
Well markers can be color coded by surface.
Fault / Gridding Control Framework Editor

Piecewise linear interpolation
The Fault and Gridding Control Frameworks now provide piecewise linear interpolation
between the control vertices for faults and gridding controls. This is now the default behavior,
instead of cubic spline interpolation. You can select the interpolation type for all faults or
individual faults as required.
Import/export
You can now export and import fault frameworks and gridding control frameworks to/from file.
Snap edit mode

An additional edit mode allows you to move control vertices and “snap” them onto other objects
in the display (for instance the lines of a wireframe, or the surfaces of another fault or gridding
control).
Usability
The rendering performance of the fault framework and gridding control framework editors has
been greatly improved.

Property Population
Display of well logs from property population
During property population operations, the generated well logs (for example, primary and
lumped logs) can be accessed using a separate node on the data tree.
Variograms
Variogram usability has been significantly improved in 2002A_1; and you now have greater
control over variogram modeling parameters. Experimental variogram calculation performance
has been improved and memory usage has been reduced.
Indicator classification
The indicator class index, which is used to fill the property grid, is now displayed alongside the
indicator class name in the indicator classification editor.
Unstructured and Structured Gridders

Edit layering panel
You can generate default equal proportional sub-unit layers directly from the main Edit Layer
Controls panel, that is without having to open and accept the default values in a second panel.
Radial LGRs in Structured Gridder

There is a new Minimum DeltaR field on the LGR folder, for use when defining radial LGRs.
This parameter constrains the minimum annular thickness permitted in a radial LGR grid. It
defaults to 5 feet (the ECLIPSE 300 default).
Well gridding in unstructured gridder

The full range of radial growth styles are now available for horizontal and vertical fracture well
styles. Small cells at the ends of vertical fracture wells have been removed to improve simulator
performance.
Fault Property Calculator

IJK faulting
The Fault Property Calculator is now available with IJK zig-zag faults.

Volumetrics
Improved algorithm for fluid contact intersections
An improved algorithm has been implemented for calculating grid cell intersections with
horizontal fluid contact surfaces. The method is faster and more accurate than the previous
algorithm.
Managing data quality problems

The volumetrics option now includes automatic checks for cells with null values, negative
volumes (due to “inside-out” cells) and inconsistent saturation values.
Simulator Interface
ECLIPSE interface
You can choose to use ECLIPSE as the simulator instead of FrontSim, using the same basic set-
up for simulation runs.
Remote simulations
Simulation runs can be launched for remote execution, instead of running large simulation jobs
on the same system as FloGrid.
Fault properties for simulation

Fault transmissibilities computed and exported by the Fault Property Calculator can be
included in the simulation data.
Simulation Manager (and Volumetrics Graphics)

Enhancements to the Simulation Manager and graphical displays include an option to load
historical data for comparison purposes, ability to plot all results against time (instead of just
minimum, maximum and selected curves) and ability to import restart files as well as
streamlines for 3D display.
Usability
There have been a number of usability improvements including reorganization of panels,
improved status information and addition of a Notes panel, and enhancements to plots.
Calculator
The calculator has been extended to handle operations on properties with multiple realizations.

Grouping realizations
You can now use an option to automatically “guess” groups for quick classification of multiple
realization runs for volumetrics or simulation.
2D Mapping Canvas
Convergent gridder
A convergent gridding algorithm (based on the CPS gridder) has been added as an interpolation
algorithm for mesh map creation.
Maps of summed or averaged properties

When building a mesh map from simulation grid properties, you can work with lumped or
averaged values from multiple layers if required.
Well Correlation Canvas

Display using TVDSS
You can now switch to display logs in TVDSS instead of MD.
Line tracker
A line tracker tool is available for aiding correlation work.
Completion intervals
Well completion intervals can now be visualized on the 2D well correlation canvas.

Structured gridder
Radial LGRs
You can define radial LGRs from the LGR folder. Radial LGRs may be defined in one host cell,
centered on the cell center, or over a two by two block of four host cells, centred on the common
corner of the hour cells.
Dual porosity/permeability system models

You may import maps for fracture or matrix properties into FloGrid, upscale these properties on
structured grids, and export GRDECL keywords files, which define a dual system grid and
associated properties (you could already do this on unstructured grids). You can also now create
a Structured Gridder model from an imported GRID file that represents a split dual system
grid.
Resample LGRs
You may generate LGRs in which the underlying structural or property model is sampled in
order to generate the LGR cell geometry. These LGRs therefore enable you to honor the geology
more closely than previously.
Grid editing using contour and scatter data

The structure and properties of a structured grid can be edited using contour and scatter data in
the Property Editor panel. The data is supplied using the boundary data structures and the
program produces an edit of the grid, which is a smooth interpolation of the supplied data. The
property editing supports structured and unstructured grids.
IJK zigzag grids for reverse faults

Reverse faults are supported by IJK zigzag grids. The program automatically adds extra layers
to support them. They are pinched out in areas outside the reverse faults.
Refine and coarsen in IJK

Selected ranges of IJK can be grouped or sub-refined. The grid and properties are updated
automatically.
Upgridding multi-block models and guide layers

A corner point based multi-block geological model can be upgridded directly into a single
simulation grid. Also, it is possible to fix selected layer boundaries as barriers to the upgridding
process. These are initialized to be unit boundaries.

Unstructured gridder
Radial flow based properties for 3D well domains
The volume and transmissibility calculations in the 3D well domains now use radial flow theory.
This improves the bottom hole pressure calculations at wells and as a result even coarse radial
refinements can provide accurate simulations.
Enhanced pinchout handling

The thickness and pore volume criteria for pinching out grid cells can now optionally be a cell-
based property. The pore volumes of the pinched out cells can optionally be aggregated into
neighboring cells.
Improved dual source models

The Dual Source Model feature, which allows grids to be based on one structural framework
while the properties can be based on another has been improved, so that property sampling at
faults follows the property model accurately.
3D Viewer
• The 3D Viewer now supports seismic, well logs and markers
• The 3D viewer now has a arbitrary plane slicing option (Scene | Grid | Plane Slicer...).
This allows the digitizing of line features that are subsequently used to slice the grid by
selecting all cells ‘above’ or ‘straddling’ the plane. The plane may be angled in both the
horizontal and vertical axes.
• The import of FrontSim output into pre and post applications has been made faster and
more robust through the use of a new shared file format. This format is optimized to
improve visualization performance.
• The Iso-Cell Selection option (Scene | Grid | Iso-Cell Selection...) allows the selection
of a collection of cells through which a surface of constant value (isosurface) would pass.
Cell selection is achieved with the aid of an interpolation method that computes a cell’s
minima and maxima from its neighboring cells. The selected cells may be used to edit
existing or new properties using the Simulation Property Editor.
• The Streamline Display dialog has been redesigned into three folders that represent
line attributes, line filtering and property thresholding. The panel is now far less
imposing and easier to use.
• The Streamline Display dialog’s Filtering folder has a new Select Penetrated Cells
toggle. This selects and displays just the cells penetrated by the currently displayed
streamline segments. These cells and their properties can then be manipulated using the
Simulation Property Editor.
• A new option Use Wheel Mouse on the IJK Slice dialog allows use of the mouse wheel
button on Windows machines to ‘animate’ slice selections through the model.
• Individual unstructured grid cell outlines are now ‘knitted’ together to create more
‘renderable friendly’ lines. This speeds up rendering of unstructured grids by up to 100%.

• Additional properties and timesteps from INIT and RESTART files may be imported onto
the currently active grid using the File | Import | Property menu.
• Both initial and restart properties may now be exported to INIT and RESTART format files
using the File | Export | Property option. These files may then be imported into other
applications that support this format.
• The text font and height used to display titles may be customized using a new button on the
Edit Titles dialog.
• The text font and height used to name the wells may be customized using a new button on
the Wells dialog.
• Well and Grid Appearance dialogs/toolbar buttons now reflect and only affect the state of
the currently active grid.
• The name of the currently active grid now appears on the title bar of relevant dialogs.
• New toolbar buttons to toggle the display of axes and to toggle if axes should cover the
displayed or whole model extent.
• Cell selections may now be made on the intersections of multiple digitized boundary
regions.
• IJK Slice, VOI and Threshold cell selection dialogs now all have an Exclusive option to
invert the current selection.
• We now honor IJ slicing by default when K slicing - this gives a more intuitive slicing
approach.
• The menu structure has been changed to both locate menu items more logically and allow
greater extensibility.
• A ‘dialog launch’ toolbar has been added to the 3D Viewer providing buttons that ‘launch’
commonly used dialogs directly rather than having to use the menus.
• The video toolbar can now be applied for I, J, K animation in addition to time animation.
There is an additional toolbar to select between IJK and T animation.
General
Init and Restart files
Properties in both structured and unstructured grids can be exported in INIT and RESTART file
formats.
Import grids as geological models

It is possible to import corner point grids into FloGrid and treat them as geological models. This
allows you to generate other grids based on imported grids. The Create Models module
provides this feature.
Simple Mesh Map Creation

The Create Simple Mesh Map facility allows you to create simple models by entering a few
points in a matrix, which are then used to generate mesh maps for horizons or other properties.
See "Mesh Map Data" on page 347.

New front end to the calculator
The Advanced Calculator with expression handling has a push button front end similar to a
hand held model.
Reservoir Data Store Panel Removed

The Reservoir Data Store module has been removed from FloGrid. The new Main Window tree
means that you always have access to the Surface, Faults and Wells without launching a separate
window.
Major Tools Enhanced or New

• Comprehensive 3D visualization of all input and generated data (seismic, maps, well
deviations, logs, markers, RESCUE geological models, simulation models, simulation
input data, simulation results).
• Facilities to validate geological input data with options for data clean-up.
• Interactive and programmable calculators
• Basic structural framework building
• Geological and simulation model creation
• Geostatistical property population
• Volumetrics
• Fault property calculation
• Well planning
• 2D mapping canvas
• 2D well log correlation canvas
• Structured grid generation
• Unstructured grid generation
• Multiple realization handling

Structured grid editor

Fault creation and healing
You can now introduce new faults in the Grid Editor, using the Split Ordered Selection
option.
You can now heal faults using two new options. The Heal Ordered Selection and Heal
Selection options remove vertical splits, along selected paths or pyramid faces respectively.
Structured Gridder
Imported Grid models
In 2001A_1 you can add / edit / remove LGRs from imported grid models.
Areal gridder
In 2001A and previous versions, the calculation of unit thicknesses took place as soon as the
areal grid had been built. By default, this calculation is now delayed until the 'Set Layering'
button is pressed, or, if that is not pressed, until the 3D grid is built. This enables you to iterate
over the areal grid building stage more quickly.

Structured gridder
Delete, Rename, Copy
You can now delete or rename an existing structured gridding model. You can also create a new
structured gridding model by copying an existing model. These facilities are accessed from the
File menu.
Flexible, iterative workflow

It is now possible to iterate over all stages of creating a structured simulation grid. Changing an
object, for example redefining and rebuilding the areal grid, causes all dependent objects, for
example the 3D grid, to be deleted. You are warned, and given to opportunity to cancel the
action before making such changes.
Areal gridder
You may specify the areal grid cells by typing in the approximate cell size (DX, DY) required
as an alternative to giving the NX, NY. The DX, DY values are converted to NX, NY for use by
the gridder.
Vertical gridder
You are told how many cells will be generated in the 3D grid, and given the opportunity to
cancel, before the gridder starts the possibly lengthy process of generating the 3D grid.
Editable fault zigzag via block assignment

FloGrid 2001A allows you to modify the zigzag location of a fault in the simulation grid. If
FloGrid’s automatic fault placement algorithm gives an inappropriate result, you can edit the
grid’s BLOCK property, and your choice of blocks is respected in subsequent grid building
operations. Your choices persist until the next time that the areal grid is built. You can force a
reset by deleting the BLOCK property
LGRs
All the LGR gridding controls have been brought together into the LGR folder. The vertical
gridding folder no longer contains LGR controls.
LGRs may now be added, edited or deleted after the 3D parent grid has been generated. If the
parent grid exists, you can click on the Update 3D grid button, and only the changes, that is the
new and edited LGRs, are gridded, rather than the whole grid being regenerated. To upscale
properties on the new LGRs only, select those domains through the Edit| Volume of Interest |
Domain Selection menu and set the Edit Scope option (on the Structured Gridder |
Properties panel) to Main Viewer selected cells before upscaling.

You now have more control over the LGR geometry. You can define variable LGR cell sizes
within each host cell by entering weights into each of the tables defining the number of
refinements per host row/column/layer. Default numbers of refinements per host
row/column/layer can also be preset before defining the LGR extent.
IJK fault export

FloGrid 2001A allows you to set and export transmissibilities on all simulation faults (both IJ
and IJK faults). The new facility allows the fault transmissibility to be controlled separately for
each blockunit-blockunit interface. This is based on an automatically generated MULTNUM
property and MULTREGT table.
Control line import and export

FloGrid 2001A allows you to export and import control line sets. This is useful when a you have
a new version of a structural framework, which has a re-positioned axes origin. In this case the
hand edited gridding controls can be preserved from one model to the next.
High density fault trace performance

FloGrid 2001A allows you to have fault traces / tip-loops of extremely high density with no loss
of performance. In previous versions building an areal grid could take you a very long time if
the faults that you had imported had more than 100 points on them.
Memory requirements
There have been significant reductions in the amount of memory required to store structured
grids. These savings are available for newly created grids and imported EGRID format grids.
Imported grid models

You can create a structured gridding model by importing an existing GRID or EGRID format
grid file. For 2001A you can view this imported grid, create new simulation properties, and use
the new Simulation Grid Editor.
Simulation Grid Editor

Structured grid editor
The grid editor offers lateral (horizontal) and vertical (along the coordinate line) editing
functionality for corner point simulation structured grids. The editing workflow starts with the
selection of the coordinate lines followed by horizontal and/or vertical editing and then, saving
the edits performed.

RESCUE models
Sampling surfaces from the RESCUE wireframe
Structural sampling from a RESCUE model has been significantly improved. This particularly
affects those models that have unconformities modeled as separate surfaces (for example
EarthVision models).
Editing of RESCUE faults

FloGrid 2001A allows you to edit the faults that are imported with a RESCUE model. This is
especially useful when the “tip-loop” definition of the fault is absent or wrongly specified for
use by FloGrid.
Enhanced fault editor

The fault trace editor has been enhanced to allow you create faults in 3D rather than the previous
2D. You can now establish 3D pick guides based on other fault traces and control lines. The fault
editor is no longer locked into an areal view so you can view the third dimension (depth) while
editing, without having to suspend the edit.
Upgrade to the property model property cache

The property array cache can now be disabled entirely. This is useful if memory is severely
limited.
RESCUE versions
FloGrid 2001A uses the latest version of the RESCUE library (version 26).
You can now import gOcad / RC2 models in RESCUE version 26 format and also rotated
models where all the structure maps and property grids have been rotated by global angle.
Property and simulation property editors

Advanced expression editors
A new option now exists for editing Property Model and Simulation properties. This option, the
Advanced Expression, offers much more complexity than the existing simple expressions
without you having to understand the complexities of the Calculator language.
It allows you to type in a single arithmetic expression, which is then used to edit the currently
selected property. The expression may span several lines, and include conditional (if, then,...),
relative (>, =,...) and logical (and, or,...) controls as well as most common arithmetic ones (log,
exp, sin,...).
In essence, the Advanced Expression is similar to a single statement from a simple
programming language.

Unstructured Gridder (PetraGrid)
Face-based simulation grid properties
Transmissibility can now be displayed in the Main Viewer on a face-by-face basis. Thus the
value appearing on a cell-face is the actual transmissibility across that face. The new property
names “Trans” and appear in the lists of properties in the relevant panels. Face-based simulation
grid properties can be edited and created using the Simulation Grid Properties Editor panel.
Rename
You can now rename an existing unstructured gridding model. The facility is accessed from the
File menu.
Grid cell-centre editor

The Cell Centre Editor allows you to make modifications to the points used to construct cells
in 2D PEBI grids. Cell center editing is not normally required but it can be used to make
adjustments to the grid in complex regions where there are several close or intersecting features.
The editor can also be used to modify the points used to define the vertices of cells in 2D
tetrahedral grids.
Vertical zigzag faults

The vertical zigzag fault option of the Structured Gridder is now available for unstructured
grids. This option, available only for grids built from Rescue models, allows the fault to move
through the grid with different IJ locations in different K layers.
Editable block assignment

FloGrid 2001A allows you to modify the logical location of a fault in the simulation grid. If
FloGrid’s automatic fault placement algorithm gives an inappropriate result, you can edit the
grid’s BLOCK property and your choice of blocks will be respected in subsequent grid
generation operations. Your choices will persist until the number of cells in the areal grid
changes. You can force a reset by deleting the BLOCK property.
Well tracing without property model

It is now possible to perform well tracing on imported grids with no underlying property model.
Main Viewer
Time taken to import models
This has been significantly reduced by both providing direct read access to the ECLIPSE
output files and ensuring all required data is extracted from the RESTART files in one single
pass. Direct read access means we extract property data directly from the ECLIPSE files as and
when we need it.

Memory usage
This has been significantly reduced without degrading rendering speed or quality.
Hardcopy options
These have been improved with the addition of an option for high quality Vector Postscript. This
option generates superior output with improved hidden line/hidden surface algorithms. Please
note that generating high quality Vector Postscript takes time.
Rubberband zoom
A facility has been added allowing you to ’lasso’ an area of interest with a rubber band box.
When the area is selected, just that area is zoomed to fill the 3D window. Each zoom is added
to a list so that you can unzoom to any previous level. An option also exists to unzoom to the
starting point.
Grid cell distortion

This option allows the grid to be both ’flattened’ and ’thickened’ to enable better evaluation of
property distribution in highly dipping or exceedingly thin reservoirs.
View model statistics

This option provides statistics on the active grid, current property and wells. The dialog can be
toggled between displaying information for the whole model or for just the current selection.
Display shale breaks

This option allows cell faces above and below thin inactive layers such as shale breaks to be
hidden so reducing the amount of data to be shown and speeding up model interaction. Some
models have many such internal inactive layers; if so this option can have a dramatic effect on
speed.
Usability improvements
• Improvements to axes including drawing at model or selected cells extents and ability to
set the number of decimal places.
• Many titles may now be displayed on the Main Viewer at the same time. The active grid
name, current property name and current timestep can now be displayed within any title.
• When the application is busy the cursor changes to an hour glass shape when it is over the
Main Viewer.
• You can now freeze the display allowing multiple changes to be made before re-rendering
the view.
• The choice of linking rotation, translation and/or zoom between master and slave viewers
may now be made as the slave is created.
• 3D windows have become hot spots. This means that new windows avoid overdrawing
them, to minimize re-rendering of the 3D view.
• The Tile 3D Windows option allows automated tiling of master and slave viewers.

• The new Object Rotation dialog (which complements the existing Camera Rotation
option) allows animation of model rotation.
• The Normalize panel allows better control over how the 3D view is normalized.
• Stereo capabilities have been improved and enhanced to be more easily tailored to the
user’s preference. Stereo is now available on platforms with suitable graphics cards.
• You may now access the Display | Color Legend | Object for Color Legend menu option
with a left mouse click on the color legend. With multiple objects in the viewer this allows
you to easily select the data model the legend should represent.
• Streamlines, like grid cell lines and faces may now be toggled using a ”Display
Streamlines” icon.
• Grid and property imports may now be cancelled whilst in the import is in progress.
Cancelling whilst reading the grid aborts the import immediately. Cancelling whilst reading
properties aborts the read but the model is still displayed
• Streamlines display may now be interactively controlled from the Streamlines | Edit
Streamlines dialog. Streamlines can be displayed as lines or tubes, and the tube radius can
be modified.

Faults
Selecting fault traces in the main viewer
The pick and Ctrl pick selections of fault traces in the Main Viewer are now linked to the
Reservoir Data Store fault tree. The tree scrolls to the latest pick.
Fault trace export from the RDS fault tree in CPS format
Traces can be single lines and open or closed polygons. Z values are exported if they exist. As
the CPS format does not support the definition of up-thrown or down-thrown status or which
surface / map a fault polygon may be assigned to, this information is not captured when the file
is exported.

The fault block splitting algorithms have been extended to support more complex wireframes.
This addresses problems that typically occurred when manual fault block splitting has been
required and where there are pinched out horizons.
“Die out” fault modeling

Map based modeling of faults that die out in the reservoir is now available.
Faults can now “die out” as they pass down through the structural framework. This feature is
currently controlled in the Reservoir Data Store where fault traces can be associated with
surfaces using the right-hand table.
Note This is not the same as assigning traces to maps.
If a fault has any traces associated to any surfaces then the structural framework interprets the
top associated surface as being the highest horizon that is cut by the fault and the bottom
associated surface as being the lowest horizon that is cut by the fault. If no surfaces are
associated (the default) then the fault is assumed to pass all the way thrown the model. This
information is used to ensure that the grid blocks have no throw in horizons outside the fault.
This is also reflected in the FAULTS keyword output.
Hint The new feature can be turned off in the Config file if you encounter problems.
Node finder
This is a find and scroll to facility on the trees, in the Reservoir Data Store and structural
framework folders.

The Node Finder allows you to move to specific nodes in a tree based on the name of the node.
You specify a label pattern (ASCII characters with one or more instances of a wildcard '*') and
the Node Finder populates a list box with the node labels that match the pattern. Clicking on
the list box entries causes the tree containing the matched node to scroll in order to make the
node visible.
The Node Finder is triggered by positioning the mouse pointer on any of the tree nodes (not
necessarily selected) and clicking the right mouse button with the Ctrl key pressed.
On the Node Finder there are check-boxes to decide whether the search should be case
sensitive and whether the matched labels are to be sorted alphabetically.
Reservoir data store

In the Reservoir Data Store each search is carried out in the context of the current folder (that
is Maps, Faults or Wells). If the folder is changed when the Node Finder is open, it will
automatically update its hits trying to match the same pattern to the new context.
structural framework
In the structural framework, Faults folder, there are two instances of the Node Finder
available: one for the Available/Unavailable faults trees and one for the Volume of Interest
tree.
Rescue models
Property model
You can now create and visualize simulation properties, including results, on the Rescue
Property Model from which the simulation grid was built. It is also possible to export new or
modified Rescue Property Model properties back to the original Rescue model.
Memory requirements
There have been significant reductions in the amount of memory required to load Rescue
models. This reduction in memory and other optimizations mean that Rescue models now load
much more quickly.
Property scenarios
There is basic support for Property Scenarios, a mechanism for managing which groupings of
properties form a model.
Property and structural models

Property model visualization dialog
There is now an option to clear all previous selections in the Structural and Property Model
Visualization dialogs.

The Property Model Visualization dialog allows you to select and display block unit wire-
frames, block unit surfaces, block unit surface colors and property slices from multiple block
units. The selections are cumulative, with new selections added to the selections already made.
The Clear button provides an easy way to clear all the selections cumulated in the display.
Note The same functionality is also provided in the structural framework Block Unit
Selection dialog to clear all block unit selections.
Coloring block units.

To allow you to easily identify particular block units in the display, an option has been added to
the Property Model and structural framework Display dialogs to allow you to choose the
color of the selected block unit surfaces.
Properties
Under certain circumstances the restriction that properties must exist over the entire property
model has been lifted. This change allows you to visualize and upscale properties that do not
exist in all block units. If an upscaler requires a property or properties that do not exist in parts
of the model, upscaled cell values where properties are missing will be defaulted.
Note Currently, this restriction is only lifted for Rescue models that have extra information
about property scenarios provided.
Structured gridder
Zigzag faults
The way that the Structured Gridder samples heights of zigzagged faults has been changed. In
99B the heights of the extrapolated horizons at the location of the co-ordinate line were used. In
2000A the coordinate line is moved back to the fault (in the same way GRID does) to get the
throws. The throws are then shifted on the co-ordinate line so that at least one of the heights
matches one of the un-extrapolated horizons (an improvement over GRID).
Note The coordinate line is not moved in the case of vertically zigzagged faults (where the
fault appears in multiple coordinate lines). This coordinate line move can be switched
off via the Config file if you detect a problem.
Unit thickness
The unit thickness calculation has been corrected in the Structured Gridder. It now takes no
account of the extrapolated thicknesses. This change will mean that, if the simple top- or
bottom- conforming options are used (in the Vertical Gridding table in the Structured
Gridder), the number of layers in the simulation grid might differ from 99B.

Hint 99B back-compatibility ECL.CFG options exist if they are needed.
EGRID export
This option allows you to export grid geometries in the new EGRID format in binary or ASCII
format. This format is much faster to load in other applications and is the preferred way of
exchanging grid geometries in 2000A.
The Structured Gridding Export Data panel has been extended to provide two new output
options EGRID and FEGRID on the Select Output Format drop-down. In addition in 2000A,
if you do not specify a file extension or indeed specify an incorrect file extension for the selected
grid type, the correct file extension is created.
Streamline visualization
Streamlines can be imported using the Import Streamlines menu option in the Structured
Gridder module.
Streamlines can be added to the Main Viewer using the Display Streamlines button. Once in
the Main Viewer, streamlines can be thresholded, colored, animated etc. using the same options
as included and described in FloViz.
Streamlines are currently associated with one simulation grid, determined by the current model
(grid) when the streamlines are imported.
Upscaler
Reporter
The Upscaler reporter has been fixed to correctly report the number of cells to be upscaled and
the number done so far.
Microgrids
An option has been included to refine the microgrids used to hold sampled data from the fine
grid models. You can control the refinement by multiplying the nx, ny, nz dimensions by any
three integers. You can also specify a fixed refinement. These controls can be applied to
truncated cells and untruncated cells independently. This was implemented to allow you to (i)
control and reduce any sampling errors that might occur (ii) implement standard sampling if the
model has little heterogeneity on the scale of the simulation grid blocks.
Tops
The dx, dy, dz upscaler has been extended so that is now also computes Tops values for the
simulation grid blocks.
Note For 2000A this option is only available via the Config file.

Main viewer
Color coded control lines
Control lines are now colored in the Main Viewer according to their classification (for example
I-Line, J-Line, Zig-Zag, Out-of-Boundary...). Selected control lines are highlighted with red
dashed lines alternating with the original control line color.
Selecting control lines

Improvements have also been made to how control lines are selected from different parts of the
program such as the Main Viewer, the Edit Control Lines panel and the Control Lines folder
in the Structured Gridder module.
Save and restore

In 2000A, on Unix platforms, Save and Restore now uses the standard swap mechanism to back
the save and restore persistent heap.
Hint 99B back-compatibility ECL.CFG options exist if they are needed.
Unstructured Gridder (PetraGrid)

EXTREPGL keyword
This keyword lists the global cells to be replaced by LGR cells for a specific LGR. In 99B the
set of global cells was assumed to be the union of the parent cells of LGR cells. The new
keyword was introduced as the previous approach may omit some global cells.
Elliptic background cells

This feature provides elliptic background cell distributions around horizontal wells and
fractured vertical wells. The growth and theta divisions of the cell distributions are derived from
the well refinements.
Improvements to 3D well gridding

A number of improvements have been made to the 3D well gridding algorithms, enabling them
to handle long wells and other complexities.
Use of property types

The Property Edit panel now accepts property types and versions. Its use for unstructured grids
is now consistent with structured grids.

EGRID file support
You can now import and export unstructured grid geometry via a new file format with the
extension .EGRID. For backward compatibility the .PGRID format will also be supported. The
.EGRID format can have combined structured and unstructured grids in a single model.
Additional radial well controls

Control of radial divisions for both 2D and 3D well grids have been extended. Now, the types
of refinements are logarithmic, geometric, linear and custom. Further, you can optionally set a
minimum limit on the outer radius of the first cell next to the well; or even fix it at a specific
value.
Scenario support
This provides support for geological models that have multiple property scenarios within a
single model. You are able to select a working scenario during vertical gridding and cell
property generation stages.
Changes between 99B and 2000A output

1 The measured depth values are correctly imported in the 2000A Generic Well Deviation
Survey reader. Hence, there could be differences in the .trj and .schecl files for models
which use that reader.
2 Radial bulk cell distribution around selected wells has been improved.
3 The Well connection calculation for single cell wells has been changed, so that it now
intersects the well track with the grid and selects all such cells, where as in 99B cell
selection forced the cells to a single column.
4 Grid smoothing has been made symmetric for symmetric initial grids. Hence, there will be
changes to models with smoothing.
5 Fractured vertical well gridding has been improved to make small cells bigger, to improve
simulation speed.
6 Fractured horizontal well gridding has been improved to allow wells with multiple
fractures close to each other to grid. This changes all fractured horizontal well models
slightly.
7 Boundary and fault intersection handling has been improved, and slight changes may be
observed near intersections.
8 Made areas masked around each feature a function of the local background cell size. This
will improve hence change grids whose background cells have variable sizes.
9 Changed the units for aquifer cross section areas to ft2 from acres when external units are
ECLIPSE-FIELD.
10 The parameter name in command files has changed to CrossSectionArea from Area.
Back compatibility is maintained for command files with argument Area in acres.

Developments in FloGrid 99B
General
Trees
Improved usability of all trees. The scrolled position of a tree is now maintained when contents
are modified.

Visualizing contours
2D and 3D structure and property contours can be imported, assigned to surfaces, given
property types or units, queried for information, displayed in 3D as colored lines and picked in
3D to make boundaries and control lines.
Contours are imported via a control file, which supports a flexible definition of 2D and 3D
contours in various formats. They are displayed in the Map folder.
Default splitter trace

This option is available from a fault node and builds a default splitter trace for a fault if
upthrown and downthrown traces have been assigned to one or more surfaces. The default
splitter trace will be constructed from the uppermost upthrown trace and the lowermost
downthrown trace.
Property model
Rescue models
FloGrid 99B supports Version 19 Rescue models. This version allows FloGrid to load Rescue
structure and properties into memory only when they are required. This significantly reduces
memory requirements and allows much larger models to be loaded without turning off Save
and Restore.
Visualization improvements
The Property Model Visualization dialog has adopted the same IJ and K slicing look and feel
as the Gridding and Upgridding panels. It supports control and shift selections of slices,
increment, decrement and typed in selections. I, J and K slicing is available for the entire model
rather than on a per block unit basis.

Property model probe
Information about a property model can be obtained by picking on cells of the 3D grid. The
block, unit and IJK number for the picked cell is displayed on the status line of the Main Viewer.
OpenSGM 5.0
FloGrid has been upgraded to support the current version of SGM.
Note Unfaulted SGM models must now be supplied in SGM 5.0 format. Faulted SGM
models should be supplied via Rescue.
Rescue models
Unfaulted Rescue model horizons can be added to the Reservoir Data Store.
Note This option is available only via a config option. If the config option is set, surfaces
and associated mesh maps are created when an unfaulted Rescue model is read. This
is intended primarily for use with the PetraGrid dual source model.
Use the RMS 3D grid geometry when sampling Rescue models instead of using the supplied
block unit horizon data. This option allows FloGrid to handle Irap Rescue models where the 3D
grids do not follow the faults, or the faults have been zigzagged or have had their slopes
restricted in RMS. Even if faults have been gridded exactly in RMS we recommend this option
is used.
Structured gridding
Enhanced vertical gridding
Existing on, off and proportional gridding options have been extended to allow for users to
specify different thicknesses or percentages of grid layers within a unit. In addition, grid layers
can be constructed directly from property model layers. Vertical gridding using property model
layers can be done on a unit wide basis or on a per block unit basis.
Interregion transmissibility multipliers

For each grid, you can enter a list of pairs of integers and transmissibility multipliers for that
pair. Integers in the list should correspond to cell values in a MULTNUM array. If no MULTNUM
array exists, one will be created using the block unit number. 1 is added to the block number to
avoid using 0 as a MULTNUM region. The list of integer pairs and multipliers can be exported to
ECLIPSE.
LGRs
LGRs can now be added or modified once a simulation grid has been built. If an LGR is added
or edited when a grid already exists, the grid will be regenerated. Properties associated with the
previous grid will be deleted.

Vertical gridding parameters
Vertical gridding parameters can now be changed once a simulation grid has been built. If a
parameter is modified when a grid already exists, the grid will be regenerated. Properties
associated with the previous grid will be deleted.
Control lines
Z values of control lines are retained when they are edited. In 98B_1 this was available via a
config option. It is the default in 99B.
Previous behavior when editing control lines was to get the z values for new or edited control
lines by resampling from the property model. The new option retains the z values of the original
points, allowing more accurate editing.
Upscaling simulation properties

Single phase upscaling
Faster and more accurate single phase upscaling. Prior to 99B, property model properties were
sampled by taking each simulation cell; querying the property model to establish the property
model grid spacing at that point; constructing an appropriate resolution microgrid within the
simulation cell; sampling the XYZ location of the property model at the center of each
microcell. In 99B, the IJK position of each corner of each simulation cell in the property model
is stored. IJK information includes fractions to define exactly where a corner lies within a
property model cell. IJK information from each corner is used as before to construct an
appropriate resolution microgrid. However, instead of doing XYZ queries at each microcell
center, property model IJK positions are interpolated onto each microcell and properties are
looked up using the integer parts of interpolated IJK values. This new approach speeds up
upscaling by reducing the number of XYZ searches, uses less memory and is more accurate as
it allows properties in microcells to follow any fine resolution geological layering. As IJK cell
corner information is stored with the grid, subsequent upscaling runs for the same grid will be
much faster.
LGR gridding
The approach has been extended to LGR gridding to ensure properties in LGR cells correspond
to the correct property cells even when the XYZ positions of the LGR corners are calculated by
interpolating the corners of the parent cell.
Upscaling by region
Upscaling by region. Upscaling can now be performed on all cells or just the cells currently
selected in the Main Viewer. This allows you to test upscaling speed or accuracy on a few cells
and allows different upscaling techniques to be used in different regions. Depending on the
outcome of these tests, grids can be rebuilt, new upscaling parameters chosen or remaining
properties computed using the property editor and / or calculator.

Adjoint upscaler
This is very similar to the linear boundary condition method (without face multipliers), but only
performs one flow-like simulation, rather than the usual three. The method for backing out the
upscaled values is modified so that they can be retrieved from the single simulation without
approximation. The technique is related to the adjoint methods used in history matching.
Half grid block upscaling

This performs linear boundary condition upscaling on each half grid block, in each of the three
flow directions. The difference between the values in each corresponding pair of half blocks is
a diagnostic measure of the validity of the upscaled values.
Face multipliers
Face multipliers on the linear boundary condition and half grid block upscalers. These are either
user specified for the side faces, computed by the algorithm, or defaulted to unity.
Property edit history and replay facilities

Full histories of how each property was created and subsequently edited are available via an
Extended Property Information panel. Information includes upscaling methods and
parameters, operations and what cell selection criteria were used. Facilities are provided for
browsing edits and where possible recovering them for replaying on subsequent properties.
dx, dy and thickness upscalers

Three new upscalers have been added to compute corner point cell sizes. This allows you to
quality assure your model and can be used in grid calculations such as setting inactive cells.
Unstructured gridding (PetraGrid)

Radial wells
User controllable r and theta divisions for radial wells. This enables the use of customized
specification of the number and size of cells in a radial well domain in the R and theta directions.
Horizontal wells with multiple fractures

This will generate a grid representing a horizontal or sloping well intersected by fractures,
which can be oriented along (parallel fracture) or across (perpendicular fracture) the well track.
Dual source model

A dual source gridding model allows you to combine structure and property from two different
models of the reservoir. This is particularly useful if the structure is built within FloGrid and
properties are imported from a geological modeling package.

Transition bulk regions
This gridding style provides a linear decrease of cell size from a maximum at the boundary to a
minimum at user specified distance inwards from it, and could be used to smooth cell sizes at
bulk boundaries.
Vertical gridding
This provides flexible control over the sub-division of units. The available gridding styles are;
proportional, top conforming (offlap), bottom conforming (onlap) and property model based.
Algebraic upscaling
This allows algebraic upscaling of reservoir properties. A total of 13 methods are available.
Tensor permeability handling

This option enables handling of any symmetric positive definite tensor permeability description.
Simulations are performed using computationally expensive multi-point fluxes.
Generating well connections for selected wells

Allows creating well connections for a user selectable subset of the wells.
2.5D unstructured grids with 3D well domains

This creates composite well domains with a 2D part and a 3D part. The two outermost sets of
cells are of 2D type and the remaining cells are of 3D type.
Local grid refinement

This allows local grid refinements (LGRs) to be defined, which may be 2D or 3D. LGR support
for unstructured grids for dual porosity models will be supported in ECLIPSE 2000A.
Dual porosity solution display

This version of FloGrid supports the visualization of ECLIPSE output from unstructured dual
porosity grids.
Importing new wells into existing gridding models

This option allows you to access any new wells defined in the Reservoir Data Store since the
gridding model was created.
Reduced output to ECLIPSE using SOLVNUM

This option reduces the size of the ECLIPSE keyword file by generating them only for active
cells.

3D visualization
Simulation property editor
Derived quantities
A favorite in RTView, we now have a fully functional Simulation Property Editor panel with
which new properties can be created or existing ones edited. Recurrent properties are now
available as operands allowing new recurrent properties to be created or existing ones to be
edited. T+1-T" and "T-T0 operators are now available from the drop-down list to generate
difference properties based on existing recurrent properties.
Main Viewer
Color legend
The color legend editing facilities have been much improved. Edits are now property
independent, allowing choice of colors for Continuous, discrete and logarithmic legends. A
property’s Color Map Editor is accessed via the Color Legend | Color Legend Editor menu
option or by clicking on the Color Legend directly. The editors are type dependant, meaning
each is tailored to the integer, float or ternary data belonging to the property.
Commands
All options available from the Main Viewer are now commanded. A session should be wholly
re-playable via the created command file.
Background color
The viewer background color can be toggled from the default black background with white lines
to a white background with black lines via the File | HardCopy Colors menu option.
Inactive cells
The display of inactive cells can now be toggled via the Grid | Display | Display Inactive Cells
option. The color used to display these inactive cells can also be set.
Wells
Only wells completed in the currently selected cells are now shown. Previously all wells were
always shown which could cause problems when attempting to view for example a particular
slice. All wells may be displayed via a switch on the Wells... panel.
FloViz wells are now drawn using enhanced visual primitives which have improved their
display both in the Main Viewer and on hard copy. They are also now affected by directional
lighting.

Multi-segmented wells
ECLIPSE multi-segmented wells are now supported via the well annex.
Dual porosity
Dual porosity is now supported via a check box on the ECLIPSE Import dialog. This button is
only required for Eclipse.GRID files - unstructured and .EGRID files know if they are dual
porosity and will ignore this flag.
Image formats
Support for JPEG, TIFF and PBM image formats.
Mouse actions
You can switch between using the default RTView style mouse interaction for rotation, zoom
etc. and the Geoframe settings via the Preferences | Mouse Buttons menu option.
Multiphase and hierarchical upscaling (FloGeo

option)
Note These options are only available if you have a FloGeo license.
Structured simulation properties

In the Structured Simulation Properties window, the 2-Phase, Multilevel and Diagnostic
folders are present.
In the Property Model Property Editor window, you can choose whether you wish to generate
properties by using an expression, a Calculator program, or SCAL records.
In the Simulation Property Editor window, you can choose whether you wish to generate
properties by using an expression, a Calculator program, or SCAL records.
Multilevel workflow
This is the hierarchical workflow to upscale at different data scales for example from core scale
to lithofacies then from lithofacies to full field.
The FloGrid main window

This now includes a tree display of the models within the program and associated details.
SCAL scaling details

These are supplement attributes (SCALE and DIRECTION) that are created in the new upscaled
SCAL records. You can edit the Record labels to display this data.

The FloGeo multilevel folder
This provides the link back to SCAL for the upscaled properties. It allows SCAL records to be
created, one for each simulation cell, which hold the selected upscaled properties. This data can
then be used as input to the next level of upscaling
Two-phase upscaling
This comprises the following methods:
• Constant fractional flow
• Capillary equilibrium
• Constant saturation
• Majority vote
There is also support for using J-functions, binning to a template set of curves, generating
directional output curves, directional input curves and allowing upscaling of a region (set of
selected cells) in the simulation grid.
Diagnostics
These are different statistical methods that allow data to be calculated for the fine scale property
distribution within each simulation grid cell.
Current methods that are provided are:
• Standard deviation
• One-point probability
• Two-point probability
• Prob outside [av – scale, av + scale]
Export
Export currently comprises:
• FloGrid export panel for grid, properties, well trajectories
• SCAL export of 2 phase curves
In other words, you must export the data in two places.
Note Note also there are currently backwards links to SCAL but no forward links from
SCAL to FloGeo which means that you must manage the upscaled curves.

Developments for FloGrid 98B
General
Save and restore
A facility to save and restore all model data and relationships associated with a session. Saved
workspace files work across all machines of the same type (for example SGI, Sun...) and the
same program version.
To upgrade from one release to the next, FloGrid will restore and play a command file
embedded within the Workspace file. Workspace files that are loaded on a different
machine type (for example saved on SGI, the opened on Sun) will attempt to restore the saved
workspace using the original embedded command file.
If the workspace cannot be restored (for example, if the paths to data files in the command file
are not replicated on the new machine, the embedded command file will be saved in the working
directory as a file called RECOVERY.CMDLOG.
A New Workspace option is also provided which clears all existing data from the program.
Main window menu

Calculator and text editor access from the main window menu.

Right mouse button menu
Right mouse button options to delete maps, faults and surfaces from the Reservoir Data Store
trees, providing no structural models are present.
Improved tree behavior.

The multi select options have been removed. The program acts on selected nodes, automatically
detecting multiple selections, improved error messages.
Multiple file selection dialogs for importing multiple maps.
Added a CPS fault reader which supports the definition of fault polygons specified as upthrown
and downthrown traces. Extended the I J ID fault reader to support names not surrounded by
quotes.
structural framework
Deleting structural models
A menu option to delete structural models, if and only if, no property models exist.

Property model
Rescue
An upgraded Rescue interface to use the publicly available Rescue 1.0 class libraries, developed
in conjunction with and supported by most of the leading geological modeling applications
(contact geomodelling vendors for their release dates).
Deleting models
A menu option to delete structural models, if and only if, no property models exist.
Structured gridding
Interface
The top level structured gridding interface has been rationalized. Users now choose to create
one of three types of model - corner point, rectangular or upgridded with the highly specialized
upgridding option moved from the corner point gridding window to a separate window.
Control line gridding

A default set of control lines and polygons corresponding to the faults in the associated
structural / property model is generated each time a gridding model is created. Control lines /
polygons can then be edited, deleted, merged or copied prior to deciding which control lines
should be gridded to. Control lines can be copied from one gridding model to another.
Areal grid editing

This allows you to interactively select and move individual nodes in an areal grid. In FloGrid
98B this is only available for grids with vertical co-ordinate lines.
Sloping faults
Structured gridding to sloping faults using sloping coordinate lines. This option allows you, in
a single pass, to build a grid which honours the selected upthrown and downthrown sections of
control polygons.
Areal rectangular gridding

Areal rectangular gridding with facilities for interactive (3D and tabular) addition, deletion and
moving of rows and columns and rotation and translation of boundaries.
Thickness layering
Vertical gridding support for constant thickness layering within units. Grid layers within a unit
can be built upwards from the bottom surface of a unit, or downwards from the top surface.

Grid geometries
An option to export grid geometries in the expanded .GRID format.
Well trajectories
An option to compute and export well trajectories in FloGrid for importing into Schedule. If
Perm X, Y and Z exist these values are included in the trajectory file. Otherwise they are
defaulted.
Fault locations
An option to compute and export simulation fault locations in a separate fault file.
Upgridding a block unit grid

An option to fix the number of rows, columns or layers when upgridding a block unit grid,
honoring other upgridding parameters as possible.
Upscaling / simulation properties

Simulation properties window
The upscaling window has been replaced by a new Simulation Properties window. This
window contains a property tree, organized by property type, which supports options for
querying, creating, editing and deleting properties.
Versioning of properties
Versioning of properties within a gridding model is now supported. Each time the upscaler is
run, a new version of each property can be created with user selected names or the old property
can be overridden. At export time, users select which version of a property they wish to export.
The latest version is exported by default. There is now no need to create a separate upscaling
framework model.
Modifying simulation properties

Options for modifying simulation properties using the Calculator or by using simple
expressions.
Power upscaling
User defined exponent when using power upscaling.
Upscaling
Folders are provided for single phase upscaling and if FloGeo is licensed, multiphase upscaling.

Validating properties
Options to validate upscaled properties. These are currently provided in the form of additional
upscalers providing statistical and diagnostic information about an upscaled property.
Unstructured Gridding (PetraGrid)

3D PEBI gridding
This facility provides the generation of 3D PEBI grids for modeling horizontal or deviated
wells. This option is best suited to near well regions consisting of layers of slowly varying
thickness.
Note This option is only available to sponsors until FloGrid Version 99B
3D local grid refinements

This facility provides the insertion of unstructured refinements into existing corner point or
2.5D unstructured grids. They may be output as LGRs for local time stepping or as an in-place
LGRs, by updating the parent grid. This option is best suited to parent grids containing host cells
that have a similar areal to thickness ratio and are close to orthogonal.
Segmented coordinate lines

This facility enables gridding to faults that are curved in cross-section. It generates 2.5D
unstructured grids based on piecewise linear coordinate lines.
Multi-point flux approximations

This option generates flow coefficients for ECLIPSE to take account of non-orthogonal effects
in modeling flows across cell interfaces.
Multi-cell aquifers
This is an extension to the existing numerical aquifer handling. It provides the use of multiple
cell aquifers, each with its own set of properties.
Variable gridding
This facility provides a smoothly varying background grid that takes all wells into account.
Cells grow from wells starting from a user specified minimum size to a user specified maximum
size.
Well connection upscaling

This facility allows the use of a fine grid single phase simulation result to calculate well
connection factors for coarse grids. The user has to create an appropriate fine grid, run a single
phase simulation and read the summary files into the PetraGrid module.

3D visualization
Well visualization
Improved and speeded up well visualization. Wells are now rendered as tubes, with optional
labels.
Color legend
A more flexible color legend. You can override the default color legend minimum and
maximum values for any property type.
Cell probe
A cell probe for providing cell based information about a user selected list of properties.
Postscript hardcopy
This option creates a vector postscript file, in landscape or portrait mode for all line and surface
data and titles. It also has control for the paper size and options for color and gray scale modes.
Note In FloGrid 98B wells are not plotted in the postscript file.
An option to change how much grid lines are raised above the surface. On certain occasions grid
lines may come through from layers below. Unfortunately, this effect is model sensitive. This
feature allows the user to control how much grid lines are lifted towards the eye away from their
corresponding surface, thereby allowing you to interactively control this effect.
VRML export
This allows printable items from the current display to be exported in VRML 1 or VRML 2
format and viewed using external VRML browsers.
Note VRML export has been disabled.
Multiphase and hierarchical upscaling (FloGeo

option)
Note These options are only available to sponsors until FloGrid 99B.

Bibliography
Appendix M
Beal, C.: The Viscosity of Air, Water, Natural Gas, Crude Oil and its Associated Gases at Oil-Field
Temperatures and Pressures, [Ref. 1]
Trans. AIME, Vol. 165, Page 94 - 115. 1946

Beggs, H. D., and Estimating the Viscosity of Crude Oil Systems, [Ref. 2]
Robinson, J. R.: J. Pet. Tech., Page 1140 - 1141, Sept. 1975.
Brown, K. E., and The Technology of Artificial Lift Methods, [Ref. 3]
Beggs, H. D.: Vol. 1, PennWell Publishing Co., Tulsa, 1977.
Clark Isobel, Practical Geostatistics, [Ref. 4]
Applied Science Publishers Ltd., Barking, Essex, U.K., , 1979

Dake, L. P.: Fundamentals of Reservoir Engineering, [Ref. 5]
Elsevier Scientific Publishing Co., Amsterdam, 1978.

Dale, M., Ekrann, S., Effective Relative Permeability and Capillary Pressure for 1D Heterogeneous Media, [Ref. 6]
Mykkeltveit, J. and 4th European Conference on the Mathematics of Oil Recovery, Roros, Norway, June 7-10, 1994.
Virnovsky, G.
Davis, J. C., Statistics and Data Analysis in Geology [Ref. 7]
Wiley, , 1973
Deutsch Clayton, and GSLIB - Geostatistical Software Library and User’s Guide [Ref. 8]
Journel A. G., Oxford University Press, Inc., New York, New York, 10016, 1992
Dukowicz, J. K. Efficient Volume Computation for Three-Dimensional Hexahedral Cells [Ref. 9]
Journal of Computational. Physics, 74, Page 493-496, ,1988.

Durlofsky L. J., A New Method for the Scale Up of Displacement Processes in Heterogeneous
Jones R. C., Reservoirs [Ref. 10]
Milliken W. J. Fourth European Conference on the Mathematics of Oil Recovery, Røros, 1994.
Farmer C. L, A Global Optimisation Approach to Grid Generation [Ref. 11]
Heath D. E. and Moody SPE 21236, 11th SPE Symposium on Reservoir Simulation, Anaheim, 1991
R. O.
FloGrid User Guide Bibliography 905

Fisher, Q.J., and Knipe, Fault Sealing Processes in Siliciclastic Sediments, [Ref. 12]
R.J., Faulting, Fault Sealing and Fluid Flow in Hydrocarbon Reservoirs, Geological Society Special
Publications, G. Jones, Q. F. Fisher, and R.J. Knipe, (eds.),Vol. 147, Page 117-134, 1988.
Foxford, K.A., Walsh, Structure and Content of the Moab Fault Zone, Utah, USA, and it Implications for Fault Seal
J.J., Watterson, J., Prediction, [Ref. 13]
Garden, I.R., Guscott, Faulting, Fault Sealing and Fluid Flow in Hydrocarbon Reservoirs, G. Jones, Q. F. Fisher, and R.J.
S.C., and Burley, S.D., Knipe, (eds.)Geological Society Special Publications, Vol. 147, Page 87-103, 1998.
Frick, T. C.: Petroleum Production Handbook, [Ref. 14]
Vol. 2, Millet the Printer Inc., Dallas, for the Society of Petroleum Engineers.
Fulljames, J.R., Fault Seal Processes, in Norwegian Petroleum Society, (eds.), [Ref. 15]
Zijerveld, L.J.J., Hydrocarbon Seals–Importance for Exploration and Production (conference abstracts): Oslo,
Franssen, R.C.M.W., Norwegian Petroleum Society, Page 5, 1996.
Ingram, G., and
Richard, P.D.,
Gunasekera, D. et al. “A Multi-Point Flux Discretization Scheme for General Polyhedral Grids.” [Ref. 16]
SPE paper 48855, 1998

Gunasekera, D., “Segmented Coordinate Line Based Unstructured Grid.” [Ref. 17]
Herring, J. and Cox, J. 1998
Gunasekera, D., Cox, J. “The Generation and application of K-orthogonal grid systems” [Ref. 18]
and Lindsey, P. SPE Paper 37998, 1997
Hall, K. R., and How to Solve Equation of State for Z-Factors, [Ref. 19]
Yarborough, L.: The Oil and Gas Journal, Page 86 - 88, Feb. 18, 1974.
Heinemann, Z. and “Modelling Reservoir Geometry With Irregular Grids” [Ref. 20]
Brand. C SPE Paper 18412, February 1989.
Hull, J., Thickness-Displacement Relationships for Deformation Zones, [Ref. 21]
Journal of Structural Geology, Vol. 10, Page 431-435, 1988.

Isaaks Edward, and An Introduction to Applied Statistics [Ref. 22]
Srivastava R. M., Oxford University Press, Inc., New York, New York, , , , 10016, 1989
Katz, D. L., Monroe, R. Surface Tension of Crude Oils Containing Dissolved Gases, [Ref. 23]
R., and Trainer, R. P.: Pet. Tech., SPE Reprint Series, No. 15, “Phase Behavior”, Page 1624, Sept. 1943.
King, M. J., Application of Novel Upscaling Approaches to the Magnus and Andrew Reservoirs [Ref. 24]
MacDonald, D. G, Todd, SPE 50643, SPE European Petroleum Conference, The Hague, 1998.
S. P and Leung, H.
Knipe, R.J., Juxtaposition and Seal Diagrams to Help Analyze Fault Seals in Hydrocarbon Reservoirs,[Ref. 25]
American Association of Petroleum Geologists Bulletin, v. 81, Page 187-195, 1997.
Knott, S.D., Beach, A., Spatial and Mechanical Controls on Normal Fault Populations, [Ref. 26]
Brockband, P.J., Journal of Structural Geology, Vol. 18, Page 359-372, 1996.
Brown, J.L.,
McCallum, J.E., and
Weldon, A.I.
Knupp, P. M. On the Invertibility of the Isoparametric Map [Ref. 27]
Computer Methods in Applied Mechanics and Engineering, 78, Page 313-329, 1990.
906 Bibliography FloGrid User Guide

Lee, A. L., Gonzalez, M. The Viscosity of Natural Gases, [Ref. 28]
H., and Eakin, B. E.: J. Pet. Tech., Page 997 - 1000, Aug. 1966.
Lindsay, N.G., Murphy, Outcrop Studies of Shale Smear on Fault Surfaces, [Ref. 29]
F.C., Walsh, J.J., and International Association of Sedimentologists Special Publication 15, Page 113-123, 1993.
Watterson, J.,
Madsen, R. A. Change of Scale for the Full Permeability Tensor on a Tetrahedral Grid [Ref. 30]
th
4 European Conference on the Mathematics of Oil Recovery, Roros, Norway, June 7-10, 1994.
Manzocchi, T., Walsh, Fault Transmissibility Multipliers for Flow Simulation Models, [Ref. 31]
J.J., Nell, P., and Petroleum Geoscience, Vol. 5, Page 53-63, 1999.
Yielding, G.,
Olea Ricardo A., Geostatistical Glossary and Multilingual Dictionary [Ref. 32]
Oxford University Press, Inc., New York, New York, 10016, 1991
Porkess Roger, ED, Dictionary of Statistics, [Ref. 33]
Harper Collins, 1991

Saad N., Optimal Gridding of Stochastic Models for Scale-up [Ref. 34]
Kalkomey C. T. and Fourth European Conference on the Mathematics of Oil Recovery, Røros, 1994.
Ounes, A.
Smith, E. H. The Influence of Small-Scale Heterogeneity on Average Relative Permeability, in Reservoir
Characterisation II, [Ref. 35]
Lake, L.W., Carroll, H.B. and Wesson, T.C., Academic Press, 1991.
Spiegel, M. R. Vector Analysis and an Introduction to Tensor Analysis, [Ref. 36]
Schaum’s Outline Series, McGraw-Hill, 1959.

Standing, M. B.: Volumetric and Phase Behavior of Oil Field Hydrocarbon Systems, [Ref. 37]
Ninth printing by Millet the Printer Inc., Dallas, for the Society of Petroleum Engineers, .1981
Vazquez, M., and Beggs, Correlations for Fluid Physical Property Predictions, [Ref. 38]
H. D.: J. Pet. Tech., Page 968 - 970, June 1980
Yielding, G., Freeman, Quantitative Fault Seal Prediction, [Ref. 39]
G., and Needham, B., American Association of Petroleum Geologists Bulletin, Vol. 81, Page 897-917, 1997.
FloGrid User Guide Bibliography 907

908 Bibliography FloGrid User Guide
Index
Appendix N
Binning . . . . . . . . . . 455 Add . . . . . . . . . . . . .349, 353

Numerics 3D Editor . . . . . . . . . . . . 179 Above . . . . . . . . . . 357
All traces . . . . . . . . 369
Structured Gridder . . 312
1 Phase. . . . . . . . . . . . . . 451 Below. . . . . . . . . . . 357
3D Grid. . . . . . . . . . . . . . 660
2 Phase. . . . . . . . . . 453, 589 Components . . . . . . 658
2D Mapping Canvas . 657
Map-assigned traces to view369
2 phase 3D grid contours settings . 665 Non-splitting traces
Binning . . . . . . . . . . 455
3D Viewer Traces
Upscaling Options . . 456
Configuring . . . . . . . 747 Add369
2D Mapping Canvas . . . . 647 Connect cells . . . . . . 161 Pause . . . . . . . . . . . 102
3D Grid. . . . . . 651, 657 Grid editing . . . . . . . 122 Property types . . . . . 141
Axis Property Editing panel654 Grid Editor. . . . . . . . 122 Single cell. . . . . . . . 503
Boundaries . . . . . . . 649 IJ and K Slicing . . . . 225 Splitting traces . . . . 369
Common workflows. 674 IJ slicing . . . . . . . . . 145 Wells . . . . . . . . . . . 539
Contour lines . . . . . . 649 IJK extents . . . . . . . . 146
Drag, drop and dependencies651 Add lateral well . . . . . . . 380
IJK slice... . . . . . . . . 145
Edit menu . . . . . . . . 653 Adjoint upscaler . . . . . . . 894
3D Viewer - overview . . . 107
Fault Traces. . . . . . . 648 Advanced Expression . . . 224
Map . . . . . . . . 651, 657 3D Visualization
Editors . . . . . . . . . . 881
Markers . . . . . . . . . 648 New . . . . . . . . 896, 903
Advanced layering . . . . . 323
Normalize . . . . . . . . 659
Scatter sets . . . . . . . 648 Aerial, vertical unit . . . . . 347
Styles . . . . . . . . . . . 654 Aggregate nodes . . . . . . . 527
Translate . . . . . . . . . 659 A Aggregate triangles . . . . . 527
Tree . . . . . . . . . . . . 649
abs . . . . . . . . . . . . . . . . . 711 Algebraic upscaling . . . . 895
Wells . . . . . . . . . . . 648
Abs Perm Flow Based . . . 489 Algorithms
2D Viewer . . . . . . . . . . . 660
Absolute extrapolation threshold528 lumping . . . . . . . . . 241
3D Grid. . . . . . . . . . 660
population. . . . . . . . 253
Fault Traces Editor. . 673 Absolute permeability, Kx, Ky, Kz428
Layout . . . . . . . . . . 660 Alias . . . . . . . . . . . . . . . 553
acos . . . . . . . . . . . . . . . . 711
Map . . . . . . . . . . . . 660 All Faces . . . . . . . . . . . . 544
Acquifers
Select Time Step . . . 666 Analytical tools
Multi-cell. . . . . . . . . 902
2D Viewer Editors. . . . . . 671 crossplot . . . . . . . . . 293
Active Grid . . . . . . . . . . . 160
3 phase histogram . . . . . . . . 292
FloGrid User Guide Index 909

variogram . . . . . . . . .294 azimuth Deviation . . . . . . . . . 315
AND . . . . . . . . . . . . . . . .713 data for gridding algorithms840 Edit . . . . . . . . . 180, 515
Azimuthal divisions. . . . . 510 Export, PetraGrid . . . 502
Animating Well Events . . .643
Grid. . . . . . . . . . . . . 514
Anisotropic Gridding . . . .769 import, PetraGrid . . . 501
Anisotropic gridding. . . . .769 Major and minor points128
Anisotropy. . . . . . . . . . . .526 B Name. . . . . . . . 180, 312
New . . . . . . . . . . . . 515
antilog10 . . . . . . . . . . . . . 711
Background color . . . . . . 896 Polygon file format . . 502
Aquifer . . . . . . . . . . . . . .540 Projection . . . . . . . . 528
Barefoot Events . . . . . . . 634
Name . . . . . . . . . . . .160 Rectangle file format. 806
Properties . . . . . 161, 541 Binning . . . . . . . . . . . . . 456
Select . . . . . . . 179, 311
2 phase . . . . . . . . . . 455
Areal grid . . . . 318, 320, 331 Type . . . . . . . . 180, 312
3 phase . . . . . . . . . . 455
New . . . . . . . . . 879, 900 Vertical . . . . . . . . . . 328
All other methods . . 455
Areal gridding . . . . . . . . .764 Curves . . . . . . . . . . 456 Boundary list . . . . . . . . . . 180
Arithmetic averaging468, 471, 473 Bivariate statistics plotting 293 Bounday
asin . . . . . . . . . . . . . . . . . 711 Grid. . . . . . . . . . . . . 330
Black Oil
Assign Correlations. . . . . . . 613 Bounding Box
Fault Traces . . . . . . .370 and Freeze . . . . . . . . 135
BLOCK . . . . . . . . . . . . . 543
Maps . . . . . . . . 355, 372 and Rotation. . . . . . . . 95
Block Units . . . . . . . . . . 190 disabling with Grid Thickening158
Traces . . . . . . . . . . .369
Creation . . . . . . . . . 211 Turning on . . . . . . . . 172
Associate Horizons, Constructing758
Family . . . . . . . . . . .141 break . . . . . . . . . . . 705, 708
Blocks . . . . . . . . . . . . . . 190
Traces . . . . . . . . . . .372 breakpoints . . . . . . . . . . . 732
Assignment - new . . 882
atan . . . . . . . . . . . . . . . . . 711 Auto split . . . . . . . . 186 Build . . . . . . . 320, 328, 331
ATTRIBUTE . . . . . . 775, 793 BlockUnitID . . . . . . 542 Block units. . . . . . . . 188
Build units. . . . . . . . 188 Corner point grid . . . 764
Attributes
Color . . . . . . . . . . . 887 Units . . . . . . . . . . . . 183
Contour maps . . . . . .350
Fault splitting limitations213 Upscaling. . . . . . . . . 485
Maps . . . . . . . . 342, 350
Mesh maps . . . . . . . .342 Grid . . . . . . . . . . . . 763 Built in functions . . . . . . . 729
PropBlockUnitID. . . 542 Built-in Functions . . . . . . 711
Auto connect . . . . . . . . . .502
Sampling. . . . . . . . . 759
Auto create splitter trace . .369 Bulk . . . . . . . . . . . . 514, 895
Select . . . . . . . 144, 225
Alignment . . . . . . . . 517
Auto set controls . . . . . . .539 Splitting faults . 176, 209
Boundary . . . . . . . . . 514
Auto split. . . . . . . . . . . . .186 Splitting faults - new 885
Controls. . . . . . . . . . 514
Splitting faults, Limitations213
Autogenerate IJK Fault Location table Create . . . . . . . . . . . 514
Unit horizon . . . . . . 190
418 Grid. . . . . . . . . . . . . 514
Upscaling . . . . . . . . 466
Autonormalize . . . . . . . . .133 Grid Style . . . . . . . . 516
Bottom Names . . . . . . . . . . . 514
Average Dx . . . . . . . . . . .319 3D . . . . . . . . . . . . . 182 Regions . . . . . . . . . . 525
Average Dy . . . . . . . . . . .319 Bottom conforming (offlap)322 Spaced. . . . . . . . . . . 513
Averaging Boundaries BUNIT . . . . . . . . . . . . . . 543
Harmonic, Upscaling469, 471 2D Viewer. . . . . . . . 670
Harmonic-arithmetic .472 Volume of Interest . . 153
Power . . . . . . . 469, 472
Boundaries settings panel. 666
Simple - upscaling. . .471
Boundary . . . . . . . . . . . . 311
C
Axes, configure . . . . . . . .172
Bulk . . . . . . . . . . . . 514 caAutoDirName. . . . . . . . 731
Axes, Flip X . . . . . . . . . .139 Clipping . . . . . . . . . 526
caAutoFileName . . . . . . . 731
Axis Property Editing panel654 Copy. . . . . . . . . . . . 180
Create . . . . . . . . . . . 180 caAutoRun . . . . . . . . . . . 731
Axis template. . . . . . . . . .347
Definition . . . . . . . . 175 Caching, Rotation . . . . . . . 95
910 Index FloGrid User Guide

Calculate visualisation On-line help . . . . . . 735
Displacement. . . . . . 529 configuring . . . . . . . 738 Property Model . . . . 736
Schedule connections 502 colon . . . . . . . . . . . . . . . 717 Property Model . . . . 736
Calculator. . . . . . . . 224, 440 Reservoir Data Store 736
Color
Configuring . . . . . . . 746 Structured Gridder . . 741
Background . . . . . . . 896
Edit . . . . . . . . . . . . 447 Unstructured Gridder 744
Block units. . . . . . . . 887
Reset . . . . . . . . . . . 142 Upgridder . . . . . . . . 741
Control lines. . . . . . . 889
Show . . . . . . . . . . . 142 Upscaler . . . . . . . . . 742
Color Legend
symbols . . . . . . . . . 713 Configuring 3D Viewer . . 747
Editing. . . . . . . . . . . 168
Upscaling . . . . . . . . 447 Connect cells 161, 540 to 541,
Integer properties . . . 168
Calculator symbols . . . . . 713 Object for. . . . . . . . . 171 544 to 545
Capillary equilibrium 454, 481 Real properties . . . . . 169 Connection. . . . . . . . . . . 503
Cascade . . . . . . . . . . . . . . 76 Ternary Display . . . . 170 Direction . . . . . . . . 161
Color legend . . . . . . 896, 903 Permeability limit . . 546
Case Sensitivity . . . . . . . 702
Porosity limit . . . . . 546
Cell . . . . . . . . . . . . . . . . 503 Colors
Hardcopy . . . . . . . . . 139 Connection Factor592, 617 to 618
Add . . . . . . . . . . . . 503
Generation . . . . . . . 527 Command file Constant . . . . . . . . . . . . 331
In I . . . . . . . . . . . . . 517 Replaying . . . . . . . . . 98 Constant Dx . . . . . . . . . . 331
Length . . . . . . 508, 513 Commands . . . . . . . 730, 896 Constant Dy . . . . . . . . . . 331
Probe . . . . . . . . . . . 903 Adding a Pause. . . . . 102 Constant fractional flow454, 481
Size . . . . . . . . 508, 517 Play Commands . . . . 101
Size limits . . . . . . . . 517 Constant Multiplier . . . . . 553
Property names. . . . . 811
Upscaling . . . . . . . . 449 Recording the Current Position102 Constant saturation . .453, 481
Width . . . . . . . . . . . 513 Constants . . . . . . . . . . . . 730
Comments. . . . . . . . 448, 702
Cell Connection Factors. . 618 Constrain Drag . . . . . . . . 639
Common Editor commands
Calculation . . . 592, 617
2D Viewer . . . . . . . . 671 Constructing
Cell Display . . . . . . . . . . 158 Block Unit Horizons 758
Common features
Outline Control . . . . . 96 Horizons. . . . . . . . . 757
Expression Calculator 688
Cell display Micro grid. . . . . . . . 464
Common problems. . . . . . 732
Configuring . . . . . . . 753 Units . . . . . . . . . . . 757
Common Workflows
Cell Face Display . . . . . . 159 Contact Sets . . . . . . .571, 579
2D Mapping Canvas . 674
Cell Probe . . . . . . . . . . . 147 Contact sets
COMPDAT Keywords
Cells Defining . . . . . . . . . 581
Export, PetraGrid . . . 810
Automatic selection . 538 Displaying . . . . . . . 582
COMPDAT keywords Using . . . . . . . . . . . 583
Connect 161, 540 to 541,
Calculate connections 502
544 to 545 ContactRegion property. . 580
Edit . . . . . . . . . . . . 529 Compilation . . . . . . . . . . 704
Continuation Character . . 702
Grid . . . . . . . . . . . . 883 Components
Contour Display Controls 663
Grid, Editor . . . . . . . 882 Add . . . . . . . . . . . . . 658
In J . . . . . . . . . . . . . 517 Layout . . . . . . . 658, 850 Contour lines
inside-out . . . . . . . . 467 Remove . . . . . . . . . . 658 2D Viewer . . . . . . . 669
Center of Rotation . . . . . . 134 Composite 1-D solutions . 472 Contour lines editor
2D Viewer . . . . . . . 672
Chears . . . . . . . . . . . . . . 799 Composite units . . . . . . . . 717
Input format . . . . . . 799 Contour map
Configure
Attributes . . . . . . . . 350
Clipping boundary. . . . . . 526 Graph . . . . . . . . . . . 290
Formats . . . . . . . . . 350
close . . . . . . . . . . . . . . . 705 Configuring Visualization . . .350, 780
Coarse BUG . . . . . . . . . . 489 Calculator . . . . . . . . 746
Contour Maps
Layout . . . . . . . . . . . 746
Coarse grid . . . . . . . . . . . 807 Create. . . . . . . . . . . 663
Main Viewer . . . . . . 747
Coarsening for property model On-line Help . . . . . . 735 Contour maps

Node options . . . . . .352 Block units . . . . . . . 211 Model - New . . . . . . 900
Contour value dialog. . . . .666 Bulk . . . . . . . . . . . . 514 Points . . . . . . . . . . . 127
Family . . . . . . . . . . 141 Property model . . . . . 217
Contours settings . . . . . . .665
Fault traces . . . . . . . 211 Structured model . . . 177
Control file format . . . . . .774 Mesh surfaces . . . . . 758 Structured model - New899
Control line Model . . . . . . . . . . . 177 Delete - New . . . . . . . . . . 879
Gridding. . . . . . . . . .900 Properties . . . . . . . . 223
Derived Multiplier . . . . . . 553
Import and export . . .880 Property Model . . . . 217
List . . . . . . . . . . . . .317 Property type . . . . . . 141 Derived quantities - New . 896
New . . . . . . . . . . . . .893 Property type family140 to 141 Deviate grid. . . . . . . . . . . 526
Table . . . . . . . . . . . .315 Property Types. . . . . 437 Deviation refinement . . . . 528
Control Lines Surface . . . . . . . . . . 345
Diagnostics . . . . . . . . . . . 461
Select . . . . . . . . . . . .889 Trace/polygon . . . . . 369
Traces . . . . . . . . . . . 369 Diagnostics - new . . . . . . 898
Control lines
Unit . . . . . . . . . . . . 176 Digitize. . . . .126 to 128, 530
Color coded . . . . . . .889
Create Contour Map . . . . 663 3D Viewer . . . . 126, 128
Control section keywords .774 3D viewer . . . . . . . . 128
Create Fault Trace . . . . . . 663
Control Surfaces Delete points . . . . . . 127
Coloration . . . . . . . .316 Create Scatter Set . . . . . . 663 Main viewer . .126 to 127
Controls Create traces . . . . . . . . . . 211 Major points. . . . . . . 126
Auto set . . . . . . . . . .539 Cross Section Minor points. . . . . . . 126
Bulk. . . . . . . . . . . . .514 Grid . . . . . . . . . . . . 526 New points. . . . . . . . 126
Using multiple pick points128
Convert Cross section . . . . . . . . . 521
Sim grid . . . . . . . . . .491 End points . . . . . . . . 521 Digitize - 3D Viewer . . . . 637
Structured grid . . . . .806 Position. . . . . . . . . . 521 Digitize Grid . . . . . . . . . . 332
Coordinate Crossplot . . . . . . . . . . . . 293 dimensional consistency . . 718
Lines . . . . . . . . 328, 762 cubic . . . . . . . . . . . . . . . 714 Directional output . . . . . . 457
Tubes . . . . . . . . . . . .762
Curves Directions . . . . . . . . . . . . 417
Coordinate system . . 181, 313 Binning. . . . . . . . . . 456 Displacement calculation . 529
Change349, 353, 371, 380
Display
Coordinates . . . . . . . 181, 313
Maps . . . . . . . . . . . . 356
Copy- New . . . . . . . . . . .879
Copying vectors . . . . . . . .719
D Model . . . . . . . . . . . 178
Property. . . . . . . . . . 146
Corner point grid Damage Skin . . . . . . . . . 617 Shale breaks . . . . . . . 883
Build . . . . . . . . . . . .764 Data Displaying
Corner point gridding . . . . 311 Input threshold. . . . . 238 Well Tracks . . . . . . . 376
Corner point gridding - Overview20 Data format keywords . . . 774 Domains . . . . . . . . . . . . . 449
Grid. . . . . . . . . . . . . 527
Corner point grids. . . . . . .762 Data location keywords . . 776
IJK numbering . . . . . 531
cos . . . . . . . . . . . . . . . . . 711 Data Model. . . . . . . . . . . 190
Dual Porosity. . . . . . . . . . 806
cosh . . . . . . . . . . . . . . . . 711 Data plotting tools
Dual porosity. . . . . . . . . . 897
CPS . . . . . . . . 365, 785, 789 crossplot . . . . . . . . . 293
variogram . . . . . . . . 294 Dual porosity - New . . . . . 895
Export traces. . . . . . .372
Fault traces export . . .885 Debugging . . . . . . . . . . . 732 Dual source model - New . 894
CPS1 Decimation level display Dual system. . . . . . . . . . . 546

Save. . . . . 343, 367, 781 Configuring . . . . . . . 752 Dx . . . . . . . . . . . . . . . . . 331
CPS3 DEG . . . . . . . . . . . . . . . 710 Average . . . . . . . . . . 319
Save. . . . . . . . . . . . .367 Delete Dy
SVS . . . . . . . . . 343, 781 LGR . . . . . . . . 411, 537 Average . . . . . . . . . . 319
Create Line . . . . . . . . . . . . 332 Constant . . . . . . . . . 331

ENDPOINT MARKER . . 792 External Faces . . . . . . . . 544
E endproc. . . . . . . . .705 to 706 External model . . . . . . . . 220
endwhile . . . . . . . . . 705, 708 External properties . . . . . 221
ECLIPSE
Output . . . . . . . . . . 895 EPSILON . . . . . . . . . . . . 710 extrapolation
PetraGrid . . . . . . . . 807 Equilibrium results, gridding algorithms840,
Upscaling . . . . . . . . 430 Capillary . . . . . 454, 481 843
Edit erf . . . . . . . . . . . . . . . . . 711 Extrapolation Threshold . 528

Active Grid erfc. . . . . . . . . . . . . . . . . 711 EXTREPGL keyword . . . 889
Grid
Error
Edit122 MPFA ortho limit . . . 547
Boundaries . . . . . . . 515
Boundary . . . . . . . . 180
Events. . . . . . . . . . . . . . . 633 F
Barefoot. . . . . . . . . . 634
Calculator . . . . . . . . 447
Name. . . . . . . . . . . . 633 Face multipliers . . . . . . . 894
Calculator script. . . . 447
Perforations Events . . 634 Face-based simulation grid properties
Cell Centers. . . . . . . 529
Color Legend. . . . . . 168 Executing Realizations . . . 628 882
Color Map. . . 168 to 169 EXP . . . . . . . . . . . . . . . . 710 Faces . . . . . . . . . . . . . . . 544
Direction . . . . . . . . . 491 exp . . . . . . . . . . . . . . . . . 711 factorial . . . . . . . . . . . . . .711
Expression . . . . . . . 447
Experimental variogram . . 302 FALSE . . . . . . . . . . . . . 710
Properties . . . . 540, 544
Scope . . . 448, 452, 457 expn . . . . . . . . . . . . . . . . 711 Family
Titles . . . . . . . . . . . 171 Associate . . . . . . . . 141
Export
Traces . . . . . . . . . . . 115 Create. . . . . . . . . . . 141
boundaries, PetraGrid 502
Type . . . . . . . . . . . . 491 Names . . . . . . . . . . 141
COMPDAT keywords, PetraGrid
Wellpath . . . . . . . . . 637 810 Property Types140 to 141
Control line . . . . . . . 880 Property types . . . . . 141
Edit Keywords
EDIT Keywords, PetraGrid808 Select . . . . . . 141 to 142
Export, PetraGrid . . . 808
EGRID . . . . . . . . . . 888 Fault
Edit Menu . . . . . . . . . . . 112
Grid geometry, PetraGrid808 Locations - new. . . . 901
Editor GRID Keywords, PetraGrid808 Fault framework editor . . 191
3D Viewer. . . . . . . . 122 GRID/EDIT Keywords, PetraGrid
Advanced Expression 881 Fault Permeability. . . . . . 564
808
Fault Framework . . . 191 IJK Faults . . . . . . . . 771 Fault Property Calculator. 551
Grid cell center . . . . 882 Properties. . . . . . . . . 220 Derived Multiplier . . 561
Property . . . . . . . . . 881 Regions . . . . . . . . . . 502 Fault Export . . . . . . 567
Property model . . . . 223 Schedule connections 810 Faults . . . . . . . . . . . 560
Simulation property . 881 Traces as CPS. . . . . . 372 Permeability . . . . . . 556
Editor defaults Traces in CPS. . . . . . 885 Shale . . . . . . . . . . . 555
configuring . . . . . . . 755 Trajectory, PetraGrid. 810 Thickness . . . . . . . . 555
Upscaling. . . . . . . . . 430 Transmissibility. . . . 557
Editors
VRML. . . . . . . . . . . 903 workflow . . . . . . . . 559
2D Viewer. . . . . . . . 671
Well deviation surveys636 Fault Property Calculator - technical
EGRID background . . . 559
Well Events . . . . . . . 636
Export - new . . . . . . 888
Well keywords . . . . . 810 Fault Thickness . . . . . . . 562
File support . . . . . . . 890
Well trajectory . . . . . 810
Fault Traces
ei . . . . . . . . . . . . . . . . . . 711 Wells . . . . . . . . . . . . 639
Create. . . . . . . . . . . 663
Elliptic . . . . . . . . . . . . . . 516 Expression . . . . . . . . . . . 224 Sampling of . . . . . . .211
Background cells - new889
Expression Calculator. . . . 687 Fault traces
Well . . . . . . . . . . . . 516
Common Features. . . 688 2D Viewer . . . . . . . 670
else . . . . . . . . . . . . . . . . 705
Expression Calculator language695 Fault traces editor
endfunc . . . . . . . . 705 to 706 2D Viewer . . . . . . . 673
Expressions . . . . . . . 439, 695
endif . . . . . . . . . . . . . . . 705

Fault traces settings panel .666 File function example . . . . . . . 706
Faults . . . . . . . . . . . 211, 431 EGRID . . . . . . . . . . 890 Function reference . . . . . . 697
Alias . . . . . . . . . . . .553 Import, Export and Status430
Functions . . . . . . . . 702, 706
Analysis . . . . . . . . . .210 File Formats
FVF . . . . . . . . . . . . . . . . 504
Analysis and ordering 210 Chears . . . . . . . . . . 799
Assign Traces . . . . . .370 GeoLith . . . . . . . . . 799
Autogenerate . . . . . .418 Fill Pattern Match . . . . . . 691
Block recursive volume splitting
210
Fill Series . . . . . . . . . . . . 691 G
Block splitting . 176, 209 Floating point variables . . 703
GAMMA . . . . . . . . . . . . 710
Block splitting - new .885 Floating point vector . . . . 703
gamma . . . . . . . . . . . . . . 711
Block splitting limitations213 FloGrid License Features . 756
Block splitting, Limitations213 Generate
Flow Based. . . . . . . . . . . 489 Face angle, PetraGrid 543
Constant Multiplier . .553
Controls, PetraGrid . .512 Flow based upgridding . . 494 Grid. . . . . . . . . . . . . 525
Derived Multiplier. . .553 Flux . . . . . . . . . . . . 547, 902 Grid, PetraGrid. . . . . 525
Digitize . . . . . . . . . .637 Integer, PetraGrid . . . 542
Formation volume factor . 504
digitize . . . . . 126 to 128 Properties, PetraGrid. 542
Formats Property model . . . . . 224
Editor - new . . . . . . .881
Chears, Geolith . . . . 799 Real, PetraGrid. . . . . 542
Ends . . . . . . . . . . . .320
Contour maps . . . . . 350 Well connections - new895
Export . . . . . . . 558, 771
Control file . . . . . . . 774
Faults Property Calculator553 Generic (AVS) . . . . . . . . . 430
GRID . . . . . . . . . . . 377
Grid . . . . . . . . . . . . .512 Geolith . . . . . . . . .798 to 799
Images . . . . . . . . . . 897
Grid Style. . . . . . . . .513 Data file structure . . . 799
Import maps . . . . . . 376
High density fault trace performance Input format . . . . . . . 799
880 Keywords . . . . . . . . 774
ID number . . . . . . . .784 Maps . . . . . . . 342, 350 Geometric
IJK fault export . . . . .880 Mesh maps . . . . . . . 342 Averaging468 to 469, 471
Importing traces . . . .366 Polygons . . . . . . . . . 502 PetraGrid . . . . . . . . . 508
Markers . . . . . . . . . .784 Property Model . . . . 773 Upscalers . . . . . . . . . 467
Names . . . . . . . . . . .784 RESCUE. . . . . . . . . 798 Geometry . . . . . . . . . . . . 431
New . . . . . . . . . . . . .885 Well logs. . . . . . . . . 386
Geomodel Property Cache
Options . . . . . . . . . .368 fractional dimensions. . . . 733 Configuring . . . . . . . 736
Ordering of. . . . . . . .210 Fractional flow Global Nx/Ny . . . . . . . . . 318
Re-order . . . . . . . . . .188 Constant . . . . . 454, 481
Select for Splitting. . .186 global variables . . . . . . . . 732
Fracture
set major/minor. . . . .128 Graph
Bottom . . . . . . . . . . 510
Sloping . . . . . . . . . .900 Configure. . . . . . . . . 290
Controls . . . . . . . . . 510
Styles . . . . . . . . . . . .553 Graphics Options . . . . . . . . 94
Half length . . . . . . . 510
Surfaces . . . . 365 to 366
Permeability . . . . . . 511 GRID
Swap Up . . . . . . . . . 116
Porosity . . . . . . . . . 511 Well import format377, 386
Trace display . . . . . .367
Top . . . . . . . . . . . . . 510 Grid
Trace export in CPS. .885
Width . . . . . . . . . . . 510 Algebraic domains . . 527
Trace formats . . . . . .365
Trace options . . 368, 370 Fracture orientation . . . . . 510 Area . . . . . . . . 879, 900
Traces import . . . . . .365 Framework Areal 318, 320, 331, 900
Vertical zigzag . . . . .882 Select . . . . . . . . . . . 144 Blocks . . . . . . . . . . . 763
XY pairs. . . . . . . . . .785 Boundary . . . . . 330, 514
Freeze . . . . . . . . . . . . . . 135
Zigzag . . . . . . . 526, 887 Build . . . . . . . . . . . . 764
FrontSim Bulk . . . . . . . . . . . . 514
Zigzag - new. . . . . . .879
Realizations. . . . . . . 629 Cell distortion. . . . . . 883
Faults Property Calculator
Full 3-D solutions . . . . . . 473 Cell-center editor . . . 882
Alias . . . . . . . . . . . .553
func . . . . . . . . . . . . . . . . 705 Coarse . . . . . . . . . . . 807
Faults . . . . . . . . . . . .553
Constructing. . . . . . . 464
function arguments . . . . . 706

Convert . . . . . . . . . . 491 Parameters . . . . . . . . 319 IJK directions . . . . . . . . . 517
Corner Point . . . . . . 762 Rectangular 20, 193, 330 IJK Faults
Corner point . . . . . . 769 Vertical . . 767, 893, 895 Export . . . . . . . . . . 771
Cross section . . . . . . 526 Vertical - new . . . . . . 892
IJK numbering, PetraGrid 531
Deviation . . . . 526, 528 Gridding Controls . . . . . . 313
Deviation refinement 528 IJK Slicer. . . . . . . . . . . . 150
Grids
Diagnostics . . . . . . . 429 Image formats . . . . . . . . 897
Interpolation
Digitize . . . . . . . . . . 332 Image output defaults
Anisotropic . . . . . . . . . . . 769
Dimensions . . . . . . . 330 configuring . . . . . . . 755
Editor . . . . . . . . . . . 880 Gross thickness section. . . 800
Image, Save As... . . . . . . 854
Export. . . . . . . . . . . 808
Fault . . . . . . . . . . . . 512 Import . . . . . . . . . 344 to 345
Fine . . . . . . . . . . . . 807 Boundary, PetraGrid 501
Generate . . . . . 525, 542 H Control line. . . . . . . 880
Geometries . . . . . . . 901 Controls . . . . . .344, 346
Half grid block upscaling . 894 Fault traces . . 365 to 366
Isotropic . . . . . . . . . 769
Location . . . . . . . . . 330 Hardcopy Colors . . . . . . . 139 GRID well format . . 377
Properties . . . . . . . . 451 Hardcopy options. . . . . . . 883 Map formats . . . . . . 376
Refinement, PetraGrid517 Map parameters.344, 346
Hardware Renderer . . . . . . 94
Rotate . . . . . . . . . . . 331 Mesh maps . . 344 to 345
Harmonic averaging . 469, 471 points, PetraGrid . . . 502
Simulation. . . . . . . . 491
Smoothness . . . . . . . 769 Harmonic-arithmetic averaging472 Properties, PetraGrid 806
Spacing . . . . . . . . . . 330 Help Results, FloGrid . . . 430
Style . . . . 505, 513, 516 Configuring . . . . . . . 735 Results, PetraGrid . . 806
Style, bulk . . . . . . . . 516 Well Events. . . . . . . 633
Histogram . . . . . . . . . . . . 292
Style, faults . . . . . . . 513 Well formats . . . . . . 376
Horizons . . . . . . . . . . . . . 190 Well logs . . . . . . . . 386
Style, wells . . . . . . . 505
Constructing. . . . . . . 757
Translate . . . . . . . . . 331 Impossible Realizations. . 627
Nonconformity rules . 758
Type, PetraGrid 525, 537 Inactive Cells . . . . . . . . . 159
Well s . . . . . . . . . . . 504 Horizontal wells
Projection . . . . . . . . 528 include. . . . . . . . . . .705, 708
Grid Convert. . . . . . . . . . 806
Horz Increment. . . . . . . . . . . . 226
Grid display
(bulk spaced) . . . . . . 506 Indicator Classes Selector 239
Configuring . . . . . . . 752
(fixed spaced). . . . . . 506 indicator classifications
Grid Keywords 2D/3D (fixed spaced) 507 selective population . 272
Export, PetraGrid . . . 808 algebraic (bulk spaced)506
Initialization method . . . . 532
Grid Lines . . . . . . . . . . . 173 algebraic (fixed spaced)507
fractured (bulk spaced)507 Inner radius . . . . . . . . . . 509
Grid Statistics . . . . . . . . . 167
fractured (fixed spaced)507 Input and output - example 707
GRID/EDIT sections . . . . 808
Host cells . . . . . . . . . . . . 538 Insert
Grid/Match host cell . . . . 431
Horizon definitions . 759
Grid/Set location . . . . . . . 431 I Line . . . . . . . . . . . 331
Gridded property editor features694 J Line . . . . . . . . . . . 332
Gridder I Instance Numbers . . . . . . . 76
Configuring . . . . . . . 744 int . . . . . . . . . . . . . . . . . .711
i0 . . . . . . . . . . . . . . . . . . 711
Gridding. . . . . . . . . . . . . 537 Integer properties upscale method549
i0e . . . . . . . . . . . . . . . . . 711
Anisotropic . . . . . . . 769
i1 . . . . . . . . . . . . . . . . . . 711 interpolation
Areal . . . . . . . . . . . 764
results, gridding algorithms840
Control line . . . . . . . 900 i1e . . . . . . . . . . . . . . . . . 711
Corner point . . . 20, 311 Inverse threshold input data238
if . . . . . . . . . . . . . . . . . . 705
Isotropic . . . . . . . . . 769 inverse units . . . . . . . . . . 717
igamma. . . . . . . . . . . . . . 711
Method . . . . . . 320, 330 IRAP . . . . 344, 782, 786, 790
Order . . . . . . . . . . . 524 igammac . . . . . . . . . . . . . 711
Iso Cell Selection . . . . . . 154

Isotropic Gridding . . . . . .769 Enable . . . . . . . . . . 537 Add . . . . . . . . . . . . . 369
Isotropic gridding . . . . . . .769 Enable all . . . . . . . . 537 Assign Surfaces 355, 372
Gridding . . . . . . . . . 893 Assign Traces. . . . . . 369
Index . . . . . . . . . . . 537 Attributes. . . . . 342, 350
Location . . . . . . . . . 409 Contours . . . . . . . . . 350
J Names . . . . . . 408, 537
New . . . . . . . . 537, 879
Display . . . . . . . . . . 356
Display / datum plane 356
j0 . . . . . . . . . . . . . . . . . . 711 Refinements . . . . . . 410 Formats . . . . . . 342, 350
j1 . . . . . . . . . . . . . . . . . . 711 Save . . . . . . . . . . . . 411 Import . . . . . . . 344, 346
Select domain . . . . . 408 Import formats . . . . . 376
JPEG, format . . . . 854 to 855
Lights . . . . . . . . . . . . . . 136 Mesh map attributes . 342
Mesh map formats . . 342
Limitations
Mesh map import344 to 345
Fault Block Splitting 213
K Fault block splitting algorithm213
Mesh map node options348, 352
Mesh map operations757, 813
Linear . . . . . . . . . . . . . . 555 Mesh map types . . . . 342
K Layer
Select . . . . . . . . . . . .666 Linear thickness-displacement relation Null value . . . . . . . . 346
555 Options . . . . . . . . . . 353
k0 . . . . . . . . . . . . . . . . . . 711
Lithology dependent . . . . 555 Property. . . . . . 228, 343
k0e . . . . . . . . . . . . . . . . . 711 Scatter Sets . . . . . . . 353
LN10 . . . . . . . . . . . . . . . 710
k1 . . . . . . . . . . . . . . . . . . 711 Surface . . . . . . . . . . 342
LN2 . . . . . . . . . . . . . . . . 710 . . . . . . . . . . . . . . . . . . . 342
k1e . . . . . . . . . . . . . . . . . 711
Location Surfaces. . . . . . . . . . 356
Keyword Editor . . . . . . . .418
Keywords . . . . . . . . 776 Thickness. . . . . 343, 346
Keywords . . . . 635, 705, 729 Types. . . . 342, 350, 780
log . . . . . . . . . . . . . . . . . 711
COMPDAT . . . . . . .502
log10 . . . . . . . . . . . . . . . 711 Marker flattening . . . . . . . 683
Control section . . . . .774
Data format . . . . . . .774 LOG10E . . . . . . . . . . . . 710 Markers
Data location . . . . . .776 Creating. . . . . . . . . . 683
LOG2E . . . . . . . . . . . . . 710
Export, PetraGrid808, 810 editing . . . . . . . . . . . 684
Logarithmic thickness-displacement Endpoint . . . . . . . . . 792
MULTREGT. . . . . . .417 relation . . . . . . 555
New . . . . . . . . . . . . .889 Max
Lump tab
Kh . . . . . . . . . . . . . . . . .592 Upscaling. . . . . . . . . 447
algorithms . . . . . . . . 241
Kx . . . . . . . . . . . . . . . . .428 Measurement quantities . . 570
Lumping data
Ky . . . . . . . . . . . . . . . . .428 algorithms . . . . . . . . 241 Memory
Requirements . . . . . . 880
Kz. . . . . . . . . . . . . . . . . .428
Usage . . . . . . . . . . . 883
Usage - Save and Restore98
M MenuPick . . . . . . . . . . . . 731
L Main Viewer
Mesh Map . . . . . . . . . . . . 357
Interpolate . . . . . . . . 665
Language Definition . . . . .702 Configuring . . . . . . . 747
New . . . . . . . . . . . . 896 Mesh map editor features . 694
Layer
Majority vote . . . . . 453, 455 Mesh maps . .342, 344 to 345
Type. . . . . . . . . . . . .321
Attributes. . . . . . . . . 342
Layering Manual connect... . . . . . . 503
Formats . . . . . . . . . . 342
Advanced . . . . . . . . .323 Manual fault block splitting212 Node options . . . . . . 348
Layout Map . . . . . . . . . . . . . . . . 660 Operations . . . . 757, 813
Components . . . 658, 850 2D Mapping Canvas. 657 Types. . . . . . . . . . . . 342
Configuring . . . . . . .746 Map Axes. . . . . . . . . . . . 172 Mesh surfaces
LGR . . . . . . . . . . . . 408, 536 Map contours settings . . . 665 Create . . . . . . . . . . . 758
3D- New . . . . . . . . .902 Micro grid . . . . . . . . . . . . 466
Maps . . . . . . . 183, 341, 357
Delete . . . . . . . 411, 537 Constructing. . . . . . . 464
2D Viewer. . . . . . . . 669

Microgrids . . . . . . . . . . . 888 Name Events . . . . . . . . . . 633 Property version . . . 446
Min Names Scatter Sets . . . . . . . 353
Upscaling . . . . . . . . 447 Bulk . . . . . . . . . . . . 514 Upscaling . . . . . . . . 456
Min sat separation Configuring . . . . . . . 744 OR . . . . . . . . . . . . . . . . 713

Upscaling . . . . . . . . 457 Family . . . . . . . . . . . 141 Orientation. . . . . . . . . . . .511
Faults . . . . . . . . . . . 784
Minimize Children . . . . . . 76 Orthogonality . . . . . .320, 769
LGR . . . . . . . . 408, 537
Minimum Upscaling . . . . . . . . 468
Property. . . . . . . . . . 447
PetraGrid . . . . . . . . 509 Property Type. . . . . . 141 Outer radius . . . . . . . . . . 509
Minimum pore volume Never ending while loops . 732 Output format. . . . . . . . . 430
PetraGrid . . . . . . . . 545 Output tab . . . . . . . . . . . 268
NNC . . . . . . . . . . . . 423, 425
Model OUTPUT.PRT . . . . . . . . 706
NNCs . . . . . . . . . . . 417, 421
Create . . . . . . . 177, 217
Data . . . . . . . . . . . . 190 Nodes
Delete177, 217, 899 to 900 Contour maps . . . . . . 352
Display . . . . . . . . . . 178
External . . . . . . . . . 220
Finder . . . . . . . . . . . 885
Mesh maps. . . . . . . . 348
P
Null. . . . . . . . . . . . . 759 Pause
Model status . . . . . . . . . . 178
PEBI . . . . . . . . . . . . 528 Add . . . . . . . . . . . . 102
Mouse Scatter Sets . . . . . . . 353
Actions - new . . . . . 897 Peaceman Radius . . . . . . 618
Normalize . . . . . . . . . . . . 133
Mouse Buttons . . . . . . . . . 95 Peaceman’s Formula . . . . 617
NOT . . . . . . . . . . . . . . . . 713
Move PEBI
Null value . . . . . . . . . . . . 346 3D gridding -New . . 902
3D Viewer. . . 127 to 128
Map import parameter346 Aggregate nodes
Down . . . . . . . . . . . 184
Set null interpretation349, 353 Nodes
Line . . . . . . . . . . . . 332
Main Viewer . . . . . . 127 Nx . . . . . . . . . . . . . . . . . 330 PEBI527
Up . . . . . . . . . . . . . 184 Nx’s . . . . . . . . . . . . . . . . 319 Node aggregation tolerance528
MPFA ortho error limit . . 547 Ny . . . . . . . . . . . . . . . . . 330 Permeability directions547
Multi-Apply Calculator . . 690 Ny’s . . . . . . . . . . . . . . . . 319 Perforations . . . . . . . . . . 634

Events . . . . . . . . . . 634
Multilevel upscaling . . . . 459
Permeability. . . . . . . . . . 428
Multiphase and hierarchical upscaling
Connection . . . . . . . 546
897, 903
Multiple Realizations. . . . 623
O Fracture . . . . . . . . . .511
Upscale method. . . . 549
FrontSim simulations 629 Object Appearance. . 132, 171 Upscaling .454, 470, 479
Volumetrics . . . . . . . 624 Object Rotation . . . . . . . . 136 PermZ . . . . . . . . . . . . . . 489
Multiple Realizations - Overview25 Offlap . . . . . . . . . . . . . . . 322 Perspective. . . . . . . . . . . 134
Multi-point flux . . . . . . . 547 ONE_DIV_PI . . . . . . . . . 710 PetraGrid . . . . . . . . . . . . 808
Multi-point flux - new . . . 902 ONE_DIV_SQRT2 . . . . . 710 Fault controls . . . . . 512
MultNum ONE_DIV_SQRTPI . . . . . 710 MultNum . . . . . . . . 543
PetraGrid . . . . . . . . 543 Unstructured/structured806
Onlap . . . . . . . . . . . . . . . 322
MULTREGT. . . . . . 418, 431 PHI . . . . . . . . . . . . . . . . 710
OpenSGM 5.0 . . . . . . . . . 892
MULTREGT keyword . . . 417 PI . . . . . . . . . . . . . . . . . 710
Operators . . . . . . . . 713, 729
PI_DIV_2 . . . . . . . . . . . 710
Options
Contour map nodes . . 352 PI_DIV_4 . . . . . . . . . . . 710
N Fault Traces . . . 368, 370 Pick Items

Select . . . . . . . . . . . 128
Faults . . . . . . . . . . . 368
Name Hardcopy . . . . . . . . . 883 Pick points
Boundary . . . . 180, 312 Mesh map nodes. . . . 348 3D Viewer . . . . . . . 128
Name conflicts . . . . . . . . 732 PetraGrid . . . . . . . . . 525 Digitize . . . . . . . . . 128

Set major points . . . .129 proc . . . . . . . . . . . . . . . . 705 Validation . . . . . . . . 902
Picking mode . . . . . . . . . .133 Procedures . . . . . . . 702, 706 Version . . . . . . . . . . 901
Version options. . . . . 446
Picture Exaggeration. . . . .137 Production History . . . . . 633
First . . . . . . . . . . . . 633 Property Editor
PINCH keyword arguments425
Properties. . . . . . . . . 436
Pinchout criteria . . . . . . . .423 PROFILE.CAL . . . . . . . . 731
Property Model215, 218, 229, 886
Pinch-out thickness limit . .545 Projection Plane . . . 180, 312
Configuring . . . . . . . 736
Plane . . . . . . . . . . . . . . . .368 PROPBLOCK . . . . . . . . 543 Create . . . . . . . . . . . 217
Plane Slicer . . . . . . . . . . .156 PROPBUNIT . . . . . . . . . 543 Input Formats . . . . . . 773
Properties probe . . . . . . . . . . . . 892
Play Commands . . . . . . . .101
Acquifer . . . . . . . . . 541 Property editor . . . . . 223
Play commands . . . . . . . .532
Cell Probe . . . . . . . . 147 Property model
Plotting tools Create . . 140 to 141, 223 Generate . . . . . . . . . 224
crossplot. . . . . . . . . .293 Defining . . . . . . . . . 223 Property Model - New . . . 891
histogram . . . . . . . . .292 Display . . . . . . . . . . 146
variogram . . . . . . . . .294 Property Population Manager
Generate, PetraGrid . 542
Output tab . . . . . . . . 268
PM properties Property Editor . . . . 436
thresholding input values238
Upscaling . . . . . . . . .451 Simulation - new . . . 882
Thresholding . . . . . . 148 Property Statistics . . . . . . 166
Points
Merge . . . . . . . . . . .530 Types . . . . . . . . . . . 437 Proportional . . . . . . . . . . 322
Property Bottom Anchored . . . 125
Polygon
Display . . . . . . . . . . 146 Top Anchored. . . . . . 125
Create . . . . . . . . . . .369
Edit . . . . . . . . 540, 544 PROPUNIT. . . . . . . . . . . 543
Polygons
Edit history . . . . . . . 894 Pseudo-variables . . . . . . . 694
Digitize . . . . . . . . . .637
Edit records . . . . . . . 447
digitize . . . . . 126 to 128
Editor . . . . . . . . . . . 223
File format . . . . . . . .502
Editor tree . . . . . . . . 435
set major/minor. . . . .128
Pore volume property . . . .423
Export. . . . . . . . . . . 220
External . . . . . . . . . 221
Q
Porosity . . . . . . . . . . 428, 512 External model . . . . 220 quad . . . . . . . . . . . . . . . . 714
Connection . . . . . . . .546 External property types221
Fracture . . . . . . . . . . 511 Family types . . . . . . 141
Upscale method . . . .549 Grid . . . . . . . . . . . . 451
Upscaling . . . . . . . . .470 Import, FloGrid . . . . 430 R
Possible Realizations . . . .627 Import, PetraGrid. . . 806
Information . . 446 to 447 Radial . . . . . . . . . . . . . . . 516
PostScript . . . . . . . . . . . .853 Divisions . . . . . . . . . 509
Maps . . . . . . . 228, 343
Hardcopy . . . . . . . . .903 Style . . . . . . . . . . . . 508
Names . . . . . . . . . . 447
Postscript. . . . . . . . . . . . .853 Replay facilities . . . . 894 Wells . . . . . . . . 516, 894
PostScript output files defaults Sampling. . . . . . . . . 464 Radial well controls . . . . . 890
configuring . . . . . . . .754 Scenario223, 229, 433, 886 radians . . . . . . . . . . . . . . 712
Power averaging Select . . . . . . . 146, 225
Radius . . . . . . . . . . . . . . 509
Upscaling . . . . . 469, 472 Select types . . . . . . . 142
Inner . . . . . . . . . . . . 509
Simulation. . . . . . . . 897
Power upscaling . . . . . . . .901 Outer . . . . . . . . . . . . 509
Simulation Property editor896
presval . . . . . . . . . . . . . .714 Wells . . . . . . . . . . . . 508
Simulation property editors881
print . . . . . . . . . . 705 to 706 Supported . . . . . . . . 801 rand . . . . . . . . . . . . . . . . 711
Print Setup. . . . . . . . . . . .109 Threshold . . . . . . . . 449 raw . . . . . . . . . . . . . 714, 718

Type, information. . . 446 read . . . . . . . . . . .705 to 706
Printing Expressions . . . . .733
Type, mapping files . 219
printnr . . . . . . . . . 705 to 706 Reading from file. . . . . . . 706
Type, name . . . . . . . 141
Probability Types to add . . . . . . 141 Realizations. . . . . .627 to 628
Upscaling . . . . . 461, 484 Upscaling429, 451, 468, 893, 901 FrontSim . . . . . . . . . 629

Realizations Dialog (Simulation)630 Rotation Scatter value dialog. . . . . 667
Realizations Dialog (Volumetrics)625 Angle . . . . . . . . . . . 330 Scatters settings panel . . . 665
Recording Position . . . . . 102 Rotation Caching . . . . . . . . 95 Scenarios . . . . . . . . .222, 890
Rectangular gridding20, 193, 330 Rotation Controls Select . . . . . . . . . . . 225
setting Mouse Button functions95 Schedule
Recursive volume splitting 210
Style . . . . . . . . . . . . . 94 Calculate connections 502
REFDEPTH . . . . . . . . . . 793
Rotation, Object. . . . . . . . 136 Export connections, PetraGrid810
Reference coordinate system181, 313
Rubber Band Zoom . . . . . 135 Scope
Refinement Upscaling .448, 452, 457
Rubberband zoom . . . . . . 883
LGR . . . . . . . . . . . . 410
Run Differencing . . . . . . . 444 Seek to point . . . . . . . . . 134
PetraGrid . . . . . . . . 517
Run time errors . . . . . . . . 704 Segmented coordinate lines902
Refresh View . . . . . . . . . 138
RUNSPEC . . . . . . . . . . . 808 Select
Region multipliers. . . . . . 418
3D Viewer . . . . . . . 128
Regions . . . . . . . . . . . . . 895 Blocks . . . . . . .144, 225
Bulk . . . . . . . . . . . . 525 Boundary . . . . . 179, 311
Export. . . . . . . . . . .
Multipliers . . . . . . .
502
418
S Control lines . . . . . . 889
Domain for LGR . . . 408
Section . . . . . . . . . . 809 Sample Families . . . . 141 to 142
Upscaling . . . . . . . . 893 Block boundaries . . . 759 Faults for splitting . . 186
Relational operator reference697 Properties. . . . . . . . . 464 Main Viewer . . . . . . 127
Relative extrapolation threshold528 Surfaces from the RESCUE wire- Pick items - 3D Viewer128
frame . . . . 881 Pick items - Main Viewer128
Rename- New . . . . . . . . . 879
Sample Z-Value . . . . . . . . 115 Property . . . . . .146, 225
Renderers, Graphics . . . . . 94 Property - types . . . . 142
SATNUM
Reporter . . . . . . . . . . . . . 888 Quantity . . . . . . . . . 141
Upscaling. . . . . . . . . 476
RESCUE . . . . . . . . . . . . 798 Scenario . . . . . . . . . 225
Saturation Units . . . . . . . .144, 225
Models . . . . . . . . . . 881
Constant . . . . . 453, 481
Versions . . . . . . . . . 881 Select Fine BUG. . . . . . . 488
Save . . . . . . . . . . . . . . . . 889
Rescue Select/move - 3D Viewer. 638
CPS1 . . . . 343, 367, 781
Sampling. . . . . . . . . 881 Selective Population Options268
CPS3 . . . . . . . . . . . . 367
RESCUE faults - new . . . 881 LGR . . . . . . . . . . . . 411 template . . . . . . . . . 272
RESCUE model handling Memory Usage . . . . . . 98 Sequential Gaussian Simulation253
Configuring . . . . . . . 739 Save and Restore Sequential Gaussian Simulation
RESCUE property editor features692 Configuring . . . . . . . 743 algorithm. . . . . 253
Reservoir Data Store Save View Set
Configuring . . . . . . . 736 PostScript . . . . . . . . 853 Down . . . . . . . . . . . .116
Reservoir data store . . . . . 899 SCAL . . . . . . . . . . . . . . . 645 Up . . . . . . . . . . . . . .116
Reset Scaling details . . . . . 897 Set DZ and K Range . . . . 125

Selected Points . . . . 530 Upscaling. . . . . . . . . 460 Set View . . . . . . . . . . . . 134
Up/Down . . . . . . . . 116 Scalars . . . . . . . . . . . . . . 729 Shale Breaks . . . . . . . . . 883
Z-Values . . . . . . . . . 116 Scale to anisotropy . . . . . . 526 Shale Gouge Ratio . . . . . 564
Restore. . . . . . . . . . . . . . 889 Scatter Sets Show Titles . . . . . . . . . . 172
Memory usage . . . . . . 98 Create . . . . . . . . . . . 663
Shrink . . . . . . . . . . . . . . 137
Restore Children . . . . . . . . 76 Node options . . . . . . 353
SI . . . . . . . . . . . . . . . . . 717
Results Scatter Sets editor
Import, PetraGrid . . . 806 2D Viewer SimCellIDToIndex . . . . . 721
return . . . . . . . . . . 705 to 706 2D Viewer SimCreateEmptyProperty 722

Scatter Sets Editor SimGetPropReportSteps . 723
Right mouse button menu 899
673 SimIndexToCellID . . . . . 723
Rotate Grid. . . . . . . . . . . 331

Simple averaging Stack overflow . . . . . . . . 732 Styles . . . . . . . . . . . . . . . 553
Upscaling . . . . . . . . .471 Standard deviation. . 461, 484 Supported operators . . . . . 713
SimPropToVec . . . . . . . . .724 Standard operator reference697 Surface Maps. . . . . . . . . . 342
Simulation Starting FloGrid . . . . . . . . 37 Surfaces
Grid . . . . . . . . . . . . .491 UNIX . . . . . . . . . . . . 37 Assigning Maps . . . . 356
Grid block volumes . .467 Create . . . . . . . 345, 758
Startup files . . . . . . . . . . 731
Grid Editor . . . . . . . .880 Faults . . . . . .365 to 366
Grid faults . . . . . . . .361 Statements . . . . . . . . . . . 702
Limiting rules. . . . . . 759
IJK numbering . . . . .531 Statistics Maps . . . . . . . . 355, 372
Modifying properties - new901 Grid . . . . . . . . . . . . 167 Traces . . . . . . . . . . . 372
Properties window. . .901 Property . . . . . . . . . 166
Surfaces data . . . . . . . . . . 341
Property editor . . . . .896 Well . . . . . . . . . . . . 167
Upscaling properties893, 901 Surfaces ordering . . . . . . . 356
Stereo. . . . . . . . . . . . . . . 137
Simulation Flux Output Based swap . . . . . . . . . . . . . . . . 714
Stereo support
488 to 489, 496 configuring . . . . . . . 749 Swap Down. . . . . . . . . . . 116
Simulation grids (3D property grid)670 Faults . . . . . . . . . . . 116
stop . . . . . . . . . . . . 705, 708
Simulation property editors881 Swap Up . . . . . . . . . . . . . 116
Stratamodel . . . . . . 218, 798
Faults . . . . . . . . . . . 116
Simulation Setup . . . . . . .587 Streamline Display . . . . . 161
Symbol functions . . . 714, 729
SimVecToProp . . . . . . . . .724 Streamline Simulation . . . 585
Syntax . . . . . . . . . . . . . . 702
sin. . . . . . . . . . . . . . . . . . 711 2 Phase . . . . . . . . . . 589
Run time errors. . . . . 704
Single phase upscaling486, 893 RUN. . . . . . . . . . . . 590
Running the Simulation591 Syntax error. . . . . . . . . . . 704
sinh . . . . . . . . . . . . . . . . . 711
Streamline visualization. . 888 Syntax error signalled on a valid line733
Size
Cells . . . . . . . . 508, 517 Streamlines
Edit . . . . . . . . . . . . 161
Slice Plane. . . . . . . . . . . .157
Slicing data options . . . . .403
Streamlines display
Configuring . . . . . . . 753
T
Sloping faults. . . . . . . . . .900 tan . . . . . . . . . . . . . . . . . 711
string . . . . . . . . . . . . . . . 705
Slow execution. . . . . . . . .733 tanh . . . . . . . . . . . . . . . . 712
String concatenation . . . . 703
Smoothing iterations. . . . .517 Target saturation increment457
String constants. . . . . . . . 703
Smoothness . . . . . . . 319, 769 Template, output grid . . . . 272
String variables . . . . . . . . 703
Software Renderer . . . . . . .94 Templates
Strings . . . . . . . . . . . . . . 729
Solution data Axis . . . . . . . . . . . . 347
Structural data model. . . . 190
Import, FloGrid. . . . .430 Tensor Perm Flow Based / Variability
Structural model . . . 175, 886
SOLVNUM 489
Horizon rule . . . . . . 184
Reduced output to ECLIPSE895 Tensor permeability handling895
New . . . . . . . . . . . . 899
Splitter trace . . . . . . . . . .891 Unconformity rule . . 184 Ternary Display . . . . . . . . 170
Splitting Structure. . . . . . . . . . . . . 702 Ternary legend display
Fault blocks . . . 176, 209 Configuring . . . . . . . 752
Structured grid
Fault blocks - new . . .885
Convert. . . . . . . . . . 806 Text Edit Windows. . . . . . . 79
Fault blocks, Limitations213
Model into fault blocks209 Structured grid editor. . . . 880 Text strings . . . . . . . . . . . 702
Recursive volume . . .210 Structured Gridder Th. Reference . 183, 346, 357
Select faults . . . . . . .186 Configuring . . . . . . . 741 Thickness . . . . . . . . . . . . 521
Splitting trace. . . . . . 360, 372 Smoothness . . . . . . . 319 Layering . . . . . . . . . 900
sqrt . . . . . . . . . . . . . . . . . 711 Structured gridder . . 309, 407 Map. . . . . . . . . 343, 346
New . . . . . . . . . . . . 887 Thickness Maps . . . . . . . . 343
SQRT2 . . . . . . . . . . . . . .710
Properties (Upscaler) 427
srand . . . . . . . . . . . . . . . . 711 Threshold
Structured simulation properties897 Extrapolation . . . . . . 528

Input data (Property Population Transmissibility Multipliers565 Min . . . . . . . . . . . . 447
Manager) . 238 Transmissibility multipliers423 Min sat separation . . 457
Property . . . . . . . . . 449 Upscalers - New . . . . . . . 894
transmissibility name . . . . 423
Threshold pressure . . . . . 554 Upscaling. . . . .447, 897, 903
Transparency . . . . . . . . . . 160
Thresholding Properties . . 148 1 Phase . . . . . . . . . . 451
Triangle center aggregation tolerance527
TIFF, format . . . . . 854 to 855 2 Phase . . . . . . . . . . 453
TRUE . . . . . . . . . . . . . . . 710 2 phase . . . . . . .456, 898
Tile . . . . . . . . . . . . . . . . . 76
Two line trace . . . . . 371, 373 3D solutions . . . . . . 473
Tile 3D Windows . . . . . . . 76 Algebraic . . . . . . . . 895
Two phase
Time Animation . . . . . . . 130 Upscaling. . . . . . . . . 898 All cells . . . . . . . . . 449
Titles, Edit . . . . . . . . . . . 171 Applicability . . . . . . 464
Two point probability 461, 484
Arithmetic averaging468, 471, 473
Titles, Show . . . . . . . . . . 172 TWO_DIV_PI . . . . . . . . . 710 Build . . . . . . . . . . . 485
Toolbars . . . . . . . . . . . . . . 94 TWO_DIV_SQRTPI . . . . 710 Capillary pressure . . 476
Top conforming (onlap) . . 322 Constant fractional flow481
Top/3D. . . . . . . . . . . . . . 182 Constant saturation453, 481
Constructing micro grid464
Tops. . . . . . . . . . . . . . . . 888
Depth section. . . . . . 799 U Definition . . . . . . . . 463
Diagnostics . . . .461, 463
TOPX . . . . . . . . . . . . . . 793 UASSOC.CAL . . . . . . . . 719 Directional output . . 457
TOPY . . . . . . . . . . . . . . 793 UNDEFINED . . . . . 703, 710 Domains . . . . . . . . . 449
Trace cell . . . . . . . . . . . . 503 UNIT . . . . . . . . . . . . . . . 543 Export . . . . . . . . . . 430
Geometric. . . . . . . . 467
Traces . . . . . . . . . 366 to 367 Unit
Geometric averaging468 to 469,
Add . . . . . . . . . . . . 369 Create . . . . . . . . . . . 176
471
Auto create . . . . . . . 369 Unit System. . . . . . . . . . . . 94 Grid diagnostics . . . 429
Create . . . . . . . 211, 369
Units. . . . . . . . 190, 717, 729 Half grid block . . . . 894
Defining splitting traces for sloping
Block. . . . . . . . 188, 190 Harmonic averaging469, 471
faults . . . . 361
Build . . . . . . . . . . . . 183 Harmonic-arithmetic averaging472
Edit . . . . . . . . . . . . 115
Constructing. . . . . . . 757 IJK extents . . . . . . . 450
Export as CPS . . . . . 372
Select . . . . . . . 144, 225 IJK slice . . . . . . . . . 450
Fault formats . . . . . . 365
Vertical . . . . . . . . . . 347 Inside out cells . . . . 467
Fault Import . . . . . . 365
Units example . . . . . . . . . 717 Load SCAL. . . . . . . 460
Faults . . . . . . . . . . . 370
Logical coordinates of the block cor-
Display UNITS Keyword . . . . . . . 635 ners . . . . . 466
Fault Traces367 Units table. . . . . . . . . . . . 717 Majority vote . .453, 455
Import. . . . . . . . . . . 366 Max . . . . . . . . . . . . 447
Unstructured Gridder
Maps . . . . . . . . . . . 369 Micro grid. . . . . . . . 466
Configuring . . . . . . . 744
New . . . . . . . . . . . . 891 Multilevel . . . . . . . . 459
Options . . . . . . . . . . 370 Unstructured gridder . . . . 499
Non-dimensional real properties468
Single Line . . . 371, 373 Overview . . . . . . . . . . 24
One-point probability461, 484
Splitting . . . . . 360, 372 Upgridder . . . . . . . . 487, 497 Orthogonality . . . . . 468
Surfaces . . . . . . . . . 372 Configuring . . . . . . . 741 Permeability . . . . . . 470
Trajectories Upgridding . . . . 20, 203, 415 Phase combination. . 453
Export, PetraGrid . . . 810 Block unit grid . . . . . 901 PM Properties . . . . . 451
Wells . . . . . . . . . . . 901 Flow based. . . . . . . . 494 Porosity . . . . . . . . . 470
Trajectory Upscale. . . . . . . . .451 to 452 Power. . . . . . . . . . . 901
Export, PetraGrid . . . 810 Connections (Advanced)503 Power averaging469, 472
Permeability. . . 454, 470 Probability . . . .461, 484
Trans multiplier. . . . . . . . 554
Properties . . . . . . . . 429
Transition bulk regions . . 895 Upscaler . . . . . . . . . 464, 888
Region . . . . . . . . . . 893
Adjoint . . . . . . . . . . 894
Translate Grid . . . . . . . . . 331 Relative permeability 479
Configuring . . . . . . . 742
Transmissibility multiplier513, 545 SATNUM . . . . . . . . 476
Method . . . . . . . . . . 451

Scope . . . . 448, 452, 457 vfft. . . . . . . . . . . . . . . . . 714 VRML export . . . . . . . . . 903
Simulation grid . . . . .467 vfloor. . . . . . . . . . . . . . . 714 vscale . . . . . . . . . . . . . . . 715
Simulation properties893, 901
View vscprod . . . . . . . . . . . . . . 715
Single phase . . . 486, 893
Refresh . . . . . . . . . . 138 vset. . . . . . . . . . . . . . . . . 716
Solutions . . . . . . . . .472
Set . . . . . . . . . . . . . 134
Well connections . . . .902 vshift . . . . . . . . . . . . . . . 716
View mode . . . . . . . . . . . 133
Usability improvements . .883 vsmooth . . . . . . . . . . . . . 716
vinc . . . . . . . . . . . . . . . . 715
user . . . . . . . . . . . . . . . . .712 vsolvematrix . . . . . . . . . . 716
vinclog. . . . . . . . . . . . . . 715
usertype. . . . . . . . . . . . . .705 vsort . . . . . . . . . . . . . . . . 716
vinsert . . . . . . . . . . . . . . 715
vsubtract . . . . . . . . . . . . . 716
vintegrpoly . . . . . . . . . . . 715
vsum. . . . . . . . . . . . . . . . 716
vintegrtrap . . . . . . . . . . . 715
V vinterp . . . . . . . . . . . . . . 715
vsumsqr . . . . . . . . . . . . . 716
vwritecol. . . . . . . .705 to 706
vabs . . . . . . . . . . . . . . . .714 vlaplace . . . . . . . . . . . . . 715
vadd . . . . . . . . . . . . . . . .714 vlen . . . . . . . . . . . 714 to 715
Validating properties. . . . .902 vlog . . . . . . . . . . . . . . . . 715
Variability . . . . . . . . . . . .489 vlsqfit . . . . . . . . . . . . . . 715
W
Variability based upgridding493 vmax . . . . . . . . . . . . . . . 715 Well
Variable . . . . . . . . . . . . . .516 vmaxdiff. . . . . . . . . . . . . 715 Controls. . . . . . . . . . 890
Export connections, PetraGrid810
Variable declarations. . . . .703 vmedian . . . . . . . . . . . . . 715
Well deviation surveys
Variable gridding . . . . . . .902 vmin . . . . . . . . . . . . . . . 715
Export . . . . . . . . . . . 636
Variables . . . . . . . 702 to 703 vmindiff . . . . . . . . . . . . . 715
Well Event Manager. . . . . 641
variables . . . . . . . . . . . . .732 vminus . . . . . . . . . . . . . . 715
Well Events
Variogram . . . . . . . . . . . .294 vmultipy. . . . . . . . . . . . . 715 Animating . . . . . . . . 643
experimental . . . . . . .302 vnearest . . . . . . . . . . . . . 715 Export . . . . . . . . . . . 636
vaverage . . . . . . . . . . . . .714 vnegate . . . . . . . . . . . . . 715 Import . . . . . . . . . . . 633
vceiling . . . . . . . . . . . . . .714 vnpv . . . . . . . . . . . . . . . 715 Well logs
vcopy . . . . . . . . . . . 714, 719 Color Shading . . . . . 685
Volume of Interest
Displaying . . . . . . . . 680
vcopyconv . . . . . . . . 714, 719 Boundaries . . . . . . . 153
removing . . . . . . . . . 682
vcopyraw. . . . . . . . . 714, 719 Grid Cells . . . . . . . . 152
Selecting Domains . . 152 Well marker correlation . . 681
vdelete . . . . . . . . . . . . . .714
Volume of interest . . . . . . 572 Well marker correlations
vderivpoly . . . . . . . . . . . .714 removing . . . . . . . . . 682
Boundaries . . . . . . . 450
vdivide . . . . . . . . . . . . . .714 Grid cells . . . . . . . . 450 Well markers
Vectors . . 703, 705, 708, 729 Volumetrics . . . . . . . . . . 569 Displaying . . . . . . . . 680
Version Contact Sets . . 571, 575 removing . . . . . . . . . 682
Property . . . . . . . . . .446 Limitations . . . . . . . 569 Well Statistics . . . . . . . . . 167
Versioning of properties . .901 Multiple Realization. 577 Wellpath
Multiple Realizations 624 Edit . . . . . . . . . . . . . 637
Vertical boundary . . . . . . .328
Realization Dialog . . 625
Vertical Edit. . . . . . . . . . .124 Wells . . . . . .503 to 504, 632
run definitions . . . . . 574
Add . . . . . . . . . . . . . 539
Vertical gridder . . . . . . . .879 Single run . . . . . . . . 576
Aliases. . . . . . . . . . . 143
Vertical gridding767, 893, 895 vpolynom . . . . . . . . . . . . 715 Appearance of . . . . . 165
Vertical gridding - new . . .892 vpow . . . . . . . . . . . . . . . 715 Connection upscaling 902
Vertical Well Planning . . .632 vrandomfill. . . . . . . . . . . 715 Connections . . . . . . . 502
Controls. . . . . . . . . . 504
Vertical zigzag faults. . . . .882 vreadcol . . . . . . . . 705 to 706
Data Logs . . . . . . . . 386
vexpon . . . . . . . . . . . . . .714 vresize . . . . . 708, 714 to 715 Deviation surveys . . . 376

Displaying. . . . . . . . 680 while . . . . . . . . . . . 705, 708
Elliptic . . . . . . . . . . 516
Export keywords . . . 810
while example . . . . . . . . . 708 Y
White space. . . . . . . . . . . 702
Export Trajectories. . 810 yn . . . . . . . . . . . . . . . . . 712
Generate connections 895 Width . . . . . . . . . . . . . . . 511
Grid . . . . . . . . . . . . 504 Window
GRID import format. 377 Components . . . 658, 850
Grid Style . . . . . . . . 505 Window List . . . . . . . . . . . 76 Z
Horizontal wells with multiple frac-
Window Menu . . . . . . . . . . 76 Z rotation . . . . . . . . . . . . 347
tures . . . . . 894
Import formats. . . . . 376 Windows, Tile . . . . . . . . . . 76 Zigzag faults . . . . . .526, 887
node . . . . . . . . . . . . 632 Wire Frame . . . . . . . . . . . . 95 ZMAP . . . . . . . . . . .344, 782
Projection . . . . . . . . 528 Workspace. . . . . . . . . . . . . 98 Zoom
Radial . . . . . . . 516, 894
write . . . . . . . . . . .705 to 706 Rubberband . . . . . . 883
Radius . . . . . . . . . . 508
removing. . . . . . . . . 682 writing to file. . . . . . . . . . 706 Zoom, Rubber Band . . . . 135
Skin . . . . . . . . . . . . 508 Z-Value
Track display . . . . . . 376 Sampling . . . . . . . . .115
Track Displaying . . . 376
Trajectories . . . . . . . 901 X Z-Values
Digitized points . . . . 126
Wells display XYOFFSET . . . . . . . . . . 792 Moved points . . . . . 127
configuring . . . . . . . 752 Reset . . . . . . . . . . . .116
XYUNITS. . . . . . . . . . . . 792
Wells settings panel . . . . . 666
XYZ Exaggeration . . . . . . 137


Flog Ug

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Flog Ug

Încărcat de

Drepturi de autor:

Formate disponibile

ECLIPSE* reservoir simulation software

Trademarks & service marks

Chapter 1 - New developments ..................................................................................................... 13

Chapter 2 - Introduction ................................................................................................................. 15

Chapter 3 - Getting started............................................................................................................. 37

Chapter 4 - Short Tutorials............................................................................................................. 39

Chapter 5 - User Interface .............................................................................................................. 75

Chapter 6 - Save and Restore ........................................................................................................ 97

Chapter 7 - Commands................................................................................................................. 101

Chapter 8 - 3D Viewer ................................................................................................................... 107

FloGrid User Guide 3

Chapter 9 - Structural Framework ............................................................................................... 175

Chapter 10 - Fault framework editor ........................................................................................... 191

Chapter 11 - Geological Property model .................................................................................... 215

Chapter 12 - Property population................................................................................................ 231

4 FloGrid User Guide

Chapter 14 - Data tree................................................................................................................... 333

Chapter 15 - LGRs, Resizing, Aquifers and NNCs ..................................................................... 407

Chapter 16 - Structured gridder properties ................................................................................ 427

Chapter 17 - Upgridder ................................................................................................................. 487

Chapter 18 - Generating an unstructured grid ........................................................................... 499

Chapter 19 - LGRs, Aquifers and Properties for an unstructured grid.................................... 535

FloGrid User Guide 5

Chapter 20 - Fault Property Calculator ....................................................................................... 551

Chapter 21 - Volumetrics.............................................................................................................. 569

Chapter 22 - Contact Sets ............................................................................................................ 579

Chapter 23 - Streamline Simulation ............................................................................................ 585

Chapter 24 - Multiple Realizations .............................................................................................. 623

Chapter 25 - Well Planning........................................................................................................... 631

Chapter 26 - Core Analysis .......................................................................................................... 645

6 FloGrid User Guide

Chapter 28 - 2D Well Log Correlation Canvas............................................................................ 679

Chapter 29 - Expression Calculator ............................................................................................ 687

Appendix A - Calculator Language ............................................................................................. 701

Appendix B - Configuring FloGrid............................................................................................... 735

Appendix D - Corner point gridding............................................................................................ 761

Appendix E - Input file formats .................................................................................................... 773

FloGrid User Guide 7

Appendix F - Importing Data From GeoFrame ........................................................................... 803

Appendix G - Unstructured Gridder files.................................................................................... 805

Appendix H - Property Population Glossary.............................................................................. 813

Appendix I - Reference Tutorials ................................................................................................. 823

Appendix J - Mapping Packages................................................................................................. 839

Appendix K - Printing images...................................................................................................... 853

Appendix L - History of developments ....................................................................................... 859

Appendix M - Bibliography .......................................................................................................... 905

Appendix N - Index ....................................................................................................................... 909

8 FloGrid User Guide

FloGrid User Guide 9

10 FloGrid User Guide

FloGrid User Guide 11

12 FloGrid User Guide

FloGrid User Guide New developments 13

14 New developments FloGrid User Guide

FloGrid User Guide Introduction 15

16 Introduction FloGrid User Guide

Tasks in a common modeling workflow

FloGrid User Guide Introduction 17

18 Introduction FloGrid User Guide

Three gridding approaches are supported:

FloGrid User Guide Introduction 19

Using an imported grid

20 Introduction FloGrid User Guide