You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To build dune and the corresponding OPM master branches from source (e.g., you are a macOS user), you can run the script
37
-
`./build_dune_and_opm-flow.bash`, which in turn should build flow in the folder ./build/opm-simulators/bin/flow (for macOS users the dependecies such as boost can be installed using macports).
38
-
If you are a Linux user (including the windows subsystem for Linux), then you could try to build Flow with mpi support,
39
-
by running the script `./build_opm-flow_mpi.bash` instead of `./build_dune_and_opm-flow.bash`.
36
+
If you are a Linux user (including the Windows subsystem for Linux), then you could try to build Flow from the master branches with mpi support, by running the script `./build_opm-flow_mpi.bash` (See the [_CI.yml_](https://github.com/cssr-tools/expreccs/blob/main/.github/workflows/CI.yml)), which in turn should build the executable in ./build/opm-simulators/bin/flow_gaswater_dissolution.
40
37
41
-
For macOS users with the latest chips (M1/M2, guessing also M3?), the ecl and opm packages are not available via pip install. Then before installation, remove ecl and opm from the requierements.txt, then proceed with the Python requirements installation, and once inside the vexpreccs Python environment, add the flag `-DPYTHON_EXECUTABLE=/Users/dmar/expreccs/vexpreccs/bin/python` (by typing `which python` in the terminal you get your path) to the cmake (lines 24 in the bash scripts), build flow by running the bash script, and finally, add to the python path the folder where you have built it, e.g., by opening in an editor the vexpreccs/bin/activate script, pasting the following line (edited with the path where you built opm with Python)
42
-
`export PYTHONPATH=$PYTHONPATH:/Users/dmar/expreccs/build/opm-common/build/python` at the end of the script, and deactivating and activating the virtual environment.
38
+
For macOS users with the latest chips (M1/M2, guessing also M3?), the opm Python package is not available via pip install, while resdata might not be available depending on the Python version (e.g., it is not found using Python 3.9, but it is installed using Python 3.10). If you face this issue, then before installation, remove resdata and opm from the `requirements.txt`, then proceed with the Python requirements installation, install the OPM Flow dependencies (using macports or brew), and once inside the vexpreccs Python environment, run the `./build_opm-flow_macOS.bash`, and deactivate and activate the virtual environment (this script builds OPM Flow as well as the opm Python package, and it exports the required PYTHONPATH).
43
39
44
40
## Running expreccs
45
41
You can run _expreccs_ as a single command line:
@@ -50,7 +46,7 @@ Run `expreccs --help` to see all possible command line argument options. Inside
50
46
flow executable and simulation parameters. See the .txt files in the examples and tests/configs folders.
51
47
52
48
## Getting started
53
-
See the [_documentation_](https://daavid00.github.io/expreccs/introduction.html).
49
+
See the [_documentation_](https://cssr-tools.github.io/expreccs/introduction.html).
54
50
55
51
## About expreccs
56
52
The expreccs package is funded by Wintershall Dea, Equinor, Shell, and the Research Council of Norway [project number 336294].
Copy file name to clipboardexpand all lines: docs/_sources/configuration_file.rst.txt
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
==================
2
2
Configuration file
3
3
==================
4
-
We consider the configuration file (`input.txt <https://github.com/daavid00/expreccs/blob/main/examples/input.txt>`_) available in the
4
+
We consider the configuration file (`input.txt <https://github.com/cssr-tools/expreccs/blob/main/examples/input.txt>`_) available in the
5
5
examples folder. The parameters are chosen to show the functionality and capabilities of the **expreccs** framework regarding generation
6
6
of corner-point grids (cpg), heterogeinities (e.g., different rock properties, faults), adding wells, and defining schedules for the
7
-
operations. See the `example1.txt <https://github.com/daavid00/expreccs/blob/main/examples/example1.txt>`_ for a simpler configuration
7
+
operations. See the `example1.txt <https://github.com/cssr-tools/expreccs/blob/main/examples/example1.txt>`_ for a simpler configuration
8
8
file.
9
9
10
10
The first input parameter in the configuration file is:
@@ -183,7 +183,7 @@ Since we defined six wells (three of them inside the site model), then each row
183
183
the first three defining the injection time, number of restart files in the solution for the regional, number of restart files in the solution for the site/reference, and maximum solver time step, and 2*6 additional
184
184
entries to define injected fluid (0 water, 1 CO2) and the injection rates from well 0 to well 5 respectively. If in line 14 the wells
185
185
option is activated, then at the end of each row we add the values from the wells (BHP control) on the boundaries in the order of bottom, right, top,
186
-
and left with two values respectively (0 for producers and 1 for injectors, and the BHP in Pascals, see `example1_wells.txt <https://github.com/daavid00/expreccs/blob/main/examples/example1_wells.txt>`_).
186
+
and left with two values respectively (0 for producers and 1 for injectors, and the BHP in Pascals, see `example1_wells.txt <https://github.com/cssr-tools/expreccs/blob/main/examples/example1_wells.txt>`_).
187
187
188
188
.. warning::
189
189
Keep the linebreak between the sections in the whole configuration file and do not add linebreaks inside the sections
<h1>Configuration file<aclass="headerlink" href="#configuration-file" title="Link to this heading"></a></h1>
89
-
<p>We consider the configuration file (<aclass="reference external" href="https://github.com/daavid00/expreccs/blob/main/examples/input.txt">input.txt</a>) available in the
91
+
<p>We consider the configuration file (<aclass="reference external" href="https://github.com/cssr-tools/expreccs/blob/main/examples/input.txt">input.txt</a>) available in the
90
92
examples folder. The parameters are chosen to show the functionality and capabilities of the <strong>expreccs</strong> framework regarding generation
91
93
of corner-point grids (cpg), heterogeinities (e.g., different rock properties, faults), adding wells, and defining schedules for the
92
-
operations. See the <aclass="reference external" href="https://github.com/daavid00/expreccs/blob/main/examples/example1.txt">example1.txt</a> for a simpler configuration
94
+
operations. See the <aclass="reference external" href="https://github.com/cssr-tools/expreccs/blob/main/examples/example1.txt">example1.txt</a> for a simpler configuration
93
95
file.</p>
94
96
<p>The first input parameter in the configuration file is:</p>
95
97
<divclass="highlight-python notranslate"><divclass="highlight"><pre><span></span><spanclass="linenos">1</span><spanclass="sd">"""Set the full path to the flow executable and flags"""</span>
the first three defining the injection time, number of restart files in the solution for the regional, number of restart files in the solution for the site/reference, and maximum solver time step, and 2*6 additional
240
242
entries to define injected fluid (0 water, 1 CO2) and the injection rates from well 0 to well 5 respectively. If in line 14 the wells
241
243
option is activated, then at the end of each row we add the values from the wells (BHP control) on the boundaries in the order of bottom, right, top,
242
-
and left with two values respectively (0 for producers and 1 for injectors, and the BHP in Pascals, see <aclass="reference external" href="https://github.com/daavid00/expreccs/blob/main/examples/example1_wells.txt">example1_wells.txt</a>).</p>
244
+
and left with two values respectively (0 for producers and 1 for injectors, and the BHP in Pascals, see <aclass="reference external" href="https://github.com/cssr-tools/expreccs/blob/main/examples/example1_wells.txt">example1_wells.txt</a>).</p>
243
245
<divclass="admonition warning">
244
246
<pclass="admonition-title">Warning</p>
245
247
<p>Keep the linebreak between the sections in the whole configuration file and do not add linebreaks inside the sections
@@ -87,7 +89,7 @@ <h1>Examples<a class="headerlink" href="#examples" title="Link to this heading">
87
89
<sectionid="example-1">
88
90
<h2>Example 1<aclass="headerlink" href="#example-1" title="Link to this heading"></a></h2>
89
91
<p>We consider the configuration file ‘example1.txt’ in the
90
-
examples folder (the animation in the <aclass="reference external" href="https://github.com/daavid00/expreccs">Github home page</a> was based on this configuration file).
92
+
examples folder (the animation in the <aclass="reference external" href="https://github.com/cssr-tools/expreccs">Github home page</a> was based on this configuration file).
91
93
If the results are to be saved in a folder called ‘hello_world’, this is achieved by the following command:</p>
0 commit comments