Intersect

High-resolution reservoir simulator

Installation and deployment guide

Version 2024.3
Intersect Installation and deployment guide

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 Installation and deployment guide

Table of Contents
1 Introduction ................................................................................................................. 1
1.1 Platform availability ....................................................................................................................... 1
1.2 Supported platforms for licensing ............................................................................................... 1
1.3 Prepare to install Intersect ............................................................................................................ 2
1.4 DVD organization ........................................................................................................................... 2

2 Install Intersect on Windows ..................................................................................... 3

2.1 Install Intersect .............................................................................................................................. 3
2.2 Install Intel MPI ............................................................................................................................... 4
2.3 Configure GPU for simulation ...................................................................................................... 4
2.4 Test the Intersect installation ....................................................................................................... 5
Test Intersect using the Simulation Launcher .............................................................................. 5
Test Intersect from the command line .......................................................................................... 6
2.5 Installed directory structure ......................................................................................................... 6
2.6 Troubleshoot the Windows installation ....................................................................................... 7

3 Install Intersect on Linux ............................................................................................ 8

3.1 Install Intersect .............................................................................................................................. 8
3.2 Configure MPI for Linux ................................................................................................................ 9
SSH configuration ...................................................................................................................... 10
Use LSF queuing ....................................................................................................................... 11
Intel MPI settings ........................................................................................................................ 12
Open MPI settings ...................................................................................................................... 13
3.3 Install OFED drivers .................................................................................................................... 13
3.4 Install CUDA ................................................................................................................................. 14
3.5 SLB licensing ............................................................................................................................... 15
3.6 Test the Intersect installation ..................................................................................................... 15

i
Intersect Installation and deployment guide

ii
Intersect Installation and deployment guide

1
Introduction
1.1 Platform availability
Platform Operating system Required software Notes
Windows Windows 10 Professional or Microsoft .NET 4.5 or later Minimum screen resolution for PC
Enterprise x64 systems is 1024x768
Intel MPI 2018.1 or later (2018.1 and
Windows 11 Professional or 2021.11 are included but requires 32 bit is not supported
Enterprise installation)
Linux Red Hat Enterprise Linux Intel MPI 2018.1 or later (2018.1 and A scheduling system is
Server 8 Update 4 (x86_64) 2021.11 are included and recommended. LSF 9.1.3 or later
or later minor update automatically installed) supported, with LSF 10.1 or later
recommended and required for
Open MPI 4.1.x (runtime distribution is
GPU scheduling
not included, can be downloaded from
NVIDIA)
Windows Windows Server 2019 HPC Intel MPI not required
Cluster Pack

Intersect is supported only on x64 Intel-compatible processor hardware that supports the AVX instruction set (introduced
with Intel Sandy Bridge processors in 2011). Use with processors that support additional instructions, e.g. AVX2
(introduced with Intel Haswell processors in 2013) is recommended.
On Linux platforms, Intersect GPU options require an NVIDIA GPU device built on the Volta, Ampere or Hopper
architectures. The Intersect GPU option currently targets the high performance V100, A100 and H100 GPU devices.
On Windows platforms, Intersect GPU options require an NVIDIA GPU device built on the Turing or Ampere
architectures. These devices include the NVIDIA RTX A2000, RTX A3000, RTX A4000, RTX A5000 and RTX A6000.

1.2 Supported platforms for licensing

Windows
• The supported platforms are: Windows 10 64-bit, Windows 11, and Windows Server 2019 HPC Pack.

Introduction | Supported platforms for licensing | Windows

1
Intersect Installation and deployment guide

Linux
• The supported platform for Linux is Red Hat Enterprise Linux Server 8 Update 4 x86_64.

1.3 Prepare to install Intersect

Intersect can be installed independently of any previous major or incremental release of Eclipse or Intersect. It can also
be installed over existing installations.
1. If you have an existing Eclipse installation you should always ensure that the macros directory is backed up before
proceeding with the software installation.

Note: To use Intersect, it is essential that the macros included with this release are installed over any older versions.

2. If Eclipse is already installed, Intersect must be installed to the same directory as Eclipse.
For all applications, the manuals are available in PDF (Portable Document Format) that can be browsed and printed with
PDF readers.

Note: These instructions assume that the software is installed on a default path /ecl on Linux and C:\ecl on
Windows.

The steps required to install Intersect are:

1. Install the Intersect software.
2. Install a license (if required).
3. Install Intel MPI on Windows, or Configure the MPI on Linux.
4. Test the installation of Intersect works correctly.

Install Eclipse and Intersect

Intersect includes components from Eclipse. We recommend that you install older versions in numeric order. You should
install Intersect last if Eclipse and Intersect have the same version number.

1.4 DVD organization

Intersect software is distributed on a single DVD.

DVD 1
DVD 1 contains software for Windows and Linux. This includes:
• Intersect installation with documentation, data and examples.
• Utility resources for Windows and Linux.

Introduction | DVD organization | DVD 1

2
Intersect Installation and deployment guide

2
Install Intersect on Windows
Before installing Intersect, check that the following prerequisites are met:
• You have administrator privileges to install Intersect.
• The install directory path contains no spaces in the path name, not for example in C:\Program Files\ecl.
• We recommend you disable your virus checker temporarily during the installation process.

Note: Intersect manuals, in PDF format, are installed by default. From the launcher, click the manuals button and a
bookshelf displays.

Note: It is assumed throughout this section, that the installation location is C:\ecl.

If required you can download Acrobat Reader from http://get.adobe.com/reader/.

The recommended version is Adobe Reader XI. Alternatively, use a different PDF reader of your choice.

Note: If you have installed a previous version of Intersect 2024.3 you can upgrade it by installing this version of Intersect
2024.3. Uninstalling Intersect will remove the installation, including any simulator generated output files. Files shared with
other SLB product installations will not be removed.

2.1 Install Intersect

1. Insert the DVD in the DVD drive (or run setup if you have downloaded it).
The SLB installation panel should appear; if not use Windows Explorer to access the DVD and run setup.exe.
2. Click Install Products.
3. Click Intersect to install Intersect.
4. When the Intersect installation wizard opens, follow the instructions and click Next on each window to proceed.
5. By default, Intersect is installed to C:\ecl. To change the installation location, click the icon with three dots to the
right of the location text box, and then select a folder.

Note: If you already have Eclipse installed, you must install Intersect into the same location.

6. Then click Install, and when the installation is complete, click Finish.

Install Intersect on Windows | Install Intersect

3
Intersect Installation and deployment guide

Note: We do not support installation directories with a space in the name; for example: Program Files.

The IX Connector is installed locally under C:\ecl\20xx.x\IX\Connector (where x represents the product
version). If Petrel is installed, you can choose this connector via File - Options - Install IX connector.
If required, install the Schlumberger Licensing Tool by following the instructions in the Schlumberger Licensing User
Guide.

2.2 Install Intel MPI

Note: After installing Intersect, you need to install Intel MPI even if parallel simulations are not required.

To install Intel MPI:

1. From the SLB Installation panel, select Intel MPI. Then select Intel MPI 2021.11 or Intel MPI 2018.1. The newer
version is recommended, though you can use the older version for legacy compatibility. With the new 2021 version,
we have tested the following set of environment variables:
• export I_MPI_FABRICS=shm:ofi
• export I_MPI_COLL_EXTERNAL=0
• export I_MPI_CBWR=1
• export I_MPI_OFI_PROVIDER=mlx

Note: If you are using v2021.11 or later, the Intel installer program no longer sets the ONEAPI_ROOT environment
variable to the installed location of the Intel MPI directory. This variable is needed by the Schlumberger Simulation
Runtime (ECLRUN) program. This variable is now set automatically when you install Intel MPI from the Install Menu
dialog box.

2. In the Location to Extract Files window, click Extract to use the default location. (Intersect may not work if you
change this location.)
3. When the installation wizard opens, follow the instructions to proceed.

2.3 Configure GPU for simulation

If you intend to run Intersect on an NVIDIA GPU on a Windows system, you must configure the GPU to not use system
memory as a backup.

Note: If you do not plan to use an NVIDIA GPU for simulation, you can ignore this section.

If a GPU run falls back to system memory it will perform poorly. To avoid this, make the following changes to your system
configuration:
1. Open the NVIDIA Control Panel.
2. Browse to the Manage 3D Settings pane.
3. In the Global Settings tab, in the Settings section, find the CUDA -- Sysmem Fallback Policy setting.

Note: If this setting is present, your GPU driver is compatible with this process. If the setting is not present, upgrade
to the latest driver for your GPU.

Install Intersect on Windows | Configure GPU for simulation

4
Intersect Installation and deployment guide

4. In the Manage 3D Settings pane, on the Program Settings tab, in the Select a program to customize section, find the
ix.exe executable.

Note: You might need to use the Add button and then select the executable from the file system, where it will be
located under the installation directory. The default location is: C:\ecl\2024.3\ix\x64_msmpi\ix.exe.
The area you chose to install Intersect to, the version of Intersect, and the preferred MPI implementation (msmpi or
ilmpi) will affect which executable you select.

5. In the Preferred graphics processor list, select High-performance NVIDIA processor for this program.
6. In the Specify the settings for this program list, for CUDA -- Sysmem Fallback Policy select Prefer No
Sysmem Fallback.
This prevents the GPU from using system memory to supplement GPU memory.

2.4 Test the Intersect installation

The Intersect installation can be tested either by using the Simulation Launcher or using the command line.

Test Intersect using the Simulation Launcher

To start the Simulation Launcher either double-click the desktop icon (if you selected previously to create a desktop
shortcut) or click Start and then select Program Files, Schlumberger, Intersect and Simulation Launcher.
A screen similar to that shown below should appear.

A sample dataset is provided with the Intersect installation, located at ..\IX\Examples\Example_2\IX.DATA.

To open the dataset:
1. Select Migrator in the Intersect group.
2. Click Add Dataset, and select the IX.DATA file, and then click Run.
3. Select Intersect in the Intersect group.

Install Intersect on Windows | Test the Intersect installation | Test Intersect using the Simulation Launcher
5
Intersect Installation and deployment guide

4. Click Add Dataset, select the IX.afi file, and then click Run.
Alternatively, if you already have an AFI file skip the first two steps and go directly to running Intersect.
If you already have an Eclipse dataset that you wish to simulate in Intersect, use the Migrator option in the same manner
to convert the dataset to AFI format.

Note: We recommend that you test the installation with one of the example datasets before running your own models.

The simulation should run and end as shown in the example below.

Test Intersect from the command line

The Migrator can convert an Eclipse keyword file into an AFI file, which can then be read by Intersect.
1. Use the following ECLRUN command line: eclrun ecl2ix basename, where basename is the root name of
the input dataset. This command just generates the AFI file but does not run or simulate it.
2. To run or perform the actual simulation using the AFI file the following command is used: eclrun ix basename.
Intersect will read the AFI file and perform the simulation.
If the input Eclipse dataset is altered, the AFI file must be regenerated from the dataset first before being given to
Intersect to be simulated.
An AFI consists of {basename}.afi, and its associated files; basename_ECL2IX.gsg, basename_ECL2IX_IX.ixf,
basename_ECL2IX_FM.ixf, basename_fm_edits.ixf and basename_reservoir_edits.ixf.
For information on using ECLRUN, refer to the ECLRUN User Guide provided as a separate part of the Intersect install.
For information on using the Migrator, refer to the Migrator User Guide provided as a separate part of the Intersect install.

2.5 Installed directory structure

At the top level, the following directories are visible. Other directories may exist depending on whether other SLB
applications are installed.
C:\ecl\2024.3
C:\ecl\macros
C:\ecl\tools

Install Intersect on Windows | Installed directory structure

6
Intersect Installation and deployment guide

2.6 Troubleshoot the Windows installation

Windows HPC
Installing Intersect for Windows HPC is the same as installing Eclipse. For further information see the Eclipse
Installation Guide. Contact SLB Support for further help.

Note: Intel MPI is not required if Windows HPC is in use. Do not install it on the HPC cluster.

Install Intersect on Windows | Troubleshoot the Windows installation

7
Intersect Installation and deployment guide

3
Install Intersect on Linux
Before installing Intersect, check that the following prerequisites are met:
• You have root privileges to install the Intersect software.
• All the hosts have the same User and Address mappings, such as from NIS.
• Intel MPI is installed. This is automatic but you need to configure it before running Intersect.
• The file system you choose for installing Intersect is accessible from all nodes, for example an NFS share. The file
system server must not be used for running simulations.
• If you use LSF, you must install LSF 9.1 or later on all the nodes.

Note: It is assumed throughout this section, that the installation location is /ecl.

3.1 Install Intersect

1. Mount the DVD and change the directory to the mounted path.
2. Change to the UNIX/install directory and run the cdinst.csh script.

Options for linux_x86_64 20xx.x

1) INTERSECT
2) Tools
Select A - Install all of the above
N - Install none of these
S - Select a subset
Please enter choice:

3. Enter A to install all programs.

4. At the location prompt, enter the path to install the software, if different to the default path. This path should be
available in the same place on all the machines in the cluster.

Note: If Eclipse is already installed, you must install Intersect in the same location.

5. At the next prompt, enter Y to install the macros.

Note: To use Intersect it is essential that the macros included with this release are installed over any older versions.

Install Intersect on Linux | Install Intersect

8
Intersect Installation and deployment guide

Available programs for linux_x86_64 20xx.x

1) INTERSECT
2) Tools
Select A - Install all of the above
N - Install none of these
S - Select a subset
Please enter choice: a

Enter proposed location for installation (default /ecl):

Installing INTERSECT (size ********* bytes)

Installing Tools (size *******)

Do you want to install the macros [default n]? y

Installing macros (size ****** bytes)

6. Set up the environment so that users can access the software:

a. If the user's shell is TCSH or CSH, edit the .cshrc file in the user’s home directory. If it does not exist, create it.
This file may contain many lines, however it should set the path to include the macros directory (which can be
done by running the @eclrunsetup.csh script in the macros directory). If you have installed to a different
path, you must replace /ecl with your chosen directory. You must log off and log on, or run "source
~/.cshrc" for these changes to take effect. An example is shown below:

setenv SLBSLS_LICENSE_FILE port@license_server

setenv ECLPATH /ecl
source /ecl/macros/@eclrunsetup.csh

b. If the user's shell is BASH, edit the .bash_profile file in the user’s home directory to include the following
lines (you must log off and log on for these changes to take effect):

export SLBSLS_LICENSE_FILE=port@license_server
export ECLPATH=/ecl
. /ecl/macros/@eclrunsetup.sh

3.2 Configure MPI for Linux

The Intel and Open MPI is automatically installed with Intersect. The Intel and Open MPI uses SSH to set up the
communication between nodes, so make sure that passwordless SSH is set up between any computers used to run
Intersect.

Warning: If other applications rely on SSH to work, talk to your system administrator to check the following procedure
will not cause any problems with other applications.

The objective of the steps below is to make sure that public and private keys exist for users and that the
authorized_keys file exists and has the correct keys. However, what you need to do depends on the current setup.

Hint: It is usually a good idea to set the SSH configuration to automatically accept connections to new machines. If this
step is not completed, then you have to log on to every machine in the cluster before you can guarantee that a MPI job
will work correctly.

1. Check if everything is already working, by trying to connect to another machine in the cluster. For example,
connecting from comp001 to comp002 using SSH should not require a password

Install Intersect on Linux | Configure MPI for Linux

9
Intersect Installation and deployment guide

comp001:/home/smessenger>ssh comp002
Last login: Thu Apr 9 10:37:03 2015 from comp001.geoquest
comp002:/home/smessenger>

2. If you can successfully connect to another machine in the cluster, skip to SSH configuration (p.10).
3. Evaluate your current setup. Figure 3.1 describes how to set up SSH.

Figure 3.1. SSH Setup

SSH configuration
1. First check that SSH is set up to accept connections to new machines, as shown above.
2. Create a file called config in the users .ssh directory, or add the following line if the config file already exists.

comp002:/home/smessenger>cd .ssh
comp002:/home/smessenger/.ssh>cat config
StrictHostKeyChecking=no

3. Set permissions.
• Set permissions for the config file to 400 to ensure that users have read permission.
• Set permissions for the authorized_keys to 600.
• Set permissions for $HOME and $HOME/.ssh to a minimum of 755. This makes sure that other users cannot
write to those directories.

Install Intersect on Linux | Configure MPI for Linux | SSH configuration

10
Intersect Installation and deployment guide

Use LSF queuing

If you are using LSF, you need to edit the LSF startup file /etc/init.d/lsf to add an entry for ulimit so that
MPI can run when under LSF control. To do this, open the file and add the entry for ulimit as shown here:

#!/bin/sh
# $Id: startup.svr4,v 1.10 2015/04/08 06:13:09 xltang Exp $
#
# Start and stop LSF daemons, System V / OSF version
# Make sure we're running a shell that understands functions
#
# The following is for the Linux chkconfig utlility
# chkconfig: 35 99 01
# description: Load Sharing Facility
#
# The following is for the Linux insserv utility
### BEGIN INIT INFO
# Provides: lsf
# Required-Start: $remote_fs
# Required-Stop: $remote_fs
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Description: Start LSF daemons
### END INIT INFO

#line added so INTERSECT can run over Infiniband when under LSF control.
ulimit -l 1024000000

if test "$SH5" != "/bin/sh5" -a -r /bin/sh5

then
SH5=/bin/sh5
export SH5
exec /bin/sh5 "$0" "$@"
fi
check_env () {
if [ x$LSF_ENVDIR = x ]; then
# Using default path of lsf.conf...
LSF_CONF=/lsftop/lsf/conf/lsf.conf

Note: By default, LSF saves temporary files in a hidden directory called .lsbatch which is inside the user’s home
directory. This can cause problems if the home directories do not have much free space, or quotas are enabled. Avoid
this issue by adding the following setting in lsf.conf:
LSB_STDOUT_DIRECT=Y
You must restart LSF for this change to take effect.

We no longer recommend LSF HPC. However if you wish to use LSF and the Intel MPI, you may need to edit the Intel
MPI location in the intelmpi_wrapper script. The following assumes that Intersect has been installed in /ecl, and
LSF has been installed in /lsf. If you have installed it elsewhere, you must use the appropriate path.
1. In the LSF directory (/lsf in this example), edit the file
/lsf/9.1/linux2.6-glibc2.3-x86_64/bin/intelmpi_wrapper
2. Search for the line MPI_TOPDIR="........"
3. Replace the line with the correct location of the Intel MPI. If the default settings have been used, this line should look
like
MPI_TOPDIR="/ecl/tools/linux_x86_64/intel/mpi/5.0.2/"
4. Find all occurrences of "$MPI_TOPDIR/bin" and replace with "$MPI_TOPDIR/bin64"

Install Intersect on Linux | Configure MPI for Linux | Use LSF queuing
11
Intersect Installation and deployment guide

5. If you wish to use SSH to start the MPI daemons:

a. Search for the line
MPDBOOT_CMD="$MPI_TOPDIR/bin64/mpdboot"
b. And change to
MPDBOOT_CMD="$MPI_TOPDIR/bin64/mpdboot -r /usr/bin/ssh"

Intel MPI settings

The Intel MPI should detect and use the correct interface. If not, setting an environment variable as below will force a
protocol to be chosen:

Device type Description Setting

Shared Memory Shared-memory transport (used for intra-node communication only). shm
DAPL DAPL-capable network fabrics, such as InfiniBand*, iWarp*, Dolphin*, and dapl
XPMEM* (through DAPL*).
Std Ethernet TCP/IP-capable network fabrics, such as Ethernet and InfiniBand* tcp
(through IPoIB*).
InfiniPath TMI-capable network fabrics including Intel True Scale Fabric, Myrinet* tmi
(through Tag Matching Interface)
OpenFabrics OpenFabrics Interfaces* (OFI)-capable network fabrics, such as Intel True ofi
Interfaces Scale Fabric, Intel Omni-Path Architecture, InfiniBand*, and Ethernet
Preferred setting for
(through OFI API).
v2021+.
OFED OFA-capable network fabric including InfiniBand* (through OFED* verbs) ofa
Preferred setting for
v2018.

* Trademarks.
• For v2021+, set the I_MPI_FABRICS environment variable as follows:

export I_MPI_FABRICS=shm:ofi

This sets Intel MPI to try the chosen devices in order.

It is also recommended to set these other variables:

export I_MPI_COLL_EXTERNAL=0

export I_MPI_CBWR=1

export I_MPI_OFI_PROVIDER=mlx

Note: DAPL, TMI, and OFA fabrics are deprecated for Intel MPI v2021+.

• For v2018, set the I_MPI_FABRICS_LIST environment variable as follows:

export I_MPI_FABRICS_LIST=ofa,tcp

This sets Intel MPI to try the chosen devices in order.

• I_MPI_FALLBACK and I_MPI_DEVICE are no longer required and should be removed if set.

Install Intersect on Linux | Configure MPI for Linux | Intel MPI settings
12
Intersect Installation and deployment guide

• To print out the connection or interface type used, set the following environment variable:

export I_MPI_DEBUG=2

• When multiple MPI versions are installed, ECLRUN will use the most recent compatible version by default. To
override this behavior and disable ECLRUN version detection, set the I_MPI_ROOT environment variable and
PATH to the install location of the desired MPI version. To do this, run the Intel bash shell script:

source setvars.sh

This will set the environment variable(s) and PATH appropriately.

Open MPI settings

You must configure Open MPI before use. The NVIDIA* HPC-X* distribution is recommended.
You can download HPC-X here. On the Download tab at the bottom of the page, select the appropriate version, and OS
distro, version and architecture. There are two types of driver available. The "Inbox" drivers have the most generic code,
while "MLNX_OFED" drivers are optimized for use with Mellanox (InfiniBand*) hardware.
After download of HPC-X, unpack the TGZ file to a destination directory. You must modify the Linux environment to
make sure that the Open MPI binaries can be found. The HPC-X README.TXT file describes the steps to take. Using
the bash shell, set the HPCX_HOME variable to the destination directory, source the hpcx-init.sh script, and then
run hpcx_load to configure the environment.

$ bash
$ export HPCX_HOME="unpack_directory"
$ source $HPCX_HOME/hpcx-init.sh
$ hpcx_load

You can run Intersect with Open MPI using ECLRUN by setting the --comm parameter.

eclrun --comm openmpi --np 2 ix example.afi

* Trademarks

3.3 Install OFED drivers

A version of the Open Fabrics Enterprise Distribution (OFED) drivers is part of the Red Hat installation. It may, however,
be necessary to upgrade these drivers using the instructions found on the Open Fabrics website http://
www.openfabrics.com.
The latest OFED version at the time of release is available on the DVD in the 3rdparty/linux/resources/
OFED directory.

Note: If you use InfiniPath, download the drivers and instructions from http://www.qlogic.com.

General InfiniBand notes

To use InfiniBand cards, you must assign an IP address to the card. This also allows you to "ping" the other computers
using the InfiniBand interface. If the ping succeeds then you know all the hardware is physically connected properly.
Follow the install instructions from the InfiniBand supplier. However, the following additional steps may be necessary. A
good indication is when IP over InfiniBand is working properly, but Intersect is not.

Install Intersect on Linux | Install OFED drivers | General InfiniBand notes

13
Intersect Installation and deployment guide

1. Edit the file /etc/security/limits.conf.

2. Add the following two lines:

* soft memlock 102400000000

* hard memlock 102400000000

The value represents the number of kilobytes that may be locked by a process. The limits.conf file contains further
documentation.

3.4 Install CUDA

Note: Intersect GPU options require an NVIDIA GPU device and the latest CUDA drivers.

The Intersect GPU option does not require the CUDA runtime, but to avoid possible compatibility issues it is
recommended that the installed NVIDIA drivers for the GPU device are up to date. In particular please note that drivers
prior to release 450 are not supported. Driver versions up to release 525 have been tested, but it cannot be guaranteed
that the most recent versions will always be compatible in the future. You can find some useful installation instructions at
docs.nvidia.com/cuda/cuda-installation-guide-linux and developer.nvidia.com/cuda-downloads. The following steps are
based on these resources and apply to a basic Red Hat Enterprise Linux distribution using cuda 11.4. The steps do vary
from system to system, so some modifications are likely to be required in practice.
1. Prepare the system for the CUDA installation (if not done already):
sudo yum install kernel-devel-$(uname -r) kernel-headers-$(uname -r) kernel-
debug-$(uname -r)
sudo reboot
sudo yum install --enablerepo=extras epel-release
sudo yum install dkms
2. Get up-to-date drivers.
To do this, select a recent version of the CUDA repositories. In this example, version 11.4 is selected:
wget https://developer.download.nvidia.com/compute/cuda/11.4.0/
local_installers/cuda-repo-rhel7-11-4-local-11.4.0_470.42.01-1.x86_64.rpm
sudo rpm -i cuda-repo-rhel7-11-4-local-11.4.0_470.42.01-1.x86_64.rpm
sudo yum clean all

Note: You can also download the packages from the NVIDIA website.

3. Install the dkms dependencies:

sudo yum -y install nvidia-driver-latest-dkms
4. Install the most recent drivers, and do a final reboot:
sudo yum install cuda-drivers
sudo reboot
5. Verify that the installation has succeeded by typing nvidia-smi.
If the installation has succeeded, the nvidia-smi executable will output information about the GPU and the
installed drivers.
If the installation did not succeed, it must be fixed before you can run Intersect with the GPU option.

Install Intersect on Linux | Install CUDA

14
Intersect Installation and deployment guide

3.5 SLB licensing

Following the installation of Intersect, you must install the Schlumberger Licensing tool. You can find this in the
3rdparty/PC/resource/Slblicensing directory on the installation DVD.

3.6 Test the Intersect installation

The following information may be useful for a simple test of Intersect.

Run from the command line

The Migrator can convert an Eclipse keyword file into an AFI file, which can then be read by Intersect.
• The following ECLRUN command line generates the AFI file but does not run or simulate it: eclrun ecl2ix
basename where basename is the root name of the input dataset. This command just generates the AFI file but
does not run or simulate it.
• To run or perform the actual simulation using the AFI file the following command is used: eclrun ix basename.
Intersect reads the AFI file and performs the simulation.
If the input Eclipse dataset is changed, the AFI file must be regenerated from the dataset first, before being given to
Intersect to be simulated.
An AFI consists of {basename}.afi, and its associated files basename_ECL2IX.gsg, basename_ECL2IX_IX.ixf,
basename_ECL2IX_FM.ixf, basename_fm_edits.ixf and basename_reservoir_edits.ixf.
For information on using ECLRUN, see the ECLRUN User Guide provided as a separate part of the Intersect installation.

Test Intersect with an example data file

1. Create a temporary directory, and copy the example IX.DATA from ../ix/Examples/Example_2/ into the
directory.
2. Change to the temporary directory and run the example using the command eclrun ecl2ix IX.
You should see a simulation run and exit normally, as below:

...
REPORT Keyword migration summary:
+-------------------------+
| Fully migrated | 53 |
| Partially migrated | 4 |
| Not migrated | 6 |
| Ignored | 8 |
| Total | 68 |
+-------------------------+
INFO IX.afi is created.
INFO Migration complete. Elapsed time 0hrs:0mins:10secs (10secs)
REPORT Message summary
+---------------------------+
| Message Level | Frequency |
+---------------------------+
| INFO | 32 |
| WARNING | 14 |
| ERROR | 0 |
+---------------------------+
INFO Run finished normally.

Install Intersect on Linux | Test the Intersect installation | Test Intersect with an example data file
15