//  Script generated by Search Maker Pro:

sQ1=new Array();sQ1[1]=new Array("TGmanual/index.html","TGmanual","","Reference Manual");sQ1[2]=new Array("TGmanual/69.html","Overview of data requirements","","[UP] [TOP] [HOME] TransGen data requirements TransGen is a system for estimating and outputting either single or two-phase faulted transmissibility data suitable for inclusion in flow simulation models.    One of the design goals was to minimise the amount of work required when preparing input and using output from TransGen.  To achieve this goal, the program mimics the behaviour of the Eclipse keyword system and adopts other Eclipse styles and conventions.  TransGen (via the WizGen module) constructs and uses its own run instruction file (<Project>.TGDATA file) which conforms to and uses Eclipse keywords.  For details of the TransGen instruction file click here. TransGen will only take an Eclipse format cellular model as input, it does not take horizon and fault files from a seismic interpretation package.  Wells are positioned by the indices of the cells they connect with, not by well trajectories in UTM or geographical coordinates.  For TransGen:-   Only an eight corner-point geometry is supported   Only a Cartesian Coordinate system can be used.  TransGen does not accept radial coordinates.   Only one Eclipse 'reservoir' is allowed per model (i.e. Eclipse keyword NUMRES = 1  which means only one coordinate system per model)   Only a subset of (the most common) Eclipse keywords is used (TransGen generates an error message for unrecognised keywords)   Inactive cells are used in fault seal potential/permeability calculations and therefore property data must be entered for all cells TransGen uses the offset of cell corners to estimate displacement.  It can find the faults from the positions of offset cells, and a FAULTS file is not required, but cell-centred geometries cannot be used.  TransGen assumes the slip vector is oriented parallel to the COORD lines.  There are various methods to inactivate regions of the reservoir model in Eclipse so that grid-blocks take no part in the Eclipse simulation.  TransGen similarly calculates and displays the properties of connections in the active regions of the model.  However, as material may be incorporated into faults in the 'active' regions from the inactive regions outside, TransGen still relies on the cell geometry and shale content (or Net-to-Gross) of cells which may have been inactivated.   Although they take no part in the simulation, they cannot be ignored.  In order to calculate fault seal potential (i.e. SGR and/or CSP in "Basic project" mode),  property data have to be supplied for inactive cells, and mis-shapen cells outside the active region could result in an incorrect computation.  In this way, TransGen is more demanding of the geometrical integrity and property data of the model than Eclipse. HINT:- See the Technical Description for a detailed description of what TransGen does. Eclipse files can be written by cellurisation packages in an order which departs from the Eclipse standard.  Eclipse essentially reduces a reservoir model to a matrix of transmissibilities,  so mirroring of the data does not result in incorrect results.  It does matter for visualisation purposes however, when it is difficult to check the geology of a mirrored model.  TransGen will accept input data in any row-ordered format.  The data can be read into and visualised in the ViewGen module and if the model is incorrectly oriented, selecting an alternative input layout in the WizGen module will allow the model to be re-visualised correctly.  Buckled, concave or 'inside-out' cells have an incorrect ordering. The ViewGen module of TransGen identifies such geometrical defects and treats all incorrectly ordered cells as defective and inactivates them.  FileGen The FileGen module within TransGen is an Eclipse file pre-processor.  It has been written to simplify Eclipse files and sort out the input data needed by TransGen by simply removing keywords TransGen does not use (or recognise).  In the best cases, when the structure of the Eclipse input files is straightforward, this could be done manually, but can still be done more reliably using the FileGen module. However, Eclipse is very flexible in the way input files can be constructed.  Input data can be read in and then overwritten or modified later, by the same or different keywords, resulting in what is essentially a 3D worksheet.  This may be done in an attempt to obtain a better simulation result, but the result of many changes over time can be a very complicated and obscure Eclipse run file.  In the worst case, sections of data may be made totally redundant, different parameters may be made interdependent through COPY keywords and modified by a chain of other keywords whose order is critical.  These changes can be made over several files, which themselves may be too large to edit, making manual editing very difficult. In these cases, the FileGen module is essential to enable straightforward preparation of the TransGen input files.    However there is no substitute for understanding how the the Eclipse run file has been constructed and why modifications were made, but FileGen will simplify the task.  What FileGen does is:- read one (or several) Eclipse input files, following all the links by INCLUDE keywords to other secondary files  and compile a single temporary file containing all the data. It then searches through this temporary file and finds all the locations of the Eclipse keywords that TransGen recognises.  Multiple occurrences of keywords and modifications to keywords will be identified in their order of occurrence.  Keywords which modify or copy data arrays are also identified.  The list and number of keywords provides an outline of the structure of the input data. Each of the types of data identified by keywords can be written to a separate files (or combined if required).  The data includes relevant BOX statements, which define the spatial range of the keyword.   FileGen extracts all the data that TransGen requires from the Eclipse input data.  All that remains to complete the TransGen instruction file is to add or modify TransGen specific keywords to control the TransGen run.  This is done interactively, step-by-step, in the WizGen wizard. Minimum data requirements ESSENTIAL ECLIPSE DATA In order to load and view a model, the data associated with the following keywords are required:- DIMENS (or SPECGRID)                        - to define the number of columns, rows, and layers COORD                                                      - to define the map position of the cell corners ZCORN                                                       - to define the depth of the cell corners UNITS (LAB or FIELD or METRIC)        - to define the units END                                                             - to end the file Additionally, in order to view cell and fault properties and generate transmissibility multipliers, the data associated with the following Eclipse keywords are required:- PERMX and PERMY                                  - to define cell permeabilities (The  PERMX data can be replicated in the PERMY array using the COPY keyword) NTG or TGVS or both                                 - to define the effective Vshale content of the cells MULTX and MULTY                                   - X and Y direction cell transmissibility multipliers optionally used in transmissibility expressions ECLIPSE KEYWORDS WHICH MODIFY DATA ARRAYS It these are present in the original run file, they should also be included in the TransGen run file to ensure that TransGen uses the same data as that used by Eclipse. ADD                                                            COPY EQUALS MULTIPLY Data arrays may be reset (wholly or in part) by reading the same keyword a second time. e.g. PERMX may reset the array initially set by a previous PERMX keyword.  ECLIPSE KEYWORDS WHICH CONTROL WHICH CELLS ARE ACTIVE It these are present in the original run file, they should also be included in the TransGen run file to ensure that TransGen identifies the same cell/cell connections as Eclipse. ACTNUM MINPV MINPVV PORO OPTIONAL KEYWORDS for visualisation purposes PERMZ FAULTS TGWELL            (New TransGen keyword) TGSTRLNE        (New TransGen keyword) ECLIPSE DEFAULTS Eclipse assumes: A cell with a zero porosity is inactive A cell with a net pore volume of less than 1.0E-06 is inactive (unless redefined by the MINPV keyword) A cell with zero permeabilities (in X,Y and Z) is inactive. A cell with zero NTG is inactive A faulted connection has no fault zone property associated and is fully open, i.e. its transmissibility is the unfaulted transmissibility.   The TransGen instruction runfile [UP] [TOP] [HOME]");sQ1[3]=new Array("TGmanual/5.html","Reference Manual","","[UP] [TOP] [HOME] TRANSGEN Reference Manual Welcome to the TransGen on-line reference manual.  This reference manual consists of a number of sections containing a detailed description of the TransGen software.  The manual is ordered according to a typical workflow. In the following sections: <MB1> refers to mouse button 1 (left) <MB2> refers to mouse button 2 (middle) <MB3> refers to mouse button 3 (right) <Project> refers to the basename of the TransGen project runfile (<Project>.TGDATA file) To return back to the WorkFlow Advisor, click on the Home link. NOTE:- TransGen version 3 is not compatible with TransGen version 2 and TGDATA files prepared for version 2 may not run in version 3. This section describes the type of data that TransGen requires Overview of data requirements This section describes the functionality new to the TranGen 3.2 release. TransGen version 3.2 This section will show you how to start TransGen. Starting TransGen This section will show you how to access the online help system at any time during a TransGen session. Accessing the Workflow Advisor The first step in the TransGen workflow is selecting or creating a project to work on. Project Selection It is possible to Pause, Resume, Terminate or Kill any of the TransGen Processes. Managing TransGen tasks Once a project has been created/selected, FileGen can optionally be used to make the Eclipse data input files more manageable for the user. Preparing Eclipse input data WizGen is the application which builds the runfile determining what will be calculated and how for the current input data. Using WizGen to create a TransGen runfile The input model can then be checked, the outputs calculated, and the results viewed in ViewGen. Viewing the model and calculating output The 2PhaseGen application (if licensed & selected on the Title page of WizGen in Flexible project mode) creates fault pseudo-relative permeability and capillary pressure tables for a TransGen model from the groupings of variables determined by ViewGen. Using the 2PhaseGen module Xphoto can be launched from the Control Menu to save images from ViewGen Saving images Keywords (from Eclipse and TransGen) in the TransGen runfile, supply the instructions and data to the calculation and graphics module ViewGen Keywords [UP] [TOP] [HOME]");sQ1[4]=new Array("TGmanual/70.html","The TransGen instruction runfile","","[UP] [TOP] [HOME] TransGen Instruction file (<Project>.TGDATA file) Data defining the input model and instructions for calculating the output data in TransGen are supplied to the calculation and graphics module ViewGen in a text file (<Project>.TGDATA) created via the WizGen module using Eclipse format Keywords.  HINT:- The WizGen interactive wizard provides an easy and reliable method for creating and editing the TGDATA file. Do NOT be tempted to edit the TGDATA run file manually. Unlike Eclipse, the TransGen instruction file is not split into sections.  Large datasets will automatically use the INCLUDE keyword to merge input from several files into one dataset, whilst retaining an instruction file of manageable size.TransGen uses a small subset of all the available Eclipse keywords and defines several new keywords used to enter information specific to the calculations performed by TransGen.  All new TransGen Keywords start with TG. Keywords and their associated data can be input in any order, with the following exceptions (DIMENS, COORD, ZCORN, END). It is essential to specify the units that are used in the model (using one of the following keywords: METRIC, FIELD, LAB ). TransGen will generate an error message if the program encounters an unrecognised keyword. Example <Project>.TGDATA file An example of the <project_name>.TGDATA runfile as generated using WizGen in "Basic project" mode (see Using WizGen to create a TransGen runfile for further details) is shown below. The keywords are highlighted in blue. These are predominantly Eclipse keywords allowing the import and export of data from/to the parent flow simulation model.  Some keywords, i.e. those prefixed by TG such as TGVS, TGFSP etc, are TransGen specific and are used solely to define data or processes within TransGen. Click on any of them to follow link to details on the format of data associated with that keyword. --<TITLE+> --Project Type: LIGHT TITLE FAULT 64_Basic - TransGen test model from PUNQ --<TITLE-> --<COORDINATE+> DIMENS --NX  NY NZ 2 10 20 / METRIC TGAXES 1 0 / --<COORDINATE-> --<INCLUDES+> --co-ordinate line data INCLUDE 'fault64_input/COORD.data' / --corner-point depths INCLUDE 'fault64_input/ZCORN.data' / --permeability in X direction INCLUDE 'fault64_input/PERMX.data' / --permeability in Y direction INCLUDE 'fault64_input/PERMY.data' / --net to gross property INCLUDE 'fault64_input/NTG.SECT' / --<INCLUDES-> --vshale content INCLUDE 'fault64_input/TGVS.data' / --<OPTIONS+> --lower limits TGMETRIC TGMINTR 1.0e-06 / TGVOLERR 1.0e-06 / MINPV 1.0e-06 / TGDISC 1 / --<OPTIONS-> --<LIGHT+> TGFSP --calculation of fault seal potential measures 'csp' 0 2 -1 0 1 '8-13,26-29,34,38,45-47' 1 1 1 '' 1 / 'sgr' -1 1 0 1 4 '' 1 6 1 '' 1 / / --automatically generated plugins to calculate fault rock thickness and fault permeability TGPLUGIN 'THICK=fault64_input/.plugins/_AUTO_THICK_PLUGIN.cpp' 'PERM=fault64_input/.plugins/_AUTO_PERM_PLUGIN.cpp' / --<LIGHT-> --<OUTPUTS+> --specify outputs TGRPT 'EDITNNC=fault64_output/editnnc.out' 'TRANX=fault64_output/tranx.out' 'TRANY=fault64_output/trany.out' 'GRAPHICS' / --OUTPUTS-> END [UP] [TOP] [HOME]");sQ1[5]=new Array("TGmanual/71.html","Example Instruction file 1","","[UP] [NEXT] [TOP] [HOME] [TOC] SIMPLE.TGDATA TITLE simple DIMENS --NX  NY NZ 2 1 4 / COORD ----x1 y1 z1  x2 y2 z2 0.00    0.00    0.00    0.00     0.00    500.00 100.00  0.00   0.00 100.00 0.00   500.00 200.00  0.00  0.00  200.00    0.00    500.00 0.00    100.00  0.00  0.00  100.00    500.00 100.00  100.00    0.00    100.00  100.00    500.00 200.00  100.00    0.00    200.00  100.00    500.00 / ZCORN ---top 1 0  0  10  10 0 0 10 10 ---base 1 20 20 30 30 20 20 30 30 20 20 30 30 20 20 30 30 ---base 2 40 40 50 50 40 40 50 50 40 40 50 50 40 40 50 50 ---base 3 60 60 70 70 60 60 70 70 60 60 70 70 60 60 70 70 --base 4 80 80 90 90 80 80 90 90 / permx 10 20 30 40 50 60 70 80 / COPY 'permx'  'permy' / / PORO 8*.2 / NTG .2 .3 .4 .8 .8 .9 .7 .8 / TGVS .1 .2 .2 .12 .3 .2 0 .1 / --EQUATION CONSTANTS TGKSE 0.4 4. 0.25 1. 5. 1. / --DISPLACEMENT TO THICKNESS TGTDE 0.005882 1. / --UNITS UNITS 'metric' / --REPORTING DETAILS TGRPT 'TRANX=simple_output/tranx.out' 'TRANY=simple_output/trany.out' 'FAULTS=simple_output/faults.out' 'EDITNNC=simple_output/editnnc.out' 'GRAPHICS'  / END [UP] [NEXT] [TOP] [HOME] [TOC]");sQ1[6]=new Array("TGmanual/72.html","Example TGDATA file","","[UP] [TOP] [HOME] The TransGen instruction runfile An example of the <project_name>.TGDATA runfile as generated using WizGen in "Basic project" mode (see Using WizGen to create a TransGen runfile for further details). The keywords (predominately Eclipse keywords) are shown in blue. Click on any of them to follow link to details on the format of data associated with that keyword. --<TITLE+> --Project Type: LIGHT TITLE FAULT 64_Basic - TransGen test model from PUNQ --<TITLE-> --<COORDINATE+> DIMENS --NX  NY NZ 2 10 20 / METRIC TGAXES 1 0 / --<COORDINATE-> --<INCLUDES+> --co-ordinate line data INCLUDE 'fault64_input/COORD.data' / --corner-point depths INCLUDE 'fault64_input/ZCORN.data' / --permeability in X direction INCLUDE 'fault64_input/PERMX.data' / --permeability in Y direction INCLUDE 'fault64_input/PERMY.data' / --net to gross property INCLUDE 'fault64_input/NTG.SECT' / --<INCLUDES-> --vshale content INCLUDE 'fault64_input/TGVS.data' / --<OPTIONS+> --lower limits TGMETRIC TGMINTR 1.0e-06 / TGVOLERR 1.0e-06 / MINPV 1.0e-06 / TGDISC 1 / --<OPTIONS-> --<LIGHT+> TGFSP --calculation of fault seal potential measures 'csp' 0 2 -1 0 1 '8-13,26-29,34,38,45-47' 1 1 1 '' 1 / 'sgr' -1 1 0 1 4 '' 1 6 1 '' 1 / / --automatically generated plugins to calculate fault rock thickness and fault permeability TGPLUGIN 'THICK=fault64_input/.plugins/_AUTO_THICK_PLUGIN.cpp' 'PERM=fault64_input/.plugins/_AUTO_PERM_PLUGIN.cpp' / --<LIGHT-> --<OUTPUTS+> --specify outputs TGRPT 'EDITNNC=fault64_output/editnnc.out' 'TRANX=fault64_output/tranx.out' 'TRANY=fault64_output/trany.out' 'GRAPHICS' / --OUTPUTS-> END [UP] [TOP] [HOME]");sQ1[7]=new Array("TGmanual/toc.html","Table of Contents","","TGmanual TGmanual Reference Manual Overview of data requirements The TransGen instruction runfile TransGen version 3.2 Traces and Fault Zones Starting TransGen Accessing the Workflow Advisor Project Selection Managing TransGen tasks Preparing Eclipse input data Using WizGen to create a TransGen runfile Using WizGen in Basic Project mode Title page Coordinate system page Included Data page Including Transmissibility Multipliers from Eclipse Miscellaneous Options page Fault Rock Properties page Plugins generated by WizGen in Basic project mode Output - simulator input page Project (TGDATA) File Session Log Contents page Using WizGen in Flexible Project mode Title page Coordinate System page User-defined keywords page Example of calculating user-defined cell properties in the CELLPROP plugin Included Data page Including Transmissibility Multipliers from Eclipse Miscellaneous Options page Fault Seal Potential Variables page FSP calculation in TransGen Version 3 Issues associated with FSP calculations Typical Fault Seal Potential Variable settings User-defined plugins page Defining Two-phase flow plugins DRAG plugin FZONE plugin Using Plugins in TransGen Prefix and Property options for plugins C++ language use in plugins C++ functionality in DRAG & FZONE plugins Output - simulator input page Output - derived and user-defined properties page Changes to Connection property output in 3.2 release Drag applied to fault traces page Hierarchical fault zone definition page Ramp geometry Stochastic ramp placement Two phase flow - INPUT page Using the Two phase flow functionality Two phase flow - FAULT ROCK PROPERTIES page Two phase flow - GROUPINGS & OUTPUT page Project (TGDATA) File Session Log Contents page Viewing the model and calculating output Including Drag/Hierarchical Fault Zones Two-Phase ViewGen calculations File menu in ViewGen Edit menu in ViewGen Show cells toggles cell display on/off Show faults toggles fault display on/off Show coords toggles display of COORD lines on/off Show traces toggles display of faulted traces on/off Show x-section toggles cross-section display on/off Show wells toggles well display on/off Show streamlines Show VOI toggles bounding box on/off Show arrow toggles reference arrow on/off Cell controls Examples Examples Examples Examples Cell colours Fault controls Examples Fault colours Coord controls Dynamic controls Properties display X-Section details Well details Sub-resolution display Cell Properties menu in ViewGen Fault Properties menu in ViewGen Displaying two-phase fault rock properties Help menu in ViewGen Using the 2PhaseGen module Saving images Keywords Keyword Description");sQ1[8]=new Array("TGmanual/9.html","Project Selection","","[UP] [TOP] [HOME] PROJECT SELECTION The first step in using TransGen is to create/select a Project on which to work. This is done via the Project Information window accessed by clicking on the Folder icon in the TransGen Control Menu. The TransGen Project Information window. The Project Infomation window allows creation/selection of a TransGen project runfile (<project>.TGDATA file).  In addition, it allows the user to manage the TransGen component processes (see Managing TransGen tasks).  If you are opening a new TransGen project, click on Create a new project... to open the Create a new project window as shown below.  Browse through the directories in the Directories box to an appropriate directory (e.g. Fault64) and append the new TransGen project name (e.g. F64_light) to the directory path in the Enter new project name window, as shown below. HINT:- Earlier versions of TransGen required the Project filename (both the basename and .TGDATA extension) to be input at this point in uppercase.  In TransGen3.0, the restriction on the project name has been relaxed to allow lower case letters and/or numbers, but must start with a letter and the uppercase .TGDATA run file extension is now automatically added to the Project name when it is accepted by clicking on either the Apply or OK button in the Project Information window.  Click on OK to update the Project Information window with the new TransGen Project Name and Project Directory as shown below. NOTE:- The Project Name and Project Directory are only editable via the Create a new project or Open an existing project options. Click on Apply to confirm project details and move the window to a convenient position on the screen so that the component TransGen tasks can be managed (see Managing TransGen tasks) or click on OK to dismiss the window. Having clicked on the Apply option for a newly created TransGen project, the following pop-up window will be displayed. Click on OK to close the pop-up window and return to the Project Information window. Optionally toggle the Allow access to FileGen option "on" to enable FileGen if you need to filter the Eclipse input files. Then click on OK to quit the Project Information window. The newly created Project name will be displayed on the title bar of the Control Menu (as shown below) and the run file (<Project_name>.TGDATA) plus two new directories (<Project_name>_INPUT  & <Project_name>_OUTPUT) will be automatically added to the Project Directory. Optionally, if you have toggled the Allow access to FileGen option "on", click on the FileGen icon and refer to the section on Preparing Eclipse input data to filter very large Eclipse input files into a number of smaller files based on essential keywords and create an initial project file to be used by WizGen. Otherwise, click on the WizGen icon and refer to the section on Using WizGen to create a TransGen runfile. To open a previously created project, click on the Open an existing project... button in the Project Information window (as shown below). Browse through the Directories to the directory containing the relevant *.TGDATA run file and either double click on the *.TGDATA filename or single click on it and then on OK to update the Project Information window (as shown below). NOTE:- The project file selected MUST be a previously created *.TGDATA run file, i.e. it must have a name of the form "<project_name>.TGDATA" with the TGDATA suffix in uppercase. An Error message window will be displayed if an incorrectly named file is selected. Click on either the OK or Apply button in the Project Information window to open this project. HINT:- Click on Apply and refer to the section on Managing TransGen tasks to use any of the other options in the Project Information window. Once a project has been selected, the active project name will be displayed in the title bar of the TransGen Control Menu. Click on the WizGen icon and refer to the section on Using WizGen to create a TransGen runfile to edit the existing run file or to create a new run file in "Flexible project" mode. [UP] [TOP] [HOME]");sQ1[9]=new Array("TGmanual/10.html","Preparing Eclipse input data","","[UP] [TOP] [HOME] Optionally, using FileGen to prepare Eclipse input data Once a project has been selected (see Project Selection), the active project will be displayed in the title bar of the TransGen Control Menu. For a new TransGen Project, the input Eclipse format data required from the reservoir simulation model might need to be restructured using FileGen.  This optional application is designed to make the data files more manageable for the user. It filters data contained in very large Eclipse input files into a number of smaller files based on essential keywords and also creates an initial project file which is then used by WizGen. The FileGen icon on the Control Menu will only be functional if the Allow access to FileGen option is toggled "on" in the Project Information window. Click on the third icon in the Control Menu to launch FileGen. FileGen will search through one or several Eclipse data files (following INCLUDE statements) to locate the data TransGen requires and places the data in *.DATA files in the TransGen Project directory or in a subdirectory which it creates with the name <Project name>_INPUT.  HINT:- See Essential Eclipse Data in the section on TransGen data requirements for a list of Eclipse keywords that TransGen recognises and needs. The first stage is to open the Eclipse files - click on the Open button to display the Choose input files window as shown below. Click on Add to open the Choose file name window and navigate to the relevant directory containing the Eclipse files to be used as input. Select a file and click on the Apply button to add that Eclipse file to the Choose input files window. Repeat until all the required files have been added; then press OK to add the last one and dismiss the Choose file name window. Any files that have been added in error can be removed from the input file list by selecting them and pressing Remove. When the list of Eclipse files is complete, press OK to close the Choose input files window.  Then click on the Merge at the top of the main FileGen menu to follow the links via INCLUDE keywords to secondary files, and create a single temporary input file in the /tmp subdirectory. The next stage is to find the data associated with each Eclipse keyword and either place it in the <Project>.TGDATA file, or in an associated include file.  The latter is best for the large data blocks.  By default, COORD, ZCORN, ACTNUM, NTG,  PERMX, PERMY, PORO, MULTX, MULTY, VSH, SWAT and FAULTS data are placed as secondary files by FileGen in the <Project>._INPUT subdirectory, with INCLUDE statements in the <Project>.TGDATA file.  To change the location where FileGen places the data associated with a particular keyword, click the Browse... button for the particular keyword. This launches a file selection box.  It might, for example, be useful to place the poroperm data in a separate subdirectories if there are several realisations. FileGen is designed to allow you to structure the data in a tidy and efficient manner.  NOTE:- FileGen makes the directories NEW_INPUT and NEW_OUTPUT by default,  but you may have made others in addition outside FileGen.  (If a directory does not exist, this is not a problem - FileGen will prompt with a red warning message to ask you to make the directory when it tries to write the files). First select the directory in which to wish to place the data, e.g. F64_POROPERM. Add the new filename for the data (e.g. PERMX.DATA) and click on OK. Repeat to place PERMY and PORO data in appropriately named files in the same new F64_POROPERM subdirectory. Once the location for the input data has been defined, click on Search, and FileGen will search for the data.  If the Eclipse source files are very large, this may take some time. FileGen works down the list of keywords,  indicating its progress in the 'State' column:  Data that has been found will be identified by a tick Data that is absent will be marked by a cross, and the filename will be greyed out when it has finished searching.  Data that FileGen is actively looking for is shown by an eye symbol and lastly; data that FileGen still has to search for are shown by a question mark. NOTE:- The way data is read in from an Eclipse run file is not always straightforward. Data may be missing because a necessary file was omitted from the list of input files or the data was input in another way.  EQUALS blocks can be used to set the value of any input array,  and COPY may be used to transfer the contents of one array into another.   ADD and MULTIPLY may also be used to modify the values. Multiple occurences of Keywords (shown by the Number field) should be investigated. It is possible that an Eclipse input file was read twice on its own or through an include statement.  In this case, the redundant data should be omitted. Alternatively, the data for the Eclipse parameter arrays may be defined in several places.  For example, the PERMX data may initially have been set to a certain value and modified by one or more subsequent PERMX block each perhaps with an associated BOX keyword.    In this case, the order in which the PERMX blocks are read could be very important. When the data search is complete, the data can be written to the TransGen input files by clicking on the Write button (as shown below).  As files are successfully written, the State marker will change as shown below.  Note what data has been successfully written (HINT:- See Essential Eclipse Data in the section on TransGen data requirements for a list of Eclipse keywords that TransGen recognises and needs) and click on Quit to exit FileGen. Once the relevant TransGen input files have been created, use the WizGen module to create a model runfile.  [UP] [TOP] [HOME]");sQ1[10]=new Array("TGmanual/11.html","Using WizGen to create a TransGen runfile","","[UP] [TOP] [HOME] Using WizGen to create a TransGen runfile WizGen allows the user to create a runfile (<Project>.TGDATA) which will control the calculations made by TransGen via ViewGen. Press the fourth icon in the Control Menu to launch WizGen. This launches the Title page of  WizGen .  New to the TransGen 3.0 release, at this point the user must choose if TransGen is to operate in "Basic project" or "Flexible project" mode. The choice of mode governs which pages are loaded into the program and hence what the user sees in WizGen and the range of choices available. Basic project operating mode The "Basic project" operating mode is intended for new or inexperienced TransGen users who only require access to a small set of prescribed methods for the calculation of fault-rock seal potential, thickness and permeability and hence faulted transmissibility. Using WizGen on a Basic project automatically creates the TGFSP strings and thickness and permeability plugins (i.e. essential THICK and PERM macros written in C++ accessed via the TGPLUGIN keyword) required in all TransGen runs. Using TransGen in Basic project mode will still provide a geologically meaningful model in most circumstances. Flexible project operating mode The "Flexible project" operating mode offers the more advanced user the opportunity to completely define the number and form of the Fault Seal Potential measures calculated. Plugins may be based on suggested examples or can be written and tested by the user within WizGen. The user may define new data variables, so that user data can be read into and/or manipulated in TransGen and used within plugins. FSP measures and user-defined variables can be output as connection or cell properties. Two additional plugins can be used in "Flexible project" mode:- the "CELLPROP" plugin is run (if present) at the very beginning of the calculations allowing the user to calculate the contents of new cell properties. the "AREA" plugin is run (if present) immediately prior to calculation of transmissibility. Include fault drag and hierarchical zone effects Having selected the Flexible project operating mode, you can choose to toggle this separately licensed option "on" to include the effects of sub-resolution geometrical fault characteristics in the flow simulator such as:- the effects of user-defined faults not included explicitly in the geometry of the simulation model. the uncertainty in fault throw or of local geological drag on faults included explicitly in the simulation model. inclusion of fault relay zones and other forms of locally-paired slip surfaces on faults included in the input model as single surfaces. NOTE:- This geometrical functionality (new to the TransGen 3.2 release) operates only on single-phase properties. Although TransGen can be run combining both this and the two-phase fault rock functionality, it will be internally contradictory. Combining the two sets of functionality is therefore NOT recommended. Include two-phase fault rock calculations Having selected the Flexible project operating mode, you can choose to toggle this separately licensed option "on" to use different relative permeability, across-fault flow rates and fluid property data for oil and water. For a brand new TransGen project, the WizGen Title page will appear as shown above, with the controls (apart from Quit) inoperative (greyed-out) and neither the Basic project nor Flexible project mode selected. For an existing TransGen Project, the WizGen Title page will appear as shown below with the operating mode in which the TransGen Project was previously run automatically selected and the controls activated, e.g. F64_basic.TGDATA in Basic Project mode. An existing Basic project can either be re-run in "basic" mode with the same/different WizGen settings or upgraded to "Flexible project" mode by selecting the Flexible project option to allow greater flexibility in the number and form of Fault Seal Potential measures calculated and also with the options to either Include fault drag and hierarchical zone effects in the single-phase simulation model or Include two-phase fault rock calculations to take into account two phase flow changes in water and oil saturations in the transmissibility multiplier calculations. NOTE:- A Basic project can be converted to a Flexible project, but not vice-versa. However, when a project is converted from basic to flexible, a copy of the "basic" TGDATA file is made and stored in a file called <Project_Name>.TGDATA.bak in the project directory, so the basic project can be restored if necessary. The appearance and options presented in WizGen will depend on the operating mode selected. Select either Basic project (recommended for new/inexperienced/basic TransGen users) or Flexible project (for advanced users) and click on the relevant section below to use WizGen to create a TransGen run file (i.e. <project_name>.TGDATA) giving instructions to be used in ViewGen to calculate output. Using WizGen in Basic Project mode Using WizGen in Flexible Project mode [UP] [TOP] [HOME]");sQ1[11]=new Array("TGmanual/12.html","Viewing the model and calculating output","","[UP] [TOP] [HOME] VIEWING THE MODEL AND CALCULATING OUTPUT Starting ViewGen Once a run instruction file (<project_name>.TGDATA) has been created and saved using WizGen, the model can be run by selecting the ViewGen icon on the TransGen Control Menu (as shown below). This performs the calculations, generates output files and launches the ViewGen graphics viewer. The progress of the ViewGen run can be monitored in the xterm from which the user started the TransGen session and the Log generated by the current run together with any generated error messages can be viewed in the Session Log window accessed via WizGen. HINT:- ViewGen can be run initially without calculating fault properties (i.e. with the Do not calculate fault properties option toggled "on" via the Miscellaneous Options page of WizGen) to check the input model has been imported correctly. If there are problems, return to the Coordinate System page of WizGen to check the layout of the input data has been specified correctly. If the Include fault drag and hierarchical zone effects option has been toggled "on" in WizGen ("Flexible Project" mode) with appropriate Drag applied to fault traces and Hierarchical fault zone definition settings, ViewGen will check the input data, identify the system traces, process user-defined traces, place fault zones and make a coherent geometrical model before calculating model properties, generating the output files and opening the main ViewGen graphics window. See section below for further details:- Including Drag/Hierarchical Fault Zones If the Include two-phase fault rock calculations option has been toggled "on" in WizGen ("Flexible Project" mode) with the appropriate single-phase and two-phase settings, ViewGen will check the input data, define the cell groups and output the KRNUM tables necessary to run the 2PhaseGen application before calculating the model properties, generating the output files and opening the ViewGen graphics window. See section below for further details:- Two-Phase ViewGen calculations On completion of a successful ViewGen run with the current TGDATA file settings and provided the Enable 3D graphics viewer after calculation has completed option is toggled "on" (default setting) via the Output page of WizGen, the ViewGen graphics window (shown below) will be displayed. HINT:- The progress of the ViewGen run can be monitored in the Xterm window from which the current TransGen session was started. The ViewGen graphics window allows the user to view the input simulator model and the new fault-related properties that have been calculated. Initially the model volume outline will be displayed in map view, scaled to the window, with the origin indicated by an arrow, but with no cells or faults displayed until selected. To display the model data in the ViewGen graphics window, toggle "on" the required elements via the Show options in the Edit menu. In the example shown below the cells and faults in the current project are displayed enclosed in the volume of interest box with an arrow adjacent to the origin of the model (row1, column 1) pointing downwards.  The model has been moved in the window using the following mouse actions:- <MB1> to rotate the model. Click and drag to rotate the model about its centre. Drag to left or right to rotate the model about the screen's vertical axis, drag up or down to rotate about the screen's horizontal axis. <MB2> to zoom into/out from the model. Click and drag down to zoom in. Click and drag upwards to zoom out. <MB3> to pan the model. Click and drag the mouse to move the model in the desired direction. NOTE:- New to the TransGen 3.1 release, there is a Messages text bar under the main 3D viewer window. This can be used to access information on the properties of a cell, fault connection or fault trace selected in the 3D viewer window, i.e. place the cursor over a cell, fault connection or trace currently displayed in the viewer window and click the left mouse button (<MB1>) whilst holding down the Control (Ctrl) key to send information on that object to the Messages text window. For a selected cell, the information displayed will be the cell's position (column, row, layer) and the value of the active cell property (as shown below). For a selected fault connection, the information displayed will be the positions of the two connected cells and the value of the active fault property. For a selected fault trace, the information displayed will be the trace definition and the throw. HINT:- Fault traces are 2D objects, new to the TransGen version 3.2 release - see section on Traces and Fault zones. While fault traces will automatically be displayed when the Show traces option is toggled "on" in the Edit menu, they are only strictly relevant when including fault drag and hierarchical zone effects in the run file (see using WizGen in Flexible project mode). NOTE:- New to the TransGen version 3.2 release, more detailed information about each of these object types can be displayed in the new Properties window accessed via the Properties Display option on the ViewGen Edit menu. See also the additional graphics functionality for fault traces are available via the ViewGen Edit menu, i.e. Show traces and Sub-resolution display options. The ViewGen viewer window main menu bar contains five submenus: File                           - to close the application Edit                          - to select which features of the model will be displayed (cells, faults, coord lines, traces, wells,  x-section, volume of interest (VOI) box, origin arrow),  volume and value filters to select subsets of the data, colourbars to determine how the data will be displayed, and other viewer controls. Cell Properties     - to choose which cell property will be 'active' and displayed in the viewer. Fault Properties   - to choose which fault property will be 'active' and displayed in the viewer. Help                         -to display details of the TransGen version and launch the on-line Workflow Advisor. These are detailed in the following sections:- File menu in ViewGen Edit menu in ViewGen Cell Properties menu in ViewGen Fault Properties menu in ViewGen Help menu in ViewGen [UP] [TOP] [HOME]");sQ1[12]=new Array("TGmanual/13.html","Saving images","","[UP] [TOP] [HOME] USING XPHOTO Whenever you want to save all or part of your current TransGen ViewGen (or 2PhaseGen) Viewer window display to a graphics file, click on the Xphoto icon in the TransGen Control Menu. The first time you access Xphoto in the current session, you will be prompted to select the screen on which to display it.  Click on the screen and the Xphoto window will appear: The options in the Xphoto window allow you to create a PNG, JPEG or Binary RGB format file from all or part the current window display to a specified output file. HINT:- To view the details of all the Xphoto features, click on the Help button to open a Netscape window and wait until the xphoto.html file is loaded.  Xphoto (hardcopy) options Capture type Click on the default option, i.e. Window and select from Region, Window or Whole screen to define the area to be captured to a hardcopy file. Pre-selection delay (secs) Default setting 0 secs. This optional setting can be used to set a pre-selection delay, i.e. select and drag the slider control to set an appropriate time interval between selecting the Capture option and selecting the area to be captured. Post-selection delay (secs) Default setting 0 secs. This optional setting can be used to set a post-selection delay, i.e. select and drag the slider control to set an appropriate time interval after you have captured an area but before the hardcopy file is created, to give you time to display a pop-down menu for example. Output format Click on the default output option, i.e. PNG and select from PNG, JPEG or Binary RGB formats. If JPEG format is selected there is an option to increase/decrease the JPEG quality using a slider control. Output file To define the destination and name of the hardcopy output file. Either type in the full path and an appropriate output file name or click on the `...' button to open a chooseFileShell window to navigate to the required directory and then type in the appropriate output file name. An appropriate path and output file MUST be defined before you can capture an image. Other options An optional extra allowing for potential future enhancements and other miscellaneous options. At present, the following options are available and will be applied if the relevant arguments are typed in the Other options box:-   -e <err-file>   Any run-time errors and verbose mode diagnostics will be written to <err-file>. If this option is not specified the output is written to standard error. If this option is not specified and -verbose option is used the -nograb option is enabled automatically (to avoid server hangup).   -noblend     Ignore transparent overlay windows. These are included and blended by default. -qlength <m>    Max. size in bytes of the XColor array that can be used with the XQueryColors function. (default = X-max-request-size*4). This argument need not normally be supplied but some servers are a little non-standard!   -verbose    Output verbose diagnostics to the Project Messages Window.   -nograb   By default Xphoto will grab the X-server while an image is being captured. Use this option to disable the server grab. This option is enabled automatically if any output is being written to stderr or stdout. Hide window during capture Default setting "off". Click "on" to hide the Xphoto window while capturing an image. Control buttons To Capture the area for hardcopy, Preview the result and Exit from the Xphoto window and/or to view information on the Xphoto features in a Netscape window via the Help button.  Capture To capture the relevant region, window or whole screen using the current Xphoto settings. Preview To preview the created hardcopy file. Exit To close the Xphoto window. Help To open a Netscape session displaying details of the Xphoto features as shown below. [UP] [TOP] [HOME]");sQ1[13]=new Array("TGmanual/17.html","Starting TransGen","","[UP] [TOP] [HOME] STARTING TRANSGEN TransGen Control Menu The Control Menu is the module launcher for TransGen To access the Control Menu and the TransGen Introduction window, type '/<TG_HOME>/bin/transgen` at an Xterm prompt (where <TG_HOME> is the installation directory of TransGen). The TransGen Control Menu is active throughout a TransGen session and should be displayed at some convenient location on your screen. When the Control Menu is first accessed, only the Workflow Advisor, Project Selection, Xphoto and Exit options are active, as shown above. The FileGen, WizGen, ViewGen and 2PhaseGen modules are inaccessible until a TransGen Project on which to work has been created/selected. Also initially displayed is the Introduction pop-up window (shown below) summarises what the TransGen program does and the function of the modules within TransGen. Click on OK to close the window. (Optionally set the Do not display again option "on" before closing the window to prevent the display of this Information window when opening TransGen in future.) Create a new or select an existing TransGen Project via the Project selection icon to activate all the icons on the Control Menu (as shown below with the project PUNQ_DYNAMIC selected). The Control Menu is the means of access into all the TransGen modules via selectable icons including:- Workflow Advisor - to access the on-line Help documentation. Project selection - to create/select the active TransGen project and manage the TransGen tasks. FileGen - optionally to select and structure the input data relevant  to the active TransGen project from one or more Eclipse data files. NOTE:- The FileGen icon is "greyed-out" and inoperable in the TransGen 3.2 release unless the "Allow access to FileGen" option is toggled "on" in the Project Information window when creating a new or opening an existing TransGen project - see Project Selection. WizGen - to interactively create (or modify) the settings in the TGDATA run file which control the TransGen run. ViewGen - to calculate fault transmissibility information for inclusion in the Eclipse reservoir simulation model and optionally to display the model geometry, inputs and outputs in the 3D viewer. 2PhaseGen - to calculate relative permeabilities for oil and water and hence the fault transmissibility information. Xphoto - to provide Hardcopy output in PNG, JPEG or RGB format from a TransGen session. Exit - to quit the current TransGen session and close down all active modules. For a newly created TransGen project, the main modules should be used in the order in which they are arranged on the Control Menu, i.e. Project selection to create/open the TransGen project, FileGen to pre-process the input Eclipse format files, WizGen to create the TransGen run file, ViewGen to view the input model, calculate the effect of the fault-rocks properties and generate output data as specified in the run file and then optionally 2PhaseGen if using TransGen including two-phase fault rock calculations. [UP] [TOP] [HOME]");sQ1[14]=new Array("TGmanual/16.html","Accessing the Workflow Advisor","","[UP] [TOP] [HOME] Accessing the Workflow Advisor Click on the WorkFlow Advisor icon in the TransGen Control Menu to launch the on-line help system at any point in a TransGen session. The Workflow Advisor includes an Overview of TransGen, a Technical Description of what the program does, a Reference Manual on using TransGen, Keywords, Frequently Asked Questions, Search Documentation, the means to Contact Badleys for support and Project Conversion information from TransGen 2.0 to 3.0. [UP] [TOP] [HOME]");sQ1[15]=new Array("TGmanual/78.html"," ","","[UP] [TOP] [HOME] [TOC] ITEM SELECTION FROM THE EDIT SUBMENU Show cells toggles cell display on/off Show faults toggles fault display on/off Show coords toggles display of COORD lines on/off Show x-section toggles cross-section display on/off Show wells toggles well display on/off Show VOI toggles bounding box on/off Show arrow toggles reference arrow on/off [UP] [TOP] [HOME] [TOC]");sQ1[16]=new Array("TGmanual/79.html","Show cells toggles cell display on/off","","[UP] [NEXT] [TOP] [HOME] Show cells Click on the Show cells option in the Edit menu to toggle the display of cells "on" or "off". When toggled "on" a green indicator is visible and the cells are displayed in the viewer window (as shown below). NOTE:- The active property displayed in the cells is set via the Cell Properties menu, which and how the cells are displayed is determined by the Cell Controls settings and the colour display is determined by the Colourmap Editor settings for Cell colours. [UP] [NEXT] [TOP] [HOME]");sQ1[17]=new Array("TGmanual/18.html","Managing TransGen tasks","","[UP] [TOP] [HOME] MANAGING TRANSGEN TASKS TransGen processes may be paused and restarted or stopped via the Project Information window.  This is opened by clicking on the second icon in the TransGen control menu. The currently active processes have names which are shown in black (WizGen and ViewGen in the current example).  Lengthy processes may be paused by clicking on the Pause button.  They may be restarted by pressing clicking on the Resume button. Processes which may have been supplied with incorrect input data can be stopped via the Terminate button (which sends a SIGTERM signal).  This ends the process in a controlled manner and should close open files.  Should a process fail to respond, it can be killed with the KILL button (which sends a SIGKILL signal). [UP] [TOP] [HOME]");sQ1[18]=new Array("TGmanual/80.html","Show faults toggles fault display on/off","","[PREV] [UP] [NEXT] [TOP] [HOME] Show Faults Click on the Show faults option in the Edit menu to toggle the display of faults "on" or "off". When toggled "on" a green indicator is visible and the faults are displayed in the viewer window (as shown below). NOTE:- The active property displayed on the faults is set via the Fault Properties menu, which and how the faults are displayed is determined by the Fault Controls settings and the colour display is determined by the Colourmap Editor settings for Fault colours. [PREV] [UP] [NEXT] [TOP] [HOME]");sQ1[19]=new Array("TGmanual/81.html","Show coords toggles display of COORD lines on/off","","[PREV] [UP] [NEXT] [TOP] [HOME] Show Coords Click on the Show coords option in the Edit menu to toggle the display of coordinates "on" or "off". When toggled "on" a green indicator is visible and the coordinates are displayed in the viewer window (as shown below). NOTE:- Which coordinates and how they are displayed are determined by the Coord Controls settings. [PREV] [UP] [NEXT] [TOP] [HOME]");sQ1[20]=new Array("TGmanual/82.html","Show x-section toggles cross-section display on/off","","[PREV] [UP] [NEXT] [TOP] [HOME] Show x-section Click on the Show x-section option in the Edit menu to toggle the display of cross-section(s) "on" or "off". When toggled "on" a green indicator is visible and the cross-section loaded as a data file associated the TGXSECT keyword (via Included Data page of WizGen), is displayed as shown below. NOTE:-  How the x-section is displayed is determined by the X-section details and with the Fill x-section option toggled "on" (default setting), the cell property displayed on the x-section is determined by the current Cell Properties setting with the colours set via the Colourmap Editor for Cell colours. [PREV] [UP] [NEXT] [TOP] [HOME]");sQ1[21]=new Array("TGmanual/83.html","Show wells toggles well display on/off","","[PREV] [UP] [NEXT] [TOP] [HOME] Show wells Click on the Show wells option in the Edit menu to toggle the display of wells "on" or "off". When toggled "on" a green indicator is visible and the wells, loaded as a data file associated with the TGWELL keyword (via Included Data page of WizGen), are displayed as shown below. NOTE:-  How the wells are displayed depends on the current Well details settings; the default display is to show the wells by Approximate bores. In the display shown below the well names have also been displayed - well1 is a producer well (bore displayed as a dotted line) and well2 is an injector well (bore displayed as a solid line). [PREV] [UP] [NEXT] [TOP] [HOME]");sQ1[22]=new Array("TGmanual/84.html","Show VOI toggles bounding box on/off","","[PREV] [UP] [NEXT] [TOP] [HOME] Show VOI Clicking on the Show VOI option in the Edit menu toggles on/off the display of the "Volume of Interest" bounding box.  A green indicator is visible in the Edit menu when the option is toggled "on" and the box is displayed in the ViewGen graphics window as shown below. [PREV] [UP] [NEXT] [TOP] [HOME]");sQ1[23]=new Array("TGmanual/19.html","Modifying the title","","[UP] [TOP] [HOME] [TOC] SETTING THE PROJECT TITLE To change the name, click in the white window where you wish to add or delete new characters from the name. If a title is given it is incorporated into any output files requested using the keyword TGRPT. To continue the workflow: press Next (Click it to see how to define the coordinate system. ) Pressing Back or Contents returns to  the main WizGen menu. [UP] [TOP] [HOME] [TOC]");sQ1[24]=new Array("TGmanual/20.html","Modifying the coordinate system","","[UP] [TOP] [HOME] [TOC] SELECTING THE CORRECT COORDINATE SYSTEM TransGen uses the Eclipse standard ordering by default.  The ordering of data in the Eclipse standard and RMS output is always in row order.  In the Eclipse standard,  the origin of the model (Row 1, Column 1) is at the top left of the model.  Rows increase downwards, and the XY coordinates which define the position of the COORD lines are given relative to the model origin, with Y increasing downwards. However, in other models the position of the origin, and the direction in which rows and columns increase may differ.  (RMS for example, provides many options tto output the data in different ways.)  Also the co-ordinates that defined the positions of the COORD lines may be given as a local coordinate system relative to the model origin (as per Eclipse), or relative to a geographic origin with Y increasing upwards (The RMS default). The appropriate system must be selected:  if  incorrect,  the model will either be mirrored, or the cells will be inactivated as they have a negative volume. A diagram in map view, showing the nature of the Coordinate system is shown for each of the the options. The position of the origin is shown by a blue diamond Rows are shown by bold red arrows, row numbers increasing with the length of the arrow Columns are shown thinner arrows, column numbers increasing with the length of the arrow The directions in which the X and Y coordinates increase are shown by black lines.  These coordinates are used to define the position of the COORD lines. System 3 RMS and real world coordinates (Y increasing upwards) is a common form of RMS output. This section specifies the parameters for the TGAXES keyword. To continue the workflow: press Next (Click it to see how to choose additional include files.)  Pressing Back allows the user to revise the project title.  Pressing Contents returns the user to the main menu. [UP] [TOP] [HOME] [TOC]");sQ1[25]=new Array("TGmanual/21.html","Adding include files","","[UP] [TOP] [HOME] [TOC] ADDING INCLUDE FILES The data blocks that FileGen created should be included in the TransGen project file (<project>.TGDATA).  Additional data may be included at this stage. To add additional data (that was not included by FileGen), press Browse, which launches a file-selection window Select the directory by double clicking (.. moves up a level), select the file and press OK.  When all the files have been added press the Next button. To follow the workflow: press Next (Click  to see how to  set the Output options for TransGen.) Pressing Back allows the user to return to the previous window and revise the coordinate system. Pressing Contents returns to the main WizGen menu. [UP] [TOP] [HOME] [TOC]");sQ1[26]=new Array("TGmanual/22.html","Modifying the output options","","[UP] [TOP] [HOME] [TOC] CHOOSING THE OUTPUT OPTIONS The main results that the ViewGen module of TransGen generates are the graphical window and output files specified by the TGRPT keyword. a graphics display, this is optional as ViewGen can be run as a batch process from the command line. Eclipse format Transmissibility multipliers: TRANX and TRANY files for neighbour connections and an EDITNNC file for non-neighbour connections.  These output files are shown in the upper box in the window. The graphical output may be toggled on or off.  A green box and a tick is shown when graphical output is enabled: This toggle pops-out and greys-out, when graphical output is deselected: In the lower box, other output files generated by the TGXRPT keyword can be specified: An Eclipse format FAULTS file (TransGen will find the faults if none were supplied) Transmissibility multipliers for each cell-cell connection Area of connection for each cell-cell connection Unfaulted transmissibilities for each cell-cell connection Shale Gouge Ratio for each cell-cell connection Fault permeabilityfor each cell-cell connection Fault thickness for each cell-cell connection Fault throw for each cell-cell connection Output files are generated when a file name is present.  EDITNNC, TRANX, and TRANY files are generated by default and the results placed in the ./'Project'_OUTPUT subdirectory.  Clearing any of the white editable filename boxes (by double clicking on them and pressing delete) will suppress file output.   File output can be activated by filling in the file names, either by typing the full pathname/filename in any of the white boxes, or pressing one of the Browse Buttons to launch a file selection box.  Directories can be selected by double-clicking with <MB1> in the Directories box ( the directory ending with two dots means go up a level).  Existing files can be selected by double-clicking with <MB1> in the Files box.  A new file can be created by appending a new filename to the existing (or reselected path in the Selection box).  Press OK to proceed, or Cancel to drop the changes.  This will return control to the main output option selection window. To continue the workflow: press Next (Click to show how to control howTransGen calculates fault properties) Pressing Back allow the user to  revise which include files are used. Clicking Contents returns the user to the main FileGen window. [UP] [TOP] [HOME] [TOC]");sQ1[27]=new Array("TGmanual/23.html","Modifying the calculation options","","[UP] [TOP] [HOME] [TOC] CHOOSING THE CALCULATION OPTIONS TransGen can use different methods for calculating the effective shale content of the fault wall rocks, and the method by which the shale gouge ratio is calculated.  Limits can be set on the transmissibility multipliers that are output, as well as the minimum cell volume. Evshale computation method The manner in which the effective vshale (shale content) computation is performed is controlled by the right hand box.  It may be calculated in one of the 3 following methods: Use NTG only - TransGen considers the non-net region to be shale and takes the shale content to equal 1 minus the Net-to-Gross value (where Net-to-Gross is the ratio of the net thickness of good reservoir, i.e. sand to gross interval thickness). Use Vshale only - TransGen takes Vshale as the shale content. Use NGT and VShale - TransGen assumes the non-net region to be pure shale, and takes the shale content to be: The one used is selected by an appropriate radio button, and is dependant on the availability of Net-to-Gross (NTG) and  vshale (TGVS) data.  This defines the parameters for the TGEVS keyword. SGR averaging method The method that TransGen uses to compute the shale gouge ratio of the fault rock is controlled by the left hand box.  The shale gouge ratio is the distance-weighted average of the shale content of the rocks that have moved past a point on a fault.  For each faulted cell, TransGen calculates the SGR from the effective vshale content of the cells that have moved past it along the direction of the COORD lines. The SGR may be different for upthrown and downthrown sides of the fault. Select which values TransGen uses from the following:- Use footwall only Use hangingwall only Use average of both The one used is selected by the appropriate radio button and defines parameters for the TGSGRM keyword. Ignore limits Calculation limits are set in the lower box. Multiplier cutoff - Transmissibility multipliers less than this cutoff value will be ignored  This defines the TGMINTR keyword. Eclipse has no equivalent to this keyword, and it is recommended that the cutoff value should not be increased unless in very special circumstances. Cell Volume cutoff - The cell volume cutoff is used by TransGen as a precision limit for rejecting badly constructed cells.  It is different from the Eclipse limit of minimum cell pore volumes (Eclipse MINPV keyword),  which TransGen also recognises.  A grid-block is flagged as inactive by TransGen if any component tetrahedra have a volume of less than minus this value or if the total cell volume is less than this volume. As porosities cannot be greater than 1.0, it is pointless setting MINPV (the cell pore volume) to less than this value.  In the absence of PORO data, TransGen sets the porosities to 1.0, and in the absence of a MINPV keyword, MINPV is defaults to 1.0e-06 as in the Eclipse. Values which depart from the default values should be typed into the appropriate white data entry boxes. This toggle is popped-out and greyed-out by default: to indicate that ViewGen will normally calculate fault properties: It may be preferable for ViewGen not to perform the calculation, for reasons such as rapidly viewing the geometry of the model.  In this case the toggle button should be depressed.  It will then be shown in green, with a tick: This selects the TGNOCALC keyword. Press Next  to choose to the parameter values for key TransGen relationships or press Back to revise which outputs are generated. To continue the workflow: press Next (Click to show how to control how to change the values of key parameters) Pressing Back allow the user to  revise the output options. Clicking Contents returns the user to the main FileGen window. [UP] [TOP] [HOME] [TOC]");sQ1[28]=new Array("TGmanual/24.html","Modifying the TransGen relationships","","[UP] [TOP] [HOME] [TOC] DEFINING KEY TRANSGEN RELATIONSHIPS The parameters that define the key relationships between: Fault displacement and fault-zone thickness SGR and fault rock permeability Depth dependency can all be altered in the following window. By default, the parameterised relationships relating fault displacement to fault-zone thickness and SGR to fault zone permeability suggested by Manzocchi et al. (1999) are supplied.  By default, no depth dependency is included in the fault-zone permeability. To accept these defaults, just click the next button. To choose a relationship that differs from the defaults, click on the appropriate toggle button and enter the appropriate values.  More details are given in the following sections. Modifying the displacement / thickness relationship Modifying the SGR / permeability relationship Adding depth-dependency to fault-permeability To follow the workflow press Next button (Click here) Press the Back button to revise the calculation options. Pressing the Contents button returns to the main WizGen window. [UP] [TOP] [HOME] [TOC]");sQ1[29]=new Array("TGmanual/25.html","Viewing and editing  the TGDATA file directly","","[PREV] [UP] [TOP] [HOME] [TOC] VIEWING AND EDITING THE TRANSGEN RUN FILE This launches the WizGen project file editor. [PREV] [UP] [TOP] [HOME] [TOC]");sQ1[30]=new Array("TGmanual/26.html","Inspecting the ViewGen run log","","[UP] [TOP] [HOME] [TOC] INSPECTING THE VIEWGEN RUN LOG Pressing the final 'Goto' button from the WizGen main window launches the ViewGen log viewer.  This project report is in the <Project>.TGPRT file.  Each step in the TransGen run is given a new number.  Warning messages are prefixed by an exclamation mark  Use the scroll bar on the right of the window to browse up and down the file. The other controls: The five blue control buttons at the bottom of the window are the same as the WizGen project file editor, and have the following effects: The Back button returns to the WizGen project file editor The Next button is inactive The Contents button returns the user to the main WizGen window The Save button is inactive. The Quit button exits WizGen without saving the <Project>.TGDATA file [UP] [TOP] [HOME] [TOC]");sQ1[31]=new Array("TGmanual/85.html","Show arrow toggles reference arrow on/off","","[PREV] [UP] [TOP] [HOME] Show arrow Clicking on Show arrow option in the Edit menu toggles on/off the display of a reference arrow just outside the "Volume of Interest" bounding box.  The arrow is drawn adjacent to the origin of the model, (row1, column 1) and points downwards.  The arrow is displayed in the ViewGen window shown below together with the VOI box. [PREV] [UP] [TOP] [HOME]");sQ1[32]=new Array("TGmanual/27.html","Modifying the displacement / thickness relationship","","[UP] [NEXT] [TOP] [HOME] [TOC] MODIFYING THE DISPLACEMENT / THICKNESS RELATIONSHIP The fault displacement /  fault-zone thickness relationship can be supplied either: as a parameterised equation or in the form of a table of paired displacement thickness values Changing the equation parameters Using the Displacement to Thickness equation Clicking on the Displacement to Thickness button: shows the form of the equation at the top of the window.  The parameters a and b may be altered in the two white data entry boxes.  This defines the TGTDE keyword. Using a Displacement vs Thickness table Clicking on the Displacement vs Thickness button: allows any user-defined function to be described by pairs of displacement / thickness data.  Pairs o f values should be entered into the white data entry boxes.TransGen uses linear interpolation between these values using the TGTDT keyword.  Leave blank if not required. Pressing Save will save the relationship to the <Project>.TGDATA file. When all the relationships have been correctly modified, press Next to continue... [UP] [NEXT] [TOP] [HOME] [TOC]");sQ1[33]=new Array("TGmanual/28.html","Modifying the SGR / permeability relationship","","[PREV] [UP] [NEXT] [TOP] [HOME] [TOC] MODIFYING THE SGR / FAULT-ROCK PERMEABILITY RELATIONSHIP The SGR / fault-rock permeabiliity relationship can be supplied either: as a parameterised equation or in the form of a table of paired displacement thickness values Changing the equation parameters: Clicking on the SGR to Permeability button: shows the form of the equation at the top of the window.  The parameters a, b, c, d, and e (as well as the limit f) may be altered in the five white data entry boxes. Using a SGR / Permeability table: Clicking on the SGR vs Permeability button: allows any user defined function to be described by pairs of SGR / Permeability data.  Pairs o f values should be entered into the white data entry boxes. TransGen uses linear interpolation between these values.  Leave blank if not required. Pressing Save will save the relationship to the <Project>.TGDATA file. When all the relationships have been correctly modified, press Next to continue... [PREV] [UP] [NEXT] [TOP] [HOME] [TOC]");sQ1[34]=new Array("TGmanual/29.html","Adding depth-dependency to fault-permeability","","[PREV] [UP] [TOP] [HOME] [TOC] ADDING DEPTH DEPENDENT FAULT-PERMEABILITIES The fault-rock permeabilities can be optionally modified by a depth dependent permeability multiplier.  This is added in the form of a table of paired displacement thickness values: Using a SGR / Permeability table: Clicking on the Depth vs Perm. multiplier button: allows any user defined function to be described by pairs of SGR / Permeability data.  Pairs o f values should be entered into the white data entry boxes. TransGen uses linear interpolation between these values. Pressing Save will save the relationship to the <Project>.TGDATA file. When all the relationships have been correctly modified, press Next to continue... [PREV] [UP] [TOP] [HOME] [TOC]");sQ1[35]=new Array("TGmanual/30.html","File menu in ViewGen","","[UP] [NEXT] [TOP] [HOME] File menu in ViewGen Click on File in the ViewGen menu bar to access the option to Close the viewer window. [UP] [NEXT] [TOP] [HOME]");sQ1[36]=new Array("TGmanual/31.html","Edit menu in ViewGen","","[PREV] [UP] [NEXT] [TOP] [HOME] Edit menu in ViewGen The settings in the Edit menu determine which and how the elements are displayed in the viewer window. Click on Edit on the ViewGen menu bar to display the Edit drop-down menu (click on the pale line below immediately below Edit to display it as a Tear-off menu as shown below). Either click on any option in the above menu to follow a link to the relevant section of the manual or work systematically through this section to see how to change the general viewer settings, determine which and how various elements of the model are displayed. General Viewer display control:- This is achieved via the View Controls window accessed by clicking on the View controls... option in the Edit menu. The vertical exaggeration can be controlled by the slider at the right of the control box or numerically by entering a number into the Vert Exag data entry box, and then clicking on either the Apply or OK button. In addition to moving the model using mouse actions, accurate and repeatable positioning can be achieved by inputting appropriate settings in the data entry boxes of the View Controls window and then pressing either the Apply or OK button. The background can be changed from the default black to white using the White background toggle button and then pressing the Apply or OK button. Toggle the Auto-rotate button "on" to spin the model about the model centre round an axis parallel to the screen vertical.  Toggling Auto-rotate "off" (default setting) stops auto-rotation. With the Lighting "on" the model is lit from the front. Toggling this option "off" will turn off this light source. The Reset view button puts the model display back to the default map projection. Close dismisses the window without applying any additional changes, OK applies any changes and dismisses the View Controls window. What elements are displayed:- The following Edit options toggle on or off the main elements of the display. Show cells toggles cell display on/off Show faults toggles fault display on/off Show coords toggles display of COORD lines on/off Show traces toggles display of faulted traces on/off Show x-section toggles cross-section display on/off Show wells toggles well display on/off Show streamlines Show VOI toggles bounding box on/off Show arrow toggles reference arrow on/off Controlling how cells are displayed: Cell controls Cell colours Controlling how faults are displayed: Fault controls Fault colours Controlling how Coord lines are displayed: Coord controls How to view dynamic data: Dynamic controls To display Properties of cells, fault connections or traces: Properties display Controlling how cross-sections are displayed: X-Section details Controlling how Wells are displayed: Well details To display fault zone details added to a fault trace: Sub-resolution display [PREV] [UP] [NEXT] [TOP] [HOME]");sQ1[37]=new Array("TGmanual/32.html","Cell Properties menu in ViewGen","","[PREV] [UP] [NEXT] [TOP] [HOME] Cell Properties menu in ViewGen Click on Cell Properties on the ViewGen menu bar to select the active cell property for display in the viewer window. Most of the cell properties will be those imported from the Eclipse reservoir model. The Cell Properties menu consists of a basic list of 18 items from which one at a time can be selected as the "active" property for display in the cells. Items for which there is no data will be greyed out.  The currently active property is indicated by a green index (as shown above for the 'PERMX' cell property). NOTE:- To display the currently selected Cell Property in the ViewGen window, the Show cells option must be toggled "on" in the Edit menu with appropriate Cell controls and Cell colours settings. PERMX These are the horizontal permeability data in the 'X' direction from the PERMX array of the Eclipse model. PERMY These are the horizontal permeability data in the 'Y' direction from the PERMY array of the Eclipse model. PERMZ These are the vertical permeability data from the PERMZ array of the Eclipse model. NTG  These are the Net to Gross data from the NTG array of the Eclipse model. TGVS These are the Vshale data input using the TGVS keyword. PORO These are the Porosity data from the PORO array of the Eclipse model. SATNUM These are indices for each grid-block in the model referencing the saturation function data as defined by the SWOF keyword (for further details see the SATNUM keyword). Data files associated with both the SATNUM and SWOF keywords must be included in the TGDATA run file to implement the two-phase flow functionality. MULTX These are the horizontal transmissibility multiplier data in the `X' direction from the MULTX array of the Eclipse model. MULTY These are the horizontal transmissibility multiplier data in the `Y' direction from the MULTY array of the Eclipse model. MULTZ These are the vertical transmissibility multiplier data from the MULTZ array of the Eclipse model. Zones Depth This is the depth of each cell calculated as the average depth of the cell corners from the ZCORN data Connections These are the number of connections each cell has to other cells across the faults.  (Cells away from faults have 0 connections.) Dynamic data This option is used to display dynamic data from Eclipse restart files as a movie (use the Edit, Dynamic controls... option to choose the restart set).  The data that can be displayed as a cell property are: PRESSURE (oil pressure) SWAT (water saturation) FLOWATI, FLOWATJ, FLOWATK (water flow rates in the i,j, and k directions) FLOOILI, FLOO ILJ, FLOWOILK (oil flow rates in the i,j and k directions) FLOGASI, FLOGASJ, FLOWGASK (gas flow rates in the i,j and k directions) The following cell properties can only be displayed when the Include two-phase fault rock calculations has been selected in WizGen (in Flexible project mode) and appropriate input, fault rock properties, groupings and output settings for Two phase flow have been saved prior to running ViewGen. KRnumX+ KRnumX- KRnumY+ or KRnumY- The indices associated with the following KRNUM directional keywords (created at the end of the ViewGen run using the divisions and priorities assigned via the Two phase flow - Groupings section in WizGen) can be displayed as cell properties. Each index defines the relative permeability and capillary pressure (SWOF) table assigned to a particular cell in that particular direction, i.e. with KRnumX+ selected, the SWOF table assigned for flow from cell [X Y Z] to cell [X+1 Y Z] will be displayed, while by selecting KRnumX- the SWOF table assigned for flow from cell [X Y Z] to cell [X-1 Y Z] will be displayed. The total number of tables will equal the number of original tables as defined by the SATNUM keyword plus the number of new tables created for faulted cells using the Two phase flow - Groupings settings in WizGen. Cell Pressure If cell pressure data have been loaded to calculate the across-fault flow rates in the Two-phase flow module (i.e. declared as a Cell Property on the User-defined keywords page and with the relevant file loaded via the Included data page of WizGen) the cell pressures can be displayed in ViewGen. Having used WizGen in Flexible project mode to create the TGDATA run file, there may be additional Cell Properties added as User-defined keywords with data imported via the Included Data page and/or calculated via the CELL plugin. For example:- Eff. vshale This is could be an effective vshale value calculated via a User-defined CELLPROP plugin for each grid-block from Net-to-Gross data already included in the model (see Example of calculating user-defined cell properties in the CELLPROP plugin for futher details) [PREV] [UP] [NEXT] [TOP] [HOME]");sQ1[38]=new Array("TGmanual/33.html","Fault Properties menu in ViewGen","","[PREV] [UP] [NEXT] [TOP] [HOME] Fault Properties menu in ViewGen Click on Fault Properties in the ViewGen menu bar to access the list of properties which can be selected for display on the faults. The Fault Properties menu consists of  a variable length list of items from which one at a time can be selected as the "active" property for display on the fault(s).  Properties for which no data have been calculated in the current TransGen run will be greyed out and unselectable. The currently active property is indicated by a green index, as shown above for Trans. multiplier. NOTE:- To display the currently selected Fault Property in the viewer window, the Show faults option must be toggled "on" in the Edit menu with appropriate Fault controls and Fault colours settings. Trans. multiplier Select this option to display the transmissibility multiplier values calculated by TransGen, i.e. the ratio of faulted and unfaulted transmissibilities at each point on the fault surface. For details on how these values are calculated when using WizGen in Basic project mode, see Transmissibility Multiplier calculation in the Technical Description of what TransGen does. HINT:- When using WizGen in Flexible project mode, these computed Transmissibility multiplier values can be selected for output to file via the TRMULT(C) option on the Output - derived and user-defined properties page. Faulted trans. This is the across-fault transmissibility calculated by TransGen per connection and displayed as either raw (average) or normalised per unit area (average/area).  It is the transmissibility across the fault when the effect of fault-zone material is included.  For consistency with ECLIPSE, transmissibility units are as follows:-   in metric units:    0.008527*milliDarcy-metres   in field units: 0.00127*milliDarcy-feet   in lab units:   3.6*milliDarcy-cm. In each case the numerical value is Darcy's constant (CDARCY) for that set of units. For details on how these values are calculated when using WizGen in Basic project mode, see Faulted Transmissibility calculations in the Technical Description of what TransGen does. HINT:- When using WizGen in Flexible project mode, these computed Faulted transmissibilities can be selected for output to file via the FTRANS (C) option on the Output - derived and user-defined properties page. Unfaulted trans. This is the across-fault transmissibility calculated by TransGen per connection and displayed as either raw (average) or normalised per unit area (average/area).  The unfaulted transmissibility values are those calculated across fault juxtapositions, BUT for which the effect of the fault-zone material is ignored (i.e. the input model). For details on how these values are calculated when using WizGen in Basic project mode, see Unfaulted Transmissibility calculations in the Technical Description of what TransGen does. HINT:- When using WizGen in Flexible project mode, these computed Unfaulted transmissibilities can be selected for output to file via the UFTRANS (C) option on the Output - derived and user-defined properties page. Permeability This is the fault rock permeability in milliDarcies, calculated in TransGen from the Fault Seal Potential measure(s) (i.e. SGR and/or CSP as set on the Fault Rock Properties page when using WizGen in Basic project mode or as defined in the PERM plugin of WizGen in Flexible project mode). The Permeability data can be displayed as a single averaged value for each connection (average) or with the values at each connection vertex interpolated across the connection (smoothed). For details on how these values are calculated when using WizGen in Basic project mode, see Fault Permeability Calculation in the Technical Description of what TransGen does. HINT:- When using WizGen in Flexible project mode, these computed Permeabilities can be selected for output to file via the PERM (C) option on the Output - derived and user-defined properties page. Displacement This is the fault slip, i.e. offset of cell corners from one side of the fault to the other measured in the direction of the COORD lines.  In TransGen, displacement is always calculated assuming the displacement vector of the fault is parallel to the COORD lines used to construct the 3D model geometry.  The units depend on the model units. It can be displayed as a single averaged value for each connection (average) or with the values at each connection vertex interpolated across the connection (smoothed). Thickness This is the thickness of the fault zone, calculated from the amount of displacement (for further details, refer to the section on Fault Thickness Calculation in the Technical Description of TransGen).  The units depend on the model units. It can be displayed as a single averaged value for each connection (average) or with the values at each connection vertex interpolated across the connection (smoothed). For details on how these values are calculated, see Fault Thickness Calculation in the Technical Description of what TransGen does. HINT:- When using WizGen in Flexible project mode, these computed fault-zone Thicknesses can be selected for output to file by setting the THICK (C) option on the Output - derived and user-defined properties page. Overlap area This is the area of overlap between any two juxtaposed cells.  This area is a polygon defined by the vertices at the top or bottom of the cells.  The units depend on the model units, e.g. square metres, square feet. Depth The depth of each connection calculated as the average depth of each connection vertex. Dynamic data Select this option to allow the display of Eclipse generated dynamic data from restart files as a fault property (See section on using the Dynamic Controls for details). The dynamic data that can be viewed as fault properties are: FLOWATN (water flow through the faulted connection) FLOOILN (oil flow through the faulted connection) FLOGASN (gas flow through the faulted connection) DARCY_VEL This user-defined connection property will appear as a displayable fault property if:- Include two-phase fault rock calculations has been selected on Title page of WizGen (in Flexible Project mode) DARCY_VEL has been declared as a connection property on the User-defined keywords page of WizGen The associated file defining the across-fault flow rates for Two-Phase flow calculations has been loaded via the Included Data page of WizGen HINT:- None of the internally-derived two-phase fault rock properties (e.g. capillary threshold pressure, porosity, connate water saturation, effective water saturation, etc.) can currently be visualised directly in ViewGen. However these properties can be viewed using a workaround using the single-phase plugins and user-defined cell properties (see section on Displaying two-phase fault rock properties in ViewGen below). Which other Fault connection parameters are available on Fault Properties menu will be determined by the settings in the current TGDATA run file. Fault Seal Potential measure(s) in a Basic project If fault properties are calculated using a TGDATA runfile created via WizGen in "Basic project" mode, either sgr (Shale Gouge Ratio) and/or csp (Clay Smear Potential) will be available for display on the faults (depending on the settings made on the Fault Rock Properties page of WizGen):- sgr This is the Shale Gouge Ratio, a prediction of the shale content of the fault zone (expressed as a proportion) assuming shale material is incorporated into the fault gouge in the same proportions as it occurs in the wall rocks of the slipped interval (for further details, refer to the section on Calculation of SGR in the Technical Description of TransGen). It can be displayed as a single averaged value for each connection (average) or with the values at each connection vertex interpolated across the connection (smoothed). csp This is the Clay Smear Potential, a measure of clay smear thickness incorporated into the fault zone based on shale source bed thickness and displacement distance (for further details, refer to the section on Calculation of CSP in the Technical Description of TransGen). It can be displayed as a single averaged value for each connection (average) or with the values at each connection vertex interpolated across the connection (smoothed). Fault Seal Potential measures/Connection properties in a Flexible project If fault properties are calculated using a TGDATA runfile created via WizGen in "Flexible project" mode, up to 5 different Fault Seal Potential measures as defined on the Fault Seal Potential Variables page of WizGen, and any user-defined Connection Properties imported into TransGen and/or calculated in a user-defined THICK or PERM plugin will be available for display on the faults. HINT:- When using WizGen in Flexible project mode, these computed values can be selected for output to file on the Output - derived and user-defined properties page. Displaying two-phase fault rock properties [PREV] [UP] [NEXT] [TOP] [HOME]");sQ1[39]=new Array("TGmanual/34.html","Help menu in ViewGen","","[PREV] [UP] [TOP] [HOME] THE HELP SUBMENU Click on Help on the ViewGen menu bar The Help submenu consists of two items: About... Docs... About... Opens the following dialog box: Click on OK or Close to dismiss it. Docs... Which launches this online documentation. [PREV] [UP] [TOP] [HOME]");sQ1[40]=new Array("TGmanual/35.html","Cell controls","","[UP] [NEXT] [TOP] [HOME] Cell Controls With Show cells toggled "on", click on the Cell controls... option in the ViewGen Edit menu to access the Cell Controls window. This is the principal dialog box which controls the display of cells. The Cell Columns/Rows/Layers list boxes, the Property filter box  and the Inactive only toggle control which cells are selected for display.  The Cell outline selection and the Fill cells toggle control how they are displayed. The operation of these items are described below: The active Cell property is selected by the Cell Properties menu. Cell colours are controlled by the Cell Colourmap editor. The Cells Columns/Rows/Layers list boxes The Cell Columns, Rows and Layers lists allow mouse-driven selection of which cells to display, by their position in the model.  By default, all the cells are selected (shown in the Column, Row and Layer lists by a black background).   Moving the scroll bar to the right of each list allows movement through the entire list. To change the set of cells that are displayed: Clicking on the All / None button selects/deselects the entire list Clicking with <MB1> on a single Row/Column/Layer selects a single item only from the each of the lists. Clicking with <MB1> on a single Row/Column/Layers, and then holding down shift and clicking on another Row/Column selects all Rows / Columns / Layers in that range. Holding down the Contrlol key and clicking with <MB1> selects /  deselects additional items from the lists. Then click on OK or Apply to update the displayed cells in ViewGen. Examples Property filter The cell Property filter selects the cells to display by value.  By default, the range is set to include all cells between the minimum and the maximum  value of the cells (i.e. all cells).  The range may be restricted to show only certain cells, and then the Inclusive toggle button becomes active.  By default it is set as inclusive, all cells within the range are displayed. If toggled off, the range is exclusive,  only cells outside the range will be displayed Clicking on the Reset button, resets the range to the minimum and maximum values of the data. To operate the filter: Type the minimum and maximum values into the white data entry boxes. Set the Inclusive toggle button if appropriate Then press OK or Apply. Examples Cell views box The three toggle buttons operate as follows: Fence type Fill cells toggles between filling the cells with colour (default) or showing them as an outline wireframe.  Inactive only toggles between showing the active cells (default) or those which have been inactivated. Select the mode, then press OK or Apply to update the displayed cells in ViewGen. Examples Cell Outline box Cell outlines are added in black to filled cells.  The outlines are not drawn when the model is drawn in wireframe mode (not filled). The four radio buttons operate as follows: Both outlines both the upper faces and side faces of cells.  Just tops outlines the upper faces of cells Just sides outlines the side faces of cells Neither switches off the black outline Select the mode, then press OK or Apply Examples [UP] [NEXT] [TOP] [HOME]");sQ1[41]=new Array("TGmanual/36.html","Fault controls","","[UP] [NEXT] [TOP] [HOME] Fault Controls With Show faults toggled "on", click on the Fault controls... option in the ViewGen Edit menu to access the Fault Controls window. This is the principal dialog box which controls the display of faults.  The Faults Columns/Rows/Layers list boxes,  the Imported Faults list box, the Property filter and the Always display ViewGen generated faults option settings, control which part of which faults will be displayed.  Apart from colours, the manner in which an active fault property is displayed is controlled by Fault Views box.  The operation of these are described below: The active fault property is selected by the Fault Properties menu. Fault colours are controlled by the Fault Colourmap editor. The Fault Columns/Rows/Layers list boxes These boxes allows a mouse-driven selection of faults that lie within selected regions of the model.  By default, the entire volume is selected (selected volumes are shown in the Fault cols, rows and layers lists by white text on a black background).   Only those fault faces indexed to cells lying in the selected region will be displayed.  Moving the scroll bar to the right of each list allows movement through the entire list. To change the set of cells that are displayed: All / None selects/deselects the entire list Clicking with <MB1> on a single Row/Column/Layer selects a single item only from each of the lists. Clicking with <MB1> on a single Row/Column/Layer, and then holding down shift and clicking on another Row/Column/Layer selects all Rows / Columns / Layers in that range. Holding down the Control key and clicking with <MB1> selects /  deselects additional items from the lists. Then press OK or Apply to update the display in the ViewGen window. The Imported faults list box This lists all the faults imported into TransGen from the Eclipse model (via the FAULTS keyword on the Included Data page in WizGen). Many fault faces may be associated with a single name by using the Eclipse FAULTS keyword in the input data. If Eclipse FAULTS data has not supplied or has not been included in the current TransGen project, this list will be empty. HINT:- Even if FAULTS data are not included, ViewGen will find the faults by the offset of cell corners and these will be displayed with the Always display ViewGen generated faults option toggled "on" (default setting). Toggle this option "off" to visualise individual user-defined faults rather than the automatically generated "background" faults. The Imported faults list allows mouse-driven selection of Eclipse faults by name.  By default, all the Imported faults are selected (shown by white text on a black background in the fault-name list).   Only those Imported faults that are selected will be displayed.  Moving the scroll bar to the right of each list allows movement through the entire list. To change the set of Imported faults that are displayed: All / None selects/deselects the entire list Clicking with <MB1> on a fault name selects a single item from the list Clicking with <MB1> on a single name, and then holding down shift and clicking on another name selects all names in that range. Holding down the Contrlol key and clicking with <MB1> selects /  deselects additional items from the list. Then press OK or Apply Property filter The Property filter selects where the active fault property will be displayed by value.  By default, the range is set to include the entire range of the fault property  (i.e. everywhere).  The range may be restricted to show values within a certain range, and then the Inclusive toggle button becomes active.  By default, the Inclusive option is toggled "on" - all values within the range are displayed. If toggled "off," the range becomes exclusive - only cells outside the range will be displayed. Pressing the Reset button, resets the range to the minimum and maximum values of the currently selected Fault Property data. To operate the filter: Type the lower and upper limits for the range into the white data entry boxes. Set the Inclusive toggle button if appropriate Then press OK or Apply Fault Views box Faulted cell faces can be displayed by a colour-fill controlled by the active cell and/or fault property. The currently selected Fault property can be displayed at Connections. However if the reservoir is completely offset, TransGen does not display fault properties for unconnected (or inactive) cells.  It is possible to display a cell property on the Upthrow or Downthrown side of the fault.  The cell edges can also be added The active fault property is selected by the Fault Properties menu. Fault colours are controlled by the Fault Colourmap editor. The active cell property is selected by the Cell Properties menu. Cell colours are controlled by the Cell Colourmap editor. The fault views box controls whether: The active Fault Property is displayed at faulted cell-cell Connections in the appropriate fault colours. (The region of juxtaposition) The active Cell property from the Upthrown side of the fault is displayed in the appropriate cell colours. The active Cell Property from the Downthrown side of the fault is displayed in the appropriate cell colours. The fault views box also controls whether: The Outline of faulted cell faces are drawn at faulted Connections.  These are drawn in black if a fault connection property is displayed or in white if no property is displayed. The outline of Upthrown cell faces are drawn  These are drawn in black if an upthrown cell property is displayed or in white if no property is displayed. The outline of Downthrown cell faces are drawn  These are drawn in black if an Downthrown cell property is displayed or in white if no property is displayed. To use the box, select the Property and/or Outline then press OK or Apply Always display ViewGen generated faults By default, this option is toggled "on" to display any faults not imported into TransGen from the Eclipse model, but generated by ViewGen by the offset of cell corners. Toggle it "off" to remove these ViewGen generated faults from the viewer window, then click on either OK or Apply to update the display in the ViewGen window. The Close button dismisses the Fault Controls window with no further changes being made. Examples [UP] [NEXT] [TOP] [HOME]");sQ1[42]=new Array("TGmanual/37.html","Coord controls","","[UP] [TOP] [HOME] Coord Controls Click on Coord Controls... option in the ViewGen Edit menu to access the Coord Controls window. The manner in which COORD lines are displayed is controlled by the Row/Column list boxes, the Line extent box, and the Line fill box.  This is of particular interest when resolving geometrical problems in the model: The Column/Row list boxes By default, the COORD lines on every column and every row are selected (shown in the Column and Row lists in black).   Moving the scroll bar to the right of each list allows movement through the entire list To change the set of lines which are displayed: All / None selects/deselects the entire list Clicking with <MB1> on a single column/row selects a single item from the list. Clicking with <MB1> on a single column/row, and then holding down shift and clicking on another column/row selects all columns/rows in that range. Holding down the Control key and clicking with <MB1> selects /  deselects additional items from the list. To use the lists, make the selection then press OK or Apply Line extent box The position and orientation of the COORD lines are defined by a pair of X,Y,Z coordinates.  If coincident, Eclipse assumes the COORD lines are vertical, otherwise they are extrapolated as necessary to the Z range of the data in the ZCORN section.  The two radio buttons in the Line extent box control the display of COORD lines as follows: Original displays lines between the two X,Y,Z coordinates as read in. ie, the data as it is read in. Trimmed displays lines to the full range of the Eclipse model i.e., how TransGen and Eclipse use the data One particular danger is that COORD lines may cross within the range of the model, but not within the range of the COORD data. To use the box, make the selection and press OK or Apply Line fill box The two radio buttons in the Line fill box control the display of COORD lines as follows: Solid draws the COORD lines as solid lines. Dashed draws the COORD lines as dashed lines. To use the box, make the selection and press OK or Apply. The Close button dismisses the window with no further changes being made. [UP] [TOP] [HOME]");sQ1[43]=new Array("TGmanual/38.html","Well details","","[UP] [TOP] [HOME] Well details Wells positions are shown in the viewer window for wells specified by the TGWELL keyword when the Show wells option in the Edit menu is toggled "on". The settings applied via the Well details option in the Edit menu determine how the wells are displayed. Click on Well details in the Edit menu to access three toggled on/off display options:- Show name Approximate bore  Mark cells The options that are active are shown by a green indicator to the left of the text. Approximate bore shows the wells by solid lines for producers and dashed lines for injectors. Mark cells shows the grid-blocks to which the wells are connected in white (producers) and grey (injectors). or both may be selected: With Show name toggled "on" the Well name is displayed at the top of the bore. [UP] [TOP] [HOME]");sQ1[44]=new Array("TGmanual/75.html","Examples","","[UP] [TOP] [HOME] COL/ROW/LAYER FILTER EXAMPLES By default all rows and columns are selected Here a set of rows are selected and displayed together with faults to give a set of serial sections.  Layer 9 has zero permeability and porosity and has been inactivated.  Inactive cells are not shown by the view, hence layer 9 is shown as a missing layer. By selecting the top and bottom layer faults can be viewed inside the model. [UP] [TOP] [HOME]");sQ1[45]=new Array("TGmanual/74.html","Examples","","[UP] [TOP] [HOME] CELL PROPERTY FILTER EXAMPLES By default the cell property filter is set to the range of the data.  Here Net-To-Gross data is visualised.  The filter can be set to only include high net regions.  This is useful for viewing channels, and checking juxtaposition relationships at faults.  The inclusive toggle is set, all values between 0.7 and 0 .961 are included and displayed. Alternatively, the filter can be set to be exclusive  With the Inclusive option toggled "off", all values between 0.7 and 0 .961 are excluded and only cells with values outside this range are displayed. [UP] [TOP] [HOME]");sQ1[46]=new Array("TGmanual/73.html","Examples","","[UP] [TOP] [HOME] CELL VIEWS EXAMPLES By default , the active cells are shown filled in colour. If the Fill cells toggle is deselected, the cells are shown in wireframe, but coloured by value. If the Inactive only toggle is selected, inactive cells will be displayed.  One layer consists of cells with zero permeabilities.  These are below the range of the colourbar and shown in grey.   Other cells to the right, in the downthrown region of the main fault, have been inactivated by an ACTNUM statement, but have values in the range of the colourbar. Inactive cells can also be shown in colour.  To view cells which have been inactivated by having a geometrical defect, do not inactive cells using an ACTNUM section or by setting poroperms to zero, and then toggle Inactive only button "on".  Those that have inactivated by having a bad geometry will remain.  [UP] [TOP] [HOME]");sQ1[47]=new Array("TGmanual/76.html","Examples","","[UP] [TOP] [HOME] CELL OUTLINE EXAMPLES By default, just the tops of cells are outlined. Both the tops and the sides can be outlined Cell outlines can be deselected Or cell outlines just shown for the sides of cells. This a good way of showing the fault pattern, particularly when a single layer is displayed. [UP] [TOP] [HOME]");sQ1[48]=new Array("TGmanual/39.html","Cell colours","","[PREV] [UP] [TOP] [HOME] Cell Colours Click on the Cell colours... option in the ViewGen Edit menu to access the Cell Colourmap Editor window. Fill colours for the reservoir cells can be set using the Colourmap Editor.  The basic layout and mode of operation of Colourmap Editor is the same whether it is  opened from 'Cell colours' or 'Fault colours'.  The title bar of the window gives the property (cell or fault) for which the colourmap is being edited, i.e. the property currently selected via the Cell Properties menu.  Each property has a default colourmap associated with it, which will appear on the first display of that property.  For most properties the default colourmap is a spectrum, but net-to-gross, Vshale and SGR have their own colourmaps. Adjusting the range for display: The range of values for display is set  in the Range boxes: The upper and lower values setting the range of the colourbar are set in the two white data entry boxes, but by default they are set to the maximum and minimum of the active cell (or fault) property.  To alter either value, double click on value to be changed and type in new value.  Pressing the Reset button sets the range back to that of the selected data. The Scaling option can be used to select either Linear or Logarithmic scaling for the colourbar, between the upper and lower values. The Number of labels posted on the colourbar is set by the number of labels slider bar. Out of range data is displayed by the colours of the separate bars at the top and bottom of the colourbar.   It is possible to add a different marker colour  to these parts to distinguish over-range and under-range data. (See below). To temporarily modify the Colourbar use the appropriate Marker Modes:- Add marker:- To add a marker of the current select colour at any point on the colourbar. Change marker:- With this mode selected, you can change the colour of a selected marker. Delete marker:- To remove any unwanted marker colours, set this mode 'on' then move cursor to colour bar and position over unwanted colour marker and click <MB1> to delete that colour and refresh the colourbar either by linear interpolation between the two adjacent colour markers or by block fill. Stretch:- To stretch a colour interval.  Toggle the Stretch mode 'on', place cursor over the appropriate colour marker in the colour bar, and use <MB1> with click, hold and drag action to stretch the colour interval.  Release mouse button to instigate change and reinterpolate between new stretched colour settings. Move marker:- To move a selected colour marker to a new position. To load an existing colourmap file:- 1. In the Colourmap Editor, click on the List button with 3 dots on it to the right of the File: box to open the File Selection menu. 2. Scroll through the list of colourmap resource files and click on one to select it. 3. With required file in Selection box, click on Load to close the File Selection menu and display the chosen colourmap file in the Colourbar of the Colourmap Editor. 4. If a file has been used with a particular property, it remains associated with it and will be used next time the property is selected. NOTE:- Colourmaps are stored on a per-user basis (not per-project), in a directory called .tg_cmaps in the user's home directory. To create a new colourmap file:- 1. Either select the Clear button below the Colourbar to clear it completely prior to creating a completely new colourmap or Load an existing colourmap file for modification as described previously. 2. Select source of colour input:- either palette of 64 basic colours or cube (where the number of selectable colours in an RGB cube are defined by the intensity) 3. Click on the required input colour in the palette or cube to select it.  If necessary, modify it by varying the Intensity. The colour will be displayed in the select box. 4. Choose appropriate Interpolation mode; None, Linear or block-Fill mode. 5. With the Add marker input mode selected (default setting), move the cursor to the required position on the Colourbar using the Pointer value (displayed below the Colour bar) to place the colour contour accurately.  Click <MB1> to place colour. 6. Select and add further colours, until the Colourbar is set satisfactorily. 7. Modify any of the markers in the Colourbar using the appropriate Marker Modes:-   Change marker:- With this mode selected, you can change the colour of a selected marker.   Delete marker:- To remove any unwanted marker colours, set this mode 'on' then move cursor to colour bar and position over unwanted colour marker and click <MB1> to delete that colour and refresh the colourbar either by linear interpolation between the two adjacent colour markers or by block fill.   Stretch:- To stretch a colour interval.  Toggle the Stretch mode 'on', place cursor over the appropriate colour marker in the colour bar, and use <MB1> with click, hold and drag action to stretch the colour interval.  Release mouse button to instigate change and reinterpolate between new stretched colour settings.   Move marker:- To move a selected colour marker to a new position. 8. Set the Range to define the minimum and maximum values between which the cells (or faults) are to be colour-contoured.  Click on Reset to set minimum and maximum values to those of the currently selected data. To alter either value, double click on value to be changed and type in new value. 9. Click, hold and drag the slider control to adjust the Number of Labels between 2 and 21.  This setting, in conjunction with the Range settings, determines the actual values labelled on the current colourbar. 10. Set the Scaling of the Colourbar labels to either Linear (default setting) or Logarithmic. (HINT: Logarithmic is useful for properties such as permeability.) 11. When complete, type in an appropriate File name and Save as a Colourmap resource file. NOTE:- Colourmaps are stored on a per-user basis (not per-project), in a directory called .tg_cmaps in the user's home directory. 12. Select Apply to apply the new Colourmap to the data in the Viewer window.  If satisfied click on Okay to apply settings. Alternatively, select Close to close the Colourmap Editor without applying any changes. [PREV] [UP] [TOP] [HOME]");sQ1[49]=new Array("TGmanual/40.html","Fault colours","","[PREV] [UP] [TOP] [HOME] Fault Colours Click on the Fault colours... option in the ViewGen Edit menu to access the Fault Colourmap Editor. Fill colours for the currently active Fault Property can be set using the Colourmap Editor.  The basic layout and mode of operation of Colourmap Editor is the same whether it is  opened from 'Cell colours' or 'Fault colours'.  The title bar of the window gives the property (cell or fault) for which the colourmap is being edited., i.e. the property currently selected via the Fault Properties menu  Each property has a default colourmap associated with it, which will appear on the first display of that property.  For most properties the default colourmap is a spectrum. How to adjust the range of the display How to temporarily modify the colourbar How to load an existing colourmap How to create a new colourmap [PREV] [UP] [TOP] [HOME]");sQ1[50]=new Array("TGmanual/41.html","Dynamic controls","","[UP] [TOP] [HOME] Dynamic Controls TransGen has the ability to view the results of the Eclipse simulation (using binary restart files) as movies:- to show changes in cell and/or fault properties, e.g. oil pressure, water saturation, across-fault fluid flow etc.  over time, i.e. over the time interval defined in by the Eclipse restart data. NOTE:- An *.EGRID file together with a set of restart files (*.Xnnnn) must have been output for the current Eclipse model as requested by the user during the Eclipse run in order to view the results via the Dynamic Controls option in the ViewGen window. To view dynamic cell or fault property data, first access the Dynamic Controls from the Edit menu. Initially no dynamic data are loaded  and the dynamic Fault and Cell properties will be greyed out as unavailable.  The first step is to locate and load the .EGRID file and associated restart files.  Click on the Load solution set... button. This opens the Choose restart set window. Double click to select the correct directory in the Directories box.  When the correct directory has been located, file(s) with the extension ".EGRID" will appear in the Files box.  Click on the required *.EGRID file (there is usually only one per Eclipse run). This automatically loads any relevant restart files (i.e. with the same root name). NOTE:- The restart files (*.Xnnnn) must be in the same directory as the *.EGRID file. Click once on the .EGRID file (e.g. TWO_PHASE_FAULTS.EGRID) and press OK.   The lists in the Dynamic Controls window will no longer be greyed out.  Click on an item in the Faults and/or Cells list to select a fault and/or cell property you want to display. By default all the available timesteps are selected. Hold down the Control key while clicking on any timesteps you do not want to include in the dynamic display. As some changes may occur over brief time ranges, it may be possible to restrict the timestep range considerably. Via the ViewGen, Edit menu, select the main components for display, such as cells and/or faults and/or wells. If necessary use the Cell Controls and/or Fault Controls to determine which and how the data are displayed. Orientate the model appropriately in the ViewGen window using the following Mouse button actions:- <MB1> to rotate the model. Click and drag to rotate the model about its centre. Drag to left or right to rotate the model about the screen's vertical axis, drag up or down to rotate about the screen's horizontal axis. <MB2> to zoom into/out from the model. Click and drag down to zoom in. Click and drag upwards to zoom out. <MB3> to pan the model. Click and drag the mouse to move the model in the desired direction. Initially the cells will be gray (values unset), until the first timestep is read when the movie is played.  To do this press the Play forwards button in the Dynamic controls window.  The movie can be paused at any point using the Pause button and resumed with either play button.  Stopping the movie and restarting it, will start the movie at the first time step. Only one set of restart files may be viewed at a time, but it is possible to show dynamic fault and cell data simultaneously.  The cell colours and cell filters work with dynamic data in the same way as static data, so it is possible to show subsets of cells and faults in different colours, etc. It is possible to toggle between the display of static cell and fault property data using the Cell properties and Fault properties menu. To show the dynamic data again, the Dynamic data option should be selected as the active property in the Cell Properties and/or Fault properties menus. [UP] [TOP] [HOME]");sQ1[51]=new Array("TGmanual/42.html","X-Section details","","[UP] [TOP] [HOME] X-section details The X-section options determine how a cross-section is displayed in the viewer window. NOTE:- Cross-sections should be loaded using the TGXSECT keyword and selected for display by toggling the Show x-section option "on". Clicking on X-Section details option in the ViewGen Edit menu accesses two options:- Toggle on and off the following:- Fill x-section - fills the cell faces along the section with the active cell property Outline x-section - draws the outline of the cells in black if filled, or white if unfilled. When active, a green indicator is shown to the left of the two items. [UP] [TOP] [HOME]");sQ1[52]=new Array("TGmanual/43.html","Keywords","","[UP] [TOP] [HOME] KEYWORDS These notes assume that a user of TransGen has some knowledge of using Keywords in Eclipse. In TransGen, instructions and data are supplied to the calculation and graphics module ViewGen in an instruction text file (<Project>.TGDATA) created via the WizGen module using Keywords. The Keywords used in the <Project>.TGDATA file include:- A small subset of the available Eclipse Keywords - to define the data from the Eclipse model to be used in a TransGen run. New Transgen Keywords - to enter information specific to the calculations performed by TransGen.  All TransGen-specific Keywords start with TG. Click here for details of the Eclipse data that TransGen requires Click here for details of the TransGen instruction file. NOTE:- It is recommended that you use the WizGen module to add all the relevant keywords to the instruction file (<Project>.TGDATA) in the correct order and that you do not attempt to edit the TGDATA manually. General rules for Keywords in the .TGDATA file Keyword Order TransGen requires the keyword order at the top of the file to be:- TITLE [optional] DIMENS (or SPECGRID) TGAXES [optional] COORD ZCORN The final keyword must be: END Format of Keywords A keyword is written on a new line in the instruction file and can be written in upper, lower or mixed case. Data required by the keyword immediately follows the keyword.  Comments are allowed between a keyword and any associated data.  Data The type and quantity of data required to follow a keyword is specific to the keyword itself and the current input state.  In general, data input for a keyword is terminated by a forward slash (/).  There must be a space between the data and the slash. TransGen ignores surplus white-space characters (e.g. new-line, space, tab) when reading keyword data.  Therefore, the two examples given below are equally valid:- example 1: DIMENS     10 20               30 / and example 2: DIMENS 10 20 30 / TransGen conforms to the Eclipse method of reading repeat numerical data using the '*' operator. Ten equal values of (for example) porosity can be written as: PORO 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 0.2 / or PORO 10*0.2 / Note that there should be no spaces on either side of the '*' operator. Character data should be enclosed in single quotes.  The exception to this rule is TITLE which reads character data unquoted and does not require a slash (/) to end the character input - in this case the input is restricted to the end of the line. The most common reason for an instruction file to be rejected by TransGen is the absence of a slash (/) at the end of a data record.  Another common error is the absence of an END statement at the end of the file. TransGen ignores 'flat' cells with coincident top and bottom surfaces, (ie, identical Z values at the corner positions).  Such planar 'cells'  have no volume, contain no fluid, cannot support any flow, and have no connections to other cells and are also ignored by Eclipse. At unconformities where footwall erosion has occurred, their position contributes no information with respect to the pre-erosion displacement field.  As they have no thickness they contribute no shale  to the SGR computation,.  In models with unconformities a large proportion of the model (80% is not unusual) may consist of such redundant cells.  Such cells are identified and flagged when the ZCORN data is loaded;  later when the property data is read, none  is stored.  This considerably improves memory usage and speed, but does necessitate the geometry to be loaded before property data.  A message reporting the number of 'flat' cells will be present in the log file. For any faulted active cell, TransGen determines the displacement by finding the position of an 'non-flat' cells in the same layer on the opposite side of the fault.  If an 'non-flat' cell in a corresponding layer does not exist, perhaps because of erosion at an unconformity, TransGen estimates the displacement as best it can, starting by seeking to find the displacement from a layer which exists on both sides of the fault lower down.  A message that displacement have been estimated rather than determined will appear in the log file. Keywords recognised by TransGen Click on any keyword listed below for details on the format necessary for recognition within TransGen. ACTNUM,  ADD,  BOX,  COORD,  COPY,  DIMENS,  EDITNNC,  END,  ENDBOX,  EQUALS,  FAULTS,  FIELD,  INCLUDE,  KRNUM,  LAB,  METRIC,  MINPV,  MINPVV, MULTIPLY,  MULTX,  MULTY,  MULTZ,  NNC,  NTG,  PERMX,  PERMY,  PERMZ,  PORO,  SATNUM,  SPECGRID,  SWOF,  TGAXES,  TGDRAG,  TGEVS,  TGFSP,  TGFZONE,  TGKDT,  TGKSE,  TGKST,  TGMETRIC,  TGMINTR,  TGNEWKEY,  TGNNC,  TGNOCALC,  TGPLUGIN,  TGREMNNC,  TGRPT,  TGSGRM,  TGSHALE,  TGSTRLNE,  TGTDE,  TGTDT,  TGTHROW,  TGTRACE,  TGVOLERR,  TGVS,  TGWELL,  TGXRPT,  TGXSECT,  TGXTRACE,  TITLE,  TRANX,   TRANY,  UNITS,  ZCORN  Keyword Description [UP] [TOP] [HOME]");sQ1[53]=new Array("TGmanual/44.html","Keyword Description","","[UP] [TOP] [HOME] Keyword Descriptions The list of keywords given below include:- Eclipse keywords used in the TransGen <Project>.TGDATA file (generated by the WizGen module) to determine what Eclipse data and how they are included in the TransGen calculations (via the ViewGen module) of permeability and transmissibility multipliers from the Fault Seal Potential measures (e.g. DIMENS, COORD, ZCORN, NTG, PERMX, PERMY). TransGen specific keywords to enter information specific to the calculations performed by TransGen (e.g. TGAXES, TGFSP, TGMETRIC, TGNEWKEY,TGPLUGIN , TGSHALE) All TransGen-specific Keywords start with TG. TransGen specific keywords to input/output fault trace properties when using the new fault drag and hierarchical zone effects functionality (i.e. TGTRACE, TGDRAG, TGTHROW, TGFZONE, TGXTRACE). Eclipse keywords used in the TransGen <Project>.TGDATA file (generated by the WizGen module) to determine what Eclipse format data is output from TransGen to include modifications to the transmissibilities in the parent simulator model (i.e. EDITNNC, TRANX, TRANY, NNC). The format necessary for inclusion of these keywords in a TransGen run is described below. NOTE:- It is recommended that you use the WizGen module to add all the relevant keywords to the instruction file (<Project>.TGDATA) in the correct order and that you do not attempt to edit the TGDATA manually. ACTNUM Active Grid Block Identification This is one of the Eclipse keywords which can be used in the Eclipse simulation model to control which cells are active/inactive (see also MINPV, MINPVV and PORO). If the ACTNUM keyword is included in the Eclipse model, it must also be included in the TransGen run file to ensure the same cells are active/inactive in both models. The ACTNUM keyword is followed by one integer for every grid block in the current box.  A value of 1 indicates that the corresponding grid block is active, whilst a 0 indicates that it is inactive.  The data must be terminated by a slash (/). Grid blocks are ordered with the X axis index cycling fastest, followed by the Y and Z axis indices.  Repeat counts may be used for repeated values (e.g. 12*0).  Note that spaces may not be inserted on either side of the asterisk. ADD Adds a constant to the specified array in current box This is one of the Eclipse keywords which can be used to modify data arrays in the Eclipse simulation model (see also COPY, EQUALS and MULTIPLY). If the ADD keyword is included in the Eclipse parent model, it should also be included in the TransGen run file to ensure data compatibility between the two models. The ADD keyword can be followed by any number of records, each of which is terminated by a slash (/).  The data is terminated by a null record (i.e. a record with no data before the terminating slash).  Each record consists of at least 2, and up to 8 items of data. Item 1  The name of the array to be modified (enclosed in quotes). Item 2  The constant to be added to the array specified by item 1.  The constant may be positive or negative, and may be real or integer. Items 3-8 may be used to redefine the input box for this and subsequent operations within the current keyword. If items 3-8 are not defined (a slash is inserted after item 2), they default to the values which were used for the previous operation within the current keyword.  For the first operation in the keyword, the box defaults to the values set by the most recent BOX or ENDBOX keyword.  If there is no preceding BOX or ENDBOX in the current section, the box is taken to include the entire reservoir. Item 3  IX1   First block to be modified on the X axis. Item 4  IX2   Last block to be modified on the X axis. Item 5  JY1   First block to be modified on the Y axis. Item 6  JY2   Last block to be modified on the Y axis. Item 7  KZ1   First block to be modified on the Z axis. Item 8  KZ2   Last block to be modified on the Z axis. The data must satisfy         1 <= IX1 <= IX2 <= NDIVIX         1 <= JY1 <= JY2 <= NDIVIY         1 <= KZ1 <= KZ2 <= NDIVIZ BOX Re-defines the current input box This Eclipse keyword when included in the parent simulator model should be followed by six integers which re-define the current input box.  Subsequent operations using COPY or MULTIPLY only alter grid blocks within the current input box.  Similarly, data read into an array (e.g. using PERMX or PORO) are assigned to the grid blocks in the current input box. N.B. BOX remains active until it is disabled with ENDBOX or re-defined with another BOX command. If you forget to disable BOX you may restrict the region where later keywords are applied. BOX can also be redefined by commands which use a box as part of their input data (e.g. ADD, COPY). A box defined as part of another command also remains active until disabled or redefined. The data should be terminated by a slash (/).  Item 1  IX1   First block on X axis of the new input box. Item 2  IX2   Last block on X axis of the new input box. Item 3  JY1   First block on Y axis of the new input box. Item 4  JY2   Last block on Y axis of the new input box. Item 5  KZ1   First block on Z axis of the new input box. Item 6  KZ2   Last block on Z axis of the new input box. The data must satisfy         1 <= IX1 <= IX2 <= NDIVIX         1 <= JY1 <= JY2 <= NDIVIY         1 <= KZ1 <= KZ2 <= NDIVI N.B. BOX/ENDBOX inside the  should not be placed inside the '--<RELATIONS+>/--<RELATIONS->' delimitors that WizGen uses to define its sections.   The user must move the keyword(s) outside of the delimitors. WizGen will not output them inside these sections, but they may be added in the WizGen Project file editor, but at any other position in the file.  This does not place any restriction on functionality. COORD Co-ordinate lines The data associated with this Eclipse keyword must be included in the TransGen run file to define the map position of the cell corners. Each co-ordinate line defines the positions for the grid block corner points for each (i, j) in the grid.  Given the depth of a particular grid block corner, and the associated co-ordinate line, the x and y co-ordinates of the corner point can be calculated. A co-ordinate line is specified by two triplets of x, y and z co-ordinates, representing two distinct points on it.  If the (x,y) co-ordinates of the top and bottom points are identical, then the z co-ordinates of the points are not used. UNITS: m (METRIC), ft (FIELD), cm (LAB) DEFAULT:  <undefined> The keyword line is followed by (NDIVIX+1)(NDIVIY+1) co-ordinate lines, each consisting of two point each consisting of 3 values: the x, y and z co-ordinates.  The current version of the program limits the number of reservoirs (or sets of co-ordinate lines) in the grid to one.  The last co-ordinate line is followed by a slash (/). For example:- COORD    1000    2000    1000    3000    1000    1000    1000    0           1000    1000     0          1000    2000    0           1000    2000     0          1000    3000    0           1000    3000     0          1000    0           2000    1000    0            2000   1000    1000    2000    1000    1000     2000   1000    2000    2000    1000    2000     2000   1000    3000    2000    1000    3000     2000   1000    0           4000    1000    0           4000    1000    1000    4000    1000    1000    4000    1000    2000    4000    1000    2000    4000    1000    3000    4000    1000    3000    4000    1000    0           0           2000    0           0           2000    1000    0           2000    1000    0           2000    2000    0           2000    2000    0           2000    3000    0           2000    3000    0           2000    0           500      2000     0          500      2000    1000    500      2000     1000   500      2000    2000    500      2000     2000   500      2000    3000    500      2000     3000   500      2000    0          1000    2000      0         1000    2000    1000   1000    2000     1000   1000    2000    2000   1000    2000     2000   1000    2000    3000   1000    2000     3000   1000    2000     / COPY Copies data from one array to another This is one of the Eclipse keywords which can be used to modify data arrays in the Eclipse simulation model (see also ADD, EQUALS and MULTIPLY). If the COPY keyword is included in the Eclipse parent model, it should also be included in the TransGen run file to ensure data compatibility between the two models. The COPY keyword may be followed by any number of records, each of which is terminated by a slash (/).  The data is terminated by a null record (i.e. a record with no data before the terminating slash).  Each record consists of at least 2, and up to 8 items of data. Item 1  The name of the source array from which data is to be copied (enclosed in quotes). Item 2  The name of the destination array (enclosed in quotes).  Often the destination array is altered. Items 3-8 may be used to redefine the input box for this and subsequent operations within the current keyword. If items 3-8 are not defined (a slash is inserted after item 2), they default to the values which were used for the previous operation within the current keyword.  For the first operation in the keyword, the box defaults to the values set by the most recent BOX or ENDBOX keyword.  If there is no preceding BOX or ENDBOX in the current section, the box is taken to include the entire reservoir. Item 3  IX1   First block to be modified on the X axis. Item 4  IX2   Last block to be modified on the X axis. Item 5  JY1   First block to be modified on the Y axis. Item 6  JY2   Last block to be modified on the Y axis. Item 7  KZ1   First block to be modified on the Z axis. Item 8  KZ2   Last block to be modified on the Z axis. The data must satisfy         1 <= IX1 <= IX2 <= NDIVIX         1 <= JY1 <= JY2 <= NDIVIY         1 <= KZ1 <= KZ2 <= NDIVIZ DIMENS Specify the model dimensions The data associated with this Eclipse keyword must be included in the TransGen run file to define the number of columns, rows and layers in the model. The keyword is followed by three integers which define the number of blocks along the X, Y and Z axes respectively. The data must be terminated by a slash (/). NOTE:- The DIMENS keyword and the relevant associated data are automatically added to the <project_name>.TGDATA run file when the Columns, Rows and Layers in the current project are defined and saved via the Coordinate System page in WizGen in either Basic or Flexible Project mode. DIMENS IX  IY  IZ   / Item 1  Number of grid blocks in the x direction Item 2  Number of grid blocks in the y direction Item 3  Number of grid blocks in the z or depth direction DIMENS MUST be specified at the top of the TransGen run file.  Geometry and property keywords depend on the dimensions of model being known, and an error will be generated if the DIMENS (or SPECGRID) keyword is missing. EDITNNC Change a non-neighbour connection The data associated with this EDITNNC Eclipse keyword can be output from TransGen providing a list of transmissibility multipliers for all faulted non-neighbour connections.  The faulted non-neighbour connections are those of the parent model (i.e. the model defined by the ZCORN geometry which is input to both Eclipse and TransGen). Data associated with this keyword are output to the file specified for EDITNNC on the Output - simulator input page in WizGen.  The form of the keyword output by TransGen is as follows:- EDITNNC IX  IY  IZ  JX  JY  JZ  TRANM / . . / Each line following the EDITNNC keyword specifies a faulted non-neighbour connection and the associated transmissibility multiplier and is terminated with a slash (/).  After the last non-neighbour modification a single slash (/) terminates the list. The arguments in each line are: IX, IY, IZ  The co-ordinates of the first cell joined to the non-neighbour connection. JX, JY, JZ  The co-ordinates of the second cell joined to the non-neighbour connection. TRANM   The transmissibility multiplier for the non-neighbour connection.  The multiplier TRANM cannot be negative but can be zero. The EDITNNC data together with the TRANX, TRANY data (and NNC data- if the new fault drag and hierarchical zone effects were incorporated in the TransGen model) output from a TransGen run should be included in the EDIT section of the Eclipse input file. NOTE:- Prior to the TransGen version 3.2 release, there was a one-to-one correspondence between across- fault connections in the Eclipse simulator and in TransGen. Provided, as was usually the case, the fault rock permeability was lower than the harmonic average permeability of the two grid-blocks, the transmissibility multipliers output to the EDITNNC file were in the range 0.0 to 1.0. However the current version of TransGen including fault drag and hierarchical zone effects can produce radically different sets of across- fault connections to those in the parent model, and this can result in:- Many Transmissibility multiplier values of 0.0 in the EDITNNC file. These are for connections that exist in the parent model, but are not formed following the user-defined geometrical modifications to the fault trace. A value of zero in the file is necessary for these connections; if they were omitted from the file, the simulator would use the default unfaulted transmissibility for these connections. Many Transmissibility multiplier values in the EDITNNC file considerably larger than 1.0. These values do not reflect calculation of very high fault rock permeability, but are generally generated for connections with much larger juxtaposition areas in the user-defined model than in the parent model. END Marks the end of the input This Eclipse keyword has no data field.  It marks the end of the input read from the instruction file. When TransGen reads the END keyword it finishes reading and begins computation, even if END does not occur at the end of a file. ENDBOX Reset box to encompass the entire grid The Eclipse ENDBOX keyword has no associated data. It causes the input box to be reset so that it encompasses the entire grid.  Thus, for an 11 by 19 by 4 grid, it has the same effect as: BOX 1   11   1   19   1   4   / EQUALS Set array to a constant in current box This is one of the Eclipse keywords which can be used to modify data arrays in the Eclipse simulation model (see also ADD, COPY and MULTIPLY). If the EQUALS keyword is included in the Eclipse parent model, it should also be included in the TransGen run file to ensure data compatibility between the two models. The EQUALS keyword may be followed by any number of records, each of which is terminated by a slash (/).  The data is terminated by a null record (i.e. a record with no data before the terminating slash).  Each record consists of at least 2, and up to 8 items of data. Item 1  The name of the array to be modified (enclosed in quotes). Item 2  The constant to be added to the array specified by item 1.  The constant should be positive, and may be real or integer. Items 3-8 may be used to redefine the input box for this and subsequent operations within the current keyword. If items 3-8 are not defined (a slash is inserted after item 2), they default to the values which were used for the previous operation within the current keyword.  For the first operation in the keyword, the box defaults to the values set by the most recent BOX or ENDBOX keyword.  If there is no preceding BOX or ENDBOX in the current section, the box is taken to include the entire reservoir. Item 3  IX1   First block to be modified on the X axis. Item 4  IX2   Last block to be modified on the X axis. Item 5  JY1   First block to be modified on the Y axis. Item 6  JY2   Last block to be modified on the Y axis. Item 7  KZ1   First block to be modified on the Z axis. Item 8  KZ2   Last block to be modified on the Z axis. The data must satisfy         1 <= IX1 <= IX2 <= NDIVIX         1 <= JY1 <= JY2 <= NDIVIY         1 <= KZ1 <= KZ2 <= NDIVIZ FAULTS Specify fault positions This Eclipse keyword can be used to specify fault positions during input or to report fault positions in an output file. By default, TransGen locates faults in the model by searching for fault displacements implicit in the corner-point geometry (keywords COORD and ZCORN). In previous versions of TransGen, the FAULTS keyword prompted ViewGen to import user-defined cell faces and to mark these faces as faulted within the model. If the FAULTS keyword was specified in the TGDATA file ViewGen did not attempt to automatically search for faults. Calculations were based solely on the imported faults. New to TransGen 3.1, faults are always generated automatically by ViewGen. The FAULTS keyword can still be used to import user-defined faults for visualisation, but only those user-defined faults that coincide with faults found by ViewGen can be viewed. There is no limit to number of fault data records, each record defining a segment of a fault, as follows: Item 1  Fault Name    (Up to 8 characters, enclosed in inverted commas). Item 2  IX1   Lower I-coordinate of cells along the fault. Item 3  IX2   Upper I-coordinate of cells along the fault.     IX1 must equal IX2 if the face (Item 8) is 'X' or 'I'. Item 4  IY1   Lower J-coordinate of cells along the fault. Item 5  IY2   Upper J-coordinate of cells along the fault.     IY1 must equal IY2 if the face (Item 8) is 'Y' or 'J'. Item 6  IZ1   Lower K-coordinate of cells along the fault. Item 7  IZ2   Upper K-coordinate of cells along the fault.     IZ1 must equal IZ2 if the face (Item 8) is 'Z' or 'K'. Item 8  Face of the fault.     This should be one of 'X', 'Y', 'Z', 'I', 'J', 'K', 'X-', 'Y-', 'Z-', 'I-', 'J-', 'K-'. The set of records must end with a blank record, containing only a slash (/). HINT:- The FAULTS (derived connection property) data can be output to file at the end of a TransGen run via the Output - derived and user-defined properties page of WizGen. FIELD Indicates that field units are to be used i.e. all units of length are reported in feet. This Eclipse keyword has no associated data. The units of measurement (i.e. Metric, Field or Lab) in a TransGen project are set via the Units option on the Coordinate System page of WizGen. INCLUDE Name of data file to be included The name of the data file to be included at the current position, enclosed in quotes, should be inserted on the line after the keyword.  The data should be terminated by a slash (/). The data file may contain any valid TransGen keyword, and can INCLUDE other data files (such as cell or connection properties associated with User-defined keywords as in a Flexible WizGen project).  INCLUDE is normally used to limit the size of the main instruction file. The format of the INCLUDE keyword in the TGDATA run file is determined by the Eclipse data files selected via the Included Data page of WizGen. So, for example, the INCLUDE entries in the TGDATA file could be as follows:- --<INCLUDES+> INCLUDE `/home/aeh/TGproject/<project_name>_INPUT/COORD.DATA' / INCLUDE `/home/aeh/TGproject/<project_name>_INPUT/ZCORN.DATA' / INCLUDE `/home/aeh/TGproject/<project_name>_INPUT/TGVS.DATA' / INCLUDE `/home/aeh/TGproject/<project_name>_INPUT/PERM.DATA' / --<INCLUDES-> KRNUM Directional keywords indexing each cell to relative permeability & capillary pressure tables These six Eclipse KRNUM directional keywords (KRNUMX, KRNUMX- KRNUMY, KRNUMY-, KRNUMZ KRNUMZ-) and the indices defining which relative permeability and capillary pressure table to apply to each grid-block in the simulation model, are created at the end of the ViewGen run according to the divisions and priorities assigned on the Two phase flow - Groupings section in WizGen and output  to a file as specified in the Two phase flow - Output section in WizGen. NOTE:- To implement the use of Two-phase fault rock properties in the Eclipse simulation model, a file containing the KRNUM keywords together the upscaled relative permeability and capillary pressure tables output (SWOF output file) from the Two-Phase Flow module in TransGen need to be included in the simulator. The KRNUM data file replaces the original SATNUM data. For example, KRNUMY is used to define the SWOF table for flow from cell [I J K] to cell [I J+1 K], while KRNUMY- defines the table for flow from cell [I J K] to cell [I J-1 K]. For all unfaulted cell faces and for all cells in the two vertical directions (i.e. KRNUMZ and KRNUMZ-) the original SATNUM index is used. In the 3*3*2 example illustrated above, 16 cell edges are faulted. Assuming the cells originally have the same relative permeability functions, then the original SATNUM file will be:- SATNUM 18*1 / If a separate pseudo-relative permeability function is calculated for each faulted cell face, then the new KRNUM file will be:- KRNUMY 1 1 1 1 2 1 1 3 1 1 1 1 1 4 1 1 5 1 / KRNUMY- 1 1 1 1 1 6 1 1 7 1 1 1 1 1 8 1 1 9 / KRNUMY 10 11 1 1 1 1 1 1 1 12 13 1 1 1 1 1 1 1 / KRNUMY- 1 1 1 14 15 1 1 1 1 1 1 1 16 17 1 1 1 1 / KRNUMZ 18*1 / KRNUMZ- 18*1 / LAB Indicate that lab units are to be used i.e. all units of length are reported in centimetres The Eclipse keyword has no associated data. The units of measurement (i.e. Metric, Field or Lab) in a TransGen project are set via the Units option on the Coordinate System page of WizGen. METRIC Indicate that metric units are to be used i.e. all units of length are reported in metres The Eclipse keyword has no associated data. The units of measurement (i.e. Metric, Field or Lab) in a TransGen project are set via the Units option on the Coordinate System page of WizGen. MINPV Sets a minimum pore volume any cell must have to be active The keyword is used in the Eclipse model to declare a threshold pore volume which any cell must exceed or it will be made inactive. The MINPV keyword sets a threshold value for all the cells in the current model. An inactive cell does not contribute to the total volume of the system and is treated by default as a barrier. This is one of the Eclipse keywords which can be used in the Eclipse simulation model to control which cells are active/inactive (see also ACTNUM, MINPVV and PORO).  If the keyword is not included in the Eclipse run file, the minimum pore volume automatically defaults to1.0E-6 (in the current units). The keyword should be followed by a line containing the threshold pore volume, in the current units,  and terminated by a slash (/).  The value for a threshold pore volume should be a positive real number. NOTE:- New to TransGen version 3.2, the Cell pore volume cut-off (set on the Miscellaneous Options page of WizGen) defines the MINPV keyword in the TransGen run file and can either be kept at the default setting of 1.0E-6 or changed to mirror a different MINPV value included in the Eclipse simulator run file. MINPV 1.0e-06 / Units: cubic metres (METRIC),  rb (FIELD) or cubic centimetres (LAB). HINT:- MINPV only affects active cells, those which have been rendered inactive via the ACTNUM keyword will remain so, even if their pore volume exceeds the threshold set by MINPV. MINPVV (Advanced keyword) Sets the minimum pore volume a number of cells must have to be active The MINPVV keyword is used in the Eclipse model to declare a threshold pore volume which a cell must exceed or it will be made inactive.  One threshold value is input for each cell in the current BOX.  If the keyword is not included, a default value of 1.0 E-6 is set and is applied to all the cells.  An inactive cell does not contribute to the total volume of the system and is treated by default as a barrier. This is one of the Eclipse keywords which can be used in the Eclipse simulation model to control which cells are active/inactive (see also ACTNUM, MINPV and PORO).  NOTE:- If the MINPVV keyword is included in the Eclipse parent model, it should be included in the TransGen run file to ensure TransGen identifies the same active/inactive cells. The MINPVV keyword should be followed by a line containing one positive real number for every cell in the current box, specifying its threshold pressure in the current units,  and terminated by a slash (/). For example:- -----  IX1 - IX2  IY1 - IY2  IZ1 - IZ2 BOX                 1         8      2         2      2        3  / MINPVV 1000.0 1000.0 1000.0 1000.0 1000.0 1000.0 1000.0 1000.0    500.0   500.0   500.0   500.0   500.0   500.0   500.0   500.0  / ENDBOX Units: cubic metres (METRIC),  rb (FIELD) or cubic centimetres (LAB). MINPVV only affects active cells, those which have been set inactive via the ACTNUM keyword will remain so even if their pore volume exceeds the threshold set by MINPVV. MULTIPLY Multiply array by a constant in current box This is one of the Eclipse keywords which can be used to modify data arrays in the Eclipse simulation model (see also ADD, COPY and EQUALS). If the MULTIPLY keyword is included in the Eclipse parent model, it should also be included in the TransGen run file to ensure data compatibility between the two models. The MULTIPLY keyword may be followed by any number of records, each of which is terminated by a slash (/).  The data is terminated by a null record (i.e. a record with no data before the terminating slash).  Each record consists of at least 2, and up to 8 items of data. Item 1  The name of the array to be modified (enclosed in quotes). Item 2  The constant by which the array specified in item 1 is to be multiplied.  The constant should not be negative, but may be real or integer. Items 3-8 may be used to redefine the input box for this and subsequent operations within the current keyword. If items 3-8 are not defined (a slash is inserted after item 2), they default to the values which were used for the previous operation within the current keyword.  For the first operation in the keyword, the box defaults to the values set by the most recent BOX or ENDBOX keyword.  If there is no preceding BOX or ENDBOX in the current section, the box is taken to include the entire reservoir. Item 3  IX1   First block to be modified on the X axis. Item 4  IX2   Last block to be modified on the X axis. Item 5  JY1   First block to be modified on the Y axis. Item 6  JY2   Last block to be modified on the Y axis. Item 7  KZ1   First block to be modified on the Z axis. Item 8  KZ2   Last block to be modified on the Z axis. The data must satisfy         1 <= IX1 <= IX2 <= NDIVIX         1 <= JY1 <= JY2 <= NDIVIY         1 <= KZ1 <= KZ2 <= NDIVIZ NOTE:- If this keyword is present in the Eclipse parent model run file, it should be included in the TransGen run file to ensure TransGen uses the same data as used in the parent model. MULTX X direction transmissibility multipliers MULTX, MULTY and MULTZ are grid-block-based multipliers used by Eclipse. They have the same format as any other grid-block property (e.g. PERMX) and can be included in a TransGen run in exactly the same fashion. NOTE:- If MULTX values from Eclipse are included in TransGen, they will influence the contents of the TransGen TRANX output file as the transmissibilities will be calculated as a function of both MULTX and fault rock. A MULTX value assigned to a cell (I, J, K) is applied to the transmissibilities between this cell and all cells with which it forms connections in the X+ direction, i.e. those with the indices (I+1, J, K*), where K* can take any value. Hence, if no fault is present on the X+ side of cell (I, J, K), the multiplier is only applied to the single connection into cell (I+1, J, K), but if a fault is present, MULTX is applied to any connection (neighbour or non-neighbour) formed from (I,J,K) in this direction. The keyword should be followed by one non-negative real number for every grid block in the current input box specifying the X direction transmissibility multipliers.  The data must be terminated by a slash (/). UNITS:  mD (METRIC, FIELD or LAB) Every MULTX value in the top plane (k = 1) must be specified in one way or another by the end of the instruction file.  Values in lower planes (K > 1) which are not specified, default to the plane above. Grid blocks are ordered with the X axis index cycling fastest, followed by the Y and Z axis indices.  Repeat counts may be used for repeated values (e.g. 115*208.4).  Note that spaces may not be inserted on either side of the asterisk. MULTY Y direction transmissibility multipliers MULTX, MULTY and MULTZ are grid-block-based multipliers used by Eclipse. They have the same format as any other grid-block property (e.g. PERMX) and can be included in a TransGen run in exactly the same fashion. NOTE:- If MULTY values from Eclipse are included in TransGen, they will influence the contents of the TransGen TRANY output file as the transmissibilities will be calculated as a function of both MULTY and fault rock. A MULTY value assigned to a cell (I, J, K) is applied to the transmissibilities between this cell and all cells with which it forms connections in the Y+ direction, i.e. those with the indices (I, J+1, K*), where K* can take any value. Hence, if no fault is present on the Y+ side of cell (I, J, K), the multiplier is only applied to the single connection into cell (I, J+1, K), but if a fault is present, MULTY is applied to any connection (neighbour or non-neighbour) formed from (I,J,K) in this direction. The keyword should be followed by one non-negative real number for every grid block in the current input box specifying the Y direction transmissibility multipliers.  The data must be terminated by a slash (/). UNITS:  mD (METRIC, FIELD or LAB) Every MULTY value in the top plane (k = 1) must be specified in one way or another by the end of the instruction file.  Values in lower planes (K > 1) which are not specified default to the plane above. Grid blocks are ordered with the X axis index cycling fastest, followed by the Y and Z axis indices.  Repeat counts may be used for repeated values (e.g. 115*208.4).  Note that spaces may not be inserted on either side of the asterisk. MULTZ Z direction transmissibility multipliers MULTX, MULTY and MULTZ are grid-block-based multipliers used by Eclipse. They have the same format as any other grid-block property (e.g. PERMX) and can be included in a TransGen run in exactly the same fashion. MULTZ is analogous to MULTX and MULTY, and apply to connections in the Z+ direction. The keyword should be followed by one non-negative real number for every grid block in the current input box specifying the Z direction transmissibility multipliers.  The data must be terminated by a slash (/). UNITS:  mD (METRIC, FIELD or LAB) Every MULTZ value in the top plane (k = 1) must be specified in one way or another by the end of the instruction file.  Values in lower planes (K > 1) which are not specified default to the plane above. Grid blocks are ordered with the X axis index cycling fastest, followed by the Y and Z axis indices.  Repeat counts may be used for repeated values (e.g. 115*208.4).  Note that spaces may not be inserted on either side of the asterisk. NNC Explicit entry of non-neighbour connections The output of data associated with the NNC Eclipse keyword is new to the TransGen version 3.2 release, allowing the output of transmissibility data for non-neighbour connections that do not exist in the geometry of the parent model. These NNC connections are generated when using WizGen in Flexible project mode with the new fault drag and hierarchical zone features included in the run file. Data associated with this keyword are output to a file specified for NCC on the Output - simulator input page in WizGen. The form of the keyword output is as follows:- NNC   IX  IY  IZ  JX  JY  JZ  TRAN /   .   . / Where [IX, IY, IZ] [JX  JY  JZ] is a non-neighbour connection as defined by the coordinates (X, Y, Z) of the two cells (I and J) joined at the non-neighbour connection that does not exist in the geometry of the parent model and TRAN is transmissibility of the non-neighbour connection. These non-neighbour connections are common on traces modified using the new functionality. The output file containing the NNC data together with the EDITNNC, TRANX and TRANY files can then included in the EDIT section of the Eclipse input file to allow the implicit representation of more complex geometry than is represented explicitly in the simulation model. NOTE:- Two forms of NNC connections are produced by the new functionality:- across- fault connections in which JX = IX+1 and IY = JY, or in which IX = JX and JY = IY+1. These connections are generated either because of throw changes on the trace or because of the inclusion of a fault zone same-stack connections in which IX = JX and IY = JY. These connections can only be generated by fault zones (See Processing modified traces). NTG Net to Gross Ratio The data associated with this Eclipse keyword are needed in TransGen to define the shale content of the cells. Net to Gross is a measure of the net thickness of good reservoir (i.e. sand) to gross interval thickness with values ranging from 1 for best sands to 0 for non-reservoir (i.e. 100% shale). The keyword is followed by one non-negative real number between 1.0 and 0.0 for every grid block in the current input box.  The values specified are used to convert from gross to net thickness, and act as multipliers of grid block pore volumes and transmissibilities in the X and Y directions.  The data must be terminated by a slash (/). Any NTG values which are not specified when the end of the instruction file is reached default to 1.0. Grid blocks whose pore volume is zero are treated by TransGen as inactive.  Inactive blocks can be unambiguously identified by setting either PORO or NTG to zero in inactive blocks.  It is also possible to use the ACTNUM keyword. Grid blocks are ordered with the X axis index cycling fastest, followed by the Y and Z axis indices.  Repeat counts may be used for repeated values (e.g. 115*0).  Note that spaces may not be inserted on either side of the asterisk. For example:- -------- IX1-IX2 JY1-JY2 KZ1-KZ2 BOX 6   11   4   9   2   3    / NTG    6*0.4   6*0.4   6*0.48   6*0.51   6*0.7   6*0.72    6*0.4   6*0.4   6*0.48   6*0.51   6*0.7   6*0.72   / PERMX X direction absolute permeabilities The data associated with this (and the PERMY) Eclipse keyword are needed in TransGen to define the cell permeabilities. The keyword is followed by one non-negative real number for every grid block in the current input box specifying the X direction absolute permeability.  The data must be terminated by a slash (/). UNITS:  mD (METRIC, FIELD or LAB) Every PERMX value in the top plane (k = 1) must be specified in one way or another by the end of the instruction file.  Values in lower planes (K > 1) which are not specified default to the plane above. Grid blocks are ordered with the X axis index cycling fastest, followed by the Y and Z axis indices.  Repeat counts may be used for repeated values (e.g. 115*208.4).  Note that spaces may not be inserted on either side of the asterisk. For example:- -------- IX1-IX2 JY1-JY2 KZ1-KZ2 BOX 5   16   3   8   1   1   / PERMX    100   1500   10*60      90   1500    10*60     80   1500    10*65     70   1500    10*70     60   1500    10*75     50   1500    10*75   / PERMY Y direction absolute permeabilities The data associated with this (and the PERMX) Eclipse keyword are needed in TransGen to define the cell permeabilities. The keyword is followed by one non-negative real number for every grid block in the current input box specifying the Y direction absolute permeability.  The data must be terminated by a slash (/). UNITS:  mD (METRIC, FIELD or LAB) Every PERMY value in the top plane (k = 1) must be specified in one way or another by the end of the instruction file.  Values in lower planes (K > 1) which are not specified default to the plane above. Grid blocks are ordered with the X axis index cycling fastest, followed by the Y and Z axis indices.  Repeat counts may be used for repeated values (e.g. 115*208.4).  Note that spaces may not be inserted on either side of the asterisk. For example:- -------- IX1-IX2 JY1-JY2 KZ1-KZ2 BOX 5   16   3   8   1   1   / PERMY     100   1500   10*60       90    1500   10*60      80    1500   10*65      70    1500   10*70      60    1500   10*75      50    1500   10*75   / PERMZ Z direction absolute permeabilities The data associated with this Eclipse keyword can be included in TransGen. The keyword is be followed by one non-negative real number for every grid block in the current input box specifying the Z direction absolute permeability.  The data must be terminated by a slash (/). UNITS:  mD (METRIC, FIELD or LAB) Every PERMZ value in the top plane (k = 1) must be specified in one way or another by the end of the instruction file.  Values in lower planes (K > 1) which are not specified default to the plane above. Grid blocks are ordered with the X axis index cycling fastest, followed by the Y and Z axis indices.  Repeat counts may be used for repeated values (e.g. 115*208.4).  Note that spaces may not be inserted on either side of the asterisk. PORO Grid block porosities This Eclipse keyword when included in the Eclipse simulation model defines the porosities of every cell in the current input box. It is also one of the Eclipse keywords used in the Eclipse simulation model to control which cells are active/inactive (see also ACTNUM, MINPV and MINPVV), i.e. the cells whose pore volume is zero are treated by Eclipse as inactive. If data associated with the PORO keyword are included in the Eclipse parent model, they should also be included in the TransGen run file. The PORO keyword should be followed by one non-negative real number for every grid block in the current input box specifying the grid block porosities. The data must be terminated by a slash (/). Grid blocks are ordered with the X axis index cycling fastest, followed by the Y and Z axis indices.  Repeat counts may be used for repeated values (e.g. 115*0.217).  Note that spaces may not be inserted on either side of the asterisk. For example:- -------- IX1-IX2 JY1-JY2 KZ1-KZ2 BOX 5   16   3   8   2   3   / PORO   0.16   0.14   0.12   0.1   0.08   0.09   0.1   0.11   0.12   0.13   0.14   0.14   0.16   0.14   0.12   0.1   0.09   0.09   0.1   0.11   0.12   0.13   0.14   0.14   0.15   0.14   0.12   0.1   0.10   0.09   0.1   0.11   0.12   0.13   0.14   0.14   0.15   0.14   0.12   0.1   0.10   0.09   0.1   0.11   0.12   0.13   0.14   0.14   0.14   0.14   0.12   0.1   0.09   0.09   0.1   0.11   0.12   0.13   0.14   0.14   0.14   0.14   0.12   0.1   0.08   0.09   0.1   0.11   0.12   0.13   0.14   0.14   0.18   0.15   0.12   0.1   0.08   0.09   0.1   0.11   0.12   0.13   0.15   0.15   0.18   0.15   0.12   0.1   0.09   0.09   0.1   0.11   0.12   0.13   0.15   0.15   0.15   0.15   0.12   0.1   0.10   0.09   0.1   0.11   0.12   0.13   0.15   0.15   0.15   0.15   0.12   0.1   0.10   0.09   0.1   0.11   0.12   0.13   0.15   0.15   0.15   0.15   0.12   0.1   0.09   0.09   0.1   0.11   0.12   0.13   0.15   0.15   0.15   0.15   0.12   0.1   0.08   0.09   0.1   0.11   0.12   0.13   0.15   0.15   / NOTE:- In the absence of PORO data, TransGen sets the porosities to 1.0. RPTRST Controls on output to the RESTART file The Eclipse RPTRST should be followed by a list of mnemonics which control the output of data to the Restart file. The list should be terminated by a slash (/). One of the Eclipse output controlled by this keyword is FLOWS, i.e. the output of interblock flows (including non-neighbour connection flows and flows between global and local grids). The Eclipse Restart file can be used in TransGen as a source of across-fault flow rates when including two-phase fault rock calculations in the run file (see Using WizGen in Flexible project mode) SATNUM Index Grid referencing the saturation function data The Eclipse SATNUM keyword indexes each grid-block in the model to a set of relative permeability and capillary pressure curves as defined by the SWOF keyword. The keyword takes only integer values, but in all other respects is identical to other grid-block properties recognised by TransGen. NOTE:- The data associated with the SWOF and SATNUM keywords derived from an Eclipse reservoir model MUST be input into TransGen in order to implement the Two-phase flow functionality. Examples:- SATNUM 2 2 2 2 2 2 2 1 1 1 1 6 6 6 6 6 ... 1 1 1 1 1 1 1 1 2 2 2 2 2 2 1 1 1 6 6 6 6 6 6 6 / or SATNUM 128*1 256*2 / The SATNUM keyword is essential for running the TransGen Two-phase fault-rock calculations and should be loaded via the Included Data page of WizGen in Flexible project mode. SATNUM is a recognised TransGen keyword and therefore it does not need to be specified as a user-defined grid-block property. SPECGRID Specify the model dimensions, number of reservoirs and coordinate system This Eclipse keyword is followed by four integers and a character;  which define the number of grid-blocks along the X, Y and Z axes respectively, the number of reservoirs, and a flag which indicates whether the Cylindrical or Cartesian coordinates are used.  Following the keyword, there is a single record containing four integers and a character, and the data must be terminated by a slash (/). SPECGRID 10 20  12 1 F Item 1  Number of grid blocks in the x direction - for Cartesian geometries Item 2  Number of grid blocks in the y direction - for Cartesian geometries Item 3  Number of grid blocks in the z or depth direction - for Cartesian geometries Item 4 The number of reservoirs, each with its own coordinate system.  For TransGen this must only be one. Item 5 A single T or F indicating Cylindrical or Cartesian coordinates.  TransGen only accepts Cartesian coordinates. SPECGRID should be specified at the top of the instruction file.  Geometry and property keywords depend on the dimensions of model being known, and an error will be generated if a SPECGRID or DIMENS keyword is missing.  TransGen only accepts a single reservoir in a 8 cornerpoint cartesian geometry. SWOF Defines water & oil relative permeability & water-oil capillary pressure as a function of water saturation The Eclipse SWOF keyword defines the water relative permeability, oil relative permeability and water-oil capillary pressures as a function of water saturation. The keyword should be followed by as many tables as the highest integer in the SATNUM grid, each terminated by a slash (/). The order of the tables correspond to the SATNUM indexing. NOTE:- The data associated with the SWOF and SATNUM keywords derived from an Eclipse reservoir model MUST be input into TransGen in order to implement the Two-phase flow functionality. Each table consists of 4 columns of data:- Column 1. Water saturation Values should be between 0 and 1 and should increase monotonically down the column. The first value in the column is interpreted as the connate water saturation. Column 2. Water relative permeability Values should be between 0 and 1 and should be level or increase monotonically down the column. The first value in the column must be zero. Column 3. Oil relative permeability Values should be between 0 and 1 and should be level or decrease down the column. The last value in the column must be zero. Column 4. Capillary pressure Values should be level or decrease down the column. Units are bars (METRIC), psi (FIELD) or atm (LAB). Example:- SWOF 0.3817 0.0 0.85 2.95990 0.5053 0.000001 0.8228 1.45830 0.5913 0.00001 0.4985 0.44050 0.6297 0.1131 0.0199 0.05020 0.6633 0.1907 0.0072 0.02620 0.7001 0.3001 0.0000 0.0000 / end table 1 0.1458 0.0 0.85 2.96180 0.3308 0.000001 0.8496 1.53730 0.5 0.00001 0.4164 .33570 0.5423 0.008 0.3247 .04620 0.5588 0.0477 0.045 .02110 0.7 0.3 0.0000 0.0000 / end table 2 The tables associated with the SWOF keyword are essential for running the TransGen Two-phase functionality and the file containing this data must be loaded via the Two phase flow - INPUT page of WizGen in Flexible project mode. In the current version of TransGen, all SWOF tables should be contained in the same file. NOTE:- SWOF is the only saturation function keyword recognised and supported by the current version of TransGen. Other Eclipse keywords for defining two or three phase relative permeability or capillary pressure functions (e.g. SGFN, SWFN, SOF2, SOF3, SOF32D, SGOF, SLGOF) are not supported. NOTE:- Endpoint scaling is not supported by the current version of TransGen. TGAXES (new TransGen keyword) Define the ordering of the cells in the input files and direction of the Y axis for the COORD section This TransGen keyword allows the import of data ordered in a different manner from the Eclipse default.  Data for TransGen must be ordered in row order  (columns cycle fastest),  but the origin (Row 1,  Column 1) may be placed in any corner of the model.  Similarly, the direction in which the x and y coordinates are ordered, defining the position of the COORD lines,  may be in local model coordinates (Y increases 'downwards') or in geographic coordinates (Y increases 'upwards' to the north).  The keyword should be followed by a record containing two integer numbers and terminated by a slash (/).  For example: the eclipse default is:- TGAXES 1  0  / Item 1 IORDER specifies the position of the origin and the direction of the rows and columns            IORDER =1 (Row 1,  Column 1)  in 'top left' .  Rows are east-west                            This is a special case for the Eclipse default, the only permitted value ILOCAL is 0            IORDER =2 (Row 1,  Column 1)  in bottom left.  Rows are east-west            IORDER =3 (Row 1,  Column 1)  in top left.  Rows are east-west                             IORDER=3 ILOCAL = 0 is also the Eclipse default.                             IORDER=3, ILOCAL  =1 is a frequent RMS ordering            IORDER = 4 (Row 1,  Column 1)  in bottom right  Rows are east-west            IORDER = 5 (Row 1,  Column 1)  in top right  Rows are east-west Item 2 ILOCALspecifies the direction in which Y increases.  It may have two values:        0 - local coordinate system. Y increases 'downwards'        1 - Geographic coordinate system. Y increases 'upwards' ie to the north in map view. TGDRAG (new TransGen version 3.2 keyword) To manually define throw modifications When using the new Include fault drag and hierarchical zone effects functionality, this TransGen keyword allows manual definition of throw modifications on all fault traces in the model (either included explicitly in the geometry of the parent model or included as user-defined faults using TGTHROW). The keyword is designed to allow a portion of the throw of a fault to be accommodated with local normal drag (the yellow areas in the cartoon below), but can also be used to include uncertainty in fault throws in the model. NOTE:- Probabilistic and/or deterministic fault throw modification can also be made using the equations set via the Drag applied to fault traces page in the WizGen or by user-defined criteria specified in the DRAG plugin. The keyword can be followed by as many definitions as needed on separate lines, each line and the file are terminated by a slash. The format of each line is: I J `Direction' Drag_ratio / Drag_ratio can take any positive or negative value (or zero) and defines the ratio between the throw of the trace after drag has been applied to the throw on the trace reflected in the original model geometry. Hence a value of 0.5 will halve the throw, a value of 0.0 will get rid of the fault throw altogether, a value of 1.0 will leave the throw unaltered, a value of 2.0 will double the throw and a value of  1.0 will switch the sense of throw of the fault. Based on the input values, revised drag ratios are calculated and applied on a layer-by- layer basis, using similar considerations to those discussed in relation to the TGTHROW keyword to ensure coherent geometries. Example The following TGDRAG definition applied to the parent model shown in Figure a, will result in the geometry shown in Figure b. NOTE:- In this example an integer value is written for each line in the file to the right of the slash - anything to the right of a slash is ignored while the file is being read and these are only placed in the file for reference, to highlight portions of model in which the values of TGDRAG result in different behaviour  - these are highlighted in Fig. b. For the traces labelled 1, values of TGDRAG are in the range 0 to 1 and the fault throw is progressively lowered. For the traces labelled 2, Drag ratios are in the range 1.0 to 2.0, and the fault throws are increase by up to 100%. All traces associated with the splay fault labelled 3 have TGDRAG values set to -1.0 and the sense of throw of this fault is reversed. The traces labelled 4 have drag ratios around 1.0 adding fairly random variability to the fault throws. Like the example discussed with reference to TGTHROW, the display shown in Figure b is not obtained by ViewGen and is shown for illustrative purposes only. One or more files containing the TGDRAG keyword and others (e.g. TGFZONE, TGTHROW and/or TGTRACE) can be included in the TransGen run via the Included Data page of WizGen, along with all cell and (if used) user-defined connection properties, when running in Flexible project mode with the Include fault drag and hiererchical zone effects option selected. NOTE:- If TGDRAG is used to modify the throw on user-defined fault traces, the keyword MUST be loaded into TransGen AFTER the TGTHROW definition. HINT:- The TGDRAG data can be output to file at the end of a TransGen run via the Output - derived and user-defined properties page of WizGen. TGEVS This TransGen keyword has been made redundant in TransGen 3 and has been replaced by the effective Vshale settings in the new TGFSP keyword. The TGEVS keyword will be recognised by version 3, but TransGen stops with an error report. Method of effective vshale calculation in TransGen version 3 In TransGen version 3, how the effective vshale property is calculated and used for a particular fault seal potential measure is set as part of the new TGFSP keyword (instead of the now defunct TGEVS keyword). When using WizGen in "Basic project" mode, the effective vshale can be calculated from net-to-gross only, vshale only or a combination of both (depending on the data associated with the NTG and TGVS keywords included in the current TransGen run and the Effective vshale computation method set on the Fault Rock Properties page of WizGen). When using WizGen in "Flexible project" mode, the effective vshale can be calculated similarly or based on a user property depending on the Effective vshale setting applied via the Fault Seal Potential Variables page of WizGen. Net-to-gross only - TransGen considers the non-net region to be shale and takes the shale content to equal 1 minus the Net-to-Gross value (where Net-to-Gross is the ratio of the net thickness of good reservoir, i.e. sand to gross interval thickness).                                                                               eVs = (1 - NTG) Vshale only - TransGen takes Vshale as the shale content.                                                                                 eVs = TGVS NGT and VShale - TransGen assumes the non-net region to be pure shale and takes the Effective Vshale content of a grid block to be:-                                                                       eVs = (1 - NTG) + (TGVS x NTG) User Property - Transgen takes the user-defined Effective Vshale grid values assigned to a user-defined keyword. These values should all ideally lie between 0.0 and 1.0. If the user-defined Effective Vshale grid contains values less than 0.0 or greater than 1.0, these values will still be included in the FSP calculation, but the results cannot be guaranteed meaningful. Meaningful FSP values are assumed to have a range from zero to infinity and all numbers entering the summation are either zero or positive. TGFSP (new TransGen version 3.2 keyword) To allow the calculation of fault seal potential (FSP) measures NOTE:- The now redundant TGSGRM and TGEVS keywords are replaced by settings in the TGFSP keyword. The keyword is followed by up to 5 Fault Seal Potential (FSP) definitions each on separate lines, each terminated by a "/". The keyword is then terminated by another "/". The keyword and associated FSP definitions are created automatically by settings saved on the Fault Rock Properties page of WizGen in "Basic project" mode or on the Fault Seal Potential Variables page of WizGen for a "Flexible project". Each FSP definition consists of 12 settings separated by spaces, i.e:- TGFSP name  l  m  n  p  shale_switch  shale_string  distance_switch  combine_switch  evshale_switch  evshale_string  plunge_correction  / / where:- name is the FSP variable name, which is case-sensitive (e.g. 'sgr'). exponent l is the power to which "throw" is raised. exponent m is the power to which "thickness" is raised. exponent n is the power to which "distance" is raised. exponent p is the power to which "eVshale" is raised. shale_switch  1 = named layers; 2 = eVshale cutoff; 3 = import from user-defined keyword; 4 = everything is shale. shale_string if shale_switch = 1, shale_string = a list of layers (e.g. '3-5, 7, 9')                                if shale_switch = 2, shale_string = a cutoff value (e.g. '0.7')                                if shale_switch = 3, shale_string = a user-defined keyword (e.g. 'shale_1')                                if shale_switch = 4, shale_string ie empty (e.g. ' ') distance_switch  1 = centre of beds; 2 = far side of beds; 3 = near side of beds. combine_switch  1 = max layers then sum; 2 = sum then max layers; 3 = max; 4 = min; 5 = mean; 6 = sum then average; 7 = sum in footwall; 8 = sum in hangingwall evshale_switch 1 = ntg; 2 = tgvs; 3 = ntg and tgvs; 4 = import from user-defined keyword evshale_string if evshale_switch = 1, 2 or 3, evshale_string is empty (e.g. ' ')                                     if ev_switch + 4, evshale_string = a user-defined keyword name (e.g. 'evshale_1') plunge_correction  0 = calculated on vertical projection; 1 = calculated in 3D For example:- TGFSP `sgr'    -1 1 0 1 4 ' ' 1 6 1 ' ' 1 / 'csp_yielding'    0 2 -1 0 1 '8-13, 26-29, 34, 38, 45-47' 1 1 1 ' ' 1 / 'csp_fulljames'   0 2 -1 0 2 '0.5' 2 2 3 ' ' 1 / /   The name and the two strings must be included in single quotes ' '.  The contents of the strings depend on previously-defined switches. If particular exponents are set to 0.0, the options for subsequent settings are irrelevant to the calculation. Nonetheless, valid options MUST be supplied. So, for example, if exponent n is set to 0.0 (as it would be in the SGR calculation), a distance_switch must still be defined. Similarly, if exponent p is set to 0.0, the effective Vshale of each cell is not included in the calculation, but still a valid evshale_switch must be applied. If not, ViewGen will issue an error message and stop. TGFZONE (new TransGen version 3.2 keyword) To include user-defined fault zone(s) in a TransGen run When using the new Include fault drag and hierarchical zone effects functionality, this TransGen keyword can be used to include large fault zones visible seismically, but too small for explicit representation in the parent flow model. The TGFZONE keyword can be followed by as many definitions as needed on separate lines, each line and the file are terminated by a slash. The format of each line is:- I J `Direction' type length width r1 r2 r3 r4 damage_para damage_perp / I and J are the indexes of the cell stacks to which the fault trace is adjacent. Direction can be either `DIR-X' or `DIR-Y'. The single quotation marks are essential. Type must be set 1 (there is no functionality associated with type in this version of TransGen). Length and width are the components in the XY plane of the length of the fault zone component parallel and perpendicular to the trace. Units are meters (metric), feet (Field), cm (lab) r1, r2, r3 and r4 are throw ratios assigned to the four corners of the ramp. Damage_para and damage_perp are permeability multipliers used in the ramp. These parameters are defined fully in the section on Fault zone properties. For example:- TGFZONE --I J direction type length width r1 r2 r3 r4 kmult_para kmult_perp 9 3 'DIR_X' 1 50 20 1.0 1.0 0.0 0.0 1.0 1.0 / 12 15 'DIR_Y' 1 14 30 0.7 0.8 0.3 0.2 0.75 0.25 / / HINT:- The TGFZONE keyword should only be used to include large deterministic fault zones visible seismically, but too small for explicit representation in the flow model. Smaller, sub-seismic fault zone structure is better modelled stochastically using the WizGen tool (see using the Assign hierarchical zones option on the Hierarchical fault zone definition page in WizGen). One or more files containing this new keyword and others (e.g. TGTHROW, TGDRAG and/or TGTRACE) can be included in a TransGen run via the Included Data page of WizGen, along with all cell and (if used) user-defined connection properties, when running a project in Flexible project mode with the Include fault drag and hiererchical zone effects option selected. HINT:- The TGFZONE data can be output to file at the end of a TransGen run via the Output - derived and user-defined properties page of WizGen. TGKDT This TransGen keyword has been made redundant in TransGen 3 and has been replaced by the PERM plugin either created automatically by WizGen in "Basic project" mode (see Plugins generated by WizGen in Basic project mode) or by the user via the User-defined plugins page of WizGen (in "Flexible project" mode).  The keyword (which was used in TransGen 2 to include permeability modifier versus depth data) will be recognised by version 3, but TransGen stops with an error report. TGKSE This TransGen keyword has been made redundant in TransGen 3 and has been replaced by the PERM plugin either created automatically by WizGen in "Basic project" mode (see Plugins generated by WizGen in Basic project mode) or by the user via the User-defined plugins page of WizGen (in "Flexible project" mode).  The keyword (which was used in TransGen 2 to input the constants in the equation defining the relationship between shale gouge ratio and permeability) will be recognised by version 3, but TransGen stops with an error report. TGKST This TransGen keyword has been made redundant in TransGen 3 and has been replaced by the PERM plugin either created automatically by WizGen in "Basic project" mode (see Plugins generated by WizGen in Basic project mode) or by the user via the User-defined plugins page of WizGen (in "Flexible project" mode).  The keyword (which was used in TransGen 2 to input a shale gouge ratio vs permeability lookup table) will be recognised by version 3, but TransGen stops with an error report. TGMETRIC The TransGen TGMETRIC keyword (new to the version 3 release) acts as a binary switch in the TGDATA  file; it is either included, in which case it is applied (default) or excluded and therefore not applied. With the TGMETRIC keyword included in the TGDATA file, all calculated fault displacement, fault rock thickness and all Fault Seal Potential measures are reported (graphically and in output files) and stored internally within TransGen using metres as the unit of length. When using WizGen in "Basic project" mode, the TGMETRIC keyword is ALWAYS included in the TGDATA files. However, with WizGen in "Flexible project" mode, the user has the option to NOT include the TGMETRIC keyword by selecting the FSPs in native units option on the Miscellaneous Options page. With the TGMETRIC keyword missing from the TGDATA runfile, all fault displacement, fault rock thickness and all calculated FSP measures are reported in the units of length appropriate to the Units specified on Coordinate System page of WizGen, i.e. feet if the Units are FIELD or cm if the Units are LAB. Inclusion or exclusion of the TGMETRIC keywordmakes absolutely no difference if the Units in the TGDATA run file are METRIC. Depth is not affected by the keyword which is always displayed and stored internally in the units of length appropriate to the TGDATA file. The purpose of the TGMETRIC keyword is to ensure plugins are transportable between different UNITS conventions. Clay Smear Potential (CSP) for example has the dimensions of length. If the UNITS in TGDATA are set to FIELD, then CSP will be reported in metres if TGMETRIC is present and in feet if it is not. With the TGMETRIC keyword included (i.e. activated), this means a PERM plugin with a particular sealing threshold applied to CSP will not need to be changed if the same plugin is used in a reservoir model of another field which has been built using a different UNITS convention. If TGMETRIC is not included (in Flexible project mode only), many plugins will be specific to the UNITS convention for which they have been written. Inclusion/exclusion of the TGMETRIC keyword does not influence the transmissibility calculation: dimensions of fault thickness are always converted back to the specified units system before transmissibilities are calculated ensuring consistency of units in the TRANX and TRANY files. TGMINTR Sets a minimum unfaulted transmissibility any connection must have to be output This TransGen keyword is provided for the user to declare a threshold unfaulted transmissibility value that any connection must exceed or it will be excluded from the output files.  The keyword together with the default value of 1.0 E-6 (i.e. the threshold Eclipse uses for this property) is automatically included in the TGDATA run file using the Unfaulted transmissibility cutoff setting on the Miscellaneous Options page of WizGen in either "Basic" or "Flexible project" mode. The default value should only be changed in exceptional circumstances and should never to set to a value greater than 1.0 E-6 if Eclipse input is being generated. The keyword is followed by a line containing the threshold value, terminated by a slash (/) The value for a minimu transmissibility multiplier cutoff should be a positive real  number. TGMINTR 1.0e-06  / Units: dimensionless HINT:- The TGMINTR setting only affects active connections, so for example those which have been set inactive via the TGREMNNC keyword will remain so even if their unfaulted transmissibilities exceeds the threshold set by TGMINTR. TGNEWKEY New keyword, added to TransGen version 3, to allow the inclusion of user-defined grid-block (i.e. cell) and connection properties. It is automatically added to the TDDATA run file when any new Cell property and/or Connection property keywords are defined via the User-defined keywords page when using WizGen in "Flexible Project" mode. The TGNEWKEY keyword is followed by as many lines as there are new properties, terminated by a slash (/). Each line has the form: `name' property_type/ where property_type is 1 for grid-block (cell) properties and 2 for connection properties. The name can be up to 32 characters long and may contain underscores(_) and numbers as well as letters. However, the first character of the name must be a letter. The letters can be either upper or lower case, but if used in plugins, the property name must be referenced exactly as input as the C++ macro language is case sensitive. TGNEWKEY `cell_property1' 1 / `cell_property2' 1 / `cell_property3' 1 / `connection_property1' 2 / `connection_property2' 2 / / User-defined keywords can be used in plugins, in the TGFSP Keyword and visualised in the graphics interface. If a user-defined keyword referenced via theTGFSP keyword or in a User-defined plugin is not defined using TGNEWKEY, the Transgen run will fail and issue an error message. Unlike recognized grid-block properties (e.g. PERMX, ATCNUM), the values of user-defined grid-block properties do not need to be included explicitly in the TransGen run through instructions in the TGDATA file (although they can be). They may also be calculated in the CELLPROP plugin (see Example). If the values of the property are not included explicitly, they are assigned an initial value of 0.0. TGNNC This keyword has been made redundant in TransGen 3. It will be recognised by version 3, but TransGen stops with an error report. You can create a similar user-defined non-neighbour connection property in TransGen version 3 when using WizGen in "Flexible project" mode by adding it as a User-defined keyword and including an appropriate data file via the Included Data page. Input a user-defined non-neighbour connection property This keyword can be used to input a user-defined property onto fault surfaces for visualisation purposes.  The form of the keyword is as follows: TGNNC IX  IY  IZ  JX  JY  JZ  User-Value / . . / Each line following the TGNNC keyword specifies a connection (neighbour or non-neighour and is terminated with a slash (/).  After the last non-neighbour connection a single slash (/) terminates the list. The arguments in each line are: IX, IY, IZ  The co-ordinates of the first cell joined to the non-neighbour connection. JX, JY, JZ  The co-ordinates of the second cell joined to the non-neighbour connection. User-Value  A real number representing the value of some user-defined property. The user-defined property is not used in any computation.  It can be selected for visualisation from within the graphics viewer. TGNOCALC (new TransGen keyword) Prevent calculation of fault transmissibility multipliers This keyword does not take any data. If present, TransGen builds the Eclipse model geometry, reads property data, but does not perform any calculations. Inclusion of this keyword in the TGDATA run file allows the model to be visualised quickly. This keyword is automatically included in the TGDATA run file when the Do not perform calculation option is toggled "on" in the Miscellaneous Options page of WizGen. TGPLUGIN New keyword added to TransGen version 3 allowing flexible calculations of effective Vshale, fault permeability, fault thickness and across-fault connection area for inclusion in transmissibility calculations. The form of the TGPLUGIN keyword is a set of strings enclosed by single quotes (one string per line) that associate a plugin name with a full C++ source filename. The source file contains the plugin code. For example:- TGPLUGIN `CELLPROP=/home/aeh/TGproject/TGproject_INPUT/.plugins/cellproperties.cpp' `THICK=/home/aeh/TGproject/TGproject_INPUT/.plugins/thickness.cpp' `PERM=/home/aeh/TGproject/TGproject_INPUT/.plugins/permeability.cpp' `AREA=/home/aeh/TGproject/TGproject_INPUT/.plugins/area.cpp' / A plugin is a macro, written in C++, that manipulates the values of cell and connection properties. There are four types of plugin which may be used during the TransGen calculations, two of which are essential, i.e. Fault thickness and fault permeability MUST be calculated via the THICK and PERM plugins. The CELLPROP and AREA plugins are not essential. NOTE:- When using WizGen Light, the THICK and PERM plugins are automatically created and saved to the project's <project_name>_INPUT/.plugins directory as _AUTO_THICK_PLUGIN.cpp and _AUTO_PERM_PLUGIN.cpp respectively and added as strings below the TGPLUGIN keyword in the TGDATA run file when new Fault Rock Properties settings are saved. When using WizGen Heavy, all plugins have to be created via the User-defined plugins page of WizGen Heavy. TGREMNNC (new TransGen keyword) Disable non-neighbour connections within the model This TransGen keyword is supplied for compatibility with future releases of TransGen. However, due to small discrepancies in numerical accuracy between TransGen and Eclipse, TransGen occasionally specifies more non-neighbour connections than Eclipse finds. A warning detailing which NNCs are extra is generated during Eclipse input, and can be safely ignored. If desired, the TGREMNNC keyword can be used with the list given in the Eclipse warning to remove these NNCs from the TransGen output. The form of the keyword is as follows: TGREMNNC IX  IY  IZ  JX  JY  JZ   / . . / Each line following the TGREMNNC keyword specifies a non-neighbour connection and is terminated with a slash (/).  After the last non-neighbour connection a single slash (/) terminates the list. The arguments in each line are: IX, IY, IZ  The co-ordinates of the first cell joined to the non-neighbour connection. JX, JY, JZ  The co-ordinates of the second cell joined to the non-neighbour connection. TGRPT (new TransGen keyword) Controls on output from TransGen This TransGen keyword is generated when output file(s) are specified for one or more properties on the Output - simulator input page of WizGen.This keyword is followed by several arguments that control what the program outputs and where the output is written. TransGen can output the following keywords (and associated data) for later inclusion in an Eclipse simulation: EDITNNC, TRANX, TRANY, NNC (or NNC MULT, TX REPL, TY REPL for inclusion in a MORE simulation). The parameter GRAPHICS will be specified with the Enable 3D graphics viewer after calculation has completed option toggled "on" (default setting). The keyword and associated string(s) are automatically added to the TGDATA run file by setting and saving the Output - simulator input page appropriately in WizGen. TGRPT 'EDITNNC=editnnc.data' 'TRANX=tranx.data' 'TRANY=trany.data' 'GRAPHICS' / The character string following the '=' sign is the name of the output file into which results will be written. The GRAPHICS parameter is a simple switch and does not require a file name. The parameters can be written in upper, lower or mixed case. The data must be terminated by a slash (/). HINT:- Additional outputs of derived and/or user-defined properties are controlled via TGXRPT keyword. TGSGRM This TransGen keyword has been made redundant in TransGen 3 and has been replaced by an option in the TGFSP keyword. TGSGRM will be recognised by version 3, but TransGen stops with an error report. Across-fault Shale Gouge Ratio combination method This keyword specifies how SGR values calculated at identical positions but on different sides of a fault surface are combined to give the same SGR value to both vertices. The form of the keyword is as follows: TGSGRM method / where method is one of 'hangingwall', 'footwall' or 'average' (note: the parameter must be enclosed in quotes). If 'footwall' is specified the SGR value from the up-thrown side of the fault is used in both vertices, 'hangingwall' causes the down-thrown SGR value to be used. The default is 'average', which means the arithmetic average of the two SGR values is used in both vertices. N.b. where footwall layers are eroded it is recommended that 'hangingwall' is used. Different methods can be defined for different volumes of the reservoir using the BOX/ENDBOX keywords. TGSHALE (new TransGen version 3.1 keyword) Shale Data This TransGen keyword and the associated data only needs to be incorporated in the TGDATA run file (by adding the relevant file on the Included Data page of WizGen) if Clay Smear Potential (in a "Basic project") or any Fault Seal Potential measure (in a "Flexible project") are calculated using the TGSHALE keyword for Shale definition:- see using the Defined shale cells option for Shale definition under CSP options when using either Only CSP or CSP then SGR to calculate fault permeability on the Fault Rock Properties page of WizGen in "Basic project" mode. OR see using Shale definition based on the TGSHALE keyword on the Fault Seal Potential Variables page of WizGen in "Flexible project" mode. The data associated with this keyword determines if a cell should be regarded as shale or not. The keyword should be followed by one non-negative real number of either 1.0 or 0.0 for each cell in the current project where 1.0 represents a shale cell and 0.0 a non-shale cell. Only cells defined as shales are subsequently used to calculate the fault seal potential measure. The data must be terminated by a slash (/). Grid blocks are ordered with the X axis index cycling fastest, followed by the Y and Z axis indices.  Repeat counts may be used for repeated values (e.g. 115*0).  Note that spaces may not be inserted on either side of the asterisk. TGSTRLNE (new TransGen development keyword) Allow the display of streamlines from 3DSL The TranGen keyword is followed by an integer specifying the number of streamlines followed by a slash (/), and block of data for each streamline.   The wells will be displayed when wells are selected.  This keyword is under development and the current limited capability does not reflect what will be available in the future. Each streamline  data block consists of a header record containing an integer specifying the number of nodes in the streamline; a record for each node with X, Y, Z and time of flight, and a final data block terminator consisting of a slash (/). flowed -- TGSTRLNE 997 / -- STREAMLINE=10 NNODES=282 N_SOURCES/SINKS=2 SLTYPE=1 -- NODE=2 WELL=WELL1  LAYER=11 -- NODE=282 WELL=WELL2  LAYER=1 -- X-COORD      Y-COORD      Z-COORD (m)  TOF(days)    BLOCKINDEX 282 / 0.2450000E+04 0.1850000E+04 0.3671200E+04 0.0000000E+00 0.2475225E+04 0.1900000E+04 0.3676210E+04 0.1157407E-04 0.2500000E+04 0.1983561E+04 0.3684583E+04 0.2664420E+03 0.2519080E+04 0.1999988E+04 0.3691049E+04 0.4226107E+03 0.2561148E+04 0.2100012E+04 0.3694734E+04 0.1388542E+04 0.2570230E+04 0.2200023E+04 0.3700764E+04 0.2385265E+04 ... 272 records omitted ... 0.3497699E+04 0.3900000E+04 0.3331850E+04 0.2136167E+07 0.3399813E+04 0.3805615E+04 0.3345406E+04 0.2138803E+07 0.3300188E+04 0.3815180E+04 0.3354544E+04 0.2139157E+07 0.3250000E+04 0.3850000E+04 0.3356975E+04 0.2139157E+07 / TGTDE This keyword has been made redundant in TransGen 3 and has been replaced by the THICK plugin either automatically by WizGen in "Basic Project" mode (see Plugins generated by WizGen in Basic project mode) or created by the user via the User-defined plugins page of WizGen (in "Flexible Project" mode).  The TGTDE keyword will be recognised by version 3, but TransGen stops with an error report. Co-efficients of equation relating displacement to thickness The equation used to calculate fault thickness as a function of fault displacement is: where THICKf and Df are the thickness and displacement at a particular connection vertex.  The constants a and b are the two data items in the TGTDE keyword.  The data must be terminated with a slash (/). If TGTDE is not specified in the run file, the constants a and b default to 0.00588 (1/170) and 1 respectively (following Manzocchi et al 1999). TGTDT This keyword has been made redundant in TransGen 3 and has been replaced by the THICK plugin either automatically by WizGen in "Basic Project" mode (see Plugins generated by WizGen in Basic project mode) or created by the user via the User-defined plugins page of WizGen (in "Flexible Project" mode). The TGTDT keyword will be recognised by version 3, but TransGen stops with an error report. Displacement to thickness lookup table This keyword can be used instead of TGTDE and allows input of a table of paired displacement and thickness values. The thickness of a faulted connection vertex is calculated from this table by linear interpolation. The data is supplied as an even number of paired real values of displacement and thickness. The data must be terminated with a slash (/). e.g. TGTDT 0.1 0.001 1. 0.01 10. 0.1 100. 1.0 etc / TGTHROW (new TransGen version 3.2 keyword) To define User-defined fault throws When using the new Include fault drag and hierarchical zone effects functionality, this TransGen keyword can be used to:- define the locations and throws of  fault trace(s) that do not exist explicitly in the model geometry modify the throw of a trace with an explicit throw in the model geometry. This is not recommended - the TGDRAG keyword, which is associated with a greater range of functionality, is designed to do this. The keyword can be followed by as many definitions as needed on separate lines, each line and the file are terminated by a slash. The format of each line is:- I J `Direction' Throw I and J are the indexes of the cell stacks to which the fault trace is adjacent. Direction can be either `DIR-X' or 'DIR-Y'. The single quotation marks are essential. If the direction is `DIR-X`, the trace lies between the cell stacks [I,J] and [I+1,J], and if it is `DIR-Y', it lies between cell stacks [I,J] and [I,J+1]. Note that traces cannot be defined on the X- and Y- faces of a cell stack - this must be achieved by assigning the trace to the X+ and Y+ faces of the adjacent cell stack. Throw can take both positive and negative values. A negative throw value signifies that the cell stack closer to the model origin lies on the upthrown (footwall) side of the fault, while a positive throw value signifies that it lies on the downthrown (hangingwall) side of the fault. Units are the native units of the TransGen run (meters for metric, feet for field and cm for lab). For example the line:- 12 32 `DIR-X' -23.0 / places a user-defined trace between cell stack [12 32] and [13 32] with the depths of the faces of the former stack being raised by 12.5m and of the latter stack lowered by 12.5 m. If the same trace is specified twice, the two throws are summed. See Processing modified traces (in the section on The revised ViewGen workflow) for details of how the input data are processed to produce a coherent geometrical model. Faults defined using the TGTHROW keyword are processed independently of faults included explicitly in the model geometry. However if a user-defined trace specified with TGTHROW overlies an existing trace in the parent model, ViewGen issues a warning and lists the trace in the TGPRT file. Only the throw specified in the TGTHROW keyword is used to construct the 2D sub-resolution fault throw grid. Example Application of the following listed TGTHROW include file to an initially unfaulted 20 by 20 cell model (Fig a) will result in the coherent sub-resolution fault geometry shown in Figure b. NOTE:- Fig b is shown purely as an example of the operation of the TGTHROW keyword - this display will not be obtained in ViewGen since the parent model (Fig a) remains unfaulted (see Visualising fault drag and/or fault zone data for further discussion). One or more files containing the TGTHROW keyword and others (e.g. TGFZONE, TGDRAG and/or TGTRACE) can be included in the TransGen run via the Included Data page of WizGen, along with all cell and (if used) user-defined connection properties, when running a "Flexible project" with the Include fault drag and hiererchical zone effects option selected. HINT:- The TGTHROW data can be output to file at the end of a TransGen run via the Output - derived and user-defined properties page of WizGen. TGTRACE (new TransGen version 3.2 keyword) Allows the inclusion of user-defined trace properties When using the new Include fault drag and hierarchical zone effects functionality, this TransGen keyword allows the inclusion of to 10 user-defined trace properties for each fault trace (system or user-defined) in the model. These properties can then be used in DRAG and/or FZONE plugins (see The set of trace properties available for use in the DRAG & FZONE plugins). The keyword can be followed by as many definitions as needed on separate lines, each line and the file are terminated by a slash. The format of each line is: I J `Direction' `i1 i2 i3 i4 i5' `d1 d2 d3 d4 d5' / [i1 to i5] are five user-defined properties with integer values and [d1 to d5] are five user-defined properties with non- integer values (floating point numbers). These user-defined trace properties are entirely optional and fewer than five values of each can be specified. For example the line: 12 32 `DIR-X' `11 22 13' `12.322423 0.0001' / assigns to the trace three user-defined integer values and two user-defined floating point values, while the line: 12 32 `DIR-X' `' `12.322423  / uses only one user-defined value which is a floating point number. One or more files containing the TGTRACE keyword and others (e.g. TGFZONE, TGTHROW and/or TGDRAG) can be included in the TransGen run via the Included Data page of WizGen, along with all cell and (if used) user-defined connection properties, when running a project in Flexible mode with the Include fault drag and hiererchical zone effects option selected. HINT:- The TGTRACE data can be output to file at the end of a TransGen run via the Output - derived and user-defined properties page of WizGen. TGVOLERR (new TransGen keyword) Sets a minimum cell volume error tolerance This TransGen keyword sets a precision limit for rejecting badly constructed cells. It is automatically included in the TransGen run file using the Cell volume error tolerance, Lower limits setting on the Miscellaneous Options page of WizGen (default value 1.0e-06).  A grid-block is flagged as inactive by TransGen if any component tetrahedra have a volume of less than minus this value, or the total cell volume is less than this volume. Changing it from a value of 1.0e-06 should only be done in special circumstances. NOTE:- This Cell volume error tolerance cutoff is different from the Eclipse limit on minimum cell pore volumes set by the MINPV keyword which TransGen also recognises (as set by the Cell pore volume cutoff on the same page of WizGen). The keyword should be followed by a record setting the limit, followed by a slash.  TGVOLERR 1.0e-06 / Units: cubic metres (METRIC),  cubic feet (FIELD) or cubic centimetres (LAB). TGVS (new TransGen keyword) Vshale content To use Effective vshale values based on either Vshale only or NTG and Vshale (see Effective vshale computation method on the Fault Rock Properties page of WizGen for a "Basic" TransGen project or the Effective vshale setting on the Fault Seal Potential Variables page of WizGen for a "Flexible" TransGen project), data specifying the Vshale content of each cell needs to be incorporated in the <Project_name>.TGDATA run file. In order to use the vshale data, you need to include the file containing the TGVS keyword and associated Vshale data via the Included Data page of WizGen. The data associated with this TransGen keyword defines the fractional shale content of each grid-block. The keyword should be followed by one non-negative real number (between zero and one inclusive) for every grid block in the current input box specifying the vshale content where 0 indicates no shale content (i.e. pure sand) and 1 indicates 100% shale content.  The data must be terminated by a slash (/). Grid blocks are ordered with the X axis index cycling fastest, followed by the Y and Z axis indices.  Repeat counts may be used for repeated values (e.g. 15*0.7).  Note that spaces may not be inserted on either side of the asterisk. TGVS -----this is actually Vshale. 0.292 0.281 0.312 0.352 0.302 0.33 0.309 0.381 0.296 0.332 0.301 0.3 0.264 0.301 0.261 0.256 ... ... 0.785 0.773 0.796 0.778 / TGWELL (new TransGen keyword) Well specification data This TransGen keyword provides a limited version of the Eclipse COMPDAT keyword. TGWELL is followed by any number of records, each record terminated by a slash (/).  A single record can be used to define several connections within a well, as long as the well is situated in the same vertical column of grid blocks.  A deviated well can be defined to exist in several columns of grid blocks, but each column will require a separate record. The set of records must end with a blank record, containing only a slash (/). Item 1  Well name (enclosed in quotes). Item2  I - location of connecting grid block(s) (there is no default, see below). Item 3  J - location of connecting grid block(s) (there is no default, see below). Item 4  K - location of upper connecting block in this set of data. Item 5 K - location of lower connecting block in this set of data. Item 6 Integer specifying if well is a producer (1) or injector (0) Transgen only supports the items listed above, and will ignore any other data in the record.  No defaults are assumed because Transgen does not support the Eclipse WELSPECS keyword.  TGWELL is only used by the graphics module to show well positions - the well data is not used in any calculations. e.g. TGWELL 'well1'   4   5   1   7   1 / 'well1'   4   6   8   11   1 / 'well2'   13   34   1   10   0 / / TGXRPT (new TransGen keyword) Extended output options from TransGen This TransGen keyword is generated when output file(s) are specified for one or more properties on the Output - derived and user-defined properties page of WizGen in Flexible project mode. The keyword is followed by several arguments that control which and where the output is written. The derived connection properties are the additional variables derived for each connection during calculation of  transmissibilities. All connections across faults (neighbour and non-neighbour) are included in each output file. Other connection and/or cell properties associated with user-defined keywords can also be output. New to the TransGen version 3.2 release, derived Trace properties, i.e. TGTRACE, TGDRAG, TGTHROW, TGFZONE, TGXTRACE allow the user to output fault trace information from a TransGen run including fault drag and/or sub-resolution zone effects. The extra output is not intended for inclusion in the parent simulation model, but uses the same format as the Eclipse EDITNNC keyword (without forward slashes). The keyword supplements the TGRPT keyword which controls the output of files for input back into the Eclipse (or MoReS or More) simulation.  These additional output files can easily be imported into a spreadsheet or similar application. Each selected parameter together with its intended destination output file is added as a string enclosed in quotes below the TGXRPT keyword in the TGDATA run file, e.g.:- TGXRPT 'FAULTS=faults.out' 'AREA=area.out' 'PERM=perm.out' 'sgr=sgr.out' / The character string following the '=' sign is the name of the output file into which results will be written. The data must be terminated by a slash (/). The properties that can be output are:- Derived Connection properties FAULTS - an Eclipse format FAULTS file (TransGen will automatically find the faults) TRMULT - Transmissibility multipliers calculated for each cell-cell connection AREA - Area of connection for each cell-cell connection (only if modified via the AREA plugin) FTRANS - Faulted transmissibilities for each cell-cell connection UFTRANS - Unfaulted transmissibilities for each cell-cell connection (transmissibility including fault juxtaposition, but excluding any fault-rock thickness) PERM - Fault permeability for each cell-cell connection THICK - Fault-rock thickness for each cell-cell connection THROW - Fault throw for each cell-cell connection FSP measures - any FSP measures calculated in the current run, e.g. csp_yielding, csp_fulljames, sgr values can each be output to data files Derived Trace properties (New to the TranGen version 3.2 release when including fault drag/zone effects in a TransGen "Flexible project") TGTRACE - to output user-defined trace properties for those traces modified via the TGTRACE input file. TGDRAG - to output drag trace data for those traces where the drag ratio is not equal to 1.0. TGTHROW - to output user-defined throw values for those traces where the throw is not equal to 0.0. TGFZONE - to output all TGFZONE data included in the current run. TGXTRACE - to output summary information on every fault trace (system or user-defined) in the current model User-defined keywords (connections & cells) User-defined keywords - any cell and/or connection properties generated to user-defined keywords in current run can each be output to data files. TGXSECT (new TransGen keyword) Specify a cross-section (fence diagram) within the TransGen model This TransGen keyword is followed by any number of records, each specifying a block face within the model.  Every I,J position along the fence diagram must be specified, not just the positions of the corners or 'fence posts'.  Each face is defined by the I, J position of the block and the face name (enclosed in quotes).  The cross-section contains all the blocks in the K ('vertical') direction.  The face name indicates which edge of the block is displayed: either parallel to the X or Y axis, and either nearer(-) or further(+) from the grid origin. The default is '+' which implies the edge furthest from the grid origin; e.g. 'X' is equivalent to 'X+' and means Each record must be terminated with a forward slash (/) and the end of data is indicated by an empty record i.e. a record containing only a forward slash(/). TGXSECT 1 1 'X' / 1 2 'X' / 1 2 'Y-' / / If a cross-section is defined it may be visualised in the graphics viewer. The cross-section is not used in any calculations and TGXSECT is used only in visualisation. TGXTRACE (new TransGen version 3.2 keyword to output data when including fault drag & hierarchical zone effects in Flexible project mode) Output data containing summary info of every fault trace in the model When using the new Include fault drag and hierarchical zone effects functionality, this TransGen keyword can be used to output data summarising information on every fault trace (system and user-defined) in the current TransGen model via the Output - derived and user-defined properties page of WizGen in Flexible project mode. This file cannot subsequently be reloaded into a TransGen run. The file lists 7 items per trace. These are:- Trace location System throw on the trace User-defined throw Drag ratio Fault zone flag (1 if a fault zone is present, 0 if not) Trace length Trace width These properties are discussed and defined in Trace Properties in the section on Traces and Fault zones. Note that the system throw is the throw on the trace contained in the input ZCORN file, while the user-defined throw is that value included in the TGTHROW keyword (or, although not recommended, calculated in the DRAG or FZONE plugins). The aveThrow variable available for use in plugins (via User-defined plugins page of WizGen) and displayed in the Graphics windows (see Visualising fault drag and/or fault zone data) is the sum of these two values. TITLE Identify the TransGen run The keyword is followed by a text record, up to 80 characters long, used to identify a TransGen run.  If a title is given it is incorporated into any output files requested using the keyword TGRPT. TRANX X direction transmissibilities The data associated with the TRANX Eclipse keyword can be output from TransGen providing faulted transmissibilities for X-neighbour connections, which can be subsequently used in Eclipse to overwrite the X direction transmissibility for the +X face of each specified grid block.  A value specified for block (I , J, K) is the transmissibility between blocks (I, J, K) and (I+1, J, K).  The form of the keyword output by TransGen is as follows:- BOX IX1 IX2 JY1 JY2 KZ1 KZ2 / TRANX tx1 tx2 tx3 ... / The current release of TransGen only outputs TRANX in boxes where IX1 = IX2, JY1 = JY2. This output file together with the EDITNNC, TRANY files (and NNC file- if the new fault drag and hierarchical zone effects were incorporated in the TransGen model) should be included in the EDIT section of the Eclipse input file. NOTE:- If the current TransGen run includes fault drag and hierarchical zone effects (new to version 3.2 release), the output X direction transmissibilities may be rather different. Specifically they can contain:- Many values of 0.0. These are for connections that exist in the parent model, but are not formed by the user-defined geometrical modifications to the fault trace. A value of zero in the file is necessary for these connections, if they were omitted from the file, the simulator would use the default unfaulted transmissibility for these connections. Values for connections that do not exist in the parent model. These can be formed for a variety of reasons, e.g. a user-defined fault on an unfaulted trace (the value in the file will be zero if the user-defined throw on this fault exceeds the height of the cells), or neighbour connections that are not formed in the parent model, but are formed in the user-defined model (e.g. because a drag-ratio has lowered the throw of the fault). TRANY Y direction transmissibilities The data associated with the TRANY Eclipse keyword can be output from TransGen providing faulted transmissibility values for Y-neighbour connections, which can be subsequently used in Eclipse to overwrite the Y direction transmissibility for the +Y face of each specified grid block.  A value specified for block (I , J, K) is the transmissibility between blocks (I, J, K) and (I, J+1, K).  The form of the keyword output by TransGen is as follows:- BOX IX1 IX2 JY1 JY2 KZ1 KZ2 / TRANY ty1 ty2 ty3 ... / The current release of TransGen only outputs TRANY in boxes where IX1 = IX2, JY1 = JY2. This output file together with the EDITNNC, TRANX files (and NNC file- if the new fault drag and hierarchical zone effects were incorporated in the TransGen model) should be included in the EDIT section of the Eclipse input file. NOTE:- If the current TransGen run includes fault drag and hierarchical zone effects (new to version 3.2 release), the output Y direction transmissibilities may be rather different. Specifically they can contain:- Many values of 0.0. These are for connections that exist in the parent model, but are not formed by the user-defined geometrical modifications to the fault trace. A value of zero in the file is necessary for these connections, if they were omitted from the file, the simulator would use the default unfaulted transmissibility for these connections. Values for connections that do not exist in the parent model. These can be formed for a variety of reasons, e.g. a user-defined fault on an unfaulted trace (the value in the file will be zero if the user-defined throw on this fault exceeds the height of the cells), or neighbour connections that are not formed in the parent model, but are formed in the user-defined model (e.g. because a drag-ratio has lowered the throw of the fault). UNITS Specify measurement units This keyword is followed by a parameter (enclosed in quotes) which specifies if measurements are based on 'metric', 'field' or 'lab'.  The parameter must be followed with a slash (/). UNITS: m (METRIC), ft (FIELD), cm (LAB) NOTE:- New to TranGen version 3, the TGMETRIC keyword defines the units of displacement and fault seal potential measures (TGFSP) as metric when the UNITS keyword is not set. ZCORN Depths of grid block corners Each grid block has 8 corners.   This Eclipse keyword enables the depths of each corner of each grid block to be separately specified.  It is used for specifying depths for corner point geometry. This keyword and associated data must be included in TransGen run file (together with the DIMENS and COORD keyword data) in order to load and view the parent model in TransGen. The keyword line is then followed by                                2 *  NDIVIX  *  2  *  NDIVIY  *  2  *  NDIVIZ values, with the two corners in the i direction, and so on.  The last value is followed by a slash (/).  If a BOX keyword has been used prior to ZCORN, the ZCORN data should only apply to the current BOX.  The keyword must be followed by                                    2 *  NDX  * 2  *  NDY  *  2  *  NDZ values, where NDX, NDY, and NDZ are the dimensions of the current box. [UP] [TOP] [HOME]");sQ1[54]=new Array("TGmanual/45.html","Starting modules from the command line","","[UP] [TOP] [HOME] [TOC] STARTING MODULES FROM THE COMMAND LINE It is possible to start the modules directly at the command prompt:  ViewGen, FileGen, WizGen All the modules, except transgen use a command of the form: % <module name> <project> <project directory> Where <project name> is the basename of the PROJECT.TGDATA file.            <project directory> is the directory containing the PROJECT.TGDATA file            <session file>    is the name of a saved session file i.e.: % filegen <project name> <project directory> % wizgen <project name> <project directory> % viewgen <project name> <project directory> % viewgen <project name> <project directory> <session file> For example: % filegen ANDY /disk1/TransGen_Data One situation where this may be required is when ViewGen is used without graphical output to calculate fault properties for a number of stochastic realisations in a batch job. TransGen The TransGen control bar can be started by either: % transgen or by taking a path and project as a parameter in the form: % transgen <project directory>/<project>.TGDATA which starts TransGen and loads the project specified into the control bar. e.g. % transgen /disk1/TransGen_Data/ANDY.TGDATA [UP] [TOP] [HOME] [TOC]");sQ1[55]=new Array("TGmanual/77.html","Examples","","[UP] [TOP] [HOME] FAULT CONTROLS EXAMPLES The default view is to show the currently selected fault property at reservoir connections. Switching on an outline for the connections emphasizes the connection polygons.  Connections only exist where cells are juxtaposed against active cells.  The cells of layer 9 are inactive and no fault property is drawn.  Similarly no connection exists when a cell is faulted against a region above or beneath the reservoir model. The connection polygons are also shown clearly by the connection outlines alone. Fault properties are only drawn at reservoir - reservoir overlaps  The outlines of the upthown  and downthrown sides of the fault show the full extents of the upthrown and downthrown sides of the fault.  This shows the extents of cells that are faulted against regions outside the limits of the reservoir. Cell properties for the upthrown and downthrown sides of the fault can also be displayed.  In the example below, the cell property for the upthrown side of the faults are drawn (plus outlines) together with an outline only for the downthrown side.  Connection properties (i.e. fault properties) are deselected, so no fault property is drawn in the area of overlap.  Connection (fault) properties are shown in preference to cell properties at reservoir / reservoir overlaps. The juxtapositions of the main flow units can be selected by showing these layers.  Here they are coloured by the cell property on the upthrown and downthrown sides.  If a connection property was selected, the connections of these units would be coloured by a fault property.  A single fault was selected spatially by columns and rows, or if a FAULTS file is loaded, faults can be selected by name. [UP] [TOP] [HOME]");sQ1[56]=new Array("TGmanual/86.html","Using WizGen in Basic Project mode","","[UP] [NEXT] [TOP] [HOME] Using WizGen in Basic Project mode Having selected the operating mode (i.e. Basic Project) on the Title page, WizGen leads the user through the process of making a complete TransGen run file (<Project>.TGDATA) simply by clicking on the Next >> button after completing each stage, as described below. NOTE:- It is recommended that WizGen is used to construct/edit the TGDATA run file as hand-editing can easily lead to mistakes. When the TGDATA run file is completed to your satisfaction, click on the ViewGen icon in the Control Menu to initiate the calculations and to display the results in the ViewGen graphics window - see section on Viewing the model and calculating output for details. Title page To select Basic Project mode and/or set the title of the current Project. Coordinate system page To specify the coordinate system defining the layout of the input data, to input the number of columns, rows and layers in the model and optionally to change the units of measurement used in the project Included Data page To choose which data files are included in the current TransGen run. Miscellaneous Options page To optionally change the default cutoff limits and/or tolerances used to exclude data from the calculations and/or to run TransGen without calculating the fault properties, e.g. to check the input data in ViewGen. Fault Rock Properties page To determine how the fault-rock permeability and hence faulted transmissibility data are calculated as a function of two fault seal potential measures (Shale Gouge Ratio and/or Clay Smear Potential), displacement and fault-rock thickness. Output - simulator input page To specify output options and destination files for the calculated faulted transmissibility data for inclusion into the parent simulator model. Project (TGDATA) File To view the current contents of the TGDATA run file. Session Log To view the Session Log generated by the last ViewGen run. Contents page To view/edit any of the current WizGen contents, to inspect the project's TGDATA file and/or to inspect the session log generated by last TransGen calculation. [UP] [NEXT] [TOP] [HOME]");sQ1[57]=new Array("TGmanual/87.html","Using WizGen in Heavy Project Mode","","[PREV] [UP] [TOP] [HOME] [TOC] Using WizGen in Heavy Project mode This operating mode, new to TransGen 3.0, allows expert users far greater flexibility in modelling fault rock properties for inclusion in flow simulation models. The user can interact directly with the internal code to define user-specific algorithms foe defining fault rock thickness and permeability. Miscellaneous Options page In `Heavy' mode, the NTG Discretisation are currently inoperative (greyed-out). This functionality will be implemented, sometime in the future, to select where shale is positioned within cells. The FSP units control (in `Heavy' mode only) allows the user to alter the units for outputting Fault Seal Potential measures from the default in metres to native units, i.e. in feet if Units set to FIELD or in centimetres if Units set to LAB (as set on the Coordinate System page). With the default FSPs in metric selected, the TGMETRIC keyword (new to TransGen 3) is automatically added to the TGDATA run file. With the TGMETRIC keyword included (activated), fault displacement, fault rock thickness and all calculated Fault Seal Potential measures are reported (both graphically & in output files) and stored internally within TransGen using metres as the unit of length. When the alternative FSPs in native units is selected, the TGMETRIC keyword is omitted from the TGDATA file. With the TGMETRIC keyword missing from the TGDATA runfile, all fault displacement, fault rock thickness and all calculated FSP measures are reported in the units of length appropriate to the Units specified on Coordinate System page of WizGen, i.e. feet if the Units are FIELD or cm if the Units are LAB. Inclusion or exclusion of the TGMETRIC keyword makes absolutely no difference if the Units in the TGDATA run file are METRIC. NOTE:- When using WizGen in `Light' mode, the TGMETRIC keyword is ALWAYS included in the TGDATA files. Depth is not affected by the keyword which is always displayed and stored internally in the units of length appropriate to the TGDATA file. The purpose of the TGMETRIC keyword is to ensure plugins are transportable between different UNITS conventions. Clay Smear Potential (CSP) for example has the dimensions of length. If the UNITS in TGDATA are set to FIELD, then CSP will be reported in metres if TGMETRIC is present and in feet if it is not. With the TGMETRIC keyword included (i.e. activated), this means a PERM plugin with a particular sealing threshold applied to CSP will not need to be changed if the same plugin is used in a reservoir model of another field which has been built using a different UNITS convention. If TGMETRIC is not included (in Heavy Project mode only), many plugins will be specific to the UNITS convention for which they have been written. Inclusion/exclusion of the TGMETRIC keyword does not influence the transmissibility calculation; dimensions of fault thickness are always converted back to the specified units system before transmissibilities are calculated ensuring consistency of units in the TRANX and TRANY files. [PREV] [UP] [TOP] [HOME] [TOC]");sQ1[58]=new Array("TGmanual/88.html","Using WizGen in Flexible Project mode","","[PREV] [UP] [TOP] [HOME] Using WizGen in Flexible project mode Having selected the Flexible project operating mode on the Title page, WizGen leads the user through the process of making a complete TransGen run file (<Project>.TGDATA) simply by clicking on the Next >> button after completing each stage, as described below. NOTE:- It is strongly recommended that WizGen is always used to construct/edit the TGDATA run file as hand-editing can easily lead to mistakes. When the TGDATA run file is completed to your satisfaction, click on the ViewGen icon in the Control Menu to initiate the calculations and to display the input model and the results in the ViewGen graphics window - see section on Viewing the model and calculating output for details. Title page To select Flexible project mode, possibly also include EITHER two-phase fault rock calculations OR fault drag & hierarchical zone effects. Coordinate System page To specify the layout of the input data, define the number of Columns, Rows & Layers and set appropriate units of measurement. User-defined keywords page To define new keywords for cell or connection properties. Included Data page To choose which data files are included in the current TransGen run. Miscellaneous Options page To optionally set FSP units and/or alter lower cutoff limits. To run the model without performing calculations, i.e. to view the input data in ViewGen. Fault Seal Potential Variables page To define the fault seal potential variables for calculating up to 5 FSP measures for the fault rock. User-defined plugins page To create and modify user-defined calculation modules (plugins). NOTE:- A PERM plugin to calculate fault permeability from one or more Fault Seal Potential measures plus a THICK plugin to calculate fault-rock thickness from displacement are essential for calculating faulted Transmissibility multipliers. Output - simulator input page To specify output options and destination files for input into Eclipse, MoReS (for Shell users) and/or More (Roxar Modular Oil Reservoir Evaluation) simulation models. Output - derived and user-defined properties page To output derived fault connection, trace properties and/or data calculated for user-defined keywords to file. The following 2 pages can only be accessed if the TransGen installation is licensed for the sub-resolution fault-zone structure functionality (new to the TransGen 3.2 release) and if the Include fault drag and hierarchical zone effects option has been toggled "on" via the Title page in WizGen in Flexible project mode. Drag applied to fault traces page To allow for the inclusion of uncertainty in fault throw or of local geological drag on all faults traces in the model. Hierarchical fault zone definition page To allow the construction of heirarchical fault zones, e.g. a fault represented as a continuous discontinuity in the reservoir simulation model can be segmented at a sub-resolution scale as a hierarchy of unbreached and breached relays. The following 3 pages can only be accessed if the TransGen installation is licensed for the Two Phase Flow module and if the Include two-phase fault rock calculations option has been toggled "on" via the Title page in WizGen in Flexible project mode. Two phase flow - INPUT page To define the two-phase flow input parameters including the file containing relative permeability tables, the keyword defining the source of across-fault flow rates and the fluid property settings including the oil-water contact. Two phase flow - FAULT ROCK PROPERTIES page To view/edit the fault-rock properties equations used to calculate relative permeabilities for water and oil. Two phase flow - GROUPINGS & OUTPUT page To set groupings and specify destinations for two-phase flow output files. Project (TGDATA) File To view the current settings in the TGDATA run file. Session Log To view the Session log generated by the last run made with ViewGen. Contents page To view/edit any of the current WizGen page contents, to view the current TGDATA file and/or the Session log generated by last TransGen calculation. [PREV] [UP] [TOP] [HOME]");sQ1[59]=new Array("TGmanual/89.html","FSP calculation in TransGen Version 3","","[UP] [NEXT] [TOP] [HOME] FSP calculations in TransGen Version 3 The TGFSP keyword in the TGDATA runfile can be followed by up to 5 Fault Seal Potential definitions including for example any of the following:- basic Shale Gouge Ratio, Clay Smear Potential (Yielding et al. 1997), Clay Smear Potential (Fulljames et al. 1997), Vshale weighted Clay Smear Potential, Shale Smear Factor (Lindsay et al. 1993), Shale Smear Factor for multiple shale beds, Distance-weighted variants on SGR. The instructions for each FSP measure in the TGFSP keyword string are based on the general equation:- The introduction of shale faces in the FSP calculations is a significant conceptual difference between the Shale Gouge Ratio (SGR) in TransGen Version 2 and the FSP calculation in Version 3. In Version 2, SGR is calculated as a function of the faulted faces of all the cells in the model that have slipped past the vertex of the connection being processed. In Version 3, a subset of these faces (which can include none or all of them) are designated shale faces (i.e. EffectiveVshale) and only these shale faces are used in the FSP calculation. The Figure below shows a cartoon of a simple 2D model with dipping COORD lines. Cells that have been designated shales are shown in brown, while non-shales which are not therefore included in the FSP calculation are shown in yellow. For each of the four shale faces (1 to 4), the figure shows the definition of Throw (D), Thickness (t) and Effective Vshale (eVs) included in the FSP equation. Figure (b) shows the the three possible definitions of the Distance term for a calculation on the vertex highlighted with a red dot.  NOTE:-The Throw term is not necessarily the same for the 4 shale faces - for example if there is stratigraphic growth across the fault and these Throws can differ from the fault displacement of the vertex, calculated from the Throw in the hangingwall and the the Throw in the footwall. These displacements are functions of the vertex being processed, rather than of the shale layers that have passed this vertex. By default, TransGen reports the FSP measures in 3D, by measuring all distances, thicknesses and throws parallel to the COORD lines bounding the faulted connection faces as shown in Figures (a) and (b) above. TransGen assumes implicitly, therefore, that the displacement vector of the fault is parallel to the COORD lines used to construct the 3D model geometry. By changing the Plunge correction option to Strike projection, the FSP measures can be reported on a vertical projection of the fault. The definition of throw (D), thickness (t) and distance (d) terms in the FSP calculation using this option are shown in Figure (c) above. However this option is NOT available for Fault displacement which is always reported in 3D. If desired, the vertical component of fault displacement can be calculated in a thickness plugin. [UP] [NEXT] [TOP] [HOME]");sQ1[60]=new Array("TGmanual/90.html","Title page","","[UP] [TOP] [HOME] Title Page Having selected the Flexible project option on the Title page of WizGen, as shown below, the following options are accessible:- Include fault drag and hierarchical zone effects - optionally to model user-defined and stochastically-generated fault zone structure and to include the effects of these sub-resolution geometrical fault characteristics in the single-phase flow simulator. Include two-phase fault rock calculations - optionally to incorporate methodology taking into account dynamic two phase changes in water/oil saturations in the fault-rock that occur during reservoir production (instead of the default single phase treatment of faults where the multipliers act indiscriminately on all fluid phases). Next >> - to access the next page (i.e. Coordinate System page) in the sequential process to set up the <Project_Name>.TGDATA run file. Contents -  to view/edit the Contents page, i.e. any or all the current settings in the TGDATA run file, to inspect the project's TGDATA file and/or to inspect the log generated by the last TransGen calculation. Save - to save the current settings of WizGen to the project's TGDATA run file. Quit - to exit from WizGen with or without saving any changes to the <Project_name>.TGDATA run file. Set the title for this project - to modify the project title. Include fault drag and hierarchical zone effects option Toggle the Include fault drag and hierarchical zone effects option "on" (default setting "off") if you want to include the effects of sub-resolution geometrical fault characteristics in the single-phase flow simulator such as:- the effects of user-defined faults not included explicitly in the geometry of the simulation model. the uncertainty in fault throw or of local geological drag on faults included explicitly in the simulation model. inclusion of fault relay zones and other forms of locally-paired slip surfaces on faults included in the input model as single surfaces. If this option is toggled "on" and the feature is currently licensed, two extra pages (i.e. the Drag applied to fault traces & Hierarchical fault zone definition pages) are automatically added to WizGen. HINT:- Much of the new functionality is associated with a new type of TransGen object called a faulted trace - see section on Traces and Fault zones for details. NOTE:- This separately licensed new geometrical functionality operates only on single-phase properties. Although TransGen can be run combining both this and the two-phase fault rock functionality, it will be internally contradictory. Combining the two sets of functionality is therefore NOT recommended. Include two-phase fault rock calculations option If the Include two-phase fault rock calculations option is toggled "on" (default setting "off") and the two-phase software feature is currently licensed, three additional pages are automatically added to WizGen, i.e. the Two phase flow- Input, Fault Rock Properties and Groupings & Output pages. These additional pages allow specification of all the necessary parameters and values required by ViewGen and 2PhaseGen to generate two-phase fault rock properties. Set the title for this project Optionally to change the TransGen project name, click in the white window where you wish to add or delete new characters from the name and update as required or double click to select the current name and type in new project name, e.g. PUNQ_2-phase as shown below. The title is incorporated into any output files requested using the keyword TGRPT. With the Flexible project option toggled "on" (and optionally also either the Include fault drag and hierarchical zone effects or Include two-phase fault rock calculations option):- Continue the workflow by clicking on Next >> to view/edit the Coordinate System page. Alternatively, click on Contents to view/modify any or all of the current Contents of the previously saved TGDATA file for the current Flexible project, inspect the project's TGDATA file and/or inspect the log generated by last TransGen calculation for the current project. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. [UP] [TOP] [HOME]");sQ1[61]=new Array("TGmanual/91.html","Coordinate System page","","[UP] [TOP] [HOME] Coordinate System page This is the Next >> page accessed in WizGen from the Title page or by selecting the Goto... button for Specify the coordinate system containing the input data from the Contents page. It allows the user to specify the layout of the input data. TransGen uses the Eclipse standard ordering by default, as shown above. The ordering of data in the Eclipse standard and RMS output is always in row order.  In the Eclipse standard,  the origin of the model (Row 1, Column 1) is at the top left of the model.  Rows increase downwards, and the XY coordinates which define the position of the COORD lines are given relative to the model origin, with Y increasing downwards. However, in other models the position of the origin, and the direction in which rows and columns increase may differ.  (RMS for example, provides many options to output the data in different ways.)  Also, the co-ordinates that defined the positions of the COORD lines may be given as a local coordinate system relative to the model origin (as per Eclipse), or relative to a geographic origin with Y increasing upwards (the RMS default). The appropriate system must be selected; if  incorrect,  the model will either be mirrored or the cells will be inactivated as they have a negative volume. A diagram in map view, showing the nature of the Coordinate system is shown for each of the options. The position of the origin is shown by a blue diamond Rows are shown by bold red arrows, row numbers increasing with the length of the arrow Columns are shown thinner arrows, column numbers increasing with the length of the arrow The directions in which the X and Y coordinates increase are shown by black lines.  These coordinates are used to define the position of the COORD lines. HINT:- System 3 RMS with real world coordinates (with Y increasing upwards) is a common form of RMS output. Defining the Coordinate System 1. Either retain the System 1 Eclipse standard (default) or select the relevant coordinate layout for the input data. This setting defines the parameters for the TGAXES keyword in the TGDATA run file. 2. If the TransGen project has already been worked on in Basic project mode, the number of Columns, Rows and Layers in the Project will be automatically included. However, if the project is accessed for the first time in Flexible project mode, the settings will be blank and MUST be entered by the user. These settings will define the parameters for the DIMENS or SPECGRID keyword in the TGDATA runfile. 3. Optionally change the default Units setting from METRIC (i.e. in metres) to either FIELD (i.e. in feet) or LAB (i.e. in centimetres). This sets the units of measurement assumed in the project and sets the METRIC, FIELD or LAB keyword in the TGDATA run file. To continue the workflow, click on Next >> to view/edit the User-defined keywords page. Alternatively, click on the << Back button to return to the Title page to view/edit the title for the current Flexible project and/or to EITHER Include fault drag and hierarchical zone effects OR Include two-phase fault rock calculations in the current runfile. Or click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. [UP] [TOP] [HOME]");sQ1[62]=new Array("TGmanual/92.html","User-defined keywords page","","[UP] [TOP] [HOME] User-defined keywords page This is the Next >> page accessed via WizGen in Flexible project mode from the Coordinate System page or by selecting the Goto... button for Define new keywords for cell or connection properties from the Contents page. Up to 10 new Cell Property and/or 5 new Connection Property keywords can be added to allow the inclusion of user-defined properties in the calculations performed by TransGen. Each new keyword added on this page is appended to the TGNEWKEY keyword string in the TGDATA runfile. Examples of the need for User-defined keywords To import new user-defined cell or connection properties into the model; the new properties are identified as keywords which can then be entered on the Included Data page. To define new cell or connection properties for use in FSP and/or User-defined plugins. See Example below where User-defined keywords are used to build a FSP measure via the CELLPROP plugin. To graphically display (or output to file) cell/connection properties in ViewGen which are not automatically available, e.g. effective vshales associated with a particular Fault Seal Potential measure and/or which cells are designated as shales in the current model run. NOTE:- In TransGen Version 2, the item Effective Vshale appeared in the cell properties pulldown menu in the graphical interface. In Version 3 there is no longer necessarily a unique value of Effective Vshale in each grid-block, since each FSP measure (up to 5 of which can be included in a single TransGen run) can be based on a different definition of Effective Vshale. Therefore, if graphical display of an Effective Vshale associated with a particular FSP is required, it must be defined as a user-defined cell property. 1. Input required Cell and/or Connection Properties Click on the relevant Property type (Cell Property is selected by default) and type an appropriate name. For example, the keywords evs1 and binary_shale have been input as 2 new Cell Properties. Up to 10 new user-defined Cell Property and 5 new Connection Property keywords can be added. Each name can be up to 32 characters long and may contain underscores (_) and numbers as well as letters. However, the first character of the name MUST be a letter. HINT:- The letters can be either upper or lower case or a mixture of both.  If the property is used in a plugin (to calculate a FSP measure or in a user-defined plugin), remember C++ is case sensitive and all prefix and property names should be used in lower case. 2. Save to TGDATA runfile Click on the Save button at the bottom right of the page to add the TGNEWKEY to the TGDATA run file with following strings:- TGNEWKEY 'evs1' 1 / 'binary_shale' 1 / / Once user-defined cell or connection properties have been defined by keywords added on this page, they can be included in the TransGen run in exactly the same way as standard grid-block properties such as ntg, tgvs, permx, permy (via the Included Data page of WizGen) and/or used in a FSP measure (via the Fault Seal Potential Variables page of WizGen) and/or in a User-defined plugin (via User-defined plugin page of WizGen as shown in the example below), output as data files (via the Output page) and visualised in the graphics interface. Using the two-phase flow functionality If you are licensed to use the Two-phase flow module and have chosen to Include two-phase fault rock calculations (via Title page of WizGen) in the current TransGen run, the property used to declare the across-fault flow rates must be declared on the User-defined keywords page and the associated file loaded via the Included data page. The across-fault flow rates are either loaded as a user-defined fault property, i.e. a single value of across-fault flow rate (Darcy velocity) loaded for each connection or calculated from a grid of cell pressures loaded as a user-defined cell property. In the example shown below, keywords for both these methods of calculating across-fault flow rates have been added to the User-defined keywords page. Each of these keywords appears as the first entry in the relevant data file which then needs to be added to the Included Data page of WizGen. Including User-defined fault trace properties If you are licensed to use this new functionality and have chosen to Include fault drag and hierarchical zone effects (via Title page of WizGen) in the current TransGen run, up to 10 user-defined fault trace properties can be declared as keywords on the User-defined keywords page and the associated file(s) containing the keyword(s) and properties loaded via the Included Data page (for further details see Trace Properties in the section on Traces and Fault zones). To continue the workflow, click on Next >> to view/edit the Included Data page. Alternatively, click on the << Back button to return to the Coordinate System page to view/edit the title for the current project. Or click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. Example of calculating user-defined cell properties in the CELLPROP plugin [UP] [TOP] [HOME]");sQ1[63]=new Array("TGmanual/93.html","Included Data page","","[UP] [TOP] [HOME] Included Data page This is the Next >> page accessed in WizGen from the User-defined keywords page or by selecting the Goto... button for Choose which data files are included from the Contents page. The relevant input data blocks created via FileGen should be included in the TransGen project runfile (i.e. <project>.TGDATA).  Additional data may also be included at this stage. NOTE:- If the current TransGen Project is opened for the first time in "Flexible project" mode, the Included Data page will initially be blank as shown below. However, if it has already been worked on as a "Basic project" which has been upgraded to a "Flexible project", the Included Data page will automatically show the data files added previously. Adding Data Files 1. To add a data file, click on the top Browse... button to open a file selection window, shown below. 2. Navigate to the <project>_INPUT directory (e.g. F64_New_INPUT) and click on a file, e.g. COORD.DATA to select it. 3. Click on OK to load the selected file into the Included Data window of WizGen. 4. Repeat to add all other files. Data to include In order to load and view a model, the data associated with the following Eclipse keywords MUST be in the first two files added to the Included Data page of WizGen:- COORD                            - to define the map position of the cell corners ZCORN                             - to define the depth of the cell corners Additionally, in order to view cell and fault properties and to generate transmissibility multipliers, the data associated with the following keywords are required:- PERMX and PERMY     - to define cell permeabilities NTG or TGVS or both     - to define the shale content of the cells MULTX and MULTY      - to import grid-block-based transmissibility multipliers from Eclipse (new to TransGen version 3 - see section on Including Transmissibility Multipliers from Eclipse for details) To run the Two-Phase Flow module, the data associated with the following keyword must also be included:- SATNUM                         - to access a set of relative permeability and capillary pressure curves for each cell in the model Other possible data files to include are those associated with keywords that modify the data arrays (ADD, COPY, EQUALS, MULTIPLY) if these are present in the original Eclipse run file to ensure TransGen uses the same data as Eclipse. Similarly, if any of keywords that control which cells are active (i.e. ACTNUM, MINPV, MINPVV, PORO) are present in the Eclipse run file, these should also be included to ensure TransGen identifies the same cell/cell connections as Eclipse. Optionally, the data files associated with the keywords PERMZ, FAULTS, TGWELL, TGSTRLNE, MULTZ , TGXSECT can be added for visualisation purposes. If you are proposing to calculate any Fault Seal Potential measure using Shale definition based on the TGSHALE keyword (see Shale definition setting on the Fault Seal Potential Variables page), the file containing the TGSHALE keyword and associated data (values for every cell with 1 representing a shale cell and 0 a non-shale cell) must be included on this page of WizGen Heavy. User-defined Cell Property file(s) Once appropriate User-defined keywords have been defined, user-defined cell properties can be included in the TransGen run in exactly the same way as standard grid-block properties (e.g. NTG, PERMX, TGVS). The include file for a user-defined Cell Property file with the keyword cell_property1 in a 300 grid-block model might be:- cell_property1 100*0.02 100*23 100*0.1 / This file can then be attached to the TransGen run on the Included Data page of WizGen in the same way as the other files. If values of a user-defined cell property are read into TransGen (rather than calculated in a plugin) it is essential that values are included for each cell in the model. If there are 100 cells in the model, there must be 100 values provided with the keyword or TransGen will stop with an error message. If you are proposing to use the Two-phase module, a source of across-fault flow rates must be included. To calculate the across-fault flow rates from a grid of cell pressures, the relevant Cell Property keyword (e.g. CELL_PRESSURE) must be declared on the User-defined keywords page and the associated data file loaded by adding it to the Included Data page. The Cell Pressure input file (e.g. cell_pressure.txt) should include a grid of cell pressures where the units are bars (METRIC), psi (FIELD) or atm (LAB). Example:- CELL_PRESSURE --at 2 years, using PDO U. 265.23  264.91    266.45  266.19    266.16  265.78    265.69  265.58 265.51  265.24    265.14  266.75    298.17  302.67    304.21  305.56 306.7   307.81   309.13   310.6    312.16  313.78    315.23  316.04 330.31  330.31    330.31  330.31    330.31  330.31    330.31  330.31 330.31  330.31    330.31  330.31    330.31  330.31    330.31  330.31 ... 278.24  277.72    277.21  276.78    276.46  276.27    276.19  276.27 276.53  276.94    277.61  278.53    279.57  280.61    281.56  282.36 282.91  283.01    282.65  281.98    281.11  280.1 278.95 277.59 276.06  274.51    273.05  271.66    270.31  268.91    267.7   266.84 265.89  264.77    263.86  262.83    262.45  262.52    262.74  337.77 / User-defined Connection Property file(s) Once appropriate User-defined keywords have been defined, user-defined connection properties can be imported into the TransGen model. The format for the imported connection data is based on that used to export connection data using the TGXRPT keyword, i.e. each line of data in the file refers to one connection, contains 7 items and is terminated by a slash (/). The total list of connections is then terminated by another slash. The line: I1 J1 K1 I2 J2 K2 value / therefore refers to a faulted connection between cells (I1, J1, K1) and (I2, J2, K2) and an include file for a user-defined connection CON_PROP1 might look like:- CON_PROP1 1 1 2 2 1 5 0.7453 / 1 1 2 2 1 6 0.67 / 1 1 2 2 1 7 0.112 / / Both neighbour and non-neighbour connections can be included in the file; TransGen only discriminating between these connection types when outputting the EDITTNNC, TRANX and TRANY Eclipse include files. If the user-defined connection file contains reference to non-existent or unfaulted connections (i.e. connections between grid-blocks without explicit displacements across them defined in the ZCORN file) they are ignored by TransGen and a warning message is issued. It is not required that all faulted connections have data values associated with them when using a new user-defined connection keyword; if a connection does not have a value specified in the input, the value for that connection defaults to -1.0, the value assigned to "undefined" connections. NOTE:- User-defined connection properties are only stored as connection averages within TransGen, i.e. as c.user_defined_connection. Whereas most other connection properties calculated by TransGen are stored both as connection vertex properties (e.g. v.fsp1) and as average connection properties (e.g. c.thick). Similarly if you are proposing to use the Two-phase module, a source of across-fault flow rates must be included. If the source of across-fault flow rates is via a user-defined fault property, i.e. a single value of across-fault flow rate (Darcy velocity) loaded for each connection, the relevant Connection Property keyword (e.g. DARCY_VEL) must be declared on the User-defined keywords page and the associated data file loaded by adding it to the Included Data page. The Darcy Velocity input file (e.g. darcy_vel.txt) should include the following data with a positive value for the Darcy Velocity signifying a flow from cell I1 J1 K1 to cell I2 J2 K2 and a negative value indicating flow from cell I2 J2 K2 to cell I1 J1 K1 and the units of across-fault Darcy velocity in metres/day (METRIC), ft/day (FIELD) or cm/hour (LAB). Example:- DARCY_VEL ---I1  J1  K1  I2  J2  K2  VALUE 1   7    1   2    7   4    -0.001894186    / 1   7    1   2    7   5    -0.003168526    / 1   7    1   2    7   6    -0.00079227 / 1   7    1   2    7   7    -0.001143496    / 1   7    2   2    7   5    -0.002235422    / 1   7    2   2    7   6    -0.000294127    / 1   7    2   2    7   7    -0.00055016 / 1   7    2   2    7   8    -0.000810556    / 1   7    3   2    7   6    0.000233575 / 1   7    3   2    7   7    6.15184E-05 / ... 36  111   20   36   112  12    -0.064336965    / 36  111   20   36   112  13    -0.071158179    / 36  111   20   36   112  14    -0.079036781    / 36  111   20   36   112  15    -0.086137624    / 36  111   20   36   112  16    -0.101391355    / / Data to include when using the new Fault Trace and Zone functionality If you are licensed to use the new TG version 3.2 functionality and have toggled the Include fault drag and hierarchical zone effects option "on" (via the Title page of WizGen), files containing the following new keywords and associated data can be included on this page. TGTHROW - to define the location and throws of new user-defined fault traces (i.e. to include additional sub-resolution traces) in the model. TGFZONE - to include new user-defined fault zone(s) in the model. TGDRAG - to manually define throw modifications on any or all fault traces (system or user-defined) in the model. TGTRACE - to include up to 10 user-defined trace properties for any or all fault traces (system or user-defined) in the model. In the example shown below the first eight files include data on the cell geometries and cell properties, while the final four files include the new trace-related keywords and associated user-defined data. HINT:- Fault traces are automatically recognised by ViewGen from the geometry of the input model. These fault traces contained explicitly in the parent model geometry (termed system traces) do NOT need to be included as data files. Similarly each system trace has, by default, a single fault zone associated with it which can then have structure applied via the Hierarchical fault zone definition page of WizGen. When all the relevant  files have been added, click on the Next>> button to view/edit Miscellaneous Options page. Alternatively, click on the << Back button to return to the User-defined keywords page to view/edit the layout of the input data, the number of Rows, Columns and Layers in the current project and the Units setting. Or click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. Including Transmissibility Multipliers from Eclipse [UP] [TOP] [HOME]");sQ1[64]=new Array("TGmanual/94.html","Miscellaneous Options page","","[UP] [TOP] [HOME] Miscellaneous Options page This is the Next >> page accessed in WizGen from the Included Data page or by selecting the Goto... button for Miscellaneous options from the Contents page. The options currently available on this page to Flexible project users are:- to alter the FSP units from the default "metric" units to "native" units set on the Coordinate System  page of WizGen. to optionally change the Lower limits settings. to toggle "on" the option Do not perform calculation to just view the current input data. The NTG Discretisation options are currently inoperative (greyed-out). This functionality will be implemented, sometime in the future, to select where shale is positioned within cells. FSP units The FSP units control allows the user to alter the units for outputting Fault Seal Potential measures from the default in metres to native units, i.e. to feet if Units set to FIELD or to centimetres if Units set to LAB (as set on the Coordinate System page). With the default FSPs in metric selected, the TGMETRIC keyword (new to TransGen 3) is automatically added to the TGDATA run file. With the TGMETRIC keyword included (activated), fault displacement, fault rock thickness and all calculated Fault Seal Potential measures are reported (both graphically & in output files) and stored internally within TransGen using metres as the unit of length. NOTE:- The FSP units control is automatically locked to FSPs in metric "on" if the Include fault drag and hierarchical zone effects option has been selected on the Title page of WizGen. HINT:- Depth is not affected by the TGMETRIC keyword which is always displayed and stored internally in the units of length appropriate to the TGDATA file. The purpose of the TGMETRIC keyword is to ensure plugins are transportable between different UNITS conventions. Clay Smear Potential (CSP) for example has the dimensions of length. If the UNITS in TGDATA run file are set to FIELD, then CSP will be reported in metres if TGMETRIC is present and in feet if it is not. With the TGMETRIC keyword included (i.e. activated), this means a PERM plugin with a particular sealing threshold applied to CSP will not need to be changed if the same plugin is used in another reservoir modelwhich has been built using a different UNITS convention. When the alternative FSPs in native units is selected, the TGMETRIC keyword is omitted from the TGDATA file. With the TGMETRIC keyword missing from the TGDATA runfile, all fault displacement, fault rock thickness and all calculated FSP measures are reported in the units of length appropriate to the Units specified on Coordinate System page of WizGen, i.e. feet if the Units are FIELD or cm if the Units are LAB. Inclusion or exclusion of the TGMETRIC keyword makes absolutely no difference if the Units specified on the Coordinate System page are METRIC. If TGMETRIC is omitted by selecting the FSPs in native units, many plugins will be specific to the UNITS convention for which they have been written. Inclusion/exclusion of the TGMETRIC keyword does not influence the transmissibility calculation; dimensions of fault thickness are always converted back to the specified units system before transmissibilities are calculated ensuring consistency of units in the TRANX and TRANY files. Lower limits Unfaulted transmissibility cutoff:- any connection with an unfaulted transmissibility value less than the specified cutoff value will be ignored by TransGen. It defines the TGMINTR keyword in the TGDATA run file and follows the default value used in Eclipse which ignores connections with transmissibilities less than 1.0e-06. This cutoff is provided to allow TransGen to match Eclipse behaviour and should only be changed from the default value to mirror changes in the parent simulator run file. Cell volume error tolerance:- this cutoff is used by TransGen as a precision limit for rejecting badly constructed cells and defines the TGVOLERR keyword in the TGDATA run file.  It is different from the Eclipse limit of minimum cell pore volumes (Eclipse MINPV keyword) which TransGen also recognises.  A cell is flagged as inactive by TransGen, if any component tetrahedra have a volume of less than minus this value or the total cell volume is less than this volume. Cell pore volume cut-off:- this cutoff defines the MINPV keyword in the TGDATA run file, which is then used by TransGen to render inactive any cells which have a pore volume less than the defined threshold. This cutoff is provided to allow TransGen to match Eclipse behaviour and should only be changed from the default value (1.0e-06) to mirror changes in the simulator run file. HINT:- Only change these default Lower limits either to reflect changes from the defaults in the parent Eclipse run file or in the case of Cell volume error tolerance to change the limit used to identify and exclude geometrically corrupt cells from the calculations in TransGen. Do not perform calculation By default, the Do not perform calculation option is toggled "off", i.e. Fault Seal Potential measures on the Fault Seal Potential Variables page of WizGen will automatically be calculated when ViewGen is selected for the generated TGDATA run file. If you want to use ViewGen to just view the geometry of the current TransGen model prior to running any FSP and Transmissibility multiplier calculations, click on the button to turn the Do not perform calculation option "on". When the Miscellaneous Options page is set as required, click on the Next>> button to view/edit the Fault Seal Potential Variables page. Alternatively, click on the << Back button to return to the Included Data page to view/edit the data included in the current runfile. Or click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. [UP] [TOP] [HOME]");sQ1[65]=new Array("TGmanual/95.html","Fault Seal Potential Variables page","","[UP] [TOP] [HOME] Fault Seal Potential Variables page This is the Next >> page accessed in WizGen (in "Flexible project" mode) from the Miscellaneous Options page or by selecting the Goto... button for Define fault seal potential variables from the Contents page. The Fault Seal Potential Variables page of WizGen offers options to:- set the instructions for calculating up to 5 Fault Seal Potential (FSP) measures for the fault wall rock in a single Transgen run. The settings on this page of WizGen are used to construct the TGFSP string in the TGDATA runfile. It is recommended that the TGFSP strings are constructed/edited via this page in WizGen, rather than hand-editing the TGDATA file which can easily lead to mistakes. NOTE:- If the current TransGen Project has already been worked on as a "Basic project" which has been upgraded to a "Flexible project", the Current FSP setting will be either csp or sgr (as shown below) as set on the Fault Rock Properties page of WizGen in "Basic project" mode. Whereas, if the Project is accessed for the first time in "Flexible project" mode, no FSPs will exist and the page will initially be blank - select the the File, New option, enter a new FSP name and then continue to set the variables as shown below. The settings on this page in WizGen set the TGFSP keyword record in the TGDATA runfile. The TGFSP keyword can be followed by up to 5 Fault Seal Potential definitions including, for example, any of the following:- basic Shale Gouge Ratio, Clay Smear Potential (Yielding et al. 1997), Clay Smear Potential (Fulljames et al. 1997), Vshale weighted Clay Smear Potential, Shale Smear Factor (Lindsay et al. 1993), Shale Smear Factor for multiple shale beds. The instructions for each FSP measure in the TGFSP keyword are based on the general equation:- together with the choice of Combination option, Effective Vshale, Shale definition and Plunge correction settings. See section on FSP calculation in TransGen Version 3 for full details. NOTE:- Which Fault Seal Potential measure(s) are then used to calculate fault permeability and hence transmissibility multipliers are user-defined in the PERM plugin on the next page of WizGen Heavy (see User-defined plugins page). Adding/Editing Fault Seal Potential measures All Fault Seal definitions are added as Plugins Files under the TGFSP keyword in the TGDATA runfile via the File, New option on the Fault Seal Potential Variables page. 1. Enter new FSP name: Click on the current File setting at the top of the Fault Seal Potential Variables page to access the following drop-down menu. Click on New to open the Plugin prompt window. Click in the currently empty box and type in the required new FSP name, e.g. csp_yielding NOTE:- The name should be input in lower case and can include any combination of letters and numbers, but without spaces. The name will be the first item of each FSP definition below the TGFSP keyword in the TGDATA runfile. Click on OK to close the Plugin prompt returning to the Fault Seal Potential Variables page of WizGen where the Current FSP box has been updated to the new FSP name. NOTE:- All values and settings changed and saved on the page will be applied to the Current FSP. Selecting an alternative Current FSP, as shown below, will update the contents of the Fault Seal Potential Variables page. 2. Input/Edit Equation constants Having created a new FSP file name or selected an existing FSP file for editing, you need to input/edit appropriate Equation constants where:- Exponent l is the power to which "throw" is raised. Exponent m is the power to which "thickness" of a shale source bed is raised. Exponent n is the power to which "distance" is raised. Exponent p is the power to which "eVshale" (i.e. the effective Vshale content) is raised. Valid values need to be input for each Equation constant. Even parameter(s) not needed in a particular FSP measure (e.g. Distance for Shale Gouge Ratio or Throw and Effective Vshale for Clay Smear Potential) must have a valid exponent, i.e. set an exponent to 0.0 to exclude that parameter and all associated settings from the current FSP measure. So, for example for Clay Smear Potential, the Equation constants should be set as shown below, given CSP is defined as:- NOTE:- When an exponent is set to zero, the options for that particular component are irrelevant to the calculation. However, all associated settings must still be defined, e.g. even if exponent p is set to 0.0 as above in a CSP equation, a valid Effective vshale setting must be selected (even though never used), otherwise ViewGen using the generatedTGDATA runfile will stop with an error message. These Equation constants will define settings 2-5 in the 12 setting definition added for each FSP definition below the TGFSP keyword in the TGDATA runfile. See the section on the TGFSP keyword for further details. 3. Select appropriate Distance option When the Current FSP is Clay Smear Potential, it is important to select the correct Distance options setting:- For CSP after Yielding et al. 1997 this method uses Centre of beds as the distance option. For CSP after Fulljames et al. 1997, the distances are measured to the Far-side of beds. NOTE:- Selecting the Near-side of beds option can result in incalculable connections between two non-shale layers if the N exponent is set to < 0.0 (for example as in CSP calculations), resulting in FSP values of infinity at certain connection vertices. This problem has been overcome by introducing the concept of "undefined" vertices and connections - see section on Inactive FSP values. 4. Select Combination option The setting selected defines the precise way the summation in the FSP calculation is performed. Maximum from layers then sum With this option selected, the FSP term (as defined by the other settings on the Fault Seal Potential Variables page) for each shale layer in the footwall and hangingwall are compared and the maximum value from each layer is included in the summations. This option is recommended by Yielding et al. (1997) for calculating Clay Smear Potential. So, for example, where two shale layers a and b have been displaced past a particular vertex on a fault, if the FSP Term for shale layer a is greater in the hangingwall than in the footwall, while the same FSP Term for shale layer b is greater in the footwall, then the final FSP calculated at the vertex is:- FSP = hwFSPa + fwFSPb In certain instances this method can result in numerical ambiguities, in which case TransGen will issue an error warning and stop. HINT:- Do not use this Combination option setting with the Shale definition set to either Effective Vshale cutoff or Based on user-property as these introduce ambiguity into the FSP calculation, resulting in the TransGen run failing with an error message. See Invalid FSP options in the section on Issues associated with FSP calculations. Sum layers then take maximum With this option selected, the FSP terms are summed independently in the hangingwall and footwall sides of the fault. The final FSP is then the larger of these two values. This combine option is used in the definition of Clay Smear Potential published by Fulljames et al. (1997). Maximum value No summation of the individual FSP terms for the shale layers displaced past a particular vertex on a fault. The final FSP value is the maximum calculated for that vertex. Minimum value No summation of the individual FSP terms for the shale layers displaced past a particular vertex on a fault. The final FSP value is the minimum calculated for that vertex. Mean value The final FSP is the average of all the individual FSP terms for all the shale layers displaced past a particular vertex on a fault. Sum layers then take average With this option selected, the FSP terms are summed independently in the hangingwall and footwall sides of the fault. The final FSP is then the average of these two values. Sum in footwall The final FSP is the sum of the individual FSP terms for all the shale layers displaced past a particular vertex in the footwall of the fault. Sum in hangingwall The final FSP is the sum of the individual FSP terms for all the shale layers displaced past a particular vertex in the hangingwall of the fault. 5. Select Effective vshale method Which grid blocks are treated as shales in the current FSP measure depend on the Effective Vshale (Evshale) values of the grid blocks. The Effective vshale can be calculated in one of the 4 following methods dependant on the availability of Net-to-Gross and/or Vshale data or another User property:- HINT:- A valid Effective vshale setting must be selected even if evshale is not used in the current Equation, i.e. when Exponent p = 0 such as in the calculation of Clay Smear Potential. Net-to-gross only - TransGen considers the non-net region to be shale and takes the shale content to equal 1 minus the Net-to-Gross value (where Net-to-Gross is the ratio of the net thickness of good reservoir, i.e. sand to gross interval thickness). eVs = (1 - NTG) Vshale only - TransGen takes Vshale as the shale content. eVs = TGVS NGT and VShale - TransGen assumes the non-net region to be pure shale and takes the Effective Vshale content of a grid block to be:- eVs = (1 - NTG) + (TGVS x NTG) User Property - Transgen takes the user-defined Effective Vshale grid values assigned to a user-defined keyword. These values should all ideally lie between 0.0 and 1.0. If the user-defined Effective Vshale grid contains values less than 0.0 or greater than 1.0, these values will still be included in the FSP calculation, but the results cannot be guaranteed meaningful. Meaningful FSP values are assumed to have a range from zero to infinity and all numbers entering the summation are either zero or positive. Select the appropriate option, depending whether Net-to-Gross (NTG) and/or  Vshale (TGVS) data or a User property to define shale content has been included for the current Project (see Included Data page). 6. Set the Plunge correction switch By default, TransGen reports the FSP measures in 3D (i.e. Three dimensional option "on"), by measuring all distances, thicknesses and throws parallel to the COORD lines bounding the faulted connection faces. TransGen assumes implicitly, therefore, that the displacement vector of the fault is parallel to the COORD lines used to construct the 3D model geometry. By selecting the alternative Strike projection option, the FSP measures can be reported on a vertical projection of the fault. HINT:- To see how the throw, thickness and distance terms used in FSP calculations are measured, see Figures (a) and (b) for the default Three dimensional setting and Figure (c) for the Strike Projection setting in the section on FSP calculation in TransGen Version 3. 7. Set Shale definition This setting defines which cells to use in the Current FSP calculation. Shale faces (see the section on FSP calculation in TransGen Version 3) are not constructed for non-shale cells. Non-shale cells are simply ignored in the FSP calculation. NOTE:- To correctly calculate the values of FSP measures based on the concept of discrete shale layers (e.g. CSP), Shale face bunching is used to combine multiple, vertically adjacent shale faces into a single face for use in the FSP calculation. This operation (described in the section on Issues associated with FSP calculations) is ALWAYS applied, EXCEPT when the Shale definition is Based on all cells. Select the option appropriate to the Current FSP using the following as a guide:- Based on all cells With this option selected, every cell is treated as shale, with the FSP calculation being equivalent to that performed for Shale Gouge Ratio in TransGen Version 2. Selection of this option automatically deactivates shale bunching. Layers With this option selected, named layers define the cells treated as shales. This setting is necessary when calculating Clay Smear Potential as per Yielding et al. 1997. The named layers should be input as a list separated by commas. Multiple adjacent layers can be defined by a hyphen separating the first and last of these layers, e.g. `1,2,3,5,7,8,9,10' can be input as `1-3,5,7-10'. The list can be up to 256 characters long. Spaces are ignored (indeed spaces are removed by WizGen to shorten the length of the string). Effective Vshale cutoff Select this option and input an Effective Vshale cutoff value (e.g. 0.5) to be applied to the Effective vshale values defined by the current Effective vshale setting. Cells with eVs below the specified cutoff are designated shale cells and used in the current FSP calculation. TGSHALE keyword Select this option to use data defining the shale (set to 1) or non-shale (set to 0) status of every cell in the current model. Only shale cells are used in the current Fault Seal Potential calculation. NOTE:- To use this option, the file containing the TGSHALE keyword and all the associated data must be added to the TGDATA run file via the Included Data page. User-property Select this option to use a user-defined keyword to assign shale cells. The keyword must have been added via the User-defined keywords page and the file headed by this keyword and including binary values of 0.0 or 1.0 (or any other value) for each cell in the current model included via the Included Data page. Any user-supplied grid cell value that is non-zero is considered to represent a shale. 8. Add other FSPs to be calculated Return to point 1 and repeat the procedure to include up to 5 FSP calculations in the current TGDATA run file. Refer to section on Typical Fault Seal Potential Variable settings to calculate Shale Gouge Ratio, Clay Smear Potential as per either Yielding or Fulljames, Shale Smear Factor as per Lindsay or combining multiple shale beds. 9. Manage the FSPs via the File options The 'File' pulldown menu in the top left corner of the page controls how FSPs are created, destroyed and stored. The menu contains 4 entries:-  New, Save, Library and Remove. Select New to input a name for a new FSP. Select Save to save the Current FSP definition to the FSP library file. This file is stored in the user's home directory (file location is <HOME>/.transgen/fsp.lib). The 'fsp.lib' file contains the user's favourite FSP definitions that can be stored and retrieved when required. A corporate  fsp.lib  file may be created and copied into each user's home directory. Select Library to open up a list box containing the user's stored FSP definitions. The box would be similar to this: A selected entry can be deleted from the library or loaded into the FSP page. Select Remove to remove the current FSP from the TGDATA file and from the list of selectable Current FSPs - displayed top right of page (the previous FSP, if one exists, becomes the Current FSP). If there are no FSPs defined on the page, all the controls become insensitive except the File menu which allows a new FSP to be created or loaded from the library. When the Fault Seal Potential Variables page is set as required, click on the Next>> button to view/edit the User-defined plugins page. Alternatively, click on the << Back button to return to the Miscellaneous Options page to view/edit the Lower limits for Multiplier and/or Cell volume cutoff and whether to perform calculation or not via ViewGen. Or click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. FSP calculation in TransGen Version 3 Issues associated with FSP calculations Typical Fault Seal Potential Variable settings [UP] [TOP] [HOME]");sQ1[66]=new Array("TGmanual/97.html","User-defined plugins page","","[UP] [TOP] [HOME] User-defined plugins page This is the Next >> page accessed in WizGen (in "Flexible project" mode) from the Fault Seal Potential Variables page or by selecting the Goto... button for Add and modify user-defined calculation modules (plugins) from the Contents page. The User-defined plugins page of WizGen allows the user to:- create plugin(s) that manipulate the values of cell and connection properties, e.g. to input user-specific algorithms for defining fault rock thickness and fault rock permeability. optionally create up to nine 2Phase plugins to calculate fault rock properties (the user can specify if a particular two-phase relationship should be based on an equation or a plugin via the Two phase flow - page 2 of WizGen). optionally create DRAG and/or FZONE plugins to define drag on fault traces and/or to model sub-grid block fault effects based on user-defined criteria. Initially this page of WizGen opens with the current THICK plugin displayed which will either be that copied from the automatically generated THICK plugin having converted the current TransGen project from "Basic" to "Flexible project" mode or the default THICK plugin for a TransGen project created from new in "Flexible project" mode as shown below. A Plugin is a macro, written in C++, that manipulates the value of existing cell and connection properties. There are four types of plugin which can be used during TransGen calculations (in Flexible project mode), i.e. CELLPROP, THICK, PERM, AREA plugins, of which two (THICK and PERM plugins) are essential, i.e. Fault-rock thickness and fault permeability MUST be calculated at each vertex in a fault connection via the THICK and PERM plugins in order to calculate the faulted transmissibilities. ViewGen will stop with an error message if the THICK and PERM plugins are not supplied. The CELLPROP and AREA plugins are not essential. It is important to appreciate the order in which plugins are run: first CELLPROP, then THICK, then PERM and finally AREA. CELLPROP plugin The principle purpose of the CELLPROP plugin is to specify user-defined algorithms for determining:- (a) the effective Vshale of cells for a particular FSP calculation (b) the cells designated as the shale faces for a particular FSP calculation However, any user-defined cell property can be modified in the plugin, e.g. a user-defined cell property could be created by combining other cell data. See example of using the CELLPROP plugin. NOTE:- The CELLPROP plugin runs early on in the TransGen calculation, after all the include files have been read in and the geometry of the cells has been calculated, but before any faults have been identified. Therefore, fault properties cannot be used in a CELLPROP plugin. THICK & PERM plugins These plugins are called at every vertex of every active faulted connection in the model, i.e. only cells adjacent to faults are used in calculations in these plugins.  The THICK plugin calculates the thickness of the fault rock at each vertex of a fault connection. The PERM plugin calculates the permeability of the fault rock at each vertex in a fault connection. Both these plugins MUST be included in the TGDATA run file. The THICK AND PERM plugins should operate principally on vertices. Fault connection information is available if required (e.g. the direction of the connection, user-defined connection properties). HINT:- As a general rule, user-defined cell properties should not be updated in the THICK and PERM plugins. NOTE:- Most connection properties calculated by TransGen are stored internally both as connection vertex properties (e.g. v.fsp1) and as average connection properties (e.g. c.thick). The exception is the connection area, for which a value at the vertex is meaningless. However, user-defined connection properties are only stored as connection averages (e.g. as c.user_defined_connection). There is therefore no v.user_defined_connection definition for use in plugins. AREA plugin This plugin allows manipulation of the area of fault connection in the model and is called just prior to calculation of faulted transmissibility. An AREA plugin cannot access vertex properties as they are not referenced at this point of the TransGen calculations. See section on Using Plugins in TransGen for further details. 2Phase plugins When the Include two-phase fault rock calculations option is toggled "on" (via the Title page), three extra pages are added to WizGen and on the second page of these (Two phase flow - FAULT ROCK PROPERTIES) the user can specify if a particular two-phase relationship should be based on an Equation or a user-defined Plugin. When the user selects the Plugin option to define a particular fault rock property, the relevant new plugin complete with default code (i.e. using the equation setting) is added to the User-defined plugins page. Any or all of the following 9 user-defined plugins can be used in the two-phase flow module:- PORO_FR plugin - to calculate fault rock porosity SWOR plugin - to calculate water saturation at irreducible oil SWC plugin - to calculate connate water saturation PC_D and PC_I plugins - to calculate capillary pressure in the drainage and imbibition cycles respectively KRW_D and KRW_I plugins - to calculate relative permeability of water in the drainage and imbibition cycles respectively KRO_D and KRO_I plugins - to calculate relative permeability of oil in the drainage and imbibition cycles respectively See the section on Defining Two-phase flow plugins for further details. Fault drag and hierarchical zone effect plugins When the Include fault drag and hierarchical zone effect plugins option is toggled "on" (via the Title page), two extra pages (Drag applied to fault traces & Hierarchical fault zone definition) are added to WizGen. On these new pages, the user can choose to define either drag on fault traces and/or to model sub-grid block fault effects according to user-defined criteria in the DRAG and/or FZONE plugin(s). When the user selects the Use a plugin option, the following new plugins complete with default code are added to the User-defined plugins page:- FZONE plugin - to allow the incorporation of sub-grid block fault effects DRAG plugin - to allow modelling of drag on fault traces Creating User-defined plugins Fault permeability and fault rock thickness, which are essential to the transmissibility calculations performed in TransGen, MUST be calculated in the PERM and THICK plugins respectively. Other properties can also be calculated in plugins, but there is no obligation to do so. There are default THICK and PERM plugins which can be used as un-edited or modified as required. 1. Select Function Click on the arrow key to the right of the current Function to access and select from the list, e.g. the THICK function has been chosen to create a plugin to calculate fault rock thickness from displacement. NOTE:- Up to 9 two-phase flow plugins (as shown below) are added to the Function list when the user sets any of the Two phase flow - Fault Rock Properties to be based on a Plugin rather than an Equation. NOTE:- The DRAG and/or FZONE plugin functions are accessible via the Function list provided the Use a plugin option is selected on the Drag applied to fault traces and/or Hierarchical fault zone definition pages of WizGen. The plugin code can be altered to model the drag on fault traces and/or attach sub-grid resolution fault zones to fault traces according to user-defined criteria. 2. View/edit default THICK plugin With the Function set to THICK, the default THICK plugin is displayed as shown below. The default THICK macro displayed in the User-defined plugins window, as shown above, will act in the same way as the default THICK plugin automatically written by WizGen in "Basic project" mode, i.e. fault rock thickness is calculated at each vertex of each faulted connection according to the following expressions:- If the displacement is less than the defined minimum of 0.001 (i.e. 1mm in metric units), then:- This cutoff value is included to prevent a thickness at a vertex with zero displacement being set to zero, which would in turn prevent an area-weighted harmonic average being calculated for this connection. Otherwise fault rock thickness is calculated at each connection vertex as a function of displacement where the constants `a' and `b' are 0.005882 and 1 respectively:- You can use the default code unaltered or modify it using section on C++ language use in plugins for guidance. Cell and Fault variables must be referred to in plugins using the correct format. This is prefix.property where the prefix identifies which internally stored array is being referenced and the property tells C++ which of the internally stored values associated with a particular cell or fault connection is being referenced, e.g. v.displ is the vertex property fault displacement and v.thick is the vertex property fault thickness (see section on Prefix options and properties available to different plugins for further details). The currently selected Function determines which of the 3 boxes at the bottom right of the page (as shown below) are active for the selection of allowed 2Phase, Cell or Fault variables which can be used in the plugins. So for example, with the plugin Function set to THICK, only the Cell or Fault buttons are active.  To include the Fault variable for displacement in the plugin code, select the relevant position in the code after the relevant fault prefix (e.g. v. for vertex property) and then click on the Fault displ option as shown below. 3. Build Plugin When the plugin appears to be correct, click on the Build button at the top of the User-defined plugins page. If there are any identifiable errors in the C++ code or if incorrect variable(s) and/or illegal variable prefixes have been used, error message(s) will be displayed in the window. Click on Return to code to re-display and correct the code. On successful completion, the "Build Successful" message will be displayed (as shown below). Click on Return to code to re-display code. 4. Save Plugin Click on the Save File option to save the compiled plugin to the default file name (<project_name>THICK.cpp) in the subdirectory <project_name>INPUT/.plugin of the current project area. The File menu contains 4 options:- Open - to choose an existing plugin file and to display the source code in the User-defined plugins window. This source code can be associated with another plugin type, i.e. CELLPROP, THICK, PERM or AREA and/or edited, compiled (via Build option) and saved to a different plugin filename. Save - to save any changes to the plugin source code to the file name currently displayed bottom left of the page (e.g. Triangle_PERM.cpp) in the <Project_name>_INPUT/.plugins subdirectory of the current TransGen Project area. Save As - to save the plugin source code to a different user-defined filename and/or directory. By default, the file selection dialog opens at a directory under the user's home directory called .transgen/plugins. This directory is created the first time TransGen is executed and simply provides a convenient place to store plugins - they may be stored anywhere including a directory common to a group of users who might want to share plugins. Remove - to erase the contents of the text edit window for either a AREA or CELLPROP Function plugin. The *.cpp file is not deleted and can be re-accessed via the Open option. This option cannot be used for either a THICK or PERM Function plugin as both are needed for a successful TransGen run as shown in the Error message pop-up. 5. Repeat process to create PERM plugin Select the PERM Function to access the current plugin code. The default code (as shown below) simply sets all fault rock permeabilities to 1mD. You can use this default code or you can input different code to calculate fault rock permeability as a function of, for example, Shale Gouge Ratio (SGR) using the following expression:- NOTE:- The SGR must be defined as a FSP measure via the Fault Seal Potential Variables page of WizGen. HINT:- If the PERM plugin uses any FSP measure which does NOT use all faces as shale faces (i.e. all models in which the Shale definition is NOT set to Based on all cells), care must be taken to ensure permeabilities for undefined (i.e. incalculable) FSP values are assigned appropriate values. Refer to Inactive FSP values in the section on Issues associated with FSP calculations for further details. Click on Build to compile the newly input code. When the new plugin has been successfully compiled, click on Return to code and then on Save to save the plugin as <project_name>_PERM.cpp in the <project_name_INPUT/.plugin subdirectory of the project area.  6. Save plugin settings to TGDATA file When all the required Plugin(s) have input, built and saved to file(s), click on the Save button (bottom right of window) to add the TGPLUGIN Keyword to the <Project>.TGDATA file, as shown below. The TGPLUGIN Keyword is followed by single quotes (one string to a line) that associate a plugin name with the full C++ source filename, where the source file contains the plugin code, e.g. --<PLUGINS+> `THICK=/home/TGprojects/<project_name>/<project_name>_INPUT/.plugins/<project_name>THICK.cpp' `PERM=/home/TGprojects/<project_name>/<project_name>_INPUT/.plugins/<project_name>PERM.cpp' / --<PLUGINS-> Optionally defining Two-phase flow plugins If any of the petrophysical fault rock properties in the Two phase flow module are set to be calculated via Plugin (rather than via the default Equation - as set on the Two phase flow - FAULT ROCK PROPERTIES page), refer to the following section to define these plugin(s). Defining Two-phase flow plugins Optionally defining Drag applied to Fault Traces and/or Fault Zone hierarchy via plugins If the Use a plugin option is selected on either or both of the new WizGen pages (Drag applied to fault traces and/or Hierarchical fault zone definition) to apply stochastic and/or deterministic drag to fault traces and/or define sub-grid block fault zone structure, refer to the following sections to define these plugin(s). DRAG plugin FZONE plugin When the THICK and PERM Plugins and optionally any other Plugin the user wants to use in the current TransGen run are set as required, click on Save and then on the Next>> button in the User-defined plugins page to view/edit the Output - simulator input page. Alternatively, click on the << Back button to return to the Fault Seal Potential Variables page. Or click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. Using Plugins in TransGen Prefix and Property options for plugins C++ language use in plugins C++ functionality in DRAG & FZONE plugins [UP] [TOP] [HOME]");sQ1[67]=new Array("TGmanual/98.html","Output - simulator input page","","[UP] [TOP] [HOME] Output - simulator input page This is the Next >> page accessed in WizGen in Flexible project mode from the User-defined plugins page or by selecting the Goto... button for Specify simulator output options from the Contents page. The primary purpose of TransGen is to calculate simulator include files which are representative of the properties and structure of the faults in the model. This page allows the user to specify the output of the calculation results generated by running the current TGDATA file via ViewGen to files suitable for inclusion in the parent model which will be one of the following:- Eclipse simulator MoReS simulator (for Shell users only) MORE simulator (the Roxar Modular Oil Reservoir Evaluation simulator) HINT:- You may not initially want to output any files until you have viewed and perhaps recalculated the fault properties via ViewGen. By default, the results that the ViewGen module of TransGen generates, are output to the graphical window., i.e. the Enable 3D graphics viewer after calculation option is toggled "on", as shown bottom left of the page. This is optional as ViewGen can be run as a batch process. The graphical output may be toggled on or off.  A green box and a tick is shown when graphical output is enabled: The file output is activated by inputting directory/filename target either by typing the full pathname/filename in the relevant box or by selecting the appropriate Browse... button to open a File selection window in which to navigate to the required OUTPUT directory and select/input output file name, as shown below for the Transmissibility data files editnnc.txt, tranx.txt and trany.txt. Directories can be selected by double-clicking with <MB1> in the Directories box ( the directory ending with two dots means go up a level).  Existing files can be selected by double-clicking with <MB1> in the Files box.  A new file can be created by appending a new filename to the existing (or reselected path in the Selection box).  Press OK to proceed, or Cancel to drop the changes.  This will return control to the Output page of WizGen. In the example shown above, the following Eclipse-format Transmissibility data files have been selected for output from TransGen (for subsequent inclusion in the Eclipse parent model):- EDITNNC file - Transmissibility multipliers for all faulted non-neighbour connections TRANX file - X-direction transmissibilities for all faulted neighbour connections TRANY file - Y-direction transmissibilities for all faulted neighbour connections NNC file - Transmissibilities for all faulted non-neighbour connections not in the original parent model, but generated via the new fault drag and hierarchical zone functionality. NOTE:- The NNC file output option for the Eclipse simulator is new to the TransGen version 3.2 release. It is only relevant when including fault drag and sub-resolution fault zone effects in the simulation model, i.e. with the Include fault drag and hierarchical zone effects option toggled "on" via the Title page of WizGen in "Flexible project" mode. Otherwise the NCC output option will be "greyed-out" and unsettable. When the Output settings are saved to the TGDATA run file, they are added as strings below the TGRPT keyword, as shown below:- --<OUTPUTS+> TGRPT 'EDITNNC=/output_directory/editnnc.txt' 'TRANX=/output_directory/tranx.txt' 'TRANY=/output_directory/trany.txt' 'GRAPHICS' / --<OUTPUTS-> With these Output settings, the graphical display will be activated when ViewGen is successfully run using the saved TGDATA file and the Transmissibility data will be exported to the files as specified to be input into the Eclipse model. When the Output - simulator input page is set as required, click on the Next >> button to view/edit the Output - derived and user-defined properties page. Alternatively, click on the << Back button to return to the User-defined plugins page. Or click on the Contents button to access the Contents page to view/edit any of the current WizGen page settings, inspect the current TGDATA file or the session log generated by last ViewGen calculation. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. [UP] [TOP] [HOME]");sQ1[68]=new Array("TGmanual/99.html","Confirm TGDATA file page","","[PREV] [UP] [TOP] [HOME] [TOC] Confirm TGDATA file page This is the Next >> page accessed in WizGen Heavy from the Output page or by clicking on the << Back button three times on the Contents page. By this stage, the input to the TGDATA run file should be complete and a confirmation window will appear.  The runfile needs to be saved before it can be used in ViewGen to view the input model and perform the specified calculations.  Click on either the Confirm or Save button to save the current TGDATA file settings. Saving the results of the WizGen session: Click on the Confirm button to save the <Project>.TGDATA file and exit from WizGen; allowing ViewGen to be run to visualise the model and perform the calculations. Click on the Save button to save the <Project>.TGDATA file; allowing ViewGen to be run, to visualise the model and perform the calculations.  Selecting the Save option will leave WizGen open to allow the user to  examine and modify the .TGDATA file directly and to view the log of the last ViewGen run. Click on the Quit button to end the WizGen session, but the user will be asked if they wish to save the modified TGDATA file. Pressing << Back returns to the Output page. Pressing Next >> allows the user to view (and potentially edit, although this is best done via the relevant page in WizGen) the <Project>.TGDATA file. Click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. [PREV] [UP] [TOP] [HOME] [TOC]");sQ1[69]=new Array("TGmanual/100.html","Contents page","","[UP] [TOP] [HOME] Contents page This page can be accessed any time when using WizGen by clicking on the Contents button. Use the Contents page, Goto... buttons to view/edit any of the current WizGen page settings, inspect the project's TGDATA file and/or inspect the Session log generated by last TransGen calculation. HINT:- There will be 3 additional options on the Contents page of WizGen in Flexible project mode if the user has chosen to Include two-phase fault rock calculations (see below for details) or 2 additional options if the user has chosen to Include fault drag and hierarchical zone effects (see below for details) in the current run. Click on the relevant Goto... button (outlined in red in the menu below) to navigate to the appropriate contents in this Manual for full details. Only three of the five blue control buttons at the bottom of the window are operational on the Contents page. Click on the relevant to have the following effects:- << Back button to page back through the WizGen pages starting with the Session Log window to examine the last ViewGen run log. Save - to save any previously unsaved changes to the current <Project>.TGDATA run file. Quit button to exit WizGen with or without saving any changes made to the <Project>.TGDATA file. NOTE:- Having saved the WizGen settings, the next stage in the workflow is to run ViewGen to visualise the Eclipse model and the new fault-related properties calculated using the current TGDATA run file. This is launched from the TransGen Control menu. If the Include two-phase fault rock calculations option is selected on the Title page of WizGen in the "Flexible project" mode, additional Two phase flow options are displayed on the Contents page as shown below. Click on the relevant Goto... button to display and edit any of these 3 additional pages to include dynamic two-phase flow changes in water/oil saturations that occur during production in the across-fault permeability/transmissibility multiplier calculations. Click on the relevant Goto... button (outlined in red in the menu below) to navigate to the appropriate contents in this Manual for full details. If the Include fault drag and hierarchical zone effects option is selected on the Title page of WizGen in the "Flexible project" mode, additional Fault trace/Fault zone options are displayed on the Contents page as shown below. Click on the relevant Goto... button to display and edit any of these 2 additional pages to include the effects of sub-resolution geometrical fault characteristics in the across-fault permeability/transmissibility multiplier calculations. Click on the relevant Goto... button (outlined in red in the menu below) to navigate to the appropriate contents in this Manual for full details. [UP] [TOP] [HOME]");sQ1[70]=new Array("TGmanual/101.html","Prefix and Property options for plugins","","[PREV] [UP] [NEXT] [TOP] [HOME] Prefix and Property options for Plugins Referencing cell and connection properties in plugins Fault permeability and fault rock thickness, which are essential to the transmissibility calculations performed by TransGen, MUST be calculated in the PERM and THICK plugins respectively. Other properties can also be calculated in plugins, but there is no obligation to do so. Cell and connection properties must be referred to in plugins using the correct format. This is:- prefix.property The prefix identifies which internally stored array within TransGen to access. The property tells C++ which of the internally stored values associated with a particular cell or connection is being referenced. C++ is a case sensitive language. All prefix and property names should be used in lower-case. NOTE:- Two-Phase plugins do NOT use variable prefixes at all - see Two-Phase documentation. Only trace properties are available for use in DRAG and FZONE plugins (see Table of trace properties) and must be referred to using the "t." prefix. Prefix Options for Cells and Connections Prefixes for Cell Properties Any of the following 5 prefixes can be used in the PERM, THICK and AREA plugins. However, none of these prefixes are accepted by the CELLPROP plugin, where all cell properties MUST be prefixed by "cell" to take the variable value of that cell. The "cell" prefix can also be used for cell properties in an AREA plugin, but not in either the PERM or THICK plugins. Prefixes for Connection Properties The following prefixes associated with connections are shown below. The v.prefix cannot be used in the AREA plugin. NOTE:- A plugin is checked for illegal variable prefixes when the plugin is compiled by clicking on the Build button on the User-defined plugins page in WizGen. Properties available to different plugins The following lists show the suitability of various property types as input to/output from the various plugins. NOTE:- If an unsuitable data type is called on in a particular plugin, no error message is reported and the plugin will compile and run successfully. However, the output will in all likelihood be meaningless. Cell properties available to plugins Cell properties as input and output Certain cell properties must be loaded into TransGen as they influence the transmissibility calculations (e.g. PERMX, PERMY). Certain other properties are calculated by TransGen as a function of the model geometry (e.g. j, depth). These two types of property can always be used in all plugins. Other grid block property names are recognized by TransGen although they are not essential input (e.g. PORO, ACTNUM, MULTX). If these are referred to in a plugin, but have not been loaded, they are assigned a default value (as shown below). HINT:- See Including Transmissibility Multipliers from Eclipse for a description of the way TransGen treats MULTX and MULTY. This treatment is new to TransGen Version 3. Any user-defined cell property introduced via the User-defined keywords page of WizGen in Flexible project mode is initially assigned a default value 0.0. This can be modified before any plugins are run by defining its value in each cell through an input file (see including User-defined Cell Property files via the Included Data page), or its value can be modified by calculation in a plugin. If a user-defined cell property is used as input to a calculation in a plugin, it has the value assigned at that particular stage of the calculation. As described previously, it is very important to appreciate the order in which plugins are run: first CELLPROP, then THICK, then PERM, then AREA. NOTE:- User-defined cell properties are treated in the same way as other cell properties with the important difference that they may be output as well as input. These are the only type of grid-block property that can be modified, all others are read only. Fault connection properties available to plugins Most fault properties calculated by TransGen are stored internally both as connection vertex properties (e.g. v.thick, v.displ, v.fsp1) and as average connection properties (e.g. c.thick, c.displ, c.fsp1). The exceptions are direction and area (i.e. c.dir and c.area), for which a value at the vertex is meaningless. However, user-defined connection properties are only stored as connection averages, e.g. c.user_defined_connection. Therefore, there is NO v.user_defined_connection definition available for use in plugins. Vertex fault properties available to plugins Connection average fault properties available to plugins Fault connection properties as input and output Fault connection information has two kinds of prefix, connection averages (c.property) and connection vertex (v.property). Before the THICK, PERM, and AREA plugins are run, any properties stored at vertices (i.e. displacement, thickness, permeability and FSP measures) will have been averaged to provide a connection average property representative of the values at the vertices of the connection after the last plugin has been run. Hence, if a property, v.fsp1, is modified in each of the three plugins that reference faults:- In the THICK plugin, the values for c.fsp1 represent the averages of the values of v.fsp1 calculated in the TGFSP keyword; In the PERM plugin, the values of c.fsp1 represent the averages of the values of v.fsp1 calculated in the THICK plugin In the AREA plugin, the values of c.fsp1 in the AREA plugin represent the averages of the values of v.fsp1 calculated in the PERM plugin. User-defined connection properties are assigned initial defaulted values of -1.0, representative of undefined connections. If no data have been loaded for these connections (see including User-defined Connection Property files via the Included Data page), they have a value of -1.0 when they are called in plugins. Their values may, of course, be updated in the plugins. NOTE:- Fault properties CANNOT be used as input to or output from a CELLPROP plugin. Using Fault connection properties in the THICK & PERM plugins The THICK plugin should be used to calculate fault rock thickness and the PERM plugin used to calculate fault rock permeability. Both these plugins MUST be included in the TransGen run file. Permeability and thickness must be calculated on connection vertices, using code such as:- v.thick = 0.005882 * v.displ; which simply defines fault rock thickness to be a fraction of fault displacement, and:- double term1; double term2; term1 = 0.4   4.0 * v.sgr; term2 = pow(1 - v.sgr, 5.0); v.perm = pow(10.0, term1 - 0.25*term2); which calculates fault rock permeability as a function of SGR using the expression:- See section on C++ language use in plugins for information about the language and logic of writing plugins. Outputting properties stored at vertices Both connection average (c.property) and connection vertex (v.property) properties can be used as input to the THICK and PERM plugins. If both are available, we recommend that vertex properties be used to calculate other vertex properties (e.g. thick, perm or to modify properties generated with the TGFSP keyword) as this ensures greater precision. There is no problem, however, with using connection average properties to calculate vertex properties if a vertex property does not exist. For example:- v.perm = v.fsp1 + c.user1; is ideal, and v.perm = c.fsp1 + c.user1; is acceptable but not recommended as it is less precise. The commands:- c.perm = v.fsp1 + c.user1; or c.perm = c.fsp1 + c.user1; should never be used, as perm is stored at vertices as well as connections. If a fault connection property is stored at both vertices and connections, the connection average properties should NOT be used as output. This is because the property is averaged as a function of the values at the connection vertices after the plugin has been run and the averaging will overwrite the existing connection averages. Therefore, any connection averages modified in the THICK or PERM plugin for these properties will later be overwritten during the averaging process. Connection properties stored at both vertices and as connection averages that are available as output are fault rock thickness (called thick in plugins), fault rock permeability (called perm in plugins) and the FSP measures. Outputting properties that are stored only as connection average values Vertex properties should generally be avoided if calculating fault properties that only exist as averages (e.g. the values of user-defined connections). This is because the PERM and THICK plugins are run on every vertex of every connection, so a command such as:- c.user1 = v.fsp1 + v.fsp2; would continually update the value of the user-defined property as each vertex is processed and the final value would depend only on the last vertex processed. It is therefore not appropriate to the connection as a whole. Instead the command:- c.user1 = c.fsp1 + c.fsp2; should be used. There are exceptions to this rule. An example would be if a user-defined connection property is defined to store the maximum FSP value present on a connection. In this case the code:- if (v.fsp1 > c.user1) {    c.user1 = v.fsp1; } would set the user-defined connection property user1 (which has the initial default value of -1.0) to the maximum value of fsp1 present on the connection vertices. [PREV] [UP] [NEXT] [TOP] [HOME]");sQ1[71]=new Array("TGmanual/102.html","C++ language use in plugins","","[PREV] [UP] [NEXT] [TOP] [HOME] C++ language use in plugins C++ is a complex programming language - fortunately only a very small subset is required to construct even the most sophisticated plugin. The plugin is in fact a C++ function that is called by ViewGen; the vertex, connection and cell information is passed into the plugin function. ViewGen automatically adds the function call information to the plugin code: the user does not have to be concerned about the semantics of argument passing. The following sections describe systematically the functionality of C++ that will most commonly be required in plugins. The semi-colon All declarations and statements in C++ must be terminated by a semi-colon `;'. The most likely reason for a plugin to fail to compile is that a semi-colon has been omitted. The compiler may issue many lines of errors because of this simple mistake! Constants and temporary variables Any constants or temporary variables used in a plugin should be declared as double precision floating point numbers. The easiest way of declaring constants is to use a single line, e.g. double a = 0.005882; but the same result could be obtained on two lines, e.g. double a; a = 0.005882; It follows, therefore that 'a' does not have to be a constant, but can be a temporary variable. For instance, the code below sets two temporary variables as double precision numbers which are then calculated and used later in the code:- double term1; double term2; term1 = 0.4 - 4.0*v.sgr; term2 = pow(1 - v.sgr , 5.0); v.perm = pow(10.0, term1 - 0.25*term2); Once they have been calculated on the third and fourth lines, term1 and term2 are treated in exactly the same way as any other variable (e.g. v.sgr). The `dir' symbol The connection property c.dir differs from all other cell or fault properties in that it is a symbolic constant rather than a double precision number. It can have one of two values:- 'DIR_X' for a connection perpendicular to X - between grid-blocks (I, J, K1) and (I+1, J, K2) or  `DIR_Y' for a connection perpendicular to Y - between grid-blocks (I, J, K1) and (I, J+1, K2). c.dir cannot be used in calculations and the only relational operators for which it is relevant are `==' and `!='. A condition such as:- if (c.dir == DIR_Y) { is perfectly acceptable and will evaluate to either true or false, but the expressions:- if (c.dir < 0.2) { or v.perm = 23.0*c.dir ; are meaningless and the compiler will issue an error. Brackets `( )'  Brackets are needed in the following situations:- 1. For defining the order of algebraic operations in a standard manner, e.g. v.perm = a + b * c; is not the same as: v.perm = (a + b) * c; The `*' operator takes precedence unless brackets are used. 2. In functions called from the Math library, e.g. v.thick = a * pow(v.displ, b); the brackets contain the arguments sent to the `pow' function. 3. To specify a relational operator, e.g. if (a == b) { A symmetrical set of brackets that open and close each other in a logical fashion must be used at all times. Braces  { }  Braces are used in conjunction with relational operators. An opening brace is needed immediately after a conditional clause and a closing brace is needed to end the operation to be performed subject to this condition. Two pairs of braces were therefore used in the example given of the thickness plugin (one for the `if' and one for the `else' conditions). If a pair of braces is not included in a conditional statement, C++ assumes that the condition lasts only for the next statement. Hence the code:- if (a < 23.0) b = 45.0; c = 15.0; would mean that b would be set to 45 only if a is less than 23, but c would be set to 15 whatever the value of a. The correct way of writing this code is using braces:- if (a < 23.0) { b = 45.0; c = 15.0; } Comments Comments can be incorporated into the plugin code - any text on a line after the `//' symbol is considered a comment and is ignored by ViewGen and the C++ compiler, e.g. // a and b are used later double a = 0.005882; // 1/170 = 0.005882 double b = 1.0; v.thick = pow(a, b); //  v  means the vertex As far as the compiler is concerned, this is exactly the same as double a = 0.005882; double b = 1.0; v.thick = pow(a, b); Operators and Libraries Mathematical operators The mathematical operators are fairly obvious:- The Math libraries The pow function used in the example is drawn from the C++ Math library. The so-called prototype of the `pow' function in the library is:- double pow(double base, double exponent); The `double' before the `pow' indicates the function returns a double precision value, and the function takes two arguments, both double precision. If the function is called with constants as arguments they are automatically converted to doubles, e.g. v.thick = pow(0.005882, 1.0); The prototypes for all (potentially) useful math library functions are:- Relational operators C++ has a rich set of relational operators that are used to compare two values against each other. For instance, the `<' operator evaluates to true if the value to the left of the operator is less than the value to the right and false if not. Relational operators are typically used with `if' statements so the plugin author can determine what action to take based on a certain condition being true or false. For example, the following code calculating fault permeability as the harmonic average of the cell permeabilites if CSP is below a defined sealing threshold. Otherwise it sets fault permeability to zero. double csp_cutoff = 5.0; double perm1; double perm2; if (c.dir == DIR_X) {    perm1 = up.permx;    perm2 = down.permx; } else {    perm1 = up.permy;    perm2 = down.permy; } if (v.csp_measure < csp_cutoff) {    v.perm = 1 / (0.5 / perm1 + 0.5 / perm2 ); } else {    v.perm = 0.0; } The terms inside the parenthesis i.e. `c.dir == DIR_X' and `v.csp_measure < csp_cutoff' evaluate to either true or false. If the condition is true the first clauses of the `if' statements are executed; if the condition is false the clauses following the `else' are executed. The full set of relational operators are:- NOTE:- x = y is not a relational operator but an assignment. If the following code is included in a plugin:- if (v.fsp1 = -1.0) {    v.perm = 0.0 ; } else {    // more code here } the assignment (v.fsp1 = -1.0) will be made and the condition will then be evaluated as true. Hence v.perm will be set to 0.0 whatever the starting value of v.fsp1. The result of this bit of code, therefore, will be to overwrite the fsp1 values at every vertex in a model with undefined value (-1.0) and to set the permeability of every vertex in the model to be 0.0. The plugin will never call the bit of code written after the `else' statement. This is unlikely to be what was intended and the first line of code should have been:- if (v.fsp1 == -1.0) { In this case, the permeability of vertices of connections undefined in fsp1 is set to 0.0, and all defined connections are dealt with in the code following the else statement. Relational expressions (such as `a < b') may be grouped together logically within parentheses to test more than one condition at once. If expr1 and expr2 are two relational expressions:- if (expr1 && expr2) {    // do this } else { // do that } means that both expr1 and expr2 must be true for the first statement (`do this') to be executed. The symbol `&&' is called the AND operator. Alternatively:- if (expr1 || expr2) {    // do this } else {    // do that } means that if either expr1 or expr2 is true the first statement is executed. The symbol `||' is called the OR operator. An example of using OR in a permeability plugin that uses CSP might be:- if (v.csp > cutoff || v.csp == UNDEFINED_VALUE) {    v.perm = 0.0; } else { // set permeability in some other way } NOTE:- The symbol `UNDEFINED_VALUE' takes the value -1.0; we have introduced it for use in plugins to make them easier to read. Multiple conditional statements The `if' statement can have one, two or many clauses. A clause can be one or more statements (a statement is defined by a line of code that is terminated by a semi-colon). If a clause consists of more than one statement the clause must be enclosed in braces `{ }'. To help reduce any compilation errors, it is suggested braces are always used to enclose the clauses in an `if' statement, even if the clause only contains one statement. For instance:- if (up.ntg < 0.4) {    up.my_property1 = 1.0;    up.my_property2 = 0.0; } else if (up.ntg < 0.7) {    up.my_property1 = 0.5;    up.my_property2 = 0.5; } else {    up.my_property1 = 0.0;    up.my_property2 = 1.0; } There can be many `else if' conditions between the first `if' and the final `else'. Indeed, there does not have to be a final `else' here. The braces group together the statements within a clause and make the plugin easier to read. [PREV] [UP] [NEXT] [TOP] [HOME]");sQ1[72]=new Array("TGmanual/103.html","Issues associated with FSP calculations","","[PREV] [UP] [NEXT] [TOP] [HOME] Issues associated with FSP calculations Shale face bunching A geocellular model may contain shale layers that are more than one grid-block thick. In this case, the general FSP expression will give different answers if the shale is treated as two separate shale faces rather than as a single shale. Shale bunching refers to the operation of combining multiple, vertically adjacent shale faces into a single face for use in the FSP calculation. This is illustrated in the figure below, showing the equations used to define the thickness ('bunched t') and effective vshale (`bunched eVs`) values used. Distance (`bunched d`) and throw (`bunched D`) are also calculated as a function of the bunched face. Shale bunching is important for correctly calculating the values of FSP measures that are based on the concept of discrete shale layers (e.g. CSP). However, for FSP measures based on the concept of a continuous distribution of effective Vshale (e.g. SGR), all cells are designated as shale cells (i.e. the Shale definition is Based on all cells) and bunching is inappropriate. Hence, shale bunching is ALWAYS applied, EXCEPT when the Shale definition is Based on all cells. Inactive FSP values The concept of undefined vertices and connections has been introduced as a consequence treating shale faces and non-shale faces in different ways. Any FSP measure which does not use all faces as shale faces (i.e. all models in which the Shale definition is NOT set to Based on all cells) will contain some undefined (i.e. incalculable) values. The FSP value of a vertex or connection is made "undefined" if the cell on either side of the connection being processed is a designated shale cell. The reason for inactivating the FSP measures in this case is to avoid calculating a FSP value of infinity. Vertices with a FSP measure inferred as "undefined" have the FSP value assigned to -1. If one vertex within a connection evaluates the FSP to be "undefined", all other vertices within that connection automatically have the value for the FSP set to -1. Since all valid FSPs have a range equal to or greater than 0.0, any vertices or connections with negative FSP should be considered undefined. Care must be taken in the permeability plugin (See User-defined plugins page) to assign appropriate values for fault permeability to these "undefined" FSP values (either by using an FSP which does have defined connection, by using the cell properties adjacent to these connection, or by assigning a constant permeability to them). Invalid FSP options Certain FSP strings have the potential to introduce ambiguity into the calculation, in which case TransGen will issue an error message and stop. Only two such cases have been identified to date:- With the Combination option set to Maximum from layers then sum and with the Shale definition set to Effective Vshale cutoff With the Combination option set to Maximum from layers then sum and with the Shale definition set to Based on user-property The reason for disallowing these combinations is owing to shale bunching, resulting in, for example one shale layer existing on the footwall side of the fault, while two are present on the hangingwall side (as shown in the Figure above). The particular Combination setting demands that the maxima of particular pairs of layers are submitted to the summation, but even in this simple illustration there is no unambiguous way in which pairs of layers can be compared. Displaying Effective Vshale and designated Shale layers In TransGen Version 2, the item Effective Vshale appeared in the cell properties pulldown menu in the graphical interface. In Version 3 there is no longer necessarily a unique value of Effective Vshale in each grid-block, since each FSP measure (up to 5 of which can be included in a single TransGen run) can be based on a different definition of Effective Vshale. Therefore, if graphical display of an Effective Vshale associated with a particular FSP is required, it must be defined as a user-defined cell property. Up to ten user-defined cell properties are allowed and, if defined, new properties are dynamically added to the cell properties menu. Similarly, the cells used as designated shale layers may differ from one FSP to another. Therefore, to be available for visualisation, the shale descriptions must be defined as user-defined cell properties and the FSPs constructed in such a way as to use shale definition based on a user-defined cell property. For more information, see TGNEWKEY and the CELLPROP plugin and changes to the graphical interface. FSP value calculation and storage FSP values are calculated and stored at each vertex of each connection. In addition, the area-weighted arithmetic average FSP value is computed from the FSP values at the vertices and stored in the connection. In the graphics interface, the average FSP value (i.e. connection value) is displayed when the average sub-option is selected, and an interpolation of FSP vertex values when the smooth sub-option is selected in the fault properties pulldown menu.  Both vertex and connection FSP values can be accessed in the permeability and thickness plugins. We recommend using the vertex FSP wherever possible, since the value of the FSP may change rapidly over the area of a connection. Editing FSPs in Plugins All FSPs are editable in plugins. This can be extremely useful, but is not generally recommended. (See, for example, Shale Smear Factor combining multiple shale beds). Dimensions of FSPs. The dimensions of an FSP are Length^(Exponent L + Exponent M + Exponent N). If the keyword TGMETRIC is included in the TGDATA file (i.e. with the FSPs in metric option selected on the Miscellaneous Options page of WizGen in Flexible project mode), TransGen will calculate and report all FSP values (and fault displacement/thickness) using the units of Length set to Metric (i.e. metres). IF the keyword TGMETRIC is omitted (i.e. with the FSPs in native units option selected on the Miscellaneous Options page of WizGen in Flexible project mode), the unit of Length corresponds to the Units specified for the project (i.e. feet for FIELD and centimetres for LAB as set on the Coordinate System page of WizGen). Use of the TGMETRIC keyword does not influence the dimensions in which the transmissibility calculations are made - these are scaled to the input UNITS. If the TGDATA file is created by WizGen in Basic project mode, TGMETRIC is inserted into the file by default. This is required for `basic' plugin compatibility, since cutoff values of non-dimensionless FSP measures (e.g. CSP) used in the automatically generated plugins are in metric units. [PREV] [UP] [NEXT] [TOP] [HOME]");sQ1[73]=new Array("TGmanual/104.html","Typical Fault Seal Potential Variable settings","","[PREV] [UP] [TOP] [HOME] Typical Fault Seal Potential Variable settings This section describes typical settings required in WizGen in Flexible project mode to calculate the most commonly used measures of Fault Seal Potential, i.e. Shale Gouge Ratio, Clay Smear Potential as per Yielding et al. or as per Fulljames et al., Shale Smear Factor as per Lindsay or by combining multiple shale beds. The user can also create their own method, for example see the modified version of calculating Clay Smear Potential created using user-defined keywords in the CELLPROP plugin. Shale Gouge Ratio (SGR) SGR is defined as:- Equation constants Therefore, in the generalised FSP equation, Exponent l = -1, Exponent m = 1, Exponent n = 0 and Exponent p = 1. Distance options Distance is not used in the equation (since Exponent n = 0), however a valid distance option is still required. Distance option, Centre of beds (distance_switch = 2) is as good as any. Combination options If the properties of the cells in the footwall and hangingwall are the same, any of the Combination options - Maximum of layers then sum, Sum layers then maximum, Sum layers then take average, Sum in hangingwall or Sum in footwall would give sensible answers. The option Sum layers then take average is equivalent to the default in TransGen version 2, and is, in general, our recommended combine option for SGR. Sum in hangingwall is recommended for growth faults or in reservoirs with severely eroded crests. Effective vshale This setting will depend on the Included Data for the current project. If, as in the TRIANGLE demo dataset, there is only NTG data, the Net-to-gross only option would be applicable. Plunge correction Retain the default Three dimensional setting unless you specifically want to report the FSP measures on a vertical projection of the fault. Shale definition If, as in the TRIANGLE demo dataset, all the cells have a non-zero Vshale, all cells must be used in the calculation. Shale definition is therefore set to Based on all cells. The WizGen Fault Seal Potential Variables page looks like this:- and the TGFSP keyword record in the TGDATA run file is:- 'sgr' -1 1 0 1 4 ' ' 1 6 1 ' ' 1 / where the string is:- 'name' l m n p shale_switch shale_ string distance_switch combine_switch evshale_switch evshale_string plunge_correction / Clay Smear Potential (CSP) after Yielding et al. 1997 CSP is defined as:- Equation constants Therefore, in the generalised FSP equation, Exponent l = 0, Exponent m = 2, Exponent n = -1 and Exponent p = 0. Distance options Centre of beds (distance_switch = 2) setting is appropriate. Combination options The summation is performed on the maximum values of the terms calculated in the footwall and hangingwall, i.e. Maximum from layers then sum. Effective vshale This setting will depend on the Included Data for the current project. If, as in the TRIANGLE demo dataset, there is only NTG data, the Net-to-gross only option would be applicable. Plunge correction Retain the default Three dimensional setting unless you specifically want to report the FSP measures on a vertical projection of the fault. Shale definition When using the Maximum from layers then sum combination option, the only possible Shale definition to individually name the Layers. The WizGen Fault Seal Potential Variables page looks like this:- and the TGFSP keyword record in the TGDATA run file is:- 'csp_yielding' 0 2 -1 0 1 '8-13, 26-29, 34, 38, 45-47' 1 1 1 ' ' 1 / where the string is:- 'name' l m n p shale_switch shale_ string distance_switch combine_switch evshale_switch evshale_string plunge_correction / Clay Smear Potential (CSP) after Fulljames et al. 1997 The Fulljames et al. (1997) definition differs from that of Yielding et al. in that:- Distances are measured to the Far side of beds. FSP is calculated independently in the hangingwall and footwall sides of the fault and the final FSP is the maximum of these, i.e. Combination options setting should be Sum layers then take maximum. NOTE:- It is possible with this method of CSP calculation to base the Shale definition on any of the options, but for direct comparison with the CSPs obtained as per Yielding et al., the Layers setting has been retained. The WizGen Fault Seal Potential Variables page looks like this:- and the TGFSP keyword record in the TGDATA run file is:- 'csp_fulljames' 0 2 -1 0 1 '8-13, 26-29, 34, 38, 45-47' 2 2 1 ' ' 1 / where the string is:- 'name' l m n p shale_switch shale_ string distance_switch combine_switch evshale_switch evshale_string plunge_correction / Shale Smear Factor (SSF) after Lindsay et al. 1993 The original SSF formulation (Lindsay et al. 1993) is:- This method does not consider the possibility of multiple shales, calculating the SSF value associated with every shale that has passed a point on a fault and taking the minimum. Unlike both SGR and CSP, faults with lower value of SSF are more likely to have higher sealing capacity. Equation constants Therefore, in the generalised FSP equation, Exponent l = 1, Exponent m = -1, Exponent n = 0 and Exponent p = 0. Distance options Distance is not used in the equation (since Exponent n = 0), however a valid distance option is still required. Distance option, Centre of beds (distance_switch = 2) is as good as any. Combination options The formulation of SSF attributed to Lindsay et al. calculates the SSF value associated with every shale that has passed a point on a fault and takes the minimum, so the Combination options should be set to the Minimum value. NOTE:- More connections will be undefined using SSF as a FSP measure than when using either of the CSP methods. This is because any connections which have not had any shales layers pass them are undefined for SSF because the Minimum value combination option setting does not involve summation and it is impossible to define the minimum term of no terms at all. Whereas all the CSP measures involve some sort of summation and the sum of no terms is 0.0. Effective vshale This setting will depend on the Included Data for the current project. If, as in the TRIANGLE demo dataset, there is only NTG data, the Net-to-gross only option would be applicable. Plunge correction Retain the default Three dimensional setting unless you specifically want to report the FSP measures on a vertical projection of the fault. Shale definition This should be set to Effective Vshale cutoff and input an appropriate value, e.g. 0.5 to define the shale layers based on the Effective vshale (which is a simple function of Net-to-gross). The WizGen Fault Seal Potential Variables page looks like this:- and the TGFSP keyword record in the TGDATA run file is:- 'ssf_lindsay' 1 -1 0 0 2 '0.5' 2 4 1 ' ' 1 / where the string is:- 'name' l m n p shale_switch shale_ string distance_switch combine_switch evshale_switch evshale_string plunge_correction / Shale Smear Factor (SSF) Definition 2 This SSF combines multiple shale beds using the expression:- This expression cannot be calculated directly using the generalized expression for FSP and this is a rare example of when it is useful to modify a FSP in the PERM or THICK plugin. The Fault Seal Potential Variables are set to calculate the summed Shale bed thicknesses which are then used in either the permeability or thickness plugin to get the expression for SSF. Equation constants To calculate the summed shale bed thicknesses in the generalised FSP equation, Exponent l = 0, Exponent m = 1, Exponent n = 0 and Exponent p = 0. Distance options Distance is not used in the equation (since Exponent n = 0), however a valid distance option is still required. Distance option, Centre of beds (distance_switch = 2) is as good as any. Combination options This is set to Sum layers then take average to calculate shale bed thickness from the average of the thickness in the footwall and thickness in the hangingwall. Effective vshale This setting will depend on the Included Data for the current project. If, as in the TRIANGLE demo dataset, there is only NTG data, the Net-to-gross only option would be applicable. Plunge correction Retain the default Three dimensional setting unless you specifically want to report the FSP measures on a vertical projection of the fault. Shale definition This should be set to Effective Vshale cutoff and input an appropriate value, e.g. 0.5 to define the shale layers based on the Effective vshale (which is a simple function of Net-to-gross). The WizGen Fault Seal Potential Variables page looks like this:- and the TGFSP keyword record in the TGDATA run file is:- 'ssf_2' 0 1 0 0 2 '0.5' 1 6 1 ' ' 1 / where the string is:- 'name' l m n p shale_switch shale_ string distance_switch combine_switch evshale_switch evshale_string plunge_correction / The THICK (or PERM) plugin is then used to modify the summed shale bed thickness to derive an expression for SSF as shown below in the User-defined plugins page of WizGen. The if statement is needed to ensure that connections which have had no shales pass them are set to undefined connections, otherwise they would take on values of infinity. [PREV] [UP] [TOP] [HOME]");sQ1[74]=new Array("TGmanual/105.html","Using Plugins in TransGen","","[UP] [NEXT] [TOP] [HOME] Using Plugins in TransGen A plugin is a macro, written in C++, that manipulates the values of cell and connection properties. Plugins are essential to even the most simple TransGen v3 run. The absolute minimum requirement of a "Basic" TransGen project are the automatically generated plugins which calculate fault thickness and permeability, i.e. the THICK and PERM plugins. In a "Flexible" project, the user must include both the THICK and PERM plugins and can use another two plugins (CELLPROP and AREA), while the addition of two-phase functionality to a "Flexible" project can potentially introduce another nine plugins (see Defining Two-phase flow plugins). Alternatively, when using the new option to include fault drag and hierarchical zone effects in a "Flexible" project, the drag applied to fault traces can be defined via the DRAG plugin and/or the FZONE plugin can be used to place fault zones on fault traces. A TransGen "Basic" project does not allow direct interaction with the plugin source code. The Fault Rock Properties page in WizGen Basic contains relationships governed by equations. The constants contained in the equations can be edited. When the project is saved, two plugins called _AUTO_THICK_PLUGIN.cpp and _AUTO_PERM_PLUGIN.cpp (incorporating these constants) are saved in the <project_name>_INPUT/.plugin sub-directory of the current project directory. When a TransGen project is converted from "Basic" to "Flexible", the default plugins used to control fault thickness and permeability are copied to new file names, i.e. <project_name>_THICK.cpp and <project_name>_PERM.cpp stored in the same <project_name>_INPUT/.plugin directory. The contents of the two plugins are initially unchanged and therefore the converted "Flexible" project will produce the same results as the preceding "Basic" project. When using TransGen in "Flexible project" mode, any of the plugins can subsequently be edited and re-built via the User-defined plugins page of WizGen. When a TransGen project is created from new in "Flexible project" mode, a full default suite of plugins are automatically accessed and stored in the <project_name>_INPUT/.plugin directory. Any or all of them can be edited via the User-defined plugins page of WizGen.  In summary, each project contains a plugin directory which contains the TransGen default plugin suite and may also contain plugins derived from these defaults and subsequently edited within a "Flexible project". In addition, a directory is provided within the user's home directory to store plugins for general application across several projects. The four standard plugins are shown below. Both the THICK and PERM plugins are essential to calculate fault rock thickness and fault permeability - ViewGen will stop with an error message if the THICK and PERM plugins are not supplied (except when the Do not calculate fault properties option is toggled "on" via the Miscellaneous Options page in WizGen). The CELLPROP and AREA plugins are not essential. When using TransGen in Flexible project mode, all plugins including the 2 essential plugins for fault thickness and fault permeability calculation are added as a single string below the TGPLUGIN keyword in the TGDATA run file. The form of the TGPLUGIN keyword is a set of strings enclosed by single quotes (one string to a line) that associate a plugin name with a full C++ source filename. The source file contains the plugin code. For example, the TGPLUGIN keyword entry in the TGDATA file might be:- ViewGen reads the TGPLUGIN keyword and uses a C++ compiler to transform the source code into binary. At the appropriate point during the calculation steps, ViewGen attaches the binary plugin code and calls the plugin repeatedly for each connection vertex or cell within the model. Vertex, connection and cell property values are loaded into the plugin, the plugin code runs and the updated values are read back into the model each time the plugin is called. Hence the user has complete control over the property values within the model. Summary of the TransGen calculations The objective of a plugin is to calculate cell or connection properties, based on existing cell or connection properties, using user-defined algorithms. In order to design efficient and numerically robust plugins, it is vital to have some understanding of the TransGen calculations. This section summarises how TransGen calculates fault connection properties and the order in which the various calculations are performed. Each faulted connection between active cells is stored internally within TransGen as polygons of connected 3D vertices for both cells associated with the connection. Each vertex contains geometric information and fault property data. TransGen automatically calculates and stores displacement, and up to five FSP measures at each vertex of the connection. Fault rock thickness and permeability are also defined at each connection vertex, their values are calculated in the THICK and PERM plugins. In the diagram below, the two triangular coincident connections  A  and  B  perfectly share an edge but the three vertices in  A  are distinct from the three vertices in  B  although two vertices from either connection share the same geometric position. The values of the FSP measures calculated at the geometrically similar vertices may be different. Connection average properties are also calculated and stored. For all vertex properties with the exception of fault rock thickness, the area-weighted arithmetic average is used. For fault rock thickness, an area-weighted harmonic average is used. The graphics viewer provides two options to display some of the items in the fault properties menu - `smooth' or `averaged'. The two displays are drawn directly from the vertex and (averaged) connection values stored within the model respectively. For certain fault properties (e.g. the area of the connection or its direction) a value at a vertex is meaningless, and only "average" values are stored. User-defined connection properties introduced with the TGNEWKEY keyword are only present in TransGen as connection averages. The CELLPROP plugin cannot access fault connection information. Only cell properties can be used. The THICK and PERM plugins should operate principally on vertices. Connection information is available if required (e.g. the direction of the connection, user-defined connection properties). The  AREA  plugin should operate on connection properties as it is called just prior to the transmissibility calculation step and vertex properties are not referenced at this point. Fault displacement and all FSPs are averaged before the THICK plugin is run. The objective of this plugin is to calculate fault rock thickness at each vertex of each connection. Since it is possible to modify the FSP values at connection vertices, all FSPs as well as fault rock thickness are averaged after the THICK plugin is run (i.e. immediately before the PERM plugin is run). There is no need to average fault displacement again at this stage since it cannot be edited in a plugin. Similarly, all FSPs as well as both fault rock thickness and fault rock permeability are averaged before running the AREA plugin. Since it is impossible to change connection vertex values in the AREA plugin, no more averaging needs to be done prior to calculating the transmissibilities of the connections. The CELLPROP plugin The principle purpose of the CELLPROP plugin is to specify user-defined algorithms for determining (a) the effective Vshale values of cells, and (b) which cells to use to define the shale faces - used in particular FSP calculations. However, any user-defined cell property can be modified in the plugin. The CELLPROP plugin runs quite early on in the TransGen calculation, after all include files have been read in, and the geometry of the cells has been calculated, but before any faults have been identified. Therefore fault properties cannot be used in the CELLPROP plugin. Only cell properties can be used in this plugin and only with the general "cell" prefix. The CELLPROP plugin is called once for every grid-block in the model. The THICK and PERM plugins The THICK plugin should be used to calculate fault rock thickness and the PERM plugin used to calculate fault rock permeability. Both these plugins MUST be included in the TransGen run file. These plugins are called at every vertex of every active faulted connection in the model. Only cells adjacent to faults are used in calculations in these plugins. Thickness and permeability MUST be calculated on connection vertices, i.e. v.thick defined as a fraction of v.displ, v.perm calculated as a function of v.sgr. When using cell properties in the THICK or PERM plugins, any of the 5 cell prefixes (i.e. up, down, min, max, ave) are available for use (but NOT the general "cell" prefix which MUST be used in a CELLPROP plugin and can be used in an AREA plugin). If a fault property is used to modify the values of a user-defined cell property, the connection average prefix should be used rather than the vertex prefix to define the fault property. This is because these plugins are run on every vertex of the connections, so code such as:- up.cell_prop1 = v.fsp1; would continually update the value of cell_prop1 as each vertex is processed and the final value of up.cell_prop1 would simply be assigned the value of fsp1 of the last vertex processed. The following code is more appropriate as it assigns the same (i.e. the average) value of fsp1 to the cell as each vertex is processed:- up.cell_prop1 = c.fsp1; There are, however, exceptions to this advice, similar to those discussed under Outputting properties stored only as connection averages. As a general rule, however, we recommend that user-defined cell properties are not updated in the THICK and PERM plugins, for the reason discussed in the section on the AREA plugin below. The AREA plugin The optional inclusion of the AREA plugin allows modification of the Area term used in the faulted transmissibility equation. For further details refer to the Introduction of the AREA term in the Technical Description of what TransGen does. It can also be used to update user-defined cell properties. Unlike the THICK and PERM plugins, the AREA plugin is called once per connection. Therefore, only connection average fault properties (e.g. c.area, c.user_connection, c.fsp1) should be used as both input and output. When using cell properties in the AREA plugin, all 5 cell prefixes (i.e. up, down, min, max, ave) plus the general "cell" prefix (i.e. only cell property prefix useable in a CELLPROP plugin) are available for use. The reason why user-defined cell properties should be updated in the AREA plugin rather than the THICK or PERM plugins is explained below, with reference to a simple 8 grid-block model. Cell (1,2,1) is bounded by a fault on two sides and forms connections with 4 other cells. Each of these 4 connections is rectangular and therefore has 4 vertices. Assume we have a particular property for each connection, that this property is additive, and that we want to report the sum of this property as a user-defined cell property (GB1). An example might be the total area of the X and Y edges of each cell that are faulted. Provided we have not included any values for GB1 and it has not been used in any previous plugins, its value in all cells will be 0.0 (the default). Assume that the area of all the connections in this example is 100 sq.m . We include the following code in the AREA plugin:- up.GB1 = up.GB1 + c.area; down.GB1 = down.GB1 + c.area; The plugin will be called once for every faulted connection in the model. The first connection involving block (1,2,1) to be called is the one to block (2,2,1). (1,2,1) is the "down" grid-block, and (2,2,1) is the "up" one with respect to this connection. The first line of code will add 100 to the value of GB1 for cell (2,2,1), and the second will update the value of cell (1,2,1). The next connection (between blocks (1,2,2) and (2,2,2)) will add another 100 to block (1,2,1) (through the first line of code) and then update cell (2,2,2) through the second. Continuing the processing will finally give a values of GB1 = 400 for block (1,2,1), 200 for blocks (1,1,2), (1,2,2) and (2,2,2), and 100 for blocks (1,1,1) and (2,2,1). Blocks (2,1,1) and (2,1,2) are not associated with any faulted connections, and therefore the values of GB1 will not be modified from the original value of 0.0. If the same code were inserted in the PERM or THICK plugins, the final values of GB1 would not be correct, because GB1 would be modified for every vertex of every x y z (1,1,1) (2,1,1) (1,1,2) (1,2,1) (1,2,2) (2,2,1) (2,2,2) x y z (1,1,1) (2,1,1) (1,1,2) (1,2,1) (1,2,2) (2,2,1) (2,2,2) rather than once for every connection. Since there are 4 vertices for every connection in this model, the final value of GB1 for block (1,2,1) would therefore be 1600 rather than 400. This example serves to illustrate some of the pitfalls associated with calculating cell properties in plugins. [UP] [NEXT] [TOP] [HOME]");sQ1[75]=new Array("TGmanual/106.html","Example of calculating user-defined cell properties in the CELLPROP plugin","","[UP] [TOP] [HOME] Example of calculating user-defined cell properties in the CELLPROP plugin In this modified version of calculating Clay Smear Potential (CSP), the effect of the clay layers are weighted by their Vshale values to illustrate the method of building a FSP measure using User-defined keywords and the CELLPROP plugin. NOTE:- This is a non-standard FSP measure and its use is NOT necessarily recommended. 1. Add User-defined keywords On the User-defined keywords page of WizGen Heavy, type in two new Cell Properties, e.g. binary_shale to be used to define the shale cells of the model and evs1 to be used to define their fractional shale content. Click on Save at the bottom of the screen to update the TGDATA run file with the TGNEWKEY  which will contain the 2 keywords as shown below:- TGNEWKEY 'evs1' 1 / 'binary_shale' 1/ / In the current example, there is no data which can be loaded for these 2 user-defined keywords. Instead, their properties will be calculated in the CELLPROP plugin. 2. Update Fault Seal Potential Variables On the Fault Seal Potential Variables page of WizGen Heavy, create a new FSP name, e.g. csp_fulljames2. Set variables to calculate CSP as per Fulljames et al. 1997 and in addition:- Set Equation constant p (evshale) to 1.0. Set Effective vshale to be Based on User property: evs1. Set Shale definition to be Based on user-property: binary_shale. The WizGen Fault Seal Potential Variable page looks like this:- Click on Save to add the new CSP measure to the TGFSP string(s) in the TGDATA run file:- TGFSP 'sgr' -1 1 0 1 4 ' ' 1 6 1 ' ' 1 / 'csp_fulljames2'  0 2 -1 1 3 'binary_shale' 2 2 4 'evs1' 1 / / where the string is:- 'name' l m n p  shale_switch  shale_ string  distance_switch  combine_switch  evshale_switch  evshale_string  plunge_correction / 3. Create a User-defined CELLPROP plugin On the User-defined plugins page of WizGen, select the CELLPROP function and input code to calculate values for evs1 and binary_shale from the Net-to-Gross data already included in the model. For example, evs1 is set to (1 - NTG) and binary_shale to 1.0 if the NTG is less than 0.5 and to 0.0 if the NTG is more than 0.5. Click on Build to compile the plugin and check for any errors. If, as in this case, the build is successful, click on Return to code to re-display code, then click on the Save As, File option and save it as e.g. cellprop1.cpp. HINT:- The "cell." prefix in front of the Cell Properties (cell.evs1, cell.ntg and cell.binary_shale) is the only permitted prefix in a CELLPROP plugin - see Prefixes for Cell Properties in the section on Prefix and Property options for plugins. Click on Save to add the new CELLPROP to the TGPLUGIN string in the TGDATA run file, for example:- --<PLUGINS+> TGPLUGIN 'THICK=/home/TGprojects/<project_name>/<project_name>_INPUT/.plugins/<project_name>_THICK.cpp' 'PERM=/home/TGprojects/<project_name>/<project_name>_INPUT/.plugins/<project_name>_PERM.cpp' `CELLPROP=//home/TGprojects/<project_name>/<project_name>_INPUT/.plugins/<project_name>_CELLPROP.cpp' / --<PLUGINS-> 4. Check the PERM plugin Check the PERM plugin is set correctly and if necessary edit and re-build. In the current example, the vertex permeability is set to the harmonic average of the two grid-block permeabilities unless the calculated value for the newly created FSP measure (i.e. csp_fulljames2) is either greater than 0.5 or is an undefined_value in which cases the permeability is set to zero. 5. Run ViewGen Click on ViewGen to run the model with the new Vshale-weighted CSP measure. HINT:- If the model run fails for any reason, click on the Goto... button for Inspect the log generated by last TransGen calculation on the WizGen Contents page to see the error message(s). [UP] [TOP] [HOME]");sQ1[76]=new Array("TGmanual/107.html","Title page","","[UP] [TOP] [HOME] Title Page Having selected the Basic project option on the Title page of WizGen, as shown below, the following options are accessible:- Next >> - to access the next page (i.e. Coordinate System page) in the sequential process to set up the <Project_Name>.TGDATA run file. Contents -  to view/edit the Contents page, i.e. any or all the current settings in the TGDATA run file, to inspect the project's TGDATA file and/or to inspect the log generated by the last TransGen calculation. Save - to save the current settings of WizGen to the project's TGDATA run file. Quit - to exit from WizGen with or without saving any changes to the <Project_name>.TGDATA run file. Set the title for this project - to modify the project title. To change the TransGen project name, click in the white window where you wish to add or delete new characters from the name and update as required or double click to select the current name and type in new project name. The title is incorporated into any output files requested via the Output - simulator input page of WizGen. To continue the workflow, click on Next >> to view/edit the Coordinate System page. Alternatively, click on Contents to view/modify any or all of the current Contents of the previously saved TGDATA file for the current basic Project, inspect the project's TGDATA file and/or inspect the log generated by last TransGen calculation for the current project. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. [UP] [TOP] [HOME]");sQ1[77]=new Array("TGmanual/108.html","Coordinate system page","","[UP] [TOP] [HOME] Coordinate System page This is the Next >> page accessed in WizGen, Basic project mode from the Title page or by selecting the Goto... button for Specify the coordinate system containing the input data from the Contents page. It allows the user to specify the layout of the input data, define the number of Columns, Rows and Layers in the model and optionally change the units of measurement in the project from the Metric default setting. TransGen uses the Eclipse standard ordering by default, as shown above. The ordering of data in the Eclipse standard and RMS output is always in row order.  In the Eclipse standard,  the origin of the model (Row 1, Column 1) is at the top left of the model.  Rows increase downwards, and the XY coordinates which define the position of the COORD lines are given relative to the model origin, with Y increasing downwards. However, in other models the position of the origin and the direction in which rows and columns increase may differ.  (RMS for example, provides many options to output the data in different ways.)  Also, the co-ordinates that defined the positions of the COORD lines may be given as a local coordinate system relative to the model origin (as per Eclipse), or relative to a geographic origin with Y increasing upwards (the RMS default). The appropriate system must be selected; if  incorrect, the model will either be mirrored or the cells will be inactivated as they have a negative volume. A diagram in map view, showing the nature of the Coordinate system is shown for each of the options. The position of the origin is shown by a blue diamond Rows are shown by bold red arrows, row numbers increasing with the length of the arrow Columns are shown thinner arrows, column numbers increasing with the length of the arrow The directions in which the X and Y coordinates increase are shown by black lines.  These coordinates are used to define the position of the COORD lines. HINT:- System 3 RMS with real world coordinates (with Y increasing upwards) is a common form of RMS output. Defining the Coordinate System 1. Either retain the System 1 Eclipse standard (default) or select the relevant coordinate layout for the input data. This setting defines the parameters for the TGAXES keyword in the TGDATA run file. 2. Input the number of Columns, Rows and Layers in the current Grid-block model for the current project - no defaults are supplied for these values in a new project - values MUST be entered by the user. These settings will define the parameters for the DIMENS or SPECGRID keyword in the TGDATA runfile. NOTE:- If you click on either the <<Back or Next>> button to leave this page before inputting values for the Cols, Rows and Lyrs, the following Error Pop-up will be displayed. 3. Optionally change the default Units setting from METRIC (i.e. in metres) to either FIELD (i.e. in feet) or LAB (i.e. in centimetres). This sets the units of measurement assumed in the project and sets the METRIC, FIELD or LAB keyword in the TGDATA run file. To continue the workflow, click on Next >> to view/edit the Included Data page. Alternatively, click on the << Back button to return to the Title page to view/edit the title for the current project and/or whether the data is treated as a Basic Project or a Flexible Project in the current runfile. Or click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. [UP] [TOP] [HOME]");sQ1[78]=new Array("TGmanual/109.html","Included Data page","","[UP] [TOP] [HOME] Included Data page This is the Next >> page accessed in WizGen Basic project mode from the Coordinate System page or by selecting the Goto... button for Choose which data files are included from the Contents page. The relevant input data blocks created via FileGen should be included in the TransGen project runfile (i.e. <project>.TGDATA).  Additional data may also be included at this stage. The Included Data page of WizGen will initially be blank, as shown above. Adding Data Files 1. To add a data file, click on the top Browse... button to open a file selection window, shown below. 2. Navigate to the <project>_INPUT directory (e.g. F64_New_INPUT) and click on a file, e.g. COORD.DATA to select it. 3. Click on OK to load the selected file into the Included Data window of WizGen. 4. Repeat to add all other files. Data to include In order to load and view a model, the data associated with the following Eclipse keywords MUST be the first two files added to the Included Data page of WizGen in the following order:- COORD                            - to define the map position of the cell corners ZCORN                             - to define the depth of the cell corners Additionally, in order to view cell and fault properties and to generate transmissibility multipliers, the data associated with the following keywords are required:- PERMX and PERMY     - to define cell permeabilities NTG or TGVS or both    - to define the shale content of the cells MULTX and MULTY      - optionally to import grid-block-based transmissibility multipliers from Eclipse (new to TransGen version 3 - see section on Including Transmissibility Multipliers from Eclipse for details) Other possible data files to include are those associated with keywords that modify the data arrays (ADD, COPY, EQUALS, MULTIPLY) if these are present in the original Eclipse run file to ensure TransGen uses the same data as Eclipse. Similarly, if any of keywords which control which cells are active (i.e. ACTNUM, MINPV, MINPVV, PORO) are present in the Eclipse run file, these should also be included to ensure TransGen identifies the same cell/cell connections as Eclipse. Optionally, the data files associated with the keywords PERMZ, FAULTS, TGWELL, TGSTRLNE, TGXSECT can be added for visualisation purposes. If you are proposing to calculate the Clay Smear Potential of the fault-rock using Defined shale cells (see CSP options on the Fault Rock Properties page), a file containing appropriate data associated with the TGSHALE keyword must be included. If you choose to calculate the effective vshale based on either Vshale only or NTG and Vshale, (see Effective vshale computation method on the Fault Rock Properties page), a file containing appropriate data associated with the TGVS keyword must be included. See the sections on TransGen data requirements and/or on Keywords for further details. When all the relevant  files have been added, click on the Next>> button to view/edit Miscellaneous Options page. Alternatively, click on the << Back button to return to the Coordinate System page to view/edit the layout of the input data, the number of Rows, Columns and Layers in the current project and the Units setting. Or click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. Including Transmissibility Multipliers from Eclipse [UP] [TOP] [HOME]");sQ1[79]=new Array("TGmanual/110.html","Miscellaneous Options page","","[UP] [TOP] [HOME] Miscellaneous Options page This is the Next >> page accessed in WizGen Basic project mode from the Included Data page or by selecting the Goto... button for Miscellaneous options from the Contents page. The only options currently available on this page to Basic Project users are to:- change the Lower limits from the default settings. toggle "on" the option Do not perform calculation to just view the current input data in ViewGen In Basic project mode, both the NTG Discretisation and the FSP units options are currently inoperative (greyed-out). The NTG Discretisation functionality will be implemented sometime in the future to select where shale is positioned within cells. The FSP units control is automatically locked to FSPs in metric "on" in Basic project mode, so the TGMETRIC keyword (new to TransGen 3) is automatically added to the TGDATA run file. With the TGMETRIC keyword included (i.e. activated), fault displacement, fault rock thickness and all calculated Fault Seal Potential measures are reported (both graphically & in output files) and stored internally within TransGen using metres as the unit of length, regardless of the current Units setting (Metric, Field or Lab) on the Coordinate System page. Lower limits Unfaulted transmissibility cutoff:- sets a minimum unfaulted transmissibility any connection must have to be output. It defines the TGMINTR keyword in the TGDATA run file and follows the default value used in Eclipse for this property. This cutoff is provided to allow TransGen to match Eclipse behaviour and should only be changed in exceptional circumstances to mirror changes in the parent simulator run file. Cell volume error tolerance:- this cutoff is used by TransGen as a precision limit for rejecting badly constructed cells and defines the TGVOLERR keyword in the TGDATA run file.  It is different from the Eclipse limit of minimum cell pore volumes (Eclipse MINPV keyword) which TransGen also recognises.  A cell is flagged as inactive by TransGen, if any component tetrahedra have a volume of less than minus this value or the total cell volume is less than this volume. Cell pore volume cut-off:- this cutoff defines the MINPV keyword in the TGDATA run file, which is then used by TransGen to render inactive any cells which have a pore volume less than the defined threshold. This cutoff is provided to allow TransGen to match Eclipse behaviour and should only be changed from the default value (1.0e-06) to mirror changes in the simulator run file. HINT:- Only change these default Lower limits either to reflect changes from the defaults in the parent Eclipse run file or in the case of Cell volume error tolerance to change the limit used to identify and exclude geometrically corrupt cells from the calculations in TransGen. Do not perform calculation By default, the Do not perform calculation option is toggled "off", i.e. Fault Seal Potential measures and Permeabilities set on the Fault Rock Properties page of WizGen will automatically be calculated when ViewGen is selected for the generated TGDATA run file. 2. If you want to use ViewGen to just view the geometry of the current TransGen model prior to running any FSP and Transmissibility multiplier calculations, click on the button to turn the Do not perform calculation option "on". 3. When the Miscellaneous Options page is set as required, click on the Next>> button to view/edit the Fault Rock Properties page. Alternatively, click on the << Back button to return to the Included Data page to view/edit the data included in the current runfile. Or click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. [UP] [TOP] [HOME]");sQ1[80]=new Array("TGmanual/111.html","Fault Rock Properties page","","[UP] [TOP] [HOME] Fault Rock Properties page This is the Next >> page accessed from WizGen in Basic project mode from the Miscellaneous Options page or by selecting the Goto... button for Determine the fault rocks properties from the Contents page. The Fault Rock Properties page of WizGen in Basic project mode offers options to:- calculate Fault permeability as a function of combinations of two Fault Seal Potential measures, i.e. Clay Smear Potential (CSP) and/or Shale Gouge Ratio (SGR) define the constants (a and b) in the equation for calculating fault rock Thickness from fault Displacement. select the Effective Vshale computation method dependant on the input data (i.e. the imported Net-to-Gross and/or Vshale data defining the shale content of the cellular grid). define the form of the Clay Smear Potential algorithm. define the relationship between SGR, CSP and fault rock permeability (CSP cutoff and SGR constants a, b, c, d) In order for the calculations in TransGen version 3 to run, plugins to compute thickness and permeability must be supplied. Using WizGen in Basic project mode automatically generates and rewrites these plugins whenever new Fault Rock Properties page settings are saved. The two plugins are stored in the following specially named files in the project's `_INPUT/.plugins' directory as:- <current_directory>/<project_title>_INPUT/.plugins/_AUTO_THICK_PLUGIN.cpp <current_directory>/<project_title>_INPUT/.plugins/_AUTO_PERM_PLUGIN.cpp and are added as strings referenced to the TGPLUGIN keyword in the TGDATA run file. For further details refer to the section on Plugins generated by WizGen in Basic project mode. The selected CSP and/or SGR settings are saved to the TGDATA file under the new TGFSP keyword. The relationships between the calculated Fault Seal Potential(s) of the fault-rock and the permeabilities are shown in the Fault property relationships text, top right on the Fault Rock Properties page (as shown below). HINT:- See the Technical Description for details on how TransGen calculates fault-rock permeabilities and transmissibilities from the Fault Seal Potential(s) using the Fault Rock Properties settings. Fault permeability is a function of TransGen in "Basic project" mode offers three options for calculating fault-rock permeability based on combinations of two different Fault Seal Potential measures, i.e. Shale Gouge Ratio (SGR) and/or Clay Smear Potential (CSP). NOTE:- This and other Fault Property relationships settings, defined on the Fault Rock Properties page, determine the format of the automatically generated PERM plugin used to calculate fault permeabilities and ultimately transmissibility multipliers (see Technical Description of what TransGen does for details). SGR (Shale Gouge Ratio) SGR provides a measure of the proportion (ratio) of shale in the fault zone assuming shale material is incorporated into the fault gouge in the same proportions as it occurs in the wall rocks of the slipped interval.  A high SGR is expected to correspond to more phyllosilicates in the fault zone and therefore greater seal potential. The shale gouge ratio is the distance-weighted average of the shale content of the rocks that have moved past a point on a fault.  For each faulted cell, TransGen calculates the SGR from the effective vshale content of the cells that have moved past it along the direction of the COORD lines. SGR is calculated at each vertex of the intersection polygon, on both sides of the fault, so there are two SGR values for each vertex. An average SGR is calculated for each faulted cell-to-cell connection, i.e. the SGR of the fault-rock is taken as the average of the footwall and hangingwall SGR values for connecting cells:- See section on the Calculation of Shale Gouge Ratio in the Technical Description of what TransGen does for further details. CSP (Clay Smear Potential) CSP provides a measure of clay smear (in terms of thickness) incorporated into the fault zone based on the shale source bed Thickness and displacement Distance. CSP increases with shale source bed thickness (there is more material to incorporate into the fault zone) and decreases with increasing distance from the source bed (as displacement at the fault increases, the shale incorporated into the fault zone becomes thinner). The thicker the Clay Smear, the greater the fault seal potential. The shale source beds are identified as Named layers, via the Evshale cutoff or as Defined shale cells. See section on the Calculation of Clay Smear Potential in the Technical Description of what TransGen does for further details. NOTE:- As the calculation of Clay Smear Potential is strictly only valid where reservoir (i.e. non-shales) are juxtaposed across a fault, inactive CSP values of -1 are automatically assigned where shale layers are juxtaposed across a fault, i.e. incalculable CSP values that tend to infinity. For further details, see Inactive FSP values in the section on Issues associated with FSP calculations. The calculated permeability, faulted transmissibilities and transmissibility multiplier values will be set to 0.0 where the CSP values are -1.0. Only SGR Using the Only SGR (default) setting, the Fault permeabilities are calculated from the SGR values using the following expression, where a, b, c and d are set by default to 0.4, 4.0, 0.25 and 5.0 in the SGR options. NOTE:- Only SGR is the default function to determine fault permeability using TransGen version 3.1 in Basic project mode, performing fault permeability calculations in a similar way to the default calculations in TransGen version 2. Only CSP Using the Only CSP setting, the Fault permeability is set to zero when the calculated CSP value is greater than the user-specified CSP cutoff (i.e. clay smear thicknesses greater than the cutoff value are assumed to be totally sealing). Otherwise, the fault permeabilities are set to the average of the unfaulted Permeabilities on either side of the fault. CSP then SGR When CSP then SGR is used, the Permeability is set to zero when the CSP value is greater than the user-specified CSP cutoff (i.e. clay smear thicknesses at or greater than the cutoff value are assumed to be totally sealing). Otherwise, the Fault permeabilities are calculated from the SGR values using the above expression, where a, b, c and d are set by default to 0.4, 4.0, 0.25 and 5.0 in the SGR options. Displacement to Thickness options These constants define fault rock thickness as a fraction of fault displacement. The equation used to calculate fault thickness as a function of fault displacement is:- where THICKf and Df are the thickness and displacement at a particular connection vertex.  The constants a and b default to 0.005882 (1/170) and 1 respectively (following Manzocchi et al. 1999). To change either Constants, double click on the current value and type in required new constant. NOTE:- These constants are substituted in the automatically generated THICK plugin used to calculate fault-rock thickness and ultimately the transmissibility multipliers (see Technical Description of what TransGen does for details).  Effective vshale computation method The fault-rock composition is controlled by the Effective Vshale (Evshale) values of the grid blocks. The Effective vshale can be calculated in one of the 3 following methods dependant on the availability of Net-to-Gross and vshale data. i.e. what data has been imported via the Included data page. Net-to-gross only - TransGen considers the non-net region to be shale and takes the shale content to equal 1 minus the Net-to-Gross value (where Net-to-Gross is the ratio of the net thickness of good reservoir, i.e. sand to gross interval thickness). Vshale only - TransGen takes Vshale as the shale content. NGT and VShale - TransGen assumes the non-net region to be pure shale, and takes the Effective Vshale content of a grid block i to be:- The Net-to-gross data has to be input into the current TransGen project as data associated with the Eclipse format keyword NTG from the flow simulation model. To use Vshale data in the calculations, it must be defined and loaded using the TGVS keyword. The file(s) containing either the NTG and/or TGVS keyword(s) plus the associated data for all the grid cells in the current model must be added to the current TransGen run via the Included Data page of WizGen. SGR options If either the Only SGR or CSP then SGR fault permeability calculation option has been selected, the SGR options displays editable default values for the SGR equation constants (a, b, c and d) in the following equation. To change any constant, double click on the current value and type in the required new constant. CSP options If you have chosen to calculate Fault permeability and Transmissibility multipliers as a function of either Only CSP or CSP then SGR, you will need to set the CSP options. Shale definition & Shale data settings Evshale cutoff With this option selected, the cells treated as shales can be defined by a single Shale data cutoff value. Click the Evshale cutoff option "on" and input a single cutoff value in the Shale data box, i.e. a floating point number between 0.0 and 1.0, such as 0.5. Cells with eVs below the specified cutoff are designated shale cells and are used in the current CSP calculation. Named layers With this option selected, named layers define the cells treated as shales. Click the Named layers option "on" and input the layers as a list separated by commas in the Shale data box. Multiple adjacent layers can be defined by a hyphen separating the first and last of these layers, e.g. `1,2,3,5,7,8,9,10' can be input as `1-3,5,7-10'. The list can be up to 256 characters long. Spaces are ignored (indeed spaces are removed by WizGen to shorten the length of the string). Defined shale cells With this option selected, the cells with values of 1.0 associated with the TGSHALE keyword are treated as shales. With an appropriate TGSHALE data file loaded into TransGen (via the Included Data page), click the Defined shale cells option "on". Cells with the TGSHALE value at 1.0 are designated shale cells and are used in the current CSP calculation. CSP cutoff (m) The CSP cutoff value is used when calculating fault permeability as a function of either Only CSP or CSP then SGR. If the calculated Clay Smear Potential exceeds the cutoff value, the permeability is automatically set to zero, i.e. clay smear assumed to be totally sealing. When the Fault Rock Properties page is set as required, click on Save to save the current settings to the TGDATA run file, then click on the Next>> button to view/edit the Output - simulator input page. Alternatively, click on the << Back button to return to the Miscellaneous Options page to view/edit the Lower limits for Multiplier and/or Cell volume cutoff and whether to perform calculation or not via ViewGen. Or click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. Plugins generated by WizGen in Basic project mode [UP] [TOP] [HOME]");sQ1[81]=new Array("TGmanual/112.html","Output - simulator input page","","[UP] [TOP] [HOME] Output - simulator input page This is the Next >> page accessed from WizGen in Basic project mode from the Fault Rock Properties page or by selecting the Goto... button for Specify simulator output options from the Contents page. This page allows the user to specify the output target of the calculation results generated by running the current TGDATA file via ViewGen. By default, the results that the ViewGen module of TransGen generates, are output to the graphical window., i.e. the Enable 3D graphics viewer after calculation has completed option is toggled "on", as shown below. This is optional as ViewGen can be run as a batch process. The graphical output may be toggled on or off.  A green box and a tick is shown when graphical output is enabled: The newly calculated transmissibilities (i.e. including the effects of fault-rock) from the current TransGen run need to be output as files containing data for the following three Eclipse-format keywords for inclusion in the Eclipse flow simulator model:- EDITNNC - to output Transmissibility multipliers for all faulted non-neighbour connections TRANX - to output X-direction transmissibilities for all faulted neighbour connections TRANY - to output Y-direction transmissibilities for all faulted neighbour connections NOTE:- The option to output data associated with the Eclipse NNC keyword will be greyed out and unsettable as this output is for transmissibilies for faulted non-neighbour connections NOT included in the original parent model, i.e. generated via the fault drag and hierarchical zone functionality in Flexible Project mode. HINT:- You may not initially want to output these files until you have viewed and perhaps recalculated the fault properties via ViewGen. Alternatively, Shell users can choose to output data suitable for inclusion in their in-house MoReS simulator. Similarly, users of the Roxar More (Modular Oil Reservoir Evaluation) simulator can choose to output data in a format suitable for direct inclusion in that flow simulation model, i.e. as NNC MULT, TX REPL & TY REPL format data. The file output for any of these data is activated by inputting directory/filename target either by typing the full pathname/filename in the relevant box or by selecting the appropriate Browse... button to open a File selection window in which to navigate to the required OUTPUT directory and select/input output file name. Directories can be selected by double-clicking with <MB1> in the Directories box ( the directory ending with two dots means go up a level).  Existing files can be selected by double-clicking with <MB1> in the Files box.  A new file can be created by appending a new filename to the existing (or reselected path in the Selection box).  Press OK to proceed, or Cancel to drop the changes.  This will return control to the Output page of WizGen. When the Output page is set as required, click on the Next >> button to view the current Project (TGDATA) File. Alternatively, click on the << Back button to return to the Fault Rock Properties page to view/edit the fault rock properties used to calculate fault permeabilities and transmissibility multipliers. Or click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. [UP] [TOP] [HOME]");sQ1[82]=new Array("TGmanual/113.html","Confirm TGDATA file page","","[PREV] [UP] [TOP] [HOME] [TOC] Confirm TGDATA file page This is the Next >> page accessed in WizGen from the Output page or by clicking on the << Back button three times on the Contents page. By this stage, the input to the TGDATA run file should be complete and a confirmation window will appear.  The runfile needs to be saved before it can be used in ViewGen to view the input model and perform the specified calculations.  Click on either the Confirm or Save button to save the current TGDATA file settings. Saving the results of the WizGen session: Click on the Confirm button to save the <Project>.TGDATA file and exit from WizGen; allowing ViewGen to be run to visualise the model and perform the calculations. Click on the Save button to save the <Project>.TGDATA file; allowing ViewGen to be run, to visualise the model and perform the calculations.  Selecting the Save option will leave WizGen open to allow the user to  examine and modify the .TGDATA file directly and to view the log of the last ViewGen run. Click on the Quit button to end the WizGen session, but the user will be asked if they wish to save the modified TGDATA file. Pressing << Back returns to the Output page. Pressing Next >> allows the user to view (and potentially edit, although this is best done via the relevant page in WizGen) the <Project>.TGDATA file. Click on the Contents button to access the Contents page to view/edit any of the current TGDATA file settings, inspect the project's TGDATA file and/or inspect the log generated by last ViewGen calculation. The next stage in the workflow is to run ViewGen.  This is launched from the the TransGen control menu.  Click here for details. [PREV] [UP] [TOP] [HOME] [TOC]");sQ1[83]=new Array("TGmanual/114.html","Contents page","","[UP] [TOP] [HOME] Contents page This page can be accessed any time when using the WizGen module by clicking on the Contents button or by clicking on the Next>> button in the window displaying the Session Log. Use the Contents page to view/edit any of the current WizGen page settings, inspect the currently saved project's TGDATA file and/or inspect the log generated by last TransGen calculation. Click on the relevant Goto... button (outlined in red in the menu below) to navigate to the appropriate contents in this Manual for full details. Only three of the five blue control buttons at the bottom of the window are operational on the Contents page. Click on <<Back, Save or Quit to have the following effects:- << Back button to page back through the WizGen pages starting with the Session Log window to examine the last ViewGen run log. Save to save any previously unsaved changes made in WizGen to the <Project>.TGDATA run file. Quit button to exit WizGen with or without saving any changes made to the <Project>.TGDATA file. NOTE:- Having saved the WizGen settings, the next stage in the workflow is to run ViewGen to visualise the input reservoir model and the new fault-related properties calculated using the current TGDATA run file. This is launched from the TransGen Control menu. [UP] [TOP] [HOME]");sQ1[84]=new Array("TGmanual/115.html","Section","","[UP] [TOP] [HOME] [TOC] Project (TGDATA) file window Click on Goto... button for this Advanced option on the Contents page of WizGen (as shown above), to launch the WizGen Project file editor (as shown below) displaying the currently saved settings in the Project (TGDATA) file.  By default, the Project (TGDATA) File is opened with the Read only mode toggled "on" (as shown below). The scroll bar at the right of the window enables the user to browse through the file. It is possible to edit the Project (TGDATA) runfile directly in this window by clicking on the Read Only "on" button (green tick) to turn it "off". It is then possible to edit the text directly in the white window. However, this method of editing the Project (TGDATA) file should only be used under special circumstances. A far more reliable method of editing the TGDATA file is on the relevant Page(s) of WizGen, i.e. click repeatedly on the << Back button until the relevant page(s) in WizGen are accessed, then reset and save the option(s) as required. Click on any of five blue control buttons at the bottom of the window to have the following effects:- << Back button to return to the Confirm TGDATA file page of WizGen. Next >> button to advance to the Session Log window (as shown below) to examine the last ViewGen run log. Contents button to return to the Contents page of WizGen. Save button to save the current <Project>.TGDATA runfile settings.  The button will be greyed out and inoperative if the current settings of the <Project> TGDATA file have already been saved. Quit button to exit WizGen with or without saving any changes made to the <Project>.TGDATA file. [UP] [TOP] [HOME] [TOC]");sQ1[85]=new Array("TGmanual/116.html","Section","","[UP] [TOP] [HOME] [TOC] Session Log window Click on Goto... button for the Advanced, Inspect the log generated by last TransGen calculation option on the Contents page of WizGen or on the Next >> button in the Project (TGDATA) File window (see above) to launch the Session Log window. The Session Log (stored in the <Project>.TGPRT file) is automatically generated when a saved version of the <Project>TGDATA file is run by clicking on the ViewGen icon in the TransGen Control Menu. Each step in the ViewGen run is given a new number.   The Session Log will report errors encountered during a ViewGen run, including report(s) of defective cells, as well as missing or defective keywords in the TransGen TGDATA runfile. Each step in the TransGen run is given a new number in the Session Log.  Warning messages are prefixed by an exclamation mark.  Use the scroll bar on the right of the window to browse up and down the file. The five blue control buttons at the bottom of the window are the same as the Project (TGDATA) File window and have the following effects:- << Back button returns the user to the Project (TGDATA) File window. Next >> button returns the user to the WizGen Contents Page. Contents button returns the user to the WizGen Contents Page. Save button is inactive. Quit button exits WizGen without saving the <Project>.TGDATA file. Typical warning messages in Session Log When reading the ZCORN section, a number of 'flat' cells will not be read in if they have zero thickness (i.e. four coincident Z values for the top and bottom of the grid block ).  They typically occur at unconformities. These cells have no volume,  have no connections and support no flow and are ignored by TransGen. After reading the END statement, TransGen will report the number of geometrically valid cells.  Some of these may be switched "off" by an ACTNUM keyword, or by having a zero permeability or porosity.  As Eclipse ignores these inactive cells, by default TransGen does not display them, but optionally for QC purposes they may be viewed in ViewGen.  These cells may contain Vshale or NTG data which is used by the SGR calculation.  However, no connections will be made to faulted inactive cells. After reading the END keyword, TransGen also reports the number of grid-blocks that have net pore volumes less than the limit set by the MINPV keyword.  TransGen, like Eclipse, treats cells with net pore volumes less than MINPV as inactive.  These should typically have small volumes. Cells with large negative volumes are the result of corrupt geometries.  These 'concave' cells are often the result of crossing COORD lines and should be investigated.  The location of these cells is given in the log file and whilst inactive cells are invisible by default in the viewer, they can be selected and displayed. TransGen reports the amount of memory used as a guide to the optimum hardware requirements. When a layer has been eroded from one side of a fault, typically the footwall, TransGen cannot determine the displacement for a layer directly from the data, but instead has to estimate the displacement from the adjacent layers.  In the case of footwall erosion it will use the displacement from the lower layers which are present on both sides of the fault.  TransGen reports when this occurs, and it is an indication that it is worth checking that the correct method is used for calculating SGR.  Where footwall erosion is present, SGR may be best determined from the hangingwall only. Faulted connections with transmissibility multipliers less than the multiplier cutoff limit will be ignored.  The number of these ignored connections will be reported by TransGen. [UP] [TOP] [HOME] [TOC]");sQ1[86]=new Array("TGmanual/117.html","Including Transmissibility Multipliers from Eclipse","","[UP] [TOP] [HOME] Including Transmissibility Multipliers from Eclipse MULTX, MULTY and MULTZ are grid-block-based transmissibility multipliers used by Eclipse. They have the same format as any other grid-block property (e.g. PERMX) and can be included in a TransGen run in exactly the same fashion. A MULTX value assigned to a cell (I, J, K) is applied to the transmissibilities between this cell and all cells with which it forms connections in the X+ direction (i.e. those with the indices (I+1, J, K*), where K* can take any value). Hence if no fault is present on the X+ side of cell (I, J, K), the multiplier is only applied to the single connection into cell (I+1, J, K), but if a fault is present, MULTX is applied to any connection (neighbour or non-neighbour) formed from (I, J, K) in this direction. MULTY and MULTZ are analogous and apply to connections in the Y+ direction and Z+ directions respectively. MULTX and MULTY can have an influence on faulted connections. The figures below shows XZ cross-sections of a simulation model. Figure (a) shows cells with very low MULTZ values of 0.001shaded (i.e. low transmissibility due to dipping shales) and cells with high MULTZ values of 1.0 in white. Fig (b) shows the same values, but with the cells indexed to MULTX. Figure (c) shows that between them, these 2 sets of multipliers define the 2 continuous sedimentological transmissibility baffles. Figure (d) shows a faulted version of this model, with the (2D) cell indices labelled for grid-blocks that will be influenced by the MULTX values. If MULTX is included in the TransGen run file, the "faulted" (i.e. including fault rock) and "unfaulted" (i.e. the simulator default which excludes fault rock) transmissibilties across all faulted connections will be calculated including the MULTX values. (See TransGen Transmissibility Calculations in the Technical Description of what TransGen does for details). The EDITNNC, TRANX and TRANY output files will contain values (for non-neighbour and neighbour connections) representative of both the fault rock present on the connection and the MULTX and MULTY values. Since the MULT value is included in both the faulted and unfaulted transmissibility calculations, the transmissibility multipliers for non-neighbour connections (as output in the EDITNNC file) are the same irrespective of whether the MULT values were included in TransGen or not. However, the transmissibilities output in the TRAN files (for neighbour connections) will be different. For instance, the connection between cells (4,3) and (5,2) is a non- neighbour connection and Eclipse will calculate its transmissibility including the MULTX value applied to cell (4,3). The EDITNNC value calculated by TransGen will simply lower this (already low) value as a function of the fault rock present. The Eclipse calculation of the neighbour connection between cells (4,3) and (5,3), however, is overwritten by the contents of TransGen's output TRANX file, which there is calculated as a function of both MULTX and fault rock. This is a simple, but not necessarily ideal solution. In most cases, the fault geometry breaks up the continuity of the baffles, as would be expected. In the example in Figure (d), however, one connection (between cells (1,6) and (2,5)) will be influenced by the baffle where perhaps it shouldn't, as the displacement on the fault is less than a grid-block height, and the fault offset is in the opposite sense to the dip direction of the surface. Sedimentological baffles represented in this way cannot be used directly in TransGen Light fault seal calculations (e.g. to form a continuous shale smear on the connection between blocks (3,3) and (4,4)). NOTE: Sedimentological baffles should probably not be modelled in this way; i.e. as a continuous surface with a constant low transmissibility multiplier. The reason for this is exactly the same as the reason that fault rock should not be modelled as continuous surfaces with a constant low transmissibility multiplier. A constant transmissibility multiplier in a heterogeneous reservoirs implies that the properties of the baffle are heterogeneous (irrespective of whether it is a thin zone of low permeability fault rock or a thin low permeability shale drape), and this heterogeneity has no geological significance but is simply an artefact of modelling geological features using constant transmissibility multipliers. MULTZ has no influence on the transmissibility calculations in TransGen. It is a recognized keyword and, if used, does not need to be specified using TGNEWKEY. In this respect it is treated by TransGen in exactly the same way as PERMZ. [UP] [TOP] [HOME]");sQ1[87]=new Array("TGmanual/118.html","Including Transmissibility Multipliers from Eclipse","","[UP] [TOP] [HOME] Including Transmissibility Multipliers from Eclipse MULTX, MULTY and MULTZ are grid-block-based transmissibility multipliers used by Eclipse. They have the same format as any other grid-block property (e.g. PERMX) and can be included in a TransGen run in exactly the same fashion. A MULTX value assigned to a cell (I, J, K) is applied to the transmissibilities between this cell and all cells with which it forms connections in the X+ direction (i.e. those with the indices (I+1, J, K*), where K* can take any value). Hence if no fault is present on the X+ side of cell (I, J, K), the multiplier is only applied to the single connection into cell (I+1, J, K), but if a fault is present, MULTX is applied to any connection (neighbour or non-neighbour) formed from (I, J, K) in this direction. MULTY and MULTZ are analogous and apply to connections in the Y+ direction and Z+ directions respectively. MULTX and MULTY can have an influence on faulted connections. The figures below shows XZ cross-sections of a simulation model. Figure (a) shows cells with very low MULTZ values of 0.001 shaded (i.e. low transmissibility due to dipping shales) and cells with high MULTZ values of 1.0 in white. Fig (b) shows the same values, but with the cells indexed to MULTX. Figure (c) shows that between them, these 2 sets of multipliers define the 2 continuous sedimentological transmissibility baffles. Figure (d) shows a faulted version of this model, with the (2D) cell indices labelled for grid-blocks that will be influenced by the MULTX values. If MULTX is included in the TransGen run file, the "faulted" (i.e. including fault-rock) and "unfaulted" (i.e. the simulator default which excludes fault-rock) transmissibilties across all faulted connections will be calculated including the MULTX values. (See TransGen Transmissibility Calculations in the Technical Description of what TransGen does for details). The EDITNNC, TRANX and TRANY output files will contain values (for non-neighbour and neighbour connections) representative of both the fault rock present on the connection and the MULTX and MULTY values. Since the MULT value is included in both the faulted and unfaulted transmissibility calculations, the transmissibility multipliers for non-neighbour connections (as output in the EDITNNC file) are the same irrespective of whether the MULT values were included in TransGen or not. However, the transmissibilities output in the TRAN files (for neighbour connections) will be different. For instance, the connection between cells (4,3) and (5,2) is a non- neighbour connection and Eclipse will calculate its transmissibility including the MULTX value applied to cell (4,3). The EDITNNC value calculated by TransGen will simply lower this (already low) value as a function of the fault rock present. The Eclipse calculation of the neighbour connection between cells (4,3) and (5,3), however, is overwritten by the contents of TransGen's output TRANX file, which there is calculated as a function of both MULTX and fault rock. This is a simple, but not necessarily ideal solution. In most cases, the fault geometry breaks up the continuity of the baffles, as would be expected. In the example in Figure (d), however, one connection (between cells (1,6) and (2,5)) will be influenced by the baffle where perhaps it shouldn't, as the displacement on the fault is less than a grid-block height, and the fault offset is in the opposite sense to the dip direction of the surface. Sedimentological baffles represented in this way cannot be used directly in TransGen fault seal calculations (e.g. to form a continuous shale smear on the connection between blocks (3,3) and (4,4)). However, a bit of imagination with the CELLPROP plugin (to assign effective Vshale values partly as a function of the MULTX, MULTY and MULTZ), the TGFSP keyword, and the PERM and THICK plugins would probably allow this kind of effect to be modelled. NOTE: Sedimentological baffles should probably not be modelled in this way; i.e. as a continuous surface with a constant low transmissibility multiplier. The reason for this is exactly the same as the reason that fault rock should not be modelled as continuous surfaces with a constant low transmissibility multiplier. A constant transmissibility multiplier in a heterogeneous reservoirs implies that the properties of the baffle are heterogeneous (irrespective of whether it is a thin zone of low permeability fault rock or a thin low permeability shale drape), and this heterogeneity has no geological significance but is simply an artefact of modelling geological features using constant transmissibility multipliers. MULTZ has no influence on the transmissibility calculations in TransGen. It is a recognized keyword and, if used, does not need to be specified using TGNEWKEY. In this respect it is treated by TransGen in exactly the same way as PERMZ. [UP] [TOP] [HOME]");sQ1[88]=new Array("TGmanual/119.html","Plugins generated by WizGen in Basic project mode","","[UP] [TOP] [HOME] Plugins generated by WizGen in Basic project mode The plugins _AUTO_THICK_PLUGIN.cpp and _AUTO_PERM_PLUGIN.ccp are automatically generated and stored in the project's "<project_name>_INPUT/.plugins"  directory and included in the TGDATA run file under the TGPLUGIN keyword when the Fault Rock Properties settings are saved via WizGen in Basic project mode. WizGen in Basic project mode generates different forms of PERM plugin depending on which of the three fault permeability model options is selected, whereas the form of the THICK plugin is the same for all models. The constants used in both the THICK and PERM plugins are read from the Fault Rock Properties page and substituted into the plugin codes. Correspondingly, when WizGen is started in Basic project mode, the constants currently in the plugins are loaded into the Fault Rock Properties page. THICK plugin The code generated for the THICK plugin by WizGen in Basic project mode and stored in the file `_AUTO_THICK_PLUGIN.cpp' is:-  // This plugin code was generated by WizGen // to compute fault thickness // PLEASE DO NOT EDIT THIS FILE BY HAND double const_min_displ = 0.001; double const_a = 0.005882; double const_b = 1; if (v.displ < const_min_displ) {   v.thick = const_a * pow(const_min_displ, const_b); } else {   v.thick = const_a * pow(v.displ, const_b); } Where `a' and `b' are substituted from the Displacement to Thickness constants set on the Fault Rock Properties page. PERM plugin calculated from CSP only The code generated for the PERM plugin by WizGen in Basic project mode when calculating Fault permeability as a function of Only CSP and stored in the file `_AUTO_PERM_PLUGIN.cpp' is:-  // AUTO_PLUGIN_TYPE:CSP_ONLY // This plugin code was generated by WizGen // to compute fault permeability // PLEASE DO NOT EDIT THIS FILE BY HAND double const_cutoff = 5; double const_a = 0.4; double const_b = 4; double const_c = 0.25; double const_d = 5; double perm1, perm2; if (c.dir == DIR_X) {   perm1 = up.permx;   perm2 = down.permx; } else {   perm1 = up.permy;   perm2 = down.permy; } // vertex permeability set to zero if csp greater than cutoff or csp undefined if (v.csp > const_cutoff || v.csp == UNDEFINED_VALUE) {   v.perm = 0.0; } // set vertex permeability to harmonic average of the two grid-block perms else {   v.perm = 1.0 / ((0.5 / perm1) + (0.5 / perm2)); } where `cutoff' is substituted from the CSP cutoff value input by the user on the Fault Rock Properties page of WizGen in Basic project mode. NOTE:- The other constants defined in this plugin are not used in the calculations. Using the Only CSP setting, the Fault permeability is set to zero when the calculated CSP value is greater than the user-specified CSP cutoff (i.e. clay smear thicknesses greater than the cutoff value are assumed to be totally sealing). Otherwise, the fault permeabilities are set to the average of the unfaulted Permeabilities on either side of the fault. PERM plugin calculated from SGR only The code generated for the PERM plugin by WizGen in Basic project mode when calculating Fault permeability as a function of Only SGR and stored in the file `_AUTO_PERM_PLUGIN.cpp' is:-  // AUTO_PLUGIN_TYPE:SGR_ONLY // This plugin code was generated by WizGen // to compute fault permeability // PLEASE DO NOT EDIT THIS FILE BY HAND double const_cutoff = 5; double const_a = 0.4; double const_b = 4; double const_c = 0.25; double const_d = 5; double term1 = const_a - const_b * v.sgr; double term2 = const_c * pow(1.0 - v.sgr, const_d); v.perm = pow(10.0, term1 - term2); The values of the constants are read from the SGR options on the Fault Rock Properties page of WizGen in Basic project mode. The TransGen version 3 WizGen in Basic project mode uses the following expression (without dependence on fault rock displacement) for calculating permeability from SGR values based on the compilation of data by Manzocchi et al. (1999) - see Fault Permeability Calculation in the Technical Description of what TransGen does:- PERM plugin calculated from CSP, then SGR The code generated for the PERM plugin by WizGen in Basic project mode when calculating Fault permeability as a function of CSP then SGR and stored in the file `_AUTO_PERM_PLUGIN.cpp' is:-  // AUTO_PLUGIN_TYPE:CSP_THEN_SGR // This plugin code was generated by WizGen // to compute fault permeability // PLEASE DO NOT EDIT THIS FILE BY HAND double const_cutoff = 5; double const_a = 0.4; double const_b = 4; double const_c = 0.25; double const_d = 5; // vertex permeability set to zero if csp greater than cutoff or csp undefined if (v.csp > const_cutoff || v.csp == UNDEFINED_VALUE) {   v.perm = 0.0; } // set vertex permeability based on vertex sgr else {   double term1 = const_a - const_b * v.sgr;   double term2 = const_c * pow(1.0 - v.sgr, const_d);   v.perm = pow(10.0, term1 - term2); } The values of the constants are read from the Fault Rock Properties page of WizGen in Basic project mode. If the Fault permeability option CSP then SGR is selected, both these FSPs are calculated and the fault permeability calculation is a hybrid of these two methods, i.e. if the CSP at a connection is lower than the user-specified CSP cutoff, the fault permeability is calculated as a function of SGR using the expression given above. While if the CSP is greater than the cutoff (i.e. clay smear thicknesses greater than the cutoff value are assumed to be totally sealing), the fault permeability is set to zero. [UP] [TOP] [HOME]");sQ1[89]=new Array("TGmanual/120.html","Project (TGDATA) File","","[UP] [TOP] [HOME] Project (TGDATA) File page This is the Next >> page accessed from WizGen in Basic project mode from the Output - simulator input page or by selecting the Goto... button for the Inspect the project's TGDATA file option from the Contents page. By default, the Project (TGDATA) File is opened with the Read only mode toggled "on" (as shown below). The scroll bar at the right of the window enables the user to browse through the file. It is possible to edit the Project (TGDATA) runfile directly in this window by clicking on the Read Only "on" button (green tick) to turn it "off". It is then possible to edit the text directly in the white window. However, this method of editing the Project (TGDATA) file should only be used under special circumstances. A far more reliable method of editing the TGDATA file is on the relevant Page(s) of WizGen, i.e. click repeatedly on the << Back button until the relevant page(s) in WizGen are accessed, then reset and save the option(s) as required. Click on any of five blue control buttons at the bottom of the window to have the following effects:- << Back button to return to the Output - simulator input page of WizGen. Next >> button to advance to the Session Log window to examine the last ViewGen generated log file. Contents button to return to the Contents page of WizGen. Save button to save any updates made in WizGen to the <Project>.TGDATA run file settings.  The button will be greyed out and inoperative if the current settings of the <Project> TGDATA file have already been saved. Quit button to exit WizGen with or without saving any changes made to the <Project>.TGDATA file. [UP] [TOP] [HOME]");sQ1[90]=new Array("TGmanual/122.html","Session Log","","[UP] [TOP] [HOME] Session Log window This is the Next >> page accessed in WizGen from the Project (TGDATA) File page or by selecting the Goto... button for the Inspect the log generated by last TransGen calculation option from the Contents page. The Session Log is automatically generated when a saved version of the <Project>TGDATA file is run by clicking on the ViewGen icon in the TransGen Control Menu. Each step in the ViewGen run is given a new number.   The Session Log will report errors encountered during a ViewGen run, including report(s) of defective cells, as well as missing or defective keywords in the TransGen TGDATA runfile. Each step in the TransGen run is given a new number in the Session Log.  Warning messages are prefixed by an exclamation mark.  Use the scroll bar on the right of the window to browse up and down the file. The five blue control buttons at the bottom of the window are the same as the Project (TGDATA) File window and have the following effects:- << Back button returns the user to the Project (TGDATA) File window. Next >> button opens the WizGen Contents Page. Contents button opens the WizGen Contents Page. Save button to save the current <Project>.TGDATA runfile settings.  The button will be greyed out and inoperative if the current settings of the <Project> TGDATA file have already been saved. Quit button exits WizGen without saving the <Project>.TGDATA file. Typical warning messages in Session Log When reading the ZCORN section, a number of 'flat' cells will not be read in if they have zero thickness (i.e. four coincident Z values for the top and bottom of the grid block ).  They typically occur at unconformities. These cells have no volume,  have no connections and support no flow and are ignored by TransGen. After reading the END statement, TransGen will report the number of geometrically valid cells.  Some of these may be switched "off" by an ACTNUM keyword, or by having a zero permeability or porosity.  As Eclipse ignores these inactive cells, by default TransGen does not display them, but optionally for QC purposes they may be viewed in ViewGen.  These cells may contain Vshale or NTG data which is used by the SGR calculation.  However, no connections will be made to faulted inactive cells. After reading the END keyword, TransGen also reports the number of grid-blocks that have net pore volumes less than the limit set by the MINPV keyword.  TransGen, like Eclipse, treats cells with net pore volumes less than MINPV as inactive.  These should typically have small volumes. Cells with large negative volumes are the result of corrupt geometries.  These 'concave' cells are often the result of crossing COORD lines and should be investigated.  The location of these cells is given in the log file and whilst inactive cells are invisible by default in the viewer, they can be selected and displayed. TransGen reports the amount of memory used as a guide to the optimum hardware requirements. When a layer has been eroded from one side of a fault, typically the footwall, TransGen cannot determine the displacement for a layer directly from the data, but instead has to estimate the displacement from the adjacent layers.  In the case of footwall erosion it will use the displacement from the lower layers which are present on both sides of the fault.  TransGen reports when this occurs, and it is an indication that it is worth checking that the correct method is used for calculating SGR.  Where footwall erosion is present, SGR may be best determined from the hangingwall only. Faulted connections with transmissibility multipliers less than the multiplier cutoff limit will be ignored.  The number of these ignored connections will be reported by TransGen. [UP] [TOP] [HOME]");sQ1[91]=new Array("TGmanual/123.html","Output - derived and user-defined properties page","","[UP] [TOP] [HOME] Output - derived and user-defined properties page This is the Next >> page accessed when using WizGen in Flexible project mode from the Output - simulator input page or by selecting the Goto... button for Specify derived and user-defined property output options from the Contents page. This page allows the user to output derived and user-defined connection properties generated by running the currently saved TGDATA file via ViewGen. HINT:- While often useful, these properties cannot be used as input to the original simulator model. Apart from outputting data files of transmissibility multipliers and transmissibilities of all faulted connections for inclusion in the original Eclipse, MoReS or More reservoir simulation models (as set on the Output - simulator input page of WizGen), the user has options to output any of the following to file(s):- Derived Connection (C) properties FAULTS - an Eclipse format FAULTS file (TransGen will find the faults even if none were supplied) TRMULT - Transmissibility multipliers for each cell-cell connection AREA - Area of connection for each cell-cell connection FTRANS - Faulted transmissibilities for each cell-cell connection UFTRANS - Unfaulted transmissibilities for each cell-cell connection (transmissibility including fault juxtaposition, but excluding any fault-rock thickness) PERM - Fault permeability for each cell-cell connection THICK - Fault-rock thickness for each cell-cell connection THROW - Fault throw for each cell-cell connection FSP measures - any FSP measures calculated in the current run, e.g. csp_yielding, csp_fulljames, sgr values can each be output to data files (Up to 5 fault seal potential measures can be calculated in a single TransGen run as set via the Fault Seal Potential Variables page. One or more of these fault seal measures included in the PERM plugin via the User-defined plugins page will be used calculate fault permeability and hence across-fault transmissibilities including fault-rock thickness). NOTE:- All of the above connection properties could be selected as output to file(s) prior to the TransGen version 3.2 release. In general, most will be unchanged by inclusion of the new fault drag and hierarchical zone effects, reflecting only the parent model. However, the data output for TRMULT, UFTRANS and FTTRANS will include information about user-defined changes to the model, i.e. the UFTRANS, FTRANS and TRMULT output files will contain data for all connections in both the parent and user-defined models (see Changes to Connection property output in 3.2 release) Derived Trace (T) properties Five new output file type are available to output fault trace information generated from a TransGen run including fault drag and hierarchical zone effects.   TGTRACE - to output all 10 user-defined trace properties for those traces for which at least one has been modified from the default value, i.e. as applied by the TGTRACE input file in the current TransGen run. TGDRAG - to output drag ratio data for those traces where the input data has an effect on the output model geometry, i.e. where the drag ratio as applied by the TGDRAG input file in the current TransGen run is not equal to 1.0. TGTHROW - to output user-defined throw values for those traces where the input data has an effect on the output model geometry, i.e. where the user-defined fault throws as applied by the TGTHROW input file in the current TransGen run are not equal to 0.0. TGFZONE - to output all fault zone data applied in the current TransGen run, i.e. all TGFZONE data included in the current run. TGXTRACE - to output data containing summary information of every fault trace (system and user-defined) in the model (see section on the TGXTRACE keyword for details).  User-defined keywords (connections & cells) User-defined keywords - any cell and/or connection properties input as user-defined keywords and calculated in the current run. NOTE:- The names of fault seal potential measures are case-sensitive (sgr4 is NOT the same as SGR4), but both user-defined keywords and standard keywords are case-insensitive (i.e. PERM is the same as perm). The file output for any of these data is activated by inputting directory/filename target either by typing the full pathname/filename in the relevant box or by selecting the appropriate Browse... button to open a File selection window in which to navigate to the required OUTPUT directory and select/type in the output file name. When any of these extended Output settings are saved to the TGDATA run file, they are added as strings below the TGXRPT keyword, as shown below:- TGXRPT 'PERM=/output_directory/perm.txt' 'AREA=/output_directory/area.txt' TGXTRACE=/output_directory/tgxtrace.txt 'sgr=/output_directory/sgr.txt' 'CELL_PRESSURE=/output_directory/evshale1.txt' / With these settings, calculated values for the user-defined cell property "cell_press" and the FSP measure "sgr", together with the output file containing summary information on every fault trace in the current model will be output to the specified files when ViewGen is successfully run with the saved TGDATA file. NOTE:- The ability to output FSP measures and user-defined properties is new to the TransGen Version 3 release. The output format of connection properties will be the same as the Input format of user-defined connection properties. For example, the output format of the fault seal potential measure 'sgr.txt' will be written something like:- -- Connection property output for model: -- PUNQ Dynamic - TransGen project sgr -- IX IY IZ JX JY JZ VALUE 1 25 1 2 25 8 0.452703 / 1 25 1 2 25 10 0.532935 / 1 25 2 2 25 10 0.554008 / 1 25 2 2 25 11 0.569946 / 1 25 3 2 25 10 0.576589 / 1 25 3 2 25 11 0.606493 / 1 25 3 2 25 12 0.638795 / 1 25 4 2 25 11 0.647185 / . . 18 59 19 18 60 14 0.205064 / 18 59 20 18 60 14 0.238062 / 18 59 20 18 60 15 0.279552 / / The format specifier used is the C++ general floating point format which automatically employs exponential format for very large or very small numbers, i.e. 0.0000000003 will be output as 3e-10. When the Output - derived and user-defined properties page is set as required, click on the Next >> button to view the current settings in the Project (TGDATA) File. Alternatively, if the Include fault drag and hierarchical zone effecta option is toggled "on" via the Title page, clicking on the Next>> button will display the page to set the Drag applied to fault traces. Alternatively, if the Include two-phase fault rock calculations option is toggled "on" via the Title page, clicking on the Next>> button will display the first page for specifying Two phase flow - INPUT. Alternatively, click on the << Back button to return to the Output - simulator input page. Or click on the Contents button to access the Contents page to view/edit any of the current WizGen page settings, inspect the current TGDATA file and/or the session log generated by last ViewGen calculation. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. Changes to Connection property output in 3.2 release [UP] [TOP] [HOME]");sQ1[92]=new Array("TGmanual/124.html","Two phase flow - INPUT page","","[UP] [TOP] [HOME] Two phase flow - INPUT page This is the Next >> page accessed in WizGen (in "Flexible Project" mode) from the Output - derived and user-defined properties page or by selecting the Goto... button for Two phase flow - specify inputs for grouping calculations from the Contents page when the Include two-phase fault rock calculations option has been toggled "on" via the Title page of WizGen. NOTE:- The next three pages can only be accessed in WizGen if the TransGen installation is licensed to support the Two-phase flow module (see section below on Using the Two-phase flow functionality). The Two phase flow - INPUT page of WizGen allows the user to:- specify the file containing relative permeability tables. define the source of across-fault flow rates. input appropriate fluid properties. HINT:- Use the Demo dataset released with TransGen version 3.2. to compare single-phase and two-phase runs. Two runfiles (SINGLE_PHASE.TGDATA & TWO_PHASE.TGDATA) are included with the Demo data set for the 3D model described in Manzocchi et al. 2002 (see below) The directory ECL_SINGLE_PHASE contains the input (i.e. the file SINGLE_PHASE_FAULTS.DATA) and output (all the other files) for two-phase Eclipse run using only single-phase fault properties (which are calculated from the SINGLE_PHASE.TGDATA file above). The Directory ECL_TWO_PHASE contains input and output for a two-phase Eclipse run using two-phase fault rock properties calculated from the TWO_PHASE.TGDATA file  and uses one of the restart files from the Eclipse run above to get the across-fault flow rates. Manzocchi, T., Heath, A. E., Walsh, J. J., & Childs, C., 2002. The representation of two phase fault-rock properties in flow simulation models. Petroleum Geoscience, Vol. 8, 119-132. Cell relative permeability and capillary pressure Click on the Browse... button to navigate to the file containing the Eclipse SWOF keyword which defines the water relative permeability, oil relative permeability and water-oil capillary pressures as a function of water saturation. NOTE:- The Eclipse SWOF keyword is the only saturation function keyword recognised and supported by the current version of TransGen. Set the Cell index into tables to SATNUM i.e. the recognised Eclipse keyword which indexes each grid-cell in the model to a set of relative permeability and capillary pressure data as defined by the SWOF keyword. NOTE:- The SATNUM data file MUST to be loaded via the Included Data page of WizGen. However it does NOT need to be specified on the User-defined keywords page of WizGen as it is a recognised Eclipse keyword.  Source of across-fault flow rates The across-fault flow rates are loaded into the two-phase flow calculations in one of 4 ways:- Flow (from connection property) Pressure (from cell property) Pressure (from Eclipse restart file) Flow (from Eclipse restart file) In the first two cases, the relevant keyword must be declared on the User-defined keywords page with the associated data file loaded via the Included data page. HINT:- The loaded Across-fault flow rates can be displayed as fault properties and/or cell pressures as cell properties in ViewGen. The third option, i.e. calculating the flow rate from an Eclipse restart file, requires the relevant filename and location to be specified. Flow (from connection property) If the across-fault flow rates are loaded from connection property data, a single value of across- fault flow rate (Darcy velocity) should be loaded for each connection, using a user-defined keyword. The format of the file and the loading procedures are the same as for any other user-defined connection property, i.e. the property must be declared on the User-defined keywords page and the file loaded on the Included data page of WizGen. Both positive and negative values can be used, with a positive value signifying that the flow is from cell I1 J1 K1 to cell I2 J2 K2 and a negative value indicating flow from cell I2 J2 K2 to cell I1 J1 K1. The units of across- fault Darcy velocity are metres/day (METRIC), ft/day (FIELD) or cm/hour (LAB). Example: DARCY_VEL ---I1 J1 K1 I2 J2 K2 VALUE 1  7  1  2  7  4  -0.001893 / 1  7  1  2  7  5  -0.003168 / 1  7  1  2  7  6  -0.000793 / 1  7  1  2  7  7  -0.001144 / 1  7  2  2  7  5  -0.002425 / ... 36  111  20  36  112  15  0.03253 / 36  111  20  36  112  16  0.4242245 / / Pressure (from cell property) Alternatively the across- fault flow rate can be calculated from a grid of cell pressures. The data for these values are loaded into TransGen in the same way as any other user-defined cell property, i.e. the property must be declared on the User-defined keywords page and the file loaded on the Included data page of WizGen. The units of pressure are bars (METRIC), psi (FIELD) or atm (LAB). Example: CELL_PRESSURE --at 2 years, using PDO U. 265.23  264.91  266.45  266.19  266.16  265.78  265.69  265.58 265.51  265.24  265.14  266.75  298.17  302.67  304.21  305.56 306.7   307.81  309.13  310.6   312.16  313.78  315.23  316.04 330.31  330.31  330.31  330.31  330.31  330.31  330.31  330.31 330.31  330.31  330.31  330.31  330.31  330.31  330.31  330.31 ... 276.06  274.51  273.05  271.66  270.31  268.91  267.7   266.84 265.89  264.77  263.86  262.83  262.45  262.52  262.74  337.77 / Pressure (from Eclipse restart file) Alternatively the across-fault flow rates can be extracted from a specified Eclipse restart file (*.Xnnnn file output from Eclipse). Toggle the Obtain from Eclipse restart file option "on" then use the Browse... button to navigate to the relevant file. Flows derived from connection property pressure data in an Eclipse restart file, while being less accurate than flow data derived directly from an Eclipse restart file (see below), are probably more generally applicable and have the advantage of always being possible assuming restart files have been output, i.e. pressures are always written out when Eclipse writes restart files. Flow (from Eclipse restart file) Flows from connection properties in the Eclipse restart file can only be used if interblock flows (both neighbour and non-neighbour) are specified using the FLOWS option in the RPTRST keyword in the Eclipse run. This ensures the connection flows are written to each restart file. The user chooses a particular restart file from which to read the connection flows. NOTE:- When using either the Pressure or Flow (from Eclipse restart file) option as a source of across-fault flow rates, the EGRID file output by Eclipse is also necessary (and must be present in the same directory) as the particular restart file specified in WizGen. The EGRID file (one per Eclipse run) maps the order of the restart data to actual connections. Fluid Properties The following Reservoir constants are required in the two-phase calculations:- Oil and water viscosities: units are centipoise Oil and Water densities: units are kg per cubic metre (METRIC), lb per cubic foot (FIELD) or grams per cubic centimetre (LAB).  Oil-Water contact: unit in metres (METRIC), feet (FIELD) or cm (LAB) HINT:- For existing TransGen projects you may need to reset the density values to take account of the (new) standard dimensions. Oil and water densities in the previous TransGen 3.2 beta release were assumed to be in g/cc. Therefore users need to multiply their existing project density values by 1000 (for a METRIC project) or 62.42797 (for a FIELD project). A LAB project uses g/cc and so does not require altering. The viscosities are used in the up-scaling calculations. The fluid densities and the oil-water contact are used in the determination of the cycles (drainage or imbibition) of faulted connections. When the Two phase flow - page 1 is set as required, click on the Next >> button to view/edit the fault rock properties equation settings to calculate relative permeabilities for water and oil on Two phase flow - page 2. Alternatively, click on the << Back button to return to the Output - derived and user-defined properties page of WizGen. Or click on the Contents button to access the Contents page to view/edit any of the current WizGen page settings, inspect the current TGDATA file and/or the session log generated by last ViewGen calculation. Click on Save to save any modifications made on this page to the current TGDATA run file. Click on Quit to exit from WizGen with or without saving any changes to the TGDATA runfile. NOTE:- If you attempt to quit the Two phase flow page of WizGen without specifying a filename containing the relative permeability tables, a keyword for the flow rate data and/or inputting a numerical value for the Oil-water contact, the following Error Pop-up will be displayed. Click on OK to return to the page and input the required information or click on Ignore to proceed without specifying these data. Using the Two phase flow functionality [UP] [TOP] [HOME]");sQ1[93]=new Array("TGmanual/125.html","Two phase flow - FAULT ROCK PROPERTIES page","","[UP] [TOP] [HOME] Two phase flow - FAULT ROCK PROPERTIES page This is the Next >> page accessed in WizGen (in "Flexible Project" mode) from the Two phase flow - INPUT page or by selecting the Goto... button for Two phase flow - specify fault rock properties from the Contents page. This page deals with the relationships for defining the two-phase petrophysical fault rock properties. As for single-phase fault rock properties, the two-phase properties are calculated for each faulted connection in the model. The Two phase flow - FAULT ROCK PROPERTIES page of WizGen allows the user to set the equations (or 2Phase plugins) used to define:- Fault porosity. Water saturation at irreducible oil. Irreducible (connate) water saturation. Capillary pressure, Water relative permeability and Oil relative permeability for both Drainage and Imbibition. The symbols used on this page are defined below. NOTE:- The value of fault permeability for each connection derives from the single-phase TransGen calculations included in the ViewGen run. It is therefore important that the appropriate single-phase properties are used in a ViewGen run, even if the particular run is being performed primarily for determining two-phase properties. Check the PERM and THICK plugins are set appropriately via the User-defined plugins page. Each of the 9 two-phase properties can be represented by an equation or a plugin. By default, all the relationships are represented by Equations and default values are supplied for all the equation constants. The default relationships are based on published, generally heuristically-derived curves and are discussed in further detail in Manzocchi et al. (2002; Petroleum Geoscience 8, 119-132). The value of any Equation constant can be changed -  double click on the current value, type in the required new value and then click on Save to save the new setting(s) to the TGDATA file.  To use a plugin rather than the default equation to define a particular two-phase property, click on the Plugin button for that particular fault rock property (e.g. as shown below for Fault Porosity and Drainage Capillary Pressure) - the Equation constants are greyed-out and cannot be edited. Having selected the Plugin option for one or more properties, you need to return to the User-defined plugins WizGen page to define the plugin(s). Click on the <<Back, Next>> or Save button to display the following Pop-up window. Click on Yes to return to the User-defined plugins page to edit the new plugins. When the Two phase flow - page 2 is set as required, click on the Next >> button to view/edit the Groupings and Output settings on the Two phase flow - page 3. Alternatively, click on the << Back button to return to the Two phase flow - page 1 to view/edit the settings defining the Input source for relative permeability, across-fault flow rates and fluid properties data. Or click on the Contents button to access the Contents page to view/edit any of the current WizGen page settings, inspect the project's TGDATA file and/or inspect the session log generated by last ViewGen calculation. Click on Save to save any modifications made on this page to the current TGDATA run file. Click on Quit to exit from WizGen with or without saving any changes to the TGDATA runfile. [UP] [TOP] [HOME]");sQ1[94]=new Array("TGmanual/126.html","Two phase flow - GROUPINGS & OUTPUT page","","[UP] [TOP] [HOME] Two phase flow - GROUPINGS & OUTPUT page This is the Next >> page accessed in WizGen (in "Flexible Project" mode) from the Two phase flow - FAULT ROCK PROPERTIES page or by selecting the Goto... button for Two phase flow - specify groupings and output options from the Contents page. The Two phase flow - GROUPINGS page of WizGen allows the user to define:- how the Groupings of faulted grid-blocks are created. Output destinations for the Relative permeability tables and KRNUM files. Two phase flow - GROUPINGS A grouping is a set of faulted cell faces sharing similar properties for which the same up-scaled two phase properties are generated. The Groupings settings control the number of groups that ViewGen attempts to create and the structure of the hierarchy used to create the groups. A group is defined by 8 model variables:- FAULT CYCLE (Drainage or Imbibition) CELL SATNUM (i.e. original cell relative permeability and capillary pressure functions) FAULT PERMEABILITY (calculated from single-phase TransGen definitions) FAULT THICKNESS (calculated from single-phase TransGen definitions) FLOW RATE (imported directly or calculated from cell pressures) CELL PERMEABILITY (imported) CELL POROSITY (imported) CELL LENGTH (calculated from the model geometry) The cycle of the connection (Drainage or Imbibition) and the SWOF table of the faulted grid-block form the primary definitions of the groups. The number of further divisions can be defined by the user, by defining both the number of divisions to make on the basis of each variable and the priority of the variable in the grouping hierarchy. A different number of bins may be specified in the drainage and imbibition cycles, but the same parameter priorities are used for both. Parameter Priorities vary between 1 and 6 with a higher number giving greater priority to a parameter. For instance, if fault permeability is set a Parameter Priority of 6, fault permeability is positioned at the top of the hierarchy and the initial groupings are derived based on this. If three groups are specified for permeability, three sets of faulted connections are constructed based on the permeability values present. The next set of divisions (for the parameter with priority 5) is based on the values of the parameter present in each of the three bins. At each level in the hierarchy, the values of the next variable are binned based on the maximum and minimum values of the variable present in the previous bin, according to the number of divisions specified. Linear bins are used for fault thickness, cell porosity and cell length. Logarithmic bins are used for flow rate, fault permeability and cell permeability. The number of flow rate divisions is not allowed to be less than 2. This is because all cell faces with negative flow (i.e. flow is in the opposite direction) are assigned directional relative permeability functions calculated using a zero- flow rate. If less than 2 groupings are specified for flow rate by the user, WizGen issues an error. Two phase flow - OUTPUT Two-phase fault-rock properties are implemented in the simulator using directional, irreversible cell properties and TransGen outputs two files which should be included in the simulator to do this. The Two phase flow - OUTPUT settings are to specify the names of these two files, one of which will contain the new (pseudo) relative permeability and capillary tables output in the SWOF keyword (or MoReS compatible) format and the other to contain the "KRNUM" keywords which index the SWOF output into the faulted cells. NOTE:- Additionally, two constants required by the Eclipse simulator are reported on completion of running 2PhaseGen and in the header of the SWOF file. The Relative permeability tables and the KRNUM data can be output in either Eclipse, (SWOF keyword) or MoReS compatible format (for Shell users). Click either the SWOF or the MORES option "on", Browse to the required directory (e.g. the _OUTPUT directory in the current TransGen project), input an appropriate file name and Save the settings to output:- Relative permeability tables, i.e. a file containing the original and the new (pseudo) relative permeability and capillary tables (see Examples of output files for details). KRNUM  output, i.e. a file containing the KRNUM keywords (KRNUMX, KRNUMX-, KRNUMY, KRNUMY-, KRNUMZ, KRNUMZ-) plus associated indices to link the relative permeability tables output for each cell in the model (see example KRNUM output file for details). HINT:- The KRNUM output will be created at the end of a ViewGen run and the indices to the tables for KRnumX+, KRnumX-, KRnumY+ or KRnumY- can be displayed as cell properties in ViewGen. When the Two phase flow - page 3 is set as required, click on the Next >> button to view the current settings in the Project (TGDATA) File. Alternatively, click on the << Back button to return to the Two phase flow - page 2 to view/edit the settings for the fault rock properties used to calculate the relative water and oil permeabilities. Or click on the Contents button to access the Contents page to view/edit any of the current WizGen page settings, inspect the project's TGDATA file and/or inspect the session log generated by last ViewGen calculation. Click on Save to save any modifications made on this page to the current TGDATA run file. Click on Quit to exit from WizGen with or without saving any changes to the TGDATA runfile. NOTE:- If you attempt to quit the Two phase flow - page 3 without specifying filenames for the relative permeability tables and KRNUM output the following Error Pop-up will be displayed. Click on OK to return to page and input the required destinations or click on Ignore to proceed without specifying these data. Having completed both the single-phase and two-phase flow sections in WizGen, Save the settings and click on the ViewGen icon in the Control menu to check the two-phase fault rock data, create the cell groupings, output the KRNUM format file and display some of the input two-phase properties before using the 2PhaseGen application to create the new pseudo-relative permeability tables output for inclusion in the Simulator model. [UP] [TOP] [HOME]");sQ1[95]=new Array("TGmanual/127.html","Project (TGDATA) File","","[UP] [TOP] [HOME] Project (TGDATA) File The currently saved version of the Project (TGDATA) File is accessed in WizGen for a "Flexible project" by one of the following 4 methods:- Clicking on the Next>> button in the Output - derived and user-defined properties page (only with Flexible project mode enabled). Clicking on the Next>> button in the Two phase flow - page 3 (with Include two-phase fault rock calculations enabled via the Title page). Clicking on the Next>> button in the Hierarchical fault zone definition page (with Include fault drag and hierarchical zone effects enabled via the Title page). Clicking on the Goto... button to Inspect the project's TGDATA file on the Contents page.  By default, the Project (TGDATA) File is opened with the Read only mode toggled "on" (as shown below). The scroll bar at the right of the window enables the user to browse through the file. It is possible to edit the Project (TGDATA) runfile directly in this window by clicking on the Read Only "on" button (green tick) to turn it "off". It is then possible to edit the text directly in the white window. However, this method of editing the Project (TGDATA) run file should only be used under special circumstances. A far more reliable method of editing the TGDATA file is on the relevant Page(s) of WizGen, i.e. click repeatedly on the << Back button until the relevant page(s) in WizGen are accessed, then reset and save the option(s) as required. Click on any of five blue control buttons at the bottom of the window to have the following effects:- << Back button to return to the previous page of WizGen (either the Output - derived and user-defined properties page or the Hierarchical fault zone definition page or the Two phase flow - page 3 ). Next >> button to view the Session Log generated by last ViewGen run. Contents button to access the Contents page of WizGen. Save button to save the current <Project>.TGDATA runfile settings.  The button will be greyed out and inoperative if the current settings of the <Project> TGDATA file have already been saved. Quit button to exit WizGen with or without saving any changes made to the <Project>.TGDATA file. [UP] [TOP] [HOME]");sQ1[96]=new Array("TGmanual/128.html","Session Log","","[UP] [TOP] [HOME] Session Log Click on Goto... button for the Advanced, Inspect the log generated by last TransGen calculation option on the Contents page of WizGen or on the Next >> button in the Project (TGDATA) File window to launch the Session Log window. The Session Log (stored in the <Project>.TGPRT file) is automatically generated when a saved version of the <Project>TGDATA file is run by clicking on the ViewGen icon in the TransGen Control Menu. Each step in the ViewGen run is given a new number.   The Session Log will report errors encountered during a ViewGen run, including report(s) of defective cells, as well as missing or defective keywords in the TransGen TGDATA runfile. Each step in the TransGen run is given a new number in the Session Log.  Warning messages are prefixed by an exclamation mark.  Use the scroll bar on the right of the window to browse up and down the file. The five blue control buttons at the bottom of the window are the same as the Project (TGDATA) File window and have the following effects:- << Back button returns the user to the Project (TGDATA) File window. Next >> button returns the user to the WizGen Contents Page. Contents button returns the user to the WizGen Contents Page. Save button to save any previously unsaved edits to the current TGDATA run file. Quit button exits WizGen without saving the <Project>.TGDATA file. Typical warning messages in Session Log When reading the ZCORN section, a number of 'flat' cells will not be read in if they have zero thickness (i.e. four coincident Z values for the top and bottom of the grid block ).  They typically occur at unconformities. These cells have no volume,  have no connections and support no flow and are ignored by TransGen. After reading the END statement, TransGen will report the number of geometrically valid cells.  Some of these may be switched "off" by an ACTNUM keyword, or by having a zero permeability or porosity.  As Eclipse ignores these inactive cells, by default TransGen does not display them, but optionally for QC purposes they may be viewed in ViewGen.  These cells may contain Vshale or NTG data which is used by the SGR calculation.  However, no connections will be made to faulted inactive cells. After reading the END keyword, TransGen also reports the number of grid-blocks that have net pore volumes less than the limit set by the MINPV keyword.  TransGen, like Eclipse, treats cells with net pore volumes less than MINPV as inactive.  These should typically have small volumes. Cells with large negative volumes are the result of corrupt geometries.  These 'concave' cells are often the result of crossing COORD lines and should be investigated.  The location of these cells is given in the log file and whilst inactive cells are invisible by default in the viewer, they can be selected and displayed. TransGen reports the amount of memory used as a guide to the optimum hardware requirements. When a layer has been eroded from one side of a fault, typically the footwall, TransGen cannot determine the displacement for a layer directly from the data, but instead has to estimate the displacement from the adjacent layers.  In the case of footwall erosion it will use the displacement from the lower layers which are present on both sides of the fault.  TransGen reports when this occurs, and it is an indication that it is worth checking that the correct method is used for calculating SGR.  Where footwall erosion is present, SGR may be best determined from the hangingwall only. Faulted connections with transmissibility multipliers less than the multiplier cutoff limit will be ignored.  The number of these ignored connections will be reported by TransGen. [UP] [TOP] [HOME]");sQ1[97]=new Array("TGmanual/131.html","Show streamlines","","[PREV] [UP] [NEXT] [TOP] [HOME] Show Streamlines This toggled on/off option on the ViewGen Edit menu allows the display of streamline data (loaded as a data file associated with the TGSTRLNE keyword via Included Data page of WizGen), i.e. lines derived from Eclipse or another simulator showing fluid movement, for example, from injection wells to production wells. Click on the Show streamlines option in the Edit menu to toggle the display of Streamlines "on" or "off". When toggled "on" a green indicator is visible and the Streamlines are displayed. [PREV] [UP] [NEXT] [TOP] [HOME]");sQ1[98]=new Array("TGmanual/132.html","Section","","[UP] [TOP] [HOME] [TOC] Example of using the TGXRPT keyword to output FSP measures & user-defined properties The TGXRPT keyword has been extended to allow output of FSP measures and user-defined properties. The format of the keyword is the same as that used in TransGen2. Files are output in one of two formats: connection data format (all files had this format in TransGen2) and the new cell property format. Both formats have the relevant keyword names as the first record of the file and slashes added so the files can be directly re- imported back into TransGen if required. The file format for the cell property output has eight floating point numbers per line (the last line may have less than eight entries), and the data is terminated by a slash. Example In the example below, two new keywords are defined in TGNEWKEY and one FSP measure in the TGFSP keyword. The TGXRPT keyword is used to output their values after the calculations have completed along with connection permeability and area (the last two were also available in TransGen2). . . TGNEWKEY  'evshale1' 1 /  'threshold' 2 / / . . TGFSP  'sgr4'  1 1 0 1 4 ' ` 1 6 4  `evshale' 1 / / . . TGXRPT  'PERM=export_dir/perm.txt '  'AREA=export_dir/area.txt'   `sgr4=export_dir/sgr4.data'   `evshale1=export_dir/evshale1.data' `threshold=export_dir/threshold.txt'  / . Note that the names of FSP measures are case-sensitive (sgr4 is NOT the same as SGR4), but both user-defined keywords and standard keywords are case- insensitive (i.e. PERM is the same as perm). Output format for grid-block properties The file `evshale1.data' will be written something like: EVSHALE1 0.34 0.35 0.43 0.546 0.244 0.4 0.533 0.211 0.54 0.31 0.23 0.34 0.442 0.24 0.302 0.11 .... 0.35 0.43 0.546 0.244 / The format specifier used is the C++ general floating point format which automatically employs exponential format for very large or very small numbers. (i.e. 0.0000000003 will be output as 3e-10). Output format of connection properties Connection properties are output in exactly the same format as the input format of user-defined connection properties The area term IF the area term has been modified in a plugin, this modified value is the output if AREA is specified in the TGXPRT keyword. The original area of the connections cannot be output directly. [UP] [TOP] [HOME] [TOC]");sQ1[99]=new Array("TGmanual/133.html","Using the 2PhaseGen module","","[UP] [TOP] [HOME] Using 2PhaseGen The 2PhaseGen application creates pseudo relative permeability and capillary pressure tables for grid-blocks adjacent to faults from the groupings of variables determined by ViewGen. The output from 2PhaseGen (KRNUM file output) is formatted as the Eclipse SWOF keyword (or in Shell MoReS format) and contains a new pseudo table for each grouping. Original tables input using the SATNUM keyword are output first, followed by the new tables. NOTE:- Before using the 2PhaseGen module, the following needs to be done:- appropriate Two phase flow settings must be input and saved via WizGen in "Flexible project" mode.  ViewGen must run to create the groupings of faulted cells and to output an index of cells in KRNUM format identifying which pseudos to use for particular cells for a particular direction of flow to a temporary file (groupings.out) stored in the project _OUTPUT directory. This file is used by 2PhaseGen (for details see the section on Two-Phase ViewGen calculations). 1. Open the 2PhaseGen module Click on the 2PhaseGen icon towards the right on the TransGen Control Menu as shown below. Alternatively run 2PhaseGen as non-interactive (batch) version Type the following script/command at the prompt in an Xterm window:- ../<TG_HOME>/bin/2phasegenauto <TGDATA> <TGproject_dir> where <TG_HOME> is the installation directory of TransGen, <TGDATA> is the name of the runfile created by WizGen for the current TransGen project and <TGproject_dir> is the directory containing the TGDATA run file. The 2PhaseGen module (shown below) still appears, but controls are activated automatically. Settings required by the batch version are read from the TGDATA runfile in exactly the same way as normal, so WizGen must used to set up both the interactive and non-interactive runs and ViewGen used to create the groupings of faulted cells. The difference between using the interactive and non-interactive versions of 2PhaseGen are the initial maximum number of iterations. This is set to one million in the interactive version. If a solution has not converged after the maximum, a dialog window appears allowing the user to increase the maximum number of iterations and try again, skip the current group or abort altogether. In the non-interactive version, the initial maximum number of iterations is set to 300 million and if a solution does not converge the group is automatically "skipped" i.e. no dialog window appears. NOTE:- If the attributes of the model or the way the plugins that calculate fault properties are changed etc in WizGen, then a new groupings file should be generated using ViewGen before running 2PhaseGen again in either interactive or non-interactive mode. The application will open as shown above with a single frame containing 4 windows, 3 of which are initially blank graphs. The program is driven by clicking on the control button to the right of the Progress bar (bottom right of window) which is initially named Start. 2. Start application Click on Start button to prepare the two-phase plugins (either written directly by WizGen from constants or user-defined) as set on the Two phase flow - Fault Rock Properties page of WizGen. The nine files containing plugin code are read into memory and compiled. If any of the plugin files cannot be opened for any reason or the plugin code cannot be compiled, an error message detailing the problems will be displayed. For example, the following message refers to errors in the SWC (Connate water saturation) plugin. At this stage, 2PhaseGen also reads the temporary groupings.out file containing the definitions of the groups to be upscaled. If for some reason this file is not found (e.g. ViewGen has not been run or the file has been deleted), 2PhaseGen will issue an error message. For example:- When the plugins have been successfully prepared and the groupings.out file has been read, the Start button changes to Compute. At this stage you can chose to either run the application:- in "normal" default mode (i.e. with the Advanced Mode option "off") - this is the essential mode for changing the SWOF or MoReS output to be used as simulator input. or in Advanced mode (i.e. with the Advanced Mode option "on" as shown below) - to examine interactively how sensitive the pseudos are to changes in the input and to provide a quantitative feel for what the best number of grouping division might be. NOTE:- The output from 2PhaseGen using a run in which group parameters have been modified interactively should not be used as simulator input, since the up-scaled curves reflect the modified input, rather than the model specific input. However, if the Advanced Mode is selected, but the Compute stage is not interrupted, 2PhaseGen will act as it would in "normal" mode and the SWOF (or MoReS) output can be used as simulator input. 3. Compute Click on Compute to set 2PhaseGen working sequentially through the groupings information input from ViewGen, calculating a new pseudo-table for each. The variables defined in a particular grouping are displayed in the bottom right-hand window panel. The other three windows display the cell, fault and newly calculated pseudo tables for the last grouping processed. The windows display graphs for oil and water relative permeability and capillary pressure. The progress bar indicates the overall advancement as a percentage of the total number of groupings. The compute stage may take a while to complete. If 2PhaseGen is in advanced mode, the user is allowed to interrupt the compute stage at any grouping calculation by pressing the control button (which reads  Interrupt ). The group variables can be edited and a different pseudo table may be calculated for that group by pressing the Recalculate button. The control button is renamed Continue and, if pressed, causes the compute stage to continue as normal. NOTE:- Only the six variables in the boxes can be modified. The original (cell) SWOF table cannot be changed in advanced mode and, although the toggle can be changed between Drainage and Imbibition, this change is not updated in the software. Allowing these two parameters to be changed will be added to later version of 2PhaseGen. The algorithm, which implements the pseudoisation method used to create the new tables, contains several points where a parameter must converge to a solution with a suitable accuracy. To prevent an infinite loop condition which would cause the application to freeze, an upper limit is placed on the number of iterations attempted in any part of the algorithm. If the upper limit is reached the user is informed via the dialog box shown below. The user then has the choice of increasing the limit and retrying (the default), skipping the current grouping being processed or aborting the compute stage (as described below). Increase number of iterations & Retry This is the recommended procedure if this dialog appears. Increase the number of iterations (e.g. by a factor of 10) and click on the Retry button - this will usually ensure convergence. Once the upper limit on the number of iterations is changed, the new limit is applied to successive groupings. In practical terms, the upper limit is initially set to be very high within the software and non-convergence state should not be an issue. Skip If the solution cannot converge within the memory of the machine, there is probably a numerical reason for this. If this occurs, please contact user support with information of the problem. If Skip is pressed, the group being up scaled is marked as incomplete. At the end of the compute stage, 2PhaseGen searches for each incomplete grouping and attempts to find a similar grouping that has completed successfully. The search uses a minimisation algorithm to match an incomplete and complete group from a ranked list of suitable candidates. Candidates must share the same fault cycle (drainage or imbibition) and SATNUM as the incomplete group. Similarity between each candidate is assessed by comparing grouping variables weighted by the variables priority setting. The pseudo tables from the group most similar to the incomplete one are output for the incomplete group. An additional comment is added to the header of the table in the SWOF keyword indicating which table has been substituted. Abort If the run is aborted, no further calculations are made, and no 2PhaseGen output is written. 4. Write output to file Once all groups have been processed, the run control button changes to Write, and the messages window reads "new tables complete". When the Write button is pressed a file containing pseudo tables is written as the SWOF keyword (or in MoReS format). If there are any problems writing the output (e.g. file permissions, disk space, etc) they are reported in a dialog box. When the output file(s) as specified on the Two-phase flow output page in WizGen have been written, the button changes to Finish. Click on Finish to cleanly exit from the 2PhaseGen application. NOTE:- If 2PhaseGen has been run in Advanced Mode during which any of group parameters have been modified interactively, the output should NOT be used as simulator input, since the up-scaled curves reflect the modified input rather than the model specific input. However, if the Advanced Mode is selected, but the Compute stage was not interrupted, 2PhaseGen will have acted as it would in "normal" mode and the SWOF (or MoReS) output can be used as simulator input. Examples of output files The 2PhaseGen application calculates new sets of relative permeability tables for grid-blocks adjacent to faults. These tables are output using the Eclipse SWOF keyword (or in MoReS format for Shell users) as specified on the Two phase flow - Output section of WizGen. If the original model contained n tables and m new ones are calculated for the faults, the final output file will contain n + m tables, with the top ones reproducing the original tables (appropriate for unfaulted grid-blocks). Full details on the derivation of the Tables are included as comments at the top of each one. Relative permeabilities tables file -- ORIGINAL AND NEW PSUEDO REL. PERM. TABLES GENERATED BY 2PHASEGEN -- 6 ORIGINAL AND 97 NEW TABLES -- TOTAL NUMBER OF TABLES IS 103 (SET NTSFUN TO 103 IN ECLIPSE RUNSPEC SECTION) -- LARGEST TABLE CONTAINS 28 ROWS (SET NSSFUN TO 28 IN ECLIPSE RUNSPEC SECTION) SWOF -- TABLE 1 - ORIGINAL TABLE 0.3817 0 0.85 2.9599 0.5053 1e-06 0.8228 1.4583 0.5913 1e-05 0.4985 0.4405 0.6297 0.1131 0.0199 0.0502 0.6633 0.1907 0.0072 0.0262 0.7001 0.3001 0 0 / -- TABLE 2 - ORIGINAL TABLE 0.1458 0 0.85 2.9618 .... / .... -- TABLE 46 -- FAULT CYCLE: DRAINAGE -- FAULT PERMEABILITY: 0.00179307mD -- FAULT THICKNESS: 0.186239m -- FLOW RATE: 0.00487657m/DAY -- CELL PERMEABILITY: 402.097mD -- CELL POROSITY: 0.184494 -- CELL LENGTH: 75.23 -- ORIGINAL CELL TABLE NUMBER: 2 0.199812 0 0.055506 2.9618 0.236056 7.45659e-07 0.0553998 2.2679 0.486823 2.82676e-05 0.0537005 0.431316 0.505856 0.000288668 0.0531006 0.29737 0.544532 0.00500344 0.0444187 0.0562041 0.553365 0.0115648 0.0303037 0.0350734 0.556601 0.0155613 0.0203406 0.0287964 0.566937 0.0183374 0.0150864 0.0254787 0.59368 0.0217408 0.00955168 0.0209261 0.685757 0.0261557 0.000305149 0.00663319 0.688036 0.0264093 8.40631e-06 0.00625222 0.687929 0.0400969 0 0.00622588 0.688086 0.113716 0 0.0060988 0.699742 0.299769 0 0.00103016 0.699933 0.29994 0 0.00100165 / ... -- TABLE 103 -- FAULT CYCLE: IMBIBITION -- FAULT PERMEABILITY: 0.00130761mD -- FAULT THICKNESS: 0.312933m -- FLOW RATE: 2.07963e-05m/DAY -- CELL PERMEABILITY: 220.824mD -- CELL POROSITY: 0.175558 -- CELL LENGTH: 75.23 -- ORIGINAL CELL TABLE NUMBER: 2 0.1458 0 0.000757404 2.96181 0.17236 2.08692e-07 0.000482913 2.75733 0.229872 6.56727e-07 0.000481802 2.31459 0.485946 2.3862e-05 0.000410465 0.437669 0.496933 4.73326e-05 0.000374687 0.359855 0.501516 7.05713e-05 0.000338077 0.327608 0.50643 0.000116527 0.000261264 0.293238 0.509521 0.000175795 0.000176988 0.271713 0.512076 0.000298053 7.69391e-05 0.253843 0.513639 0.000612739 1.36498e-05 0.24276 0.515 0.00305691 4.6169e-07 0.233057 0.523105 0.00812683 9.03858e-08 0.177569 0.525078 0.00936099 0 0 / KRNUM output file Once each faulted cell face has been assigned to a group (created at the end of the ViewGen run according to the divisions and priorities assigned on the Two phase flow - Groupings section in WizGen), this information is output using the directional KRNUM keywords to the file specified in the Two phase flow - Output section in WizGen. The six KRNUM keywords (KRNUMX, KRNUMX- KRNUMY, KRNUMY-, KRNUMZ, KRNUMZ-) identify which set of relative permeability curves to use for flow out of each grid-block in the model. For example KRNUMY is used to define the SWOF table (see above) for flow from cell [I J K] to cell [I J+1 K], while KRNUMY- defines the table for flow from cell [I J K] to cell [I J-1 K]. For all unfaulted cell faces and for all cells in the two vertical directions (i.e. KRNUMZ and KRNUMZ-) the original SATNUM index is used. In the 3*3*2 example illustrated above, 16 cell edges are faulted. Assuming the cells originally have the same relative permeability functions, then the original SATNUM file would be:- SATNUM 18*1 / If a separate pseudo-relative permeability function is calculated for each faulted cell face, then the new KRNUM files will be:- KRNUMX 1 1 1 1 2 1 1 3 1 1 1 1 1 4 1 1 5 1 / KRNUMX- 1 1 1 1 1 6 1 1 7 1 1 1 1 1 8 1 1 9 / KRNUMY 10 11 1 1 1 1 1 1 1 12 13 1 1 1 1 1 1 1 / KRNUMY- 1 1 1 14 15 1 1 1 1 1 1 1 16 17 1 1 1 1 / KRNUMZ 18*1 / KRNUMZ- 18*1 / 5. Include Two-Phase TransGen output in Eclipse Simulation NOTE:- To implement the use of Two-phase fault rock properties in the Eclipse simulation model, a file containing the KRNUM keywords together the upscaled relative permeability and capillary pressure tables output from the Two-Phase Flow module need to be included plus the original SATNUM file in the REGIONS section of the Eclipse instructions file . Changes need to be made in the following portions of the Eclipse .DATA file to include the TransGen output:- The RUNSPEC Section The SATOPTS keyword  "DIRECT" AND "IRREVERS" should be specified below this keyword to activate directional, irreversible relative permeability tables. Example:- SATOPTS  `DIRECT' `IRREVERS'  / The TABDIMS keyword The TABDIMS keyword has up to 8 items, two of which need to be changed. NTSFUN is the total number of tables in the output SWOF file. This is the first item in the keyword. NSSFUN is the maximum number of nodes in any table. This is the third item in the keyword. The other items in the keyword should not be changed. NTSFUN and NSSFUN are reported in the 2PhaseGen "Messages" window upon completion of the up-scaling and in the header of the output SWOF file. For example, the original TABDIMS keyword may be:- TABDIMS 6 1 8 25 3 / and the header of the SWOF file may be:- -- ORIGINAL AND NEW PSUEDO REL. PERM. TABLES GENERATED BY 2PHASEGEN -- 6 ORIGINAL AND 97 NEW TABLES -- TOTAL NUMBER OF TABLES IS 103 (SET NTSFUN TO 103 IN ECLIPSE RUNSPEC SECTION) -- LARGEST TABLE CONTAINS 28 ROWS (SET NSSFUN TO 28 IN ECLIPSE RUNSPEC SECTION) in which case the new TABDIMS keyword should be:- TABDIMS 103 1 28 25 3 / The EDIT Section The single-phase TransGen output files for the EDITNNC, TRANX and TRANY keywords which are included in the Eclipse run in the Edit Section should also be included in runs using two-phase fault rock properties. The two-phase TransGen output supplements these single-phase files; it does not replace them. The PROPS Section The TransGen (2PhaseGen) output SWOF tables replace the original SWOF tables included in the PROPS section of the Eclipse instructions file. The REGIONS Section The TransGen (ViewGen) output KRNUM file, which contains the indices of SWOF tables to use for each cell in each of the six directions, should be included in the REGIONS section of the Eclipse instructions file, together with the original SATNUM data. Results of including two-phase fault rock properties in the simulation model The graph below shows a comparison of the behaviour of various models using the Demo dataset for the 3D model described in Manzocchi et al. 2002 which is included with the TransGen 3.2 release. The results obtained using TransGen in single-phase mode (solid black curve) are shown together with three other models including two-phase fault rock properties. All those including two-phase fault rock properties are similar (but not identical), with the differences attributable to variations in the up-scaling methods, derivation of the input flow rates, the groupings etc. NOTE:- The TGDATA files included with the Demo dataset (i.e. SINGLE_PHASE.TGDATA and TWO_PHASE.TGDATA) have some unconventional plugins to make the models directly equivalent to those used in the paper (which were not made using TransGen). The paper cited is "The representation of two phase fault-rock properties" by T. Mazocchi, A.E. Heath, J. J. Walsh & C. Childs  in Petroleum Geoscience, Vol. 8 2002, pp. 119-132. [UP] [TOP] [HOME]");sQ1[100]=new Array("TGmanual/134.html","Defining Two-phase flow plugins","","[UP] [TOP] [HOME] Defining Two-phase flow plugins Having selected the Plugin option to calculate one or more Two phase flow - Fault Rock Properties, click on Yes in the Edit plugins? Pop-up window to return to the User-defined plugins page (as shown below) to view/edit the default plugin(s). HINT:- The default plugin for a particular fault-rock property uses the equation and constants as currently defined on the Two phase flow - FAULT ROCK PROPERTIES page of WizGen. A new two-phase plugin is automatically added to the plugins page for each relationship specified. The following Two-phase plugin functions are dynamically added and removed from the drop-down list of Functions available on the User-defined plugin page and are used to generate plugin filenames (where required):- PORO_FR - for calculating fault rock porosity SWOR - for calculating water saturation at irreducible oil  SWC - for calculating irreducible (connate) water saturation  PC_D - for calculating the drainage Capillary Pressure curve  PC_I - for calculating the imbibition Capillary Pressure curve  KRW_D - for calculating the drainage water relative permeability curve KRW_I - for calculating the imbibition water relative permeability curve KRO_D - for calculating the drainage oil relative permeability curve KRO_I - for calculating the imbibition oil relative permeability curve For example, if Fault Porosity and Capillary Pressure are set to be calculated via Plugins (rather than by the default Equations) on the Two phase flow - FAULT ROCK PROPERTIES page, PORO_FR and PC_D are added to the Function list on the User-defined plugins page of WizGen. Initially the Two phase flow plugin is derived from the default equation and constant values in use immediately before the relationship was changed to be represented by a plugin. The new plugin is automatically written to a new file and the name of the file is linked to the plugin function. In effect, the invisible plugin that contained the equation code is copied to a new file and becomes editable by the user. A two-phase plugin can be edited, built and saved like any other plugin. Also, like any other plugin, they can be loaded from the user's library of plugins. The 2Phase drop-down list below the code window contains the names of the 3 variables which can be used within a two-phase plugin. These are:- se (effective water saturation) poro (fault porosity) perm (fault permeability) NOTE:- Two-phase plugins do not use variable prefixes. At present, no other user or system-defined cell or fault properties can be used within two-phase plugins and the drop-down lists containing the names of these variables are greyed-out. NOTE:- The other, very important, difference between a two-phase plugin and other plugin types is that a two-phase plugin returns the result of the plugin calculation. The value calculated by the plugin for, say, fault rock porosity must be sent back to the software using the `return' statement followed by the value and a semi-colon. The property a two-phase plugin calculates can be based on the values of se, poro and/or perm sent into the plugin by the software, but the property is sent back to the software via the last line of the plugin -  the `return' statement. It may be useful to always use the variable name result to store the value of the calculated property. The name result has no special meaning but it could be used to create a template for all two-phase plugins e.g. // my two-phase plugin double result; . . result = ... return result; A two-phase plugin is removed from the project by reselecting an equation to represent the particular fault property relationship on the Two phase flow -FAULT ROCK PROPERTIES page of WizGen. The most recent constants associated with the equation are recalled and the text input fields become sensitive. If a constant was deleted, the default value is used. If a two-phase plugin is removed using the Remove, File option on the User-defined plugins page, a dialog box appears offering to transfer to the two-phase fault rock properties page so the relationship can be altered to equation (as shown below). [UP] [TOP] [HOME]");sQ1[101]=new Array("TGmanual/135.html","Using the Two phase flow functionality","","[UP] [TOP] [HOME] Using the Two-phase flow functionality TransGen Version 3.1 includes functionality for calculating the effects of two-phase fault rock properties and including these effects in simulator input files through modifications to the relative permeability and capillary pressure function of grid-blocks adjacent to faults. The objective of two-phase TransGen project work-package is to allow routine inclusion of two-phase fault-rock properties in flow simulation models. The procedure adopted within TransGen to meet this objective follows four main steps:- Derive across-fault flow rates from a single-phase flow model Establish groupings of faulted blocks using 6 variables (including permeability and flow rate) Determine pseudo-relative permeability and capillary pressure tables for each grouping Output these properties for direct inclusion in the simulator Three TransGen applications are used in the implementation. WizGen in "Flexible project" mode is used to set all the parameters required. ViewGen creates the groupings of faulted cells and outputs an index of cells in the KRNUM format identifying which pseudos to use for particular cells for a particular direction of flow. 2PhaseGen is a new application which implements a pseudoisation method to calculate pseudo-relative permeability and capillary pressure tables from the groupings of faulted cells. The output from 2PhaseGen is a file containing tables in the SWOF format which can be directly included in the simulator. [UP] [TOP] [HOME]");sQ1[102]=new Array("TGmanual/136.html","Running Eclipse models with Two-Phase TransGen output","","[UP] [TOP] [HOME] [TOC] [UP] [TOP] [HOME] [TOC]");sQ1[103]=new Array("TGmanual/137.html","Displaying two-phase fault rock properties","","[UP] [TOP] [HOME] Displaying two-phase fault rock properties In the current TransGen 3.1 release, visualisation of two-phase fault rock properties in ViewGen is restricted to the directional KRNUM keywords which can be displayed as cell properties and the across-fault flow rates (if used explicitly) which can be displayed as fault properties and/or cell pressures (if used) which can be displayed as cell properties. No internally-derived properties (e.g. fault rock capillary threshold pressure, porosity, connate water saturation, effective water saturation range, etc.) can be visualised directly at present (the options will be made more comprehensive in future releases). However, these properties may be visualised using the following workaround employing the single-phase plugins and user-defined properties. For example, assume that the default two-phase fault rock property equations are used with their default values and that you want to visualise the fault rock capillary threshold pressure. The capillary threshold pressure is obtained from the drainage capillary pressure curve when the effective water saturation is 1.0. The default drainage capillary pressure equation is:- The capillary threshold pressure can therefore be obtained in the AREA plugin (on the User-defined plugins page of WizGen) as a function of c.perm, i.e. the connection average fault rock permeability calculated in the PERM plugin. If a variable thres_press is specified as a user-defined connection property (on the User-defined keywords page of WizGen), the following lines of code added in the AREA plugin will calculate its values:- double temp_poro; temp_poro = 0.05*pow(c.perm, 0.25); c.thres_press = 3* pow(porosity, 0.5)*pow(c.perm, 0.5); The thres_press connection property will then appear in the Fault properties menu in the ViewGen graphics interface and can be visualised. [UP] [TOP] [HOME]");sQ1[104]=new Array("TGmanual/138.html","Two-Phase ViewGen calculations","","[UP] [TOP] [HOME] Two-Phase ViewGen calculations Checking the input data ViewGen reads all the two-phase fault rock data specified in WizGen. Two-phase plugins (if used) are checked for consistency at the same time as the single-phase ones. Note that even if equations are used for all two-phase properties, the system represents these relationships as plugins. If a plugin contain errors, ViewGen will terminate with an error message. This kind of error will only arise if user-defined plugins have not been checked (by clicking on the BUILD option on the User-defined plugins page of WizGen) and any errors eliminated prior to using ViewGen. Defining the cell groups Groups are created at the end of a ViewGen run, according to the divisions and priorities assigned as Two phase flow - Groupings settings in WizGen.     Each cell in the model is inspected for faulted faces. A series of calculations is performed to determine if a faulted face is in the drainage or imbibition cycle and to evaluate the fault thickness and permeability, flow rate through the fault and the length, permeability and porosity of the cell containing the face. These data, combined with the SATNUM of the cell, are stored as groups. Information about the groups is output by ViewGen to a temporary file (groupings.out) stored in the project  _OUTPUT  directory. This file is used by the 2PhaseGen module. A group is defined by the following items:- FAULT CYCLE (Drainage or Imbibition) CELL SATNUM (i.e. original cell relative permeability and capillary pressure functions) FAULT PERMEABILITY (calculated from single-phase TransGen definitions) FAULT THICKNESS (calculated from single-phase TransGen definitions) FLOW RATE (imported directly or calculated from cell pressures) CELL PERMEABILITY (imported) CELL POROSITY (imported) CELL LENGTH (calculated from the model geometry) An example of a temporary groupings.out file is given below. The contents of the file are shown for completeness only; the user should not have to interact with this file: BeginParameters      FaultFlowRate: 2 2 6      FaultPermeability: 2 2 2      FaultThickness: 2 2 4      CellPermeability: 2 2 3      CellPorosity: 2 3 5      CellLength: 2 2 1 EndParameters # Definition of group number 7 BeginGroup     GroupNumber: 7     FaultCycle: DRAINAGE     RelPermTableIdx: 1     FaultFlowRate: 0.000706286 0     CellPorosity: 0.080282 0     FaultThickness: 0.203895 0     CellPermeability: 213.029 0     FaultPermeability: 0.00334088 0     CellLength: 75.1753 0 EndGroup # Definition of group number 8 BeginGroup     GroupNumber: 8 ... etc EndGroup The parameters at the top of the file report number of divisions in the drainage cycle, the number of divisions in the imbibition cycle, and the parameter priority, for the 6 grouping variables, as input in WizGen (via the Two phase flow - GROUPINGS & OUTPUT page). This is followed by a listing of the values or settings for each group in the model. In this example the original model contained 6 SWOF tables, hence the first group defined for up-scaling is number 7. Exporting the KRNUM tables Once each faulted cell face has been assigned to a group, this information is output using the directional KRNUM keywords to the file specified in the  Two-Phase flow - Output section of WizGen. For unfaulted cell faces and for all cells in the two vertical directions (i.e. KRNUMZ and KRNUMZ-), the original SATNUM index of the cell is used. (See example of KRNUM output file). Displaying Two-Phase fault rock properties At present the following can be displayed in ViewGen:- The 6 KRNUM keywords can be visualised as cell properties. Cell pressures (if used) can be visualised as cell properties. Across- fault flow rates (if used explicitly) can be visualised as fault properties. No internally-derived properties (e.g. fault-rock capillary threshold pressure, porosity, connate water saturation, effective water saturation range, etc.) can be visualised directly. However, these properties can be displayed via a workaround using the single-phase plugins and user-defined cell properties. [UP] [TOP] [HOME]");sQ1[105]=new Array("TGmanual/139.html","Document","","[PREV] [UP] [TOP] [HOME] [TOC] [PREV] [UP] [TOP] [HOME] [TOC]");sQ1[106]=new Array("TGmanual/140.html","TransGen version 3.2","","[UP] [TOP] [HOME] TransGen version 3.2 TransGen Version 3.2 includes new functionality to model user-defined and stochastically generated fault zone structure and to include the effects of these sub-resolution geometrical fault characteristics in the flow simulator. The main innovations are:- Inclusion of the effects of user-defined faults not included explicitly in the geometry of the simulation model. Inclusion of uncertainty in fault throw or of local geological drag on faults included explicitly in the simulation model. Inclusion of fault relay zones and other forms of locally-paired slip surfaces on faults included in the input model as single surfaces. The geometrical and fault rock effects of these features are exported as transmissibility or transmissibility multiplier files by TransGen, for direct inclusion in the simulator, allowing an implicit representation of more complex geometry than is represented explicitly in the model. NOTE:- The new geometrical functionality operates only on single-phase properties. A TransGen run which includes both the implicit geometrical functionality introduced in this version and the two-phase functionality introduced in the Version 3.1. will run successfully, but will be internally contradictory, since the two-phase functionality is applied exclusively at the resolution of the input model. Combining the two sets of functionality is therefore not recommended. The new functionality requires a separate license and is accessed by selecting Include fault drag and hierarchical zone effects on the Title page of WizGen in Flexible Project mode. Much of the new functionality is associated with a new type of TransGen object called a faulted trace (see section on Traces and Fault zones below for details). Other Changes to TransGen since Version 3.1 The only other unrelated changes have been made to the WizGen Miscellaneous Options page where the Lower limits box has been modified. It now contains three constants, each of which defaults to the value of 1.0E-6 . These are:- Unfaulted transmissibility cut-off (keyword TGMINTR) Cell volume error tolerance (keyword TGVOLERR - associated with identifying geometrically corrupt cells) Cell pore volume cut-off (Keyword MINPV) MINPV was not accessible in the previous version, and TGMINTR was incorrectly described as a "multiplier cut-off". TransGen will render inactive any cell with a pore volume less than the specified MINPV value and will ignore any connection with an unfaulted transmissibility value less than the specified TGMINTR value. The default values follow those in Eclipse, which considers any cells with pore volumes greater than 1.0E-6 to be inactive and does not consider connections to be present if their transmissibilities are less than 1.0E-6 . Traces and Fault Zones [UP] [TOP] [HOME]");sQ1[107]=new Array("TGmanual/141.html","Traces and Fault Zones","","[UP] [TOP] [HOME] Traces and Fault zones Introduction to Traces Any TransGen model contains a number of object types, for example cells (grid-blocks) and fault connections. The location of a cell location is defined by its XYZ position in the model and the location of a fault connection by the XYZ positions of the two cells it links. Each object has a number of properties which are either included in the TransGen run (via the Included data page in WizGen, e.g. PERMX and NTG of cells) or are calculated automatically by TransGen (for example fault connection permeability). Each type of object may additionally have sub-types, e.g. a fault connection has an average connection property (in the "PERM" and "THICK" plugins) denoted by the "c." prefix, but also has between 3 and 6 corners (vertices) denoted by the "v." prefix. Much of the new functionality in the TransGen version 3.2 is associated with a new type of TransGen object called a faulted trace. A faulted trace is a 2D object defined by the XY location of the edge of a stack of cells. Hence a trace defined by [I, J, `DIR_X'] contains all connections between cells [I,J,Z1] and [I+1, J, Z2], where Z1 and Z2 can take any values. For example, the simple 2*2*2 faulted model shown below contains 8 cells ([1,1,1], [1,2,1], [2,1,1], [2,2,1], [1,1,2], [1,2,2], [2,1,2], [2,2,2]), 3 fault connections ([1,2,1][2,2,1], [1,2,2][2,2,1] and [1,2,2][2,2,2]), and one fault trace ([1,2,`DIR_X']). Fig 1. Example of a fault trace Like fault connections, fault traces are recognised automatically by ViewGen from the geometry of the input model and a number of properties are calculated and stored for each one. A fault trace contained explicitly in the parent model geometry is termed a system trace or an explicit trace: the two terms are equivalent. New functionality allows new traces to be added to a TransGen model and for existing traces to be modified, without the need for modifying the underlying geometry of the simulation model. For clarity, the unaltered input model is termed the system model and a model containing modifications the user-defined model. The objectives of the new functionality is to calculate appropriate properties and connection transmissibilities for the user-defined model, but to output these at the resolution of the system model. For example, the user-defined model geometry shown below derives from the parent model shown above. The system trace [1,2,`DIR_X'] has had its throw modified, while a new trace ([1,1,`DIR_Y']) has been added. Any new trace added in this way is termed a user-defined trace. Fig 2. Example of a User-defined model derived from the parent model The user-defined trace [1,1,`DIR_Y'] has added one non-neighbour connection ([1,1,2][1,2,1]) to the model, and has influenced the transmissibilities of the two, originally unfaulted neighbour connections [1,1,1][1,2,1] and [1,1,2][1,2,2]. The resultant across-fault transmissibilities associated with these connections will be calculated and output by TransGen using the Eclipse NNC and TRANY keywords respectively. The across-fault transmissibility associated with the modified non-neighbour connection on the system trace (i.e. connection [1,2,1][2,2,2])will be included as a transmissibility multiplier in the EDITNNC file, with the faulted transmissibility calculated from the modified model (Fig 2), and the  no- fault rock  transmissibility calculated from the unaltered parent model |(Fig 1). For the two faulted neighbour connections on the system trace, the faulted transmissibilities calculated in the modified model (Fig 2) will be included in the TRANX file. Figure 3 (below) shows a more severe modification to the same model (Fig 1). In this example, only two across-fault connections are present; the non- neighbour connections [1,1,2][1,2,1] on the user-defined trace and [1,2,1][2,2,2] on the system trace. Since neither of the connections exist in the unaltered parent model, the faulted transmissibilities associated with them will be output into the NNC file. Additionally, five connections that existed in the parent model do not exist in the modified model. The effect of losing these connections will be included in the simulator input by setting two TRANY values (connections [1,1,1][1,2,1] and [1,1,2][1,2,2]), two TRANX values (connections [1,2,1][2,2,1] and [1,2,2][2,2,2]) and one EDITNNC (connection [1,2,1][2,2,2]) to zero. Fig 3. A second example of a user-defined model derived from the parent model in Fig 1. Trace Properties A number of properties are calculated automatically for each trace in the model, the most important of these are the length, width, aveThrow and dragRatio of the trace. The first two are used to calculate other properties (in particular the maximum size of a relay ramps that a trace can contain) but cannot be altered by the user. The second two can be redefined in a number of ways by the user, and define the final fault juxtaposition geometry used to calculate across- fault connection transmissibilities. Up to 10 user-defined trace properties can also be defined and used. The Table below lists the main properties attached to fault traces and indicates how these values may subsequently be modified during the TransGen workflow. Trace Length and Width These Trace properties are defined in the Figure below for a fully 3D model in which none of the coord lines defining the cell edges are parallel to each other. Note that only the upper three layers of this five- layer model are faulted (Fig 4a), and therefore fault connections (Fig 4b) are only present in the upper region of the model. Despite this, since it is a 2D object, the fault trace (Fig 4c) extends from the footwall side of the uppermost layer to the hangingwall side of the lower- most layer. The trace length is defined as the minimum value of the XY projection of the length of the trace measured in each layer in the model in the cells on both sides of the trace. In this example, therefore, the trace length is governed by the hangingwall cell of the upper layer, since this cell has the shortest faulted face (Fig 4d). The trace width is defined as the minimum value of the XY projection of the distance between the centre of the faulted cell face and the centre of the cell, measured in each layer in the model in the cells on both sides of the trace. The width of this trace is therefore controlled by the footwall cell of the lowest layer, since this cell is narrowest (Fig 4d). The reason for using minimum distances in the definitions of trace length and width is so that fault zone components, which are defined geometrically by length and width terms, can always be contained on the trace they are assigned to. This is discussed further in the section on Fault zone properties. Trace Average throw The aveThrow value of a trace is the summation of the system throw and the user-defined throw and can take either positive or negative values depending on whether the cell closer to the origin is on the footwall or hangingwall side of the fault. In the example shown above (Fig 4), the cells closer to the origin are on the footwall side, and the throw of the trace is negative. Fault throws can be different in a particular layer at each end of the trace (defining a horizontal displacement gradient), and can also vary between different layers in the model (if vertical displacement gradients are present). For each trace an average value is calculated. This is a simple average of the values of each end of the trace in each layer. Note that if, as in this example, certain layers are unfaulted, these will still be included in the averaging. In certain instances system traces describing complex geometries are assigned throws of zero. These are if the trace is a scissor fault (i.e. the sense of throw is different at the two coord lines as shown in Fig 5a) or if the sense of throw changes over the height of the trace (as shown in Fig 5b). Trace Drag Ratio The dragRatio is a multiplier on the aveThrow of the trace, designed to allow inclusion in a TransGen run of:- a component of normal drag associated with the fault throw, which results in lower displacement across the explicit fault and therefore a different across- fault connection geometry and stochastic modelling of uncertainty of the fault throws in the model. All traces (system and user-defined) have initial drag ratios of 1.0. User-defined trace properties Up to 10 user-defined trace properties can be included in a TransGen run and used in plugins. These are always called user1 to user10. The first 5 (user1 to user5) must take integer values, while user6 to user10 take non- integer (floating point) values. These are loaded using the TGTRACE keyword. Introduction to Fault zones A fault zone is a new kind of TransGen (version 3.2) object associated with traces. Each trace in a model may have a single fault zone associated with it, but a fault zone has no meaning except with reference to a trace. Fault zones allow inclusion in the simulation model of the transmissibilities associated with locally paired slip surfaces which may have very different juxtapositions to the single slip surface present on the trace in the parent model. Fig 6 shows an example for a simple 5 layer model. Fig 6a shows the cells in the cell stacks adjacent to the fault trace in the parent model. A fault zone (in this case, a breached relay ramp) is attached to the trace, defining the high resolution paired slip surface geometry illustrated in Fig 6b. The new functionality associated with fault zones constructs the high resolution geometry and calculates the transmissibilities of all possible flow routes between every pair of cells in the model. These are then output at the resolution of the parent model (Fig 6a). In this example the parent model does not contain a connection between the second layer in the footwall stack and the top layer in the hangingwall stack. In the high resolution model there are 6 possible flow paths between these two cells. These are:- 1. An across-fault connection into the top layer of the ramp from the footwall cell, and out of the ramp in the hangingwall cell through the low displacement breached connection. 2. The same connection into the top layer of the ramp, and out of the ramp in the hangingwall cell through the variable displacement fault at the edge of the ramp. 3. An across-fault connection into the second layer of the ramp from the footwall cell, and out of the ramp in the hangingwall cell through the low displacement breach faulted connection. 4. The same connection into the second layer of the ramp from the footwall cell, and out of the ramp in the hangingwall cell through the variable displacement fault at the edge of the ramp. 5. An unfaulted connection into the second layer of the ramp from the footwall cell, and out of the ramp in the hangingwall cell through the low displacement breach faulted connection. 6. The same connection into the second layer of the ramp from the footwall cell, and out of the ramp in the hangingwall cell through the variable displacement fault at the edge of the ramp. TransGen calculates the transmissibility associated with each of these flow paths and outputs the combined transmissibility at the resolution of the parent model (in this example using the NNC keyword, since the connection in question does not exist in the parent model.) Note that vertical non-neighbour connections can also be produced by fault zones. In this example the relay ramp in the uppermost layer provides a connection between the top layer and third layer in the hangingwall cell stack. Transmissibilities associated with vertical non-neighbour connections are also calculated and output. Exactly the same procedures are used to calculate across-fault transmissibilities associated with fault zones as are used in the rest of TransGen, i.e. the same FSP and fault rock permeability and thickness calculations defined in the PERM and THICK plugins used elsewhere in the model are repeated in the Fault Zone calculations. Certain restrictions on usage in the PERM and THICK plugins arising from the new functionality are discussed under Implications of the new functionality in the section on C++ functionality in DRAG & FZONE plugins. Fault zone properties Fault zones can be attached to traces by: Placing them manually using the TGFZONE keyword (see Including data when using the new Fault Trace and Fault Zone functionality). Placing them stochastically using the WizGen tool (using Assign hierarchical zones on the Hierarchical fault zone definition page). Placing them according to user-defined criteria using the FZONE plugin. In addition to the location of the trace containing the fault zone, a set of eight properties need to be set for each zone (as shown in the Table below). Between them, these give a full definition of the geometry of the zone. Fault zone dimensions Figure 7 (below) demonstrates the construction of the fault zone components for dipping cells with orthogonal plan- view geometries. The length (LT) of the trace is the minimum plan-view distance parallel to the fault between cell corners, and the width (WT) is the minimum plan- view distance at the cell edges perpendicular to the trace (i.e. the minimum of W1A, W1B, W2A, and W2B. (Fig 7a). The ramp dimensions are defined by a length (LR) and width (WR ) which are also distances in the XY plane: a dipping ramp is therefore longer than LR (Fig 7b). A fault zone component in a particular model layer is composed of five elements; two parent cells, two stub cells and one ramp (Fig 7b). The two stubs and the ramp are of a constant plan-view width WR. The ramp is placed in the centre of the trace, and is of plan-view length LR. Stub A always forms an unfaulted connection with Cell 1, and stub B with Cell 2 (Fig b). The Stubs have no dip component perpendicular to the trace, and their depths at the two edges of the model are equivalent to the depths of the parent cells at the ends of the trace. The dip of the Stubs parallel to the trace is equal to the plunge of the trace. This ensures that, although Cells 1 and 2 (Fig 7b) are narrower than the parent cells (Fig 7a), displacements DA, DB, DC, and DD (Fig. 7c) are identical to those at equivalent positions in the parent model (Fig 7a). Length and width of a fault zone are user-defined, and examples of fault zones with the same throw ratios r1, r2, r3, and r4, but with different widths and lengths are shown in Figure 8 (in this example both the length and the width of the trace are equal to 100m). WR and LR cannot be larger than 95% of WT and LT - if larger values are defined they are truncated to these limits (e.g. Fig. 8d). The TGFZONE keyword used to construct these fault zones is shown. The zone definition shown in (d) exceeds 95% of the trace length and width, and the zone is reset to the maximum possible size. Throws on the zone-bounding faults The depths of the eight corners of each layer in the ramp are defined by the four ratios r1, r2, r3 and r4. These are described with reference to the four fault displacements d1, d2, d3 and d4 indicated on Fig 7c. As discussed above, the displacements at each end of the ramp (DC and DD, Fig 7c) are calculated from the geometry of the parent cells. The four ramp displacements are then given by:- d1 = r1 DC d2 = (1-r2) DC d3 = (1-r3) DD d4 = r4 DD Fault zones are constructed so the same ratios (r1, r2, r3, r4) generate a ramp with the same geometry irrespective of the direction of the trace (`DIR_X' or `DIR_Y') or the sense of displacement on the fault, i.e. whether or not the cell stack closer to the origin is on the upthrown (a negative sense of throw) or a downthrown (a positive sense of throw) side of the fault. These four cases are shown in Fig. 9, using r1 = 0.7, r2 = 0.8, r3 = 0.3 and r4 = 0.2. Fault zone permeabilities The properties of the Stub cells are inherited from the parent cells, i.e. Stub A has the identical properties to Cell 1, and Stub B has identical properties to Cell 2 (Fig 7d). All properties with the exception of the two horizontal permeabilities in the ramp are the arithmetic average of the two cells. The permeability in the ramp perpendicular to the trace (KperpA) is given by the harmonic average of the two cell permeabilities (Kperp1 and Kperp2), multiplied by the fault zone variable damage_perp, while the permeability in the ramp parallel to the trace (KparaA) is given by the arithmetic average of the two cell permeabilities (Kpara1 and Kpara2), multiplied by the fault zone variable damage_para. These two variables can therefore be used to include effects on permeability of minor faults in the ramp. Plausible and Implausible fault zone geometries The ratios r1, r2, r3 and r4 can be used to define ramps with both plausible and implausible geometries. Examples of each are shown in Figures10 and 11. In general, the following inequalities must be satisfied for a ramp to have a plausible geometry:- r4 >= 0.0 r4 <= r3 <= r2 r4 <= r1 <= r2 r2 <= 1.0 The relationship between r3 and r1 is flexible - provided r4 is the smallest value present, and r2 is the largest value present, r1 and r3 can take any values to give a valid geometry. If r1=r2 and r3=r4 all the ramp dip is parallel to the trace (i.e. a relay-ramp geometry fig 10b), if r1=r4 and r2=r3 all the ramp dip is perpendicular to the trace (i.e. a lens, fig 10c), and anything in between gives rotations in both directions (Figs 10d & e). If a fault zone is included with an implausible geometry using the TGFZONE keyword, ViewGen will issue a warning, but since it is conceivable that the implausible geometry is intentional, the fault zones will be processed in exactly the same way as ones with plausible geometries. The examples shown in Figures 7 to 11 are for models with vertical faults and vertical coord lines. Faults zones, however, are constructed in the same way for more complex 3D model. Figure 12, for example, shows an unbreached relay on a more complex trace. The ramp is of constant length through the thickness of the model, but the length of the trace in this example is defined by the lowest cells in the model. Hence the stub cells are shorter in layer 5 than in layer 1. The internal checking in TransGen ensures that, irrespective of input, a ramp is contained within the trace to which it is assigned. [UP] [TOP] [HOME]");sQ1[108]=new Array("TGmanual/142.html","Drag applied to fault traces page","","[UP] [TOP] [HOME] Drag applied to fault traces page This is the Next >> page accessed in WizGen (in "Flexible project" mode) from the Output - derived and user-defined properties page or by selecting the Goto... button for Apply stochastic and/or deterministic drag to faults from the Contents page when the Include fault drag and hierarchical zone effects option has been toggled "on" via the Title page of WizGen. NOTE:- The next two pages can only be accessed in WizGen if the TransGen installation is licensed for the sub-resolution fault-trace functionality (new to the TransGen 3.2 release). The Drag applied to fault traces page of WizGen allows the user to modify the fault throw on all fault traces in the model (either included explicitly in the geometry of the parent model or included as user-defined faults using the TGTHROW keyword) using any one of the following options:- Do not apply Drag (default setting) where fault drag is omitted from the model, except where the drag is specified by a file containing TGDRAG keyword data, added to the current run via the Included Data page. Use equation where fault drag is modelled using either or both equation options, i.e. Probablistic throw uncertainty and/or Deterministic normal drag. Use a plugin where fault drag is modelled using the DRAG plugin written in the User-defined plugins page. Do not apply drag options If the default Do not apply Drag setting (as shown above) no throw modifications are applied to the current model, except where the drag ratio value included in the run via a file containing TGDRAG keyword data (see Included Data page) is anything other than 1.0.  Use equation drag options Select the Use equation option (as shown below) to access two basic options for modelling drag (Probablistic throw uncertainty and/or Deterministic normal drag). Toggle "on" the Probablistic throw uncertainty and/or the Deterministic normal drag option(s) and input appropriate settings.   NOTE:- Both options can be used together to produce a model in which stochastic variability arising from uncertainty in the definition of the fault throws is modelled first and then deterministic geological normal drag is superimposed. This is the situation illustrated by the selections shown below. Probabilistic throw uncertainty option If the probabilistic throw uncertainty toggle is activated, fault drag is modelled stochastically using one of two options. These are an absolute uncertainty on fault throw (throw +/- m) or a percentage uncertainty on fault throw (throw +/- %). The fault throw value considered when calculating this uncertainty is the summation of the system throw (i.e. arising from the input model geometry) and the user-defined throw (added using the TGTHROW keyword via the Included Data page of WizGen). As each trace is processed, a drag ratio is calculated which will result in the final fault throw either being in the range T = T± X metres, or T = T±Y %. Examples of model parameters generated using the two methods are shown below. This functionality is designed to allow inclusion in the simulation model of stochastic variability arising from uncertainties in the definition of fault juxtapositions. Throw +/- m Drag ratios (a) and implied values of final output fault trace throw (b) are shown below plotted against input fault trace throws for a model containing input trace throws in the range of -60 to 60m using a throw +/- m setting of 10 metres. Throw +/- % Drag ratios (a) and implied values of final output fault trace throw (b) are shown below plotted against input fault trace throws for a model containing input trace throws in the range of -60 to 60m using a throw +/- % setting of 5%. Deterministic normal drag option This functionality is designed to allow inclusion in TransGen of the effects of normal drag developed during the evolution of the fault throw. The growth of displacement on a particular fault might consist initially of the development of a monocline with a discrete fault surface forming only after a particular displacement, followed by a progressively larger fraction of the accumulated displacement accommodated on the discrete slip surface. The WizGen tool allows inclusion of such drag using the equation: The figures below shows the form of this equation for two sets of values of the user-defined constants, i.e. for dt = 0.5m and dp = 20m (shown in black) and dt = 3m and dp =10m (shown in pink). All throw up to the value of dt is accommodated by normal drag and the component of throw accommodated by normal drag gradually decreases as throw increases, eventually plateauing out to the value of dp at very high throw. For example the drag ratios (a) and the implied values of the final trace throw, i.e. output fault throw (b) for input trace throws in the range of -60 to 60m are shown for a model using dt = 0.5m and dp = 20m. Overwrite user-defined drag ratios This toggle (only accessible with the Use equation drag option selected) determines whether or not drag ratio values assigned using the TGDRAG keyword are preserved or overwritten by equation options defined on this page. Use a plugin option Toggle this option "on" to apply drag to fault traces using user-defined criteria applied via the DRAG plugin (see section on the DRAG plugin for full details). When the Drag applied to fault traces page is set as required, click on the Next >> button to view/edit the current settings on the Hierarchical fault zone definition page. Alternatively, click on the << Back button to return to the Output - derived and user-defined properties page. Or click on the Contents button to access the Contents page to view/edit any of the current WizGen page settings, inspect the current TGDATA file and/or the session log generated by last ViewGen calculation. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. [UP] [TOP] [HOME]");sQ1[109]=new Array("TGmanual/143.html","Hierarchical fault zone definition page","","[UP] [TOP] [HOME] Hierarchical fault zone definition page This is the Next >> page accessed in WizGen (in "Flexible project" mode) from the Drag applied to fault traces page or by selecting the Goto... button for Define sub-gridblock hierarchical fault zone structure option on the Contents page when the Include fault drag and hierarchical zone effects option has been toggled "on" via the Title page of WizGen. The WizGen Hierarchical Fault zone definition page offers three Fzone options for attaching fault zones to fault traces:- Do not apply fault zone structure - to omit fault zones from the model, or to place them manually using a file containing TGFZONE keyword data added to the current run via the Included Data page. Assign hierarchical zones - to place fault zones stochastically using the WizGen tool to assign hierarchical zones. Use a plugin - to place fault zones according to user-defined criteria using the FZONE plugin. A fault zone is a new kind of TransGen object associated with the fault traces allowing inclusion in the simulation model of transmissibilities associated with locally paired slip surfaces which may have very different juxtapositions to the single slip surface present on the trace in the parent model (see section on Fault zones for further details). The principal behind the hierarchical construction of fault zones is that a fault, represented as a continuous discontinuity in the reservoir simulation model, might be segmented at a sub-resolution scale with, for example, a low frequency of relatively large unbreached relays, a higher frequency of intermediate sized relays with single breaches and a higher-still frequency of very small, doubly-breached relays. This situation can be modelled using a hierarchy comprising three levels. Large deterministic fault zones visible seismically, but too small for explicit representation in the flow model can be included using the TGFZONE keyword. Smaller, sub-seismic fault zone structure, however, is better modelled stochastically using the WizGen Assign hierarchical zones tool which will never overwrite those included deterministically. If Do not apply fault zone structure is selected, only fault zones included using the TGFZONE keyword are applied. If Use a plugin is selected, the FZONE plugin to use should be selected from the library  or written from scratch in the User-defined Plugins WizGen page. Alternatively select the Assign Hierarchical zones option to model the fault zones stochastically as described below. Assign hierarchical zones A fault zone hierarchy can consist of one or more levels, each level characterised by 8 constants. Hierarchies can be defined via the Hierarchical fault zone definition page in WizGen by selecting the Assign hierarchical zones option (as shown below). The first time the Assign hierarchical zones option is selected for a TransGen project, the Library selection is blank and a single Hierarchical level (level 1) is assigned with default values for the eight constants (as shown below).  These values can be modified by selecting the current value in the text box and typing in the required new value plus return. With the first Hierarchical level (1) selected, set the Constants for this level. Setting the Constants for an hierarchical level A fault zone hierarchy is defined by the number of levels present and the values of the eight constants defined for each level. NOTE:- When setting Constants for several hierarchical levels, Level 1 should contain the rarer, larger ramps (i.e. lower values of the Frequency constant and higher values of Width/Throw) because the plugin written by WizGen processes each hierarchy sequentially starting from level 1. Ramps from the particular level being processed are not placed on traces which have already had ramps placed at a higher level. These constants are:- The width to throw ratio of the ramp (Width/throw) The length to width ratio of the ramp. (Length/width) Two breaching indices (Breaching index1 and Breaching index 2) A Frequency constant A multiplier on the ramp-parallel permeability (Parallel damage) A multiplier on the ramp-perpendicular permeability (Perpendicular damage) A minimum throw cut-off (Minumum throw). If a ramp from a particular level is placed on a trace, its geometry is governed by the width/throw, length/width and the two Breaching index values specified for this level and the throw on the trace. The default values shown above are those for an unbreached relay ramp. To generate a breached relay ramp, decrease the Width/throw ratio setting and either decrease the Breaching index 1 for a single-breached relay or decrease both Breaching indices for a double-breached relay. The construction of the ramp from these values is discussed in the section on Ramp geometry below. Ramp geometry The decision of whether or not to place a ramp from a particular level on each trace is governed by the Frequency constant and the Minimum throw cutoff, and is discussed in the section on Stochastic ramp placement below. Stochastic ramp placement The petrophysical properties of the ramp are derived using the values of the Parallel damage and Perpendicular damage settings for each level to modify the ramp permeabilities. The permeability in the ramp perpendicular to the trace (KperpA) is given by the harmonic average of the two cell permeabilities (Kperp1 and Kperp2), multiplied by the fault zone variable Perpendicular damage, while the permeability in the ramp parallel to the trace (KparaA) is given by the arithmetic average of the two cell permeabilities (Kpara1 and Kpara2), multiplied by the fault zone variable Parallel damage (see Figure 7(d) in the section on Fault zone dimensions). These two variables should therefore be reset to include effects on permeability of minor faults in the ramp. Creating more levels in the Hierarchy A new level can be added using the Add level button. The new level (level n) takes the values of the constants from the highest level prior to its addition (i.e. from level n-1), and the constants for each level can be reviewed and modified by selecting an existing level from the hierarchical level listing. The Remove level button removes the level currently selected (level m), and moves up all lower levels (i.e. what was level m+1 becomes the new level m). It is impossible to remove level 1 of a hierarchy if it only has 1 level. Managing the Fault zone hierarchy libraries Once the Constants (as described above) for all the required level(s) in a hierarchy have been input, the Hierarchy can be saved to the user's fault zone library. Select Save to library from the File options to access the Name prompt window. Input an appropriate name and click on OK to save the hierarchy, which can then be loaded into a subsequent TransGen run. A previously saved hierarchy can be loaded into a TransGen run by choosing the Load from library, File option. This lists the names, and number of levels, in each library item in the user's saved hierarchies. Click on the required fault zone Hierarchy followed by the Load option. HINT:- Hierarchies can also be deleted from the library using this dialog. The fault zone library is located in the file: ~/.transgen/fzone.lib When the Hierarchical fault zone definition page is set as required, click on the Next >> button to view the current settings in the Project (TGDATA) File. Alternatively, click on the << Back button to return to the Drag applied to fault traces page. Or click on the Contents button to access the Contents page to view/edit any of the current WizGen page settings, inspect the current TGDATA file and/or the session log generated by last ViewGen calculation. Click on Save to save any modifications made to the current TGDATA runfile. Click on Quit to exit from WizGen with or without saving the any changes to the TGDATA runfile. Alternatively, having completed both the Drag applied to fault traces and the Hierarchical fault zone definition pages (and all the other pages) in WizGen, Save the settings and click on the ViewGen icon to run the model as set. [UP] [TOP] [HOME]");sQ1[110]=new Array("TGmanual/144.html","Ramp geometry","","[UP] [TOP] [HOME] Ramp geometry Setting the Width/throw & Length/width ratios The size of the ramps generated at each hierarchical level are linked to the throw on the fault trace through the ratios Width/throw and Length/width. Relay ramps generally have length to width ratio between 1.0 and 10.0 (averaging ca. 3.0), and, at the point of breaching have width to throw ratios of ca. 3.0, so will be higher pre-breach. Appropriate values of Width/throw and Length/width for unbreached relays might therefore be 4.0 and 3.0, with similar Length/width ratios as for breached relays but lower Width/throw ratios. Setting the Breaching indices The geometry of the ramp is defined by the two Breaching indices included in the hierarchical level. Breaching index (BI) is defined as BI = DB/D, where DB is the throw at time of breaching and D is the present day throw on the fault. An unbreached relay is generated when both Breaching index 1 and Breaching index 2 are set to 1.0. A single-breach relay is generated when Breaching index 1 is less than 1.0 and Breaching index 2 = 1.0. If both Breaching index 1 and Breaching index 2 are less than 1.0, the ramp is doubly-breached. Below are shown examples of fault zones defined with different breaching indices on the fault trace shown in (a). (b) An unbreached relay generated with both Breaching indices set to 1.0. (c) A single-breach relay generated with Breaching index 1 = 0.4 & Breaching index 2 = 1.0. (d) A restoration of this ramp at the time of breaching (i.e. at 40% of the final throw). (e) A doubly-breached ramp generated with Breaching index 1 = 0.3, Breaching index 2 = 0.7. (f) A restoration of this ramp at the time of the formation of the first breach (i.e. at 30% of the final throw). (g) A restoration of the ramp at the time of formation of the second breach (i.e. at 70% of the final throw). All throw between 30% and 70% of the final throw is accommodated on the footwall fault, but the final 30% of throw (i.e. from Fig. (g) to fig (e)) is accommodated equally on both faults. The examples shown above with the throws restored for the breached and doubly-breached ramps illustrate some assumptions made in the construction of the ramps. The ramp construction assumes that:- There is no component of ramp dip perpendicular to the trace. The first breach occurs on the footwall fault. The dip of the ramp does not increase with accumulation of throw once the first breach has occurred. The two fault segments on each side of a doubly-breached ramp accommodate equal amounts of the throw accumulated since the second breach. The values of r1, r2, r3 and r4 used in the internal definition of the ramp (see Section on Fault zone properties) are calculated from the two breaching indices. [UP] [TOP] [HOME]");sQ1[111]=new Array("TGmanual/145.html","Stochastic ramp placement","","[UP] [TOP] [HOME] Stochastic ramp placement Fault zones are placed stochastically at each level in the hierarchy, conditioned by the Frequency constant (F) and the Minimum throw cut-off (Tmin) specified for the level, by the throw of the fault trace, i.e. the absolute value of throw after the drag ratio (if any) has been applied and by the length of the trace. At each level, ramps are constructed to give a self-similar segmented fault geometry in which a fault with a particular throw will have 10 times as many ramps (which are 10 times smaller, see Ramp geometry) than a fault with 10 times the throw. The absolute frequency of ramps generated on traces with particular throws is governed by the Frequency constant. Assuming only one hierarchical level, the average spacing (s) between ramps is:- s = frequency constant / fault throw. Hence for the default Frequency constant value of 0.01, a fault with a throw of 1m has fault zones spaced, on average, every 100 metres, while a fault with a throw of 10m has zones spaced every 1000 metres. The Figure below shows some simplified examples, i.e. scaled cartoons of faults with idealised populations of relays, generated as a function of the Frequency constant, Length/width and Width/throw settings. In each case, the relays (black) have a Length/width setting of 3.0 and in examples (a) to (e) a Width/throw setting of 2.0. (a) With the Frequency constant = 1/10 (0.10) (b) With the Frequency constant = 1/20 (0.05) (c) With the Frequency constant = 1/40 (0.025) (d) With the Frequency constant = 1/10 (0.10) for a fault with twice the throw of the fault shown in (a) (e) With the Frequency constant = 1/10 (0.10) for a fault with four times the throw of the fault shown in (a) (f) For a fault with the same throw as the fault in (a) but with two hierarchical levels; F = 1/40 (0.025) & W/T = 2.0 for the rarer fault zones and F = 1/5 (0.50) & W/T = 1.0 for the smaller, more common zones. NOTE:- In these cartoons the ramps are placed regularly on the fault - ramps generated by TransGen are placed probabilistically and are therefore not regularly spaced. The routine used to place the ramps stochastically uses the expression shown below to determine the probability that a particular trace contains a ramp:- p = (frequency constant * trace length ) / fault throw  Note that this equation can return a value > 1 (particularly for traces with very small throws), in which case, ideally, the trace would contain more that one ramp. Since TransGen only allows one ramp per trace, if this occurs a single ramp is placed on the trace. The constant Minimum throw defines the minimum fault throw (after the drag ratio has been applied) below which no fault zones will be applied, i.e. if a trace has a throw less than this value, no fault zones are applied.  This constant is included since the transmissibility effects of ramps on faults with very small throws is negligible (unless the faults have extremely low permeabilities), but the processing time associated with them can be large. The Minimum throw takes a default value of 0.1m, but, in practice, can be set to approximately the thickness of the cells. The plugin written by WizGen processes each hierarchical level sequentially, starting from level 1, which should therefore contain rarer, larger ramps (i.e. lower values of the Frequency constant and higher values of Width/throw). Ramps from the particular level being processed are not placed on traces which have already had ramps placed at a higher level. NOTE:- This means that user-defined fault zones placed using the TGFZONE keyword are never overwritten by stochastically generated ramps. [UP] [TOP] [HOME]");sQ1[112]=new Array("TGmanual/146.html","DRAG plugin","","[UP] [NEXT] [TOP] [HOME] DRAG plugin The DRAG plugin is designed to apply a drag ratio to fault traces (see section on Traces and Fault zones for further information). Although not recommended, it can also be used to modify the value of aveThrow. Since aveThrow is the summation of the system throw (which cannot be altered since it is a function of the input ZCORN geometry) and any user-defined throw input using the TGTHROW keyword, the effect of modifying aveThrow in the plugin is to modify the user-defined component of aveThrow. HINT:- Alternatively, the drag on fault traces can be defined either by including the TGDRAG keyword (and associated data) or using equation(s), i.e. for Probablistic throw uncertainty and/or Deterministic normal drag. The DRAG (and FZONE plugins) complement the existing TransGen plugins (i.e. CELLPROP, PERM, THICK, AREA - see Using Plugins in TransGen). The two new plugins are run after all system traces have been identified and any deterministic user-defined modifications to these traces using the new keywords (TGTHROW, TGDRAG, TGTRACE, TGFZONE) have been applied. Both new plugins are called once for every trace in the model, with the DRAG plugin called before the FZONE one. Hence any modifications made to trace properties in the DRAG plugin are reflected in the input to the FZONE plugin. If you want to input user-defined criteria to determine how drag is modelled on fault traces, select the Use a plugin option on the Drag applied to fault traces page of WizGen (as shown below). Then click on Next>>, <<Back or Save to access the Edit plugin pop-up and on Yes to access the User-defined plugins page. When the User-defined plugins page is accessed directly from the Drag applied to fault traces page (as shown below), the plugins page automatically opens with the Function set to DRAG and the current DRAG plugin displayed. To view/modify the user-defined DRAG plugin at any other time, click on the current Function to access the drop-down list and click on DRAG. The default DRAG plugin (shown above) is one automatically generated by the WizGen plugin tool including both probabilistic throw uncertainty (+/- 20m) and the deterministic normal drag equation with default values (see Using equation on Drag applied to fault traces page of WizGen). A few notable bits of C++ functionality used in the plugin are discussed in the section on C++ functionality in DRAG & FZONE plugins. Alter or input from scratch your required DRAG plugin code. For example, an alternative user-defined DRAG plugin could be defined with the following code:- if (t.dragFlag == false) { t.dragRatio = 0.75; } This applies a drag ratio of 0.75 to all traces that have not already been applied a drag ratio using the TGDRAG keyword. NOTE:- Only trace properties are available for use in the DRAG (and FZONE plugins) which must be referred to using the  t.  prefix. The list of available trace properties is shown below. The set of trace properties available for use in the DRAG and FZONE plugins [UP] [NEXT] [TOP] [HOME]");sQ1[113]=new Array("TGmanual/147.html","FZONE plugin","","[PREV] [UP] [TOP] [HOME] FZONE plugin The FZONE plugin is designed to place fault zones on fault traces (see section on Traces and Fault zones for further information). Although not recommended, it can also be used to assign values of dragRatio or (like the DRAG plugin) to modify the value of aveThrow. HINT:- Alternatively, Fault zone structure associated with faulted traces can be defined either by including the TGFZONE keyword (and a