eclipse grid_refernce manual

GRID

Reference Manual

2008.1

www.cadfamily.com EMail:[email protected] document is for study only,if tort to your rights,please inform us,we will delete

www.cadfamily.com

Proprietary NoticeCopyright © Schlumberger. All rights reserved.

No part of this document may be reproduced, stored in an information retrieval system, or translated in any form or retransmitted or by anymeans, electronic or mechanical, including photocopying and recording, without the prior written permission of the copyright owner.

Use of this product is governed by the License Agreement. Schlumberger makes no warranties, express, implied, or statutory, with respectto the product described herein and disclaims without limitation any warranties of merchantability or fitness for a particular purpose.

Patent informationSchlumberger ECLIPSE reservoir simulation software is protected by US Patents 6,018,497, 6,078,869 and 6,106,561, and UK PatentsGB 2,326,747 B and GB 2,336,008 B. Patents pending. Schlumberger FrontSim reservoir simulation software is protected by US Patent2004/0015295A1.

Service mark informationThe following are all service marks of Schlumberger:

The Calculator, Charisma, ConPac, ECLIPSE 100, ECLIPSE 200, ECLIPSE 300, ECLIPSE 500, ECLIPSE Office, EDIT, Extract, Fill,Finder, FloGeo, FloGrid, FloViz, FrontSim, GeoFrame, GRAF, GRID, GridSim, Nodal, NWM, Open-ECLIPSE, PetraGrid, PIPESIM,PIPESIM FPT, PIPESIM GOAL, PlanOpt, Prodman, Pseudo, PVTi, RTView, SCAL, Schedule, SimOpt, VFPi, Weltest 200.

Trademark informationSilicon Graphics and IRIX are registered trademarks of Silicon Graphics, Inc. OpenGL® and the oval logo are trademarks or registeredtrademarks of Silicon Graphics, Inc. in the United States and/or other countries worldwide. OpenInventor and WebSpace are trademarksof Silicon Graphics, Inc. IBM, AIX and LoadLeveler are registered trademarks of International Business Machines Corporation. Sun,SPARC, Solaris, Ultra and UltraSPARC are trademarks or registered trademarks of Sun Microsystems, Inc. Macintosh is a registeredtrademark of Apple Computer, Inc. UNIX is a registered trademark of UNIX System Laboratories. Motif is a registered trademark of theOpen Software Foundation, Inc. The X Window System and X11 are registered trademarks of the Massachusetts Institute of Technology.PostScript and Encapsulated PostScript are registered trademarks of Adobe Systems, Inc. OpenWorks and VIP are registered trademarksof Landmark Graphics Corporation. Lotus, 1-2-3 and Symphony are registered trademarks of Lotus Development Corporation. Microsoft,Windows, Windows NT, Windows 95, Windows 98, Windows 2000, Windows XP, Internet Explorer, Intellimouse and PowerPoint areeither registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Netscape is a registeredtrademark of Netscape Communications Corporation. AVS is a registered trademark of AVS Inc. ZEH is a registered trademark of ZEHGraphics Systems. Ghostscript and GSview are Copyright of Aladdin Enterprises, CA. GNU Ghostscript is Copyright of the Free SoftwareFoundation, Inc. Linux is Copyright of the Free Software Foundation, Inc. IRAP is Copyright of Roxar Technologies. LSF is a registeredtrademark of Platform Computing Corporation, Canada. VISAGE is a registered trademark of VIPS Ltd. Cosmo is a trademark andPLATINUM technology is a registered trademark of PLATINUM technology, inc. PEBI is a trademark of Veritas DGC Inc./HOT EngineeringGmbH. Stratamodel is a trademark of Landmark Graphics Corporation. GLOBEtrotter, FLEXlm and SAMreport are registered trademarksof GLOBEtrotter Software, Inc. CrystalEyes is a trademark of StereoGraphics Corporation. Tektronix is a registered trade mark ofTektronix, Inc. GOCAD and JACTA are trademarks of T-Surf. Myrinet is a trade name of Myricom, Inc. This product may include softwaredeveloped by the Apache Software Foundation (http://www.apache.org). Copyright (c) 1999-2001 The Apache Software Foundation. Allrights reserved. MPI/Pro is a registered trademark of MPI Software Technology, Inc. The TGS logo is a trademark of TGS, Inc. POSC, thePOSC logo and Epicentre are registered trademarks of Petrotechnical Open Standards Consortium, Inc. Red Hat is a registeredtrademeak of Red Hat, Inc. This product may include software developed using LAPACK (http://www.netlib.org/lapack/), which is copyrightof its authors. Scali is a trademark of Scali Inc.


www.cadfamily.com

GRID Reference Manual Table of Contents

3

Table of ContentsChapter 1 - New Developments ..................................................................................................... 13Changes for 2007.1 ..............................................................................................................................................................13Changes for 2006.1 ..............................................................................................................................................................14Changes for 2004A...............................................................................................................................................................15

Chapter 2 - Introduction ................................................................................................................. 17Overview............. .................................................................................................................................................................17GRID functionality.................................................................................................................................................................18Mapping facilities .................................................................................................................................................................19Seismic data ....... .................................................................................................................................................................20Depth conversion and volumetrics........................................................................................................................................21Simulation grid editing ..........................................................................................................................................................22General facilities . .................................................................................................................................................................23

Chapter 3 - Using GRID .................................................................................................................. 25Introduction......... .................................................................................................................................................................25Starting the program.............................................................................................................................................................26Configuration file options ......................................................................................................................................................28GRID terminology .................................................................................................................................................................29File handling ....... .................................................................................................................................................................30Menus................. .................................................................................................................................................................31X-Windows displays..............................................................................................................................................................33Digitizing tables .. .................................................................................................................................................................34Further help and advice........................................................................................................................................................35

Chapter 4 - Primary Menu and Edit Model.................................................................................... 37Introduction......... .................................................................................................................................................................37The Primary menu ................................................................................................................................................................38Edit model........... P.1 ..........................................................................................39Delete model ...... P.1.2 ...........................................................................................40Delete stratum .... P.1.2.2 .............................................................................................41Delete map ........ P.1.2.3 ..........................................................................................42Delete grid ......... P.1.2.4 ..........................................................................................43Delete survey ..... P.1.2.5 .............................................................................................44Change model ... P.1.3 ..............................................................................................45Change map name P.1.3.2...................................................................................................46Change map stratum P.1.3.3...................................................................................................47Change map units P.1.3.4 ...................................................................................................48Change model area P.1.3.5...................................................................................................49Change number of model strata P.1.3.6...................................................................................................50Change mesh data P.1.3.7...................................................................................................51List history file ..... P.1.4 ..............................................................................................52Output a model report P.1.5 ...................................................................................................53

Chapter 5 - Edit Map ....................................................................................................................... 55Introduction......... .................................................................................................................................................................55Edit map ............. P.2 ..........................................................................................57Edit wells ............ P.2.2 ..........................................................................................59Copy wells .......... P.2.2.2 ..........................................................................................60Add well .............. P.2.2.3 ..........................................................................................61Delete well .......... P.2.2.4 ..........................................................................................62Change wells ...... P.2.2.5 ...........................................................................................63


www.cadfamily.com

4 GRID Reference ManualTable of Contents

Change well name P.2.2.5.2...................................................................................................64Move well ............ P.2.2.5.3...........................................................................................65Input wells ........... P.2.2.6...........................................................................................66Output wells ........ P.2.2.7...........................................................................................68Define Granite settings P.2.2.8 ...................................................................................................70Change Granite settings P.2.2.9....................................................................................................71Edit faults ............ P.2.3...........................................................................................73Copy faults .......... P.2.3.2...........................................................................................74Add fault.............. P.2.3.3...........................................................................................75Delete faults ........ P.2.3.4...........................................................................................77Change fault ....... P.2.3.5...........................................................................................78Change fault name P.2.3.5.2 ...................................................................................................79Change fault type P.2.3.5.3...................................................................................................80Change fault colour fill mask P.2.3.5.4 ...................................................................................................81Change fault segment P.2.3.5.5 ...................................................................................................82Change fault trace P.2.3.5.6 ...................................................................................................83Operate on fault traces P.2.3.5.7...................................................................................................84Clip fault trace..... P.2.3.5.7.2..............................................................................................85Split fault trace .... P.2.3.5.7.3...............................................................................................86Close fault polygons P.2.3.5.7.4 ...................................................................................................87Thin faults ........... P.2.3.5.7.5...........................................................................................88Repopulate faults P.2.3.5.7.6...................................................................................................89Smooth faults ...... P.2.3.5.7.7.............................................................................................90Join faults............ P.2.3.5.7.8...........................................................................................91Extend faults ....... P.2.3.5.7.9...........................................................................................92Input faults .......... P.2.3.6...........................................................................................93Output faults ....... P.2.3.7............................................................................................98Define Granite settings P.2.3.8 .................................................................................................102Edit contours....... P.2.4...........................................................................................103Copy contours..... P.2.4.2............................................................................................104Add contours....... P.2.4.3...........................................................................................105Delete contours... P.2.4.4..............................................................................................107Change contours P.2.4.5................................................................................................108Show contour value P.2.4.5.2.................................................................................................109Change contour value P.2.4.5.3 .................................................................................................110Operate on contour values P.2.4.5.4 .................................................................................................111Change contour line P.2.4.5.5 .................................................................................................112Operate on contour lines P.2.4.5.6 .................................................................................................113Clip contours....... P.2.4.5.6.2..........................................................................................114Split contours ...... P.2.4.5.6.3...........................................................................................115Delete fault region P.2.4.5.6.4 .................................................................................................116Thin contours ...... P.2.4.5.6.5...........................................................................................117Repopulate contours P.2.4.5.6.6 .................................................................................................118Smooth contours P.2.4.5.6.7.................................................................................................119Join contours ...... P.2.4.5.6.8...........................................................................................120Extend contours .. P.2.4.5.6.9...............................................................................................121Change contour parameters P.2.4.6..................................................................................................122Show map area... P.2.4.6.2.............................................................................................123Change map area P.2.4.6.3.................................................................................................124Change contour labels P.2.4.6.4 .................................................................................................125Change contour interval P.2.4.6.5 .................................................................................................126Define Granite settings P.2.4.6.6 .................................................................................................127Input contours P.2.4.7..................................................................................................128Output contours .. P.2.4.8...............................................................................................132Sample contours. P.2.4.9................................................................................................134Test point ............ P.2.4.9.2.........................................................................................135Test map............. P.2.4.9.3.........................................................................................136Test grid .............. P.2.4.9.4.........................................................................................137Test node............ P.2.4.9.4.3.........................................................................................138


www.cadfamily.com


5

Test block ........... P.2.4.9.4.4 ........................................................................................139Test all nodes ..... P.2.4.9.4.5 ..........................................................................................140Test all blocks..... P.2.4.9.4.6 ...........................................................................................141Edit sample values P.2.4.9.4.7 .................................................................................................142Show block value P.2.4.9.4.7.2 ...............................................................................................143Define block value P.2.4.9.4.7.3.................................................................................................144Show corner value P.2.4.9.4.7.4 ................................................................................................145Define corner value P.2.4.9.4.7.5 ................................................................................................146Output block values P.2.4.9.4.7.6.................................................................................................147Output corner values P.2.4.9.4.7.7.................................................................................................148Output node values P.2.4.9.4.7.8 .................................................................................................149Show sampled contours P.2.4.9.4.7.9.................................................................................................150Save corner values on grid P.2.4.9.4.8 .................................................................................................151Save block values as grid property v P.2.4.9.4.9..................................................................................................152Show back contours P.2.4.9.5.................................................................................................153Output back contours P.2.4.9.6 .................................................................................................155Change interpolation P.2.4.9.7 .................................................................................................156Define null........... P.2.4.9.7.2 ........................................................................................157Define truncation values P.2.4.9.7.3.................................................................................................158Define damping factor P.2.4.9.7.4 .................................................................................................159Define search radius P.2.4.9.7.5 ................................................................................................160Define interpolation mode P.2.4.9.7.6 .................................................................................................163Set weighting for well control points P.2.4.9.7.7..................................................................................................165Toggle faults in interpolation P.2.4.9.7.8 .................................................................................................166Toggle minimum slope P.2.4.9.7.9 .................................................................................................167Change back contour display P.2.4.9.8.................................................................................................168Change Granite settings P.2.4.9.8.2 ................................................................................................169Change colour fill P.2.4.9.8.3 ................................................................................................170Number of styles. P.2.4.9.8.3.2 ..............................................................................................171Change index ..... P.2.4.9.8.3.3 .........................................................................................172Change limits ...... P.2.4.9.8.3.4 .........................................................................................173Set shading......... P.2.4.9.8.3.5 .......................................................................................174Reset colours...... P.2.4.9.8.3.6 .........................................................................................176Select variable transformation P.2.4.9.9..................................................................................................177Edit mesh............ P.2.5 ........................................................................................179Input mesh.......... P.2.5.2 ........................................................................................180Calculate mesh... P.2.5.3 ............................................................................................192Operate on a mesh P.2.5.4 ................................................................................................193Mask a mesh ...... P.2.5.5 .........................................................................................195Change mesh parameters P.2.5.6.................................................................................................196Change contour labels P.2.5.6.4 .................................................................................................197Change contour interval P.2.5.6.5 .................................................................................................198Show minimum & maximum P.2.5.6.6.................................................................................................199Show nulls .......... P.2.5.6.7 ........................................................................................200Define Granite settings P.2.5.6.8.................................................................................................201Change mesh map colour fill P.2.5.6.9.................................................................................................202Change key ........ P.2.5.6.9.7 ........................................................................................203Define mesh value P.2.5.7 ................................................................................................204Output mesh ....... P.2.5.8 .........................................................................................205Sample mesh...... P.2.5.9 .........................................................................................208Change mesh interpolation P.2.5.9.4 .................................................................................................209Toggle null mask boundary P.2.5.9.4.7 .................................................................................................210Show search circle P.2.5.9.4.9 .................................................................................................211Edit features ....... P.2.6 ........................................................................................213Copy features ..... P.2.6.2 ..........................................................................................214Add a feature ...... P.2.6.3 .........................................................................................215Delete features ... P.2.6.4 ............................................................................................216Change features . P.2.6.5 ..............................................................................................217Change feature name P.2.6.5.2 ................................................................................................218


www.cadfamily.com


Change a feature line P.2.6.5.3 ................................................................................................219Operate on feature lines P.2.6.5.4.................................................................................................220Clip feature line... P.2.6.5.4.2..............................................................................................221Split feature line .. P.2.6.5.4.3..............................................................................................222Thin features....... P.2.6.5.4.4.........................................................................................223Repopulate features P.2.6.5.4.5 .................................................................................................224Smooth features . P.2.6.5.4.6...............................................................................................225Join features ...... P.2.6.5.4.7..........................................................................................226Extend features... P.2.6.5.4.8..............................................................................................227Input features...... P.2.6.6...........................................................................................228Output features ... P.2.6.7..............................................................................................232Define Granite settings P.2.6.8 .................................................................................................236Change Granite settings P.2.6.9..................................................................................................237Edit captions ....... P.2.7..........................................................................................239Copy captions ..... P.2.7.2............................................................................................240Add a caption...... P.2.7.3...........................................................................................241Delete a caption.. P.2.7.4...............................................................................................242Change caption data P.2.7.5 .................................................................................................243Move a caption ... P.2.7.5.2.............................................................................................244Change a caption P.2.7.5.3.................................................................................................245Define Granite settings P.2.7.5.4 .................................................................................................246Change Granite settings P.2.7.5.5.................................................................................................247Input captions ..... P.2.7.6............................................................................................248Output captions... P.2.7.7...............................................................................................250Edit zones ........... P.2.8.........................................................................................251Copy zones......... P.2.8.2.........................................................................................252Add a zone.......... P.2.8.3.........................................................................................253Delete zones....... P.2.8.4.........................................................................................254Change a zone ... P.2.8.5............................................................................................255Input zones ......... P.2.8.6.........................................................................................256Output zones ...... P.2.8.7..........................................................................................259Define Granite settings P.2.8.8..................................................................................................262Change Granite settings P.2.8.9..................................................................................................263Edit legend.......... P.2.9.........................................................................................264Copy legend........ P.2.9.2.........................................................................................265Add a legend item P.2.9.3 .................................................................................................266Delete a legend item P.2.9.4 ................................................................................................267Move an item ...... P.2.9.5..........................................................................................268Change an item .. P.2.9.6..............................................................................................269Change legend ... P.2.9.7.............................................................................................270Define Granite settings P.2.9.8 .................................................................................................271

Chapter 6 - Edit Grid..................................................................................................................... 273Introduction ......... ...............................................................................................................................................................273Edit grid............... P.3.........................................................................................276Vector grid .......... P.3.0.2.........................................................................................278N x M grid ........... P.3.0.3.........................................................................................279Irregular grid ....... P.3.0.4..........................................................................................280Add control column P.3.0.4.1..................................................................................................282Add control row... P.3.0.4.2..............................................................................................283Delete control column P.3.0.4.3..................................................................................................284Delete control row P.3.0.4.4..................................................................................................285Change control column P.3.0.4.5..................................................................................................286Change control row P.3.0.4.6 .................................................................................................287Make grid ............ P.3.0.4.7.........................................................................................288Output control lines P.3.0.4.8 .................................................................................................289Input control lines P.3.0.4.9..................................................................................................290Mark axes ........... P.3.0.5.........................................................................................291


www.cadfamily.com


7

Input grid............. P.3.0.6 ........................................................................................292Copy grid ............ P.3.0.7 ........................................................................................295Merge grids......... P.3.0.8 ........................................................................................296Cross-section grid P.3.0.9 .................................................................................................298Edit layer............. P.3.2 ........................................................................................299Define depth of layer P.3.2.2 .................................................................................................300Define thickness of layer P.3.2.3 .................................................................................................302Add a grid layer .. P.3.2.4 .............................................................................................303Delete a grid layer P.3.2.5 .................................................................................................304Divide a grid layer P.3.2.6 .................................................................................................305Split a layer ......... P.3.2.7 ........................................................................................306Join layers .......... P.3.2.8 ........................................................................................307Edit area ............. P.3.3 ........................................................................................308Equalize area...... P.3.3.2 .........................................................................................309Equalize columns P.3.3.3 ................................................................................................310Equalize rows ..... P.3.3.4 ..........................................................................................311Define depth of an area P.3.3.5.................................................................................................312Define thickness of an area P.3.3.6.................................................................................................313Split area ............ P.3.3.7 ........................................................................................314Join an area........ P.3.3.8 ........................................................................................315Verticalize an area P.3.3.9 ................................................................................................316Edit lines ............. P.3.4 ........................................................................................317Add rows............. P.3.4.2 ........................................................................................318Add columns....... P.3.4.3 .........................................................................................319Delete a row ....... P.3.4.4 ........................................................................................320Delete a column.. P.3.4.5 ..............................................................................................321Move a row ......... P.3.4.6 ........................................................................................322Move a column ... P.3.4.7 ............................................................................................323Straighten a line.. P.3.4.8 ..............................................................................................324Equalize a line .... P.3.4.9 ...........................................................................................325Edit nodes........... P.3.5 ........................................................................................326Move a node....... P.3.5.2 ........................................................................................327Move node to node P.3.5.3 ................................................................................................328Define node depth P.3.5.4.................................................................................................329Mark node depth. P.3.5.5 ...............................................................................................330Define node thickness P.3.5.6.................................................................................................331Split nodes.......... P.3.5.7 ........................................................................................332Join nodes .......... P.3.5.8 ........................................................................................334Move a coordinate line P.3.5.9 .................................................................................................335Edit fault lines ..... P.3.6 ...........................................................................................337Move row to a fault P.3.6.2.................................................................................................338Move column to a fault P.3.6.3 .................................................................................................339Move node to fault P.3.6.4.................................................................................................340Move row to a sloping fault P.3.6.5 .................................................................................................341Move column to a sloping fault P.3.6.6..................................................................................................342Define a sloping line P.3.6.7..................................................................................................343Define line depth. P.3.6.8 ...............................................................................................344Show values ....... P.3.7 ........................................................................................345Show x,y,z .......... P.3.7.2 ........................................................................................346Show I,J,K ......... P.3.7.3 ........................................................................................347Show thickness... P.3.7.4 .............................................................................................348Highlight depth range P.3.7.5 .................................................................................................349Highlight thickness range P.3.7.6 ..................................................................................................350Check grid orthogonality P.3.7.7 ..................................................................................................351Calculate grid orthogonality P.3.7.7.2..................................................................................................352Show orthogonality for a grid block P.3.7.7.3 ..................................................................................................353Show orthogonality colour fill P.3.7.7.4...................................................................................................354Display orthogonality report P.3.7.7.8..................................................................................................355Edit blocks .......... P.3.8 ........................................................................................357


www.cadfamily.com


Refine grid .......... P.3.8.2.........................................................................................358Create local grid refinement P.3.8.2.2 .................................................................................................359Radial local grid refinement P.3.8.2.3..................................................................................................360Delete local grid refinement .3.8.2.4 ....................................................................................................361Delete all local grid refinements P.3.8.2.5 .................................................................................................362Input LGR ........... P.3.8.2.6.........................................................................................363Show local grid refinement P.3.8.2.7 ..................................................................................................365Edit active cells ... ................................................................................................................................................... P.3.8.3366Define active layer P.3.8.3.2 .................................................................................................367Define active area P.3.8.3.3 ................................................................................................368Define active blocks P.3.8.3.4..................................................................................................369Show active ........ P.3.8.3.5.........................................................................................370Input active cell numbers P.3.8.3.6..................................................................................................371Output active cell numbers P.3.8.3.7..................................................................................................372Operate on active cells P.3.8.3.8 .................................................................................................373Show total active cells P.3.8.3.9 .................................................................................................374Edit region numbers P.3.8.4 .................................................................................................375Define region layer P.3.8.4.2 .................................................................................................376Define region area P.3.8.4.3.................................................................................................377Define region blocks P.3.8.4.4..................................................................................................378Show region numbers P.3.8.4.5..................................................................................................379Input region numbers P.3.8.4.6 .................................................................................................380Output region numbers P.3.8.4.7..................................................................................................381Operate on region numbers P.3.8.4.8.................................................................................................382Display region numbers P.3.8.4.9..................................................................................................383Edit properties..... P.3.8.5............................................................................................384Define property layer P.3.8.5.2 .................................................................................................385Define property area P.3.8.5.3.................................................................................................386Define property blocks P.3.8.5.4..................................................................................................387Show property..... P.3.8.5.5............................................................................................388Input property...... P.3.8.5.6...........................................................................................389Output property ... P.3.8.5.7..............................................................................................390Operate on properties P.3.8.5.8 .................................................................................................391Display property values P.3.8.5.9 .................................................................................................392Show property fill P.3.8.5.9.2.................................................................................................393Move property key P.3.8.5.9.4 .................................................................................................394Change property key P.3.8.5.9.5 .................................................................................................395Show property contours P.3.8.5.9.6..................................................................................................396Edit fluids-in-place P.3.8.6 ..................................................................................................397Calculate fluids-in-place P.3.8.6.2 .................................................................................................398Show fluids-in-place P.3.8.6.3 .................................................................................................399Output fluids-in-place P.3.8.6.4..................................................................................................400Delete regions..... P.3.8.7............................................................................................401Delete property ... P.3.8.8.............................................................................................402Coarsen grid ....... P.3.8.9..........................................................................................403Create grid coarsening P.3.8.9.2 .................................................................................................404Delete grid coarsening P.3.8.9.3..................................................................................................405Input grid coarsening P.3.8.9.4..................................................................................................406Grid utilities ......... P.3.9.........................................................................................407Output grid .......... P.3.9.2.........................................................................................408Operate on grid geometry P.3.9.3..................................................................................................414Move origin ......... P.3.9.3.2.........................................................................................415Relocate grid....... P.3.9.3.3..........................................................................................416Rotate grid .......... P.3.9.3.4.........................................................................................417Scale grid ............ P.3.9.3.5.........................................................................................418Order grid blocks. P.3.9.3.6.................................................................................................419Split grid .............. P.3.9.4.........................................................................................420Rejoin split grid nodes P.3.9.5 ..................................................................................................421Calculate properties by map averaging P.3.9.6 ..................................................................................................422


www.cadfamily.com


9

Calculate pore volumes and transmissibilities P.3.9.7...................................................................................................427Convert grid data to map data P.3.9.8.................................................................................................434

Chapter 7 - Simulation Results.................................................................................................... 439Introduction......... ...............................................................................................................................................................439Simulator results . P.4 ................................................................................................440Edit solutions ...... P.4.2 ..........................................................................................441Load solutions .... P.4.2.2 ............................................................................................442Display solutions. P.4.2.3 ................................................................................................443Show solution fill . P.4.2.3.2 ...............................................................................................444Show contour sequence P.4.2.3.9.................................................................................................445Create a solution P.4.2.4 ...............................................................................................446Create differences P.4.2.5.................................................................................................447Output solution ... P.4.2.6 .............................................................................................448Clear a solution... P.4.2.7 .............................................................................................449Load active cell numbers from INIT file P.4.2.8..................................................................................................450

Chapter 8 - Edit Survey ................................................................................................................ 451Introduction......... ...............................................................................................................................................................451Edit survey.......... P.5 ........................................................................................452Edit shot lines ..... P.5.2 ...........................................................................................454Add a shot line.... P.5.2.2 ............................................................................................455Delete a shot line P.5.2.3 ...............................................................................................457Digitize a section P.5.2.4 ...............................................................................................458Operate on horizon P.5.2.5 .................................................................................................460Show value ......... P.5.2.6 ........................................................................................461Define value........ P.5.2.7 ........................................................................................462Sample horizon... P.5.2.8 .............................................................................................463Input survey ........ P.5.3 ........................................................................................464Output survey ..... P.5.4 ...........................................................................................466Sample survey.... P.5.5 ............................................................................................467Test survey ......... P.5.5.3 ........................................................................................468Set interpolation debug P.5.5.6.7 .................................................................................................469Output misties..... P.5.5.9 ...........................................................................................470Change survey parameters P.5.6.................................................................................................471Change horizon numbers P.5.7.................................................................................................472Define Granite settings P.5.8..................................................................................................473

Chapter 9 - Map Utilities ............................................................................................................... 475Introduction......... ...............................................................................................................................................................475Map utilities......... P.6 ........................................................................................477ECLMap options P.6.2.................................................................................................478Depth conversion P.6.2.2 ................................................................................................479Convert a point on a map P.6.2.2.2.................................................................................................483Convert map ....... P.6.2.2.3 ........................................................................................484Convert a shot point P.6.2.2.4 .................................................................................................485Convert a shot line P.6.2.2.5 .................................................................................................486Convert horizon .. P.6.2.2.6 .............................................................................................487Volumetrics ......... P.6.2.3 ........................................................................................488Calculate volumes P.6.2.3.2.................................................................................................489Operate on volumes P.6.2.3.3.................................................................................................491Show volumes .... P.6.2.3.4 ...........................................................................................492Sample volumes . P.6.2.3.5 ..............................................................................................493Show zone area.. P.6.2.3.6 .............................................................................................494Calculate water saturation P.6.2.4..................................................................................................495Import map data . P.6.3 ..............................................................................................497Import one or more mesh maps P.6.3.2 .................................................................................................498


www.cadfamily.com


Import Stratamodel data P.6.3.3 .................................................................................................502Import EarthVision data P.6.3.4..................................................................................................509Import / export DXF files P.6.3.5..................................................................................................514Import DXF data . P.6.3.5.2..............................................................................................515Export DXF data . P.6.3.5.3...............................................................................................519Export maps........ P.6.4.........................................................................................521Copy map data ... P.6.5.............................................................................................523Process well data P.6.6.................................................................................................524Input well trajectory data P.6.6.2..................................................................................................525Output well connection data P.6.6.3 ..................................................................................................529Delete well trajectory data P.6.6.4 .................................................................................................531Input CLAN ......... P.6.6.5.........................................................................................532

Chapter 10 - Change Settings...................................................................................................... 533Introduction ......... ...............................................................................................................................................................533Change settings.. P.7...............................................................................................536

Chapter 11 - Clear Workspace ..................................................................................................... 539Introduction ......... ...............................................................................................................................................................539Clear workspace . P.8................................................................................................540

Chapter 12 - Run Files.................................................................................................................. 541Run files.............. R ..........................................................................................541Execute a run file R.2 ................................................................................................545Open a run file .... R.3 ............................................................................................546Close a run file .... R.4 ............................................................................................547Path .................... R.5 .........................................................................................548Set option............ R.6 .........................................................................................549Show coordinate position R.7 ...................................................................................................550

Chapter 13 - Display ..................................................................................................................... 551Introduction ......... ...............................................................................................................................................................551Display ................ D ..........................................................................................553Refresh ............... D.2 .........................................................................................554Unzoom .............. D.3 .........................................................................................555Define zoom........ D.4 .........................................................................................556Increase display.. D.5 ...............................................................................................557Change display ... D.6 .............................................................................................558Change box ........ D.6.2 ........................................................................................559Change coordinate box D.6.2.2 .................................................................................................560Change coordinate level D.6.2.2.2..................................................................................................561Change coordinate ticks D.6.2.2.3..................................................................................................562Toggle coordinate box labels D.6.2.2.4 ..................................................................................................563Change coordinate box labels D.6.2.2.5..................................................................................................564Change Granite settings D.6.2.2.6.................................................................................................565Change graticule box D.6.2.3 .................................................................................................566Change graticule level D.6.2.3.2.................................................................................................567Change graticule ticks D.6.2.3.3..................................................................................................568Toggle graticule labels D.6.2.3.4 .................................................................................................569Change graticule labels D.6.2.3.5.................................................................................................570Change Granite settings D.6.2.3.6.................................................................................................571Toggle seconds on graticule labels D.6.2.3.7..................................................................................................572Change map display D.6.3..................................................................................................573Change wells ...... D.6.3.2 .........................................................................................574Change faults...... D.6.3.3 ..........................................................................................575Change contours D.6.3.4 ................................................................................................576


www.cadfamily.com


11

Change mesh ..... D.6.3.5 ..........................................................................................577Change features . D.6.3.6 ..............................................................................................578Change captions. D.6.3.7 ...............................................................................................579Change zones .... D.6.3.8 ...........................................................................................580Change grid ........ D.6.4 ........................................................................................581Change grid display D.6.4.2 .................................................................................................582Change display box D.6.4.3 .................................................................................................583Change display plane D.6.4.4 ................................................................................................584Change Granite settings D.6.4.5 .................................................................................................585Show grid contours D.6.4.6 ..................................................................................................586Change survey display D.6.5..................................................................................................587Change menu ..... D.6.6 ..........................................................................................588Change header ... D.6.6.2 ............................................................................................589Change advice.... D.6.6.3 ............................................................................................590Change option .... D.6.6.4 ...........................................................................................591Move options menu D.6.6.5.................................................................................................592Change colour representation D.6.7...................................................................................................593Change locator ... D.6.8 ...............................................................................................594Change hard copy plot options D.6.9 ..................................................................................................595Change view....... D.7 .........................................................................................596Edit XY-plane...... D.7.2 ..........................................................................................597Edit XZ-plane...... D.7.3 ..........................................................................................598Edit YZ-plane...... D.7.4 ..........................................................................................599Display 3D grid ... D.7.5 .............................................................................................600Rotate view......... D.7.6 ........................................................................................601Edit shot line section D.7.7 ..................................................................................................602Map view options D.7.8 ................................................................................................603Overlay maps ..... D.7.8.2 ..........................................................................................604Show 3D map ..... D.7.8.3 ..........................................................................................605Change 3D map display D.7.8.3.8.................................................................................................607Change 3D picture D.7.8.3.9 ..................................................................................................609Arbitrary cross-section D.7.8.4 ..................................................................................................610Map cross-section on grid XZ/YZ view D.7.8.5....................................................................................................611Display map gradient data D.7.8.6 .................................................................................................612Change text for high & low points D.7.8.6.5 .................................................................................................614Display well trajectory data D.7.8.7 .................................................................................................615Edit local grid refinement D.7.9..................................................................................................617Set up digitizing table D.8..................................................................................................618Plot display ......... D.9 .........................................................................................619

Menu Template .............................................................................................................................. 621

File Names.... ................................................................................................................................ 623

Granite Settings ............................................................................................................................ 625Introduction......... ...............................................................................................................................................................625Pens ................... ...............................................................................................................................................................626Markers............... ...............................................................................................................................................................627Wells ................... ...............................................................................................................................................................629Fill areas ............. ...............................................................................................................................................................631Text..................... ...............................................................................................................................................................633

Thickness Correction Factor ....................................................................................................... 635

Digitizing Tables............................................................................................................................ 637Connecting digitizing tables................................................................................................................................................637


www.cadfamily.com


Configuring digitizing tables................................................................................................................................................639Setting up a table from GRID..............................................................................................................................................644

Map Projections ............................................................................................................................ 645Definitions of common terms ..............................................................................................................................................645Choice of map projection ....................................................................................................................................................647Projection facilities ..............................................................................................................................................................648Spheroids (Ellipsoids) .........................................................................................................................................................654

Arithmetic Formulae..................................................................................................................... 657

Dictionary of Abbreviations......................................................................................................... 667Introduction ......... ...............................................................................................................................................................667Verbs .................. ...............................................................................................................................................................668Nouns ................. ...............................................................................................................................................................670

Glossary of Terms ........................................................................................................................ 677

Unit Conversion Factors .............................................................................................................. 683Introduction ......... ...............................................................................................................................................................683Sampling values for simulation grids ..................................................................................................................................685

UKOOA Formats ........................................................................................................................... 687

ConPac Interpolation & Contouring............................................................................................ 689

Use of Configuration Files ........................................................................................................... 695Introduction ......... ...............................................................................................................................................................695SYSTEM section... ...............................................................................................................................................................699GRID section....... ...............................................................................................................................................................700HELP section....... ...............................................................................................................................................................707GRANITE section ...............................................................................................................................................................708

History of Development ............................................................................................................... 709Introduction ......... ...............................................................................................................................................................709New Developments for 2003A ............................................................................................................................................710New Developments for 2002A ............................................................................................................................................711New Developments for 2001A ............................................................................................................................................712New Developments for 2000A ............................................................................................................................................713New Developments for 99A ................................................................................................................................................715New Developments for 98A ................................................................................................................................................719New developments for 97A.................................................................................................................................................721New developments for 96A.................................................................................................................................................725

Index of Options ........................................................................................................................... 729

Index ............. ................................................................................................................................ 739


www.cadfamily.com

GRID Reference Manual New DevelopmentsChanges for 2007.1

13

Chapter 1New Developments

Changes for 2007.1Maintenance of this application is continuing until further notice.


www.cadfamily.com

14 New Developments GRID Reference ManualChanges for 2006.1

Changes for 2006.1Maintenance continues for GRID software.


www.cadfamily.com

GRID Reference Manual New DevelopmentsChanges for 2004A

15

Changes for 2004ANo major modifications have been implemented in GRID since the 2003A release was announced. The following changes have been made for maintenance purposes.

EGRID file exportWhen exporting a grid containing LGRs, the parent grid was reported incorrectly as GRID0001 instead of GLOBAL. This problem has been corrected.

GRID display headerThe display header has been modified slightly, to ensure that the grid size can be read for models with >99 layers.


www.cadfamily.com

16 New Developments GRID Reference ManualChanges for 2004A


www.cadfamily.com

GRID Reference Manual IntroductionOverview

17

Chapter 2Introduction

OverviewGRID is an interactive package providing integrated mapping and gridding facilities for use by geologists, geophysicists and reservoir engineers. The map editing and contouring options, together with options for editing and mapping seismic data, depth conversion and volumetrics, and options for editing and displaying simulation grids, provide a complete environment for model development from exploration mapping right through to simulation grid generation.

GRID users should note that many of the functions provided here are being replaced and extended by the latest SIS product developments:

• A new generation of 3D automatic simulation gridding and upscaling facilities is available in FloGrid. Refer to the "FloGrid User Guide" for more details.

• Additional simulation pre-processing functions are available through ECLIPSE Office. See the "ECLIPSE Office User Guide".

• The SIS GeoFrame software provides a full suite of geological and geophysical applications, mapping and 3D geologic modelling. Contact your local sales and support representative for information.


www.cadfamily.com

18 Introduction GRID Reference ManualGRID functionality

GRID functionalityThe GRID program provides four principal groups of modules:

• Map editing and contouring

• Interpreted seismic data editing

• Volumetrics and depth conversion

• Simulation grid generation

Maps can be digitized from hand drawn or computer drawn maps or can be input as control points, contour lines or regular grid meshes from other mapping packages. Many options are available for editing and manipulating the map data. All editing facilities are fully interactive. A comprehensive selection of map projections is available.

GRID provides facilities for producing quality contour maps from interpreted seismic data, from digitized contour lines or from scattered data points. Options include time-depth conversion of data either at shot point locations or on regular grid meshes. Volumetric analysis is available on structure or isopach maps.

Options for simulation grid generation enable the user to construct a reservoir grid in a form suitable for input to a simulator. Grids can be constructed using conventional block centred geometry, or corner point geometry can be used to construct complex irregular grids.


www.cadfamily.com

GRID Reference Manual IntroductionMapping facilities

19

Mapping facilitiesMaps can be built up using the fully interactive facilities for digitizing and editing or by importing data from third party mapping packages. Map data consist of:

• Contours

(i.e. contour lines, control points or gridded contour data held in a regular mesh)

• Faults

(vertical, sloping, regional and boundary faults)

• Wells

• Features

(e.g. fluid contacts, international boundaries, coastlines etc.)

• Captions

(text annotation)

• Zones

(polygonal areas, depicting lease boundaries, blocks etc.)

Options are available for gridding and contouring back digitized or scattered data at any required contour interval, using contour lines or colour-filled contours. GRID offers full control over sampling and interpolation parameters, to handle problems due to complex surfaces, discontinuities and poorly distributed data. Extensive facilities are provided for arithmetic and logical operations on mesh data.

3-D and cross-section views can be displayed, and high quality hard copy output can be produced on a wide range of plotters.

Additional options include use of different map projections and picture-building facilities, allowing several maps to be overlaid on one display.


www.cadfamily.com

20 Introduction GRID Reference ManualSeismic data

Seismic dataOptions for handling interpreted seismic data include:

• Interactive digitizing and editing of shot lines and seismic sections.

• Input of data from third party interpretation workstations.

• Gridding and contouring of seismic times and depths.

The full power of the sampling and interpolation facilities can be used when creating time and depth maps from a seismic survey.


www.cadfamily.com

GRID Reference Manual IntroductionDepth conversion and volumetrics

21

Depth conversion and volumetricsGRID includes a variety of methods for time-depth conversion for the following types of data:

• Shot points

• Shot lines

• Seismic horizons

• Time maps

Missing data due to pinch-outs or eroded surfaces can be handled by the depth conversion process.

The volumetric analysis facilities can be used with depth or thickness maps. The numerical integration routines can calculate volumes within irregular regional boundaries and can handle vertical or sloping faults. Oil-water contacts and other cut-off levels can be accounted for accurately.


www.cadfamily.com

22 Introduction GRID Reference ManualSimulation grid editing

Simulation grid editingGRID enables 3D reservoir simulation grids to be constructed interactively, using background maps as an aid to the grid design, and provides sampling facilities for defining the grid structure and properties from mapped data.

Simulation grids are constructed using the concepts of coordinate lines and corner depths, allowing block centre or corner point grids to be generated and manipulated. The coordinate line framework allows 3-dimensional grids to be generated with vertical or sloping faults, while maintaining the integrity of the grid.

Facilities for building and editing grids include:

• Regular grid creation(e.g. By specifying vectors of DX and DY values, by marking a boundary box and specifying the number of columns and rows, or by marking a box and entering the column and row positions).

• Corner point grid creation(By manipulating a regular grid or by creating an irregular grid directly).

• Display of background maps, e.g. for the identification of fault traces and feature lines and for ensuring that wells are appropriately separated.

• Interactive display and editing of grids, using an areal view of any layer or a cross-section through any row or column.

• 3-D displays of grid structure.

• Sampling depth and thickness maps for structural definition.

• Splitting grid nodes to model faults, and subdivision and separation of grid layers to represent different strata.

• Sampling maps to obtain block properties, such as porosity, permeability and saturation distributions.

• Colour fill displays and contouring of grid block properties.

• Construction and display of cartesian and radial local grid refinements.

• Definition of regions.

• Definition of active/inactive cells.

• Grid data output to files for direct input to ECLIPSE or other simulation packages (or to the auxiliary program, Fill).

GRID also provides facilities for reading and displaying simulation results. Grid block values can be shown over a sequence of time steps, using block colour fill or contour displays. Alternatively, contours of a particular solution value can be shown at a sequence of time steps on one display (e.g. to show the progress of a water flood front or water coning).

The well trajectory options allow the user to read in well deviation survey data, display well positions overlaid on a simulation grid, and compute the well connection positions. Connection data can be exported as a list of pro-forma WELSPEC and COMPDAT keywords, to be edited for input to ECLIPSE. Alternatively, a trajectory file can be output for use with the Schedule program.


www.cadfamily.com

GRID Reference Manual IntroductionGeneral facilities

23

General facilitiesThe GRID menu system was designed to work on interactive graphical terminals supported by the SIS Granite graphics package, including X-windows workstations and PCs. It also allows the program to run in fully interactive mode during digitizing. On-line Help is available from the menu system.

The graphical display facilities allow 3D displays of mesh maps and simulation grids on any terminal. As well as providing interactive displays, GRID can produce output to a wide range of plotters, including Calcomp, Versatec, HP and colour PostScript devices. CGM metafile output is also supported.

Run files, representing a sequence of interactive operations, can be written and executed by the program. The run files which are created by GRID can be edited using any text editor to allow repetitive tasks (such as sampling a series of maps) to be performed easily. Run files may also be used to set up batch runs.


www.cadfamily.com

24 Introduction GRID Reference ManualGeneral facilities


www.cadfamily.com

GRID Reference Manual Using GRIDIntroduction

25

Chapter 3Using GRID

IntroductionThis chapter gives a short introduction to starting and running GRID. It is recommended that this section of the manual is read before attempting to use the program for the first time. Details on how to perform specific tasks within GRID are given in later sections of this manual.


www.cadfamily.com

26 Using GRID GRID Reference ManualStarting the program

Starting the programDepending on the installation, GRID may be started up from a program launcher window or from a command line. To execute the program from a command line, type the start-up command, e.g. @grid, $grid, or the equivalent for your system. (If you are unsure about the command, contact the person responsible for the program installation at your site.)

The installation may be set up to start automatically in “interactive, with graphics” mode. Otherwise, on start-up, a “pre-menu” will be displayed, as described below. This may be preceded by prompts to select the program version (e.g. 2000A or 2001A).

The “pre-menu” offers the following options:

Interactive, no graphicsOption 1 allows use of the menus and commands in text form, without a graphical display. It gives access to the usual menu options, but pictures can be obtained only via a plotter. (This option was originally intended for use with non-graphical terminals.)

Interactive, with graphicsInteractive, with graphics is the usual mode of execution for GRID. After this option is selected, a simple menu of available graphical devices will appear, and the user should type in the appropriate number for the terminal or workstation being used. The GRID Primary Menu is then displayed, and the user can select options as required.

Execute run file onlyOption 3 may be useful for sampling a series of maps or sending a series of pictures to a plotter.

Show version size and datesOption 4 provides a display showing the maximum workspace available for this version of the program, and the last date of change for GRID and the main software annexes which make up the program.

GRID Version 2001A Baseline: /gss/bsl/source/2001a_w52Locked - Expiry Date 1-jan-2002Please choose type of run :1 : Interactive, no graphics2 : Interactive, with graphics3 : Execute run file only4 : Show version size and datesX : Exit


www.cadfamily.com

GRID Reference Manual Using GRIDStarting the program

27

ExitOption X may also be selected from the pre-menu. This will immediately return the user to the host operating system.

Note that on start-up, the program will search the current directory for a PROFILE.RF file. If it exists this run file will be executed. This facility is very useful for setting up the session defaults (e.g. to load in a particular model).


www.cadfamily.com

28 Using GRID GRID Reference ManualConfiguration file options

Configuration file optionsTo run GRID, the following information must be present in the configuration file:

• A valid password.

• The name of the directory where the GRID help files are kept, together with the full name of the file containing the GRID menu definitions.

• A Granite sub-section defining all the available graphical devices.

The password controls the expiry date for the program.

Further details of configuration file usage are given in Appendix M. If you require assistance in setting configuration file options, please contact customer support.


www.cadfamily.com

GRID Reference Manual Using GRIDGRID terminology

29

GRID terminologyWhen using the GRID package, it is important to understand the terminology used to refer to data entities. The most fundamental term is the term ‘model’, which is used to refer to all the data, maps, surveys and simulation grids, associated with a particular study. Normally, a separate model, preferably in its own directory, should be created for each project undertaken.

A great deal of confusion is caused by the multiple use made of the term ‘grid’ in the oil industry. In the GRID program, three different types of data grid are encountered. These are simulation grids, regular grids for maps, and coordinate grids. To make it apparent which type of grid is being referred to at any time, the program always refers to a simulation grid as a ‘grid’, but refers to a map grid as a ‘mesh’. (Coordinate grids are rarely mentioned as such.)

A full alphabetical list of the meaning of the terms used in the GRID program is given in the "Glossary of Terms" on page 677 at the end of this manual.


www.cadfamily.com

30 Using GRID GRID Reference ManualFile handling

File handlingGRID handles all aspects of file creation and deletion for the files corresponding to the maps, surveys and grids available in a GRID model. The user should never need to edit or delete files which are internal to GRID. However, some maintenance of the files used to transfer data between other packages and GRID may be necessary from time to time. A full list of the files which may be created is given in Appendix B.

Use of unformatted model files is recommended, to reduce disk space requirements and speed up model I/O. Unformatted storage may be selected interactively via menu P.7.3, or by using a PROFILE.RF run file to set the file format on start-up. Alternatively, the default file format can be defined by including the following section in the configuration file:

The Convert utility program can be used to convert GRID model files from unformatted to formatted, or vice versa. It also provides an option to list the physical file names corresponding to the map strata in a GRID model.

Converting pre-98A unformatted PC files to 98A readable unformatted PC filesThe PC versions of 98A GRID, GRAF and ECLIPSE are based on the DEC Visual Fortran compiler and can read unformatted UNIX files. However they can not read unformatted files created for earlier PC versions of the same programs, which were based on the Salford Fortran compiler. These unformatted (binary) files must first be updated using the Bin9798 utility which can be run from an MS-DOS window.

The first step is to change to the directory containing the data, in this example it is called “c:\example\data”. Bin9798 renames this directory, by adding “_BAK_97A” to its name, e.g. “c:\example\data_BAK_97A” will contain pre-98A compatible files. A new directory is created with the original name containing 98A compatible files.

Formatted files and UNIX systems are not affected by this compiler change.

If you require further details on the format and contents of the GRID model files, or on use of the Convert program, please contact customer support.

SECTION GRIDFORMATTED FALSE

> cd c:\example\data> $bin9798


www.cadfamily.com

GRID Reference Manual Using GRIDMenus

31

MenusA menu consists of a series of options displayed down the right hand side of the screen. There are normally up to 9 menu options plus 5 general options which remain the same on each menu. Option 1 is usually the “Return” option which returns the user to the previous level in the menu tree. An exception to this rule is the Primary Menu for which “Exit” is the last option, to prevent the user from exiting the program accidentally.

The general options are:

A menu option may be selected either by moving the graphics cursor or mouse pointer over the box and sending the location or by pressing the appropriate key on the keyboard. Note that no carriage return is necessary when a menu option is selected - GRID responds immediately to the keystroke.

In addition, the following special keys can be used for fast selection of frequently-used options:

These special keys are not shown on the menu, but the user can choose to type the appropriate character when prompted to select a menu option.

Note Some users have special run files, e.g. I.RF for single-key selection. If such a run file is present in the current model directory, it will override the hidden key definition (see Chapter 12).

Advice is given at the bottom of the screen, along with prompts for input data. Information will also be displayed at the bottom of the screen ending with the & character. The & means “Type RETURN to continue”, so that displayed information is held until the user has read it.

• “P” - (Primary) Return to primary menu• “R” - (Run file) Enter run file option• “D” - (Display) Enter display options (See Chapter 13)• “A” - (Abandon) Abandon edits made during this menu entry• “H” - (Help) Show Help on selected option

• “C” - (P.7) “Chg settings”• “I” - (D.7.4) “Edt YZ-plane”• “J” - (D.7.3) “Edt XZ-plane”• “K” - (D.7.2) “Edt XY plane”• “L” - (D.7.9) “Edt LGR”• “M” - (D.7.8) “Map view opts”• “S” - (P.3.7) “Sho values”• “U” - (D.3) “Unzoom”• “Z” - (D.2) “Zoom”• “+” - increment current plane number• “-” - decrement current plane number.


www.cadfamily.com

32 Using GRID GRID Reference ManualMenus

Information about the current GRID session is continuously updated in the header box at the top of the screen. The current menu position in the program hierarchy is indicated in the top right hand corner of the screen (e.g. P.2.4.3). When some options are selected, e.g. adding a contour, the header information is temporarily overwritten by information about the current option.


www.cadfamily.com

GRID Reference Manual Using GRIDX-Windows displays

33

X-Windows displaysWhen GRID is running under X-windows, the Granite device driver opens a new window, in which all interactive operations are performed. The menu options can be accessed as usual, by typing characters on the keyboard or moving the mouse.

It is possible to move or resize the Granite window, via the normal window management operations of the workstation. When a window is resized or exposed, GRID automatically refreshes the model display, after checking the current screen dimensions and reinitialising the display boxes as necessary.

On workstations where back-up storage is available for the display, the Granite window need not be refreshed unless the window size changes. Unnecessary redrawing can be avoided by setting the keyword REPAIR to FALSE in the appropriate section of the configuration file.

Configuration file options can also be used to select the preferred start-up position and font style, e.g.:

SECTION GRANITESUBSECT DRIVER 29SELECT TRUENAME XWINDOW DESCRIPT NCD X-terminalXWDMIN 0.140YWDMIN 0.220XWDMAX 0.99YWDMAX 0.97FONTS *Cour*-r-*REPAIR FALSE


www.cadfamily.com

34 Using GRID GRID Reference ManualDigitizing tables

Digitizing tablesWhen a digitizing table is being used the function of the cross-hairs is replaced by the digitizing cursor. Menu options can be selected by pressing the appropriate buttons on the cursor. On some cursors there may not be sufficient buttons for each of the menu options, and in this case the menu template in Appendix A can be used. The user digitizes three corners of the box containing the options menu, which can be placed anywhere on the table. Menu options can then be selected by digitizing a point in the appropriate box or by pressing the appropriate cursor button.

The digitizing table will primarily be used during the map editing stage. However, it can also be used when editing or creating grids. In the latter case it will not always be convenient to use Button 1 when a digitized point is requested, since this would override the current option. The user should in these cases use button 0, or button 10.

The set-up procedures available for digitizing tables are described in Appendix E.


www.cadfamily.com

GRID Reference Manual Using GRIDFurther help and advice

35

Further help and adviceYou should now be familiar with the basic operation of the program and know how to select options from a menu.

A description of each menu option is given in the following chapters of this manual. This information can also be displayed during a GRID session, via the on-line Help facility. A structure chart of the menu hierarchy is issued with this manual.

Please contact customer support if you require further help and advice, details of training courses or assistance with a particular modelling problem.


www.cadfamily.com

36 Using GRID GRID Reference ManualFurther help and advice


www.cadfamily.com

GRID Reference Manual Primary Menu and Edit ModelIntroduction

37

Chapter 4Primary Menu and Edit Model

IntroductionA model refers to the complete collection of data (maps, grids and surveys) used in GRID for a particular project. A model must be created or loaded into the current session before any of its associated maps, simulation grids or surveys can be edited.

When any of the first 6 options on the primary menu are selected, if no model is loaded (e.g. at the start of a session, or if the model has just been cleared) the user is prompted for the model name.

The program checks whether the requested model exists in the current user directory and if it does exist then the model specification file is loaded and its associated data displayed on the screen. (The model name may optionally be entered as a file path name, including directory. The directory specified will then become the default directory for GRID files used in the current program session.) If the model does not exist, the user is prompted to create a new model (see option P.1, “Edt model”, page 39).

When a model is created, a corresponding model file is written to disk (see Appendix B for details of the file naming convention). A history file is also created, to record the time, date and user name at model creation, followed by any subsequent changes to the model data.

After a model has been created or loaded, the screen is refreshed and the model area is highlighted by a box. Note that the box is drawn to give the largest possible display area whilst keeping the x and y coordinates scaled in the same proportion.


www.cadfamily.com

38 Primary Menu and Edit Model GRID Reference ManualThe Primary menu

The Primary menuThe first menu that is presented on entering the GRID program is the Primary Menu. The menu options are as follows:

Selecting one of the primary options 1-8 will lead to another menu. The GRID menu structure is hierarchical (see the structure chart supplied with this manual, ../../grid_charts/Primary_Menu_Structure.pdf). The current menu position in the tree is displayed at the top right-hand corner of the screen (e.g. P.2.4.3). The menu position number corresponds to the option number shown on the relevant page of this manual.

The user can terminate the program and return to the host operating system, by selecting option 9 (Exit).

It is possible to return directly to the Primary Menu from any other menu in the Primary tree by selecting the general option P. (Selecting P from the Run Files menu, the Display Options, or any option selected via a special key, results in a return to the last menu visited in the Primary tree.) On returning to the Primary Menu, the user is prompted to save the current map, grid or survey which is being edited. (It is often useful to do this periodically during long editing sessions.)

Help on the options within a menu can be obtained by selecting the general option H and then indicating the option for which help is required.

Table 4.1 The Primary menu

Option Function

1 Edt model

2 Edt map

3 Edt grid

4 Sim results

5 Edt survey

6 Map utils

7 Chg settings

8 Clr wrkspc

9 Exit

Edit model

Edit map

Edit grid

Simulator results

Edit survey

Map utilities

Change settings

Clear workspace

Exit


www.cadfamily.com

GRID Reference Manual Primary Menu and Edit ModelEdit model P.1

39

Edit model P.1

Edt model

PurposeEdit the model or change the model parameters.

DescriptionIf the model does not exist the user is asked whether a new model is to be created with the given name. If a model is to be created, the user is prompted for the following parameters:

A description of the map projections available with GRID is given in Appendix F of this manual. If a projection is associated with the model, then the lat/long extent of the model will be prompted for and the smallest area containing the lat/long extent calculated in map coordinates. The calculated values will be presented to the user as defaults for the model area. It is expected that the calculated values will be rounded to suitable values by the user.

Areal map units may be either feet or metres (unless a projection is specified, in which case they are metres).

After a model has been loaded, the following menu is displayed:

The “Return” option returns the user to the Primary menu. Each of the other options is described in the relevant help section.

Default projectionMinimum lat/long coordinates (if a projection is defined)Maximum lat/long coordinates (if a projection is defined)Areal map unitsMinimum x,y coordinatesMaximum x,y coordinatesDefault number of mesh rows and columnsNumber of model strata

Table 4.2 Menu P.1

Option Function

1 Return

2 Del model

3 Chg model

4 Lst history

5 Out mod rpt

Delete model

Change model

List history

Output model report


www.cadfamily.com

40 Primary Menu and Edit Model GRID Reference ManualDelete model P.1.2

Delete model P.1.2

Del model

PurposeDelete data from the model.

DescriptionThe following menu is displayed:

The “Return” option returns the user to the “Edt model” menu options. Each of the other options is described in the relevant help section.

Table 4.3 Menu P.1.2

Option Function

1 Return

2 Del stratum

3 Del map

4 Del grid

5 Del survey

Delete stratum

Delete map

Delete grid

Delete survey


www.cadfamily.com

GRID Reference Manual Primary Menu and Edit ModelDelete stratum P.1.2.2

41

Delete stratum P.1.2.2

Del stratum

PurposeDelete a map stratum from the model.

DescriptionThe user is prompted for the name of the map from which the stratum is to be deleted and for the stratum number to be deleted. A menu of current map names and a menu of strata for the selected map can be obtained by typing ‘H’ for help.

Confirmation from the user is required to delete the map stratum.

If the stratum is deleted, it will no longer be available to the model and the corresponding disk file will be deleted.


www.cadfamily.com

42 Primary Menu and Edit Model GRID Reference ManualDelete map P.1.2.3

Delete map P.1.2.3

Del map

PurposeDelete a map and all its strata from the model.

DescriptionThe user is prompted for the name of the map to be deleted. A menu of current map names can be obtained by typing ‘H’ for help.

Confirmation from the user is required to delete the map.

If the map is deleted then it will no longer be available to the model, all the map strata and their corresponding files are removed from the disk.


www.cadfamily.com

GRID Reference Manual Primary Menu and Edit ModelDelete grid P.1.2.4

43

Delete grid P.1.2.4

Del grid

PurposeDelete a simulation grid.

DescriptionThe user is prompted for the name of the grid to be deleted. A list of the current grids in the model can be obtained by typing ‘H’ instead of a grid name.

Confirmation from the user is required to delete the grid.

If a grid is deleted, it will no longer be available to the model and the corresponding disk file will be deleted.

If the deleted grid is currently loaded, it will be cleared from memory and from the display.


www.cadfamily.com

44 Primary Menu and Edit Model GRID Reference ManualDelete survey P.1.2.5

Delete survey P.1.2.5

Del survey

PurposeDelete a survey from the model.

DescriptionThe user is prompted for the name of the survey to be deleted. A list of the current surveys in the model can be obtained by typing ‘H’ instead of a survey name.

Confirmation from the user is required to delete the survey.

If the survey is deleted, it will no longer be available to the model and the corresponding disk file will be removed from the disk.


www.cadfamily.com

GRID Reference Manual Primary Menu and Edit ModelChange model P.1.3

45

Change model P.1.3

Chg model

PurposeChange data within the model.


The “Return” option returns the user to the “Edt model” menu options. Each of the other options is described in the relevant help section.


Option Function

1 Return

2 Chg map nmes

3 Chg map str

4 Chg map unit

5 Chg mod area

6 Chg mod str

7 Chg mesh dat

Change map names

Change map stratum

Change map units

Change model area

Change number of strata

Change mesh data


www.cadfamily.com

46 Primary Menu and Edit Model GRID Reference ManualChange map name P.1.3.2

Change map name P.1.3.2

Chg map nmes

PurposeChange a map name.

DescriptionThe user is prompted for the map name to be changed. It is not possible to rename maps associated with surveys, nor is it possible to rename maps for individual strata. A check is made to ensure that the new map name supplied does not already exist within the model.

User confirmation is required to change the map name.


www.cadfamily.com

GRID Reference Manual Primary Menu and Edit ModelChange map stratum P.1.3.3

47

Change map stratum P.1.3.3

Chg map str

PurposeChange a map stratum number.

DescriptionThe user is prompted for the map name and stratum number to be changed. It is not possible to change stratum numbers associated with surveys. A check is made to ensure that the new stratum number supplied does not already exist within the map.

User confirmation is required to change the stratum number.


www.cadfamily.com

48 Primary Menu and Edit Model GRID Reference ManualChange map units P.1.3.4

Change map units P.1.3.4

Chg map unit

PurposeChange map units.

DescriptionThe user is prompted for the map name for which for which the map units are to be redefined.

It is not possible to change map units for maps associated with surveys, nor is it possible to change map units for an individual map stratum. A check is made to ensure that the new map units are valid.

User confirmation is required to change the map units.


www.cadfamily.com

GRID Reference Manual Primary Menu and Edit ModelChange model area P.1.3.5

49

Change model area P.1.3.5

Chg mod area

PurposeChange the model area.

DescriptionThe model area is the area displayed on the screen delimited by the coordinate box (default colour green). Each map stratum also has its own user defined area which may be different from the model area.

The user is prompted for the minimum and maximum coordinates of the required area. If a projection exists for the model, the area must be supplied in latitude and longitude, and the program will automatically calculate a coordinate box to enclose the area. The eastings and northings of this box may be redefined by the user.

If the model area is changed, the user is prompted whether or not to redraw the screen.

When data are plotted, output is automatically clipped to the model area, unless clipping is disabled via option D.6.9.8 (“Chg clipping”, see page 595).

Note that sometimes changes to the model area can lead to errors in map displays and sampling, if the X,Y origin for the new model area is different from the areas defined for existing maps.


www.cadfamily.com

50 Primary Menu and Edit Model GRID Reference ManualChange number of model strata P.1.3.6

Change number of model strata P.1.3.6

Chg mod str

PurposeChange the number of model strata.

DescriptionThe user is prompted for the number of strata required.

The number of strata can only be increased (or left unchanged).


www.cadfamily.com

GRID Reference Manual Primary Menu and Edit ModelChange mesh data P.1.3.7

51

Change mesh data P.1.3.7

Chg mesh dat

PurposeChange the default number of mesh rows and columns.

DescriptionThe user is prompted for the new default number of mesh rows and columns. The row and column numbers specified will be the defaults used when subsequent meshes are calculated.


www.cadfamily.com

52 Primary Menu and Edit Model GRID Reference ManualList history file P.1.4

List history file P.1.4

Lst history

PurposeList the history file for the current model.

DescriptionThe screen is cleared and the history file is listed to the screen. The current picture will be redrawn after the complete file has been listed.


www.cadfamily.com

GRID Reference Manual Primary Menu and Edit ModelOutput a model report P.1.5

53

Output a model report P.1.5

Out mod rpt

PurposeOutput a file giving the current status of the model.

DescriptionA file called ‘modelname.RPT’ will be output to the current root directory.

The report will list the model area and units, the model projection parameters (if a projection is being used), and all maps, grids and surveys associated with the model.


www.cadfamily.com

54 Primary Menu and Edit Model GRID Reference ManualOutput a model report P.1.5


www.cadfamily.com

GRID Reference Manual Edit MapIntroduction

55

Chapter 5Edit Map

Introduction

Map dataA map contains data such as contour lines and fault traces which define a surface, as well as cultural information such as feature lines, well locations and captions. The “Edt map” menu gives access to options for editing the following types of data:

• Wells

• Faults

• Contours

• Mesh Data

• Features

• Captions

• Zones

• Legend

Specifying map namesA map name used in a GRID model consists of up to 8 characters. There are a few restrictions on map names, to avoid conflict with arithmetic expressions that may be used in the parser: (e.g. symbols such as + and names such as LOG are not allowed). See the discussion of the P.2 “Edt map” menu on page 57 for a full list of restrictions.

A single map name, such as TOPS, may be used to refer to a number of different maps by means of a secondary parameter called the stratum number. This allows data to be stored in a structured manner, with each stratum number corresponding to a layer of the model. (Note that it is not necessary to define data for every model layer, for a particular map name.)


www.cadfamily.com

56 Edit Map GRID Reference ManualIntroduction

Whenever a prompt for a map is issued the user may respond either by giving the name of the map only, in which case a second prompt will be issued for the stratum number, or else by entering the map name with the stratum number in parentheses, e.g. TOPS(1) refers to stratum 1 of a map called TOPS.

It is also possible that the map is an auxiliary map for a survey, in which case the stratum number may also be qualified by the letter T for times or D for depths.

If ‘H’ is typed instead of a map name, a help menu will be displayed, listing all the map names defined in the model, and one of these can be selected from the menu. Similarly, help can be requested when selecting a stratum, resulting in a menu list of all the strata defined for the current map.

Map unitsWhen a new map is created, the areal units used will be the default units defined for the model. The user will be prompted for map units, which are the units used for Z-values (e.g. contours).

Valid units are:

(See Appendix J for unit conversion factors used in the model.)

If you need to create a map of data for which none of the valid units appear to be appropriate, choose FRACTION. This allows any numerical values to be included in the map data (not just fractional values).

METRES FEET CM KM KFT

MDARCY DARCY

FRACTION PERCENT

MSEC SEC M/SEC

M3 ACRE-FT STB RB MCF


www.cadfamily.com

GRID Reference Manual Edit MapEdit map P.2

57

Edit map P.2

Edt map

PurposeCreate a new map or edit an existing map.

DescriptionAfter a map stratum has been read or created, the following menu is displayed:

The user is prompted for the name of the map to be edited and for its stratum number.

The map name and its stratum number may be specified in the short form: Map_name(Stratum_number), e.g. TOPS(1)

If an unrecognised map name is given, the user is asked whether a new map is to be created. The user will be asked to give the units for contour values for the map and whether the map is to be areal or cross- sectional.

The following are invalid characters, and are not allowed in map names:

+, -, *, /, =

The following are invalid map names, and are not allowed within the program, as these names will conflict with the use of the parser:

SQRT, SIN, COS, TAN, LOG, LN, EXP, ABS, INT, NULL

IF, THEN, ELSE, ENDIF, EQ, GT, GE, LT, LE, NE, OR, AND

The stratum number must then be given (if it has not already been entered in parentheses). If the given stratum already exists, it will be read from disk, otherwise the user will be asked whether a new stratum is to be created. Any stratum number may be used up to the current maximum number of strata specified for the model. (This limit may be increased from the Edit Model menu). The map area is requested for each new stratum (default is the model area).

A single .Lnnnn (or .Mnnnn) file is created for the new stratum.

Table 5.1 Menu P.2

Option Function

1 Return

2 Edt wells

3 Edt faults

4 Edt contours

5 Edt mesh

6 Edt features

7 Edt captions

8 Edt zones

9 Edt legend

Edit wells

Edit faults

Edit contours

Edit mesh (i.e. gridded contour data)

Edit features

Edit captions

Edit zones

Edit legend


www.cadfamily.com

58 Edit Map GRID Reference ManualEdit map P.2

Whenever a map is loaded the user can choose whether its contours should be drawn. If contour information is not required, some time can be saved by not drawing them. Note that the contour display can be toggled on/off during editing, by use of the Display menu option D.6.3.4 “Tog contours” (see page 576).

When the “Return” option is selected from the “Edt map” menu the user is asked whether to save the current map on disk and is returned to the Primary menu.

If the map is saved the existing file for this stratum will be overwritten and an entry made in the model history file. Additional comments may be entered into the history file, as required.

If the map is not saved it remains the current map and may be saved on a subsequent occasion. In order to return to the unedited map it must first be cleared from the model using the P.8 “Clr wrkspc” menu (see page 540) and re-loaded from disk.


www.cadfamily.com

GRID Reference Manual Edit MapEdit wells P.2.2

59

Edit wells P.2.2

Edt wells

PurposeEdit the wells on the current map.


The “Return” option returns the user to the “Edt map” menu. Each of the other options is described in the following sections.

If the “Abandon” option is selected then any edits made during the current entry to the “Edt wells” option will be discarded.


Option Function

1 Return

2 Cpy wells

3 Add well

4 Del well

5 Chg wells

6 Inp wells

7 Out wells

8 Def granite

9 Chg granite

Copy wells

Add well

Delete well

Change wells

Input wells

Output wells

Define granite settings

Change granite settings


www.cadfamily.com

60 Edit Map GRID Reference ManualCopy wells P.2.2.2

Copy wells P.2.2.2

Cpy wells

PurposeCopy the wells from another map stratum onto the current map stratum.

DescriptionThe user is prompted for the map name and the stratum number from which to copy the wells. The wells and their granite settings will be copied from the given map onto the current map.

It is not possible to copy wells if the current map already has one or more wells defined on it.


www.cadfamily.com

GRID Reference Manual Edit MapAdd well P.2.2.3

61

Add well P.2.2.3

Add well

PurposePosition a new well symbol on the current map.

DescriptionThe user is prompted for the name of the new well to be added. If no name is required enter RETURN.

Well names are not displayed by default, but can be shown by selecting the display option D.6.3.2.3, “Tog wll nmes” (see page -574).

It is possible to define the well location in latitude & longitude, eastings & northings or by digitizing the position of the well.

If the well location is defined by latitude & longitude or eastings & northings then a check is made to see that it is within the model limits.

Data (Z) values are NOT stored at well locations. Well values should be defined by entering single point contours on the appropriate maps using the “Edt contours” options, from menu P.2.4 (see page -103).

The well symbol will be displayed on the map using the current granite settings defined in the “Def granite” option.

The symbol and text representations for individual wells can be changed using the “Chg granite” option.


www.cadfamily.com

62 Edit Map GRID Reference ManualDelete well P.2.2.4

Delete well P.2.2.4

Del well

PurposeDelete well(s) from the current map.

DescriptionThe user is asked for the name of the well to be deleted.

If an asterisk ‘*’ is entered, all the wells on the map will be deleted upon confirmation by the user.

If the letter ‘Q’ is entered, each well will be highlighted in turn and the user can select to delete the well or not. Sequencing through the wells can be ended by entering the letter ‘E’.

If no name is entered then the user is asked to select the well to be deleted from the map, by digitizing a point close to the well on the screen. The well is highlighted by a cross and confirmation is requested to delete it.

Note that if the well location that has been deleted has an associated data (Z) value then it is important to ensure that the data value is also deleted using the “Del contours” option.


www.cadfamily.com

GRID Reference Manual Edit MapChange wells P.2.2.5

63

Change wells P.2.2.5

Chg wells

PurposeChange or move the wells on the current map.


The “Return” option returns the user to the “Edt wells” menu. Each of the other options is described in the following sections.

If the “Abandon” option is selected then any edits made during the current entry to the “Edt wells” option will be discarded.

Table 5.2 Menu P.2.2.5

Option Function

1 Return2 Chg wel nam3 Mov well

Change well namesMove wells


www.cadfamily.com

64 Edit Map GRID Reference ManualChange well name P.2.2.5.2

Change well name P.2.2.5.2

Chg wel nam

PurposeTo change the name of a well on a map.

DescriptionThe user is asked to select a well to be changed and then prompted for the well name. Press the RETURN key to leave the current well name unchanged.


www.cadfamily.com

GRID Reference Manual Edit MapMove well P.2.2.5.3

65

Move well P.2.2.5.3

Mov well

PurposeMove a well from an existing location to a new location on the current map.

DescriptionThe user is asked to select the well on the map to be moved. The well is highlighted by a cross and the user is asked whether to define the new well location by latitude & longitude, eastings & northings or by digitizing a point.

If the new well location is defined by latitude & longitude or eastings & northings then a check is made to see that it is within the model limits.

The well will then be deleted from the old location and redrawn at the new location.

Note Note that if the well location that has been moved has an associated data (Z) value then it is important to ensure that the data value is also moved to the new location.


www.cadfamily.com

66 Edit Map GRID Reference ManualInput wells P.2.2.6

Input wells P.2.2.6

Inp wells

PurposeInput well locations from a data file onto the current map, clipping to the model area if required.

DescriptionWells may be read in addition to any that already exist on the map.

The user is prompted for the name of the file containing the well locations and whether it is required to clip the data to the model area.

The first line of the data file will then appear at the bottom of the screen and the new menu will allow the user to skip through the file and view the data. The option “Next line” should be selected to skip any header records until the first well location is displayed. Data input will commence with the current record being displayed when the option “Return” is selected.

Three columns of data are expected on each record:

or

If the first character of the first record in the file is a * or (, then it is assumed to be a format statement, e.g. (A8,2F12.3), and it will be the default when the user is prompted for the input format. If the first record is not a format statement then the default input format will be list directed ‘*’.

If list directed input is used then the file should be in the form:

where the well name is in single quotes.

Otherwise, if a user specified format e.g. (A8,2F12.5) or (2F12.5,A8) is defined, then the program will automatically read the well name first or last depending upon the position of the character specifier ‘A’ within the Fortran format.

If a user specified format is given, a check is made to ensure the format statement is enclosed within brackets. If it is not, brackets will be added.

Each well will be displayed on the map as it is read into the program. Wells will be displayed on the map using the current granite settings defined in the “Def granite” option.

Well names are not displayed by default but can be shown by selecting the display option D.6.3.2.3, “Tog wll nmes” (see page -574).

The symbol and text representations for individual wells can be changed using the “Chg granite” option.

When input is complete, the user is informed of the number of wells that were read. If input data has been clipped, then the number of wells in the file and the number of wells actually input to the model is returned.

X-location Y-location Well name

Well name X-location Y-location

X-location Y-location ‘Well name’


www.cadfamily.com

GRID Reference Manual Edit MapInput wells P.2.2.6

67

Well locations that are in LATITUDE & LONGITUDE may be read using the UKOOA format or in DEGREES format for decimal degrees. These are described in Appendix K.

ExampleA file called ECL.WEL contains six wells to be input to the current map. The file ECL.WEL looks like:

The required menu options would be:

RECORD 1:(2F12.3,A8)RECORD 2: 273926.406 320046.062 P01RECORD 3: 278242.468 327856.593 P02RECORD 4: 282516.062 336018.000 P03RECORD 5: 296861.000 349817.812 P04RECORD 6: 310834.437 357874.281 P05RECORD 7: 326619.687 361741.531 P06

"Edt wells""Inp wells"'Enter name of file to be read...' ( ECL.WEL is entered )'Clip input data ? (y/N)' ( N is entered )"Next line" ( to skip format line )"Return" ( 1st well

location shown )'Enter record format, e.g. (2E13.5,A8) or RETURN for (2F12.3,A8)'

( RETURN to read file )6 wells read...&


www.cadfamily.com

68 Edit Map GRID Reference ManualOutput wells P.2.2.7

Output wells P.2.2.7

Out wells

PurposeOutput well locations from the current map to a data file, clipping to the model area or a polygon, if required.

DescriptionThe user is prompted for the root name of the file to be opened for output. The output file will be given the name ‘root.WEL’.

The user is then asked if it is required to clip the output data. If clipping is selected, the choice must be made to clip to the model area or to a digitized polygon.

It is possible to output wells in any appropriate format. Each output record will contain three pieces of information in either of the following orders:

or

List directed output ‘*’ is the default. However, the user may specify an output format, e.g. (A8,2F12.5) or (2F12.5,A8) and the program will automatically output the well name first or last depending upon the position of the character specifier ‘A’ within the Fortran format.

Note For list directed output, the well name will appear in single quotes, e.g. ‘Well-1’.


The first record to be written to the output file is the format used. Subsequent records will contain the well data in the specified format.

When output is complete, the user is informed of the number of wells that were written to the file. If output data has been clipped, then the number of wells on the map and the number of wells actually output is returned. Well locations may also be output in latitude & longitude using the UKOOA format or in DEGREES format for decimal degrees. These are described in Appendix K.

ExampleA map contains six wells to be output to a file called ECL.WEL using the format (2F12.3,A8). No clipping is required.

X-location Y-location Well name

Well name X-location Y-location


www.cadfamily.com

GRID Reference Manual Edit MapOutput wells P.2.2.7

69

The required options would be:

The file ECL.WEL will look like:

"Edt wells""Out wells"'Enter output file root' ( ECL is entered )File ECL.WEL opened...&'Clip output data to model area ? (y/N)' ( N is entered )'Enter record format, e.g.. (2E13.5,A8)' ( (2F12.3,A8) is entered )6 wells output...&

RECORD 1:(2F12.3,A8)RECORD 2: 273926.406 320046.062 P01RECORD 3: 278242.468 327856.593 P02RECORD 4: 282516.062 336018.000 P03RECORD 5: 296861.000 349817.812 P04RECORD 6: 310834.437 357874.281 P05RECORD 7: 326619.687 361741.531 P06


www.cadfamily.com

70 Edit Map GRID Reference ManualDefine Granite settings P.2.2.8

Define Granite settings P.2.2.8

Def granite

PurposeDefine the well symbol and text representation to be used when new wells are added to the current map or input from a data file.


The “Return” option returns the user to the “Edt wells” menu and the map will be redrawn if necessary. Each of the other options leads to a further menu for setting Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current default Granite attributes for the well symbol or well text. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.

Note This menu changes the default settings to be used for new wells. To change an existing well, use the “Chg granite” option.


Option Function

1 Return

2 Def wll sym

3 Def wll txt

Define well symbol

Define text for well name


www.cadfamily.com

GRID Reference Manual Edit MapChange Granite settings P.2.2.9

71

Change Granite settings P.2.2.9

Chg granite

PurposeChange the well symbol and text representation used to draw and label an existing well on the current map.

DescriptionThe user is asked to select the well on the map for which the Granite settings are to be changed. The well is highlighted by a cross and the following menu is displayed:

The “Return” option returns the user to the “Edit wells” menu and redraws the selected well using the new representations. Each of the other options leads to a further menu for setting Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current Granite attributes for the selected well symbol or well text. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.

This menu changes the Granite settings to be used for an existing well. To change the parameters to be used for creating a new well, use the “Def granite” option.


Option Function

1 Return

2 Chg wll sym

3 Chg wll txt

Change well symbol

Change text for well name


www.cadfamily.com

72 Edit Map GRID Reference ManualChange Granite settings P.2.2.9


www.cadfamily.com

GRID Reference Manual Edit MapEdit faults P.2.3

73

Edit faults P.2.3

Edt faults

PurposeEdit the faults on the current map.


Faults are represented by lines or areas on the map. They form boundaries to the interpolation procedure when sampling a map. The correct representation of faults on the map is essential to getting proper interpolated results.

It is recommended that fault traces are digitized before contour lines to help ensure that contours do not stray across faults. (It is not necessary for contours to be digitized all the way up to faults.)

If the contour map is in the form of a grid mesh then the faults should correspond to those used in the original gridding process. The “Cpy faults” option is convenient in this case to ensure that precisely the same fault traces are used.

Only two line styles are used for all the faults on the map. One style is used for major fault segments (default is dashed) and one style is used for minor fault segments (default is dotted). The use of major and minor fault segments is described in the section on “Add faults” (see page 75).

The “Return” option returns the user to the “Edt map” menu. Each of the other options is described in the following sections.

If the “Abandon” option is taken then any edits made during the current entry to the “Edt faults” option will be discarded.


Option Function

1 Return

2 Cpy faults

3 Add fault

4 Del fault

5 Chg fault

6 Inp faults

7 Out faults

8 Def granite

Copy faults

Add fault

Delete fault

Change fault

Input faults

Output faults



www.cadfamily.com

74 Edit Map GRID Reference ManualCopy faults P.2.3.2

Copy faults P.2.3.2

Cpy faults

PurposeCopy the faults from another map stratum onto the current map stratum.

DescriptionThe user is prompted for the map name and the stratum number from which to copy the faults.

The faults and their granite settings will be copied from the given map onto the current map.

It is not possible to copy faults if the current map already has one or more faults on it.


www.cadfamily.com

GRID Reference Manual Edit MapAdd fault P.2.3.3

75

Add fault P.2.3.3

Add fault

PurposeDigitize a fault trace onto the current map.

DescriptionThe user is prompted for the name of the fault to be digitized. If no name is required enter RETURN.

Fault names are not displayed by default, but can be shown by selecting the display option D.6.3.3.3, “Tog flt nmes” (see page 575).

The user is then prompted for the type of fault trace. Four types of fault trace are available:

1 Vertical Fault

The fault trace consists of a single line from one end of the fault to the other. A vertical fault will normally consist of a single major fault segment.

2 Sloping Fault or Region Fault

The fault trace consists of a closed line, digitized continuously around the edge of the fault.

Sloping faults should be built from sections of major and minor fault segments (see discussion below). The usual recommended convention when digitizing sloping faults, is to put major segments along the upthrown side and minor segments on the downthrown side.

For a Region Fault, the fault trace should be digitized continuously around the edge of the region as a single major segment. The first and last points of the fault will automatically be joined to close the region. The interior and exterior of the region will be treated separately for contouring and interpolation.

3 Boundary Fault

The fault trace should be digitized continuously around the edge of the boundary as a single major segment. The first and last points of the fault will automatically be joined to close the boundary. Gridding is limited to interior of the given boundary and provides an effective means of limiting a contour map to avoid edge effects due to over-extrapolation.

4 Slope Discontinuity

This is a single line representing a significant change of slope, but with no associated throw. The line should not be closed. This type of discontinuity can be seen as a front on weather maps, but is not widely used in geological models.

If a non-vertical fault is being added to the map, the user will be asked if it is required that the fault be a mask to mesh colour fill.

All types of fault may be built from three types of line:

1 Major segments are treated as barriers to the interpolation algorithm and as discontinuities to the contouring algorithm.

2 Minor segments are transparent during interpolation but are still treated as discontinuities for contouring.


www.cadfamily.com

76 Edit Map GRID Reference ManualAdd fault P.2.3.3

3 Grid segments are major fault segments but are defined by moving along simulation grid lines. Grid segments may be used to put ‘zig-zag’ faults on to maps.

Option P.2.3.5.5, “Chg flt seg” (see page 82), allows segments of a fault trace to be redefined as major or minor.

As the fault trace is digitized, it will appear on the screen as a white line, when digitizing is finished and the user returns to the “Edt fault” menu, the fault trace will be re-drawn using the current granite settings defined in the “Def granite” option.

Note Note that proper use of major and minor fault segments is essential when sampling maps in conjunction with simulation grids. (See description of the split nodes option, P.3.5.7, “Spl nodes” on page 332.)


www.cadfamily.com

GRID Reference Manual Edit MapDelete faults P.2.3.4

77

Delete faults P.2.3.4

Del fault

PurposeDelete fault(s) from the current map.

DescriptionThe user is asked for the name of the fault to be deleted.

If an asterisk ‘*’ is entered then all the faults on the map will be deleted upon confirmation by the user.

If the letter ‘Q’ is entered then each fault is highlighted in turn and the user can select to delete the fault or not. Sequencing through the faults can be ended by entering the letter ‘E’.

If no name is entered, the user is prompted to select a fault to be deleted from the map, by digitizing a point close to the fault on the screen. The fault is highlighted and confirmation is requested to delete it.


www.cadfamily.com

78 Edit Map GRID Reference ManualChange fault P.2.3.5

Change fault P.2.3.5

Chg fault

PurposeChange a fault name, type or colour fill mask, change major or minor fault segments, or change or operate on fault trace lines.


The “Return” option returns the user to the “Edt faults” menu. Each of the other options is described in the relevant help sections.


Option Function

1 Return

2 Chg flt nam

3 Chg flt typ

4 Chg flt msk

5 Chg flt seg

6 Chg flt trc

7 Opr flt trc

Change fault name

Change fault type

Change fault colour fill mask

Change fault segment

Change fault trace

Operate on fault traces


www.cadfamily.com

GRID Reference Manual Edit MapChange fault name P.2.3.5.2

79

Change fault name P.2.3.5.2

Chg flt nam

PurposeTo change the name of a digitized fault.

DescriptionThe user is asked to select a fault to be changed and then prompted for the fault name. Press the RETURN key to leave the current fault name unchanged.


www.cadfamily.com

80 Edit Map GRID Reference ManualChange fault type P.2.3.5.3

Change fault type P.2.3.5.3

Chg fault typ

PurposeTo change the type of a digitized fault to vertical, sloping/region or boundary fault.

DescriptionThe user is asked to select a fault to be changed and then prompted for the fault type. Hit the RETURN key to leave the current fault type unchanged.

The main fault types are VERTICAL (suitable for a single fault trace line), SLOPING (or REGION) or BOUNDARY fault (suitable for closed fault traces) and slope DISCONTINUITY. If the user tries to change to an inappropriate fault type, a warning is given. The colour mask status of a fault will be preserved when changing between SLOPING/REGION and BOUNDARY types.

See the description of “Add fault” (P.2.3.3, page 75) for further information on fault types.


www.cadfamily.com

GRID Reference Manual Edit MapChange fault colour fill mask P.2.3.5.4

81

Change fault colour fill mask P.2.3.5.4

Chg flt msk

PurposeTo toggle a fault from being colour fill masked or not.

DescriptionThe user is asked for the name of the fault to be masked / unmasked. If no name is entered then the user is asked to select the fault on the map to be masked / unmasked by digitizing a point close to the fault on the screen. The fault is highlighted and confirmation is requested to colour fill mask / unmask it.

Note Note that this option is used for selective colour fill within regional or boundary faults. Vertical faults cannot be colour fill masked.


www.cadfamily.com

82 Edit Map GRID Reference ManualChange fault segment P.2.3.5.5

Change fault segment P.2.3.5.5

Chg flt seg

PurposeRedefine part of a fault trace to be a major or minor segment.

DescriptionThe user is prompted to select the endpoints of the fault section to be changed. The endpoints of the selected section are highlighted and the user is asked whether the section is to be a major or minor segment. If RETURN is entered, the section is left unchanged.

The fault will be redrawn using the granite settings defined in the “Def granite” option, appropriate to the new fault segmentation type.


www.cadfamily.com

GRID Reference Manual Edit MapChange fault trace P.2.3.5.6

83

Change fault trace P.2.3.5.6

Chg flt trc

PurposeRedigitize a section of a fault trace on the current map.

DescriptionThe user is prompted to select the endpoints of the fault section to be changed. The endpoints of the selected section are highlighted and the section is erased from the display.

Confirmation is requested to proceed with the change. If the change is continued, part of the remaining fault trace is highlighted, together with the start point from which redigitizing should start.

If the original fault was closed, the section to be changed will be selected according to the shortest distance around the closed polygon. After redigitizing, if the fault is a sloping, regional or boundary fault and the new line is not closed, the user will be prompted to close the fault. If it is decided not to close the fault, the fault type will change to vertical.

(See also option P.2.3.5.7.4, “Close flts” on page 87 to close a fault polygon, and option P.2.3.5.3, “Chg flt typ” on page 80, to change the fault type.)


www.cadfamily.com

84 Edit Map GRID Reference ManualOperate on fault traces P.2.3.5.7

Operate on fault traces P.2.3.5.7

Opr flt trc

PurposeEditing operations to modify the XY traces for digitized fault lines on the current map.


The “Return” option returns the user to the “Chg faults” menu. Each of the other options is described in the relevant help sections.

Table 5.3 Menu P.2.3.5.7

Option Function

1 Return

2 Clp flt trc

3 Spl flt trc

4 Close flts

5 Thin flts

6 Repop flts

7 Smooth flts

8 Join flts

9 Extend flts

Clip fault trace

Split fault trace

Close fault polygons

Thin faults

Repopulate faults

Smooth faults

Join faults

Extend faults


www.cadfamily.com

GRID Reference Manual Edit MapClip fault trace P.2.3.5.7.2

85

Clip fault trace P.2.3.5.7.2

Clp flt trc

PurposeClip the end of a digitized fault trace on the current map.

DescriptionThis option allows the ends of fault traces to be clipped. The user is asked to select the point at which each fault line is to be clipped.

When the “Clp flt trc” option is selected, the user may clip as many or as few faults as required. Clipping will cease on selection of another menu option.

The section of the fault from the nearest end point to the selected point (i.e. the section with the fewest data points) will be erased from the map.


www.cadfamily.com

86 Edit Map GRID Reference ManualSplit fault trace P.2.3.5.7.3

Split fault trace P.2.3.5.7.3

Spl flt trc

PurposeSplit a fault trace on the current map into two faults.

DescriptionThis option enables a digitized fault line to be split into two. The user is asked to select the point at which each fault is to be split.

When the “Spl flt trc” option is selected, the user may split as many or as few faults as required. Splitting will cease on selection of another menu option.

The nearest fault to the point selected will be split by dividing the fault into two separate fault lines at the given point. If any of the fault lines is reduced to a single point, it will be discarded. It may be made easier if the digitized points on the fault trace are displayed on the screen, which can be done with the display option D.6.3.3.4, “Tog flt pnts” (see page 575).

The fault name for the original fault will be used to construct names for the two new faults in the form ‘oldnameA’ and ‘oldnameB’.

Note Note that if the original fault trace was SLOPING/REGIONAL or BOUNDARY, it will be changed to VERTICAL if this operation changes the fault line so that it is no longer closed.


www.cadfamily.com

GRID Reference Manual Edit MapClose fault polygons P.2.3.5.7.4

87

Close fault polygons P.2.3.5.7.4

Close flts

PurposeClose digitized fault polygons on the current map.

DescriptionThis option closes individual fault polygons, according to the distance between the start and end points. (See also option P.2.3.5.7.8, “Join flts”, page 91.)

The user is prompted to enter the maximum extrapolation factor. This is used as a multiplier on the average length of the existing line segments, to calculate the limit on the length of a new line segment which can join two fault points. Note that if this limit is too large, unrealistic connections may result.

The user can choose to close all possible faults or selected lines only. To finish line selection, pick another menu option.

At the end of the operation, the program reports the total number of faults which were closed.


www.cadfamily.com

88 Edit Map GRID Reference ManualThin faults P.2.3.5.7.5

Thin faults P.2.3.5.7.5

Thin flts

PurposeThin digitized fault lines on the current map.

DescriptionThis option allows fault traces to be thinned by removing points according to the curvature of the fault line. At each point, the angle between adjacent line segments is checked before deciding to remove the point. Note that this will result in a higher density of points on curved sections of each fault, with less points on relatively straight sections. It may be necessary to use the option “Repop flts” (P.2.3.5.7.6, see page 89) in combination with this thinning operation, to obtain a good distribution of points along the entire fault.

The user can choose to thin all faults or selected lines only. To finish line selection, pick another menu option.

At the end of the operation, the program reports how many faults were thinned and the percentage of data points removed.


www.cadfamily.com

GRID Reference Manual Edit MapRepopulate faults P.2.3.5.7.6

89

Repopulate faults P.2.3.5.7.6

Repop flts

PurposeRepopulate digitized fault lines on the current map, by adding additional points.

DescriptionThis option allows fault traces to be repopulated with additional XY points. The user is prompted to choose one of the following methods:

1 Insertion

2 Replacement

Method 1 keeps all existing points on the fault, but inserts new points on each line segment if the line segment is longer than the required repopulation interval.

Method 2 replaces the current fault trace with a new fault which has points spaced according to the repopulation interval, retaining only the first and last points.

The user is prompted to define the repopulation interval as a fractional value, which will be used as a multiplier on the average length of each line segment. For example, if the average distance between two points on a fault is 50 metres and the user enters an interval value of 0.4, the repopulation interval will be 20 metres.

The user can choose to repopulate all faults or selected lines only. To finish line selection, pick another menu option.

At the end of the operation, the program reports how many faults were repopulated and the increase in the number of data points.


www.cadfamily.com

90 Edit Map GRID Reference ManualSmooth faults P.2.3.5.7.7

Smooth faults P.2.3.5.7.7

Smooth flts

PurposeSmooth digitized fault lines on the current map, by reinterpolation.

DescriptionThis option allows fault traces to be smoothed by reinterpolating XY points. Smoothing is performed by replacing each point with a new XY point calculated as the mid-point of the line joining the mid-points of the adjacent line segments. The first and last points are unchanged. It may be necessary to increase the density of points along the faults using “Repop flts” (P.2.3.5.7.6, see page 89) before smoothing the lines.

The user can choose to smooth all faults or selected lines only. To finish line selection, pick another menu option.

At the end of the operation, the program reports how many faults were smoothed.


www.cadfamily.com

GRID Reference Manual Edit MapJoin faults P.2.3.5.7.8

91

Join faults P.2.3.5.7.8

Join flts

Purpose Join (or close) digitized fault lines on the current map.

Description This option connects separate fault traces together and/or closes individual faults, according to the distance between the start and end points. (See also option P.2.3.5.7.4, “Close flts”, page 87.)

The user is prompted to enter the maximum extrapolation factor. This is used as a multiplier on the average length of the existing line segments, to calculate the limit on the length of a new line segment which can join two fault points. Note that if this limit is too large, unrealistic connections may result.

The user is also prompted to indicate whether faults can be allowed to cross existing faults, when creating a new fault trace.

The user can choose to join all faults or selected pairs of lines only. When selecting lines, a fault can be closed by picking the same line for the first and second fault. To finish line selection, pick another menu option.

At the end of the operation, the program reports the total number of faults on the map before and after joining.

Note The program will not check for fault line connections which intersect contours. If this operation results in contour lines crossing the new fault, the user must decide whether to modify the fault trace or the contours, to avoid sampling problems.


www.cadfamily.com

92 Edit Map GRID Reference ManualExtend faults P.2.3.5.7.9

Extend faults P.2.3.5.7.9

Extend flts

PurposeExtend digitized fault traces on the current map.

DescriptionThis option can be used to extend fault traces by linear extrapolation.

The user is prompted to enter the maximum extrapolation factor. This is used as a multiplier on the average length of the existing line segments, to calculate the limit on the length of a new line segment which can be used to extend a fault. Note that as the new line will be a straight extension of the last line segment, it is advisable to use a small extrapolation factor (e.g. 1.0 or less). If it is necessary to add a relatively long fault segment, use option P.2.3.5.6, “Chg flt trc” (see page 83) to edit the fault by hand.

The user is also prompted to indicate whether faults can be allowed to cross existing faults, when extending a fault trace.

The user can choose to extend all faults or selected lines only. When selecting lines, the user can also choose to extend both ends or only the end nearest the selection point. To finish line selection, pick another menu option.

At the end of the operation, the program reports the total number of faults which were extended.


www.cadfamily.com

GRID Reference Manual Edit MapInput faults P.2.3.6

93

Input faults P.2.3.6

Inp faults

PurposeInput fault traces from a data file onto the current map, clipping to model area if required.

DescriptionFaults may be read in addition to any that already exist on the map.

The user is prompted for the name of the file containing the fault traces and whether it is required to clip the data to the model area. The user can also choose to ‘thin’ the digitized input file.

Four standard types of formatted input file structure are allowed:

Fault traces can also be read from formatted files in UKOOA structure, from CPS-3 binary fault files or from EarthVision vertical or non-vertical fault trace files.

An additional special file structure is available for input and output of fault types (vertical, sloping, regional or boundary) and segment types (major or minor). This option can be selected by entering the keyword SPECIAL when prompted for file layout.

STRUCTURE a: X1 Y1 X2 Y2Four REAL numbers are expected on each record, for example:

A new fault trace will be started whenever the X2,Y2 coordinate of one record differs from the X1,Y1 coordinate of the next record.

a X1,Y1,X2,Y2b X,Y,IDc X,Yd X,Y,NAME

X1-location Y1-location X2-location Y2-location218649.03100 387929.34300 230555.53100 366823.09300230555.53100 366823.09300 240717.20300 350704.71800240717.20300 350704.71800 253900.21800 335572.68700253900.21800 335572.68700 265840.65600 323167.68700265840.65600 323167.68700 278604.34300 309494.71800278604.34300 309494.71800 290488.53100 296790.87500290488.53100 296790.87500 298255.37500 285674.28100298255.37500 285674.28100 306982.78100 272687.03100


www.cadfamily.com

94 Edit Map GRID Reference ManualInput faults P.2.3.6

STRUCTURE b: X Y IDTwo REAL numbers and an INTEGER id-number are expected on each record, for example:

A new fault trace will be started whenever the fault-ID changes.

STRUCTURE c: X YTwo REAL numbers are expected on each record, and a marker card is used to separate different fault traces. The user is prompted for a REAL value to represent the marker (e.g. 1.0E20), for example:

A new fault trace will be started whenever a marker card is encountered.

X-location Y-location Fault-ID253900.21800 335572.68700 1265840.65600 323167.68700 1278604.34300 309494.71800 1290488.53100 296790.87500 1298255.37500 285674.28100 1306982.78100 272687.03100 1636141.68700 227020.06200 2617731.75000 229109.53100 2595155.50000 232837.46800 2573246.87500 237401.62500 2553058.50000 240528.90600 2

X-location Y-location1.00000002E+20 1.00000002E+20253900.21800 335572.68700265840.65600 323167.68700278604.34300 309494.71800290488.53100 296790.87500298255.37500 285674.28100306982.78100 272687.031001.00000002E+20 1.00000002E+20636141.68700 227020.06200617731.75000 229109.53100595155.50000 232837.46800573246.87500 237401.62500553058.50000 240528.90600533424.25000 243844.68700


www.cadfamily.com


95

STRUCTURE d: X Y NAMETwo REAL numbers and a CHARACTER fault name are expected on each record, for example:

Note that if list directed input * is being used the fault name may be in single quotes.

A new fault trace will be started whenever the fault name changes.

SPECIAL structure: X Y NAME TYPE SEGMENTEach record contains two REAL numbers and 3 CHARACTER keywords, the fault name, fault type and segment type. The available mnemonics for fault type are V - vertical, S (or R) - sloping (or regional) B - boundary fault and D - slope discontinuity. The mnemonics MAJOR and MINOR indicate segment type, e.g.

A new fault trace will be started whenever the fault name or fault type changes.

For all the above types of file structure the X and Y locations should be in model coordinates (typically metres or feet). Fault trace locations that are in LATITUDE & LONGITUDE may be read using the UKOOA format or in DEGREES format for decimal degrees. These are described in Appendix K.

If the input file name ends with the extension .svf, the user will be prompted to select file type CPS-3, before the file is opened.

If the input file name ends with ‘vflt’, the user will be prompted to select file type EarthVision.

X-location Y-location Fault-name253900.21800 335572.68700 Fault-A265840.65600 323167.68700 Fault-A278604.34300 309494.71800 Fault-A290488.53100 296790.87500 Fault-A298255.37500 285674.28100 Fault-A306982.78100 272687.03100 Fault-A636141.68700 227020.06200 Fault-B617731.75000 229109.53100 Fault-B595155.50000 232837.46800 Fault-B573246.87500 237401.62500 Fault-B553058.50000 240528.90600 Fault-B

X-location Y-location Fault-name Type Segment549537.5625 6018282.500 Fault-C V Major553802.2500 6015529.000 Fault-C V Major556347.3125 6011674.000 Fault-C V Major557103.9375 6007268.000 Fault-C V Major556347.3125 6022964.000 Fault-D S Major563569.7500 6024547.000 Fault-D S Major571067.3750 6026130.500 Fault-D S Major574713.0000 6024685.000 Fault-D S Major578152.2500 6023721.000 Fault-D S Major574369.0625 6023101.500 Fault-D S Minor569829.2500 6021931.000 Fault-D S Minor564601.5625 6021587.000 Fault-D S Minor557172.7500 6022619.500 Fault-D S Minor556347.3125 6022964.000 Fault-D S Minor


www.cadfamily.com

96 Edit Map GRID Reference ManualInput faults P.2.3.6

For other file types, the first line of data will then appear at the bottom of the screen and the new menu will allow the user to skip through the file and view the data. The option “Next line” should be selected to skip any header records until the first X Y location (or marker card if structure b) is displayed. Data input will commence with the current record being displayed when the option “Return” is selected.

The file type can be selected after viewing the file header, by entering A, B, C or D in response to the prompt:

A menu selection list of file types can be obtained by responding with H for Help at this stage.

UKOOA format can be selected by responding to this prompt with UKECL, UK84 or UK85, or CPS-3 input can be selected at this stage by entering CPS. EarthVision input can be selected by entering EV. The keyword SPECIAL can be entered to allow input of fault type and segment information.

For CPS-3 or EarthVision data, the user will not be prompted for a format. However, EarthVision files must be identified as vertical (.vflt) or non-vertical (.nvflt). For non-vertical EarthVision faults, the user will also be prompted to define the polygons as boundary faults or sloping faults. Choose boundary faults if the fault traces surround the active data on the map, or sloping if the fault traces outline the fault surface. All faults will be set to the same type. If necessary, this can be modified later via “Chg flt typ” (P.2.3.5.3, see page 80).

In all cases the file can be read using list-directed input ‘*’ or a user supplied format statement.

If the first character of the first record in the file is a * or (, then it is assumed to be a format statement e.g. * or (2F12.3,I4), and it will be the default when the user is prompted for the input format, if the first record is not a format statement then the default input format will be list directed ‘*’.


Fault traces are marked on the map as each fault is read into the program. Unless the SPECIAL file structure is used for input, all fault traces will be stored and displayed as major fault segments, using the current granite settings defined in the “Def granite” option. If required, faults may be re-defined as ‘minor segments’ using the “Chg flt seg” option.

If fault names are not given in the input file, faults are automatically named according to the fault-ID (if given) or the order in which they are read. The fault name will take the form ‘FLT-n’, where ‘n’ is an integer number. Fault names are not displayed by default, but can be shown by selecting the display option D.6.3.3.3, “Tog flt nmes”; see page 575.

If fault types are not defined in the input file, they are taken to be vertical, unless a closed fault trace is detected, when the fault type will be defined as sloping.

Layout: a) X1,Y1,X2,Y2 b) X,Y,ID c) X,Y or d) X,Y,NAME ? (a/B/c/d)


www.cadfamily.com


97

ExampleA file called ECL.FLT contains two faults to be input to the current map. The file ECL.FLT looks like:


RECORD 1:(2F12.3,I2)RECORD 2: 273926.406 320046.062 1RECORD 3: 278242.468 327856.593 1RECORD 4: 282516.062 336018.000 1RECORD 5: 296861.000 349817.812 2RECORD 6: 310834.437 357874.281 2RECORD 7: 326619.687 361741.531 2

"Edt faults""Inp faults"'Enter name of file to be read...' ( ECL.FLT is entered )'Clip input data to model area ? (y/N)' ( N is entered )'Thin digitised input data ? (y/N)' ( N is entered )'Layout: a) X1,Y1,X2,Y2 b) X,Y,ID c) X,Y or d) X,Y,NAME ? (a/B/c/d)'

( B is entered )"Next line" ( to skip format line)"Return" ( 1st fault

location shown )'Enter record format, e.g. (2E13.5,I4) or RETURN for (2F12.3,I2)'

( RETURN to read file)2 faults read...&


www.cadfamily.com

98 Edit Map GRID Reference ManualOutput faults P.2.3.7

Output faults P.2.3.7

Out faults

PurposeOutput fault traces from the current map to a data file, clipping to the model area if required.

DescriptionThe user is prompted for the root name of the file to be opened for output. The output file will be given the name ‘root.FLT’.

The user is then prompted to choose whether to clip the data to the model area, and to select the output file structure.

Four different types of structure are available:

An additional special file structure is available for input and output of fault types (vertical, sloping, regional or boundary) and segment types (major or minor). This option can be selected by entering the keyword SPECIAL when prompted for file layout.

STRUCTURE a: X1 Y1 X2 Y2Four REAL numbers are written to each record, for example:




www.cadfamily.com

GRID Reference Manual Edit MapOutput faults P.2.3.7

99

STRUCTURE b: X Y IDTwo REAL numbers and an INTEGER id-number are written on each record, for example:

STRUCTURE c: X YTwo REAL numbers are written on each record, and a marker card is used to separate different fault traces. The user is prompted for a REAL value to represent the marker (e.g. 1.0E20), for example:

STRUCTURE d: X Y NAMETwo REAL numbers and a CHARACTER fault name are written on each record, for example:

X-location Y-location Fault-ID253900.21800 335572.68700 1265840.65600 323167.68700 1278604.34300 309494.71800 1290488.53100 296790.87500 1298255.37500 285674.28100 1306982.78100 272687.03100 1636141.68700 227020.06200 2617731.75000 229109.53100 2595155.50000 232837.46800 2573246.87500 237401.62500 2553058.50000 240528.90600 2


X-location Y-location Fault-name253900.21800 335572.68700 Fault-A265840.65600 323167.68700 Fault-A278604.34300 309494.71800 Fault-A290488.53100 296790.87500 Fault-A298255.37500 285674.28100 Fault-A306982.78100 272687.03100 Fault-A636141.68700 227020.06200 Fault-B617731.75000 229109.53100 Fault-B595155.50000 232837.46800 Fault-B573246.87500 237401.62500 Fault-B553058.50000 240528.90600 Fault-B


www.cadfamily.com

100 Edit Map GRID Reference ManualOutput faults P.2.3.7

Note that if list directed input * is being used the fault name will be written in single quotes.

SPECIAL structure: X Y NAME TYPE SEGMENTEach record contains two REAL numbers and 3 CHARACTER keywords, the fault name, fault type and segment type. The available mnemonics for fault type are V - vertical, S (or R) - sloping (or regional) B - boundary fault and D - slope discontinuity. The mnemonics MAJOR and MINOR indicate segment type, e.g.

For all the above types of file structure the X and Y locations will be in model coordinates (typically metres or feet). Fault trace locations may be output in LATITUDE & LONGITUDE using the UKOOA format or in DEGREES format for decimal degrees. These are described in Appendix K.

List directed output ‘*’ is the default. However, the user may specify an output format, e.g. (2F12.5,I4).


The first record to be written to the output file is the format used, subsequent records will contain the fault data in the specified format.

When output is complete, the user is informed of the number of faults that were written to the file.

The option "Out flt maps" P.6.4.3 (see page 521) can be used to output faults from more than one stratum or map.

ExampleA map contains two faults to be output to a file called ECL.FLT using the format (2F12.3,I2). No clipping is required.

X-location Y-location Fault-name Type Segment549537.5625 6018282.500 Fault-C V Major553802.2500 6015529.000 Fault-C V Major556347.3125 6011674.000 Fault-C V Major557103.9375 6007268.000 Fault-C V Major556347.3125 6022964.000 Fault-D S Major563569.7500 6024547.000 Fault-D S Major571067.3750 6026130.500 Fault-D S Major574713.0000 6024685.000 Fault-D S Major578152.2500 6023721.000 Fault-D S Major574369.0625 6023101.500 Fault-D S Minor569829.2500 6021931.000 Fault-D S Minor564601.5625 6021587.000 Fault-D S Minor557172.7500 6022619.500 Fault-D S Minor556347.3125 6022964.000 Fault-D S Minor


www.cadfamily.com

GRID Reference Manual Edit MapOutput faults P.2.3.7

101


The file ECL.FLT will look like:

"Edt faults""Out faults"'Enter output file root' ( ECL is entered )File ECL.FLT opened ...&'Clip output data to model area ? (y/N)' ( N is entered )'Layout: a) X1,Y1,X2,Y2 b) X,Y,ID c) X,Y or d) X,Y,NAME ? (a/B/c/d) '

( B is entered )'Enter record format, e.g. (2E13.5,I4) or RETURN for *'

( (2F12.3,I2) is entered )2 faults output...&



www.cadfamily.com



Def granite

PurposeDefine the pen and text representations to be used when drawing faults on the current map.


The “Return” option returns the user to the “Edt faults” menu. Each of the other options leads to a further menu for setting Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current default Granite attributes for the major or minor fault line or text. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.

The pen and text representations defined here will be applied to all faults on the current map.


Option Function

1 Return

2 Def maj pen

3 Def min pen

4 Def text

5 Def marker

Define pen for major fault lines

Define pen for minor fault lines

Define text for fault names

Define marker for fault points


www.cadfamily.com

GRID Reference Manual Edit MapEdit contours P.2.4

103

Edit contours P.2.4

Edt contours

PurposeEdit the digitized contours on the current map.

DescriptionThis menu can only be entered if a mesh has not previously been defined. The following menu is displayed:

These options can be used to edit a set of contour lines and/or scattered data points, representing a geological surface or property.

Contours can be drawn in one of two line styles (either major or minor contours). The Granite settings for contours are set from the “Def granite” menu, selected from menu P.2.4.6, “Chg cnt pars” (see page 122).

The parameters controlling interpolation and back contouring are set from the “Smp contours” menu.

The “Return” option returns the user to the “Edt map” menu. Each of the other options are described in the relevant help sections.

If the “Abandon” option is taken, any edits made during the current entry to the “Edt contours” option will be discarded.


Option Function

1 Return

2 Cpy contours

3 Add contours

4 Del contours

5 Chg contours

6 Chg cnt pars

7 Inp contours

8 Out contours

9 Smp contours

Copy contours

Add contours

Delete contours

Change contours

Change contour parameters

Input contours

Output contours

Sample contours


www.cadfamily.com

104 Edit Map GRID Reference ManualCopy contours P.2.4.2

Copy contours P.2.4.2

Cpy contours

PurposeCopy the contours from another map stratum onto the current map stratum.

DescriptionThe user is prompted for the map name and the stratum number from which to copy the contours. If the map name and stratum number supplied is a mesh map then the contours will be interpolated from the mesh.

The contours and their granite settings will be copied from the given map onto the current map.

Note It is not possible to copy contours if the current map already has one or more contours defined on it.


www.cadfamily.com

GRID Reference Manual Edit MapAdd contours P.2.4.3

105

Add contours P.2.4.3

Add contours

PurposeDigitize contours onto the current map.


The user is prompted for the value of the contour to be digitized. If required, the contour interval can also be entered. For example to digitize a map that has a contour interval of 25m and a base contour of 100m:

‘Enter contour value (,increment)’ (enter 100,25)

The current contour value and interval is displayed at the top of the screen.

“Abandon” is used to abandon the current input line upon confirmation from the user.

“Continue” is used to continue digitizing the current input line.

“Cls contour” is used to close the current contour by automatically adding an extra point onto the input line that is coincident with the first point. The input line is then redrawn in the colour and line style defined in the “Def granite” option.

“New contour” is used to start digitizing a new contour defined by the current contour value. If an input line is already displayed on the screen, it will be redrawn in the colour and line style defined in the “Def granite” option. The new input line will be drawn in white.

“Inc contour” is used to increment the current contour value by the contour interval. The new value will be displayed at the top of the screen. If an input line is already displayed on the screen, it will be redrawn in the colour and line style defined in the “Def granite” option.

“Dec contour” is used to decrement the current contour value by the contour interval. The new value will be displayed at the top of the screen. If an input line is already displayed on the screen, it will be redrawn in the colour and line style defined in the “Def granite” option.

Data values at WELL locations should be input by digitizing a single point contour at the well. The value of the single point contour will be displayed at the location of the well.


Option Function

1 Return

2 Abandon

3 Continue

4 Cls contour

5 New contour

6 Inc contour

7 Dec contour

Abandon current contour

Continue current contour

Close current contour

Start new contour

Increment contour value

Decrement contour value


www.cadfamily.com

106 Edit Map GRID Reference ManualAdd contours P.2.4.3

As a general rule for digitizing a contour map which will be used for gridding or for sampling, the user should aim for a roughly uniform coverage of the map using intermediate contours where necessary and a roughly uniform spacing of points along the contours. More contours are better than more points on the same contours. In regions of tight but uniform gradient it is often better not to digitize every contour but to allow the program to interpolate and produce a more even gradient.


www.cadfamily.com

GRID Reference Manual Edit MapDelete contours P.2.4.4

107

Delete contours P.2.4.4

Del contours

PurposeDelete digitized contour(s) from the current map.

DescriptionThe user is asked for the value of the contour to be deleted.

If an asterisk ‘*’ is entered then all the contours on the map will be deleted upon confirmation by the user.

If the letter ‘Q’ is entered then each contour is highlighted in turn and the user can select to delete the contour or not. Sequencing through the contours can be ended by entering the letter ‘E’.

If no value is entered then the user is asked to select the contour on the map to be deleted by digitizing a point close to the contour on the screen. The contour is highlighted and confirmation is requested to delete it.


www.cadfamily.com

108 Edit Map GRID Reference ManualChange contours P.2.4.5

Change contours P.2.4.5

Chg contours

PurposeChange digitized contour lines on the current map.


The “Return” option returns the user to the “Edt contour” menu. Each of the other options are described in the relevant help sections.


Option Function

1 Return

2 Sho cnt val

3 Chg cnt val

4 Opr cnt vals

5 Chg cnt lne

6 Spl contours

Show contour value

Change contour value

Operate on contour values

Change contour line

Split contours


www.cadfamily.com

GRID Reference Manual Edit MapShow contour value P.2.4.5.2

109

Show contour value P.2.4.5.2

Sho cnt val

PurposeShow the value of a digitized contour on the current map.

DescriptionThe user is prompted to select the contour.

The nearest contour to the point selected will be highlighted and its value will be displayed at the bottom of the screen.


www.cadfamily.com

110 Edit Map GRID Reference ManualChange contour value P.2.4.5.3

Change contour value P.2.4.5.3

Cng cnt val

PurposeChange the value of a digitized contour on the current map.

DescriptionThe user is prompted for the value of the contour to be changed. If the value is not known, enter RETURN. It is then necessary to digitize a point on or close to the required contour.

The nearest contour to the point selected will be highlighted. The user is prompted for a new contour value (default being the current value). The contour is then redrawn with the new value.


www.cadfamily.com

GRID Reference Manual Edit MapOperate on contour values P.2.4.5.4

111

Operate on contour values P.2.4.5.4

Opr cnt vals

PurposeOperate on the Z-values of the digitized contours on a map.

DescriptionThis option can be used to perform arithmetic or logical operations on the Z-values of contours on the current map. Simple arithmetic operations can be performed by entering a symbol (+,-,*,/) followed by a constant. Any other function or expression supported by the parser may be used, provided that it refers to only the current map stratum, NULL and constant values. The symbol Z may be used in place of the full map name, e.g. LOG(Z) or LOG(MAPX(1)) to replace the contour values on MAPX stratum 1 with their logarithmic values. See Appendix G for further information on use of the parser.

The user can choose to operate on all contours on the map, or on selected contours only.

If the calculation results in NULL values for certain contours, the user will be prompted to delete all null-valued contours after the operation.


www.cadfamily.com

112 Edit Map GRID Reference ManualChange contour line P.2.4.5.5

Change contour line P.2.4.5.5

Chg cnt lne

PurposeRedigitize a section of a contour on the current map.

DescriptionThe user is prompted for the value of the contour to be changed. If the value is not known, enter RETURN. It is then necessary to digitize a point on or close to the required contour.

The nearest contour of the given value to the point selected is highlighted. If no value is given the nearest contour of any value will be highlighted.

The user is required to select the endpoints of the contour section to be changed. The endpoints of the selected section are highlighted and the section is erased from the display.

Confirmation is requested to proceed with the change. If the user confirms to proceed, the endpoints of the section are unhighlighted and part of the remaining contour is highlighted. Redigitizing should start from the highlighted part of the remaining contour.


www.cadfamily.com

GRID Reference Manual Edit MapOperate on contour lines P.2.4.5.6

113

Operate on contour lines P.2.4.5.6

Opr cnt lnes

PurposeEditing operations to modify the XY traces for digitized contour lines on the current map.

Description The following menu is displayed:

The “Return” option returns the user to the “Chg contours” menu. Each of the other options is described in the relevant help sections.


Option Function

1 Return

2 Clp contours

3 Spl contours

4 Del flt reg

5 Thin cnts

6 Repop cnts

7 Smooth cnts

8 Join cnts

9 Extend cnts

Clip contours

Split contours

Delete fault region

Thin contours

Repopulate contours

Smooth contours

Join contours

Extend contours


www.cadfamily.com

114 Edit Map GRID Reference ManualClip contours P.2.4.5.6.2

Clip contours P.2.4.5.6.2

Clp contours

PurposeClip the end of a digitized contour on the current map.

DescriptionThis option allows the ends of contours to be clipped. The user is asked to select the point at which each contour is to be clipped.

When the “Clp contours” option is selected, the user may clip as many or as few contours as required. Clipping will cease on selection of another menu option.

The section of the contour from the nearest end point to the selected point (i.e. the section with the fewest data points) will be erased from the map.

The option is useful, for example, if a fault line has been moved slightly, resulting in contours traversing the fault trace.


www.cadfamily.com

GRID Reference Manual Edit MapSplit contours P.2.4.5.6.3

115

Split contours P.2.4.5.6.3

Spl contours

PurposeSplit a contour on the current map into two contours.

DescriptionThis option enables a digitized contour to be split into two. The user is asked to select the point at which each contour is to be split.

When the “Spl contours” option is selected, the user may split as many or as few contours as required. Splitting will cease on selection of another menu option.

The nearest contour to the point selected will be split by dividing the contour into two separate contour lines at the given point. It may be made easier if the actual contour points are displayed on the screen, which can be done with the display option D.6.3.4.3, “Tog cnt pnts” (see page 576).

The option is useful, for example, if a new fault is digitized crossing a number of contour lines. The ends of the new contours may then be re-digitized according to the new map.


www.cadfamily.com

116 Edit Map GRID Reference ManualDelete fault region P.2.4.5.6.4

Delete fault region P.2.4.5.6.4

Del flt reg

PurposeDelete the contours in a fault region.

DescriptionA fault is selected by the user. All the contour points which lie within the area bounded by the fault trace are deleted. Any contour lines which pass entirely through the fault region will be split into two. If the fault region is not closed, it will be closed automatically by a line joining the first and last points of the fault trace.


www.cadfamily.com

GRID Reference Manual Edit MapThin contours P.2.4.5.6.5

117

Thin contours P.2.4.5.6.5

Thin cnts

PurposeThin digitized contour lines on the current map.

DescriptionThis option allows contours to be thinned by removing points according to the curvature of the contour line. At each point, the angle between adjacent line segments is checked before deciding to remove the point. Note that this will result in a higher density of points on curved sections of each contour, with less points on relatively straight sections. It may be necessary to use the option “Repop cnts” (P.2.4.5.6.6, see page 118) in combination with this thinning operation, to obtain a good distribution of points along the entire contour.

The user can choose to thin all contours or selected lines only. To finish line selection, pick another menu option.

At the end of the operation, the program reports how many contours were thinned and the percentage of data points removed.


www.cadfamily.com

118 Edit Map GRID Reference ManualRepopulate contours P.2.4.5.6.6

Repopulate contours P.2.4.5.6.6

Repop cnts

PurposeRepopulate digitized contour lines on the current map, by adding additional points.

DescriptionThis option allows contours to be repopulated with additional XY points. The user is prompted to choose one of the following methods:

1 Insertion

2 Replacement

Method 1 keeps all existing points on the contour, but inserts new points on each line segment if the line segment is longer than the required repopulation interval.

Method 2 replaces the current contour with a new contour which has points spaced according to the repopulation interval, retaining only the first and last points.

The user is prompted to define the repopulation interval as a fractional value, which will be used as a multiplier on the average length of each line segment. For example, if the average distance between two points on a contour is 20 metres and the user enters an interval value of 0.4, the repopulation interval will be 8 metres.

The user can choose to repopulate all contours or selected lines only. To finish line selection, pick another menu option.

At the end of the operation, the program reports how many contours were repopulated and the increase in the number of data points.


www.cadfamily.com

GRID Reference Manual Edit MapSmooth contours P.2.4.5.6.7

119

Smooth contours P.2.4.5.6.7

Smooth cnts

PurposeSmooth digitized contour lines on the current map, by reinterpolation.

DescriptionThis option allows contours to be smoothed by reinterpolating XY points. Smoothing is performed by replacing each point with a new XY point calculated as the mid-point of the line joining the mid-points of the adjacent line segments. The first and last points are unchanged. It may be necessary to increase the density of points along the contours using “Repop cnts” (P.2.4.5.6.6, see page 118) before smoothing the lines.

The user can choose to smooth all contours or selected lines only. To finish line selection, pick another menu option.

At the end of the operation, the program reports how many contours were smoothed.


www.cadfamily.com

120 Edit Map GRID Reference ManualJoin contours P.2.4.5.6.8

Join contours P.2.4.5.6.8

Join cnts

PurposeJoin (or close) digitized contour lines on the current map.

DescriptionThis option connects separate contours together and/or closes individual contours, according to the distance between the start and end points. Contours cannot be joined across faults.

The user is prompted to enter the maximum extrapolation factor. This is used as a multiplier on the average length of the existing line segments, to calculate the limit on the length of a new line segment which can join two contour points. Note that if this limit is too large, unrealistic connections may result.

The user can choose to join all contours or selected pairs of lines only. When selecting lines, a contour can be closed by picking the same line for the first and second contour. To finish line selection, pick another menu option.

At the end of the operation, the program reports the total number of contours on the map before and after joining.


www.cadfamily.com

GRID Reference Manual Edit MapExtend contours P.2.4.5.6.9

121

Extend contours P.2.4.5.6.9

Extend cnts

PurposeExtend digitized contour lines on the current map.

DescriptionThis option can be used to extend contours by linear extrapolation. Contours cannot be extended across faults. This option may be used, for example, to extrapolate digitized contour traces up to fault edges.

The user is prompted to enter the maximum extrapolation factor. This is used as a multiplier on the average length of the existing line segments, to calculate the limit on the length of a new line segment which can be used to extend a contour. Note that as the new line will be a straight extension of the last line segment, it is advisable to use a small extrapolation factor (e.g. 1.0 or less). If it is necessary to add a relatively long contour segment, use option P.2.4.5.5, “Chg cnt lne” (see page 112) to edit the contour by hand.

The user can choose to extend all contours or selected lines only. When selecting lines, the user can also choose to extend both ends or only the end nearest the selection point. To finish line selection, pick another menu option.

At the end of the operation, the program reports the total number of contours which were extended.


www.cadfamily.com

122 Edit Map GRID Reference ManualChange contour parameters P.2.4.6

Change contour parameters P.2.4.6

Chg cnt pars

PurposeChange parameters for drawing the contours on the current map.


The “Return” option returns the user to the “Edt contour” menu. Each of the other options is described in the following sections.


Option Function

1 Return2 Sho map area3 Chg map area4 Chg cnt lbls5 Chg cnt int6 Def granite

Show map areaChange map areaChange contour labelsChange contour intervalDefine granite settings


www.cadfamily.com

GRID Reference Manual Edit MapShow map area P.2.4.6.2

123

Show map area P.2.4.6.2

Sho map area

PurposeShow the current map area.

DescriptionOn selecting this option, the current map area is highlighted by a white box. If the map area extends beyond the current model area the highlighted box will be drawn off the screen unless the display area is increased.

When this option is selected for a mesh map, a message will be displayed, showing the number of rows and columns in the mesh.

Selecting the option when the map area is already shown will turn off the highlighting.

Note that the coordinate box that is drawn on the screen (default green) delimits the model area, not the map area.


www.cadfamily.com

124 Edit Map GRID Reference ManualChange map area P.2.4.6.3

Change map area P.2.4.6.3

Chg map area

PurposeChange the current map area.

DescriptionThis option allows the user to change the current map area. The user is prompted for the minimum and maximum coordinates of the required area.

When interpolating, only data within the map area are considered.

When plotting, automatic clipping of data is to the model area.

Note that the coordinate box that is drawn on the screen (default green) delimits the model area not the map area. The current map area can be highlighted using the P.2.4.6.2 “Sho map area” option (see page 123).


www.cadfamily.com

GRID Reference Manual Edit MapChange contour labels P.2.4.6.4

125

Change contour labels P.2.4.6.4

Chg cnt lbls

PurposeChange the number of decimal points on digitized contour labels for the current map.

DescriptionThe user is prompted for the number of decimal points required when drawing major or minor contour labels. Integer labels can be selected by entering the letter ‘I’.


www.cadfamily.com

126 Edit Map GRID Reference ManualChange contour interval P.2.4.6.5

Change contour interval P.2.4.6.5

Chg cnt int

PurposeChange the major contour interval for digitized contours on the current map.

DescriptionThe user is prompted for the major contour interval and the base value from which major contour values are to be calculated.

A contour will be drawn as a major contour if the difference between the contour value and the base value is an exact multiple of the major contour interval, otherwise it will be drawn as a minor contour.


www.cadfamily.com

GRID Reference Manual Edit MapDefine Granite settings P.2.4.6.6

127

Define Granite settings P.2.4.6.6

Def granite

PurposeDefine the pen and text representation to be used for drawing digitized contours on the current map.


The “Return” option returns the user to the “Chg cnt pars” menu. Each of the other options leads to a further menu for setting Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current default Granite attributes for the major or minor contour line, text or marker. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.

The pen and text representations defined here will be applied to all digitized contours on the current map.


Option Function

1 Return

2 Def maj pen

3 Def min pen

4 Def maj txt

5 Def min txt

6 Def marker

Define pen for major contours

Define pen for minor contours

Define text for major contours

Define text for minor contours

Define marker for points


www.cadfamily.com

128 Edit Map GRID Reference ManualInput contours P.2.4.7

Input contours P.2.4.7

Inp contours

PurposeInput digitized contours from a data file onto the current map, clipping to the model area if required.

DescriptionDigitized contours may be read in addition to any that already exist on the map.

The user is asked whether the file is in SAVE file, ASCII or ZMAP format:

The name of the file containing the digitized contours is then requested, and the user is prompted to choose whether to clip the input data to the model area and whether to ‘thin’ the digitized input data.

If the file is not in SAVE file format then the file structure and format must be defined, as follows:

The first line of the data file will then appear at the bottom of the screen and the new menu will allow the user to skip through the file and view the data. The option “Next line” should be selected to skip any header records until the first X Y Z location (or marker card) is displayed. Data input will commence with the current record being displayed when option “Return” is selected.

Two types of file structure are allowed:

• X Y Z with marker card, or

• X Y Z ID

The user is asked to define the type of file structure by specifying whether or not the contours have an identifier (ID).

In both cases the file can be read using list-directed input ‘*’ or a user supplied format statement.

If the first character of the first record in the file is a * or (, then it is assumed to be a format statement e.g. * or (2F12.3,I4), and it will be the default when the user is prompted for the input format. If the first record is not a format statement then the default input format will be directed ‘*’.


Contour locations that are in LATITUDE and LONGITUDE may be read using the UKOOA format or in DEGREES format for decimal degrees. These are described in Appendix K.

Contours in Z-Map two-field format may be read by entering the keyword ZMAP (or ZYCOR), in response to the prompt to enter the record format for an ASCII file. This is an alternative to entering Z in response to the first prompt to select file type (for backward compatibility with old run files).

’Is the format SAVE file, ZMAP or ASCII ? (s/z/A)’


www.cadfamily.com

GRID Reference Manual Edit MapInput contours P.2.4.7

129

STRUCTURE a: X Y Z with marker cardThree REAL numbers are expected on each record, and a marker card is used to separate different contour lines. The user is prompted for a REAL value to represent the marker, (e.g. 1.0E30), for example:

A new contour will be started whenever a marker card is encountered.

STRUCTURE b: X Y Z ID

Three REAL numbers and an INTEGER id-number are expected on each record, for example:

A new contour will be started whenever the contour-ID changes.

For the above types of file structure the X and Y locations should be in model coordinates (typically metres or feet).

Save file formatThe SAVE file format has the following structure:

261697.437 318804.25 6900.0263695.281 323413.031 6900.01.00000001E+30 1.00000001E+30 1.00000001E+30479767.843 239377.687 6900.0478163.093 220257.515 6900.01.00000001E+30 1.00000001E+30 1.00000001E+30310834.437 357874.281 6900.0670049.937 274363.781 7300.0451978.937 169249.703 7000.0523144.062 207053.890 7100.0563194.687 199555.750 7200.0410756.417 323092.093 7500.0

X-location Y-location Z-value Contour-ID253900.21800 335572.68700 500 1265840.65600 323167.68700 500 1278604.34300 309494.71800 500 1290488.53100 296790.87500 500 1298255.37500 285674.28100 500 1306982.78100 272687.03100 500 1636141.68700 227020.06200 600 2617731.75000 229109.53100 600 2595155.50000 232837.46800 600 2573246.87500 237401.62500 600 2553058.50000 240528.90600 600 2

Record 1 4 integers as follows:Integer 1 dummy


www.cadfamily.com

130 Edit Map GRID Reference ManualInput contours P.2.4.7

Records 2 and 3 are repeated until the end-of-file is reached or an end-of-file marker is found (identified by two records containing the integer 1).

‘ZMAP’ formatThe expected ZMAP format has the following structure.

For each contour:

This structure is repeated for each contour in the file.

An alternative structure is available. This corresponds to output from the Contouring subtask of Z-Map Plus:

For each contour:

This structure is repeated for each contour in the file.

GRID will skip past ZMAP header records beginning with ’!’ and any header data found between two ’@’ characters. Other ZMAP format characters will not be recognized automatically by GRID. If necessary these can be skipped by viewing the data and using the "Next line" option before reading the data.

Integer 2 1Integer 3 1Integer 4 2

Record 2 Integer number of words in next record (NWORD).Record 3 NWORD reals, i.e. NWORD/3 triplets of x,y,value.

Record 1 2 real numbers:Real 1 Marker value (0.1E+31)Real 2 Contour Z-value

Record 2 2 real numbers, defining the X,Y location etc. of a contour point (in model coordinates)

Record 1 2 real numbers:Real 1 Marker value (0.1E+31)Real 2 Marker value (0.1E+31)

Record 2 2 real numbers:Real 1 Contour Z-valueReal 2 Continuation flag in the form x.y where

x = 1 for a new line or 0 for a continuation line

y = 2 or 4 (downhill direction flag ignored by GRID)

Record 3 2 real numbers, defining the X,Y location etc. of a contour point (in model coordinates)


www.cadfamily.com

GRID Reference Manual Edit MapInput contours P.2.4.7

131

If two null values are found on the first line of a ZMAP file, GRID will prompt the user to confirm which structure should be used: 'Data structure from Z-Map Plus Contouring sub-task ? (Y/n)' The default response is 'Y', to select the alternative structure. (Note that this form is NOT available as output from GRID.)

ExampleContours are marked on the map as each contour is read into the program. Contours will be stored and displayed using the current granite settings defined in the “Chg cnt pars” then “Def granite” option.

Consider the following example.

A file called ECL.CNT contains two contours to be input to the current map. The file ECL.CNT looks like:


RECORD 1:(2F12.3,F6.1)RECORD 2: 273926.406 320046.062 100.0RECORD 3: 278242.468 327856.593 100.0RECORD 4: 282516.062 336018.000 100.0RECORD 5: 296861.000 349817.812 200.0RECORD 6: 310834.437 357874.281 200.0RECORD 7: 326619.687 361741.531 200.0

"Edt contours""Inp contours"'Is the data in SAVE file format ? (y/N)' ( N is entered )'Enter name of file to be read...' ( ECL.CNT is entered )'Clip input data to model area ? (y/N)' ( N is entered )'Thin digitized input data ? (y/N)' ( N is entered )"Next line" ( to skip format line )"Return" ( 1st XYZ location shown )'Do the contours have an identifier ? (y/N)' ( N is entered )'Enter record format, e.g. (3E13.5) or RETURN for (2F12.3,F6.1)' ( RETURN to read file )2 contours read...&


www.cadfamily.com

132 Edit Map GRID Reference ManualOutput contours P.2.4.8

Output contours P.2.4.8

Out contours

PurposeOutput digitized contours from the current map to a data file, clipping to the model area if required.

DescriptionThe user is asked if it is required to output the contours in SAVE file format. Responding with Y or N to this prompt selects SAVE file or standard GRID format. Alternatively, the keyword ZMAP (or ZYCOR) can be used to select Z-Map two-field format, or UKECL, UK84 or UK85 can be used to select one of the UKOOA output options.

The user is prompted for the root name of the file to be opened for output. If SAVE file format is selected, the output file will be given the name ‘root.UCT’; otherwise it will be given the name ‘root.CNT’.

The user is then asked if it is required to clip the data to the model area.

Save file formatThe SAVE file format has the following structure:

Records 2 and 3 are written for each contour to be output, with a maximum of 80 contour points in each record.

An end-of-file marker is written as two records containing an integer 1.

Standard GRID file formatThree numbers will be output to each record in the form

List directed output ‘*’ is the default. However, the user may specify an output format, e.g. (3F12.5). Contour locations that are in LATITUDE and LONGITUDE may be written using the UKOOA format or in DEGREES format for decimal degrees. These are described in Appendix K.

Record 1 4 integers as follows:Integer 1 dummyInteger 2 1Integer 3 1Integer 4 2

Record 2 Integer number of words in next record (NWORD).Record 3 NWORD reals, i.e. NWORD/3 triplets of x,y,value.

X-location Y-location Z-value


www.cadfamily.com

GRID Reference Manual Edit MapOutput contours P.2.4.8

133

The ZMAP file structure is as described for contour input: see P.2.4.7, “Inp contours” (page 128). The default format is (2F15.3), but the user may specify any other suitable format. The alternative ZMAP structure, as output by the Contouring sub-task of Z-Map Plus is NOT available for output from GRID.


The first record to be written to the output file is the format used, and subsequent records will contain the contour data in the specified format.

A marker card is inserted in the file at the end of every contour. If list-directed output is used then the value of the marker card is 1.0E30, otherwise the user is prompted for a value for the marker card.

When output is complete, the user is informed of the number of contours that were written to the file.

ExampleA map contains two contours to be output to a file called ECL.CNT using the format (3F12.3). No clipping is required.


The file ECL.CNT will look like:

"Edt contours""Out contours"'Output in SAVE file format ? (y/N)' ( N is entered )'Enter output file root' ( ECL is entered )File ECL.CNT opened ...&'Clip output data to model area ? (y/N)' ( N is entered )'Enter record format, e.g. (3E13.5) or RETURN for *' ( (3F12.3) is entered )'Enter contour value on marker card or RETURN for 999999.' ( RETURN is entered )2 contours output...&

RECORD 1:(3F12.3)RECORD 2: 999999.000 999999.000 999999.000RECORD 3: 273926.406 320046.063 100.000RECORD 4: 278242.468 327856.593 100.000RECORD 5: 282516.062 336018.000 100.000RECORD 6: 999999.000 999999.000 999999.000RECORD 7: 296861.000 349817.812 200.000RECORD 8: 310834.437 357874.281 200.000RECORD 9: 326619.687 361741.531 200.000


www.cadfamily.com

134 Edit Map GRID Reference ManualSample contours P.2.4.9

Sample contours P.2.4.9

Smp contours

PurposeSample a map containing digitized contours or scattered data.


This “Smp contours” menu allows a map to be sampled for test purposes so that interpolation parameters can be fine-tuned or other adjustments made to the map.

Typically, a user would define the interpolation parameters for a particular map and perform a number of “Tst point” operations to check what interpolated values would be returned. After appropriate interpolation parameters have been selected, the option “Sho bck cnts” can be used to see what the mesh contours would look like if the map were to be sampled with these parameters.

Option 4 “Tst grid” is only available if a simulation grid has been loaded.

The “Return” option returns the user to the “Edt contours” menu options. Each of the other options is described in the relevant help sections.


Option Function

1 Return

2 Tst point

3 Tst map

4 Tst grid

5 Sho bck cnts

6 Out bck cnts

7 Chg interp

8 Chg bck cnts

9 Var transfrm

Test point

Test map

Test grid

Show back contours

Output back contours

Change interpolation

Change back contour display

Select variable transformation


www.cadfamily.com

GRID Reference Manual Edit MapTest point P.2.4.9.2

135

Test point P.2.4.9.2

Tst point

PurposeSample the value of a point on the current map, using the current interpolation parameters.

DescriptionThe user is asked to select the point on the map to be sampled.

Sampling will be done with the interpolation parameters that are defined for the current map.

When the interpolation is complete, the control points used for sampling are highlighted on the screen and the search circle is drawn. The map coordinates of the point are displayed at the bottom of the screen together with the sampled value, which is also written to the log file (LOG.RF).

If a fixed search radius is used for digitized contours, where there is a high density of contour points it may be necessary to reduce the search radius, to keep the number of sampled values below the current limit of 500 points. If this occurs, a warning message will be displayed. A warning will also be displayed if the number of fault segments is too large for the current buffer size.


www.cadfamily.com

136 Edit Map GRID Reference ManualTest map P.2.4.9.3

Test map P.2.4.9.3

Tst map

PurposeScan a digitized map for areas with insufficient data for interpolation with the given search criteria. Assist the user to improve the data distribution or select more appropriate search criteria, and thus obtain an optimal balance between interpolation quality and gridding speed.

DescriptionThe purpose of this option is to scan a digitized map and highlight areas of the map that have a sparse distribution of data. Clusters of data points are sampled for these areas using a radial search method. The extra data points can be added to the original data as new control points if the user wishes. An optimal fixed search radius is also derived from the radial search. This should be saved with the map if the user chooses to save the clustered data points.

Use of the “Tst map” option is recommended if digitized maps are to be gridded or sampled.

On selecting the option “Tst map”, the user is prompted to choose to scan contour lines or digitized points and asked for the number of lines or points required in the search circle. The fewer the number of required lines or points given, the smaller the final search radius is likely to be. The default value of 5 lines or 20 points is recommended for most maps.

The initial scan for areas of sparse data will then begin and will not take long. Any areas on the map where interpolation will not be performed using the current search criteria will be highlighted as clusters on the screen. The user is asked whether to save the new data points. If the new clusters of data are too few or too many it is possible to go back and redefine the number of lines or points to be used in the search.

If the user elects to save the new clusters of data, a prompt will be made for the number of points in each of the 16 sectors of the search circle. Interpolation of values for the new clusters will then begin. Interpolating with the radial search method is heavy on CPU and may take some time.

When Z values have been interpolated for the clustered data, the optimum search radius used is returned to the user. This should be saved with the map, as significant increases in speed will be made subsequently, when sampling the map for meshes or simulation grids.


www.cadfamily.com

GRID Reference Manual Edit MapTest grid P.2.4.9.4

137

Test grid P.2.4.9.4

Tst grid

PurposeSample nodes or blocks of a simulation grid.

DescriptionThis option should be used when preparing maps for sampling on a simulation grid, to check the interpolation parameters for each map. If the grid cannot be sampled successfully, adjustments should be made to the parameters at this stage, before sampling the grid in menu P.3, “Edt grid” (page 276). Note that the grid to be sampled must be loaded into the program via “Edt grid” before entering this option.

The following menu is displayed:

The “Return” option returns the user to the “Smp contours” menu. The “Tst point” option is as described in P.2.4.9.2 (page 135). Each of the other options is described in the relevant help section.


Option Function

1 Return

2 Tst point

3 Tst node

4 Tst block

5 Tst all ndes

6 Tst all blks

7 Edt smp vals

8 Put grd crns

9 Put grd prps

Test point

Test node

Test block

Test all nodes

Test all blocks

Edit sampled values

Save corner values on grid

Save block values as grid property


www.cadfamily.com

138 Edit Map GRID Reference ManualTest node P.2.4.9.4.3

Test node P.2.4.9.4.3

Tst node

PurposeTest sample a grid node.

DescriptionThe user is asked to select the node to be sampled. The node is highlighted and the sampled value for the selected corner of the node is displayed at the bottom of the screen.


www.cadfamily.com

GRID Reference Manual Edit MapTest block P.2.4.9.4.4

139

Test block P.2.4.9.4.4

Tst block

PurposeTest sample a grid block.

DescriptionThe user is asked to select the block to be sampled. The block is highlighted and the sampled value for the selected block is displayed at the bottom of the screen.

The following menu is displayed for obtaining block values:

The “Blk centre” option simply samples the map at the centre of the selected block.

The “Ave corners” option samples the four corners of the grid block and returns the average.

The “Ave cen+crn” option samples the four corners and the centre of the block and returns an centre-weighted average.

The “Ave fne grd” option constructs a fine grid within the grid block, samples at the centre of each fine grid block and returns the average.

The “Blk edge” option is used when an array of boundary conditions is required along an edge of a simulation grid. The block is sampled at the centres of the required edges (top, bottom, left or right).

Table 5.9 Menu P.2.4.9.4.4

Option Function

1 Return

2 Blk centre

3 Ave corners

4 Ave cen+crn

5 Ave fne grd

6 Blk edge

Block centre

Average corners

Average centre + corners

Average fine grid

Block edge


www.cadfamily.com

140 Edit Map GRID Reference ManualTest all nodes P.2.4.9.4.5

Test all nodes P.2.4.9.4.5

Tst all ndes

PurposeTest sample all grid nodes.

DescriptionThe map is interpolated at all the grid nodes and the results are stored in a local array. The results can be interrogated, changed or output from the “Edt smp vals” option (see page 142).

This option is used to ensure that a grid is being sampled correctly before actually setting the grid depths. If the sampling is not satisfactory, the interpolation parameters can be changed or new data added, while in the “Edt map” part of the program (see page 57).


www.cadfamily.com

GRID Reference Manual Edit MapTest all blocks P.2.4.9.4.6

141

Test all blocks P.2.4.9.4.6

Tst all blks

PurposeTest sample all grid blocks.

DescriptionThe map is interpolated for all the grid blocks on the current grid layer and the results stored in a local array. The results can be interrogated, changed or output from the “Edt smp vals” option (see page 142). A number of options are available for obtaining block values, as described for the “Tst blk” option (see page 139).

This option is used to ensure that the map is being sampled correctly before actually setting any grid values. If the sampling is not satisfactory, the interpolation parameters can be changed or new data added while in the “Edt map” part of the program (see page 57).


www.cadfamily.com

142 Edit Map GRID Reference ManualEdit sample values P.2.4.9.4.7

Edit sample values P.2.4.9.4.7

Edt smp vals

PurposeEdit or output sampled node or block values.


The “Return” option returns the user to the “Tst grid” menu. The other options are described in the following sections.

It is not possible to enter this menu unless all nodes or all grid blocks have been sampled previously, by selecting “Tst all ndes” or “Tst all blks” on the “Tst grid” menu.

Table 5.10 Menu P.2.4.9.4.7

Option Function

1 Return

2 Sho blk val

3 Def blk val

4 Sho crn val

5 Def crn val

6 Out blk vals

7 Out crn vals

8 Out nde vals

9 Sho smp cnts

Show block values

Define block values

Show corner values

Define corner values

Output block values

Output corner values

Output node values

Show sample contours


www.cadfamily.com

GRID Reference Manual Edit MapShow block value P.2.4.9.4.7.2

143

Show block value P.2.4.9.4.7.2

Sho blk val

PurposeShow sampled value for a grid block.

DescriptionThe user is asked to select the block to be shown. The block is highlighted and the sampled value for the selected block is displayed at the bottom of the screen.


www.cadfamily.com

144 Edit Map GRID Reference ManualDefine block value P.2.4.9.4.7.3

Define block value P.2.4.9.4.7.3

Def blk val

PurposeRedefine sampled value for a grid block.

DescriptionThe user is asked to select the block to be defined. The block is highlighted and a new value can be entered.


www.cadfamily.com

GRID Reference Manual Edit MapShow corner value P.2.4.9.4.7.4

145

Show corner value P.2.4.9.4.7.4

Sho crn val

PurposeShow sampled value for a grid node corner.

DescriptionThe user is asked to select the node to be shown. The node is highlighted and the sampled value for the selected corner of the node is displayed at the bottom of the screen.


www.cadfamily.com

146 Edit Map GRID Reference ManualDefine corner value P.2.4.9.4.7.5

Define corner value P.2.4.9.4.7.5

Def crn val

PurposeRedefine sampled value for a grid node corner.

DescriptionThe user is asked to select the corner of the node to be defined. The node is highlighted and a new value can be entered. The values at each corner of the node will be reset according to the manner in which the node is split.


www.cadfamily.com

GRID Reference Manual Edit MapOutput block values P.2.4.9.4.7.6

147

Output block values P.2.4.9.4.7.6

Out blk val

PurposeOutput sampled block values.

DescriptionThe sampled values can be output to a file in a format suitable for input to a reservoir simulator. Output is written to a file with extension .GRDECL (or .GEC if 3-character file extensions are used). If a file of this type is already open, the new output will be added to that file. Otherwise a new file will be created. If the file already exists, the user is asked whether it should be overwritten. The file may optionally be closed after writing the sampled values.

The user is prompted for the name of the keyword which is to be used as a header for the array. The data output is preceded by the BOX keyword to indicate the grid layer used for sampling.


www.cadfamily.com

148 Edit Map GRID Reference ManualOutput corner values P.2.4.9.4.7.7

Output corner values P.2.4.9.4.7.7

Out crn val

PurposeOutput sampled corner values.




www.cadfamily.com

GRID Reference Manual Edit MapOutput node values P.2.4.9.4.7.8

149

Output node values P.2.4.9.4.7.8

Out nde vals

PurposeOutput sampled node values.



This option differs from the previous option (“Out crn vals”, page 148) in that only one value is output for each grid node, irrespective of whether the node is split. The value of the top, left node corner is the output value. However, the previous option should be used if the grid does contain split nodes.


www.cadfamily.com

150 Edit Map GRID Reference ManualShow sampled contours P.2.4.9.4.7.9

Show sampled contours P.2.4.9.4.7.9

Sho smp cnts

PurposeContour back sampled block or node values.

DescriptionThe sample node or block values can be contoured back at any suitable contour interval and contour quality, with optional colour fill.

If contours are already drawn reselection of this option removes them.


www.cadfamily.com

GRID Reference Manual Edit MapSave corner values on grid P.2.4.9.4.8

151

Save corner values on grid P.2.4.9.4.8

Put grd crns

PurposeSave the sampled corner values on the simulation grid.

DescriptionThis option allows the user to save the corner point values obtained by sampling the current map on the current simulation grid layer. The option “Tst all ndes” must first be used to test sample all the grid nodes.

The user is prompted to indicate whether the map represents depth or thickness values:

If the response is neither ‘D’ nor ‘T’, the grid will not be modified.

If the map represents depths, further prompts are issued, allowing the user to choose whether to change the layers above or below the current layer. If the map represents thickness, the top or bottom of the layer may be changed, and the layers above or below the current one can also be reset accordingly.

The grid changes can be abandoned by selecting the Abandon option from the “Tst grid” menu. On exit from the “Tst grid” menu, the user will be given the option to save the simulation grid on disk.

Note This option is available to allow users to save sampled data immediately, instead of resampling the map from the “Edt grid” menu (P.3). However, the recommended method for setting grid corner depths is to use “Edt grid”.

The sampled corner point values may also be saved to an ASCII file, using option P.2.4.9.4.7.7, “Out crn vals” (see page 148).

Are map values depth, thickness or other ? (D/t/o)


www.cadfamily.com

152 Edit Map GRID Reference ManualSave block values as grid property v P.2.4.9.4.9

Save block values as grid property v P.2.4.9.4.9

Put grd prps

PurposeSave the sampled block values as a simulation grid property.

DescriptionThis option allows the user to save the block values obtained by sampling the current map. The option “Tst all blks” (see page 141) must first be used to test sample all the grid blocks.

The user is prompted for the name of the property to be saved. This must be a grid property which has already been defined via the grid editing option P.3.8.5, “Edt property” (see page 384). New properties cannot be created from within “Tst grid” (see page 137). The sampled block values will be copied to the selected property for the current grid layer.

The grid changes can be abandoned by selecting the Abandon option from the “Tst grid” menu. On exit from the “Tst grid” menu, the user will be given the option to save the simulation grid on disk.

Note This option is available to allow users to save sampled data immediately, instead of resampling the map from the “Edt grid” menu (P.3, see page 276). However, the recommended method for setting grid properties is to use “Edt grid”.

The sampled grid block values may also be saved to an ASCII file, using option P.2.4.9.4.7.6, “Out blk vals” (see page 147).


www.cadfamily.com

GRID Reference Manual Edit MapShow back contours P.2.4.9.5

153

Show back contours P.2.4.9.5

Sho bck cnts

PurposeShow back-interpolated contours of all or part of the current map so that they can be compared to the digitized contours.

DescriptionThe digitized data are first interpolated on to a regular grid mesh and then the back contours are drawn on the current map, in addition to the digitized contours.

Note Note that the actual mesh is not stored; it is only calculated to derive the back contours and is then discarded.

Back contours should be shown to check that appropriate interpolation parameters have been selected for the current map. If the back contours are not satisfactory, it may be necessary to digitize more data in sparse areas of the map and/or modify the interpolation parameters.

On selecting the option “Sho bck cnts”, the user is asked whether to contour the full map, current zoom area or a user-defined polygon. If a polygon is selected this may be digitized and saved to a file, or read from an existing file, or a zone boundary may be selected, if any zones are present on the current map. If only a particular area of a large map is of interest, considerable time may be saved by back contouring a polygon or the current zoom area.

The user is then prompted for the number of mesh rows and columns, the major and minor contour interval, the contour quality and whether or not colour fill is required. The number of mesh rows and columns defined will refer to the full map area. This ensures that consistent results are obtained when sampling part or all of the map.

Progress of the calculation of the mesh is indicated on the advice line at the bottom of the screen by the message:

Progress of the contouring is indicated on the advice line at the bottom of the screen by the message:

Back contours can be removed from the display by reselecting this menu option. Alternatively they can be removed by selecting option D.6.3.4.5, “Rem bck cnts” (see page 576), which allows the user to delete back contours without returning to the “Smp contours” menu, if they have been kept on the screen during later operations.

On some devices the colour fill capability can be used to great effect in conjunction with the “Chg fill” option P.2.4.9.8.3 (see page 170), which allows gradually changing colour sequences to be set up, rather than the default contrasting colours.

GRIDDING ROW 10GRIDDING ROW 20 ..... up to the number of mesh rows specified.

LINKING STRIP 10LINKING STRIP 20 .... up to the number of mesh rows X contour quality.


www.cadfamily.com

154 Edit Map GRID Reference ManualShow back contours P.2.4.9.5


www.cadfamily.com

GRID Reference Manual Edit MapOutput back contours P.2.4.9.6

155

Output back contours P.2.4.9.6

Out bck cnts

PurposeOutput back contours from the current map to a data file.

Note Note that this option may be selected only if back contours are actually shown on the current map.

DescriptionIf back contours are shown on the map, they may be output to a file and subsequently read into the program as if they had been digitized.

The user is prompted for the root name of the file to be opened for output. The output file will be given the name ‘root.CNT’.

The contours that are output to the file will be separated by a marker card (marker value 1.0E30) and will be written using list-directed output as for option P.2.4.8, “Out contours” (see page 132).


www.cadfamily.com

156 Edit Map GRID Reference ManualChange interpolation P.2.4.9.7

Change interpolation P.2.4.9.7

Chg interp

PurposeChange the interpolation parameters to be used when sampling the current map.


The “Return” option returns the user to the “Smp contours” menu. The other options are described in the relevant help sections.


Option Function

1 Return

2 Def null

3 Def trn vals

4 Def dmp fac

5 Def sch rad

6 Def int mod

7 Wgt well pts

8 Tog int flts

9 Tog min slp

Define null value

Define truncation values

Define damping factor

Define search radius

Define interpolation mode

Set weighting for well control points

Toggle faults in interpolation

Toggle minimum slope


www.cadfamily.com

GRID Reference Manual Edit MapDefine null P.2.4.9.7.2

157

Define null P.2.4.9.7.2

Def null

PurposeDefine the null value to be used when sampling.

DescriptionThe null value is used to denote a value where the interpolator is unable to determine a value. The default null value is 1000000.0.

Notes• It is recommended that null values should be outside the valid data range for the current

map. (Do not use the null value as a method of setting the default for sampling onto a simulation grid.)

• It is recommended that the same null value is used on all maps for a particular model, especially if mesh operations are to be undertaken at a later stage.

• Zero values should not be used for nulls, as this can cause problems with sampling, even if there are no zero data values on the map. The program will not accept new nulls with an absolute value less than 0.01.

• If null values are returned in unexpected positions when sampling a map, check the other interpolation parameters and the distribution of data on the map.


www.cadfamily.com

158 Edit Map GRID Reference ManualDefine truncation values P.2.4.9.7.3

Define truncation values P.2.4.9.7.3

Def trn vals

PurposeDefine floor and ceiling truncation values to be used when sampling.

DescriptionOn selecting this option, the user is asked if floor, ceiling, or local truncation are required. If floor or ceiling truncation is switched on, floor or ceiling values must be defined. Local truncation does not require a value, but is simply switched on or off.

If floor, ceiling or local truncation is switched on a prompt will be issued for a tolerance value. Best results will be obtained by setting the tolerance value to be 0.6 (60 per cent) of the minor contour interval.

The following points should be considered:

• If the tolerance is set to zero, the effect will be to literally truncate the data to the specified floor and ceiling limits.

• If the tolerance is non-zero, the interpolated value at a point may reach beyond the floor and ceiling limits, but interpolations beyond the limits will be contained within the specified tolerance. This has the effect of making the resulting surface slope continuous beyond the limits, with un-modified surface inside the limits.

• The default tolerances for a given map are set according to the actual data range. If all Z values are positive, the floor value is set to zero, but if the map includes negative data values, the floor value is reduced to the minimum data value. The normal default ceiling value is 1000000, but this will be increased to the maximum data value, if this is higher. If the map data are edited subsequently, to include values which fall outside the current limits, the program will reset the floor and ceiling limits according to the new data range.

FLOOR LEVEL TRUNCATION - Sets the minimum allowed interpolationvalue. Note that if all Z values are

positive, the default value is zero, sothat negative values will not be returnedunless this limit is changed.

CEILING LEVEL TRUNCATION - Sets the maximum allowed interpolationvalue.

LOCAL TRUNCATION - This has the effect of preventingspurious contours from being drawn onflat topped hills or valleys.


www.cadfamily.com

GRID Reference Manual Edit MapDefine damping factor P.2.4.9.7.4

159

Define damping factor P.2.4.9.7.4

Def dmp fac

PurposeDefine the damping factor to be used when sampling.

DescriptionThe damping factor is used to ensure that the distance weighting function does not tend to infinity at control points.

The default value is 0.0001 and such small values should be used, to closely honour the control points. However, increasing the value to say 0.01 or 0.1 has the effect of smoothing the data.

The use of the damping factor in the weighting function is discussed in the section on option P.2.4.9.7.6, “Def int mod” (see page 163).


www.cadfamily.com

160 Edit Map GRID Reference ManualDefine search radius P.2.4.9.7.5

Define search radius P.2.4.9.7.5

Def sch rad

PurposeDefine the search radius to be used when sampling.

DescriptionThe interpolation algorithm fits a polynomial surface to the control points within a ‘search radius’ from the sample point.

The search radius is the most important interpolation parameter that can be adjusted when sampling a map.

Four different types of search are available:

1 Fixed search radius

2 Variable search radius

3 Optimal search radius

4 Radial search method

Depending on the type of data to be sampled consideration must be given as to what type of search to use, for example:

• Digitized contours

• Scattered data (Well values or XYZ gravity & magnetic data)

• Meshed data

• Seismic data

The different types of search are discussed below:

Fixed Search RadiusThe search radius is set at a fixed value. A fixed search radius offers the advantage of high speed if the data is uniformly distributed and a near optimum value can be chosen. However, it may be difficult to choose a suitable value, even when data are evenly spread, and different search radii will give different results.


The search radius is measured as a fraction of the screen size, e.g. 0.2.

The value should be chosen so that at least three or four different value contours of different value fall within the search circle at all points of interest on the map.

• Scattered data


The value should be sufficiently large to encompass a representative selection of data at all points. If there are only a few data points (e.g. well values), then use a radius to include them all.

• Mesh data


www.cadfamily.com

GRID Reference Manual Edit MapDefine search radius P.2.4.9.7.5

161

The search radius is measured in units of mesh cell size. The default value of 2.05 will encompass an optimum 13 nodes on an unfaulted map. For heavily faulted maps larger values of the search radius may have to be used to prevent the occurrence of nulls. In this case A value of 3.05 should be sufficient.

• Seismic data


The value should be chosen so that at least three or four different shotlines fall within the search circle at all points of interest on the map.

Variable Search RadiusThis method is the default method for digitized maps. A pre-sweep of the data is made to set a radius appropriate to different areas of the map. The radius will then vary continuously over the map, being smaller in areas of dense data and larger in areas of sparse data. The limits of the variation can be changed by the user.

On selecting a Variable Search radius, the user is prompted for the degree of variation required, for example: the default value is 3.0 which allows the search radius to vary by a factor of 3 from its mean value.


A variable search radius will yield good results, especially if the density of the data varies over the map. However, on some data sets the search radius may be wrongly predicted, particularly in the presence of faults. Depending on the density of digitized contours on the map, a choice of 3 - 5 different valued contours should be made.

• Scattered data

The variable search radius is not suited to scattered data.

• Mesh data

Not available for mesh data.

• Seismic data

A variable search radius will yield best results as the method is most suited to line oriented data.

The variable search radius offers the advantage of repeatable results and the treatment is more appropriate than a fixed search radius over a map with variable density data.

Optimal Search MethodIf Optimal Search radius is selected, each time the map is sampled, the program will attempt to find the most suitable fixed radius for use at all points on the entire map. Processing is then as for Fixed Search Radius.

Radial Search MethodUsed in “Tst map” only.

The Radial Search Method, although slow, should give good results in nearly every case and avoid null values interior to maps. The method is used for finding values in areas of sparse data when using the “Tst map” facility.


www.cadfamily.com

162 Edit Map GRID Reference ManualDefine search radius P.2.4.9.7.5

The radial search method makes maximum use of the available data in all directions from the interpolation point. Only a limited number of points are selected in each of the 16 sectors of the search area radiating from the interpolation point so that the calculation is not swamped with points on one side in order to have sufficient on the other. However, the method is really only suitable for finding a small number of isolated points, partly because the method is rather slow, but mainly because, unlike the other methods, it does not represent a slope continuous function over the area of the map.

Number Of OctantsFinally the user is prompted for the number of adjacent octants which may be empty before a null value is returned. A default value of 7 empty octants is set.

The octant check is performed before the position of control points are checked with respect to faults. A small wedge of data on a narrow fault block is therefore not rejected by the octant check.

Gridding may be limited to the regions of the control data by reducing the number of octants to 4 or 5. In order to interpolate up to the corners of a mesh, the number of octants should be set to 7.


www.cadfamily.com

GRID Reference Manual Edit MapDefine interpolation mode P.2.4.9.7.6

163

Define interpolation mode P.2.4.9.7.6

Def int mod

PurposeDefine the interpolation mode to be used when sampling.

DescriptionThe interpolation algorithm fits a polynomial surface to the points within a ‘search’ radius from the required point. The polynomial surface which is fitted depends on the interpolation mode that is used. The different types of surface available are as follows:

For scattered data1 Weighted average of points in search circle.

2 Weighted least squares fit of reduced 2nd order surface. (Default)

3 Not used.

4 Returns the number of points in the circle.

5 Weighted least squares fit of plane surface.

6 Weighted least squares fit of full 2nd order surface.

For mesh data0 Do not interpolate (look up data values directly from mesh).

1 Weighted average.

2 Weighted least squares fit of plane surface. (Default)

3 Weighted least squares fit of reduced 2nd order surface.

4 Weighted least squares fit of full 2nd order surface.

The weighting function which is used is:

[EQ 5.1]

where

is the weight allocated to a control point

is the search radius

is the distance of the control point from the centre of the search circle

is the damping factor

Note the minimum number of data points which are required within the search circle, when interpolating scattered data. Averaging (mode 1) will work with any number of points. A minimum of 3 points is needed to fit a plane surface (mode 5). To fit a reduced 2nd order surface (mode 2), at least 5 data points are needed, and for a full 2nd order surface (mode 6), at least 6 points are needed in each sample.

W S R–( )2

R2 ES+--------------------=

W

S

R

E


www.cadfamily.com

164 Edit Map GRID Reference ManualDefine interpolation mode P.2.4.9.7.6

Note that interpolation mode 0 for mesh data simply takes the nearest mesh value to the point to be sampled. Faults are ignored. This option may be useful for very fine geostatistical data to be averaged on simulation grid blocks, or for taking values from a mesh where the data are integer-valued (e.g. lithofacies region identifiers).


www.cadfamily.com

GRID Reference Manual Edit MapSet weighting for well control points P.2.4.9.7.7

165

Set weighting for well control points P.2.4.9.7.7

Wgt well pts

PurposeSet weighting for well control points used in interpolation.

DescriptionBy default, no special weighting is applied to any control points in interpolation, and data values at wells are treated equally with data values on contours, etc.

If this option is selected, the user can select an integer weighting value (> 1) to be applied to well control points. The user is also prompted for the maximum distance from a well to a data point, defined as a fraction of the model width (i.e. in world coordinates, as for the search radius).

When sampling the contour map, the positions of wells on the map will be used to identify the control points to be weighted. The program selects the nearest point to each well, within the specified maximum range. A warning is issued if no such points are found (which may indicate that the specified maximum range is too small). The weighting is achieved by adding multiple control points to the sampled data (e.g. if the weight is 5, an extra 4 points will be used for each well control point).

This option will have no effect if no wells are present on the current map.

Note:

• If the well data values deviate significantly from the general surface defined by the contour values, it is quite likely that either the interpolation process will be unable to honour all points (regardless of weighting) or the well points will be honoured but the interpolated surface will not be realistic. This may be improved by varying other parameters such as search radius, interpolation mode, etc., or it may be necessary to reinterpret the mapped surface in the region of the wells.

• Changing the well control point weighting alone may give unacceptable results (e.g. ‘bull’s-eye’ patterns in the back contours).

• The weighting method may be inefficient in use of space and processing time, if very large numbers of wells are present.

• If there are two or more data points equally close to a well but with different values, the program will select the first point found. It is the user’s responsibility to resolve the ambiguity by removing any anomalous points and/or redefining the required well control point.


www.cadfamily.com

166 Edit Map GRID Reference ManualToggle faults in interpolation P.2.4.9.7.8

Toggle faults in interpolation P.2.4.9.7.8

Tog int flts

PurposeToggle (on or off) the inclusion of faults in the interpolation algorithm.

DescriptionThe fault lines on the map can be excluded from the interpolation algorithm. This option will speed up the interpolation time of maps for which the faults may be ignored. For example, although the Tops contours may be discontinuous at fault lines, isopach or property contours may be continuous.


www.cadfamily.com

GRID Reference Manual Edit MapToggle minimum slope P.2.4.9.7.9

167

Toggle minimum slope P.2.4.9.7.9

Tog min slp

PurposeTo toggle the ‘minimum slope’ switch. This switch is used to improve the contouring of data that has limiting values, e.g. a percentage which may take any value between and including 0 & 100 but no value outside this range.

DescriptionThe normal bicubic interpolation process uses average partial derivative information at each mesh node to control the slope and to impart slope continuity to surfaces. This has the effect of causing overthrow when a parameter reaches its limiting value.

This effect can be eliminated by togging the ‘minimum slope’ switch on, which causes the minimum partial derivatives to be used at each node (derived by differencing neighboring nodes) rather than the average.

Note that, if the limiting value contour is required, a much improved effect can be obtained by preprocessing the mesh to selectively offset instances of the limiting value by a fraction of the contour interval. The limiting value contour will then be drawn in a coherent way surrounding the instances in the mesh rather than appearing profusely in random geometric patterns all over the area where the parameter is at its limiting value.


www.cadfamily.com

168 Edit Map GRID Reference ManualChange back contour display P.2.4.9.8

Change back contour display P.2.4.9.8

Chg bck cnts

PurposeChange the Granite settings and colour fill for back contours.


The “Return” option returns the user to the “Smp contours” menu options. Each of the other options is described in the relevant help sections.

Note that Granite settings for digitized contours are changed with menu P.2.4.6.6. (see page 127).


Option Function

1 Return

2 Chg granite

3 Chg fill


Change colour fill


www.cadfamily.com

GRID Reference Manual Edit MapChange Granite settings P.2.4.9.8.2

169

Change Granite settings P.2.4.9.8.2

Chg granite

PurposeChange the pen and text representation to be used for ‘back contours’ on the current map. (Not digitized contours)


The “Return” option returns the user to the “Chg bck cnts” menu. Each of options 2 to 5 leads to a further menu for setting Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current default Granite attributes for the major or minor back contour line or text. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.

Option 6 allows the number of decimal places used on ‘back contour’ labels to be defined. Enter ‘I’ if integer labels are required.

Note Granite settings for digitized contours are changed via menu P.2.4.6.6. (see page 127).

Table 5.13 Menu P.2.4.9.8.2

Option Function

1 Return

2 Def maj pen

3 Def min pen

4 Def maj txt

5 Def min txt

6 Chg num dec





Change number of decimal places


www.cadfamily.com

170 Edit Map GRID Reference ManualChange colour fill P.2.4.9.8.3

Change colour fill P.2.4.9.8.3

Chg fill

PurposeChange the colours used for colour filled ‘back contours’ or grid blocks.

Note that this option should only be selected after the colour fill is displayed on the screen. If colour fill is displayed after the colours are changed, any colours defined here will be overwritten.

DescriptionA number of different methods are available for changing the colours used. The following menu is displayed:

Table 5.14 Menu P.2.4.9.8.3

Option Function

1 Return2 Num styles3 Chg index4 Chg limits5 Set shading6 Res colours

Number of stylesChange indexChange limitsSet shadingReset colours


www.cadfamily.com

GRID Reference Manual Edit MapNumber of styles P.2.4.9.8.3.2

171

Number of styles P.2.4.9.8.3.2

Num styles

PurposeSet the number of colour fill styles used.

DescriptionThe number of different colour fill styles used for filling contours can be reset.

By default the fill area representations 1-8 (inclusive) are set using the colour representations 8-15 (inclusive), so that:

If more than 8 colours are required for colour fill, colour representations 16 upwards should be defined accordingly.

Note Colour representations 0-7 (inclusive) are used for the display of menu options etc. and it is therefore not advisable to re-define their representations.

The user may find the “Set shading” option (see page 174) convenient for setting colour representations rather than setting individual colours.

If an attempt is made to use more colours than the current device can support, it may be found that the colour representations for other objects on the screen are inadvertently changed.

Table 5.15 Default fill area representation settings

Fill area representation

Uses colour representation

1 8

2 9

3 10

4 11

5 12

6 13

7 14

8 15


www.cadfamily.com

172 Edit Map GRID Reference ManualChange index P.2.4.9.8.3.3

Change index P.2.4.9.8.3.3

Chg index

PurposeChange the fill area representation for a given index.

DescriptionThe fill area representation for a given fill area index can be set. The following menu is displayed:

See Appendix C for further details on fill area representations.

Note that if the “Sho examples” option is selected, the current map display will be replaced by a summary of the current default Granite attributes for the selected fill area. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.

Table 5.16 Menu P.2.4.9.8.3.3

Option Function

1 Return

2 Chg style

3 Chg hatch

4 Chg colour

5 Sho examples

Change fill area style

Change hatch style

Change fill area colour index

Show examples


www.cadfamily.com

GRID Reference Manual Edit MapChange limits P.2.4.9.8.3.4

173

Change limits P.2.4.9.8.3.4

Chg limits

PurposeChange the contour limits to be associated with a particular fill area index.

DescriptionBy default, the range between the minimum and maximum contour value is divided by the number of ‘fill styles’ defined by the user. Fill area indices are then changed at the nearest major contour value to the calculated limits.

This option allows the default limits to be overridden. The user is prompted for the lower and upper limits for a selected fill area index.


www.cadfamily.com

174 Edit Map GRID Reference ManualSet shading P.2.4.9.8.3.5

Set shading P.2.4.9.8.3.5

Set shading

PurposeSet gradations of colour shading to be used for colour fill.

DescriptionThis option allows the colour fill to be set up with gradual shading from one colour to another.

The user is asked how many colours are to be used for the shading process. The user should enter a number that is related to the number of major contour levels on the map (see note below).

A colour intensity value is then requested. An intensity of 1.0 will give clear, sharp and bright colours, but if a smaller intensity value is specified, say 0.75 or 0.5 then the colours will be more mute. A default intensity of 0.75 is offered, as this has been found to give good results on a variety of workstations and plotters.

The user is prompted for a colour number for the minimum value in the sequence. The colour number specified will be used for sequence number 1, corresponding to the minimum data interval. Prompts are then issued for further sequence numbers and colours. (If no sequence number value is entered then the last sequence number will be assumed.)

Colour indices 0-7 are as follows:

Colour indices 8 upwards are used for colour fill and are likely to be modified as the colour shades are set.

Colour representations for sequence numbers that have not been set are calculated by linear interpolation between the sequence numbers that are set. The maximum number of shades which can be set depends on the capabilities of the device being used. Note that it is usually necessary to refresh the screen before the new shading is obtained, although some changes may be observed immediately.

Table 5.17 Colour indices

Index Colour

0 Black

1 White

2 Red

3 Green

4 Yellow

5 Blue

6 Cyan

7 Magenta


www.cadfamily.com

GRID Reference Manual Edit MapSet shading P.2.4.9.8.3.5

175

The following typical dialogue creates a shading sequence from white, through cyan to blue, using 70 colour intervals.

NoteThe actual shading obtained will depend on the display device capabilities and the major contour intervals used for the map. E.g. if there are only five different valued contours on a map then only be four different colours can be used, so it would be no use defining the number of colours to be greater than four!

The number of colours specified is used to define a sequence ranging from the minimum contour value to the maximum value, for example: For a contour range from 100m to 375m, at a 25m interval, a suitable number of colours would be 12, one colour for each contour interval.

The algorithm for producing colour fill between contours uses the major contour intervals to define colour interval ranges, and these may not correspond exactly to the default ranges set up by the user. Note, however, that the key displayed will correspond to the ranges actually obtained.

It may be possible to improve the colour shading by modifying the contour intervals used (e.g. for a mesh display, see menu option P.2.5.6.5 “Chg cnt int”, page 198).

Enter number of colours (2 to 256) or RETURN for 70 ' 'Enter colour intensity or RETURN for 0.75 ' ' Enter colour number for first interval or RETURN for 2 '1' (white) Enter interval number for next colour or RETURN for the last one '35' Enter colour number or RETURN for 7 ' ' (cyan) Enter interval number for next colour or RETURN for the last one ' ' Enter colour number for last interval or RETURN for 7 '5' (blue) Redraw picture (Y/n) 'Y'

Contour valuesSequence Number

100m (Minimum) 1

125m 2

150m 3

175m 4

200m 5

225m 6

250m 7

275m 8

300m 9

325m 10

350m 11

375m 12


www.cadfamily.com

176 Edit Map GRID Reference ManualReset colours P.2.4.9.8.3.6

Reset colours P.2.4.9.8.3.6

Res colours

PurposeReset colour representations.

DescriptionThe colours which have been set using the “Set shading” option can be reset to their original colours.

If when setting the shading the number of styles was not changed then the resetting of colours will occur instantaneously; otherwise the picture must be redrawn.


www.cadfamily.com

GRID Reference Manual Edit MapSelect variable transformation P.2.4.9.9

177

Select variable transformation P.2.4.9.9

Var transfrm

PurposeAllows the interpolation variables to be transformed to LOG(Z) or 1/Z instead of interpolating natural data. For the log transform, logarithmically spaced contours may be used.

DescriptionIf a log or inverse transform is selected, the data will be transformed before interpolation and the results will be converted back into natural data space. Data values less than or equal to zero will be treated as null.

For log interpolation, contours can be displayed on equal intervals or logarithmically spaced intervals. The user will be prompted for minor and major contour intervals as usual, but when log contours are displayed these will be used to define the number of contours per decade.

This option may be suitable for certain types of property data, such as permeability, depending on the data distribution. It should be used with caution and is not recommended for structure data such as TOPS maps.


www.cadfamily.com

178 Edit Map GRID Reference ManualSelect variable transformation P.2.4.9.9


www.cadfamily.com

GRID Reference Manual Edit MapEdit mesh P.2.5

179

Edit mesh P.2.5

Edt mesh

PurposeEdit a mesh.

DescriptionThis menu can be entered only if digitized contours have not been defined previously. The following menu is displayed:

As an alternative to representing the geological surface as a set of data points, the surface may be stored as a ‘mesh’. A mesh is a regular grid for which surface values are known at nodes. Meshes are commonly used by mapping packages since they can be manipulated easily. The term ‘mesh’ is used to differentiate these regular map grids from simulation grids (see Glossary).

The program can work with digitized data or with grid meshes, depending on the user’s preference or the operations that are required.

Note that after a mesh has been defined for a particular map stratum, it is not possible to enter the “Edt contours” menu.

The “Return” option returns the user to the “Edt map” menu options. Each of the other options is described in the following sections.

If the “Abandon” option is taken then any edits made during the current entry to the “Edt mesh” option will be discarded.


Option Function

1 Return

2 Inp mesh

3 Cal mesh

4 Opr mesh

5 Msk mesh

6 Chg msh pars

7 Def msh val

8 Out mesh

9 Smp mesh

Input mesh

Calculate mesh

Operate on mesh

Mask mesh

Change mesh parameters

Define mesh value

Output mesh

Sample mesh


www.cadfamily.com

180 Edit Map GRID Reference ManualInput mesh P.2.5.2

Input mesh P.2.5.2

Inp mesh

PurposeRead a grid mesh from a data file into the current map.

DescriptionThis option allows a regular grid mesh of data values to be read from an external file, which may have been created by the GRID program or a third party software package. The program offers a number of different formats for reading a mesh.

The user will be prompted first for the name of the input data file, and then given the option to read the file description from an external control file. An external control file can be generated by reading an input file interactively and then saving the file description. It consists of a list of parameter settings (one per line) and can be edited by the user.

If no control file is selected, the user is then prompted for the file type. The following file types may be selected, either by typing in one of the mnemonics shown here, or by entering ’H’ (for help) and then selecting the required type from a menu:

Note Other file formats can be set up on request provided that the format is available.

When a file type has been selected, the program will set up the default parameters for reading the data. Values which can be obtained from the file header will be identified, depending on the file type, and parameters which must be entered by the user will be set to suitable defaults. The file description will be displayed on the screen, and the user can then choose to change the default parameters, read the file or quit.

Table 5.2 Mesh file types

Type Description

ASCII Formatted text file of Z values

SAVE (CPS-1) Binary SAVE file

CPS-3 Binary file in CPS-3 (SVS) format

ISM Binary file in ISM format

ZMAP Formatted text file from ZMAP

LCT Formatted text file from LCT

IRAP-FORMAT Formatted text file from IRAP

IRAP-SINGLE Binary file in IRAP single map file format

IRAP-MULTI Binary file in IRAP multiple map format

SATTLEGGER Formatted text file from Sattlegger

XYZ Formatted text file of X,Y,Z values

EV-2DGRID Binary file in EarthVision '2D grid' format


www.cadfamily.com

GRID Reference Manual Edit MapInput mesh P.2.5.2

181

The file description parameters which may be changed will depend on the file type selected. In general, the following are considered:

For ASCII and XYZ formatted files, the user may choose to browse through the file and inspect the input data, before changing the file description. The first line of the data file will then appear at the bottom of the screen and the new menu will allow the user to skip through the file and view the data. Note that the program will not identify the start of the data from the last line viewed (as is the case with some other input options).

Further details are given below for each file type. Note that the user may redefine the areal position of the mesh, whether or not it is given in the input file header. To define the mesh position, further prompts will be issued, e.g.:

The minimum XY coordinate of the map will represent the mesh origin in XY. By defining an angle of rotation in degrees (+ve from X-axis, anti-clockwise), it is possible to display the mesh as a rotated system. The maximum XY coordinate will represent the limit of the mesh and should have the coordinate values of the opposite diagonal to the origin.

After the data file has been read successfully, the user can choose to save the file description to an external file.

Finally, the user is prompted for the contour interval, contour quality and the search radius to be used for redrawing contours and interpolating values.

NROW Number of mesh rowsNCOL Number of mesh columnsXMIN Minimum X valueYMIN Minimum Y valueXMAX Maximum X valueYMAX Maximum Y valueANGLE Angle of rotation of mesh

(decimal degrees, anticlockwise, positive from X-axis)MESHSIZE Sattlegger input only: triangular mesh spacing, used to compute the number

of rows and columns.NULL Null value used for data in the fileORIGIN Position of mesh origin (at row=1, column=1), top left or bottom leftORDER Order of data in file, defined by indicating whether the second data point is

along the first row or the first columnBLOCK Flag indicating whether data are blocked, or written in a single recordSTART For an ASCII or XYZ file, the line number containing the first data value

(after the header). For an IRAP multiple map file, the file number (layer) required.

FORMAT The Fortran format to be used for reading a text file.PROJCHECK EarthVision input only: YES or NO to indicate whether the projection

parameters and model area are to be checked.

Enter minimum X,Y or RETURN for 540000.,5995000.Enter angle of rotation degrees decimal (+ve) or RETURN for .000Enter maximum X,Y or RETURN for 570000.,6030000.


www.cadfamily.com


Note Note that the use of NULL values has changed for GRID version 94A. In previous versions of the program, the current null value for the map was used as a maximum data value when storing Z values read from a file. For example, if the map null value was 1000000.0 and the file contained values of 1.0E30, these would then be stored as 1000000.0.

The NULL parameter is now identified from the file header when possible, and whenever a data value equal to NULL is encountered, it will be stored as the current defined null value for the map. This may result in changes to the way that some values are processed. E.g. if indeterminate data in a file are set to 1.0E30 and the user sets the NULL parameter to 1.0E6 when loading data, values of 1.0E30 in the file will be treated like normal data values.

ASCII filesThe default structure for ASCII formatted files is:

ASCII file example:

For an ASCII file with non-default structure, the user can identify the parameters to be read from the header, the position of the first line of data, the ordering of data in the file and the format to be used for input.

The following parameters may be read from the header:

NROW, NCOL, XMIN, YMIN, XMAX, YMAX, ANGLE, NULL

The user must indicate the line containing the data and its position in the line. Data items should be separated by spaces and/or commas. Parameters which are not defined in the file header may be defined by the user, or the current defaults for the map may be used.

Data ordering:

ASCII files may have the mesh data specified in one of four orders, depending on the mesh origin (top or bottom left), the order in which the data points were written to the file and whether the data was written in blocks of rows or columns:

• First data value is top left hand corner of mesh and second data value is along the first row.

• First data value is top left hand corner of mesh and second data value is along the first column.

• First data value is bottom left hand corner of mesh and second data value is along the first row.

• First data value is bottom left hand corner of mesh and second data value is along the first column.

Record 1 no. of rows (NROW) no. of columns (NCOL)Records 2 to End-of-file NROW x NCOL items of grid data

5 46900.00 7000.00 7100.00 7000.00 7200.007000.00 7100.00 7000.00 6900.00 7000.007100.00 7000.00 6900.00 6800.00 6850.007000.00 6900.00 6800.00 6700.00 6720.00


www.cadfamily.com


183

The following prompts allow the order of the input points to be set:

If the data is not blocked, then it will have been output as a single list of Z values, e.g.:

If the data IS blocked, then it may be blocked by row or column, depending on the order of data storage. If the second data point is along the first column, the file is assumed to be blocked by row, whereas if the second data point is along the first row, the file is assumed to be blocked by column. (Any other arrangement would be logically incorrect.)

Data blocked by row would have been output by statements such as:

Data blocked by column would have been output by statements such as:

If the order of points is not given correctly the contour map may be drawn upside down or back to front.

Format:

The mesh data can be read using list-directed input or using a user-supplied Fortran format. If a user-specified format is given, a check is made to ensure the format statement is enclosed within brackets. If it is not, brackets will be added. There is usually no need to specify a format, provided that there are spaces between the data elements.

SAVE (CPS-1) file formatThis is a binary file, usually with file extension .sav

This format is available with or without an extended header. The extended header format should be used to read SAVE files that have been generated by CPS, when the user responded YES to the prompt ’Write parameter record?’ in the CPS-1 Save file option.

If this file type is selected, GRID prompts the user:

Is the first point at the top left corner or the bottom left corner ? (T/b)Is the second data point along the first row or the first column ? (r/C) Is the data stored in blocks ? (Y/n)

WRITE(LUNOUT,ZFMT) (RVAL(I), I = 1, NROW*NCOL)

IVAL = 0DO 190 I = 1, NCOL

WRITE(LUNOUT,ZFMT) (RVAL(IVAL+I), I = 1, NROW)IVAL = IVAL + NROW

190 CONTINUE

IVAL = 0DO 290 I = 1, NROW

WRITE(LUNOUT,ZFMT) (RVAL(IVAL+I), I = 1, NCOL)IVAL = IVAL + NCOL

290 CONTINUE

Does file have extended header section ? (y/N)


www.cadfamily.com


Use of the extended header can also be selected in the control file, by the command line:

The file structure is as follows:

Short header format

The number of rows and columns will be taken from the file header. The user may specify the following parameters:

XMIN, YMIN, XMAX, YMAX, ANGLE, NULL

Extended header format



CPS-3 file formatThis is a binary file format, usually with the file extension .svs.

TYPE SAVE (CPS-1) EXTENDED

Record 1 4 integers as follows:Integer 1 dummyInteger 2 no. of rows (NROW)Integer 3 no. of columns (NCOL)Integer 4 dummy

Record 2 NROW grid values for column 1.Record NCOL+1 NROW grid values for column NCOL

Record 1 4 integers, treated as dummies by GRIDRecord 2 80-character string, ignored by GRIDRecord 3 256 4-byte numbers, of which GRID reads the following:

Item 1 NROWItem 2 NCOLItem 5 XMINItem 6 XMAXItem 7 YMINItem 8 YMAXItem 25 NULL

Record 4 NROW grid values for column 1...Record NCOL+3 NROW grid values for column NCOL


www.cadfamily.com


185

The structure is as follows:

Data values for columns 2 to NCOL are held in pairs of records, in the same format as records 6 and 7.

The user may specify the following parameters, to define the areal position of the mesh:

XMIN, YMIN, XMAX, YMAX, ANGLE

ISM file format

This is a binary file format, with the following structure:



ZMAP file formatThis is a special case of the ASCII formatted text file, in the standard layout produced by ZMAP. The following information is read from the header:

NROW, NCOL, XMIN, YMIN, XMAX, YMAX, NULL



Record 4 Length of next data recordRecord 5 NROW bias values (added to Z values)Record 6 Length of next data recordRecord 7 Z values for first column, compressed to remove strings of nulls..

Record 1 320 characters:XMIN, XMAX, YMIN, YMAX, NULL are extracted from characters 161 to 240. NCOL, NROW are extracted from characters 241 to 248.

Record 2 160 characters (read if character 153 of record 1 is ’Y’)Record 3 NCOL grid values for row 1...Record NROW+2 NCOL grid values for row NROW


www.cadfamily.com


The user may choose to redefine the areal position of the mesh by specifying:


(Note that ZMAP formatted files may also be read by selecting the file type as ASCII and identifying the appropriate header items and file layout.)

LCT file format

This is a special case of the ASCII formatted text file, with the following structure:



(Note that LCT formatted files may also be read by selecting the file type as ASCII and identifying the appropriate header items and file layout.)

IRAP-FORMAT file formatIRAP ’Formatted File’ format is another special case of the ASCII file type. The file structure is as follows:

Old format

Before IRAP Version 6.1:

Record 1 header recordRecord 2 Xmin, Ymin, Xmax, Ymax, Ncol, Nrow in the format (4E14.7,2I5)Record 3 + grid values in format (10X,5E14.7) blocked by columns.

Record 1 2 integers and 2 reals as follows:Integer 1 no. of columns (NCOL)Integer 2 no. of rows (NROW)Real 1 row increment (XDEL)Real 2 col. increment (YDEL)

Record 2 4 real numbers as follows:Real 1 minimum X value (XMIN)Real 2 maximum X value (XMAX)Real 3 minimum Y value (YMIN)Real 4 maximum Y value (YMAX)

Record 3+ NCOL*NROW grid values, not necessarily blocked by rowReal 1 Row 1 Col 1Real 2 Row 1 Col 2Real 3 Row 1 Col 3...Real (NCOL*NROW)-1 Row NROW Col

NCOL-1Real (NCOL*NROW) Row NROW Col

NCOL


www.cadfamily.com


187

New format

IRAP Version 6.1 or later:

The default NULL value for this file type is 9999900.0.

If the file type IRAP-FORMAT is selected, the user is prompted to indicate whether it is OLD or NEW.

The number of rows and columns will be taken from the file header.

The user may specify the following parameters:


Note that although GRID can read a file in the NEW layout, containing information on the angle of rotation, this option has not been fully tested. If problems occur with use of a rotated mesh, define the mesh areal position and angle by hand, instead of using defaults from the file header.

IRAP formatted files may also be read by selecting the file type as ASCII and identifying the appropriate header items and file layout.

IRAP-SINGLE file formatIRAP ’Single Grid File’ files are binary files with the following structure:

Record 1 2 integers and 2 reals as follows:Integer 1 IRAP version identifierInteger 2 no. of rows (NROW)Real 1 row increment (XDEL)Real 2 col. increment (YDEL)

Record 2 4 real numbers as follows:Real 1 minimum X value (XMIN)Real 2 maximum X value (XMAX)Real 3 minimum Y value (YMIN)Real 4 maximum Y value (YMAX)

Record 3 1 integer and 3 reals as follows:Integer 1 no. of columns (NCOL)Real 1 angle of rotationReal 2 X-origin for rotationReal 3 Y-origin for rotation

Record 4 7 integers (IRAP internal use only)Record 5+ NCOL*NROW grid values, not necessarily blocked by row:

Real 1 - Row 1 Col 1Real 2 - Row 1 Col 2Real 3 - Row 1 Col 3...Real (NCOL*NROW)-1 Row NROW Col

NCOL-1Real (NCOL*NROW) Row NROW Col

NCOL


www.cadfamily.com


Old format

Before IRAP Version 6.1.

New format

IRAP Version 6.1 or later.

The default null value for reading this file type is set to 1.0E20 in GRID. However, this can be modified by the user if necessary. (NB: Some IRAP files contain null values of 1.0E30)

Record 1 2 integers and 6 real numbers, as follows:Integer 1 no. of columns (NCOL)Integer 2 no. of rows (NROW)Real 1 minimum X value (XMIN)Real 2 maximum X value (XMAX)Real 3 minimum Y value (YMIN)Real 4 maximum Y value (YMAX)Real 5 row increment (XDEL)Real 6 col. increment (YDEL)

Record 2 NCOL grid values for row 1...Record NROW+1 NCOL grid values for row NROW

Record 1 2 integers and 6 real numbers, as follows:Integer 1 - no. of columns (NCOL)Integer 2 - no. of rows (NROW)Real 1 - minimum X value (XMIN)Real 2 - maximum X value (XMAX)Real 3 - minimum Y value (YMIN)Real 4 - maximum Y value (YMAX)Real 5 - row increment (XDEL)Real 6 - col. increment (YDEL)

Record 2 1 integer and 3 reals as follows:Integer 1 - no. of columns (NCOL)Real 1 - angle of rotationReal 2 - X-origin for rotationReal 3 - Y-origin for rotation

Record 3 7 integers (IRAP internal use only)Record 4 NCOL grid values for row 1. . .Record NROW+3 NCOL grid values for row NROW


www.cadfamily.com


189

If the file type IRAP-SINGLE is selected, the user is prompted to indicate whether it is OLD or NEW.



Note that although GRID can read a file in the NEW layout, containing information on the angle of rotation, this option has not been fully tested. If problems occur with use of a rotated mesh, define the mesh areal position and angle by hand, instead of using defaults from the file header.

IRAP-MULTI file format

IRAP ‘Multiple Grid File’ files are binary files with the following structure:

Then for each IRAP file number (i.e. layer):

The user is prompted for the IRAP file number to be read.

The default null value for reading this file type is set to 0.1E31 in GRID. However, this can be modified by the user if necessary.

The user may specify the following parameters, to define the areal position of the mesh: XMIN, YMIN, XMAX, YMAX, ANGLE

Record 1 4 integers as follows:Integer 1 IRAP file number (i.e. layer)Integer 2 no. of columns (NCOL)Integer 3 no. of rows (NROW)Integer 4 IRAP file type (= 3)

Record 2 3 real numbers as follows:Real 1 minimum X value (XMIN)Real 2 maximum X value (XMAX)Real 3 row increment (XDEL)

Record 3 3 real numbers as follows:Real 1 minimum Y value (YMIN)Real 2 maximum Y value (YMAX)Real 3 col. increment (YDEL)

Record 1 4 integers as follows:Integer 1 IRAP file number (i.e. layer)Integer 2 no. of columns (NCOL)Integer 3 no. of rows (NROW)Integer 4 IRAP file type (= 3)

Record 2 NCOL grid values for row 1...Record NROW+1 NCOL grid values for row NROW


www.cadfamily.com


SATTLEGGER formatA Sattlegger type grid is treated by defining an appropriate rectangular grid mesh over the area covered by the triangular mesh and assigning null values to all grid nodes. Values are then assigned to nodes in the rectangular grid which are coincident with the triangular mesh. The resultant mesh therefore contains twice as many points as the original triangular mesh but the remaining null points are ignored during interpolation and contouring.

For these grids the first four records of the file are treated as comment cards, and the user should define the following parameters:


In addition, the user must enter the MESHSIZE parameter so that the grid can be constructed properly. This will be used to compute parameters XINC and YINC, indicating the X-increment and Y-increment for the mesh which will be stored by GRID. NCOL and NROW are computed internally from these values. The increments are calculated as:

[EQ 5.1]

[EQ 5.2]

This will place the Sattlegger data points exactly on mesh nodes, provided that the mesh position is defined correctly. (This can be checked if necessary by reading the Sattlegger data into another map as XYZ scattered data and overlaying the two maps.)

The data values in the file are read using a single record for each point, in the form:

x-coordinate, y-coordinate, value

The user is prompted for the format of the records. The grid data can be read using list-directed input or using a user-supplied format. If a user-specified format is given, a check is made to ensure the format statement is enclosed in brackets. If it is not, brackets will be added.

XYZ filesFiles in X,Y,Z format should have three columns of data, namely:

x-location y-location value

The user should define the number of mesh rows and columns.

If the file contains marker cards, the NULL parameter used for reading these data should be set to the marker value.

Each data point is assigned to the nearest node to the given x,y location. (This should correspond precisely to a node if the map area and number of rows and columns have been specified correctly.) Any nodes that have not been assigned a value when the end of file is reached will be left with null values.



EV-2DGRID (EarthVision '2D grid') filesThis is a binary file format produced by EarthVision (from Dynamic Graphics, Inc.). This type of file normally has extension .2grd. GRID can read this format on most Unix systems. (Contact customer support for advice if you see the error message 'Cannot read EarthVision 2D grid file on this machine'.)

XINC MESHSIZE2

-----------------------------=

YINC MESHSIZE 32

-------⋅=


www.cadfamily.com


191

EarthVision 2D grid files can be read via “Inp mesh” or via the “Mesh files” option of “Import maps” (P.6.3.2, see page 497). Note that projection checking is available from either of these options, but if you want to load associated fault trace files automatically, the “Mesh files” option must be used.

Note Note that EarthVision exchange files cannot be read in the same way as 2D mesh maps. Use the "Earthvision" option of “Import maps” (P.6.3.4, see page 497), which allows bulk input of data via the EarthVision-GRID exchange format.



In addition, the PROJCHECK parameter can be set to YES or NO to enable or disable checks on the projection and model area.


www.cadfamily.com

192 Edit Map GRID Reference ManualCalculate mesh P.2.5.3

Calculate mesh P.2.5.3

Cal mesh

PurposeCalculate a regular grid mesh to represent the current map.

DescriptionThis option allows a regular mesh to be calculated from other model data. The option employs a general input parser so that map or survey names can be used as variables in arithmetic and logical expressions. The parser is described in Appendix G, ‘Using Arithmetic Formulae’.

The user is asked whether to calculate the mesh for the full map, current zoom area or a user defined polygon. If a polygon is selected, it may be digitized and saved to a file or read from an existing file, or if zones are present on the map, the user may select a zone boundary.

The next prompt is for the name of the map or survey to be gridded. (An arithmetic or logical expression may be entered.) The stratum number of the map or the horizon number of the survey must be entered in brackets together with the name, otherwise a syntax error will be reported (e.g. TOPS(3)).

The user will also be asked for number of rows and columns required in the mesh. The rows and columns will cover the entire map area so that if gridding the current zoom area or a polygon then the results will be consistent with gridding the full map.

If a survey horizon appears in the formula the user is asked if time or depth data is to be used on each occurrence.

If digitized contours are used to calculate the new mesh, they will be interpolated using the current sampling parameters for the contour map.

When the mesh has been calculated, the user is prompted for the minor and major contour intervals and the contour quality with which the new map is to be drawn.

Note that if fault data are to be used with the new mesh map, the faults should be defined or copied via menu P.2.3, “Edt faults” (see page 73), before entering this option.


www.cadfamily.com

GRID Reference Manual Edit MapOperate on a mesh P.2.5.4

193

Operate on a mesh P.2.5.4

Opr mesh

PurposeOperate on the current mesh.

DescriptionThis option allows a regular mesh to be modified by arithmetic or logical operations, using other map data. The option employs a general input parser so that map or survey names can be used as variables in expressions. The use of the parser is described in Appendix G, "Arithmetic Formulae" on page 657.

This option differs from the “Cal mesh” option in that the mesh must have been defined previously.

Typical operations include:

• Multiplying by a constant to change Z units

• Adding or subtracting other mesh maps to generate isopachs.

The user is asked whether to operate on the full mesh, current zoom area or a user defined polygon. If a polygon is defined, it may be digitized and saved to a file or read from an existing file, or if zones are present on the map, the user may select a zone boundary. The user has the option to operate on the interior or exterior of the polygon.

Finally the operation to be performed must be entered. A full arithmetic or logical expression may be used, or an operation to be performed on the current map data may be entered as an arithmetic operator (+, -, *, /) followed by a constant or map name(s).

Note that the keyword NULL may be used to refer to null data values on a map, when performing operations, e.g.

If an error, such as attempted divide by zero, occurs while processing a map, the results will be set to NULL at the affected data points, and a warning will be issued.

If a survey horizon appears in the formula the user is asked if time or depth data is to be used on each occurrence.

A special operation is available to fill in null data values on a mesh: enter the keyword @FILL instead of an operation or expression. The map will be resampled at mesh nodes which currently have NULL data values. This may be useful for filling in data in fault regions, for example. Note that an alternative method is to resample the mesh directly by typing its name, e.g. TOPS(1). Use of @FILL will leave non-null values unchanged, but resampling the entire mesh may give smoother results. The edges of large groups of nulls are treated as boundaries. To interpolate null values inside these large null regions it is first necessary to switch off the null boundaries, P.2.5.9.4.7 "Tog nul bnd" (see page 210). The user can also use this option to choose whether to interpolate values only at the nodes at the edge of the null region, or at all nodes that have sufficient data within the search radius.

IF (MAPA(1) EQ NULL) THEN MAPB(1) ELSE MAPA(1) ENDIF


www.cadfamily.com

194 Edit Map GRID Reference ManualOperate on a mesh P.2.5.4

After the mesh operation has been performed, the user is prompted for the minor and major contour intervals and the contour quality with which the map is to be drawn.


www.cadfamily.com

GRID Reference Manual Edit MapMask a mesh P.2.5.5

195

Mask a mesh P.2.5.5

Msk mesh

PurposeMask part of the current mesh map, and set to null.

DescriptionAreas of the map which are not required, or where there are bad data points, can be masked using this option.

The user is prompted to choose whether to mask the sloping faults on the map or define a polygon. If sloping faults are selected, all nodes inside the sloping fault polygons are set to null.

Alternatively, the area to be masked is defined by digitizing a polygon, or loading the polygon definition from a file, or if zones are present on the current map, a zone boundary may be selected. The defined polygon may be saved to an external file if required.

The user is prompted to choose whether to mask the interior or exterior of the polygon, i.e. set all nodes inside or outside the polygon to null


www.cadfamily.com

196 Edit Map GRID Reference ManualChange mesh parameters P.2.5.6

Change mesh parameters P.2.5.6

Chg msh pars

PurposeChange parameters for drawing the mesh map.


The “Return” option returns the user to the “Edt mesh” menu. Options 2-4 and 9 are similar to the options for digitized contour maps. Each of the other options is described in the following sections.


Option Function

1 Return

2 Sho msh area

3 Chg msh area

4 Chg labels

5 Chg cnt int

6 Sho min max

7 Sho nulls

8 Def granite

9 Chg fill

Show mesh area (see page 123)

Change mesh area (see page 124)

Change contour labels

Change contour interval

Show minimum/maximum values

Show nulls

Define granite

Change colour fill


www.cadfamily.com

GRID Reference Manual Edit MapChange contour labels P.2.5.6.4

197

Change contour labels P.2.5.6.4

Chg labels

PurposeChange the number of decimal points on gridded contour labels for the current map.

DescriptionThe user is prompted for the number of decimal points required when drawing major or minor contours labels. Integer labels can be selected by entering the letter ‘I’.


www.cadfamily.com

198 Edit Map GRID Reference ManualChange contour interval P.2.5.6.5

Change contour interval P.2.5.6.5

Chg cnt int

PurposeChange the contour interval to be used when contouring the current mesh map.

DescriptionThe user is prompted for the major and minor contour intervals and the contour quality.

The contour quality provides control over the ‘jaggedness’ of the contour lines:

The quality may be increased to any number, within the limits of the workspace available for contouring, to give very smooth contours even on coarse meshes.

Note that if the contour interval is too fine, the contouring operation may fail, with a message such as:

If this occurs, it may be necessary to increase the minor contour interval and/or reduce the contour quality index, before proceeding with the display.

Quality 1 Single line segments are drawn between each mesh cellQuality 2 The cell is divided into 4 and a fast interpolation made from the coarse mesh

at the new locations.

CONTOUR DENSITY TOO HIGH AT INTERVAL:.100E+01MINIMUM FOR DATA IS:.400E+01...&


www.cadfamily.com

GRID Reference Manual Edit MapShow minimum & maximum P.2.5.6.6

199

Show minimum & maximum P.2.5.6.6

Sho min max

PurposeShow the minimum and maximum node values of the mesh.

DescriptionThe minimum and maximum valued nodes are highlighted on the map. The row/column number and value for each, is shown at the bottom of the screen.


www.cadfamily.com

200 Edit Map GRID Reference ManualShow nulls P.2.5.6.7

Show nulls P.2.5.6.7

Sho nulls

PurposeShow the null nodes in the mesh by highlighting them.

DescriptionThe locations of all the null nodes in the mesh are highlighted. Afterwards, the user can choose either to unhighlight the null nodes or to redraw the picture. Depending on the density of nulls, it may be quicker to redraw.


www.cadfamily.com

GRID Reference Manual Edit MapDefine Granite settings P.2.5.6.8

201


Def granite

PurposeDefine the pen and text representation to be used when drawing mesh contours on the current map.


The “Return” option returns the user to the “Chg msh pars” menu. Each of the other options leads to a further menu for setting Granite attributes, as described in Appendix C.

Note Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current default Granite attributes for the major or minor contour line, grid line or text. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.


Option Function

1 Return

2 Def maj pen

3 Def min pen

4 Def maj txt

5 Def min txt

6 Def grd pen

7 Def pst txt





Define pen for mesh grid

Define text for posting values


www.cadfamily.com

202 Edit Map GRID Reference ManualChange mesh map colour fill P.2.5.6.9

Change mesh map colour fill P.2.5.6.9

Chg fill

PurposeChange the colours used for colour filled contours.

Note that this option should only be selected after the colour fill is displayed on the screen. If colour fill is displayed after the colours are changed, any colours defined here will be overwritten.

DescriptionA number of different methods are available for changing the colours used. The following menu is displayed:

Option 7 is included only on the “Chg fill” menu for colour filled mesh maps.


Option Function

1 Return

2 Num styles

3 Chg index

4 Chg limits

5 Set shading

6 Res colours

7 Chg key

Number of styles

Change index

Change limits

Set shading

Reset colours

Change key


www.cadfamily.com

GRID Reference Manual Edit MapChange key P.2.5.6.9.7

203

Change key P.2.5.6.9.7

Chg key

PurposeChange the position and/or appearance of the colour fill key.


This menu allows the user to change the appearance of the colour fill key, to move and resize it, and to change the number of colour intervals appearing on the key.

Table 5.6 Menu P.2.5.6.9.7

Option Function

1 Return

2 Chg text

3 Move key

4 Resize key

5 Chg key inc

6 Chg num dec

Change text

Move key

Resize key

Change key increment


Option 2 Allows all attributes of the key text to be changed (height, colour etc.).Option 3 Allows the user to reposition the key but maintain the current key

dimensions.Option 4 Allows the key to be repositioned and rescaled.Option 5 Can be used when a large number of colours are being used on the map, which

can lead to too many colour intervals being displayed on a limited size key. The user is asked for a number of colours to omit between each colour being drawn. The key will then be redrawn missing out some colours, so aiding readability.

Option 6 Allows control over the number of decimal places to be used with the key values. The maximum number of decimal places allowed is 6. Entering ‘0’ will give integer values.


www.cadfamily.com

204 Edit Map GRID Reference ManualDefine mesh value P.2.5.7

Define mesh value P.2.5.7

Def msh val

PurposeDefine or check the value at a node on a mesh.

DescriptionThe user is prompted to select the node for which a new value is required. The selected node is highlighted and its row and column number is displayed at the bottom of the screen.

The user is prompted for a new value, default being the current value.


www.cadfamily.com

GRID Reference Manual Edit MapOutput mesh P.2.5.8

205

Output mesh P.2.5.8

Out mesh

PurposeOutput the mesh data from the current map to a data file.

DescriptionThe mesh may be output in the form of contours and/or gridded mesh data. If contour output is requested, the user is prompted for a file root and the contour data are written to a formatted file with the name ‘root.CNT’, using the default list-directed format, with marker value 1.0E30. These contours may be read back into another map, as if they had been digitized.

For mesh output, the full mesh grid or a sub-grid may be written. If a sub-grid is requested, its extent may be defined by:

• Row and column numbers

• XY limits

• Digitizing the corners of the required area

The nearest mesh nodes to the corners digitized or the XY limits given are used to define the sub-grid. The row/column and XY extent of the sub-grid are then echoed back to the user.

The output mesh may also be coarsened by means of a coarsening factor (default is 1, i.e. no coarsening). If the mesh is coarsened, the last row and/or column included in the output may be adjusted to obtain a regular mesh. The XY extent of the resulting mesh will be displayed if it does not cover the full map area.

The user is asked whether the output file is required in SAVE file format (binary), CPS-3 format (binary), XYZ or LCT format. If none of these is selected, ASCII format is assumed. The root name of the data file must be entered. Formatted output files will be given the name ‘root.GCT’ and binary files will be given the name ‘root.UGC’.

ASCII file formatIf the file is to be written in character format then it will have the following structure:

Data values are written with the row number increasing faster than the column number. The mesh can be written using list-directed output or using a user-supplied format. If a user-specified format is given, a check is made to ensure the format statement is enclosed within brackets. If it is not, brackets will be added.

Record 1 no. of rows (N) no. of columns (M)Record 2 to end-of-file

N x M items of gridded data


www.cadfamily.com

206 Edit Map GRID Reference ManualOutput mesh P.2.5.8

ASCII file example:

XYZ file formatFiles output in X,Y,Z format will have three columns of data, namely

• x-location

• y-location value

Data values are written with the row number increasing faster than the column number. Values can be written using list-directed output or using a user-supplied format. If a user-specified format is given, a check is made to ensure the format statement is enclosed within brackets. If it is not, brackets will be added.

SAVE file format (binary)

CPS-3 file format

This is a binary file format, with the following structure:

4 46900.00 7000.00 7100.00 7000.007000.00 7100.00 7000.00 6900.007100.00 7000.00 6900.00 6800.007000.00 6900.00 6800.00 6700.00

Record 1 4 integers as follows:Integer 1 dummyInteger 2 no. of rows (NROW)Integer 3 no. of columns (NCOLInteger 4 dummy

Record 2 NROW grid values for column 1..........Record NCOL+1 NROW grid values for column NCOL



Record 4 Length of next data record


www.cadfamily.com

GRID Reference Manual Edit MapOutput mesh P.2.5.8

207

Data values for columns 2 to NCOL are held in pairs of records, in the same format as records 6 and 7.

LCT file format

The option "Out msh maps" P.6.4.2 (see page 521) can be used to output mesh data from more than one stratum or map.

Record 5 NROW bias values (treated as dummies)Record 6 Length of next data recordRecord 7 Z values for first column, compressed to remove strings of nulls..

Record 1 Header recordLCT-GRID*ASCII *ASCII FORMATTED GRID FILE

Record 2 .... user-defined text ...Record 3 Xmin, Ymin, Xmax, Ymax, Ncol, Nrow in the format (4E14.7,2I5)Record 4 to end-of-file

Grid values in format (10X,5E14.7), with the column number increasing faster than the row number.


www.cadfamily.com

208 Edit Map GRID Reference ManualSample mesh P.2.5.9

Sample mesh P.2.5.9

Smp mesh

PurposeSample a mesh.


This “Smp mesh” menu allows a mesh map to be sampled so that the contouring parameters can be adjusted.

The “Return” option returns the user to the “Edt mesh” menu.


Option Function

1 Return

2 Tst point

3 Tst grid

4 Chg interp

5 Var transfrm

Test point (see page 135)

Test grid (see page 137)


Select variable transformation (see page 177)

Options 2 to 5 are the same as for digitized contour maps; see menu P.2.4.9, “Smp contours” (page 134 and following).

Option 3 is available only if a simulation grid has been loaded.


www.cadfamily.com

GRID Reference Manual Edit MapChange mesh interpolation P.2.5.9.4

209

Change mesh interpolation P.2.5.9.4

Chg interp

PurposeChange the interpolation parameters to be used when sampling the current mesh map.


The “Return” option returns the user to the “Smp mesh” menu. Options 2 to 6 and 8 are described in the contour map section P.2.4.9.7 (page 156 and following).


Option Function

1 Return

2 Def null

3 Def trn vals

4 Def dmp fac

5 Def sch rad

6 Def int mod

7 Tog nul bnd

8 Tog int flts

9 Sho sch crl

Define null value (see page 157)

Define truncation values (see page 158)

Define damping factor (see page 159)

Define search radius (see page 160)

Define interpolation mode (see page 163)

Toggle null mask boundary

Toggle faults in interpolation (see page 166)

Show search circle


www.cadfamily.com

210 Edit Map GRID Reference ManualToggle null mask boundary P.2.5.9.4.7

Toggle null mask boundary P.2.5.9.4.7

Tog nul bnd

PurposeToggle (on or off) the treatment of any null mask or null data region as a boundary for interpolation.

Description

Null boundaryBy default, the null mask boundary option is ON, i.e. the interpolation algorithm for mesh data will treat the edge of any significant null region as a boundary for interpolation purposes. (Isolated null values or groups of nulls with width less than the search radius are not treated as significant.) This means that non-null values cannot be sampled outside the region of valid data for the map, and any null masks applied to the data will be honoured exactly.

If the null mask boundary option is toggled OFF, values can be sampled within null regions provided that sufficient non-null data are present within the search radius. The general effect is to extend the non-null data area by distances up to the value of the search radius.

Interpolation at nodes with null neighborsBy default, to avoid instability problems, values will not be sampled for mesh nodes that do not have any non-null neighbors, except with interpolation mode 1 (weighted averaging). The user may wish to override this restriction. If the null mask boundary is toggled OFF, a second prompt will be issued:

Respond with Y to allow sampling at mesh nodes that do not have any non-null neighbors.

Caution Check the results carefully if this option is used. Interpolation modes 3 (reduced 2nd order surface) and 4 (2nd order surface) may give unstable results if sampling is permitted too far from valid control points.

Interpolate nodes with null neighbours (y/N)


www.cadfamily.com

GRID Reference Manual Edit MapShow search circle P.2.5.9.4.9

211

Show search circle P.2.5.9.4.9

Sho sch crl

PurposeShow the search circle used with the current interpolation parameters.

DescriptionThis option can be used to check the search circle used for sampling the current map/survey, with the current interpolation parameters.


www.cadfamily.com

212 Edit Map GRID Reference ManualShow search circle P.2.5.9.4.9


www.cadfamily.com

GRID Reference Manual Edit MapEdit features P.2.6

213

Edit features P.2.6

Edt features

PurposeEdit the features on the current map.


Features can be drawn in any colour and linestyle and would typically represent international boundaries, rivers, coastlines, lease-lines, fluid contacts, etc.

Features play no part in the interpolation process.

The “Return” option returns the user to the “Edt map” menu. Each of the other options are described in the following sections.

If the “Abandon” option is taken then any edits made during the current entry to the “Edt features” option will be discarded.


Option Function

1 Return

2 Cpy features

3 Add feature

4 Del features

5 Chg features

6 Inp features

7 Out features

8 Def granite

9 Chg granite

Copy features

Add feature

Delete features

Change feature

Input features

Output features




www.cadfamily.com

214 Edit Map GRID Reference ManualCopy features P.2.6.2

Copy features P.2.6.2

Cpy features

PurposeCopy the features from another map stratum to the current map stratum.

DescriptionThe user is prompted for the map name and the stratum number from which to copy the features.

The features and their granite settings will be copied from the given map onto the current map.

It is not possible to copy features if the current map already has one or more features defined on it.


www.cadfamily.com

GRID Reference Manual Edit MapAdd a feature P.2.6.3

215

Add a feature P.2.6.3

Add feature

PurposeDigitize a feature onto the current map.

DescriptionThe user is prompted for the name of the feature to be digitized. If no name is required enter RETURN.

Feature names are not displayed by default, but can be shown by selecting display option D.6.3.6.3, “Tog fet nmes” (see page 578).

The feature can be constructed using existing line data on the map, such as digitized faults, contours or zone boundaries, or may be defined as a digitized segment.

As the feature is digitized, it will appear on the screen as a white line. When digitizing is finished and the user returns to the “Edt features” menu, the feature will be re-drawn using the current granite settings, as defined in the “Def granite” option.

Linestyles for existing features can be changed using the “Chg granite” option.


www.cadfamily.com

216 Edit Map GRID Reference ManualDelete features P.2.6.4

Delete features P.2.6.4

Del features

PurposeDelete feature(s) from the current map.

DescriptionThe user is asked for the name of the feature to be deleted.

If an asterisk ‘*’ is entered then all the features on the map will be deleted upon confirmation by the user.

If the letter ‘Q’ is entered then each feature is highlighted in turn and the user can select to delete the feature or not. Sequencing through the features can be ended by entering the letter ‘E’.

If no name is entered then the user is asked to select the feature on the map to be deleted by digitizing a point close to the feature on the screen. The feature is highlighted and confirmation is requested to delete it.


www.cadfamily.com

GRID Reference Manual Edit MapChange features P.2.6.5

217

Change features P.2.6.5

Chg feature

PurposeChange feature names and lines on the current map.


The "Return" option returns the user to the "Edt feature" menu. Each of the other options are described in the relevant help sections.


Option Function

1 Return

2 Chg fet nam

3 Chg fet lne

4 Opr fet lnes

Change feature name

Change feature line

Operate on feature lines


www.cadfamily.com

218 Edit Map GRID Reference ManualChange feature name P.2.6.5.2

Change feature name P.2.6.5.2

Chg fet name

PurposeTo change the name of a digitized feature.

DescriptionThe user is asked to select a feature to be changed and then prompted for the feature name. Press the RETURN key to leave the current feature name unchanged.


www.cadfamily.com

GRID Reference Manual Edit MapChange a feature line P.2.6.5.3

219

Change a feature line P.2.6.5.3

Chg fet lne

PurposeRedigitize a section of a feature on the current map.

DescriptionThe user is asked to select the endpoints of the feature section to be changed. The endpoints of the selected section are highlighted and the section is erased from the display.

Confirmation is requested to proceed with the change. If the user confirms to proceed, the endpoints of the section are unhighlighted and part of the remaining feature is highlighted. Redigitizing should start from the highlighted part of the remaining feature.


www.cadfamily.com

220 Edit Map GRID Reference ManualOperate on feature lines P.2.6.5.4

Operate on feature lines P.2.6.5.4

Opr fet lnes

PurposeEditing operations to modify digitized feature lines on the current map.


The “Return” option returns the user to the “Chg features” menu. Each of the other options are described in the relevant help sections.


Option Function

1 Return

2 Clp fet lne

3 Spl fet lne

4 Thin fets

5 Repop fets

6 Smooth fets

7 Join fets

8 Extend fets

Clip feature line

Split feature line

Thin features

Repopulate features

Smooth features

Join features

Extend features


www.cadfamily.com

GRID Reference Manual Edit MapClip feature line P.2.6.5.4.2

221

Clip feature line P.2.6.5.4.2

Clp fet lne

PurposeClip the end of a digitized feature line on the current map.

DescriptionThis option allows the ends of feature lines to be clipped. The user is asked to select the point at which each feature line is to be clipped.

When the “Clp fet lne” option is selected, the user may clip as many or as few features as required. Clipping will cease on selection of another menu option.

The section of the feature from the nearest end point to the selected point (i.e. the section with the fewest data points) will be erased from the map.


www.cadfamily.com

222 Edit Map GRID Reference ManualSplit feature line P.2.6.5.4.3

Split feature line P.2.6.5.4.3

Spl fet lne

PurposeSplit a feature line on the current map into two features.

DescriptionThis option enables a digitized feature line to be split into two. The user is asked to select the point at which each feature is to be split.

When the “Spl fet lne” option is selected, the user may split as many or as few features as required. Splitting will cease on selection of another menu option.

The nearest feature to the point selected will be split by dividing the feature into two separate feature lines at the given point. If any of the feature lines is reduced to a single point, it will be discarded. It may be made easier if the digitized points on the feature line are displayed on the screen, which can be done with the display option D.6.3.6.4, “Tog fet pnts” (see page 578).

The feature name for the original feature will be used to construct names for the two new features in the form ‘oldnameA’ and ‘oldnameB’.


www.cadfamily.com

GRID Reference Manual Edit MapThin features P.2.6.5.4.4

223

Thin features P.2.6.5.4.4

Thin fets

PurposeThin digitized feature lines on the current map.

DescriptionThis option allows feature lines to be thinned by removing points according to the curvature of the feature line. At each point, the angle between adjacent line segments is checked before deciding to remove the point. Note that this will result in a higher density of points on curved sections of each feature, with fewer points on relatively straight sections. It may be necessary to use the option “Repop fets” (P.2.6.5.4.5, see page 224) in combination with this thinning operation, to obtain a good distribution of points along the entire feature.

The user can choose to thin all features or selected lines only. To finish line selection, pick another menu option.

At the end of the operation, the program reports how many features were thinned and the percentage of data points removed.


www.cadfamily.com

224 Edit Map GRID Reference ManualRepopulate features P.2.6.5.4.5

Repopulate features P.2.6.5.4.5

Repop fets

PurposeRepopulate digitized feature lines on the current map, by adding additional points.

DescriptionThis option allows feature lines to be repopulated with additional XY points. The user is prompted to choose one of the following methods:

1 Insertion

2 Replacement

Method 1 keeps all existing points on the feature, but inserts new points on each line segment if the line segment is longer than the required repopulation interval.

Method 2 replaces the current feature line with a new feature which has points spaced according to the repopulation interval, retaining only the first and last points.

The user is prompted to define the repopulation interval as a fractional value, which will be used as a multiplier on the average length of each line segment. For example, if the average distance between two points on a feature is 50 metres and the user enters an interval value of 0.4, the repopulation interval will be 20 metres.

The user can choose to repopulate all features or selected lines only. To finish line selection, pick another menu option.

At the end of the operation, the program reports how many features were repopulated and the increase in the number of data points.


www.cadfamily.com

GRID Reference Manual Edit MapSmooth features P.2.6.5.4.6

225

Smooth features P.2.6.5.4.6

Smooth fets

PurposeSmooth digitized feature lines on the current map, by reinterpolation.

DescriptionThis option allows feature lines to be smoothed by reinterpolating XY points. Smoothing is performed by replacing each point with a new XY point calculated as the mid-point of the line joining the mid-points of the adjacent line segments. The first and last points are unchanged. It may be necessary to increase the density of points along the features using “Repop fets” (P.2.6.5.4.5, see page 224) before smoothing the lines.

The user can choose to smooth all features or selected lines only. To finish line selection, pick another menu option.

At the end of the operation, the program reports how many features were smoothed.


www.cadfamily.com

226 Edit Map GRID Reference ManualJoin features P.2.6.5.4.7

Join features P.2.6.5.4.7

Join fets

PurposeJoin (or close) digitized feature lines on the current map.

DescriptionThis option connects separate feature lines together and/or closes individual features, according to the distance between the start and end points.

The user is prompted to enter the maximum extrapolation factor. This is used as a multiplier on the average length of the existing line segments, to calculate the limit on the length of a new line segment which can join two feature points. Note that if this limit is too large, unrealistic connections may result.

The user can choose to join all features or selected pairs of lines only. When selecting lines, a feature can be closed by picking the same line for the first and second feature. To finish line selection, pick another menu option.

At the end of the operation, the program reports the total number of features on the map before and after joining.


www.cadfamily.com

GRID Reference Manual Edit MapExtend features P.2.6.5.4.8

227

Extend features P.2.6.5.4.8

Extend fets

PurposeExtend digitized feature lines on the current map.

DescriptionThis option can be used to extend feature lines by linear extrapolation.

The user is prompted to enter the maximum extrapolation factor. This is used as a multiplier on the average length of the existing line segments, to calculate the limit on the length of a new line segment which can be used to extend a feature. Note that as the new line will be a straight extension of the last line segment, it is advisable to use a small extrapolation factor (e.g. 1.0 or less). If it is necessary to add a relatively long feature segment, use option P.2.6.5.3, “Chg fet lne” to edit the feature by hand (see page 219).

The user can choose to extend all features or selected lines only. When selecting lines, the user can also choose to extend both ends or only the end nearest the selection point. To finish line selection, pick another menu option.

At the end of the operation, the program reports the total number of features which were extended.


www.cadfamily.com

228 Edit Map GRID Reference ManualInput features P.2.6.6

Input features P.2.6.6

Inp features

PurposeInput feature lines from a data file onto the current map, clipping to the model area if required.

DescriptionFeatures may be read in addition to any that already exist on the current map.

The user is prompted for the name of the file containing the features and whether it is required to clip the data to the model area. The user can also choose to ‘thin’ the digitized input file.

Four standard types of input file structure are allowed:

STRUCTURE a: X1 Y1 X2 Y2Four REAL numbers are expected on each record, for example:

A new feature will be started whenever the X2,Y2 coordinate of one record differs from the X1,Y1 coordinate of the next record.




www.cadfamily.com

GRID Reference Manual Edit MapInput features P.2.6.6

229

STRUCTURE b: X Y IDTwo REAL numbers and an INTEGER id-number are expected on each record for example:

A new feature will be started whenever the feature-ID changes.

STRUCTURE c: X YTwo REAL numbers are expected on each record, and a marker card is used to separate different features. The user is prompted for a REAL value to represent the marker (e.g. 1.0E20), for example:

A new feature will be started whenever a marker card is encountered.

X-location Y-location Feature-ID253900.21800 335572.68700 1265840.65600 323167.68700 1278604.34300 309494.71800 1290488.53100 296790.87500 1298255.37500 285674.28100 1306982.78100 272687.03100 1636141.68700 227020.06200 2617731.75000 229109.53100 2595155.50000 232837.46800 2573246.87500 237401.62500 2553058.50000 240528.90600 2



www.cadfamily.com

230 Edit Map GRID Reference ManualInput features P.2.6.6

STRUCTURE d: X Y NAMETwo REAL numbers and a CHARACTER feature name are expected on each record, for example:

Note that if list directed input * is being used the feature name may be in single quotes.

A new feature will be started whenever the feature name changes.

For all the above types of file structure the X and Y locations should be in model coordinates (typically metres or feet). Feature lines that are in LATITUDE & LONGITUDE may be read using the UKOOA format or in DEGREES format for decimal degrees. These are described in Appendix K.

The first line of the data file will then appear at the bottom of the screen and the new menu will allow the user to skip through the file and view the data. The option “Next line” should be selected to skip any header records until the first X Y location (or marker card if structure b) is displayed. Data input will commence with the current record being displayed when the option “Return” is selected.


If the first character of the first record in the file is a * or (, then it is assumed to be a format statement e.g.. * or (2F12.3,I4), and it will be the default when the user is prompted for the input format. If the first record is not a format statement then the default input format will be list directed ‘*’.


Features are marked on the map as each feature is read into the program. Features will be displayed on the map using the current granite settings defined in the “Def granite” option.

If feature names are not given in the input file, features are automatically named according to the feature-ID (if given) or the order in which they are read. The feature name will take the form ‘FET-n’, where ‘n’ is an integer number.

Feature names are not displayed by default but can be shown by selecting display option D.6.3.6.3, “Tog fet nmes” (see page 578).

The symbol and text representations for individual features can be changed using the “Chg granite” option.

X-location Y-location Feature-name253900.21800 335572.68700 FeatureA265840.65600 323167.68700 FeatureA278604.34300 309494.71800 FeatureA290488.53100 296790.87500 FeatureA298255.37500 285674.28100 FeatureA306982.78100 272687.03100 FeatureA636141.68700 227020.06200 FeatureB617731.75000 229109.53100 FeatureB595155.50000 232837.46800 FeatureB573246.87500 237401.62500 FeatureB553058.50000 240528.90600 FeatureB


www.cadfamily.com

GRID Reference Manual Edit MapInput features P.2.6.6

231

ExampleA file called ECL.FTR contains two features to be input to the current map. The file ECL.FTR looks like:



"Edt features""Inp features"'Enter name of file to be read...' ( ECL.FTR is entered )'Clip input data to model area ? (y/N)' ( N is entered )'Thin digitized input data ? (y/N)' ( N is entered )'Layout: a) X1,Y1,X2,Y2 b) X,Y,ID c) X,Y or d) X,Y,NAME ? (a/B/c/d) '

( B is entered )"Next line" ( to skip format line )"Return" ( 1st feature

location shown )'Enter record format, e.g. (2E13.5,I4) or RETURN for (2F12.3,I2)'

( RETURN to read file )2 features read...&


www.cadfamily.com

232 Edit Map GRID Reference ManualOutput features P.2.6.7

Output features P.2.6.7

Out features

PurposeOutput features from the current map to a data file, clipping to the model area if required.

DescriptionThe user is prompted for the root name of the file to be opened for output. The output file will be given the name ‘root.FTR’.

The user is then prompted to choose whether to clip the data to the model area, and to select the output file structure.

Four different types of structure are available:

STRUCTURE a: X1 Y1 X2 Y2Four REAL numbers are written to each record, for example:




www.cadfamily.com

GRID Reference Manual Edit MapOutput features P.2.6.7

233

STRUCTURE b; X Y IDTwo REAL numbers and an INTEGER id-number are written on each record, for example:

STRUCTURE c: X YTwo REAL numbers are written on each record, and a marker card is used to separate different features. The user is prompted for a REAL value to represent the marker (e.g. 1.0E20), for example:

X-location Y-location Feature-ID253900.21800 335572.68700 1265840.65600 323167.68700 1278604.34300 309494.71800 1290488.53100 296790.87500 1298255.37500 285674.28100 1306982.78100 272687.03100 1636141.68700 227020.06200 2617731.75000 229109.53100 2595155.50000 232837.46800 2573246.87500 237401.62500 2553058.50000 240528.90600 2



www.cadfamily.com

234 Edit Map GRID Reference ManualOutput features P.2.6.7

STRUCTURE d: X Y NAMETwo REAL numbers and a CHARACTER feature name are written on each record, for example:

Note that if list directed input * is being used the feature name will be written in single quotes.

For all the above types of file structure the X and Y locations will be in model coordinates (typically metres or feet). Feature locations may be output in LATITUDE & LONGITUDE using the UKOOA format or in DEGREES format for decimal degrees. These are described in Appendix K.

List directed output ‘*’ is the default. However, the user may specify an output format, e.g. (2F12.5,I4).


The first record to be written to the output file is the format used, and subsequent records will contain the feature data in the specified format.

When output is complete, the user is informed of the number of features that were written to the file.

ExampleA map contains two features to be output to a file called ECL.FTR using the format (2F12.3,I2). No clipping is required.


X-location Y-location Feature-name253900.21800 335572.68700 FeatureA265840.65600 323167.68700 FeatureA278604.34300 309494.71800 FeatureA290488.53100 296790.87500 FeatureA298255.37500 285674.28100 FeatureA306982.78100 272687.03100 FeatureA636141.68700 227020.06200 FeatureB617731.75000 229109.53100 FeatureB595155.50000 232837.46800 FeatureB573246.87500 237401.62500 FeatureB553058.50000 240528.90600 FeatureB

"Edt features""Out features"'Enter output file root' ( ECL is entered )File ECL.FTR opened ...&'Clip output data to model area ? (y/N)' ( N is entered )'Layout: a) X1,Y1,X2,Y2 b) X,Y,ID c) X,Y or d) X,Y,NAME ? (a/B/c/d) '

( B is entered )'Enter record format, e.g. (2E13.5,I4) or RETURN for *'

( (2F12.3,I2) is entered )2 features output...&


www.cadfamily.com

GRID Reference Manual Edit MapOutput features P.2.6.7

235

The file ECL.FTR will look like:



www.cadfamily.com



Def granite

PurposeDefine the pen and text representation to be used when new features are added to the current map or input from a data file.


The “Return” option returns the user to the “Edt features” menu. Each of the other options leads to a further menu for setting Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current default Granite attributes for the feature line or text. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.


Option Function

1 Return

2 Def fet pen

3 Def fet txt

4 Def fet mrk

Define pen for feature lines

Define text for feature names

Define marker for feature points


www.cadfamily.com


237


Chg granite

PurposeChange the pen and text representation used to draw and label an existing feature on the current map.

DescriptionThe user is asked to select the feature on the map for which the granite settings are to be changed. The feature is highlighted and the following menu is displayed:

The “Return” option returns the user to the “Edt features” menu and redraws the selected feature using the new representations. Each of the other options leads to a further menu for setting Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current default Granite attributes for the selected feature line or text. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.


Option Function

1 Return

2 Chg fet pen

3 Chg fet txt

4 Chg fet mrk

Change pen for feature lines

Change text for feature names

Change marker for feature points


www.cadfamily.com

238 Edit Map GRID Reference ManualChange Granite settings P.2.6.9


www.cadfamily.com

GRID Reference Manual Edit MapEdit captions P.2.7

239

Edit captions P.2.7

Edt captions

PurposeEdit the captions on the current map.


Captions may be used to annotate the map.

Captions may be placed anywhere on the map and at any angle. They may be displayed in any number of different fonts, character height and colour.


If the “Abandon” option is taken then any edits made during the current entry to the “Edt captions” option will be discarded.


Option Function

1 Return

2 Cpy caption

3 Add caption

4 Del caption

5 Chg cap data

6 Inp caption

7 Out caption

Copy captions

Add caption

Delete caption

Change caption data

Input captions

Output captions


www.cadfamily.com

240 Edit Map GRID Reference ManualCopy captions P.2.7.2

Copy captions P.2.7.2

Cpy captions

PurposeCopy the captions from another map stratum onto the current map stratum.

DescriptionThe user is prompted for the map name and the stratum number from which to copy the captions. The captions and their Granite settings will be copied from the given map to the current map.

It is not possible to copy captions if the current map already has one or more captions defined on it.


www.cadfamily.com

GRID Reference Manual Edit MapAdd a caption P.2.7.3

241

Add a caption P.2.7.3

Add caption

PurposeAdd a caption to the current map.

DescriptionThe user is asked to select the start point of the caption, and a point in the required direction. The actual length of the direction line is not relevant. The length of the caption is determined by the character height and the number of characters in the caption.

The user is prompted for the caption to be written. Captions may be written in upper case, lower case or a mixture of both. Captions will be displayed on the map using the current granite settings defined in the “Def granite” option.

The text representation for individual captions can be changed using the “Chg granite” option.

The following special captions are available for general annotation purposes:

Note Special captions will be displayed using the current granite settings defined in the “Def granite” option - in the same way as for normal captions.

Table 5.2 Special captions

Caption Effect

@LOGO Substitute company logo (if available)

@TIME Substitute current time

@DATE Substitute current date

@USERID (@USID) Substitute current user-identifier

@ARROW Draw an arrow from start point to end point (arrow head is put at the end of the line with head size equal to the text height)

@OPENARROW Same as for @ARROW but will draw an ‘open arrow’ instead

@NORTH Draws a North sign in the shape of a North Star with a ‘N’ at the top of it. Its size and direction depend on the start and finish points input for the caption


www.cadfamily.com

242 Edit Map GRID Reference ManualDelete a caption P.2.7.4

Delete a caption P.2.7.4

Del caption

PurposeDelete a caption from the current map.

DescriptionThe user may choose to delete all captions, sequence through possible captions to delete (‘query delete’), or select one caption for deletion with the cursor.

If an asterisk ‘*’ is entered then all the captions on the map will be deleted upon confirmation by the user.

If the letter ‘Q’ is entered then each caption is highlighted in turn and the user can select to delete the caption or not. Sequencing through the captions can be ended by entering the letter ‘E’.

If no name is entered then the user is asked to select the caption on the map to be deleted by digitizing a point close to the caption on the screen. The caption is highlighted and confirmation is requested to delete it.


www.cadfamily.com

GRID Reference Manual Edit MapChange caption data P.2.7.5

243

Change caption data P.2.7.5

Chg cap data

PurposeChange the caption data on a map, by moving captions, changing the caption text or setting the granite attributes.


Options 2, 3 and 5 can be used to change existing captions on the map. Option 4 is used to define the default granite settings to be used when adding a new caption.


Option Function

1 Return

2 Mov caption

3 Chg caption

4 Def granite

5 Chg granite

Move a caption

Change caption text




www.cadfamily.com

244 Edit Map GRID Reference ManualMove a caption P.2.7.5.2

Move a caption P.2.7.5.2

Mov caption

PurposeMove a caption from one location to another on the current map.

DescriptionThe user is asked to select the caption to be moved by digitizing a point close to the caption on the screen. The caption is highlighted by a box and the user is prompted for a new start point and direction for the caption.


www.cadfamily.com

GRID Reference Manual Edit MapChange a caption P.2.7.5.3

245

Change a caption P.2.7.5.3

Chg caption

PurposeChange the text of an existing caption on the current map.

DescriptionThe user is asked to select the caption to be changed by digitizing a point close to the caption on the screen. The caption is highlighted by a box and the user is prompted for the new text. (Special captions may be defined, e.g. @LOGO, @NORTH, as when adding a new caption.)


www.cadfamily.com

246 Edit Map GRID Reference ManualDefine Granite settings P.2.7.5.4


Def granite

PurposeDefine the text representation to be used when drawing new captions that are added to the current map.


Text representations are described in Appendix C.

Note that if the “Sho examples” option is selected, the current map display will be replaced by a summary of the current default Granite attributes for new captions. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.


Option Function

1 Return

2 Chg font

3 Chg prec

4 Chg exp fac

5 Chg spacing

6 Chg colour

7 Chg height

8 Sho examples

Change text font

Change text precision

Change text expansion factor

Change text spacing

Change colour

Change text height

Show examples


www.cadfamily.com

GRID Reference Manual Edit MapChange Granite settings P.2.7.5.5

247

Change Granite settings P.2.7.5.5

Chg granite

PurposeChange the text representation used to draw an existing caption on the current map.

DescriptionThe user is asked to select the caption on the map for which the granite settings are to be changed. The caption is highlighted by a box and the following menu is displayed:

The “Return” option returns the user to the “Chg cap data” menu and redraws the selected caption using the new representations. Text representations are described in Appendix C.

Note that if the “Sho examples” option is selected, the current map display will be replaced by a summary of the current default Granite attributes for the caption. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.


Option Function

1 Return

2 Chg font

3 Chg prec

4 Chg exp fac

5 Chg spacing

6 Chg colour

7 Chg height

8 Sho examples

Change text font



Change text spacing

Change colour

Change text height

Show examples


www.cadfamily.com

248 Edit Map GRID Reference ManualInput captions P.2.7.6

Input captions P.2.7.6

Inp captions

PurposeInput captions from a data file onto the current map.

DescriptionThe user is prompted for the name of the file containing the captions.

The first line of the data file will then appear at the bottom of the screen and the new menu will allow the user to skip through the file and view the data. The option “Next line” can be used to view the caption records. Data input will commence with the current record being displayed when the option “Return” is selected.

The first line of the file is a header record, indicating the format which should be used to read the data. (List-directed input, '*', is used for captions.)

Each line of the data file will represent one caption and should look like:

where

Note that values on each record are not separated by commas, but by blank spaces.

ExampleA file called ECL.CAP contains 4 captions to be input to the current map. The file looks like:

’Text’ X1 Y1 X2 Y2 IFONT IPREC EXP SPA ICOL HT

’Text’ is the caption text (in single quotes)X1 Y1 is the caption start point in map coordinatesX2 Y2 is the caption direction end point in map coordinatesIFONT is the Granite text font number (INTEGER)IPREC is the Granite text precision number (INTEGER)EXP is the Granite text expansion factor (REAL)SPA is the Granite text spacing factor (REAL)ICOL is the Granite text colour number (INTEGER)HT is the text height in cm (REAL)

RECORD 1: *RECORD 2:’The 1st caption’ 49262. 25511. 59717. 10710. 1 3 1.0 0.0 1 0.4RECORD 3:’Another caption’ 45135. 3137.5 52839. 5134.0 1 3 1.0 0.0 3 0.4RECORD 4:’Third caption’ 45891. 9333.0 45941. 9333.0 5 3 1.0 0.0 7 0.4RECORD 5:’@NORTH’ 64051. 20348. 64051. 25718. 2 3 1.0 0.0 7 0.4


www.cadfamily.com

GRID Reference Manual Edit MapInput captions P.2.7.6

249


"Edt captions""Inp caption"‘Enter name of file to be read...’(ECL.CAP is entered)"Nxt line"(to view contents)"Nxt line""Nxt line""Nxt line""1st line"(to go back to the top)"Return"(RETURN to read file)4 captions read...&


www.cadfamily.com

250 Edit Map GRID Reference ManualOutput captions P.2.7.7

Output captions P.2.7.7

Out captions

PurposeOutput captions from the current map to a data file.

DescriptionThe user is prompted for the root name of the file to be opened for output. The output file will be given the name ‘root.CAP’.

All captions on the current map are written to an ASCII formatted file using list-directed output ‘*’.

The first record written to the file is a header record, indicating the format used to read the data. (List-directed input, '*', is used for captions.)

Each line of the data file will represent one caption and contain the following data:

where

’Text’ X1 Y1 X2 Y2 IFONT IPREC EXP SPA ICOL HT

’Text’ is the caption text (in single quotes)X1 Y1 is the caption start point in map coordinatesX2 Y2 is the caption direction end point in map coordinatesIFONT is the Granite text font number (INTEGER)IPREC is the Granite text precision number (INTEGER)EXP is the Granite text expansion factor (REAL)SPA is the Granite text spacing factor (REAL)ICOL is the Granite text colour number (INTEGER)HT is the text height in cm (REAL)


www.cadfamily.com

GRID Reference Manual Edit MapEdit zones P.2.8

251

Edit zones P.2.8

Edt zones

PurposeEdit the zones on the current map.


Zones may be used to delimit areas on the map such as lease blocks, for display purposes and also for volumetric analysis (ECLMap options). They may be displayed in any hatch style or colour.

Zone boundaries may be digitized from other existing lines on the map such as fault traces, feature lines, contour lines, or even other zone boundaries, thus allowing zones to abut each other exactly.


If the “Abandon” option is taken then any edits made during the current entry to the “Edt zones” option will be discarded.


Option Function

1 Return

2 Cpy zones

3 Add zone

4 Del zone

5 Chg zone

6 Inp zones

7 Out zones

8 Def granite

9 Chg granite

Copy zones

Add zone

Delete zone

Change zone

Input zones

Output zones

Define granite

Change granite


www.cadfamily.com

252 Edit Map GRID Reference ManualCopy zones P.2.8.2

Copy zones P.2.8.2

Cpy zones

PurposeCopy the zones from another map stratum onto the current map stratum.

DescriptionThe user is prompted for the map name and the stratum number from which to copy the zones.

The zones and their granite settings will be copied from the given map onto the current map.

It is not possible to copy zones if the current map already has one or more zones defined on it.


www.cadfamily.com

GRID Reference Manual Edit MapAdd a zone P.2.8.3

253

Add a zone P.2.8.3

Add zone

PurposeDigitize a zone onto the current map.

DescriptionThe user is prompted for the name of the zone to be digitized. If no name is required enter RETURN.

Zone names are not displayed by default, but can be shown by selecting display option D.6.3.8.3 “Tog zon lbls” (see page 580).

The zone can be constructed using existing line data on the map, such as digitized faults, features, contours or zone boundaries, or it may be defined as a digitized segment.

As the zone is digitized, it will appear on the screen as a white line. When digitizing is finished and the user returns to the “Edt zone” menu, the zone will be re-drawn using the current Granite settings defined in the “Def granite” option.

Linestyles for existing zones can be changed using the “Chg granite” option.


www.cadfamily.com

254 Edit Map GRID Reference ManualDelete zones P.2.8.4

Delete zones P.2.8.4

Del zones

PurposeDelete zone(s) from the current map.

DescriptionThe user is asked for the name of the zone to be deleted.

If an asterisk ‘*’ is entered then all the zones on the map will be deleted on confirmation by the user.

If the letter ‘Q’ is entered then each zone is highlighted in turn and the user can select to delete the zone or not. Sequencing through the zones can be ended by entering the letter ‘E’.

If no name is entered then the user is asked to select the zone to be deleted by digitizing a point close to the zone boundary on the screen. The zone will be highlighted and confirmation is requested to delete it.

Note A zone for which the given point is inside will be selected in preference to a zone for which the given point is outside.


www.cadfamily.com

GRID Reference Manual Edit MapChange a zone P.2.8.5

255

Change a zone P.2.8.5

Chg zone

PurposeRedigitize a section of a zone boundary on the current map.

DescriptionThe user is asked to select the endpoints of the zone boundary to be changed. The section to be changed will be selected according to the shortest distance around the zone boundary. The endpoints of the selected section are highlighted and the section is erased from the display.

Confirmation is requested to proceed with the change. If the change is continued, part of the remaining zone boundary is highlighted, together with the start point from which redigitizing should start.

Note A zone for which a given point is inside will be selected in preference to a zone for which a given point is outside.


www.cadfamily.com

256 Edit Map GRID Reference ManualInput zones P.2.8.6

Input zones P.2.8.6

Inp zones

PurposeInput zone boundaries from a data file onto the current map, clipping to the model area if required.

DescriptionZones may be read in addition to any that already exist on the map.

The user is prompted for the name of the file containing the zones and whether it is required to clip the data to the model area.

Three types of input file structure are allowed:

• X1, Y1, X2, Y2

• X, Y, ZONE or

• X, Y

Structure a: X1 Y1 X2 Y2Four real numbers are expected on each record, for example:

A new zone will be started whenever the X2,Y2 coordinate of one record differs from the X1,Y1 coordinate of the next record.

Structure b: X Y ZONETwo real numbers and a character name are expected on each record.



www.cadfamily.com

GRID Reference Manual Edit MapInput zones P.2.8.6

257

Only if list directed input * is being used should the zone name be in single quotes, for example:

A new zone will be started whenever the zone name changes.

Structure c: X YTwo real numbers are expected on each record, and a marker card is used to separate different zones. The user is prompted for a real value to represent the marker (e.g. 1.0E20), for example:

A new zone will be started whenever a marker card is encountered.

For all the above types of file structure the X and Y locations should be in model coordinates (typically metres or feet). Zone limits that are in latitude & longitude may be read using the UKOOA format, described in Appendix K.

The first line of the data file will then appear at the bottom of the screen and the new menu will allow the user to skip through the file and view the data. The option “Next line” should be selected to skip any header records until the first X Y location (or marker card if structure b) is displayed. Data input will commence with the current record being displayed when the option “Return” is selected.


If the first character of the first record in the file is a * or (, then it is assumed to be a format statement, e.g. (2F12.3,A8), and it will be the default when the user is prompted for the input format. If the first record is not a format statement then the default input format will be list directed ‘*’.

X-location Y-location Zone-name253900.21800 335572.68700 ‘Zone-1’265840.65600 323167.68700 ‘Zone-1’278604.34300 309494.71800 ‘Zone-1’290488.53100 296790.87500 ‘Zone-1’298255.37500 285674.28100 ‘Zone-1’306982.78100 272687.03100 ‘Zone-1’636141.68700 227020.06200 ‘Zone-2’617731.75000 229109.53100 ‘Zone-2’595155.50000 232837.46800 ‘Zone-2’573246.87500 237401.62500 ‘Zone-2’553058.50000 240528.90600 ‘Zone-2’



www.cadfamily.com

258 Edit Map GRID Reference ManualInput zones P.2.8.6

If a user specified format is given, a check is made to ensure the format statement is enclosed within brackets, if it is not, brackets will be added.

Zones are marked on the map as each zone is read into the program. Zones will be displayed on the map using the current granite settings defined in the “Def granite” option.

Zones that are input to a map are named automatically according to the order in which they are read. The zone name will take the form ‘ZON-n’, where ‘n’ is an integer number.

Zone names are not displayed by default but can be shown by selecting display option D.6.3.8.3 “Tog zon lbls” (see page 580).

The symbol and text representations for individual zones can be changed using the “Chg granite” option.

ExampleA file called ECL.ZON contains two zones to be input to the current map. The file ECL.ZON looks like:


RECORD 1:(2F12.3,A8)RECORD 2: 273926.406 320046.062 ZONE-1RECORD 3: 278242.468 327856.593 ZONE-1RECORD 4: 282516.062 336018.000 ZONE-1RECORD 5: 296861.000 349817.812 ZONE-2RECORD 6: 310834.437 357874.281 ZONE-2RECORD 7: 326619.687 361741.531 ZONE-2

‘Edt zones’‘Inp zones’‘Enter name of file to be read...’ (ECL.ZON is entered)‘Clip input data to model area ? (y/N)’ (N is entered )‘Are zones stored as a) X1,Y1,X2,Y2 b) X,Y,ZONE or c) X Y ? (a/B/c)’

(B is entered)‘Next line’ (to skip format line)‘Return’ (1st zone location shown)‘Enter record format, e.g. (2E13.5,A8) or RETURN for (2F12.3,A8)’

(RETURN to read file)2 zones read...&


www.cadfamily.com

GRID Reference Manual Edit MapOutput zones P.2.8.7

259

Output zones P.2.8.7

Out zones

PurposeOutput zone boundaries from the current map to a data file, clipping to the model area if required.

DescriptionThe user is prompted for the root name of the file to be opened for output. The output file will be given the name ‘root.ZON’.

The user is then asked if it is required to clip the data to the model area.

The user is prompted for the file structure. Three different types of structure are available:

• X1, Y1, X2, Y2

• X, Y, ZONE or

• X, Y

Structure a: X1 Y1 X2 Y2Four real numbers are written to each record, for example:

Structure b: X Y ZONETwo real numbers and a character name are written on each record.



www.cadfamily.com

260 Edit Map GRID Reference ManualOutput zones P.2.8.7

If list directed output * is being used the zone name will be in single quotes, for example:

Structure c: X Y

Two real numbers are written on each record, and a marker card is used to separate different zones. The user is prompted for a real value to represent the marker (e.g. 1.0E20), for example:

For all the above types of file structure the X and Y locations will be in model coordinates (typically metres or feet). Zone boundaries may be output in latitude & longitude using the UKOOA format, described in Appendix K.

List directed output ‘*’ is the default. However, the user may specify an output format, e.g. (2F12.5,A8). If a user specified format is given, a check is made to ensure the format statement is enclosed within brackets. If it is not, brackets will be added. The first record to be written to the output file is the format used.

Subsequent records will contain the zone data in the specified format.

When output is complete, the user is informed of the number of zones that were written to the file.

ExampleA map contains two zones to be output to a file called ECL.ZON using the format (2F12.3,A8), no clipping is required.

X-location Y-location Zone-name253900.21800 335572.68700 ‘Zone-1’265840.65600 323167.68700 ‘Zone-1’278604.34300 309494.71800 ‘Zone-1’290488.53100 296790.87500 ‘Zone-1’298255.37500 285674.28100 ‘Zone-1’306982.78100 272687.03100 ‘Zone-2’636141.68700 227020.06200 ‘Zone-2’617731.75000 229109.53100 ‘Zone-2’595155.50000 232837.46800 ‘Zone-2’573246.87500 237401.62500 ‘Zone-2’553058.50000 240528.90600 ‘Zone-2’



www.cadfamily.com

GRID Reference Manual Edit MapOutput zones P.2.8.7

261


The file ECL.ZON will look like:

‘Edt zones’‘Out zones’‘Enter output file root’(ECL is entered)File ECL.ZON opened ...&‘Clip output data to model area ? (y/N)’(N is entered)‘Output zones as a) X1,Y1,X2,Y2 or b) X,Y,ZONE or c) X Y ? (a/B/c)’

(B is entered)‘Enter record format, e.g. (2E13.5,A8) or RETURN for *’

((2F12.3,A8) is entered)2 zones output...&

RECORD 1:(2F12.3,A8)RECORD 2: 273926.406 320046.063 Zone-1RECORD 3: 278242.468 327856.593 Zone-1RECORD 4: 282516.062 336018.000 Zone-1RECORD 5: 296861.000 349817.812 Zone-2RECORD 6: 310834.437 357874.281 Zone-2RECORD 7: 326619.687 361741.531 Zone-2


www.cadfamily.com



Def granite

PurposeDefine the fill area, pen and text representations to be used when new zones are added to the current map or input from a data file.


The “Return” option returns the user to the “Edt zones” menu. Each of the other options leads to a further menu for setting Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current default Granite attributes for the zone line text or fill. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.


Option Function

1 Return

2 Def pen

3 Def text

4 Def fill

Define pen for zone boundary

Define text for zone name

Define fill area colour and style


www.cadfamily.com


263


Chg granite

PurposeChange the fill area, pen and text representations to draw and label an existing zone on the current map.

DescriptionThe user is asked to select the zone on the map for which the granite settings are to be changed. The zone is highlighted and the following menu is displayed:

The “Return” option returns the user to the “Edt zones” menu and redraws the selected zone using the new granite representations. Each of the other options leads to a further menu for setting Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current default Granite attributes for the selected zone line, text or fill. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.


Option Function

1 Return

2 Chg pen

3 Chg text

4 Chg fill

Change pen for zone boundary

Change text for zone name

Change fill area colour and style


www.cadfamily.com

264 Edit Map GRID Reference ManualEdit legend P.2.9

Edit legend P.2.9

Edt legend

PurposeEdit the legend for the current map.


A legend may be defined for each map. The legend is not displayed on the screen unless the “Edt legend” option is selected. The legend will be drawn when the map is output as a scaled plot, but will not be drawn on unscaled plots. The user can switch off the legend in scaled plots by using option D.6.9 "Chg plot" (see page 595).

The legend consists of an array of boxes, each of which may contain data such as a well symbol, a fill area box, or line segment, followed by user defined annotation to describe the symbol. The arrangement of the legend is in rows and columns as defined by the user. While editing the legend box, the display is explicitly divided into boxes. These boxes will not appear on the plotted output and are only for user reference. The size of the legend box is determined by the character height of the text and by the number of rows and columns. The size of the legend on the screen is the same as the finished plot.

The “Return” option returns the user to the “Edt map” menu options. Each of the other options is described in the following sections.

If the “Abandon” option is taken then any edits made during the current entry to the “Edt legend” option will be discarded.


Option Function

1 Return

2 Cpy legend

3 Add item

4 Del item

5 Mov item

6 Chg item

7 Chg legend

8 Def granite

Copy legend

Add item to legend

Delete item

Move item

Change item

Change legend



www.cadfamily.com

GRID Reference Manual Edit MapCopy legend P.2.9.2

265

Copy legend P.2.9.2

Cpy legend

PurposeCopy the legend from another map stratum to the current map stratum.

DescriptionThe user is prompted for the map name and the stratum number from which to copy the legend. The legend and its granite settings will be copied from the given map onto the current map.

It is not possible to copy the legend from another map stratum if a legend is already defined on the current map.


www.cadfamily.com

266 Edit Map GRID Reference ManualAdd a legend item P.2.9.3

Add a legend item P.2.9.3

Add item

PurposeAdd an item to the legend of the current map.

DescriptionIf no legend has been defined then the user is asked how many rows and columns are required in the legend box. A maximum of 10 rows and 10 columns is allowed.

The position of the new data must be specified as a row, column pair and the user is asked to select the type of data to be entered from the following menu:

The “Return” option returns the user to the “Edt map” menu.

Options 2-4 are selected if point, line or area data is to be added to the legend. The user is prompted for the relevant Granite settings:


Option

1 Return

2 Add well

3 Add line

4 Add area

5 Add text

Add well number

Add line style

Add area fill style

Add text

Well Well number, colour numberLine Line style, colour numberArea Fill style, hatch style (if relevant), colour number and the text to describe the

symbol entry.Text is selected if it is required to enter text only.


www.cadfamily.com

GRID Reference Manual Edit MapDelete a legend item P.2.9.4

267

Delete a legend item P.2.9.4

Del item

PurposeDelete a legend item.

DescriptionThe user is prompted to define the row and column number of the legend entry to be deleted. Confirmation is requested to delete the entry.

The entire legend can be deleted by responding with ‘*’ instead of a row, column pair.


www.cadfamily.com

268 Edit Map GRID Reference ManualMove an item P.2.9.5

Move an item P.2.9.5

Move item

PurposeMove a legend entry from one row/col. location to a new location.

DescriptionThe user is asked to select the entry to be moved by defining its row and column location. The user is then prompted for the new row and column location.


www.cadfamily.com

GRID Reference Manual Edit MapChange an item P.2.9.6

269

Change an item P.2.9.6

Chg item

PurposeChange a legend entry.

DescriptionThe user is asked to select the entry to be changed by defining its row and column location. The entry can then be replaced in the same way as adding an item.


www.cadfamily.com

270 Edit Map GRID Reference ManualChange legend P.2.9.7

Change legend P.2.9.7

Chg legend

PurposeChange the number of legend rows and columns.

DescriptionThe number of rows and columns in the legend box can be changed.

The items are stored sequentially with row number increasing faster than column number, so that changing the number of rows and columns alters the relative positions of items as they appear in the box.

Although it is possible to reduce the total number of items, some data may be lost by doing so and the user will be asked to confirm that the number of items is to be reduced.


www.cadfamily.com

GRID Reference Manual Edit MapDefine Granite settings P.2.9.8

271


Def granite

PurposeDefine the text representation to be used when drawing the legend.

DescriptionThe character height will determine the overall size of the legend box. When a scaled plot is drawn, the title boxes, projection box and scale bar text will be drawn using the text representation defined for the legend, if a legend is present.


Text representations are described in Appendix C.

Note that if the “Sho examples” option is selected, the current map display will be replaced by a summary of the current default Granite attributes for legend text. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.


Option Function

1 Return

2 Chg font

3 Chg prec

4 Chg exp fac

5 Chg spacing

6 Chg colour

7 Chg height

8 Sho examples

Change text font



Change text spacing

Change colour

Change text height

Show examples


www.cadfamily.com



www.cadfamily.com

GRID Reference Manual Edit GridIntroduction

273

Chapter 6Edit Grid

Introduction

Simulation grid dataThe data for defining a simulation grid are held together in a .FNODE (or .NODE) file, which can contain some (or all) of the following:

• Data defining the grid coordinate system

• Grid geometry, defined by xyz coordinate data

• Local grid refinement and coarsening data

• Active/inactive cell indicators

• Region identifiers

• Grid block properties

Options for creating and editing these data types are accessed via the “Edt grid” menu tree. Facilities are included for constructing the grid geometry, defining vertical depths and thicknesses using map data, sampling properties from maps and writing out the grid data for input to a simulator.

Note The map data and simulation grid data for a model are stored independently. For example, if a TOPS map is modified after creating a simulation grid, the grid will not be changed until the depths are resampled via the “Edt grid” options.


www.cadfamily.com

274 Edit Grid GRID Reference ManualIntroduction

Terminology

Grid originIt is usual for a simulation grid to be defined with its origin located near the top left-hand corner, with the X-axis increasing from right to left, the Y-axis increasing down the screen and the Z-axis representing depths which increase from the top of the grid. This grid coordinate system is completely different to the map coordinate system which is based on the model area. When a new grid is created, the user will be prompted to specify the grid origin and the orientation of the grid axes, relative to the map coordinates. The XYZ position of a grid node can then be defined relative to the grid origin. A grid cell is identified by its IJK position relative to the grid origin.

Grid planesWhile a grid is being edited, it may be viewed as an XY layer, an XZ cross-section or a YZ cross-section. The surface to be viewed is specified by the cell layer, row or column number and the face required. In general, the plane number and face can be specified together, e.g. the top of layer 5 can be selected by typing ‘5T’.

• A LAYER (XY-plane) is defined by a fixed K-number and T for TOP or B for BOTTOM.

• A ROW (XZ-plane) is defined by a fixed J-number and B for BACK or F for FRONT.

• A COLUMN (YZ-plane) is defined by a fixed I-number and L for LEFT or R for RIGHT.

Selecting nodesA node is the point at the intersection of a row and a column. Each coordinate line of the grid is a straight line joining all nodes with the same IJ value: these lines may be vertical or sloping. The depth values at each corner of a node may be different, provided that each corner lies on the correct coordinate line. A node with different depth values is created by vertical splitting (to define fault throws), or horizontal splitting (to define gaps between layers).

A simulation grid can be manipulated by moving individual or groups of nodes from one location to another on the screen. Nodes are selected by placing the graphical cursor close to the node. In many instances it is also important to know which corner of a node has been selected, e.g. when defining split nodes. GRID chooses a node by selecting the nearest corner of the grid block in which the cursor lies.

Specifying depthsA number of grid editing options allow the user to specify depths, thicknesses or fault throws. These can be set in a number of ways:

• A constant, e.g. 1000.

The depth (or throw, or thickness) is set to the given value.

• The letter S.


www.cadfamily.com

GRID Reference Manual Edit GridIntroduction

275

The user is prompted for the name of the map to be sampled. If the map differs from the current map the screen will be redrawn to show the new contours. The depths at individual nodes are then obtained from sampling the map at the node point.

• The letter C.

This can be used to copy depths from another simulation grid layer with the same IJ dimensions. The program will prompt for the grid name, layer number and surface (Top or Bottom).

Numbers or ‘S’ may optionally be preceded by an operator. Valid operators are as follows:

where

If any null values are returned when sampling a map, the user is asked to enter a value for all the nodes at which null values have been returned. For most options, the user can then choose whether to continue with the operation. (For some options the operation is immediately discontinued if null values are returned.) Null values can be found and eliminated by first sampling the map from the “Tst grid” menus and adjusting the map interpolation parameters, such as the search radius. Any null values which cannot be eliminated in this way should be set to an appropriate value for the operation to be performed (e.g. for depths, use a reference depth which is close to the range of actual depths sampled).

After a layer depth or thickness is modified, the user will be prompted to choose whether to change all layers below and/or above the layer being edited by a corresponding amount.

Advanced griddingGRID provides facilities for building complex, irregular Cartesian models with sloping coordinate lines. These can be defined to represent sloping faults and other geological features, and may be adjusted “by hand” using the grid editing facilities. Option P.3.0.4, “Irregular”, provides the basic construction method for irregular control lines (see page 280), and option P. 3.0.8, “Merge grids”, can be used to build a sloping model (see page 296).

Although accurate and useful models can be built using these facilities, success depends on the user’s skill and experience, and laborious editing may be required. For more automatic gridding facilities, use FloGrid for building structured or unstructured grids. Refer to the "FloGrid User Guide" for information, or contact your local SIS support representative.

Table 6.1 Valid operators for use when specifying depths

Operator Action

= (arg)

+ (arg)

- (arg)

/ (arg)

* (arg)

> (arg)

< (arg)

**(arg)

set current value to (arg)

add (arg) to current value

subtract (arg) from current value

divide current value by (arg)

multiply current value by (arg)

(arg) is a lower bound to current value

(arg) is an upper bound to current value

raise current value to power (arg)

(arg) is a constant or the letter S.


www.cadfamily.com

276 Edit Grid GRID Reference ManualEdit grid P.3

Edit grid P.3

Edt grid

PurposeCreate a new simulation grid or modify an existing grid.

DescriptionThe “Edt grid” menu is as follows:

The user is prompted for the name of the simulation grid to be edited. The names of simulation grids currently associated with the model may be listed by typing ‘H’ in response to the prompt.

If an unrecognized grid name is given the user is asked whether a new grid is to be created. If it is, the user is prompted for the map to be displayed on the screen while the grid is being created, and the following menu is presented:

Table 6.2 Menu P.3

Option Function

1 Return

2 Edt layer

3 Edt area

4 Edt lines

5 Edt nodes

6 Edt flt lnes

7 Sho values

8 Edt blocks

9 Grd utils

Edit layer

Edit area

Edit lines

Edit nodes

Edit fault lines

Show values

Edit blocks

Grid utilities

Table 6.3 Menu for creating new grid

Option Function

1 Return

2 Vector grid

3 N x M grid

4 Irregular

5 Mark axes

6 Input grid

7 Copy grid

8 Merge grids

9 X-sect grid

Create vector grid

Create N x M grid

Create irregular grid

Create grid by marking axes

Input grid

Copy grid

Merge grids

Create cross-section grid


www.cadfamily.com

GRID Reference Manual Edit GridEdit grid P.3

277

If any of options 2 to 6 are selected, the grid coordinate system must be defined relative to the map system. The grid coordinate system is usually different to the map coordinate system, except that the scale for both systems is the same. It is usual for the grid origin to be located near the top left hand corner of the map, with Y increasing down the map, although it is also possible to define grid axes oriented in the same way as the map axes.

When creating a new simulation grid, its coordinate system is defined by entering the origin, the direction for the X-axis and the relative orientation of the Y-axis. The origin and X-direction can be defined by entering map coordinates or by digitizing the locations.

An additional option is provided, to use ‘grid default’ axes. These will be set at the top left-hand corner of the model area. This option is not recommended when constructing a new grid interactively, but is useful when loading a grid from a file via “Input grid” (P.3.0.6, see page 292), when the default axes may be overwritten, if axes data are found in the grid file.

For further information on the different methods for creating grids, refer to the sections describing options 2 to 9.

After a grid has been created, or if the grid already exists, the user will be prompted for a map to be displayed on the screen. The map can be specified with a fixed stratum, e.g. TOPS(1), or a variable stratum, e.g. TOPS(*). If the wild card * is entered for the stratum, the current map will be set according to the grid XY-plane on display. For example, if layer 3T is shown, the map will be TOPS(3). The variable stratum option will remain active while a grid is loaded, until the user selects another map stratum which does not correspond to the XY-plane, or until “Edt map” (P.2, see page 57), or “ECLMAP opts” (P.6.2, see page 478) is entered, when the map stratum must be frozen.

The program then checks whether the grid contains sloping coordinate lines. If it does, and the sloping coordinate lines option has not been enabled, the user can choose whether to switch the option on before starting to edit the grid. No prompt will be issued if the option is already on. (See “Tog slp crds”, P.7.5., page 536.)

The “Edt grid” menu is then displayed. When the “Return” option is selected from the “Edt grid” menu, the user is asked whether to save the current grid and is returned to the highest level menu. If the grid is saved, the existing .FNODE (or .FND) file will be overwritten. If the grid is not saved, it remains the current grid and may be saved on a subsequent occasion. If the old version of the grid is required in this GRID session, the grid must be cleared from the session and the grid reloaded.


www.cadfamily.com

278 Edit Grid GRID Reference ManualVector grid P.3.0.2

Vector grid P.3.0.2

Vector grid

PurposeCreate a new regular grid using the vectors method.

DescriptionThe user is prompted for a series of DX values, terminated by a carriage return, followed by a series of DY values, terminated by a carriage return. The grid is displayed as it is entered, X and Y axes starting from the given origin.

Multiple entries of the same value can be shortened to the form N*val, e.g. if 25 cells were required all of length 35 feet, the response would be 25*35.0.

At least one DX entry and one DY entry must be given.


www.cadfamily.com

GRID Reference Manual Edit GridN x M grid P.3.0.3

279

N x M grid P.3.0.3

N x M grid

PurposeCreate a new regular grid using the N x M method.

DescriptionThe user is asked to enter two opposite corners of a box which will form the boundary of the grid. The box is constructed parallel to the given grid coordinate system. Any corner of the box can then be adjusted until the “Box ready” option is selected.

At all stages locations may be entered at the keyboard in map coordinates, or selected using the cursor.

The user will be asked for the number of columns of grid blocks and the number of rows of grid blocks. A grid is constructed within the box, with equally spaced grid blocks in the x and y directions.


www.cadfamily.com

280 Edit Grid GRID Reference ManualIrregular grid P.3.0.4

Irregular grid P.3.0.4

Irregular

PurposeCreate a new grid using the irregular grid method.

DescriptionThe following menu is presented:

This is the most complex of all the grid creation methods. The grid is constructed by creating control lines to construct a ‘skeleton’ grid. After the skeleton grid has been made it can be filled with equalized areas of grid blocks to form a full corner point grid.

Control lines (rows or columns) will become rows or columns within the finished grid when it is constructed. Lines may be entered in any direction: the program will invert any columns for which the start point has a higher y-coordinate than the end point (measured in grid coordinates) and any rows for which the start point has a higher x-coordinate than the end point.

Control lines are built out of any number of sections, each of which may either be entered using the cursor (or the digitizer if it has been set up) or picked from existing lines on the screen such as fault lines or feature lines. Thus, it can be ensured that grid lines run along faults by picking up fault lines directly.

The maximum number of control lines allowed for the skeleton grid depends on a program parameter (MXCTL). The usual upper limit is 50 rows and 50 columns.

Normally, the order in which the control lines are entered is arbitrary. By default, the program automatically sorts the lines from left to right and top to bottom (in grid coordinates based on the start points of the lines) when the “Make grid” option is selected. However, the user may choose whether automatic sorting is required, by responding to the prompt: ‘Sort control lines before grid generation? (Y/n)’. If the lines are not sorted, they will be processed in the order they were defined by the user. This may be useful, for example, when defining a grid with a curved boundary, where the geometry prevents automatic sorting from producing a satisfactory grid.


Option Function

1 Add ctl col

2 Add ctl row

3 Del ctl col

4 Del ctl row

5 Chg ctl col

6 Chg ctl row

7 Make grid

8 Out ctl lnes

9 Inp ctl lnes

Add control column

Add control row

Delete control column

Delete control row

Change control column

Change control row

Make grid

Output control lines

Input control lines


www.cadfamily.com

GRID Reference Manual Edit GridIrregular grid P.3.0.4

281

If the digitizing table has been set up, control lines should be entered by means of the table, otherwise the graphical cursor or mouse should be used.

Note Fault lines are represented within the grid by rows or columns of split nodes. Grid lines which lie along fault lines should therefore be split using the “Split nodes” option in order to obtain a throw at the fault when defining node depths.

If sloping faults on the map are to be modeled as vertical faults or as sloping faults in the simulation grid, then the sloping faults should have been input using major and minor fault segments as described in the “Add fault” section. A control line should then be placed along the major segment of the fault.

To model sloping faults in the simulation grid, it is not necessary to put control lines along both the upthrown and downthrown sections of the fault trace. The appropriate gap will appear naturally in the grid once the correct depths and sloping coordinate lines have been defined.

If options 1 to 7 are selected the current option is shown at the top of the screen in the header information area.


www.cadfamily.com

282 Edit Grid GRID Reference ManualAdd control column P.3.0.4.1

Add control column P.3.0.4.1

Add ctl col

PurposeCreate a control column for the irregular grid method.


A control column is a YZ-column which must be followed when an irregular grid is created. It can be made up of any number of line segments, joined together in any order. Control columns need not be parallel to the grid Y-axis, but should be oriented along the J-direction of the required final grid. Control columns should not cross each other.

It is not necessary for columns to cross the top and bottom rows in the grid although this will give greater control over the grid. If the bounding rows are not crossed, the first two points or last two points in the column will be extrapolated as necessary.

Points on lines are selected by calculating the nearest location on the line to the given point.

In order to use contour line segments the contours must be digitized lines, not contours generated from a mesh.

When a complete line has been entered the “Return” option should be taken so that the line is saved and a new line can be started.

Note During grid construction, control columns are colour-coded green, while control rows are yellow.


Option Function

1 Return

2 Add dig seg

3 Add flt seg

4 Add fet seg

5 Add cnt seg

6 Add zon seg

7 Abandon

Add digitized segment

Add fault segment

Add feature segment

Add contour segment

Add zone segment

Abandon current line


www.cadfamily.com

GRID Reference Manual Edit GridAdd control row P.3.0.4.2

283

Add control row P.3.0.4.2

Add ctl row

PurposeCreate a control row for the irregular grid method.


A control row is an XZ-row which must be followed when an irregular grid is created. It can be made up of any number of line segments joined together in any order. Control rows need not be parallel to the grid X-axis, but should be oriented along the I-direction of the required final grid. Control rows should not cross each other.

It is not necessary for rows to cross the left and right columns in the grid, although this will give greater control over the grid. If the bounding columns are not crossed, the first two points or last two points in the row will be extrapolated as necessary.

Points on lines are selected by calculating the nearest location of the line to the given point.

In order to use contour line segments the contours must be digitized lines, not contours generated from a mesh.

When a complete line has been entered, the “Return” option should be taken so that the line is saved and a new line can be entered.

Note During grid construction, control rows are colour-coded yellow, while control columns are green.


Option Function

1 Return

2 Add dig seg

3 Add flt seg

4 Add fet seg

5 Add cnt seg

6 Add zon seg

7 Abandon

Add digitized segment

Add fault segment

Add feature segment

Add contour segment

Add zone segment

Abandon current line


www.cadfamily.com

284 Edit Grid GRID Reference ManualDelete control column P.3.0.4.3

Delete control column P.3.0.4.3

Del ctl col

PurposeDelete a control column.

DescriptionThe user is asked to select the control column to be deleted. The selected column is highlighted and confirmation required to delete it.


www.cadfamily.com

GRID Reference Manual Edit GridDelete control row P.3.0.4.4

285

Delete control row P.3.0.4.4

Del ctl row

PurposeDelete a control row.

DescriptionThe user is asked to select the control row to be deleted. The selected row is highlighted and confirmation required to delete it.


www.cadfamily.com

286 Edit Grid GRID Reference ManualChange control column P.3.0.4.5

Change control column P.3.0.4.5

Chg ctl col

PurposeChange a control column.

DescriptionA section of a control column can be changed by selecting the start and end points of the section to be changed and respecifying the section in a similar fashion to adding a new control column (see Add ctl col P.3.0.4.1, page 282).


www.cadfamily.com

GRID Reference Manual Edit GridChange control row P.3.0.4.6

287

Change control row P.3.0.4.6

Chg ctl row

PurposeChange a control row.

DescriptionA section of a control row can be changed by selecting the start and end points of the section to be changed and respecifying the section in a similar fashion to adding a new control row (see Add ctl row P.3.0.4.2, page 283).


www.cadfamily.com

288 Edit Grid GRID Reference ManualMake grid P.3.0.4.7

Make grid P.3.0.4.7

Make grid

PurposeFill a skeleton grid of control lines with equalized areas of grid blocks.

DescriptionWhen the skeleton grid is ready the “Make grid” option should be selected. The user will first be asked whether the control lines are to be saved in a file (as for the “Out ctl lnes” option), and whether to sort the control lines before grid generation. By default, the program will sort the control lines into order (columns left to right and rows top to bottom) to ensure that all sub-sections of the grid will be identified correctly. However, in some cases it will be preferable to use the control lines in the order specified by the user (e.g. for a grid with a highly curved boundary).

Then the endpoints of each section of the grid are highlighted in turn, and the user is prompted for the number of columns or rows to create in each section. Equalized areas of grid blocks are then generated for each section of the skeleton grid.

The grid will be saved automatically in a file and the “Edt grid” menu will be presented.

Any further changes to the grid, such as locally moving grid nodes away from wells, can then be made from the “Edt grid” menus.


www.cadfamily.com

GRID Reference Manual Edit GridOutput control lines P.3.0.4.8

289

Output control lines P.3.0.4.8

Out ctl lnes

PurposeOutput control lines to a user file.

DescriptionControl lines may be output to a user file so that the same lines can be used to construct further grids. The user will always be prompted to save control lines when the “Make grid” option is selected.

The user is asked for the root name of the file to which the lines are to be written. The file will be given an extension .CTL.


www.cadfamily.com

290 Edit Grid GRID Reference ManualInput control lines P.3.0.4.9

Input control lines P.3.0.4.9

Inp ctl lnes

PurposeInput control lines from a user file.

DescriptionControl lines which have been output previously to a user file can be read back using this option. The lines may be deleted or changed using the options on this menu.

The user is asked for the name of the file from which the lines are to be read. The control lines will be drawn on the screen as they are read.


www.cadfamily.com

GRID Reference Manual Edit GridMark axes P.3.0.5

291

Mark axes P.3.0.5

Mark axes

PurposeCreate a new grid using the ‘mark axes’ method.

DescriptionThe user is asked to enter two opposite corners of a box which will form the boundary of the grid. The box is constructed parallel to the given grid coordinate system. Any corner of the box can then be adjusted until the “Box ready” option is selected. The user can then enter columns and rows parallel to the box sides to form a grid, by selecting options from the menu:

1 Ready

2 Add column

3 Add row

4 Abandon

This option can be used to ensure that columns and rows are spaced in such a way as to place wells centrally within grid blocks. When the user has entered enough rows and columns the “Ready” option will save the current grid and present the “Edt grid” menu.

Option 4 allows the creation of the grid to be abandoned at any time.


www.cadfamily.com

292 Edit Grid GRID Reference ManualInput grid P.3.0.6

Input grid P.3.0.6

Input grid

PurposeRead an existing grid from an ECLIPSE GRID file or ECLIPSE data file, or from a VIP data file.

DescriptionExisting simulation grids can be read into the GRID program. The user is prompted to indicate the type of file used for input:

The supported file types are:

If data are to be read from an ECLIPSE input data file, the user is prompted for the name of the file to be read and whether it is formatted. The standard .FILLED file and .GRDECL file are always formatted. If unformatted input is selected, a .GRDBIN file (produced by the BINARY option in “Out grid”) will be expected. If the file exists, the program looks for keywords SPECGRID, MAPAXES, COORD and ZCORN. An error is flagged if COORD or ZCORN is encountered before the SPECGRID keyword.

Once the global grid has been read the program checks the file for local grid refinements. The keywords for these are described in option P.3.8.2.6, “Inp LGR” (see page 363), which can also be used to read LGRs.

All other keywords which may be present in the data file are ignored. If property or active cell keywords are to be read they should be read using option P.3.8.5.6, “Inp property” (see page 389) or option P.3.8.3.6, “Inp active” (see page 371).

Input Eclipse EGRID or GRID file, data file or VIP file ? (e/g/D/v)

E An ECLIPSE grid in the extensible grid file format (i.e. a .EGRID or .FEGRID file). This format was introduced for the 2000A release and provides advantages in file size and input performance.

G A full grid in a .GRID file written using level 2 on the ECLIPSE output keyword GRIDFILE. Note that this contains information for all cells, not just the active cell data written when using level 1. (However, files output using level 1 may be loaded, provided that all cells are active.)

D A grid in the corner point format used for ECLIPSE input, produced by the FILL program or by GRID itself (i.e. a .FILLED file, a .GRDECL file or a .GRDBIN file).

NB: A corner point grid may be produced from block centre keywords by producing a .FILLED file from the FILL program.

V Alternatively, a grid can be read from a VIP data file, containing corner-point data defined by a CORP array.


www.cadfamily.com

GRID Reference Manual Edit GridInput grid P.3.0.6

293

If data are to be read from an ECLIPSE EGRID or GRID file, then the user is prompted for the name of the file to be read and whether the file is formatted. (Unformatted files have suffix .EGRID or .GRID whereas formatted files will have suffix .FEGRID or .FGRID). The entire GRID file is read, so that a grid created in this way will automatically contain any local grid refinements found in the file. Note that the grid must be complete (i.e. inactive cells must be included in the file).

If a MAPAXES keyword is found in a FILLED file, or if the corresponding data are found in an ECLIPSE EGRID or GRID file, the user will be given the option to use these data to define the grid coordinate system relative to the map system. The MAPAXES keyword is used to export the current grid axes when writing grid geometry data from GRID (see option P.3.9.2, “Out grid”, page 408). It will be copied to grid data files by FILL and ECLIPSE, allowing the grid to be positioned correctly if it is reloaded into GRID. The data associated with the MAPAXES keyword should not be changed by the user.

The user will also be prompted for the units of the input grid and for whether the grid is in map coordinates. (The grid is in map coordinates if its areal coordinate system is defined relative to the map origin, otherwise the XY values are taken as relative to the newly defined grid origin.) The data read will then be scaled appropriately, depending on the areal units of the model and the depth units given for the grid. If a GRIDUNIT keyword is found in the input file, the default grid units will be as specified by this keyword.

After the data have been read the grid coordinates are processed into the internal format used by GRID. The program checks the depths of the corners at each grid node searching for 'split nodes'. A node will be marked as split (either vertically or horizontally) if corner depths differ by greater than 0.001. Split nodes are displayed using tickmarks along block faces when the grid is displayed.

Notes• If a 'block centre' grid is read from an ECLIPSE GRID file then every node will be marked

as split in every direction so that, by default, every block face will be displayed with tick marks. However, the display of these tickmarks can be turned off using the Display option D.6.4, “Chg grid” (see page 581). (It is most efficient to do this before reading the grid.)

• GRID does not allow 2D radial local grid refinements to be displayed. All 2D radial local grid refinements are transformed to 3D refinements for GRID. (Note that solution data for 2D radial refinements will automatically be expanded to 3D when the data are loaded from restart files.)

• A VIP data file must contain the following data:

NX NY NZ COMP grid dimensions

CORP array of 24 corner point values for each grid block

The user will be prompted to enter the input data units and whether the grid is in map units. The following prompts are for VIP-specific options:

Reverse Y-direction for VIP grid ? (Y/n)


www.cadfamily.com

294 Edit Grid GRID Reference ManualInput grid P.3.0.6

This is needed to handle the CORP data in cases where the original X and Y axes were 'lefthanded', i.e. the Y-axis increases up the page. If the keyword RIGHTHANDED is present in the input file, the default for the above prompt is changed to N. If the grid is in map units, the default is also changed to N, as the Y-direction will be reversed automatically when converting the XY values to grid units.

In standard XYZ order, the CORP array consists of eight triplets of coordinate values for each grid block: (x1,y1,z1), (x2,y2,z2)..... (x8,y8,z8). In EIGHT order, the array is arranged as 8 x-values, 8 y-values, then 8 z-values: (x1,x2..... x8), (y1,y2..... y8), (z1,z2..... z8). The default response will be adjusted if the option EIGHT is given on the same line as CORP.

The user can choose whether to write out a new .GRID file directly, using the CORP array data:

Note that the construction of VIP grid blocks may not give straight coordinate lines throughout the reservoir, as in GRID models, and the grid may be altered due to coordinate line definition when it is read into GRID. However, a .GRID file written using the CORP array data will correspond exactly to the original VIP model.

Contact SIS Customer Support if you wish to discuss VIP-GRID conversion problems.

• A .EGRID data file may contain a dual porosity grid, in which the matrix geometry is defined together with the active cell numbering for both the matrix and fracture. As the GRID program does not explicitly handle dual porosity models, this will be handled as follows:

• The matrix geometry is loaded

• The user is prompted to set the active cell numbers using either the matrix or the fracture values.

Is CORP array order standard XYZ or EIGHT ? (s/E)

Write out a .GRID file now using CORP arrays ? (y/N)


www.cadfamily.com

GRID Reference Manual Edit GridCopy grid P.3.0.7

295

Copy grid P.3.0.7

Copy grid

PurposeCopy an existing grid.

DescriptionA new grid can be created by copying an existing grid associated with the current model. (Grids associated with other models must be written to a user file and read using the “Inp grid” facility.)

The user is prompted for the name of the grid to be copied.


www.cadfamily.com

296 Edit Grid GRID Reference ManualMerge grids P.3.0.8

Merge grids P.3.0.8

Merge grids

PurposeCreate a grid with sloping coordinate lines by merging the coordinate lines from two grids.

DescriptionThis option can be used to create a simulation grid with sloping coordinate lines for modelling faults. Before using “Merge grids”, two dummy grids must be created, representing the top and bottom of the reservoir grid structure. These two grids are then merged to form a new grid in which the coordinate lines are defined by pairs of corresponding points taken from the top and bottom grids.

The user is expected to create a first grid using a top structure map and a second grid using a bottom structure map. Grid rows or columns should be placed along fault lines on each map. (The fault lines will represent the intersections of the faults with the surfaces represented by the two maps, and so a sloping fault will be in different locations on each map.) The number of rows and columns must be the same for both grids.

Depths must be set for each grid by sampling the appropriate map before the coordinate lines can be merged.

On entering the “Merge grids” option, the user will be prompted as follows:

Merging of the grids is achieved by copying the coordinate lines and top corner depths of the first grid, to the top layer of the new grid, and then copying the coordinate line locations and depths for the second grid, to the bottom layer of the new grid. Split node flags will also be copied if present.

The top or bottom of the coordinate lines may be taken from the second grid to define the bottom layer of the new grid: this depends on which surface of the dummy grid was sampled when it was set up. The user is prompted to choose which surface of the bottom grid will be used:

Before saving the new grid, the program will check the depths of the top and bottom of the new coordinate lines and highlight any nodes where the bottom of the coordinate line is too high (i.e. the bottom depth is less than or equal to the top depth). The user may, however, choose to continue and save the new grid, after such errors have been found, in order to check where the problems have occurred.

The new grid will consist of a single layer, with sloping coordinate lines where required. To obtain a final model, it can be split into further layers and the intermediate depths can be sampled as required.

Enter depth units for grid or RETURN for FEETEnter the name of the grid to be copiedEnter the name of the bottom grid

Use depths from top or bottom of coordinate lines ? (T/b)


www.cadfamily.com

GRID Reference Manual Edit GridMerge grids P.3.0.8

297

Note It is important that both grids have the same units and axes, since coordinate line locations are measured in grid coordinates. If the bottom grid is defined with different units and/or different axes, warnings will be issued and the program will adjust the data for merging.


www.cadfamily.com

298 Edit Grid GRID Reference ManualCross-section grid P.3.0.9

Cross-section grid P.3.0.9

X-sect grid

PurposeCreate a cross-section grid.

DescriptionThis option allows a cross-section grid to be created. The option is useful if the cross-section geometry has been drawn as a section through the reservoir.

The grid is created along the x-axis of the display and the display is changed to an XZ cross-section. The user is prompted for the width (DY) of all the cells and whether a digitizing table is to be set up. The DX of each required cell can then be entered in turn in a similar fashion to the “Vector grid” option.

When all the cells have been given areal dimensions the top depths for cells can either be digitized (using the cursor if no table has been set up) or a single top depth can be given. Similarly, depths for subsequent layers can be set by digitizing along a layer or by entering a DZ value.


www.cadfamily.com

GRID Reference Manual Edit GridEdit layer P.3.2

299

Edit layer P.3.2

Edt layer

PurposeEdit all the nodes on a grid layer.

DescriptionThe “Edt layer” option displays the following menu:

The “Return” option returns the user to the “Edt grid” menu options. Each of the other options is described in the following sections.

If the “Abandon” option is taken then any edits made during the current entry to the “Edt layer” option will be discarded.


Option Function

1 Return

2 Def dep lay

3 Def thk lay

4 Add layer

5 Del layer

6 Div layer

7 Spl layer

8 Jn layer

Define depth of layer

Define thickness of layer

Add layer

Delete layer

Divide layer

Split layer

Join layer


www.cadfamily.com

300 Edit Grid GRID Reference ManualDefine depth of layer P.3.2.2

Define depth of layer P.3.2.2

Def dep lay

PurposeDefine the depth of a grid layer.

DescriptionThe depths of all the nodes in the current edit layer can be changed. The current edit layer can be changed when this option is selected. The user is prompted for the new depths, which may be defined by a constant, an expression, by sampling a map or by copying depths from another grid layer. (Enter ‘S’ to sample a map, ‘C’ to copy depths.)

For sloping coordinate lines the sampled depth is unlikely to be the same as the depth at the point the coordinate line intersects the map surface. This problem is overcome by repeating the sampling. An alternative, which may be useful in cases where the iterative method does not converge, is to use the bisection method to find the intersection depth. (Enter ’I’ for the bisection method.)

For further details see "Specifying depths" on page 274.

The user is then prompted to choose whether to change the nodes in all layers below the current layer and whether to change the nodes in all the layers above the current layer.

Note that fault throws will only be set correctly if the appropriate nodes have first been ‘split’ using option P.3.5.7, “Spl nodes” (see page 332) or the automatic splitting facility P.3.9.4, “Spt grid” (see page 420), to allow more than one depth to be set at each node. If nodes lie on fault lines and have not been split it is likely that null values will be returned at these nodes. Null values may also be returned at nodes which lie within an area bounded by major fault lines (e.g. sloping fault planes or fault regions which do not have a minor fault segment as one side). Any nodes which lie outside the model area will also be set to null, as will nodes at which values cannot be sampled from a specified map, due to sparse data or incorrect sampling parameters.

If null values are obtained, the user will be prompted as follows:

The null values are processed according to the user's response:

• If a number is entered at this stage, it will be used to replace the null values.

• If option 'F' is selected, the null values will be filled by finding any non-null nodes from the surrounding grid blocks and averaging their values using inverse distance weighting, allowing for split nodes. The process is repeated up to 10 times. If any null corners remain, the user is prompted to enter a default value for these points.

• If option 'U' is selected, the node values are taken from the existing grid depths.

Note that when selecting a value to use in place of nulls, it is recommended that a suitable datum level should be entered instead of the default null value (typically 1.0E6). Otherwise, the range of depths used for cross-section displays and 3-D displays will be exaggerated and it will be difficult to display and edit the resulting grid.

WARNING - Null value returned at highlighted point(s)...&Enter value for nulls (or F - Fill or U - Use old values)


www.cadfamily.com

GRID Reference Manual Edit GridDefine depth of layer P.3.2.2

301

If depth checking is enabled, the computed depths for each node will be adjusted to ensure that layers in the grid do not overlap. If coordinate checking is enabled, further checks will be applied, to ensure that node depths are not set to values which would result in coordinate lines crossing. These checking facilities can be toggled off, if required, via options P.7.8, “Tog dep chk” and P.7.9, “Tog crd chk” (see page 536).

This option is not available from cross-sectional displays: the display can be changed to an areal display when the option is selected.


www.cadfamily.com

302 Edit Grid GRID Reference ManualDefine thickness of layer P.3.2.3

Define thickness of layer P.3.2.3

Def thk lay

PurposeDefine the thickness of a grid layer.

DescriptionThe thickness of all the nodes in the current edit layer can be defined by entering a constant, an expression or by sampling a map.

The user is prompted for the thickness of the current edit layer (see note on ‘Specifying depths’ at the beginning of this chapter). The thickness of the current layer can be set by changing either the bottom depths or the top depths of the layer. If the bottom depths are changed then the depths of all deeper layers can also be reset accordingly. If top depths are changed then the depths of all shallower layers can be reset.

If depth checking is enabled, the computed depths for each node will be adjusted if necessary, to ensure that layers in the grid do not overlap. If coordinate checking is enabled, further checks will be applied, to ensure that node depths are not set to values which would result in coordinate lines crossing. These checking facilities can be toggled off, if required, via options P.7.8, “Tog dep chk” and P.7.9, “Tog crd chk” (see page 536).

A correction factor for sloping coordinates lines can be applied to sampled values when defining grid node thicknesses. The correction factor must be enabled using option P.7.5, “Tog slp crds”. (See Appendix D for details.)



www.cadfamily.com

GRID Reference Manual Edit GridAdd a grid layer P.3.2.4

303

Add a grid layer P.3.2.4

Add layer

PurposeAdd a layer to the grid.

DescriptionThe user is asked whether to add the new layer to the top or to the bottom of the grid. If the new layer is added to the top of the grid, it will become layer 1 and the existing layers will be renumbered accordingly.

The user is prompted for the thickness of the layer to be added. If the current display is of a grid cross-section, then the new layer may be added by marking the depth of each node using the input locator or digitizing table.

The pattern of ‘split’ nodes is copied from above or below so that faults are continued through the grid layers.



www.cadfamily.com

304 Edit Grid GRID Reference ManualDelete a grid layer P.3.2.5

Delete a grid layer P.3.2.5

Del layer

PurposeDelete a layer of nodes from the grid.

DescriptionIf the grid is being edited from an areal display, the user is asked for the layer to delete, the default being the layer on display. The numbering of the layers below the deleted layer is then adjusted.

If the grid is being edited from a cross-sectional display the user is asked to select the layer to be deleted. The selected layer is highlighted and confirmation requested to delete it.

A layer cannot be deleted if only one layer of grid blocks remains.

A layer cannot be deleted if it contains nodes shared with an LGR or host grid.


www.cadfamily.com

GRID Reference Manual Edit GridDivide a grid layer P.3.2.6

305

Divide a grid layer P.3.2.6

Div layer

PurposeDivide a grid layer.

DescriptionIf the grid is being edited from an areal display, the user is asked to enter the number of layers into which the current edit layer is to be divided.

If the grid is being edited from a cross-sectional display the user is asked to select the layer to be divided and the number of required layers.

The thicknesses of the new layers may be calculated either by equally dividing the thickness of the current layer at each node or by entering the fraction of the total thickness to be assigned to each layer. (It is not necessary for the sum of the fractions to be equal to 1, as each fraction will be divided by the total fraction when the thickness of each layer is calculated.)


www.cadfamily.com

306 Edit Grid GRID Reference ManualSplit a layer P.3.2.7

Split a layer P.3.2.7

Spl layer

PurposeSplit a layer of grid nodes.

DescriptionThis option allows the top of one grid layer to be separated from the bottom of the grid layer immediately above it in order to model, for example, shale layers.

The option is independent of option P.3.5.7, “Spl nodes” (see page 332), which splits nodes vertically, so nodes can have up to 8 different corner depths.

The user is asked to enter the thickness of the gap between the upper and lower layers: this may be determined by sampling a map. Only those nodes at which the gap thickness is greater than 0.01 will be split.

If the top of the grid blocks is being edited, all lower layers can be moved down by the gap thickness. If the bottom of the grid blocks is being edited, all upper layers can be moved up.

Nodes which have been split in this way are marked by a single line from the node towards the centre of the grid block.

Arithmetic formulae can be used for this option, as for other depth or thickness setting options. For example, to check that the gap thickness at each node is positive, select this option and enter the expression ‘>0’ at the prompt.



www.cadfamily.com

GRID Reference Manual Edit GridJoin layers P.3.2.8

307

Join layers P.3.2.8

Jn layer

PurposeRejoin a layer of grid nodes.

DescriptionThis option allows a layer of grid nodes which have been split, using option P.3.2.7 “Spl layer” (see page 306) or P.3.3.7 “Spl area” (see page 314), to be rejoined.

If the top of the grid blocks is being edited, all lower layers can be moved up by the gap thickness. If the bottom of the grid blocks is being edited, all upper layers can be moved down.



www.cadfamily.com

308 Edit Grid GRID Reference ManualEdit area P.3.3

Edit area P.3.3

Edt area

PurposeEdit an area of nodes on a grid layer.

DescriptionThe “Edt area” option displays the following menu:

The “Edt area” options are only available from areal displays of the grid. The user will be asked for the layer to be edited when this option is selected.


Option 2 operates on regular areas of the grid. The area selected is the smallest grid area that contains two given input points.

The other options operate on more general areas of the grid. The area can be selected by selecting nodes around the exterior of the required region. It is not necessary to select every node on the boundary: missed nodes will be selected automatically by ‘zig-zagging’ along the grid. (Note that in setting up the zig-zag pattern, the column number will be incremented if possible, before incrementing the row number.) Alternatively, an area can be defined by a ‘box’ within a range of rows and columns, or by selecting a grid region number which corresponds to the required area.

If the “Abandon” option is taken then any edits made during the current entry to the “Edt area” option will be discarded.


Option Function

1 Return

2 Equ area

3 Equ columns

4 Equ rows

5 Def dep are

6 Def thk are

7 Spl area

8 Jn area

9 Vrt area

Equalize area

Equalize columns

Equalize rows

Define depth of area

Define thickness of area

Split area

Join area

Verticalise (‘straighten’) area


www.cadfamily.com

GRID Reference Manual Edit GridEqualize area P.3.3.2

309

Equalize area P.3.3.2

Equ area

PurposeRegenerate an area of the grid by moving both rows and columns to give an equalized grid area.

DescriptionAn area of the grid is selected and the grid within the area regenerated to give an equally spaced grid. Note that this option also moves the nodes on the boundary of the selected area and may not be suitable if the boundary lies along a fault trace.

The user is asked to select the area to be regenerated and to confirm that the area is correct. The area will be the smallest area of grid blocks containing two marked locations.

If sloping coordinate lines have been activated then the user is asked whether to move the top or bottom of the coordinate lines along the row, or both. If only the top or bottom is to be moved the layer at which to fix the opposite end must be given.

This option is not available from cross-sectional displays.


www.cadfamily.com

310 Edit Grid GRID Reference ManualEqualize columns P.3.3.3

Equalize columns P.3.3.3

Equ columns

PurposeRegenerate an area of the grid by moving columns so that they are equally separated.

DescriptionAn area of the grid is selected and the grid within the area regenerated to give equally spaced columns. The nodes on the boundary columns are not moved.

The user is asked to select the area to be regenerated and to confirm that the area is correct.

If sloping coordinate lines have been activated then the user is asked whether to move the top or bottom of the coordinate lines along the row, or both. If only the top or bottom is to be moved, the layer at which to fix the opposite end must be given.



www.cadfamily.com

GRID Reference Manual Edit GridEqualize rows P.3.3.4

311

Equalize rows P.3.3.4

Equ rows

PurposeRegenerate an area of the grid by moving rows so that they are equally separated.

DescriptionAn area of the grid is selected and the grid within the area regenerated to give equally spaced rows. The nodes on the boundary rows are not moved.

The user is asked to select the area to be regenerated and to confirm that the area is correct.

If sloping coordinate lines have been activated then the user is asked whether to move the top or bottom of the coordinate lines along the row, or both. If only the top or bottom is to be moved, the layer at which to fix the opposite end must be given.



www.cadfamily.com

312 Edit Grid GRID Reference ManualDefine depth of an area P.3.3.5

Define depth of an area P.3.3.5

Def dep are

PurposeDefine the depth of an area of a grid layer.

DescriptionAn irregular area of the grid is selected. This can be done by marking nodes around its boundary, or by defining a box within a selected range of rows and columns, or by specifying a grid region number.

The user is prompted for the new depths (see "Specifying depths" on page 274) and then asked whether to change the depths of nodes in all layers below the current layer and above the current layer.

Note that fault throws will only be set correctly if the appropriate nodes have first been ‘split’, using option P.3.5.7, “Spl nodes” (see page 332) or the automatic splitting facility P.3.9.4, “Spt grid” (see page 420), to allow more than one depth to be set at each node.

Only the nodes which lie within the area are changed. Corners of split nodes which lie outside the area will be changed according to the manner in which individual nodes have been split.

If depth checking is enabled, the computed depths for each node will be adjusted to ensure that layers in the grid do not overlap. If coordinate checking is enabled, further checks will be applied, to ensure that node depths are not set to values which would result in coordinate lines crossing. These checking facilities can be toggled off, if required, via options P.7.8, “Tog dep chk” and P.7.9, “Tog crd chk” (see page 536).



www.cadfamily.com

GRID Reference Manual Edit GridDefine thickness of an area P.3.3.6

313

Define thickness of an area P.3.3.6

Def thk are

PurposeDefine the thickness of an area of a grid layer.

DescriptionAn irregular area of the grid is selected. This can be done by marking nodes around its boundary, or by defining a box within a selected range of rows and columns, or by specifying a grid region number.

The user is prompted for the new thicknesses (see notes on ‘Specifying depths’ at the beginning of this chapter). The thickness of the current layer can be set by changing either the bottom depths or the top depths of the layer. If the bottom depths are changed, the depths of all deeper layers can also be reset accordingly. If top depths are changed, the depths of all shallower layers can be reset.


If depth checking is enabled, the computed depths for each node will be adjusted if necessary, to ensure that layers in the grid do not overlap. If coordinate checking is enabled, further checks will be applied, to ensure that node depths are not set to values which would result in coordinate lines crossing. These checking facilities can be toggled off, if required, via options P.7.8, “Tog dep chk” and P.7.9, “Tog crd chk” (see page 536).




www.cadfamily.com

314 Edit Grid GRID Reference ManualSplit area P.3.3.7

Split area P.3.3.7

Spl area

PurposeSplit an area of grid nodes.

DescriptionThis option allows the top of one grid layer to be separated from the bottom of the grid layer immediately above it in order to model, for example, shale layers. The option is independent of option P.3.5.7, “Spl nodes” (see page 332), which splits nodes vertically, so nodes can have up to 8 different corner depths.

An irregular area of the grid can be selected.

The user is asked to enter the thickness of the gap between the upper and lower layers and this may be determined by sampling a map. Only those nodes at which the gap thickness is greater than 0.01 will be split.

If the top of the grid blocks is being edited, all lower layers can be moved down by the gap thickness. If the bottom of the grid blocks is being edited, all upper layers can be moved up.

Nodes which have been split in this way are marked by a single line from the node towards the centre of the grid block.


Arithmetic formulae can be used for this option, in the same way as for other depth or thickness setting options. For example, to check that the gap thickness at each node is positive, select this option and enter ‘>0’ at the prompt.



www.cadfamily.com

GRID Reference Manual Edit GridJoin an area P.3.3.8

315

Join an area P.3.3.8

Jn area

PurposeRejoin an area of grid nodes.

DescriptionThis option allows an area of grid nodes which have been split, using option P.3.2.7 “Spl layer” (see page 306) or P.3.3.7 “Spl area” (see page 314), to be rejoined.

If the top of the grid blocks is being edited, all lower layers can be moved up by the gap thickness. If the bottom of the grid blocks is being edited, all upper layers can be moved down.

An irregular area of the grid can be selected for rejoining.



www.cadfamily.com

316 Edit Grid GRID Reference ManualVerticalize an area P.3.3.9

Verticalize an area P.3.3.9

Vrt area

Purpose‘Verticalize’ the coordinate lines within an area of the grid.

DescriptionThis option allows an area of coordinate lines which have been made sloping to be reset to be vertical.

An irregular area of the grid can be selected for ‘verticalizing’.



www.cadfamily.com

GRID Reference Manual Edit GridEdit lines P.3.4

317

Edit lines P.3.4

Edt lines

PurposeEdit rows or columns of grid nodes.

DescriptionThe “Edt lines” option displays the following menu:


If the “Abandon” option is taken then any edits made during the current entry to the “Edt lines” option will be discarded.


Option Function

1 Return

2 Add rows

3 Add columns

4 Del row

5 Del column

6 Move row

7 Mov column

8 Str line

9 Equ line

Add rows

Add columns

Delete row

Delete column

Move row

Move column

Straighten line

Equalize line


www.cadfamily.com

318 Edit Grid GRID Reference ManualAdd rows P.3.4.2

Add rows P.3.4.2

Add rows

PurposeAdd a number of rows to the grid.

DescriptionThis option can be used either to add rows to the grid, or to divide an existing row. If the grid is the global grid the user is asked:

If the grid is an LGR it can not be extended, although a row can still be divided.

If rows are added to the front of the grid, their width will be proportional to the original last row in the grid. The user can enter a constant proportionality factor or a different factor for each new row. The active cell number, coarsening group number and any region or property value, will be copied from the original last row.

If rows are added to the back of the grid, their width will be proportional to the original first row in the grid. The user can enter a constant proportionality factor or a different factor for each new row. The active cell number, coarsening group number and any region or property value, will be copied from the original first row.

If this option is used to divide a row of blocks, the user is first asked to select the row before being prompted for the number of new rows. The new rows are obtained either by equally dividing the current row or by entering the fraction of the current row to be used for each new row. (It is not necessary for the sum of the fractions to be equal to 1, as each fraction will be divided by the total fraction when new rows are calculated.) The active cell number and any region or property values for the new grid blocks will be copied from the blocks in the row that has been selected.

This option is not available from XZ-plane displays of the grid but is available from YZ-plane displays. This option is also not available for radial LGRs.

Extend grid forwards, backwards or divide a row (f/b/D) ?


www.cadfamily.com

GRID Reference Manual Edit GridAdd columns P.3.4.3

319

Add columns P.3.4.3

Add columns

PurposeAdd a number of columns to the grid.

DescriptionThis option can be used either to add columns to the grid, or to divide an existing column. If the grid is the global grid the user is asked:

If the grid is an LGR it can not be extended, although a column can still be divided.

If columns are added to the left hand edge of the grid, their width will be proportional to the original first column in the grid. The user can enter a constant proportionality factor or a different factor for each new column. The active cell number, coarsening group number and any region or property value, will be copied from the original first column.

If columns are added to the right hand edge of the grid, their width will be proportional to the original last column in the grid. The user can enter a constant proportionality factor or a different factor for each new column. The active cell number, coarsening group number and any region or property value, will be copied from the original last column.

If this option is used to divide a column of blocks, the user is first asked to select the column before being prompted for the number of new columns. The new columns are obtained either by equally dividing the current column or by entering the fraction of the current column to be used for each new column. (It is not necessary for the sum of the fractions to be equal to 1, as each fraction will be divided by the total fraction when new columns are calculated.) The active cell number and any region or property values for the new grid blocks will be copied from the blocks in the column that has been selected.

This option is not available from YZ-plane displays of the grid.

Extend grid left, right or divide a column (l/r/D) ?


www.cadfamily.com

320 Edit Grid GRID Reference ManualDelete a row P.3.4.4

Delete a row P.3.4.4

Del row

PurposeDelete a row from the grid.

DescriptionA row of nodes is selected by placing the cursor close to a node in the row. The selected row is highlighted and confirmation requested to delete the row.

Removal of a row of nodes between two rows of cells will result in a single row of cells. The properties and region numbers of the row containing the cursor will be deleted, and the properties and region numbers of the new row will be taken from the cells in the other row. The remaining rows will be renumbered.

This option is not available from XZ-plane displays of the grid.


www.cadfamily.com

GRID Reference Manual Edit GridDelete a column P.3.4.5

321

Delete a column P.3.4.5

Del column

PurposeDelete a column from the grid.

DescriptionA column of nodes is selected by placing the cursor close to a node in the column. The selected column is highlighted and confirmation requested to delete the column.

Removal of a column of nodes between two columns of cells will result in a single column of cells. The properties and region numbers of the column containing the cursor will be deleted, and the properties and region numbers of the new column will be taken from the cells in the other column. The remaining columns will be renumbered.



www.cadfamily.com

322 Edit Grid GRID Reference ManualMove a row P.3.4.6

Move a row P.3.4.6

Mov row

PurposeMove a grid row.

DescriptionIf the current session has sloping coordinate lines enabled, the user is asked whether to move the top or bottom of the coordinate lines along the row, or both. If only the top or bottom is to be moved, the layer at which to fix the opposite end must be given.

A node on the row to be moved is selected and a new position for the node requested. Each node in the row is then moved along the line joining it to the adjacent row. This scheme ensures that regular grids parallel to the axes remain regular, whatever the alignment to the grid origin.

If coordinate line checking is enabled, checks will be applied, to ensure that nodes are not moved to positions which would result in coordinate lines crossing. These checking facilities can be toggled off, if required, using option P.7.9, “Tog crd chk” (see page 536).

This option is not available from XZ-plane displays of the grid.


www.cadfamily.com

GRID Reference Manual Edit GridMove a column P.3.4.7

323

Move a column P.3.4.7

Mov column

PurposeMove a grid column.

DescriptionIf the current session has sloping coordinate lines enabled, then the user is asked whether to move the top or bottom of the coordinate lines along the column, or both. If only the top or bottom is to be moved the layer at which to fix the opposite end must be given.

A node on the column to be moved is selected and a new position for the node is requested. The node in the column is then moved along the line joining it to the adjacent column. This scheme ensures that regular grids remain regular, whatever the alignment of the grid to the grid origin.

If coordinate line checking is enabled, checks will be applied to ensure that nodes are not moved to positions which would result in coordinate lines crossing. These checking facilities can be toggled off, if required, with option P.7.9, “Tog crd chk” (see page 536).



www.cadfamily.com

324 Edit Grid GRID Reference ManualStraighten a line P.3.4.8

Straighten a line P.3.4.8

Str line

PurposeStraighten a section of a grid row or column.

DescriptionIf the current session has sloping coordinate lines enabled, the user is asked whether to move the top or bottom of the coordinate lines along the line, or both. If only the top or bottom is to be moved the layer at which to fix the opposite end must be given.

Two nodes along a column or a row are selected. The nodes are checked to ensure they lie on the same row or column, and that no nodes between the specified nodes are split. The nodes along the line are repositioned along a line from one node to the other. The new nodes are placed at the intersection of the straight line with the crossing rows or columns.

This option is not available from cross-section displays of the grid.


www.cadfamily.com

GRID Reference Manual Edit GridEqualize a line P.3.4.9

325

Equalize a line P.3.4.9

Equ line

PurposeEqualize a section of a grid row or column by repositioning the nodes at regular intervals along the current line.

DescriptionIf the current session has sloping coordinate lines enabled, the user is asked whether to move the top or bottom of the coordinate lines along the line, or both. If only the top or bottom is to be moved the layer at which to fix the opposite end must be given.

Two nodes along a column or a row are selected. The nodes are checked to ensure they lie on the same row or column, and that no nodes between the specified nodes are split. The nodes along the line are repositioned at equal distances along the existing line.


www.cadfamily.com

326 Edit Grid GRID Reference ManualEdit nodes P.3.5

Edit nodes P.3.5

Edt nodes

PurposeEdit individual grid nodes.

DescriptionThe “Edt nodes” option displays the following menu:

The “Return” option returns the user to the “Edt grid” menu. Each of the other options is described in the following sections.

If the “Abandon” option is taken then any edits made during the current entry to the “Edt nodes” option will be discarded.


Option Function

1 Return

2 Mov node

3 Mov nde-nde

4 Def nde dep

5 Mrk nde dep

6 Def nde thk

7 Spl nodes

8 Jn nodes

9 Mov crd lne

Move node

Move node to node

Define node depth

Mark node depth

Define node thickness

Split nodes

Join node

Move coordinate line


www.cadfamily.com

GRID Reference Manual Edit GridMove a node P.3.5.2

327

Move a node P.3.5.2

Mov node

PurposeMove a node to another location.

DescriptionIf the current session has sloping coordinate lines enabled, then the user is asked whether to move the top or bottom of the coordinate line or both. If only the top or bottom of the line is to be moved the user is prompted for the layer at which to fix the line. Nodes can then be selected and moved on the screen.

If coordinate line checking is enabled, checks will be applied to ensure that nodes are not moved to positions which would result in coordinate lines crossing. These checking facilities can be toggled off, if required, with option P.7.9, “Tog crd chk” (see page 536). (Note that the checks may not provide complete protection, if the adjacent grid blocks are not convex.)

Any number of nodes can be moved without additional prompts until another option is selected or this option reselected. The depth of the node is not changed, even if the node is being moved from a cross-sectional display. For cross-sectional displays the node will be moved in the X or Y direction only.


www.cadfamily.com

328 Edit Grid GRID Reference ManualMove node to node P.3.5.3

Move node to node P.3.5.3

Mov nde-nde

PurposeMove a node to the same location as another node, i.e. make two nodes coincident.

DescriptionIf the current session has sloping coordinate lines enabled, then the user is asked whether to move the top or bottom of the coordinate line or both. If only the top or bottom of the line is to be moved the user is prompted for the layer at which to fix the line.

Nodes can then be selected and moved on the screen. Before each node is moved the user is asked for confirmation. It is not recommended that nodes are made coincident unless it is absolutely necessary to have triangular blocks along a sealing fault.

Any number of nodes can be moved without additional prompts until another option is selected or this option reselected.

The depth of the node is not changed even if the node is being moved from a cross-sectional display.


www.cadfamily.com

GRID Reference Manual Edit GridDefine node depth P.3.5.4

329

Define node depth P.3.5.4

Def nde dep

PurposeDefine the depth at a single node.

DescriptionThe user is asked to select the node at which the depth is to be defined and prompted for the new depth for the node (see notes on ‘Specifying Depths’ at the beginning of this chapter). If the node is not split the node depth is set to the given depth. If it has been split, only the corners not separated from the selected corner by split faces are changed. The user is asked whether the depths of higher and lower nodes are to be changed by the same amount as the selected node.

If depth checking is enabled, the node depth will be adjusted to ensure that layers in the grid do not overlap. If coordinate checking is enabled, further checks will be applied, to ensure that the new node depth will not result in coordinate lines crossing. These checking facilities can be toggled off, if required, via options P.7.8, “Tog dep chk” and P.7.9, “Tog crd chk” (see page 536).


www.cadfamily.com

330 Edit Grid GRID Reference ManualMark node depth P.3.5.5

Mark node depth P.3.5.5

Mrk nde dep

PurposeMark the depth of a single node from a cross-sectional display.

DescriptionThe user is asked to select the node for which the depth is to be defined and asked to mark the new depth for the node. The given x- or y-location is ignored: only the depth is significant for the given point and the node is moved up or down its coordinate line to the given depth.

If the node is not split the node depth is set to the given depth. If it has been split, only the corners not separated from the selected corner by split faces are changed.

The depths of nodes below and above the selected node can also be changed by the same amount.

If depth checking is enabled, the node depth will be adjusted to ensure that layers in the grid do not overlap. If coordinate checking is enabled, further checks will be applied to ensure that the new node depth will not result in coordinate lines crossing. These checking facilities can be toggled off, if required, with options P.7.8, “Tog dep chk” and P.7.9, “Tog crd chk” (see page 536).

This option is not valid from areal displays.


www.cadfamily.com

GRID Reference Manual Edit GridDefine node thickness P.3.5.6

331

Define node thickness P.3.5.6

Def nde thk

PurposeDefine the thickness at a single node.

DescriptionThe user is asked to select the node at which the thickness is to be defined and prompted for the new thickness at the node (see notes on ‘Specifying Depths’ at the beginning of this chapter). If the node is not split the node thickness is set to the given thickness. If it has been split, only the corners not separated from the selected corner by split faces are changed.

The depths of nodes below and above the selected node can also be changed by the same amount.

If depth checking is enabled, the node depth will be adjusted to ensure that layers in the grid do not overlap. If coordinate checking is enabled, further checks will be applied, to ensure that the new node depth will not result in coordinate lines crossing. These checking facilities can be toggled off, if required, with options P.7.8, “Tog dep chk” and P.7.9, “Tog crd chk” (see page 536).


www.cadfamily.com

332 Edit Grid GRID Reference ManualSplit nodes P.3.5.7

Split nodes P.3.5.7

Spl nodes

PurposeSplit grid nodes.

DescriptionThe corners at each grid node are all held at the same depth until the node has been defined as `split’. When a node has been split, a different depth can be held for each corner at the node. Which depths actually differ is determined by the manner in which the node is split. This “Spl nodes” option defines the vertical splitting at nodes. (Horizontal splitting to model shale breaks is defined using the options “Spl layer”, page 306, or “Spl area”, page 314.)

When nodes are split in one layer, the layers below and above can be optionally split at the same time. When a layer is added to the grid, the fault pattern from the adjacent layer is copied to the new layer. Similarly, if new rows or columns are added, they will have split nodes defined where necessary to maintain the fault pattern.

When the option is selected the following sub-menu appears:

Any number of nodes may be split by moving from one node to the next. The nearest node is selected as each data point is given. If selected nodes are not adjacent, intermediate nodes are also included, using a `zig-zag’ pattern if selected nodes do not lie on the same column or row. (The column number is incremented preferentially to the row number.)

The “Delete prev” option deletes the previous node. Note that it only deletes one node at a time.

When the “End” option is selected, the given nodes will be marked as split by drawing tick marks along the appropriate grid block faces. In fact, the option may be better described as splitting `faces’ rather than nodes. Tick marks are drawn along the downthrown edge of the block face after the node depths have been redefined.

The option does not change the depths at any of the split nodes. This must be done by using one of the methods for defining depths and initially the side of the grid line that is marked will be arbitrary. Since all the corners of the end nodes of a line of split nodes must necessarily have the same depths, the tickmarks will be drawn on the same block face as for the adjacent split node.

A node may be split in any number of different directions to represent crossing faults or `T’ faults.

When depths are defined at nodes that have been split in this manner, all corners which are not separated by a split face will be given the same depth. Corners separated by a split face will have different depths. In practice, this means that a node should be split in at least two directions to define a fault along a row, column or at a corner. At the edges of the grid the splitting of the nodes is `reflected’ to enable this to happen.

1 Data point2 Test point 3 Delete prev 4 End


www.cadfamily.com

GRID Reference Manual Edit GridSplit nodes P.3.5.7

333

For non-split nodes, depths or thicknesses are sampled at the nodal point. If the node is split then more than one depth is sampled at corners, depending on the way in which the node is split. The program searches around the split node looking for fault traces on the sampled map. If a major fault segment is found within a half-cell distance of the split node, then the sampled points will be taken from either side of the point at which a line from the node to an adjacent node crosses the fault. The node which is used to construct the crossing line depends on the geometry of the split node. For example, if the node is split column-wise, lines are constructed from the node in the previous column to the split node and from the next column to the split node. This scheme means that it is not necessary for grid nodes to overlay fault traces exactly.

If no fault is found within the half-cell distance, all corners will be sampled at the node location. (This situation is most likely to occur when non-faulted thickness maps are being sampled for a faulted grid.)


www.cadfamily.com

334 Edit Grid GRID Reference ManualJoin nodes P.3.5.8

Join nodes P.3.5.8

Jn nodes

PurposeRejoin split grid nodes.

DescriptionThe user is asked to select the nodes to be rejoined and whether to rejoin nodes in layers below and above the current layer. The option works in a similar way to the split node option, by joining the specified block faces. It is therefore necessary to select at least two nodes for the option to have any effect.

After a node has been rejoined, if there remains at least one split face at the node, then the corner depths at the node are unchanged and may be inconsistent with the splitting of the node. However, when the depths are reset they will be reset according to the current splitting configuration. If there are no split block faces remaining at the node then all the corners at the node will take the depth of the top left corner of the node.


www.cadfamily.com

GRID Reference Manual Edit GridMove a coordinate line P.3.5.9

335

Move a coordinate line P.3.5.9

Mov crd lne

PurposeMove the top or bottom of a coordinate line at a split node, to define a sloping coordinate line.

DescriptionThe user is asked to select the corner to act as a pivot point and the corner to be moved. The new position for the moved corner must then be selected.

The coordinate line at the selected node is redefined from the pivot corner to the moved corner.

The selected node must be split for this option to be used from an areal display.


www.cadfamily.com

336 Edit Grid GRID Reference ManualMove a coordinate line P.3.5.9


www.cadfamily.com

GRID Reference Manual Edit GridEdit fault lines P.3.6

337

Edit fault lines P.3.6

Edt flt lnes

PurposeEdit rows or columns of grid nodes. These options have been designed primarily for use with fault lines within the grid.

DescriptionThe “Edt flt lnes” option displays the following menu:


If the “Abandon” option is taken then any edits made during the current entry to the “Edt flt lnes” option will be discarded.


Option Function

1 Return

2 Mov row-flt

3 Mov col-flt

4 Mov nde-flt

5 Mov row-slp

6 Mov col-slp

7 Def slp lne

8 Def dep lne

Move row to fault

Move column to fault

Move node to fault

Move row to slope

Move column to slope

Define sloping line

Define depth line


www.cadfamily.com

338 Edit Grid GRID Reference ManualMove row to a fault P.3.6.2

Move row to a fault P.3.6.2

Mov row-flt

PurposeMove a row of the simulation grid onto a section of a fault.

DescriptionIf the current session has sloping coordinate lines enabled, then the user is asked whether to move the top or bottom of the coordinate lines along the row, or both. If only the top or bottom is to be moved the layer at which to fix the opposite end must be given.

The section of the fault line to be used is obtained by marking the endpoints of the section. The selected section is highlighted and confirmation is requested that the section is correct. The segment of the row to be moved is obtained by selecting two nodes along the same row. The user is asked whether to proceed and then the row will be moved onto the fault at the points where the grid lines on either side of the selected row cross the fault line. The nodes will not be moved at points where this would result in grid lines crossing.

Fault lines are represented within the grid by a series of split nodes. After the row has been moved onto the fault line it should be split using the “Spl nodes” option (P.3.5.7, see page 332) and the grid should then be resampled.

This option is not available from cross section displays of the grid.


www.cadfamily.com

GRID Reference Manual Edit GridMove column to a fault P.3.6.3

339

Move column to a fault P.3.6.3

Mov col-flt

PurposeMove a column of the simulation grid onto a section of a fault.

DescriptionIf the current session has sloping coordinate lines enabled, then the user is asked whether to move the top or bottom of the coordinate lines along the column, or both. If only the top or bottom is to be moved the layer at which to fix the opposite end must be given.

The section of the fault line to be used is obtained by marking the endpoints of the section. The selected section is highlighted and confirmation that the section is correct requested. The segment of the column to be moved is obtained by selecting two nodes along the same column. The user is asked whether to proceed and then the column will be moved on to the fault at the points where the grid lines on either side of the selected column cross the fault line. The nodes will not be moved at points where this would result in grid lines crossing.

Fault lines are represented within the grid by series of split nodes. After the column has been moved onto the fault line it should be split using the “Spl nodes” option (see page 332) and the grid should then be resampled.



www.cadfamily.com

340 Edit Grid GRID Reference ManualMove node to fault P.3.6.4

Move node to fault P.3.6.4

Mov nde-flt

PurposeMove a single node onto a fault.

DescriptionIf the current session has sloping coordinate lines enabled, then the user is asked whether to move the top or bottom of the coordinate line or both. If only the top or bottom of the line is to be moved the user is prompted for the layer at which to fix the line.

Individual nodes can be selected and moved on to fault lines. This option may be useful for getting nodes onto fault junctions, where the “Mov row-flt” and “Mov col-flt” options can be awkward, as they only move nodes along existing grid lines. The node will be moved to the nearest location on the nearest fault to the given cursor position.

Any number of nodes can be moved without additional prompts until another option is selected or this option reselected.


www.cadfamily.com

GRID Reference Manual Edit GridMove row to a sloping fault P.3.6.5

341

Move row to a sloping fault P.3.6.5

Mov row-slp

PurposeSplit a row of nodes, resample the depths on either side of a sloping fault and reposition one side of the row of nodes on the other side of the fault.

DescriptionThe “Mov row-slp” option assumes that the row to be split has already been lined up along one side of a sloping fault using the “Mov row-flt” option.

The segment of the row to be split is obtained by selecting two nodes along the same row. The side of the row from which the first node was selected is the side that will be moved on to the fault section. The section of the fault line to be used is obtained by marking the endpoints of the section. The selected section is highlighted and confirmation that the section is correct requested.

The user is the prompted for the throw at the fault (see "Specifying depths" on page 274). If a throw is entered explicitly, the downthrown side is taken as the side from which the first node was selected and the given throw will be added to the depths on that side of the row without changing the depths on the other side. If the throw is to be set by sampling a map, the depths on both sides of the split row will be reset according to the sampled values. The depths of nodes in deeper layers than the current layer will be automatically changed by the same amount as the nodes in the current layer.

The side of the row to be moved will be placed on to the selected fault segment at the points where the grid lines on either side of the selected row cross the fault line. The nodes will not be moved at points where this would result in grid lines crossing.

This option is not recommended for general use, since sloping fault lines are not often digitized on a map to the correct scale. This can lead to gross exaggeration of the slope of the fault if it is taken from a single map. The user may prefer to consider using the “Merge grids” facility P.3.0.8, page 296) for defining sloping faults.



www.cadfamily.com

342 Edit Grid GRID Reference ManualMove column to a sloping fault P.3.6.6

Move column to a sloping fault P.3.6.6

Mov col-slp

PurposeSplit a column of nodes, resample the depths on either side of a sloping fault and reposition one side of the column of nodes on the other side of the fault.

DescriptionThe “Mov col-slp” option assumes that the column to be split has already been lined up along one side of a sloping fault using the “Mov col-flt” option.

The segment of the column to be split is obtained by selecting two nodes along the same column. The side of the column from which the first node was selected is the side that will be moved on to the fault section. The section of the fault line to be used is obtained by marking the endpoints of the section. The selected section is highlighted and confirmation that the section is correct requested.

The user is then prompted for the throw at the fault (see note on ‘Specifying depths’ at the beginning of this chapter). If a throw is entered explicitly the downthrown side is taken as the side from which the first node was selected and the given column will be added to the depths on that side of the column, without changing the depths on the other side. If the throw is to be set by sampling a map, the depths on both sides of the split column will be reset according to the sampled values. The depths of nodes in deeper layers than the current layer will be automatically changed by the same amount as the nodes in the current layer.

The side of the column to be moved will be placed on to the selected fault segment at the points where the grid lines on either side of the selected column cross the fault line. The nodes will not be moved at points where this would result in grid lines crossing.

This option is not recommended for general use, since sloping fault lines are not often digitized on a map to the correct scale. This can lead to gross exaggeration of the slope of the fault if it is taken from a single map. The user may prefer to consider using the “Merge grids” facility, page 296, for defining sloping faults.



www.cadfamily.com

GRID Reference Manual Edit GridDefine a sloping line P.3.6.7

343

Define a sloping line P.3.6.7

Def slp lne

PurposeDefine the slope angle for a line of coordinate lines.

DescriptionSloping coordinate lines may be used within the grid to model sloping faults on the map. This option allows the user to enter the angle of a line of sloping coordinate lines to the vertical.

The user is asked to select the grid line for which the slope is to be defined and to enter the angle of the slope to the vertical. The line is defined by moving from one grid node to the next. If nodes are missed, nodes will automatically be selected ‘zig-zagging’ along the grid. The zig-zag will be made by incrementing the column number in preference to the row, whenever possible.

The azimuthal angle for each line is made in two sweeps. Firstly, along rows, and secondly, along columns. During the first sweep an azimuthal direction is defined along intersecting columns and during the second sweep along intersecting rows. At corners, the calculated angle is therefore a combination of the two sweeps. The angle will vary continuously along the fault.

The vertical angle is defined so that the bottom of the coordinate line is moved towards the opposite side of the grid block from which the first node of the row is selected. The coordinate line is held fixed at the node corner diagonally opposite to the first node corner selected.

Coordinate lines which have been made to slope can be straightened by entering an angle to the vertical of ‘=0’ in this option. (Simply entering ‘0’ will not be sufficient.) Alternatively, the “Vrt area” option P.3.3.9 (see page 316) can be used to straighten all lines in an area.

This option does not change the depths of any nodes which lie on the coordinate lines. These should be set by defining the grid depths in some way. However, it should be noted that if sloping faults are to be correctly represented, proper use should be made of the ‘Major’ and ‘Minor’ segments when digitizing fault traces. It has been found that sloping faults are often drawn on maps with gaps across the fault of disproportionate width. Minor fault segments are transparent to the interpolation algorithm and so the surface on either side of the corresponding major segment is continuous. The proper throw will therefore be obtained at the fault even if the grid line appears to be in the middle of the fault region. (The position of the split grid line will be the proper location of the fault trace for the given angle, if it had been drawn to scale.) Note that when the contouring back option is used, the minor segments are not treated as transparent.

This option cannot be used within radial grid refinements, although the outer coordinate lines of a radial LGR can be changed by using this option on the parent grid.

The user may prefer to consider using the “Merge grids” facility P.3.0.8 (see page 296) for defining sloping faults.


www.cadfamily.com

344 Edit Grid GRID Reference ManualDefine line depth P.3.6.8

Define line depth P.3.6.8

Def dep lne

PurposeDefine the depth of a line of grid nodes.

DescriptionThe depth of a line of nodes can be defined. If nodes along the line have been split, only the depths on the side of the line from which the node was selected are changed. Thus, for example, a fault throw can be changed.

The line is defined by moving from one grid node to the next. If nodes are missed, nodes will be automatically selected by ‘zig-zagging’ along the grid. The zig-zag will be made by incrementing the column number in preference to the row number, where possible.

The user is prompted for the new depth for the line (see "Specifying depths" on page 274). The depths of the nodes in the line are changed and the user asked whether to change the depths of layers below and above the current layer.


www.cadfamily.com

GRID Reference Manual Edit GridShow values P.3.7

345

Show values P.3.7

Sho values

PurposeShow or highlight grid values.

DescriptionThe “Sho values” option displays the following menu:


Note This menu can be selected quickly from any menu via the special key “S”.


Option Function

1 Return

2 Sho x,y,z

3 Sho x,y,z

4 Sho nde thk

5 Hgh dep rng

6 Hgh thk rng

7 Chk angles

Show x,y,z values

Show i,j,k positions

Show node thickness

Highlight depth range

Highlight thickness range

Check grid orthogonality


www.cadfamily.com

346 Edit Grid GRID Reference ManualShow x,y,z P.3.7.2

Show x,y,z P.3.7.2

Sho x,y,z

PurposeShow the coordinates of a grid node or corner.

DescriptionThe x,y coordinates can be shown in grid units (relative to the grid origin), or in map units. Radial coordinates can be selected for radial LGRs, to show distance from grid centre and angle in degrees, instead of the cartesian x,y position.

The user is asked to select the node for which the coordinates are required. The x,y,z location of the selected corner will be shown at the bottom of the screen until another node or another option is selected.

If the current grid contains LGRs, the nearest corner in any grid shown on the display will be selected. To show x,y,z positions on LGR nodes that cannot be viewed on a global plane, use “Edt LGR” (option D.7.9, page 617, or type “L”) to edit the required grid.


www.cadfamily.com

GRID Reference Manual Edit GridShow I,J,K P.3.7.3

347

Show I,J,K P.3.7.3

Sho i,j,k

PurposeShow the i,j,k coordinates of a grid block.

DescriptionThe user is asked to select the block for which the coordinates are required. The i,j,k values of the selected block will be shown at the bottom of the screen until another block or another option is selected.


www.cadfamily.com

348 Edit Grid GRID Reference ManualShow thickness P.3.7.4

Show thickness P.3.7.4

Sho nde thk

PurposeShow thickness of a grid block at a node.

DescriptionThe user is asked to select the node at which the thickness is required. The thickness at the given node (or corner if the node is split) will be shown at the bottom of the screen until another node or another option is selected.

Note that, if the current grid contains LGRs, the nearest corner in any grid shown on the display will be selected. If the corner is shared by two grids, both node thickness values will be shown. To show thickness values at LGR nodes that cannot be viewed on a global plane, use “Edt LGR” (option D.7.9, page 617, or type “L”) to edit the required grid.


www.cadfamily.com

GRID Reference Manual Edit GridHighlight depth range P.3.7.5

349

Highlight depth range P.3.7.5

Hgh dep rng

PurposeHighlight the nodes within a given range of depths.

DescriptionThe user is prompted for the range of depths required, e.g. 7200, 7500, and given the option to change the Granite settings for the markers used to highlight the nodes.

All the nodes within the given depth range will be highlighted. The highlights will not be removed until the display is refreshed.


www.cadfamily.com

350 Edit Grid GRID Reference ManualHighlight thickness range P.3.7.6

Highlight thickness range P.3.7.6

Hgh thk rng

PurposeHighlight the nodes having a given range of thicknesses.

DescriptionThe user is prompted for the range of thicknesses required, e.g. -1000, 0, and given the option to change the Granite settings for the markers used to highlight the nodes.

All the nodes within the given thickness range will be highlighted. The highlights will not be removed until the display is refreshed.


www.cadfamily.com

GRID Reference Manual Edit GridCheck grid orthogonality P.3.7.7

351

Check grid orthogonality P.3.7.7

Chk angles

PurposeCheck grid angles for orthogonality.

DescriptionThe “Chk angles” option displays the following menu:

This menu allows the user to check the angles of a simulation grid, by calculating a measure of orthogonality. The program calculates and displays the maximum deviation from 90 degrees for any corner of a grid block. These angles are calculated in the XY plane by default, but the user may choose to check angles in the XZ or YZ plane.

The “Return” option returns the user to the “Edt grid” menu options. Options 5, 6 and 7 are as described for property fill (see the “Edt property” menus, P.3.8.5, page 384). Each of the other options is described in the following sections.


Option Function

1 Return

2 Cal orthog

3 Sho orthog

4 Sho orth fll

5 Chg orth fll

6 Mov orth key

7 Chg orth key

8 Rpt orthog

Calculate orthogonality

Show orthogonality for a grid block

Show orthogonality colour fill

Change orthogonality colour fill

Move orthogonality colour key

Change orthogonality colour key

Display orthogonality report


www.cadfamily.com

352 Edit Grid GRID Reference ManualCalculate grid orthogonality P.3.7.7.2

Calculate grid orthogonality P.3.7.7.2

Cal orthog

PurposeCalculate orthogonality for simulation grid block angles.

DescriptionThis option calculates the orthogonality measure for all blocks in a simulation grid. Usually, the angles in the XY plane are calculated, but the user may select the XZ or YZ plane if required.

For each grid block, 8 angles are calculated at each corner of the two faces in the selected plane. The program checks for non-convex grid blocks (where an individual angle may deviate from 90 degrees by up to 270 degrees).

The orthogonality measure for a particular grid block is the worst deviation from 90 degrees for any corner of the grid block.

After this calculation has been performed, the user can check the orthogonality of individual grid blocks, select a colour display of the orthogonality measure, or display or print a report summarizing the results for the complete grid (see the other options for menu P.3.7.7, “Chk angles”, page 351).

Note that this orthogonality measure is most useful for detecting distorted grid blocks in an irregular grid, and can also be used for qualitative comparisons of different simulation grids. However, the user should be aware that this measure does not take account of flow directions: a grid which appears orthogonal here may be subject to errors in a five-point difference scheme, if it is not oriented correctly for the predominant flow directions. In some cases, a grid with some distorted cells may be a more suitable model than an orthogonal grid which does not represent the reservoir geometry accurately.


www.cadfamily.com

GRID Reference Manual Edit GridShow orthogonality for a grid block P.3.7.7.3

353

Show orthogonality for a grid block P.3.7.7.3

Sho orthog

PurposeShow the orthogonality measure for a grid block.

DescriptionThe user is asked to select the required grid block. The i,j,k values and the orthogonality measure of the selected block will be shown at the bottom of the screen until another block or another option is selected.


www.cadfamily.com

354 Edit Grid GRID Reference ManualShow orthogonality colour fill P.3.7.7.4

Show orthogonality colour fill P.3.7.7.4

Sho orth fll

PurposeShow a colour fill display of the grid block orthogonality measure.

DescriptionEach grid block will be colour filled according to its orthogonality value, as calculated by option P.3.7.7.2, “Cal orthog” (see page 352).

When the blocks are colour filled, reselection of this option removes the colour fill. Colour fill will be removed automatically when the “Chk angles” menu is exited.


www.cadfamily.com

GRID Reference Manual Edit GridDisplay orthogonality report P.3.7.7.8

355

Display orthogonality report P.3.7.7.8

Cal orthog

PurposeDisplay / print a report on the orthogonality of a grid.

DescriptionAn orthogonality summary is shown for the global grid and for any LGRs which exist within the grid. The user may choose to print the report to a file. After viewing or printing the report, select Q to quit and return to the “Chk angles” menu.

ExampleExample orthogonality report:

Orthogonality Report for Grid D4Deviation from orthogonality in XY plane(Worst deviation from 90 degrees for any grid block corner)Maximum deviation for all grid blocks = 51.9 degrees------------------------------------------------------------Global grid Size: 30 x 17 x 5Total cells: 2550 Total active cells: 2089Max deviation: 51.9 Worst cell: (8,6,1)Deviation range Total cells Total active cells< 10.0 1475 ( 57.8 % ) 1310 ( 62.7 % )10.0 - 20.0 690 ( 27.1 % ) 474 ( 22.7 % )20.0 - 30.0 195 ( 7.6 % ) 150 ( 7.2 % )30.0 - 40.0 130 ( 5.1 % ) 100 ( 4.8 % )40.0 - 50.0 45 ( 1.8 % ) 40 ( 1.9 % )50.0 - 60.0 15 ( .6 % ) 15 ( .7 % )60.0 - 70.0 0 ( .0 % ) 0 ( .0 % )70.0 - 80.0 0 ( .0 % ) 0 ( .0 % )80.0 - 90.0 0 ( .0 % ) 0 ( .0 % )> 90.0 0 ( .0 % ) 0 ( .0 % )--------------------------------------------------------------


www.cadfamily.com

356 Edit Grid GRID Reference ManualDisplay orthogonality report P.3.7.7.8


www.cadfamily.com

GRID Reference Manual Edit GridEdit blocks P.3.8

357

Edit blocks P.3.8

Edt blocks

PurposeEdit grid block data.

DescriptionThe “Edt block” option displays the following menu:



Option Function

1 Return

2 Ref grid

3 Edt active

4 Edt regions

5 Edt property

6 Edt FIP

7 Del regions

8 Del property

9 Crs grid

Refine grid

Edit active/inactive cells

Edit regions

Edit properties

Edit fluids-in-place

Delete regions

Delete properties

Coarsen grid


www.cadfamily.com

358 Edit Grid GRID Reference ManualRefine grid P.3.8.2

Refine grid P.3.8.2

Ref grid

PurposeLocal grid refinement options.

DescriptionThe “Ref grid” option displays the following menu:

The local grid refinement option allows areas of the grid to be refined for use with the ECLIPSE local grid refinement facility. Both Cartesian and 3D radial local refinements can be created (but not 2D radial). Nested grids can also be created.

When the grid geometry and associated parameters are output, local grid refinement keywords will be generated automatically for refined areas of the grid.

Refined parts of the grid are displayed automatically. Local grids may be edited either by simply typing "L" or by using option D.7.9, “Edt LGR” (see page 617), on the “Chg view” display menu. Grids can be nested when editing a refined grid by creating a new LGR within the refined grid.

After LGRs have been defined, some of the normal grid editing facilities are no longer available. For example, it is not possible to add rows where the coarse grid has been refined or to move the grid. It is possible to move nodes within the fine grid and to move nodes which are shared by both the coarse and fine grids (although this is not recommended). Consistency is maintained between the fine grid and the coarse grid at nodes which are common to the two grids, but GRID does not ensure that the fine grid fits exactly into the coarse grid if the fine grid has been edited manually.

Block values for local grid blocks default to the corresponding coarse grid block values. The default values may be overwritten by resampling layers in the fine grid, to allow greater definition of block properties in the fine grid.

The “Return” option returns the user to the “Edt blocks” menu options. Each of the other options is described in the following sections.


Option Function

1 Return

2 Cre LGR

3 Rad LGR

4 Del LGR

5 Del all LGRs

6 Inp LGR

7 Sho LGR name

Create Cartesian LGR

Create Radial LGR

Delete LGR

Delete all LGRs

Input LGR

Show LGR name


www.cadfamily.com

GRID Reference Manual Edit GridCreate local grid refinement P.3.8.2.2

359

Create local grid refinement P.3.8.2.2

Cre LGR

PurposeCreate a Cartesian local grid refinement.

DescriptionThe user is asked to select the area of the grid to be refined. Two points are marked and the smallest grid area which contains both points is highlighted.

The user is asked to confirm that the area is correct and will then be prompted for the range of layer numbers to be refined.

Each row, column and layer in the refined area may be arbitrarily divided into any number of fine rows, columns and layers, using the same techniques as used for adding rows and columns in the coarse grid. The user is prompted for the number of fine columns in each coarse column, followed by the fractions to allocate to each fine column. The procedure is then repeated for the rows and finally for the layers.

The fine grid is then drawn at the required position in the coarse grid.

Refinements can be created within already refined areas of the grid, by first selecting an LGR (by typing "L", or using option D.7.9, "Edt LGR", page 617). However, depending on the version of the simulator to be used, there may be restrictions on the use of nested LGRs. Therefore, the first time a nested LGR is created, the program warns the user, and asks if he or she wishes to continue creating the LGR.

Refinements cannot be created within radial LGRs.


www.cadfamily.com

360 Edit Grid GRID Reference ManualRadial local grid refinement P.3.8.2.3

Radial local grid refinement P.3.8.2.3

Rad LGR

PurposeCreate a radial local grid refinement.

DescriptionECLIPSE supports two types of radial refinements: a single-column radial LGR that occupies one column in the parent grid; and a 4-column radial LGR which occupies a 2x2 box within the parent grid. The user is first asked to specify which type of LGR is required, and to select a block (or group of blocks) to be refined. The user is then prompted for the number of radial cells, the range of layers to be refined and the inner radius for the radial refinement (in the current model area units).

Azimuthal cell blocks are created automatically by GRID. In the single-column radial LGR each parent grid block is divided into four azimuthal blocks with edges aligned with the block diagonals. The 4-column radial LGR contains eight azimuthal cells, each parent grid block being divided into two by joining the node at the centre of the four columns to the four corners of the 2x2 box.

ECLIPSE also allows radial LGRs in which the host cells are not split azimuthally: a 2D single-column radial LGR with one azimuthal cell of 360 degrees; and a 4-column radial LGR containing four azimuthal cells. GRID however cannot be used to create these alternative LGRs.

The radial division of the cells may be specified by the user or may be defaulted to a logarithmic increase in radius from the inner radius. The inner radii are the same for each layer, so that the inner cells form vertical cylinders. For the 4-column radial LGR, the central co-ordinate line must be vertical to ensure that the refined cells line up with the host cells. The outer radius of the refinement is set by ECLIPSE so the LGR volume is equivalent to the host cell volume.

The division of the layers can be specified in the same way as for a Cartesian refinement: either by entering fractions or by allowing the cells to be divided equally.

The fine grid is then drawn at the required position in the coarse grid.

Refinements can be created within already refined areas of the grid, by first selecting an LGR (by typing "L", or using option D.7.9, "Edt LGR"). However, depending on the version of the simulator to be used, there may be restrictions on the use of nested LGRs. Therefore, the first time a nested LGR is created, the program warns the user, and asks if he or she wishes to continue creating the LGR.

Note Radial LGRs cannot be refined.


www.cadfamily.com

GRID Reference Manual Edit GridDelete local grid refinement .3.8.2.4

361

Delete local grid refinement .3.8.2.4

Del LGR

PurposeDelete a local grid refinement.

DescriptionThe user is asked to select the local grid refinement to be deleted by placing the cursor in a block of the locally refined area, or by selecting the LGR from a list of grid names. The refinement will be highlighted and the user asked to confirm that it should be removed.

If a local grid refinement is itself refined, then its refinements must be deleted before the LGR can be deleted. These are deleted in the same way as any other LGR.


www.cadfamily.com

362 Edit Grid GRID Reference ManualDelete all local grid refinements P.3.8.2.5

Delete all local grid refinements P.3.8.2.5

Del all LGRs

PurposeDelete all local grid refinements.

DescriptionThe user is asked to confirm that all local grid refinements are to be removed. This option may be useful if it is found that some new editing must be made to the coarse grid, which cannot be done while local grid refinements are defined.

If the current grid is an LGR, the program will restore the global grid edit status before performing any deletions.


www.cadfamily.com

GRID Reference Manual Edit GridInput LGR P.3.8.2.6

363

Input LGR P.3.8.2.6

Inp LGR

PurposeRead LGR grids from a formatted data file (e.g. FILLED file or GRDECL file).

DescriptionThis option provides an alternative method of reading an LGR, instead of reading the entire grid using the “Input grid” (P.3.0.6) option for ECLIPSE GRID files. LGRs are loaded into the existing coarse grid.

The option works in the same way as reading a normal grid from a FILLED file, except that it looks for the keyword RADFIN4, RADFIN or CARFIN. If one of these keywords is found, the program checks that the grid does not already exist, or overlaps an existing LGR. Then the user is prompted to choose whether to load the LGR.

The data following the RADFIN4, RADFIN or CARFIN keyword may consist of either a complete set of corner point data for the LGR (keywords COORD and ZCORN) or a suitable set of LGR refinement keywords (NXFIN, NYFIN, NZFIN, HXFIN, HYFIN, HZFIN and HRFIN, plus INRAD for a radial grid). See the "ECLIPSE Reference Manual" and "ECLIPSE Technical Description" for full details of the refinement data. If the corner point data are not given, an LGR will be constructed by GRID, using any of the refinement data that are available, or suitable default values if necessary.

If a MAPAXES keyword is found in the input file, and the axes do not match the current grid axes, the user is prompted to choose whether the LGR should be adjusted:

If corner point data are input, but the LGR being read will not fit exactly into the global cells which contain it, a warning is issued, and the user is given the option to force the LGR into the grid, by adjusting the global grid if necessary:

This option may be useful if, for example, the LGR has been adjusted or resampled as a separate grid, so that it does not fit the host grid exactly, but the user now wishes to include it in a full field model. To ensure GRID puts the LGR cells in the correct host cells the NXFIN, NYFIN and NZFIN keywords can be used before the COORD and ZCORN keywords. However, care must still be taken in loading an LGR which does not match the global grid. If the LGR is nowhere near the correct position, the global grid may appear corrupted after inserting the local grid. (If there are obvious problems, use the abandon key "A" to remove the new LGR immediately.)

'Adjust LGR position from axes defined in file ? (Y/n)'

'Adjust grid structures to force LGR input ? (y/N)'


www.cadfamily.com

364 Edit Grid GRID Reference ManualInput LGR P.3.8.2.6

Notes• Only the structural data are read. Property or region data for the LGR should be read

separately by editing the local grid and then using the option “Inp property” P.3.8.5.6, page 389, or “Inp region” P.3.8.4.6, page 380.

• Nested LGRs (i.e. refinements within refinements) can be input. The first time a nested grid is read, the program warns the user that a nested LGR structure is being created. The format of the CARFIN and RADFIN keywords for nested LGRs is given in the "ECLIPSE Reference Manual". GRID will only read a nested grid if the host grid name specified by the CARFIN / RADFIN keyword matches the name of an existing LGR.


www.cadfamily.com

GRID Reference Manual Edit GridShow local grid refinement P.3.8.2.7

365

Show local grid refinement P.3.8.2.7

Sho LGR name

PurposeShow the name of a local grid refinement.

DescriptionThe user is asked to select the LGR for which the name is required. Its name will be shown at the bottom of the screen.


www.cadfamily.com

366 Edit Grid GRID Reference ManualEdit active cells P.3.8.3

Edit active cellsP.3.8.3

Edt active

PurposeDefine grid cells to be active or inactive.

DescriptionThe “Edt active” option displays the following menu:


Grid cells are defined to be active or inactive by an active cell number, set to 1 for active cells and 0 for inactive cells.

Active cells are shown by default as solid grid lines on the screen and inactive cells as dotted lines. The active/inactive cell display can be changed from display option D.6.4.2, “Chg grd dsp” (see page 582), which allows either the active or inactive cell display to be switched off. Inactive cells will not be shown in 3D grid displays.


Option Function

1 Return

2 Def act lay

3 Def act are

4 Def act blk

5 Sho active

6 Inp active

7 Out active

8 Opr active

9 Tot active

Define active layer

Define active area

Define active block

Show active

Input active cell numbers

Output active cell numbers

Operate on active cells

Show total active cells


www.cadfamily.com

GRID Reference Manual Edit GridDefine active layer P.3.8.3.2

367

Define active layer P.3.8.3.2

Def act lay

PurposeDefine a layer of grid cells to be active or inactive.

DescriptionA layer of grid blocks can be defined to be active or inactive by entering 0 (inactive), 1 (active) or S to sample a map. If the active cells are to be defined by sampling a map, the sampled values are rounded to 0 or 1.


www.cadfamily.com

368 Edit Grid GRID Reference ManualDefine active area P.3.8.3.3

Define active area P.3.8.3.3

Def act are

PurposeDefine an area of grid cells to be active or inactive.

DescriptionAn area of grid blocks can be defined to be active or inactive. The area is defined by marking cells on the edge of the area, or by specifying a box within a range of rows and columns, or by selecting a grid region number. The area can be any shape and will be closed automatically.

The user is then prompted for the active cell number. The response can be 0 (inactive), 1 (active) or S to sample a map. If the active cells are defined by sampling a map, the sampled values are rounded to 0 or 1.

The active/inactive cell numbers may be copied to cells with the same I,J positions in layers below and above the current layer.


www.cadfamily.com

GRID Reference Manual Edit GridDefine active blocks P.3.8.3.4

369

Define active blocks P.3.8.3.4

Def act blk

PurposeDefine individual grid cells to be active or inactive.

DescriptionGrid cells can be defined to be active or inactive one cell at a time. The user is asked whether to make cells inactive (0) or active (1). All selected cells will then be set accordingly until a new option is selected or this option selected again. Each cell will be redrawn as it is selected.


www.cadfamily.com

370 Edit Grid GRID Reference ManualShow active P.3.8.3.5

Show active P.3.8.3.5

Sho active

PurposeShow whether a grid cell is active or inactive.

DescriptionAs each cell is selected it is highlighted and a message given at the bottom of the screen indicating whether the cell is active or inactive.


www.cadfamily.com

GRID Reference Manual Edit GridInput active cell numbers P.3.8.3.6

371

Input active cell numbers P.3.8.3.6

Inp active

PurposeRead active cell numbers from a user file or an ECLIPSE INIT file.

DescriptionThe user is asked whether the data are to be read from a user data file or an ECLIPSE INIT file.

The user is prompted for the name of the file to be read and whether it is formatted. If the file exists, it is read until the ACTNUM data are found. If the grid contains LGRs, the user can choose to load data for all grids or for the current grid only (global or LGR). If the current grid is an LGR and input is from a user data file, the user can also choose whether to identify the LGR in the file or read the first ACTNUM array found.

If the file is a user data file, the format for the ACTNUM array should be as for the .GRDECL file written by the "Out active" option (P.3.8.3.7, see page 372) or the "Out grid" option (P.3.9.2, see page 408). Repeated values are allowed, as for ECLIPSE input, e.g. 5*1 can be used to represent five active cells. If the array contains too many or too few values, a warning is given, e.g.:

The default is to abandon input, but if the user chooses to continue, the data will be loaded into the grid, with any missing values set to zero.

Alternatively, data can be read from a binary data file (.GRDBIN), as written by "Out grid" (P.3.9.2), by selecting the data file to be unformatted.

If the data are read from an INIT file, then the file is searched for the pore volume array. Each cell will then be set active or inactive depending on whether the pore volume is greater than 0.000001. If an LGR is currently being edited, the pore volume array for the current LGR name is read.

Note A GRDECL file written by "Out active" (P.3.8.3.7) will not contain any CARFIN, RADFIN or REFINE keywords to identify LGRs. For this type of input, the user should choose to load data for the current grid only and read the first ACTNUM array found.

ACTNUM array contains insufficient values. Continue ? (y/N)


www.cadfamily.com

372 Edit Grid GRID Reference ManualOutput active cell numbers P.3.8.3.7

Output active cell numbers P.3.8.3.7

Out active

PurposeWrite active cell numbers to a user file.

DescriptionThe active cell array can be output to a file in a format suitable for input to a reservoir simulator. Output is written to a file with extension .GRDECL (or .GEC if 3-character extensions are used). The file will be opened if it has not already been opened, otherwise output will be added to existing output. If the file already exists, the user is asked whether to overwrite it.

The array is written out headed by the keyword ACTNUM with column numbers increasing fastest, then row numbers, then layer numbers. For example for a 10x7x2 grid:

ACTNUM1 1 1 1 1 1 1 0 0 01 1 1 1 1 1 1 1 0 01 1 0 1 1 1 1 1 1 01 1 0 0 0 1 1 1 1 11 1 0 0 0 1 1 1 1 01 1 0 0 1 1 1 1 0 01 0 0 0 0 1 1 0 0 01 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 1/


www.cadfamily.com

GRID Reference Manual Edit GridOperate on active cells P.3.8.3.8

373

Operate on active cells P.3.8.3.8

Opr active

PurposeOperate on the active cell array.

DescriptionThis option allows the user to operate on the entire ACTNUM array (rather than just a single layer). The arithmetic/logical parser may be used to give formulae which involve property or region number arrays. The results of the operation will be rounded to 0 or 1 to assign an active cell number.


www.cadfamily.com

374 Edit Grid GRID Reference ManualShow total active cells P.3.8.3.9

Show total active cells P.3.8.3.9

Tot active

PurposeShow total number of active cells

DescriptionA message is output, showing the total number of cells in the grid and the total number of active cells. If an XY plane is currently displayed, a further message is output, showing the totals for the current layer.


www.cadfamily.com

GRID Reference Manual Edit GridEdit region numbers P.3.8.4

375

Edit region numbers P.3.8.4

Edt regions

PurposeDefine region numbers for the grid.

DescriptionThe “Edt regions” option displays the following menu:


Regions are defined by integer values associated with each grid cell. Typical region arrays used for Eclipse input include: FIPNUM (for fluids-in-place reporting), SATNUM (for defining saturation table regions), EQLNUM (for equilibration regions).

The maximum number of different region arrays which may be set up for each grid depends on a program parameter (MXREG). This is usually set to 50.

The user is prompted for name of the region number array to be edited. If the region does not already exist a new one can be created. All cells will be given a region number of 1 when a new region is created.

New region names are checked for invalid characters and reserved keywords in the same way as for property names. A region cannot be created with the same name as an existing property.


Option Function

1 Return

2 Def reg lay

3 Def reg are

4 Def reg blk

5 Sho region

6 Inp region

7 Out regions

8 Opr region

9 Dsp regions

Define region layer

Define region area

Define region blocks

Show region numbers

Input region numbers

Output region numbers

Operate on region numbers

Display regions


www.cadfamily.com

376 Edit Grid GRID Reference ManualDefine region layer P.3.8.4.2

Define region layer P.3.8.4.2

Def reg lay

PurposeDefine a layer of region numbers.

DescriptionRegion numbers can be defined for a layer of grid cells.

Region numbers can be defined by entering a number or sampling a map, or by using the arithmetic/logical parser. The results will be rounded to the nearest integer. The facilities available for sampling maps are the same as those described when defining property layers.


www.cadfamily.com

GRID Reference Manual Edit GridDefine region area P.3.8.4.3

377

Define region area P.3.8.4.3

Def reg are

PurposeDefine region numbers for an area of grid cells.

DescriptionThe region numbers for an area of grid cells can be defined.

The area is defined by marking cells on the edge of the area, or by specifying a box within a range of rows and columns, or by selecting a grid region number. The area can be any shape and will be closed automatically.

Region numbers can be defined by entering a number or sampling a map, or by using the arithmetic/logical parser. The results are rounded to the nearest integer. The facilities available for sampling maps are the same as those described when defining property layers.


www.cadfamily.com

378 Edit Grid GRID Reference ManualDefine region blocks P.3.8.4.4

Define region blocks P.3.8.4.4

Def reg blk

PurposeDefine region numbers for individual grid cells.

DescriptionThe user is prompted for the region number to be set and asked to select the cells required. All selected cells will then be set accordingly until a new option is selected or this option selected again.


www.cadfamily.com

GRID Reference Manual Edit GridShow region numbers P.3.8.4.5

379

Show region numbers P.3.8.4.5

Sho region

PurposeShow the region number for a grid cell.

DescriptionAs each cell is selected it is highlighted and a message given at the bottom of the screen showing its region number.


www.cadfamily.com

380 Edit Grid GRID Reference ManualInput region numbers P.3.8.4.6

Input region numbers P.3.8.4.6

Inp region

PurposeRead region numbers from a user file.

DescriptionA property can be read from:

a A user data file, or

b An ECLIPSE INIT file.

The user is prompted for the name of the file to be read. If the file exists, it is read until the required region array is found. If the grid contains LGRs, the user can choose to load data for all grids or for the current grid only (global or LGR). If the current grid is an LGR and input is from a user data file, the user can also choose whether to identify the LGR in the file or read the first array found with the required region name.

For input from a user data file, the region number array must be complete for the current grid. Region numbers are expected with column number increasing fastest, then row number, then layer number. The format for the region array should be as for the .GRDECL file written by the “Out regions” option (P.3.8.4.7, see page 381) or the “Out grid” option (P.3.9.2, see page 408). Repeated values can be handled in the same way as for ECLIPSE input, e.g. 5*7 for 5 cells in region 7. If the array contains too many or too few values, a warning is given, e.g.

The default is to abandon input, but if the user chooses to continue, the data will be loaded into the grid, with any missing values set to zero. If the number of values in the array is less than the total, but equal to the number of active cells, the input values will be stored for active cells only.

For input from an INIT file, only region numbers for active cells will be input. Region numbers will not be modified for inactive cells.

Note A GRDECL file written by “Out regions” (P.3.8.4.7) will not contain any CARFIN, RADFIN or REFINE keywords to identify LGRs. For this type of input, the user should choose to load data for the current grid only and read the first suitable property array found.

SATNUM array contains insufficient values. Continue ? (y/N)


www.cadfamily.com

GRID Reference Manual Edit GridOutput region numbers P.3.8.4.7

381

Output region numbers P.3.8.4.7

Out region

PurposeWrite region numbers to a user file.

DescriptionThe region number array can be output to a file in a format suitable for input to a reservoir simulator. Output is written to a file with extension .GRDECL (or .GEC if 3-character extensions are used). The file will be opened if it has not already been opened, otherwise output will be added to existing output. If the file already exists, the user is asked whether to overwrite it.

The array is written out headed by the name of the region number with column numbers increasing fastest, then row numbers, then layer numbers.

For example for a 10x7x2 grid:

SATNUM7 7 5 4 2 1 1 2 5 67 6 4 2 1 1 1 1 3 57 6 4 2 2 1 2 2 3 57 6 4 3 2 2 2 2 4 57 6 5 4 3 2 2 3 4 57 7 6 5 4 3 3 3 5 57 7 6 5 4 3 2 5 5 51 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 1/


www.cadfamily.com

382 Edit Grid GRID Reference ManualOperate on region numbers P.3.8.4.8

Operate on region numbers P.3.8.4.8

Opr region

PurposeOperate on the region numbers array.

DescriptionThis option allows the user to operate on the entire array (rather than just a single layer). The arithmetic/logical parser may be used to give formulae which involve property or region number arrays. The results of the operation will be rounded to the nearest integer.


www.cadfamily.com

GRID Reference Manual Edit GridDisplay region numbers P.3.8.4.9

383

Display region numbers P.3.8.4.9

Dsp regions

PurposeChange region number display.


The “Return” option returns the user to the “Edt regions” menu. Option 3 is described in the “Smp contour” section, P.2.4.9.8.3 (see page 134). The other options operate in the same way as for property data.


Option Function

1 Return

2 Sho reg fll

3 Chg reg fll

4 Mov reg key

5 Chg reg key

6 Sho reg cnts

7 Chg reg cnts

8 Out reg cnts

Show region fill

Change region fill

Move region key

Change region key

Show region contours

Change region contours

Output region contours


www.cadfamily.com

384 Edit Grid GRID Reference ManualEdit properties P.3.8.5

Edit properties P.3.8.5

Edt property

PurposeDefine properties for the grid.

DescriptionThe “Edt property” option displays the following menu:


The maximum number of different property arrays which may be set up for each grid depends on a program parameter (MXPRP). This is usually set to 50.

The user is prompted for the name of the property array to be edited and the units associated with the property. The units which are currently valid may be listed by typing H in response to the unit prompt. If the property does not already exist a new one can be created. All cells will be given a property value of -1.0E20 when a new property is created. This means that any undefined properties which are output will be written as ******** and can be identified easily in the data file.

Note New property names are checked for invalid characters or use of reserved parser keywords in the same way as map names. Additional checks are made for use of the keyword ACTNUM, conflict with existing region names, and special property calculation keywords (e.g. @DX, @TOPS).

A warning will also be issued if the property name corresponds to a keyword from the “Out grid” option (P.3.9.2, see page 408), such as DXV, DEPTH or TRAN. A property can be created with one of these names, but it cannot be written out via “Out grid”.


Option Function

1 Return

2 Def prp lay

3 Def prp are

4 Def prp blk

5 Sho property

6 Inp property

7 Out property

8 Opr property

9 Dsp property

Define property for layer

Define property for area

Define property for blocks

Show property

Input property

Output property

Operate on properties

Display property values


www.cadfamily.com

GRID Reference Manual Edit GridDefine property layer P.3.8.5.2

385

Define property layer P.3.8.5.2

Def prp lay

PurposeDefine a layer of property values.

DescriptionProperty values can be defined for a layer of grid cells. Values may be defined by entering a value, sampling a map, by using the arithmetic/logical parser or by defining a map averaging calculation.

If the parser is used then any property or region number array name may be used as a variable in the formula, as well as ACTNUM and the special names @PORV, @TOPS, etc. (see “Opr property”, P.3.8.5.8, page 391).

If required, values can be copied from another layer of the same grid. E.g. permeability values for layer 2 can be copied by entering the expression ‘= PERMX(2)’.

The map averaging calculations are as described for option P.3.9.6, “Cal ave prps” (see page 422). Note that only the current property can be averaged from here, for the current grid layer only. If a control file is read, defining other properties and layers, these will be ignored.

If a map is to be sampled the a block property can be obtained in one of a number of ways, selected from the following menu:

The “Blk centre” option simply samples the map at the centre of the selected block.

The “Ave corners” option samples the four corners of the grid block and returns the average.

The “Ave cen+crn” option samples the four corners and the centre of the block and returns a centre-weighted average.

The “Ave fne grd” option constructs a fine grid within the grid block, samples at the centre of each fine grid block and returns the average.

The “Blk edge” option samples the map at the centre of a selected edge of the block. This facility allows a series of boundary conditions to be defined. (For example, this might be required in groundwater flow simulation).


Option Function

1 Return

2 Blk centre

3 Ave corners

4 Ave cen+crn

5 Ave fne grd

6 Blk edge

Block centre

Average corners

Average centre+corners

Average fine grid

Block edge


www.cadfamily.com

386 Edit Grid GRID Reference ManualDefine property area P.3.8.5.3

Define property area P.3.8.5.3

Def prp are

PurposeDefine property values for an area of grid cells.

DescriptionThe property values for an area of grid cells can be defined. The area is defined by marking cells on the edge of the area, or by specifying a box within a range of rows and columns, or by selecting a grid region number. The area can be any shape and will be closed automatically.

Sampled block values can be obtained by any one of the methods described for the “Def prp lay” option (P.3.8.5.2, see page 385).

The @FILL function fills in NULL property values, using the same interpolation algorithm as the FILL program; see "FILL Reference Manual". The algorithm works on all cell blocks in a grid layer, but only property values within the defined area are updated. Therefore, data outside the area may be used to interpolate values inside the area.

The @FILL_A function works in the same way as the @FILL function, but the interpolation algorithm only sees the data within the defined area. Data outside this area have no effect on the result.


www.cadfamily.com

GRID Reference Manual Edit GridDefine property blocks P.3.8.5.4

387

Define property blocks P.3.8.5.4

Def prp blk

PurposeDefine property values for individual grid cells.

DescriptionThe user is prompted for the property value to be set and asked to select the cells required. All selected cells will then be set accordingly until a new option is selected or this option selected again.


www.cadfamily.com

388 Edit Grid GRID Reference ManualShow property P.3.8.5.5

Show property P.3.8.5.5

Sho property

PurposeShow the property value for a grid cell.

DescriptionAs each cell is selected it is highlighted and a message given at the bottom of the screen showing its property value.


www.cadfamily.com

GRID Reference Manual Edit GridInput property P.3.8.5.6

389

Input property P.3.8.5.6

Inp property

PurposeRead property values from a user file.

DescriptionA property can be read from:

a A user data file.

b An ECLIPSE INIT file, or

c An ECLIPSE RESTART file.

This allows an array of solution values at a given timestep to be loaded as a property.

The user is prompted for the name of the file to be read and whether it is formatted. If the file exists, it is read until the required property is found. If the grid contains LGRs, the user can choose to load data for all grids or for the current grid only (global or LGR). If the current grid is an LGR and input is from a user data file, the user can also choose whether to identify the LGR in the file or read the first array found with the required property name.

For a user data file, property values are expected with column value increasing fastest, then row value, then layer value. The property value array must be complete for the current grid.

A formatted user data file should have a layout as for the .GRDECL file written by the “Out property” option (P.3.8.5.7, page 390) or the “Out grid” option (P.3.9.2, page 408). Repeated values can be handled in the same way as for ECLIPSE input, e.g. 5*0.7 for 5 cells with property value 0.7. If the array contains too many or too few values, a warning is given, e.g.

The default is to abandon input, but if the user chooses to continue, the data will be loaded into the grid, with any missing values set to zero. If the number of values in the array is less than the total, but equal to the number of active cells, the input values will be stored for active cells only.

A property can also be read from a binary data file (.GRDBIN) as produced by the BINARY option in “Out grid” (P.3.9.2). This file type is selected by choosing the file type as (a) and requesting input as unformatted.

For input from an INIT or RESTART file, only properties for active cells will be input (except for the pore volume array PORV, which should be defined for all cells). Property values will not be modified for inactive cells.

Note A GRDECL file written by “Out property” (P.3.8.5.7) will not contain any CARFIN, RADFIN or REFINE keywords to identify LGRs. For this type of input, the user should choose to load data for the current grid only and read the first suitable property array found.

PORO array contains insufficient values. Continue ? (y/N)


www.cadfamily.com

390 Edit Grid GRID Reference ManualOutput property P.3.8.5.7

Output property P.3.8.5.7

Out property

PurposeWrite property values to a user file.

DescriptionThe property value array can be output to a file in a format suitable for input to a reservoir simulator. Output is written to a file with extension .GRDECL (or .GEC if 3-character extensions are used). The file will be opened if it has not already been opened, otherwise output will be added to existing output. If the file already exists, the user is asked whether to overwrite it.

The array is written out headed by the name of the property value with column values increasing fastest, then row values, then layer values.

For example for a 4x5x2 grid:

TOPS 6957.0293 6827.7383 6885.4526 6987.0996 6891.6362 6862.9048 6891.3120 6896.3525 6912.6079 6889.0908 6902.5703 6956.3691 6947.5122 6916.7280 6926.2529 6977.3535 7035.0859 6980.2202 6981.8228 7032.41947504.5581 7454.9375 7287.3545 7101.0884 7453.7114 7353.6958 7171.1694 6960.6465 7418.3066 7299.6733 7150.3345 6956.4429 7415.0659 7305.6895 7194.7832 7035.1997 7445.7651 7362.5664 7254.5601 7157.6382/


www.cadfamily.com

GRID Reference Manual Edit GridOperate on properties P.3.8.5.8

391

Operate on properties P.3.8.5.8

Opr property

PurposeOperate on the property array.

DescriptionThis option allows the user to operate on the entire array (rather than just a single layer). The arithmetic/logical parser may be used to give formulae which involve property or region number arrays. Note that the keyword NULL can be used to refer to null values in a calculation. The keyword ACTNUM can be used to check whether a cell is active.

The following special names can be used in calculations:

The program will automatically obtain the corresponding value for each cell. Note that @PORV returns the pore volume in cubic metres and @PORV_RB, @PORV_FT, @PORV_M return the pore volume in reservoir barrels, cubic feet or cubic metres respectively. The other special values are computed in appropriate units for the current grid. If the grid is non-radial, null values are returned for @DR and @DTHETA. If it is radial, @DX and @DY are returned as null.

The @FILL function fills in NULL property values using the same interpolation algorithm as the FILL program. It interpolates values in a layer, along the grid rows and columns, by using an inverse distance weighted average; see the "FILL Reference Manual". Distances are measured horizontally, any slope or distortion in the layer being ignored. FILL calculates distances based on the top layer of the grid, whereas GRID calculates the horizontal distance between the cell centres in the layer. Therefore, the two programs will give different answers if these distances are different (e.g. if the grid contains coordinate lines that are inclined at more than one angle.)

The @FILL_A function works in the same way as the @FILL function, and gives the same results as @FILL when used from this option or the "Def prp lay" option, P.3.8.5.2 (page 385). However, when used from the "Def prp are" option, P.3.8.5.3 (page 386), the interpolation algorithm only uses data within a defined area of the grid.

@FILL_L copies properties from a parent grid to a grid refinement. The LGR should be selected before the @FILL_L operation is performed. It has no effect on the global grid. If LGR properties are not defined then ECLIPSE uses the host cell properties, so it is not necessary to use @FILL_L. However the operation is useful for defining LGR properties so they can be subsequently modified.

To operate on a property for a single layer, see option P.3.8.5.2, “Def prp lay”.

@DX @DY @DZ @DR @DTHETA @TOPS

@DEPTH @PORV @PORV_RB @PORV_FT @PORV_M

@FILL @FILL_A @FILL_L


www.cadfamily.com

392 Edit Grid GRID Reference ManualDisplay property values P.3.8.5.9

Display property values P.3.8.5.9

Dsp property

PurposeChange property value display.


The “Return” option returns the user to the “Edt property” menu. Option 3 is described in the “Smp contour” section, P.2.4.9.8.3 (page 134 and following). The other options are described in the following sections.


Option Function

1 Return

2 Sho prp fll

3 Chg prp fll

4 Mov prp key

5 Chg prp key

6 Sho prp cnts

7 Chg prp cnts

8 Out prp cnts

Show property fill

Change property fill

Move property key

Change property key

Show property contours

Change property contours

Output property contours


www.cadfamily.com

GRID Reference Manual Edit GridShow property fill P.3.8.5.9.2

393

Show property fill P.3.8.5.9.2

Sho prp fil

PurposeShow properties with colour fill.

DescriptionEach grid block will be colour filled according to its property value (or region number).

When the blocks are colour filled, reselection of this option removes the colour fill. Colour fill will be removed automatically when the “Edt property” or “Edt regions” menu is exited.


www.cadfamily.com

394 Edit Grid GRID Reference ManualMove property key P.3.8.5.9.4

Move property key P.3.8.5.9.4

Mov prp key

PurposeMove property key.

DescriptionThe key display for property value or region number colour fill can be placed anywhere on the screen. The key is moved by selecting one of the corners of the key area and selecting its new location. The area obscured by the key area is not redrawn by default but can be redrawn using the “Refresh” option on the “Display” menu.


www.cadfamily.com

GRID Reference Manual Edit GridChange property key P.3.8.5.9.5

395

Change property key P.3.8.5.9.5

Chg prp key

PurposeChange key for properties or region numbers.

DescriptionThe following options are available for changing the key:

Each options 2 and 3 leads to a further menu for setting Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current grid display will be replaced by a summary of the current default Granite attributes for the key text or background. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.

Option 4 allows the number of decimal places shown on the key to be changed.

Table 6.9 Menu P.3.8.5.9.5

Option Function

1 Return

2 Chg key txt

3 Chg key bck

4 Chg num dec

Change key text representation

Change key background



www.cadfamily.com

396 Edit Grid GRID Reference ManualShow property contours P.3.8.5.9.6

Show property contours P.3.8.5.9.6

Sho prp cnts

PurposeContour back property array.

DescriptionThe property array can be contoured back at any desired contour interval and contour quality, with optional colour fill. The grid block values are used as the basis for contouring, and values set at the edges of the grid equal to the value of the block. Contours will therefore intersect the grid edges at right angles, provided contour quality 1 is used. Higher qualities will result in much smoother contours but will tend to overshoot at the edges.

Contouring back-sampled data is much more effective than block filling for identifying areas where more work may be required.

If contours are already drawn, reselection of this option removes them. Contours will be removed automatically when the “Edt property” or “Edt regions” menu is exited.

Note that LGR contours are only drawn when LGRs are displayed. The contours drawn for LGR blocks when the coarse grid is displayed are the contours for the coarse grid cell values.


www.cadfamily.com

GRID Reference Manual Edit GridEdit fluids-in-place P.3.8.6

397

Edit fluids-in-place P.3.8.6

Edt FIP

PurposeCalculate rock and fluid volumes for grid.

DescriptionThe “Edit FIP” option displays the following menu:

Fluids-in-place will be calculated according to the property arrays which have been defined. The program searches for the following property names: SOIL, SWAT, SGAS, RS and RV. Fluids-in-place are calculated using a pore volume array and the solution arrays found.

The user is prompted for the formation volume factors to be applied for each phase present:

• If SOIL or RV is found an oil formation volume factor is requested.

• If SGAS or RS is found a gas formation volume factor is requested.

• If SWAT is found a water formation volume factor is requested.

Fluids-in-place arrays are set up for each of the phases present, with the names FIP-OIL, FIP-WAT, FIP-GAS, FIP-DGAS (dissolved gas) and FIP-VOIL (vaporized oil) as appropriate. The data stored in these arrays is not saved by the program and will be lost when the menu is exited unless output to a data file.

A pore volume array will also be calculated. This array is calculated by computing the bulk volumes of each cell and then multiplying by a porosity (or PORO) array, if it exists, and by an NTG array, if it exists, to give the final result. (Note that the pore volume of inactive cells is set to zero.)

Fluids-in-place can calculated for designated areas of the grid by defining a FIPNUM region number array. Fluids-in-place for individual FIPNUM regions are reported separately.

The “Return” option returns the user to the “Edt blocks” menu options. All calculated data are discarded when the “Return” option is taken.

Note that the accuracy of the fluids-in-place calculated by this option depends on the sizes of grid blocks defined for the simulation grid. Volumetrics based on fine map meshes can be calculated using the ECLMAP options.


Option Function

1 Return

2 Cal FIP

3 Sho FIP

4 Out FIP

Calculate fluids-in-place

Show fluids-in-place

Output fluids-in-place


www.cadfamily.com

398 Edit Grid GRID Reference ManualCalculate fluids-in-place P.3.8.6.2

Calculate fluids-in-place P.3.8.6.2

Cal FIP

PurposeCalculate rock and fluid-in-place volumes for the grid.

DescriptionThe pore volume for each grid block is calculated, then the fluid volumes for each phase present. It is assumed that the fluid is evenly distributed throughout the grid blocks. Only active grid blocks are included in the calculation.

Pore volume is calculated as:

where:

Rock volumes are calculated from the corner point geometry of each cell using the same methods as ECLIPSE

POROSITY and NTG (net-to-gross) arrays are property arrays that have been defined previously for the grid.

For each phase, fluid-in-place is calculated as:

where:

S is the saturation for the appropriate phase

B is the formation volume factor for the appropriate phase.

In addition, dissolved gas is calculated by RS*FIP(oil) and vaporized oil by RV*FIP(gas). The effects of rock compressibility are ignored.

PORV = Rock volume * POROSITY * NTG

FIP = ( S / B ) * PORV


www.cadfamily.com

GRID Reference Manual Edit GridShow fluids-in-place P.3.8.6.3

399

Show fluids-in-place P.3.8.6.3

Sho FIP

PurposeShow rock and fluid volumes for grid blocks.

DescriptionThe pore volume and fluid-in-place for selected grid blocks is displayed at the bottom of the screen.


www.cadfamily.com

400 Edit Grid GRID Reference ManualOutput fluids-in-place P.3.8.6.4

Output fluids-in-place P.3.8.6.4

Out FIP

PurposeOutput rock and fluid volumes for grid blocks.

DescriptionThe pore volume and fluid-in-place arrays will be output to a user file. In addition, a summary will be produced, giving the fluid totals in regions defined by a FIPNUM region array, together with the total fluids-in-place. (Only active cells will be included in the calculation.)


www.cadfamily.com

GRID Reference Manual Edit GridDelete regions P.3.8.7

401

Delete regions P.3.8.7

Del regions

PurposeDelete a region number array.

DescriptionThe user is prompted for the name of the region number array to be deleted. Confirmation for deletion of the array is required. The array name will be removed from the list of available arrays.


www.cadfamily.com

402 Edit Grid GRID Reference ManualDelete property P.3.8.8

Delete property P.3.8.8

Del property

PurposeDelete a property array.

DescriptionThe user is prompted for the name of the property array to be deleted. Confirmation for deletion of the array is required. The array name will be removed from the list of available arrays.


www.cadfamily.com

GRID Reference Manual Edit GridCoarsen grid P.3.8.9

403

Coarsen grid P.3.8.9

Crs grid

PurposeLocal grid coarsening options.

DescriptionThe “Crs grid” option displays the following menu:

The local grid coarsening option allows areas of the grid to be blocked together for use with the ECLIPSE local grid coarsening facility.

When the grid geometry and associated parameters are output, local grid coarsening keywords can be generated for the coarsened areas.

Coarsened areas of the grid are displayed with no separating grid lines, although the outer lines of the coarsened cells follow the geometry of the non-coarsened cells rather than being replaced by a single straight line.

Except for the display of the coarse grid, cells within coarsened areas are not treated differently from any other cells. For example, if a map is sampled onto a grid, all the cells within the coarsened region will be sampled as usual.



Option Function

1 Return

2 Cre coarse

3 Del coarse

4 Inp coarse

Create grid coarsening

Delete grid coarsening

Input grid coarsening


www.cadfamily.com

404 Edit Grid GRID Reference ManualCreate grid coarsening P.3.8.9.2

Create grid coarsening P.3.8.9.2

Cre coarse

PurposeCreate a grid coarsening.

DescriptionThe user is asked to select the area of the grid to be coarsened.

Two points are marked and the smallest grid area which contains both points is highlighted.

The user will then be asked the range of layer numbers to be coarsened.

The coarsened area of the grid will then be drawn with no intermediate grid lines (except for fault tick marks).


www.cadfamily.com

GRID Reference Manual Edit GridDelete grid coarsening P.3.8.9.3

405

Delete grid coarsening P.3.8.9.3

Del coarse

PurposeDelete grid coarsening.

DescriptionThe user is asked to select the local grid coarsening to be deleted by placing the cursor in a block of the coarsened area. The area will be highlighted and the user asked to confirm that the coarsening is to be removed.


www.cadfamily.com

406 Edit Grid GRID Reference ManualInput grid coarsening P.3.8.9.4

Input grid coarsening P.3.8.9.4

Inp coarse

PurposeRead a coarse grid definition from a file.

DescriptionThis option enables a local grid coarsening to be read from an ECLIPSE keyword file. The user is prompted for the name of the file to be read. The given file is searched for COARSEN keywords.

The COARSEN keywords should be followed by rows of up to 9 numbers as follows:

where

Grid coarsenings will be created for each volume of cells specified, provided these do not overlap and are not adjacent to local grid refinements. The number of columns, rows and layers may be omitted, in which case they will be defaulted to 1. The number of columns, rows and layers created must be an exact division of the range of cells to be coarsened.

Note that GRID creates a separate coarsening for each coarsened cell, so that regions for which NC, NR or NL are specified to be greater than one will be output as a series of separate coarsenings.

COARSEN-- IC1 IC2 IR1 IR2 IL2 NC NR NLdata ... /

... //

IC1 is the first column in the volumeIC2 is the last column in the volumeIR1 is the first row in the volumeIR2 is the last row in the volumeIL1 is the first layer in the volumeIL2 is the last layer in the volumeNC is the number of coarse grid columnsNR is the number of coarse grid rowsNL is the number of coarse grid layers


www.cadfamily.com

GRID Reference Manual Edit GridGrid utilities P.3.9

407

Grid utilities P.3.9

Grd utils

PurposeA number of options which apply to the whole grid are collected together under this menu.

DescriptionThe “Grid utilities” option displays the following menu:



Option Function

1 Return

2 Out grid

3 Opr geometry

4 Spt grid

5 Jn grid

6 Cal ave prp

7 Cal trans

8 Grid to maps

Output grid

Operate on grid geometry

Split grid nodes automatically

Rejoin split grid nodes

Calculate properties by map averaging

Calculate pore volumes and transmissibilities

Convert grid data to map data


www.cadfamily.com

408 Edit Grid GRID Reference ManualOutput grid P.3.9.2

Output grid P.3.9.2

Out grid

PurposeOutput the grid in the form of keywords for use by ECLIPSE or other reservoir simulators.

DescriptionThe grid can be output to a file in a format suitable for input to a reservoir simulator. Output is written to a file with extension .GRDECL (or .GEC if 3-character extensions are used). The file will be opened if it has not already been opened, otherwise output will be added to existing output. If the file already exists, the user is asked whether to overwrite it. On exit from this option, the file may be closed immediately, or left open for further output.

The user is prompted for a list of keywords to be output. If the letter ‘H’ is typed in response to the keyword prompt a list of the available keywords is given.

Available grid definition keywords include:

Miscellaneous keywords:

COORD, ZCORN (for corner point geometry)TOPS, DXV, DYV, DX, DY, DZ (for block centre geometry)ACTNUM (active cell numbers)COARSEN (local grid coarsening)SPECGRID, TOPSNODE, (for use in FILL)DZCORN, ZNODE, DZNODE (for use in FILL)NXFIN,NYFIN,NZFIN (local grid refinement)HXFIN,HYFIN, HZFIN (local grid refinement)HRFIN,INRAD (radial LGRs)

BOX The user is prompted for the box of cells to be written.ENDBOX Adds ENDBOX keyword after global data.TRAN Outputs transmissibilities between neighboring and non-neighboring blocks

output is TRANX, TRANY, TRANZ, NNC and PORV.EGRID Outputs a full ECLIPSE .EGRID extensible grid file.GRID Outputs a full ECLIPSE .GRID file.DEPTH Outputs block centre depths.WELLS Outputs the block numbers for well locations on a map.WELSPECS Outputs skeleton well specification data for wells on a map FAULTS Outputs fault segment dataBINARY Outputs ECLIPSE GRID section keywords to binary fileACRES Outputs data in form suitable for ACRES inputCFEST Outputs data in form suitable for CFEST input


www.cadfamily.com

GRID Reference Manual Edit GridOutput grid P.3.9.2

409

In addition any region number or property array can be output. Comments may be entered by starting a line with --

The list can be ended by just entering a carriage return in response to the prompt. Up to 250 keywords can be output at one time.

The user is prompted for the output units for lengths. Areal dimensions or depth dimensions will be scaled to the given units. Note that ECLIPSE requires all input to be in the same units.

The user may also select whether to output the grid coordinate axes and grid units (MAPAXES and GRIDUNIT keywords). The data associated with these keywords can be used to position the grid correctly if it is later reloaded into a GRID model via option P.3.0.6, “Input grid” (page 292).

All the selected keywords will be written to the output file in the order given. If locally refined grids are defined, the following output options will be offered:

If option S is chosen, further prompts will be issued for the user to choose whether to output data for the global grid and for each local grid.

If the grid contains nested LGRs (i.e. refinements within refinements) the program asks the user to choose whether they should be output in ECLIPSE 300 format (see the "ECLIPSE Reference Manual", CARFIN and RADFIN):

Note that if keywords DX, DY, DZ, DXV or DYV are selected for block-centred geometry, the sizes of any local grid cells will be rescaled if necessary to fit in the host cells. This will avoid error messages from ECLIPSE which might occur in cases where the host cells are not exactly rectangular. Use of block-centred output for irregular grids is not recommended.

If the TRAN keyword is selected, then transmissibilities TRANX, TRANY and TRANZ are calculated together with transmissibilities between non-neighbour cells due to faulting. The transmissibility calculation is the same as used with the NEWTRAN keyword in ECLIPSE. Transmissibilities can only be generated if property arrays have been set up with the names POROSITY, PERMX, PERMY and PERMZ. In addition, the calculation will look for property arrays NTG, MULTX, MULTY and MULTZ and use them in the calculation if they are found.

Notes• As keywords are output in the order they are requested, the SPECGRID keyword should be

selected before the COORD and ZCORN keywords, if the file is to be used with the FILL program (or loaded back into GRID). The SPECGRID keyword is not necessary for normal input to ECLIPSE, as dimensions should be specified in the RUNSPEC section.

If BOX limits are defined for the global grid, the user will be offered the option to adjust the dimensions written with the SPECGRID keyword to allow for the box limits:

CHEARS Outputs data in form suitable for CHEARS inputVIP Outputs data in form suitable for VIP input

A - Write all data, G - Global grid onlyL - Write all LGRs, S - Select required grids

Output nested LGRs in Eclipse 300 format ? (Y/n)

Change SPECGRID dimensions to BOX size? (y/N)


www.cadfamily.com


The default response is ‘No’ if the BOX keyword has been output, ‘Yes’ otherwise.

• Skeleton WELSPECS data can be output here, using well positions from a map. To process well connection data and output COMPDAT keywords defining connection positions, see Well data menu P.6.6 (page 524).

• If the FAULTS keyword is entered, a list of fault segments will be generated for use with the ECLIPSE keyword MULTFLT.

GRID uses two methods to identify which segments belong to which fault. In the first method GRID attempts to match grid faults with map faults. The user is asked to specify a map, a map stratum, and a grid layer. Grid faults that match a map fault are given the same name as the map fault.

GRID uses the second method if no map has been specified and for any grid faults that have not been matched. In this method GRID concatenates neighboring split nodes to form a fault. New faults are started whenever GRID finds a gap between split nodes and, optionally, whenever the fault throw direction changes. The user is asked to confirm this option. Fault names are constructed in the form 'FLT-nn' where nn is a counter, and are not related to the fault names on any maps.

If a grid fault has been moved or extended beyond the original map fault then GRID may not identify it properly. GRID may also have difficulty if there are several map faults close together. It is therefore recommended that the FAULTS output is carefully checked. If GRID does have problems identifying the grid faults, or if no suitable map exists, then a new map can be created and faults copied from the grid to the map. The run file FAULTS.RF provided with the example model SNARK illustrates this.

• If BINARY is entered, any ECLIPSE GRID section keywords (except FAULTS and COARSEN) will be written to a special unformatted file with suffix .GRDBIN. The .GRDECL file will also be created, with comments indicating which keywords have been written to the binary file. Keywords for other sections (EDIT, REGIONS and SCHEDULE) and any other keywords which are not yet available in binary form, will be written to the .GRDECL file as usual.

A binary file created in this way is intended to be read by ECLIPSE, using a command of the form

Note that this file type is intended simply to provide savings in time and storage space for users creating large simulation models. It is not equivalent to the ECLIPSE .INIT file.

• If ACRES is entered, data suitable for input to the Acres simulator from ARCO will be generated. Output is to a file with suffix .GRDACR. The following Acres keywords can be used:

Block centred geometry data:

DX, DY, DZ

HTOP, HMID, HBTM

FAULT

Corner point geometry data:

XYZCORNERS

IMPORT ‘MYFILE.GRDBIN’ /

NXNYNZ Outputs NX NY NZ and REFINE data


www.cadfamily.com


411

Block centred geometry keywords and corner point geometry keywords cannot be mixed. Corner point geometry data will be output using map axes.

Properties and regions can be output by entering the property or region name. The following property names will be translated:

The following region names will be translated:

For all other properties and regions, the Acres keyword will be the same as the property or region name.

Miscellaneous keywords

Comments can be entered by starting a line with ’;’ or ’--’.

• If CHEARS is entered, data suitable for input to Chevron’s CHEARS simulator will be generated. Output is to a file with suffix .GRDCHE. The following CHEARS data can be generated:

MODELSIZE

Local grid definition data (GRIDDEF etc.)

Grid structure data

DX, DY, DXA, DYA, GROSS, TDEPTH, NET

GRID property Acres Keyword

PORO POR

NTG NET/GROSS

GRID region Acres Keyword

EQLNUM EQLGROUP

FIPNUM VOLREGION

PVTNUM PVTGROUP

SATNUM SATGROUP

ACTNUM Outputs POR multiplier to define active and inactive cellsBOX Outputs data from a box in the global gridGRID Outputs ECLIPSE GRID file


www.cadfamily.com


Miscellaneous keywords

Property and region data (according to what is defined for the current grid).

Comments can be entered by starting a line with ‘*’ or ‘--’.

The user can select keywords using either the ECLIPSE or CHEARS mnemonics. ECLIPSE keywords will be translated to CHEARS names where possible. If a property is requested which does not have a known CHEARS name, the user will be prompted for a mnemonic. The output data will be sorted to group keywords in the appropriate CHEARS input data sections if necessary.

Note that the keywords DX and DY in CHEARS correspond to the ECLIPSE keywords DXV and DYV, while the CHEARS keywords DXA and DYA correspond to ECLIPSE keywords DX and DY. If the user enters either DX or DY a further prompt is issued, to check the actual CHEARS keyword required. The recommended selection is DXA or DYA, to obtain a full array of values instead of just a vector.

The keyword TDEPTH in CHEARS is equivalent to TOPS in ECLIPSE. There is no CHEARS keyword corresponding to the ECLIPSE DEPTH array. The keyword NET is used for net thickness, instead of defining NTG. If NET is requested it will be taken from the property NET or DZNET (if available), otherwise GRID will compute net thickness using NTG.

After CHEARS has been selected from within “Out grid”, the CHEARS output style will be retained until the user reenters “Out grid” and switches it off (in response to a prompt from the program). This will allow CHEARS-compatible output from “Out property”, for example.

• If VIP is entered then output suitable for input to the VIP-CORE initialization module can be generated. Output is to a file with suffix .VIP. The heading ‘ARRAYS’ will be written to the file automatically when it is opened. The following VIP keywords can be output:

BOX Outputs only a box of dataENDBOX Ends box limits on outputMTBRDEF Defines material balance regions, using FIPNUM or multiple

grid regionsACTNUM Outputs POROSITY multiplier to define active and inactive

cellsTRAN Outputs pore volumes and transmissibilities between

neighboring and non-neighboring blocksGRID Outputs ECLIPSE GRID file

SPECGRID Output as NX NY NZ COMPXCORN, YCORN, ZCORN

(ZCORNW, ZCORSE, ZCORSW are automatically output if the grid contains split nodes)

CORP Corner point geometry array with eight X,Y,Z values for each grid block (use instead of XCORN, etc.)

DEPTH, MDEPTH, DZCORN, DX, DY, DZBOX The user is prompted for the box of cells to be written (output as

comments)


www.cadfamily.com


413

In addition, any property or region number arrays may be output. If a property array is requested, the user can optionally change the keyword name for the array. If a region number is output, the keyword name IREGION will be used. No locally refined grids will be output when VIP type output is requested.

• If CFEST is entered, GRID will prompt for the node numbering increment to be used.

• If MAP units are chosen for grid output, the X,Y positions of the grid nodes will be given in map units (usually metres) relative to the model origin. Depths will be converted to the same units used for map distances.

An option to output the grid coordinates in units ‘MAPFT’ is available. The grid node positions will be exported in feet, but with the X,Y values calculated relative to the model origin instead of the grid origin. Note that this method is not recommended for general use, as UTM values will require 8 significant figures when converted to feet, leading to loss of accuracy.

• The output box limits defined by the BOX keyword refer to the global grid. If box limits are defined for a global grid containing LGRs, only LGRs containing cells within those limits can be exported. The box limits used for output will be the last box defined before output begins (i.e. only one set of box limits can be used for each “Out grid” command and repeating the BOX keyword will change the limits for all keywords).

If the user enters the keyword ENDBOX, this keyword will be written at the end of the global data and the box will be turned off on exit. Otherwise, if the current output file is kept open, the user can choose to save the box limits for further use.

• If LGR data are output, the user can choose whether to use CARFIN/RADFIN or REFINE keywords for LGR identification. Note that CARFIN or RADFIN must be used to define an LGR, but REFINE can be used to introduce additional data arrays after the first definition in an ECLIPSE input file. (See the "ECLIPSE Reference Manual" and "ECLIPSE Technical Description" for further information.)

TRAN Outputs transmissibilities between neighboring blocks, output is TX, TY, TZ

WELLS Outputs the block numbers for well locations on a map


www.cadfamily.com

414 Edit Grid GRID Reference ManualOperate on grid geometry P.3.9.3

Operate on grid geometry P.3.9.3

Opr geometry

PurposeOptions to move the grid origin, relocate, rotate and scale the grid, are provided under this menu, together with an option to reorder the grid block numbers.

DescriptionThe “Opr geometry” option displays the following menu:

The “Return” option returns the user to the “Grid utils” menu. Each of the other options is described in the following sections.


Option Function

1 Return

2 Mov origin

3 Rel grid

4 Rot grid

5 Scl grid

6 Order grid

Move origin

Relocate grid

Rotate grid

Scale grid

Order grid blocks


www.cadfamily.com

GRID Reference Manual Edit GridMove origin P.3.9.3.2

415

Move origin P.3.9.3.2

Mov origin

PurposeMove the grid origin.

DescriptionThe current grid coordinate system is redefined.

The origin may be optionally placed at the top left corner of grid cell 1, 1 with the x-axis along the top grid row.

If the above option is not taken, the user is asked to mark or enter at the keyboard a new origin and a point in the new x-direction. The user has the choice of defining a coordinate system with the y-axis increasing down or up the screen. It is normal for the origin to be placed near the top, left corner of the map with the y-axis downwards.

The coordinates of all the points in the grid are transformed to the new coordinate system. The grid itself is not moved relative to the map.


www.cadfamily.com

416 Edit Grid GRID Reference ManualRelocate grid P.3.9.3.3

Relocate grid P.3.9.3.3

Rel grid

PurposeMove the entire grid.

DescriptionA node is selected to be moved and a new location for the node marked. The whole grid is then moved parallel to the x and y axes to bring the selected node to the new point.


www.cadfamily.com

GRID Reference Manual Edit GridRotate grid P.3.9.3.4

417

Rotate grid P.3.9.3.4

Rot grid

PurposeRotate the entire grid.

DescriptionA node is selected around which to pivot the grid. The angle of rotation can be entered in degrees, anti-clockwise, or a second node can be selected and moved. In this case the grid will be rotated about the pivot node so that the second node lies along the line from the pivot to the new point.


www.cadfamily.com

418 Edit Grid GRID Reference ManualScale grid P.3.9.3.5

Scale grid P.3.9.3.5

Scl grid

PurposeScale the entire grid.

DescriptionThe user is prompted for the scale factors in the x, y and z directions. All grid coordinates will be re-scaled from the grid origin. This option may be useful if old grids have been read in with units which are different from those used on new maps that are to be sampled.


www.cadfamily.com

GRID Reference Manual Edit GridOrder grid blocks P.3.9.3.6

419

Order grid blocks P.3.9.3.6

Order grid

PurposeAllows user to define the I,J,K order and renumber the grid blocks.

DescriptionBy default, simulation grids used in GRID and ECLIPSE are created with the XY origin at the top left corner (when viewing the top plane in 2D) and with depths increasing downwards. The I, J, K numbering of the grid blocks follows the XYZ axes. However, GRID has the flexibility to allow users to create grids which do not use this convention, and grids created by third-party packages may be based on a different coordinate scheme. This option allows the user to convert grids to the standard numbering method, or to change the coordinate scheme ready for export to another system.

This option can only be used with an XY display of the grid. The user is prompted to mark the grid I, J origin, block (1, 1) and then the direction of increasing I, e.g. block (2, 1). The selected points are adjusted so that the origin is at a corner of the grid. The resulting I,J directions are marked and the operation can be abandoned at the next prompt: ‘Reorder blocks with I,J as shown ?’ The user can also choose to reorder blocks in the K-direction.

Notes• This option does not modify the grid origin or axes.

These can be changed using option P.3.9.3.2, “Mov origin” (page 415). Note that it may be necessary to change the axes before displaying an XZ or YZ view of the reordered grid, although it is not essential to align the X and Y axes precisely with the I and J directions.

• Care must be taken if a grid contains radial LGRs, as some I,J,K numbering schemes will cause the theta-direction to change from anticlockwise to clockwise. A warning will be issued if the radial theta-direction is affected.

• In general, the recommended practice is to work with grids which are ordered using the standard GRID numbering method. For example, use of grids with the K-direction inverted may lead to problems with cross-section views, etc. Users working with third-party software can use this option to reorder their grids after importing them to GRID and to renumber grid blocks before export if necessary.


www.cadfamily.com

420 Edit Grid GRID Reference ManualSplit grid P.3.9.4

Split grid P.3.9.4

Spt grid

PurposeSplit grid nodes automatically.

DescriptionThis facility lets GRID define split nodes automatically by following the fault lines defined on a map. When this option is taken the user will be prompted for the map to be used.

The user can choose whether to split nodes over the entire grid or within a selected area. The area is defined by marking nodes around its boundary, or by a box within a selected range of rows and columns, or by a grid region, as for "Def prp are" P.3.8.5.3, page 386. The range of grid layers for splitting can be selected to include all layers in the grid, or may be restricted by the user.

The algorithm works by following the major segments of each fault trace in turn. The nearest grid node to each data point of the fault segment is found and a split node is defined as the trace is followed from one grid node to the next. If two data points are separated by a distance greater than the grid node spacing, the trace will be followed through the grid by zig-zagging along the fault lines until the node is reached.

Since this is very much a ‘black box’ approach to node splitting, it is recommended that the nodes that have been split are checked carefully by the user. Some spurious nodes may be split at the edges of the grid and the user should take the time to tidy these up.

(Note that the algorithm used to find points for sampling at split nodes does not require nodes to lie exactly along fault traces.)


www.cadfamily.com

GRID Reference Manual Edit GridRejoin split grid nodes P.3.9.5

421

Rejoin split grid nodes P.3.9.5

Jn grid

PurposeJoin grid nodes automatically.

DescriptionThis facility lets GRID rejoin split nodes automatically. The user can choose whether to join nodes over the entire grid or within a selected area. The area is defined by marking nodes around its boundary, or by a box within a selected range of rows and columns, or by a grid region, as for "Def prp are" P.3.8.5.3 (page 386). The range of grid layers for joining can be selected to include all layers in the grid, or may be restricted by the user.

This operation affects vertical splits, used to represent faults, not gaps between grid layers.

See also option P.3.5.8 "Jn nodes" (page 334) which allows the user to select nodes to be rejoined (e.g. along a line corresponding to a particular fault).


www.cadfamily.com

422 Edit Grid GRID Reference ManualCalculate properties by map averaging P.3.9.6

Calculate properties by map averaging P.3.9.6

Cal ave prps

PurposeCalculate values for multiple properties for one or more grid layers, by sampling and averaging maps.

DescriptionThis option provides facilities for sampling detailed maps onto a fine grid and averaging the results to obtain upscaled values for coarse grid blocks. It can also be used for calculating multiple properties for several grid layers, by straightforward sampling at coarse grid block centres. A command file can be used to define the relationships between grid layers and map strata, and the calculations to be performed.

The user can choose whether to calculate the properties over the entire grid or within a selected area. The area is defined by marking nodes around its boundary, or by a box within a selected range of rows and columns, or by a grid region, as for “Def prp are” P.3.8.5.3 (see page 386). The range of grid layers for calculation can be selected to include all layers in the grid, or may be restricted by the user.

The parameters controlling the sampling and averaging operations may be defined by reading an external control file or edited interactively. The following information is required:

• Fine grid subdivisions

The fine grid for sampling can be constructed by subdividing each grid block in the I and J directions according to the minimum number of fine cells specified and the maximum fine cell width. Alternatively, fine mesh subdivisions can be used, based on the node positions for a specified mesh map. This method identifies the mesh nodes in each grid block and operates directly on the node values instead of resampling the map.

In the K direction, the number of subdivisions per grid layer will be determined by the number of map strata corresponding to each layer. If required, the user can specify a thickness map name for constructing the fine layers. Otherwise, equal layer subdivisions will be used.

The fine grid subdivisions can be specified in the control file using a command of the form:

For mesh map subdivisions, the command is of the form:

• Relationships between grid layers and map strata

If grid layers do not correspond exactly to map strata, the user must define the map strata corresponding to each grid layer in the selected range. The control file commands are of the form:

FINEGRID SUBDIVISIONS n MAXWIDTH w THICKNESS mapname

FINEGRID MESHMAP mapname1 THICKNESS mapname2

GRIDLAYER n STRATA s1 s2 s3


www.cadfamily.com

GRID Reference Manual Edit GridCalculate properties by map averaging P.3.9.6

423

or:

If the grid layer numbers correspond to map strata, this can be specified in the control file by:

• Grid property averaging methods

For each property to be calculated, the user should give:

• Property name

• Units

• Mnemonic for map or calculation

• For each independent direction, the averaging method and map or calculation to be used for weighting.

The control file commands for defining a property are of the form:

where

The property may be an existing or new grid property. If it already exists, the units must be as defined when the property was created.

The FROM mnemonic may be a map name or it may correspond to a CALCULATE expression. The map stratum should not be included, as this will be taken from the GRIDLAYER parameters.

The following directions can be selected using the OVER keyword: I, J, K, IJ, JK, IK, IJK. The OVER keyword may be repeated up to 3 times, to ensure that each of the I, J and K directions is referenced once. The order of processing will correspond to the order in which the OVER keywords are specified.

For example, to compute porosity by weighted averaging, independent of direction, the following command could be used:

GRIDLAYER n STRATA s1 TO s2

GRIDLAYER * STRATA *

GRIDPROPERTY ppp UNITS uuu FROM mmm & OVER dir method WEIGHT www

ppp is the property name.uuu is a valid property unit (e.g. FRACTION).mmm is a mnemonic of up to 8 characters, corresponding to a map name or a

CALCULATE parameter to be used for the property values.dir can be one of I, J, K, IJ, JK, IK, IJK.method is a valid averaging method (see below).www is a mnemonic of up to 8 characters, corresponding to a map name or a

CALCULATE parameter to be used for the weighting function.

GRIDPROPERTY PORO UNITS FRACTION FROM POROSITY & OVER IJK AVERAGE WEIGHT WWW


www.cadfamily.com


To compute permeability by averaging over IK slices and then taking the harmonic average in the J direction, the following command could be used:

The following averaging methods are available:

A weighting function may be specified for the arithmetic averaging, harmonic averaging or geometric averaging options. The WEIGHT may be defined by a map name or a CALCULATE expression.

• Calculations for properties and weights

Any properties or weights which are not defined by sampling single maps must be specified using the CALCULATE keyword. The calculation expression can be any valid arithmetic or logical expression (as used elsewhere in GRID), using constants, NULL and map names. A leading =, + or - sign may be present when using a simple arithmetic expression. The control file format is:

The special keywords @DX, @DY, @DZ may be used to refer to fine cell dimensions. E.g. to define the fine cell volume for use as a weight, the following expression could be used:

The user can choose to save the current set of commands in a control file after the property calculations are complete, or after quitting without performing any calculations. The external control file can then be used as a basis for further property calculations if required.

GRIDPROPERTY PERMY UNITS MDARCY FROM PERM &OVER IK AVERAGE OVER K HARMONIC_AV

• SUM - Summation• AVERAGE - Simple arithmetic average• HARMONIC_AV - Harmonic average• GEOMETRIC_AV - Geometric average• MINIMUM - Use minimum value• MINIMUM - Use maximum value• FREQUENCY - Select data value by frequency count (see

note 4 below).

CALCULATE xxx BY expression

CALCULATE VOLUME BY @DX * @DY * @DZ


www.cadfamily.com

GRID Reference Manual Edit GridCalculate properties by map averaging P.3.9.6

425

Example control file

Notes• To display or edit a single property, use menu P.3.8.5 (“Edt property”, see page 384).

Map averaging may also be selected when calculating a single property for the current grid layer, using option P.3.8.5.2 (“Def prp lay”, see page 385) or P.3.8.5.3 (“Def prp are”, see page 386).

• Setting the number of fine grid subdivisions to 1 and specifying only one map stratum per grid layer will give results equivalent to sampling properties from single maps at grid block centres.

• Weighted averages are calculated as follows:

AVERAGE:

[EQ 6.1]

HARMONIC_AV:

[EQ 6.2]

GEOMETRIC_AV:

[EQ 6.3]

• The FREQUENCY option can be applied to data which can be treated as integer-valued or to real numbers divided into intervals with a specified spacing. The grid block value is set to the integer value (or the upper limit of the interval) which occurs most frequently. If equal counts occur, the lowest numerical value will be selected.

For example, this method could be used to select facies types according to permeability ranges, when upscaling from fine mesh maps. The resulting property could then be used in an operation to define SATNUM regions. (See menu option P.3.8.4.8, “Opr region”, page 382.)

-- Simulation grid property averaging from map data-- GRID Version CUR Date: 24/08/93 Time: 11:08:53-- Fine grid subdivisions

FINEGRID SUBDIVISIONS 2 MAXWIDTH 100.0 THICKNESS DZ-- Relationships between grid layers and map strata

GRIDLAYER 1 STRATA 1 2GRIDLAYER 2 STRATA 3 4

-- Grid property averaging methodsGRIDPROPERTY PORO UNITS FRACTION FROM PORO &

OVER IJK AVERAGE WEIGHT WPOROGRIDPROPERTY PERMX UNITS MDARCY FROM PERM &

OVER JK AVERAGE OVER I HARMONIC_AV-- Calculations for properties and weights

CALCULATE WPORO BY = @DX * @DY * @DZEND

Weighted arithmetic mean SUM WEIGHT PROPERTY⋅( )SUM WEIGHT( )

---------------------------------------------------------------------------=

Weighted harmonic mean SUM WEIGHT( )SUM WEIGHT PROPERTY⁄( )---------------------------------------------------------------------------=

LOG Weighted geometric mean( ) SUM WEIGHT LOG PROPERTY( )⋅( )SUM WEIGHT( )

--------------------------------------------------------------------------------------------=


www.cadfamily.com


The control file command for integer data is of the form:

To apply the frequency count to data intervals with a specified spacing, use:

Note that the FREQUENCY option is not available for directional averaging.

• Expressions in control files may be continued over more than 1 line, by entering a continuation symbol (&) at the end of each incomplete line.

GRIDPROPERTY ppp UNITS uuu FROM ccc OVER IJK & FREQUENCY INTEGER

GRIDPROPERTY ppp UNITS uuu FROM ccc OVER IJK & FREQUENCY SPACING sss


www.cadfamily.com

GRID Reference Manual Edit GridCalculate pore volumes and transmissibilities P.3.9.7

427

Calculate pore volumes and transmissibilities P.3.9.7

Cal trans

PurposeCalculate values for pore volumes and transmissibilities for one or more grid layers, by sampling and averaging maps, or by using current grid block property values.

DescriptionThis option provides facilities for sampling detailed maps onto a fine grid and calculating pore volumes and transmissibility values to obtain upscaled values for coarse grid blocks. A command file can be used to define the relationships between grid layers and map strata, and the calculations to be performed.

The user can choose whether to calculate the properties over the entire grid or within a selected area. The area is defined by marking nodes around its boundary, or by a box within a selected range of rows and columns, or by a grid region, as for “Def prp are” P.3.8.5.3, page 386. The range of grid layers for calculation can be selected to include all layers in the grid, or may be restricted by the user.

Calculations are available for:

• Pore volumes.Volumes can be calculated by sampling maps over a fine grid, or by using grid block properties for porosity and net-to-gross values.

• Half-block transmissibilities.For upscaling transmissibilities from a fine grid, half-block values can be calculated by sampling maps. For a given direction, the fine grid transmissibilities are summed over parallel planes between the block centre and the corresponding block face. Harmonic averaging is then used to compute the average transmissibility. (This method is analogous to Kirchoff’s laws for electrical circuits.) Half-block values may also be calculated using grid block properties for permeability and net-to-gross.

• Transmissibilities and non-neighbour connections.The total transmissibilities between adjacent grid blocks can be calculated by combining half-block values or by the standard method of using grid block properties for permeability and net-to-gross. A multiplier may be applied at this stage, and NNCs can be calculated.

The results can be saved as grid block properties and also written directly to a file. Non-neighbour connections are not saved, and must be written out immediately.

Controlling parameters for the calculationsThe parameters controlling the calculations may be defined by reading an external control file or edited interactively. The following information is required:


www.cadfamily.com

428 Edit Grid GRID Reference ManualCalculate pore volumes and transmissibilities P.3.9.7

Fine grid subdivisionsThe fine grid for sampling can be constructed by subdividing each grid block in the I and J directions according to the minimum number of fine cells specified and the maximum fine cell width. This is the recommended approach, but as an alternative method, fine mesh subdivisions can be used, based on the node positions for a specified mesh map. This method identifies the mesh nodes in each grid block and operates directly on the node values instead of resampling the map.

In the K direction, the number of subdivisions per grid layer will be determined by the number of map strata corresponding to each layer. If required, the user can specify a thickness map name for constructing the fine layers. Otherwise, equal layer subdivisions will be used.

The fine grid subdivisions can be specified in the control file using a command of the form:

For mesh map subdivisions, the command is of the form:

Relationships between grid layers and map strataIf grid layers do not correspond exactly to map strata, the user must define the map strata corresponding to each grid layer in the selected range. The control file commands are of the form:

Note that the number of map strata for a given grid layer will define the number of fine layers used for calculations for grid blocks in this layer. If the grid layer numbers correspond to map strata, this can be specified in the control file by:

In this case, only one fine layer can be used for each grid layer. It is convenient to use this option to set up dummy layer data, when all the calculations use grid block properties instead of sampling maps.

Transmissibility calculation parametersThe user must indicate the units to be used for results (METRIC or FIELD units), the minimum pore volume cut-off value and the pore volume property to be used for checking against the cut-off limit.

The minimum pore volume cut-off defaults to 0.000001, but another constant value or the name of a property array may be specified. The pore volume for checking may be an existing grid property or may be calculated during the current calculation session.

The control file command is of the form:

FINEGRID SUBDIVISIONS n MAXWIDTH w THICKNESS mapname

FINEGRID MESHMAP mapname1 THICKNESS mapname2

GRIDLAYER n STRATA s1 s2 s3 or GRIDLAYER n STRATA s1 TO s2


TCALC UNITS uuu MINPV mmm PV ppp HTRAN hhh MINNNC ccc


www.cadfamily.com


429

where

Pinchout parametersIf non-neighbour connections are calculated, parameters controlling pinchout options can be set using a command of the form:

where

See the notes below for further information on pinchouts.

Pore volume calculationPore volumes can be calculated from map values or from grid block properties. The user must supply the property name for the calculated results, and the map or property names for obtaining porosity and net-to-gross values. A constant may be used for net-to-gross.


uuu is the keyword FIELD or METRICmmm is a constant or a grid block property name to be used for the minimum pore

volume cut-offppp is a grid block property name for the pore volumes to be checked (which may

already exist, or may be calculated during this current session)hhh is the option CUTOFF or NOCUTOFF, indicating whether the pore volume

cut-off is to be applied to half-block transmissibility calculations (default is CUTOFF)

ccc is the minimum transmissibility value for removing small NNCs.

PINCHOUT PINCHX xxx PINCHY yyy PINCHZ zzz GAP ggg &LAYERSPLIT lll PINCHTRAN ttt PINCHMULT mmm

xxx is the threshold width for horizontal pinchouts in the X-directionyyy is the threshold width for horizontal pinchouts in the Y-directionzzz is the threshold width for vertical pinchoutsggg is the keyword YES or NO for selecting the GAP option, controlling

generation of vertical pinchouts when cells are made inactive due to the minimum pore volume

lll is the maximum space between split layers, for which a transmissibility can be calculated

ttt is the keyword TOPBOT or ALL for the PINCHTRAN option, defining whether the pinchout transmissibility is calculated from the top and bottom cell only, or from a harmonic average of the Z-direction transmissibilities for all cells in the pinchout

mmm is the keyword TOP or ALL for the PINCHMULT option, defining whether the multiplier for the pinchout transmissibility is taken as the Z-direction multiplier for the top cell or the minimum multiplier for all cells in the pinchout.

PORV FROM opt PROPERTY vvv PORO ppp NTG nnn


www.cadfamily.com


where

Half-block transmissibility calculationsHalf-block transmissibilities can be calculated from map values or from grid block properties. The user must supply the property name for the calculated results, and the map or property names for obtaining permeability and net-to-gross values. A constant may be used for net-to-gross.


where

Transmissibility calculationsTransmissibilities can be calculated from half-block values or from grid block properties. The user must supply the property name for the calculated results, and the names of the property arrays to be used for calculation. A transmissibility multiplier may be defined as a constant or a grid block property.

For transmissibility calculations from half-block values, the control file command is of the form:

where

For transmissibility calculations from grid block property values, the control file command is of the form:

opt is the option MAPS or GRIDvvv is the name of the pore volume property (e.g. PORV)ppp is the name of the porosity map or property (e.g. PORO)nnn is a constant or the name of the NTG map or property (e.g. NTG).

HTRAN dir FROM opt PROPERTY hhh PERMEABILITY ppp NTG nnn

dir is one of the six possible directions X+ X- Y+ Y- Z+ Z-opt is the option MAPS or GRIDhhh is the name of the half-block transmissibility property (e.g. HTRANXP)ppp is the name of the permeability map or property (e.g. PERMX)nnn is a constant or the name of the NTG map or property (e.g. NTG).

TRAN dir FROM HTRAN PROPERTY ttt & HTR- hm HTR+ hp MULTIPLIER mmm

dir is one of the three possible directions X Y Zttt is the name of the transmissibility property (e.g. TRANX)hm is the name of the negative half-block property (e.g. HTRANXM)hp is the name of the positive half-block property (e.g. HTRANXP)mmm is a constant or the name of the multiplier property (e.g. MULTX).

TRAN dir FROM GRID PROPERTY ttt & PERMEABILITY ppp NTG nnn MULTIPLIER mmm


www.cadfamily.com


431

where

Non-neighbour connectionsNon-neighbour transmissibilities can be calculated and written to a file, provided that transmissibility values are being computed for all valid directions. The control file command is:

The user can choose to save the current set of commands in a control file after the transmissibility calculations are complete, or after quitting without performing any calculations. The external control file can then be used as a basis for further calculations if required.

dir is one of the three possible directions X Y Zttt is the name of the transmissibility property (e.g. TRANX)ppp is the name of the permeability map or property (e.g. PERMX)nnn is a constant or the name of the NTG map or property (e.g. NTG)mmm is a constant or the name of the multiplier property (e.g. MULTX).

TRAN NNC


www.cadfamily.com



Notes• To display or edit other grid block properties, see option P.3.9.6 (“Cal ave prp”, page

422) or menu P.3.8.5 (“Edt property”, page 384).

• Setting the number of fine grid subdivisions to 1 and specifying only one map stratum per grid layer will give results equivalent to sampling properties from single maps at grid block centres.

• Note that if fine mesh map subdivisions are used for pore volume calculations, the pore volume will be obtained directly by summing the contribution for each mesh map node within the grid block. The accuracy of these calculations will depend on the refinement of the mesh.

-- Transmissibility calculation options-- GRID Version 97A Date: 17/03/97 Time: 10:31:05-- Fine grid subdivisions

FINEGRID SUBDIVISIONS 1-- Relationships between grid layers and map strata

GRIDLAYER 1 STRATA 1GRIDLAYER 2 STRATA 2GRIDLAYER 3 STRATA 3GRIDLAYER 4 STRATA 4

-- Transmissibility units and minimum pore volume checkTCALC UNITS FIELD MINPV 0.000001 PV PORV MINNNC 0.01

-- Pinchout connection optionsPINCHOUT PINCHZ .100 GAP YES LAYERSPLIT 10.000 PINCHTRAN ALL

-- Pore volume calculationPORV FROM GRID PROPERTY PORV PORO PORO NTG 1

-- Half-block transmissibility calculationsHTRAN X- FROM GRID PROPERTY HTRANXM PERMEABILITY PERMX NTG 1HTRAN X+ FROM GRID PROPERTY HTRANXP PERMEABILITY PERMX NTG 1HTRAN Y- FROM GRID PROPERTY HTRANYM PERMEABILITY PERMX NTG 1HTRAN Y+ FROM GRID PROPERTY HTRANYP PERMEABILITY PERMX NTG 1HTRAN Z- FROM GRID PROPERTY HTRANZM PERMEABILITY PERMX NTG 1.0HTRAN Z+ FROM GRID PROPERTY HTRANZP PERMEABILITY PERMX NTG 1.0

-- Transmissibility calculationsTRAN X FROM HTRAN PROPERTY TRANX &

HTR- HTRANXM HTR+ HTRANXP MULTIPLIER 1.0TRAN Y FROM HTRAN PROPERTY TRANY &

HTR- HTRANYM HTR+ HTRANYP MULTIPLIER 1.0TRAN Z FROM HTRAN PROPERTY TRANZ &

HTR- HTRANZM HTR+ HTRANZP MULTIPLIER 1.0TRAN NNCEND


www.cadfamily.com


433

However, half-block transmissibility calculations on a fine mesh are performed by averaging the permeability over the mesh nodes and applying this to the coarse grid block geometry. Harmonic permeability averaging is used in the relevant principal flow direction, and net-to-gross values are included in the calculation for horizontal directions. This approach has been taken to avoid severe errors due to directional effects when the grid block is rotated relative to the fine mesh, but in many such cases, use of fine grid subdivisions may be preferred.

• The transmissibility calculations used here are based on the ECLIPSE corner point methods, also known as NEWTRAN (see "Corner point transmissibility calculations" in the "ECLIPSE Technical Description" for further details).

• When setting up half-block property names, note that the symbols ‘-’ and ‘+’ should not be included in property mnemonics.

• Expressions in control files may be continued over more than 1 line, by entering a continuation symbol (&) at the end of each incomplete line.

• The pinchout parameters are intended to be compatible with options that can be set in ECLIPSE (see the ECLIPSE keywords PINCH and PINCHXY). Note the following calculation conventions:

• Pinchout connections can only be formed across inactive cells (including cells made inactive by the MINPV cut-off, as defined for this calculation).

• If horizontal pinchouts are requested (X- or Y- direction) these will be generated across inactive cells which have an overall cell width less than the specified threshold value. Other parameters such as GAP do not apply to horizontal pinchouts.

• The GAP parameter allows NNCs across cells which are inactive due to MINPV, even if the thickness exceeds the Z-direction threshold. The threshold thickness will be strictly applied to all cells, if the GAP option is set to NO.

• The LAYERSPLIT parameter defines the maximum empty space allowed between cells in adjacent grid layers. This is unlimited, by default, unless specified by the user. If a limit is set, then the sum of all empty spaces between inactive cells will be checked, before generating a pinchout.

• The PINCHTRAN parameter allows the pinchout transmissibility to be computed as a harmonic average of all the Z-direction transmissibilities for the cells within the pinchout. By default, only the top and bottom active cells are used in this calculation.

• The PINCHMULT parameter allows the multiplier for the pinchout to be taken as the minimum multiplier over all cells within the pinchout. Otherwise, the multiplier for the top cell will be used. This option is ignored if PINCHTRAN ALL has been selected.

• Note that if a cell has pore volume less than 0.000001 it will be treated as zero, regardless of the MINPV setting. Such cells are assumed to be barriers to flow unless the cell thickness is strictly less than the pinchout threshold.

• GRID does not remove NNCs between inline cells (which may occur in pinchouts). In the simulator, these non-neighbour connections may be removed and treated as normal connections between active cells, by adding the transmissibilities to the appropriate cell values. ECLIPSE will perform this processing for NNCs that are generated in GRID and input as user-defined connections.


www.cadfamily.com

434 Edit Grid GRID Reference ManualConvert grid data to map data P.3.9.8

Convert grid data to map data P.3.9.8

Grid to maps

PurposeConvert grid data into a set of maps.

DescriptionData stored in a GRID model, i.e. geometry, properties and regions, can be converted into map data. This option, when used in conjunction with option P.6.4 "Export maps", page 521, provides an efficient means of exporting grid data to other programs such as FloGrid.

One map stratum is created for each layer of the grid. Only areal maps can be created, and this option can only be used from an XY display. Either the entire grid area can be mapped or an area can be selected. One or more layers can be mapped.

Instructions and parameters can be read in from a control file, described below, or entered manually. The user can select whether to output geometry maps (depths or thicknesses), property maps or region maps. A list of selected maps is displayed on the screen. and the user is asked if he/she wants to modify the list, create the maps or quit.

The default names for the maps are TOPS and BOTTOM for node depths, THICK for thicknesses, and the property and region name for property and region maps. The user can specify new names for any map or a root which will prefix the default names, e.g. if the root is ’MAP’ the default thickness map name will become ’MAP_THIC’. Note that map names must be no more than eight characters long.

When the list of maps has been completed GRID checks each new map to see if there are any existing maps with the same name. If the map name is new GRID will create a new map. If the map already exists and the units of the existing map differ from those of the new map, the user is asked to find another name for the new map. If the units are the same GRID gives the user the option of overwriting the existing map. In this case any existing mesh or contour data is deleted. The default is to delete any existing fault data, but any well data, feature data, caption data, zone data or legend data will be preserved.

Three types of map can be created: contour maps, scattered data maps or mesh maps. In addition grid-splits can be saved as map faults.

Contour maps will be the same as those produced by back-contouring, i.e. geometry map contours will match the back-contours produced by option D.6.4.6 "Sho grd cnts", page 586, property map contours will be the same as those produced by option P.3.8.5.9.6 "Sho prp cnts", page 396, and region map contours will be the same as those produced by option P.3.8.4.9.6 "Sho reg cnts", page 383.

Scattered data maps consist of data values at arbitrarily distributed points. They are stored as contour maps with one data point on each contour. They have one data point for each node value or block value. Split node values are moved a fraction of a grid cell away from the node, determined by a parameter EPSILON. Block values can be set at the centre of the top, middle or bottom face of the cell, depending on the parameter LEVEL.

Mesh maps are created by interpolating the grid data. The same maps could be created by using option P.2.5.3 "Cal mesh" (see page 192) on a scattered data map.


www.cadfamily.com

GRID Reference Manual Edit GridConvert grid data to map data P.3.9.8

435

A fairly simple approach is used for saving grid splits as map faults. GRID first joins up splits along columns, labelling these as FLT-1, FLT-2 ... and then joins up splits along rows. Therefore zig-zag faults will be made up of several non-consecutively numbered row and column faults.

Interpolation flags and parameters from the control file, or default values are displayed and can be edited by typing in a keyword (see Table 6.3 below). Parameters and map names can be saved to a control file for future use.

Users unfamiliar with the meanings of the various interpolation parameters are recommended to accept the default values. These have been chosen to give reasonable maps for a wide range of data sets. Fine tuning can be carried out by adjusting each parameter in turn and examining the results.

A local grid refinements (LGR) can be mapped by first selecting it (type "L" for option D.7.9 "Edt LGR", see page 617). Radial LGRs cannot be mapped.

Control fileA control file can be used to store layer limits, map names, interpolation flags and parameters. The control file consists of a list of keywords, which can be in any order. If there is no keyword for a parameter GRID sets that parameter to its default value.

Layer limits are defined by the LAYERS keyword followed by two integers:

The default value for layer1 is 1 and the default value for layer2 is equal to the number of layers in the grid.

Map names can be specified using the following syntax:

whereKeywords for parameters are given in the following table:

LAYERS layer1 layer2

datatype griddata mapname [units]

datatype must be either GEOMETRY, PROPERTY or REGIONgriddata depends on the datatype:

datatype: griddata:

GEOMETRY TOPS, BOTTOM, THICKPROPERTY a property nameREGION a region name,

mapname is the map name and must be 8 or less characters long,units is optional, but if used must be consistent with the griddata units.


www.cadfamily.com


Table 6.3 Parameter keywords used in the control file and for editing

Keyword Description Default Range

MAPTYPE Map type MESH CONTOUR

MESH

SCATTER

Flags and parameters for maps made from node data (depths and thicknesses)

NODE USE FAULT

NODE USE *

Flag to use grid splits as faults

during interpolation. If this flag is FALSE only one data value is used at each split node.

TRUE TRUE

FALSE

NODE DEL FAULT

NODE DEL *

Flag to delete any existing map faults TRUE TRUE

FALSE

NODE SAVE FAULT

NODE SAVE *

Flag to save grid splits as map faults TRUE TRUE

FALSE

NODE CLIP FAULT

NODE CLIP *

Flag to clip contours to map faults (Contour maps only)

FALSE TRUE

FALSE

EPSILON If grid splits are used as faults, the split node values are moved a

fraction epsilon of a grid cell away from the node

0.025 > 0

Flags and parameters for maps made from block data (regions and properties)

BLOCK USE FAULT

BLOCK USE *

Flag to use grid splits as faults

during interpolation

FALSE TRUE

FALSE

BLOCK DEL FAULT

BLOCK DEL *

Flag to delete any existing map faults TRUE TRUE

FALSE

BLOCK SAVE FAULT

BLOCK SAVE *

Flag to save grid splits as map faults FALSE TRUE

FALSE

BLOCK CLIP FAULT

BLOCK CLIP *

Flag to clip contours to map faults (Contour maps only)

FALSE TRUE

FALSE

LEVEL (x,y) coordinates for block values can be set at the centre of the top, middle or bottom face of the grid block (scattered data maps and mesh maps), or at the centre of the top or bottom face of the grid block for contour maps. NB this option only has any effect if the grid contains sloping coordinate lines.

TOP TOP

MIDDLE

BOTTOM

Parameters for contour maps


www.cadfamily.com

GRID Reference Manual Edit GridConvert grid data to map data P.3.9.8

437

MINOR INTERVAL

MINOR

Minor contour interval. If the default contour interval is used then appropriate values will be selected for each map.

DEFAULT > 0

MAJOR INTERVAL

MAJOR

Major contour interval (must be a multiple of minor contour interval).

DEFAULT DEFAULT or >= 0

QUALITY Contour quality. (Parameter used by the CONPAC contouring package.)

1.0 > 0.1

Parameters for mesh maps

BOUNDARY If this flag is TRUE mesh points outside the grid boundary will be set to NULL

TRUE TRUE

FALSE

NROW Number of mesh rows Model default

4 - 10000

NCOL Number of mesh columns Model default

4 -10000

XMIN Minimum map x-coordinate Model default

< XMAX

YMIN Minimum map y-coordinate Model default

< YMAX

XMAX Maximum map x-coordinate Model default

> XMIN

YMAX Maximum map y-coordinate Model default

> YMIN

MAP_NULL Null value to be used for map 0.1E7

Null value for grid properties

GRID_NULL If a grid property has this value it will be treated as null and ignored

-1E20

CONPAC parameters for interpolating grid data at mesh points

(See Section P.2.4.9.7 "Chg interp" for more information on CONPAC parameters.)

MODE Interpolation mode. See P.2.4.9.7.6 "Def int mod"

2

DAMPING FACTOR

DAMPING

DAMP

Damping factor. See P.2.4.9.7.4 "Def dmp fac"

0.1 0.001 - 10.0

FLOOR Lower truncation level. See P.2.4.9.7.3 "Def trn vals"




www.cadfamily.com


If the grid contains reverse faults it will be necessary to map fault blocks separately, by selecting an area of the grid.

Areas of the grid are defined by selecting grid blocks in the display layer - either by digitizing, specifying rows and column limits, or by specifying a region number. The area defined for the display layer applies to all layers that are mapped. Therefore if the grid contains sloping coordinate lines, the (X,Y) coordinates of the area will change from layer to layer, although the (I,J) coordinates will remain the same.

Grid areas are not stored in the control file. However a region can be defined with the same boundaries as the area, and this can be used to define the grid area before the control file is read in.

CEILING Upper truncation level. See P.2.4.9.7.3 "Def trn vals"

LOCAL Local truncation flag. See P.2.4.9.7.3 "Def trn vals"

FALSE TRUE

FALSE

TOLERANCE Tolerance if lower, upper or local truncation used

> 0.00001

EMPTY OCTANTS

EMPTY

OCTANTS

Maximum number of empty octants allowed when interpolating a mesh value. See P.2.4.9.7.5 "Def sch rad"

7 0-7

SEARCH RADIUS

SEARCH

RADIUS

Search radius in world coordinates, or set to OPTIMAL. See P.2.4.9.7.5 "Def sch rad"

OPTIMAL OPTIMAL or > 0

Keywords can be used in a control file, or to edit the data in GRID.

Keywords marked * can only be used in the control file. To edit node or block fault flags in GRID type the keywords NODE or BLOCK. GRID will then prompt for each flag value. The NODE and BLOCK fault flags are displayed in tabular form.

Some keywords can be abbreviated. Where this is the case the full keyword is given first, e.g. ‘SEARCH RADIUS’, followed by the allowed abbreviation(s), e.g. ‘SEARCH’ and ‘RADIUS’.




www.cadfamily.com

GRID Reference Manual Simulation ResultsIntroduction

439

Chapter 7Simulation Results

IntroductionGRID can read solution data from ECLIPSE restart files, and display the results using colour-filled grid blocks or contours. The solution display can be shown against a background map. Derived quantities can be used to calculate new solution values by arithmetic formulae or by taking differences between timesteps.

Results data can be displayed on an existing grid, or a new grid can be created by loading in an ECLIPSE .GRID output file. (Note the requirement for the active cell numbers in the grid to match the active cells used in the ECLIPSE run, allowing for pore volume cut-offs etc.)

Note that further facilities for presentation of solution data are available in ECLIPSE Office, and in the post-processing program GRAF, together with extensive line graphics options for displaying vector data (e.g. oil production vs. time). For 3D visualization of simulation results, use FloViz.


www.cadfamily.com

440 Simulation Results GRID Reference ManualSimulator results P.4

Simulator results P.4

Sim results

PurposeDisplay simulator results.

DescriptionThe “Sim results” option displays the following menu:

This option allows the user to load results data from ECLIPSE restart files and display the solutions for active grid blocks.

The user is prompted for the name of the grid to be displayed and for the name of the solution data to be displayed. If the grid does not already exist in the model, a new grid can be created in the same way as when the “Edt grid” option P.3 (see page 276) is selected. In particular, it is possible to take the “Input grid” option P.3.0.6 (see page 292) and read a grid from an ECLIPSE .GRID file, thus ensuring that the file is correct for the solution data to be read.

The “Return” option returns the user to the primary menu.

Table 7.1 Menu P.4

Option Function

1 Return

2 Sim solution Display simulator solutions


www.cadfamily.com

GRID Reference Manual Simulation ResultsEdit solutions P.4.2

441

Edit solutions P.4.2

Sim solution

PurposeEdit and display solution arrays for the grid.

DescriptionThe “Sim solution” option displays the following menu:

The “Sim solution” facility allows output data to be read from ECLIPSE restart files and used to create displays. The data is not stored internally by GRID on exit from this menu.

New solution data for all time steps may be created using arithmetic/logical formulae, which can include any loaded solution parameters as variables, as well as any properties or region numbers which have been defined for the grid.

The maximum number of solutions which may be loaded at one time depends on a program parameter (MXSOL). This is usually set to 50.

The “Return” option returns the user to the “Sim results” menu and discards all loaded solution data. Each of the other options is described in the following sections.


Option Function

1 Return

2 Lod solution

3 Dsp solution

4 Cre solution

5 Cre diff

6 Out solution

7 Clr solution

8 Lod active

Load solutions

Display solutions

Create solutions

Create differences

Output solutions

Clear solutions

Load active cell numbers


www.cadfamily.com

442 Simulation Results GRID Reference ManualLoad solutions P.4.2.2

Load solutions P.4.2.2

Lod solution

PurposeLoad solution data from a restart file.

DescriptionThe user is prompted for the following information:

• The root name of the restart file

(which may optionally be preceded by a directory path)

• Are the restart files formatted?

• Are the restart files unified?

• The first time-step required.

• The last time-step required.

GRID will check that the appropriate file exists and, if no first time step is specified for non-unified files, that at least one file exists with sequence number less than 500.

The data for the first time-step are read, to establish which solutions are to be loaded and messages are written to the screen as subsequent data are loaded.

GRID will check that the number of active cells in the restart files is the same as the number of active cells defined by the ACTNUM array for the current grid. The data cannot be loaded unless the number of active cells is consistent. It is recommended that either the current solution grid is read as a new grid when viewing solution data for the first time or that the active cell array produced by ECLIPSE is read from the INIT file to define active cell numbers (option P.3.8.3.6, “Inp active”, see page 442, or option P.4.2.8, “Lod active”, see page 450), since ECLIPSE automatically sets cells with pore volumes less than 0.000001 to be inactive.

GRID does not allow 2D radial local grid refinements. All solution data for 2D radial grids will be expanded automatically to 3D by giving the 4 azimuthal cells the same value.

The current release does not have facilities for displaying output from Vertical Equilibrium or dual porosity runs.

Up to 50 solution names can be loaded at one time and sequence (time-step) numbers up to 1000 are allowed by default. These numbers are set in program parameters MXSOL and MXSEQ respectively.


www.cadfamily.com

GRID Reference Manual Simulation ResultsDisplay solutions P.4.2.3

443

Display solutions P.4.2.3

Dsp solution

PurposeDisplay solution arrays for the grid.

DescriptionThe user is prompted for the solution array and sequence number to be displayed. The following menu options are available:

Options 3 to 8 operate in the same way as for property data.

Options 2 and 9 are described in the following sections.


Option Function

1 Return

2 Sho sol fll

3 Chg sol fll

4 Mov sol key

5 Chg sol key

6 Sho sol cnts

7 Chg sol cnts

8 Out sol cnts

9 Sho cnt seq

Show solution fill

Change solution fill

Move solution key

Change solution key

Show solution contours

Change solution contours

Output solution contours

Show contour sequence


www.cadfamily.com

444 Simulation Results GRID Reference ManualShow solution fill P.4.2.3.2

Show solution fill P.4.2.3.2

Sho sol fll

PurposeDisplay solution arrays with colour fill.

DescriptionThe grid cells are colour-filled using values for the current solution array and sequence number, in the same way as for property arrays. The following menu is then available for changing the display:

Options 2-6 are used for showing different time steps. Option 7 can be used to show the current data value for selected cells, at the current time step.

Note that when a grid contains LGRs, the solution values for LGR cells can be obtained through “Sho value”, without using the display menu option D.7.9, “Edt LGR”. However, this display option may be used to show the solution for one local grid only, e.g. to view interior local cells which are not visible on a global display.

1 Return2 Step forward3 Step back4 Jump5 Sequence forward6 Sequence backward7 Show value


www.cadfamily.com

GRID Reference Manual Simulation ResultsShow contour sequence P.4.2.3.9

445

Show contour sequence P.4.2.3.9

Sho cnt seq

PurposeDisplay a sequence of contours from all timesteps.

DescriptionThe user is prompted for the value of a contour to be displayed and the quality at which the contour is to be drawn. The contours at the given value will be drawn for every time-step of the current solution.

By choosing a suitable contour value, a front can be followed through the entire simulation on the same display.


www.cadfamily.com

446 Simulation Results GRID Reference ManualCreate a solution P.4.2.4

Create a solution P.4.2.4

Cre solution

PurposeCreate a new solution.

DescriptionA new solution array (for every time-step) can be created using the arithmetic/logical parser. Property arrays, region number arrays and existing solution arrays may all appear as variables in the given formula. In addition, the name @PORV may be used to calculate the pore volume for the cells in units of cubic metres (or @PORV_RB for reservoir barrels) and may be used in the formula for volumetrics purposes.

The user is prompted for the name of the new solution array, which may be displayed in the same way as any other solution array.


www.cadfamily.com

GRID Reference Manual Simulation ResultsCreate differences P.4.2.5

447

Create differences P.4.2.5

Cre diff

PurposeCreate a new solution by taking differences.

DescriptionA new solution array (for every time-step) can be created by taking the differences from one time step to the next. The first time step is given values of zero.

The user is prompted for the name of the new solution array.


www.cadfamily.com

448 Simulation Results GRID Reference ManualOutput solution P.4.2.6

Output solution P.4.2.6

Out solution

PurposeWrite solution values to a user file.

DescriptionA solution data array can be output to a file. Output is written to a file with extension .GRDECL (or .GEC if 3-character extensions are used). The file will be opened if it has not already been opened, otherwise output will be added to existing output. If the file already exists, the user is asked whether to overwrite it.

The array is written out, headed by the name of the solution array and the sequence number, with column values increasing fastest, then row values, then layer values.

E.g. for a 4x5x2 grid:

SWAT 15 0.4000 0.4500 0.4500 0.4500 0.4100 0.4600 0.4600 0.4700 0.4200 0.4750 0.4750 0.4900 0.4250 0.4800 0.4850 0.4950 0.4250 0.4800 0.4900 0.50000.6000 0.6500 0.6500 0.6500 0.6100 0.6600 0.6600 0.6700 0.6200 0.6750 0.6750 0.6900 0.6250 0.6800 0.6850 0.6950 0.6250 0.6800 0.6900 0.7000/


www.cadfamily.com

GRID Reference Manual Simulation ResultsClear a solution P.4.2.7

449

Clear a solution P.4.2.7

Clr solution

PurposeClear a solution.

DescriptionIf too many solution arrays are loaded, it may be necessary to clear some solution data from memory before creating or loading new arrays. This option prompts for the name of the solution array to be cleared, and frees the associated workspace.


www.cadfamily.com

450 Simulation Results GRID Reference ManualLoad active cell numbers from INIT file P.4.2.8

Load active cell numbers from INIT file P.4.2.8

Lod active

PurposeRead active cell numbers from an ECLIPSE INIT file, to modify current grid for solution display.

Description The user is prompted to indicate whether the INIT file is formatted or unformatted and to enter its name.

The selected INIT file is searched for the pore volume array. Each cell will then be set active or inactive depending on whether the pore volume is greater than 0.000001. The global grid and all LGRs are processed in this operation.

If the array is read satisfactorily, the grid can be redrawn, displaying the new active/inactive cells. The user can also choose to save the changed grid permanently.


www.cadfamily.com

GRID Reference Manual Edit SurveyIntroduction

451

Chapter 8Edit Survey

IntroductionThe ECLMap options include facilities for reading or digitizing survey data, consisting of navigation lines and interpreted seismic horizon data (time and/or depth values).

After a survey has been loaded into the program, the horizon data can be sampled, gridded and contoured. Each survey has associated time and depth maps, which can be edited via the “Edt map” menu (see page 57). Fault lines and control data (e.g. contour lines, well depths) can be entered on these maps and will be included with the seismic data when a horizon is sampled. The “Smp survey” menu (see page 467) provides options for test sampling the data and changing the interpolation parameters, to obtain the most suitable parameters for creating a gridded mesh map from the original data. An option to identify mis-ties at shot line intersections is also provided.

When a survey has been edited and checked, and satisfactory interpolation parameters have been defined, the time or depth data from a horizon can be used to create a new mesh map via the “Cal mesh” command (reached via the “Edit map” menu).

Additional facilities for depth conversion of seismic horizon data or time maps are provided from the “Map utils” menu (see page 477).


www.cadfamily.com

452 Edit Survey GRID Reference ManualEdit survey P.5

Edit survey P.5

Edt survey

PurposeCreate a new seismic survey or edit an existing survey.

DescriptionAfter a survey has been read or created, the following menu is displayed:

The user is prompted for the name of the survey to be edited and the horizon number required. If the horizon number is not zero, either a time or depth horizon can be edited. Horizon zero does not have any associated data and is used to display the navigation only.

The survey name and its horizon number may be specified in the short form: Survey_name(Horizon_number + T or D), e.g. NETH(2T)

Horizon number zero should be given if no time or depth data has been input, i.e. only the navigation data is available.

If an unrecognized survey name is given then the user is asked whether a new survey is to be created. The user will be prompted to enter the units of time values in the survey and the range of values, and similarly, the depth units and depth range. The given ranges are used for the display of shotline sections and may be changed from menu P.5.6, “Chg svy pars” (see page 471).

In addition to the survey file, two map names are allocated with the same name as the survey. One set of maps is used for time data, with the stratum number corresponding to the survey horizon number, and the second set is used in a similar manner for depth data. The maps may be edited in the same way as any other map. Any fault lines or contour data (e.g. at well locations) on the maps will be included with the seismic data whenever an horizon is sampled.

When editing a survey, any time or depth horizon can be displayed whether or not it has any associated data. The navigation lines will be drawn as solid lines along lines where data exist for the given horizon, but as dotted lines where no data exists.

Table 8.1 Menu P.5

Option Function

1 Return

2 Edt sht lnes

3 Inp survey

4 Out survey

5 Smp survey

6 Chg svy pars

7 Chg hor nums

8 Def granite

Edit shot lines

Input survey

Output survey

Sample survey

Change survey parameters

Change horizon numbers



www.cadfamily.com

GRID Reference Manual Edit SurveyEdit survey P.5

453

When the “Return” option is selected from the “Edt survey” menu the user is asked whether to save the survey on disk and is returned to the Primary menu.

If the survey is saved the existing .SVY or .FSV file will be overwritten and an entry is made in the model history file. Additional comments may be entered into the history file, as required.

If the survey is not saved, it remains the current survey and may be saved on a subsequent occasion. In order to return to the unedited survey it must first be cleared from the model using menu P.8, “Clr wrkspc” (see page 540), and re-loaded from disk.

Note that it is possible to change horizons or to change between editing times or depths by selecting the display options:

“D”

“Chg view”

“Edt XY-plane”


www.cadfamily.com

454 Edit Survey GRID Reference ManualEdit shot lines P.5.2

Edit shot lines P.5.2

Edt sht lnes

PurposeEdit shot line data.


Shot line data can be entered and edited in the form of navigation lines and picked horizon data.

Data are stored as a series of vectors for each shot line, indexed by shot point number. The user is prompted for the shot point interval at which data values are to be stored on each shot line, whenever a shot line is created or modified. The first and last shot points will always be stored.

The “Return” option returns the user to the “Edt survey” menu. Each of the other options is described in the following sections.


Option Function

1 Return

2 Add sht lne

3 Del sht lne

4 Dig section

5 Opr horizon

6 Sho value

7 Def value

8 Smp horizon

Add shot line

Delete shot line

Digitize section

Operate on horizon

Show value

Define value

Sample horizon


www.cadfamily.com

GRID Reference Manual Edit SurveyAdd a shot line P.5.2.2

455

Add a shot line P.5.2.2

Add sht lne

PurposeDigitize a new shot line or change an existing shot line.

DescriptionNavigation data for shot lines can be digitized on to the current survey. New lines can be added to the survey, or existing navigation lines can be changed. If a digitizing table is to be used, it should first be set up using the “Set dig tbl” option D.8 on the “Display” menu (see page 618). The following menu is displayed:

The user is prompted for the shot point storage interval. If a storage interval of less than zero (e.g. -1) is entered, the raw data will be stored without interpolation. Otherwise, a base value should be entered, for constructing a list of interpolation points at the given interval. By default, only interpolated data will be stored. However, the user may choose to store all data (i.e. raw data as well as interpolated points). In all cases, the first and last points on the line will be stored, and no data will be extrapolated beyond these points.

The user must also enter the interval between shot points to be input. (This will normally be the same as, or a multiple of, the shot point storage interval.)

The typical distance, in centimeters, between shot points on the map is then requested. The distance between shot points is used as a loose check (an error of up to 75% on this distance is allowed) to ensure that shot points are not redigitized or missed by mistake. The check can be switched off by entering a distance of zero between points.

When option 2 is selected, the user is prompted for the name of the shot line to be digitized. If the shot line already exists then the user is asked whether to continue with this line. The numbers of the first, second and last shot points must then be given.

When digitizing the line, input points subsequent to the second point will be numbered according to the interval given when the “Add sht lne” option was selected, until the shot point number exceeds or is equal to the number given as the last point. The shot point number is then set to the last point number and no more points will be accepted.

Option 5 allows the shotline to be restarted from any shotpoint.

Option 6 allows the user to respecify the interval between shotpoints.

Option 7 allows the user to respecify the distance between shotpoints.

Option 8 allows a miscellaneous point to be added without invoking the distance check.

1 Return2 New line3 Abandon4 Continue5 Restart6 Set interval7 Set spacing8 Add point


www.cadfamily.com

456 Edit Survey GRID Reference ManualAdd a shot line P.5.2.2

When a “New line” is started or the “Return” option is selected the current input line is saved by interpolating the input points on to the current storage interval.

The first and last points are always saved. When modifying an existing line, only the parts of the line between the first and last shot points given will be changed. If the first and last points extend beyond the limits of the current line then any existing horizon data will be extended with null data.


www.cadfamily.com

GRID Reference Manual Edit SurveyDelete a shot line P.5.2.3

457

Delete a shot line P.5.2.3

Del sht lne

PurposeDelete shotline(s) from the current survey.

DescriptionThe user is asked to name or select the shot line to be deleted.

If an asterisk ‘*’ is entered in response to the name, then all the shotlines on the survey will be deleted, on confirmation by the user.

If the letter ‘Q’ is entered in response to the name, each shot line is highlighted in turn and the user can select to delete the line or not. Sequencing through the shotlines can be ended by entering the letter ‘E’.

If no name is entered, then the user is asked to select the shotline on the survey to be deleted by digitizing a point close to the line on the screen. The shotline is highlighted and confirmation is requested to delete it.


www.cadfamily.com

458 Edit Survey GRID Reference ManualDigitize a section P.5.2.4

Digitize a section P.5.2.4

Dig section

PurposeDigitize a seismic section.

DescriptionSeismic sections for a shot line can be digitized, whether or not navigation data already exist for the shot line. New horizons can be digitized on to existing shot lines or new shot lines and existing horizons can be changed.

The user is asked to enter or select the shot line for which the section is to be digitized and prompted for the following:

• Whether time or depth horizons are to be digitized

• The range of time or depth values

• The range of shot point values to be digitized.

The display screen will be confined to the range of data values entered. If the requested shot line does not already exist, it will be created with the range of shot point values given.

The user is prompted for the shot point storage interval. If a storage interval of less than zero (e.g. -1) is entered, the raw data will be interpolated onto storage points corresponding to existing navigation data. Otherwise, a base value should be entered, for constructing a list of interpolation points at the given interval. If a storage interval is specified, the user may choose whether to reinterpolate existing data.

The user is then required to calibrate the digitizing table. A special set-up mode is used, so that it is not necessary to use the display option D.8 “Set dig tbl” (see page 618) prior to selecting this option. The table is calibrated by digitizing known shot points along the shot line and arbitrary points along specified horizons. (Alternatively, data can be edited on the screen, by selecting input via the graphics locator instead of using a digitizing table.)

After a digitizing table has been set up, the following menu is displayed for digitizing the section:

When option 2 is selected, the user is prompted for the horizon number to be digitized. The horizon may then be digitized over any range of shot point values. When another horizon is started or “Return” is selected, the input data are stored by interpolating the input line on to the stored shot point numbers for the line. No values beyond the digitized data will be overwritten. If the horizon is a new horizon, data outside the digitized range will be left with null values. If an existing horizon is changed, data outside the digitized range is left unchanged.

1 Return2 New horizon3 New segment4 Abandon5 Continue


www.cadfamily.com

GRID Reference Manual Edit SurveyDigitize a section P.5.2.4

459

Fault cuts may entered by finishing a line segment and taking the “New segment” option. The current horizon will be continued with a break at the point where the new segment was started. Fault cuts will be marked at the beginning and ends of line segments. Any shot points that lie between pairs of fault cuts (i.e. the end of one line segment and the beginning of the next) will be given null values. Reverse faults cannot be modeled.


www.cadfamily.com

460 Edit Survey GRID Reference ManualOperate on horizon P.5.2.5

Operate on horizon P.5.2.5

Opr horizon

PurposeOperate on a seismic horizon.

DescriptionSimple arithmetic operations can be performed on a range of horizons. If the current display is areal (XY), the user is prompted for the line name to operate on. ‘Q’ or ‘*’ may be entered to query the lines or change all the lines. If the current display is a cross section of a shot line, it is assumed the user intends to operate on the horizons for the current shotline only.

The user will then be asked if it is required to operate on times or depths, and for the range of horizons to be changed.

The range should be specified in the form Hor_1:Hor_2, for example:

• To change horizons 5 to 8 inclusive, enter 5:8

• To change horizon 4 to maximum horizon number, enter 4:

• To change horizons 1 to 6 inclusive, enter 1:6 or :6

If the current display is a cross section of a line, the horizons specified by the user will be highlighted.

The operation to be performed must then be entered. Typically, the operation would begin with + or - some constant, to bring out mis-ties with intersecting shotlines.


www.cadfamily.com

GRID Reference Manual Edit SurveyShow value P.5.2.6

461

Show value P.5.2.6

Sho value

PurposeShow the value of a shot point.

DescriptionOn selecting this option, the user is prompted to choose whether to show shot point values only, fault cut values only or all values.

Further prompts are then issued to select points. The shotline name, shot point (or fault cut) number and its value are displayed at the bottom of the screen.

Note that for an areal display (XY-plane) of horizon zero (i.e. navigation data only), the selected shot point will have no data value.


www.cadfamily.com

462 Edit Survey GRID Reference ManualDefine value P.5.2.7

Define value P.5.2.7

Def value

PurposeDefine the value of a shot point.

DescriptionOn selecting this option, the user is prompted to choose whether to select shot point values only, fault cut values only, or all values.

Further prompts are then issued to select points. The value of the selected point is displayed at the bottom of the screen and the user is prompted to enter a new value. (Hit Return to leave value unchanged).

Cross-section displays will be altered immediately when a new value is entered. When editing an areal display with shot point values shown, the numbers will not be updated to show the new values until the screen is refreshed.

Note that for an areal display (XY-plane) of horizon zero (i.e. navigation data only), the selected shot point will have no data value.


www.cadfamily.com

GRID Reference Manual Edit SurveySample horizon P.5.2.8

463

Sample horizon P.5.2.8

Smp horizon

PurposeSample a seismic horizon.

DescriptionThis option allows the time or depth values for a seismic horizon to be set by sampling a map.

The option allows the use of arithmetic formulae so that, for example, thicknesses may be added to the current depth values, if these have been determined in some other way than the depth conversion techniques provided on the “Map utilities” menu P.6 (see page 477).

The user is prompted for the horizon to be sampled, whether to sample only at missing depths, and the name of the map to be sampled. The map name may be replaced by a formula or preceded by arithmetic operators.


www.cadfamily.com

464 Edit Survey GRID Reference ManualInput survey P.5.3

Input survey P.5.3

Inp survey

PurposeInput seismic navigation and (if required) associated time or depth data.

Description

Input from a fileThe user is prompted for the name of the file containing the survey data. (Note that survey data can be input only from an areal display.)

The first line of the data file will then appear at the bottom of the screen and the new menu will allow the user to skip through the file and view the data. The option “Next line” should be selected to skip any header records until the first shot point number is displayed. Data input will commence with the current record being displayed when the option “Return” is selected.

If the first character of the first record in the file is a * or (, it is assumed to be a format statement, e.g. (A32, 3E13.5), and it will be the default when the user is prompted for the input format. If the first record is not a format statement, then the default input format will be list directed ‘*’. Note that the shot line name may be up to CHARACTER*32 and that the shot point number is input as REAL.

The user will be prompted for the format to be used for reading the file. If a user-specified format is given, a check is made to ensure that the format statement is enclosed within brackets. If it is not, brackets will be added.

It is possible to read the whole input file or to read only selected shot lines. If the user chooses to read selected shot lines only, as each shot line is read the user will be asked if it is to be saved. If it is saved, the shot line will then be drawn on the screen, otherwise the next shot line will be read. When the end of the file is reached, the total number of shot lines read will be indicated.

The user may choose to check the navigation data for inconsistencies. If checking is requested, further prompts will be issued, to enter the approximate distance between shot points (in metres), the distance tolerance value and the maximum shot line deviation angle. A file root for the error report must be supplied. As the data are read, any errors will be reported in a file, with name <root>.ERR. Problems with shot point numbers (e.g. repetition) will also be reported.

The data must be in tabular form: Shot line name, shot point no.,vector 1, vector 2, ... , vector N where any number of vectors may be given.

The user is asked for the total number of columns of data in the input file. If the total number of columns of data is 4 or more (i.e. horizon data are present), the user is asked if the input data are time or depth data. The user will be asked to identify the data in each column, e.g. data in column 3 may be X-locations, column 4 may be y-locations and column 5 may be time data for horizon 6.

Note Shot line name and shot point number are assumed to be columns 1 and 2 respectively.


www.cadfamily.com

GRID Reference Manual Edit SurveyInput survey P.5.3

465

When the file format, contents, etc., have been established, the shot point storage interval must be specified. If a storage interval of less than zero (e.g. -1) is entered, the raw data will be stored without interpolation. Otherwise, a base value should be entered, for constructing a list of interpolation points at the given interval. By default, only interpolated data will be stored. This may result in more data being stored than were originally present in the file, or it may result in extraneous data being discarded. Alternatively, the user may choose to store all data (i.e. raw data as well as interpolated points). In all cases, the first and last points on the line will be stored.

Navigation data may be read using UKOOA format, as described in Appendix K.

The old ECL ‘MALLAN’ format may be used by typing MALLAN in response to the prompt for the file format.

In order that null data can be read without adjusting the internal null value, the user is now asked for an input null value. Any values in the data that are found to be greater than or equal to the input null value will be reset to the current internal null value.

If required, the input shot lines may be clipped outside the model area. If this option is selected, any shot line segments which fall entirely outside the model area will be discarded.

Fault cut dataFault cut data can be read with formatted vector data or list-directed input. Fault cut data for a particular shot line should follow the shot point data for that line. The format is similar to the shot point data format:

where the FAULTCUT keyword is used in place of the shot line name and null values are entered for any horizon where the fault cut is not defined.

Fault cut data can also be read from ‘MALLAN’ files.

'FAULTCUT', shot point no.,vector 1, vector 2, ... , vector N


www.cadfamily.com

466 Edit Survey GRID Reference ManualOutput survey P.5.4

Output survey P.5.4

Out survey

PurposeOutput navigation and/or time and depth data from the current survey to a data file.

DescriptionThe user is prompted for the root name of the file to be used. The file will be given the name ‘root.SHT’.

The type of data to be output is then requested. It is possible to output survey times, depths or just the navigation data.

If survey times or depths are to be output, a horizon range must be entered. This may be given as, e.g. ‘2:7’ for horizons 2 to 7 inclusive, ‘3:3’ for just horizon 3 or ‘*’ for all horizons.

If horizon time or depth data are to be output, an option to output fault cut data will be offered.

The user may choose to output all shot line data or selected lines only. If selected lines are to be written out, a further prompt will be issued for the shot line name. If an asterisk ‘*’ is entered, all shot lines will be written (i.e. the selection option is cancelled). If the letter ‘Q’ is entered, shot lines will be highlighted as they are written, and the user can choose whether to output each line. If a shot line name is entered, that line will be output, or if the user enters RETURN with no shot line name, a line may be selected with the mouse or cursor.

The user is then prompted to choose whether to clip output lines outside the model area. If this option is selected, any shot line segments which fall entirely outside the model area will be discarded.

The user is then prompted for an output format, e.g. (A32,3E13.5) (default is list directed ‘*’). Note that the shot line name may be up to CHARACTER*32 and that the shot point number is output as REAL.

The data are output as: shot line name, shot point number, Easting, Northing, followed by horizon times or depths if requested.

If fault cut data are written out, the fault cuts corresponding to a particular shot line will be output immediately after the shot point data for that line. The same data format is used, with the keyword ‘FAULTCUT’ replacing the shot line name, and null data values are used for any horizon where the fault cut is not defined.

If a user-specified format is given, a check is made to ensure the format statement is enclosed within brackets. If it is not, brackets will be added.

Navigation data may also be output in latitude & longitude using the UKOOA format, described in Appendix K.

The old ECL ‘MALLAN’ format may be used by typing MALLAN in response to the prompt for the file format.

When output is complete, the user is informed of the number of shot lines that were written to the file.


www.cadfamily.com

GRID Reference Manual Edit SurveySample survey P.5.5

467

Sample survey P.5.5

Smp survey

PurposeSample a survey.


The “Smp survey” menu allows seismic survey data to be sampled, so that the interpolation and contouring parameters can be adjusted.

The “Return” option returns the user to the “Edt survey” menu.

Options 2 and 4 to 8 are the same as for digitized contour maps.

Options 3 and 9 are described in the following sections.


Option Function

1 Return

2 Tst point

3 Tst survey

4 Sho svy cnts

5 Out svy cnts

6 Chg interp

7 Chg granite

8 Chg fill

9 Out misties

Test point

Test survey

Show survey contours

Output survey contours



Change colour fill

Output mis-ties


www.cadfamily.com

468 Edit Survey GRID Reference ManualTest survey P.5.5.3

Test survey P.5.5.3

Tst survey

PurposeScan a digitized survey for areas with insufficient data for interpolation with the given search criteria. Assist the user to improve the data distribution or select more appropriate search criteria, and thus obtain an optimal balance between interpolation quality and gridding speed.

DescriptionThe purpose of this option is to scan a digitized survey and highlight areas of the survey that have a sparse distribution of data. Clusters of data points are sampled for these areas using a radial search method. The extra data points can be added to the original data as new control points if the user wishes. An optimal fixed search radius is also derived from the radial search. This should be saved with the survey if the user chooses to save the clustered data points.

On selecting the option “Tst survey”, the user is asked if it is required to scan contour lines or digitized points and prompted for the number of lines or points required in the search circle. The fewer the number of required lines or points given, the smaller the final search radius is likely to be. The default value of 5 lines or 20 points is recommended for most surveys.

The initial scan for areas of sparse data will then begin and will not take long. Any areas on the survey where interpolation cannot be performed using the current search criteria will be highlighted as clusters on the screen. The user is prompted to save the new data points if required. If the new clusters of data are too few or too many it is possible to go back and redefine the number of lines or points to be used in the search.

If the user elects to save the new clusters of data, a prompt for the number of digitized points in each of the 16 sectors of the search circle will be made. Interpolation of values for the new clusters will then begin. Interpolating with the radial search method is heavy on CPU and may take some time.

When Z values have been interpolated for the clustered data, the optimum search radius used is returned to the user. This should be saved with the survey, as significant increases in speed will be made when subsequently sampling the survey to create mesh maps.

Note that the extra data points sampled will be stored on the stratum of the associated time or depth map, corresponding to the time or depth horizon being tested. E.g. If the survey is E1215 horizon 5, time data (E1215(5T)), then the data will be stored on stratum 5 of the E1215 time map.


www.cadfamily.com

GRID Reference Manual Edit SurveySet interpolation debug P.5.5.6.7

469

Set interpolation debug P.5.5.6.7

Set debug

PurposeChange the interpolation debug level.

Note that this option is primarily for the use of programmers and is not recommended for general use.

DescriptionThe debug level for the interpolation routines can be changed.

A facility for increasing the amount of workspace supplied to the interpolation and contouring routines is also provided. This facility should not be needed by the general user.


www.cadfamily.com

470 Edit Survey GRID Reference ManualOutput misties P.5.5.9

Output misties P.5.5.9

Out misties

PurposeOutput shotline intersection points and mistie data to a file.

DescriptionThe user will be asked for the name of an output file. If this file already exists the user will be warned and can respecify the name if required. Next a shotline name is requested. The user may select all shotlines (by typing ‘*’), explicitly name one shotline, or press ‘Return’ to select a particular shotline using the cursor. Finally, a horizon range is required. This is the range over which mistie data will be output for the selected shotlines. The user may select a range of horizons (e.g. ‘1:5’ for horizons 1 to 5 inclusive), a single horizon (e.g. ‘2:2’ for horizon 2) or all horizons (by typing ‘*’). If ‘0:0’ is selected, no mistie data will be output.

Intersection data will consist of the shot point numbers (as real numbers) for each line at the intersection point, together with the name of the intersecting line, and the Eastings and Northings (and latitude & longitude) of the intersection point.

Mistie data will consist of the shot point number at the intersection point, with a mistie value (positive or negative from the current line) in the survey units for each horizon specified. If no data are available at the intersection point for either line then ‘null’ will be written. If 2 or more lines intersect with the current line, then the mean and standard deviation mistie value for each horizon will be output. These values are calculated from all non-null misties.

A second output file is also created containing only the line names and shot point numbers of the intersections. This file has the same name as the mistie output file, but with the suffix ’.INS’ appended.


www.cadfamily.com

GRID Reference Manual Edit SurveyChange survey parameters P.5.6

471

Change survey parameters P.5.6

Chg svy pars

PurposeChange the parameters associated with a survey.



Option Function

1 Return

2 Chg pnt mrks

3 Chg val lbls

4 Chg num lbls

5 Chg svy area

Change point marks

Change value labels

Change number labels

Change survey area

Option 2 allows the interval between shot point markers to be changed.Option 3 allows the interval between shot points labelled with the current horizon

values to be changed.Option 4 allows the interval between shot points labelled with the shot point number to

be changed.Option 5 allows the user to change the survey area.


www.cadfamily.com

472 Edit Survey GRID Reference ManualChange horizon numbers P.5.7

Change horizon numbers P.5.7

Chg hor nums

PurposeChange horizon numbers for a survey.

DescriptionThis option can be used to change the horizon numbers that are currently stored. For example, it might be necessary to renumber the horizons if a new horizon is identified between two existing horizons.

The corresponding stratum numbers for the time and depth maps associated with each horizon will also be changed.

The user is prompted for the range of horizons to be changed. The range should be specified in the form Hor_1:Hor_2, for example:

• To change horizons 5 to 8 inclusive, enter 5:8

• To change horizon 4 to maximum horizon number, enter 4:

• To change horizons 1 to 6 inclusive, enter 1:6 or :6

The user is the prompted for the change in numbering that is required. This must be defined by + or - an integral number (e.g. +2).


www.cadfamily.com

GRID Reference Manual Edit SurveyDefine Granite settings P.5.8

473

Define Granite settings P.5.8

Def granite

PurposeDefine the pen, text and shot point marker representations to be used when drawing and labelling shot lines.


The “Return” option returns the user to the “Edt survey” menu. Each of the options 2 to 7 leads to a further menu for setting Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current default Granite attributes for the line, text or marker. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.

Option 8 allows the size of tickmarks drawn at fault cuts to be changed.

On selecting the option to return, the user is prompted for the shotline name to change. The shot-line name may given as ‘*’ or ‘Q’ or a name template. If ‘*’ is entered all shot lines will be changed. If Q or a template is given the user will be asked whether to change each line in turn (if it matches the template).

This option may be used to redefine shot line drawing colours before new shot lines are created. For example, if shot lines from different years of origin are read on to the same survey file they may be identified more easily by colour coding.


Option Function

1 Return

2 Def sht pen

3 Def lne txt

4 Def val txt

5 Def num txt

6 Def pnt mrk

7 Def flt pen

8 Def flt tck

Define shot line pen

Define line text

Define value text

Define number text

Define point marker

Define fault pen

Define fault ticks


www.cadfamily.com

474 Edit Survey GRID Reference ManualDefine Granite settings P.5.8


www.cadfamily.com

GRID Reference Manual Map UtilitiesIntroduction

475

Chapter 9Map Utilities

IntroductionThe Map Utilities include the ECLMap options for depth conversion and volumetrics, together with general options for importing map data and processing well data.

Depth conversionTime to depth conversion can be performed for time maps or seismic horizon data. The following conversion methods are available:

• Interval velocity method

• Depth related method

• Thickness related method

• Table look-up

• Direct interpolation for shot point depth data

• Depth dependent velocity method

• Faust’s method

The formulae are given in the section describing the Depth Conversion menu (see page 479). Choice of the most appropriate method will depend on available information on rock types, velocities, etc. If velocity data are available in map form, a map name can be entered wherever a velocity constant is expected in a formula: the map will be sampled at each point where conversion is performed.

Depth conversion can be carried out using a step-by-step approach, starting from the top horizon. Eroded surfaces, pinch-outs, salt domes etc. can be modeled by converting the same horizon from a number of different upper horizons. Fault cuts on shot lines are handled automatically.


www.cadfamily.com

476 Map Utilities GRID Reference ManualIntroduction

VolumetricsThe volumetric analysis options can be used to calculate bulk volumes from depth or thickness maps, taking account of vertical or sloping faults. Volumes can be calculated for the full map area or for individual zones (e.g. lease blocks).

Bulk volumes can be operated on using porosity and saturation maps to obtain pore volumes and fluids-in-place. Cut-off values can be entered, to exclude volumes of mesh cells with porosity or saturation less than a specified limit.

A water saturation map for use with the volumetrics calculations can be calculated from maps of porosity, top and bottom depths, together with a user-specified value for the free water level. The calculation can use a formula for water saturation vs. height or tabular data can be input for interpolation.

Importing map dataMenu P.6.3 (see page 497) provides miscellaneous options for importing map data from external files. These include facilities to read in one or more mesh maps and construct GRID map strata, options to load in Stratamodel cell attribute data or EarthVision data, and facilities for exporting multiple mesh maps.

Well dataFacilities are provided to read in well trajectory data, for use in defining well completions for a simulation grid. The well positions can be displayed using option D.7.8.7, “Sho well trj” (see page 615).


www.cadfamily.com

GRID Reference Manual Map UtilitiesMap utilities P.6

477

Map utilities P.6

Map utils

PurposeEnter map utilities menu.

DescriptionA number of diverse utility functions have been grouped together on this menu. The following options are available:

The “Return” option returns the user to the Primary menu. Each of the other options is described in the following sections.

Table 9.1 Menu P.6

Option Function

1 Return

2 ECLMap opts

3 Import maps

4 Export maps

5 Copy maps

6 Well data

Access ECLMap special options

Options to import external map data

Options to export map data

Copy existing map data to new maps

Options to process well data


www.cadfamily.com

478 Map Utilities GRID Reference ManualECLMap options P.6.2

ECLMap options P.6.2

ECLMAP opts

PurposeAccess ECLMap options for volumetrics, depth conversion and picture building.

DescriptionThe following ECLMap options are available from this menu:

The “Return” option returns the user to the “Map utils” menu. Each of the other options is described in the following sections.


Option Function

1 Return

2 Dep convert

3 Volumetrics

4 Cal wtr sat

Depth conversion

Volumetric analysis

Calculate water saturation map


www.cadfamily.com

GRID Reference Manual Map UtilitiesDepth conversion P.6.2.2

479

Depth conversion P.6.2.2

Dep convert

PurposePerform depth conversion of maps or shot point data.

DescriptionThe following depth conversion options are available:

A comprehensive set of depth conversion facilities is offered. Depth conversion of maps or seismic horizons may be performed. The technique allows the user to account for missing data due to eroded surfaces or pinched out layers, and will depth convert fault cuts on shot lines. A choice of depth conversion methods is offered:

(i) Interval velocity method

[EQ 9.1]

Typically the interval velocity will be in map form, being input from well velocities or other velocity control points. The velocity field can be edited as contours within “Edt map”.


Option Function

1 Return

2 Cnv point

3 Cnv map

4 Cnv sht pnt

5 Cnv sht lne

6 Cnv horizon

Convert point

Convert map

Convert shot point

Convert shot line

Convert horizon

Table 9.4 Depth conversion methods

Option Function

1 Int velocity

2 Dep method

3 Thk method

4 Tbl look-up

5 Sample

6 Dep velocity

7 Faust

Interval velocity method

Depth related method

Thickness related method

Table look-up

Direct interpolation from map

Depth dependent velocity

Faust’s method

D2 D1Vi T2 T1–( )

2---------------------------+=


www.cadfamily.com

480 Map Utilities GRID Reference ManualDepth conversion P.6.2.2

(ii) Depth related methodVelocity varies linearly with depth.

[EQ 9.2]

[EQ 9.3]

This formula will provide only an approximate tie to well control points and therefore should be used only for regional depth conversion studies. Vo can be input as a map, which can be used to account for geological factors such as uplift.

(iii) Thickness related method

[EQ 9.4]

If

[EQ 9.5]

Otherwise

[EQ 9.6]

This is most often used to depth convert the thick Permian salt layers of NW Europe, where there is often an inverse linear relationship between the velocity and the thickness of the layer. In this case, the minimum allowable velocity would be 4200m/sec, preventing a use of a very slow velocity for calculations within salt swells and domes.

(iv) Table lookup The user must provide a file containing two columns of data. The first column should contain two-way time differences (in SECONDS) and the second column the corresponding thicknesses. For each data point we then have:

[EQ 9.7]

This is most useful in regional studies where velocity information is limited to time versus depth graphs for a very small number of wells and a regionally varying velocity field is not available.

(v) Direct interpolationThis method is only available for shotpoint data and is similar to the previous method except that thicknesses are sampled directly from a thickness map.

Note that it does not require any time data to be available and may be useful when a thickness map has been determined by some means other than depth conversion for the horizon in question.

It should be noted that if direct interpolation is used at one horizon then it will not be possible to depth convert a lower horizon unless times are known at that horizon. The “Smp horizon” option is provided on menu P.5.2, “Edt sht lnes” (see page 454), to enable mapped times to be sampled back on to shot lines. This is most useful for marine data where the Water Bottom is not digitized as a horizon. Water Depth maps can be simply converted to time and sampled back to the shot lines.

Vz Vo kz+=

D2 D1Vok

------ D1+⎝ ⎠⎛ ⎞ exp

k T2 T1–( )2

------------------------⎝ ⎠⎛ ⎞ 1–⋅+=

Vdz Vo k zd⋅+=

Vdz Vmin<

D2 D1Vmin T2 T1–( )

2---------------------------------+=

D2 D1Vok

------ expk T2 T1–( )

2------------------------⎝ ⎠⎛ ⎞ 1–⋅+=

D2 D1 zd atT2 T1–( )+=


www.cadfamily.com

GRID Reference Manual Map UtilitiesDepth conversion P.6.2.2

481

(vi) Depth dependent velocity method

[EQ 9.8]

[EQ 9.9]

This is very similar to the (ii) Depth related method but the formula allows the wells to be tied exactly. can be input as a map (as for the (ii) Depth related method).

It might prove useful in some cases to produce independently via grid arithmetic, allowing the velocity field to be quality controlled before the depth is calculated.

(vii) Faust’s methodWhere Faust’s law is valid, the velocity curve is:

[EQ 9.10]

Above a critical depth, either a constant minimum velocity is assumed or a parabolic velocity law is used, i.e.

(constant)

or

(parabolic law)

Prompts are issued for the following values:

• Faust’s law constant, f

• Power value, N (> 1, usually N = 3 or 6)

• Choose whether to use a constant minimum velocity or parabolic law above a critical depth (C/P)

• If constant minimum velocity is selected, enter the required value

• If a parabolic law is used, enter the critical depth.

Note that map names may be entered instead of constants for the parameters f and N.

The symbols in the formulae are:

is the two-way time to the upper surface

is the two-way time to the lower surface

is the depth of the upper surface

is the depth of the lower surface

is an interval velocity

is a velocity constant

is a depth dependent velocity

is a thickness dependent velocity

is a minimum velocity

VzVo kD1+

1.0 0.25k T2 T1–( )–------------------------------------------------=

D2 D1Vz T2 T1–( )

2---------------------------+=

Vo

Vz

Vz fz1 N⁄=

Vz Vo=

Vz Vo kz2+=

T1

T2

D1

D2

Vi

Vo

Vz

Vdz

Vmin


www.cadfamily.com

482 Map Utilities GRID Reference ManualDepth conversion P.6.2.2

Depth conversion is normally carried out from the top horizon to the bottom horizon. A step-by-step approach is adopted, allowing the user full control at each stage. For each depth conversion step the user is prompted for the number of the horizon to be converted and the upper horizon. The depth and time values for the upper horizon will be used to obtain and in the formulae given above.

Note that it is not necessary for the upper horizon to be the immediately preceding horizon. For the first horizon, an upper horizon of 0 may be entered so that starting values of zero times at zero depths.

Depth conversion cannot take place at any point when any of the values , or are null. This will happen at pinch outs, on-laps etc. In this case the user should proceed to depth-convert the same target horizon but with a higher upper horizon. This step-by-step approach allows a new velocity to be specified appropriate to the layer through which the sound is travelling. For each horizon converted the user will be asked whether to convert only null values, i.e. values which have not already been depth converted. It is important that the question is answered correctly (i.e. with ‘Y’ - the default) if data points are not to be inadvertently reconverted.

Fault cuts on shot lines are depth-converted automatically, with depth and time values on the upper horizon interpolated from the depth and time values at the same shot point value as the fault cut on the upper horizons.

The user is prompted for the velocities and velocity slopes used in the formulae for each depth conversion. The arithmetic/logical parser is used to evaluate any expression entered at this point, so velocities may be constants or map names or more complicated expressions. Maps will be depth converted by gridding the expression given. Shot line data will be depth-converted by interpolating the given maps on to the shot point locations. (If no x,y locations are available for shot lines then the velocities or slopes must be entered as constants). The depth conversion formulae assume that velocities are entered in units such that the times are converted to depths with the units given when the survey or maps were created. If the velocity map units are not suitable for this then a conversion factor should be entered as part of the expression for the velocity or slope.

Note that it is assumed that the time values associated with shot point data or maps always represent two-way travel times.

is the lower horizon depth

is the distance from the upper horizon to the lower horizon

is the rate of change of velocity with depth or thickness.

z

zd

k

T1 D1

D1 T1 T2


www.cadfamily.com

GRID Reference Manual Map UtilitiesConvert a point on a map P.6.2.2.2

483

Convert a point on a map P.6.2.2.2

Cnv point

PurposeDepth convert at a point on a map.

DescriptionThe user is prompted for the name of the time maps to be converted and for the name of the target depth maps. The given time maps must exist but a new set of depth maps may be created at this point. The user is prompted for the stratum number to be converted. A time map must exist for the given stratum. Although it is not necessary for a depth map to exist, a recognized map name must be given as the target depth map, so that upper horizon values can be found.

A series of arbitrary points may then be entered for depth conversion. At each point any of the depth conversion methods may be used. The calculated depth at each point will be displayed at the bottom of the screen.

Depths at new points will be calculated until another option is selected.


www.cadfamily.com

484 Map Utilities GRID Reference ManualConvert map P.6.2.2.3

Convert map P.6.2.2.3

Cnv map

PurposeDepth convert a map stratum.

DescriptionThe user is prompted for the name of the time maps to be converted and for the name of the target depth maps. The given time maps must exist but a new set of depth maps may be created at this point. The user is then prompted for the stratum number to be converted. A time map must exist for the given stratum. The user will be prompted for the number of rows and columns in the target depth grids and for their areal extent.

A series of time horizons may then be depth converted using any of the methods described previously. As each horizon is converted the user will be asked whether to save the converted map and, if so, the contour intervals and contour quality to be used for drawing it. If digitized contours exist on the target map stratum, then confirmation will be requested to delete them.

When the series of depth conversions is ended, the user will be asked if the converted maps are to be stored on disk. If so a message will also be written to the history file.


www.cadfamily.com

GRID Reference Manual Map UtilitiesConvert a shot point P.6.2.2.4

485

Convert a shot point P.6.2.2.4

Cnv sht pnt

PurposeDepth convert a shot point.

DescriptionThe user is prompted for the name of the survey to be converted.

A series of arbitrary shot points may then be selected for depth conversion at any horizon for which time data exists at the chosen shot point. At each point any of the depth conversion methods may be used. The calculated depth at each point will be displayed at the bottom of the screen.

Depths at new points will be calculated until another option is selected.


www.cadfamily.com

486 Map Utilities GRID Reference ManualConvert a shot line P.6.2.2.5

Convert a shot line P.6.2.2.5

Cnv sht lne

PurposeDepth convert a shot line.

DescriptionShot lines may be depth converted one at a time, either for test purposes, or if changes have been made which affect only individual lines.

The user is prompted for the name of the survey to be converted and is asked to select the shot line to be depth converted.

A series of horizons may then be depth converted, provided time data are available on the shot line for the given horizon. Any of the available depth conversion methods may be used. If the depth conversion is performed satisfactorily, the horizon data can be saved.

When the sequence of depth conversions is finished, the whole survey can be saved on disk. Note that for large surveys it may be more efficient (though less safe) to depth convert a number of lines before saving the results, due to the amount of disk I/O required. Each time the survey is saved a message will be written to the history file.


www.cadfamily.com

GRID Reference Manual Map UtilitiesConvert horizon P.6.2.2.6

487

Convert horizon P.6.2.2.6

Cnv horizon

PurposeDepth convert a seismic horizon.

DescriptionThis option allows all the shot lines in the survey to be depth converted at one time.

The user is prompted for the name of the survey to be converted.

A series of horizons may be depth converted, provided time data are available. Any of the available depth conversion methods may be used. If the depth conversion is performed satisfactorily, the horizon can be saved.

When the sequence of depth conversions is finished, the whole survey can be saved on disk. Note that for large surveys it may be more efficient (though less safe) to depth convert a number of horizons before saving the results, due to the amount of disk I/O required. Every time the survey is saved a message will be written to the history file.


www.cadfamily.com

488 Map Utilities GRID Reference ManualVolumetrics P.6.2.3

Volumetrics P.6.2.3

Volumetrics

PurposePerform volumetric analysis on depth or thickness maps.


Volumetric analysis in ECLMap is based on regular meshes of arbitrary size. A finer mesh will give more accurate results but will require greater computing time.

If it is required to calculate volumes within arbitrary polygonal areas (such as lease blocks), these should be defined as zones. The zones may be defined either on the depth or thickness map for which volumes are to be calculated, or on a separate map.

Bulk volumes may be determined from either structure or thickness maps and subsequently multiplied by porosity or saturation maps to obtain pore volumes and fluids-in-place.

The user is prompted for the root name of the file to be opened for output. The output file will be given the name ‘root.VOL’.

All the results from volumetric calculations are written to the screen and to the output filename supplied by the user.

The user is prompted for a map name and stratum number. Any zones on the given map will be those for which volumes are calculated. The map dimensions will also be used as defaults for subsequent prompts. If the zones are defined on a separate map to the depth or thickness map for which volumes are to be calculated, the zone map name should be supplied here by the user.

The area for which volumetrics are required and the size of the volumetrics mesh are then prompted for.

Note that although the volumetrics options will locally grid or re-grid any of the maps used, as necessary, this may take considerable computing time. It is recommended that maps are converted to gridded mesh maps before performing the volumetrics.



Option Function

1 Return

2 Cal volumes

3 Opr volumes

4 Sho volumes

5 Smp volumes

6 Sho zon are

Calculate volumes

Operate on volumes

Show volumes

Sample volumes

Show zone area


www.cadfamily.com

GRID Reference Manual Map UtilitiesCalculate volumes P.6.2.3.2

489

Calculate volumes P.6.2.3.2

Cal volumes

PurposeCalculate volumes for a given depth or thickness map.

DescriptionThe user is asked if it is required to calculate volumes for depth or thickness maps.

The user is prompted for the operation to be performed. The three operations =, + and - are available.

• If ‘=’ is entered, the user is prompted for the output units, and a new current bulk volume is calculated.

• If ‘+’ is entered, the volume calculated will be added to the current volume.

• If ‘-’ is entered, the volume calculated will be subtracted from the current volume.

The name of the depth or thickness map to be used in the calculation is then requested. This map may be different from the map name supplied for zone definition when the “Volumetrics” option was entered.

A cut-off depth or thickness must also be given. This can be used to exclude from the the volumetrics calculation any cells that are below a contact level, or that have less than a given thickness.

The user is requested to specify if the full map volume is required.

Before calculating volumes, the given map is gridded. (If the map has the same area and dimensions as the required volume mesh, then the map is simply copied, so setting up a suitable mesh map in advance can save considerable computation time.) Volumes for each mesh cell are then calculated.

After the volume mesh has been derived, the volume of each zone will be calculated and reported individually. If requested, the total volume for the full map is then calculated and reported. All results are written to the output file specified by the user. The user can choose whether to display results to the screen as well.

Each cell of the volume mesh is classed as one of six categories, according to the nature of the zone boundaries and faults which pass through the cell:

Class 1: Undivided cellsClass 2: Simple boundary cutsClass 3: Simple fault cutsClass 4: Simple boundary cuts with faultsClass 5: Complex divisions or single NULLSClass 6: More than one NULL value


www.cadfamily.com

490 Map Utilities GRID Reference ManualCalculate volumes P.6.2.3.2

The accuracy with which volumes are calculated varies according to the class to which the cell belongs. The following methods are used:

In practice classes 4 and 5, although poor approximations, are rare events and so do not harm overall accuracy significantly.

The number of cells in each class is determined and the sub-volume of each class is defined in the result in addition to the total volume of all the classes.

The volume mesh is stored locally by the program and may be sampled or contoured using the “Smp volumes” option (see page 493).

Class 1: The cell volume is calculated, taking into account the curvature of the cell.Class 2: The cell is divided accurately into vertical prisms and each prism treated as a

trapezoid.Class 3: As for class 2Class 4: The mean cell height is calculated and used for the volume calculation.Class 5: Complex divisions are cells that do not fall into Classes 1-4. An

approximated volume is calculated automatically for isolated single NULL cells.

Class 6: Clusters of two or more adjoining NULL cells are not included in the volumetric calculations The number of such cells is simply flagged here.


www.cadfamily.com

GRID Reference Manual Map UtilitiesOperate on volumes P.6.2.3.3

491

Operate on volumes P.6.2.3.3

Opr volumes

PurposeOperate on the calculated volumes.

DescriptionThis option allows operations on current calculated volumes.

The operation may be entered using the general arithmetic/logical parser, although the expression would normally begin with * or /. Map names may be entered in place of variables in the expression. Any required maps are gridded on to the same size mesh as the volume mesh, if necessary, and then a cell value for each mesh cell is calculated by taking an average of its four corner values.

A cut-off value for the calculated mesh may be entered, so that, for example, volumes of cells with porosity less than 0.05 are excluded, or cells with oil saturation less than 0.1 are excluded.

The volume mesh is operated on by the calculated mesh and a volume report given for each zone.


www.cadfamily.com

492 Map Utilities GRID Reference ManualShow volumes P.6.2.3.4

Show volumes P.6.2.3.4

Sho volumes

PurposeShow volume calculated for a particular zone.

DescriptionThe user is asked to select the zone on the map for which it is required to know the volume.

The calculated volume for the selected zone will be displayed at the bottom of the screen.


www.cadfamily.com

GRID Reference Manual Map UtilitiesSample volumes P.6.2.3.5

493

Sample volumes P.6.2.3.5

Smp volumes

PurposeSample the volume mesh.

DescriptionA volume mesh is stored, containing the volume of each cell. This mesh may be sampled or contoured in the same way as a map mesh. By contouring the volume mesh, areas of high and low volume are easily identified.

Note that the volume interpolation parameters are only used from this menu. The interpolation parameters used during volumetric calculations are those stored with the map being gridded.


Options 2 to 5 are the same as for contour maps. The Granite settings and colour fill settings that can be changed are those for drawing the volume contours.


Option Function

1 Return

2 Tst point

3 Sho vol cnts

4 Out vol cnts

5 Chg interp

6 Chg vol cnts

7 Chg vol fll

Test point

Show volume contours

Output volume contours



Change colour fill


www.cadfamily.com

494 Map Utilities GRID Reference ManualShow zone area P.6.2.3.6

Show zone area P.6.2.3.6

Sho zone area

PurposeShow the area of a particular zone.

DescriptionThe user is asked to select the zone on the map for which it is required to know the area.

The area of the zone is then calculated and will be displayed at the bottom of the screen.


www.cadfamily.com

GRID Reference Manual Map UtilitiesCalculate water saturation P.6.2.4

495

Calculate water saturation P.6.2.4

Cal wtr sat

PurposeCalculate a water saturation map from porosity and depth maps.

DescriptionThe user is prompted for the following:

• Map name for the calculated water saturation mesh

• Number of rows and columns for new saturation mesh

• Whether to perform calculations for the full map, current zoom area, or a polygon (which may be digitized, read from a file or taken from a map zone boundary)

• Porosity map, top depth map and bottom depth map to be used in the calculation.

If the water saturation map already exists, the user can choose to re-grid, modify the existing map, or quit. If a map is modified within a selected area (e.g. within a digitized polygon), values outside that area will be unchanged.

The porosity map must be in fractional units (i.e. 0 to 1). If any of these maps are not mesh maps, a mesh will be interpolated. If any of the meshes do not have the same number of rows and columns as requested for the water saturation map, a mesh of the same size will be interpolated.

Finally, the free water level will be requested. This should be entered in the same units as the depth maps.

The water saturation curve may be interpolated using an internal formula or by using a file of tabular data. If tabular data are requested, the file name, input format and marker card value must be entered.

The tabular data file should contain data in three columns:

Several curves may be defined, delimited by marker records, e.g.

The calculated water saturation map will be in fractional units (i.e. 0 to 1).

Column 1 Water saturationColumn 2 Height above free water level (in depth map units)Column 3 Porosity

0.3 100.0 0.150.35 80.0 0.150.4 60.0 0.159999 9999 99990.2 100.0 0.200.25 80.0 0.200.3 60.0 0.209999 9999 9999


www.cadfamily.com

496 Map Utilities GRID Reference ManualCalculate water saturation P.6.2.4

Before the calculation is performed, the user is given the option to set saturation values to NULL in pinchout regions. Otherwise, the water saturation will be set according to the top surface height, wherever this is at, or below, the bottom surface, and this can result in poor contouring on the final saturation map.


www.cadfamily.com

GRID Reference Manual Map UtilitiesImport map data P.6.3

497

Import map data P.6.3

Import maps

PurposeAccess special options for importing map data from external files.

DescriptionThe following options are available for importing map data:



Option Function

1 Return

2 Mesh files

3 Stratamodel

4 Earthvision

5 DXF files

Import one or more mesh maps

Import Stratamodel data

Import EarthVision data

Import / export DXF files


www.cadfamily.com

498 Map Utilities GRID Reference ManualImport one or more mesh maps P.6.3.2

Import one or more mesh maps P.6.3.2

Mesh files

PurposeImport data for one or more mesh maps.

DescriptionThis option allows the user to load mesh data from one or more external files. If required, a control file can be read, to define the input data structure and specify the maps to be loaded. Fault data may be loaded at the same time as mesh data if required. The user may also define a simple arithmetic operation to be performed on the raw data (e.g. multiply by a constant).

The parameters defining the input data structure may be read from a control file or defined interactively, as for the “Inp mesh” option (P.2.5.2, see page 180). The user will then be prompted to decide whether fault data processing or map operations are required. If not, no further prompts for fault files or operations will be issued. Otherwise, the fault file layout must be defined before entering the list of maps to be read. The list of maps to be loaded may be read from the same control file as the input structure parameters or defined interactively. The user may edit this list before reading the data.

Before loading in any data, the program will check whether any of the maps exist already. If so, a warning is issued and the user may choose to abandon the data input. If fault data are to be input, the user can decide whether to delete or keep any old fault data on the maps.

The units to be used for new maps may be defined before starting to load the data. If new maps are being created, the program will issue prompts to define the map units, if these are undefined when the first stratum for each new map is processed.

If fault input is enabled, the user will be prompted to enter a fault file name for each map, unless the mesh is an EarthVision 2D grid, for which the fault trace files can be identified automatically from the header. If no fault traces exist for a particular map, the fault file name should be omitted.

If map operations are enabled, the user will be prompted to enter an operation to be performed on the raw input data. The operation can be omitted if not required for a particular map.

On systems where an interrupt facility is available, the user can break in and abandon data loading after data input has started, by hitting the escape key <ESC>. If a user interrupt occurs, data loading will end as soon as possible after processing the current map.

After a group of maps has been loaded, the user can choose to save the commands to an external control file.


www.cadfamily.com

GRID Reference Manual Map UtilitiesImport one or more mesh maps P.6.3.2

499

Example control file to read maps but no fault trace data:

Example control file to read maps and fault trace data, inverting the Z-axis for the structure maps:

-- Mesh data file description-- GRID Version CUR Date: 13/07/93 Time: 13:24:17

TYPE ASCIINROW HEADER LINE 8 ITEM 1NCOL HEADER LINE 8 ITEM 2XMIN 540000.0YMIN 5995000.XMAX 570000.0YMAX 6030000.ANGLE .000NULL HEADER LINE 7 ITEM 2ORIGIN T (Top Left)ORDER C (Along Columns)BLOCK Y (Blocked)START 11 (First line of data)FORMAT *

-- Commands for loading mesh data filesMAP XXX STRATUM 2 MESH zmapa.gctMAP XXX STRATUM 3 MESH zmapb.gctMAP YYY STRATUM 1 MESH zmap1.gct UNITS FRACTIONMAP YYY STRATUM 2 MESH zmap2.gctEND

-- Mesh data file description-- GRID Version 95B Date: 20/03/95 Time: 12:17:19

TYPE CPS-3--NROW Read from file--NCOL Read from file--XMIN Read from file--YMIN Read from file--XMAX Read from file--YMAX Read from file

ANGLE .000--NULL Read from file--ORIGIN T (Top Left)--ORDER C (Along Columns)--BLOCK Y (Blocked)--START Default from file--FORMAT (Binary)-- Commands for loading mesh data files

FAULTS YESFAULTFILES CPS-3MAP TOPS STRATUM 1 MESH surface1.svs UNITS FEET &

FAULTS faults1.svf OPERATION *-1.MAP TOPS STRATUM 2 MESH surface2.svs UNITS FEET &

FAULTS faults2.svf OPERATION *-1.MAP PROP STRATUM 1 MESH property.svs UNITS FRACTION

END


www.cadfamily.com

500 Map Utilities GRID Reference ManualImport one or more mesh maps P.6.3.2

Notes1 When data are loaded into an existing map with this option, any existing mesh or contour

data will be deleted.

2 The areal dimensions of each map stratum are defined according to the data being read. Other map parameters, such as contour intervals for drawing, will be set to appropriate defaults and may be modified by the user by means of the “Edt map” menu (P.2, see page 57).

3 The new maps are not drawn on the screen during processing, but can be edited later by means of “Edt map”.

4 The control keywords for specifying fault input are:

where

The THIN and CLIP keywords may be omitted. See note (5) for details on EarthVision faults.

where

5 For EarthVision 2D grid files, the names of a corresponding vertical fault file and a non-vertical fault file can be read from the file header, and the faults will be loaded automatically if the user specifies FAULTS AUTO with no additional FAULTFILES parameters.

FAULTS YES THIN CLIP

YES/NO enables or disables fault inputTHIN indicates fault traces are to be thinnedCLIP indicates fault traces are to be clipped to the model area

FAULTFILES ttt FORMAT fff MARKER mmm START lll

ttt is the fault file layout, selected from:A: X1,Y1,X2,Y2B: X,Y,IDC: X,YD: X,Y,NAMESPECIAL: special fault file with major and

minor traces identifiedCPS-3: CPS-3 binary fault file (.svf)EV-VERTICAL: EarthVision vertical faultsEV-NONVERT: EarthVision non-vertical faultsUKECL, UK84

or UK8:

UKOOA format fault file

fff is the Fortran format for reading the faults, needed for fault layouts A, B, C, D and SPECIAL. This should be set to * for free-format input in most cases.

mmm is the marker value for separating fault traces, needed only for layout C.lll is the line number for the start of the fault trace data (default 1).


www.cadfamily.com

GRID Reference Manual Map UtilitiesImport one or more mesh maps P.6.3.2

501

The user can choose whether to treat EarthVision fault polygons as boundary faults or sloping fault outlines. If the fault traces surround the map surface data they should be boundary faults, whereas they should be treated as sloping faults if they surround the fault surface data. Specify BOUNDARY or SLOPING at the end of the FAULTS line, e.g.:

See option P.2.3.5.3, “Chg flt typ” (see page 80), which allows individual faults to be changed.

6 Note that this method can be used to read fault trace data only, if the faults file is specified but no mesh file is defined.

7 The list of maps to be loaded consists of lines in the following form:

or (in the case of IRAP multi-grid files):

8 For IRAP multiple gridded files, the user can specify which layer is to be loaded into a particular map stratum. If the layer number is not defined in the list of maps, the START parameter is used to select the default file layer.

9 The units used for a particular map must be used for all strata associated with that map. The UNITS parameter is not required for strata belonging to an existing map.

10 If operations on mesh data are enabled, the OPERATION keyword is used to define a simple arithmetic operation on the input data (e.g. *-1 to invert the Z-axis). Note that this operation cannot include variables referring to other map names. To handle more complex calculations, use “Opr mesh” (P.2.5.4, see page 193) after loading the data.

FAULTS AUTO BOUNDARYFAULTS AUTO CLIP SLOPING

MAP mmm STRATUM sss MESH filename1 UNITS uuu & FAULTS filename2 OPERATION xxx

MAP mmm STRATUM sss MESH filename1 LAYER lll & UNITS uuu FAULTS filename2 OPERATION xxx


www.cadfamily.com

502 Map Utilities GRID Reference ManualImport Stratamodel data P.6.3.3

Import Stratamodel data P.6.3.3

Stratamodel

PurposeImport data from a Stratamodel file (type BINARY or SM4) and create mesh maps for one or more GRID model strata.

DescriptionThis option allows the user to load mesh data from a file output by Stratamodel’s SGM package, and create a set of mesh maps for one or more GRID strata. Data from several Stratamodel layers may be aggregated into one GRID model layer, as the file is read. If required, a control file can be read, to define the input data structure and specify the maps to be loaded.

The Stratamodel file should be of type BINARY (extension .glk) or SM4 (file extension .ldf).

The BINARY files contain header data describing the model dimensions and file contents, and arrays of cell attribute data for each layer in the model. The attribute data are identified by labels (i.e. names of up to 20 characters). A BINARY file may also contain depth data for fault surfaces and non-conformities.

The SM4 files contain data for each cell in the form

where up to 100 attributes such as cell thickness, porosity, etc., may be stored for each cell. The X and Y values must be present in the first two elements of each cell record. Other attributes can be identified by their position in the data record.

For the data to be loaded into GRID, one of the cell attributes must be used to identify the GRID stratum numbers for storing the cell data.

GRID will require the following parameters to be defined, before the Stratamodel data are loaded:

X Y Z attribute1 attribute2 attribute3 ....


www.cadfamily.com

GRID Reference Manual Map UtilitiesImport Stratamodel data P.6.3.3

503

Mesh map input parameters

For BINARY files, all parameters (except the angle of rotation) can be obtained automatically from the file header. For SM4 files, the user must supply all parameters.

The parameters may be read from a control file or defined interactively, as for the “Inp mesh” option (P.2.5.2, see page 180).

Stratamodel data input parameters

Up to 8 characters may be used for each attribute name, map name, or calculation variable. Up to 20 characters may be used for the attribute labels used with BINARY files.

The Stratamodel data input parameters may be read from the same external control file as the mesh map parameters, or defined interactively. When a BINARY file is loaded, the user is offered options to view the file header contents, and to print the header data to a text file. If required, a list of attribute names and labels can be obtained from the file header data.

TYPE File type (SM4 or BINARY)NROW Number of mesh rowsNCOL Number of mesh columnsXMIN Minimum X valueYMIN Minimum Y valueXMAX Maximum X valueYMAX Maximum Y valueANGLE Angle of rotation of mesh (decimal degrees, anticlockwise, positive from X-

axis)NULL Null value used for data in the fileFORMAT The Fortran format to be used for reading a text file.

SGMFILE Stratamodel data file, e.g. xxx.ldfRECLEN Length of data record for each cell (SM4 files only)ATTRIBUTE Names of attributes to be used for the GRID maps. For BINARY files, the

attribute label must be given. For SM4 files, the user must supply the position of each attribute in the input data record.

STRATUM Number for each GRID model stratum, with the Stratamodel attribute to be used for identifying input layers, and a list of the attribute values corresponding to each stratum.

MAP Names of maps to be created in GRID, together with the property attribute and units for each map, the averaging method to be used for aggregating data and the weighting function (if any).

CALCULATE Map properties and weighting functions may be calculated from one or more attributes, if required.

FAULTS Maps to be constructed from fault surface arrays. Depths may be stored as positive or negative.

UNCONFORMITIES

Maps to be constructed from non-conformity surface arrays. Depths may be positive or negative.


www.cadfamily.com


Before loading in any data, the program will check whether any of the maps exists already. If so, a warning is issued and the user may choose to abandon the data input.

Data input is performed in two phases: the input file is read in the first phase, and new GRID maps are constructed in the second phase. On systems where an interrupt facility is available, the user can break in and abandon data loading after data input has started. If a user interrupt occurs, data loading will end as soon as possible after reading the current record or after processing the current map.

On exit from this option, the user can choose to save the data input commands to an external control file.

Example control files

Control file to read BINARY fileThis example retains the ‘bottom up’ ordering of the Stratamodel sequence, and stores all depths as read (i.e. negative depths, decreasing downwards).

-- STRATAMODEL data file description-- GRID Version 94A Date: 19/11/93 Time: 18:00:56

TYPE BINARY--NROW Read from file--NCOL Read from file--XMIN Read from file--YMIN Read from file--XMAX Read from file--YMAX Read from file

ANGLE .000--NULL Read from file--FORMAT (Binary)-- STRATAMODEL data input options

SGMFILE fault4b.glk-- Attribute positions in STRATAMODEL file

ATTRIBUTE TOPS LABEL TOPSATTRIBUTE POROSITY LABEL POROSITY/D2ATTRIBUTE SEQUENCE LABEL SEQUENCE

-- Relationships between Grid strata and Stratamodel layersSTRATUM * SEQUENCE *

-- Grid maps to be createdMAP PORO PROPERTY POROSITY UNITS FRACTION AVERAGEMAP TOPS PROPERTY TOPS UNITS METRES MAXIMUM

-- Fault surfaces in STRATAMODEL fileFAULTS MAP FAULTS DEPTH NEGATIVE UNITS METRES

-- Unconformity surfaces in STRATAMODEL fileUNCONFORMITIES MAP UNCONF DEPTH NEGATIVE UNITS METRESEND


www.cadfamily.com


505

Control file to read SM4 fileThis example reads data into a GRID model with layers ordered ‘top-down’, and stores depths as positive values. The SM4 file contains cell centre depths and thicknesses, so cell tops are calculated as the data are read.

Notes1 When data are loaded into an existing map, any existing mesh or contour data will be

deleted.

2 The areal dimensions of each map stratum are defined according to the data being read. Other map parameters, such as contour intervals for drawing, will be set to appropriate defaults and may be modified by the user with the “Edt map” menu P.2 (see page 57).

3 The new maps are not drawn on the screen during processing, but can be edited later with “Edt map”.

-- STRATAMODEL data file description-- GRID Version CUR Date: 21/07/93 Time: 17:29:56

TYPE SM4NROW 99NCOL 99XMIN 50.0YMIN 50.0XMAX 9850.000YMAX 9850.000ANGLE .000NULL -99999.0FORMAT *

-- STRATAMODEL data input optionsSGMFILE faulta4.ldfRECLEN 9

-- Attribute positions in STRATAMODEL fileATTRIBUTE SEQUENCE POSITION 7ATTRIBUTE DEPTH POSITION 3ATTRIBUTE THICK POSITION 8ATTRIBUTE POROSITY POSITION 9

-- Relationships between Grid strata and Stratamodel layersSTRATUM 1 SEQUENCE 4STRATUM 2 SEQUENCE 3STRATUM 3 SEQUENCE 2STRATUM 4 SEQUENCE 1

-- Grid maps to be createdMAP PORO PROPERTY POROSITY UNITS FRACTION AVERAGE WEIGHT THICKMAP TOPS PROPERTY TOPZ UNITS METRES MINIMUMMAP ISOCH PROPERTY THICK UNITS METRES SUM

-- Calculation for TOP depthsCALCULATE TOPZ BY -(DEPTH + 0.5*THICK)END


www.cadfamily.com


4 For BINARY files, attributes are identified by their labels. Four special labels are recognized:

Each BINARY file contains a list of labels for any other attributes it contains. The labels can be up to 20 characters (including embedded blanks). The user should provide an attribute name of up to 8 characters (with no embedded blanks), for each attribute to be processed by GRID.

Note that the HEIGHT attribute may be undefined in BINARY files output from SGM Version 4.0 or later. If the HEIGHT attribute is used to construct any maps, GRID will issue a warning and the user may choose to abandon input.

5 For file type SM4, the ATTRIBUTE parameters are used to define all data values which can be obtained from a file record, except for the cell X,Y values, which will be taken automatically from record positions 1 and 2.

6 Relationships between GRID strata and Stratamodel layers are defined by the STRATUM parameters. The attribute used for identifying layers may be the Stratamodel layer number, the Stratamodel sequence number, or a special attribute created by the user in the Stratamodel data. The attribute should take integer values. The following options are available:

• Each STRATUM number corresponds to a single Stratamodel attribute number. This can be indicated in the control file by

STRATUM * attribute *

e.g. STRATUM * SEQUENCE *

• Each STRATUM number corresponds to a group of one or more attributes, indicated by STRATUM n attribute a1 a2 a3 or STRATUM n attribute a1 TO a2

e.g. STRATUM 1 SGMLAYER 1 2 3 4 5

or STRATUM 2 SGMLAYER 10 TO 16

The list of layers may be continued over more than one line, by entering a continuation symbol (&) at the end of each incomplete line.

Note that only one attribute may be used in a particular input session (e.g. do not try to identify GRID STRATUM 1 by SEQUENCE and STRATUM 2 by LAYERS).

7 GRID maps to be created from the Stratamodel data are defined by MAP parameters. In the control file, the MAP description is in the form:

MAP mmm PROPERTY ppp UNITS uuu method WEIGHT www

where:

TOPS Top depth for each cellSEQUENCE Stratigraphic sequence number from SGM modelHEIGHT Gross cell thicknessSGMLAYER Layer number from SGM model

mmm is a valid map name (e.g. TOPS).ppp is a mnemonic of up to 8 characters, corresponding to an ATTRIBUTE or

CALCULATE parameter.


www.cadfamily.com


507

The WEIGHT keyword is optional.

8 The PROPERTY to be loaded into a given map may be a simple attribute or a variable which can be computed from the cell attributes using a CALCULATE expression.

9 The units used for a particular map must be used for all strata associated with that map.

10 The following averaging methods are available for aggregating Stratamodel layers into a GRID stratum:

11 A weighting function may be specified for the arithmetic averaging, harmonic averaging or geometric averaging options. The WEIGHT may be a simple cell attribute or a variable which can be computed from the cell attributes using a CALCULATE expression.

The weighted averages are calculated as follows:

AVERAGE:

[EQ 9.11]

HARMONIC_AV:

[EQ 9.12]

GEOMETRIC_AV:

[EQ 9.13]

In each case, the summation is performed on a cell-by-cell basis for each GRID stratum, using data values selected according to the attribute given by the STRATUM parameters.

12 Any properties or weights which are not defined as simple cell attributes must be specified using the CALCULATE keyword. The calculation expression can be any valid arithmetic or logical expression (as used elsewhere in GRID), using constants, NULL and ATTRIBUTE mnemonics. A leading =, + or - sign may be present when using a simple arithmetic expression.

The expression may be continued over more than 1 line, by entering a continuation symbol (&) at the end of each incomplete line.

13 Fault surface maps can be loaded from a BINARY file by using the FAULTS keyword in the command file:

uuu is a valid map unit (e.g. METRES). method is the averaging method (see the following note).

www is a mnemonic of up to 8 characters, corresponding to an ATTRIBUTE or CALCULATE parameter.

SUM SummationAVERAGE Simple arithmetic averageHARMONIC_AV Harmonic averageGEOMETRIC_AV Geometric averageMINIMUM Use minimum valueMAXIMUM Use maximum value

FAULTS MAP mmm DEPTH ddd UNITS uuu

Weighted arithmetic mean Σ WEIGHT PROPERTY⋅( )Σ WEIGHT( )

-------------------------------------------------------------------=

Weighted harmonic mean Σ WEIGHT( )Σ WEIGHT PROPERTY⁄( )-------------------------------------------------------------------=

LOG Weighted geometric mean( ) Σ WEIGHT LOG PROPERTY( )⋅( )Σ WEIGHT( )

----------------------------------------------------------------------------------=


www.cadfamily.com


where:

Note that fault surface data consist of cell corner depths only.

14 Non-conformity surface data are similar to fault surface data and can be loaded using a command of the form:

where:

mmm is a valid map name (e.g. TOPS).ddd is the keyword POSITIVE or NEGATIVE.uuu is a valid map unit (e.g. METRES).

UNCONFORMITIES MAP mmm DEPTH ddd UNITS uuu

mmm is a valid map name (e.g. TOPS).ddd is the keyword positive or negative.uuu is a valid map unit (e.g. METRES).


www.cadfamily.com

GRID Reference Manual Map UtilitiesImport EarthVision data P.6.3.4

509

Import EarthVision data P.6.3.4

Earthvision

PurposeImport data from an EarthVision-GRID 3D exchange file and create mesh maps for one or more GRID model strata.

DescriptionThis option allows the user to load mesh data from an exchange file output by EarthVision and create a set of mesh maps for one or more GRID strata. If required, a control file can be read, to describe the input data and specify the maps to be loaded.

The EarthVision file should be of type EV-EXCHANGE. To load data from 2D gridded mesh files (type EV-2DGRID) use the “Mesh files” input option (P.6.3.2, see page 498), or read the data for an individual map using “Inp mesh” (P.2.5.2, see page 180).

The EarthVision exchange file contains the following data:

• Model range and projection description

• Layer geometry data for one or more layers, defined by TOP and THICKNESS values, together with fault traces

• Optional property data for one or more properties per layer (e.g. porosity).

GRID will require the following parameters to be defined, before the EarthVision data are loaded. The parameters can be defined interactively or by reading an external control file.

Mesh map input parameters

Usually, all parameters are defaulted to be read from the input file. However, the user may modify the XY range and mesh angle if necessary. (E.g. this might be required to convert between local coordinates and UTM coordinates, if different conventions have been used for the EarthVision and GRID models.)

TYPE File type (EV-EXCHANGE)NROW Number of mesh rowsNCOL Number of mesh columnsXMIN Minimum X valueYMIN Minimum Y valueXMAX Maximum X valueYMAX Maximum Y valueANGLE Angle of rotation of mesh (decimal degrees, anticlockwise, positive from

X-axis)NULL Null value used for data in the fileFORMAT The Fortran format to be used for reading a text file.PROJCHECK YES or NO to indicate whether the projection parameters and model area

are to be checked.


www.cadfamily.com

510 Map Utilities GRID Reference ManualImport EarthVision data P.6.3.4

EarthVision data input parameters

When the EarthVision exchange file is loaded, the user is offered options to view the file header contents, and to print the header data to a text file. If the PROJCHECK option is selected, the projection data will be checked for consistency with the GRID model. If the data are inconsistent, the user will be given options to write out a pro-forma run file to create a new GRID model and to choose whether to continue reading the data.

Before loading in any data, the program will check whether any of the maps exist already. If so, a warning is issued and the user may choose to abandon the data input.

On systems where an interrupt facility is available, the user can break in and abandon data loading after data input has started. If a user interrupt occurs, data loading will end as soon as possible after reading the current record or after processing the current map.

On exit from this option, the user can choose to save the data input commands to an external control file.

EVFILE EarthVision data file, e.g. exchange.dataFAULTS YES or NO, to indicate whether fault data should be read from the file. If

YES, add BOUNDARY or SLOPING to indicate whether closed fault polygons are to be treated as boundary faults or sloping faults.

FAULTNAMES CONNECT or IGNORE, to indicate whether to use fault name data from EarthVision, if available. If the CONNECT option is set, all fault traces with the same name will be concatenated. Otherwise, GRID will assign a unique name to each fault trace and any names found in the data file will be ignored.

LOCALFAULTS

MINOR or MAJOR, to indicate whether local fault segments from EarthVision should be set to minor or major segments in GRID. This option can only be used if fault types are given in the data file.

MAJORDOWN MINOR or MAJOR, to indicate whether MAJORDOWN fault segments from EarthVision should be set to minor or major segments in GRID. This option can only be used if major fault polygons are treated as sloping faults, not boundary faults.

ATTRIBUTE Names of attributes in the EarthVision file, with their identifying labels.STRATUM Number for each GRID model stratum, with the corresponding

EarthVision layer number.MAP Names of maps to be created in GRID, together with the property attribute

and units for each map. The user may also define an operation to be performed on the raw data (e.g. to multiply by a constant).


www.cadfamily.com


511


Notes• When data are loaded into an existing map, any existing mesh or contour data will be

deleted.

• The areal dimensions of each map stratum are defined according to the data being read. Other map parameters, such as contour intervals for drawing, will be set to appropriate defaults and may be modified by the user by means of the “Edt map” menu (P.2, see page 57).

• The new maps are not drawn on the screen during processing, but can be edited later using “Edt map”.

• The FAULTS option allows the user to choose whether to read the fault trace data associated with each top or thickness layer. By default, the option is YES (read fault traces). If, for some reason, the fault traces are not required, select FAULTS NO.

• By default, fault polygons will be treated like SLOPING faults. This is appropriate if the polygons enclose fault regions. If the polygons enclose parts of the surface map, they should be treated as BOUNDARY faults. The fault types can be modified individually after loading, using "Chg flt typ" (P.2.3.5.3, see page 80).

-- EARTHVISION data file descriptionTYPE EV-EXCHANGE

--NROW Read from file--NCOL Read from file--XMIN Read from file--YMIN Read from file--XMAX Read from file--YMAX Read from file

ANGLE .000--NULL Read from file--FORMAT (Binary)

PROJCHECK YES-- EARTHVISION EXCHANGE FILE data input optionsEVFILE exchange.dataFAULTS YES SLOPINGFAULTNAMES CONNECTLOCALFAULTS MINORMAJORDOWN MINOR-- Property attributes in EARTHVISION fileATTRIBUTE TOP LABEL TOPATTRIBUTE THICK LABEL THICKNESS-- Relationships between GRID strata and EARTHVISION layersSTRATUM * EVLAYER *-- GRID maps to be createdMAP TOPS PROPERTY TOP UNITS FEETEND


www.cadfamily.com

512 Map Utilities GRID Reference ManualImport EarthVision data P.6.3.4

• Versions of EarthVision released from 1997 onwards may output additional fault data, defining the fault names and fault types. EarthVision fault types are 'MAJOR', 'LOCAL VF' and 'LOCAL NVF'. By default, if these data are available, GRID will concatenate fault traces with the same fault names, and the LOCAL faults will consist of MINOR fault segments.

The FAULTNAMES option can be set to IGNORE the EarthVision names. The LOCALFAULTS option can be used to set local fault traces to MAJOR fault segments.

• An additional fault type, ’MAJORDOWN’, can be found in EarthVision output from end 1998. This corresponds to the downthrown side of a major fault. If the fault polygons are treated as sloping faults, GRID will set the MAJORDOWN traces to be MINOR fault segments, by default. The MAJORDOWN option can be used to indicate that these should be treated as MAJOR segments if necessary.

If fault polygons are treated as boundary faults, the MAJORDOWN traces will always be treated as MAJOR segments.

• The EarthVision file header contains a list of labels for the property attributes in the file. The user should provide an attribute name of up to 8 characters (with no embedded blanks), for each attribute to be processed by GRID. The control file command to define an attribute is in the form:

where:

To read in tops and thickness values, supply attribute names corresponding to labels TOP and THICKNESS.

• Relationships between GRID strata and EarthVision layers are defined by the STRATUM parameters. Note that only one EarthVision layer can be put into a GRID stratum, and no averaging is performed when the data are imported. By default, the GRID strata correspond exactly to the layer numbers. However, the user may choose to specify the layer numbering scheme exactly, or may choose to load data only from particular layers.

In the control file, the STRATUM command takes the following form:

• GRID maps to be created from the EarthVision data are defined by MAP parameters. In the control file, the MAP description is in the form:

where:

ATTRIBUTE aaa LABEL lll

aaa is the local attribute name to be used in GRIDlll is the EarthVision property label

- Each STRATUM number corresponds to an EarthVision layer number:STRATUM * EVLAYER *- User-defined STRATUM numbersSTRATUM 1 EVLAYER 1

MAP mmm PROPERTY ppp UNITS uuu OPERATION xxx

mmm is a valid map name (e.g. TOPS).ppp is a mnemonic of up to 8 characters, corresponding to an ATTRIBUTE

name.


www.cadfamily.com


513

The OPERATION keyword is optional. It could be used, for example, to perform a units conversion or to invert the Z-axis.

• The depth values transferred in this exchange file are positive increasing downwards, which is the usual convention in GRID, and so they do not need to be inverted.

uuu is a valid map unit (e.g. METRES).xxx is an operation to be performed on the raw data (e.g. *-1)


www.cadfamily.com

514 Map Utilities GRID Reference ManualImport / export DXF files P.6.3.5

Import / export DXF files P.6.3.5

DXF files

PurposeImport / export data via DXF files.

DescriptionThe following options are available for DXF data:

DXF (Drawing Interchange Format) files are used for transferring data between Autodesk’s AutoCAD system and other CAD programs. The facilities provided in GRID allow the user to read vector data (contours, fault traces and features), well positions and mesh XYZ data from an ASCII DXF file. The “Out DXF” option writes out data in DXF format.

The “Return” option returns the user to the “Import maps” menu. Each of the other options is described in the following sections.


Option Function

1 Return

2 Inp DXF

3 Out DXF

Import DXF data

Export DXF data


www.cadfamily.com

GRID Reference Manual Map UtilitiesImport DXF data P.6.3.5.2

515

Import DXF data P.6.3.5.2

Inp DXF

PurposeImport DXF data for one or more map strata.

DescriptionThis option allows the user to load data from one or more DXF files. If required, a control file can be read, to define the input data structure and specify the maps to be loaded. For contours or mesh data, the user may also define a simple arithmetic operation to be performed on the raw data (e.g. multiply by a constant).

This option is for ASCII DXF files only. The data items which GRID recognizes are limited to those needed for input, and GRID will not attempt to interpret colours, line styles, etc. These facilities are appropriate for importing maps digitized using a CAD package, for example. GRID cannot read binary DXF files or DXB files.

ASCII DXF files contain data arranged in pairs, consisting of an integer group-code followed by a data value on the next line. GRID recognizes the following group-codes:

GRID expects that the data to be read will be preceded by the following lines to indicate the start of the entities section:

Entity types recognized by GRID are POLYLINE, POINT and TEXT. Each polyline is made up of a set of VERTEX entities. Different types of data (e.g. contours, faults) are identified by the DXF layer-id, which should be defined for each entity, as explained below. For additional information on DXF files, see the AutoCAD Reference Manual, or refer to Graphics File Formats (David C. Kay and John R. Levine, Windcrest/McGraw-Hill, 1992).

The parameters defining the input data structure may be read from a control file or defined interactively. The first panel defines mesh size and position parameters, as for the “Inp mesh” option (P.2.5.2, see page 180). These data are not significant unless mesh XYZ data are to be loaded. Otherwise, they can be left at default values.

0 Start of data section or entity1 Text value (e.g. well name)8 Layer identifier10 X-coordinate20 Y-coordinate30 Z-coordinate70 For a polyline entity, indicates whether line is closed

0SECTION

2ENTITIES


www.cadfamily.com

516 Map Utilities GRID Reference ManualImport DXF data P.6.3.5.2

The user will then be prompted to choose whether to load the following entities and enter the DXF layer-id for each type of entity to be read:

Contour and mesh XYZ data cannot be loaded at the same time, so selection of contour input deselects mesh input and vice versa. The DXF layer-id is used to identify different types of data, so a unique layer-id must be used for each entity type.

Further prompts are issued for the user to choose whether map operations are required and whether the data are to be clipped to the model area and/or thinned as they are read.

The list of maps to be loaded may be read from the same control file as the input structure parameters or defined interactively. The user may edit this list before reading the data.

Before loading in any data, the program will check whether any of the maps exists already. If so, a warning is issued and the user may choose to abandon the data input. If polyline data or well data are loaded, the user can choose to delete or keep any existing data. (Mesh data will overwrite any existing mesh.)

Map units and map operations are defined in the same way as for the mesh map import option “Mesh files”, P.6.3.2 (see page 498).

On systems where an interrupt facility is available, the user can break in and abandon data loading after data input has started, by hitting the escape key <ESC>. If a user interrupt occurs, data loading will end as soon as possible after processing the current map.

After a group of maps has been loaded, the user can choose to save the commands to an external control file.

• Contours (POLYLINE data)• Mesh XYZ data (POINT data)• Fault traces (POLYLINE data)• Well positions (TEXT data)• Feature lines (POLYLINE data)


www.cadfamily.com

GRID Reference Manual Map UtilitiesImport DXF data P.6.3.5.2

517

Example control fileExample control file to read DXF data:

Notes• The areal dimensions of each map stratum are defined according to the data being read.

Other map parameters, such as contour intervals for drawing, will be set to appropriate defaults and may be modified by the user by means of the “Edt map” menu.

• The new maps are not drawn on the screen during processing, but can be edited later using “Edt map”.

• If no mesh data are to be loaded, the parameters NCOL, NROW, etc. can be defaulted and omitted from the control file.

• The DXFDATA command identifies the entities to be loaded:

where:

The THIN and CLIP keywords may be omitted if thinning or clipping are not required. (These options do not affect mesh input.)

-- DXF data file description-- GRID Version 96A Date: 2/08/95 Time: 14:32:39-- (NB: mesh description needed for XYZ mesh only)

TYPE DXFNROW 20NCOL 20XMIN 540000.0YMIN 5995000.XMAX 570000.0YMAX 6030000.ANGLE .000NULL 1000000.

--FORMAT (ASCII)-- Commands for loading DXF ASCII data files

DXFDATA CONTOURS YES FAULTS YES &WELLS NO FEATURES YES THIN CLIP

DXFLAYER CONTOURS LAYERNAME CONTOURS-1DXFLAYER FAULTS LAYERNAME FAULTS-1DXFLAYER FEATURES LAYERNAME FEATURES-1MAP XXX STRATUM 1 DXF XXX.DXF UNITS METRES OPERATION *-1.MAP YYY STRATUM 1 DXF YYY.DXF UNITS FEETEND

DXFDATA CONTOURS [YES/NO] FAULTS [YES/NO] &WELLS [YES/NO] FEATURES [YES/NO] THIN CLIP

YES/NO enables or disables inputTHIN indicates polylines are to be thinnedCLIP indicates data are to be clipped to the model area


www.cadfamily.com

518 Map Utilities GRID Reference ManualImport DXF data P.6.3.5.2

• The DXFLAYER command defines the layer name to be used for each entity type. The use of layers in the DXF file format does not correspond to map strata in GRID. This input facility assumes that layer-ids can be used to identify different entity types in the DXF file. The above example shows layer names such as CONTOURS-1, but layer numbers can be used.

• The list of maps to be loaded consists of lines in the following form:

• If operations on contour or mesh data are enabled, the OPERATION keyword is used to define a simple arithmetic operation on the input data (e.g. *-1 to invert the Z-axis). Note that this operation cannot include variables referring to other map names.

MAP mmm STRATUM sss MESH filename1 UNITS uuu & FAULTS filename2 OPERATION xxx


www.cadfamily.com

GRID Reference Manual Map UtilitiesExport DXF data P.6.3.5.3

519

Export DXF data P.6.3.5.3

Out DXF

PurposeExport data from a map stratum to a DXF file.

DescriptionThis option allows the user to write out data from a selected map stratum to an ASCII DXF file. Contours, mesh XYZ points, faults, well names and features can be exported. This facility is intended for data transfer purposes only and is not suitable for sending a complete map display to a drawing package.

The user is prompted for the root name of the file to be opened for output. The output file will be given the name ‘root.DXF’.

The user is then prompted to choose whether to clip the data to the model area. (Clipping can be performed for polylines and well data, but does not apply to mesh XYZ points.)

By default, DXF file output is restricted to the ENTITIES section only. The user can override this in response to the prompt:

GRID will then output a skeleton HEADER, TABLES and BLOCKS sections at the start of the DXF file. (This may be necessary for export to some external packages.) In either case, the file will start with comments (group-code 999) identifying the GRID version, date and time and the map stratum. If mesh XYZ data are exported, further comments will show the areal range and number of rows and columns.

The DXF layer-id will be used to identify different data types written to the file. In addition, the user can choose to write a colour index to distinguish contour, fault and feature polylines.

Depending on the data found in the map stratum, the user is prompted to choose whether to write it to the file, with further prompts to define the layer-id and colour index:

Write ENTITIES section only ? (Y/n)

Write contour lines to DXF file ? (Y/n)Enter DXF layer-id for contours (1)Enter colour index for contours (6)Write mesh XYZ points to DXF file ? (Y/n)Enter DXF layer-id for mesh (1)Write fault lines to DXF file ? (Y/n)Enter DXF layer-id for faults (2)Enter colour index for faults (7)Write well positions to DXF file ? (Y/n)Enter DXF layer-id for wells (3)Write feature lines to DXF file ? (Y/n)Enter DXF layer-id for features (4)Enter colour index for features (2)


www.cadfamily.com

520 Map Utilities GRID Reference ManualExport DXF data P.6.3.5.3

The layer-id may be defined as an integer or a character string (e.g. CONTOURS). By default, GRID uses numbers 1,2,3,4 as shown above. Note that GRID requires different layer names for different data types, when reading a DXF file.


www.cadfamily.com

GRID Reference Manual Map UtilitiesExport maps P.6.4

521

Export maps P.6.4

Export maps

PurposeExport data from one or more maps.

DescriptionThe following options are available for exporting map data:

The "Return" option returns the user to the "Map utils" menu.

Option 2 allows the user to export mesh data and the associated fault data from one or more mesh maps.

Option 3 allows the user to export fault data from one or more maps, which could be either mesh maps or contour maps.

When either option 2 or option 3 is selected GRID checks all map strata to see if they contain data of the required type. For models with a large number of maps this make take a little while.

Mesh data can be output in any of the formats used in option P.2.5.8 "Out mesh" (see page 205).

Fault data can be output in any of the formats used in option P.2.3.7 "Out flt" (see page 98).

The user selects appropriate formats then constructs a list of map strata. The formats and map names are then displayed on the screen and can be edited.

Separate output files are created for the mesh data and the fault data for each map stratum selected. Unique file names are constructed by concatenating a user-supplied root with the map name, stratum number and a suffix depending on the type of file. For example, if the root is ’OUT’ then the output files containing the data from stratum 1 of map ’MAPNAME’ will be:

’OUT_MAPNAME_01.GCT’ or ’OUT_MAPNAME_01.UGC’

for the mesh data, depending on whether the file is formatted, and

’OUT_MAPNAME_01.FLT’

for the fault data.

If required, GRID will write a control file that can be used to re-import the data using option P.6.3.2 "Mesh files" (see page 498). However, if the meshes are inconsistent, e.g. if the number of columns or rows varies, then it may not be possible to re-import all the mesh files using a single control file. In this case some entries in the control file will be commented out and GRID will warn the user to edit the control file before using it.


Option Function

1 Return

2 Out msh maps

3 Out flt maps

Export data from mesh maps

Export fault data


www.cadfamily.com

522 Map Utilities GRID Reference ManualExport maps P.6.4

The control file also provides a useful record of the data that has been output and contains warnings about any inconsistencies in the output files. If a control file is not required these warning messages can still be saved to a file.


www.cadfamily.com

GRID Reference Manual Map UtilitiesCopy map data P.6.5

523

Copy map data P.6.5

Copy maps

PurposeCreate new map strata by copying existing map data.

DescriptionThe user is prompted for the map name and stratum to be copied and the destination map name and stratum, which must not exist already.

For example, TOPS(1) can be copied to new map stratum TOPS(2) or to NEW(1).

Enter ’*’ instead of a stratum number to be copied, to copy all strata from the existing map. In this case, the user is not prompted for the destination stratum. If any of the destination strata exist, the copy operation will be abandoned.

For example, TOPS(*) can be copied to NEW. This will copy TOPS(1) to NEW(1), TOPS(2) to NEW(2) etc.


www.cadfamily.com

524 Map Utilities GRID Reference ManualProcess well data P.6.6

Process well data P.6.6

Well data

PurposeAccess options for processing well data.

DescriptionThe following options are available:

The “Return” option returns the user to the Primary menu. Each of the other options is described in the following sections.


Option Function

1 Return

2 Inp wel trj

3 Out grd conn

4 Del well trj

5 Inp CLAN

Input well trajectory data

Output well connection data

Delete well trajectory data

Input Clan data


www.cadfamily.com

GRID Reference Manual Map UtilitiesInput well trajectory data P.6.6.2

525

Input well trajectory data P.6.6.2

Inp wel trj

PurposeRead in well trajectory data to be used for identifying well connections in a simulation grid.

DescriptionData may be input from files of type SINGLEWELL or MULTIWELL. The user is prompted for the file description. If required, a control file can be read, defining the input data structure and the files to be loaded.

The following parameters are required:

In addition to the file description parameters, the user can specify how many of the input data values are to be stored, allowing the data to be thinned before it is used to compute the well connection positions. Options are:

FILETYPE SINGLEWELL (each file contains data for one well) or MULTIWELL (files may contain data for several wells, separated by markers or with the number of data points specified for each well).

NULL The null value used for data in the file.XYUNITS The units used for X,Y position data (FEET, METRES or DEGREES).

If DEGREES are used, a projection must be defined and the X, Y positions should be in decimal degrees.

XYOFFSET YES if X,Y positions in deviation survey are offsets from the wellhead position or NO if the X, Y positions are absolute values.

RECLEN Length of data records for well trajectory (i.e. number of attribute parameters).

FORMAT The Fortran format to be used for reading the data records.START The position of the first line of data

(number of lines from top of file or from start of current well). ENDPOINT For MULTIWELL files the end of data for a well must be indicated by a

marker value after the last valid data for the well, or by the number of points for the well being given in the header data.

WELLNAME For MULTIWELL files, the name of the well is read from the file header (user specifies LINE and ITEM position). For SINGLEWELL files, the user may choose to enter the well name associated with each file. If no well names are given, the user can enter a default name root, to be used to set up well names.

TOPX, TOPY X,Y positions of the wellhead.

These may be read from the file header, entered as user data (for SINGLEWELL files), or defaulted to the first X,Y position read from the file.

REFDEPTH Reference depth for depth values.

This may be read from the file header, or defaulted to zero.


www.cadfamily.com

526 Map Utilities GRID Reference ManualInput well trajectory data P.6.6.2

• Store all data:

• Store data at specified storage interval (i.e. every nth point):

• Store data if spacing between values of a selected attribute exceeds a given minimum value, sss. Note that aaa is an attribute read from the data file, not a calculated value.

The user is also prompted to enter the names of the data attributes to be read, and their file positions and the units used. By default the program expects 4 special attributes to define the well trajectory: XPOS, YPOS, MD and TVD. These define the X,Y position, Measured Depth and True Vertical Depth. Other named attributes can be read, e.g. for use in calculations.

If an attribute is defined with no position in the data file, it can be defined using a CALCULATE command. Variables used for calculation may include input data attributes and also the keyword REFDEPTH.

Finally, the user is prompted for a list of input files to be loaded. If these are SINGLEWELL files and the WELLNAME, TOPX, TOPY or REFDEPTH values are user-defined, these parameters must be entered for each well data file.

The data are loaded into a model file with name in the form model.ext, where ‘.ext’ is .GWELL or .GWL for unformatted files, or .FWELL or .FWL for formatted files. These data can be used to find grid block connections in option P.6.4.3, “Out grd conn” (see page 521).

STORAGE ALL

STORAGE INTERVAL n

STORAGE ATTRIBUTE aaa SPACING sss


www.cadfamily.com

GRID Reference Manual Map UtilitiesInput well trajectory data P.6.6.2

527

ExampleExample input control file:

Notes• If well data have already been loaded into GRID, the user can choose whether to overwrite

old wells.

• Wells containing less than two depth values will be treated as vertical wells extending across the entire reservoir, when searching for well connections in “Out grd conn”.

• Measured depth is expected to increase along the wellbore. If inconsistent depths are found, the user will be warned and any data points which appear incorrect will be ignored when searching for well connections. (In some cases, these may be due to blank lines being read as lines of zero values, depending on the input format.)

• If necessary, XPOS and YPOS can be calculated from the input data instead of being loaded directly. Data in (R, THETA) form can be processed where THETA takes an angular value using the special units type ANG_DEG (for degrees) or ANG_RAD (for radians).

-- Well data file description-- GRID Version 95B Date: 15/04/95 Time: 12:56:06

FILETYPE MULTIWELLNULL 1000000.XYUNITS METRESXYOFFSET NORECLEN 4FORMAT *START 3ENDPOINT MARKER -999.0000WELLNAME HEADER LINE 2 ITEM 3TOPX HEADER LINE 2 ITEM 1TOPY HEADER LINE 2 ITEM 2REFDEPTH 20.0

-- Storage of input data values after readingSTORAGE ALL

-- Attributes in well data fileATTRIBUTE XPOS POSITION 1 UNITS METRESATTRIBUTE YPOS POSITION 2 UNITS METRESATTRIBUTE MD POSITION 3 UNITS FEETATTRIBUTE DEPTH POSITION 4 UNITS FEETATTRIBUTE TVD CALCULATE UNITS FEET

-- Attribute calculationsCALCULATE TVD BY DEPTH - REFDEPTH

-- List of input files for well dataFILE test.data

END


www.cadfamily.com

528 Map Utilities GRID Reference ManualInput well trajectory data P.6.6.2

For example, the following options could be used for the case where THETA is measured as an azimuthal angle increasing clockwise from the X-axis:

-- Define X/Y position as offset from wellheadXYOFFSET YES.....-- Attributes in well data fileATTRIBUTE R POSITION 1 UNITS METRESATTRIBUTE XPOS CALCULATE UNITS METRESATTRIBUTE YPOS CALCULATE UNITS METRESATTRIBUTE THETA POSITION 2 UNITS ANG_DEG.....-- Calculations for XPOS, YPOSCALCULATE XPOS BY R*COS(THETA)CALCULATE YPOS BY R*SIN(THETA)


www.cadfamily.com

GRID Reference Manual Map UtilitiesOutput well connection data P.6.6.3

529

Output well connection data P.6.6.3

Out grd conn

PurposeFind possible well connections in a simulation grid.

DescriptionThe user is prompted for the simulation grid name. Data can be constructed for ECLIPSE input (i.e. WELSPECS and COMPDAT data) or for input to SCHEDULE.

Well data are taken from the .GWELL file created by reading well trajectory data via option P.6.6.2, “Inp well trj” (see page 525).

For ECLIPSE data, a file with extension .GRDECL is produced. The program identifies grid blocks through which each well passes and outputs pro-forma WELSPECS and COMPDAT keywords (or WELSPECL and COMPDATL for local grids). Connections with inactive grid blocks are ignored by default.

For Schedule data, a file with extension .TRJ is produced, defining for each well:

• Well name, wellhead I and J positions

• For each grid block on the well trajectory:

• I, J, K position

• Measured depth, X-position, Y-position and TVD at the point where the well enters the grid block.

• Measured depth, X-position, Y-position and TVD at the point where the well exits the grid block.

• Face where well exits the grid block (X-, X+, Y-, Y+, Z-, Z+ or NONE).

• Grid block permeability values for each direction (i.e. PERMX, PERMY and PERMZ).

• Grid block net-to-gross value.

The user is prompted to choose whether to output well exit data, permeability and NTG values and well entry/exit faces. If measured depths are not available, the measured length within the grid block is output.

The user may also choose whether to output connection data for all cells or for active cells only. In either case, connections which have zero length (e.g. due to pinch-outs) will be omitted from the output file. The minimum length cut-off for connections can be set to a value greater than zero if required.

If a grid contains local refinements, connections can be generated for all grids, for the global grid only or for all or selected LGRs. The user can choose whether to output connections found in global grid cells which contain local refinements. If radial LGRs are present, the user can choose whether to adjust well trajectories so that local connections are defined in the centre of the radial grid (regardless of the exact well position).


www.cadfamily.com

530 Map Utilities GRID Reference ManualOutput well connection data P.6.6.3

Well connection data can also be output in a format suitable for input into ARCO’s Acres simulator. This option can be accessed by typing "A" when responding to the prompt:

GRID will use an alternative prompt:

if the ACRES flag is set to TRUE in the GRID section of the configuration file.

Do you require ECLIPSE or SCHEDULE data ? (E/s)

Do you require ECLIPSE, SCHEDULE or ACRES data ? (E/s/a)


www.cadfamily.com

GRID Reference Manual Map UtilitiesDelete well trajectory data P.6.6.4

531

Delete well trajectory data P.6.6.4

Del well trj

PurposeDelete well trajectory data for one or more wells.

DescriptionThis option deletes well data from the .GWELL file created by reading well trajectory data via option P.6.6.2, “Inp well trj” (see page 525).

The user can choose to delete all wells, enter the names of wells to be deleted or select wells from a list:

The number of wells chosen for deletion will be reported. The operation can be abandoned at this stage by responding ‘N’ to the prompt:

Otherwise the well trajectory data will be deleted and the .GWELL file will be updated.

If the well trajectory display is enabled but all wells are deleted, it will be switched off (see “Sho well trj”, menu D.7.8.7, page 615).

You can delete All wells, enter Names or Select from list...&Enter delete option (a/n/S)

Do you wish to continue ? (Y/n)


www.cadfamily.com

532 Map Utilities GRID Reference ManualInput CLAN P.6.6.5

Input CLAN P.6.6.5

Inp CLAN

PurposeInput a fixed format Clan file containing well names, positions and values for a multi-strata map.

DescriptionThis facility allows the user to read a fixed format Clan file. The header record should contain two integers (in free format), denoting the number of map strata and the maximum number of wells on any single stratum. Each subsequent record in the file should contain a stratum number, well name, well value, Latitude & Longitude. The format used to read the remainder of the file is (I3, A8, E12.5, 2F10.5).

On selecting this option, the user is prompted for the filename to be read and a new map name for storing the Clan data. Checks are made to ensure that the maximum number of strata in the file is within the maximum number of model strata, and that the maximum number of wells does not exceed the limit allowed for any single map stratum.


www.cadfamily.com

GRID Reference Manual Change SettingsIntroduction

533

Chapter 10Change Settings

IntroductionThe “Chg settings” menu P.7 provides options for changing various default program settings and also allows debug switches to be set as an aid to programmers.

Note that default settings can be changed automatically on entry to the program, by including the relevant commands in a run file named PROFILE.RF.

I/O FormatsThe usual default formats used by GRID are:

• Internal model files are formatted, unless the default has been set to unformatted in the Configuration file.

• Temporary scratch files are unformatted.

• The I/O format for plot files is determined by the site-specific defaults for the device (normally defined in the Configuration file).

• The I/O format used for external data files, for map data, etc., is fixed according to the file type (see sections on data input and output for details).

The settings for internal model files, scratch files and plot files may be changed using menu options. Note that separate switches are used for model file input and output, allowing file formats to be changed from within the program.

Use of formatted model files allows data to be transferred between different computer systems. However, use of unformatted model files is recommended as a means to reduce disk space usage and speed up program file I/O.


www.cadfamily.com

534 Change Settings GRID Reference ManualIntroduction

Note that the default model file format can be set to unformatted by including the following section in the Configuration file:

Please contact SIS customer support if you require further advice on file formats.

XY plane display refreshBy default, GRID refreshes the screen automatically whenever the XY plane is changed.

For users with slow graphical terminals, option P.7.7, “Tog XY redrw” has been added, to allow the user to revert back to the old method of redrawing areal displays only when sloping coordinate lines are in use.

Workspace usageA ‘debug’ facility is available, to allow the user to check workspace availability and usage (see Menu option P.7.2.6, “Wkspace dbg”, page 536).

Selecting workspace debug level 1 gives a screen display showing the maximum workspace dimensions available, the current workspace usage and the maximum usage during the program session. The upper limits on certain arrays (e.g. maximum number of contours on a map) are also displayed.

Debug level 2 also writes these values to a file, GRID.DBG. Usage details will be added to the print-out whenever this option is reselected and updated again on exit from the program. To switch off all workspace debug output, select debug level 0.

This information may be useful if it is necessary to redimension GRID to allow for larger models. Please contact SIS customer support if you require assistance with program dimensioning.

SECTION GRIDFORMATTED FALSE


www.cadfamily.com

GRID Reference Manual Change SettingsIntroduction

535

The following example shows the type of information printed in the GRID.DBG file:

Numerical workspace (bytes):Available = 40000000 ( = NDYNB)Reserved = 1434132Current usage = 1434132Maximum usage = 1434132

Character workspace (8-byte words):Available = 40000 ( = NDYNZ)Reserved = 1801Current usage = 1801Maximum usage = 1801

Array size limits for common data:Max points on any line = MXPNT = 10000Max maps = MXMAP = 100Max strata = MXSTR = 100Max captions on a map = MXCPF = 5000Max contours on a map = MXCTF = 5000Max faults on a map = MXFTF = 5000Max features on a map = MXFEF = 5000Max wells on a map = MXWLF = 5000Max zones on a map = MXZNF = 500

Max simulation grids = MXGRD = 50Max grid control lines = MXCTL = 50Max grid region arrays = MXREG = 50Max property arrays = MXPRP = 50Max refined grids = MXREF = 100Max solution arrays = MXSOL = 50Max solution timesteps = MXSEQ = 1000

Max well trajectories = MXGWL = 500

Max surveys = MXSVY = 40Max vectors/horizons = MXSHV = 100Max survey shot lines = MXSHT = 5000


www.cadfamily.com

536 Change Settings GRID Reference ManualChange settings P.7

Change settings P.7

Chg settings

PurposeChange the default program settings.


The options on this menu may be selected before a model is loaded in order to set switches which affect the operation of the program.

It is recommended that the user defines a PROFILE.RF to select the required menu options, thus ensuring that they are selected every time the program is executed. (See the section on Run files.)

Table 10.1 Menu P.7

Option Function

1 Return

2 Set debug

3 Set IO fmt

4 Tog bell

5 Tog slp crds

6 Tog XY redrw

7 Tog dep chk

8 Tog crd chk

Set debug switches

Set IO format

Toggle bell on/off

Toggle sloping coordinate lines

Toggle automatic redrawing of XY planes

Toggle grid node depth checking

Toggle coordinate line checking


www.cadfamily.com

GRID Reference Manual Change SettingsChange settings P.7

537

This menu can also be entered using the hot key “C” from lower levels of the program. However, the options to set I/O formats can only be used from the Primary menu level.

Option 2 allows debug switches to be set for various sections of the program. These are for programmer use only and are not intended for general use, except for the “Wkspace dbg” option P.7.2.6, which may be used to check the maximum workspace allocation and usage.

Option 3 may be used to change the formats of the internal files between formatted and unformatted. The DEFAULT is formatted. Users with large datasets may find it useful to switch to unformatted, to reduce storage requirements and increase the speed of I/O.

Option P.7.3.5 on this menu may be used to change between formatted and unformatted plot files. Unformatted plot files have the advantage of being much smaller in file size.

Option P.7.3.7, “Set tmpdir”, allows the user to redirect scratch files on UNIX systems to a specified directory, in cases where the required scratch space for the current GRID session exceeds the amount available on the default temporary disk. (For example, on RS6000 systems the usual default directory is /tmp. This can be changed, if applicable, by setting the external environment variable TMPDIR, by setting the CONFIG file keyword TMPDIR in the SYSTEM section, or with “Set tmpdir” on this menu.) Setting the directory to ‘.’ will use the current directory. If an invalid directory is specified, the scratch file directory reverts to the system-specific default.

Note that any existing scratch files will remain open after selecting option P.7.3.7: it may be necessary to clear workspace by use of menu P.8, “Clr wrkspc” (see page 540), to gain full advantage of this option. If in doubt, exit from the program and restart

Option 4 allows the user to toggle the BELL on or off. If the BELL is on, bleeps will be issued at certain stages during digitizing and map interpolation.

Option 5 enables the prompts for moving top or bottom of coordinate lines. If this option is selected the user is also asked whether a correction factor is to be applied to sampled thickness values. When sampling depths and thicknesses on sloping coordinate lines, better results may be obtained by iteration. The user can choose to iterate up to 10 times, resampling any grid nodes which move by more than a specified minimum node movement.

The user is asked whether an over relaxation parameter R should be used. Convergence of the iterations can sometimes be speeded up by using a relaxation parameter 1 <= R < 2, although this may cause the sampling to diverge. Occasionally the iterative procedure is not convergent, e.g. if the map surface is steeper than the coordinate lines. In these cases using a smaller value of R, 0 < R <= 1 will help convergence. The default value is R = 1.

(This option will also switch on automatic redrawing of the grid when moving between areal displays, even if it has been turned off via option 6.)

Option 6 switches off automatic redrawing of XY planes. For users with older graphical terminals, the refresh time required to redraw the XY display can be an annoyance. If automatic redrawing is toggled off, the display is not redrawn when the XY layer is changed, unless sloping coordinate lines have been enabled (or the “Refresh” option is taken).


www.cadfamily.com

538 Change Settings GRID Reference ManualChange settings P.7

Option 7 switches off depth checking for grid nodes. When this option is enabled, grid node depths will be checked whenever any changes are made to depths or thicknesses, to ensure that there are no overlaps between layers.

Option 8 switches off grid coordinate line checking. When this option is enabled, movement of grid coordinate lines will be restricted to prevent lines from crossing.


www.cadfamily.com

GRID Reference Manual Clear WorkspaceIntroduction

539

Chapter 11Clear Workspace

IntroductionThe “Clr wrkspc” menu options are used to clear data which are currently loaded in the program workspace arrays. This may be necessary to allow data to be reloaded from files or to make space for further edits.

Note that this option does not delete data from the model data files. However, if a map, grid or survey is cleared from the current session without saving the data on disk, the most recent changes will be lost. (This means that, if problems occur during an editing session, the changes can be abandoned by exiting to the top menu without saving the data, clearing the workspace and then re-entering the edit menu. The unchanged data will then be reloaded from disk.)


www.cadfamily.com

540 Clear Workspace GRID Reference ManualClear workspace P.8

Clear workspace P.8

Clr wrkspc

PurposeClear loaded data from the program work-space, to be reloaded from disk. This option will NOT delete any data from the model.

If a map, grid or survey has been edited during the current session, it is important to ensure that is has been saved on disk before it is cleared, if it is required to keep the edits.


Option 2 effectively restarts the program, since all data is cleared from the program workspace on confirmation by the user.

Option 3 will prompt the user for a map name. The user may select a single stratum or clear all the loaded strata for the given map.

Option 4 will clear the current simulation grid and redraw the screen without the grid.

Option 5 will clear the current survey and redraw the screen without the shot lines.

Option 6 will clear any well trajectory data loaded for use in menu P.6.6, “Well data” (see page 524).

Table 11.1 Menu P.8

Option Function

1 Return

2 Clr model

3 Clr maps

4 Clr grid

5 Clr survey

6 Clr wel dta

Clear model

Clear maps

Clear grid

Clear survey

Clear well data


www.cadfamily.com

GRID Reference Manual Run FilesRun files R

541

Chapter 12Run Files

Run files R

R

PurposeAccess run file options.


Run files can be used to log or execute menu selections and prompt responses from a command file.

Table 12.1 Menu R

Option Function

1 Return

2 Exe file

3 Opn file

4 Cls file

5 Set path

6 Set option

7 Sho crd pos

Execute file

Open file

Close file

Set path

Set option

Show coordinate position


www.cadfamily.com

542 Run Files GRID Reference ManualRun files R

The run files written by GRID are an audit trail of the options selected and responses made during the GRID session and correspond exactly to the keystrokes made. A file called LOG.RF (or log.rf if lower case file names are used) will be written every time the program is executed. This file is a precise record of the session. It may be used as a template for constructing repetitive operations, or may be copied to another file and used as an input run file to recover data that have been lost inadvertently, due to software, hardware or user error. (Note: LOG.RF will be overwritten by the next execution of the program, unless the user copies it to another run file.)

Input run files need not be quite so precise as the output file. The options specified in the run file need not necessarily be given in a precise order. If a menu option is not found on the current menu, then all menus will be searched until the option is found. The program will then take the shortest route through the menu tree to the required option. However, the user must respond correctly to any prompts that may occur along the path to the required option.

Menu options which appear in input run files may be written in abbreviated or expanded forms where appropriate, according to the dictionary of verbs and objects given in Appendix H. The options are insensitive to upper or lower case and to plural objects. Where possible, menu options are in the formalised form:

< 3-letter verb > < full object name > (single word objects)

or

< 3-letter verb > < 2x3 letter object name > (double word objects)

Run files contain only three types of data:

• Menu selections should be entered in double quotes and are written by GRID as the option appears in the menu. For input run files, options may be written in abbreviated or expanded forms. Menu selections start at the beginning of a new command line. A special type of menu selection is “Data point” which allows an x,y location to be entered. The format for data points is given below.

• Prompt responses should be entered in single quotes and are precisely the response to the prompt. Where a menu selection is followed by a series of prompts, the responses must be in the correct order. The response to a prompt cannot be continued on to another line, but need not necessarily be on the same line as the menu selection or other prompt responses following a menu selection. Any number of prompt responses can appear on a single line. Prompt responses may be replaced by a question mark '?' in the run file, indicating that a response is to be obtained from the user.

• All other data are regarded as comments, so that the file can be annotated as required.

Run file syntaxRun file syntax is checked as each line is read and errors are reported to the terminal. An error will also be reported if a menu selection is not found, although the run file will continue to execute. Note that errors are not held on the screen but can be traced if an output run file is being written.

If there are insufficient prompt responses to satisfy a menu selection, additional prompts will be given at the terminal. If the program is being executed in batch mode, default responses to unsatisfied prompts will be assumed.

Run files may be nested up to 10 deep, allowing for the use of standard run files from within input run files.


www.cadfamily.com

GRID Reference Manual Run FilesRun files R

543

In addition to menu selections some other commands are allowed:

The latter two commands are primarily intended for use in demonstration runs.

If an error is encountered during the execution of a run file the command "ERROR" is logged in any output run file in place of the offending command.

Profile run fileWhen a GRID session is started, the current directory is searched for the file PROFILE.RF (or profile.rf if lower case file names are used), and if the run file exists it is executed before any other commands can be entered. The profile facility can be used to set up preferred settings for the package, such as unformatted I/O or enabling sloping coordinate lines, etc., e.g.:

General options & special keysThe general option keys (P,R,D,A,H) and special keys for fast option selection (e.g. C for “Chg settings”) can be used in run files. These keys are described in "Using GRID" on page 25.

“END RUN FILE” should be used to end run files without encountering an end-of-file error. The run file input can be ended at any point within the file.

“DATA POINT” ’xxxx' 'yyyy' for data input where xxxx is the x-location in map coordinates, yyyy is the y-location in map coordinates. xxxx and yyyy have the Fortran format F16.6

“MAP-WORLD OFF” switches off map to world transformation for data point input and output (I/O will be in world coordinates using Fortran format F16.8)

“MAP-WORLD ON” (default) switches on map to world transformation for data point input and output (I/O will be in map coordinates using Fortran format F16.6)

“DISPLAY OFF” switches off menu display updates whilst the run file is being executed.

“DISPLAY ON” switches off menu display updates whilst the run file is being executed.

“HOLD” The execution of the run file is halted until the RETURN key is hit.

“PAUSE” ‘nnnn’ where nnnn is an integer. The execution of the run file is halted for nnnn milliseconds.

"Chg settings""Set IO fmt""Set inp fmt"Input format changed to unformatted...&"Set out fmt"Output format changed to unformatted...&"P""Return""End run file"


www.cadfamily.com

544 Run Files GRID Reference ManualRun files R

Macro facilityIt is possible to program the alphabetic keys, other than those used for general options and excluding Z. Whenever a key is pressed the program checks whether the run file key.RF exists and executes it if present. For example, an exit facility could be programmed to the X key by creating the file X.RF containing the commands

or an option facility could be programmed to the O key

If a run file exists with the same key-character as a special key option (e.g. C.RF) it will be executed in preference to that special key option.

"P" 'y'"Exit""End run file"

"Display off""R""Set option""End run file"


www.cadfamily.com

GRID Reference Manual Run FilesExecute a run file R.2

545

Execute a run file R.2

Exe file

PurposeExecute a run file.

DescriptionThe user is prompted for the root name of the run file to be executed. The run file to be executed should have the extension .RF (runfile.RF), although when the name is supplied, the extension need not be given. (If the extension is given, it will be ignored.)

If the file exists, the commands will be executed and the program proceeds as if input is being entered at the keyboard (except that not all messages will be held on the screen).

A run file can be interrupted by the user, by hitting the escape key <ESC>.

After a break-in, run file execution will stop as soon as the current command is completed.


www.cadfamily.com

546 Run Files GRID Reference ManualOpen a run file R.3

Open a run file R.3

Opn file

PurposeOpen an output run file.

DescriptionThe user is prompted for the root name of the run file to be opened. The name supplied will be given the extension .RF

Note that the file LOG.RF is always opened at the start of the program. Only one output file can be written at any time, and the LOG.RF will be closed before the new file is opened.


www.cadfamily.com

GRID Reference Manual Run FilesClose a run file R.4

547

Close a run file R.4

Cls file

PurposeClose an output run file.

DescriptionThe current output run file is closed.


www.cadfamily.com

548 Run Files GRID Reference ManualPath R.5

Path R.5

Set path

PurposeSpecify an option path.

DescriptionThe user is prompted for the option path to be followed.

The path may be specified in a manner similar to the way in which menu paths are used in the GRAF program, e.g. ‘P.2.4.9’ to sample contours.

The path should be specified from the current position in the menu tree.

Prompts associated with each menu selection will be made in the usual way.

Note that R.6 “Set option” is likely to be a more useful option for moving quickly around the menu tree.


www.cadfamily.com

GRID Reference Manual Run FilesSet option R.6

549

Set option R.6

Set option

PurposeSpecify an option to be executed.

DescriptionThe user is prompted for the option required. The option may be the menu item as specified on the relevant menu, or it may be an expanded or abbreviated form of the menu item as specified in the dictionary.

For example, the “Edt contours” option may be specified as “E CNT” or “EDT CONTOUR” or “E Contours” or “EDIT CNT” etc.

The option is insensitive to case or to plurals.

The “Set option” facility first checks whether the given option is available on the current menu. If not, the menu tree is searched until the option is found. The shortest path from the current menu to the required menu is calculated and will be followed. Any prompts along the way will be issued and will require a response in the usual way.

This option is a very powerful tool for moving quickly around the menu tree. Note that the “Set option” facility can be enhanced by using the macro facility to create an “Option” key defined by a run file O.RF, containing commands such as:

"R""Set option""End run file"


www.cadfamily.com

550 Run Files GRID Reference ManualShow coordinate position R.7

Show coordinate position R.7

Sho crd pos

PurposeShow the current cursor position in map units.

DescriptionOn choosing this option, the user is requested to select the point(s) for which the coordinate position is required.

Each point selected will be highlighted and its Easting and Northing value will be displayed at the bottom of the screen. If the model has a map projection, the Latitude and Longitude of the point selected will also be displayed.

Note This option is provided on the Run File menu, to ensure that it is accessible from both the Primary menu tree and the Display menu tree.


www.cadfamily.com

GRID Reference Manual DisplayIntroduction

551

Chapter 13Display

IntroductionThe “Display” menu provides options for zooming and panning the screen display, changing the elements shown on the display, and changing the view or layer being edited. Options for producing hard-copy plots and for setting up a digitizing table are also accessed via this menu.

The "Display" menu is invoked as a general option by typing “D” or by selecting the corresponding general option box with the cursor. It can be reached from any of the data editing menus, without the need to return to the Primary menu. The user can return to the menu from which the "Display" option was called, by using the “Return” option as many times as necessary or by selecting option “P” from any display sub-menu.

Screen refreshNote that, if required, the current screen display can be refreshed by typing “D” and then “2” from any of the data editing menus. For X-windows users, the window size and position will be checked when the screen is refreshed, and the display will be resized if necessary, to allow for any window changes.

Simulation grid displaysThe “Chg view” menu options can be used to select a layer (XY-plane) or cross-section (XZ- or YZ-plane) for editing.

A 3D view of the grid can be shown from within the display menus. However, the grid cannot be edited in 3D, and the display will revert to a plane view on return to the data editing menu. (For more comprehensive 3D visualization facilities, use FloViz.)


www.cadfamily.com

552 Display GRID Reference ManualIntroduction

Editing LGRsFor grids containing local refinements, it is possible to edit data within an LGR by selecting “Edt LGR”, option D.7.9 (see page 617), or use special key “L”.

Map view optionsMenu D.7.8, “Map view opts” (see page 603), provides access to special options for viewing map data. The “Ovl map” facility allows up to 10 different maps to be displayed, in addition to the current map which is being edited. The “Sho 3D map” menu provides options for viewing 3D displays of mesh map data. The “Arb section” option allows the user to construct an arbitrary cross-sectional view for one or more map strata. The “Grd x-sect” option can be used to display map strata on a simulation grid XZ or YZ cross-section. The “Map gradient” option provides a display of gradient arrows or streamlines derived from mesh map data. The “Sho well trj” option can be used to display well deviation survey data read in via menu P.6.6.2, “Inp well trj” (see page 525).

This menu can be accessed quickly from other GRID menus, by entering the special key “M”.


www.cadfamily.com

GRID Reference Manual DisplayDisplay D

553

Display D

D

PurposeChange the view or the contents of the current display, produce a hard copy plot or set up a digitizing table.


The “Return” option returns the user to the menu from which the Display option was selected. The other options are described in the following sections.

If general option “P” is selected from a sub-menu of the Display menu, the user is returned to the menu from which the Display option was selected.

Display options are not available from sub-menus of the Display menu.

Table 13.1 Menu D

Option Function

1 Return

2 Refresh

3 Unzoom

4 Def zoom

5 Inc display

6 Chg display

7 Chg view

8 Set dig tbl

9 Plt display

Refresh screen

Unzoom

Define zoom

Increase display area

Change display

Change view

Set up digitizing table

Plot display


www.cadfamily.com

554 Display GRID Reference ManualRefresh D.2

Refresh D.2

Refresh

PurposeRefresh the screen.

DescriptionThe screen is cleared and redrawn. This option may be used to redraw the screen if parts of the display have been erased due to moving lines, deleting items, etc.

If the screen display window has been moved or resized (X-windows display), the screen layout will be adjusted as necessary before redrawing.


www.cadfamily.com

GRID Reference Manual DisplayUnzoom D.3

555

Unzoom D.3

Unzoom

PurposeReturn to full screen picture following a zoom, pan or increase in picture size.

DescriptionThe screen is cleared and redrawn to show the default display area.


www.cadfamily.com

556 Display GRID Reference ManualDefine zoom D.4

Define zoom D.4

Def zoom

PurposeZoom or pan the current display area.


Table 13.2 Menu D.4

Option Function

1 Return

2 Zoom

3 Asp zoom

4 Pan left

5 Pan right

6 Pan up

7 Pan down

8 Abandon

9 Restore zoom

Zoom

Aspect-ratio zoom

Pan left

Pan right

Pan up

Pan down

Abandon

Restore previous zoom

Option 2 allows the user to define a zoom area on the current display. This is the default zoom option if the current view is not an areal XY plane. On selecting this option, the user should delimit the extent of the zoom area by digitizing two points on opposite diagonals. A white box will highlight the area selected, and any corner may be repositioned. When the required area has been defined, Option 1 should be selected to “Return”.

Option 3 allows the user to define a zoom area on the current display that will maintain the aspect ratio of the current display area. This is the default zoom option from an XY view. On selecting this option, the user should mark the bottom left-hand corner of the required zoom area. A diagonal line will then be drawn from the marked point. The user should then mark any point along the aspect diagonal to delimit the extent of the zoom area. The selected zoom area will be highlighted by a white box. When the required area has been defined, “Return” should be selected.

Options 4 to 7 allow the user to pan the current display left, right, up or down with a 20 per cent overlap.

Option 8 will “Abandon” any attempt to redefine the current display area.Option 9 restores the previous zoom which was applied for the current view. The zoom

coordinates are saved separately for the XY-plane, XZ-plane, YZ-plane and for 3D grid and 3D map views.


www.cadfamily.com

GRID Reference Manual DisplayIncrease display D.5

557

Increase display D.5

Inc display

PurposeIncrease display area by 50%.

DescriptionThe screen is cleared and redrawn with the display area enlarged by 50%, i.e. the current picture is drawn smaller. The option works in zoomed or unzoomed mode.


www.cadfamily.com

558 Display GRID Reference ManualChange display D.6

Change display D.6

Chg display

PurposeChange picture display.


Colour representations are described in Appendix C. If option 7 is selected the screen will be cleared and the current colour representations are shown. The user is prompted for the colour index to be changed. If no number is specified the current display will be redrawn.

The “Return” option returns the user to the “Display” menu. Other options are described in the following sections.

Table 13.3 Menu D.6

Option Function

1 Return

2 Chg box

3 Chg map

4 Chg grid

5 Chg survey

6 Chg menu

7 Chg col rep

8 Chg locator

9 Chg plot

Change box display

Change map display

Change grid display

Change survey display

Change menu display

Change colour representation

Change input locator

Change hard copy plot options


www.cadfamily.com

GRID Reference Manual DisplayChange box D.6.2

559

Change box D.6.2

Chg box

PurposeChange coordinate or graticule box display.


The “Return” option returns the user to the previous menu. Other options are described in the following sections.

Table 13.4 Menu D.6.2

Option Function

1 Return

2 Chg crd box

3 Chg grt box

Change coordinate box

Change graticule box


www.cadfamily.com

560 Display GRID Reference ManualChange coordinate box D.6.2.2

Change coordinate box D.6.2.2

Chg crd box

PurposeChange coordinate box display.


The coordinate box is the box drawn on the screen to delimit the model area. The annotation of the box may be enhanced by increasing the coordinate box display level to show coordinate labels, tickmarks and markers or lines across the display at tickmark intervals.


Table 13.5 Menu D.6.2.2

Option Function

1 Return

2 Chg crd lvl

3 Chg crd tck

4 Tog crd lbl

5 Chg crd lbl

6 Chg granite

Change coordinate box level

Change coordinate tickmarks

Toggle coordinate labels

Change coordinate labels

Change Granite


www.cadfamily.com

GRID Reference Manual DisplayChange coordinate level D.6.2.2.2

561

Change coordinate level D.6.2.2.2

Chg crd lvl

PurposeChange coordinate box display level.

DescriptionThe coordinate box can be drawn at the following levels:

The user is prompted for the required display level.

For areal (XY) displays a default base northing, base easting, northing increment and easting increment are provided automatically, but the user has the option to overwrite these values.

If the user is displaying a sectional view of a grid, XZ or YZ base and increment values are provided automatically, but these can also be overwritten.

Level 0 no display.Level 1 box only (default).Level 2 box with tickmarks around the outside.Level 3 as for 2 but with markers drawn across the display at tickmark intersections.Level 4 as for 2 but with lines drawn across the display at tickmark locations.


www.cadfamily.com

562 Display GRID Reference ManualChange coordinate ticks D.6.2.2.3

Change coordinate ticks D.6.2.2.3

Chg crd tck

PurposeChange secondary coordinate ticks.

DescriptionIn addition to the primary tickmarks drawn by default, up to 10 secondary tickmarks can be drawn between the primary tickmarks.

The user is prompted for the number of secondary tickmarks (default is zero). The number supplied will apply to both the X and Y axes.


www.cadfamily.com

GRID Reference Manual DisplayToggle coordinate box labels D.6.2.2.4

563

Toggle coordinate box labels D.6.2.2.4

Tog crd lbl

PurposeToggle coordinate box labels.

DescriptionIf labels are drawn on the coordinate box (display level 2 or higher) then they can be drawn inside or outside the coordinate box.

Although labels will not be drawn on the default screen display if they are drawn outside the box, it is sometimes preferable for plots to have the labels on the outside of the coordinate box.


www.cadfamily.com

564 Display GRID Reference ManualChange coordinate box labels D.6.2.2.5

Change coordinate box labels D.6.2.2.5

Chg crd lbl

PurposeChange coordinate box labels.

DescriptionIf labels are drawn on the coordinate box (display level 2 or higher) then they can be drawn along any edge of the box. The user is prompted to indicate on which edges of the box labels should be drawn. The default is along the bottom edge and down the left edge.


www.cadfamily.com

GRID Reference Manual DisplayChange Granite settings D.6.2.2.6

565

Change Granite settings D.6.2.2.6

Chg granite

PurposeChange granite settings for coordinate box display.


The pen, text and marker representations available are described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current default Granite attributes for the coordinate box lines, text or markers. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.

Table 13.6 Menu D.6.2.2.6

Option Function

1 Return

2 Chg pen

3 Chg text

4 Chg marker

Change pen

Change text

Change marker


www.cadfamily.com

566 Display GRID Reference ManualChange graticule box D.6.2.3

Change graticule box D.6.2.3

Chg grt box

PurposeChange graticule display.


The display of the graticule can be enhanced by increasing the display level to annotate the graticule and show markers or lines.



Option Function

1 Return

2 Chg grt lvl

3 Chg grt tck

4 Tog grt lbl

5 Chg grt lbl

6 Chg granite

7 Tog seconds

Change graticule level

Change graticule tickmarks

Toggle graticule labels

Change graticule labels

Change granite

Toggle seconds on graticule labels


www.cadfamily.com

GRID Reference Manual DisplayChange graticule level D.6.2.3.2

567

Change graticule level D.6.2.3.2

Chg grt lvl

PurposeChange graticule display level.

DescriptionA graticule can be drawn at the following levels, provided that a projection is defined for the model:

The user is prompted for the required display level.

A default base latitude, base longitude, latitude increment and longitude increment are provided automatically, but the user has the option to overwrite these values.

Level 0 no display (default).Level 1 draws tickmarks around the coordinate box.Level 2 as for 1 but markers drawn at graticule intersections.Level 3 as for 2 but lines of latitude and longitude are drawn across the display, up to

the coordinate box.


www.cadfamily.com

568 Display GRID Reference ManualChange graticule ticks D.6.2.3.3

Change graticule ticks D.6.2.3.3

Chg grt tck

PurposeChange secondary graticule ticks.

DescriptionIn addition to the primary tickmarks drawn by default, up to 60 secondary tickmarks can be drawn between the primary tickmarks.

The user is prompted for the number of secondary latitude and longitude tickmarks (defaults are both zero).


www.cadfamily.com

GRID Reference Manual DisplayToggle graticule labels D.6.2.3.4

569

Toggle graticule labels D.6.2.3.4

Tog grt lbl

PurposeToggle graticule labels.

DescriptionIf the graticule is being displayed (display level 1 or higher) then the labels can be drawn inside or outside the coordinate box.

Although labels will not be drawn on the default screen display if they are drawn outside the box, it is sometimes preferable for plots to have the labels on the outside of the coordinate box.


www.cadfamily.com

570 Display GRID Reference ManualChange graticule labels D.6.2.3.5

Change graticule labels D.6.2.3.5

Chg grt lbl

PurposeChange graticule labels.

DescriptionIf the graticule is displayed (display level 1 or higher) then the labels can be drawn along any edge of the box. The user is prompted to indicate on which edges of the box labels should be drawn. The default is along the top edge and down the right edge.


www.cadfamily.com

GRID Reference Manual DisplayChange Granite settings D.6.2.3.6

571

Change Granite settings D.6.2.3.6

Chg granite

PurposeChange Granite settings for graticule display.


The pen, text and marker representations available are described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current map display will be replaced by a summary of the current default Granite attributes for the graticule lines, text or markers. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.

Table 13.8 Menu D.6.2.3.6

Option Function

1 Return

2 Chg pen

3 Chg deg txt

4 Chg min txt

5 Chg marker

Change pen

Change degree text

Change minute text

Change marker


www.cadfamily.com

572 Display GRID Reference ManualToggle seconds on graticule labels D.6.2.3.7

Toggle seconds on graticule labels D.6.2.3.7

Tog seconds

PurposeToggle display of seconds on graticule labels.

DescriptionBy default, graticule labels are shown in degrees and minutes, together with a direction indicator (N,S,E,W). This toggle allows the user to request the display of seconds as well (e.g. for use on large-scale maps where the graticule increment is less than 1 minute).


www.cadfamily.com

GRID Reference Manual DisplayChange map display D.6.3

573

Change map display D.6.3

Chg map

PurposeChange map display.


The “Return” option returns the user to the “Chg display” menu. Other options are described in the following sections.


Option Function

1 Return

2 Chg wells

3 Chg faults

4 Chg contours

5 Chg mesh

6 Chg features

7 Chg captions

8 Chg zones

Change display of wells

Change display of faults

Change display of contours

Change display of mesh

Change display of features

Change display of captions

Change display of zones


www.cadfamily.com

574 Display GRID Reference ManualChange wells D.6.3.2

Change wells D.6.3.2

Chg wells

PurposeChange well display.


The “Return” option returns the user to the “Chg map” display menu.


Option Function

1 Return

2 Tog wells

3 Tog wll nmes

Toggle wells

Toggle well names


www.cadfamily.com

GRID Reference Manual DisplayChange faults D.6.3.3

575

Change faults D.6.3.3

Chg faults

PurposeChange fault display.




Option Function

1 Return

2 Tog faults

3 Tog flt nmes

4 Tog flt pnts

5 Tog col mask

Toggle faults

Toggle fault names

Toggle fault points

Toggle fault colour mask


www.cadfamily.com

576 Display GRID Reference ManualChange contours D.6.3.4

Change contours D.6.3.4

Chg contours

PurposeChange digitized contour display.



The option “Rem bck cnts” allows the user to delete back contours which were previously displayed using “Sho bck cnts” (P.2.4.9.5, see page 153).


Option Function

1 Return

2 Tog contours

3 Tog cnt pnts

4 Tog cnt lbls

5 Rem bck cnts

Toggle contours

Toggle contour points

Toggle contour labels

Remove back contours


www.cadfamily.com

GRID Reference Manual DisplayChange mesh D.6.3.5

577

Change mesh D.6.3.5

Chg mesh

PurposeChange mesh display.



Note that after toggling colour fill on, the colour intervals and shading can be adjusted via menu P.2.5.6.9, “Chg fill” (see page 202).

Option 9 "Chg fll opt" allows the user to choose whether to colour-fill the mesh by using contour fill or by colouring each mesh node. The second option may be less efficient for a large mesh and does not give such a high quality display, but it is useful for a mesh with highly variable data which is difficult to contour (e.g. data obtained from a geostatistical model).

For contour fill, the colour fill intervals are based on the major contours and the interval boundaries will be adjusted according to the number of major contours. For mesh node fill, the user can choose whether to use major contour spacing or regular spacing for the colour fill intervals. (Major contour spacing will give the same colour effects as for contour fill, whereas regular spacing will subdivide the range of mesh values to use all defined colour shades on equal intervals.)


Option Function

1 Return

2 Tog contours

3 Tog maj lbls

4 Tog min lbls

5 Tog mesh

6 Tog posting

7 Tog fill

8 Tog colr key

9 Chg fll opt

Toggle contours

Toggle major contour labels

Toggle minor contour labels

Toggle mesh

Toggle posting

Toggle fill

Toggle colour key

Change mesh fill option


www.cadfamily.com

578 Display GRID Reference ManualChange features D.6.3.6

Change features D.6.3.6

Chg features

PurposeChange feature display.




Option Function

1 Return

2 Tog features

3 Tog fet nmes

4 Tog fet pnts

Toggle features

Toggle feature names

Toggle feature points


www.cadfamily.com

GRID Reference Manual DisplayChange captions D.6.3.7

579

Change captions D.6.3.7

Chg captions

PurposeChange caption display.




Option Function

1 Return

2 Tog captions Toggle captions


www.cadfamily.com

580 Display GRID Reference ManualChange zones D.6.3.8

Change zones D.6.3.8

Chg zones

PurposeChange zones display.



Option 2 toggles off the display of all zones. Options 3, 4 and 5 allow zone labels, boundaries and colour fill to be selected separately.


Option Function

1 Return

2 Tog zones

3 Tog zon lbls

4 Tog zon bdry

5 Tog zon fill

Toggle zones

Toggle zone labels

Toggle zone boundaries

Toggle zone colour fill


www.cadfamily.com

GRID Reference Manual DisplayChange grid D.6.4

581

Change grid D.6.4

Chg grid

PurposeChange the display of the grid.

DescriptionThe following menu is displayed to allow the simulation grid display to be changed:

The “Return” option returns the user to the “Chg display” menu. Options 7, 8 and 9 have already been described in the “Smp contours” facilities (see P.2.4.9, page 134). The other options are described in the following sections.


Option Function

1 Return

2 Chg grd dsp

3 Chg dsp box

4 Chg dsp pln

5 Chg granite

6 Sho grd cnts

7 Chg grd cnts

8 Chg grd fll

9 Out grd cnts

Change grid display

Change display box

Change display plane

Change Granite

Show grid contours

Change grid contours

Change grid fill

Output grid contours


www.cadfamily.com

582 Display GRID Reference ManualChange grid display D.6.4.2

Change grid display D.6.4.2

Chg grd dsp

PurposeChange grid display.

DescriptionThe display of active cells, inactive cells, tickmarks between split nodes and the grid axes can be switched on or off.

It may occasionally be useful to display the inactive cells without the active cells displayed, to check the location of inactive cells which may be completely surrounded by active cells.

Switching off split node tickmarks allows a block centre grid to be displayed without the display being dominated by the tickmarks.

It may be required to turn off the grid axis display temporarily, if an axis obscures part of the grid.


www.cadfamily.com

GRID Reference Manual DisplayChange display box D.6.4.3

583

Change display box D.6.4.3

Chg dsp box

PurposeChange grid display box limits.

DescriptionThe following sub-menu is displayed to allow the grid display box limits to be changed:

The “Return” option returns the user to the Change Picture menu.

1 Return2 Full grid3 1st column4 Last column5 1st row6 Last row7 1st layer8 Last layer

Option 2 returns the display to the full grid display.Option 3 prompts for the minimum column number to be displayed.Option 4 prompts for the maximum column number to be displayed.Option 5 prompts for the minimum row number to be displayed.Option 6 prompts for the maximum row number to be displayed.Option 7 prompts for the minimum layer number to be displayed.Option 8 prompts for the maximum layer number to be displayed.


www.cadfamily.com

584 Display GRID Reference ManualChange display plane D.6.4.4

Change display plane D.6.4.4

Chg dsp pln

PurposeChange grid display plane.

DescriptionIn addition to the main grid display (shown in green on colour terminals), it is possible to show an additional grid layer, row or column, depending upon the viewpoint. The user is prompted for the layer, row or column number and the side of the block to be displayed. This facility may be used, for example, to check fault throws. The display plane is entirely passive: nodes in the display plane cannot be selected for editing, etc.

After the display plane has been enabled with this option, prompts to show a display plane will be issued when the XY, XZ or YZ edit plane is changed. The display plane can be switched off by responding NO to the prompt ‘Show display plane ?’ or by entering an invalid plane number such as -1. It can only be switched on by returning to this option.

If the user moves through the edit planes using the + or - special keys, the display plane will be incremented as well. The display plane number can be set to 0 or nplanes+1 (where nplanes is the number of rows, columns or layers in the grid, depending on the viewpoint). No display plane will be shown in this case, but it will be incremented correctly by the next + or - command. This allows the user to maintain a display of both sides of the fault planes while paging through all the cross-sections of a grid.


www.cadfamily.com

GRID Reference Manual DisplayChange Granite settings D.6.4.5

585

Change Granite settings D.6.4.5

Chg granite

PurposeChange Granite settings for grid display.

DescriptionThe granite settings used for displaying the grid can be changed. The following menu is displayed:

The options available for pens, fill areas and texts are described in Appendix C.

Note If the “Sho examples” option is selected from one of the subsequent menus, the current grid display will be replaced by a summary of the current default Granite attributes for the lines, fill area or text. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.


Option Function

1 Return

2 Chg act pen

3 Chg ina pen

4 Chg dsp pen

5 Chg ctl cols

6 Chg ctl rows

7 Chg org text

Change pen for active cells

Change pen for inactive cells

Change display pen

Change pen for control columns

Change pen for control rows

Change origin text


www.cadfamily.com

586 Display GRID Reference ManualShow grid contours D.6.4.6

Show grid contours D.6.4.6

Sho grd cnts

PurposeContour back grid depths or thicknesses.

DescriptionThe grid depths or thicknesses can be contoured back at any suitable contour interval and contour quality, with optional colour fill. The grid node values are used as the basis for re-contouring.

If contours are already drawn, reselection of this option removes them.

Note that this option should be used once depths and thicknesses have been sampled onto the simulation grid to ensure consistency between the maps and the grid.


www.cadfamily.com

GRID Reference Manual DisplayChange survey display D.6.5

587

Change survey display D.6.5

Chg survey

PurposeChange survey display.


The “Return” option returns the user to the “Chg display” menu. Each of the other options toggles the display as indicated.

Note that shot point numbers and values at fault cuts can be toggled on or off independently of the general shot point labels, but will use the same Granite settings if shown.

The fault throw indication is used on XY-displays. If selected, the tick marks at fault cuts will be modified so that the tick length on the downthrown side is half that used for the upthrown side.


Option Function

1 Return

2 Tog sht lnes

3 Tog sht pnts

4 Tog sht vals

5 Tog sht nums

6 Tog misties

7 Tog flt vals

8 Tog flt nums

9 Tog flt thrw

Toggle shot lines

Toggle shot point markers

Toggle shot point values

Toggle shot point numbers

Toggle misties

Toggle fault cut values

Toggle fault cut numbers

Toggle fault throw indication


www.cadfamily.com

588 Display GRID Reference ManualChange menu D.6.6

Change menu D.6.6

Chg menu

PurposeChange the menu display.


The “Return” option returns the user to the “Chg display” menu. Other options are described in the following sections.


Option Function

1 Return

2 Chg header

3 Chg advice

4 Chg options

5 Mov menu

Change header display

Change advice display

Change options display

Move options menu


www.cadfamily.com

GRID Reference Manual DisplayChange header D.6.6.2

589

Change header D.6.6.2

Chg header

PurposeChange header display.


The “Return” option returns the user to the “Chg menu” menu. Each of the other options leads to a further menu for setting Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current screen display will be replaced by a summary of the current default Granite attributes for the text, fill area or pen. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.


Option Function

1 Return

2 Chg hdr txt

3 Chg hdr bck

4 Chg hdr pen

Change header text

Change header background

Change divider between header and map area


www.cadfamily.com

590 Display GRID Reference ManualChange advice D.6.6.3

Change advice D.6.6.3

Chg advice

PurposeChange advice display.


The “Return” option returns the user to the “Chg menu” menu. Each of the Granite attributes, as described in Appendix C.

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current screen display will be replaced by a summary of the current default Granite attributes for the text or fill area. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.


Option Function

1 Return

2 Chg adv txt

3 Chg adv bck

Change advice text

Change advice background


www.cadfamily.com

GRID Reference Manual DisplayChange option D.6.6.4

591

Change option D.6.6.4

Chg options

PurposeChange option display.


The “Return” option returns the user to the “Chg menu” menu. Each of the other options leads to a further menu for setting Granite attributes, as described in Appendix C

Note that if the “Sho examples” option is selected from one of the subsequent menus, the current screen display will be replaced by a summary of the current default Granite attributes for the text, line fill area. On selecting an option such as “Chg colour” while showing examples, a list of possible choices will be displayed.


Option Function

1 Return

2 Chg opt txt

3 Chg opt for

4 Chg opt bck

5 Chg opt hgh

6 Chg opt pen

Change option menu text

Change option menu foreground

Change option menu background

Change option menu highlighting

Change option box pen


www.cadfamily.com

592 Display GRID Reference ManualMove options menu D.6.6.5

Move options menu D.6.6.5

Mov menu

PurposeMove the options menu.

DescriptionThe user is prompted for the new location for the options menu.

Caution Use of this facility is not recommended.


www.cadfamily.com

GRID Reference Manual DisplayChange colour representation D.6.7

593

Change colour representation D.6.7

Chg col rep

PurposeChange colour representation.

DescriptionA colour may be redefined by its red, green and blue components.

Colour representations are described in Appendix C. On selecting this option, the screen is cleared and the current colour representations are shown. The user is prompted for the colour index to be changed. If no number is specified the current display will be redrawn.


www.cadfamily.com

594 Display GRID Reference ManualChange locator D.6.8

Change locator D.6.8

Chg locator

PurposeChange graphics locator.

DescriptionThe graphics locator can be changed at any time during the execution of the program (e.g. change between graphics tablet and mouse). The user is prompted for the new locator number.

The locators available for the current device can be displayed by typing ‘H’ in response to the prompt.

Note that this facility is intended mainly for use with older Tektronix devices.


www.cadfamily.com

GRID Reference Manual DisplayChange hard copy plot options D.6.9

595

Change hard copy plot options D.6.9

Chg plot

PurposeChange default plot options for hard copy.

DescriptionThis menu allows the user to switch off selected elements of a hard copy plot, to set the plot border size and set the colour key size. The options set here will apply to all hard copy output.


The “Return” option returns the user to the “Chg display” menu.


Option Function

1 Return

2 Chg border

3 Chg title

4 Chg leg box

5 Chg prj box

6 Chg scl bar

7 Chg key box

8 Chg clipping

Change outer border of plot

Change title plot option

Change legend box plot option

Change projection box plot option

Change scale bar plot option

Change colour key box for maps

Change clipping option

Option 2 allows the user to choose whether to draw the outer border line on the plot. The user is then prompted to set minimum and maximum values for the border width (in cm.). A value of -1 indicates that the program default border width should be used.

Option 3 allows the user to switch off the hard copy plot title.Option 4 allows the user to switch off the map legend.Option 5 allows the user to switch off the projection box.Option 6 allows the user to switch off the scale bar.Option 7 allows the user to switch off the colour key on hard copy plots of colour-filled

maps. The key width and height can also be specified (in cm.). A value of -1 indicates that the program default size should be used. (Note that switching on the colour key from this menu will have no effect unless a key exists on the map display.)

Option 8 allows the user to switch off clipping for hard copy output (e.g. to draw a complete simulation grid, in cases where the grid extends beyond the model area).


www.cadfamily.com

596 Display GRID Reference ManualChange view D.7

Change view D.7

Chg view

PurposeChange the current viewpoint.


The “Return” option returns the user to the “Display” menu. Other options are described in the following sections.

Table 13.9 Menu D.7

Option Function

1 Return

2 Edt XY-plane

3 Edt XZ-plane

4 Edt YZ-plane

5 Sho 3D grd

6 Rot view

7 Edt sht sct

8 Map view opts

9 Edt LGR

Edit XY-plane

Edit XZ-plane

Edit YZ-plane

Show 3D grid

Rotate view

Edit shot line section

Special map view options

Edit LGR


www.cadfamily.com

GRID Reference Manual DisplayEdit XY-plane D.7.2

597

Edit XY-plane D.7.2

Edt XY-plane

PurposeDisplay an areal view of the grid or a survey horizon.

DescriptionIf an areal view is currently being displayed and a simulation grid is being edited, then the user is prompted for the layer number required and whether the Top or Bottom of the layer is required. (By default, the screen will be redrawn, unless automatic redrawing has been disabled. See the “Tog XY redraw” command, P.7.7, page 536.)

If an areal view is currently being displayed and a survey is being edited, then the user is prompted for the horizon number required and whether times or depths for the horizon are required. The user will also be prompted for a map stratum to be displayed. Hit RETURN if no map is required.

If a cross-section or shot-line section is being edited or a 3D display is shown, the new layer or horizon can be selected using the graphics locator.

The areal view will be displayed within the current zoom area.


www.cadfamily.com

598 Display GRID Reference ManualEdit XZ-plane D.7.3

Edit XZ-plane D.7.3

Edt XZ-plane

PurposeDisplay a cross-section through a grid row.

DescriptionIf an XZ plane is already being edited, the user is prompted for a new row and whether the Front or Back of the row is required. If an XZ plane is not being edited, the new row can be selected from the display.

If map cross-sections are enabled, then the user is also asked whether to display a map cross-section as background to the grid (see option D.7.8.5, "Grd x-sect", page 611, for further information).


www.cadfamily.com

GRID Reference Manual DisplayEdit YZ-plane D.7.4

599

Edit YZ-plane D.7.4

Edt YZ-plane

PurposeDisplay a cross-section through a grid column.

DescriptionIf a YZ plane is already being edited, the user is prompted for a new column and whether the Left or Right of the column is required. If a YZ plane is not being edited, the new column can be selected from the display.

If map cross-sections are enabled, then the user is also asked whether to display a map cross-section as background to the grid (see option D.7.8.5, "Grd x-sect", page 611, for further information).


www.cadfamily.com

600 Display GRID Reference ManualDisplay 3D grid D.7.5

Display 3D grid D.7.5

Sho 3D grid

PurposeDisplay 3D grid.

DescriptionA three-dimensional view of the grid can be displayed. The standard 3D display shows three faces of the grid at one time, the three faces to be shown being selected from the following menu:

A simple algorithm has been implemented for removing hidden lines. This involves drawing the grid from the back and drawing each block face in the background colour. The selected faces are drawn for blocks on the edge of the reservoir or for faulted blocks. This method will work well for most grids but may not be entirely suitable in all cases.

The algorithm does not give good 3D results for hard copy plots on devices which do not support colour fill (e.g. pen plotters). However, devices such as PostScript plotters or raster devices can be used successfully. The “Rot display” option prompts the user for the angle by which the viewpoint is to be rotated. The picture will be redrawn from the new viewpoint.

The editing options are not available from 3D display. If the user returns from the “Display” option without selecting a 2D display the display automatically returns to an XY-plane display of the top of layer 1.

Note The “Sho values” menu can be selected while in the 3D display menu, by hitting the “S” key. Grid blocks which are visible on the 3D view can be selected with the mouse or cursor. Highlighting is performed by redrawing a selected grid block. Note that hidden line removal is not repeated when a grid block is highlighted. To correct for accidental overdrawing, either select a few more cells, so that they are redrawn in front, or refresh the entire display by hitting “U” for unzoom, or return to the 3D menu and select the required view again.


Option Function

1 Return

2 Top,bck,lft

3 Top,frt,lft

4 Top,bck,rgt

5 Top,frt,rgt

6 Rot display

Top, back, left

Top, front, left

Top, back, right

Top, front, right

Rotate display


www.cadfamily.com

GRID Reference Manual DisplayRotate view D.7.6

601

Rotate view D.7.6

Rot view

PurposeRotate the areal view.

DescriptionThe areal view of the grid is rotated so that the grid coordinate system is parallel to the sides of the screen.

If this option is re-selected the view is rotated back to the normal display.


www.cadfamily.com

602 Display GRID Reference ManualEdit shot line section D.7.7

Edit shot line section D.7.7

Edt sht sct

PurposeDisplay a shot line section.

DescriptionThe user is prompted for the name of the shot line to be displayed. If no name is given, the required shot line may be selected by digitizing a point on or close to it on the screen.

The user is then asked whether times or depths are to be displayed.

The section is displayed with intersecting lines marked such that the size of the mark indicates the size of the mistie with the current line. Intersecting line names are shown at the top of the display.


www.cadfamily.com

GRID Reference Manual DisplayMap view options D.7.8

603

Map view options D.7.8

Map view opts

PurposeProvides options to overlay maps on the display, and to view 3D maps and arbitrary cross-sections.


The “Return” option returns the user to the “Chg view” menu.


Option Function

1 Return

2 Ovl map

3 Sho 3D map

4 Arb section

5 Grd x-sect

6 Map gradient

7 Sho well trj

Overlay maps

Show 3D map display

Arbitrary cross-section

Map cross-section on grid XZ/YZ view

Display map gradient data

Display well trajectory data

Option 2 allows the user to select one or more maps to be shown on the display, in addition to any map which is currently being edited.

Option 3 allows a 3D map display to be shown.

One or more mesh map layers can be shown.Option 4 allows the user to display an arbitrary cross-section through a set of map

layers.Option 5 allows the user to request display of map cross-sections on a grid XZ or YZ

view.Option 6 allows the user to display gradient data for a mesh map (high and low points,

gradient arrows and streamlines).Option 7 displays well trajectory data used in the “Well data” menu (P.6.6, see page

524).


www.cadfamily.com

604 Display GRID Reference ManualOverlay maps D.7.8.2

Overlay maps D.7.8.2

Ovl map

PurposeOverlay different maps on the display.


This facility allows the user to overlay up to 10 different maps on the screen in addition to the current map. All the maps will be included on any hard copy plots that are produced.

Overlay maps will be drawn in the order in which they have been specified using the “Sho map” option. The facility may be used, for example, to overlay separate coastline, boundaries or well location maps on to a series of structure maps for plotting purposes. The features will be drawn on all the output plots without the need for them to be stored on all the structure maps.

If a simulation grid is loaded, a wild card * can be entered to define the stratum for an overlay map. The overlay map stratum will then be set according to the current grid XY-plane and changed whenever the XY-plane changes. For example, if an overlay map is specified as TOPS(*) and grid layer 3T is selected, TOPS(3) will be displayed. If the appropriate map stratum is missing, the nearest stratum above the current layer will be shown (or the first available stratum, if there are none above this).

Note that it is not possible to edit overlay maps. Only the current map can be edited.


Option Function

1 Return

2 Sho map

3 Rem map

4 Lst ovl map

5 Chg ovl dsp

Show map

Remove map

List overlay maps

Change overlay display

Option 2 allows the user to specify a map name and stratum number to be added to the display.

Option 3 allows the user to remove an overlay map from the display.Option 4 will list all the maps that are currently included on the display.Option 5 allows the user to choose whether to display contours on overlay maps,

independent of the display settings in use for the current map.


www.cadfamily.com

GRID Reference Manual DisplayShow 3D map D.7.8.3

605

Show 3D map D.7.8.3

Sho 3D map

PurposeShow a 3D map display.

DescriptionThis option allows a 3D view of a mesh map to be displayed. Any mesh map can be used for the layer display, and one or more layers may be shown on one display.

On entry to this option, the user will be prompted to select a map name and the required layer(s) for display. By default, the selected map will be used to define a colour overlay for the 3D image. If a different overlay has already been displayed, further prompts will be issued, to allow the overlay to be changed.

The user is also prompted to define the direction of the data and the direction in which the layer numbering increases.

The following menu is then displayed:

One of four viewpoints can be chosen immediately (each viewpoint corresponds to looking along a particular corner) or the elevation and azimuthal angles can be set explicitly using Option 6. After a 3-dimensional image is shown, the image can be rotated by any angle using Option 7.

The selected map layers for display and the colour overlay can be changed using menu option 8, “Chg 3D disp”. This menu also allows the user to change the Z-direction (up or down), toggle the display of null data points, define a Z-exaggeration factor (default 1.0) and define a separation factor to allow gaps between layers on a multi-layer display.

By default, the image will be displayed using coloured lines. Options to change to colour fill are provided on menu option 9, “Chg 3D pict”, which also allows the user to toggle the display of the North arrow, title, key and layer labels.


Option Function

1 Return

2 Set 45 deg

3 Set 135 deg

4 Set 225 deg

5 Set 315 deg

6 Set angle

7 Rot angle

8 Chg 3D disp

9 Chg 3D pict

Set 45 degree (viewpoint)




Set angle

Rotate angle

Change 3D map display

Change 3D picture


www.cadfamily.com

606 Display GRID Reference ManualShow 3D map D.7.8.3

Proper hidden-line removal techniques are employed so that the image can be plotted correctly using display option D.9, “Plt display”.

The editing options are not available from 3D display. If the user returns from the “Display” option without selecting a 2D display the display automatically returns to an XY-plane display.


www.cadfamily.com

GRID Reference Manual DisplayChange 3D map display D.7.8.3.8

607

Change 3D map display D.7.8.3.8

Chg 3D disp

PurposeChange the current 3D map display.


This option allows a the current 3D map display to be changed. Note that the screen will not be refreshed to show changes selected here until the “Return” option is selected, allowing the user to make several changes without waiting for the screen to be redrawn.

By default, the colours will correspond to the Z-values of the current map. Using option 7, “Chg overlay”, will allow the colours to be set according to the Z-values of some other specified map. If a single layer is on display, a different map layer may be used for the overlay. If multiple layers are shown, a different map may be used for the overlay, but the layers must correspond to those used for the 3D depths. Alternatively, the layers may be colour-coded to identify the individual strata on a multi-layer display.

Table 13.14 Menu D.7.8.3.8

Option Function

1 Return

2 Tog Z dir

3 Tog 3D nulls

4 Chg Z exag

5 Chg Z separ

6 Chg 3D layer

7 Chg overlay

Toggle Z-direction

Toggle display of null data

Change Z-exaggeration factor

Change Z-separation factor

Change 3D map layers shown

Change colour overlay data

Option 2 allows the Z-direction to be toggled (up or down).Option 3 allows the user to switch the display of null data off or on.Option 4 allows the Z-exaggeration factor to be modified (default 1.0). Note that the

3D display is not ‘true-scale’ in the Z-direction, as it is adjusted to fit on the screen. However, the Z-exaggeration factor can be used to magnify differences in the Z-values.

Option 5 allows the user to enter a separation factor for multi-layer displays, to allow several layers to be viewed without overlapping. Some trial and error may be necessary to obtain the best combination of viewing angle, exaggeration and separation for a given model.

Option 6 allows a new map and/or new set of layers to be selected for display. If the current overlay map is not the same as the map used for the 3D layers, the user will be prompted to change this.


www.cadfamily.com

608 Display GRID Reference ManualChange 3D map display D.7.8.3.8

Options for use of colour fill or coloured lines are available on menu D.7.8.3.9, “Chg 3D pict” (see page 609).

When “Return” is selected, the display will be redrawn to reflect any changes made from this menu.


www.cadfamily.com

GRID Reference Manual DisplayChange 3D picture D.7.8.3.9

609

Change 3D picture D.7.8.3.9

Chg 3D pict

PurposeChange the picture options for a 3D map display.


By default, the 3D map display is drawn using colour coded lines. The lines can be set to a single colour (default white), or toggled off (if colour fill is in use), using option 2. Option 3 allows the user to switch colour fill on or off. The current colour fill options for mesh map contours will be used. (These can be modified via option P.2.5.6.9, “Chg fill”, see page 202.) A north arrow is displayed to indicate the orientation of the 3D image. If required, this can be removed using option 4.

Note that axes can be drawn on a 3D display, by setting the coordinate box level using option D.6.2.2, “Chg crd box” (see page 560).

When “Return” is selected, the display will be redrawn to reflect any changes made from this menu.

Table 13.15 Menu D.7.8.3.

Option Function

1 Return

2 Chg 3D lines

3 Chg 3D fill

4 Tog N arrow

5 Chg 3D title

6 Tog 3D key

7 Chg layer id

Set line display options

Switch colour fill on/off

Toggle North arrow

Change title

Toggle colour key

Change display of layer labels

Option 5 allows the user to choose whether to show the 3D display title. The title may be defaulted or entered by the user. The default title will indicate the map name, layer range and the name of the colour overlay maps, if present.

Option 6 allows the colour key to be toggled on or off.Option 7 allows the user to display labels showing the layer numbers. These can be

drawn on the left or right of the screen.


www.cadfamily.com

610 Display GRID Reference ManualArbitrary cross-section D.7.8.4

Arbitrary cross-section D.7.8.4

Arb section

PurposeDisplay an arbitrary map cross-section.

DescriptionThis option can be selected only from an areal display. The user is asked to mark an arbitrary line on the screen (with any number of input points), e.g. between a number of wells. Any number of interpolation points may be taken between the input points, depending on the definition required.

The user is prompted for the name of the maps to be displayed, a datum level and whether the maps are depth or thickness maps. The datum level will be subtracted from depth maps. For thickness maps, the thicknesses will be stacked above or below the datum level depending on the stratum level for the datum. This combination allows flexibility in the display. A complete cross-section may be constructed from a single structure map and a series of thicknesses by entering, e.g. DZ as the map name and TOPS(1) as the datum level, or a stack of structure maps may be viewed with any stratum as the datum level by entering, e.g. TOPS as the map name and putting the datum level at TOPS(3).

In addition the user will be prompted for the name of a property map. If a map name is given the strata will be colour filled according to sampled property values for each layer. The colour fill scheme will that set up for colour filled contours. This facility may be used to view changes in POROSITY, for example, on the cross-section structure.

Faults along the cross-section are not handled explicitly, except in so far as the interpolation will honour the faults. It is recommended that increased resolution is obtained close to faults, by entering input points either side of the fault.

The input points can be marked by arrows at the top of the display. The user is prompted to choose whether to show these arrows.

After the cross-section has been viewed on the screen, the user can choose to produce a hard copy plot before exiting. Prompts for plot size and device number are issued as for the “Plt display” option (see page 619).

The display must be returned to an areal display before any further menu selections can be taken in GRID.


www.cadfamily.com

GRID Reference Manual DisplayMap cross-section on grid XZ/YZ view D.7.8.5

611

Map cross-section on grid XZ/YZ view D.7.8.5

Grd x-sect

PurposeProvides options to draw map cross-sections on a grid XZ or YZ display.


The “Return” option returns the user to the “Map view opts” menu.


Option Function

1 Return

2 Tog x-sect

3 Chg x-sect

4 Chg ref lay

5 Chg smp pts

6 Chg granite

Toggle cross-section display on/off

Change maps to be displayed

Change reference layer in grid

Change number of sample points

Define pen for drawing map layers

Option 2 allows the user to toggle the cross-section display option ON or OFF. The user is prompted for the name of the maps, whether they are depth or thickness maps, the datum level and the range of strata to be shown. Note that a constant depth or another map stratum may be used for the datum (e.g. a TOPS map for use with a set of thickness maps).

When the option is on, further prompts are issued whenever the grid XZ or YZ view changes, to turn on the map display for the current plane.

Option 3 allows the selected maps to be changed, without toggling the cross-section display on or off.

Option 4 allows the user to change the reference layer in the grid (default layer 1T). When the maps are sampled, they will be sampled at (x,y) positions defined by the grid nodes on this reference layer. If the map strata correspond to the grid layers, the reference layer can be entered as '*' instead of a single layer. The node positions for sampling a map stratum will then be taken from the corresponding grid layer. This option may be useful for grids with sloping coordinate lines.

Option 5 allows the user to change the number of points sampled per grid block (default 0, i.e. only sample at nodes).

Option 6 can be used to change the line type, width and colour used to draw the map layers.


www.cadfamily.com

612 Display GRID Reference ManualDisplay map gradient data D.7.8.6

Display map gradient data D.7.8.6

Map gradient

PurposeDisplay gradient data for a mesh map: high and low points, gradient arrows and streamlines.

DescriptionOn entry to this option, the user will be prompted to select a map name and the required layer for display. The user is also prompted to define the direction of the data and whether to plot arrows / streamlines in the decreasing or increasing direction.

This option is only valid for mesh maps. The gradient display for the selected map will be shown on the screen until another map is selected or the display options are switched off again. The map need not be loaded for editing and contours need not be shown.

The following menu is then displayed:

To display high and low points on the selected map, use option 2, “Tog map hilo”. The points for display are found by identifying local maxima and minima on the mesh. The method inspects the Z-values within closed inner contours and labels appropriate points on the mesh. (Note that the selected points are at mesh nodes, and it may be possible to obtain a more extreme value within any given contour, if a point is sampled between mesh nodes.) If there are no closed contours on this map, these points may not be displayed.

The default labels, ‘high’ and ‘low’, reflect the origins of this option in a meteorological application. These can be changed if required using menu option 5, “Chg hilo txt”, which also allows display of numerical values and changes in text size and colour.


Option Function

1 Return

2 Tog map hilo

3 Tog grad dsp

4 Chg grad dat

5 Chg hilo txt

6 Chg colours

7 Chg arrows

8 Chg stmlines

Enable display of high and low points

Enable display of arrows or streamlines

Change map data for display

Change text for high and low points

Change colours for arrows/streamlines

Change arrow plotting parameters

Change streamline plotting parameters


www.cadfamily.com

GRID Reference Manual DisplayDisplay map gradient data D.7.8.6

613

Option 3, “Tog grad dsp” allows selection of either an arrow plot or a streamline display. Both these displays are constructed using gradient data obtained by calculating the partial derivatives DZ/DX and DZ/DY over the mesh map. The direction of the arrows will depend on the data direction set when selecting a map for display. If streamlines are selected, they can start from a set of user-defined seed points or from a single extreme point which is found automatically. The number of streamlines per seed point can also be defined. The seed points can be retained or redefined when this option is selected again, or when the map data are changed. (Display of high and low points may be useful when selecting user-defined seed points.)

The mesh map to be used for the gradient display can be changed by selecting option 4, “Chg grad dat”. This option can also be used to reverse the data direction for the current map.

The colours used for arrows or streamlines can be changed using option 6, “Chg colours”. The default display uses a single colour (default white). If colour-coded gradient lines are selected, an 8-colour display is shown, with colour intervals based on the underlying Z-values of the mesh map. The colours correspond to the line colouring used for 3D mesh displays.

Option 7, “Chg arrows”, allows the user to set parameters used for drawing arrows only. The arrows may be fixed-length or scaled with respect to the gradient values. Arrow spacing is defined with respect to the mesh rows and columns. The maximum arrow size is increased as the spacing increases. The default spacing parameter is 1, but this should be increased for dense mesh maps.

Option 8, “Chg stmlines”, allows the user to set parameters for drawing streamlines. The lines are constructed by a fourth-order Runge-Kutta integration method. The default step length factor is 0.5, which gives a Runge-Kutta step length of 0.5*(mesh interval). This can be increased for greater speed when the mesh is dense. The user can also set the number of steps between arrows and the arrow head size to be used with streamlines.


www.cadfamily.com

614 Display GRID Reference ManualChange text for high & low points D.7.8.6.5

Change text for high & low points D.7.8.6.5

Chg hilo txt

PurposeChange the text used for displaying high and low points on a map.


Option 2 allows the user to specify a text label for the high and low points (up to 10 characters). The user can also choose to show the corresponding numerical values for these points and specify the number of decimal points used. For example, this might be used to enable the display of spot maxima and minima for the selected map, on a different background map.

Option 3 allows all attributes of the key text for high points to be changed (height, colour etc.) and option 4 provides the same change menu for low points.

Option 5 sets the threshold value for the inner closed contours to be used for finding high and low points. Any features smaller than the specified size will be ignored, which gives the ability to suppress labelling of insignificant highs and lows. The size is defined as a fraction of the model area, e.g. 0.05. If the AUTO option is selected, the threshold will be taken from the mesh interval.

Table 13.18 Menu D.7.8.6.5

Option Function

1 Return

2 Chg hilo lbl

3 Chg high txt

4 Chg low txt

5 Set hilo lim

Change labels for high and low points

Change text for high points

Change text for low points

Set threshold size for inner contours


www.cadfamily.com

GRID Reference Manual DisplayDisplay well trajectory data D.7.8.7

615

Display well trajectory data D.7.8.7

Sho well trj

PurposeDisplay well trajectory data used for finding well connections.

(See the “Well data” menu, P.6.6, page 524.)

DescriptionThis menu is used to set up a well trajectory display, which will be shown on all XY or grid cross-section views until disabled again. Well trajectory lines can be shown for deviated or horizontal wells. For vertical wells, the well position on an XY view will be marked by a symbol and well label.

When a grid cross-section (XZ or YZ) view is shown, the areal positions of the wells will be checked, and only those wells which have an areal range overlapping the current cross-section will be drawn. This limits the number of wells shown on the display, but it is not based on a full trajectory calculation, so some wells may be shown even though they do not actually intersect the grid blocks on the current display.

Note that this option does not display well connections associated with a given simulation grid, but can be used to show the well trajectory data overlaid on a grid XY layer or cross-section.


The well trajectory display will not be shown until it has been enabled with option 2. Well data must first be loaded into the model with option P.6.6.2, “Inp wel trj” (i.e. the well data file with extension .GWELL or .FWELL must be present). When this display is enabled, the user can choose to disable the display of well data associated with maps.


Option Function

1 Return

2 Tog wel trj

3 Chg trj lnes

4 Chg trj sym

5 Chg trj pnts

6 Chg trj lbl

7 Chg TVD lbl

8 Chg attr lbl

Enable/disable well trajectory display

Change trajectory lines

Change well symbols

Change well data points

Change well labels

Change TVD value labels

Change attribute data labels


www.cadfamily.com

616 Display GRID Reference ManualDisplay well trajectory data D.7.8.7

Option 3 allows the user to define the Granite settings for lines to draw the trajectories. On exit from the Granite set-up menu, the user is prompted to choose whether to colour code the trajectory lines by TVD value. If colour coding is not selected, the lines may alternatively be coloured according to the corresponding well symbols. If neither of these options is used, the default colour will be taken from the Granite colour setting. If colour-coded lines are selected, an 8-colour display is shown, with intervals based on the TVD values along the line, and colours corresponding to the line colouring used for 3D mesh displays.

Option 4 allows the user to choose whether to display well symbols at the ends of the trajectory lines. Well symbols for individual wells can be copied from the well data for a given map stratum if required. Otherwise, the user can define Granite settings to be used for all well trajectory symbols.

Option 5 allows well data points to be displayed, corresponding to the XY positions of data values along the trajectory. Tickmarks or markers may be used and these may be coloured according to the trajectory line colours. The user can specify the drawing interval for data points. (Note that if TVD labels or attribute values are shown, the corresponding data points will always be marked.)

Option 6 allows the user to choose whether to display well labels and the Granite settings for the text can be modified if required.

Option 7 allows TVD value labels to be shown.

The user can modify the Granite settings for the label text and choose whether to colour the labels according to the trajectory line colours. The format for showing numbers is defined by the number of decimal places to be used. The user is also prompted to define the minimum and maximum label values to be shown (or enter U for unlimited range) and the interval between TVD labels. If minimum and maximum TVD labels are defined, this data range will also be used for colour coding the trajectory lines, with depths outside this range shown in white.

Option 8 allows the display of label values for another attribute (typically MD - measured depth). The Granite settings for the label text can be modified, although these labels will not be colour-coded. The user is prompted to define the minimum and maximum values to be labelled (enter U for unlimited range) and the interval between attribute labels.


www.cadfamily.com

GRID Reference Manual DisplayEdit local grid refinement D.7.9

617

Edit local grid refinement D.7.9

Edt LGR

PurposeEdit a locally refined grid.

DescriptionThis option can be used to select an LGR for editing or to return to editing the GLOBAL grid. On selection, the user is prompted as follows:

If the current grid is already an LGR, the default will be G, to return to the global grid. If the current grid is the global grid, the default is S, to select the LGR to be edited with the mouse or cursor. If option H is chosen, a help menu listing LGR names (plus GLOBAL) is provided for selection, allowing the user to pick a grid which is not visible on the current display.

When an LGR has been selected, the picture will be re-displayed showing only the local grid refinement. Options for grid editing will then apply to the fine grid until the user returns to coarse grid editing. Note that some options for editing fine grid geometry are restricted.

Note that movement of any of the nodes which are common to both the fine and global grids will result in nodes being moved in both grids. It is recommended that editing of fine grids is restricted to changing node depths on vertical coordinate lines and specification of fine grid property values.

Note This option can be selected quickly from any menu with the special key “L”.

Enter G-Global grid, S-Select LGR, H-Help list (g/S/h)


www.cadfamily.com

618 Display GRID Reference ManualSet up digitizing table D.8

Set up digitizing table D.8

Set dig tbl

PurposeSet up a digitizing table.

DescriptionThe user is prompted for the number of the digitizing table to be set up. The digitizing tables available on a particular site will be listed if ‘H’ is entered in response to the prompt.

On all sites option 0 is for the graphics locator. For example, digitizing may be performed using a Tektronix 4957 or 4958 connected directly to the terminal. If option 0 is selected, the user has the opportunity of changing the locator device. (The locator device may also be changed using option D.6.8, “Chg locator”, see page 594.)

On all digitizing tables (including those which operate the cross hairs), a menu can be used for selecting menu options. A menu template is available from SIS product support and is also included in Appendix A. All that is required is for the user to take a copy of the template, tape it somewhere convenient on the digitizing table and digitize the top left, top right and bottom right corners of the template. Menu options can then be selected by placing the digitizing cursor in the appropriate box.

Note that if cross-hairs are being used the position of the cross-hairs as they appear over the menu on the screen will not usually correspond to the menu template. Use of a menu template is compulsory for digitizing tables with less than 10 buttons.

A special facility is available for Tektronix tablets connected to Tektronix terminals, which allows the screen to be mapped on to a small part of the tablet. If this facility is used there will be a discontinuous jump in the cross-hairs location as the cursor is moved in and out of the designated area. The methods available for setting up a digitizing table are described in Appendix E.

Note that if a digitizing table is being used for editing grids, button 0 or button 10 must be used for selecting locations, otherwise the button number pressed overrides the selected location.


www.cadfamily.com

GRID Reference Manual DisplayPlot display D.9

619

Plot display D.9

Plt display

PurposePlot the current display to a secondary device.

DescriptionIf an automatic hardcopy device is available, the user will be asked whether automatic hardcopy is required. If it is, the picture will be redrawn on the screen without the menu display or advice line and copied to the hardcopy unit. The menu will then be re-displayed.

If no automatic hardcopy unit is available or if it is not selected, the user is prompted for whether a scaled plot is required or not. If so, the XY scale must be entered, and also the Z scale if the current picture is of a 3D grid. The user also has the option of selecting the largest scale plot that will fit on the plotter.

If a scaled plot is not required, the user is asked to specify the size of the plot in centimeters. The response should be in the form XxY. If Y is omitted (e.g. 15x), then the picture is plotted at the largest scale such that the width of the plot is Xcm. Similarly, if X is omitted (e.g. x15), the picture is plotted at the largest scale such that the height of the plot is Ycm. When specifying output size, note that this size refers to the map area, and the total plot size will include titles, borders, etc.

By default, plots will be drawn with titles, a scale bar (if appropriate), a legend box (if one is defined for the current map), and a projection box (if a projection is defined for the model). The default hard copy plot options can be modified using menu D.6.9, “Chg plot”, see page 595. This allows the user some control over the actual plot size which will be obtained for a given plot scale.

If a plot has already been produced during the current program session, the previous scale or size will be remembered and offered as the new default.

The user will now be prompted for the device number of the plotter. A list of available devices will be given if ‘H’ is entered in response to the prompt.

After the plotter device is opened, the program checks that the requested plot will fit on the plotter. If it will not, then a message is sent to the user and the plot aborted. In the case of Calcomp or Versatec type plotters, the program will automatically rotate the plot and try plotting it again before returning an error message.

It is possible to send a plot to any Granite device. A useful option is to send the picture to the current device so that a manual screen dump can be taken. When the picture is sent to the current device it will be held on the screen until a button is pressed.


www.cadfamily.com

620 Display GRID Reference ManualPlot display D.9


www.cadfamily.com

GRID Reference Manual Menu Template 621

Appendix AMenu Template

Figure A.1 contains a template which can be used as a menu box whilst using a digitizing table.

Options 1-9 may also be selected using cursor buttons 1-9.The general options P, R, D, A, H are given by the cursor buttons 11-15.Button 10 should be used for general input if the grid is being edited by means of the digitizing table, to avoid selecting unwanted options.


www.cadfamily.com

622 Menu Template GRID Reference Manual

Figure A.1 Digitizing table menu template

Option 1

Option 2

Option 3

Option 4

Option 5

Option 6

Option 7

Option 8

Option 9

P R D A H


www.cadfamily.com

GRID Reference Manual File Names 623

Appendix BFile Names

The following file types are used by the program. Depending on the computer system in use and the current configuration file settings, the file names may be upper or lower case. The file extensions may be up to 8 characters (UNIX convention), or restricted to 3 characters (ANSI convention, used for backward compatibility with older systems such as PCs under MS-DOS or Vax). More information will be found in the "ECLIPSE File Formats Reference Manual". Contact SIS Customer Support if you need further information.

Table B.1 Internal model files

Formatted type Unformatted type Purpose

.FNODE (.FND) .NODE (.NDE) Internal storage of grid

.FFEATURE (.FFT) .FEATURE (.FET) Internal storage of model specification

.L0001 ETC (.L01) .M0001 ETC (.M01) Internal storage of a single model stratum (one file for each stratum as specified in the FEATURE file)

.FSV .SVY Internal storage of survey

.HIS - History file

.FWELL (.FWL) .GWELL (.GWL) Special well data file

Table B.2 External files

Formatted type

Unformatted type

Purpose

.GRDECL (.GEC) .GRDBIN Output from GRID for input to reservoir simulator

.VOL - Output from volumetric analysis

.FIP - Output from fluids-in-place calculations

.DBG - Debug print file

.WEL - User output of well locations

.FLT - User output of fault traces


www.cadfamily.com

624 File Names GRID Reference Manual

The Convert utilityA facility for converting GRID model file formats has been added to the Convert utility program. This can be used, independent of GRID itself, to convert all files or selected files for a given model. For example, it can be used to convert model files to unformatted to reduce disk space usage, or to convert files to formatted for transfer to a different computer system.

The Convert program can also be used to list the physical map files associated with each map name and stratum in the model.

For information on how to run the Convert utility, please contact SIS Customer Support.

.CNT .UCT User output of contour points

.FTR - User output of features

.GCT .UGC User output of meshes

.CAP - User output of captions

.ZON - User output of zones

.SHT - User output of shot lines

.CTL - Irregular grid control lines

.PIC - User output of pictures

.RF - Run files

.RPT - Model report file

Table B.2 External files

Formatted type

Unformatted type

Purpose


www.cadfamily.com

GRID Reference Manual Granite SettingsIntroduction

625

Appendix CGranite Settings

IntroductionGranite is a graphical subroutine library. The appearance of any object on the screen may be changed by altering its Granite attribute settings. In general, all settings, except for colours, are available on every device by utilizing hardware capabilities wherever possible, or else by using software emulation.

The available settings for graphics objects in GRID are described below.


www.cadfamily.com

626 Granite Settings GRID Reference ManualPens

PensA pen is represented by the attributes:

• line style

• line width

• line colour

Only one line width is currently available for line styles other than 1 (solid). The following linestyles are available:

Figure C.1 Granite line styles


www.cadfamily.com

GRID Reference Manual Granite SettingsMarkers

627

MarkersA marker is represented by the attributes:

• marker type

• marker size (multiple of ‘d’ default 1.0)

• marker colour

• marker height (in cm.)

Marker size should be regarded as a multiplier on the marker height and should normally be left at its default value of 1.0. Marker heights are set in absolute units if centimetres so that the marker is the same size on all displays.


www.cadfamily.com

628 Granite Settings GRID Reference ManualMarkers

Figure C.2 Granite marker types


www.cadfamily.com

GRID Reference Manual Granite SettingsWells

629

WellsA well symbol is represented by the attributes:

• well type

• well colour

• well height (in cm.)

Well heights are set in absolute units of centimetres so that they are the same size on all displays. The following well symbols are available:


www.cadfamily.com

630 Granite Settings GRID Reference ManualWells

Figure C.3 Granite well symbols


www.cadfamily.com

GRID Reference Manual Granite SettingsFill areas

631

Fill areasFill areas are represented by the attributes:

• fill style ‘HOLLOW’, ‘SOLID’ or ‘HATCHED’

• style index (only for ‘HATCHED’)

• fill area colour

In general, solid area fill is used on colour devices and hatched on monochrome devices. If the style is set to hatched the following style indices are available:

Figure C.4 Granite hatched fill patterns

The number of colours available depends on the device used for display. (A maximum of 256 shades may be used if device capabilities permit.)

Colour indices 0 to 7 are normally reserved for the standard Granite colours. The following defaults are set for colours 0 to 15:


www.cadfamily.com

632 Granite Settings GRID Reference ManualFill areas

Figure C.5 Granite colour fills


www.cadfamily.com

GRID Reference Manual Granite SettingsText

633

TextText is represented by the following attributes:

• font

• precision

• expansion factor

• spacing

• colour

• character height (in cm.)

Three text precisions are available:

In all cases the character height is defined in centimetres.

The following fonts are available:

Figure C.6 Granite typefaces

Precision 1 String precision. Text angle and font are ignored. Character height is evaluated as closely as possible.

Precision 2 Character precision. Characters are placed according to height and text angle. Text angle and font are ignored for individual characters.

Precision 3 Stroke precision. Software text for which all attributes are taken into account.


www.cadfamily.com

634 Granite Settings GRID Reference ManualText

Examples of the effects of changing the text spacing and expansion factors are shown in Figure C.7.

Figure C.7 The effect of Granite text spacing and expansion factors

Cyrillic text translation optionWhen the Cyrillic font is used for text, the characters found in text strings can be mapped to the corresponding Cyrillic characters obtained from a Russian keyboard. This option is enabled by including the command CYRILLIC TRUE in the SYSTEM section of the configuration file. The correspondence between the English text and the translated Cyrillic characters is shown in Figure C.8.

Figure C.8 Cyrillic text


www.cadfamily.com

GRID Reference Manual Thickness Correction Factor 635

Appendix DThickness Correction Factor

The thickness correction factor can be applied to sampled thickness values. The correction factor attempts to account for the difference between the true vertical depths obtained at node locations and the thickness that should be used when setting depth values along sloping coordinate lines. Under most circumstances the difference is well within the uncertainty of the data. However, at large fault angles and large surface dip angles the factor may become significant.

In order to use the correction factor, sloping coordinate lines must be enabled via option P.7.5, “Tog slp crds”, on the “Chg settings” menu (see page -536). If sloping coordinate lines are subsequently disabled, the correction factor switch will also be turned off.

A geometrical construction for the correction factor is shown in Figure D.1. The angle a is the angle of the sloping line to the vertical, the angle b is the angle of the bottom surface to the horizontal. It is assumed for these purposes that the top and bottom surfaces may be regarded as parallel, so b is also the angle of the top surface to the horizontal.


www.cadfamily.com

636 Thickness Correction Factor GRID Reference Manual

Figure D.1 A geometrical construction for the correction factor

We have the vertical thickness:

[EQ D.1]

where

and

Hence

[EQ D.2]

However, it is not easy to estimate the angle b of the top surface to the horizontal, since at any particular node we have four grid block corners and each of the blocks will give a different angle.

The block to use has therefore been chosen arbitrarily in the order of priority (1) north-west, (2) north-east, (3) south-west, (4) south-east, so that in general the north-west block will be used.

The surface angle is then obtained by calculating the depth of the top of the grid block at the XY-location of the bottom of the block at the appropriate node, thus ensuring that the angle is calculated in the correct orientation.

The construction has the required property that if the top surface is flat along the coordinate line direction then the correction factor will be equal to 1.

b

b

a

L

DZ

Hb

Bottom surface

Top surface

Calculatednode location

Corrected nodelocation

H DZ Hb+=

Hb L b( )tan=

L DZ a( )tan=

DZ 11 a( ) b( )tantan+------------------------------------------H=


www.cadfamily.com

GRID Reference Manual Digitizing TablesConnecting digitizing tables

637

Appendix EDigitizing Tables

Connecting digitizing tablesGRID is designed to work with any digitizing table that can output formatted data in POINT mode.

The digitizing table should be connected via a standard serial port. An RS-232 cable with 25-pin or 9-pin D-shell connector can be used. Typically the serial communication will be set for 9600 baudrate, 8 databits per character, no parity, 1 stop bit, xon/xoff.

Once the digitizing table has been connected the communication should be tested.

On a PC the HyperTerminal program can be used to communicate directly to a serial port, e.g. COM1. On a UNIX machine enter the command

where /dev/ttyb is the device name of the port. On a Sun the serial ports are /dev/ttya and /dev/ttyb, but different names are used on other UNIX machines.

Press a button on the digitizing table tablet. If the communication is working correctly, an ASCII string should be returned on the display and the cursor will move to the next line. The ASCII string should contain the X position, Y position and button number of the tablet, e.g.:

not necessarily in that order, e.g.:

If the output is not ASCII then it will be necessary to check the communication settings and the digitizing table settings and correct any discrepancies. If the output is readable but more than one line of data is displayed each time the digitizing button is clicked, then the digitizer may be in STREAM mode and will need to be reset to POINT mode.

cat /dev/ttyb

01234,56789,1

1,+12345,+12226


www.cadfamily.com

638 Digitizing Tables GRID Reference ManualConnecting digitizing tables

Once communication is established, press all the buttons on the digitizer tablet in turn and note how each button is represented in the output string. This information can be used to define a DECODE string in the configuration file.

On a PC, exit the HyperTerminal program after it has been used to check the digitizer settings, as GRID is not able to use the port at the same time as another program.

Note A digitizing table may have various different modes of operation, which may be set by hardware dip-switches or by software signals sent to the port. If a table is used by several different operators, with different software packages, it may be necessary to check that the hardware set-up corresponds to the set-up which was used when the configuration file parameters were defined.


www.cadfamily.com

GRID Reference Manual Digitizing TablesConfiguring digitizing tables

639

Configuring digitizing tablesThe list of digitizing tables available for use with GRID must be defined in the configuration file before the program is executed (see Appendix M). Normally the configuration file for a particular system is set up when the program is installed. A summary of the configuration file data is given here for information only. If you require assistance in adding a digitizing table to the system, please contact SIS customer support.

Essential keywordsThe configuration file sub-section for digitizing tables will contain the following typical data:

These keywords are described in the following table. An example of their use is given at the end of this section.

------------------------------SECTION DIGITISERS

----------------------------SUBSECT TABLE 1SELECT TRUENAME Name or description of tableFORMAT Fortran formatNBUTTONS 4 or 16DECODE decode stringFACTOR 1.LUNIT /dev/tty0

Table E.1 Essential keywords

Keyword Description

FORMAT This is the Fortran format statement that will be used to convert unformatted output from the table to the X,Y position of the cursor and the button pressed. The X,Y position is read in integer form and the button is read as a character string. For example, if the table returned something like +33429,+22349,F when a button on the cursor was pressed, then the format string might be (I6,1X,I6,1X,A1).

NBUTTONS This is the number of buttons on the cursor, usually 4 or 16.

DECODE This translates the button string returned from the

cursor into an integer in the range 0-15, which will

be used to identify GRID menu options. If the cursor buttons are numbered, the decode string should be defined so that the program receives an integer

corresponding to the button pressed. For simple data entry, one button should be defined as ‘0’: on 16-

button cursors, button number 10 is used for this.

FACTOR This is used to translate from table coordinates to centimetres.

LUNIT The value of LUNIT is the port or terminal that the table is attached to (if applicable). This can vary depending on what machine you are using, for

example COM1 or COM2 on a PC under MS-DOS, or /dev/ttyb or /dev/tty0 on a Unix system.


www.cadfamily.com

640 Digitizing Tables GRID Reference ManualConfiguring digitizing tables

Optional keywordsThe following optional keywords can also be used:

Obsolete keywordsThe following keywords and their use are now obsolete but have been retained for backwards compatibility. They were required to read the serial port on some Hewlett-Packard machines.

If IOCTL is TRUE the following keywords may be used to set the serial device (LUNIT) port parameters:

Table E.2 Optional keywords

Keyword Description Default

PROMPT If TRUE a blank character is written to the

digitizer when it is opened to activate it.

FALSE

BLANKLINE If TRUE an extra line will be read from the

digitizing table after the location and button number are returned. This can be used to skip extra line feed characters output from the digitizer.

FALSE

ISTRING Initialisation string sent to the digitizer when it is opened.

PSTRING String sent to the digitizer every time it is read.

CHARACTERS This can be used when the digitizing table is

incapable of sending a Carriage Return. The

CHARACTERS keyword should be followed by the number of characters to read from the digitizing table before a Carriage Return is assumed. Default = 0.

0

Table E.3 Obsolete keywords

Keyword Description Default

CHARACTERS This keyword can also be used to activate C input for reading the digitizer, see the CBUFFER and IOCTL keywords.

0

CBUFFER TRUE to activate buffered C input. This can only be used if CHARACTERS > 0.

FALSE

IOCTL TRUE to set serial device parameters. This can only be used if CHARACTERS > 0. If CBUFFER is TRUE the IOCTL keyword is ignored.

FALSE

Table E.4 Obsolete keywords used with IOCTL

Keywords Description Options Default

BAUD Baudrate Any valid baudrate

9600

DATABITS Number of bits per byte 5, 6, 7 ,8 8

STOPBITS Number of stopbits sent 1, 2 1


www.cadfamily.com


641

Example: 4-button digitizerA CalComp Drawing Board III has a digitizing tablet with four buttons, labelled 0, 1, 2, 3. It is connected to a PC via COM1 and HyperTerminal is connected direct to COM1. The four buttons are pressed in turn and the following output is displayed:

Each line of the output consists of three items, the X and Y coordinates, followed by the button value. The X and Y coordinates are five digits long and each item is separated by a comma. The Fortran FORMAT statement needed to read this data is (I5,1X,I5,1X,A1), since the X and Y coordinates are integers, and the button value is a character. The 1X entries tell the program to ignore the commas.

Various DECODE strings are possible. For example if 248# is used then GRID will translate the digitizer keys as follows:

When the 0 button is pressed GRID reads character ‘1’. It searches for a ‘1’ in the decode string and fails to find it. So a value 0 is assigned to button 0. When the 1 button is pressed GRID reads character ‘2’. This is the first entry in the decode string and therefore a value of 1 is assigned to this button. Similarly button 2 is assigned a value 2 and button 3 a value 3. This means that when button 1, 2 or 3 is pressed, menu option 1, 2 or 3 will be selected - these are the most commonly used options when digitizing.

PARITY Parity checking NONE, EVEN, ODD

NONE

RECEIVER Enables/disables the port TRUE, FALSE TRUE

HUPCL Hang up on last close TRUE, FALSE TRUE

MODEMLINE Modem status lines are ignored if FALSE TRUE, FALSE FALSE

BYTESREAD Number of bytes read before a read successfully returns

An integer Value of

CHARACTERS

12345,12226,112345,12226,212345,12226,412345,12226,8

Table E.5 Example DECODE string 248#

Digitizer button

Digitizer output

GRID

0 1 0

1 2 1

2 4 2

3 8 3

Table E.4 Obsolete keywords used with IOCTL

Keywords Description Options Default


www.cadfamily.com

642 Digitizing Tables GRID Reference ManualConfiguring digitizing tables

At least one of the digitizer output characters must be missing from the DECODE string, otherwise all the digitizer buttons will correspond to menu items and it will be impossible to digitize a map. In the above example the output character ‘1’ is missing, and is replaced by a ‘#’ character. In fact any character other than a ‘1’ could have been used, e.g. 248X.

A second possible DECODE string would be ####. In this case none of the digitizer output characters ‘1’, ’2’ , ’4’ and ‘8’ appear, so all the digitizer keys have the value 0 assigned to them. However, the digitizer tablet would have to be moved from the map area to the menu template each time a new menu option was required.

The FACTOR can be found from the digitizing table manual or by checking the HyperTerminal output. Since the digitizer is calibrated in GRID a dummy value can be entered.

The CalComp Drawing Board III gives similar output on a Sun workstation, except that a blank line appears after each data line. Therefore the BLANKLINE keyword must be used in the configuration file. A configuration file entry for this digitizing table might look like:

Example: 16-button digitizerA 16-button digitizing tablet has buttons labelled from 1 to F. The digitizer output is given in the following table, along with the GRID interpretation.

------------------------------SECTION DIGITISERS----------------------------SUBSECT TABLE 1SELECT TRUENAME CalComp III on PCFORMAT (I5,1X,I5,1X,A1)NBUTTONS 4DECODE 248#FACTOR 0.00254LUNIT COM1:9600,n,8,1,p

SUBSECT TABLE 2SELECT TRUENAME CalComp III on SunFORMAT (I5,1X,I5,1X,A1)NBUTTONS 4DECODE 248#FACTOR 0.00254LUNIT /dev/ttybBLANKLINE TRUE

Table E.6 Example DECODE string 01245689ADCE37B#

Digitizer button

Digitizer output

GRID

1 0 1

2 1 2

3 2 3

4 4 4


www.cadfamily.com


643

There are several points worth noting:

• The digitizer output is 1 character long. If instead some of the output was 2 characters, e.g. if pressing E gave ‘15’, then the FORMAT statement would have to be changed. Alternatively the digitizer could be reset to give hexadecimal output.

• Digitizer buttons 1-9 have values 1-9 and will be interpreted as menu items 1-9. Since GRID has at most 9 menu items the other buttons which have values 10-15 have special meanings:

• 10 interpreted as 0

• 11 menu item P

• 12 menu item R

• 13 menu item D

• 14 menu item A

• 15 menu item H

Therefore, although the character D appears in the DECODE string, button 0 is still interpreted as 0, because the D is in the 10th position, The DECODE string 01245689A#CE37B# could also be used and gives the same interpretations.

• No digitizer output is given for button F. This button is often used to toggle between POINT and STREAM mode so should not be used. In any case GRID can only interpret values 0-15, so there is no advantage in setting the 16th character in the DECODE string to correspond to a digitizer button.

5 5 5

6 6 6

7 8 7

8 9 8

9 A 9

0 D 10

A C 11

B E 12

C 3 13

D 7 14

E B 15

F

Table E.6 Example DECODE string 01245689ADCE37B# (Continued)

Digitizer button

Digitizer output

GRID


www.cadfamily.com

644 Digitizing Tables GRID Reference ManualSetting up a table from GRID

Setting up a table from GRIDBefore using a digitizing table to enter data into GRID, the table must be calibrated from within the program, to ensure that the data points will be transformed correctly to model coordinates.

Options are provided from within the program, to set up a menu template for selecting program options while digitizing. This is essential if the cursor is restricted to 4 buttons. (See menu option D.8 “Set dig tbl”, page -618.)

The digitizing table may be calibrated using one of a number of different methods. The user should choose the method which is most convenient for the task at hand. All the methods collect a number of data points from the table, each of which will correspond to a known map point. A transformation from table coordinates to map coordinates can then be set up which is valid for any point on the table.

Calibrate map upon grid intersectionsThe user must delimit the map areal extent in the current units, e.g. grid Eastings and grid Northings, and supply increment values for both. Control points will be marked by asterisks (green is current). All of the points must be digitized in order to complete the setup.

Calibrate map upon graticule intersectionsThe user must delimit the map areal extent in Latitude and Longitude (deg, min), and supply increment values for both. Control points will be marked by asterisks (green is current). All of the points must be digitized in order to complete the setup.

Calibrate map along grid linesThe user must delimit the map areal extent in the current units, e.g. grid Eastings and grid Northings, and supply increment values for both. Arbitrary points can be digitized along the current grid line (green). Start with Northings and repeat for Eastings. An even distribution of points across the map is best.

Calibrate map along graticule linesThe user must delimit the map areal extent in Latitude and Longitude (deg, min), and supply increment values for both. Arbitrary points can be digitized along the current Graticule (green). Start with Latitude and repeat for Longitude. An even distribution of points across the map is best.

Calibrate map with arbitrary pointsThe user must specify at least four known coordinate points on the map, and is then required to digitize those points in the same order that they were specified.

Note that to calibrate the table to digitize a seismic section, use the menu option P.5.2.4 “Dig section” (see page -458).


www.cadfamily.com

GRID Reference Manual Map ProjectionsDefinitions of common terms

645

Appendix FMap Projections

Definitions of common termsAzimuthal

A class of projection where a single point has zero distortion (synonymous with plane).

Conformal

A projection where angles are preserved but only at a point. Common uses include Navigation Charts, National Surveys, Military Mapping and large scale Topographic mapping (synonymous with orthomorphic).

Conical

A class of projection where one or two standard parallels possess zero distortion.

Cylindrical

A class of projection where the central meridian possesses zero distortion (for Transverse aspect).

Ellipsoid

A solid figure for which every plane cross section is an ellipse. An ellipsoid of revolution can be generated by rotating an ellipse about one of its axes. Usually used to approximate the Geoid (synonymous with spheroid).

Equal Area

A projection where areas are preserved at the expense of shape being distorted. Uses include Volumetrics and Thematic mapping, e.g. distribution.

Equidistant

A projection where distances are true to scale along specific lines and in specific directions. Uses are general.


www.cadfamily.com

646 Map Projections GRID Reference ManualDefinitions of common terms

Geoid

The sea level equipotential surface of the earth, to which the direction of gravity is everywhere perpendicular.

Graticule

A system of lines representing meridians and parallels on a map.

Projection

Any systematic arrangement of meridians and parallels portraying the curved surface of the sphere or spheroid upon a plane.

Sphere

Used for map scales smaller than 1:5 000 000 to approximate the generating globe. (Maling 1973: USA mapped at 1:5 000 000 using the sphere showed 2/3 of all points to be within 1mm of their spheroid position.)

Spheroid

Oblate ellipsoid of revolution, used to approximate the Geoid (approximates +/- 80m from Geoid)


www.cadfamily.com

GRID Reference Manual Map ProjectionsChoice of map projection

647

Choice of map projectionNo map projection is perfect, and all map projections contain some distortion. There is often no correct or definitive projection for a particular geographical area, but a suitable choice of projection may be made, knowing the areal extent, the purpose of the map, and the map scale.

If the area is relatively small, choose the origin to the centre of the area. It makes little difference to the projection used, as most projections are good near the origin.

If the area is large, the most appropriate projection is one in which the distortion that occurs is minimised over the area concerned.

If the region is elongate and predominantly North / South in extent then a Transverse Mercator projection ( TM or UTM ) projection is the most suitable.

If the region is elongate and predominantly East / West in extent then a Conical projection ( LCC or AEA ) projection is the most suitable.

If the region is circular and located within the polar latitudes then the Universal Polar Stereographic projection is most suitable.

Young (1920), Ginzburg and Salmanora (1957) have developed the following critical values to apply in the choice of class of projection:

Critical Values of z/d: Conformal = 1.41

Equidistant = 1.73

Equal Area = 2.00

If z/d < critical value, then choose Azimithal

If z/d > critical value, then choose Conical or Cylindrical

E.g. Chile - difference in latitude = 32 degrees

difference in longitude = 7 degrees

z = 0.5 X difference in latitude

z = 0.5 X 32

z = 16

d = 7

Value = z/d = 16/7 = 2.3

Therefore choose Transverse Cylindrical projection.

min width = dmax radius = z


www.cadfamily.com

648 Map Projections GRID Reference ManualProjection facilities

Projection facilities

Available map projectionsThe following common map projections are currently available:

1 Universal Transverse Mercator

2 Oblique Mercator (Hotine)

3 Transverse Mercator

4 Mercator

5 Lambert Conformal Conic

6 Albers Equal Area

7 Universal Polar Stereographic

8 Azimuthal Equidistant

9 None (normal cartesian coordinates)

Universal Transverse Mercator projection (UTM)• Class = Cylindrical

• Contact = Secant

• Aspect = Transverse

• Property = Conformal

The UTM system was introduced by NATO for maps and surveys in the early 1950’s. The generating globe is divided into individual Zones extending 6 degrees in Longitude between limiting Parallels 80 degrees South and 84 degrees North. Consequently there are sixty identical and contiguous UTM zones, providing a complete world reference system, when combined with the Universal Polar Stereographic projection.

The UTM Zone numbering system begins at the antimeridian of Greenwich (180) with Zone 1 comprising the belt between the meridians 174 degrees West and 180 degrees with a central meridian of 177 degrees West. The Zone numbering increases Eastwards ( see following page for table of UTM zones ).

The True Origin of each Zone is located at the intersection of the central meridian with the Equator. This point is assigned false grid coordinates (defined below), so that all projected coordinates are positive. The scale factor along the central meridian of each zone is always 0.9996.

• Scale Factor 0.9996

• False Easting Northern Hemisphere = 500 000m

Southern Hemisphere = 500 000m

• False Northing Northern Hemisphere = 0m

Southern Hemisphere = 10 000 000m

The user is required to specify :

• Spheroid Australian National 1924 Australia, SE Asia


www.cadfamily.com

GRID Reference Manual Map ProjectionsProjection facilities

649

Bessel 1841 USSR, Japan, SE Asia

Clarke 1866 North America

Clarke 1880 Africa

Everest 1830 India and adjacent SE Asia

Hayford Int 1910 Rest of world

WGS 72 1978

WGS 84 1984 (GRS 80 1980)

• Central Meridian

• False Northing

Note that a non-standard spheroid (other than those listed above) may be selected, but a warning will be issued to the user.

Table F.1 U.T.M. zones

Western Hemisphere Eastern Hemisphere

ZoneCentral Meridian

E/W Extent ZoneCentral Meridian

E/W Extent

1 177W 180E to 174W 31 3E 0E to 6E

2 171W 174W to 168W 32 9E 6E to 12E

3 165W 168W to 162W 33 15E 12E to 18E

4 159W 162W to 156W 34 21E 18E to 24E

5 153W 156W to 150W 35 27E 24E to 30E

6 147W 150W to 144W 36 33E 30E to 36E

7 141W 144W to 138W 37 39E 36E to 42E

8 135W 138W to 132W 38 45E 42E to 48E

9 129W 132W to 126W 39 51E 48E to 54E

10 123W 126W to 120W 40 57E 54E to 60E

11 117W 120W to 114W 41 63E 60E to 66E

12 111W 114W to 108W 42 69E 66E to 72E

13 105W 108W to 102W 43 75E 72E to 78E

14 99W 102W to 96W 44 81E 78E to 84E

15 93W 96W to 90W 45 87E 84E to 90E

16 87W 90W to 84W 46 93E 90E to 96E

17 81W 84W to 78W 47 99E 96E to 102E

18 75W 78W to 72W 48 105E 102E to 108E

19 69W 72W to 66W 49 111E 108E to 114E

20 63W 66W to 60W 50 117E 114E to 120E

21 57W 60W to 54W 51 123E 120E to 126E

22 51W 54W to 48W 52 129E 126E to 132E

23 45W 48W to 42W 53 135E 132E to 138E

24 39W 42W to 36W 54 141E 138E to 144E

25 33W 36W to 30W 55 147E 144E to 150E


www.cadfamily.com


Oblique mercator projection (OBM)• Class = Cylindrical


• Aspect = Oblique


There are several geographical regions that are elongate in shape and centered on lines which are neither meridians or parallels, but lines which may be taken as great circle routes through the region. If conformality is required, the Oblique Mercator projection should be considered.

The Oblique Mercator is equivalent to the Transverse Mercator except that the line of zero distortion may be any great circular line, and not just any meridian. A resulting Oblique map of the world would resemble a normal aspect Mercator projection but with the land masses rotated so that the poles and equator are no longer in their usual positions.

The central line for the Oblique Mercator is defined by the user who must specify the two end points of the line. The base parallel should be to the south of the southern edge of the map.

The user may find that a circumscribing rectangle derived from the lat. long. window does not encompass the entire geographical area required. This is due to the aspect of the projection being oblique. One way that a large enough circumscribing rectangle could be generated would be to increase the extent of the lat. long. window.


• Spheroid

• Central Line

• Base Parallel

• False Easting

• False Northing

• Scale Factor.

Transverse mercator projection (TM)• Class = Cylindrical


• Aspect = Transverse


26 27W 30W to 24W 56 153E 150E to 156E

27 21W 24W to 18W 57 159E 156E to 162E

28 15W 18W to 12W 58 165E 162E to 168E

29 9W 12W to 6W 59 171E 168E to 174E

30 3W 6W to 0E 60 177E 174E to 180E

Table F.1 U.T.M. zones (Continued)

Western Hemisphere Eastern Hemisphere

ZoneCentral Meridian

E/W Extent ZoneCentral Meridian

E/W Extent


www.cadfamily.com


651

The spherical form of the Transverse Mercator was invented by the Alsatian cartographer Johann Heinrich Lambert. C.F. Gauss analysed the ellipsoidal form in 1822 and L. Kruger published studies in 1912 and 1919 providing suitable formulae for calculation.

The ellipsoidal form of the Transverse Mercator is probably used more than any other projection for geodetic mapping. With the scale along the central meridian remaining constant, the Transverse Mercator is an excellent projection for lands extending predominantly North/South.


• Spheroid


• Base Latitude

• False Easting

• False Northing

• Scale Factor.

Mercator projection (MER)• Class = Cylindrical


• Aspect = Normal


Probably the most well-known projection, presented in 1569 by Mercator on a large world map of 21 sections totaling 1.3m by 2.0m. Still used today on many traditional wall mounted political maps.

The meridians of longitude are vertical, parallel equally spaced lines, cut at right angles by horizontal straight parallels which are increasingly spaced towards each pole.

The major feature of the projection is that a sailing distance between two points is shown on the map as a straight line, and is therefore used in the production of many charts. However, great distortion of area occurs, especially in polar regions, giving rise to the classic comparison of Greenland and South America. Greenland appears larger although it is only one-eighth of the size of South America.

The user is required to specify:

• Spheroid


• Latitude to be used for calculating Scale Factor.

Lambert conformal conic projection (LCC)• Class = Conic


• Aspect = Normal


Presented by Johann Heinrich Lambert in 1772, initial use was made of an approximate version by France for battle maps during the 1914-1918 War. In some atlases, particularly British, the Lambert Conformal Conic is referred to as the Conical Orthomorphic Projection.


www.cadfamily.com


The standard parallels should be 1/6 th to 1/7 th of the way in from the North / South edge of the area to be projected. If only one standard parallel is required, both standard parallels should be made equal. The base parallel should be to the south of the southern edge of the map for maps of the northern hemisphere: in the southern hemisphere the cone is reversed.


• Spheroid


• False Easting

• False Northing

• Base Parallel

• Standard Parallels

• Scale Factor.

Albers’ equal area projection (AEA)• Class = Conic


• Aspect = Normal

• Property = Equal Area

First presented by Heinrich Christian Albers in a German periodical of 1805. The Albers projection was used for a German map of Europe in 1817, and was promoted for maps of the United States by Oscar S. Adams in the early 20th Century.

Like other normal aspect conics, the Albers Equal Area projection has concentric arcs of circles for parallels and equally spaced radii for meridians. Parallels are not equally spaced, and are furthest apart in the Latitudes between the Standard Parallels.

Scale along the parallels is too small between the Standard Parallels and too large beyond them. The converse is true for scale along the meridians, since for a given point, the meridian scale is the reciprocal of the parallel scale, to maintain equal area.

The standard parallels should be 1/6 th to 1/7 th of the way in from the North / South edge of the area to be projected. If only one standard parallel is required, both standard parallels should be made equal to that of the one desired. The base parallel should be to the south of the southern edge of the map for maps of the northern hemisphere: in the southern hemisphere the cone is reversed.


• Spheroid


• False Easting

• False Northing

• Base Parallel

• Standard Parallels.

Universal polar stereographic projection (UPS)• Class = Azimuthal


www.cadfamily.com


653


• Aspect = Normal


The stereographic projection was probably known in its polar form to the Egyptians, while Hipparchus was apparently the first Greek to use it and is generally considered as its inventor.

Parallels project into concentric circles and are spaced at increasingly wide distances, the further the latitude is from the pole. Meridians project into straight radii.

The Universal Polar Stereographic system is used for areas polewards of the UTM cover, i.e. Latitudes North of 84 degrees North and South of 80 degrees South. The Central Meridian is always Greenwich with a scale factor of 0.994. A False Easting and False Northing of 2,000,000m is added to the grid coordinates to give positive values throughout the projected area.

The user can enter alternative values for the False Easting and False Northing, if a non-standard version of the projection is required

• Scale Factor 0.994

• Central Meridian 0 deg E (Greenwich)

• False Easting Northern Hemisphere = 2,000,000m

• False Northing Northern Hemisphere = 2,000,000m


• Spheroid

• Latitude Origin (90 deg N or 90 deg S)

• False Easting

• False Northing.

Azimuthal equidistant (AZE)• Class = Azimuthal

• Aspect = Polar or Oblique

• Property = Equidistant

The Azimuthal Equidistant projection can be used in polar form, with centre at 90,00,00N or 90,00,00S, or in an oblique form, with centre at an arbitrary point. The projection is neither equal-area nor conformal, but has the property that all distances measured from the centre are true (although distances not measured along radii from the centre are not necessarily correct).

The oblique version of the projection has been implemented using formulae based on those used for maps of Micronesia.


• Spheroid

• Origin: Central Meridian and Latitude Origin

• False Easting

• False Northing

• Scale Factor.


www.cadfamily.com

654 Map Projections GRID Reference ManualSpheroids (Ellipsoids)

Spheroids (Ellipsoids)

Available spheroidsThe following spheroids are available.

Option 15 allows entry of a user-defined spheroid.

Possible user-defined spheroidsThe following are internationally recognised spheroids.

[EQ F.1]

where:

a = semi major axes

b = semi minor axes

f = flattening

Table F.2 Available spheroids

No. Spheroid Date a b

1 Airy 1849 6377563.396 6356256.910

2 Australian Nat. 1924 6378160.000 6356774.719

3 Bessel 1841 6377397.155 6356078.963

4 Clarke 1858 6378294.000 6356618.000

5 Clarke 1866 6378206.400 6356583.800

6 Clarke 1880 6378249.145 6356514.870

7 Everest 1830 6377276.345 6356075.413

8 Fischer (S.Asia) 1960 6378155.000 6356773.320

9 Fischer (Mercury) 1960 6378166.000 6356784.284

10 Fischer (Mercury) 1968 6378150.000 6356768.955

11 Hayford Int. 1910 6378388.000 6356911.946

12 Int. Astronomical 1968 6378160.000 6356774.719

13 Krasovsky 1940 6378245.000 6356863.019

14 WGS 72 1978 6378135.000 6356750.520

15 Other (User defined)

16 WGS 84 1984 6378137.000 6356752.314

b a 1 f–( )=


www.cadfamily.com

GRID Reference Manual Map ProjectionsSpheroids (Ellipsoids)

655

Table F.3 User defined spheroids

Spheroid Date a b f

Airy 1830 6376542.000 1/299.330

Airy 1837 6377541.000 1/299.320

Airy 1849 6377563.396 6356256.900 1/299.324964

Airy 1849 6377491.000 1/299.320

Airy modified 6377340.189 1/299.324964

Airy War Office 6377542.178 1/299.325

Apl 4.5 6378137.000 1/298.250

Australian I.A.U 1965 6378160.000 6356774.719 1/298.250

Beautemps-Beaupre 1816 6376522.000 1/308.650

Bessel 1841 6377397.155 6356078.963 1/299.1528

Biot and Arago 1810 6376986.000 1/308.640

Bonsdorff 1888 6378444.000 1/298.600

Bougeur,Maupertuis 1738 6397300.000 1/216.800

Clarke 1880 6378249.170 6356514.900 1/293.465

Clarke 1857 6378345.000 6356669.000 1/294.260

Clarke 1858 6378294.000 6356618.000 1/294.261

Clarke (Cyprus) 1858 6378235.600 1/294.260676

Clarke (I.G.N.) 1880 6378249.200 1/293.466020

Clarke 1863 6378288.000 1/294.360

Clarke 1866 6378206.400 6356583.800 1/294.978698

Clarke (Cape) 1880 6378249.145 1/293.466307

Clarke modified 1858 6378293.645 1/294.260

Clarke (Palestine) 1880 6378300.782 1/293.466307

Clarke modified 1880 6378249.145 1/293.465

Clarke variant 1880 6378301.000 6356871.000 1/293.470

Clarke variant 1880 6378249.000 1/293.500

Clarke-Bessel (1) 6378301.000 1/299.150

Clarke-Bessel (2) 6378190.000 1/299.150

Danish Survey 1876 6377104.430 1/300.000

Delambre 1810 6376428.000 1/311.500

Delambre 1800 6375653.000 1/334.000

Delambre (Carte de Fr.) 6376985.000 1/308.640

Everest 1830 6377276.345 6356075.413 1/300.8017

Everest alternative 1830 6377252.600 1/300.8017

Everest 1847 6376634.000 1/311.040

Everest (Borneo) 6377298.556 1/300.8017

Everest (India) 6377301.243 1/300.801725

Everest (Malaya) 6377295.664 1/300.8017


www.cadfamily.com

656 Map Projections GRID Reference ManualSpheroids (Ellipsoids)

Fisher 1868 6378338.000

Fisher (Mercury) 1960 6378166.000 6356784.284 1/298.300

Fisher (S.Asia) 1960 6378155.000 6356773.320 1/298.300

Fisher Mercury mod. 1968 6378150.000 6356768.955 1/298.300

Francoeur 1839 6377116.000 1/305.000

Geodetic Ref. Sys. 1980 6378137.000 6356752.300 1/298.2572

Germain 1882 6378284.000 1/294.300

Harkness 1891 6377972.000 1/300.200

Hayford 6378062.000 1/298.200

Hayford 1907 6378283.000 6356868.000 1/297.8+/-.9

Hayford Int. 1910 6378388.000 6356911.946 1/297.000

Heiskanen 1926 6378397.000 1/297.000

Helmert 1907 6378200.000 6356818.000 1/298.300

Helmert-Hayford 6378372.000 6356896.000 1/297.000

Hough U.S. A.M.S. 1956 6378270.000 6356794.343 1/297.000

I.M.W. Committee 1909 6378240.000 6356560.000 1/294.200

Int. Astronomical 1968 6378160.000 6356774.719 1/298.250

Int. Geodetic Assoc 6378035.000 6356715.000 1/299.150

James and Clarke 6377936.000 1/297.720

Jeffreys 1948 6378099.000 1/297.100

Kraijenhoff 6376950.000 1/309.650

Krasovsky 1940 6378245.000 6356863.019 1/298.200

Laplace 1799 6376340.000

Ledersteger 1951 6378298.000

Naval Weapons Lab NWL9D 6378145.000 6356759.800 1/298.250

New International 1980 6378137.000 6356752.314 1/298.260

Pratt 1863 6378297.000 6356695.000 1/295.260

Puissant 6376951.000 1/309.610

Reference Ellipsoid 1967 6378160.000 1/298.247167

Schmidt 1828 6376959.000 1/297.650

Schott 1877 6378054.300 1/305.480

Struve 1860 6378298.300 1/294.730

Svanberg 6376797.000 1/304.2506

Walbeck 1819 6376895.000 1/302.782136

Walbeck (2) 1819 6376896.000 1/302.780

War Office 1924 6378300.000 1/296.000

W.G.S. 60 1960 6378165.000 6356783.000 1/298.300

W.G.S. 66 1966 6378145+/-20 6356760+/-20 1/298.250

W.G.S. 72 1972 6378135+/-5 6356750.52+-5 1/298.260

W.G.S. 84 1984 6378137.000 6356752.314 1/298.2572

Table F.3 User defined spheroids (Continued)

Spheroid Date a b f


www.cadfamily.com

GRID Reference Manual Arithmetic Formulae 657

Appendix GArithmetic Formulae

Operations may be performed using arithmetic formulae in which the names of maps or property arrays appear as variable names, e.g.:

• For manipulating grid block data

• For sampling maps or surveys or operating on meshes.

If the formula to be entered is longer than one line, enter an ampersand, ‘&’. This will tell the program that you wish to continue entering the formula. The formula may be up to 10 lines long. Any trailing ampersands will be removed from the formula before it is used by the program. Note that when commands are entered via a run file, the length of each line in the file should not exceed 80 characters.

In addition to variable names the following symbols are recognized:

These special functions are described in this Appendix, but can not be used in any other arithmetic operation.

Operators: + - * / **

Relational operators: = > < >= <= <>

EQ GT LT GE LE NE

Logical operators: | &

OR AND

Functions: LOG LN SQRT EXP SIN COS TAN ABS INT

Reserved words: IF THEN ELSE ENDIF NULL

Special keywords: @DX @DY @DZ

@TOPS @DR @DTHETA @DEPTH

@PORV @PORV_M @PORV_RB

Three special functions are available for filling in null values:@FILL @FILL_A @FILL_L


www.cadfamily.com

658 Arithmetic Formulae GRID Reference Manual

The structure of an IF-THEN-ELSE clause is similar to that used in Fortran programs. Conditional statements should be enclosed in parentheses and the statement must end with ENDIF. However, the relational operators EQ, GT, etc. and the logical operators OR, AND must be in one of the forms shown above, and should not include leading or trailing dots, as they would in Fortran. Also note that ELSEIF is not available as a conditional clause, although the following construct can be used instead:

Note that the special keyword NULL is taken to mean ‘the specified null value for the current map’.

Arithmetic formulae are evaluated by translation into reverse Polish notation, i.e. after taking account of operator precedence, the calculation is performed from right to left. Use brackets where necessary to override the standard order of evaluation.

Using this evaluation order, the following calculations are the same:

Manipulating grid block dataIn this case variable names should be ACTNUM, property, region number, solution data array names or one of the special keywords listed above (e.g. @PORV). The available names will be shown if H for Help is typed in response to the prompt for the formula.

If single layers, rows or columns are being edited, the required layer, row or column number should be given in parentheses following the array name, e.g. layer 3 of the PORO array should be specified as PORO(3).

Similarly, for solution data a single time step can be specified by entering the time-step number in parentheses, e.g. step 3 of the PRES solution should be specified as PRES(3).

Example 1:

Example 2:

Note Note that variable names containing symbols (e.g. FLOOIL+) cannot be handled in arithmetic formulae. When reading properties from an external file (e.g. ECLIPSE restart file), ensure that a suitable alphanumeric internal property name is used in GRID.

IF ( condition1 ) THEN val1 ELSE IF ( condition2 ) val2 ELSE null ENDIF ENDIF

"Opr property"Enter operation '= PORO * 2 + 0.01 - 1 / 4'"Opr property"Enter operation '= -0.25 + 0.01 + (poro*2)'

IF ( @PORV(1)<0.000001 ) THEN 0 ELSE 1 ENDIF

PRES - PRES(0)


www.cadfamily.com


Sampling maps or surveys or operating on meshesIn this case variable names should be map or survey names. Stratum numbers for maps should be entered in parentheses, e.g. stratum number 1 for the TOPS map should be specified as TOPS(1). Horizon numbers for surveys should be entered in parentheses and may be followed optionally by the letter T (for time horizons) or D (for depth horizons), e.g. time horizon 10 for survey NETH should be specified as NETH(10T). If no letter is specified the user will be prompted for each horizon given (in an order determined by the reverse polish string for the given formula).

Example 3:

To change units of tops map from metres to feet:

Example 4:

To calculate thickness map of the two strata:

Example 5:

To obtain the positive difference between maps:

Example 6:

To fill in null data on MAP(1) with values from MAP(2):

Example 7:

It is often useful to fill in null mesh data on a map by interpolating the non-null values. This could be done by modifying the command in Example 6, or, more easily, by using the @FILL function:

It may be necessary to use option P.2.5.9.4.7 “Tog nul bnd” to fill a region of null values.

Filling LGR property and region valuesThe @FILL_L function can be used to fill in LGR property and region data. The LGR should first be selected, and then either option "Def prp lay", "Def prp are" or "Opr property" (P.3.8.5.2/3/8, see page 385, page 386, page 391) can be used to fill in property data, or option "Def reg lay", "Def reg are" or "Opr region" (P.3.8.4.2/3/8, see page 376, page 377, page 382) can be used to fill in region data.

@FILL_L copies data values from a parent grid to a grid refinement. It has no effect on the global grid. If LGR properties or regions are not defined then ECLIPSE uses the host cell values, so it is not necessary to use @FILL_L. However the operation is useful for defining LGR properties and regions so they can be subsequently modified.

TOPS(2)*3.2808

TOPS(2)-TOPS(1)

IF ( (TOPS(2)-TOPS(1))>0.0 ) THEN TOPS(2)-TOPS(1) &ELSE 0.0 ENDIF

IF (MAP(1) EQ NULL) THEN MAP(2) ELSE MAP(1) ENDIF

@FILL


www.cadfamily.com


Filling property nullsTwo functions @FILL and @FILL_A can be used from the "Def prp lay", "Def prp are" and "Opr property" options (P.3.8.5.2/3/8, see page 385, page 386, page 391) to fill in null property data.

When used to fill null property values the @FILL function uses the same interpolation algorithm as the FILL program, discussed below.

The @FILL_A function works in the same way as the @FILL function, and gives the same results as @FILL when used from the "Opr property" or "Def prp lay" option. However, when used from the "Def prp are" option, the interpolation algorithm only uses data within a defined area of the grid.

Note The way the FILL program works is described in the "FILL Reference Manual". Data is interpolated layer by layer using an inverse distance weighted average. However, instead of searching for nearby data points within a given search radius, the algorithm looks for data at any distance but only along grid rows and columns. This makes it a very quick way of filling in data values, but also means it should be used with some care.

ExamplesThe run file FILL.RF provided with the example model SNARK creates five new properties and fills in values using five different methods.


www.cadfamily.com


• A new property EXAMPLE1 is created and defined by sampling the map PORO(1). Values are only defined within a central area because a small search radius has been used. Null values are then filled using @FILL.

-- Demonstration of the @FILL function ------------------------------------------------------------------- Example 1: Sampling data from a map and using @FILL to extrapolate -- points outside the search radius--"Edt grid"Enter the name of the modelor RETURN for menu options 'snark'Enter the name of the grid 'colorado'Enter name of map ( H for Help ) 'poro'Enter stratum number ( H for Help ) '1'Draw contours ? (Y/n) 'Y'"Edt blocks""Edt property"Enter property name ( enter H for Help ) 'example1'Create new property EXAMPLE1 ? (Y/n) 'Y'Enter property units ( H for Help ) 'fraction'"Def prp lay"Enter number of layer or RETURN for 1T ' 'Enter value (or S to sample map or A for map averaging) 's'Enter name of map or RETURN for PORO 'PORO'Enter stratum number or RETURN for 1 ' '"Blk centre"WARNING - Null value returned at highlighted point(s)...&Enter value for null points or RETURN for -.100000E+21 ' 'Interpolation complete...&

...

...

"Def prp lay"Enter number of layer or RETURN for 1T ' 'Enter value (or S to sample map or A for map averaging) '@fill'


www.cadfamily.com


• The above example is repeated but using a larger search radius. There are no null values. One possible advantage of using @FILL in this situation is that the standard interpolation methods may not be stable if used to extrapolate outside the data points.

-- Example 2: Extending the search radius--

...

...

"Edt map" Enter name of map or RETURN for PORO 'PORO'Enter stratum number or RETURN for 1 ' '"Edt contours""Smp contours""Chg interp""Def sch rad"Variable, Optimal or Fixed search radius ? (v/o/F) 'F'Enter fixed search radius or RETURN for .35 '.7'Enter max no. of empty octants or RETURN for 7 ' '"Return""Return""Return""Return"Save map on disk ? (Y/n) 'n'"Edt grid"Enter the name of the grid or RETURN for COLORADO 'COLORADO'Enter name of map or RETURN for PORO 'PORO'Enter stratum number or RETURN for 1 ' '"Edt blocks""Edt property"Enter property name ( enter H for Help ) 'example2'Create new property EXAMPLE2 ? (Y/n) 'Y'Enter property units ( H for Help ) 'fraction'"Def prp lay"Enter number of layer or RETURN for 1T ' 'Enter value (or S to sample map or A for map averaging) 's' Enter name of map or RETURN for PORO 'PORO' Enter stratum number or RETURN for 1 ' ' "Blk centre"Interpolation complete...&


www.cadfamily.com


• The map PORO(1) consists of porosity values at six points. The property EXAMPLE3 is defined by transferring these values to the grid (using "Def prp blk"), then using @FILL. The interpolation method used by @FILL is not as good as the ones available when sampling maps, but in this example gives similar results.

-- Example 3: Using @FILL to interpolate a sparse data set--"Edt property"Enter property name ( enter H for Help ) 'example3'Create new property EXAMPLE3 ? (Y/n) 'Y'Enter property units ( H for Help ) 'fraction'"Opr property"Enter operation '=null'"Def prp blk"Enter property value '.39'"DATA POINT" ' 552855.937500' ' 6806080.000000'"Def prp blk"Enter property value '.35'"DATA POINT" ' 555518.625000' ' 6805977.000000'"Def prp blk"Enter property value '.34'"DATA POINT" ' 552581.062500' ' 6800630.500000'"Def prp blk"Enter property value '.31'"DATA POINT" ' 557236.562500' ' 6802246.500000'"Def prp blk"Enter property value '.28'"DATA POINT" ' 558559.312500' ' 6799083.500000'"DATA POINT" ' 559126.250000' ' 6803639.000000'

...

...

"Opr property"Enter operation '@fill'


www.cadfamily.com


• Example 3 is repeated but with three new data points, representing an area of low porosity at the top of the grid. Because @FILL works along columns and rows, the low porosity is propagated along the empty grid rows giving the property a striped appearance. (This is somewhat exaggerated by the choice of colours in the key.)

-- Example 4: Comparison of @FILL and @FILL_A-- Use @FILL--"Edt property"Enter property name ( enter H for Help ) 'example4'Create new property EXAMPLE4 ? (Y/n) 'Y'Enter property units ( H for Help ) 'fraction'------ Same data entered as Example 3, plus three new points:---"Def prp blk"Enter property value '.21'"DATA POINT" ' 555312.500000' ' 6808383.500000'"DATA POINT" ' 555570.187500' ' 6808280.500000'"DATA POINT" ' 555879.437500' ' 6808332.000000'

...

...

"Opr property"Enter operation '@fill'


www.cadfamily.com


• The problem in Example 4 can be overcome by using @FILL_A to fill the grid in two stages. The porosity in the lower part of the grid is filled first, based only on the initial six porosity values. It is therefore the same as the porosity in Example 3.

It is worth noting that the @FILL function does not take any account of faults in the grid. This may be reasonable. For example, if the grid layer represents a geological layer then porosity might be expected to be the same on either side of a fault. On the other hand, if the property is discontinuous across a fault, the @FILL_A command can be used from "Def prp are".

The interpolation algorithm measures distances horizontally. Therefore, when interpolating across a fault the vertical throw does not affect the answer. If the grid slopes or is distorted in one direction, then the horizontal distance will slightly under-estimate the true distance measured within the formation, giving extra weight to data in this direction. However, it should be remembered that interpolation used in @FILL is already biased towards data in certain directions (along rows and columns) and this extra bias is unlikely to make the answers any worse.

-- Example 5: Comparison of @FILL and @FILL_A-- Use @FILL_A on the same data--"Edt property"Enter property name ( enter H for Help ) 'example5'Create new property EXAMPLE5 ? (Y/n) 'Y'Enter property units ( H for Help ) 'fraction'------ Same data entered as Example 4---

...

...

"Def prp are"Enter number of layer or RETURN for 1T ' 'Define area by digitizing, box limits or region number ? (D/b/r) 'D'"DATA POINT" ' 551378.500000' ' 6806389.500000'"DATA POINT" ' 559401.125000' ' 6806338.000000'"DATA POINT" ' 560363.125000' ' 6798722.500000'"DATA POINT" ' 549746.500000' ' 6798722.500000'"End"Enter value (or S to sample map or A for map averaging) '@fill_a'"Def prp lay"Enter number of layer or RETURN for 1T ' 'Enter value (or S to sample map or A for map averaging) '@fill'


www.cadfamily.com

666 Arithmetic Formulae GRID Reference Manualwww.cadfamily.com EMail:[email protected] document is for study only,if tort to your rights,please inform us,we will delete

www.cadfamily.com

GRID Reference Manual Dictionary of AbbreviationsIntroduction

667

Appendix HDictionary of Abbreviations

IntroductionThe construction of menu options in GRID has been formalised so that each option is constructed in the form:

<Verb> <Object>

Verbs appear as three letter abbreviations, except in rare cases. For example the verb ‘Change’ always appears as ‘Chg’. When using the “Set option” facility many verbs may be abbreviated further, to one or two letters.

Objects will appear as the full word for single word object names shorter than nine letters (words longer than nine letters are shortened), or as two three-letter abbreviations for double word objects, for example, ‘Contour line’ appears as ‘Cnt lne’. All menu options are constructed out of the following verbs and objects:


www.cadfamily.com

668 Dictionary of Abbreviations GRID Reference ManualVerbs

Verbs

ABD abandonA ADD add

ARB arbitraryASP aspect

B BLD buildCA CAL calculateCH CHG change

CLR clearCLP clipCLS closeCON continueCNV convert

C CPY copyCR CRE create

DEC decrementDF DEF define

DEL deleteDEP depthDSP displayDIV divide

E EDT editEQ EQU equaliseEX EXE executeX EXT exitGO GO goto

GRD gridHG HGH highlight

INC incrementI INP inputJ JN join

JMP jumpLS LST listL LOD load

MAK makeMAP mapMRK mark


www.cadfamily.com

GRID Reference Manual Dictionary of AbbreviationsVerbs

669

MSK maskM MOV move

NEW newNUM numberOPN openOPR operate

O OUT outputOVL overlay

PN PAN panP PLT plotRF REF refresh

REL relocateREM removeRES reset

RO ROT rotateSIM simulator

S SMP sampleSQ SEQ sequence

SET setSH SHO showSP SPL split

STP stepSTR straighten

T TST testTO TOG toggleU UNZ unzoomUT UTI utilsV VOL volumetrics

VRT verticaliseZ ZM zoom

TBL Top,bck,lftTFL Top,frt,lftTBR Top,bck,rgtTFR Top,frt,rgt


www.cadfamily.com

670 Dictionary of Abbreviations GRID Reference ManualNouns

Nouns

ACT activeACT ARE active areaACT BLK active blockACT LAY active layerACT PEN active penADV adviceALL BLK all blocksALL LGR all fine gridsALL NDE all nodesANG angleARE areaAXS GRD axes gridBCK CNT back contourBCK backwardBLL bellBLK blockBLK FLL block fillBLK VAL block valueBLU blueBND boundaryBOX boxCAP captionCAP TXT caption textCRS GRD coarse gridCLR colourCOL REP colour representationCOL columnCOL-FLT column to faultCOL-SLP column to slopeCNT contourCNT INT contour intervalCNT LBL contour labelCNT LNE contour lineCNT PNT contour pointCNT VAL contour valueCTL COL control column


www.cadfamily.com

GRID Reference Manual Dictionary of AbbreviationsNouns

671

CTL ROW control rowCNT SEG contour segmentCRD coordinatesCRD LNE coordinate lineCRD LVL coordinate levelCRD TCK coordinate tickCRN cornerCRN VAL corner valueCRS SCT cross sectionDBG debugDEP depthDEP ARE depth areaDEP CNT depth contourDEP LAY depth layerDEP LNE depth lineDEF RNG depth rangeDFF differenceDIG SEG digitize segmentDIG TBL digitizing tableDMP FAC damping factorDSP displayDSP BOX display boxDSP PEN display penDSP PLN display planeDIS distanceDWN downELE elementEXP examplesEXP FAC expansion factorFLT faultFLT CUT fault cutFLT LNE fault lineFLT NME fault nameFLT NDE fault nodeFLT PEN fault penFLT REG fault regionFLT SEG fault segmentFLT TCK fault tick markFET SEG feature segmentFET feature


www.cadfamily.com


FET NME feature nameFLE fileFLL fillFLL REP fill representationFNE GRD fine gridFIP fluids-in-placeFNT fontFOR forwardGRA graniteGRT graticuleGRT LVL graticule levelGRT TCK graticule tickGRN greenGRD gridGRD DBG grid debugGRD DSP grid displayGRD SEG grid segmentHCH hatchHDR headerHGT heightHGH highlightHIS historyHOR horizonHOR NUM horizon numbersINI PEN inactive penIND indexINP FMT input formatINT interpINT FLT interpolation faultsINT MOD interpolation modeINV intervalIO input outputIRR GRD irregular gridKEY keyKEY BCK key backgroundKEY TXT key textLFT leftLIM limitsLAB labelLAY layer


www.cadfamily.com


673

LEG legendLGR LGRLNE lineLOC locatorMAJ CNT major contourMAJ PEN major penMAJ SEG major segmentMAJ SEG major textMAP mapMRK markerMIN MAX minimum/maximumMIN PEN minor penMIN TXT minor textMIN SEG minor segmentMEN menuMSH meshMSH CNT mesh contourMSH PEN mesh penMSH PAR mesh parametersMSH VAL mesh valueMIN MAX minimum maximumMSC PNT miscellaneous pointMIS mistieMOD modelNDE nodeNDE DEP node depthNDE-NDE node to nodeNDE-FLT node to faultNDE VAL node valueNUM DEC number of decimalsNUM LBL number labelsNUM STR number of strataNLL nullNXM nxmOPT optionORG originORG TXT origin textOUT FMT output formatPAR parametersPTH path


www.cadfamily.com


PEN penPIC picturePNT pointPNT MRK point markersPOS positionPRJ DBG projection debugPRC precisionPRP propertyPRP ARE property areaPRP BLK property blockPRP CNT property contoursPRP FLL property fillPRP KEY property keyPRP LAY property layerPST postingPST TXT posting textRED redREG regionREG ARE region areaREG BLK region blockREG CNT region contoursREG FLL region fillREG KEY region keyREG LAY region layerRES resultsRGT rightROW rowROW-FLT row to faultROW-SLP row to slopeRPT reportSCL FAC scaling factorSCR FMT scratch formatSCH CRL search circleSCH RAD search radiusSCT sectionSEG segmentsSET settingsSHD shadingSHT LNE shot lineSHT NUM shot number


www.cadfamily.com


675

SHT PEN shot line penSHT PNT shot pointSHT VAL shot valueSIZ sizeSLP slopeSLP LIN sloping lineSMP CNT sample contoursSOL solutionSOL CNT solution contoursSOL FLL solution fillSOL KEY solution keySPC spacingSTR stratumSTY styleSVY surveySVY CNT survey contoursSVY PAR survey parametersSYM symbolTBL DBG table debugTXT textTHK thcknssTHK ARE thickness areaTHK CNT thickness contoursTHK LAY thickness layerTHK RNG thickness rangeTCK tickTRN VAL truncation valuesTYP typeUNIT unitUP upUTL utilVAL valueVAL LBL value labelsVAL TXT value textVEC vector gridVPT viewpointVOL volumesVOL CNT volume contoursVOL FLL volume fillWLL well


www.cadfamily.com


WLL NME well nameWLL SYM well symbolWLL TXT well textWID widthWSP wrkspcXY xy-planeXYZ x,y,zXZ xz-planeYZ yz-planeZM zoomZON zoneZON LBL zone labelsZON SEG zone segment3D FLL 3d fill3D GRD 3d grid3D MAP 3d map45 DEG 45 degrees135 DEG 135 degrees225 DEG 225 degrees315 DEG 315 degrees


www.cadfamily.com

GRID Reference Manual Glossary of Terms 677

Appendix IGlossary of Terms

Active block

A block which has not been declared inactive and consequently will be included in a subsequent simulation by ECLIPSE or other simulator.

Advice line

A single line at the bottom of the screen for displaying advice or messages to the user.

Fine grid

A locally refined area of the grid.

Back contours

Contours redrawn from scattered data (digitized contours, seismic shot lines, simulation grid data, spot values).

Coordinate box

Box bounding area of interest.

Caption

Text on a map.

Coarse grid

Main grid which may optionally contain a fine grid.

Colour representation

Red, green, blue components of a colour.

Contour

A line of data points having the same associated value (may be a single point).

Contour interval

Difference in value between adjacent contours.


www.cadfamily.com

678 Glossary of Terms GRID Reference Manual

Contour segment

Part of a digitized contour line used in the construction of another line.

Control column

A line constructed in the “Irregular” grid option for controlling the path of a grid column.

Control row

A line constructed in the “Irregular” grid option for controlling the path of a grid row.

Coordinate line

A line from the top to bottom of the simulation grid. All grid nodes must lie on coordinate lines.

Digitized segment

A part of a line which is input manually.

Digitizing table

A tablet or table which can be calibrated for data input.

Damping factor

A interpolation parameter controlling smoothing for polynomial surface fitting.

Display

Current screen display except for header, advise and menu areas.

Display box

The box of rows, columns and layers currently included in the simulation grid display.

Expansion factor

Text output parameter describing the distance between characters.

Fault

A line along which a contour map is discontinuous.

Fault zone

The area on a map delimited by a sloping fault.

Fault segment

Part of a fault which is included in the construction of another line.

Feature

A line on the map representing an object which has no effect on the contour surface (e.g. lease-lines, reservoir boundaries, fluid contacts).

Feature segment

Part of a feature which is included in the construction of another line.

Fill

A coloured or hatched area.


www.cadfamily.com


Fill representation

The bundle of parameters controlling the way in which an area is filled.

Fluids-in-place

Volume data calculated from simulation grid data.

Font

Text style.

Granite

The library of device drivers used by the GRID and GRAF programs. Provides facilities for setting colours and styles for all texts, lines, markers or filled areas.

Graticule

Line of latitude or longitude.

Grid

Simulation grid.

Grid segment

Line along grid rows and/or columns used in the construction of another line.

Header

Two line area at the top of the screen used to display information to the user.

Horizon

A surface identified from seismic sections.

Interpolation

The process of obtaining an estimate of the value of a parameter on a surface away from data points.

Interpolation mode

The method used for interpolation.

Irregular grid

A grid constructed such that nodes do not lie along straight lines.

Key

Display of colour fill limits.

Layer

A simulation grid layer.

Legend

Box containing information about markers and styles used on a map.

Locator

The pointing device used to control the cross-hairs or screen cursor.


www.cadfamily.com


Major contour

A contour optionally drawn in a different linestyle from the majority of contours.

Major fault segment

Part of a fault line at which a discontinuity is assumed for both interpolation and contouring back.

Map

A picture which may contain wells, faults, contours, features, captions and zones.

Marker

A symbol used to mark a single point on the picture.

Minor segment

Part of a fault line at which a discontinuity is assumed only when contouring back.

Mesh

A regular grid used by mapping packages for storing and manipulating surface information.

Mesh contour

A contour drawn from a mesh.

Miscellaneous point

An isolated shot point along a shot line which can be input without checking for acceptable spacing.

Mistie

The difference between data values on picked horizons at points where shot lines cross.

Model

The total collection of data available to the user in the current GRID session.

Node

The intersection point of a grid row and a grid column.

Null value

A point for which no value is known or can be interpolated using the current parameter settings.

Origin

The point on a map from which all grid distances are measured.

Path

The list of option selections required to get from one point in the menu tree to another.

Pen

The attributes of a line.

Picture

Element of screen display for building plotter output.


www.cadfamily.com


Precision

The accuracy with which text is drawn on the screen. Text may be hardware, character or stroke precision (see Appendix C).

Property

Non-integer values stored for each grid block e.g. porosities, permeabilities, net-to-gross ratios.

Region

Integer values stored for each grid block, e.g. equilibration region numbers, saturation table region numbers.

Scaling factor

Text output parameter describing the lengthwise stretching of characters.

Search radius

The radius of the circle within which points will be included for interpolation.

Section

Display along a seismic shot line.

Segments

Local picture storage capability on some graphics devices.

Shading

Colour sequence from one colour to another using small changes in colour representation (depending on device capability).

Shot line

Areal trace of a seismic line.

Shot point

Single data point on a shot line.

Shot number

Shot point number of data point on a shot line.

Shot value

Value at a data point on a shot line.

Slope

Inclination of a coordinate line to the vertical.

Solution

Output array from a simulator containing data at a time step for all active blocks.

Stratum

A map layer.

Survey

A series of interpreted seismic shot lines or seismic navigation lines.


www.cadfamily.com


Truncation values

Limits for interpolated values.

Volumetrics

Volume data calculations.

Well

A point on a map marked by a well symbol.

Workspace

Computer memory and diskspace allocated for use by GRID.

Zone

An area on a map which may be filled with colour or hatching.

Zone segment

Part of the boundary of a zone which may be used in the construction of another line.

Zoom

Show only a part of the full picture on the screen.


www.cadfamily.com

GRID Reference Manual Unit Conversion FactorsIntroduction

683

Appendix JUnit Conversion Factors

IntroductionThe following units are recognized in GRID:

The ‘standard’ unit for each type is given first (e.g. METRES) and the line below will contain the absolute unit (1.0). On the same line as the standard unit, it is possible to have a further 4 sub-units (e.g. FEET, CM, etc.) and below each sub-unit is the conversion factor from the given sub-unit to the ‘standard’ unit. Unit names are restricted to 8 characters.

The following additional units are used for conversions within the program, e.g. to write out transmissibilities in units required by a third party simulator:

METRES FEET CM KM KFT 1.0 .3048 .01 1000.0 304.8FRACTION PERCENT 1.0 .01 MDARCY DARCY1.0 1000.MSEC SEC1.0 1000.M3 ACRE-FT STB RB MCF1.0 1233.4818 0.15898 0.15898 28.32 M/SEC 1.0

CPM3/D/B CPM3D/KP 1.0 0.01CPB/D/PS MD-FT 1.0 887.311


www.cadfamily.com

684 Unit Conversion Factors GRID Reference ManualIntroduction

The abbreviated names are as follows:

Transmissibility units:

Angular units:

The units available are stored in a file called ‘MENUS’ which is located in the help directory for the program. This file contains all the menus for the program, a finite list of valid verbs and nouns, and the units, which are at the end of the file. (The location of this file is defined in the configuration file., as described in Appendix M.)

If it is required to make use of a unit that is not in the default list, it may be added to the default list by editing the ‘MENUS’ file.

Caution If editing the ‘MENUS’ file, it is very important to do so with extreme caution. It would be advisable to make a backup copy of the file (e.g. MENUS.SAV) before making any changes. Do not delete any units that are already defined.

There is a maximum limit of 50 different types of units that may be defined (e.g. METRES, MSEC etc... ). For each type of unit, up to 4 further sub-units (e.g. FEET, CM etc. ) may be defined if required.

ANG_RAD ANG_DEG 1.0 0.017453292

CM centimetreKM kilometreKFT thousand feetMSEC millisecondM3 cubic metreACRE-FT acre-footSTB standard barrelRB reservoir barrelMCF thousand cubic feetM/SEC metres / second

CPM3/D/B cP.m3/day/bar (centipoise-m3/day/bar)CPM3D/KP cP.m3/day/kP (centipoise-m3/day/kiloPascal)CPB/D/PS cP.rb/day/psi (centipoise-barrel/day/psi)MD-FT millidarcy-foot

ANG_RAD radiansANG_DEG degrees


www.cadfamily.com

GRID Reference Manual Unit Conversion FactorsSampling values for simulation grids

685

Sampling values for simulation gridsNote that GRID does not perform any conversions automatically when sampling values for simulation grids.

When numbers are sampled from depth maps, for example, they are copied directly to the grid without further conversion. Therefore if depth maps are defined in METRES, the corresponding grid must be created with depth units of METRES. If necessary, unit conversion can be performed by the user after maps have been sampled. For depth values, use menu option P.3.9.3.5, “Scl grid” (see page -418), to scale the entire grid in the Z-direction. For property values, menu option P.3.8.5.8, “Opr property” (see page -391) can be used to multiply all values of a property by a suitable conversion factor.

When grid data are output to a .GRDECL file for input to the simulator (see menu option P.3.9.2, “Out grid”, page -408), unit conversions will be performed correctly, from the units used internally in GRID to the units requested for output. E.g., if a simulation is to be run in Field Units, the grid can be output in FEET.


www.cadfamily.com

686 Unit Conversion Factors GRID Reference ManualSampling values for simulation grids


www.cadfamily.com

GRID Reference Manual UKOOA Formats 687

Appendix KUKOOA Formats

If the model has a map projection defined, it is possible to input and output the following data in Latitude and Longitude:

• Well symbols

• Fault traces


• Features

• Zones

• Seismic navigation

Data can be input or output in the following format:

where:

Zline,Isht, Ideg,Imin,Rsec,Zns, Ideg,Imin,Rsec,Zew, Reast, Rnrth-----Latitude----- ----Longitude----- --X-- --Y--

Zline = Line name

or contour Z-value

(character A16)

(real number)Isht = Point number (integer I8)Ideg = Degrees Lat (integer I3)Imin = Minutes Lat (integer I2)Rsec = Seconds Lat (real F6.3, F4.1 or F5.2) **Zns = North/South (character A1)Ideg = Degrees Lon (integer I3)Imin = Minutes Lon (integer I2)Rsec = Seconds Lon (real F6.3, F4.1 or F5.2) **Zew = East/West (character A1)Reast = Easting (X) (real F10.1 or F9.1)


www.cadfamily.com

688 UKOOA Formats GRID Reference Manual

The Easting and Northing fields are ignored when reading data.

To input or output data in UKOOA format, at the prompt for the required format enter ‘UK84’ , ‘UK85’ , or ‘UKECL’ to invoke one of the above formats.

For example, to input some wells in UKOOA format:

Note that when reading data into the program via an input option, no header records are assumed. The user must use the option “Next line” to skip through the data file to the first data point to be read.

Similarly, when writing data from the program via an output option, no header records will be written.

Output in decimal degreesFormats are also available for input and output of Latitude and Longitude in decimal degrees. (This facility is currently available for well data, feature lines, faults and contours, for models where a projection is defined.)

The general format is:

where:

To select decimal degrees for input or output, enter DEG or DEGREES at the prompt for the required format.

Rnrth = Northing (Y) (real F10.1 or F9.1)** see respective formats defined below.UKECL = (I2.2,A16,I8,I3,I2,F6.3,A1,I3,I2,F6.3,A1,2F10.1)UK84 = (A16,I8,I3,I2,F4.1,A1,I3,I2,F4.1,A1,2F10.1)UK85 = (1X,A16,I8,I2,I2,F5.2,A1,I3,I2,F5.2,A1,2F9.1)

‘Edt wells’‘Inp wells’‘Enter name of file to be read...’ (enter file name)‘Clip input data ? (y/N)’ (enter Y or N)‘Next line’ (to skip any header records)‘Return’ (1st well location shown)‘Enter record format, e.g. (2E13.5,A8) or RETURN for *’

(enter UK84 )

Zname,Dlat,Dlon

Zname = Line or well name (character A16) or contour Z-value (real number)Dlat = Degrees Lat (real F13.5)Dlon = Degrees Lon (real F13.5)


www.cadfamily.com

GRID Reference Manual ConPac Interpolation & Contouring 689

Appendix LConPac Interpolation &

Contouring

ConPac is the library of interpolation and contouring routines used in GRID. These notes are intended to give the user some insight into the methods used in ConPac, with their characteristics and limitations in different situations.

GeneralThe interpolation methods used are mathematical techniques for estimating the value of a parameter at positions lying on or between points where the values are known or have been estimated. In general, the parameter can be thought of in this context as a surface (single valued function of x,y) extending over the area of interest, whose height above some datum is known at discrete locations. The surface may be discontinuous, that is, cut by vertical or sloping faults. It may also be incomplete, in the sense that the surface values are unknown (or null), or specifically divided into a number of closed regions.

Three major classes of data are identified which require different approaches to interpolation. They are distinguished on the basis of distribution of points rather than quantity, quality or degree of continuity.

Insufficient scattered data setsData sets which are not sufficient to define the supposed surface to the user’s satisfaction or over which there is some doubt. These will normally be newly digitized maps or data sets, where the control points are clustered together leaving large spaces with no values.

Sufficient scattered data setsScattered data sets which are sufficient to define the surface well enough for the purpose in hand.


www.cadfamily.com

690 ConPac Interpolation & Contouring GRID Reference Manual

Regular or semi-regular data sets Regular or semi-regular grids with data at the nodes and therefore ideally arranged to represent the surface. Normally such grids will have been derived from type (ii) scattered data sets and will be ‘‘models’’ of the surface ready for use in processes such as reservoir simulation, volumetrics or contouring. These are called ‘mesh maps’ in GRID terminology.

It is important to note that discontinuities or faults in the surfaces are more a part of the supposed ‘‘model’’ of the surface than the control data, so that the interpolation processes are constrained to observe the positions of faults only and to derive values along their edges and internal surfaces from the relevant surrounding values. In special cases fixed values can be associated with fault edges if required.

The software has a number of controls which, if carefully used, will give good results over a very wide range of data sets. However, if carelessly applied, poor results can be obtained in any situation. The default settings are intended to give reasonable results over the bulk of cases and provide a starting point for tests aimed at improving results for any class of dataset. Results are not usually very sensitive to the controls and it will be found that they can be kept constant for quite large classes of data set.

Search radiusThis is the most important parameter in the interpolation process, since it determines which control points are used in any calculation. For regular arrangements of data as in grids, it is easily chosen and can be constant over an entire map. For non-regular data the problem is much more difficult and becomes more so the more irregular the distribution becomes. The use of a fixed radius is rarely practical for normal data sets, since it is usually difficult to choose a sensible value because of local variations in data density. For large data sets it may be impractical to plot the points at all so that a visual estimate is not possible.

Two approaches to overcoming this problem are included in the software. One attempts to vary the search radius smoothly over the map area, and the other attempts to identify and fill the sparse areas. It has been found that the latter offers the more general solution and has the advantage that the user can augment or modify the results if necessary. The following four questions are the essence of the problem of choosing the relevant data for an interpolation.

• How many points are required ?

• How far do we need to go to obtain enough data ?

• How far can we go before the data are irrelevant ?

• What distribution of data is satisfactory ?

The measurable quantities referred to are number, distance and distribution of points. They are all measured with reference to the ‘‘search circle’’ centred at the interpolation point and divided into eight equal sectors or octants. The user can control (a) the radius of the circle or the way the program varies the radius, (b) the number of adjacent octants which may be empty before interpolation is deemed to be invalid and, in certain circumstances, (c) the number of points chosen in different directions.

Note that the position of each point used in an interpolation is also checked to see whether its importance is diminished or cancelled by the presence of faults.


www.cadfamily.com


Determination of the search circle

Fixed search radiusThe user must decide, by examining the distribution of data, what fixed value will always encompass enough control points to give a satisfactory interpolation. Too large a value may incur a high CPU usage and there is a buffer limit of 500 points currently in place. In the event of this buffer being filled, the search radius will be reduced locally, to obtain an acceptable sample size.

For relatively small data sets, say up to 100 points, a radius which will include them all from any position can be a reasonable choice. The weighting function will ensure that each is honoured to the degree allowed by the damping factor. For larger data sets this will not be satisfactory and a radius must be chosen which will encompass only local subsets of the data.

Again it is the weighting function which allows this ‘‘sliding’’ window since it ensures that the weights of points on the edge of the circle are zero and that they increase steadily to a maximum as they approach the interpolation point.

With line-oriented data such as digitized contours or seismic shotline data it is better to include in the circle a given number of lines of data irrespective of how many points this represents. The corollary of this is that when digitizing contours it is better to have more contours than more points on existing ones.

Optimal search radiusIf ‘Optimal Search Radius’ is requested, the program attempts to find the most suitable fixed radius for the entire map. Processing is then as for ‘Fixed Search Radius’.

Variable search radiusThe user controls the computation of a ‘‘mean value’’ for the search radius and the magnitude of excursions away from this mean value. The mean value calculation is based on statistics which assume that the data are clustered along lines, and seeks to find the radius which will, on average, encompass a certain number of these lines.

Use of variable search radius is not appropriate for scattered data points.

‘‘Test map’’ and radial search processThe program scans the map area for relatively sparse areas within the main body of data and computes strategic locations for points which will improve the distribution, to the point where a known, fixed search radius will always yield sufficient points. Values are obtained for these points by the use of a radial search in each of sixteen sectors. The search terminates when enough points have been found or if no points exist anywhere in that sector. The user specifies the minimum requirement in each sector and the number of points to be seen on average in the fixed radius. This method has proved to be very useful in this context of making estimates of values at long distances from data. It is, however, not suitable for computing grid values directly, since in allowing a free range to the search process the continuity property imparted by the weighting function has been lost.

Search circle checksHowever the search radius is arrived at, the rules applied to decide whether the data are adequate in each case are as follows.

• The absolute minimum number of non-null points varies with degree of polynomial surface being fitted:


www.cadfamily.com


full second order minimum = 6

reduced second order minimum = 5

plane minimum = 3

average minimum = 1

In practice these numbers are rarely enough since their distribution in the circle is also important (e.g. any number of co-linear or co-cyclic points will be insufficient for fitting a second order polynomial surface) and we should ensure a reasonable spread.

• Distribution.

Distance of nearest non-null point must be as follows:

• Less than 0.7 of the search radius when gridding or sampling from scattered data of type (ii).

• Less than 1.414 when sampling from a rectangular grid with the standard radius of 2.05 grid meshes. For larger radii the limit is increased proportionately, i.e. data of type (iii).

• Less than 0.8 of the search radius when using the radial search technique. Normally data of type (i).

The maximum number of empty octants lying adjacent to each other in the circle must be less than or equal to the specified value except when sampling from data of type (iii) when the octant check is not used.

Note that a value of 4 or 5 for the adjacent octant limit has the useful effect of ‘‘trimming’’ the gridding operation fairly close to the main body of data. A value of 7 effectively eliminates the check and gives good coverage in gridding operations, but poor interpolations may result from using inadequate clusters of data. Values of 0, 1 and 2 are usually much too cautious and many perfectly good values will be replaced with nulls.

Polynomial surface fitting and the weighting functionFirst and second order polynomial surfaces can be chosen in the gridding and sampling operations. These are fitted to the data in the search circle using a weighted least squares criterion. Best results seem almost always to result from the use of a reduced second order surface. This is the lowest order polynomial surface allowing interpolations above or below observed values and is generally more stable, requires fewer points to define it and less arithmetic for the least squares fit than the full paraboloid.

The degree of surface continuity and the degree of honouring of control points are both simultaneously controlled by modification of the weighting function. Surface continuity is controlled by the program using the fault data, while the user may adjust the ‘‘Damping factor’’ to achieve a smoothing effect on the data during gridding. A small damping factor causes the weighting function to be strongly ‘‘peaked’’ giving very high weighting to control points near the interpolation point. A large damping factor ‘‘flattens’’ the function and reduces the effect of local, unwanted variations. Digitizing ‘‘noise’’ can be effectively eliminated by this means.

The actual choice of damping factor depends on the characteristics of the data in use and is generally arrived at empirically. The very low default value gives effectively ‘‘deterministic’’ interpolation.


www.cadfamily.com


Exponential truncationThis process is able to modify the surface shapes produced by the polynomials. High and low points, either global or local (within the search radius), are modified so that a chosen level is never exceeded and so that the surface generated over an area is slope-continuous with the unmodified surfaces surrounding it. It should be noted that the surface is kept within a limit which lies beyond the chosen value and not within the chosen value itself. The degree to which it may pass beyond the value is given by the truncation tolerance. To retain the slope-continuous effect the tolerance should not be very small; if the tolerance is set to zero the program will simply truncate to the chosen floor or ceiling level. Local exponential truncation uses the highest and lowest values in the search circle as its local ‘‘floor’’ and ‘‘ceiling’’. This facility is a most effective way of controlling surfaces generated from digitized contour maps. A peculiarity of such maps is that the absence of a contour usually implies that the surface does not reach that level, and so it is important that the interpolation process should take account of this.

Interpolation around faultsAlthough mathematical and logical problems in the neighbourhood of discontinuities cause severe programming problems, the rules from the user’s point of view are straightforward. The program regards all discontinuities as closed regions (e.g. vertical faults are constructed by the program as very steep narrow zones). This is to ensure that the surface is singled-valued everywhere, i.e. no point has more than one value.

Values exactly on the edges of the faults are obtained by interpolation using only ‘‘visible’’ points outside the fault region and any control points provided on the edge itself, unless the edge is transparent when it will not affect the choice of control points.

Values for points lying on the fault plane are treated differently depending on whether scattered or gridded data are in use. When sampling scattered data, a null value will be returned unless there are sufficient data inside the zone to enable the interpolation or alternatively if a transparent edge (minor fault) allows a view of the data beyond it. When sampling from a grid or mesh, values inside a fault zone are obtained by reference to the edge data (themselves obtained from outside) so that an accurate ‘‘join’’ is obtained exactly on the fault edge between the fault plane and the fault-block surface beyond. This latter condition is vital for all modeling, volumetric and contouring processes.

During gridding operations GRID ensures that a secondary pass is made to replace null values on fault planes with values obtained as described above.

ContouringContouring is performed on any data of type (iii), i.e. any regular or semi-regular grid or mesh. The contouring algorithm is unique to ConPac and is notable for the quality of map produced, its speed of execution and its ability to deal with discontinuities and colour “fill” in a rigorous and satisfactory way. The user specifies contour interval and fill data, etc., and “contour quality”. The latter is an integer number and simply specifies the number of subdivisions of the grid or mesh which is to occur while drawing the contours. Quality 1 means contour the mesh as it is, quality 2 means divide each cell into four subcells using a bi-cubic surface with slope continuity everywhere away from fault edges before contouring, quality 3 means divide into 9 subcells, and so on.


www.cadfamily.com


While the program is contouring the word ‘‘linking’’ appears on the screen with a count of the number of rows of subcells processed. The computation and drawing of the contours with or without fill are distinct operations, so that once computed they can be drawn as often as required with different fill colours, etc., without re-computing.


www.cadfamily.com

GRID Reference Manual Use of Configuration FilesIntroduction

695

Appendix MUse of Configuration Files

IntroductionThe configuration file (“config file”) is the primary method of passing configuration data to GRID and other programs in the ECLIPSE suite of software. It can be used to configure several aspects of a system for use with the programs (e.g. graphical devices such as plotters), as well as other site-dependent data, such as passwords.

The following configuration file parameter sections are most important for users of GRID:

This Appendix gives guidelines on use of configuration files with GRID, including details of the SYSTEM, GRID, HELP and GRANITE sections. The DIGITISERS section is described in Appendix E. For further details or updates, please contact SIS customer support.

Configuration file typesOn start-up, GRID will process the standard ‘master’ configuration file, ECL.CFG, and any auxiliary files (ECL.CFA, ECL.CFU), if present.

• SYSTEM section: system set-up options such as the file naming convention.

• GRID section: dimensioning parameters for dynamic memory allocation as well as flags for formatted files and the digitizer bleep.

• DIGITISERS section: set-up parameters for digitizing tables• HELP section: file locations for program menus and help.• GRANITE section: parameters for plotters and display devices.


www.cadfamily.com

696 Use of Configuration Files GRID Reference ManualIntroduction

The standard configuration file is mandatory and must be present in the system area from which a package is executed: this is usually managed within the macro that starts up the program, which copies the ‘master’ configuration file to your local directory. (The ‘master’ file is normally copied from a file called CONFIG.ECL, which can be found in the directory containing the macros for running SIS software.)

The auxiliary configuration files are optional, and if present will be processed in the same way as the main configuration file. Parameters declared in the auxiliary files will be added to, or replace, data read from the main config file. The auxiliary files can be used to set up user-dependent or run-dependent parameters without altering the master configuration file (e.g. for experimenting with new driver configurations).

ECL.CFU is the user-specific configuration file. If used, it should be stored in the user’s login directory. It will be copied to the working directory by the macro that runs the program, and removed from that directory after the program exits. Any parameters set in ECL.CFU will override those in ECL.CFG.

ECL.CFA is the local auxiliary configuration file which resides in the working directory and overrides both ECL.CFG and ECL.CFU. It will not be overwritten or deleted by the program macros.

(A third auxiliary configuration file, ECL.CFM is created by some macros when running a program. This is used for run-time information and is not important for GRID parameters as described here.)

An example of usage of the auxiliary configuration files might be: ECL.CFU is used to define a preferred font for a user’s workstation, while ECL.CFA is used to specify the file naming convention for a particular model in its local directory.

Configuration file structure The configuration file is divided into several sections, declared using the keyword SECTION, e.g.:

SECTION PASSWORDSSECTION SYSTEMSECTION GRIDSECTION GRAFSECTION EXTRACTSECTION DIGITISERSSECTION HELPSECTION PLOTITSECTION GRANITESECTION ALPHASECTION GRANULESECTION SYMBOLSECTION FRAMEWORKSECTION FRAMEDRAW


www.cadfamily.com

GRID Reference Manual Use of Configuration FilesIntroduction

697

Sections may be declared in any order, and may also be subdivided into Subsections by using the keyword SUBSECT. For example the GRANITE Section is divided into Subsections:

Notes• Comment lines may be inserted anywhere in the configuration file, beginning with two

hyphens “--” in the first two columns.

• Blank lines are ignored.

• Keywords should be entered in the form of one keyword/argument pair per line, with at least one blank space after the keyword.

• The type of argument used will depend on the keyword and may be integer, real, character or logical. Character strings need not be enclosed in quotes. Logical arguments may be abbreviated to a single letter, i.e. T for TRUE or F for FALSE.

• The end of the file is denoted by a single keyword “END.”

SECTION GRANITESUBSECT DRIVER 1...SUBSECT DRIVER 2etc.


www.cadfamily.com

698 Use of Configuration Files GRID Reference ManualIntroduction

A simple example configuration file is shown below:

-------------------------------------------- CLIENT CONFIGURATION FILE --------------------------------------------

SECTION PASSWORDSSUBSECT 97APASSWORD A50CHARACTERCRYPTICPASSWORD------------------------------------------SECTION SYSTEMFILELOCK TRUE------------------------------------------SECTION GRIDGRIDSIZE MEDIUMFORMATTED TRUEMESHCOMP FALSEBELL FALSE------------------------------------------SECTION HELPGRIDMENU /sim/97a/grid/help/MENUSGRID /sim/97a/grid/help------------------------------------------SECTION GRANITESUBSECT DRIVER 29SELECT TRUENAME XWINDOWDESCRIPT NCD X-terminalXWDMIN 0.140YWDMIN 0.220XWDMAX 0.99YWDMAX 0.97FONTS -adobe-courier-bold-r-normal--*14*-iso8859-1RESERVE 16MAXVERT 260REPAIR FALSE------------------------SUBSECT DRIVER 38SELECT TRUENAME POSTSCRIPT 3DESCRIPT Colour PS (Landscape)ROTATE FBANOP 0XMINDC 3.4XMAXDC 27.9YMINDC 0.65YMAXDC 20.35------------------------------------------END.


www.cadfamily.com

GRID Reference Manual Use of Configuration FilesSYSTEM section

699

SYSTEM section The SYSTEM section of the configuration file specifies parameters which can be used when running various programs, including GRID. The following keywords may be applicable for a given GRID session.

File handling options:

• SUFFIX xxx

where xxx is UNIX or ANSI. The default is generally UNIX, which means that file names can use full-length extensions (e.g. CHAP.SMSPEC, CHAP.S0001,...). Models originating from older Vax or PC systems may use the ANSI suffix (e.g. CHAP.SMS, CHAP.S01,...).

• CASE xxx

where xxx is UPPER, LOWER or BOTH. The default is UPPER, which means that the file naming convention is upper case (e.g. CHAP.SMSPEC). CASE LOWER is used for lower case names (e.g. chap.smspec). CASE BOTH allows use of mixed-case file names.

• FILELOCK xxx

where xxx is logical TRUE or FALSE (default FALSE). When file locking is activated, an additional file with extension .LOK is created in the working directory whenever a file is opened (e.g. TEST.GRDECL.LOK). The presence of that file prevents other programs from opening the file while it is in use. This helps to avoid errors which might occur when programs such as ECLIPSE try to read an incomplete file that is being created by GRID.

• TMPDIR directory_location

This option allows the user to redirect scratch files on a Unix system to a specified directory instead of the system default (which is usually /tmp). Using ‘TMPDIR .’ (i.e. a single dot for directory_location) sets the directory to the current working directory. This is sometimes necessary when the space required for temporary files exceeds the space available on the default temporary disk.

Cyrillic translation:

• CYRILLIC xxx

where xxx is TRUE or FALSE (default FALSE). This flag is used to activate the Cyrillic translation option in GRID, so that text displayed using the Cyrillic font is converted according to the Russian keyboard convention.


www.cadfamily.com

700 Use of Configuration Files GRID Reference ManualGRID section

GRID sectionThe GRID section in the configuration file is used to specify the program dimensions for dynamic memory allocation. If the program executable has been set up to work with dynamic memory allocation, the default workspace dimensions can be overridden with specified parameters.

The configuration file entries in the GRID section have the following format:

where:

For example, the master configuration file at a user site might have the following entry:

A user who needs GRID dimensioned larger for a particular model, could create an ECL.CFA file with the entry:

This enables a number of users to work with different workspace dimensions, without the need to recompile or relink the program.

Note The workspace allocation is performed when GRID starts up. While the program is running, the memory requirements will remain fixed. It is still possible to run out of space during a program run, if the dimensions were set too small at the start.

The actual workspace sizes for the current program run and the amount of space in use at any time can be checked via menu option P.7.2.6, “Wkspace dbg” (see Chapter 10, page -536). If necessary, loaded data can be cleared from workspace via menu P.8, “Clr wrkspc” (see Chapter 11, page -540). However, it may be necessary to exit the program and start up again with modified dimensions, if any maximum limits are reached.

SECTION GRIDGRIDDIMS <full path name of dimensions file>GRIDSIZE <section in dimensions file to use>

GRIDDIMS points to the name of a separate file containing dimension

parameters (see below)GRIDSIZE is a mnemonic pointing to a section in the dimensions file.

SECTION GRIDGRIDDIMS /sim/macros/gridsize.datGRIDSIZE MEDIUM

SECTION GRIDGRIDSIZE LARGE


www.cadfamily.com

GRID Reference Manual Use of Configuration FilesGRID section

701

GRID dimensions fileThe dimensions file has the following format:

There is no restriction on the file name used for dimensions, as the full path name has to be entered in the configuration file. As for the config file, parameters are entered on separate lines, with blank lines and lines starting with ‘--’ treated as comments that can be ignored.

The GRIDSIZE names are used to identify the different workspace size options which can be selected. One of these should correspond to the GRIDSIZE mnemonic given in the config file.

The keywords for the parameters which can be set in the dimensions file are:

GRIDSIZE <name1><keyword1> <new value><keyword2> <new value>.... ........ ....GRIDSIZE <name2><keyword1> <new value><keyword2> <new value>.... ........ ....

NDYNB The size in BYTES of the array used for integers, logicals and single precision real numbers in GRID. (Default 40 000 000)

NDYNZ The number of eight-character words used by GRID.

(Default 40 000)ISMAX This is the only logical keyword used in this file. If ISMAX is set to TRUE

then the values of NDYNB and NDYNZ are considered to be the maximum total amount of workspace to be allocated. If ISMAX is set to FALSE then NDYNB and NDYNZ represent the extra workspace to be allocated after the fixed workspace arrays have been set up.

The fixed arrays in GRID are relatively small, so this parameter can normally be set TRUE. (Default TRUE)

MXPNT Maximum number of points in a digitized polyline. (Default 10000)

MXREG Maximum number of region number arrays. (Default 50)MXGRD Maximum number of grids. (Default 50)MXREF Maximum number of refined grids. (Default 100)MXPRP Maximum number of property arrays. (Default 50)MXCTL Maximum number of control lines. (Default 50)

MXSOL Maximum number of solution arrays. (Default 50)MXSEQ Maximum number of sequence numbers for each solution array. (Default

1000)


www.cadfamily.com


MXRSZ Maximum number of solution mnemonics. (Default 200)

MXMAP Maximum number of maps. (Default 100)MXSTR Maximum number of strata. (Default 100)

MXCPF Maximum number of captions on a map. (Default 5000)MXCTF Maximum number of contours on a map. (Default 5000)MXFEF Maximum number of features on a map. (Default 5000)MXFTF Maximum number of faults on a map. (Default 5000)MXWLF Maximum number of wells on a map. (Default 5000)MXZON Maximum number of zones on a map. (Default 500)

MXSVY Maximum number of surveys. (Default 40)MXSHV Maximum number of vectors / horizons for each seismic line. (Default 100)MXSHT Maximum number of shot lines in a survey. (Default 5000)

MXMWD Maximum number of eight-character words per line (in help). (Default 2 - this should not be modified)

MXMOP Maximum number of items in scrolling ‘help’ menu. (Default 150)

MXGWL Maximum number of general GRID wells. (Default 500)MXATW Maximum number of GRID well attributes. (Default 50)


www.cadfamily.com


703

An example dimensions file is shown below. This has three sections: LARGE, MEDIUM and SMALL..

--/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/---- File gridsize.dat---- Contains the default sizes of the data structures in Grid----/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/----------------------------------------------------------------GRIDSIZE LARGE

NDYNB 80,000,000NDYNZ 80,000

ISMAX TRUE

MXPNT = 10000

MXREG = 50MXGRD = 50MXREF = 100MXPRP = 50MXCTL = 50

MXSOL = 50MXSEQ = 1000MXRSZ = 200

MXMAP = 100MXSTR = 100MXCPF = 5000MXCTF = 5000MXFEF = 5000MXFTF = 5000MXWLF = 5000MXZNF = 500

MXSVY = 40MXSHV = 100MXSHT = 5000

MXMWD = 2MXMOP = 150

MXGWL = 500MXATW = 50


www.cadfamily.com


----------------------------------------------------------------GRIDSIZE MEDIUM

NDYNB 40,000,000NDYNZ 40,000

ISMAX TRUE

MXPNT = 10000








www.cadfamily.com


705

Four other keywords can be used in the GRID section:

• ACRES xxx

----------------------------------------------------------------GRIDSIZE SMALL

NDYNB 20,000,000NDYNZ 20,000

ISMAX TRUE

MXPNT = 10000







END

--/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/---- End of file----/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/


www.cadfamily.com


where xxx is TRUE or FALSE (default FALSE) determines whether GRID prompts for Acres format output.

• BELL xxx

where xxx is TRUE or FALSE (default FALSE) determines whether a bell is sounded during digitizing and map interpolation. This can be reset from within GRID using option P.7.4 “Tog bell” (see page -536).

• FORMATTED xxx

where xxx is TRUE or FALSE (default TRUE) determines whether formatted or unformatted files are used. This can be reset from within GRID using option P.7.3 “Set IO fmt” (see page -536).

• MESHCOMP xxx

where xxx is TRUE or FALSE (default FALSE) determines whether the internal mesh files should be compressed. Compressed files take up less space but are incompatible with versions of GRID earlier than 94A. This can be reset from within GRID using option P.7.3.6 “Set mesh cmp” (see page -536).


www.cadfamily.com

GRID Reference Manual Use of Configuration FilesHELP section

707

HELP sectionThe HELP section in the configuration file contains the file locations for the GRID MENUS and help files, e.g.:

For 2000A and later releases of GRID, these files can also be identified by a generic file name containing environment variables to identify the top level directory, e.g.:

The program cannot be used unless the MENUS file is defined and can be opened when starting up. There may also be problems if the MENUS file does not correspond to the current version of the program. GRID will write a diagnostic to the log file, indicating which MENUS file was used if this does not match the version expected for the program executable.

Normally, users should not change the HELP section in the installed configuration file. However, it may be useful to refer to this section for trouble-shooting purposes (e.g. when first using a new release, if there are problems with the menus).

------------------------------------------SECTION HELPSUBSECT 97AGRIDMENU /sim/97a/grid/help/MENUSGRID /sim/97a/grid/help------------------------------------------

SECTION HELP------------GRID $ECLARCH/$ECLVER/grid/help/GRIDMENU $ECLARCH/$ECLVER/grid/help/MENUS


www.cadfamily.com

708 Use of Configuration Files GRID Reference ManualGRANITE section

GRANITE section The GRANITE section of the configuration file specifies all the graphical devices which can be used when running GRID. It is divided into subsections, each of which corresponds to a particular device. All Granite drivers specified in the config file must have at least the following keywords:SUBSECT DRIVER integerSELECT TRUE/FALSENAME driver_nameDESCRIPT optional_long_description

The SUBSECT argument defines the driver number that will be used for reference in the driver selection menu, and should fall within the range 1-100. The driver numbers do not have to be consecutive.

The SELECT field determines whether or not a driver is available. To remove a driver, merely set the SELECT field to FALSE: it is not necessary to comment out the whole subsection. The driver concerned will then not appear on the driver selection menu.

The NAME keyword specifies precisely which driver is required, and has specific reserved arguments. In some cases, the name argument must be followed by a further parameter, defining, for example, the plotter or terminal type.

The DESCRIPT keyword gives a description which will appear in the driver selection list.

Various default parameters for a Granite driver can be modified using the configuration file, e.g. fonts, number of colours, maximum size, etc. The example configuration file at the beginning of this Appendix shows two Granite drivers, for an X-terminal and a Postscript plotter.

A detailed list of Granite drivers is provided in the "GRAF Reference Manual".


www.cadfamily.com

GRID Reference Manual History of DevelopmentIntroduction

709

Appendix NHistory of Development

IntroductionChanges for previous GRID releases are shown in this appendix. The changes for the latest releases are at the front of this document. If you require any further information on the history of GRID, please contact SIS customer support.


www.cadfamily.com

710 History of Development GRID Reference ManualNew Developments for 2003A

New Developments for 2003AThe following modifications have been implemented since the 2002A release was announced.

Problems on Sun workstationsSome users experienced problems when using 2002A GRID on Sun workstations under Solaris 8. For example, the program would hang when selecting a map from a menu list. This was due to compiler optimization errors, and was resolved for the 2002A_1 release.

EGRID file exportWhen exporting a grid in EGRID format, there was a problem when using MAP units (i.e. UTMs) or MAPFEET. The data were not converted, but written out relative to the grid origin. This problem has been corrected.

Solution dataGRID now supports import of the DRAINAGE array from restart files written by 2003A ECLIPSE. These data can be loaded and displayed as solution data or imported as property data.


www.cadfamily.com

GRID Reference Manual History of DevelopmentNew Developments for 2002A

711

New Developments for 2002AThe following modifications have been implemented for the 2002A release.

Use of Digitizers on PCsThe digitizer interface on PCs has been modified to resolve problems setting up and using digitizing tablets. It is also possible to re-calibrate the digitizer without exiting the program.

Note that it may be necessary to change hardware switches and port settings, as well as defining the digitizer parameters in the configuration file, when preparing to use a digitizer with GRID. For more information on digitizer set-up, see Appendix E

Workspace DimensionsA warning message is now issued, if the user has attempted to redefine the workspace size, but the GRID dimensions file could not be read. See Appendix M for more information on workspace allocation in GRID.

Contouring Large Mesh MapsSome problems with contouring large mesh maps containing complex fault patterns have been resolved, by increasing the default internal array sizes used within GRID. It may also be necessary to increase the workspace allocation for large models, see Appendix M.

Hard Copy Plots with ZoomSome users reported problems with obtaining hard copy plots of zoomed views. This was caused by the zoom being undone when a list of plotters was displayed on the screen. Zooms are now restored correctly after the hard copy help display.

Improvements in “Grid to maps” OptionOption P.3.9.8 “Grid to maps” has been modified to handle creation of maps for a grid property that contains null values. The default null value for properties is -1E20, whereas the usual null value on mesh maps is 1E6. Two parameters are now defined, GRID_NULL and MAP_NULL, to allow for this. See page 434 for details on the “Grid to maps” option.

When creating a scattered data map, problems may occur if the number of scattered data points exceeds the defined limit on the number of contours. GRID will now produce a single error message and exit the map creation process as soon as the limit is exceeded. If this happens, the user should increase the parameter MXCTF and restart GRID. See Appendix M for information on the grid size parameters.


www.cadfamily.com


New Developments for 2001A

Importing Stratamodel and EarthVision data on PCsGRID can now import binary Stratamodel .glk files and EarthVision files on PC systems as well as UNIX, via “Stratamodel” option P.6.3.3 (page 502) and “Earthvision” option P.6.3.4 (page 509).

Note that support for transfer of 3D geological models via the RESCUE format is available in FloGrid - see the FloGrid User Guide for more details.

Improved colour shadingThe method for setting the Red-Green-Blue representation for different colours has been improved. Previously, small numerical errors could result in RGB values outside the permitted range, and affected colours would not be updated. The modification gives better quality colour shading (e.g. for mesh maps, back contours or grid properties), particularly on PCs.

Zooming and panningThe “Def zoom” menu, D.4 has been modified to ensure that control remains in the menu after a panning option. This allows the user to pan across the screen to an area of interest without having to reselect the zoom menu.

Improved identification of options from run filesThe method for identifying options from run files has been improved. This will provide backward compatibility with older run files that contained zoom and pan commands. This may also affect command flow in other run files, that previously gave errors due to unrecognized commands.

“Date stamps” informationThe “Date stamps” option, P.7.2.7 (page 536) now shows the program version and baseline, along with the date of last modification, date of last build and source directory for the major program components. This information may be useful for support purposes, to confirm exactly which product release is in use.

Loading solutions from unified restart filesWhen reading unified restart files for solution display, via option P.4.2.2, “Lod solution” (page 442), some users reported spurious error messages when a range of timesteps was selected. This problem has been fixed in 2001A.


www.cadfamily.com


713

New Developments for 2000AThe following new facilities and modifications have been implemented for the 2000A release.

Support for EGRID extensible grid file formatGRID now supports the new Extensible Grid file (EGRID) format. The file contains the same information as the standard grid file in corner point or block centered grids, including inactive cell data, local grid refinements and coarsenings. It can also be used for unstructured grids and composite grid models, which are not available in GRID.

The format is typically more efficient, generating a smaller file, that is faster to load into post processing programs. Files in this format have extension .EGRID (binary) or .FEGRID (formatted).

EGRID files may be generated by pre-processors or selected for output from ECLIPSE, by setting the second GRIDFILE option to 1 in the GRID section of the ECLIPSE input data. Examples of use of the GRIDFILE keyword are shown below.

GRID can read EGRID files via the “Input grid” option (P.3.0.6). To write files in this format, use “Out grid” (P.3.9.2) and enter the keyword EGRID.

Extended CPS SAVE formatGRID can now import mesh maps in CPS-1 SAVE format with an extended header.

This format is obtained when a SAVE file is exported from CPS and the user chooses to write the parameter record.

ZMAP contour inputThe prompt from “Inp contours” (P.2.4.7) has been updated to make it clear that ZMAP files can be read. GRID will now skip past standard header lines at the start of a ZMAP contour file.

Importing Stratamodel dataSome .glk files exported from Stratamodel contain blank attribute names. To allow the data to be loaded into GRID, dummy attribute names will be substituted. It is the user’s responsibility to map these dummy names to the correct properties.

Exporting XYZ mesh dataAn error writing out X and Y values to a formatted XYZ mesh file was corrected for the 99A_2 release of GRID.

-- Extensible EGRID file onlyGRIDFILE0 1 /

-- Both EGRID and Extended GRID fileGRIDFILE2 1 /


www.cadfamily.com


“Tst point” optionA problem with the “Tst point” option for sampling maps was fixed in the 99A_2 release. This occurred when using variable search radius on SGI systems, resulting in a program crash.

Calculating saturation mapsThe “Cal wtr sat” option now allows water saturations to be set to NULL in pinchout regions.

Workspace dimensions set-upThe workspace debug output from “Wkspace dbg” (P.7.2.6) now indicates the name of the file used to define the workspace dimensions (e.g. /ecl/macros/gridsize.dat) and the size selected (e.g. MEDIUM).

Identification of menu and help filesThe menu file and help directory to be used when running GRID are identified in the HELP section of the configuration file. These files can now be identified by a generic file name containing environment variables to identify the top level directory, e.g.:

Licensing changesFor the 2000A release, GRID can run using a GRID licence or a FloGrid licence. Ask your local support contact, if you have any questions on product licensing.

Schlumberger logoThe default logo has been updated to the latest Schlumberger format.

SECTION HELP------------GRID $ECLARCH/$ECLVER/grid/help/GRIDMENU $ECLARCH/$ECLVER/grid/help/MENUS


www.cadfamily.com


715


Exporting & copying map dataTwo new options have been added to the “Map utilities” menu.

• The “Export maps” option, P.6.4, allows the user to export data from multiple maps and strata. Either mesh maps or fault data from either mesh or contour maps can be exported. The user can select which maps and strata to output and the format of the output files.

• The “Copy map” option, P.6.5, allows the user to copy all the data stored in an existing map, e.g. fault data, contour data, caption data will all be copied. The user can either copy a single stratum or all strata in the map.

Filling null values in mesh mapsNull values in mesh maps can be filled by interpolating the non-null mesh values. Two improvements have been made to simplify and speed up this process.

• The @FILL function can now be used to resample the mesh at null nodes, see Appendix G.

• Previous releases of GRID do not interpolate mesh values at nodes where all the surrounding mesh values are null. Therefore null areas have to be filled iteratively, from the edges inwards. An extra feature has been added to Option P.2.5.9.4.7 “Tog nul bnd” to allow interpolation at all nodes inside a null area.

EarthVision data importGRID recognizes the new EarthVision fault type MAJORDOWN. The user can choose whether to set MAJORDOWN segments to be minor or major segments, see P.6.3.4 “Earthvision”.

Grid to map conversionA new option has been added to convert grid data to map data, “Grid to maps”, P.3.9.8. Mesh maps, contour maps or scattered data maps can be made from geometry (e.g. tops or thicknesses), property or region data. This option, when used with the new multiple map export option, provides an efficient means of exporting grid data for use in other applications.

Node splitting & joining• The user can now select an area of the grid when using the automatic node splitting routine

P.3.9.4 “Spt grid”, which splits grid nodes along map faults.

• Split nodes from multiple faults can now be joined in one step. A new option allows the user to select an area of the grid and join all nodes in it, option P.3.9.5 “Jn grid”.

Defining region data in LGRsThe @FILL_L function can now be used to copy region data from a parent grid to an LGR, see Appendix G.


www.cadfamily.com


Adding rows & columnsThe “Add rows” and “Add columns” options, P.3.4.2 and P.3.4.3, can now be used to extend the grid by adding rows or columns to the edges of the grid. They can still be used to sub-divide columns and rows.

Moving rows & columnsThe “Mov row” and “Mov column” options, P.3.4.6 and P.3.4.7, can now be used with sloping coordinate lines in the same way as for vertical lines, following the correction of a problem with the algorithm.

Rotating the gridThe grid rotation option P.3.9.3.4 “Rot grid” has been modified, so that the grid can now be rotated by specifying an angle, as well as by moving a node.

Acres format outputGRID can now export grid data and well trajectory data in a format suitable for ARCO’s Acres simulator. See options P.3.9.2 “Out grid” and P.6.6.3 “Out grd conn”.

Tabs as delimitersTabs can now be used as delimiters in most input files, including data files, control files and parameter files. Options that have been modified include:

ECLMAP optionsEarlier versions of the GRID program, help files and documentation distinguished between GRID options and ECLMap options. This distinction has been removed.

P.2.2.6 “Inp wells”P.2.3.6 “Inp faults”P.2.4.7 “Inp contours” P.2.5.2 “Inp mesh”P.2.6.6 “Inp features”P.2.8.6 “Inp zones”P.3.0.6 “Input grid” - VIP dataP.3.9.6 “Cal ave prps”P.3.9.7 “Cal trans”P.3.9.8 “Grid to maps”P.6.3.2 “Mesh files”P.6.3.3 “Stratamodel” - control filesP.6.3.4 “Earthvision” - control filesP.6.3.5.2 “Inp DXF”P.6.6.2 “Inp wel trj”


www.cadfamily.com


717

Scrolling interactive help filesWhen the “Help” option is selected, GRID displays the help file corresponding to the option selected. The user can now scroll backwards and forwards through the help file and select the number of lines to scroll.

Paging through the electronic version of the manualThe electronic version of this manual is supplied either in FrameViewer format or as a PDF file. To make it easier to browse the FrameViewer version of the manual, two buttons have been added at the beginning of each file:

These buttons can be used to page backwards and forwards through the FrameViewer book.

Demonstration run fileA run file DEMO99A.RF has been included in the Grainne example directory. This demonstrates many of the features listed above.

New Developments for 98A_1The following new facilities and modifications were implemented for the 98A_1 release.

Importing LGRsWhen an LGR is imported, “Inp LGR” P.3.8.2.6, GRID checks to see if it fits properly into the host grid. If it doesn’t the user is given the option of adjusting the host grid to allow the LGR to fit. GRID then has to decide which LGR cells belong in each host cell. Two improvements have been made to the way this is done:

• The user can specify how a Cartesian LGR fits by using NXFIN/NYFIN/NZFIN keywords in the data file. For radial refinements the NZFIN keyword can be used.

• If the NZFIN keyword is not used, GRID will determine how the LGR layers fit into the host grid by matching the inside corner nodes along the first coordinate line of the LGR, i.e. the back left coordinate line. (97A GRID uses the second coordinate line, 98A uses the second coordinate line in the second row.)

Sloping coordinate linesGRID uses an iterative method to sample depths on grids with sloping coordinate lines. In some circumstances this does not converge, e.g. if the map surface is steeper than the coordinate lines, or if the map surface is very badly behaved. Two new techniques have been added for dealing with these problems:


www.cadfamily.com


• An ’over-relaxation’ parameter R can now be used within the iterations. Convergence of the iterations can sometimes be speeded up by using a relaxation parameter 1 <= R < 2, although this may cause the sampling to diverge. If the iterative procedure is not convergent, then a smaller value of R, 0 < R <= 1 may help. The default value is R = 1, which gives the same results as earlier versions of GRID.

The relaxation parameter can be set using option P.7.5 "Tog slp crds".

• The intersection of sloping coordinate lines with a map surface can be found using the bisection method. This can cope with awkward maps but does not deal with split nodes. Therefore the user needs to resample the map once after finding the intersections.

This option can be used by entering the letter “I” when specifying the depth in options P.3.2.2 "Def dep lay", P.3.3.5 "Def dep are" and P.3.5.4 "Def nde dep".


www.cadfamily.com


719


PC releases (Windows 95 and NT)The PC implementation of GRID is now based on DEC Visual Fortran. The screen display has been improved and user-defined memory allocation is now available.

Note The 98A PC versions of GRID, GRAF and ECLIPSE can now read binary (unformatted) UNIX files, but can not read binary files created by earlier PC releases. See the section on File Handling in Chapter 3 for details on updating existing PC binary files so they can be read by 98A software.Formatted files and UNIX systems are unaffected by the change.If you have any questions about the new binary format, contact SIS customer support.

Map data input and outputThe following changes affect input and output operations for map data:

• For contour data, Z-Map formats can be selected by the keyword ZMAP instead of the old ZYCOR keyword. For input, the standard ZMAP format is in two columns, in the form:

An alternative structure is available, corresponding to output from the Contouring subtask of Z-Map Plus, in the form:

For ZMAP input, GRID will check the first line, and allow the user to select the alternative structure if appropriate. For output, only the standard format is available.

• The obsolete CPS-PC format for mesh map data is no longer supported.

• The DEGREES layout for X,Y values in decimal degrees is now available for zone data as well as features, faults, contours and wells. For all these data types, DEGREES input is now free-format by default.

EarthVision data importUpdates for compatibility with the latest version of the EarthVision export file, include the option to read fault trace names and types. Fault traces with the same name can be concatenated to construct sloping fault polygons on the imported maps.

NULL Z-valueX-value Y-valueX-value Y-value.... ....

NULL Z-valueZ-value Continuation-flagX-value Y-valueX-value Y-value.... ....


www.cadfamily.com


Masking fault regions on mapsThe "Msk mesh" option has been extended to allow the user to mask all sloping fault regions on a mesh map. This will be useful in cases where it is necessary to null out data near faults and reinterpolate (e.g. when reconciling mesh map data and fault traces after importing third party data).

LGR editing and displayEnhancements for LGR editing and display include:

• The options "Sho active", "Sho property", "Sho region" and "Sho FIP" will show both global and local values when applicable, if selected while a grid containing LGRs is displayed.

• Some problems with cross-section displays containing radialLGRs have been corrected.

Nested LGRsNested LGRs can now be read or created and exported, for compatibility with the nested LGR options in ECLIPSE 300.

Note that changes to the internal data file structure for grids containing LGRs mean that .FNODE and .NODE files created by GRID 98A cannot be used with older versions of GRID.


www.cadfamily.com

GRID Reference Manual History of DevelopmentNew developments for 97A

721

New developments for 97AThe following new facilities and modifications have been implemented since the 96A release in March 1996.

User-defined memory allocationThe maximum limits on workspace that can be handled in GRID are now defined in an external configuration file, allowing the user to redimension program workspace without the need to recompile and relink.

Hot keys for fast option selectionThe use of ‘hot keys’ to enable fast selection of options has been extended to include the following keys:

All the hot key options can now be selected from the Display menus as well as from the Primary menus.

ProjectionsChanges to options for spheroid definition include:

• WGS 84 can be selected as a standard spheroid, instead of as a user-defined spheroid.

• The Australian National spheroid is now accepted as a valid spheroid for UTM coordinates.

• Non-standard spheroids can now be used with UTM coordinates, although a warning will be issued. This will improve compatibility with other software packages, where the selection of spheroids for UTM is not checked.

Use of scratch files for map dataGRID will now automatically clear scratch files for maps that have been edited and saved, if this is necessary to avoid problems with file unit allocation. (If the user chooses to edit a large number of maps without saving changes, it will still be necessary to use the “Clr maps” option to free the files.)

Map editing & samplingModifications to map editing and sampling include:

• Maps containing more than 100 strata can be handled if required (subject to the maximum limit being set in the configuration file).

• Faults loaded from a file with the SPECIAL fault format can now be thinned and clipped as they are read. When faults are clipped on input, closed polygons will be preserved where possible, by concatenating clipped segments.

• Options for entering a polygon mask for map operations now include selection of a zone boundary from the current map.

“C” - “Chg settings” “L” - “Edt LGR”“M” - “Map view opts”


www.cadfamily.com

722 History of Development GRID Reference ManualNew developments for 97A

• Zero or near-zero values are no longer accepted when defining nulls for sampling maps. This will help to prevent interpolation errors caused by incorrect use of null values.

Map data inputUpdates to import options for third-party data include:

• The defaults for IRAP file input have been modified, so that the default IRAP version is now NEW and the default null value is 0.1E31.

• The Stratamodel input for binary GLK files now checks for use of the redundant HEIGHT attribute and warns the user if necessary. (GRID can still read older GLK files, where the HEIGHT attribute is valid.)

Overlay map displaysWhen a simulation grid is loaded, overlay maps can be set up so that the map stratum is varied with the grid layer, by selecting the wild card * instead of a stratum number. For example, if the overlay map is selected as TOPS(*), the map TOPS(1) will be shown with simulation grid layer 1, but will be replaced with TOPS(2) when layer 2 is edited.

The same convention can be used for selecting the current map for grid editing. If the wild card * is entered instead of a stratum number, then the default map layer will be set according to the current XY-plane. This option will be deactivated if a map is selected for sampling, with a different stratum number, or if the map editing menu is entered.

Editing grids with sloping coordinate linesWhen a grid is selected for editing, it is now checked for sloping coordinate lines. If the sloping coordinate lines options are not switched on, the user will be prompted at this stage, before starting grid editing.

Use of these options is not compulsory, but is recommended when sampling depths or thicknesses, or editing the grid by moving nodes. (Note that the “Chg settings” menu can now be entered via the hot key “C” at any point in the menu hierarchy, if the user wishes to change the option settings.)

Additional checks have also been added to the “Merge grids” option, to ensure that the bottom grid axes and units match those for the top grid, and convert the data if necessary. After creating a grid via “Merge grids”, prompts for sloping coordinate line options will be generated as above.

Grid block propertiesChanges to grid block property editing and display include:

• When reading active cell numbers, property values or region data from a formatted data file (e.g. GRDECL or FILLED file), the array size is checked and a warning issued if there are too many or insufficient data values. If the number of property or region values equals the number of active cells and the user chooses to load the data, they will be stored in active cell positions.

• The default values offered to replace nulls when sampling a map have been modified. Instead of defaulting to the null value on the map, the default for ACTNUM or region values is set to zero, and null property values are set to -1.0E20. The user can override these defaults by entering a value for the null points when prompted.


www.cadfamily.com


723

Note that this change may give different results with run files used for sampling in 96A or older versions of GRID, in cases where the user set null defaults by defining the map null.

• The colour keys for property fill and region fill have been improved. The keys are adjusted automatically to fit on the page, even for large numbers of colour intervals. If necessary, intermediate values may be omitted to avoid overwrites.

LGR editingThe “Edt LGR” option can now be selected via hot key “L” from any menu. The user now has the option of selecting an LGR from a list of sub-grid names, as an alternative to selecting on the screen.

When “Sho values” is selected for a global grid containing LGRs, both global and local values will be shown when applicable:

• “Sho i,j,k” shows cell number and grid (for both grids)

• “Sho x,y,z” picks the nearest node in any grid

• “Sho node thk” shows the node thickness for the nearest node, displaying values for both the global grid and LGR if the node is common to both.

LGRs can now be constructed in GRID by reading CARFIN or RADFIN keywords from an external file, together with suitable keywords from NXFIN, NYFIN, NZFIN and HXFIN, HYFIN, HZFIN (see the “Inp LGR” option, P.3.8.2.6.)

When reading active cell numbers, property values or region data for grids containing LGRs, the user is now prompted to load data for all the grids or the current grid only. If the current grid is an LGR, the user can choose to load the first array found or identify the required LGR in the file.

Property averaging & transmissibility calculationsThe user can now specify that grid layers correspond to map strata in “Cal ave prps” or “Cal trans”, without the need to enter all layer numbers. In the control file, this is specified by:

The transmissibility calculations now include pinchout options for generating NNCs across inactive layers in the vertical direction (or across inactive rows or columns in the horizontal direction). For vertical pinchouts, the user can set parameters defining the maximum gap between active cells and the effects of minimum pore volume cut-off. A minimum value for NNC transmissibilities can also be set, to reject NNCs with very small values.

Simulation grid outputWhen “Out grid” is used to write out grid values within box limits, and the SPECGRID keyword is written for the global grid, the user can now choose to adjust the dimensions to the box size.



www.cadfamily.com


Well trajectoriesSome further improvements have been made to the well trajectory calculations, to resolve problems searching for connections in horizontal or deviated wells that penetrate through the bottoms of grid layers. A problem with prematurely abandoning the search for vertical well trajectories in irregular grids with sloping faults, pinchouts and gaps between layers has also been corrected.

An option to delete all or selected well trajectories from GRID has been added (option P.6.4.4, “Del well trj”.)

The well trajectory display facility now allows wells to be drawn on grid cross-sections as well as XY views. For the current cross-section, the view will show all wells with an areal range which intersects the XZ or YZ plane. (Note that a visible well does not necessarily penetrate all grid blocks shown on the current display.)

Volumetrics & water saturation calculationsThe ECLmap options for volumetrics and water saturation calculations have been improved:

• The user now has the option to write the volumetrics report to a file only, instead of displaying results on the screen. The prompt to choose whether to calculate volumes over the full map now defaults to ‘Yes’.

• The interpolation methods for calculating water saturation maps from tables have been improved, to give more accurate results and faster calculation times.

• The user can now choose to recalculate water saturations within a selected polygon, rather than re-gridding the entire map. This allows use of different look-up tables and contact depths in different zones.


www.cadfamily.com


725

New developments for 96AThe following new facilities and modifications have been implemented since the 95B release in April 1995. Note that some of these updates are already available to users with recent 95B installations. Changes available only in GRID 96A are marked with an asterisk.

Special key for "Sho values" menu *The "Sho values" menu can now be selected by typing S when prompted to select a primary menu option. This allows the user to check grid block numbers and xyz values from any other grid editing menu, or while editing a map.

The full set of 'hidden' menu keys, including those introduced in the 95B release, is now:

• "I" - "Edt YZ-plane",

• "J" - "Edt XZ-plane",

• "K" - "Edt XY plane",

• "S" - "Sho values",

• "U" - "Unzoom",

• "Z" - "Zoom",

• "+" - increment current plane number,

• "-" - decrement current plane number.

DXF file input *DXF (Drawing Interchange Format) files are used for transferring data between Autodesk's AutoCAD system and other CAD programs.

Facilities are now provided in GRID to allow the user to read digitized map data (contours, fault traces and features), well positions and mesh XYZ data from an ASCII DXF file and to write out map data in DXF format. See the documentation for option P.6.3.5, "DXF files", for further information.

Note Redundant options for handling Mimic files and Ordnance Survey data files have now been removed from menu P.6.3.

Contour and fault data in degreesContour and fault data can now be read or written in decimal degrees, using layout type DEG or DEGREES. The data will be read in 3 columns, consisting of Z-value, latitude and longitude.

Mesh map input options• Input from IRAP formatted and single grid files has been modified to allow for different

formats introduced with IRAP version 6.1. The user is prompted to indicate whether the OLD or NEW version is required. (Note: Although the NEW format can include an angle of rotation in the file header, GRID will not use this for mesh map creation, so a user-defined angle should be entered if appropriate.)


www.cadfamily.com


• CPS-3 file input has been revised to allow for a number of changes in recent CPS releases.

• Input from ZMAP mesh files can now handle additional lines beginning with @, ! or + in the file header.

Map gradient display *New map gradient display options are available for mesh maps. Menu D.7.8.6, "Map gradient" provides facilities to show high and low points on maps, and draw gradient arrows or streamlines computed from the partial derivatives of the underlying data. Lines can be colour-coded according to the mesh data values, using the colouring scheme for 3D mesh lines.

Mesh map interpolationA new interpolation mode is available for mesh map data. This looks up data values directly from the mesh, with no further processing, and faults are not considered. The method is very fast and may be suitable for fine geostatistical data or for data which are considered as integers, such as facies indicators or region identifiers. Select this method by choosing interpolation mode 0 from option P.2.5.9.4.6, "Def int mod".

Well trajectory display *Well trajectory data used for finding well connections can now be displayed on XY views using display menu D.7.8.7, "Sho wel trj". Well trajectory lines can be shown for deviated or horizontal wells, colour coded by TVD and annotated with TVD and measured depth values. For vertical wells, the well position will be marked by a symbol and well label.

Grid block thickness correction factorThe thickness correction factor which can be applied to layer thickness values for a simulation grid has been revised. Much better results can now be obtained by using this option in cases where the grid has sloping coordinate lines and the layer surfaces are dipping. (Use of the thickness correction factor can be enabled via menu option P.7.5, "Tog slp crds".)

Grid block property calculations *• Special variable names for use in grid block property calculations now include @DX, @DY,

@DZ, @DR, @DTHETA, @TOPS and @DEPTH, in addition to @PORV. If these variables are used in an arithmetic expression, GRID will compute the appropriate values in the same way as they are calculated for output in "Out grid".

• The existing @PORV variable always returns pore volumes in cubic metres. Two additional pore volume variables are now available:

• @PORV_RB, which computes volumes in reservoir barrels, and

• @PORV_FT, which returns pore volumes in cubic feet.

Input of grid properties and regions• Region data can now be read from an ECLIPSE INIT file, using option P.3.8.4.6, "Inp

region".

• The "Inp property" and "Inp region" options can now read LGR data from an INIT or restart file in one operation for the entire grid. Previously, each LGR had to be selected via the display option "Edt LGR" before loading data.


www.cadfamily.com


727

Reordering grid blocks *Simulation grids imported from third-party packages sometimes do not conform to the ECLIPSE convention of numbering blocks from an origin in the top left corner of the screen. To allow grids to be converted to the ECLIPSE standard, a new option has been provided for renumbering the grid blocks.

Menu P.3.9 has been reorganized and the following grid geometry operations are now available via P.3.9.3, "Opr geometry":

• "Mov origin" - Move origin

• "Rel grid" - Relocate grid

• "Rot grid" - Rotate grid

• "Scl grid" - Scale grid

• "Order grid" - Order grid blocks

Simulation grid data output• An option to output data compatible with Chevron's CHEARS simulator is now available.

• The LGR keywords NXFIN/NYFIN/NZFIN and HXFIN/HYFIN/HZFIN can be written from "Out grid".

• NNC calculations across pinchouts incorrectly multiplied Z-transmissibility values by NTG, in previous versions of GRID. This error has now been corrected.

• A binary output option is now available for ECLIPSE GRID section data. If the keyword BINARY is entered from "Out grid", large arrays such as COORD and ZCORN will be written to an unformatted file with extension .GRDBIN. An associated .GRDECL file will also be produced, containing comments on the contents of the binary file and an IMPORT command to input the binary file to ECLIPSE.

Scratch file handlingOn certain Unix systems, it is sometimes necessary to redirect scratch files to a specified directory, e.g. in cases where the scratch space needed for the current GRID session exceeds the amount available on the default temporary disk. A configuration file option is now available for this purpose (- set the directory name using keyword TMPDIR in the SYSTEM section). Alternatively, the option P.7.3.7, "Set tmpdir", can be used to redirect scratch file output during a GRID session.

Cyrillic text option *When the Cyrillic font is selected, GRID can map the characters found in names for wells, faults, features and zones, captions and legends to the corresponding Cyrillic characters obtained from a Russian keyboard. To enable this 'translation' facility, include the command CYRILLIC TRUE in the SYSTEM section of the configuration file.


www.cadfamily.com



www.cadfamily.com

GRID Reference Manual Index of Options 729

Appendix OIndex of Options

The Primary menu .................................................................... ..............................36Edit model ................................................................................... P.1 ........................37Delete model ............................................................................... P.1.2 .....................38Delete stratum............................................................................. P.1.2.2 ..................39Delete map ................................................................................. P.1.2.3 ..................40Delete grid .................................................................................. P.1.2.4 ..................41Delete survey ............................................................................. P.1.2.5 ..................42Change model ............................................................................ P.1.3 .....................43Change map name ..................................................................... P.1.3.2 ..................44Change map stratum ................................................................ P.1.3.3 ..................45Change map units ...................................................................... P.1.3.4 ..................46Change model area .................................................................... P.1.3.5 ..................47Change number of model strata .............................................. P.1.3.6 ..................48Change mesh data...................................................................... P.1.3.7 ..................49List history file ............................................................................ P.1.4 .....................50Output a model report .............................................................. P.1.5 .....................51Introduction ............................................................................... ..............................53Edit map ...................................................................................... P.2 ........................55Edit wells ..................................................................................... P.2.2 .....................57Copy wells................................................................................... P.2.2.2 ..................58Add well ...................................................................................... P.2.2.3 ..................59Delete well................................................................................... P.2.2.4 ..................60Change wells............................................................................... P.2.2.5 ..................61Change well name...................................................................... P.2.2.5.2 ...............62Move well .................................................................................... P.2.2.5.3 ...............63Input wells................................................................................... P.2.2.6 ..................64Output wells ............................................................................... P.2.2.7 ..................66Define Granite settings .............................................................. P.2.2.8 ..................68Change Granite settings ............................................................ P.2.2.9 ..................69Edit faults .................................................................................... P.2.3 .....................70

Edt modelDel modelDel stratumDel mapDel gridDel surveyChg modelChg map nmesChg map strChg map unitChg mod areaChg mod strChg mesh datLst historyOut mod rpt

Edt mapEdt wellsCpy wellsAdd wellDel wellChg wellsChg wel namMov wellInp wellsOut wellsDef graniteChg graniteEdt faults


www.cadfamily.com

730 Index of Options GRID Reference Manual

Copy faults ..................................................................................P.2.3.2 ................. 71Add fault......................................................................................P.2.3.3 ................. 72Delete faults.................................................................................P.2.3.4 ................. 74Change fault ................................................................................P.2.3.5 ................. 75Change fault name .....................................................................P.2.3.5.2 .............. 76Change fault type .......................................................................P.2.3.5.3 .............. 77Change fault colour fill mask ...................................................P.2.3.5.4 .............. 78Change fault segment ................................................................P.2.3.5.5 .............. 79Change fault trace ......................................................................P.2.3.5.6 .............. 80Operate on fault traces...............................................................P.2.3.5.7 .............. 81Clip fault trace.............................................................................P.2.3.5.7.2 ........... 82Split fault trace ............................................................................P.2.3.5.7.3 ........... 83Close fault polygons ..................................................................P.2.3.5.7.4 ........... 84Thin faults....................................................................................P.2.3.5.7.5 ........... 85Repopulate faults........................................................................P.2.3.5.7.6 ........... 86Smooth faults ..............................................................................P.2.3.5.7.7 ........... 87Join faults .....................................................................................P.2.3.5.7.8 ........... 88Extend faults ...............................................................................P.2.3.5.7.9 ........... 89Input faults ..................................................................................P.2.3.6 ................. 90Output faults ...............................................................................P.2.3.7 ................. 95Define Granite settings ..............................................................P.2.3.8 ................. 99Edit contours ...............................................................................P.2.4 .................. 100Copy contours.............................................................................P.2.4.2 ............... 101Add contours ..............................................................................P.2.4.3 ............... 102Delete contours ...........................................................................P.2.4.4 ............... 104Change contours.........................................................................P.2.4.5 ............... 105Show contour value ...................................................................P.2.4.5.2 ............ 106Change contour value................................................................P.2.4.5.3 ............ 107Operate on contour values........................................................P.2.4.5.4 ............ 108Change contour line...................................................................P.2.4.5.5 ............ 109Operate on contour lines ..........................................................P.2.4.5.6 ............ 110Clip contours...............................................................................P.2.4.5.6.2 ......... 111Split contours ..............................................................................P.2.4.5.6.3 ......... 112Delete fault region......................................................................P.2.4.5.6.4 ......... 113Thin contours ..............................................................................P.2.4.5.6.5 ......... 114Repopulate contours .................................................................P.2.4.5.6.6 ......... 115Smooth contours ........................................................................P.2.4.5.6.7 ......... 116Join contours ...............................................................................P.2.4.5.6.8 ......... 117Extend contours ..........................................................................P.2.4.5.6.9 ......... 118Change contour parameters......................................................P.2.4.6 ............... 119Show map area ...........................................................................P.2.4.6.2 ............ 120Change map area........................................................................P.2.4.6.3 ............ 121Change contour labels ...............................................................P.2.4.6.4 ............ 122Change contour interval............................................................P.2.4.6.5 ............ 123Define Granite settings ..............................................................P.2.4.6.6 ............ 124Input contours.............................................................................P.2.4.7 ............... 125Output contours .........................................................................P.2.4.8 ............... 129Sample contours .........................................................................P.2.4.9 ............... 132Test point .....................................................................................P.2.4.9.2 ............ 133Test map.......................................................................................P.2.4.9.3 ............ 134Test grid .......................................................................................P.2.4.9.4 ............ 135Test node......................................................................................P.2.4.9.4.3 ......... 136Test block.....................................................................................P.2.4.9.4.4 ......... 137Test all nodes...............................................................................P.2.4.9.4.5 ......... 138

Cpy faultsAdd faultDel faultChg faultChg flt namChg fault typChg flt mskChg flt segChg flt trcOpr flt trcClp flt trcSpl flt trcClose fltsThin fltsRepop fltsSmooth fltsJoin fltsExtend fltsInp faultsOut faultsDef graniteEdt contoursCpy contoursAdd contoursDel contoursChg contoursSho cnt valCng cnt valOpr cnt valsChg cnt lneOpr cnt lnesClp contoursSpl contoursDel flt regThin cntsRepop cntsSmooth cntsJoin cntsExtend cntsChg cnt parsSho map areaChg map areaChg cnt lblsChg cnt intDef graniteInp contoursOut contoursSmp contoursTst pointTst mapTst gridTst nodeTst blockTst all ndes


www.cadfamily.com


Tst all blksEdt smp valsSho blk valDef blk valSho crn valDef crn valOut blk valOut crn valOut nde valsSho smp cntsPut grd crnsPut grd prpsSho bck cntsOut bck cntsChg interpDef nullDef trn valsDef dmp facDef sch radDef int modWgt well ptsTog int fltsTog min slpChg bck cntsChg graniteChg fillNum stylesChg indexChg limitsSet shadingRes coloursVar transfrmEdt meshInp meshCal meshOpr meshMsk meshChg msh parsChg labelsChg cnt intSho min maxSho nullsDef graniteChg fillChg keyDef msh valOut meshSmp meshChg interpTog nul bndSho sch crlEdt featuresCpy featuresAdd feature

Test all blocks.............................................................................. P.2.4.9.4.6 ..........139Edit sample values ..................................................................... P.2.4.9.4.7 ..........140Show block value ....................................................................... P.2.4.9.4.7.2 .......141Define block value...................................................................... P.2.4.9.4.7.3 .......142Show corner value...................................................................... P.2.4.9.4.7.4 .......143Define corner value.................................................................... P.2.4.9.4.7.5 .......144Output block values................................................................... P.2.4.9.4.7.6 .......145Output corner values................................................................. P.2.4.9.4.7.7 .......146Output node values ................................................................... P.2.4.9.4.7.8 .......147Show sampled contours ............................................................ P.2.4.9.4.7.9 .......148Save corner values on grid........................................................ P.2.4.9.4.8 ..........149Save block values as grid property.......................................... vP.2.4.9.4.9 .......150Show back contours ................................................................... P.2.4.9.5 .............151Output back contours ................................................................ P.2.4.9.6 .............153Change interpolation ................................................................. P.2.4.9.7 .............154Define null................................................................................... P.2.4.9.7.2 ..........155Define truncation values ........................................................... P.2.4.9.7.3 ..........156Define damping factor............................................................... P.2.4.9.7.4 ..........157Define search radius .................................................................. P.2.4.9.7.5 ..........158Define interpolation mode........................................................ P.2.4.9.7.6 ..........161Set weighting for well control points ...................................... P.2.4.9.7.7 ..........163Toggle faults in interpolation ................................................... P.2.4.9.7.8 ..........164Toggle minimum slope ............................................................. P.2.4.9.7.9 ..........165Change back contour display................................................... P.2.4.9.8 .............166Change Granite settings ............................................................ P.2.4.9.8.2 ..........167Change colour fill ....................................................................... P.2.4.9.8.3 ..........168Number of styles ........................................................................ P.2.4.9.8.3.2 .......169Change index .............................................................................. P.2.4.9.8.3.3 .......170Change limits .............................................................................. P.2.4.9.8.3.4 .......171Set shading .................................................................................. P.2.4.9.8.3.5 .......172Reset colours ............................................................................... P.2.4.9.8.3.6 .......174Select variable transformation.................................................. P.2.4.9.9 .............175Edit mesh..................................................................................... P.2.5 ...................176Input mesh .................................................................................. P.2.5.2 ................177Calculate mesh............................................................................ P.2.5.3 ................190Operate on a mesh ..................................................................... P.2.5.4 ................191Mask a mesh ............................................................................... P.2.5.5 ................193Change mesh parameters.......................................................... P.2.5.6 ................194Change contour labels ............................................................... P.2.5.6.4 .............195Change contour interval............................................................ P.2.5.6.5 .............196Show minimum & maximum................................................... P.2.5.6.6 .............197Show nulls ................................................................................... P.2.5.6.7 .............198Define Granite settings .............................................................. P.2.5.6.8 .............199Change mesh map colour fill ................................................... P.2.5.6.9 .............200Change key.................................................................................. P.2.5.6.9.7 ..........201Define mesh value...................................................................... P.2.5.7 ................202Output mesh ............................................................................... P.2.5.8 ................203Sample mesh ............................................................................... P.2.5.9 ................206Change mesh interpolation....................................................... P.2.5.9.4 .............207Toggle null mask boundary...................................................... P.2.5.9.4.7 ..........208Show search circle ..................................................................... P.2.5.9.4.9 ..........209Edit features ................................................................................ P.2.6 ...................210Copy features.............................................................................. P.2.6.2 ................211Add a feature .............................................................................. P.2.6.3 ................212


www.cadfamily.com


Delete features ............................................................................P.2.6.4 ............... 213Change features ..........................................................................P.2.6.5 ............... 214Change feature name.................................................................P.2.6.5.2 ............ 215Change a feature line ................................................................P.2.6.5.3 ............ 216Operate on feature lines ............................................................P.2.6.5.4 ............ 217Clip feature line ..........................................................................P.2.6.5.4.2 ......... 218Split feature line..........................................................................P.2.6.5.4.3 ......... 219Thin features ...............................................................................P.2.6.5.4.4 ......... 220Repopulate features ...................................................................P.2.6.5.4.5 ......... 221Smooth features ..........................................................................P.2.6.5.4.6 ......... 222Join features ................................................................................P.2.6.5.4.7 ......... 223Extend features ...........................................................................P.2.6.5.4.8 ......... 224Input features ..............................................................................P.2.6.6 ............... 225Output features...........................................................................P.2.6.7 ............... 229Define Granite settings ..............................................................P.2.6.8 ............... 233Change Granite settings ............................................................P.2.6.9 ............... 234Edit captions................................................................................P.2.7 .................. 235Copy captions .............................................................................P.2.7.2 ............... 236Add a caption..............................................................................P.2.7.3 ............... 237Delete a caption ..........................................................................P.2.7.4 ............... 238Change caption data ..................................................................P.2.7.5 ............... 239Move a caption............................................................................P.2.7.5.2 ............ 240Change a caption ........................................................................P.2.7.5.3 ............ 241Define Granite settings ..............................................................P.2.7.5.4 ............ 242Change Granite settings ............................................................P.2.7.5.5 ............ 243Input captions .............................................................................P.2.7.6 ............... 244Output captions ..........................................................................P.2.7.7 ............... 246Edit zones ....................................................................................P.2.8 .................. 247Copy zones ..................................................................................P.2.8.2 ............... 248Add a zone ..................................................................................P.2.8.3 ............... 249Delete zones ................................................................................P.2.8.4 ............... 250Change a zone.............................................................................P.2.8.5 ............... 251Input zones ..................................................................................P.2.8.6 ............... 252Output zones...............................................................................P.2.8.7 ............... 255Define Granite settings ..............................................................P.2.8.8 ............... 258Change Granite settings ............................................................P.2.8.9 ............... 259Edit legend...................................................................................P.2.9 .................. 260Copy legend ................................................................................P.2.9.2 ............... 261Add a legend item......................................................................P.2.9.3 ............... 262Delete a legend item...................................................................P.2.9.4 ............... 263Move an item ..............................................................................P.2.9.5 ............... 264Change an item...........................................................................P.2.9.6 ............... 265Change legend ............................................................................P.2.9.7 ............... 266Define Granite settings ..............................................................P.2.9.8 ............... 267Introduction ................................................................................ ........................... 269Edit grid .......................................................................................P.3 ..................... 273Vector grid...................................................................................P.3.0.2 ............... 275N x M grid ...................................................................................P.3.0.3 ............... 276Irregular grid...............................................................................P.3.0.4 ............... 277Add control column...................................................................P.3.0.4.1 ............ 279Add control row .........................................................................P.3.0.4.2 ............ 280Delete control column................................................................P.3.0.4.3 ............ 281Delete control row......................................................................P.3.0.4.4 ............ 282Change control column .............................................................P.3.0.4.5 ............ 283

Del featuresChg featureChg fet nameChg fet lneOpr fet lnesClp fet lneSpl fet lneThin fetsRepop fetsSmooth fetsJoin fetsExtend fetsInp featuresOut featuresDef graniteChg graniteEdt captionsCpy captionsAdd captionDel captionChg cap dataMov captionChg captionDef graniteChg graniteInp captionsOut captionsEdt zonesCpy zonesAdd zoneDel zonesChg zoneInp zonesOut zonesDef graniteChg graniteEdt legendCpy legendAdd itemDel itemMove itemChg itemChg legendDef granite

Edt gridVector gridN x M gridIrregularAdd ctl colAdd ctl rowDel ctl colDel ctl rowChg ctl col


www.cadfamily.com


Chg ctl rowMake gridOut ctl lnesInp ctl lnesMark axesInput gridCopy gridMerge gridsX-sect gridEdt layerDef dep layDef thk layAdd layerDel layerDiv layerSpl layerJn layerEdt areaEqu areaEqu columnsEqu rowsDef dep areDef thk areSpl areaJn areaVrt areaEdt linesAdd rowsAdd columnsDel rowDel columnMov rowMov columnStr lineEqu lineEdt nodesMov nodeMov nde-ndeDef nde depMrk nde depDef nde thkSpl nodesJn nodesMov crd lneEdt flt lnesMov row-fltMov col-fltMov nde-fltMov row-slpMov col-slpDef slp lneDef dep lneSho valuesSho x,y,z

Change control row ................................................................... P.3.0.4.6 .............284Make grid .................................................................................... P.3.0.4.7 .............285Output control lines................................................................... P.3.0.4.8 .............286Input control lines ...................................................................... P.3.0.4.9 .............287Mark axes .................................................................................... P.3.0.5 ................288Input grid .................................................................................... P.3.0.6 ................289Copy grid..................................................................................... P.3.0.7 ................292Merge grids ................................................................................. P.3.0.8 ................293Cross-section grid....................................................................... P.3.0.9 ................295Edit layer ..................................................................................... P.3.2 ...................296Define depth of layer ................................................................. P.3.2.2 ................297Define thickness of layer ........................................................... P.3.2.3 ................299Add a grid layer ......................................................................... P.3.2.4 ................300Delete a grid layer ...................................................................... P.3.2.5 ................301Divide a grid layer ..................................................................... P.3.2.6 ................302Split a layer.................................................................................. P.3.2.7 ................303Join layers .................................................................................... P.3.2.8 ................304Edit area....................................................................................... P.3.3 ...................305Equalize area............................................................................... P.3.3.2 ................306Equalize columns ....................................................................... P.3.3.3 ................307Equalize rows.............................................................................. P.3.3.4 ................308Define depth of an area ............................................................. P.3.3.5 ................309Define thickness of an area ....................................................... P.3.3.6 ................310Split area ...................................................................................... P.3.3.7 ................311Join an area.................................................................................. P.3.3.8 ................312Verticalise an area ...................................................................... P.3.3.9 ................313Edit lines ...................................................................................... P.3.4 ...................314Add rows..................................................................................... P.3.4.2 ................315Add columns............................................................................... P.3.4.3 ................316Delete a row ................................................................................ P.3.4.4 ................317Delete a column.......................................................................... P.3.4.5 ................318Move a row ................................................................................. P.3.4.6 ................319Move a column ........................................................................... P.3.4.7 ................320Straighten a line.......................................................................... P.3.4.8 ................321Equalize a line............................................................................. P.3.4.9 ................322Edit nodes.................................................................................... P.3.5 ...................323Move a node................................................................................ P.3.5.2 ................324Move node to node .................................................................... P.3.5.3 ................325Define node depth...................................................................... P.3.5.4 ................326Mark node depth........................................................................ P.3.5.5 ................327Define node thickness................................................................ P.3.5.6 ................328Split nodes ................................................................................... P.3.5.7 ................329Join nodes .................................................................................... P.3.5.8 ................331Move a coordinate line .............................................................. P.3.5.9 ................332Edit fault lines............................................................................. P.3.6 ...................333Move row to a fault.................................................................... P.3.6.2 ................334Move column to a fault ............................................................. P.3.6.3 ................335Move node to fault ..................................................................... P.3.6.4 ................336Move row to a sloping fault...................................................... P.3.6.5 ................337Move column to a sloping fault ............................................... P.3.6.6 ................338Define a sloping line .................................................................. P.3.6.7 ................339Define line depth........................................................................ P.3.6.8 ................340Show values ................................................................................ P.3.7 ...................341Show x,y,z ................................................................................... P.3.7.2 ................342


www.cadfamily.com


Show I,J,K ...................................................................................P.3.7.3 ............... 343Show thickness ...........................................................................P.3.7.4 ............... 344Highlight depth range ...............................................................P.3.7.5 ............... 345Highlight thickness range .........................................................P.3.7.6 ............... 346Check grid orthogonality ..........................................................P.3.7.7 ............... 347Calculate grid orthogonality.....................................................P.3.7.7.2 ............ 348Show orthogonality for a grid block........................................P.3.7.7.3 ............ 349Show orthogonality colour fill..................................................P.3.7.7.4 ............ 350Display orthogonality report ....................................................P.3.7.7.8 ............ 351Edit blocks ...................................................................................P.3.8 .................. 352Refine grid ...................................................................................P.3.8.2 ............... 353Create local grid refinement .....................................................P.3.8.2.2 ............ 354Radial local grid refinement .....................................................P.3.8.2.3 ............ 355Delete local grid refinement...................................................... .3.8.2.4 .............. 356Delete all local grid refinements...............................................P.3.8.2.5 ............ 357Input LGR....................................................................................P.3.8.2.6 ............ 358Show local grid refinement.......................................................P.3.8.2.7 ............ 360Edit active cells ...........................................................................P.3.8.3 ............... 361Define active layer......................................................................P.3.8.3.2 ............ 362Define active area .......................................................................P.3.8.3.3 ............ 363Define active blocks ...................................................................P.3.8.3.4 ............ 364Show active .................................................................................P.3.8.3.5 ............ 365Input active cell numbers ..........................................................P.3.8.3.6 ............ 366Output active cell numbers.......................................................P.3.8.3.7 ............ 367Operate on active cells ...............................................................P.3.8.3.8 ............ 368Show total active cells................................................................P.3.8.3.9 ............ 369Edit region numbers ..................................................................P.3.8.4 ............... 370Define region layer.....................................................................P.3.8.4.2 ............ 371Define region area ......................................................................P.3.8.4.3 ............ 372Define region blocks ..................................................................P.3.8.4.4 ............ 373Show region numbers................................................................P.3.8.4.5 ............ 374Input region numbers ................................................................P.3.8.4.6 ............ 375Output region numbers.............................................................P.3.8.4.7 ............ 376Operate on region numbers ......................................................P.3.8.4.8 ............ 377Display region numbers ............................................................P.3.8.4.9 ............ 378Edit properties ............................................................................P.3.8.5 ............... 379Define property layer.................................................................P.3.8.5.2 ............ 380Define property area ..................................................................P.3.8.5.3 ............ 381Define property blocks ..............................................................P.3.8.5.4 ............ 382Show property ............................................................................P.3.8.5.5 ............ 383Input property ............................................................................P.3.8.5.6 ............ 384Output property .........................................................................P.3.8.5.7 ............ 386Operate on properties ................................................................P.3.8.5.8 ............ 387Display property values ............................................................P.3.8.5.9 ............ 388Show property fill ......................................................................P.3.8.5.9.2 ......... 389Move property key.....................................................................P.3.8.5.9.4 ......... 390Change property key .................................................................P.3.8.5.9.5 ......... 391Show property contours............................................................P.3.8.5.9.6 ......... 392Edit fluids-in-place.....................................................................P.3.8.6 ............... 393Calculate fluids-in-place............................................................P.3.8.6.2 ............ 394Show fluids-in-place ..................................................................P.3.8.6.3 ............ 395Output fluids-in-place ...............................................................P.3.8.6.4 ............ 396Delete regions .............................................................................P.3.8.7 ............... 397Delete property ...........................................................................P.3.8.8 ............... 398

Sho i,j,kSho nde thkHgh dep rngHgh thk rngChk anglesCal orthogSho orthogSho orth fllCal orthogEdt blocksRef gridCre LGRRad LGRDel LGRDel all LGRsInp LGRSho LGR nameEdt activeDef act layDef act areDef act blkSho activeInp activeOut activeOpr activeTot activeEdt regionsDef reg layDef reg areDef reg blkSho regionInp regionOut regionOpr regionDsp regionsEdt propertyDef prp layDef prp areDef prp blkSho propertyInp propertyOut propertyOpr propertyDsp propertySho prp filMov prp keyChg prp keySho prp cntsEdt FIPCal FIPSho FIPOut FIPDel regionsDel property


www.cadfamily.com


Crs gridCre coarseDel coarseInp coarseGrd utilsOut gridOpr geometryMov originRel gridRot gridScl gridOrder gridSpt gridJn gridCal ave prpsCal transGrid to maps

Sim resultsSim solutionLod solutionDsp solutionSho sol fllSho cnt seqCre solutionCre diffOut solutionClr solutionLod active

Edt surveyEdt sht lnesAdd sht lneDel sht lneDig sectionOpr horizonSho valueDef valueSmp horizonInp surveyOut surveySmp surveyTst surveySet debugOut mistiesChg svy parsChg hor numsDef granite

Map utilsECLMAP optsDep convertCnv pointCnv map

Coarsen grid................................................................................ P.3.8.9 ................399Create grid coarsening .............................................................. P.3.8.9.2 .............400Delete grid coarsening............................................................... P.3.8.9.3 .............401Input grid coarsening ................................................................ P.3.8.9.4 .............402Grid utilities ................................................................................ P.3.9 ...................403Output grid ................................................................................. P.3.9.2 ................404Operate on grid geometry......................................................... P.3.9.3 ................410Move origin................................................................................. P.3.9.3.2 .............411Relocate grid ............................................................................... P.3.9.3.3 .............412Rotate grid................................................................................... P.3.9.3.4 .............413Scale grid ..................................................................................... P.3.9.3.5 .............414Order grid blocks ....................................................................... P.3.9.3.6 .............415Split grid ...................................................................................... P.3.9.4 ................416Rejoin split grid nodes............................................................... P.3.9.5 ................417Calculate properties by map averaging.................................. P.3.9.6 ................418Calculate pore volumes and transmissibilities ...................... P.3.9.7 ................423Convert grid data to map data................................................. P.3.9.8 ................430Introduction ............................................................................... ............................435Simulator results ........................................................................ P.4 ......................436Edit solutions .............................................................................. P.4.2 ...................437Load solutions ............................................................................ P.4.2.2 ................438Display solutions........................................................................ P.4.2.3 ................439Show solution fill ....................................................................... P.4.2.3.2 .............440Show contour sequence............................................................. P.4.2.3.9 .............441Create a solution......................................................................... P.4.2.4 ................442Create differences....................................................................... P.4.2.5 ................443Output solution .......................................................................... P.4.2.6 ................444Clear a solution........................................................................... P.4.2.7 ................445Load active cell numbers from INIT file ................................ P.4.2.8 ................446Introduction ............................................................................... ............................447Edit survey .................................................................................. P.5 ......................448Edit shot lines.............................................................................. P.5.2 ...................450Add a shot line............................................................................ P.5.2.2 ................451Delete a shot line ........................................................................ P.5.2.3 ................453Digitize a section ........................................................................ P.5.2.4 ................454Operate on horizon .................................................................... P.5.2.5 ................456Show value .................................................................................. P.5.2.6 ................457Define value ................................................................................ P.5.2.7 ................458Sample horizon........................................................................... P.5.2.8 ................459Input survey................................................................................ P.5.3 ...................460Output survey............................................................................. P.5.4 ...................462Sample survey ............................................................................ P.5.5 ...................463Test survey .................................................................................. P.5.5.3 ................464Set interpolation debug ............................................................. P.5.5.6.7 .............465Output misties ............................................................................ P.5.5.9 ................466Change survey parameters ....................................................... P.5.6 ...................467Change horizon numbers.......................................................... P.5.7 ...................468Define Granite settings .............................................................. P.5.8 ...................469Introduction ............................................................................... ............................471Map utilities ................................................................................ P.6 ......................473ECLMap options ........................................................................ P.6.2 ...................474Depth conversion ....................................................................... P.6.2.2 ................475Convert a point on a map ......................................................... P.6.2.2.2 .............480Convert map ............................................................................... P.6.2.2.3 .............481


www.cadfamily.com


Convert a shot point...................................................................P.6.2.2.4 ............ 482Convert a shot line .....................................................................P.6.2.2.5 ............ 483Convert horizon..........................................................................P.6.2.2.6 ............ 484Volumetrics .................................................................................P.6.2.3 ............... 485Calculate volumes ......................................................................P.6.2.3.2 ............ 486Operate on volumes...................................................................P.6.2.3.3 ............ 488Show volumes.............................................................................P.6.2.3.4 ............ 489Sample volumes..........................................................................P.6.2.3.5 ............ 490Show zone area ...........................................................................P.6.2.3.6 ............ 491Calculate water saturation ........................................................P.6.2.4 ............... 492Import map data.........................................................................P.6.3 .................. 494Import one or more mesh maps ...............................................P.6.3.2 ............... 495Import Stratamodel data ...........................................................P.6.3.3 ............... 499Import EarthVision data............................................................P.6.3.4 ............... 506Import / export DXF files .........................................................P.6.3.5 ............... 512Import DXF data.........................................................................P.6.3.5.2 ............ 513Export DXF data .........................................................................P.6.3.5.3 ............ 517Export maps ................................................................................P.6.4 .................. 519Copy map data............................................................................P.6.5 .................. 521Process well data ........................................................................P.6.6 .................. 522Input well trajectory data ..........................................................P.6.6.2 ............... 523Output well connection data ....................................................P.6.6.3 ............... 527Delete well trajectory data ........................................................P.6.6.4 ............... 529Input CLAN ................................................................................P.6.6.5 ............... 530Introduction ................................................................................ ........................... 531Change settings...........................................................................P.7 ..................... 534Introduction ................................................................................ ........................... 537Clear workspace .........................................................................P.8 ..................... 538Run files .......................................................................................R ....................... 539Execute a run file ........................................................................R.2 .................... 543Open a run file ............................................................................R.3 .................... 544Close a run file ............................................................................R.4 .................... 545Path...............................................................................................R.5 .................... 546Set option .....................................................................................R.6 .................... 547Show coordinate position..........................................................R.7 .................... 548Introduction ................................................................................ ........................... 549Display .........................................................................................D ....................... 551Refresh .........................................................................................D.2 .................... 552Unzoom........................................................................................D.3 .................... 553Define zoom ................................................................................D.4 .................... 554Increase display ..........................................................................D.5 .................... 555Change display ...........................................................................D.6 .................... 556Change box..................................................................................D.6.2 ................. 557Change coordinate box..............................................................D.6.2.2 .............. 558Change coordinate level ............................................................D.6.2.2.2 ........... 559Change coordinate ticks ............................................................D.6.2.2.3 ........... 560Toggle coordinate box labels ....................................................D.6.2.2.4 ........... 561Change coordinate box labels...................................................D.6.2.2.5 ........... 562Change Granite settings ............................................................D.6.2.2.6 ........... 563Change graticule box .................................................................D.6.2.3 .............. 564Change graticule level ...............................................................D.6.2.3.2 ........... 565Change graticule ticks................................................................D.6.2.3.3 ........... 566Toggle graticule labels ...............................................................D.6.2.3.4 ........... 567Change graticule labels..............................................................D.6.2.3.5 ........... 568

Cnv sht pntCnv sht lneCnv horizonVolumetricsCal volumesOpr volumesSho volumesSmp volumesSho zone areaCal wtr satImport mapsMesh filesStratamodelEarthvisionDXF filesInp DXFOut DXFExport mapsCopy mapsWell dataInp wel trjOut grd connDel well trjInp CLAN

Chg settings

Clr wrkspcRExe fileOpn fileCls fileSet pathSet optionSho crd pos

DRefreshUnzoomDef zoomInc displayChg displayChg boxChg crd boxChg crd lvlChg crd tckTog crd lblChg crd lblChg graniteChg grt boxChg grt lvlChg grt tckTog grt lblChg grt lbl


www.cadfamily.com


Chg graniteTog secondsChg mapChg wellsChg faultsChg contoursChg meshChg featuresChg captionsChg zonesChg gridChg grd dspChg dsp boxChg dsp plnChg graniteSho grd cntsChg surveyChg menuChg headerChg adviceChg optionsMov menuChg col repChg locatorChg plotChg viewEdt XY-planeEdt XZ-planeEdt YZ-planeSho 3D gridRot viewEdt sht sctMap view optsOvl mapSho 3D mapChg 3D dispChg 3D pictArb sectionGrd x-sectMap gradientChg hilo txtSho well trjEdt LGRSet dig tblPlt display

Change Granite settings ............................................................ D.6.2.3.6 ............569Toggle seconds on graticule labels .......................................... D.6.2.3.7 ............570Change map display .................................................................. D.6.3 ..................571Change wells............................................................................... D.6.3.2 ...............572Change faults .............................................................................. D.6.3.3 ...............573Change contours......................................................................... D.6.3.4 ...............574Change mesh............................................................................... D.6.3.5 ...............575Change features.......................................................................... D.6.3.6 ...............576Change captions ......................................................................... D.6.3.7 ...............577Change zones.............................................................................. D.6.3.8 ...............578Change grid................................................................................. D.6.4 ..................579Change grid display................................................................... D.6.4.2 ...............580Change display box ................................................................... D.6.4.3 ...............581Change display plane ................................................................ D.6.4.4 ...............582Change Granite settings ............................................................ D.6.4.5 ...............583Show grid contours.................................................................... D.6.4.6 ...............584Change survey display.............................................................. D.6.5 ..................585Change menu.............................................................................. D.6.6 ..................586Change header............................................................................ D.6.6.2 ...............587Change advice ............................................................................ D.6.6.3 ...............588Change option ............................................................................ D.6.6.4 ...............589Move options menu ................................................................... D.6.6.5 ...............590Change colour representation .................................................. D.6.7 ..................591Change locator............................................................................ D.6.8 ..................592Change hard copy plot options................................................ D.6.9 ..................593Change view ............................................................................... D.7 .....................594Edit XY-plane.............................................................................. D.7.2 ..................595Edit XZ-plane.............................................................................. D.7.3 ..................596Edit YZ-plane.............................................................................. D.7.4 ..................597Display 3D grid .......................................................................... D.7.5 ..................598Rotate view.................................................................................. D.7.6 ..................599Edit shot line section.................................................................. D.7.7 ..................600Map view options....................................................................... D.7.8 ..................601Overlay maps.............................................................................. D.7.8.2 ...............602Show 3D map.............................................................................. D.7.8.3 ...............603Change 3D map display............................................................ D.7.8.3.8 ............605Change 3D picture ..................................................................... D.7.8.3.9 ............607Arbitrary cross-section .............................................................. D.7.8.4 ...............608Map cross-section on grid XZ/YZ view ................................. D.7.8.5 ...............609Display map gradient data ....................................................... D.7.8.6 ...............610Change text for high & low points .......................................... D.7.8.6.5 ............612Display well trajectory data...................................................... D.7.8.7 ...............613Edit local grid refinement ......................................................... D.7.9 ..................615Set up digitizing table................................................................ D.8 .....................616Plot display ................................................................................. D.9 .....................617


www.cadfamily.com

738 Index of Options GRID Reference Manualwww.cadfamily.com EMail:[email protected] document is for study only,if tort to your rights,please inform us,we will delete

www.cadfamily.com

GRID Reference Manual Index 739

Appendix PIndex

Numerics2000A, new developments for701

2001A, new developments for700



3D grid, display D.7.5 . . . 588

3D map display, change D.7.8.3.8595

3D map, show D.7.8.3 . . . 593

3D picture, change D.7.8.3.9597





AAbbreviations, dictionary of655

Active area, define P.3.8.3.3356

Active blocks, define P.3.8.3.4357

Active cell numbersinput P.3.8.3.6 . . . . . 359output P.3.8.3.7 . . . . 360

Active cell numbers from INIT file, load P.4.2.8 . . . . . . . 438

Active cells, edit P.3.8.3 . . 354

Active cells, operate on P.3.8.3.8361

Active layer, define P.3.8.3.2355

Active, show P.3.8.3.5 . . . 358

Addcaption P.2.7.3 . . . . . 229columns P.3.4.3 . . . . 307contours P.2.4.3 . . . . . 93control column P.3.0.4.1270control row P.3.0.4.2 . 271fault P.2.3.3 . . . . . . . . 63feature P.2.6.3. . . . . . 203grid layer P.3.2.4. . . . 291legend item P.2.9.3 . . 254rows P.3.4.2 . . . . . . . 306shot line P.5.2.2 . . . . 443well P.2.2.3 . . . . . . . . 49zone P.2.8.3 . . . . . . . 241

Advice, change D.6.6.3 . . 578

Advice, further help and . . . 24

Arbitrary cross-section D.7.8.4598

Areaactive, define P.3.8.3.3356depth of, define P.3.3.5300edit P.3.3 . . . . . . . . . 296equalize P.3.3.2. . . . . 297join P.3.3.8 . . . . . . . . 303property, define P.3.8.5.3374region, define P.3.8.4.3365split P.3.3.7 . . . . . . . 302thickness of, define P.3.3.6301verticalise P.3.3.9 . . . 304

Areas, fill . . . . . . . . . . . . 619

Arithmetic formulae . . . . . 645

Axes, mark P.3.0.5 . . . . . 279

BBack contour display, change P.2.4.9.8

156

Back contours, output P.2.4.9.6143

Back contours, show P.2.4.9.5141

Block valuedefine P.2.4.9.4.7.3 . 132show P.2.4.9.4.7.2 . . 131

Block values as grid property, save P.2.4.9.4.9 . . . . 140

Block values, output P.2.4.9.4.7.6135

Block, test P.2.4.9.4.4 . . . 127

Blocksactive, define P.3.8.3.4357edit P.3.8. . . . . . . . . 345property, define P.3.8.5.4375region, define P.3.8.4.4366test all P.2.4.9.4.6. . . 129

Box display, change D.6.2 547

CCalculate

fluids-in-place P.3.8.6.2386grid orthogonality P.3.7.7.2340mesh P.2.5.3 . . . . . . 180


www.cadfamily.com

740 Index GRID Reference Manual

pore volumes and transmissibilities P.3.9.7 . . . .415

properties by map averaging P.3.9.6410

volumes P.6.2.3.2 . . .477water saturation P.6.2.4483

Captionadd P.2.7.3 . . . . . . . .229change P.2.7.5.3 . . . .233delete P.2.7.4 . . . . . .230move P.2.7.5.2 . . . . .232

Caption data, change P.2.7.5231

Caption display, change D.6.3.7567

Captionscopy P.2.7.2 . . . . . . .228edit P.2.7 . . . . . . . . .227input P.2.7.6 . . . . . . .236output P.2.7.7 . . . . . .238

Change3D map display D.7.8.3.85953D picture D.7.8.3.9 .597advice D.6.6.3. . . . . .578back contour display P.2.4.9.8156box display D.6.2 . . .547caption data P.2.7.5 . .231caption display D.6.3.7567caption P.2.7.5.3 . . . .233colour fill P.2.4.9.8.3 .158colour representation D.6.7581contour interval P.2.5.6.5186contour interval, major P.2.4.6.5114contour labels, digitized P.2.4.6.4

113contour labels, gridded P.2.5.6.4185contour line P.2.4.5.5 .100contour parameters P.2.4.6110contour value P.2.4.5.3.98control column P.3.0.4.5274control row P.3.0.4.6 .275coordinate box labels D.6.2.2.5552coordinate level D.6.2.2.2549digitized contour display D.6.3.4

564digitized contours P.2.4.596display box limits D.6.4.3571display D.6 . . . . . . . .546display plane D.6.4.4 .572fault colour fill mask P.2.3.5.469fault display D.6.3.3 .563fault name P.2.3.5.2 . . .67fault P.2.3.5 . . . . . . . .66fault segment P.2.3.5.5 .70fault trace P.2.3.5.6 . . .71

fault type P.2.3.5.3 . . . 68feature display D.6.3.6566feature line P.2.6.5.3 . 207feature name P.2.6.5.2206features, names and lines P.2.6.5205Granite settings

for coordinate box display D.6.2.2.6 . . . . . 553

for graticule display D.6.2.3.6 559

for grid display D.6.4.5 . . 573pen and text for back contours

P.2.4.9.8.2 . . . . 157pen and text for existing feature

P.2.6.9 . . . . . . . 225pen and text for existing zone

P.2.8.9 . . . . . . . 251text for existing caption

P.2.7.5.5 . . . . . 235well symbol and text P.2.2.959

graticule box D.6.2.3 554graticule labels D.6.2.3.5558graticule level D.6.2.3.2555graticule ticks D.6.2.3.3556grid D.6.4 . . . . . . . . 569grid display D.6.4.2 . 570hard copy plot options D.6.9583header D.6.6.2 . . . . . 577horizon numbers P.5.7460index P.2.4.9.8.3.3 . . 160interpolation P.2.4.9.7 144item P.2.9.6 . . . . . . . 257key P.2.5.6.9.7 . . . . . 191legend P.2.9.7 . . . . . 258limits P.2.4.9.8.3.4 . . 161locator D.6.8 . . . . . . 582map area P.2.4.6.3 . . 112map display D.6.3 . . 561map name P.1.3.2 . . . . 34map stratum P.1.3.3 . . 35map units P.1.3.4 . . . . 36menu D.6.6 . . . . . . . 576mesh D.6.3.5 . . . . . . 565mesh data P.1.3.7 . . . . 39mesh interpolation P.2.5.9.4197mesh map colour fill P.2.5.6.9190mesh parameters P.2.5.6184model area P.1.3.5 . . . 37model P.1.3 . . . . . . . . 33number of model strata P.1.3.638option D.6.6.4 . . . . . 579property key P.3.8.5.9.5383secondary coordinate ticks D.6.2.2.3

550settings . . . . . . . . . . 521

settings P.7 . . . . . . . . 524survey display D.6.5 . 575survey parameters P.5.6459text for high & low points D.7.8.6.5

602view D.7 . . . . . . . . . 584well display D.6.3.2 . 562well name P.2.2.5.2 . . . 52wells P.2.2.5 . . . . . . . . 51zone P.2.8.5 . . . . . . . 243zones D.6.3.8 . . . . . . 568

Checkgrid orthogonality P.3.7.7339

Choice of map projection . 635

CLAN, input P.6.6.5 . . . . . 520

Clearsolution P.4.2.7 . . . . . 437workspace (chapter) . 527workspace P.8. . . . . . 528

Clipcontours P.2.4.5.6.2 . . 102fault trace P.2.3.5.7.2. . 73feature line P.2.6.5.4.2209

Closefault polygons P.2.3.5.7.475run file R.4. . . . . . . . 535

Coarsen grid P.3.8.9 . . . . . 391

Colour fill, change P.2.4.9.8.3158

Colour fill, orthogonality, show P.3.7.7.4342

Colour representation, change D.6.7581

Colours, reset P.2.4.9.8.3.6 164

Columndelete P.3.4.5 . . . . . . 309move P.3.4.7. . . . . . . 311move to fault P.3.6.3 . 327move to sloping fault P.3.6.6330

Columnsadd P.3.4.3 . . . . . . . . 307equalize P.3.3.3. . . . . 298

Common terms, definitions of633

Configuration file options . . 20

Configuration files, use of (appendix)683

Configuring digitizing tables627

Connecting digitizing tables625

ConPac interpolation & contouring677

Contour interval, change P.2.5.6.5186

Contour interval, major, change P.2.4.6.5


www.cadfamily.com


114

Contour labels, digitized, change P.2.4.6.4113

Contour labels, gridded, change P.2.5.6.4185

Contour line, change P.2.4.5.5100

Contour lines, operate on P.2.4.5.6101

Contour parameters, change P.2.4.6110

Contour sequence, show P.4.2.3.9433

Contour value, change P.2.4.5.398

Contour value, show P.2.4.5.297

Contour values, operate on P.2.4.5.499

Contour,back, display, change P.2.4.9.8156

Contours . . . . . . . . . . . . 105add P.2.4.3. . . . . . . . . 93change P.2.4.5 . . . . . . 96clip P.2.4.5.6.2 . . . . . 102copy P.2.4.2 . . . . . . . . 92delete P.2.4.4 . . . . . . . 95display, change D.6.3.4564edit P.2.4 . . . . . . . . . . 91extend P.2.4.5.6.9 . . . 109input P.2.4.7 . . . . . . 116join P.2.4.5.6.8 . . . . . 108output P.2.4.8. . . . . . 120repopulate P.2.4.5.6.6 106sample P.2.4.9 . . . . . 122smooth P.2.4.5.6.7 . . 107split P.2.4.5.6.3 . . . . 103thin P.2.4.5.6.5 . . . . . 105

Contours, back, output P.2.4.9.6143

Control columnadd P.3.0.4.1 . . . . . . 270change P.3.0.4.5 . . . . 274delete P.3.0.4.3. . . . . 272

Control linesinput P.3.0.4.9 . . . . . 278output P.3.0.4.8 . . . . 277

Control rowadd P.3.0.4.2 . . . . . . 271change P.3.0.4.6 . . . . 275delete P.3.0.4.4. . . . . 273

Conversion factors, unit . . 671

Conversion, depth P.6.2.2. 467

Convertgrid data to map data P.3.9.8422horizon P.6.2.2.6 . . . 475map P.6.2.2.3 . . . . . . 472point on a map P.6.2.2.2471

shot line P.6.2.2.5 . . . 474shot point P.6.2.2.4 . . 473

Coordinate box labelschange D.6.2.2.5. . . . 552toggle D.6.2.2.4 . . . . 551

Coordinate level, change D.6.2.2.2549

Coordinate line, move P.3.5.9323

Coordinate position, show R.7538

Coordinate ticks, secondary, change D.6.2.2.3. . . . . . 550

Copycaptions P.2.7.2. . . . . 228contours P.2.4.2 . . . . . 92faults P.2.3.2. . . . . . . . 62features P.2.6.2 . . . . . 202grid P.3.0.7 . . . . . . . . 283legend P.2.9.2 . . . . . . 253map data P.6.5 . . . . . 511wells P.2.2.2 . . . . . . . . 48zones P.2.8.2 . . . . . . 240

Corner valuedefine P.2.4.9.4.7.5 . . 134show P.2.4.9.4.7.4 . . . 133

Corner values on grid, save P.2.4.9.4.8139

Corner values, output P.2.4.9.4.7.7136

Correction factor, thickness (appendix)623

Createdifferences P.4.2.5. . . 435grid coarsening P.3.8.9.2392local grid refinement P.3.8.2.2347solution P.4.2.4 . . . . . 434

Cross-sectionarbitrary D.7.8.4 . . . . 598grid P.3.0.9 . . . . . . . . 286

Cross-section grid P.3.0.9 . 286

Cross-section on grid XZ/YZ view, map D.7.8.5 . . . . . . . 599

DDamping factor, define P.2.4.9.7.4147

Data, map, copy P.6.5 . . . . 511

Data, process well P.6.6 . . 512

Data, seismic . . . . . . . . . . . 17

Debug, interpolation, set P.5.5.6.7457

Define

active area P.3.8.3.3 . 356active blocks P.3.8.3.4357active layer P.3.8.3.2 355block value P.2.4.9.4.7.3132corner value P.2.4.9.4.7.5134damping factor P.2.4.9.7.4147depth of an area P.3.3.5300depth of layer P.3.2.2 288Granite settings

digitized contours, for P.2.4.6.6115

fill area, pen and text for new zones P.2.8.8 . . 250

for well symbol and text P.2.2.858

pen and text for faults P.2.3.8 .90

pen and text for mesh contours P.2.5.6.8 . . . . . 189

pen and text for new features P.2.6.8. . . . . . . 224

pen, text and shot point marker P.5.8 . . . . . . . . 461

text for drawing legend P.2.9.8259

text for new captions P.2.7.5.4234

interpolation mode P.2.4.9.7.6151line depth P.3.6.8 . . . 332mesh value P.2.5.7 . . 192node depth P.3.5.4 . . 317node thickness P.3.5.6 319null P.2.4.9.7.2 . . . . 145property area P.3.8.5.3374property blocks P.3.8.5.4375property layer P.3.8.5.2373region area P.3.8.4.3. 365region blocks P.3.8.4.4366region layer P.3.8.4.2 364search radius P.2.4.9.7.5148sloping line P.3.6.7. . 331thickness of area P.3.3.6301thickness of layer P.3.2.3290truncation values P.2.4.9.7.3146value P.5.2.7 . . . . . . 450zoom D.4 . . . . . . . . 544

Definitions of common terms633

Deleteall local grid refinements P.3.8.2.5

350caption P.2.7.4 . . . . . 230column P.3.4.5. . . . . 309contours P.2.4.4 . . . . . 95control column P.3.0.4.3272control row P.3.0.4.4 273


www.cadfamily.com


fault region P.2.4.5.6.4104faults P.2.3.4 . . . . . . . .65features P.2.6.4 . . . . .204grid coarsening P.3.8.9.3393grid layer P.3.2.5 . . . .292grid P.1.2.4 . . . . . . . . .31legend item P.2.9.4 . .255local grid refinement P.3.8.2.4349map P.1.2.3 . . . . . . . . .30model P.1.2. . . . . . . . .28property P.3.8.8 . . . . .390regions P.3.8.7 . . . . .389row P.3.4.4 . . . . . . . .308shot line P.5.2.3 . . . . .445stratum P.1.2.2 . . . . . .29survey P.1.2.5 . . . . . . .32well P.2.2.4 . . . . . . . . .50well trajectory data P.6.6.4519zones P.2.8.4 . . . . . . .242

Depth conversion and volumetrics17

Depth conversion P.6.2.2 . .467

Depth of an areadefine P.3.3.5 . . . . . .300

Depth of layerdefine P.3.2.2 . . . . . .288

Depth range, highlight P.3.7.5337

Depth, linedefine P.3.6.8 . . . . . .332

Depth, nodedefine P.3.5.4 . . . . . .317

Development, history of . .697

Developmentsnew . . . . . . . . . . . . . .13

Dictionary of abbreviations655

Differencescreate P.4.2.5. . . . . . .435

Digitize a section P.5.2.4 . .446

Digitizing tableset up D.8 . . . . . . . . .606

Digitizing tables . . . . . . . .625

Digitizing tables, configuring627

Digitizing tables, connecting625

Display3D grid D.7.5 . . . . . .588change D.6 . . . . . . . .546increase D.5 . . . . . . .545map gradient data D.7.8.6600orthogonality report P.3.7.7.8343plot D.9 . . . . . . . . . .607property values P.3.8.5.9380

region numbers P.3.8.4.9371solutions P.4.2.3 . . . . 431well trajectory data D.7.8.7603

Display (chapter). . . . . . . 539

Display box limits, change D.6.4.3571

Display D . . . . . . . . . . . . 541

Display plane, change D.6.4.4572

Displays, X-windows . . . . 23

Divide a grid layer P.3.2.6 293

DXF dataexport P.6.3.5.3 . . . . 507import P.6.3.5.2 . . . . 503

DXF files, Import/export P.6.3.5502

EEarthVision data, import P.6.3.4497

ECLMap options P.6.2 . . . 466

Editactive cells P.3.8.3 . . 354area P.3.3. . . . . . . . . 296blocks P.3.8 . . . . . . . 345captions P.2.7. . . . . . 227contours P.2.4 . . . . . . 91fault lines P.3.6 . . . . 325faults P.2.3. . . . . . . . . 61features P.2.6 . . . . . . 201fluids-in-place P.3.8.6 385grid. . . . . . . . . . . . . 261grid P.3 . . . . . . . . . . 264layer P.3.2 . . . . . . . . 287legend P.2.9 . . . . . . . 252lines P.3.4 . . . . . . . . 305local grid refinement D.7.9605map . . . . . . . . . . . . . 43map P.2 . . . . . . . . . . . 45mesh P.2.5 . . . . . . . . 167model P.1 . . . . . . . . . 27nodes P.3.5 . . . . . . . 314properties P.3.8.5 . . . 372region numbers P.3.8.4363sample values P.2.4.9.4.7130shot line section D.7.7590shot lines P.5.2 . . . . . 442solutions P.4.2 . . . . . 429survey (chapter) . . . . 439wells P.2.2 . . . . . . . . . 47XY-plane D.7.2 . . . . 585XZ-plane D.7.3 . . . . 586YZ-plane D.7.4 . . . . 587

zones P.2.8 . . . . . . . . 239

Edit model, primary menu and (chapter)25

Editing simulation grid . . . . 17

Equalizearea P.3.3.2. . . . . . . . 297columns P.3.3.3 . . . . 298line P.3.4.9 . . . . . . . . 313rows P.3.3.4 . . . . . . . 299

Execute run file R.2 . . . . . 533

ExportDXF data P.6.3.5.3 . . 507DXF files P.6.3.5 . . . 502maps P.6.4 . . . . . . . . 509

Extendcontours P.2.4.5.6.9 . . 109faults P.2.3.5.7.9 . . . . . 80features P.2.6.5.4.8 . . 215

FFacilities, general . . . . . . . . 18

Facilities, mapping. . . . . . . 16

Facilities, projection . . . . . 636

Factor, thickness correction623

Factors, unit conversion . . 671

Faultadd P.2.3.3 . . . . . . . . . 63change P.2.3.5 . . . . . . 66

Fault colour fill mask, change P.2.3.5.469

Fault display, change D.6.3.3563

Fault lines, edit P.3.6 . . . . 325

Fault name, change P.2.3.5.267

Fault polygons, close P.2.3.5.7.475

Fault region, delete P.2.4.5.6.4104

Fault segment, change P.2.3.5.570

Fault tracechange P.2.3.5.6 . . . . . 71clip P.2.3.5.7.2 . . . . . . 73split P.2.3.5.7.3 . . . . . . 74

Fault traces, operate on P.2.3.5.772

Fault type, change P.2.3.5.3. 68

Faultscopy P.2.3.2 . . . . . . . . 62delete P.2.3.4 . . . . . . . 65edit P.2.3 . . . . . . . . . . 61


www.cadfamily.com


extend P.2.3.5.7.9 . . . . 80in interpolation, toggle P.2.4.9.7.8

154input P.2.3.6 . . . . . . . 81join P.2.3.5.7.8 . . . . . . 79output P.2.3.7. . . . . . . 86repopulate P.2.3.5.7.6 . 77smooth P.2.3.5.7.7 . . . 78thin P.2.3.5.7.5 . . . . . . 76

Feature display, change D.6.3.6566

Feature linechange P.2.6.5.3 . . . . 207clip P.2.6.5.4.2 . . . . . 209split P.2.6.5.4.3 . . . . 210

Feature linesoperate on P.2.6.5.4 . 208

Feature name, change P.2.6.5.2206

Feature, add P.2.6.3 . . . . . 203

Featurescopy P.2.6.2 . . . . . . . 202delete P.2.6.4 . . . . . . 204edit P.2.6 . . . . . . . . . 201extend P.2.6.5.4.8 . . . 215input P.2.6.6 . . . . . . 216join P.2.6.5.4.7 . . . . . 214names and lines, change P.2.6.5205output P.2.6.7. . . . . . 220repopulate P.2.6.5.4.5 212smooth P.2.6.5.4.6 . . 213thin P.2.6.5.4.4 . . . . . 211

File handling (chapter). . . . 21

File names (appendix) . . . 611

Files, run (chapter) . . . . . 529

Files, run R. . . . . . . . . . . 529

Fill areas . . . . . . . . . . . . 619

Fluids-in-placecalculate P.3.8.6.2 . . 386edit P.3.8.6 . . . . . . . 385output P.3.8.6.4 . . . . 388show P.3.8.6.3 . . . . . 387

Formats, UKOOA . . . . . . 675

Formulae, arithmetic . . . . 645

Further help and advice . . . 24

GGeneral facilities . . . . . . . . 18

Glossary of terms . . . . . . 665

GRANITE section of config. file696

Granite settingscoordinate box display, for

change D.6.2.2.6 . . . . . . .553digitized contours, for

define P.2.4.6.6 . . . . . . . . 115fill area, pen and text for new zones

define P.2.8.8 . . . . . . . . .250graticule display, for

change D.6.2.3.6 . . . . . . .559grid display, for

change D.6.4.5 . . . . . . . .573pen and text

for back contours, change P.2.4.9.8.2. . . . .157

for existing feature, change P.2.6.9 . . . . . . .225

for existing zone, change P.2.8.9 . . . . . . .251

for faults, define P.2.3.8 . . . 90for mesh contours, define

P.2.5.6.8 . . . . . .189for new features, define P.2.6.8

224pen, text and shot point marker for

shot linesdefine P.5.8 . . . . . . . . . . .461

text for drawing legenddefine P.2.9.8 . . . . . . . . .259

text for existing captionchange P.2.7.5.5. . . . . . . .235

text for new captionsdefine P.2.7.5.4 . . . . . . . .234

well symbol and textchange P.2.2.9 . . . . . . . . . . 59

Granite settings (chapter) . 613

Granitesettingswell symbol and text

define P.2.2.8 . . . . . . . . . . 58

Graticule boxchange D.6.2.3 . . . . . 554

Graticule labelschange D.6.2.3.5. . . . 558toggle D.6.2.3.4 . . . . 557

Graticule levelchange D.6.2.3.2. . . . 555

Graticule tickschange D.6.2.3.3. . . . 556

GRIDfunctionality . . . . . . . . 16section of config. file 688terminology . . . . . . . . 21

Gridchange D.6.4 . . . . . . 569coarsen P.3.8.9 . . . . 391copy P.3.0.7 . . . . . . 283cross-section P.3.0.9. 286delete P.1.2.4 . . . . . . . 31edit. . . . . . . . . . . . . 261edit P.3 . . . . . . . . . . 264input P.3.0.6 . . . . . . 280irregular P.3.0.4 . . . . 268make P.3.0.4.7 . . . . . 276N x M P.3.0.3 . . . . . 267output P.3.9.2 . . . . . 396refine P.3.8.2 . . . . . . 346relocate P.3.9.3.3 . . . 404rotate P.3.9.3.4. . . . . 405scale P.3.9.3.5 . . . . . 406split P.3.9.4 . . . . . . . 408test P.2.4.9.4 . . . . . . 125utilities P.3.9 . . . . . . 395values of, show P.3.7 333vector P.3.0.2 . . . . . 266

Grid blocks, order P.3.9.3.6407

Grid coarsening, create P.3.8.9.2392

Grid coarsening, delete P.3.8.9.3393

Grid coarsening, input P.3.8.9.4394

Grid contours, show D.6.4.6574

Grid data to map data, convert P.3.9.8422

Grid display, change D.6.4.2570

Grid geometry, operate on P.3.9.3402

Grid layeradd P.3.2.4 . . . . . . . 291delete P.3.2.5 . . . . . . 292divide P.3.2.6 . . . . . 293

Grid orthogonalitycalculate P.3.7.7.2 . . 340check P.3.7.7 . . . . . . 339

GRID, setting up a table from632

GRID, using . . . . . . . . . . . 19

Gridsmerge P.3.0.8 . . . . . 284

HHandling, file . . . . . . . . . . 21

Hard copy plot options, change D.6.9583

Header


www.cadfamily.com


change D.6.6.2 . . . . .577

Help and advice, further . . .24

HELP section . . . . . . . . . .695

High & low points, text for, change D.7.8.6.5 . . . . . .602

Highlightdepth range P.3.7.5 . .337thickness range P.3.7.6338

History filelist P.1.4 . . . . . . . . . . .40

History of development. . .697

Horizonconvert P.6.2.2.6 . . . .475operate on P.5.2.5 . . .448sample P.5.2.8 . . . . . .451

Horizon numberschange P.5.7 . . . . . . .460

II,J,K

show P.3.7.3 . . . . . . .335

ImportDXF data P.6.3.5.2 . .503EarthVision data P.6.3.4497map data P.6.3. . . . . .485mesh maps P.6.3.2 . . .486Stratamodel data P.6.3.3490

Import/exportDXF files P.6.3.5 . . . .502

Increasedisplay D.5 . . . . . . . .545

Indexchange P.2.4.9.8.3.3 . .160

Inputactive cell numbers P.3.8.3.6359captions P.2.7.6 . . . . .236CLAN P.6.6.5 . . . . . .520contours P.2.4.7. . . . . 116control lines P.3.0.4.9.278faults P.2.3.6 . . . . . . . .81features P.2.6.6 . . . . .216grid coarsening P.3.8.9.4394grid P.3.0.6 . . . . . . . .280LGR P.3.8.2.6 . . . . . .351mesh P.2.5.2 . . . . . . .168property P.3.8.5.6 . . .377region numbers P.3.8.4.6368survey P.5.3 . . . . . . .452

well trajectory data P.6.6.2513wells P.2.2.6 . . . . . . . 54zones P.2.8.6 . . . . . . 244

Interpolation debug, set P.5.5.6.7457

Interpolation mode, define P.2.4.9.7.6151

Interpolation, change P.2.4.9.7144

Interval, contour, change P.2.5.6.5186

Interval, major, contour, change P.2.4.6.5114

Irregular grid P.3.0.4 . . . . 268

Itemchange P.2.9.6 . . . . . 257move P.2.9.5 . . . . . . 256

JJoin

area P.3.3.8 . . . . . . . 303contours P.2.4.5.6.8 . 108faults P.2.3.5.7.8 . . . . 79features P.2.6.5.4.7 . . 214layers P.3.2.8 . . . . . . 295nodes P.3.5.8 . . . . . . 322

KKey, change P.2.5.6.9.7 . . 191

LLayer

define active P.3.8.3.2 355define depth of P.3.2.2288define thickness of P.3.2.3290edit P.3.2 . . . . . . . . . 287grid, delete P.3.2.5 . . 292split P.3.2.7 . . . . . . . 294

Layer, property, define P.3.8.5.2373

Layer, region, define P.3.8.4.2364

Layersjoin P.3.2.8 . . . . . . . 295

Legendchange P.2.9.7 . . . . . 258copy P.2.9.2 . . . . . . . 253edit P.2.9 . . . . . . . . . 252

Legend itemadd P.2.9.3 . . . . . . . . 254delete P.2.9.4 . . . . . . 255

LGR, input P.3.8.2.6. . . . . 351

Limits, change P.2.4.9.8.3.4161

Line depth, define P.3.6.8 . 332

Line, equalize P.3.4.9 . . . . 313

Line, sloping, define P.3.6.7331

Line, straighten P.3.4.8 . . . 312

Linesedit P.3.4 . . . . . . . . . 305

List history file P.1.4 . . . . . 40

Load active cell numbers from INIT file P.4.2.8 . . . . . . . 438

Load solutions P.4.2.2. . . . 430

Local grid refinementcreate P.3.8.2.2 . . . . . 347delete P.3.8.2.4 . . . . . 349edit D.7.9 . . . . . . . . . 605radial P.3.8.2.3 . . . . . 348show P.3.8.2.7 . . . . . 353

Local grid refinements, delete all P.3.8.2.5350

Locator, change D.6.8 . . . 582

Low points, text for, change D.7.8.6.5602

MMake, grid P.3.0.4.7 . . . . . 276

Mapconvert P.6.2.2.3 . . . . 472cross-section on grid XZ/YZ view

D.7.8.5 . . . 599delete P.1.2.3 . . . . . . . 30edit . . . . . . . . . . . . . . 43edit P.2. . . . . . . . . . . . 45projections (appendix)633test P.2.4.9.3 . . . . . . . 124utilities . . . . . . . . . . 463utilities P.6 . . . . . . . . 465view options D.7.8 . . 591

Map areachange P.2.4.6.3 . . . . 112show P.2.4.6.2 . . . . . 111

Map averaging, calculate properties by P.3.9.6 . . . . . . . 410

Map data


www.cadfamily.com


copy P.6.5 . . . . . . . . 511import P.6.3 . . . . . . . 485

Map display, change D.6.3 561

Map gradient data, display D.7.8.6600

Map name, change P.1.3.2 . 34

Map projection, choice of. 635

Map stratum, change P.1.3.3 35

Map units, change P.1.3.4. . 36

Map, point on, convert P.6.2.2.2471

Mapping facilities . . . . . . . 16

Mapsexport P.6.4 . . . . . . . 509overlay D.7.8.2 . . . . 592

Mark axes P.3.0.5 . . . . . . 279

Mark node depth P.3.5.5. . 318

Markers . . . . . . . . . . . . . 615

Mask mesh P.2.5.5. . . . . . 183

Maximum & minimum, show P.2.5.6.6187

Menu and edit model, primary25

Menu template . . . . . . . . 609

Menu, change D.6.6 . . . . 576

Menu, primary . . . . . . . . . 26

Menus . . . . . . . . . . . . . . . 22

Merge grids P.3.0.8 . . . . . 284

Meshcalculate P.2.5.3 . . . . 180change D.6.3.5. . . . . 565edit P.2.5 . . . . . . . . . 167input P.2.5.2 . . . . . . 168mask P.2.5.5 . . . . . . 183operate on P.2.5.4 . . . 181output P.2.5.8. . . . . . 193sample P.2.5.9 . . . . . 196

Mesh data, change P.1.3.7 . 39

Mesh interpolation, change P.2.5.9.4197

Mesh map colour fill, change P.2.5.6.9190

Mesh maps, import P.6.3.2 486

Mesh parameters, change P.2.5.6184

Mesh value, define P.2.5.7 192

Minimum & maximum, show P.2.5.6.6187

Minimum slope, toggle P.2.4.9.7.9155

Misties, output P.5.5.9 . . . 458

Model

change P.1.3 . . . . . . . . 33delete P.1.2. . . . . . . . . 28edit P.1. . . . . . . . . . . . 27

Model area, change P.1.3.5 . 37

Model report, output P.1.5. . 41

Model, primary menu and edit25

Movecaption P.2.7.5.2 . . . . 232column P.3.4.7 . . . . . 311column to fault P.3.6.3327column to sloping fault P.3.6.6330coordinate line P.3.5.9323item P.2.9.5 . . . . . . . 256node P.3.5.2 . . . . . . . 315node to fault P.3.6.4 . 328node to node P.3.5.3 . 316options menu D.6.6.5 580origin P.3.9.3.2 . . . . . 403property key P.3.8.5.9.4382row P.3.4.6 . . . . . . . . 310row to fault P.3.6.2 . . 326row to sloping fault P.3.6.5329well P.2.2.5.3 . . . . . . . 53

NN x M, grid P.3.0.3 . . . . . . 267

Names, file (appendix) . . . 611

New developments. . . . . . . 13for 2000A . . . . . . . . 701for 2001A . . . . . . . . 700for 2002A . . . . . . . . 699for 2003A . . . . . . . . 698for 96A . . . . . . . . . . 713for 97A . . . . . . . . . . 709for 98A . . . . . . . . . . 707for 99A . . . . . . . . . . 703

Nodemove P.3.5.2. . . . . . . 315move to fault P.3.6.4 . 328move to node P.3.5.3 . 316test P.2.4.9.4.3 . . . . . 126

Node depthdefine P.3.5.4 . . . . . . 317mark P.3.5.5 . . . . . . . 318

Node thickness, define P.3.5.6319

Node values, output P.2.4.9.4.7.8137

Nodesedit P.3.5 . . . . . . . . . 314

join P.3.5.8 . . . . . . . 322split P.3.5.7 . . . . . . . 320test all P.2.4.9.4.5. . . 128

Nouns . . . . . . . . . . . . . . 658

Null mask boundary, toggle P.2.5.9.4.7198

Null, define P.2.4.9.7.2 . . 145

Nulls, show P.2.5.6.7. . . . 188

Number of model strata, change P.1.3.638

Number of styles P.2.4.9.8.3.2159

OOpen run file R.3 . . . . . . 534

Operate onactive cells P.3.8.3.8. 361contour lines P.2.4.5.6101contour values P.2.4.5.499fault traces P.2.3.5.7. . 72feature lines P.2.6.5.4 208grid geometry P.3.9.3 402horizon P.5.2.5 . . . . 448mesh P.2.5.4 . . . . . . 181properties P.3.8.5.8 . 379region numbers P.3.8.4.8370volumes P.6.2.3.3. . . 479

Optionchange D.6.6.4 . . . . 579set R.6 . . . . . . . . . . 537

Options menumove D.6.6.5 . . . . . 580

Options, configuration file . 20

Options, ECLMap P.6.2. . 466

Options, view, map D.7.8 591

Order, grid blocks P.3.9.3.6407

Origin, move P.3.9.3.2. . . 403

Orthogonality colour fill, show P.3.7.7.4342

Orthogonality for a grid block, show P.3.7.7.3 . . . . . 341

Orthogonality of grid, calculate P.3.7.7.2340

Orthogonality report, display P.3.7.7.8343

Outputactive cell numbers P.3.8.3.7360back contours P.2.4.9.6143


www.cadfamily.com


block values P.2.4.9.4.7.6135captions P.2.7.7 . . . . .238contours P.2.4.8. . . . .120control lines P.3.0.4.8.277corner values P.2.4.9.4.7.7136faults P.2.3.7 . . . . . . . .86features P.2.6.7 . . . . .220fluids-in-place P.3.8.6.4388grid P.3.9.2 . . . . . . . .396mesh P.2.5.8 . . . . . . .193misties P.5.5.9 . . . . . .458model report P.1.5 . . . .41node values P.2.4.9.4.7.8137property P.3.8.5.7 . . .378region numbers P.3.8.4.7369solution P.4.2.6 . . . . .436survey P.5.4 . . . . . . .454well connection data P.6.6.3517wells P.2.2.7 . . . . . . . .56zones P.2.8.7 . . . . . . .247

Overlay, maps D.7.8.2. . . .592

PPath R.5 . . . . . . . . . . . . .536

Pens . . . . . . . . . . . . . . . .614

Plot display D.9 . . . . . . . .607

Point on a map, convert P.6.2.2.2471

Point, test P.2.4.9.2 . . . . . .123

Pore volumes and transmissibilities, calculate P.3.9.7 .415

Primary menu . . . . . . . . . .26

Primary menu and edit model (chapter)25

Process well data P.6.6 . . .512

Program, starting . . . . . . . .19

Projection facilities. . . . . .636

Projection, map, choice of .635

Projectionsmap (appendix) . . . . .633

Propertiesedit P.3.8.5 . . . . . . . .372operate on P.3.8.5.8 . .379

Properties by map averaging, calculate P.3.9.6. . . . . . . .410

Propertydelete P.3.8.8 . . . . . .390input P.3.8.5.6 . . . . . .377

output P.3.8.5.7 . . . . 378show P.3.8.5.5 . . . . . 376

Property area, define P.3.8.5.3374

Property blocks, define P.3.8.5.4375

Property contours, show P.3.8.5.9.6384

Property fill, show P.3.8.5.9.2381

Property keychange P.3.8.5.9.5 . . 383move P.3.8.5.9.4 . . . 382

Property layer, define P.3.8.5.2373

Property values, display P.3.8.5.9380

RRadial local grid refinement P.3.8.2.3348

Radius, search, define P.2.4.9.7.5148

Refine grid P.3.8.2. . . . . . 346

Refresh D.2 . . . . . . . . . . 542

Region area, define P.3.8.4.3365

Region blocks, define P.3.8.4.4366

Region layer, define P.3.8.4.2364

Region numbersdisplay P.3.8.4.9. . . . 371edit P.3.8.4 . . . . . . . 363input P.3.8.4.6 . . . . . 368operate on P.3.8.4.8 . 370output P.3.8.4.7 . . . . 369show P.3.8.4.5 . . . . . 367

Regions, delete P.3.8.7 . . . 389

Rejoin split grid nodes P.3.9.5409

Relocate grid P.3.9.3.3 . . . 404

Repopulatecontours P.2.4.5.6.6 . 106faults P.2.3.5.7.6 . . . . 77features P.2.6.5.4.5 . . 212

Reset colours P.2.4.9.8.3.6 164

Results, simulation (chapter)427

Results, simulator P.4 . . . 428

Rotategrid P.3.9.3.4 . . . . . . 405view D.7.6. . . . . . . . 589

Rowdelete P.3.4.4 . . . . . . 308move P.3.4.6 . . . . . . 310move to fault P.3.6.2. 326move to sloping fault P.3.6.5329

Row, control, delete P.3.0.4.4273

Rowsadd P.3.4.2 . . . . . . . . 306equalize P.3.3.4. . . . . 299

Run fileclose R.4 . . . . . . . . . 535execute R.2 . . . . . . . 533open R.3 . . . . . . . . . 534

Run files (chapter) . . . . . . 529

Run files R . . . . . . . . . . . 529

SSample

contours P.2.4.9 . . . . 122horizon P.5.2.8 . . . . . 451mesh P.2.5.9 . . . . . . . 196survey P.5.5 . . . . . . . 455volumes P.6.2.3.5 . . . 481

Sample values, edit P.2.4.9.4.7130

Sampled contours, show P.2.4.9.4.7.9138

Sampling values for simulation grids673

Save block values as grid property P.2.4.9.4.9 . . . . . 140

Save corner values on grid P.2.4.9.4.8139

Scale grid P.3.9.3.5. . . . . . 406

Search circle, show P.2.5.9.4.9199

Search radius, define P.2.4.9.7.5148

Secondary coordinate ticks, change D.6.2.2.3. . . . . . 550

Seconds on graticule labels, toggle D.6.2.3.7. . . . . . 560

Section, digitize P.5.2.4 . . 446

Section, GRANITE . . . . . 696

Section, HELP. . . . . . . . . 695

Section, SYSTEM . . . . . . 687

Seismic data . . . . . . . . . . . 17

Select variable transformation P.2.4.9.9165

Setinterpolation debug P.5.5.6.7457option R.6 . . . . . . . . 537shading P.2.4.9.8.3.5 . 162weighting for well control points

P.2.4.9.7.7 . 153

Set up digitizing table D.8. 606


www.cadfamily.com


Setting up table from GRID632

Settingschange (chapter) . . . 521change P.7 . . . . . . . . 524

Settings, Granite (chapter) 613

Shading, set P.2.4.9.8.3.5 . 162

Shot lineadd P.5.2.2. . . . . . . . 443convert P.6.2.2.5 . . . 474delete P.5.2.3 . . . . . . 445section, edit D.7.7 . . 590

Shot lines, edit P.5.2 . . . . 442

Shot pointconvert P.6.2.2.4 . . . 473value of, show P.5.2.6 449

Show3D map D.7.8.3 . . . . 593active P.3.8.3.5. . . . . 358back contours P.2.4.9.5141block value P.2.4.9.4.7.2131contour sequence P.4.2.3.9433contour value P.2.4.5.2 97coordinate position R.7538corner value P.2.4.9.4.7.4133fluids-in-place P.3.8.6.3387grid contours D.6.4.6 574I,J,K P.3.7.3 . . . . . . . 335local grid refinement P.3.8.2.7353map area P.2.4.6.2 . . 111minimum & maximum P.2.5.6.6187nulls P.2.5.6.7 . . . . . 188orthogonality colour fill P.3.7.7.4

342orthogonality for a grid block

P.3.7.7.3 . . 341property contours P.3.8.5.9.6384property fill P.3.8.5.9.2381property P.3.8.5.5 . . . 376region numbers P.3.8.4.5367sampled contours P.2.4.9.4.7.9138search circle P.2.5.9.4.9199solution fill P.4.2.3.2 432thickness P.3.7.4 . . . 336total active cells P.3.8.3.9362value, of shot point P.5.2.6449values, of grid P.3.7 . 333volumes P.6.2.3.4 . . . 480x,y,z P.3.7.2 . . . . . . . 334zone area P.6.2.3.6 . . 482

Simulation grid, editing . . . 17

Simulation results (chapter)427

Simulator results P.4. . . . . 428

Slope, minimum, toggle P.2.4.9.7.9155

Sloping line, define P.3.6.7 331

Smoothcontours P.2.4.5.6.7 . . 107faults P.2.3.5.7.7 . . . . . 78features P.2.6.5.4.6 . . 213

Solutionclear P.4.2.7 . . . . . . . 437create P.4.2.4 . . . . . . 434output P.4.2.6 . . . . . . 436

Solution fill, show P.4.2.3.2432

Solutionsdisplay P.4.2.3 . . . . . 431edit P.4.2 . . . . . . . . . 429load P.4.2.2 . . . . . . . 430

Spheroids (Ellipsoids) . . . 642

Splitarea P.3.3.7. . . . . . . . 302contours P.2.4.5.6.3 . . 103fault trace P.2.3.5.7.3. . 74feature line P.2.6.5.4.3210grid P.3.9.4 . . . . . . . . 408layer P.3.2.7 . . . . . . . 294nodes P.3.5.7 . . . . . . 320

Split grid nodes, rejoin P.3.9.5409

Starting the program. . . . . . 19

Straighten a line P.3.4.8 . . 312

Stratamodel data, import P.6.3.3490

Stratum, delete P.1.2.2 . . . . 29

Styles, number of P.2.4.9.8.3.2159

Surveydelete P.1.2.5 . . . . . . . 32display, change D.6.5 575edit (chapter) . . . . . . 439input P.5.3 . . . . . . . . 452output P.5.4 . . . . . . . 454parameters, change P.5.6459sample P.5.5 . . . . . . . 455test P.5.5.3 . . . . . . . . 456

SYSTEM section . . . . . . . 687

TTable from GRID, setting up632

Tables, digitizing . . . . . . . 625

Template, menu (appendix)609

Terminology, GRID . . . . . 21

Terms, glossary of. . . . . . 665

Testall blocks P.2.4.9.4.6 129all nodes P.2.4.9.4.5 . 128block P.2.4.9.4.4 . . . 127grid P.2.4.9.4 . . . . . . 125map P.2.4.9.3. . . . . . 124node P.2.4.9.4.3 . . . . 126point P.2.4.9.2 . . . . . 123survey P.5.5.3 . . . . . 456

Text . . . . . . . . . . . . . . . . 621

Text for high & low points, change D.7.8.6.5 . . . . . 602

Thicknesscorrection factor (appendix)623node, define P.3.5.6 . 319of area, define P.3.3.6 301of layer, define P.3.2.3290range, highlight P.3.7.6338show P.3.7.4 . . . . . . 336

Thincontours P.2.4.5.6.5 . 105faults P.2.3.5.7.5 . . . . 76features P.2.6.5.4.4. . .211

Ticks, coordinate, secondary, change D.6.2.2.3 . . . . . 550

Togglecoordinate box labels D.6.2.2.4551faults in interpolation P.2.4.9.7.8

154graticule labels D.6.2.3.4557minimum slope P.2.4.9.7.9155null mask boundary P.2.5.9.4.7198seconds on graticule labels D.6.2.3.7

560

Total active cells, show P.3.8.3.9362

Transformation, select variable P.2.4.9.9165

Truncation values, define P.2.4.9.7.3146

UUKOOA formats . . . . . . 675

Unit conversion factors . . 671

Unzoom D.3. . . . . . . . . . 543

Use of configuration files (appendix)683

Using GRID . . . . . . . . . . . 19


www.cadfamily.com


Utilitiesgrid P.3.9 . . . . . . . . .395map (chapter) . . . . . .463map P.6 . . . . . . . . . .465

VValue

define P.5.2.7 . . . . . .450

Values for simulation grids,sampling673

Variable transformation, select P.2.4.9.9165

Vector grid P.3.0.2 . . . . . .266

Verbs. . . . . . . . . . . . . . . .656

Verticalise, area P.3.3.9 . . .304

Viewchange D.7 . . . . . . . .584rotate D.7.6. . . . . . . .589

View options, map D.7.8 . .591

Volumescalculate P.6.2.3.2 . . .477operate on P.6.2.3.3 . .479sample P.6.2.3.5 . . . .481show P.6.2.3.4. . . . . .480

Volumetrics P.6.2.3 . . . . . .476

Volumetrics, depth conversion and17

WWater saturation, calculate P.6.2.4483

Weighting for well control points, set P.2.4.9.7.7 . . . . 153

Welladd P.2.2.3. . . . . . . . . 49delete P.2.2.4 . . . . . . . 50move P.2.2.5.3 . . . . . . 53

Well connection data, output P.6.6.3517

Well control points, weighting for, set P.2.4.9.7.7 . . . . 153

Well data, process P.6.6 . . 512

Well name, change P.2.2.5.2 52

Well trajectory datadelete P.6.6.4 . . . . . . 519display D.7.8.7 . . . . 603input P.6.6.2 . . . . . . 513

Wells . . . . . . . . . . . . . . . 617change or move P.2.2.5 51change, display of D.6.3.2562copy P.2.2.2 . . . . . . . . 48edit P.2.2 . . . . . . . . . . 47input P.2.2.6 . . . . . . . 54output P.2.2.7. . . . . . . 56

Workspaceclear (chapter) . . . . . 527clear P.8 . . . . . . . . . 528

Xx,y,z

show P.3.7.2 . . . . . . 334

X-windows displays . . . . . 23

XY-planeedit D.7.2 . . . . . . . . . 585

XZ-planeedit D.7.3 . . . . . . . . . 586

YYZ-plane

edit D.7.4 . . . . . . . . . 587

ZZone

add P.2.8.3 . . . . . . . . 241change P.2.8.5 . . . . . 243

Zone areashow P.6.2.3.6 . . . . . 482

Zoneschange D.6.3.8 . . . . . 568copy P.2.8.2 . . . . . . . 240delete P.2.8.4 . . . . . . 242edit P.2.8 . . . . . . . . . 239input P.2.8.6 . . . . . . . 244output P.2.8.7 . . . . . . 247

Zoomdefine D.4 . . . . . . . . 544


www.cadfamily.com

eclipse grid_refernce manual

Documents