E2V User Guide

© 2008 Landmark Graphics Corporation

R5000.0.1
 © 2008 Landmark Graphics Corporation
All Rights Reserved Worldwide

This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also
protected by Federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed,
stored in a retrieval system, or translated into any human or computer language, in any form or by any means,
electronic, magnetic, manual, or otherwise, or disclosed to third parties without the express written permission of:

Landmark Graphics Corporation

2107 CityWest Blvd, Building 2, Houston, Texas 77042-3051, USA
P.O. Box 42806, Houston, Texas 77242, USA
Phone:713-839-2000, FAX: 713-839-2015
Internet: www.halliburton.com/landmark

Trademarks
3D Drill View, 3D Drill View KM, 3DFS, 3D Surveillance, 3DView, Active Field Surveillance, Active Reservoir Surveillance, ADC,
Advanced Data Transfer, ARIES, ARIES DecisionSuite, AssetConnect, Asset Decision Solutions, Asset Development Center,
AssetDirector, Asset Journal, AssetLink, AssetLink Advisor, AssetLink Director, AssetLink Observer, AssetObserver, AssetObserver
Advisor, Asset Performance, AssetPlanner, AssetSolver, AssetSolver Online, AssetView, BLITZPAK, CasingLife, CasingSeat,
COMPASS, Corporate Data Archiver, Corporate Data Store, Data Analyzer, DataManager, DataStar, DBPlot, Decision Management
System, DecisionSpace, DecisionsSpace 3D Drill View KM, DecisionSpace AssetLink, DecisionSpace AssetPlanner, DecisionSpace
AssetSolver, DecisionSpace AssetView 2D, DecisionSpace AssetView 3D, DecisionSpace Atomic Meshing, DecisionSpace Decision
Management Systems(DMS), DecisionSpace for Production, DecisionSpace Infrastructure, DecisionSpace Nexus, DecisionSpace
PowerModel, DecisionSpace PrecisionTarget, DecisionSpace Reservoir, DecisionSpace TracPlanner, DecisionSpace Well Seismic
Fusion, DecisionSpace WellSolver, DecisionSuite, DepthTeam, Depth Team, DepthTeam Explorer, Depth Team Explorer, DepthTeam
Express, Depth Team Express, DepthTeam Extreme, Depth Team Extreme, DepthTeam Interpreter, Depth Team Interpreter, Desktop
Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery, Discovery Asset, Discovery FrameBuilder, DMS, Drillability Suite,
Drilling Desktop, DrillModel, Drill-to-the-Earth Model, Drillworks, Drillworks ConnectML, DSS, Dynamic Reservoir Management,
Dynamic Surveillance System, EarthCube, EDM, EDT, eLandmark, Engineer’s Data Model, Engineer's Desktop, Engineer’s Link,
ESP, Event Similarity Prediction, ezFault, ezModel, ezSurface, ezTracker, FastTrack, FG+, FieldPlan, Field Scenario Planner, FZAP!,
GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix Exploration System, GeoLink, GeoProbe GF DataServer, GES, GES97,
GESXplorer, GMAplus, GMI Imager, GRIDGENR, Handheld Field Operator, HHFO, I2 Enterprise, iDIMS, IsoMap, iWellFile, i Wellfile,
KnowledgeSource, Landmark, Landmark Decision Center, Landmark & Design, Landmark Logo and Design, Landscape, Lattix,
LeaseMap, LMK Resources, LogEdit, LogM, LogPrep, Make Great Decisions, MathPack, MIMIC, MIMIC+, Model Builder,
MyLandmark, Nexus, Object MP, OpenBooks, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWorks,
OpenWorks Development Kit, OpenWorks Well File, OpenWorks Production, PAL, Parallel-VIP, PetroBank, PetroBank Explorer,
PetroBank Master Data Store, PetroWorks, PetroWorks Asset, PetroWorks Pro, PetroWorks ULTRA, PlotView, Point Gridding Plus,
Pointing Dispatcher, PostStack, PostStack ESP, PostStack Family, PowerCalculator, PowerExplorer, PowerExplorer Connect,
PowerGrid, PowerHub, Power Interpretation, PowerJournal, PowerModel, PowerView, PrecisionTarget, Presgraf, Pressworks,
PRIZM, Production Asset Manager, Production, PROFILE, Project Administrator, ProMAGIC, ProMAGIC Connect, ProMAGIC
Server, ProMAX, ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX 4D, ProMAX Family, ProMAX MVA, ProMAX VSP, pSTAx,
Query Builder, Quick, Quick+, QUICKDIF, QuickWell, QuickWell+, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RAYMAP+,
Real Freedom, Real Time Asset Management Center, Real Time Decision Center, Real Time Operations Center, Real Time
Production Surveillance, Real Time Surveillance, Real-Time View, Reference Data Manager, Reservoir Framework Builder, RESev,
ResMap, RightTime, RTOC, SCAN, SeisCube, SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisWorks 2D,
SeisWorks 3D, SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerSection, SeisWorks PowerView,
SeisXchange, Semblance Computation and Analysis, Sierra Family, SigmaView, SimConnect, SimConvert, SimDataStudio,
SimResults, SimResults+, SimResults+3D, SIVA+, SLAM, smartSECTION, Spatializer, SpecDecomp, StrataAmp, StrataMap,
StrataModel, StrataSim, StrataWorks, StratWorks, StratWorks 3D, StreamCalc, StressCheck, STRUCT, Structure Cube, Surf &
Connect, SynTool, SystemStart, SystemStart for Clients, SystemStart for Servers, System Start for Servers, SystemStart for Storage,
Tanks & Tubes, TDQ, Team Workspace, TERAS, The Engineer’s Desktop, Total Drilling Performance, TOW/cs, TOW/cs Revenue
Interface, TracPlanner, TracPlanner Xpress, Trend Form Gridding, Turbo Synthetics, VESPA, VESPA+, VIP, VIP-COMP, VIP-CORE,
VIPDataStudio, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, Wellbase,
Wellbore Planner, Wellbore Planner Connect, WELLCAT, Well Cost, WELLPLAN, Well Seismic Fusion, WellSolver, WellXchange,
WOW, Xsection, You're in Control. Experience the difference, ZAP!, and Z-MAP Plus are trademarks, registered trademarks or
service marks of Landmark Graphics Corporation.

All other trademarks, service marks and product or service names are the trademarks or names of their respective owners.

Note
The information contained in this document is subject to change without notice and should not be construed as a commitment by Landmark
Graphics Corporation. Landmark Graphics Corporation assumes no responsibility for any error that may appear in this manual. Some states
or jurisdictions do not allow disclaimer of expressed or implied warranties in certain transactions; therefore, this statement may not apply to you.
Landmark acknowledges that certain third party code has been bundled with, or embedded in, Landmark’s
software. The licensors of this third party code, and the terms and conditions of their respective licenses,
may be found at the following location:

..\Nexus-VIP5000.0.1\help\com\lgc\dspx\Third_Party.pdf
Landmark E2V User Guide

Table of Contents

Table of Contents

E2V (Eclipse-to-VIP)
Introduction..................................................................................................................... 7
Using E2V........................................................................................................................ 8
Setting the Properties .................................................................................................8
Defining the Conversion Files .................................................................................13
Converting to VIP ....................................................................................................14
Troubleshooting ............................................................................................................. 15
Conversion Issues in VIP-CORE .............................................................................15
Conversion Issues in VIP-EXEC .............................................................................18

Appendix A: UTM Coordinates

Grid Scaling .............................................................................................................22
None .........................................................................................................................22
Shift to Origin ..........................................................................................................23
UTM Axes Align Only ............................................................................................24
UTM Coordinates ....................................................................................................25

Appendix B: Large Model Option

Introduction.................................................................................................................... 27
General Operation of the Large Model Option.............................................................. 28
Running Large Model Option from the Command Line ............................................... 29
Error Logging ..........................................................................................................30
Running Large Model Option from the User Interface ................................................. 31

Appendix C: Unsupported Eclipse Keywords

R5000.0.1 Table of Contents v

E2V User’s Guide Landmark

vi Table of Contents R2003.19.3

Landmark E2V User Guide

E2V (Eclipse-to-VIP)

Introduction

E2V is a Windows application to assist in the conversion of Eclipse

data files into an equivalent VIP format. The program works by looking
at the entire Eclipse data file and mapping the Eclipse keywords and
associated arguments on to the VIP equivalents where possible. The
VIP data can be parsed into SimData Studio and converted to Nexus
format if you are using that application.

Within VIP, start the program by selecting E2V from the Input menu
in DESKTOP-VIP, or by running the program E2V.exe. Within Nexus,
click the E2V icon on the main Nexus application window. The
E2V utility opens as shown below:

Various buttons and menu options let you control the conversion of
Eclipse data to VIP. These are discussed in detail on the following
pages.

R5000.0.1 Introduction: E2V (Eclipse-to-VIP) 7

E2V User Guide Landmark

Using E2V

Setting the Properties

Before you begin an Eclipse-to-VIP conversion, you may want to
review and set the preferences used in the conversion. To do this, select
Properties option on the Tool menu. You will see an E2V Translation
Options dialog box with two tabs in it, as discussed below.

Standard Options
The default set of options are grouped under the Standard tab, and
control the following:

• Null Keywords. Include Eclipse keywords that are categorized as

having no (or a null) effect on the VIP simulation. An example of
such a keyword is the Eclipse DEBUG keyword which has no
effect on either the Eclipse or VIP simulation results. These
keywords are included as comment lines in the VIP file.

• Include Comments. Any comment lines in the original Eclipse

data file will be included as comment lines in the VIP file. These
will be mapped onto the closest VIP equivalent section where
possible.

• Create Include Files. It is possible to send array-based properties

to separate include files instead of to a single file. This can reduce
the size of the translated CORE file. This was always done for the

8 Using E2V: E2V (Eclipse-to-VIP) R5000.0.1

Landmark E2V User Guide

CORP array for corner point systems. The name of the included
array is formed from the root case name plus the array name. You
can include all arrays in a single file by deactivating the Create
Include Files option on the Properties dialog box.

• Binary CORP File. The default is to produce a text VIP CORE

file, but this can be a very large file. This option produces a binary
CORP file which is typically 75% smaller than the equivalent text
version.

• Right-handed Grids. Instructs E2V to place a RIGHTHANDED

keyword into the converted CORP file for grids that are right
handed instead of the default of left handed.

• Solution Data Cards. Converts Eclipse Solution cards into

similar VIP timestep controls.

• Preferred Production Phase. It is possible to specify a preferred

phase for all production wells in the VIP file. In Eclipse a well can
be specified with both oil and gas production limits and be under
BHP rate control. Since the VIP equivalent well only allows a
single production limit this option overrides the default selection
of the latter which uses the largest of the two limits. If Oil is
chosen as the preferred production phase then such wells would be
given an oil limit even if the gas limit was larger.

• Well Data Control. You can specify none, wild card wells, or All
Wells. If wild card wells is selected, the data for wells specified
with wild cards in Eclipse will be converted into a minimal
number of lines of VIP data. If All Wells is selected, E2V will
attempt to compress all the well control data into as few lines as
possible.

R5000.0.1 Using E2V: E2V (Eclipse-to-VIP) 9

E2V User Guide Landmark

Advanced Options
There are several advanced facilities with can effect the contents of the
VIP mapped file. These are grouped under the Advanced tab.

• Specials. Landmark continually enhance the facilities offered by

VIP and this option controls the translation of such facilities. It is
intended for Landmark internal use only since these facilities will
be only available in future releases of VIP.

• Grid Optimization. This controls a powerful facility which

processes the data contained in the Eclipse GRID and EDIT
sections into a format that can be understood by VIP. One
advantage of this facility is that the resulting CORE file is small,
but it is difficult to make modifications to the resulting file since it
contains the grid described in terms of transmissibilities, cell
centre depths, pore volumes and faults. Basically this option
replaces the VIP CORE calculation of these quantities and can
take a considerable time to calculate. The resulting VIP CORE file
does initialize in a much shorter time since a large amount of
calculations are not required. It is recommended that this option is
used only by experienced users.

• Kh calculation for wells. Eclipse allows the effects of geometry

to be included in the calculation of the connection factor between a
well perforation and corresponding grid block. In VIP the
direction is assumed to be Z and the quantities Kx, Ky and DZ are
always used. If E2V encounters a perforation in X or Y (using Ky,

10 Using E2V: E2V (Eclipse-to-VIP) R5000.0.1

Landmark E2V User Guide

Kz, DY and Kx, Kz, DX respectively) then it calculates the value

used by Eclipse and writes this to the FPERF card as the Kh value.
The default is for this option to be enabled to allow the closest
match between Eclipse and VIP files.

• Maintain MLTFAULT. The default method of handling

MLTFAULT cards is to map these onto a set of transmissibility
modifier cards. This makes it easier to apply subsequent
modifications to the faults since the structure of the original
Eclipse definition is maintained. However, the VIP equivalent
representation can be considerably larger than that of Eclipse since
multiple fault multipliers on any one fault need to be represented
by the full definition of every fault connection instead of a single
line as in Eclipse. You can map each fault onto a single
transmissibility modifier card by deactivating the Maintain
MLTFAULT option on the Properties dialog box.

• Maintain ACTNUM. The default method of handling the

ACTNUM arrays has been modified so that the PORO array is
maintained as the original definition plus a set of modifier cards.
The ACTNUM array is now translated into a multiplicative array
acting on the pore volume. This allows the structure of the original
Eclipse porosity and ACTNUM arrays to be maintained. You can
combine the porosity and ACTNUM arrays into a single POR
array by deactivating the Maintain ACTNUM option on the
Properties dialog box.

• Datum depth correction. This option corrects the datum depth for
equilibration to be consistent with VIP. Specifically if the datum
depth is outside the oil zone, it will be properly adjusted to the
appropriate contact, with associated changes to the reference
pressure.

• Map grid to UTM coords. This option enables the conversion of

the MAPAXES data into the corner point values for VIP,
preserving UTM coordinates.

• Create Obs file.If the Eclipse run uses WCONHIST data, E2V
will produce a VIP observed data file.

• Eclipse BHP default depth. This option produces VIP data that
defines the reference depth for BHP calculations to be the depth to
the top perforation of the well, consistent with the Eclipse default.
This will apply only for the wells that were defaulted in Eclipse. If
explicit reference depths were entered in Eclipse, these values will
be used in VIP.

R5000.0.1 Using E2V: E2V (Eclipse-to-VIP) 11

E2V User Guide Landmark

• Extended black oil tables. This option produces PVT data for
VIP using the extended black oil format of possible, based upon
the Eclipse input method.

• Array Repeat Limit. Both Eclipse and VIP support concatenation

of equal blocks of array data using the syntax "n*value". For
example 5*4 means five elements of value 4. The default value of
n is 1000 (this is also the upper limit), but this can be changed by
entering another value. A value of 1 disables repeat counts which
can make the comparison of array values between Eclipse and VIP
easier.

Applying Selections
When you are finished selecting conversion options, click the Apply
button to store the options. The options can be reset to the defaults by
pressing the Defaults button. If the Cancel button is pressed then the
last set of options will be retained.

12 Using E2V: E2V (Eclipse-to-VIP) R5000.0.1

Landmark E2V User Guide

Defining the Conversion Files

Before converting from Eclipse-to-VIP, you must specify the files to be
converted and the resulting VIP file to be created.

Eclipse File to be Converted

The Browse button beside the Eclipse File to be Converted field lets
you select the Eclipse data file to be converted. This is the file that
Eclipse would use to control the simulation run. To select this file:

1. Click the Browse button. The Choose Eclipse File to Load dialog
box opens:

2. Double-click on the name of the file to be converted. If you do not

see the filename in this window, use the controls at the top of the
dialog box to locate the folder where it is stored.

3. Click the Open button to close the file selection dialog box. The
selected file path/name displays in the Eclipse File to be
Converted field.

VIP File to be Created

The Browse button beside the VIP File to be Created field lets you
specify the VIP data file to be created from the converted Eclipse data.
The name that you specify will be used to create two output files,
<name>i.dat and <name>r.dat, where the former is for input to the VIP
CORE program and the latter is for input to the VIP EXEC program.
These file names adhere to the usual VIP naming convention for
selecting a case for input to VIP.

R5000.0.1 Using E2V: E2V (Eclipse-to-VIP) 13

E2V User Guide Landmark

To specify the output filename:

1. Click the Browse button. The Choose VIP File to Save dialog box
opens:

2. Type in the desired filename and click the Save button.

Converting to VIP
The Convert to VIP button starts the conversion process and can only
be selected after the Eclipse and VIP files have been chosen.

The translation procedure involves loading the entire Eclipse data set
including any INCLUDE files into memory then scanning through the
contents and process these into the VIP equivalents. Due to the
different implementation of some facilities in both programs it is not
always possible to map an Eclipse keyword and it’s associated data
onto a direct equivalent in VIP. In such cases the original Eclipse data is
included as a bracketed set of comments in the VIP data set. This
allows the rapid identification of these Eclipse keywords using an
editor. For details on conversion issues, see the Troubleshooting section
later in this document.

The Exit button stops the program.

14 Using E2V: E2V (Eclipse-to-VIP) R5000.0.1

Landmark E2V User Guide

Troubleshooting

The following section presents some practical issues to consider when

converting a reservoir simulation model from Eclipse to VIP. Most
keywords in Eclipse can be translated into an equivalent keyword in
VIP. However, some keywords do not directly translate, so an attempt
is made in this section to highlight the most important of these.

Due to design differences between the simulators, there are also some
differences in default values and algorithms. The information in this
section is not intended to be exhaustive, but to serve as a reference to
aid in resolving data set conversion difficulties. The information is
organized alphabetically either by VIP keyword, Eclipse keyword, or
subject.

Conversion Issues in VIP-CORE

API. API tracking in Eclipse requires the 3 component black-oil option
in VIP.

BOTAB. VIP requires the Rs, BO, and VO data to be monotonically

decreasing and the VO data to be monotonically increasing, with
decreasing pressure. Eclipse does not impose these monotonicity
restrictions. E2V does not check for these conditions, but simply
converts the Eclipse data as specified. In addition, VIP requires an
entry in the BOTAB at pressure equal to standard pressure. If such an
entry is not provided in the Eclipse data set, then E2V extrapolates the
input data to calculate one for VIP. The user should check these
extrapolated values for consistency.

BRINE. The Eclipse water salinity option is not yet converted to VIP
format.

DWB. Water properties and rock properties in VIP are constant. If the
Eclipse data set has multiple PVTW tables or ROCK tables, E2V
averages the table properties to get the water and rock properties
entered on the DWB card.

Endpoint scaling. Eclipse defaults to two point relative permeability

endpoint scaling, while VIP defaults to three point scaling. For three
point relative permeability scaling, VIP scales relative permeability at a
fewer number of saturation endpoints than Eclipse. For water-oil
systems, water relative permeability cannot be scaled at maximum
water saturation (SWU) and oil relative permeability cannot be scaled

R5000.0.1 Troubleshooting: E2V (Eclipse-to-VIP) 15

E2V User Guide Landmark

at irreducible water saturation (SWR). For gas-oil systems, gas relative

permeability cannot be scaled at maximum gas saturation and oil
relative permeability cannot be scaled at irreducible gas saturation. The
relative permeability is taken from the saturation table for each of the
saturation endpoints identified above.

EOS. There are two formulations of the Peng-Robinson equation-of-

state. The original formulation calculates the omegaA parameter as a
single function of component acentric factor and temperature. The
omegaA calculation was later modified to use an alternative equation in
those cases where the component acentric factor is greater than 0.49.
The Eclipse default is the original formulation. The modified
formulation is requested with the PRCORR keyword in Eclipse. The
VIP Peng-Robinson default is the modified version. The original
formulation is requested with the PRORIG keyword in VIP. Significant
differences will occur if different Peng-Robinson formulations are
used.

Gas oil contact. VIP and Eclipse use the gas oil contact specification
data differently. Eclipse uses the specified GOC as a guide to calculate
initial conditions. If there is an inconsistency in initialization data
controls, either in composition or initial pressure, Eclipse allows the
adjustment of the location of the GOC. VIP strictly enforces the GOC.
Likewise, if there is inconsistency in initialization data controls, VIP
adjusts the initial pressure at reference depth to be consistent with the
saturation pressure at the GOC.

Hysteresis. There are differences between default settings between VIP

and Eclipse for the hysteresis options. The user should check be sure to
set the number of scanning curves to 1 for capillary pressure hysteresis
in VIP to be compatible with Eclipse. Note that the user must enter
secondary drainage curves for capillary pressure hysteresis in VIP.

IEQUIL. In some cases, Eclipse does not define initial conditions for
an equilibrium region. Since the data does not appear in the Eclipse
data set, E2V does not create the IEQUIL data in VIP. This is required
data for VIP, so the user will have to add this data to the converted data
set.

LGR. Local grid refinement data may not be converted properly into
VIP format, especially if each of the locally refined grids has corner
point data defined.

NEWTRAN. The NEWTRAN transmissibility calculation option in

Eclipse is equivalent to the NEWTRAN option in VIP. However, VIP
defaults to a more accurate harmonic integration based transmissibility

16 Troubleshooting: E2V (Eclipse-to-VIP) R5000.0.1

Landmark E2V User Guide

calculation method, while Eclipse defaults to NEWTRAN for corner

point grids and OLDTRAN for Cartesian grids. To try to reproduce the
transmissibility calculation of Eclipse in VIP, NEWTRAN should be
entered in VIP. If a more accurate method is desired, allow VIP to
default by omitting NEWTRAN.

Non-equilibrium initialization. RS and API arrays can be entered in

Eclipse for non-equilibrium black-oil initializations. Non-equilibrium
black-oil initialization requires a PSAT versus depth table or PSAT-API
versus depth table, if variable API is modeled. Variable PSAT or API
by grid block is not possible in VIP.

Oil relative permeability. Three-phase oil relative permeability is

calculated using a saturation-weighted option by default in Eclipse.
VIP uses STONE2 as the default method for this calculation. The
KROINT keyword should be used in the VIP data set to approximate
the Eclipse method.

PCW/PCG. VIP does not have an equivalent of the PCW and PCG
arrays to allow multipliers for capillary pressure by grid block. This
Eclipse option can be emulated by defining the JFUNC option in the
utility data section and then using the VOVER option to replace the
JFUNC multipliers with the appropriate capillary pressure multipliers.
Note that one set of multipliers will be applied to both the water-oil and
gas-oil capillary pressures when using the VOVER JFUNC method.

Composition vs. depth. All composition vs. depth tables in VIP must
honor the specified GOC; that is, all compositions above the specified
depth must be dew points, and all compositions at or below the GOC
must be bubble points. Eclipse does not have this restriction and will
determine where the GOC is from the input compositions and their
calculated saturation pressure. When converting this data from Eclipse
to VIP, the user may have to adjust the GOC or enter equilibrium phase
compositions to allow the model to initialize. Initial fluids in place
must be validated between the two models to insure model agreement.

SGR/SGRO. VIP requires endpoint arrays to be entered in pairs; that

is, if the SGRO array in entered, then the SGR array must be entered as
well. Similarly, SWR and SWRO must both be entered if one of them is
entered. If the Eclipse data set uses only one of the two arrays, the
converted data set will produce an error when run in VIP. The user must
create an array for the missing property. This also applies to directional
property arrays.

SGU. The value of SGU must be less than 1-SWL in VIP. This
constraint is applied if saturation endpoint arrays are input or if

R5000.0.1 Troubleshooting: E2V (Eclipse-to-VIP) 17

E2V User Guide Landmark

saturation table values are used. For the case of table control, the last
gas saturation table entry, Sgu, must not exceed 1-Swc, where Swc is
the largest water saturation entry in the corresponding water saturation
function table where krw equals zero. Eclipse does not use this
constraint and E2V does not check for it in all cases.

Reservoir temperature. The user must specify reservoir temperature

on the DWB card in VIP. This value is not available from an Eclipse
100 data set, and E2V places a value of zero for reservoir temperature
in the VIP data set.

SWATINIT. The Eclipse option to use the SWATINIT array, along

with the PCW array, to initialize water saturation to non-equilibrium
conditions is not converted into VIP format. This conversion must be
done manually. Since Eclipse internally adjusts the SWATINIT data to
account for fluid contacts, significant work must be done outside of
E2V and VIP to convert this data to be equivalent to Eclipse. To insure
that an equivalent water saturation distribution is used in VIP, it is
advisable to extract the calculated initial water saturation array from
Eclipse output, rather than use the SWATINIT array.

Temperature variation. Composition and temperature can be defined

by array input for the compositional option of VIP as in Eclipse. A
composition-temperature versus depth table can also be used in VIP.

Conversion Issues in VIP-EXEC

Automatic drilling. The Eclipse QDRILL option is not available in
VIP.

BHP control. Wells that are specified on BHP control in Eclipse,

without rate specified, are converted to producers with no rate in VIP
and are treated as undrilled. The user should check to see that all such
wells are given a QMAX equal to a value large enough to force the well
on BHP control.

BHPTAB. E2V converts VFP data from Eclipse into BHPTAB data for
VIP. Earlier versions of VIP required a consistent use of constraints in
this table, such that QLIQ and GLR were acceptable along with QOIL
and GOR, but combinations such as QLIQ and GOR were not. E2V
issues a warning comment into the VIP data set concerning any
discrepancy of this sort. For VIP versions prior to 1998.2.0, the original
VFP data must be modified to allow a consistent set of constraints in
VIP.

18 Troubleshooting: E2V (Eclipse-to-VIP) R5000.0.1

Landmark E2V User Guide

Crossflow. Eclipse models set crossflow as active, be default for each

well, while VIP models set crossflow as inactive, by default. E2V
creates XFON/XFOFF cards as required to match the Eclipse settings.
The use of the QMX option on the XFON card will disable crossflow in
a well until a non-zero rate is given to the well.

FPERF. VIP requires that a complete set of well perforation data be

entered for a well each time a set of FPERF data is entered. Eclipse
requires only the changes to well perforations to be entered. As a result,
the amount of VIP input data and Eclipse input data may differ
significantly in describing the same well perforation history.

Horizontal wells. The user should check that the KH value entered in
the FPERF data reflects the proper grid block geometry for horizontal
perforations. By default, VIP uses the grid block thickness in the KH
calculation. If the Eclipse model uses perforations in the X or Y
directions, then the FPERF data must contain the proper KH
calculation. For example, for an X direction perforation, Eclipse
calculates KH as DX*(KX*KZ).5, while the VIP default will be
DZ*(KX*KY).5. Similar differences occur for the RADB parameter in
VIP. E2V will calculate the correct Eclipse-equivalent values as an
option during conversion.

Injector mobility. The default methods for calculating mobility for

water and gas injectors are different between simulators. The Eclipse
default is total grid block mobility. The VIP default is endpoint
mobility. Injector mobility method is specified on WINJMOB and
GINJMOB cards of VIP.

RIGDEF. The data created by E2V for the RIGDEF card in VIP may
be incorrect. The user must convert any automatic workover data
manually.

Targeting. Forecast grouping and scale-back options are problematic

in data set conversion. Investigate the INJTAR option when trying to
model complex injection targeting schemes.

THP control. Wells that are specified on THP control in Eclipse,

without rate specified, are converted to producers with no rate in VIP
and are treated as undrilled. The user should check to see that all such
wells are given a QMAX equal to a value large enough to force the well
onto THP control.

Voidage injection. If injection based upon group voidage is specified

with the WCONINJ card in Eclipse, the resulting VIP data set should
be checked to insure that the FRES option is used for the injection well

R5000.0.1 Troubleshooting: E2V (Eclipse-to-VIP) 19

E2V User Guide Landmark

type and that the proper well management level is specified (e.g.
FIELD or GATHER).

Well definition. Wells with default rate specification in Eclipse may

not be completely translated into VIP format by E2V. A warning
message will appear in the VIP data set for these wells.

Well management. GRUPTREE control in Eclipse is translated into a

tree-like well management structure in VIP. The user should check this
data to be sure that it is the structure that is desired. In general, extra
well management entities may be added to balance the tree. Also, the
numbering of the well management entities may differ from the Eclipse
numbering.

WEFAC. The WEFAC option in Eclipse is translated into the

ONTIME keyword in VIP. Eclipse applies WEFAC only to the
cumulative injection and production, while VIP applies ONTIME to
both rates and cumulatives. As a result, a comparison of well rates
between VIP and Eclipse may show significant differences, while the
cumulatives match.

WLIFT. Artificial lift well control is not currently converted into VIP
format by E2V.

YINJ. An injection gas composition must be specified in VIP for all

gas injection wells, unless the well injects produced gas. This is true for
both compositional and black oil models.

20 Troubleshooting: E2V (Eclipse-to-VIP) R5000.0.1

Landmark E2V User Guide

Appendix A: UTM Coordinates

The treatment of UTM coordinates by E2V has been modified so that

numerical problems caused when translating grids from the Eclipse
coordinate system to VIP are minimized. With the 2003 release of E2V
UTM coordinates were calculated by applying a rotation and a
translation to the Eclipse grid (assuming that a suitable MAPAXES
keyword was present). In some circumstances, generally when the grid
unit system was feet, the final grid would lose accuracy when mapped
onto a single precision number. The effects of such rounding errors
could be difficult to spot, but would produce different results between
Eclipse and VIP.

In order to solve the above E2V was modified to allow control over the
way that the UTM transformation is applied. In 2003 the only choice
was UTM conversion on or off, but subsequent releases four options
over how the grid is translated, have been available: None; Shift to
origin; UTM axes align only and UTM Coordinates. Each of these are
explained below.

To enable easy comparison of these differing options the effects on the

results of the 20X20X6 Eclipse data set are shown. Below shows the
Eclipse grid and associated grid data file. All images of the grid are of
the permeability in the x direction and of layer one only with the (1, 1,
1) cell in the bottom left hand corner, such that both i and j increase
along the x and y-axes.

MAPAXES
0.58700000E+06 0.59464000E+07
0.58700000E+06 0.59465000E+07
0.58710000E+06 0.59465000E+07
/
COORD
0.00000000E+00 -0.10000000E+06
0.24443262E+04 0.00000000E+00
-0.10000000E+06 0.25883965E+04
0.74999995E+04 -0.10000000E+06
0.23968813E+04 0.74999995E+04
-0.10000000E+06 0.25672598E+04

Note however, that the grids in Eclipse are right-handed (yj+1 > yj) by
default, whereas VIP has left-handed (yj+1 < yj) grids by default, the
same handedness of the UTM Frame.

R5000.0.1 Appendix A: UTM Coordinates 21

E2V User Guide Landmark

Any changes to the translation caused by the recent E2V Update

(number 8) will be highlighted in the individual cases.

Grid Scaling
It is possible in Eclipse to set the units of the corner point grid to be
different to that of the simulation model. In 2003, E2V compensated for
this by adjusting the values of the Eclipse corner point data to match
that of the model. However, as for UTM translations, scaling from
metres to feet could result in rounding errors once the data was mapped
onto single precision values. The subsequent releases do not apply the
scaling factor to the CORP array, but instead include it as MODX,
MODY and MODZ multipliers after the CORP array is output.

None
This is equivalent to the 2003 UTM off setting and no translations are
applied to the grid. Below shows the output for both the Right hand
grids option being applied and not, respectively (a pattern that applies
to all subsequent graphs).

CORP VALUE

C LAYER 1

0 -100000 2444.326
7500 -100000 2396.881
7500 -95000 2372.198
0 -95000 2428.91
0 -100000 2507.359
7500 -100000 2459.171
7500 -95000 2431.072
0 -95000 2495.542
CORP VALUE

C LAYER 1

0 100000 2444.326
7500 100000 2396.881
7500 95000.01 2372.198
0 95000.01 2428.91
0 100000 2507.359
7500 100000 2459.171
7500 95000.01 2431.072
0 95000.01 2495.542

This behaviour has remained unchanged by recent updates.

22 Appendix A: UTM Coordinates R5000.0.1

Landmark E2V User Guide

Shift to Origin
This is a new setting and defines what happens if no UTM shift is
required. With this option E2V works out the minimum position of the
x and y coordinates of the Eclipse coordinate lines. These values are
then applied as an offset to the grid so that it is shifted closer to the
origin (0, 0). For the case of a grid entirely in negative coordinate space
it is the maximum position of x and y that defines the offset. The corner
points are calculated and two entries MODX and MODY are appended
after the CORP record. These values will be applied to VIP to move the
grid back to the correct coordinate system. The aim of this offset is to
keep the grid as close as possible to the origin and minimise the effects
of rounding errors using single precision numbers. This is particularly
important for Eclipse grids that are specified in UTM coordinates. If a
MAPAXES keyword is present then the origin specified by MAPAXES
is used to defined the x and y offsets.

In effect the result is that when plotted the grid appears to have a (0, 0)
origin but the *.CORP file contains the grid data in the UTM axes.

CORP VALUE

C LAYER 1

587000 5846500 2444.326

594500 5846500 2396.881
594500 5851500 2372.198
587000 5851500 2428.91
587000 5846500 2507.359
594500 5846500 2459.171
594500 5851500 2431.072
587000 5851500 2495.542
CORP VALUE

C LAYER 1

587000 -5846500 2444.326

594500 -5846500 2396.881
594500 -5851500 2372.198
587000 -5851500 2428.91
587000 -5846500 2507.359
594500 -5846500 2459.171
594500 -5851500 2431.072
587000 -5851500 2495.542

Previously, when having the Right hand grids option enabled the x and
y values of the CORP array had been flipped (i.e. negative to that
above). Whilst in the case where Right hand grids option was not
enabled the CORP array and graphed grid were the same as the None
case.

R5000.0.1 Appendix A: UTM Coordinates 23

E2V User Guide Landmark

UTM Axes Align Only

This setting aligns the grid with the axes specified in the MAPAXES
keyword. However, no translation is applied and the offsets are
included as MODX and MODY entries.

The values of the offsets are defined from either the data or the
MAPAXES keyword. If MAPAXES is missing then this will be
equivalent to Shift to Origin option.

CORP VALUE

C LAYER 1

0 100000 2444.326
7500 100000 2396.881
7500 95000 2372.198
0 95000 2428.91
0 100000 2507.359
7500 100000 2459.171
7500 95000 2431.072
0 95000 2495.542
CORP VALUE

C LAYER 1

0 100000 2444.326
7500 100000 2396.881
7500 95000 2372.198
0 95000 2428.91
0 100000 2507.359
7500 100000 2459.171
7500 95000 2431.072
0 95000 2495.542

When compared to previous version of E2V there are only differences

here in respect with the Right hand grids option enabled case. The grid
has changed handedness from the Eclipse right handed grid to a left
handed grid, as highlighted by a dialogue box during the conversion.
Both translations are the same as there is no option to force right
handedness in the UTM frame.

24 Appendix A: UTM Coordinates R5000.0.1

Landmark E2V User Guide

UTM Coordinates
This is equivalent to the 2003 UTM on setting and a full rotation and
translation is applied.

CORP VALUE

C LAYER 1

587000 6046500 2444.326

594500 6046500 2396.881
594500 6041500 2372.198
587000 6041500 2428.91
587000 6046500 2507.359
594500 6046500 2459.171
594500 6041500 2431.072
587000 6041500 2495.542
CORP VALUE

C LAYER 1

587000 6046500 2444.326

594500 6046500 2396.881
594500 6041500 2372.198
587000 6041500 2428.91
587000 6046500 2507.359
594500 6046500 2459.171
594500 6041500 2431.072
587000 6041500 2495.542

However, here both sets of CORP arrays and consequently the graphed
gird have been altered. Previously the CORP array in both cases
matched that of the None option and there were no MODX or MODY
modifiers.

Here both cases produce the same results, just as in the UTM Axes
Align Only case.

R5000.0.1 Appendix A: UTM Coordinates 25

E2V User Guide Landmark

26 Appendix A: UTM Coordinates R5000.0.1

Landmark E2V User Guide

Appendix B: Large Model Option

Introduction

Previous versions of E2V attempted to load the entire contents of an

Eclipse model to system memory. However, many Eclipse models are
too large to be held in memory without degrading performance. To
counter this deficiency, E2V provides an option that temporarily dumps
Eclipse data into files until the data is needed and then deletes the files
when the job is finished. This option is called the “large model option.”
It significantly reduces the memory usage for large Eclipse models.

The large model option is intended for very large models, on the order
of millions of cells. However, a PC with a small amount of RAM by
today's standards may show an improvement for models over a hundred
thousand cells.

R5000.0.1 Appendix B: Large Model Option 27

E2V User Guide Landmark

General Operation of the Large Model Option

The large model option is disabled by default.

When the option is enabled, a threshold must be defined for the

minimum number of cells that the input Eclipse grid must contain in
order for E2V to generate temporary files. Any models with cells fewer
than this threshold will not employ the large model option. A threshold
of zero causes the large model option to be utilized for all Eclipse
models. The default threshold is 5,000,000 cells.

With the large model option enabled, E2V outputs temporary files to a
new directory called “LMO” that it creates within the specified output
folder for the VIP model. Once E2V has completed its run, it deletes
these files and the directory. If an existing large model option folder
already resides in the specified output directory, E2V will delete that
folder before creating a new one.

28 Appendix B: Large Model Option R5000.0.1

Landmark E2V User Guide

Running Large Model Option from the Command Line

The large model option can be invoked at the command line with the
-BIGMODEL flag.

A typical job is run from the command line as follows:

E2V -IN "C:\Eclipse Data\" -OUT "C:\E2V Results\"

In this example, the Eclipse input files reside in the C:\Eclipse Data\
directory and the results are output to the C:\E2V Results\ directory.

Double quotes enclose the input and output arguments, since both paths
have spaces in them. Also, the paths include a closing '\'. Without this
slash, E2V would go looking for Eclipse files in the next directory up,
in this case the C:\ drive.

To use the large model option, the command would be modified as

follows:

E2V -BIGMODEL 30000 -IN "C:\Eclipse Data\" -OUT "C:\E2V Results\"

In this example, the large model option would be employed for Eclipse
models that exceed 30,000 cells.

R5000.0.1 Appendix B: Large Model Option 29

E2V User Guide Landmark

Error Logging
If there are any errors in the operation of the LMO, an error message
will appear in the <model>.dbg file as follows:

Error in ReadArrays - deleteScratchFile

Within the <model>.log file another message will appear as follows:

C
C ERROR: Unable to delete temporary files/directory created for LMO.
C Access to LMO in output directory denied.
C Please run without Large Model Option (LMO) enabled or -BIGMODEL argument.
C
E2V will either operate correctly and output the resulting VIP model or
be unable to process any grid data. In the latter case, the job must be
run again. The failure will generally be caused by the system being
unable to purge the LMO folder before it outputs its first temporary
file. In either case, E2V may have to be run without the LMO enabled.

30 Appendix B: Large Model Option R5000.0.1

Landmark E2V User Guide

Running Large Model Option from the User Interface

By default, the large model option is inactive. You can enable it in the
Advanced tab of the Properties window (Tools -> Properties ->
Advanced). A 'Large Model Optimization' check box appears at the
bottom of the Advanced tab.

Large
Model
Optimization
Option

With the check box toggled ON, you can specify the desired grid cell
threshold in the Grid Cell Threshold field. This threshold controls the
minimum number of cells a model has to contain before the large
model option is utilized.

R5000.0.1 Appendix B: Large Model Option 31

E2V User Guide Landmark

In the example below, the large model option will only operate with an
Eclipse model of sizes greater than 2000 cells.

Typically this threshold is set for only the largest models, those of
greater than a million cells.

As E2V creates and deletes temporary files and directories, it may be

not be able to delete the temporary “LMO” directory or files due to
permission limitations on the system. In this case, an error message will
be posted stating that E2V is unable to delete the temporary directory
or files.

The resulting VIP model will be correct but the output directory will
still contain a subdirectory named “LMO.” You will have to delete the
“LMO” directory manually before you can run another job with the
large model option enabled.

32 Appendix B: Large Model Option R5000.0.1

Landmark E2V User Guide

Appendix C: Unsupported Eclipse

Keywords

The following Eclipse keywords are not supported in the R2003.19.3 release of E2V.

ACTION Not Available

ADDZCORN Not Available
AIM Not Available
AIMPVI Not Available
ALPHA Not Available
AMALGAM Not Available
AMF Not Available
AMFVD Not Available
API Not Available
APIGROUP Not Available
APIVD Not Available
AQANTRC Not Available
AQCOEF Not Available
AQUCON Not Available
AQUFLUX Not Available
AQUNUM Not Available
AUTOCOAR Not Available
AUTOREF Not Available
BDENSITY Not Available
BGGI Not Available
BICAQ1 Not Available
BICAQ2 Not Available
BICAQ3 Not Available
BOGI Not Available
BRANPROP Not Available
BRINE Not Available
COAL Not Available
COALADS Not Available
COALPP Not Available
COARSEN Not Available
COLLAPSE Not Available
COMPFLSH Not Available
COMPINJK Not Available
COMPOFF Not Available
COORDSYS Not Available
COPYBOX Not Available
CRITPERM Not Available
DIFFAOIL Not Available
DIFFCGAS Not Available
DIFFCOIL Not Available
DIFFCOAL Not Available
DIFFDP Not Available

R5000.0.1 Appendix C: Unsupported Eclipse Keywords 33

E2V User Guide Landmark

DIFFMR Not Available

DIFFMR- Not Available
DIFFMTH- Not Available
DIFFMTHT Not Available
DIFFMX Not Available
DIFFMX- Not Available
DIFFMY Not Available
DIFFMY- Not Available
DIFFMZ Not Available
DIFFMZ- Not Available
DIFFR Not Available
DIFFTHT Not Available
DIFFTR Not Available
DIFFTTHT Not Available
DIFFTX Not Available
DIFFTY Not Available
DIFFTZ Not Available
DIFFUSE Not Available
DIFFX Not Available
DIFFY Not Available
DIFFZ Not Available
DISGAS Not Available
DNGL Not Available
DPKRMOD Not Available
DPNUM Not Available
DRAINAGE Not Available
DRILPRI Not Available
DRSDT Not Available
DRVDT Not Available
DUMPCUPL Not Available
DZMATRIX Not Available
DZMTRX Not Available
DZMTRXV Not Available
EDITNNC Not Available
ENDACTIO Not Available
ENDFIN Not Available
ENDNUM Not Available
ENKRVD Not Available
ENKRVDX Not Available
ENKRVDX- Not Available
ENKRVDY Not Available
ENKRVDY- Not Available
ENKRVDZ Not Available
ENKRVDZ- Not Available
ENPCVD Not Available
ENPTVD Not Available
ENPTVDX Not Available
ENPTVDX- Not Available
ENPTVDY Not Available
ENPTVDY- Not Available
ENPTVDZ Not Available
ENPTVDZ- Not Available
EQLZCORN Not Available
FACTLI Not Available

34 Appendix C: Unsupported Eclipse Keywords R5000.0.1

Landmark E2V User Guide

FIPOWG Not Available

FOAM Not Available
FOAMADS Not Available
FOAMDYCO Not Available
FOAMDYCW Not Available
FOAMMOB Not Available
FOAMMOBP Not Available
FOAMMOBS Not Available
FOAMROCK Not Available
FRICTION Not Available
FVST Not Available
FWELLS Not Available
GASBEGIN Not Available
GASCONC Not Available
GASEND Not Available
GASFCOMP Not Available
GASFDELC Not Available
GASFIELD Not Available
GASMONTH Not Available
GASYEAR Not Available
GCONPRI Not Available
GCONTOL Not Available
GCUTBACK Not Available
GCVD Not Available
GDCQ Not Available
GDCQECON Not Available
GDFILE Not Available
GDRILPOT Not Available
GETSOL Not Available
GETGLOBAL Not Available
GI Not Available
GIALL Not Available
GIMODEL Not Available
GINODE Not Available
GLIFTLIM Not Available
GLIFTOPT Not Available
GNETDP Not Available
GNETINJE Not Available
GNETPUMP Not Available
GPMAINT Not Available
GQUALITY Not Available
GRUPMAST Not Available
GRUPNET Not Available
GRUPSLAV Not Available
GSATCOMP Not Available
GSATINJE Not Available
GSATPROD Not Available
GSWINGF Not Available
GUIDERAT Not Available
HOST Not Available
HRFIN Not Available
HTFIN Not Available
HXFIN Not Available
HYFIN Not Available

R5000.0.1 Appendix C: Unsupported Eclipse Keywords 35

E2V User Guide Landmark

HYST Not Available

HYSTJ Not Available
HYSTK Not Available
HZFIN Not Available
IKRG Not Available
IKRGR Not Available
IKRGRX Not Available
IKRGRX- Not Available
IKRGRY Not Available
IKRGRY- Not Available
IKRGRZ Not Available
IKRGRZ- Not Available
IKRGX Not Available
IKRGX- Not Available
IKRGY Not Available
IKRGY- Not Available
IKRGZ Not Available
IKRGZ- Not Available
IKRO Not Available
IKRORG Not Available
IKRORGX Not Available
IKRORGX- Not Available
IKRORGY Not Available
IKRORGY- Not Available
IKRORGZ Not Available
IKRORGZ- Not Available
IKRORW Not Available
IKRORWX Not Available
IKRORWX- Not Available
IKRORWY Not Available
IKRORWY- Not Available
IKRORWZ Not Available
IKRORWZ- Not Available
IKROX Not Available
IKROX- Not Available
IKROY Not Available
IKROY- Not Available
IKROZ Not Available
IKROZ- Not Available
IKRW Not Available
IKRWR Not Available
IKRWRX Not Available
IKRWRX- Not Available
IKRWRY Not Available
IKRWRY- Not Available
IKRWRZ Not Available
IKRWRZ- Not Available
IKRWX Not Available
IKRWX- Not Available
IKRWY Not Available
IKRWY- Not Available
IKRWZ Not Available
IKRWZ- Not Available
IMKRVD Not Available

36 Appendix C: Unsupported Eclipse Keywords R5000.0.1

Landmark E2V User Guide

IMKRVDX Not Available

IMKRVDX- Not Available
IMKRVDY Not Available
IMKRVDY- Not Available
IMKRVDZ Not Available
IMKRVZ- Not Available
IMPORT Not Available
IMPTVD Not Available
IMPTVDX Not Available
IMPTVDX- Not Available
IMPTVDY Not Available
IMPTVDY- Not Available
IMPTVDZ Not Available
IMPTVDZ- Not Available
INTPC Not Available
IPCG Not Available
IPCW Not Available
ISGAS Not Available
ISGCR Not Available
ISGCRX Not Available
ISGCRX- Not Available
ISGCRY Not Available
ISGCRY- Not Available
ISGCRZ Not Available
ISGCRZ- Not Available
ISGL Not Available
ISGLX Not Available
ISGLX- Not Available
ISGLY Not Available
ISGLY- Not Available
ISGLZ Not Available
ISGLZ- Not Available
ISGU Not Available
ISGUX Not Available
ISGUX- Not Available
ISGUY Not Available
ISGUY- Not Available
ISGUZ Not Available
ISGUZ- Not Available
ISOGCR Not Available
ISOGCRX Not Available
ISOGCRX- Not Available
ISOGCRY Not Available
ISOGCRY- Not Available
ISOGCRZ Not Available
ISOGCRZ- Not Available
ISOLNUM Not Available
ISOWCR Not Available
ISOWCRX Not Available
ISOWCRX- Not Available
ISOWCRY Not Available
ISOWCRY- Not Available
ISOWCRZ Not Available
ISOWCRZ- Not Available

R5000.0.1 Appendix C: Unsupported Eclipse Keywords 37

E2V User Guide Landmark

ISWCR Not Available

ISWCRX Not Available
ISWCRX- Not Available
ISWCRY Not Available
ISWCRY- Not Available
ISWCRZ Not Available
ISWCRZ- Not Available
ISWL Not Available
ISWLPC Not Available
ISWLX Not Available
ISWLX- Not Available
ISWLY Not Available
ISWLY- Not Available
ISWLZ Not Available
ISWLZ- Not Available
ISWU Not Available
ISWUX Not Available
ISWUX- Not Available
ISWUY Not Available
ISWUY- Not Available
ISWUZ Not Available
ISWUZ- Not Available
KRGR Not Available
KRGRX Not Available
KRGRX- Not Available
KRGRY Not Available
KRGRY- Not Available
KRGRZ Not Available
KRGRZ- Not Available
KRNUMMF Not Available
KRORG Not Available
KRORGX Not Available
KRORGX- Not Available
KRORGY Not Available
KRORGY- Not Available
KRORGZ Not Available
KRORGZ- Not Available
KRORW Not Available
KRORWX Not Available
KRORWX- Not Available
KRORWY Not Available
KRORWY- Not Available
KRORWZ Not Available
KRORWZ- Not Available
KRWR Not Available
KRWRX Not Available
KRWRX- Not Available
KRWRY Not Available
KRWRY- Not Available
KRWRZ Not Available
KRWRZ- Not Available
KVGEN Not Available
LANGMUIR Not Available
LANGSOLV Not Available

38 Appendix C: Unsupported Eclipse Keywords R5000.0.1

Landmark E2V User Guide

LBCCOEF Not Available

LOTUS Not Available
MATCORR Not Available
MAXTRANZ Not Available
MAXVALUE Not Available
MAXVALUE Not Available
MAXVALUE Not Available
MINDZNET Not Available
MINPVV Not Available
MINVALUE Not Available
MINVALUE Not Available
MINVALUE Not Available
MISC Not Available
MISCEXP Not Available
MISCNUM Not Available
MULTFLT Not Available
MULTPV Not Available
MULTR- Not Available
MULTREGT Not Available
MULTTHT- Not Available
MULTX Not Available
MULTX- Not Available
MULTY- Not Available
MULTZ- Not Available
NCONSUMP Not Available
NEI Not Available
NETBALAN Not Available
NETCOMPA Not Available
NETWORK Not Available
NOAIMLGR Not Available
NODEPROP Not Available
NODPCO Not Available
NODPPM Not Available
NODPPM Not Available
NOMIX Not Available
NONNC Not Available
NOPC9 Not Available
NUMRES Not Available
OILAPI Not Available
OILVISCT Not Available
OLDTRAN Not Available
OLDTRANR Not Available
OPTIONS Not Available
OPTIONS Not Available
OPTIONS Not Available
OPTIONS Not Available
OPTIONS Not Available
OPTIONS Not Available
OPTIONS Not Available
OPTIONS Not Available
OVERBURD Not Available
PARAOPTS Not Available
PBUB Not Available
PCG Not Available

R5000.0.1 Appendix C: Unsupported Eclipse Keywords 39

E2V User Guide Landmark

PCW Not Available

PDEW Not Available
PDVD Not Available
PERMAVE Not Available
PERMMF Not Available
PIMTDIMS Not Available
PIMULTAB Not Available
PINCHXY Not Available
PLYADS Not Available
PLYMAX Not Available
PLYROCK Not Available
PLYSHEAR Not Available
PLYVISC Not Available
PLYVISCS Not Available
PMAX Not Available
PMISC Not Available
PPCWMAX Not Available
PRIORITY Not Available
PRORDER Not Available
PRVD Not Available
PSEUDOS Not Available
PVDS Not Available
PVTWSALT Not Available
QDRILL Not Available
QMOBIL Not Available
RADFIN4 Not Available
RCMASTS Not Available
RECOVERY Not Available
RECOVERY Not Available
REFINE Not Available
REFINE Not Available
REFINE Not Available
RESIDNUM Not Available
RESVNUM Not Available
ROCKWNOD Not Available
RPTISOL Not Available
RS Not Available
RSGI Not Available
RV Not Available
RVCONST Not Available
RVCONSTT Not Available
RVGI Not Available
RVVD Not Available
RVVD Not Available
SALINITY Not Available
SALT Not Available
SALTNODE Not Available
SALTVD Not Available
SCALECRS Not Available
SCALELIM Not Available
SCVD Not Available
SDENSITY Not Available
SGCWMIS Not Available
SGF3 Not Available

40 Appendix C: Unsupported Eclipse Keywords R5000.0.1

Landmark E2V User Guide

SGWCR Not Available

SKIPREST Not Available
SOF32D Not Available
SOIL Not Available
SOLVCONC Not Available
SOLVDIRS Not Available
SOLVENT Not Available
SOLVFRAC Not Available
SOMGAS Not Available
SOMWAT Not Available
SORWMIS Not Available
SPECHEAT Not Available
SPECROCK Not Available
SSFN Not Available
SSOL Not Available
STONEPAR Not Available
STOW Not Available
SURFACT Not Available
SURFADS Not Available
SURFCAPD Not Available
SURFNUM Not Available
SURFROCK Not Available
SURFST Not Available
SURFVISC Not Available
SWATINIT Not Available
SWF3 Not Available
SWGCR Not Available
SWINGFAC Not Available
SWLPC Not Available
TBLK Not Available
TBLK Not Available
THCONR Not Available
THPRES Not Available
THPRESFT Not Available
TNUM Not Available
TRACER Not Available
TRACERS Not Available
TRACTVD Not Available
TRADS Not Available
TRCOEF Not Available
TRDCY Not Available
TRDIF Not Available
TRROCK Not Available
TVDP Not Available
TVDP Not Available
TZONE Not Available
USECUPL Not Available
VAPOIL Not Available
VAPPARS Not Available
VAPPARS Not Available
VCRITVIS Not Available
VDFLOW Not Available
VECTABLE Not Available
VEFIN Not Available

R5000.0.1 Appendix C: Unsupported Eclipse Keywords 41

E2V User Guide Landmark

VEFRAC Not Available

VEFRACP Not Available
VEFRACPV Not Available
VEFRACV Not Available
VFPTABL Not Available
VISCD Not Available
VISCREF Not Available
WADVANCE Not Available
WAGHYSTR Not Available
WATERTAB Not Available
WATVISCT Not Available
WAVAILIM Not Available
WBOREVOL Not Available
WCYCLE Not Available
WDRILPRI Not Available
WDRILRES Not Available
WELLDIMS Not Available
WELLKBHP Not Available
WELPRI Not Available
WELSOMIN Not Available
WFOAM Not Available
WFRICNTL Not Available
WFRICTN Not Available
WGASPROD Not Available
WGORPEN Not Available
WGRUPCON Not Available
WHISTCTL Not Available
WINJMULT Not Available
WLIFT Not Available
WLIFTOPT Not Available
WNETCTRL Not Available
WNETDP Not Available
WORKTHP Not Available
WPAVE Not Available
WPITAB Not Available
WPLUG Not Available
WREGROUP Not Available
WSALT Not Available
WSEPCOND Not Available
WSOLVENT Not Available
WSURFACT Not Available
WTAKEGAS Not Available
WTEMP Not Available
WTHPMAX Not Available
WTRACER Not Available
WVFPEXP Not Available
XSTC Not Available
YMFVP Not Available
YSTC Not Available
ZCRITVIS Not Available
ZMF Not Available

42 Appendix C: Unsupported Eclipse Keywords R5000.0.1