Intersect

High-resolution reservoir simulator

Release notes
Version 2024.3
Intersect Release notes

Proprietary notice

Copyright © 2024 SLB, Chevron and TotalEnergies. All rights reserved.

This work contains the confidential and proprietary trade secrets of SLB and may not be copied or stored in
an information retrieval system, transferred, used, distributed, translated or retransmitted in any form or by
any means, electronic or mechanical, in whole or in part, without the express written permission of the
copyright owner.

Trademarks & service marks

SLB, Schlumberger, the SLB logotype, and other words or symbols used to identify the products and
services described herein are either trademarks, trade names or service marks of SLB 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 SLB. In addition, covers, page headers, custom
graphics, icons, and other design elements may be service marks, trademarks, and/or trade dress of SLB,
and may not be copied, imitated, or used, in whole or in part, without the express prior written permission of
SLB. Other company, product and service names are the properties of their respective owners.

Intersect ® is a mark of SLB. Intersect software is a joint product collaboration of Chevron, TotalEnergies
and SLB.

An asterisk (*) is used throughout this document to designate other marks of SLB.

Security notice

The software described herein is configured to operate with at least the minimum specifications set out by
SLB. 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 SLB representative.
Intersect Release notes

Table of Contents
1 Releases on physical media ...................................................................................... 1
2 What's new in 2024.3 .................................................................................................. 2
2.1 GPU simulation for Microsoft Windows systems ....................................................................... 2
2.2 Killough relative permeability hysteresis for oil wet systems .................................................. 2
2.3 Support for extended geological date range .............................................................................. 2
2.4 Constant pressure analytical gas and water aquifer models .................................................... 3
2.5 Improved computing of scaling factors for better convergence .............................................. 3
2.6 Reporting of RESQML property loading ...................................................................................... 3

3 What's new in 2024.2 .................................................................................................. 4

3.1 Intersect-Visage direct coupling for permeability and pore volume updating ........................ 4
3.2 Isothermal Spycher and Pruess solubility model and multicomponent solubility ................. 4
3.3 Component solubility in water initialization adjustment in enumeration workflows .............. 4
3.4 New viscosity mixing rule option: standard volume fraction weighted power-law ................ 5
3.5 Solid mobility multiplier calculation methods ............................................................................ 5
3.6 Property set for CO2 storage ........................................................................................................ 5
3.7 New reports for critical minerals workflows ............................................................................... 6
3.8 Summary and 3D reports for adsorbed component mass ........................................................ 6
3.9 Support for threshold pressure modeling in Multiscale sequential fully implicit ................... 6
3.10 New summary vectors for material balance error reporting ..................................................... 6
3.11 Initial pressure and phase saturations for reporting and expressions .................................... 7
3.12 Retirement of RedHat 7 and CentOS 7 as supported platforms ............................................... 7
3.13 Retirement of Platform MPI ........................................................................................................... 7

i
Intersect Release notes

4 What's new in 2024.1 .................................................................................................. 8

4.1 Embedded discrete fracture modeling ........................................................................................ 8
4.2 CO2Store template for CO2 storage simulation setup ............................................................... 8
4.3 Spycher and Pruess solubility model in isothermal component solubility in water
(CSIW) cases .................................................................................................................................. 9
4.4 Composition-based tabular adsorption ....................................................................................... 9
4.5 Extension of logarithmic viscosity mixing rule to aqueous phase ........................................... 9
4.6 Tabular steam and water properties ............................................................................................ 9
4.7 Component names reporting for summary and 3D-related properties .................................... 9
4.8 Component names when defining an aqueous phase composition versus depth ............... 10
4.9 Improvements to the transport solver in Multiscale SFI .......................................................... 10
4.10 Full-GPU support for analytical aquifers ................................................................................... 10
4.11 Full-GPU support for Carlson relative permeability hysteresis .............................................. 10
4.12 GPU support for numerical aquifer reporting ........................................................................... 10
4.13 Single command to reset tuning parameters to default .......................................................... 10
4.14 Minimum stable rate calculation ................................................................................................ 10
4.15 Pressure drop adjustment and scaling factor for network branches in Eclipse
Network Simulator ....................................................................................................................... 11
4.16 New well and connection reporting properties ......................................................................... 11
4.17 Support for NVIDIA® H100 GPUs ............................................................................................... 11
4.18 Addition of Open MPI support .................................................................................................... 12
4.19 Linux platform retirement and installation folder name .......................................................... 12
4.20 Platform MPI retirement .............................................................................................................. 12

5 Behavioral changes .................................................................................................. 13

5.1 2024.3 ............................................................................................................................................ 13
Changes in simulation ................................................................................................................ 13
Changes in well model ............................................................................................................... 13
Changes in field management ................................................................................................... 14
Changes in reporting .................................................................................................................. 14
5.2 2024.2 ............................................................................................................................................ 14
Changes in simulation ................................................................................................................ 14
Changes in field management ................................................................................................... 14
Changes in reporting .................................................................................................................. 15
5.3 2024.1 ............................................................................................................................................ 15
Changes in simulation ................................................................................................................ 15
Changes in multiscale extension ................................................................................................ 15

6 Licensing and installation ........................................................................................ 16

7 Platform availability .................................................................................................. 18

ii
Intersect Release notes

8 Feature compatibility and known issues ................................................................ 19

8.1 Licensing error code -5008 ......................................................................................................... 19
8.2 Aquifer modeling ......................................................................................................................... 19
8.3 Equilibration ................................................................................................................................. 19
8.4 Fluid modeling ............................................................................................................................. 20
8.5 Gridding and parallel simulation ................................................................................................ 20
8.6 Grid independent wells ............................................................................................................... 20
8.7 Grid property editing ................................................................................................................... 20
8.8 Migrator ........................................................................................................................................ 21
8.9 Petrel to Intersect workflow ........................................................................................................ 21
8.10 Reporting ...................................................................................................................................... 21
8.11 Rock physics ................................................................................................................................ 22
8.12 Solution of the equations ............................................................................................................ 22
8.13 Well modeling .............................................................................................................................. 23
8.14 Well optimizers ............................................................................................................................ 23
8.15 Third party software and hardware ............................................................................................ 23
8.16 Documentation ............................................................................................................................. 24
8.17 Macros .......................................................................................................................................... 24
8.18 Installer ......................................................................................................................................... 24

iii
Intersect Release notes

iv
Intersect Release notes

1
Releases on physical media
Intersect releases on physical media are now a ‘pull’ release instead of a ‘push’ release. If you require a physical copy,
ask your local D&I License Administrator to place an order through InTouch by creating a ticket assigned to the Helpdesk
SW — Distribution and Ordering. Additionally, physical media are only available for a single version of a major release
cycle (typically the *.1 release).

Releases on physical media

1
Intersect Release notes

2
What's new in 2024.3
2.1 GPU simulation for Microsoft Windows systems
Intersect can now run on GPU on computers that use Windows operating systems. This functionality supports NVIDIA
GPUs that use Turing or Ampere architectures. On a Windows GPU, runs typically perform well compared with runs on
CPU hardware. It is expected that this functionality will significantly improve simulation throughput for an engineer
working on a single computer specified for Petrel RE workflows.

Note: Desktop environments do not benefit from workload management software and might use the same GPU to
display graphics. This can result in inconsistent performance, or Intersect running out of GPU memory if the GPU is used
for multiple simultaneous simulations or for graphics-intensive applications.
For further information on setting up your computer for best usage of the functionality, as well as details of supported
systems, see the Intersect installation and deployment guide.

2.2 Killough relative permeability hysteresis for oil wet

systems
Relative permeability hysteresis effects following the Killough model are now available in oil wet rocks. This feature
complements the default "water wet" hysteresis model assumptions, where these different types of wettability can be
combined in a single reservoir. The "oil wet" Killough hysteresis replicates the corresponding algorithm in Eclipse, with
the migration to Intersect of the relevant keywords now possible.
For more information, refer to the Killough relative permeability hysteresis in oil wet systems chapter in the Intersect
technical description.

2.3 Support for extended geological date range

Intersect can now handle simulations that exceed the year 9999, with the capability to run with elapsed simulation time
up to 92,000,000,000 (9.2e10) days, which is approximately 252 million years. This can be utilized in geothermal and
CO2 storage workflows where geological time scale predictions may be necessary.

What's new in 2024.3 | Support for extended geological date range

2
Intersect Release notes

2.4 Constant pressure analytical gas and water aquifer

models
The range of analytical aquifer models has been extended to include constant pressure gas and water aquifers, including
brine. These are supported in black oil and compositional simulations, and can be used to efficiently model large bodies
of gas or water under the assumption of constant pressure (such as a section open to atmospheric conditions).
For more information, refer to the Constant Pressure Aquifers section of the Intersect technical description.

2.5 Improved computing of scaling factors for better

convergence
A new method for computing scale factors when the primary variables hit their upper and lower bounds has been added.
Global scale factors are no longer affected by limiting the primary variable within their range, enabling the simulation to
converge faster. Enabling this feature can improve the performance of thermal CCS models.
For more information, refer to the AlternativeBoundsScaling field description in the Intersect user guide.

2.6 Reporting of RESQML property loading

A new table has been added to the PRT file while parsing RESQML files (.epc) that contains information about the
properties found in the file, their associated grid, and attachment kind (cells, edges, and so on). It is enabled by setting
the VerbosityLevel field to 2 or higher in the GridMgr node.

Note: In the case of dual porosity and dual permeability models, the table also includes the porosity type for each
property (matrix or fracture).

What's new in 2024.3 | Reporting of RESQML property loading

3
Intersect Release notes

3
What's new in 2024.2
3.1 Intersect-Visage direct coupling for permeability and
pore volume updating
A new direct coupling workflow for Intersect-Visage is introduced in this release. It supports permeability and pore
volume updates using gRPC, a modern communication protocol, to achieve performance efficiency and stability in
coupled simulations. The workflow is fully supported in Petrel and you can launch simulations both on-prem and in the
Delfi digital platform either from Petrel or using configuration files in the same way as other coupled Intersect simulations.
For more information, refer to the new Visage coupling user guide.

3.2 Isothermal Spycher and Pruess solubility model and

multicomponent solubility
The isothermal Spycher and Pruess CO2 solubility model is now compatible with multicomponent solubility defined in
both K-value and solution gas-water ratio table formats for other components. The Spycher and Pruess model takes
priority over tabular solubility data if provided for CO2.

3.3 Component solubility in water initialization adjustment

in enumeration workflows
The ThreePhaseComponentAdjustment field has been added to the PostInitializationFlash node for use in
enumerated cases. It adjusts the composition of water in isothermal cases where hydrocarbon components such as CO2
are soluble in water. It only affects cells where there is an aqueous phase and at least one hydrocarbon phase present. It
adjusts the concentration of the water-soluble hydrocarbon components in the aqueous phase so that the aqueous
phase is in thermodynamic equilibrium with the hydrocarbon phases.

What's new in 2024.2 | Component solubility in water initialization adjustment in enumeration workflows
4
Intersect Release notes

3.4 New viscosity mixing rule option: standard volume

fraction weighted power-law
To assist in matching experimental data for fluid mixtures viscosities such as bitumen and light hydrocarbons, a new
viscosity mixing rule in thermal simulations is now available under the ViscosityMixingRule node. To calculate
the weighting factors based on component volume fractions at standard conditions, set the new PowerMixingWeighting
field to STANDARD_VOLUME_FRACTION,
For more information, refer to the Viscosity section under Fluid model in the Thermal simulation chapter of the Intersect
technical description.

3.5 Solid mobility multiplier calculation methods

You can now choose between the harmonic average calculation and the upstream weighted calculation (default) for the
solid mobility multiplier for use in the flux calculation. This is selected in the new CalculationMethod field under the
SolidMobilityMultiplier node. The harmonic average calculation method is particularly relevant for injection
studies with significant levels of salt precipitation.

3.6 Property set for CO2 storage

A new property set named CO2STORE has been added to the XYPlotSummaryReport and
Recurrent3DReport nodes. CO2STORE includes commonly requested field, well, and 3D properties in CO2
storage cases. The component-based properties are only reported for components that are soluble in water.
The properties included in CO2STORE property set are:

Property Field property Well property Recurrent 3D property

IMMOBILE_VAPOR_COMPONENT_MASS x x
MOBILE_VAPOR_COMPONENT_MASS x x
AQUEOUS_COMPONENT_MASS x x
GAS_INJECTION_CUML x x
GAS_INJECTION_RATE x x
GAS_IN_PLACE x
GAS_MASS_INJECTION_CUML x x
GAS_MASS_INJECTION_RATE x x
PRESSURE x x
PRESSURE_PORE_VOLUME_WEIGHTED x
WATER_IN_PLACE x
RES_VOLUME_INJECTION_CUML x x
RES_VOLUME_INJECTION_RATE x x
BOTTOM_HOLE_PRESSURE x
TOTAL_MOLAR_RATE x
AQUEOUS_COMPONENT_MOLE_FRACTION x
GAS_SATURATION x
WATER_SATURATION x
SOLUTION_GAS_WATER_RATIO x

What's new in 2024.2 | Property set for CO2 storage

5
Intersect Release notes

Property Field property Well property Recurrent 3D property

TEMPERATURE x
WATER_RESERVOIR_DENSITY x
WATER_VISCOSITY x
GAS_RESERVOIR_DENSITY x
GAS_VISCOSITY x

3.7 New reports for critical minerals workflows

Six new summary vectors related to component mass have been created to support workflows where tracking specific
brines is of importance, such as with the recovery of critical minerals. The vectors are available at field, group, and well
level:
• COMPONENT_MASS_PRODUCTION_RATE
• COMPONENT_MASS_INJECTION_RATE
• COMPONENT_MASS_PRODUCTION_CUML
• COMPONENT_MASS_INJECTION_CUML
• WATER_PRODUCTION_COMPONENT_MASS_CONC
• WATER_INJECTION_COMPONENT_MASS_CONC

3.8 Summary and 3D reports for adsorbed component

mass
Reporting of the adsorbed mass of a specific hydrocarbon component can now be requested using the
ADSORBED_COMPONENT_MASS property as a 3D property (under Recurrent3DReport) and a summary vector
(under GridCellProperties).

3.9 Support for threshold pressure modeling in Multiscale

sequential fully implicit
Threshold pressure modeling is now supported in the Multiscale sequential fully implicit (SFI) formulation. The option
enables you to specify a threshold for the pressure difference between areas in the reservoir, which is useful for
modeling scenarios such as imposing initial hydraulic equilibrium between communicating independent regions.

3.10 New summary vectors for material balance error

reporting
New field-level summary vectors to track material balance error have been added to the XYPlotSummaryReport
node. You can use MATERIAL_BALANCE_ERROR to report material balance error normalized by total moles and
MATERIAL_BALANCE_ERROR_COMPONENT_NORM to report material balance error normalized by component
moles. The latter is suitable for problems where the ratio of moles per component of interest to the total moles in place is
very small, such as when foreign components are injected into a reservoir.

What's new in 2024.2 | New summary vectors for material balance error reporting
6
Intersect Release notes

Note that to control the method used in convergence checks and its threshold value, you must refer to the
ComponentResidualNormalization field and the MaxReservoirComponentResidual field, respectively, in addition to the
reporting described here.

3.11 Initial pressure and phase saturations for reporting and

expressions
The initial state of the reservoir (pressure and phase saturations) can now be reported as recurrent properties and stored
for use in expressions. This enables you to create custom calculations that refer to those initial properties, for example
the pressure difference at a report step in relation to its initial value.
A new field called StoredInitialProperties under the ReportMgr node specifies which initial properties to store and use
during the simulation.

3.12 Retirement of RedHat 7 and CentOS 7 as supported

platforms
The Linux platforms Red Hat Enterprise Linux Server 7 and CentOS Linux Server 7 are end of life and Intersect 2024.1
was the last release to support these platforms. Support for these platforms has been removed from Intersect 2024.2,
leaving Red Hat Enterprise Linux Server 8 update 4 (x86_64) as the supported platform.

3.13 Retirement of Platform MPI

IBM discontinued support for Platform MPI in 2020. Intersect 2024.1 was the last release to support this MPI option.
Support for Platform MPI has been removed from Intersect 2024.2, leaving Intel MPI and Open MPI as the supported
platforms.

What's new in 2024.2 | Retirement of Platform MPI

7
Intersect Release notes

4
What's new in 2024.1
4.1 Embedded discrete fracture modeling
Intersect is now capable of simulating fractured reservoirs through embedded discrete fracture modeling (EDFM). This
functionality is currently available as a Petrel-Intersect integrated workflow and supports both natural and hydraulic
fractures.
Input fracture and matrix grids are defined in Petrel, which exports the fracture definitions as RESQML files in addition to
IXF nodes that control all aspects of the EDFM simulation. At runtime, Intersect generates the EDFM grid and embeds it
into the existing matrix grid, establishing matrix-fracture and fracture-fracture connections according to the discretization
method selected and creating the necessary fracture-well connections. Several options are available to tune the
discretization process to reach optimal performance.
You can use the EDFM functionality in combination with a variety of Intersect features, such as LGRs, grid independent
wells, GPU, and restarts, and both black oil and compositional fluid models. You can define new regions and region
mappings for the generated EDFM cells and selectively activate EDFM cells after the simulation has started.
The discretized EDFM grid with its geometry and static and dynamic properties are available for visualization in Petrel.
For more information, refer to the Embedded discrete fracture modeling (EDFM) chapter in the Intersect technical
description.

4.2 CO2Store template for CO2 storage simulation setup

The CO2Store template is a new reservoir node that enables the compact setup of an isothermal CO2 storage
simulation. Based on the selected components, the template internally expands to a compositional fluid model node
named CO2Store that includes tuned equation of state parameters, component solubility in water, brine, and aqueous
phase property models.
The generated CO2Store node can be reported in both the PRT file and a separate IXF file by setting the
VerbosityLevel field of the CO2Store node and can be modified.
For more information, refer to the CO2Store template chapter in the Intersect technical description and the CO2Store
node description in the Intersect user guide.

What's new in 2024.1 | CO2Store template for CO2 storage simulation setup
8
Intersect Release notes

4.3 Spycher and Pruess solubility model in isothermal

component solubility in water (CSIW) cases
You can now use the Spycher and Pruess model for CO2 solubility in the aqueous phase in isothermal simulations.
When the SpycherPruessSolubility node is entered for an isothermal CSIW case, CO2 solubility tables are
internally created for the model’s valid range of pressure, temperature, and salinity by default and are then used in the
simulation. Alternatively, you can specify lists of temperatures and salinities for which these internal tables are created.
For more information, refer to Implementation for isothermal simulations in the Spycher and Pruess solubility model
chapter of the Intersect technical description and the IsothermalCalculationMethod field of the
SpycherPruessSolubility node in the Intersect user guide.

4.4 Composition-based tabular adsorption

There is a new option that enables you to model adsorption as a function of composition using tables. You can specify
the option independently for each phase and specify a fraction of the pore volume to be inaccessible for adsorption. This
feature can be useful when modeling phenomena such as the adsorption of a water-based surfactant. For more
information, refer to the AdsorptionMoleFractionTable node in the Intersect user guide.

4.5 Extension of logarithmic viscosity mixing rule to

aqueous phase
A third option is now available for modeling compositional aqueous phase viscosity in thermal simulations. This model
uses a logarithmic mixing rule and includes aqueous soluble hydrocarbon, brine, and water components. You can use
this option to achieve a better match to experimental data in mixtures of components with heterogeneous viscosities,
such as bitumen and solvent.

4.6 Tabular steam and water properties

The new INTERSECT_TABULAR option enables you to use water and steam properties based on the International
Association for the Properties of Water and Steam, Industrial Formulation 1997 (IAPWS97) formulation in a tabular
format. The properties are calculated for different pressures and temperatures and their values are saved in 2D tables
internally. Bi-linear interpolation is used for table look-up. This option is valid for pressures up to 1000 bar and
temperatures from 273.15 K to 1073.15 K.
For more information, refer to the Water and steam properties section of the Intersect technical description and the
FluidMgr node description in the Intersect user guide.

4.7 Component names reporting for summary and 3D-

related properties
The file format for summary data and 3D data has been extended so that you can specify explicit names that correspond
to suffixes appended to property names. Intersect can now output these component names for all compositional
properties in summary, initial 3D, and recurrent 3D data.
For example, if requesting AQUEOUS_COMPONENT_MOLE_FRACTION in
XYPlotSummaryReport.FieldProperties outputs the properties FAMF_1, FAMF_2, and FAMF_3, these
property names are supplemented with the corresponding component names, for example 'CO2', 'Water', or 'NaCl'. Post-
processors can use this information to better label component-specific plots and 3D results.

What's new in 2024.1 | Component names reporting for summary and 3D-related properties
9
Intersect Release notes

For more information, refer to Summary Files and Restart Files in the File Formats Reference Manual.

4.8 Component names when defining an aqueous phase

composition versus depth
While defining an aqueous phase composition versus depth, it is now possible to control the order of the components for
which the mole fraction values are provided. This is enabled by the new optional ComponentName field under the
CompositionDepthTable node. You can only use this field when the CompositionType field is set to AQUEOUS.

4.9 Improvements to the transport solver in Multiscale SFI

New heuristics have been applied to the transport solver in Multiscale SFI to speed up convergence. In tested cases, an
average of 30% speed-up was observed, without changes to results. This new method is now the default, but you can
restore the old behavior through the option switch pre_2024.1_multiscale_settings.

4.10 Full-GPU support for analytical aquifers

Available analytical aquifer types (Carter-Tracy, Fetkovich, and constant flux) are now supported for full-GPU simulation
and should see the benefits of hardware acceleration.

4.11 Full-GPU support for Carlson relative permeability

hysteresis
The Carlson relative permeability hysteresis model is now supported for full-GPU simulation and should see the benefits
of hardware acceleration.

4.12 GPU support for numerical aquifer reporting

Numerical aquifer reporting such as summary vectors reporting rates and cumulative fluxes are now supported in GPU
simulation.

4.13 Single command to reset tuning parameters to default

Excessive tuning of simulation cases can have a negative impact on overall quality. The new reset_tuning_nodes
command under the TimeStepSolution node resets all tuning parameters to default to provide a 'clean state' for
datasets where heavy tuning was previously applied. Combining AutomaticTuning with reasonable convergence criteria
might improve the performance of these models.

4.14 Minimum stable rate calculation

The minimum stable rate (MSR) calculation feature enables better control of the minimum flow rate at which a well can
operate under stable conditions to ensure optimal well performance and efficiency, as well as to avoid premature closure
of wells during allocation.
The MSR calculations for different phases can be triggered either by specification of the minimum stable rate property
IDs in the XYPlotSummaryReport node or through their usage in expressions. A debug mode is available to provide

What's new in 2024.1 | Minimum stable rate calculation

10
Intersect Release notes

a more detailed view of the MSR calculation process. This calculation can be further used to control the allocated
minimum rate as part of the guide rate balance action to be above the dynamically calculated minimum stable rate
through expressions in the set_minimum_rate() command.
For more information on using the MSR feature and the relevant property IDs, refer to Minimum stable rate in the
Intersect technical description.

4.15 Pressure drop adjustment and scaling factor for

network branches in Eclipse Network Simulator
The pressure drop and scaling factor features available in Intersect to allow pressure adjustment in wellbores has been
extended to Eclipse Network Simulator for network branches. This supports the use of a reduced set of VFP tables to
represent multiple network branches by adjusting the pressure drop or the scaling factor from a table for a particular
branch. The Field Management logic supports this new functionality under the NetworkPipe node.
For more information, refer to the Intersect user guide and the BRANPROP section in the Eclipse Network Simulator
user guide.

4.16 New well and connection reporting properties

Several volume flow rate and cumulative reporting summary vectors are now available that cover combinations of
different levels (well, well-to-cell connections), phases (gas, oil, water), and conditions (surface, reservoir). They are
listed below:
• For wells (through the WellProperties reporting node):
• Phase surface volume flow cumulatives
• GAS_FLOW_CUML (WGFT)
• OIL_FLOW_CUML (WOFT)
• WATER_FLOW_CUML (WWFT)
• For well-to-cell connections (through the WellToCellConnectionProperties reporting node):
• Phase reservoir volume flow rates
• GAS_RES_VOLUME_FLOW_RATE (CGVFR)
• OIL_RES_VOLUME_FLOW_RATE (COVFR)
• WATER_RES_VOLUME_FLOW_RATE (CWVFR)
• Phase reservoir volume flow cumulatives
• GAS_RES_VOLUME_FLOW_CUML (CGVFT)
• OIL_RES_VOLUME_FLOW_CUML (COVFT)
• WATER_RES_VOLUME_FLOW_CUML (CWVFT)

4.17 Support for NVIDIA® H100 GPUs

Intersect now supports the NVIDIA H100 series of GPUs, which are more powerful than the NVIDIA A100 series.
Comparisons of models running on the NVIDIA A100 and the NVIDIA H100 cards, both in their PCIe 80 GB varieties,
showed that H100 runs ranged from 15 to 50% faster.
Please note that performance improvement will be strongly dependent on the model being run.

What's new in 2024.1 | Support for NVIDIA® H100 GPUs

11
Intersect Release notes

4.18 Addition of Open MPI support

Intersect now supports using Open MPI on Linux. Specifically, version 4.1.6 has been tested and is supported. This is in
addition to the existing Intel MPI support on Linux. The Installation and deployment guide describes how to download
and install the Open MPI runtime files.

4.19 Linux platform retirement and installation folder name

The Linux platforms Red Hat Enterprise Linux Server 7 and CentOS Linux Server 7 are approaching end of life and
Intersect 2024.1 is the last release to support these platforms. It is planned that support for these platforms will be
removed from Intersect 2024.2, leaving Red Hat Enterprise Linux Server 8 update 4 (x86_64) as the supported platform.
The Linux installation folder name has changed from ix/rh6_x86_64_* to ix/linux_x86_64_*. You must
update any scripts that refer to the old folder name accordingly.

4.20 Platform MPI retirement

IBM discontinued support for Platform MPI in 2020. Intersect 2024.1 is the last release to support this MPI option. It is
planned that support for Platform MPI will be removed from Intersect 2024.2, leaving Intel MPI and Open MPI as the
supported platforms.

What's new in 2024.1 | Platform MPI retirement

12
Intersect Release notes

5
Behavioral changes
5.1 2024.3

Changes in simulation
Default steam tables for isothermal models
• On isothermal models with component solubility in water enabled, the Ezrokhi model to determine density and
viscosity of the water phase now calculates pure water properties using INTERSECT_TABULAR steam tables. To
restore the previous behavior, specify set_int_option(name="pre_2024.3_Ezrokhi_steamtable"
value=1) in the OptionMgr node.
Capillary pressure hysteresis
• Prior to 2024.3, application of the mixed wettability capillary pressure hysteresis method with horizontal end point
scaling enabled, could produce incorrect results. It happened because of the incomplete scaling of some quantities in
the hysteresis method application. The consistency is now corrected. To restore the previous behavior, specify
set_int_option(name="pre_2024.3_mixwet_pc_hysteresis" value=1) in the OptionMgr
node.
Component properties
• On compositional fluid models, reservoir components can no longer be named H2O, WAT, or WATER using the
ComponentProperties field ComponentName node. These names are reserved for the water component. You must
provide an alternative name to avoid the validation error and enable the simulation as in previous versions.
Improved default steam tables for thermal simulations with component solubility in water
• Prior to 2024.3, in thermal models the default model for calculating thermal properties with Component Solubility in
Water (CSIW) was INTERSECT. Starting from 2024.3, the default is INTERSECT_TABULAR. The previous behavior
can be recovered by setting the ThermalProperties field to INTERSECT on the FluidMgr node.

Note: Setting the ThermalProperties field to INTERSECT on the FluidMgr node will not affect a model using the
Spycher and Pruess solubility model. In such a case, the default model will stay as the default
INTERSECT_TABULAR.

Changes in well model

Generalized Pseudo Pressure

Behavioral changes | 2024.3 | Changes in well model

13
Intersect Release notes

• Prior to 2024.3, relative permeabilities at well producing connections were recomputed without consideration of
hysteresis effects. This is consistent with the documentation for the RockModelName field of the
WellSaturationFunctions node (i.e., drainage only). For GPP workflows this behavior has now been
changed, such that grid and connection relative permeabilities are consistent. Blocking factors in presence of
hysteresis are now computed correctly. To restore the previous behavior, specify
set_int_option(name="pre_2024.3_gpp" value=1) in the OptionMgr node.

Changes in field management

Uptime fraction in historical data control
• Prior to 2024.3, when a HistoricalDataControl was deactivated, any well that was under that control had its
uptime fraction reset to 1. This meant that a user specified uptime fraction set at the same time of the control
deactivation was effectively ignored. Now such user specified uptime fractions are honored. To restore the previous
behavior, specify set_int_option(name="pre_2024.3_hdc_uptime_reset" value=1) in the
OptionMgr node.

Changes in reporting
Rate reporting on crossflowing auto-closed completions
• Prior to 2024.3, if a completion was automatically closed, but still cross-flowing, its flows were reported as zero if
queried directly via Field Management (that is, as ListProperties items or as direct get_property
commands on Completion entities in scripts). Now the correct cross-flowing values are reported. To restore the
previous behavior, specify set_int_option(name="pre_2024.3_auto_closed" value=1) in the
OptionMgr node.

5.2 2024.2

Changes in simulation
Gravity Drainage
• Prior to 2024.2, values of DUAL_POROSITY_MATRIX_HEIGHT_GRAVITY_DRAINAGE could be taken from the
fracture grid instead of the matrix grid. Since DUAL_POROSITY_MATRIX_HEIGHT_GRAVITY_DRAINAGE is a
matrix-only property its values in the fracture grid were zero instead of the correct matrix value, unless
UseMatrixAsFractureDefault was set. To restore the previous behavior, specify
set_int_option(name="pre_2024.2_gravity_drainage" value=1) in the OptionMgr node.

Changes in field management

ConfigureNetworkPipeAction
• Prior to 2024.2, using a ConfigureNetworkPipeAction on CLOSED NetworkPipe flow entities had no
effect. To restore the previous behavior, specify
set_int_option(name="pre_2024.2_closed_pipe_actions" value=1) in the OptionMgr
node.
Query of cumulative on abandoned well
• Prior to 2024.2, query of any cumulative volume/amount using commands get_property()/
get_properties() would return zero. Now it returns the last cumulative value at the point of well abandonment.
This is consistent with what is observed in summary reports. Use
set_int_option(name="pre_2024.2_abandoned_well_cuml_rpt" value=1) in the
OptionMgr node to return to the original behavior.

Behavioral changes | 2024.2 | Changes in field management

14
Intersect Release notes

Moved cell properties

• The CELL_DIMENSION_I, CELL_DIMENSION_J, and CELL_HEIGHT properties have been moved from the
get_property command of the RegionMgr node and the RegionProperty field of the ActionMgr node (where
they were inappropriately available) to the equivalent grid cell locations. If you used them in the old locations, this will
be ignored and the run will proceed.

Changes in reporting
Adsorption reporting in the PRT file
In previous releases of Intersect, volumes of adsorbed and total gas and oil, and free gas were reported in the PRT
regardless of which phase the adsorption was from. Now, these volumes are reported only if the adsorption is from the
gas or oil phase.

5.3 2024.1

Changes in simulation
Paired surface fluid model with tabular K-values
• Prior to 2024.1, the K-values defined in a paired surface fluid model were ignored if the K-values were defined in
tabular format KValueTables. This is fixed in the 2024.1 version of Intersect. To restore the previous (incorrect)
behavior, specify set_int_option(name="pre_2024.1_surface_kvalue" value=1) in the
OptionMgr node.
Isothermal component solubility in water (CSIW) models robustness improvements
• Several enhancements have been made to improve the robustness of isothermal models with gas components
dissolved in the aqueous phase, including better handling of phase state changes and fixes to logic issues in the
flash. To restore the previous behavior, specify
set_int_option(name="pre_2024.1_csiw_isothermal" value=1) in the OptionMgr node.

Changes in multiscale extension

Transport solver convergence
• New heuristics have been applied to the transport solver in Multiscale SFI to speed up convergence. This new
method is now the default. To restore the old behavior, specify
set_int_option(name="pre_2024.1_multiscale_settings" value=1) in the OptionMgr
node.

Behavioral changes | 2024.1 | Changes in multiscale extension

15
Intersect Release notes

6
Licensing and installation
The simulator checks at run time for valid licenses. This release requires date based versioned licenses.
When using the Schlumberger License Server, please note that it must be v2020 or later. Licenses that may be required
are:

Product name License feature Functionality

Intersect Core ix_base Core Intersect runtime license enabling simulation. The core license also
Simulator includes the ix_fm and ix_tools features.
ix_fm Enables Intersect Field Management.
ix_tools Enables the generation of Intersect input models from Eclipse keywords or
from the Petrel Reservoir Engineering user interface.
Intersect Enabler sim_ul Simulation upgrade license – required in conjunction with eclipse license
for Eclipse when using the “-–use-sim-ul=yes” ECLRUN command line option. The
Simulator license also includes ix_fm and ix_tools.
Eclipse (E100/ eclipse Eclipse runtime license enabling simulation – required instead of ix_base
E300) when using the “–-use-sim-ul=yes” ECLRUN command line option.
Intersect Coupler ix_coupler Enables the coupling of Intersect Field Management to multiple reservoirs
and network simulators such as GAP. For an integrated project with N1
Intersect reservoir models and N2 surface network models, the number of
ix_coupler licenses required is (N1+N2–1). Coupling to SLB applications is
excluded from this calculation.
This license also enables coupling of Intersect to an external 3rd party
controller.
Intersect Multiple ix_mr Enables Intersect to simultaneously run multiple similar realizations of the
Realization same model for a lower license cost.
ix_mr licensed models are produced by Petrel, which signs them to prevent
further modification of the model.
For each running model sharing the same unique identifier one ix_mr license
is required, but all models will share a single ix_fm, ix_base, thermal and/ or
ix_coupler license. ix_cluster_parallel and ix_ucparallel licenses are not
shared across the models.
Combined sim_thermal Simulator license enabling Thermal simulations, alternative to ix_hot.
Simulator Thermal Activated by using the “–-use-sim-ulopt” ECLRUN command line option.

Licensing and installation

16
Intersect Release notes

Product name License feature Functionality

Combined sim_compositional Simulator license enabling Compositional fluid simulations, alternative to
Simulator ix_compositional. Activated by using the “–-use-sim-ulopt” ECLRUN
Compositional command line option.
Intersect Thermal ix_hot Intersect license enabling Thermal simulations – alternative to sim_thermal
license.
Intersect ix_compositional Intersect license enabling Compositional fluid simulations – alternative to
Compositional sim_compositional license.
Intersect Cluster ix_cluster_parallel Enables Intersect parallel computing option. An ix_cluster_parallel license is
Parallel required for any model running more ways parallel than the limit of 48. This
number is calculated by multiplying the number of processes by the number
of threads per process in hybrid parallel runs.
Intersect Unlimited ix_ucparallel Enables Intersect unlimited parallel computing option. An ix_ucparallel
Cluster Parallel license is required for any model running more ways parallel than the limit of
128. This number is calculated by multiplying the number of processes by the
number of threads per process in hybrid parallel runs.
Intersect Multiscale ix_multiscale Enables Intersect Multiscale Sequential Fully Implicit (SFI) method.

Licensing and installation

17
Intersect Release notes

7
Platform availability
This release of the Intersect simulator is supported on the following platforms.
• Windows 10 (x64) with Intel MPI.
• Windows 11 with Intel MPI.
• Windows Server 2019 HPC Pack.
• Red Hat Enterprise Linux Server 8 update 4 (x86_64) with Intel MPI or Open MPI.

Platform availability
18
Intersect Release notes

8
Feature compatibility and
known issues
The Intersect and Eclipse feature compatibility section in the Intersect Migrator User Guide provides information that may
be useful when comparing the results of Intersect with those from other simulators. The list of supported Eclipse
keywords is provided in the Intersect Migrator User Guide.

8.1 Licensing error code -5008

You might experience an issue when running Intersect if the SLB Licensing environment variable uses a mixture of local
and remote license servers and the local server is defined without a port number.
When local and remote license servers are combined in the incorrect format, it will often result in a "-5008" error which
indicates that the system has detected an invalid license file path. This occurs when a path is not in the expected format
port@host or there is an inappropriate use of comma (,) characters in the license file path.
To resolve this issue, make sure that there is always a port number before each host name. For example, if @localhost
is present, change it to 27000@localhost or similar.

8.2 Aquifer modeling

• Modeling of tracers with aquifers is not available.

8.3 Equilibration
• When comparing Intersect simulation results with those from other simulators, you must compare the initial fluid in
place calculated by the simulator with the reference simulator, before the dynamic simulation is started. If there are
differences, then candidates for investigation include rock compaction, end-point scaling, capillary pressures, initial
fluid compositions, pressures, and temperatures.
• Critical fluid initialization is not currently supported when the COMPVD keyword is present. The COMPVD keyword is,
however, supported for bubble-point and dew-point fluid initialization. For critical fluid initialization, the PSAT property
is reported as zero.
• More detailed information on the Intersect initialization and equilibration may be output from the simulator, by
increasing the verbosity level of the Equilibrium Manager. Refer to the EquilibriumMgr node in the Intersect
User Guide for more information.

Feature compatibility and known issues | Equilibration

19
Intersect Release notes

• Some differences with Eclipse may be observed in the initialization of models using the brine option. This is because
the underlying formulation in Intersect is based on mole fraction rather than concentration variables, and a nonlinear
conversion is required from the input concentration values.

8.4 Fluid modeling

• Some of the algorithms for calculating thermal properties differ from those used in Eclipse Thermal. To obtain a
closer match in results, set the ThermalProperties field on the FluidMgr node to "ECLIPSE" or
"ECLIPSE_IAPWS97". For more information, refer to Thermal simulation in the Intersect Technical Description.
• The second order term of the fluid enthalpy equations is different between Intersect and Eclipse. It affects the
simulation results only if the coefficients are nonzero.
• The reduced phase formulation cannot currently be used with the variable API black oil fluid model. A validation error
will occur if you try to use these features together.
• Use of Langmuir isotherms with dual porosity systems is currently not supported.

8.5 Gridding and parallel simulation

• Unlike Eclipse, the Intersect simulator has no restrictions on forming a 1D or 2D Cartesian partitioning of the grid into
domains to be simulated by separate processor in a parallel simulation. By default, the simulator treats all grids as
unstructured and, therefore, its parallel partitioning algorithm is completely automatic. The parallel partitions can be
viewed in a 3D viewer by selecting the grid property 'PART'. The partitioning may be complicated with unstructured
grids, or grids with (possibly nested) local grid refinements.
• Traditional Cartesian partitioning is not recommended, but you can enable it by first specifying the structure of the
grid and then the IJK cuts. For more information, refer to the StructuredInfo and CartesianPartition
nodes in the Intersect User Guide.

8.6 Grid independent wells

• Grid independent wells cannot be connected to cells that have been coarsened. If grid independent wells and
coarsening are defined, Intersect issues a warning. It is responsibility of the user to prevent a grid independent well
to intersect a coarsened region of the grid.
• Grid independent wells can be defined only for Pillar grids. Intersect issues an error if grid independent wells are
defined for a different type of grid.
• The grid independent wells workflow can deal with cells with non-planar faces, but for efficiency it assumes the cells
are convex. This could lead to a slightly inaccurate connection calculation if a well crosses a non-convex area of the
cell. In this case, a refinement of the well deviation will overcome this issue.
• The grid independent wells workflow doesn't currently support multisegment wells.

8.7 Grid property editing

• Now grid property editing is possible even when geometry has not been supplied to Intersect. There are limitations to
what can be edited depending on workflow. For example, this option is not yet compatible with the use of MPFA.
Refer to Grid property editing in the Intersect Technical Description.
• There is a known issue in parallel when TRANSMISSIBILITY_I, TRANSMISSIBILITY_J or
TRANSMISSIBILITY_K edits are applied to LGR host cells when those host cells are in the halo of a parallel
partition region.

Feature compatibility and known issues | Grid property editing

20
Intersect Release notes

8.8 Migrator
• The --process-grid-edits option that disables the grid transmissibility calculation within Intersect is now
deprecated, and will be withdrawn in a future release.
• The old --eclipse-init command line option is incompatible with the default grid edits migration workflow.
Therefore, setting this option implies the --process-grid-edits option. This is now deprecated, and will be
withdrawn in a future release.
• In thermal cases with the old Migrator workflow (now the --process-grid-edits option), the use of keyword
MULTIPLY with TRANX, TRANY or TRANZ is currently not allowed. An error is issued in such cases.
• The FREQ mnemonic in the RPTRST keyword when specified in the SCHEDULE section generates 3D visualization
files (*.FXXX) in Intersect at different timesteps from Eclipse.
• CONLENST and CONLENEN values in the RFT files are incorrect for the Migrator workflow.
• For the WELSPECS and WELSPECL keywords, if the Pressure table number is defaulted, then the
WellBoreFluidModel is no longer explicitly set in the resulting WellDef node, and the default fluid model is used.
• MULTX/Y/Z- support is the same as Eclipse (i.e. support for MULTX etc. in EDIT section only in E100 style decks,
MULTPV is supported for both styles).

8.9 Petrel to Intersect workflow

• Intersect models, created using Field Management, write the Intersect IXF files directly, rather than using the Eclipse
Migrator. By using Intersect grid edits, this results in greatly improved export performance for large models.
• If the reservoir simulation grid has LGRs created in a GSG file and also in the IXF file, the combined LGRs for this
case cannot be visualized when imported back into Petrel.
• In a Petrel workflow, the generated WellToCellConnections nodes do not define the TrueVerticalDepth field.
In this case, Intersect takes the Z coordinate of the center of the connected cell as the true vertical depth of the
center of the connection.
Grid independent wells always accurately calculate the true vertical depth of the center of the connections. This
could lead to differences in results if a Petrel exported well is replaced by a grid independent well with the same
deviation and completions defined in terms of start and stop measured depth.
• If a grid independent well is added to a native Petrel case, the Y coordinates of the well deviation must be flipped (in
other words, the sign must be changed). This is due to the difference in coordinate systems used by Petrel and
Intersect.
When a well trajectory file is exported by Petrel, the Y coordinate is automatically flipped to account for this
difference. If grid independent wells are added to a Petrel case externally, it is the responsibility of the user to flip the
Y coordinate of the deviation.

8.10 Reporting
• Intersect uses a different method than Eclipse for calculating inter-region phase flows for reporting purposes. It takes
the molar rates for all components and feeds them to the configured separator for the fluid in place report. This may
give different results from Eclipse.
• For consistency with pressure reporting, Intersect calculates well TEMPERATURE as the (pore volume weighted)
average of connected cell temperatures on all wells (regardless of whether they are injector or producer, open or
shut). This differs from Eclipse 300 which generally reports WTEMP as
• flowing bottom hole temperature for flowing wells,
• average reservoir temperature for non-flowing producers,

Feature compatibility and known issues | Reporting

21
Intersect Release notes

• injected fluid temperature for non-flowing injectors.

Note that Intersect also reports BOTTOM_HOLE_TEMPERATURE for flowing wells.

8.11 Rock physics

• Intersect supports both the Killough and Carlson relative permeability hysteresis methods, but not that of Jargon,
which is available in Eclipse 300.
• To increase simulator stability, a validation check has been added to ensure that critical and maximum saturations
for each cell in the simulation grid are separated by at least 1E-06.
• A validation check ensures that saturation endpoints are defined in the correct order:
S(connate) < S(critical) < S(maximum)
This validation may not be present in other simulators. In addition, the simulator checks that the relative permeability
at maximum saturation is higher than the critical saturation value.
• The definition and calculation method for a capillary number may differ from other simulators, depending on the
feature in which it is used. For models other than the Whitson gas condensate capillary number dependent relative
permeability model, Intersect does not scale the capillary number by porosity, saturation, or immiscible relative
permeability.
• The precise way in which endpoint scaling is implemented in Intersect may differ from other simulators. For example,
Eclipse uses a special treatment of each of the intervals between the connate, critical, associated critical and
maximum saturations, which is not implemented in Intersect.
• If the scanning curves in Killough relative permeability hysteresis become too steep, Intersect has a new option to
look up the primary drainage curve. Enable this option by setting
SteepScanningCurveAsPrimaryDrainage = TRUE on the RelPermHysteresis node. This may
improve performance for some models with steep saturation curves.
• The use of nonvolatile residual oil saturation with the near critical relative permeability mixing feature can result in
nonzero mobility of the oil which can lead to convergence problems. This can be mitigated in some cases by
disabling the near critical relative permeability mixing feature.

8.12 Solution of the equations

Intersect has the ability to simulate in a variety of implicitness formulations: fully implicit, IMPSAT, IMPES and two
adaptive implicit (AIM) schemes: AIM_IMPES and AIM_IMPSAT.
• The non-fully implicit time-discretization formulations (IMPES and IMPSAT) typically suffer from small timesteps and
low simulator performance. Their adaptive implicit counterparts AIM_IMPES and AIM_IMPSAT are recommended
instead.
• In adaptive implicit (AIM) simulations, especially in parallel, the timestep size may be severely restricted by the
maximum fraction of implicit cells (refer to the AimCriteria node in the Intersect User Guide). In this case, it is
recommended to increase the maximum fraction of implicit cells from the default 10% up to a maximum of 50%.
• The IMPSAT formulation should only be used in a compositional simulation where there are more than two
hydrocarbon components. In two-component compositional or black oil simulations, the specification of IMPSAT
results in a warning and the conversion of the simulation to IMPES mode.
• In some cases, the timestep size may be limited by the time truncation error (TTE). Intersect and Eclipse use
different formulae to evaluate the TTE. If the timestep size is being severely restricted by the TTE it is recommended
that the value of this limit be increased from the default (0.1). For more details, refer to the
TimeStepSizingControls node in the Intersect User Guide.

Feature compatibility and known issues | Solution of the equations

22
Intersect Release notes

8.13 Well modeling

• When the simulator cannot find a valid flowing solution for a well (for example, if the reservoir pressure is below the
minimum BHP limit for a producer), it shuts the well along with all its connections, regardless of the setting item 9 in
the WELSPECS keyword. This differs from Eclipse, which performs a surface shut-in under these circumstances if
item 9 in the WELSPECS keyword is set to STOP.
• The solution of heaters in Intersect is different to the approach used in Eclipse. Internally, a heater with multiple cells
attached to it is treated as a whole rather than the method used by Eclipse that solves each cell individually. This is
an improvement on the Eclipse method, however it is computationally more difficult and currently suffers from known
convergence issues. If you encounter convergence issues, the workaround is to split the heater into individual cells,
which yields closer results to Eclipse.
• When using the variable API facility, the convergence behavior of the simulation may be improved by banning
crossflow in wells.
• Intersect reports the actual steam quality (WSQU) at the bottomhole depth in the well while Eclipse Thermal reports
the user-defined value. The actual steam quality is slightly different depending, for example, on well pressure and
crossflow.
• The calculation of voidage rate is performed by transforming the wellstream fluid to the average conditions over the
field or a specified region. In black oil simulations, this calculation differs between Eclipse 300 and Eclipse 100. In
Eclipse 300, the fluid properties are calculated at the average hydrocarbon pressure in the field or region. However,
in Eclipse 100 the solution gas-oil ratio (Rs) of the oil phase is also capped to not exceed the average Rs of the field
or region. The calculation in Intersect by default, follows the Eclipse 300 method, and may therefore give different
voidage rates than Eclipse 100 when the oil in the field or region is significantly undersaturated and the wellstream
gas-oil ratio is significantly higher than the average field or region Rs. Compatibility with the Eclipse 100 method can
be improved by setting the LimitByAverageRsRv field in the ResVolConditions node.
• The drift flux flow model in multisegment wells is not supported in thermal simulations.
• In runs using the hysteresis option, hysteresis does not apply in rock models that are specific to well-to-cell
connections. If a well-to-cell connection has a specific rock model assigned to it (see the field RockModelName in the
WellSaturationFunctions node), the saturation table defined in the DrainageSaturationFunction field in the
RockModelDefinition for this rock model is used for both drainage and imbibition processes.

Note: The COMPIMB feature in Eclipse has not yet been implemented in Intersect, so at present it is not possible to
provide an imbibition table for use in rock models specific to well-to-cell connections.

8.14 Well optimizers

• Only Field Management groups constraints for the same fluid phase as the optimizer target fluid phase will be
honored. A warning message is given where group constraints are incompatible with the well optimizer
• The streamline optimizer only supports deferral and control of water breakthrough.

8.15 Third party software and hardware

• Simulation Launcher requires .NET Framework 4.5 or later to function.
• If you are running serially without using the queuing system on the Microsoft HPC platform, you need to disable the
AffinityOnWindows configuration option. Refer to the ECLRUN User Guide for instructions.
• You may encounter problems running Intersect with Platform MPI using a version of LSF earlier than 9.1. When this
occurs, the simulation finishes as usual, however LSF behaves as if the simulation is still running and prevents other
jobs from starting. You can either run the Intel MPI version of Intersect (the default version), or upgrade LSF. You
must use LSF 9.1 or later.

Feature compatibility and known issues | Third party software and hardware
23
Intersect Release notes

• When running on certain OS and NAS storage hardware configurations, Intersect can experience intermittent file
system errors when attempting to clean very large directories of previous summary result data. Intersect displays a
warning message when this occurs and attempts to retry cleaning the directories. If it cannot clean out the files, the
following error message is displayed.

WARNING Filesystem error attempting to write summary report files. Retrying now.
Actual error is: boost::filesystem::basic_directory_iterator increment: Too many
levels of symbolic links: "file location"
ERROR Grid "" has already been written.

The workaround is to manually clean out the summary report files from previous runs before launching the
simulation.
• Intersect supports several different job schedulers. Each has its limitations and requirements. Full documentation on
Scheduler Integration can be found on the DVD in the 3rdParty directory.

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.

However, please note that

• On some machine setups, ECLRUN may have problems parsing the JOB ID when a submission has been made to
UGE. If this happens, the following modification to the ECLRUN script may help.
a. Find the line: return fullCmd, fullCmd, self.JobResponseScraper(result_pattern,
1)
b. Change it to: return fullCmd, fullCmd, self.JobResponseScraper(result_pattern)
• Very basic Torque functionality is enabled in ECLRUN but it is 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.
• If the disk system containing the simulation model is remote to the simulation processor(s), and therefore has a
limited transfer bandwidth, you may experience reduced simulation performance. This may be a result of simulation
database logging. This logging can be disabled by using the command-line option --no_msgdb=true.

8.16 Documentation
In some rare circumstances it has been observed that the Intersect manuals do not appear by default in the Manuals
section of the Simulation Launcher after installation. If this occurs, you can add it by following the steps below:
1. On the Tools menu, click New.
2. Select New Program, and then add the Intersect manuals.

8.17 Macros
If you encountered issues when removing the macros folder, when installing versions of Intersect prior to 2024.3, run a
repair on the macros folder. Use one of the following methods to do this:
• Right-click the installer and click Repair.
• Under Programs and Features, right-click the installed simulator and then click Repair.

8.18 Installer
• Uninstalling the release also removes the Simulation Launcher, even if other versions of the simulators are installed.

Feature compatibility and known issues | Installer

24
Intersect Release notes

• If you are installing to a network mapped drive, then you must run the install as an Administrator, or the installer does
not recognize the drive.

Feature compatibility and known issues | Installer

25