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
Copy file name to clipboardExpand all lines: content/Wells-and-Completions/WellPaths.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,13 @@ ResInsight also supports creation of your own user-defined well paths. See [Crea
14
14
## Ascii Well Paths
15
15
16
16
The command **File -> Import -> Well Data -> Import Well Paths From File** will read the well paths in the selected file, and create one entry for each well path under the {{< image-in-text src="images/3d-main-window/WellCollection.png" >}} **Wells** item in the **Project Tree**.
|rmswell | RMS well file format|[RMS Well](https://github.com/OPM/ResInsight/blob/dev/ApplicationLibCode/UnitTests/TestData/RifRmsWellPathReader/55_33-1.rmswell)|
22
+
|asc | Ascii file format|
23
+
18
24
## Importing well paths from OSDU
19
25
20
26
Well path trajectories can be downloaded from an OSDU cloud service. When storing the project file, the reference to the OSDU trajectory is stored. This will ensure that authentication and access is checked before the trajectory is downloaded.
@@ -51,6 +57,8 @@ A well path will hold well log data and well path data imported from files. A we
51
57
### Importing Well Log Files
52
58
Well log data is [imported from LAS-files]({{% relref "lasfile" %}}#importing-a-las-file).
53
59
60
+
RMS Well Log files are also supported. See [here for and example](https://github.com/OPM/ResInsight/blob/dev/ApplicationLibCode/UnitTests/TestData/RifRmsWellPathReader/55_33-1.rmswell).
61
+
54
62
### Well Path Property Editor
55
63
The well path property editor lets the user control the appearance of the well path and associate the well path to a simulation well. It also gives some information about the well path metadata.
Copy file name to clipboardExpand all lines: content/import/GeomechanicalData.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ If you have, and would like to a use these features, please see [ Build Instruct
11
11
### Geo Mechanical Data Support
12
12
Geo-mechanical data can be imported using the **Import -> Geo Mechanical Cases menu**. Here three options are present: **Import Geo Mechanical Model**, **Import Geo Mechanical Model (Time Step Filtered)** (both for odb files) and **Import Element Property Table**.
13
13
14
+
A geomechanical model can also be imported from a VTK file.
Copy file name to clipboardExpand all lines: content/releases/release-notes/releasenotes_2025_09.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,10 @@ search_ignore = true
9
9
10
10
The import dialog when searching the file system for ensemble data is improved, allowing for easy selection of multiple ensembles. When an ensemble is imported, the realization numbers in the form of a text string (1-21,30-35, 40-60) can be edited for import of a subset of realizations.
@@ -21,12 +23,23 @@ There has been several improvements related to summary performance in this relea
21
23
## Other improvements
22
24
- Logging of application operations and crash report to log file by default stored in `home_folder/.resinsight/logs`
23
25
- Improved color control of RFT ensemble curves
26
+
- Length and area of a [Polygon]({{% relref "polygons" %}}) can be displayed as a label
27
+
- Geomechanical data import has been expanded beyond the existing ABAQUS file format support. VTK grid files can now be imported as an additional source for geomechanical data, providing users with more flexibility in data ingestion. Most existing geomechanical analysis features are available for data imported from VTK.
28
+
- Import of surface in IRAP and GRI
29
+
- Import of [RMS Well Path]({{% relref "wellpaths" %}}) and RMS Well Logs
24
30
31
+
## Python API
32
+
Several improvements have been made to the Python API.
33
+
- Improved error management and error reporting
34
+
- Create grid from COORD, ZCORN and ACTNUM
35
+
- Create regular surface
36
+
- Added support for Non-Darcy parameters for perforation intervals
- New option to define the maximum number of threads to be used by ResInsight `--threadcount` This command line option can also be specified when [launching a ResInsight process from Python](
0 commit comments