Defining a Simulation Case

To construct a simulation case within Petrel you use the Define simulation case process
in the Simulation folder of the Processes; this will enable you to pull together already-
defined models, functions and controls into a case defining the model that will run in this
simulation.
The Define simulation case process will not be available before the necessary objects
have been created. Full or partial cases can be created. When a case is saved or eported,
a brief validation report is created and displayed, describing any missing, incorrect or
inconsistent data within the case.
Simulation case process steps
!efining a simulation case consists of specifying the input properties, then selecting
predefined initial conditions and fluids models, roc" physics functions, and development
strategies. #ou can select the results that the simulation should generate and the type of
simulator. The completed simulation case will appear in the list in the Cases pane.
How to define a simulation case
To add a new simulation case to the list in the Cases pane$
%. &n the Processes pane, open Simulation and select Define simulation case. This will
open the Define simulation case dialog.
'. (elect Create new case and enter the name for the new simulation case into the
adjacent field.
). (elect the Simulator from the drop-down list.
*. (elect the Type of simulation model from drop-down list. &f you select Dual Porosity
or Dual Permeability porosity models, then you are prompted for additional properties in
the Grid tab. For most grid properties you can tic" the chec"bo in the final column on
the +rid tab to define a different property for fractures as opposed to the roc" matri.
,. (elect the Grid for the simulation from the drop-down list. This contains all the grids
set up in the Models pane. The initial inputs for the simulation case will be etracted
from the grid information, but you can change these if you want.
-ote$ The inputs must include permeability on three aes .&, / and 01 and porosity.
2. To enter more inputs from an eisting model into the Grid tab, add a new blan" item at
the appropriate place in the table using the buttons immediately above the table. 3pen the
model in the Models pane, and then select a )! grid property, a transmissibility
multiplier, an a4uifer or a local grid set. 5lic" the Drop in selected item button. 6 new
input will be created and if there is a default Keyword this will be shown. &f there is no
default, or if you wish to change the current selection, clic" on the "eyword column and
select from the list of permissible Keywords.
-ote$ #ou can select the "eyword first, but you can then only insert an input that matches
your "eyword. &f you clic" on the Multiple drop in the table button, clic"ing the Drop
in selected item button will fill the rest of the table in the column with objects listed
below the selected object in the Properties folder of the Models pane.
7. &n the Functions tab, define your P8T, saturation and other roc" physics functions.
#ou add functions to the left hand list by selecting them from the top drop-down menu,
and then define the functions by dropping in your fluids and roc" physics functions into
the right hand table. 3nly one instance of each function can be added to the list.
a. First select lac! "il fluids model #P$T% in the Functions drop-down menu, to add
&nitial 5onditions and P8T functions. 5hec" Initialize by equilibration, unless you have
provided the grid properties P9:((;9:, (W6T, (+6(, 9( or P<;< and 98 or P!:W
for initiali=ation by enumeration.
&f you have a single fluid and e4uilibration region in your reservoir, then you can just
drop in the table your &nitial condition .or Fluid model if you are not using
e4uilibration1, selected from the Fluids folder in the &nput pane.
&f you have multiple fluid or e4uilibration regions then you must chec" 'egion inde(
property and select the grid property from the drop-down list that defines your fluid or
e4uilibration regions. This will fill the table with a row for each region; you can then drop
in an &nitial condition .or Fluid model1 to associate with each region.
b. -et, select Drainage relati)e permeabilities in the Functions drop-down list.
6gain, if you have a single roc" type region for the whole reservoir, then you can drop in
your Saturation Function, selected from the 'oc! physics functions folder in the &nput
pane.
&f you have multiple roc" type regions then you must chec" 'egion inde( property and
select the grid property from the drop-down list that defines your roc" type regions. This
will fill the table with a row for each region; you can then drop in a Saturation Function
to associate with each region.
c. (imilarly, you can define other saturation functions for use when modeling hysteresis
or anisotropy.
d. (elect 'oc! compaction in the Functions drop-down list. !efine single or regionally
varying compaction behavior by dropping in 'oc! compaction functions from the 'oc!
Physics Functions folder in the &nput pane into the table. 5hec" *(port as table to
eport tabular "eywords, otherwise a single roc" compressibility value will be eported
for each roc" compaction function.
>. &n the Strategies tab, add your development strategy or strategies. 6dd a new blan"
item at the appropriate place in the table using the buttons immediately above the table.
3pen the De)elopment strategies folder in the &nput pane then select the strategy that
you want to add. 5lic" on the &nsert button. The new strategy will be added into the
table.
?. &n the 'esults tab, set up the report properties and outputs that will be produced from
the simulation when the case is run.
%@. &n the +d)anced tab, specify the simulator version. &f you are using Front(im, this
tab will also contain setup options for the simulator. Petrel will select default entries for
these, and you must ma"e changes only if you fully understand the conse4uences. &f you
have any doubts, please leave the default selections.
%%. 5lic" on +pply to create the new simulation case.
%'. 9epeat the process to create all your simulation cases.
%). 5lic" on "K to close the dialog.
&f you want to chec" the consistency of the simulation case, clic" on the Chec! button.
-ote that this will not run the full simulation.
&f you want to eport the simulation "eywords and run the simulation, clic" on the 'un
button. The consistency of the case will be chec"ed before the simulation runs. While the
simulation is running, you can abort the run by clic"ing on +bort.
&f you want to eport the "eywords without running the simulation, clic" on the *(port
button.
How to set up a ,ueue Definition for 'emote -ob Submission
To set up a new ,ueue Definition for 'emote -ob Submission of simulation runs$
%. From the menu toolbar, select Tools . System settings/ This will open the System
settings dialog.
'. &n the window that opens, go to the ,ueue definition tab.
). (elect +dd a new 0ueue button to add a new 4ueue definition to Petrel.
*. &n the 1ame field, specify a name for the 4ueue definition. This will be listed in the
drop-down menu in the +d)anced tab of the Define simulation case process.
,. &n the Ser)er field, specify the server address for the machine where the simulation
should be submitted.
2. &n the 'emote directory field, enter a remote directory on the server machine to run
the simulation.
7. &n the Chec! e)ery field, enter a time interval in minutes for fetching the simulation
results in the chec" every field.
>. &n the 2SF 0ueue field, specify the 2oad Sharing Facility .A(F1 4ueue for the remote
server machine.
?. &n the Comms system field, enter the communication system used for message passing
for parallel runs, if the remote server machine supports parallel runs.
%@. &n the Hostfile field, specify the hostfile location used on the remote server, if the
remote server machine support parallel runs.
%%. The remote server machine will also re4uire that a userid and password be defined, in
order to access the remote server for submitting simulation jobs. This information is only
"ept until Petrel eits, and you will need to re-type the userid and password when you re-
run Petrel.
%'. 5lic" on "K to apply and close the dialog.
How to edit an e(isting simulation case
%. &n the Processes pane, open Simulation and select Define simulation case. This will
open the Define simulation case dialog.
'. (elect *dit e(isting case and choose the simulation case from the drop-down list.
). 5hange the simulation parameters as re4uired.
*. 5lic" on +pply to update the simulation case.
,. 5lic" on "K to close the dialog.
How to e(port simulation !eywords
:ither$
%. &n the Processes pane, open Simulation and select Define simulation case. This will
open the Define simulation case dialog.
'. (elect *dit e(isting case and choose the simulation case from the drop-down list.
). 5lic" on the *(port button. This will not run the simulation.
3r$
%. 9ight-clic" on the simulation item for the case, in the Cases pane, and select
Simulation *(port "nly from the contet menu.
The consistency of the case will be chec"ed before the "eywords are eported; a
validation report with warnings or errors will be displayed, if necessary. The eport will
create a set of data files on dis" for the simulation, which include a B.!6T6C file. The
status of and path to the B.!6T6C file is shown in the simulation case (ettings dialog, in
the &nfo tab.
How to run a simulation
:ither$
%. &n the Processes pane, open Simulation and select Define simulation case. This will
open the Define Simulation Case dialog.
'. (elect *dit e(isting case and choose the simulation case from the drop-down list.
). To eport the simulation "eywords and run the simulation, clic" on the 'un button.
3r$
%. 9ight-clic" on the simulator entry for the case in the Case pane.
'. (elect either Simulation *(port and 'un or Simulation 'un "nly from the contet
menu.
The consistency of the case will be chec"ed during eport, before the simulation runs,
and a validation report with warnings or errors will be displayed, if necessary. &f there are
errors in the case or in the eport, then the simulation will not be run.
#ou can force the simulation to run, even if Petrel thin"s there are errors, by chec"ing the
'un simulation e)en if )alidation fails chec"bo on the 'esults tab of the Define
simulation case dialog. This can be useful if you have defined parts of the case using the
"eyword editor, for eample for compositional runs, that the Define simulation case
process does not "now about.
There is no pre-validation of the simulator data files if you right-clic" on the simulation
case and select Simulation Run Only from the Cases pane.
How to stop a running simulation
:ither$
%. 9ight-clic" on the simulator case in the Cases pane and select +bort 'unning
Simulation from the contet menu.
'. #ou will get a message bo as"ing you if you want to abort the simulation. (elect "K
to abort or Cancel to continue simulation.
3r$
%. &n the Processes pane, open Simulation and select the Define simulation case
process. This will open the Define simulation case dialog.
'. (elect *dit e(isting case and choose the simulation case from the drop-down list.
). To stop the simulation, clic" on +bort.
How to rename a simulation case
To rename a simulation case$
%. &n the Cases pane, open the settings dialog for a simulation case and select the &nfo
tab.
'. 5hange the name in the 1ame field and clic" on +pply.
For Petrel generated cases .i.e. not imported cases, or those derived from imported cases1,
a case rename will immediately change the names of, and any references to, the data files
stored on dis" for the simulation.
&t is recommended that the project is saved following a case rename.
&f the project is not saved following a case rename, then when the project is net loaded,
the simulation will not correctly reference data files on dis" .an eclamation mar" will be
overlaid on the simulation icon to alert the user to this1. The simulation can be renamed
again in this scenario to recover the data set on dis".
How to manipulate simulation case details
%. &n the Cases pane double-clic" on the simulation case to be updated. This will display
the Settings dialog for the case.
'. &f you want to change the simulation name, enter the new tet into the 1ame field, in
the &nfo tab. For more information, see Dow to rename a simulation case. -ote that the
name for a simulation using a specified simulator shows the name of that simulator. #ou
cannot change that entry.
). :nter any additional information for the model into the Comments field.
*. #ou can view the simulation case parameters by clic"ing on the Definition tab. #ou
cannot change the parameters in this dialog.
,. 5lic" on +pply to update the fluid model details.
2. 5lic" on "K to close the dialog.
How to open the !eyword editor
:ither$
%. 9ight-clic" on the simulation case, in the Cases pane, for which you want to edit the
"eywords.
'. (elect the Keyword *ditor option from the contet menu. This will open the "eyword
editor with the selected simulation case ready for editing. For more information refer to
the help for the appropriate simulator "eywords.
3r$
%. &n the Processes pane, open Simulation and select Define simulation case. This will
open the Define simulation case dialog.
'. (elect *dit e(isting case and choose the simulation case from the drop-down list.
). +o to the +d)anced tab and clic" on the Keyword *ditor button. This will open the
"eyword editor with the simulation case dec" ready for editing.
How to )iew messages from the )alidation and from the simulator
#ou can view messages generated by the validation when the simulation case is eported,
and from the simulator after the simulation is run. The messages are displayed
automatically, if there are errors to report.
%. 9ight-clic" on the simulation case in the Cases pane and select Show simulation
log/ from the contet menu. This displays a spreadsheet showing the messages
generated by the simulator during the run.
To automatically display this spreadsheet at the end of the simulation run, enable +lways
show )alidation and simulation message files on the 'esults tab of the Define
simulation case process dialog.
How to )iew a simulator print file
#ou can view the print file generated by the simulator when the simulation is run. The
print file contains all the messages in the message file, plus additional reports, such as
well flows and fluids in place reports.
%. 9ight-clic" on the simulation case, in the Cases pane, and select Show print file/
from the contet menu. This opens the print file in a tet editor.
How to import a Keyword Case into Petrel
To import a "eyword case to Petrel$
%. 9ight-clic" on the bac"ground, in the Cases pane, and select &mport #on tree%/ from
the contet menu.
'. &n the &mport file dialog window select the file format type of the simulation case that
you want to import.
). Aocate the case that you want to import and clic" on "pen.
*. !epending on the file format you choose, you will get an &mport window where you
have the option to select whether or not you want to import the grid geometry, any grid
properties, summary files and more.
,. Press on "K to complete the import. &f the unit system of the "eyword case differs
from the Petrel project you are importing into, you will get an option to either convert the
case or to change the units for your Petrel project. #ou will also be notified in a message
window of inconsistent "eywords or for "eywords that Petrel cannot import.
How to #partially% con)ert a Keyword Case to a Petrel Case
To convert a "eyword case to a Petrel case$
%. 3nce a "eyword case has been imported into Petrel you can right-clic" on the
simulation case in the Cases pane and select Con)ert to Petrel Case from the contet
menu.
'. 6ll the data in the file that Petrel understands will be imported into the &nput pane and
Model pane, and added to a new case.
1ote that not all data in the file can be imported and the generated case may not be
a )alid *C2&PS* case3 0eywords that Petrel cannot import or that are irrelevant to
Petrel model will be left in the new case as user "eywords. This can affect the eport of
the converted case since Petrel will not overwrite user generated "eywords. The user will
have to do some wor" on most converted cases to fi things up. The conversion process
writes a description of what it has converted and what it has not converted to the message
log. 9ead the validation log carefully after trying to eport a converted caseE
How to load simulation results
#ou can load simulation results on simulation cases that have previously been run$
%. 9ight-clic" on the simulation case in the Cases pane and select the 2oad simulation
results from the contet menu.
'. This will import the simulation results into the 'esults pane. From here you can select
the simulation result vectors for the case and plot them in Function windows or eport
them as summary data.
How to e(port summary data
To eport summary data from Petrel$
%. &n the 'esults pane right-clic" on the Dynamic Data folder and select *(port/ from
the contet menu.
'. :nter a file name in the *(port dialog window for the summary data file.
). &n the *(port dynamic result data dialog window select the result vectors and the
simulation cases to eport.
*. 5lic" on "K to complete the eport.
How to configure custom editor
#ou can configure a custom editor other than the -otepad program in Windows to view
the simulation case "eywords and the simulation print file$
%. For the Windows operating system, declare a new *n)ironment $ariable System "ey
named *D&T"' and insert the path to the editor you wishes to use.
'. 5lic" on "K.
-ote that Petrel has to be restarted in order to recogni=e the configuration of the new
editor.
Define simulation case dialog settings
The Define simulation case process dialog gives you the options to set up a simulation
case.
6n area at the top of the dialog gives you the option to create a new simulation case. &t
also allows you to choose the simulator and grid for the case.
The following options are available$
Create new case$ 5hoose this if you want to ma"e a new simulation case.
*dit e(isting case$ 5hoose this if you want to modify a simulation case. #ou can then
choose the case from the drop-down list.
Simulator4 5hoose the simulator to be used from this drop-down list.
Type4 5hoose how to model porosity heterogeneity in the simulation. #ou can choose
from single or dual porosity, or dual permeability models.
Grid4 5hoose the grid for the simulation from this drop-down list. The grid contains all
the properties and geometry defined for your model.
There are five tabs within the dialog, each of which holds information about the
simulation case.
Grid$ &n this you can set up the grid inputs and the simulator "eyword to which each
condition maps.
Functions$ &n this you can insert fluid models and roc" physics functions for the
simulation case.
Strategies$ &n this you can insert the development strategies for the case.
'esults$ &n this you can select the output re4uirements for the case.
+d)anced$ &n this you can specify the simulator version; for Front(im simulations
additional parameters can be set.
6t the bottom of the dialog there are seven buttons.
'un4 5lic"ing on this button will run the well simulation and eport the simulator
"eywords. The "eywords will appear on the Cases tab as an option within the simulation
case.
Chec!4 5lic"ing on this button will chec" the consistency of the simulation case
selections. &t will not run the full simulation.
+bort4 5lic"ing on this button will halt the current operation. &t is available only during a
run or chec" operation.
*(port4 5lic"ing on this button will eport the simulator "eywords without running the
simulation. The "eywords will appear on the Cases pane as an option within the
simulation case.
+pply$ 5lic"ing on this button will apply the current simulation case settings. The dialog
will remain open so that you can define more cases.
"K$ 5lic"ing on this button will apply the simulation case details, and then close the
dialog.
Cancel$ 5lic"ing on this button will abandon the current settings and close the dialog.
Grid tab #Define simulation case%
The Grid tab allows you to set up the grid inputs and the simulator "eyword to which
each condition maps. The inputs are shown in a table with the corresponding "eyword
and fracture chec"bo for each.
#ou can use the buttons above the table to add new inputs at any location in the table, set
the total number of inputs and re-order the inputs.
&n order to run a simulation, the &, /, and 0 permeabilities, net to gross ratio and porosity
must be defined. The other rows have been added for convenience and are not mandatory.
6dditional rows will be added as suggestions if alternative Types of simulation to (ingle
Porosity are selected. Petrel will loo" at the selected grid and try to assign grid properties
for the mandatory items.
6s an alternative to using a property, you can set a constant value over the whole grid.
;nchec" the bo net to the blue arrow and type the value into the input column to do
this. 9ows without data in the &nput column will be ignored if a simulation is eported or
run.
&f you change the simulator and there are "eywords in the table that are not supported by
the new simulator, simulation type or initiali=ation choice .from the Functions tab1, then
these will be colored grey in the table. &nvalid rows will generally give an error message
when the case is applied or eported.
Aocal grids can only be associated with the 2ocal Grid 'efinement "eyword,
transmissibility multipliers with the Fault Transmissibility Multiplier "eyword, and
64uifers or 64uifer folders with the +0uifer "eyword.
Functions tab #Define simulation case%
The Functions tab shows the roc" physics and initial fluid conditions for the simulation
case. The functions in your cases are listed on the left hand side.
#ou add functions to the list by selecting them from the drop-down list at the top. The
functions available in the drop-down list will depend upon the simulator and simulation
type selected. There can only be one function of each type in the list. Functions that have
already been added to the list are grayed out in the list and cannot be selected. &f you
change simulator or simulation type, functions that are no longer valid are colored grey in
the list and will give an error when the case is applied or eported.
#ou can edit functions that have already been added to the simulation case by selecting
them in the list. #ou can remove functions from the simulation case by selecting them in
the list and then clic"ing on the Delete selected row#s% in the table button above the list.
The following options are then available for you to define your selected function$
'egion inde( property4 (elect this chec"bo if you want to choose a region inde
property so that you can use different fluid data for different regions of the grid. The
region inde properties can be any discrete property, such as a segment, a =one number,
facies, and so forth.
&nitiali5e by e0uilibration4 This chec"bo only appears when the lac! oil fluids
model #P$T% function is selected. #ou select this chec"bo in order to initiali=e the
reservoir by e4uilibration. &f you unselect this chec"bo, then you must have provided the
grid properties P9:((;9:, (W6T, (+6(, 9( or P<;< and 98 or P!:W, in the +rid
tab, in order to do initiali=ation by enumeration.
*(port as table4 This chec"bo only appears when the 'oc! compaction function is
selected and you have chosen an :5A&P(: simulator. #ou select this chec"bo in order to
eport tables of pore volume multiplier as a function of pressure; otherwise, the 9oc"
compaction function is eported as the single value of roc" compressibility at a reference
pressure.
Table4 #ou insert here the appropriate function, for eample Saturation Function, when
you are defining 9el Perms, or &nitial conditions .or Fluid models if you are initiali=ing
by enumeration1 when you are defining <lac" oil fluids model. 6 row will be inserted for
each region when you select the property. 5lic" on the appropriate Drop subject here
button to drop each function into the table.
Strategies #Define simulation case%
&n the Strategies tab you can insert the development strategies for the case.
#ou use the buttons above the table to add lines to the table. #ou can then select a
development strategy from the &nput pane and clic" on the Drop de)elopment
strategies here button for a line to drop the strategy into the simulation case. The
development strategies time periods must not overlap.
#ou can define the segmentation of your wells for simulation by dropping a 6ell
Segmentation Set into the 6ell Segmentation Set field above the table.
'esults tab #Define simulation case%
&n the 'esults tab you can select the output re4uirements for the simulation case. The
available options are shown in five areas$
)! Properties
Aine +raphs
Fiscellaneous
(imulation logs
9eports
7D Properties #'*ST+'T%
This area defines the grid properties loaded from the simulator, specifically pore-volume,
pressure and saturation. #ou can enter the maimum number of streamlines available
together with their time of flight. -ote that, after running the simulation, you can apply a
settings filter to reduce the number of streamlines.
2ine graphs
#ou can select the time-based production functions that will be placed into a summary
folder for the simulation. 6ll functions are selected by default, but you can deselect any
that you do not need.
Miscellaneous
<y default, validation and simulation message files are only displayed if there are errors
to report. #ou can select an option that will always show these files.
#ou can choose to try to run a simulation even if Petrel case or eport validation fails.
This is of particular use to the user who has used the "eyword editor to complete a case
definition outside the !efine simulation case process.
#ou can choose to show the simulation console while the simulation is running, in
which case a 5ommand 5onsole will show during the simulation run.
#ou can specify that Petrel will as" you to load the results once the simulation run has
ended in case you do not wish to load the results at this time.
#ou can specify that input bul" data are removed when results are imported. These are
the potentially large 3PFG+9&! or :+9&! files that are input to the simulator. This
option saves dis" space. Petrel can easily regenerate these files from the case if they are
re4uired again.
Simulation logs
#ou can select which simulation logs are created and at what fre4uency they are output
from the simulation.
'eports
These options define a spreadsheet report that will be generated when the simulation is
run. #ou can choose the report content, including simulation console messages if
re4uired. #ou can also set the system to display a prompt for confirmation before the
results are loaded when the simulation is complete.
+d)anced tab #Define simulation case%
&n the +d)anced tab you can$
(pecify the simulator version
3pen the "eyword editor .see 0eyword :ditor1
(pecify the 4ueue in which to eecute the simulation, either local or remote. For more
details see 9emote (imulation (ubmission
(pecify the eport format for the grid data. The choices are$
3PF$ This uses the 3pen Petrel binary Format. This is the most compact format; it
supports all pillar geometry types; the porosity, permeability and -T+ data is also written
to the 3PF file. This is the default format for all simulators. -ote$ This format is only
supported by :5A&P(: %@@ H )@@ from version '@@,a.
+9!:5A$ This uses the I539- and 5339! "eywords. This format only supports
vertical and straight pillars; any curved or listric pillars will be straightened on eport,
introducing inconsistency between :5A&P(:GFront(im and Petrel.
:+9&!$ This is a binary version of the I539- and 5339! "eywords, so has the same
restrictions on pillar geometry. 6ll cell property data is written as "eywords. This format
is not available with Front(im.
+9&!$ This binary format gives the J,#,I coordinates of each corner of every cell. &t can
therefore represent all cell geometries and is supported by earlier versions of :5A&P(:,
but ma"es very large files. 6ll cell property data is written as "eywords. This format is
not available with Front(im.
&f you are using Front(im, you can also set Pressure solver, (aturation solver and ) phase
solver parameters. Petrel will select default entries for these, and you must ma"e changes
only if you fully understand the conse4uences. &f you have any doubts, please leave the
default selections.
Keyword *ditor
This Keyword *ditor allows you to edit "eywords and include files that ma"e up the
simulation dec". #ou can access the "eyword editor by pressing the Keyword *ditor
button on the +d)anced tab or from the contet menu on a case in the Cases pane.
The Keyword *ditor is split into two trees. 3n the left hand side you can find the
"eywords defined and used in the simulation case. #ou can display these either by section
or the include file structure by using the radio buttons called Sort by section or Sort by
include files.
The tree on the right hand side displays the "eywords that can be inserted into your
simulation case. The list will only show the "eywords that can be inserted for the section
you have selected on the left hand side tree, e.g. 9;-(P:5, +9&!.
#ou can insert a new "eyword into your simulation case by selecting the "eyword on the
tree on the right and pressing the &nsert button. 6 tet editor will open with the "eyword
where you can add the "eywordKs parameters. <y default the editor is set to Ficrosoft
-otepad. To change editor see Dow to configure custom editor. To get help on the
mnemonics of a "eyword there is a right-clic" menu option Documentation that will
open the "eywordKs help manual page.
5lic"ing on +pply or "K immediately updates the files on dis". The refresh button
cancels any changes made since last pressing 6pply or 30.
Petrel will comment "eywords and files to indicate who created the "eyword.
&f Petrel created a "eyword it adds the following comment 88333 Program generated
!eyword9 'emo)e this comment to pre)ent Petrel editing or remo)ing this !eyword9
This tells Petrel that only Petrel can change or remove this "eyword.
Petrel also commentsGtags files by adding the following comment to the top of the file
B88333 Program generated file9 +ny edits to this file will be lost on ne(t e(port from
Petrel9C This indicates that Petrel will overwrite this file and not preserve any changes
made by the user. &t is not a good idea to remove this comment from the top of the file.
To show how the "eywords are tagged, the "eywords are color-coded as follows$
lue type indicates a Petrel generated "eyword and part of a file that can be user-edited.
lac! type indicates a "eyword that has been edited or inserted by the user and which
Petrel will not overwrite.
'ed type is due to file being BtaggedC as Petrel generated. 1 Petrel will overwrite the
entire contents of this file, regardless of the tagging of the "eywords within the file. 6lso,
section head "eywords are shown in red.
For the "eywords on the left hand side of the dialog, selecting :ser !eyword from the
right-clic" contet menu will inform Petrel that the "eyword is controlled by the user and
that Petrel cannot overwrite this "eyword when eporting the simulation files to the
simulator. 5hoosing :ser !eyword for a section or an include file sets the entire file to
Petrel generated. &t is not recommended to change this tag.
To directly edit a "eyword from the left-hand side tree, double-clic" on the "eyword or
select *dit in the right-clic" contet menu.
When an editor is opened on a single "eyword and a save is performed in the editor,
Petrel will assume that the "eyword has been updated and that the user would li"e the
net eport not to overwrite the changes and, therefore, Petrel will automatically convert
the "eyword into a :ser !eyword.
To edit an entire include file, switch to the L(ort by include filesL and double-clic" on the
file name.
To change the order of your "eywords, use the up and down arrows at the bottom left of
the Keyword *ditor dialog.
&mported simulation case
#ou import an eisting case directly into the 5ases pane .see 5ases1. &mported cases
cannot be edited or viewed directly in the !efine simulation case process. Dowever, you
can edit their dec" manually using the 0eyword :ditor, and :port and 9un their
simulations from within Petrel.
Con)erting an imported case to a Petrel case
The Con)ert to Petrel Case utility reads an imported simulation and converts it into a
Petrel 5ase. 3nly simulations imported into the Cases pane can be converted.
-ote$ 6 converted case will usually need user correction before it will eport or run
successfully. The conversion process is epected to become more complete with
successive versions of Petrel.
To convert an imported (imulation, right-clic" on the simulation case in the Cases pane
and select Con)ert to Petrel Case from the contet menu.
6 new case and simulation are created that are named after the imported simulation case
with LM53-8:9T:!L appended. 6 report on how the conversion is progressing is
written to the message log. 6t the end of this process, you should review, edit and
complete the newly converted simulation using the !efine simulation case dialog settings
process and the 0eyword :ditor. Pay particular attention to removing any duplicated or
inconsistent "eywords.
#ou can visuali=e and edit the Petrel items, such as grids, properties, fluid models and
saturation functions that have been created from the converted "eywords.
The conversion process only converts a subset of the "eywords in the dec" into Petrel
items. The "eywords not converted are reported in the message log and remain in the
converted simulation as user "eywords.
The main classes of "eywords that are converted are$
5orner point geometry "eywords I539- and 5339!, or the +!F&A: and P:T+9&!
"eywords that import this data from binary files
Property array "eywords, such as P393, P:9FJ, -T+, (6T-;F, and so forth, from
the +9&!, :!&T, P93P(, 9:+&3-( and (3A;T&3- sections
<lac" oil P8T data
(aturation and roc" compaction functions
:4uilibration data
-otable classes of "eywords that are -3T converted are$
Fodifiers .such as :N;6A(, F;AT&PA# or 53P#1
<loc" centered geometry
A+9s defined using "eywords. The wor"around for both bloc" centered geometry and
local grid refinement is to initiali=e the model in :5A&P(:, writing out an :+9&! file
.see "eyword +9&!F&A:1, and import this to Petrel with the "eywords. The conversion
process then uses the geometry from the :+9&! file.
Fultiple e4uilibration regions with multiple fluid regions. 6ll the e4uilibration region
data will be imported into every fluid model. The user will have to correct the assignment
of initial conditions on the Fluids tab of the !efine (imulation 5ase process.
6ll (;FF69# and (5D:!;A: section "eywords
&n addition, note that some "eywords will be replaced by functional e4uivalents. For
eample, the +968&T# "eyword will be replaced by !:-(&T#; bloc" centered
geometry "eywords will be replaced by corner point geometry .read from an :+9&! or
+9&! file1.
The order of mitures of converted and remaining user "eywords is li"ely to need
correction by the user.
'emote simulation submission
Petrel can run simulations in :5A&P(: and Front(im either on your local P5, or on a
remote server. &n either case, you must have an installation of :5A&P(: (imulators on
your P5, version '@@2.% or later$ this includes an application called eclrun.ee which is
used by Petrel to submit simulation runs.
&f you wish to submit runs to a remote machine, you need to configure both Petrel and the
server. !etails of how to do this are supplied below.
To submit a remote simulation, you simply select the 4ueue you wish to send it to on the
+d)anced tab of the !efine simulation case process. The eclrun.ee application will
transfer the input files to the remote machine and submit the simulation.
Petrel can be configured to submit simulations to an A(F 4ueue. A(F .load (haring
Facility1 is a 4ueuing system provided by Platform 5omputing .www.platform.com1. &f
the Petrel 4ueue is configured to point to an A(F 4ueue, the simulation will be submitted
to the A(F 4ueue; otherwise, it will run in the foreground on the remote machine.
3nce a simulation is submitted, either locally or remotely, you can shut down Petrel.
To load the results, simply right-clic" on the simulation, or on a folder of cases on the
Cases pane, and select 2oad simulation results from the contet menu. Petrel will call
eclrun.ee which will fetch any available results bac" from the remote machine and then
load them into Petrel. This may be done as often as you wish during a simulation,
allowing you to chec" on its progress. When eclrun.ee detects that the remote simulation
is finished, it will clean up the files created on the remote machine. #ou can also set the
Petrel 4ueue to periodically chec" and load results automatically.
The eclrun.ee utility records information such as the A(F job number, the report step
reached, the error messages, etc. in the simulation log.
&nstalling Petrel support for remote simulation ; eclrun
PetrelKs support for remote simulation is provided by eclrun. This must be installed on the
local P5 and on all remote servers to be used for submitting the simulation andGor
running it.
6t present submitting remote simulation is supported to all platforms supported by
:5A&P(: H Front(im .i.e. 9ed Dat Ainu, (u(: Ainu, &<F 6&J, (;- (olaris1 e(cept
Microsoft 6indows.
6fter installing eclrun on all machines in your system, you must then configure Petrel to
use it.
&nstalling eclrun on your local PC
9un either the installer for the :5A&P(: (imulators provided with this version of Petrel
or the standard :5A&P(: installer, version '@@2.% or later.
-ote$ The last version of :5A&P(: (imulators installed must be the same on both P5 and
server.
&n addition to installing the simulators themselves, the installer will$
6dd the following eecutables to the macros directory, created in your :5A&P(:
installation$ eclrun.ee, plin".ee, pscp.ee
-ote$ plin" and pscp are part of the PuTT# implementation of 3pen((D. The full install
is available from http$GGwww.chiar".greenend.org.u"GOsgtathamGputtyG
6dd the macros directory to your system P6TD variable. #ou can chec" this in the
6indows Control Panel . System . +d)anced . *n)ironment $ariables
&nstalling eclrun on a remote :1&< or 2inu( ser)er
-ote$ in following these instructions, change all references to =ecl to the actual location of
your :5A&P(: installation.
%. &nstall :5A&P(: (imulators version '@@2.% or later on your server.
-ote$ The last version of :5A&P(: (imulators installed must be the same on both P5 and
server.
'. &nstall and enable inter-host communication.
eclrun uses ((D by default for inter-host communication. #ou must install and enable
((D for this to wor". &t may be that they are not installed by default .(olaris, 6&J1 and
will have to be pic"ed up from the operating system 5!s or from the relevant vendorPs
website and installed according to the supplied instructions. 3n Ainu, ssh is normally
installed as part of the standard pac"age. 5onsult your system documentation for details.
&f you prefer, you may instead use rsh and rcp for inter-host communication. This is
not recommended$ it is less secure, and from Ficrosoft Windows it is considerably
slower than ((D. Fost modern ;-&JGAinu installations disable rsh/rcp by default$
consult your system documentation for details on how to enable it. -ote that some
systems now install the "erberos version of rsh rather than the standard version$
behavior of this version varies. &n addition to using rsh, each user will re4uire a
.rhosts file in their home directory, listing the machines from which they wish to
connect. The precise format of this file varies between ;-&JGAinu dialects, but is
usually simply a list of machine names, one per line, of the form.
machine% user
.
.
machinen user
The file can also ta"e the format$
&P address user
or to be completely insecure
Q Q
which implies access to all machines and all users, although this may not wor" on some
Ainu platforms.
The .hosts file must also have the permissions -rw-------.
). 6dd the following lines to the system .cshrc file, or to each userKs .cshrc file if
preferred. The precise location of this file varies between ;-&JGAinu implementations,
but it is often /etc/csh.cshrc - consult your system documentation for details.
if . -e GeclGmacrosGReclrunsetup 1 then source GeclGmacrosGReclrunsetup endif
6lternatively, you may add these lines to each userKs personal file ~/.cshrc
:dit the file /ecl/macros/@eclrunsetup and ma"e the following changes$
%. (et the value of AFMA&5:-(:MF&A: to point to your FA:JAF license server for
:5A&P(: .setenv LM_LICENSE_FILE 732@server1
'. (et the value of :5AP6TD to point to your :5A&P(: installation location. .setenv
ECL!"#$ /ecl1
). (et the path variable to include the eclGmacros directory i.e. set
path%&'path /ecl/macros1, assuming the macros are installed under
/ecl/macros
Configuring remote simulation 0ueues in Petrel
The information that Petrel needs to submit remote runs is stored in a configuration file.
Petrel '@@7.% can read from three configuration files$ ;ser, 6ll ;ser and +lobal. (ee
5onfiguring Petrel for details on where configuration files are stored, how to edit them
outside Petrel, and how a (ystem 6dministrator can do this centrally and distribute the
configuration.
Nueues can be defined in any or all of the three configuration files. Petrel '@@7.% will
merge the 4ueue definitions when reading the configuration file on startup. Nueues of the
same name defined in the +lobal file will override those in the 6ll ;ser file, and both will
override 4ueues of the same name defined in the ;ser file.
5hanges made to 4ueue definitions in Petrel will be saved to the ;ser configuration file
when Petrel '@@7.% is closed.
To change 4ueue definitions in Petrel '@@7.%$
%. (elect Tools . System Settings
'. (elect the ,ueue definition tab.
). Fa"e your changes as described in the net pages and clic" "K.
+dd or delete a 0ueue
To add a 4ueue, clic" the +dd a new 0ueue button and fill in its details in the boes on
the right of the dialog.
To delete a 4ueue, select it in the list on the left and clic" the 'emo)e selected 0ueue
button
Set the Default 0ueue
(elect the re4uired default 4ueue in the list and clic" the Default button below the list.
The 4ueue that is selected as default will be used for new cases.
,ueue settings
The tet entry boes on the right of the dialog define the parameters of the 4ueue. These
are used to substitute for variables in the commands defined in the +lobal configuration
file when submitting, chec"ing or "illing simulation runs.
1ame4 This is the identifier by which the 4ueue is referred to by the simulation case.
Ser)er4 Fachine to submit the simulation to. Aeave empty for local runs. 9eplaces
S(:98:9S in a command.
'emote directory4 !irectory on the remote machine to run the simulation. 9eplaces
S!&9:5T39#S in a command.
Chec! e)ery4 Time interval .in minutes1 for fetching simulation results. 3nly used with
remote submission.
2SF 0ueue4 9eplaces SN;:;:S in a command.
Comms system4 Fessage passing system used for parallel runs. This may be left blan",
in which case the command uses the architecture of the remote machine to determine the
appropriate system. 9eplaces S53FF(S in a command.
Hostfile4 Aocation of hostfile for parallel runs. &f you are using the A(F 4ueuing
system, this should be left blan" as it is automatically generated by eclrun when running
under A(F. 3therwise, it is re4uired when running parallel simulation under Ainu
.ecept (+& 6AT&J systems1, &<FKs 6&J, or Windows P5 systems. 9eplaces
SD3(TF&A:S in a command.
:serid > Password4 This information is only "ept until Petrel eits - you will need to
re-type the userid and password when you re-run Petrel. &f userid or password is not
supplied, but is re4uired by the command, you will be prompted for this information
when the simulation is submitted on the remote machine. 9eplaces S;(:9&!S and
SP6((W39!S in a command.
&f you tic" the chec" bo :se same logon for all ser)ers, you only need to enter the
userid and password once. 3therwise, each 4ueue that uses a different server will need
the userid and password to be entered.
*diting the configuration file simulator settings
The information that Petrel needs to submit remote runs is stored in a configuration file.
Petrel '@@7.% can read from three configuration files$ ;ser, 6ll ;ser and +lobal. (ee
5onfiguring Petrel for details on where configuration files are stored, how to edit them
outside Petrel, and how a (ystem 6dministrator can do this centrally and distribute the
configuration.
The configuration file is a plain tet file in JFA format. #ou may edit it using any tet
editor.
-ote$ on most Windows systems, double clic"ing on an JFA file will open it in a web
browser, which does not allow you to edit it. &nstead, open your tet editor, and open the
file from the editor.
The file contains two sets of information$
The commands used to submit simulation runs, chec" their status and retrieve results,
and abort them
The 4ueues available in which to run simulations
6n eample of the configuration file is shown here$
T5onfigurationU
V
T(imulationU
T(imulation5ommandsU
T5ommand -ameWL:5A&P(: %@@LU
T(ubmitUeclrun X-v S8:9(&3-SY X-s S(:98:9SY X-4 SN;:;:SY X-d
S!&9:5T39#SY X-m SD3(TF&A:SY X-c S53FF(SY X--username S;(:9&!SY X--
passwd SP6((W39!SY eclipse S!6T6F&A:STG(ubmitU
TFetchUeclrun X--passwd SP6((W39!SY chec" S!6T6F&A:STGFetchU
T0illUeclrun "ill S!6T6F&A:STG0illU
TG5ommandU
T5ommand -ameWL:5A&P(: )@@LU
T(ubmitUeclrun X-v S8:9(&3-SY X-s S(:98:9SY X-4 SN;:;:SY X-d
S!&9:5T39#SY X-m SD3(TF&A:SY X-c S53FF(SY X--username S;(:9&!SY X--
passwd SP6((W39!SY e)@@ S!6T6F&A:STG(ubmitU
TFetchUeclrun X--passwd SP6((W39!SY chec" S!6T6F&A:STGFetchU
T0illUeclrun "ill S!6T6F&A:STG0illU
TG5ommandU
T5ommand -ameWLFront(imLU
T(ubmitUeclrun X-v S8:9(&3-SY X-s S(:98:9SY X-4 SN;:;:SY X-d
S!&9:5T39#SY X-m SD3(TF&A:SY X-c S53FF(SY X--username S;(:9&!SY X--
passwd SP6((W39!SY frontsim S!6T6F&A:STG(ubmitU
TFetchUeclrun X--passwd SP6((W39!SY chec" S!6T6F&A:STGFetchU
T0illUeclrun "ill S!6T6F&A:STG0illU
TG5ommandU
TG(imulation5ommandsU
T(imulationNueuesU
TNueue -ameWLAocalLGU
TNueue -ameWL9emoteL (erverWLbay)L 9emote!irectoryWLGsimL GU
TNueue -ameWLA(F(erialL (erverWLsunlinuconL A(FNueueWLserial)'L
9emote!irectoryWLGscratchL GU
TNueue -ameWLParallelL (erverWLsunlinuconL A(FNueueWLserial)'L
9emote!irectoryWLGscratchL 5omms(ystemWLmpiL DostfileWLhostfile.ttLGU
TG(imulationNueuesU
TG(imulationU
TGPetrel5onfigU
The SimulationCommands section defines the format for submit, fetch .load results1,
and "ill .abort1 commands for each simulator. Words surrounded by ZSP are variables,
replaced by Petrel when a simulation is run according to the 4ueue that has been selected
and other information entered by the user in Petrel. (e4uences surrounded by X Y are only
written if Petrel has a non-blan" value for the variable enclosed.
9ecogni=ed variables are$
S!6T6F&A:S$ -ame of the data file for the simulation
S8:9(&3-S$ 8ersion of the simulator to run
S(:98:9S$ Fachine to submit the simulation to.
S;(:9&!S$ ;serid on the S(:98:9S
SP6((W39!S$ Password on the S(:98:9S
S!&9:5T39#S$ !irectory on the remote machine in which to create a temporary
directory for running the simulation.
SN;:;:S$ -ame of 4ueue in A(F or other 4ueuing system
S53FF(S$ Fessage passing system used for parallel runs
SD3(TF&A:S$ -ame of hostfile for parallel runs.
SimulationCommands can only be edited via the global config file.
&f eclrun is installed, Petrel will, by default, write eclrun commands to the configuration
file when it is first created, or else 'ecl(pse.)at, 'e3**.)at and
'+ronts(m.)at commands, which do not support remote simulation. &f you wish, you
may edit the configuration file and substitute your own local customi=ed commands for
running simulations using the above variables. (chlumberger will charge for supporting
any such custom installation.
#ou may edit the eclrun commands to use any of the options described in the section in
;sing eclrun.ee to submit and monitor simulations from the command line.
The Simulation,ueues section sets up details of the various machines to which remote
jobs may be submitted. These are best created and edited using the interface in Petrel,
described in 5onfiguring remote simulation 4ueues in Petrel.
:sing eclrun9e(e to submit and monitor simulations from the command line
eclrun can be used at the command prompt to run simulations. 6lternatively, the options
described below can be added to the Petrel configuration file to change its behavior when
called by Petrel.
For eample$
eclrun -s myserver -4 my4ueue -u myuserid -p mypasswd eclipse F#!6T6.!6T6,
will submit your simulation run to the remote machine myserver. &n the process, eclrun
will analy=e your data file to find all the re4uired included files, =ip them up, transfer
them to the remote machine in a temporary directory, un=ip them, and submit the
simulation job. &t will also store the details of your job in a file called
MYDATA.ECLRUN, and report them to you in the message log file MYDATA.MS. This
can be displayed in Petrel by right mouse clic"ing on the simulation in the Cases pane
and selecting Show simulation log from the contet menu. &t is automatically displayed
if it contains any error messages.
To get the results bac", use the command
eclrun -p mypasswd chec" F#!6T6.!6T6
This will read the details of your job from the MYDATA.ECLRUN file, connect to the
remote server to as" for any results. The server will =ip up any results files available, and
the local machine will download them and un=ip them. &t will also update the log file with
the present status of the job.
The full usage of the command is$
eclrun XoptionsY P93+96F X!&9:5T39#[F&A:Y
where
P'"G'+M is one of$
eclipse, e)@@, frontsim, flogrid, flovi=, office, schedule to run the specified application
chec" to chec" on status of previously submitted job
cleanup to force cleanup of remote wor"ing directory
"ill to abort a 4ueued or running job
D&'*CT"'? is the wor"ing directory for interactive apps. The default is the current
wor"ing directory
F&2* is the name of the input data file. This is re4uired for eclipse, e)@@, frontsim,
chec", cleanup, "ill. &t may include leading path and trailing etension with the options
,h- ,,help
Q show a help message and eit
,s S./SE01E0- ,,su)server%S./SE01E0
Q (;<(:98:9 is the &P address or name of the submission server you want to submit
the job from
,2 3.E.E- ,,2ueue%3.E.E
Q submit the simulation job to N;:;:
,u .SE0I4- ,,username%.SE0I4
Q ;(:9&! on (;<(:98:9. !efaults to local userid.
,p !"SS54- ,,pass67%!"SS54
Q password for (;<(:98:9
,7 4I0- ,,7(rector8%4I0
Q directory on (;<(:98:9 host where simulation is to run
,v 1E0SI9N- ,,vers(on%1E0SI9N
Q version to run; defaultWlatest
,:- ,,:eepcon+(;
Q 0eep an eisting configuration file :5A.5F+ file if found. This is not recommended$
better to use :5A.5F; in your home directory, or :5A.5F6 in the same directory as the
data file. -ote that :5A.5F; is not transferred to remote servers, but :5A.5F6 is.
,m $9S#FILE- ,,mach(ne+(le%$9S#FILE- ,,host+(le%$9S#FILE
Q name of file containing the hostnames of the machines to be used for parallel
processing. &f D3(TF&A: begins with \ it is ta"en as name of environment variable from
which host file is to be constructed
Q 4e+ault%'LS/_$9S#S - this means this option is not re4uired if using the A(F
4ueueing system, as the hostfile will be created automatically from the list of processors
supplied by A(F
Q -ote that you may have to prefi the \ with ] to avoid shell substitution
,,comm%C9MM
Q Fethod of inter-process communication for parallel runs. -ormally not necessary as
system will determine best available. 8alid values are$
- pvm .all systems1
- mp( .FP& with ethernetGgigabit, all system, default on (;- H (+& H Ainu ecept
6lti1
- sp2 .FP& with (P' switch, &<F only, default on &<F1
- m8r .FP& with myrinet, Ainu only1
- sca .(56A& version of FP& with best available switch, Ainu only1
- alt .FP& with -umalin" switch, Ainu 6lti 2*-bit only, default on 6lti Ainu1
,,protocol%!09#9C9L
Q Protocol and method of authentication for inter-hostcommunication. 5hoices are$
- unsecure $ uses rsh H rcp, must have .rhosts set up;
- password $ uses ssh H scp with password, must use ,,pass67 option unless
running from console.
Q 6 future version will support secure "eys.
,e E<EN"ME- ,,e=ename%E<EN"ME
Q run eecutable :J:-6F: instead of P93+96F.:J:. &f no path is given, loo"s in
normal places. -ote that the path given must be valid on the eecution machine
>nocleanup
Q !isable the automatic removal of files on remote machine after run has finished
,,7e)u;%4E/.?
Q !ebug messages. 5hoices are$
^ none
^ file - sends debug messages to file with suffi eclrunMdbg
^ both - sends debug messages to screen and the debug file
Define simulation case dialog +d)anced tab
&n this tab you can$
(pecify the simulator version
3pen the 0eyword :ditor
(pecify the 4ueue in which to eecute the simulation, either Aocal or remote. For more
details see 9emote simulation submission
(pecify the eport format for the grid data. The choices are$
%. "PF$ this uses the 3pen Petrel binary Format. This is the most compact format; it
supports all pillar geometry types; the porosity, permeability and -T+ data is also written
to the 3PF file. This is the default format for all simulators. -ote$ This format is only
supported by :5A&P(: %@@ H )@@ from version '@@2.%. 6lso, there is a "nown issue that
this format uses a lot more memory with :5A&P(: %@@ '@@2.% in parallel, and we
recommend using one of the other formats.
'. G'D*C2$ this uses the I539- and 5339! "eywords. This format only supports
vertical and straight pillars; any curved or listric pillars will be straightened on eport,
introducing inconsistency between :5A&P(:GFront(im and Petrel.
). *G'&D4 this is a binary version of the I539- and 5339! "eywords, so it has the
same restrictions on pillar geometry. 6ll cell property data is written as "eywords. This
format is not available with Front(im.
*. G'&D4 this binary format gives the ,y,= coordinates of each corner of every cell. &t
can therefore represent all cell geometries and is supported by earlier versions of
:5A&P(:, but ma"es very large files. 6ll cell property data is written as "eywords. This
format is not available with Front(im.
&f you are using Front(im, you can also set Pressure solver, (aturation solver and ) phase
solver parameters. Petrel will select default entries for these, and you must ma"e changes
only if you fully understand the conse4uences. &f you have any doubts, please leave the
default selections.
Troubleshooting remote simulation
9emote (imulation, because it involves more than one computer system, is a comple
process and unfortunately, this compleity means there are more opportunities for things
to go wrong. This section is designed to help you solve problems if they occur.
@Command not found@ or @1o such file or directory@ errors
&f you receive variants on Lcommand not foundL, follow the steps here to chec" which
command is missing.
Chec! eclrun is installed on your local PC
3pen a command prompt window .clic" the Windows (tart button1, choose Programs .
+ccessories . Command Prompt1
6t the command prompt, type eclrun. #ou should see the following$
5$]Ueclrun
usage$
eclrun XoptionsY P93+96F F&A:
where P93+96F is one of$
eclipse, e)@@, frontsim
or chec", to chec" on status of previously submitted job
or cleanup, to force cleanup of remote wor"ing directory
or "ill, to abort a 4ueued or running job
F&A: is the name of the data file for the simulation job
&t may include leading path and trailing etension
or
eclrun XoptionsY P93+96F X!&9:5T39#Y
where P93+96F is one of$
office, flovi=, flogrid, etc.
!&9:5T39# is the wor"ing directory
defaultWcurrent wor"ing directory
;se eclrun --help for more information
This version of eclrun was built on '@@2-@*-'7
eclrun$ error$ P93+96F not specified
5$]U
(imilarly, type pl(n: and pscp at the command prompt. For each command, you
should receive a usage help message.
Finally, type eclrun tests8s. #ou should receive the following response$
5$]Ueclrun testsys
ReclrunRpc
ReclrunR]
&f you get a Lcommand not foundL error message for any of the above commands, your
installation is incomplete. Please follow the instructions in &nstalling eclrun on your local
P5 or the &nstalling Petrel support for remote simulation _ eclrun section.
Chec! eclrun is installed on your remote ser)er
Aog on to your server. .&f you donKt "now how, see 5ommunication or connection errors1.
6t the command prompt, type eclrun tests8s. #ou should receive a response
similar to the following$
S eclrun testsys
ReclrunRlinu
ReclrunRG
S
&f not, eclrun is not correctly installed on your server. Please as" the system
administrator to follow the instructions under &nstalling eclrun on a remote ;-&J or
Ainu server in the &nstalling Petrel support for remote simulation _ eclrun section.
eclpython4 1o such file or directory
&f you receive the following error on your ;-&J or Ainu server$
S eclrun testsys
GusrGbinGenv$ eclpython$ -o such file or directory
S
This indicates that your environment settings have not been set up to find eclp8thon.
#ou can verify this by typing$
S which eclpython
eclpython$ 5ommand not found.
S
Please follow the instructions under the heading ;pdate the system .cshrc in the
&nstalling Petrel support for remote simulation _ eclrun section.
Communication or connection errors
&f you receive error messages of the form B;nable to connect to myserverC, try the
following tests.
&f it is the first time you tried to submit to a particular server from your P5, try again.
First-time connections have to store the remote serverKs LsignatureL in the Windows
registry, and this sometimes fails. 3ften, simply repeating the submission wor"s.
Chec! that your PC can communicate with your ser)er 8 if you are using the default
password protocol
3pen a command window and type pl(n: servername. #ou will be prompted for
your userid and password. &f you have not connected to the server before, you may also
be as"ed for permission to store the serverKs signature in the local cache. 6nswer yes.
5$]Uplin" myserver
login as$ user%
user%RmypcKs password$
Aast login$ Tue /an %@ %'$@%$*' '@@2 from mypc.bigoil.com
S eit
5$]U
Chec! that your PC can communicate with your ser)er 8 if you are using the
unsecure protocol
&f you have configured Petrel and eclrun to use the unsecure protocol, by adding the
option ,,protocol unsecure to the submit command in the global configuration
file, you should test communication as follows$
5$]Ursh myserver eclrun testsys
ReclrunRlinu
ReclrunRG
-ote$ the Ficrosoft Windows version of the rsh command is very slow. #ou are strongly
recommended to use the secure protocol, which is both more secure and much 4uic"er.
&f you receive an error message of the form
myserver.bigoil.com$ Permission denied.
rsh$ canKt establish connection
it means that your server is not configured to allow you to connect. There are two
possible causes for this$
#our .rhosts file on the server does not list your P5 name
#our server is not configured to allow connections using this protocol.
5onsult your system administrator if you need assistance resolving these problems.
?ou submit a simulation from Petrel and nothing happens
&n most cases, if you submit a remote simulation run from Petrel and it fails with an error,
the error message will be written to the simulation log. Petrel will display the log when
the submit command finishes. &f the command is successful, it will write the @o)(7 to
the simulation log. #ou can chec" the simulation log by right-clic"ing on the simulation
on the Cases pane and selecting Show simulation log from the contet menu.
Dowever, errors in the +lobal configuration file cannot be reported this way. &f eclrun
cannot parse the command line sent to it by Petrel, it just generates a low-level system
error message and eits immediately.
To chec" if this might be your problem, on the 'esults tab of the De!ine simulation "ase
process, tic" the Show simulation console option. (ubmit your simulation again. &f a
Windows command prompt window appears, displays some tet, and almost immediately
disappears, it almost certainly means that the submit command is incorrectly configured
in the +lobal configuration file.
The resolution is to carefully chec" the contents of your +lobal configuration file. (ee the
instructions under :diting the global configuration file simulator settings page.
?our simulation runs lea)e files behind on the ser)er
Eclrun copies your simulation input to a temporary directory on the server, and copies
the results bac" to your P5 when you load results in Petrel. &f it detects that the run is
finished, it will also remove the temporary directory on the server, after it has copied the
results bac" to the P5.
&f files are left behind on your server, it could be because$
6n error occurred during the submission, simulation, or fetching of results. &n this
situation, eclrun does not delete any files so that you can determine the cause of the
error, and salvage any useful results from the simulation. &f you "now why the error
occurred, it is safe to delete the temporary directory.
#ou did not as" Petrel to load results after the run had finished. Eclrun only deletes
the temporary files on the server when they have all been downloaded to the local P5
after the run has finished. &f you loo" at the results of a simulation halfway through,
decide itKs wrong in some way, then go on to submit another case without ever bothering
to "ill or fetch the final results of the first case, they will stay on the server. #ou should
always fetch results or abort simulations to ensure your server does not fill up with
LorphanedL simulations.
Petrel fails to fetch results from the ser)er
#ou right clic" on the simulation on the Cases pane in Petrel, select 2oad simulation
results, and nothing happens. There are several possible causes for this$
The simulation is very large. &f the simulation output files are very large, it may simply
be ta"ing a long time to download them from the server. &f on the 'esults tab of the
De!ine simulation "ase process, you tic" the Show simulation console option you will
see the progress of the download in a Windows command prompt window.
The results have downloaded but Petrel is idle. There is a "nown issue in Petrel '@@7.%
that if you are wor"ing in another window, Petrel goes to sleep and does not always
detect when it should start loading results. (imply move the mouse, and if it is not the
active application, clic" on the Petrel main window title. &t should wa"e up and load the
results.
The eclrun state file has been deleted. The eclrun application stores information
about a simulation run in progress in a file called MA0.N.ECL0.N. This stores things
such as the name of the server, and the name of the temporary directory on the server
where the simulation is running. &f this file is deleted during the run, eclrun will be
unable to download the results.
!o not delete the .eclrun file during a simulation run. &f this has happened for some
reason, do the following$
%. 9ight-clic" on the simulation on the 5ases pane and select (ettings
'. 3n the info tab, note the name of the directory where the !6T6 file is located.
). ;se ftp or a similar file transfer tool to copy the output files from the server to this
directory on the P5. The files on the server will be found in a directory called
useridMmyrunMyyyymmddhhmmss
*. Aoad the results into Petrel
,. 9emove the files on the server.
Simulation 'esults
(imulation results come in four forms$
%. Summary $ectors - These are stored on the 'esults tab and may be displayed in the
function window or in the map window. (ee Plotting (imulation 9esults using the data
displayed on the 9esults tab of The Petrel :plorer for details of wor"ing with these
plots.
'. Properties _ These are stored in the appropriate )! grid and displayed in much the
same way as any other grid property.
). Streamlines _ These are stored on the )! grid and displayed in a )d window. (ee
(treamlines for more details
*. Simulation logs _ These are stored on a per-simulation basis and are accessed using
the Aog folders on the &nput tree. They can be displayed in '!, )!, well section and
intersection windows. They are sometimes referred to as !ynamic Aogs.
&f the simulation was run directly from Petrel then the results will be imported
automatically to the appropriate case and model respectively.
&mport of Simulation Data
The first step is to import the files containing the simulation data. (ee Dow to import a
0eyword 5ase into Petrel. 3n import of simulation data, Petrel will create the following
folders$
6 new case in the Cases pane, where the simulation dec" "eywords and include files
will be stored and managed.
6 grid model in the Models pane, where the hori=ons, faults and properties can be
found. 6dditional files can be imported to the grid by right-clic"ing on the #ri$, the
%aults and the &ro'erties folder
(ummary vectors will be imported into the 'esults pane in a Dynami" Data folder for
display in function windows and for use with the !ynamic !ata calculator.
6dditional data objects can be converted into Petrel objects by selecting the Con)ert to
Petrel Case option from the right-clic" contet menu from the Cases pane. (ee Dow to
.partially1 convert a 0eyword 5ase to a Petrel 5ase.
(ummary data can also be eported in a Petrel 6(5&& format; see Dow to eport
summary data.
Simulated properties
(imulated properties are imported into Petrel in much the same way as any other
properties in Petrel. The only difference between simulated properties and standard
properties is that they may also have time steps associated with them. &f a property is
dropped into the time step player then it can be animated in time. Petrel will show all the
properties with the same template as the chosen property, in their date order.
:sing the Time Step Player
The time player is used to play through data time-step by time-step. &t gives an animated
picture of how the data changes with time. &t can for instance be used to compare time
dependant behavior of one property across several wells, or that of several properties
within one well. For information on how to use the Time (tep player, see Timestep
Player.
Ternary plots
Ternary plots are )! grid properties that display the relative proportions of the fluid
saturations .oil, water, gas1 in each grid cell, for each time step. The cell colour represents
the proportion of saturation in each cell.
Ternary properties are calculated automatically for )-phase cases when loading results to
Petrel. Dowever, if you need to calculate ternary plots for '-phase cases, or in other
circumstances, the wor"flow is outlined below.
Ternary plots wor!flow
%. 9ight-clic" on the Properties folder for the simulation grid you wish to create a
ternary plot and select Settings from the contet menu.
'. &n the (ettings dialog go to the Composite tab.
). &nsert a new ternary property definition by clic"ing on the +ppend item in the
table button. :nter a name and select the Type to be Ternary. 6ccept the default +eneral
template.
*. (elect the properties in the pull-down selectors at the bottom of the dialog. +enerally
map 9$ .red1 for gas, +$ .green1 for oil and <$ .blue1 for water. :nsure you select the
same time step for each property.
,. Toggle on -ormali=e to ma"e sure that all the saturations add up to % .%@@S1.
2. +enerally clic" on the button to create plots for each time step.
7. 5lic" on +pply to save the settings and on the *(ecute button to create the properties.
The properties are created in a folder beneath the simulation case with the name supplied
in step ) above.
The ternary plots can be played using the Time Player. Note: if other windows capable
of responding to the Time Player are active, you may eperience flashing or other
unepected behavior. +o to the Windows tab and toggle off such windows.
$ector plots
8ector plots allow the creation of )! vectors from properties, either static or recurrent
that are normally viewed as individual &,/,0 components. The output is a property with a
)! arrow in each grid cell representing the vector of the combined components.
:amples of such properties are Permeability, Transmissibility .in the .&-&T folder1 and
the 8:A35&T# .fluid velocities1 "eyword which, in Petrel, is added as an 6dditional
Property in the 'esults tab of the De!ine simulation "ase process.
The vector property is calculated from the main &ro'erties folder for the simulation case
)! grid or. &f a single property is calculated .for a single timestep1, only one property is
created. &f properties are created for all timesteps in the simulation a folder is
automatically created.
$ector plots wor!flow
%. 9ight-clic" on the Properties folder for the simulation grid you wish to create a
ternary plot and select Settings from the contet menu.
'. &n the (ettings dialog go to the Composite tab.
). &nsert a new vector property definition by clic"ing on the +ppend item in the
table button. :nter a name and select the Type to be (e"tor. 6ccept the default +eneral
template
*. (elect the properties in the pull down selectors at the bottom of the dialog. Fatch up
the &Q, /Q and 0Q dialogs with the appropriate properties. :nsure you select the same
time step for each property.
,. +enerally, clic" on the icon to create plots for each time step if wor"ing on recurrent
properties.
2. 5lic" on +pply to save the settings and the *(ecute button to create the properties.
8ector plots are displayed in the )! window. To display the arrows the solid fill will have
to be removed from the Style tab of the main Properties folder.
&t is also preferable to restrict the display to either a single 0 layer or a small area of
particular interest for clarity.
The appearance of the arrows may be modified in the Style tab in the (ettings dialog for
the vector plot property.
General intersection contour display
This functionality allows you to display property values on a +eneral &ntersection,
contour them and smooth the contours as re4uired. &t is assumed this will be used with
simulation results .(W6T, (3&A, P9:((;9:, etc.1 to demonstrate ZfrontsP in the
displayed property. .(ee also &so(urfaces display1.
Wor"flow$
%. !isplay a property in the )! viewer.
'. &nsert a General &ntersection from the Interse"tions folder by selecting &nsert
general intersection from the right-clic" contet menu.
). Position intersection using icons at the bottom of the window and using hot"ey .F1.
*. 9emove the property from display.
,. 5lic" on the Toggle )isuali5ation on plane button .located bottom left1, or press 5trl-
b, and select a property to display on the plane.
2. !ouble-clic" on the property name to open the Settings dialog, and while the Toggle
)isuali5ation on plane button is enabled go to the &ntersection tab on the Style tab of
the property
7. &n the Show group, clic" Contours to activate the 5ontour lines, 5ontour annotation
and 5ontour solid groups.
>. 5lic" to show the 5ontour lines and 5ontour solid, and set the parameters as
necessary.
?. &n the Show group, select the amount of resolution and smoothness.
This wor"flow does not wor" with an & or / intersection.
Aocal +rid sets and the +lobal grid should be treated as separate items for this process
and not contoured together.
&soSurfaces display
This process permits the user to create surfaces of a constant property value from a )!
grid property. &t is envisaged that this will be used with simulation results .(W6T, (3&A,
P9:((;9:, etc.1 to display ZfrontsP and how they move through a grid with time. .(ee
also +eneral intersection display1
&soSurfaces wor!flow
%. !isplay a property in the )! viewer _ generally a time dependent property from a
simulation run. (elect a time step which includes the value of the &so(urface you want to
create.
'. 3pen the Settings menu for the time step property .!ouble-clic" on the time step or
select Settings from the right-clic" contet menu.
). 5hec" the Statistics or Histogram tabs for the data range.
*. +o to the Style tab and the &soSurfaces sub-tab.
,. +ppend item in the table and provide an appropriate &sovalue. 5lic" on +pply
2. &n order to view the surface you will need to modify the property display in one of
several ways$ .note that if you clic" off the property display, the &so(urface goes tooE1
&n the Style tab of the Settings for the main &ro'erties folder you may clic" off Show
of (olid to leave just the cell outlines in the display.
!isplay the Property player select the De!ine simulation "ase process under
Simulation folder in the Processes pane. The Property player will appear on the far right
hand side of the )! viewer. ;se, and to slice the property in an appropriate location that
does not interfere with the &so(urface.
+dditional features
;se the +pply to all similar obAects in the same folder button to create an &so(urface
with the selected value in all timesteps of the property. <y using the time player it is
possible to view the movement of the surfaceGfront through time.
;se the property filter on the Filter tab in the Settings dialog for the main Properties
folder to restrict the &so(urface display to just an area of interest.
The &so(urface may be colored .and contoured1 using another property as a template. The
simplest illustration of this is to use the !:PTD property from the &nit folder .if
available1. &n the &so(urfaces tab, in the 5olor Type drop-down, select As 'ro'erty) and
from the &nit folder, clic" on the !epth property .single clic" on the name1 then clic" on
the blue arrow net to Z6s propertyP. 5lic" on +pply.
&f the &so(urface appears dim, you may add an additional light source. +o to the
Windows tab, right-clic" on the 2ight Sources folder and select &nsert light source from
the contet menu. The additional light source may be further modified by going to the
Settings for that light source.
Properties on Aocal +rids may be included or ecluded from the &so(urface calculation
and display by toggling them on or off in the tree.
Simulation logs
(imulation logs are generated when you select the 'FT, P2T and Segment options in the
Simulation 2ogs section of the 'esults tab of the Define simulation case dialog. 6
(imulation log is a time-based collection of well logs. Please refer to the reference
documentation of the simulator for details.
(elect dynamic simulation results
The (imulation logs have +lobal Templates associated with them in the same way the
normal logs do. They are available in the folder &nput tree8B6ells8BGlobal well logs 8B
Simulation logs. There may be sub-folders for 9FT, PAT and (egment, depending upon
the options you have selected for the case.
(imulation logs can be displayed in these windows$ '!, )!, Well section and
&ntersection.
To display a log corresponding to a given time$
(elect a window for display.
&dentify the well .in the &nput tree1 and display it.
(elect the log from the (imulation logs folder under the well trace.
5hoose a time from the Time Player drop-down list.
&f a log eists for the selected time it will be displayed. Aogs can be animated through
time using the Time Player controls. (ee Timestep Player.
6ll other aspects of dynamic log display are the same as for regular logs, including the
control of properties and display of logs for all wells. The only difference is that you have
to select a time using the Time Player. (ee Templates and well logs. &n particular, you can
display a log at a given time for all wells by using the global log template visuali=ation
tic"-bo.
<e aware that two different simulation logs may not contain data for the same time-step.