11117383db
* Better minimum width for well log tracks * Fix alignment of scrollbar in Well log plots * Better Well Log Plot export * Hide scroll bar before plotting * Better borders * Create plots through Python * #4817 Create WBS plots with Python * Rebase Summary and WellLogPlot on top of a new RimPlot * Also Python: Allow setting folder as a parameter to export_snapshots * #4832 Prepare for well path import command * Well Path import WIP * #4830 #4832 Import well paths and well log files from file using Python. * #4837 Implement import of formation names in Python * Fix debug build issue * Fix RiaLogging build issue * Fix warnings * Yet another RiaLogging.h import added * #4839 Import exporting of las and ascii files from well log plots |
||
|---|---|---|
| ApplicationCode | ||
| cmake | ||
| debian | ||
| doc | ||
| Fwk | ||
| OctavePlugin | ||
| patches | ||
| redhat | ||
| scripts | ||
| TestModels | ||
| ThirdParty | ||
| .appveyor.yml | ||
| .gitignore | ||
| .travis.yml | ||
| build_grpc_linux.sh | ||
| CMakeLists.txt | ||
| COPYING | ||
| Doxyfile.in | ||
| GRPC_install_instructions.txt | ||
| README.md | ||
| ResInsightVersion.cmake | ||
ResInsight
ResInsight is an open source, cross-platform 3D visualization and post processing tool for reservoir models and simulations. The system also constitutes a framework for further development and support for new data sources and visualization methods, e.g. additional solvers, seismic data, CSEM, geomechanics, and more.
The user interface is tailored for efficient interpretation of reservoir simulation data with specialized visualizations of properties, faults and wells. It enables easy handling of a large number of realizations and calculation of statistics. To be highly responsive, ResInsight exploits multi-core CPUs and GPUs. Integration with GNU Octave enables powerful and flexible result manipulation and computations. Derived results can be returned to ResInsight for further handling and visualization. Eventually, derived and computed properties can be directly exported to Eclipse input formats for further simulation cycles and parameter studies.
The main input data is *.GRID and *.EGRID files along with their *.INIT and restart files *.XNNN and *.UNRST. ResInsight also supports selected parts of Eclipse input files and can read grid information and corresponding cell property data sets.
ResInsight has been co-developed by Equinor ASA, Ceetron Solutions AS, and Ceetron AS with the aim to provide a versatile tool for professionals who need to visualize and process reservoir models. The software is copyrighted by Ceetron and Equinor and licensed under GPL 3+. See COPYING for details.
Dependencies
ResInsight uses the Equinor/libecl (formerly Ensambles/ert) library to access Eclipse result files, and the two projects collaborates closely. The source code of the approved libecl version is embedded in the ResInsight source code tree, making downloading and building simple. ResInsight also features an interface to Octave for retrieval of data from ResInsight, processing using Octave, and communication of data back into ResInsight for further handling and visualization.
Octave : http://www.gnu.org/software/octave/
Equinor/libecl : https://github.com/Equinor/libecl
Supported Platforms
ResInsight is designed cross-platform from the start. Efforts have been made to ensure that code will compile and run on Linux and Windows platforms. Tested platforms are currently 64 bit RHEL6 and Windows 7/8/10, and we have also received reports on successful builds on Ubuntu based systems.
Documentation
See the ResInsight website and the Users Guide for project documentation.
Source Code
git clone git://github.com/OPM/ResInsight.git
Contribution
Contributions are very welcome, although it might take some time for the team to accept pull requests that is not in the main line of the projects focus.
Please use the dev branch for contributions and pull requests, as it is the branch dedicated to the day to day development.
The master branch is supposed to be stable, and is updated when we want to publish a new stable release.
Release branches that might pop up are dedicated bug fix branches for the release in question.