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
Replace Eclipse trademark references and add third-party trademark notices
- Replace generic "Eclipse" usage with neutral terms ("reservoir simulation
case/file/properties/grid") across 34 content files, preserving UI labels
and menu item names that reflect the actual software interface
- Add trademark table to about.md for Eclipse® (Schlumberger), ABAQUS®
(Dassault Systèmes), SourSimRL (ESSS), StimPlan™ (NSI Technologies LLC),
Fishbones® (Fishbones AS), and GNU Octave (John W. Eaton)
- Add first-mention trademark symbols (®/™) for StimPlan and Fishbones
across relevant content pages
- Update docs-writer agent with trademark guidance, simulation type
distinction (reservoir vs geomechanical), and terminology table
Copy file name to clipboardExpand all lines: agents/docs-writer.md
+26-4Lines changed: 26 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,14 +45,36 @@ Use Hugo shortcodes for internal links — never hardcode paths:
45
45
- Use `---` horizontal rules to separate major wizard page sections.
46
46
- Do not use emoji.
47
47
48
+
## Simulation types
49
+
50
+
ResInsight supports two distinct simulation types. Use precise language to distinguish them:
51
+
52
+
-**Reservoir simulation** — results from simulators such as the *Eclipse® reservoir simulator* or OPM Flow. Stored in `.EGRID`/`.GRID`, `.UNRST`, `.SMSPEC` files etc.
53
+
-**Geomechanical simulation** — results from ABAQUS, stored in `.odb` files.
54
+
55
+
When the context is unambiguous (e.g. a page dedicated to reservoir simulation), "simulation" alone is acceptable. When both types could be in scope, be explicit: "reservoir simulation" or "geomechanical simulation".
56
+
57
+
Never use bare "simulation" in a way that could be misread as covering both types.
When the Eclipse product name cannot be avoided, use *Eclipse® reservoir simulator* on first mention per page and *Eclipse simulator* on subsequent mentions.
71
+
72
+
Other third-party trademarks used in the documentation:
73
+
74
+
| Product | Trademark owner | First-mention form |
75
+
|---------|----------------|--------------------|
76
+
| ABAQUS | Dassault Systèmes |*ABAQUS®*|
77
+
| SourSimRL | ESSS |*SourSimRL* (no symbol — unregistered trademark) |
Copy file name to clipboardExpand all lines: content/3d-main-window/3DViews.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Each item has a set of properties that can be edited in the **Property Editor**.
14
14
15
15
Several views can be added to the same case by right-clicking the case or a view and select **New View**. You can also **Copy** and then **Paste** a view into a Case. All the settings are then copied to the new view.
16
16
17
-
Views of Eclipse models and Geomechanical models has a lot in common, but Eclipse views has some features that applies to Eclipse simulations only.
17
+
Views of Eclipse models and Geomechanical models has a lot in common, but Eclipse views has some features that applies to reservoir simulations only.
18
18
19
19
## Common view features
20
20
@@ -34,7 +34,7 @@ Zoom and orientation of a model can be stored using the menu item **"Views->Stor
34
34
35
35
### Cell Result
36
36
37
-
The **Cell Result** {{< image-in-text src="images/3d-main-window/CellResult.png" >}} item defines which Eclipse or Geomechanical property the 3D View uses for the main cell color. The property can be chosen in the property panel of the **Cell Result** item. The mapping between cell values and color is defined by the **Legend Definition**{{< image-in-text src="images/3d-main-window/Legend.png" >}} along with some appearance settings on the Legend itself. (Number format etc.)
37
+
The **Cell Result** {{< image-in-text src="images/3d-main-window/CellResult.png" >}} item defines which simulation or Geomechanical property the 3D View uses for the main cell color. The property can be chosen in the property panel of the **Cell Result** item. The mapping between cell values and color is defined by the **Legend Definition**{{< image-in-text src="images/3d-main-window/Legend.png" >}} along with some appearance settings on the Legend itself. (Number format etc.)
38
38
39
39
Please refer to [Result Color Legend]({{% relref "resultcolorlegend" %}}) for details.
40
40
@@ -114,7 +114,7 @@ Select **Custom Edge Result** to specify one cell result to be mapped onto all c
114
114
Default result mapping on faults is using the result specified in **Cell Result**. If a different result mapping is wanted, enable the checkbox and select the result from the result selection dialog in the **Property Editor**. A second legend for the fault result is added to the view.
115
115
116
116
### Simulation Wells
117
-
This item controls the visualization of the Eclipse simulation wells.
117
+
This item controls the visualization of the simulation wells.
118
118
Please refer to [Simulation Wells]({{% relref "simulationwells" %}}) to read more.
-**Static** -- Eclipse properties that does not vary with time and derived properties calculated by ResInsight, c.f. [Derived Results]({{% relref "derivedresults" %}})
34
+
-**Static** -- Properties that do not vary with time and derived properties calculated by ResInsight, c.f. [Derived Results]({{% relref "derivedresults" %}})
35
35
-**SourSimRL** -- Available if SourSimRL results have been imported, c.f. [SourSimRL Import]({{% ref "soursimrlresults.md" %}})
36
36
-**Generated** -- Results generated by an Octave Script
37
-
-**Input Property** -- Directly imported Eclipse properties from ascii files
@@ -65,7 +65,7 @@ See also [ Flow Diagnostics Plots]({{% relref "flow-diagnostics-plots" %}}) and
65
65
66
66
The calculations are performed by a library called [opm-flowdiagnostics](https://github.com/OPM/opm-flowdiagnostics) developed by [SINTEF Digital](http://www.sintef.no/sintef-ikt/#/).
67
67
68
-
This method is based on the presence of a flux field, and will use the flux field written to the Eclipse result data file (Cell Properties: FLRGAS, FLRWAT, FLROIL) if available. If these are not available, the flux field is estimated by algorithms in the opm-flowdiagnostics-applications library based on pressure differences, relative and absolute permeability and viscosity. Other effects are not included.
68
+
This method is based on the presence of a flux field, and will use the flux field written to the result data file (Cell Properties: FLRGAS, FLRWAT, FLROIL) if available. If these are not available, the flux field is estimated by algorithms in the opm-flowdiagnostics-applications library based on pressure differences, relative and absolute permeability and viscosity. Other effects are not included.
69
69
70
70
A more elaborate description of the technique and how it can be utilized, can be found at Sintef's [web site](http://www.sintef.no/projectweb/mrst/modules/diagnostics/). The MRST tool described is a Matlab predecessor of the flow diagnostics calculations developed for ResInsight.
71
71
@@ -123,7 +123,7 @@ This result type is used to plot derived results based on a selection of simulat
-**Tracers** -- Lists the available simulation tracers from the Eclipse Case. The list is produced by showing only the properties with names ending with the letter "F". Select the tracers you want to investigate.
126
+
-**Tracers** -- Lists the available reservoir simulation tracers from the reservoir simulation case. The list is produced by showing only the properties with names ending with the letter "F". Select the tracers you want to investigate.
127
127
-**Result Property** -- Select the variable you want to calculate. (_Number Of Flooded PV_ is currently the only one)
Copy file name to clipboardExpand all lines: content/3d-main-window/ContourMaps.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ weight = 40
6
6
7
7
8
8
9
-
ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as Oil, Gas and Hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells.
9
+
ResInsight can create contour maps based on different forms of aggregation of 3D reservoir simulation data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as Oil, Gas and Hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells.
10
10
ResInsight is able to [export a contour map]({{% relref "contourmapexport" %}}) to a text file.
11
11
12
12
Polygons can be created from visible areas. If you want to compute contour maps for ensembles, look at [Ensemble Contour Map]({{% relref "ensemblecontourmap" %}})
@@ -16,7 +16,7 @@ Polygons can be created from visible areas. If you want to compute contour maps
16
16
Contour Maps can be created in many different ways:
17
17
18
18
- New Contour Map from the right-click menu of case or the **Contour Maps** project tree item underneath the case. These will create contour maps with default values.
19
-
- New Contour Map from 3D View in the Eclipse View right-click menu. This will create a contour map based on the existing 3D View with matching filters and result.
19
+
- New Contour Map from 3D View in the simulation View right-click menu. This will create a contour map based on the existing 3D View with matching filters and result.
20
20
- Duplicate Contour Map from the right-click menu of an existing Contour Map. This will copy the existing map.
ResInsight can create contour maps from an ensemble of grid models based on different forms of aggregation of 3D Eclipse data onto a 2D plane.
8
+
ResInsight can create contour maps from an ensemble of grid models based on different forms of aggregation of 3D reservoir simulation data onto a 2D plane.
Copy file name to clipboardExpand all lines: content/3d-main-window/Faults.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ As import of faults can be time consuming, reading of faults can be disabled fro
38
38
{{% /notice %}}
39
39
40
40
#### NNC Data
41
-
If enabled in **Preferences**, ResInsight will read Non Neighbor Connections from the Eclipse output file (_`*.INIT`_), and create explicit visualizations of those.
41
+
If enabled in **Preferences**, ResInsight will read Non Neighbor Connections from the simulator output file (_`*.INIT`_), and create explicit visualizations of those.
42
42
The NNC's are sorted onto the Fault's and their visibility is controlled along with them.
43
43
44
44
When the NNCs are imported from file, ResInsight will identify NNCs not defined in the input file (Faces with zero transmissibility is not exported from the simulator). See [Derived Results]({{% relref "derivedresults" %}}) for details on other NNC related results.
@@ -96,7 +96,7 @@ First of all, these options are only available in **Faults-only** visualization
96
96
97
97
Secondly, the option you would normally want to adjust is **Dynamic Face Selection** ( See below ).
98
98
99
-
-**Show defined faces** -- Displays the fault cell faces that are defined on the Eclipse input file (_`*.DATA`_)
99
+
-**Show defined faces** -- Displays the fault cell faces that are defined on the input file (_`*.DATA`_)
100
100
-**Show opposite faces** -- Displays the opposite fault cell faces from what is defined on the input file, based on IJK neighbors.
101
101
*These two options should normally be left **On**. They are useful when investigating the exact faults information provided on the `*.DATA` file. If you need to use them, it is normally wise to set the **Dynamic Face Selection** to "Show Both".*
102
102
-**Dynamic Face Selection** -- At one particular position on a fault there are usually two cells competing for your attention: The cell closer to you as the viewer, or the one further from you. When showing results, this becomes important because these two cell faces have different result property values, and thus color.
@@ -114,7 +114,7 @@ The color of the NNC faces are set to be a bit lighter than their corresponding
114
114
115
115
## Fault Export
116
116
117
-
Faults can be exported to separate files in the _`*grdecl`_ file format. This is useful for example if you need a list of the geometrically detected faults that has not been covered by entries in the eclipse FAULTS keyword.
117
+
Faults can be exported to separate files in the _`*grdecl`_ file format. This is useful for example if you need a list of the geometrically detected faults that has not been covered by entries in the FAULTS keyword.
118
118
119
119
To export some faults, select the faults you want to export in the **Project Tree**, and select the command **Export Faults ...** from the right-click menu.
Copy file name to clipboardExpand all lines: content/3d-main-window/FlowVectorResult.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ weight = 141
9
9
Flow Results lets the user investigate flow properties and fluxes in a reservoir, e.g. by flow vector visualizations selecting and combining different fluids and directions.
10
10
11
11
## Flow Vectors
12
-
Flow vectors are computed based on the Eclipse properties **FLRGASI/J/K FLRWATI/J/K FLROILI/J/K**.
12
+
Flow vectors are computed based on the reservoir simulation properties **FLRGASI/J/K FLRWATI/J/K FLROILI/J/K**.
13
13
Visualization of flow vector results always use velocity instead of rate. Velocity is computed as flow rate divided by cell face area.
14
14
15
15
In order to show flow vectors, check the checkbox next to **Flow Vector Result** in **Project Tree**.
@@ -58,5 +58,5 @@ For instance, the option enables comparison of horizontal and vertical flow velo
Specifically, the check-box *Divide By Area* is applicable to Eclipse properties *FLROIL, FLRGAS, FLRWAT, FLOOIL, FLOGAS, FLOWAT*, and transmissibilities *TRAN* and *riTRAN*.
61
+
Specifically, the check-box *Divide By Area* is applicable to reservoir simulation properties *FLROIL, FLRGAS, FLRWAT, FLOOIL, FLOGAS, FLOWAT*, and transmissibilities *TRAN* and *riTRAN*.
62
62
These results are listed in ResInsight postfixed by *IJK+-* or *XYZ* as shown above. As seen, checking *Divide By Area* is reflected by text */A* in legend.
By selecting a specific **Intersection Result**, the **Property Editor** allows to specify case, type or position etc depending on whether the result stem from an Eclipse case or a Geomechanical case.
192
+
By selecting a specific **Intersection Result**, the **Property Editor** allows to specify case, type or position etc depending on whether the result stems from a reservoir simulation case or a Geomechanical case.
193
193
194
194
The next step is to select an **Intersection** in **Project Tree** and define **Result Reference**.
195
-
In the example below, available sources are the two **Intersections Results** of previous figure, one of which stems from a geomechanical case and the other from an Eclipse case.
195
+
In the example below, available sources are the two **Intersections Results** of previous figure, one of which stems from a geomechanical case and the other from a reservoir simulation case.
Copy file name to clipboardExpand all lines: content/3d-main-window/LinkedViews.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ When selecting a linked view in the project tree, the different options are avai
34
34
35
35
#### Link Cell Filters
36
36
37
-
-**Range Filters** -- Range filters in master view will be applied to all dependent views where this option is active. Normally this is done by a direct copy, but if the master and dependent view is of different types (Eclipse and Geomechanical views) and the Eclipse case is within the bounds of the Geomechanical case, ResInsight tries to map the range filters to the corresponding cells in the other case.
37
+
-**Range Filters** -- Range filters in master view will be applied to all dependent views where this option is active. Normally this is done by a direct copy, but if the master and dependent view is of different types (Eclipse and Geomechanical views) and the reservoir simulation case is within the bounds of the Geomechanical case, ResInsight tries to map the range filters to the corresponding cells in the other case.
38
38
-**Property Filters** -- Property filters in master view will be applied to all dependent views where this option is active.
0 commit comments