Skip to content

Commit 23b9c67

Browse files
committed
More OPM Flow job documentation
1 parent 6ad94d0 commit 23b9c67

File tree

10 files changed

+106
-2
lines changed

10 files changed

+106
-2
lines changed
20.7 KB
Loading
87.9 KB
Loading
19.8 KB
Loading
55.4 KB
Loading
13.2 KB
Loading
21.2 KB
Loading
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
+++
2+
title = "Add a New Well"
3+
4+
weight = 40
5+
+++

content/opm-flow-integration/CreateNewJob.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ weight = 20
88

99
ResInsight refers to OPM Flow Simulations as OPM Flow Jobs. They are located in the Scripts/Jobs tree, shown in both the 3D Main Window and the Plot Main Window.
1010

11-
You can create a new job in two ways: From an already loaded grid case or from a .DATA file located on a local or network disk drive. In both cases, ResInsight creates a copy of the provided input in the selected working folder, keeping the original files unmodified.
11+
You can create a new job in two ways: From an already loaded grid case or from a .DATA file located on a local or network disk drive. In both cases, ResInsight works on a copy of the provided input in the selected working folder, keeping the original files unmodified.
1212

1313
### Create job from grid case
1414

@@ -25,3 +25,8 @@ Go to the Scripts/Jobs tree, right-click on the Jobs folder, and select "New OPM
2525
You will then be asked to select a working folder, where the job will store all input to and all output from the OPM Flow simulation.
2626
It is recommended to use an empty folder.
2727

28+
### Duplicate an existing job
29+
30+
If you want to create a copy of an existing job, right click on the existing job in the Scripts/Jobs tree and choose *Duplicate...*
31+
32+
You will be asked for a working folder for the new job. All other settings will be copied over from the existing job.

content/opm-flow-integration/JobProperties.md

Lines changed: 45 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,4 +6,48 @@ weight = 30
66

77
### Overview
88

9-
9+
When you select an OPM Flow Job in the Scripts/Jobs project tree, the property editor allows you adjust the job settings.
10+
11+
![Job Properties Overview - OPM Flow](/images/opm-flow-integration/jobproperties.png)
12+
13+
### General Group
14+
15+
**Name**: The name used for the job. The name will also be used for the generated DATA file that is sent to OPM Flow when you start the job.
16+
17+
**Input Data File**: Shows the input selected when the job was created. It is a read only setting. If you want to use a different input file, you will have to create a new job.
18+
19+
**Working Folder**: This is the folder where the generated DATA file will be saved, and where the output from the OPM Flow Simulation will we written. It is recommended to not share this folder with other jobs, as this might cause files to be overwritten or corrupted.
20+
21+
**Add Runs to Ensemble**: If this option is turned on (checked), the output from a simulation run will be written into a new sub-folder in the working folder every time you run the job. The first time you run, output will be in "run-0", then "run-1" and so on. The *Advanced* section at the bottom of the properties editor shows you what the next run ID will be and allows you to reset this to 0.
22+
23+
Additionally, the output from each run will automatically be added to both grid and summary ensembles in ResInsight, i.e. adding new realizations to ensemble summary plots.
24+
25+
### New Well Settings Group
26+
27+
The [Add a new well]({{% relref "AddNewWell" %}}) page describes how to use these settings.
28+
29+
### OPM Flow Group
30+
31+
**Run**: Click the Run button to start the OPM Flow Simulation. Refer to the [Running an OPM Flow Job]({{% relref "RunningOpmFlowJobs" %}}) page for more information about this.
32+
33+
**Pause before running OPM Flow**: When this option is turned on (checked), ResInsight will generate all the input for OPM Flow in the working folder, and then ask the user if the job should be started or not:
34+
35+
![Job Pause - OPM Flow](/images/opm-flow-integration/opmpause.png)
36+
37+
This allows you to manually check and/or edit the generated DATA file in a text editor before OPM Flow is started.
38+
39+
**Process Control**, **Simulator Options**, **Solver Settings**, **Comvergense Tolerances**: These groups allows you to control the command line parameters sent to OPM Flow when you run the job. The default settings are read from the [OPM Flow global preferences]({{% relref "OpmFlowPreferences" %}}) when the job is first created.
40+
41+
### Date Settings Group
42+
43+
![Date Settings - OPM Flow](/images/opm-flow-integration/datesettings.png)
44+
45+
*NOTE*: These settings only works if the input DATA file contains DATE keywords.
46+
47+
**Stop Simulation at Date**: If this option is turned on (checked), the simulation will stop at the selected date (an END keyword will be inserted).
48+
49+
**Append Extra Dates**: If this option is turned on (checked), extra dates will be added at the end of the schedule section.
50+
51+
**Number of Dates to Append**: Set how many DATE keywords to append.
52+
53+
**Interval**: The interval in either days or months between each added DATE keyword.
Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
+++
2+
title = "Running an OPM Flow Job"
3+
4+
weight = 50
5+
+++
6+
7+
### Start the job
8+
9+
Once a job has been properly configured, you can start the job in two ways:
10+
11+
- Right click the job in the Scripts/Jobs tree and choose "Run..."
12+
- Click the "Run"-button in the OPM Flow group in the job properties
13+
14+
ResInsight will now write the necessary input data for OPM Flow to the selected working directory. The user interface will be blocked while this is done.
15+
16+
Once the input data has been written, ResInsight will launch OPM Flow as specified in the [OPM Flow preferences]({{% relref "OpmFlowPreferences" %}}).
17+
18+
- WSL will be used on Windows if selected
19+
- MPI will be used if selected
20+
- The selected command line parameters from the job properites will be added
21+
22+
The resulting command line used to lauch OPM Flow will be shown in the ResInsight *Messages* window.
23+
24+
### Monitor the job progress
25+
26+
Once the OPM Flow process has been started, the ResInsight user interface will unblock, and you can use it as normal. The job properties of the started job will change into a running state, with two items available:
27+
28+
![Run Properties - OPM Flow](/images/opm-flow-integration/jobpropertiesrun.png)
29+
30+
**Working folder**: Shows where the OPM Flow job input and output data files can be found
31+
32+
**Stop**: Allows you to stop the job. You will be asked for confirmation.
33+
34+
![Job Progress - OPM Flow](/images/opm-flow-integration/jobprogress.png)
35+
36+
The Scripts/Jobs tree will show the job progress and the warning count found in the OPM Flow log output. Any line starting with either *Warning* or *Problem* is counted as a warning.
37+
38+
When the job has completed, *Done* will be shown in the progress field. If the job failed for some reason, the progress field will turn red, and if there are any log lines starting with *Error*, the error count will be shown. There could also be error messages shown in the ResInsight messages window.
39+
40+
### Inspect the OPM Flow log
41+
42+
![Job Log - OPM Flow](/images/opm-flow-integration/joblog.png)
43+
44+
The log output from an OPM Flow job could be inspected by right clicking the job and selecting *View Log...*. This can be done while the job is running or after it has failed or completed.
45+
46+
Right clicking in the log window gives you the option to select all the text and copy it to the clipboard, so that you could copy it to a text editor for closer inspection.
47+
48+
### Running multiple jobs
49+
50+
ResInsight allows you to run as many jobs as you want at the same time, only limited by the available computing resources.

0 commit comments

Comments
 (0)