You are on page 1of 18

ECLIPSE Suite

Version 2015.1

Release Notes
ECLIPSE Suite Release Notes

Proprietary notice
Copyright © 2015 Schlumberger. All rights reserved. Reproduction or alteration without prior written permission is prohibited, except as
allowed under applicable law.
Use of this product is governed by the License Agreement. Schlumberger makes no warranties, express, implied, or statutory, with
respect to the product described herein and disclaims without limitations any warranties of merchantability or fitness for a particular
purpose.

Trademarks & service marks


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

Security notice
The software described herein is configured to operate with at least the minimum specifications set out by Schlumberger. You are
advised that such minimum specifications are merely recommendations and not intended to be limiting to configurations that may be
used to operate the software. Similarly, you are advised that the software should be operated in a secure environment whether such
software is operated across a network, on a single system and/or on a plurality of systems. It is up to you to configure and maintain your
networks and/or system(s) in a secure manner. If you have further questions as to recommendations regarding recommended
specifications or security, please feel free to contact your local Schlumberger representative.
ECLIPSE Suite Release Notes

Table of contents

1 Release highlights.................................................................................................................................. 2
ECLIPSE 2015.1 .................................................................................................................................... 2
Performance ....................................................................................................................................... 2
Enhanced oil recovery ........................................................................................................................ 3
Other new and improved functionality ................................................................................................ 3
FrontSim 2015.1 .................................................................................................................................... 4
Performance ....................................................................................................................................... 4
Other new and improved functionality ................................................................................................ 4
ECLIPSE pre- and post-processing developments ............................................................................... 4
2 Release overview................................................................................................................................... 5
System and licensing information .......................................................................................................... 5
Platform availability ............................................................................................................................ 5
Licensing ............................................................................................................................................ 6
Deprecated features .............................................................................................................................. 7
Deleted features..................................................................................................................................... 7
3 Known issues ......................................................................................................................................... 9
ECLIPSE ................................................................................................................................................ 9
ECLIPSE 100 ................................................................................................................................... 10
ECLIPSE 300 ................................................................................................................................... 11
ECLRUN .............................................................................................................................................. 11
FrontSim .............................................................................................................................................. 11
Systems ............................................................................................................................................... 13
Documentation ..................................................................................................................................... 16

Table of contents
i
ECLIPSE Suite Release Notes

Release highlights
1
The 2015.1 release of the ECLIPSE suite includes some major developments enhancing the functionality, usability
and performance capabilities of the simulators. The developments include improvements to the performance of
ECLIPSE, both in terms of improving existing functionality and also by adding a new timestep selection scheme
capable of selecting a longer average timestep than the standard scheme. Developments to chemical enhanced oil
recovery (EOR) in this release add to available methods and improve interoperability with flux boundary conditions.
In ECLIPSE 300 generalized pseudo-pressure has been extensively improved.

These changes and others are outlined below with a full explanation in the "ECLIPSE Reference Manual" and
"FrontSim User Guide".

ECLIPSE 2015.1

Performance
A new timestep selection algorithm has been added to both ECLIPSE 100 and 300. This algorithm learns the nature
of the model during the run and tunes itself to select timesteps which progress the simulation as quickly as possible
by attempting to find the longest timestep which can converge. This algorithm has been shown to reduce runtimes in
the majority of simulations, with some cases running significantly faster. The new AITS keyword activates this
timestep selection method.

Frequency of % speed-ups with AITS. Frequency of % speed-ups with


ECLIPSE Black Oil AITS. ECLIPSE Compositional

150 40
30
100
20
50
10
0 0
-5
-10

0
5

More
10
15
20
30
50
100
200
-5
-10

0
5

More
10
15
20
30
50
100
200

Release overview
2
ECLIPSE Suite Release Notes

The CPR solver has also been enhanced to give better parallel scaling
in cases with LGRs in ECLIPSE 100. The CPR solver continues to be
an area of focus, with improved reliability and performance.

Enhanced oil recovery


ECLIPSE 100 has been extended to allow end point scaling of
relative permeability and capillary pressure to be used with both
high and low capillary number curves when using the surfactant
modeling facility. This facility may be used with both oil- and water-
wet curves.

ECLIPSE 100 and 300 have both been extended to allow a wider
range of sector modeling workflows. In ECLIPSE 100 some tracer
and chemical EOR components are able to leave sector boundaries,
particularly when pressure boundary conditions are used. In
ECLIPSE 300 this allows multi-component water components to
enter and leave a sector. Furthermore, an ECLIPSE 300 multi-
component water sector model may now be run using a full field
model with only a single water component. In both simulators a
number of improvements to the robustness of the sector modeling
facility have been made.

Other new and improved functionality


ECLIPSE 300 has been extended to allow the control of generalized pseudo-pressure (GPP) on a well-by-well basis.
The generalized pseudo-pressure method has been re-engineered to allow for improved control, reporting and ease-
of-use, making it easier to tune this facility against local grid refinement on an individual well basis.

You can now specify the artificial lift quantity (ALQ) for well THP calculations using a user-defined argument. This
allows the ALQ for a well to be dynamically controlled based on user-defined quantities or summary output.

ECLIPSE 100 and 300 have been extended to allow the user to set the default BHP limit for wells from a single
keyword. This simplifies input and is particularly helpful in circumstances when convergence issues are encountered
due to unrealistic pressure limits.

Release overview
3
ECLIPSE Suite Release Notes

A new shorthand method for specifying output data for certain coupled simulations has been created.

For the full list of new developments please refer to the "ECLIPSE Reference Manual".

FrontSim 2015.1

Performance
A new version of the linear solver allows FrontSim to run larger models in the range of 200 million active cells and
upwards. Previous versions of FrontSim terminate with models of this size.

The efficiency of the initialization of the grid module in FrontSim has been improved. For instance the
transmissibility calculation has been multi-threaded. This has most impact on screening and ranking workflows
where the initialization part takes a large portion of the total run time.

Other new and improved functionality


A new item in the GEOFLOFS keyword allows you to run FrontSim in Geoscreening mode. This aligns the
functionality and output to be identical to the engine in the Geoscreening plug-in.

The new optional keyword FBHPDEF provides a default bottom hole pressure (BHP) target or limit to be used where
none is specified for a well.

The output of the accumulated streamline Time-of-flight (TOF) data to the XXXX_TOF.txt file has been slightly
changed to make it represent the change in flow capacity better.

For more details on the new developments please refer to the "FrontSim User Guide".

ECLIPSE pre- and post-processing developments


The focus of this release has been on the maintenance of the pre- and post-processors, prioritizing business critical
defects. Subsequent releases will address additional issues.

Release overview
4
ECLIPSE Suite Release Notes

Release overview
2
• Schlumberger licensing has been updated and the 2015.1 license server contains critical security and stability
updates. If you use any SIS 2015.1 product release, including ECLIPSE, you must upgrade your Schlumberger
license servers prior to the software installation. SIS 2015.1 product releases will only run with 2015.1 or higher
versions of the Schlumberger license server. Refer to the “Schlumberger Licensing User Guide” for more
information.
• Schlumberger is working towards the retirement of the interactive products, and their replacement by Petrel
Reservoir Engineering. Customers are strongly advised to consult their SIS Account Manager about the
transition to Petrel Reservoir Engineering (RE). Note that Petrel RE includes access to some of the interactive
products (ECLIPSE Office, Schedule, FloGrid, FloViz and GRAF) under the Petrel license.
• GRAF 2015.1 will be the final release of GRAF.
• ECLIPSE 2016.1 will generate a modified SMSPEC file containing an “INTEHEAD” record; this will allow
Petrel Reservoir Engineering and other applications to determine the simulator which generated summary
output and the units convention used in the simulation. You can preview this format in 2015.1 using item 259 of
the OPTIONS keyword in ECLIPSE 100 or item 335 of the OPTIONS3 keyword in ECLIPSE 300. You should
test this new format with any in-house or third party software using ECLIPSE summary output. Details of the
new record are given in the "File Formats Reference Manual".
• ECLIPSE 2015.1 is supplied with ECLRUN 2015 Update 1 and Simulation Launcher 2015.1.
• To view the ECLIPSE suite documentation, use a PDF viewer such as Adobe Reader or Foxit Reader, which are
available as free downloads from the internet. If your installed PDF reader does not work, install one of these.
For more detailed information on the developments in this release, see the "ECLIPSE Reference Manual" and the
"FrontSim User Guide". These are available in the ECLIPSE suite documentation set. Contact your Schlumberger
Account Manager for further details.

System and licensing information

Platform availability

All
No 32-bit systems are supported.

For full information on the supported hardware, devices and software systems mentioned in this chapter, refer to the
"ECLIPSE Suite Installation Guide".

Release overview
5
ECLIPSE Suite Release Notes

Linux
• ECLIPSE is supported on Red Hat 6 Update 5 or later.
• The InfiniBand drivers that are now tested are the OFED 3.5.1 drivers. These need to be installed and built, and
instructions on how to do this are in the "ECLIPSE Suite Installation Guide". The rpms are provided on the
ECLIPSE DVD.
• The IBM Platform MPI implementation has been shown to give better performance than the Intel MPI during
benchmarking. In a very small number of cases the MPI implementation can affect results due to the ordering of
parallel reductions; for this reason the ECLRUN default remains Intel MPI.
o To select Platform MPI for a single run use the eclrun –-comm flag with argument plmpi
o To change the default alter the eclrun.config file by adding the extra line <COMM>plmpi</COMM>
within the <Eclrun></Eclrun> section. If you choose to do this be aware that you are selecting the
Platform MPI for all simulations submitted by ECLRUN on that machine, including older versions of
ECLIPSE and INTERSECT.

Windows
• Microsoft Windows 7 64-bit Professional SP1 is supported but all 64-bit variants of Windows 7 are expected to
function correctly.
• Microsoft Windows 8.1 Professional 64-bit is supported.
• Microsoft Windows Server 2012 HPC and Windows Server 2012 R2 are supported for the simulators only.

EnginFrame portal for Schlumberger simulation software


An issue has been discovered which will impact users of Petrel Run Management using the NICE EnginFrame
portal for Schlumberger simulation software (EPSSS). The fix to this is in the 3rdparty/EPSSS_patch directory
on the ECLIPSE installation DVD. Alternatively you can get it by contacting your NICE or Schlumberger Account
Manager. Note that this fix is for the EPSSS, not ECLRUN.

EnginFrame 2013 is supported for simulator job submission only.

Benchmarks
The new distribution format includes all the benchmarks and utility software. The benchmark data includes new
FrontSim and ECLIPSE 300 benchmarks. These can be found under ECLIPSE/resources/BENCHMARKS.

Certified platforms
The supported hardware platforms and operating systems can be obtained from the certified systems letter that
accompanies this release. Reference benchmarks are available from your Account Manager.

Licensing
• Schlumberger licensing has been updated and the 2015.1 license server contains critical security and stability
updates. All users of SIS 2015.1 product releases including ECLIPSE must upgrade their Schlumberger license
servers prior to the software installation. SIS 2015.1 product releases will only run with 2015.1 or higher
versions of the Schlumberger license server. Refer to the “Schlumberger Licensing User Guide” for more
information.
• From the ECLIPSE 2014.1 release onwards, the old slbfd license daemon is no longer supported. The old
slbfd daemon has not been the default mechanism of licensing for ECLIPSE for a number of years and has
been retired. If you are still using a slbfd style license, request a new style license from your Account

Release overview
6
ECLIPSE Suite Release Notes

Manager. All licenses locked to CodeMeter dongles will be the new slbsls license, so no action is needed. If
the license is locked to anything else, then the type of license can be checked by looking at one of the ECLIPSE
INCREMENT lines.
A slbsls license feature (which will work) looks like this:

INCREMENT eclipse slbsls 2014.2 30-nov-2013 1 ……….


A slbfd license feature (which will not work with ECLIPSE 2014.1 or later) looks like this:

INCREMENT eclipse slbfd 2014.2 30-nov-2013 1 ……….

Windows licensing
• The FLEXlm tools are no longer distributed on the DVDs. All licensing is now run through the Schlumberger
licensing tool. The macros that used to drive FLEXlm are also no longer available.
• When running local simulations on Windows through ECLRUN (that is for simulations launched from Petrel or
the Simulation Launcher) the license check is disabled by default in ECLRUN. Please refer to the ECLRUN
User Guide" for details on how to enable the license check. It is recommended that Codemeter dongle drivers
are updated to version 5.1 or later and the dongle firmware updated. The latest release can be obtained from
either the DVD or the Codemeter web site.

Linux licensing
• Licensing is supported on platforms using Red Hat 6 Update 5 or later. It is recommended that CodeMeter
dongle drivers are updated to version 5.1 or later and the dongle firmware updated
• Some changes were made to the LSF, PBS Pro and UGE integration kits to support the new license features in
the 2015.1 release. If any old versions have been installed they must be removed and replaced with a new
version from the ECLIPSE DVD 3rd party directory. The scheduling system itself may also require an upgrade
and the required versions are specified in the “ECLIPSE Suite Installation Guide”.

Backward compatibility
Schlumberger endeavors to maintain license back compatibility (the ability to run for example version 2013.1 of
ECLIPSE under a 2015.1 license), but this is only guaranteed over a three year cycle. Clients wishing to run
versions that are more than three years old may be required to dedicate licenses to older versions and run a separate
license server for this purpose.

Deprecated features
The following feature was deprecated in the 2015.1 release and will be deleted from the 2016.1 and future releases.
If you require this feature in future releases please contact support.

GRAF
GRAF 2015.1 is the last version of GRAF that will be released.

Deleted features
The following features were deprecated in the 2014.1 release and were deleted from the 2015.1 release of the
ECLIPSE simulators.

Release overview
7
ECLIPSE Suite Release Notes

Geomechanics
The standalone Geomechanics option in ECLIPSE 300 is superseded by Petrel Reservoir Geomechanics, coupling
VISAGE with ECLIPSE. The ECLIPSE standalone option has been removed in 2015.1.

Release overview
8
ECLIPSE Suite Release Notes

Known issues
3
This section lists the known issues for the simulators, EPP products, systems and documentation

ECLIPSE
Generic simulation grid
When specifying MULTNUM in a GSG file for use with MULTREGT, the pre-sweep is unable to identify that MULTNUM is
present. To avoid MULTREGT being disallowed as a result, when GSG input is used, the simulator assumes that
MULTNUM data will be found in the GSG file if GRIDOPTS(2) has been used to dimension it. All this is invisible if
your dataset is legal. However, there is a minor side-effect if you create an invalid dataset dimensioning MULTNUM
using GRIDOPTS(2), use it in MULTREGT, but do not include it in the GSG file. In this case the error messages state
that the values of MULTNUM are out of range rather than the keyword is missing.

Multisegment wells
For both ECLIPSE 100 Blackoil and ECLIPSE 300 Compositional, multisegment wells that include a large number
of segments and looped flow paths can experience severe convergence problems. When this occurs, convergence
can sometimes be improved by excluding acceleration in the well pressure drop calculation method (WELSEGS item
6) and/or reducing the number of segments and loops.

Non-neighbor connections
At present, any changes to non-neighbor connection transmissibilities in the SCHEDULE section are not taken into
account in a restart run, and the original NNC transmissibilities will be reloaded. Results in a restart run performed
after use of keywords such as MULTX or MULTSIG, or after OPERATER has been used to change the permeability or a
multiplier, may therefore be inconsistent with the base run in any case which has NNCs (these may be due to
complex geometry, but can also be due to the presence of LGRs, dual porosity, pinchouts, just as a few examples). If
a restart is required, it should be performed before SCHEDULE section changes are made to transmissibility.

Parallel ECLIPSE
1. There are known limitations with the combination of PINCHXY and the Parallel option. If the simulation model
contains complex geometry, for instance, Y-shaped faults, use Petrel to define the geometry and NNCs
correctly. This information can be imported into ECLIPSE using a Generic Simulation Grid (.GSG).
2. There is a known issue concerning the use of single-porosity regions (using the DPNUM keyword) for dual-
porosity parallel runs in the ECLIPSE 100 and ECIPSE 300 reservoir simulators. It principally arises where the
dual-porosity region is small and is surrounded by a large single-porosity region. This is due to the fact that on

Known issues
9
ECLIPSE Suite Release Notes

some processors, only single porosity cells occur. This may result in a communication mismatch between
processors with and without dual porosity cells and therefore causing the simulation to fail. The most reliable
workaround is to make at least one cell on each processor dual porosity (that is with DPNUM=1).

Surfactant model
Combining the Surfactant Model with the Local Grid Refinements option may lead to numerical differences
between the original and the refined cases, particularly for very fine refinements.

Sector modeling
When declaring numerical aquifers with the AQUNUM keyword as part of a sector modeling workflow, the given
inactive grid blocks that represent a numerical aquifer need to be part of the active flux region. If this is not done the
aquifer will be deactivated in the reduced run. Attention must be paid when using Petrel to define numerical aquifers
in sector models, as Petrel randomly chooses the inactive cells to define the numerical aquifer and these cells may
lay outside the active flux region. Any cell may be forced to belong to any flux region using the FLUXNUM keyword
to avoid this problem.

ECLIPSE 100
1. When using UDQs and group quantities for the normal network model, the entire FIELD is not included as a
group quantity, while FIELD is present for the extended network model.
2. When transmissibility multipliers from ROCKTABH are determined, the explicit value of the pressure is used
rather than the implicit value. Normally this has very little effect. However if there is a change in the SCHEDULE
section that causes a large pressure change where the multipliers also change rapidly with pressure, then for the
next timestep, the multiplier selected may not reflect the new pressure accurately. To avoid this, you are advised
to put in a single very small timestep immediately following any such changes.
3. When running a simulation on Linux in parallel and with very large grids, the run may terminate without
issuing any warnings or errors. If the run is repeated in serial, an error should be output indicating an issue in
the allocation of sufficient memory. In some cases the issue may be avoided by using a larger number of
processors to further partition the grid.
4. SOLVFRAC values are not transcribed from the global grid into LGRs. It is also not possible to specify
SOLVFRAC values manually using REFINE in the SOLUTION section. This results in a zero SOLVFRAC value
being used in LGR cells.
5. There is a known discrepancy between the effective water viscosity that is reported and that which is used in the
calculation of the shear water viscosity in the PLYSHEAR and PLYSHLOG options. In the shear viscosity
calculation, the effective water viscosity belonging to the upwind cell is used, and this may differ from that
belonging to the cell in question. The resulting shear viscosity that is output may, as a consequence, be
inconsistent with the cell-based effective water viscosity output.
6. For certain ECLIPSE 100 models with the POLYMER functionality, convergence and timestep control is
suboptimal, particularly at the start and end of injection. It is advisable to be conservative with timestep,
Newton and linear iteration maxima during injection and particularly at major changes in the injection schedule.
The CPR solver may provide better convergence behavior and it is advisable to compare the performance of the
standard and CPR solvers.
7. There may be oscillations in bottom hole pressure profiles for wells injecting surfactant in the Surfactant Model.
This leads to instabilities in well potential calculations which can also affect the logarithm of the capillary
number used to model the effects of surfactant injection.
8. There is a convergence issue which may occur when the Surfactant Model is combined with the Multi-
component Brine option.
9. There are known summary reporting issues associated with the water flows at global-LGR boundaries where the
flows are computed as NNC flows. The water flows at such boundaries are reported as zero. This therefore

Known issues
10
ECLIPSE Suite Release Notes

means that, in polymer flood models, the shear multipliers at such boundaries are treated as unity and so the
reported shear water viscosities are equal to the corresponding effective water viscosities. The setting of shear
multipliers at these boundaries to unity also skews the calculation of the overall shear multiplier for the global
host cells and hence skews the corresponding pre-shear water flows consequently calculated based on the post-
shear water flows.
10. OPTIONS item 60, which restores the pre-97 dual permeability solver, should not be used with the CPR solver.
In most cases it will be ignored, but in some unstable models, this combination can lead to different results and
decreased performance.

ECLIPSE 300
BRINE and BDENSITY
In ECLIPSE 300, the BDENSITY keyword has limited application within the BRINE option. If BDENSITY is used, the
simulator will only satisfactorily convert between the number of moles of water and the corresponding water volume
when the salt concentration of the injected water matches the initial salt concentration in the reservoir. In such cases,
this salt concentration value must be entered as the reference salt concentration in PVTWSALT.

Dual porosity and permeability


For Dual Porosity or Dual Permeability models, the keywords MULTSIG(V) in the SCHEDULE section modify the
matrix-fracture coupling transmissibility. There is a known issue with the multiplier values being incorrectly
exported to the restart file under the heading MULTSIGS.

Dual tubing injector pressure control


For secondary injection wells, a limit may be imposed both upon the maximum injection pressure in the secondary
well segment and a maximum pressure in an additional nominated segment. When the well is opened using the
SCONINJE or STEST keywords, these maximum pressure limits are not honored prior to opening, and injection will
typically continue for the duration of a timestep before the secondary well is closed due to these limits. This
situation may be avoided by delaying the opening of the well until these limits no longer apply.

Thermal
The steam trap control can be unstable, particularly in SAGD simulations where there are many completions. As a
result, the production rate can oscillate and timesteps may be quite small. Small differences in simulation, for
example between different versions, can shift these oscillations which gives the impression that the answers have
changed. In fact the average production rate stays the same, but the “noise” changes.

ECLRUN
If the data deck contains either reservoir coupling or parallel (or both), the features do not need to appear in the
LICENSES keyword. Adding them there may well cause problems with ECLRUN.

FrontSim
Aquifer
1. The aquifer facility in FrontSim can produce different initial transient rates compared to an ECLIPSE run on the
same model. FrontSim may calculate a spike rate on a non-converged, initial, large time step. Reducing the
initial time steps and tuning can help to reduce this effect. Typically the steady state aquifer rate should match
with ECLIPSE.

Known issues
11
ECLIPSE Suite Release Notes

2. The aquifer option does not support connection to active cell faces within the grid.
3. The aquifer option does not allow a single cell face to be connected to multiple aquifers.
4. If there is backflow (negative rates) into the aquifer, the reported rates in the summary vectors (AAQR and AAQT)
are taken as the total reservoir flow rate (including gas and oil), but using the water volume factors to calculate
the rates at surface conditions.
This is different from ECLIPSE which reports the water flow only in the AAQR/AAQT summary vectors when
backflow occurs.

Dual porosity
In some Dual Porosity models, the translation of volumes from reservoir to surface conditions does not exactly
honor the input PVT.

End-point scaling
The output of scaled capillary pressure to the debug file is incorrect.

Generic simulation grid (GSG)


FrontSim and ECLIPSE have different ways of handling GSG Transmissibility and Pore Volume (T&PV) cells that
have zero PORO. ECLIPSE can use PORV in the T&PV workflow to activate such cells, while FrontSim does not
activate such cells when non-zero PORV values are input. As a result, there may be a small difference in the number
of active cells for such models between ECLIPSE and FrontSim.

Input/output
1. The Field unit output of heat capacity is incorrect.
2. Fluid-in-place values reported in the PRT file are in surface units for black oil. For the compositional model the
values are in reservoir units and the gas in place is in Mrcf (1000 Reservoir Cubic Feet) instead of Mrb (1000
Reservoir Barrel).
3. FloViz can fail while reading in FrontSim models that include .GRID and .INIT files if there are ACTNUM
keywords in the GRID section that inactivate cells. The work around is to use Petrel.
4. When the MULTX/MULTY/MULTZ/MULTX-/MULTY-/MULTZ- keywords are used in the SCHEDULE section,
FrontSim will handle these as explained in the FrontSim User Guide. However, FrontSim does not have the
functionality to output the modified transmissibilities and multipliers to the restart files. This means that the
user will not be able to verify directly that the keywords take effect as expected other than to inspect streamlines
and pressures.

Keyword reader
If the terminating slash is missing for a SCHEDULE keyword with multiple records, it could potentially lead to
unexpected behavior, for example, the subsequent keyword will not be parsed correctly.

Pressure solver
In some cases, the new version of the third party SAMG (Algebraic MultiGrid) linear solver in the 2014.1 release
fails to solve models with a small number of grid cells. In this case, the optional one level solver should be used
instead, which is enabled by FSSOLVE 1.

Restart
A FrontSim run cannot be restarted from an ECLIPSE tracer run.

Known issues
12
ECLIPSE Suite Release Notes

Saturation solver
The FrontSim three-phase saturation solver may behave incorrectly with the combination of three-point end-point
scaling, an RV (vaporized oil) variable table, and with gravity segregation switched on.

Well model
1. A well’s individual rate limit may not be honored when this well is switched to BHP control due to the inability
to meet a user-defined target.
2. FrontSim sometimes show spikes when the target is controlled at group control level.
3. FrontSim sometimes does not manage to maintain rate limits (limits violated) when a well is converted from
group rate control to individual BHP control.
4. The steady-state productivity/injectivity index value of the well that is supported by the WELPI keyword is
treated by FrontSim as a total (all phases) PI at reservoir conditions - not surface conditions as described in the
FrontSim User Guide. This is different from the behavior of ECLIPSE, which uses the PI for the phase
indicated by WELSPECS item 6 at surface conditions.
5. There can be minor differences in results for the same dataset between platforms (Linux or PC) as well as
between released versions. These can be due to different compiler versions and/or new enhancements. The
pattern flood management (PFM) algorithm can be particularly sensitive to minor differences in results for well
rates resulting in different allocations of injection rates.

Systems
Beta and official installations
1. If you have installed a beta version of ECLIPSE 2015.1 you must uninstall it before installing the official
release.
2. When upgrading ECLIPSE, that is, you have a previous version installed, please ensure that all programs in the
ECLIPSE suite are closed before starting the installation. This includes in particular the Simulation Launcher
program and the eclrun script. If they are open, they will not be upgraded and the old versions will persist. If
this does happen, uninstall the ECLIPSE upgrade version, ensure that all programs are closed, and then re-
install it.

General
1. If you are running this combination of software:
ECLRUN
the enginframe protocol
Red Hat 5 Update 4, or later,

you must create two links in the /lib64 directory as root:

cd /lib64
ln -s /lib64/libcrypto.so.6 libcrypto.so.4
ln -s /lib64/libssl.so.6 libssl.so.4

Note: Be very careful when creating these links as any linking errors can lead to major system errors.

2. Windows 7 is not supported. You must upgrade to Windows 7 SP1 before installing ECLIPSE 2015.1.

Known issues
13
ECLIPSE Suite Release Notes

3. If you are using Windows 7 SP1 or Windows 8.1 to run an ECLIPSE model from a directory that is shared, you
must have read and write access to that shared directory. This applies even if ECLIPSE is being run directly on
the machine sharing the directory.
4. On some systems the following error maybe seen when any of the pre- and post-processing applications are
started:
The program can't start because MSVCR100.dll is missing from your computer. Try
reinstalling the program to fix this problem.

To correct this issue, install the Microsoft runtime from the DVD. The installer is on the DVD in the
3rdparty\PC\resource\vcredist_vs10 and 3rdparty\PC\resource\vcredist_vs11 directories.

5. For a Windows HPC system, make sure that you install all of the runtimes on all of the compute nodes. This
includes all of the .NET and vcredist files. These can be found in the 3rdparty\PC\resource directory

Compatibility between parallel ECLIPSE, MPI and scheduling systems


There are a variety of different versions of MPI and scheduling systems available that may be used with ECLIPSE.
In some cases problems can be seen were the parallel ECLIPSE processes fail to start correctly, or fail to exit after
the processing is complete. Problems are most likely to be seen when old versions for LSF are in use with new
versions of the MPIs. Some additional settings can be made to help mitigate the problem, but the real solution is to
upgrade to LSF 9.1:

• For Platform MPI, set the environment variable MPI_REMSH to /usr/bin/ssh


• For Intel MPI, set the environment variable I_MPI_HYDRA_BOOTSTRAP to ssh.
• For LSF, switch off the HPC extensions by removing the environment variable ECL_LSFHPC if it exists.
For example, add the following lines to the users .cshrc file

setenv I_MPI_HYDRA_BOOTSTRAP ssh


setenv MPI_REMSH /usr/bin/ssh
setenv MPI_USELSF n

Also check that ECL_LSFHPC is not set by commenting out the setting if it is present.

Scheduler limitations
1. ECLIPSE supports several different job schedulers. Each has their limitations and requirements. Full
documentation on the scheduler integration can be found on the installation DVD in the 3rdparty directory.
However please note only Windows HPC, LSF and PBS support the scheduling of MR jobs. Running MR jobs
with UGE, or on a Windows workstation with no additional scheduling may not achieve the best utilization of
resources.
2. Only the LSF and PBS schedulers, when installed with the integration kits available on the DVD, are able to
handle all the permutations of job license requirements. The current implementations of Windows HPC and
UGE are currently unable to handle ‘or’ logic in license requests, so requests where several permutations are
possible will be simplified. For example some models could use (eclipse + compositional) or e300 in the
license request. In the case of UGE, the scheduling of e300 and models including a DATACHECK license may
queue based on licenses that are not required. Windows HPC has the same limitations. Both UGE and Windows
HPC cannot schedule MR jobs for ECLIPSE releases older than 2011.1.
3. Very basic Torque functionality is enabled in ECLRUN but it not supported and is not particularly effective.
For example, the scheduling of jobs based on licenses is not enabled. Torque 2.X or 5.X has been found to be
more stable than 4.X with ECLRUN.

Known issues
14
ECLIPSE Suite Release Notes

4. On some setups ECLRUN may have problems parsing the JOB ID when a submission has been made to UGE.
If this happens then the following modification to the eclrun script may help. Find the line:

return fullCmd, fullCmd, self.JobResponseScraper(result_pattern, 1)

and change it to:

return fullCmd, fullCmd, self.JobResponseScraper(result_pattern)

Licensing
1. Including license features for two different versions of the software (for example 2015 and 2012) in the same
license file on the same server may produce issues when running the software.
2. Some problems have been seen occasionally with the license utility programs on Linux. In particular lmstat
and lmreread may cause problems. If this causes a problem please use the flex 11.12 version of these
programs, or the options to the lmutil command.
3. Some issues may be seen when a license file is re-read (automatically just after midnight or manually). This
may cause some or all of the features to be dropped. This is a particular issue when the license file contains
feature names that contain a / or \.
4. Testing has shown that some security software can cause license problems. Some examples of applications
known to cause problems are McAfee HIP and Symantec End Point Protection. Generally ECLIPSE will be
able to check out a license, however the license may never be returned. Should this issue be experienced please
uninstall (not disable as this has been shown not to work) the relevant security software to see if the issue
disappears.
5. Licensing on a virtual machine is supported, but there are specific requirements, please see the Schlumberger
Licensing User Guide.
6. Problems may be found with licensing if a Linux machine has no eth0 network port. Either use a CodeMeter
dongle for licensing, or reconfigure Linux to use the eth0 not em1 naming for network ports. Linux support can
be found via your Linux distribution.
7. All license files on a license server must be locked to the same mechanism, for example a CodeMeter dongle or
a MAC address. Mixing CodeMeter and MAC address licenses, or using multiple dongles, can lead to poor
performance and stability issues.
8. ECLIPSE 2015.1 requires a license server that uses the slbsls daemon. If an old license server is in use it will
be necessary to upgrade the license server. The Windows license server can be installed from the main menu on
the DVD. The Linux license server is available under the tools subdirectory after installation. The new license
server is only available for Linux and Windows.

Linux
1. It is not currently possible to submit jobs from one architecture of Linux system to another. Jobs must be
submitted on the same type of system to that which they will run on. For example if your job is submitted from
a system based on x86_64 architecture it must run on an x86_64 based system.
2. There are issues with PBSPro and Intel MPI.
If you are running PBSPro as your scheduling system, you should set the environment variable
ECL_PBS_CORES_PERNODE to the number of cores per node (for a Nehalem/Westmere system this is eight and
for a Sandy Bridge system this is 16).

Set the variable in the .cshrc file if you are running c-shell or .bashrc if running the bash shell.

The default chunking of 1 may not work in all cases using Intel MPI, but Platform MPI works and this setting is
not required.

Known issues
15
ECLIPSE Suite Release Notes

3. Running Torque with Intel MPI is not supported. Please use Platform MPI instead.

10G (iWarp)
Because of performance issues, 10G (iWarp) interfaces are not recommended for parallel ECLIPSE on new Intel
Sandy Bridge (or later) servers. Use InfiniBand or Infinipath adapters instead.

Documentation
PDF
For individual files, you can adjust the displayed PDF bookmarks, and other document settings, for the ECLIPSE
Suite manuals using the standard Adobe Acrobat menu options. You can use Save As to retain the changes that you
make.

HTML
SIS recommends using the PDF manuals instead of HTML. To access them, use the ECLIPSE Simulation Software
Manuals bookshelf which you open directly from the Simulation Launcher.

Known issues
16

You might also like