Академический Документы
Профессиональный Документы
Культура Документы
User Guide
Proprietary notice
Copyright (c) 2012 Schlumberger. All rights reserved. Reproduction or alteration without prior
written permission is prohibited, except as allowed under applicable law.
Use of this product is governed by the License Agreement. Schlumberger makes no warranties,
express, implied, or statutory, with respect to the product described herein and disclaims without
limitations any warranties of merchantability or fitness for a particular purpose.
Trademarks & service marks
"Schlumberger," the Schlumberger logotype, and other words or symbols used to identify the
products and services described herein are either trademarks, trade names, or service marks of
Schlumberger and its licensors, or are the property of their respective owners. These marks may
not be copied, imitated, or used, in whole or in part, without the express prior written permission of
their owners. In addition, covers, page headers, custom graphics, icons, and other design
elements may be service marks, trademarks, and/or trade dress of Schlumberger and may not be
copied, imitated, or used, in whole or in part, without the express prior written permission of
Schlumberger.
Table of Contents
1
Introduction ................................................................................................................. 1
1.1
1.2
1.3
2.2
2.3
2.4
2.5
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
Settings ...................................................................................................................... 15
5.1
5.2
5.3
5.4
Appendix .................................................................................................................... 21
7.1
Index ............................................................................................................................................................ 25
ii
1
Introduction
The Simulation Launcher is Windows based software for running the ECLIPSE, FrontSim and
INTERSECT simulators and pre and post processors. The user interface is based on the Microsoft
Windows standards on buttons and dialogs. This makes the Simulation Launcher familiar to the
majority of reservoir engineers today and ensures efficient usage of the application.
The Simulation Launcher uses a utility called ECLRUN to run the programs mentioned. The
Simulation Launcher supports the following simulation combinations:
1.1
Remote Linux/UNIX system with the LSF (Load Sharing Facility from Platform Computing)
queue system.
1.2
User Interface
The user interface is designed using Microsoft Windows standards to give a familiar look and feel.
The Simulation Launcher consists of three main parts:
The Launcher pane has the same look and feel as the Windows Explorer. Each program has an
associated icon and these can be organized into Groups.
Introduction
The Display window displays the fields needed to run the selected program selected and to
provide information about the program's associated properties. The status of a selected
simulation is also displayed within this window.
The Simulation History pane displays the history of simulations that were launched by the user
directly with Simulation Launcher or ECLRUN.
1.3
Menu Bar
The pull-down menus are listed on the Menu bar at the top of the window, and should be familiar
for most users.
1.3.1
To open a pull-down menu click on the menu with the left mouse button.
To perform any of the functions in the menu, click on it with the left mouse button.
Introduction
Exit
Closes the application.
1.3.2
1.3.3
1.3.4
Help
Diagnostics
Shows system information for troubleshooting
Manual
Opens the Simulation Launcher User Guide in Adobe Acrobat.
About
Displays the application's details, such as version, proprietary information and a short
description.
Introduction
2
Quick Start Guide
2.1
Launching a Simulation
The 2011.1 release of Simulation Launcher introduced a simple queuing mechanism to restrict the
number of jobs (instances of ECLRUN) that are running at the same time. This mechanism was
introduced to reduce the performance effect that launching lots of instances of ECLRUN at the
same time could have on the machine on which they are running. The queuing system applies to
simulators only and is enabled by default (to disable it, clear the Enable local queuing
system check box on the Simulation Launcher tab of the Settings window). The number of
jobs that can run at the same time is controlled by the value of EclNJobs (see ECLRUN Settings
(p.16) for more details).
The following procedure explains how to run a simulation using the Simulation Launcher.
1. Select a Simulator from the Simulators group.
2. Click on Add Dataset and then browse for the dataset you wish to use. You can select multiple
datasets from the browse screen.
3. Select a queue from the dropdown list.
If you have set up other queues, these will also be available for selection. See Add or delete
a queue (p.18).
Latest will work out the most up to date installed version of the simulator you have chosen
on your machine or the remote machine
5. Click on Run.
As a result the job(s) are either submitted to the Eclrun local queuing system (if enabled) or
launched directly. In case of the former, the job(s) will wait until the currently running instances of
ECLRUN finish, so making place for the pending ones (the number of pending simulations is
displayed on the status bar in the bottom-left corner of the main window).
If you launch a simulation for processing on a remote server(s) and you do not supply a user name
and password, Simulation Launcher queries ECLRUN to see if it is setup to work in password-less
mode. If it is setup this way, you are not prompted for a password. You can also enter your user
name and password details in the Queues setup window in Simulation Launcher in which case,
you do not need to supply the information when you launch a simulation. Except for these two
cases, you will be prompted for a user name and password for remote submission if you don't
provide them explicitly.
Notes:
If you are running INTERSECT then you will also have to select the number of processors that
you want to use.
Enabling and disabling the Eclrun local queuing system requires restarting Simulation
Launcher.
Changing the value of EclNJobs does not affect the Eclrun local queuing system until
Simulation Launcher is restarted.
By closing the Simulation Launcher application, you stop any pending job from being launched.
The jobs are not automatically re-launched if the Simulation Launcher has been reopened.
Host file
When submitting a parallel job or a set of parallel jobs, a shared host file can be specified in one of
two ways:
Selecting an existing host file with the Browse button (which is on the Select tab of the
Summary window of the selected simulator).
Manually adding -m hostfile to ECLRUN's command line options for the selected simulator
(see Advanced Tab (p.5) for more details). hostfile must be either a relative or absolute
path to an existing host file on the local machine.
The host file that has been selected with the Browse button can then be edited by clicking on the
Edit button. Selection can be cancelled by clicking on Clear button.
Notes:
2.1.1
The chosen host file will be used for all the selected simulation input files, without checking
whether the file's format or contents are correct.
The Edit button opens the selected host file using the default application associated with the
host file's file extension.
Advanced Tab
The Advanced tab allows you to further customize the way that you want to run the simulation.
This option is only available for use with the Schedule program.
This option is not enabled if your operating system is 32 bit because a 64 bit
executable will not work.
2.2
If the simulation is not running this button displays Run. This allows you to run the
simulation again, using the syntax specified in the Command Line Options box.
With Debug Mode, if you check this option and click on Run a command console is
displayed with the debug information from the ECLRUN instance running the
simulation. This information can be used to provide information to Schlumberger
Support if you have problems running datasets.
Automatically update every X mins. Performs the same function as Update at the
specified intervals.You can change the default interval. See Simulation Launcher
Settings (p.15).
2.2.1
2.2.2
Message Filter
The Message Filter allows you to search for specific text within displayed simulation results. By
default you see all messages type within the grid; these can be filtered by check/unchecking the
appropriate message types.
2.3
2.4
This option is only available for use with the Schedule program.
This option is not enabled if your operating system is 32 bit because a 64 bit
executable will not work.
2.5
Launching a Manual
The following procedure explains how to display a manual.
1. Select Manuals from the launcher pane
2. Select a version of the manual set to view from the dropdown list
3. Click on Run. This displays the selected manual set.
Note: Adobe Acrobat is required to view the manuals. It is on the installation DVD.
3
Administration Tasks
You can carry out the following tasks in the Launcher pane.
3.1
Adding a Group
Groups are a convenient way to organize programs in the Simulation Launcher. For example you
can create a Results Viewer group that contains the FloViz and ECLIPSE Office programs.
1. To add a Group use one of the following methods:
On the File menu, point to New, and then click New Group.
Right-click on empty space in the Launcher pane, and then click on Add Group.
2. After adding a group you can enter a new group name. Make sure that the group names are
unique.
3.2
Renaming a Group
1. In the Launcher pane, right-click the group you want to rename.
2. Click Rename.
3. Type the new group name, and then press Enter.
3.3
Removing a group
1. In the Launcher pane, right-click the group you want to remove.
2. Click Remove.
3. Click Yes to confirm the deletion of the group and all of its contents.
Note: If you remove a group that has associated programs, these programs are only deleted
from the Launcher pane and are not deleted from your system.
Administration Tasks
3.4
Adding a Program
You can add programs to the Launcher pane. These can either be copies of the default set of
programs that you have customized or you can add other SIS applications.
1. To add a Program use one of the following methods:
On the File menu, point to New, and then click New Program.
2. Select the program you wish to add and click on Add Program.
The programs available to add will depend upon what programs you have installed on your
local computer.
The Other option in the list allows you to add any other SIS application.
3.5
You can view the properties of a simulator by right-clicking on the simulator, and then pressing
Properties.
When you view the properties of one of the simulators the following will be displayed:
The Submit, Fetch (load results), and Kill (abort) Commands define the way the Simulation
Launcher administers simulations.
Words surrounded by % are variables. The Simulation Launcher uses these variables as
commands when a simulation is run. They allow you to select, for example, the datafile to be
used, the queue and the server on which to submit the simulation. All variables are optional
with the exception of %DATAFILE%.
Variables surrounded by [ ] are only written if Simulation Launcher has a non-blank value
for the variable enclosed. [] cannot be used with %DATAFILE%.
Definition
%DATAFILE% Name of the data file for the simulation. You must give a value for this variable.
%VERSION%
%SERVER%
%USERID%
Administration Tasks
10
Variable
%OPTIONS%
Definition
Any options that you want to pass to ECLRUN, the queuing system and the
executable. (See "Command syntax" in the "ECLRUN User Guide".)
3.6
You can view the properties of a program by right-clicking on the program, and then selecting
Properties.
When you view the properties of one of the ECLIPSE Pre/Post the following will be displayed
Name of Program
Allows you to change the name of the program.
Start Command
Defines the way that Simulation Launcher launches the program.
Words surrounded by % are variables. They are replaced by Simulation Launcher when
a simulation is run depending on the queue that has been selected and other
information that you enter in the Simulation Launcher.
Definition
%STARTDIR% Name of the directory the program will open files from
%VERSION%
Administration Tasks
11
Variable
%OPTIONS%
Definition
Any options that you want to pass to ECLRUN, the queuing system and the
executable. (See "Command syntax" in the "ECLRUN User Guide".)
3.7
You can view the properties of a program by right-clicking on the manual, and then selecting
Properties.
When you view the properties of one of the manuals the following will be displayed:
Name of Program
Allows you to change the name of the program.
Manual to View
Allows you to change the default manual you would like to view.
3.8
You can view the properties of a program by right-clicking on it, and then selecting Properties.
When you view, add or edit the properties of one of the SIS programs or Other programs the
following will be displayed;
Name of Program
Allows you to change the name of the program.
Program to Run
The path to the executable that you would like to start from the Simulation Launcher.
Command Line Parameters
Allow you to enter any options that you would like to pass to the executable selected
above. There are special parameters which the Simulation Launcher recognizes and
replaces with values specified by the user.
Administration Tasks
12
Words surrounded by % are variables, replaced by Simulation Launcher when a program is run,
according to selections made by the user.
Sequences surrounded by [ ] are only written if Simulation Launcher has a non-blank value
for the variable enclosed.
Variable
[%FILE%]
Definition
Will be replaced with the file the user has selected
[%FOLDER%] Will be replaced with the startup directory the user has chosen
3.9
Rename a Program
1. In the Launcher pane, right-click the program you want to rename.
2. Click Rename.
3. Type the new program name, and then press Enter.
Administration Tasks
13
4
Simulation History
You can carry out the following tasks in the Launcher pane.
The default number of items for the history is 300. This can be changed in the Simulation
Launcher Settings (see Simulation Launcher Settings (p.15)). When this number is reached,
Simulation Launcher deletes the oldest finished simulation from the list.
Checking or unchecking the View column displays a new tab with the current status and results
of the simulation (see Display simulation results (p.6)).
Double-clicking on a row opens a new tab and double clicking again on the same row closes
the tab.
By clicking on the Delete button the history item is deleted from the list.
Note: You cannot remove the history item if a tab with the results is already open. You need to
close the tab first.
Simulation History
14
5
Settings
You can change the settings by clicking on the settings in the Configuration pull down menu. The
Settings dialog includes options for changing the:
5.1
ECLRUN Settings
Enginframe settings
Settings
15
the ECLRUN User Guide for more details). If the local queuing system is enabled then the
number of instances of ECLRUN that are launched at once can be modified by the Number
of instances of ECLRUN running concurrently numeric box. The minimum
setting is 1 and the maximum is 16 (it defaults to 5).
Default version (ECLDEFVER)
Default version of a program to run (only applies to ECLIPSE or INTERSECT related
applications, such as Pre/Post, simulators). This value is not verified (it can be potentially
pointing to a non-existent version). This default version is to be used when user leaves
'latest' in the 'Select Version' filed on the summary/select window.
5.2
ECLRUN Settings
Enable License Check For Local Windows Simulations
Jobs will only then be executed when all the required resources (licenses/processors) are
available.
TRUE - use license aware scheduling, FALSE - do not use license aware scheduling.
Local Parallel Authentication
Setting NoAuthentication /LocalHost. Sets Intel MPI to allow local parallel jobs to run
without first having a to register a password in an encrypted format in the registry.
Setting Authentication Required / Multiple Machines requires you to enter a password for
running locally or on multiple hosts using parallel processing.
Number of Simulation Processes to Run Concurrently (EclNJobs)
Currently this is the number of simulations that can be run at once on your local Windows
machine. It defaults to the real number of CPU cores available (maximum of 4) if it is not
enabled. Only enable this option if you want to override the default behavior of ECLRUN
(See "Configuration" in the "ECLRUN User Guide").
Intel MPI Path
ECLRUN automatically detects the installation of the Intel MPI. However, if for some
reason ECLRUN cannot detect the path, you can enter the path in this box.
Queue System syntax: server_1:[LSF|CCS],,server_n:[LSF,CCS].
If the specified submission server is on the list, ECLRUN ignores the default mechanism of
choosing the remote queue system. This variable is intended for future expansion. In this
version of ECLRUN it has no effect, as this version of ECLRUN always uses LSF when
submitting to a remote queue.
Note: CCS denotes Microsoft HPC.
Enable FloGrid to 'Save And Restore'
Enables or disables the 'Save And Restore' option in FloGrid.
Settings
16
5.3
EnginFrame Settings
Enginframe Path
This is the last part of web address of the EnginFrame Web Service which follows the port
number. Defaults to 'enginframe'.
Enginframe Port
This is the port number under which the EnginFrame Web Service is available on a remote
server. Defaults to '8080'.
Enginframe use SSL
Indicates whether a secured or unsecured connection of the EnginFrame Web service is
required.
5.4
Queues Settings
Name
A name for the queue definition. This will be listed in the drop-down menu of queues when
submitting a simulation.
Server
The server address for the machine where the simulation should be submitted. Leave
empty for local runs. Replaces %SERVER% in a command.
Remote Queue
Queue for the remote server machine. Replaces %QUEUE% in a command. When this is
clicked to populate the drop-down list, it is automatically filled with LSF queue names only
if valid Server Name, Userid and Password entries are provided and the specified user has
access to LSF queues on the server. A queue name can be also typed directly into the
field avoiding auto-detect.
Queue options
The contents of this box are passed directly to the queuing system submission command
(bsub for LSF, qsub for PBS Pro / Torque and job submit for Microsoft HPC) through
the --queueparameters ECLRUN command line option. Data typed into this box is not
parsed or validated. Queue parameters are defined per queue (they are not shared
between queues).
Note: There is no need to type the --queueparameters option explicitly into the field as
this will be added automatically at submission time.
Settings
17
5.4.1
5.4.2
If you tick the check box Use same logon for all servers, you only need to enter the Userid
and Password once. Otherwise, each queue that uses a different server will need the Userid
and Password to be entered
The queue name drop-down list is filled in automatically only when pointing to a server with a
valid LSF installation and the specified user has access to the queues.
Queue name auto-detection runs every time the 'Remote Queue' drop down list is populated.
To add a queue, click the Add a new queue button and fill in its details in the boxes on the right
of the dialog.
To delete a queue, select it in the list on the left and click the Remove selected queue button.
Select the required default queue in the list and click the Default button below the list. The
queue that is selected as default will be used for new simulation runs.
Settings
18
6
Configuration File
All the groups and programs in the Launcher pane and settings of the Simulation Launcher are
stored in a configuration file.
The first time you run Simulation Launcher and exit, the file is created in the folder
%USERPROFILE%\Application Data\Schlumberger\Simulation Launcher
If %USERPROFILE% has not been changed on your system, this in practice means that the folder is
in one of these locations:
\Schlumberger\Simulation Launcher
\Simulation Launcher
Or C:\Users\username\AppData\Local\ Schlumberger\Simulation
Launcher
The file is called SimLaunchConfig.xml. To distribute standardized settings you can make a
common version of this file for all users.
1. First of all set up the Simulation Launcher correctly for one user.
2. Then make a copy of this user's SimLaunchConfig.xml file and distribute it to the
%ALLUSERSPROFILE% of the target machines. The possible locations for %ALLUSERSPROFILE%
are (unless the machine's system administrator has changed the defaults):
\Schlumberger\Simulation Launcher
3. You could also copy the SimLaunchConfig.xml file to a network location which is
accessible to all users. Make this file read-only if you do not want them to be able to edit the
file. This allows you to administer the settings for the Simulation Launcher for all of your users.
Configuration File
19
For example you may want to add or remove queues and this can be done from the network file
rather than visiting each user individually.
4. To apply the network configuration file to an end-user from Simulation Launcher Settings
(see Simulation launcher settings (p.15)) you can browse to this location, select this file and
restart the Simulation Launcher to apply these settings.
Simulation Launcher can read all three configuration files: user, all user and network. Simulation
Launcher merges the configuration files on startup. Any setting of the same name defined in the
network file will override those in the All User file, and both will override settings of the same name
defined in the User file.
In some cases some settings will be read-only because they exist in network or All User file and
cannot be changed. The Diagnostics dialog will display each of the configuration files if they exist
and also the merged configuration file in memory. This can be useful for support personnel.
All settings can be changed using the Simulation Launcher. However, there is one setting you have
to change directly within the xml file to stop users changing the settings:
<AllowEdit>True</AllowEdit>
Configuration File
20
7
Appendix
7.1
7.1.1
7.1.2
Appendix
21
It is also possible to run the software by opening a command prompt and running the appropriate
script.
It is advisable to call the help file before running a macro for the first time.
Syntax: $<program> [arguments...] where arguments are any of the following:
-data directory directory containing data
-help displays this information
-local use config file in directory
-over use master config file
-second identifier run identifier
-ver version run requested version of <program>
7.1.3
Characteristics
The first release of the RESQML to GSG Converter utility is limited by the functionality offered by
V1.1 of RESQML and overlaps the GSG requirements needed for input to ECLIPSE and
INTERSECT simulators. This release focuses on:
Support for single poro, dual poro, dual poro dual perm systems
Support for Cartesian local grid refinement, but not radial local grid refinement
ECLIPSE reserved names for properties must be used, unrecognized names will not be unit
converted
Appendix
22
\pc_x86_64\RESQML2GSGConverter.exe
2. Locate the file you wish to convert (with extension .RESQML or .GSG). i.e. path\data.GSG
3. Run it from the command line to convert data.GSG.
Appendix
23
cd bin\pc_x86_64
RESQML2GSGConverter.exe path\data.GSG [-x]
RESQML2GSGConverter.exe path\ data.resqml [-f] [-p] [-l]
Convert as "Macro"
1. Locate the file you wish to convert (with extension .RESQML or .GSG). i.e. path\data.GSG
2. Run it from the command line to convert data.GSG.
$resqml_gsg_converter path\data.GSG [-x]
$resqml_gsg_converter path\data.resqml [-f] [-p] [-l]
Appendix
24
Index
A
Administration ............................................................... 9
Configuration ................................................................ 3
simulators ..................................................................... 4
Simulators .................................................................. 10
File ................................................................................ 2
G
Group: Adding .............................................................. 9
L
Launcher settings ....................................................... 15
M
Manual .................................................................... 8, 12
Menu Bar ...................................................................... 2
Message filter ............................................................... 6
O
Other Application ........................................................ 12
P
Program: Adding ........................................................ 10
Program: Removing ................................................... 13
25