Installation Guide for

Blueback Toolbox
Version 20.0.1

29 November 2021

www.cegal.com
T +47 52 04 00 00
Blueback Toolbox v20 Installation Guide

Copyright © 2021 Cegal. All rights reserved.

This work contains the confidential and proprietary trade secrets of Cegal 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.

Schlumberger Trademarks & Service Marks

Schlumberger, the Schlumberger logotype, trademarks, trade names or service marks of Schlumberger may not be
copied, imitated, or used, in whole or in part, without the express prior written permission of Schlumberger.

Country of origin: Norway

Page 2 of 27
Blueback Toolbox v20 Installation Guide

Table of Contents
1 Introduction ........................................................................................................... 4
2 System Requirements .......................................................................................... 4
2.1 Public Key Token...................................................................................................... 4
2.2 Software Compatibility .............................................................................................. 4
3 Installation ............................................................................................................ 4
3.1 Downloading Blueback Toolbox................................................................................ 5
3.2 Installing Blueback Toolbox ...................................................................................... 5
3.2.1 Installing Blueback Toolbox with Windows Installer ............................................ 5
3.3 Upgrading from Previous Versions ........................................................................... 7
3.4 Installed Components ............................................................................................... 8
4 Uninstallation ...................................................................................................... 15
4.1 Uninstalling Blueback Toolbox Installed with Windows Installer (.msi) .....................15
4.1.1 Uninstalling Blueback Toolbox via the Windows Control Panel .........................16
4.1.2 Uninstalling Blueback Toolbox via .msi .............................................................16
5 Unattended Installation & Uninstallation ............................................................. 19
6 Licensing ............................................................................................................ 19
6.1 License Feature .......................................................................................................20
7 Python Tool Getting started ................................................................................ 21
7.1 Introduction..............................................................................................................21
7.2 Environment Setup ..................................................................................................21
7.2.1 How to install Python 3.6 ...................................................................................22
7.2.2 Installing Python environment for CPython tool .................................................23
7.3 Environment QC: .....................................................................................................23
7.4 Locating the Anaconda Installation ..........................................................................24
8 tNavigator Getting started ................................................................................... 25
8.1 Introduction..............................................................................................................25
8.2 Environment Setup ..................................................................................................26
8.2.1 Local simulation ................................................................................................26
8.2.2 Remote simulation ............................................................................................26
8.2.3 Job scripts .........................................................................................................27
8.2.4 Setup Petrel ......................................................................................................27

Page 3 of 27
Blueback Toolbox v20 Installation Guide

1 Introduction
Thank you for your interest in Blueback Toolbox version 20.0.1.
This installation guide for Blueback Toolbox provides step-by-step instructions for installing the
Blueback Toolbox plug-in for Petrel.
Remember: Blueback Toolbox is very much a user-driven product. Please continue to send
ideas to [email protected] or visit our support portal: blueback.zendesk.com.

2 System Requirements
Blueback Toolbox has the following system requirements:

• Petrel 2019.X, 2020.X, 2021.X(64-bit) installed on the target machine before you start the
Blueback Toolbox installation process. Note only 64-bit versions of Petrel are supported.
• Schlumberger Licensing utility, which should have been installed when Petrel was
installed, and is described in the detail in the Petrel Installation Guide.
• A dongle and valid Petrel license on your local computer or access to a license server.
• Anaconda data science software needs to be installed for the CPython version of the
Python tool to work.

Blueback Toolbox is a Petrel plug-in and has the same hardware requirements as Petrel. See
the Petrel Installation Guide for more information.

2.1 Public Key Token

The public key token for Blueback Toolbox is 422edafdd2ea0cff.

2.2 Software Compatibility

Blueback Toolbox v20.0.1 is compatible with Petrel 2019.X, 2020.X and 2021.X.
For Python tool, a separate environment needs to be created, details of which are present in
chapter 7

3 Installation
This chapter will guide you through the installation of Blueback Toolbox. Contact
[email protected] if you have any problems or questions.

Page 4 of 27
Blueback Toolbox v20 Installation Guide

3.1 Downloading Blueback Toolbox

This version of the Blueback toolbox is available by contacting the Cegal software service
desk. ([email protected])
There is one zip file each for Petrel versions:

Petrel Version Download File

Petrel 2019.X 64 bit Blueback_Toolbox_20.0.1_Petrel_2019.zip
Petrel 2020.X 64 bit Blueback_Toolbox_20.0.1_Petrel_2020.zip
Petrel 2021.X 64 bit Blueback_Toolbox_20.0.1_Petrel_2021.zip

The zipped download file is about 277 MB. This includes the installer, release notes, installation
guide and help documentation as a CHM file.

3.2 Installing Blueback Toolbox

3.2.1 Installing Blueback Toolbox with Windows Installer
The plug-in is installed using the .msi file, which installs the .pip file using PluginManager.exe
as part of the installation process.
1. Save the zipped download file in a folder (see Downloading Blueback Toolbox)
2. Unzip the file
3. Double click the .msi file to start the installation and follow the instructions

Figure 1 – Blueback Toolbox setup wizard

Page 5 of 27
Blueback Toolbox v20 Installation Guide

Figure 2 – Blueback Toolbox installation window

Figure 3 – Blueback Toolbox installation in progress

Page 6 of 27
Blueback Toolbox v20 Installation Guide

Figure 4 – Blueback Toolbox installation complete

4. Blueback Toolbox is launched from inside Petrel, so you need to start Petrel to check
that the installation has been successful.

Please note that the installer installs:

• Blueback Toolbox
• Blueback Well Test
• Blueback Marina
• Blueback Python Tool
• Blueback QI Tools
• Blueback QI Domain Objects
• Blueback BluePrint
• Blueback Unconventional Toolbox

3.3 Upgrading from Previous Versions

You can check for a new version of Blueback Toolbox within the plug-in:
1. Open Blueback Marina
2. Select Information and settings > About Blueback Toolbox from the list of tools
3. Click the “Check for update” button

Page 7 of 27
Blueback Toolbox v20 Installation Guide

If a new version is available, you will be given instructions on how to download it. The new
version of Blueback Toolbox can be installed directly using the instructions in the Installing
Blueback Toolbox section of this installation guide. The installer will detect and remove old
versions of Blueback Toolbox.

3.4 Installed Components

The Blueback Toolbox installer will make the following changes to the system:
1. Add folders to the default plug-in directory (e.g. the “Extensions” folder of the Petrel
installation directory) called:
• Blueback Toolbox_20.0
• Blueback Unconventional Toolbox_2.0
• Blueback Python Tool_2.0
• Blueback QI Domain Objects_1.0
• Blueback QI Tools_1.0
• Blueback Well Test_3.0
• Blueback BluePrint_2.0
• Marina_2.0

2. Add the following files in the “Blueback Toolbox_20.0” folder:

Figure 5 – Files added to Blueback Toolbox_20.0 folder

Page 8 of 27
Blueback Toolbox v20 Installation Guide

3. Add the following files in the “Blueback Toolbox_20.0 > Blueback.Toolbox.Marina” folder:

Figure 6 – Files added to Blueback Toolbox_20.0 > Blueback.Toolbox.Marina folder

4. Add the following files in the “Blueback Toolbox_20.0 > GeoTiff” folder:

Figure 7 – Files added to Blueback Toolbox_20.0 > GeoTiff folder

Page 9 of 27
Blueback Toolbox v20 Installation Guide

5. Add the following files in the “Blueback Toolbox_20.0 > GeoTiff > csv” folder:

Figure 8 – Files added to Blueback Toolbox_20.0 > GeoTiff > csv folder

Page 10 of 27
Blueback Toolbox v20 Installation Guide

6. Add the following files in the “Blueback Python Tool_2.0” folder:

Figure 9 – Files added to Blueback Python Tool_2.0 folder

7. Add the following files in “Blueback QI Domain Objects_1.0” folder:

Figure 10– Files added to Blueback QI Domain Objects_1.0 folder

Page 11 of 27
Blueback Toolbox v20 Installation Guide

8. Add the following file in the “Blueback QI Tools_1.0” folder

Figure 11– Files added to Blueback QI Tools_1.0 folder

9. Add the following files in the “Blueback Well Test_3.0” folder:

Figure 12 – Files added to Blueback Well Test_3.0 folder

10. Add the following files in the “Blueback BluePrint_2.0” folder:

Figure 13– Files added to Blueback BluePrint_2.0 folder

Page 12 of 27
Blueback Toolbox v20 Installation Guide

11. Add the following files in the “Blueback BluePrint_2.0 > PredefinedWorkflows” folder:

Figure 14 – Files added to Blueback BluePrint_2.0 > PredefinedWorkflows folder

12. Add the following files in the “Blueback BluePrint_2.0 > TemplateExamples” folder:

Figure 15 – Files added to Blueback BluePrint_2.0 > TemplateExamples folder

13. Add the following files in the “Marina_2.0” folder:

Figure 16 – Files added to Marina_2.0 folder

Page 13 of 27
Blueback Toolbox v20 Installation Guide

14. Add the following files in the “Blueback Unconventional Toolbox_2.0” folder:

Figure 17 – Files added to Blueback Unconventional Toolbox_2.0 folder

15. Add the following files in the “Blueback.UnconventionalToolbox.Marina” folder:

Figure 18 – Files added to Blueback.UnconventionalToolbox.Marina folder

Page 14 of 27
Blueback Toolbox v20 Installation Guide

16. Modify the PluginManagerSettings.xml file to register the plug-in modules

17. A new trusted vendor is defined, called “Cegal”, allowing Blueback Toolbox to be executed
when Petrel is executed with the medium and high security levels.
18. In Petrel’s Ocean Plug-in Manager, you can see the installed plug-ins:
• Blueback Python Tool
• Blueback Toolbox
• Blueback Well Test
• Blueback Marina
• Blueback QI Tools
• Blueback QI Domain Objects
• Blueback BluePrint

Figure 19 – Ocean Plug-in Manager showing installed plug-ins

4 Uninstallation

4.1 Uninstalling Blueback Toolbox Installed with Windows Installer

(.msi)
Petrel plug-ins installed via .msi may be uninstalled via the Windows Control Panel or by re-
running the .msi.

Page 15 of 27
Blueback Toolbox v20 Installation Guide

4.1.1 Uninstalling Blueback Toolbox via the Windows Control Panel

1. Open Windows Control Panel > Programs and Features (Programs > Uninstalling a
program in Category view)
2. Find the entry for Blueback Toolbox in the list
3. Click Uninstall. Blueback Toolbox will be uninstalled and the Installed Components
removed from the system. It will also modify the PluginManagerSettings.xml file to
unregister the plug-in modules.

4.1.2 Uninstalling Blueback Toolbox via .msi

1. Double click the .msi file to start the setup wizard

Figure 20 - Blueback Toolbox setup wizard

2. Click Next

Page 16 of 27
Blueback Toolbox v20 Installation Guide

Figure 21 - Blueback Toolbox change/repair/remove prompt

3. Click Remove and follow the prompts to uninstall Blueback Toolbox

Figure 22 - Blueback Toolbox uninstaller window

Page 17 of 27
Blueback Toolbox v20 Installation Guide

Figure 23 - Blueback Toolbox uninstallation in progress

Figure 24- Blueback Toolbox uninstallation complete

Page 18 of 27
Blueback Toolbox v20 Installation Guide

5 Unattended Installation & Uninstallation

Blueback plugins delivered as .msi files can be installed and uninstalled unattended (without
user interaction) using msiexec (e.g. from the cmd.exe command line, assuming the .msi file
is in the current directory):

• Install: msiexec /i “[plugin file name].msi” /qb

• Uninstall: msiexec /x “[plugin file name].msi” /qb

These command lines display progress on the screen and will prompt for UAC elevation
(administrative rights) if the command prompt is not elevated.

If completely silent execution is desired, and the command prompt is already elevated (started
with “Run as Administrator”), “/qb” can be replaced with “/quiet”. This will not display any error
messages, but “/|* log.txt” can be added to the command line to capture a log file for diagnosis.

6 Licensing
Blueback Toolbox uses the same licensing system as Petrel. The Ocean Store will provide
Petrel license files for the Blueback Toolbox module. These license files must be loaded into
the “Schlumberger licensing” application. See the Petrel Installation Guide for more
information.
You will also require a valid license for Petrel itself. As a minimum we suggest having a valid
Petrel Geoscience Core license.
The Blueback Toolbox license modules will be shown in the Petrel license package dialog
under “Ocean plug-ins”. Make sure that the required license modules are selected.

Page 19 of 27
Blueback Toolbox v20 Installation Guide

Figure 25 – Ocean license selector dialog

6.1 License Feature

Blueback Toolbox has the following license features:

• OCEAN_BBR_BLUEBACK_TOOLBOX_DM for Blueback Toolbox project

management,
• OCEAN_BBR_BLUEBACK_TOOLBOX_GE for Blueback Toolbox geology,
• OCEAN_BBR_BLUEBACK_TOOLBOX_GF for Blueback Toolbox geophysics,
• OCEAN_BBR_BLUEBACK_TOOLBOX_RE for Blueback Toolbox reservoir
engineering
• OCEAN_BBR_UNCONVENTIONAL_TB

Page 20 of 27
Blueback Toolbox v20 Installation Guide

7 Python Tool Getting started

7.1 Introduction
It’s necessary to have Python 3.6 installed in the system. The Python tool uses the CPython
distribution delivered with Anaconda. In case, Anaconda is not installed, it can be downloaded
from:
https://www.anaconda.com/download/
For use of Anaconda – please refer to Anacondas Terms of Service with respect to license
compliance:
https://www.anaconda.com/terms-of-service.
Please note that the current version of Anaconda implements newer versions of Python than
Python 3.6. Thus, it’s necessary to set up the environment properly for getting started with the
python tool.
After downloading Anaconda from the above-mentioned link and installing it, follow the below
mentioned steps. Please note that Anaconda should not be installed in a location with spaces
in the file path.

7.2 Environment Setup

1) Run the ‘Anaconda Prompt’ from the Start menu
2) In the prompt, navigate to anaconda-requirements-pythontool.yml file in
Extensions folder in default plugin directory (e.g., …\Petrel 2019.2
x64\Extensions\Blueback Python Tool_1.0) and run ‘conda env update --file
anaconda-requirements-pythontool.yml’.

Figure 26 - Installing Python environment for CPython tool

Page 21 of 27
Blueback Toolbox v20 Installation Guide

You should now have a ‘pythontool’ environment. The Python Tool will set as default an
environment which contains the phrase ‘Python Tool’, ignoring whitespace and case.

Figure 27 - Installed environment being recognized by the CPython tool

7.2.1 How to install Python 3.6

1) Run the ‘Anaconda Prompt’ from the Start menu
2) In the prompt, run ‘python --version’
3) If your installed Python version is 3.6, proceed to section 7.2.2
4) To list the versions of python you have available for installation run ‘conda search
python’
5) To update your current version of python run ‘conda install python=3.6’
6) Alternatively, you can create a new environment for Python 3.6 by running ‘conda
create -n py36 python=3.6 anaconda’

Page 22 of 27
Blueback Toolbox v20 Installation Guide

7.2.2 Installing Python environment for CPython tool

1) Run the ‘Anaconda Prompt’ from the Start menu
2) In the prompt, navigate to anaconda-requirements-pythontool.yml file in Extensions
folder in default plugin directory (e.g., …\Petrel 2019.2 x64\Extensions\Blueback
Python Tool_1.0) and run ‘conda env update --file anaconda-requirements-
pythontool.yml’

Figure 28 - Installing Python environment for CPython tool

7.3 Environment QC:

You can check whether the environment is installed by going to the Anaconda prompt and run:
conda activate pythontool
python

Page 23 of 27
Blueback Toolbox v20 Installation Guide

Python should report it’s running 3.6.X. One way of checking that everything is working is to
import a few libraries. E.g. type:
import numpy
import pandas

If no errors are reported, the environment is installed correctly.

Figure 29- QC of the Python environment being installed correctly

7.4 Locating the Anaconda Installation

Python tool searches for the Anaconda installation in two steps:

• Initially it searches the registry under:

o HKEY_CURRENT_USER\SOFTWARE\Python\ContinuumAnalytics\InstallPat
h
• If not, there it checks if the Anaconda install directory exists:
o HKEY_LOCAL_MACHINE\
SOFTWARE\Python\ContinuumAnalytics\InstallPath
• Lastly it checks whether the file .conda\environments.txt exists under the user’s
profile (the UserProfile folder as specified in https://docs.microsoft.com/en-
us/dotnet/api/system.environment.specialfolder?view=netframework-4.7.2)

If the above checks do not pass, Python Tool will not allow CPython to be used.

NB: It is suggested to let the IT department of your organization be aware of Anaconda

installation in your system, so that they can update the network accessibility settings,
if required.

Page 24 of 27
Blueback Toolbox v20 Installation Guide

8 tNavigator Getting started

8.1 Introduction
tNavigator in this context is a reservoir simulator from Rock Flow Dynamics. The full suite from
RFD comprises many modules for building models, running simulations and interacting with
results. The Toolbox only relies on a single executable: the standalone console simulator
(“tNavigator-con.exe”).
The Toolbox implements an Exclipse format compatible plugin which will allow users to send
models to tNavigator for simulation and read results back into Petrel.
The tNavigator simulation package must be purchased, installed and licensed separately.
Simulation jobs are submitted to the local machine (same as the running Petrel application) or
to a remote HPC cluster. The Toolbox has been developed and tested with Microsoft’s HPC
Pack 2012 R2. Other servers can be used by modifying the run scripts described below.
The HPC client package must be installed separately (from the toolbox).

Figure 30 - tNavigator client server setup

Page 25 of 27
Blueback Toolbox v20 Installation Guide

8.2 Environment Setup

8.2.1 Local simulation
Make a note of the simulator installation path, e.g.
C:\tNavigator\bin\tNavigator-con.exe

Ensure that there is a license server setup for the simulator, e.g.
set TNAVIGATOR_LICENSE_SERVER=http://10.16.208.223:180/tNavigator1/
If the checker is installed, probe for a valid license, e.g.
C:\tNavigator\bin> tNavigator-license_status.exe

13 tN_GUI 1 tN_black_oil 1 tN_compositional 1 tN_thermal 1 tN_geology 1

tN_history_matching 1 tN_multiple_realizations 0 tN_large_data_set 0
tN_geology_designer 1 tN_model_designer 1 tN_network_designer 1

8.2.2 Remote simulation

Petrel will write out the input data to a sub directory of its project path, and read simulation
results back from the same location. In this configuration you’ll have to save the project to a
disk shared with the remote processing server, e.g.
\\our_server\shared_disk\my_home\petrel_project.pet\

The simulation files for a case (e.g. “first_case”) will then be located at:
\\our_server\shared_disk\my_home\petrel_project.sim\first_case\

Make sure the HPC command line commands are in the user’s PATH, it could be:
C:\Program Files\Microsoft HPC Pack 2012\Bin

The command job will be used in three variants:

1. job submit # to queue a simulation run
2. job view # to query the state of a submitted run
3. job cancel # to prematurely terminate a submitted run

Page 26 of 27
Blueback Toolbox v20 Installation Guide

8.2.3 Job scripts

There are four template Windows scripts acting as intermediary between Petrel and the
simulation executable. Most likely you’d want to copy these to your own space and modify
them to fit the local computing environment. The scripts are located at something like:
C:\Program Files\Schumberger\Petrel 2019\Extensions\Blueback Toolbox_19.0\

There scripts purpose:

1. tNavSubmit.bat # submit a job remotely or start locally
2. tNavRun.bat # start a job
3. tNavKill.bat # terminates the job
4. tNavFetch.bat # queries the job state

In the client server case, they must be copied to a directory on the shared disk.

8.2.4 Setup Petrel

The simulation executable and the location of the four scripts must be configured in a running
Petrel session. You also need to make a new queue and point it to the HPC server. This is
described in more detail in the Marina help pages within Petrel under the tool tNavigator (as
well as in the toolbox .chm). The example below shows how the paths setup might look for
local runs.

Figure 31 - tNavigator settings in Petrel

Page 27 of 27