Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/equinor/dlisio
Python library for working with the well log formats Digital Log Interchange Standard (DLIS V1) and Log Information Standard (LIS79)
https://github.com/equinor/dlisio
dlis lis lis79 rp66v1
Last synced: about 2 months ago
JSON representation
Python library for working with the well log formats Digital Log Interchange Standard (DLIS V1) and Log Information Standard (LIS79)
- Host: GitHub
- URL: https://github.com/equinor/dlisio
- Owner: equinor
- License: other
- Created: 2018-07-03T22:16:39.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2023-11-14T12:49:00.000Z (8 months ago)
- Last Synced: 2024-04-28T12:03:20.682Z (2 months ago)
- Topics: dlis, lis, lis79, rp66v1
- Language: Python
- Homepage: https://dlisio.readthedocs.io/en/latest/
- Size: 2.89 MB
- Stars: 114
- Watchers: 11
- Forks: 37
- Open Issues: 19
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.rst
- License: LICENSE
- Security: SECURITY.md
Lists
- awesome-open-geoscience - dlisio
- awesome-open-geoscience - dlisio
- awesome-reservoir-engineering - dlisio -    dlisio is an LGPL licensed library for working with well logs in Digital Log Interchange Standard (DLIS V1) (Software / Petrophysics)
README
## Introduction ##
dlisio is an LGPL licensed library for reading well logs in Digital Log
Interchange Standard (DLIS V1), also known as [RP66
V1](https://www.energistics.org/sites/default/files/rp66v1.html), and Log Information
Standard 79 ([LIS79](https://www.energistics.org/sites/default/files/2022-10/lis-79.pdf)).
dlisio is designed as a general purpose library for reading well logs in a
simple and easy-to-use manner. Its main focus is making all the data and
metadata accessible while putting few assumptions on how the data is to be
used. This makes it suitable as a building block for higher level applications
as well as for being used directly.
dlisio focuses above all on correctness, performance and robustness. Its core,
which does all the heavy lifting, is implemented in C++. Both the C++ core and
the python wrappers are backed by an extensive test-suite. It strives to be
robust against files that do not strictly adhere to the specifications, which
is a widespread issue with both DLIS and LIS files. dlisio tries to account for
many of the known specification violations out there, but only when it can do
so without compromising correctness. It will not do any guess work on your
behalf when such violations pose any ambiguity.
## Installation ##
dlisio supplies pre-built python wheels for a variety of platforms and
architectures. The wheels are hosted through the [Python Package Index
(PyPI)](https://pypi.org/) and can be installed with:
```bash
pip install dlisio
```
| | macOS Intel | macOS ARM | Windows 64bit | Windows 32bit | manylinux x86_64 | manylinux aarch64 | manylinux i686 | musllinux x86_64
|---------------|----|-----|-----|----|----|----|----|----|
| CPython 3.7 | ✅ | - | ✅ | ✅ | ✅ | ✅ | ✅ | - |
| CPython 3.8 | ✅ | - | ✅ | ✅ | ✅ | ✅ | ✅ | - |
| CPython 3.9 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| CPython 3.10 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| CPython 3.11 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| CPython 3.12 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
See [Build dlisio](#Build-dlisio) for building dlisio from source.
## Getting started ##
dlisio's documentation is hosted on
[readthedocs](https://dlisio.readthedocs.io/en/stable/). Please refer there for
proper introduction to dlisio and the file-formats DLIS and LIS. Here is a
motivating example showcasing how to read the curve-data from a DLIS-file:
```python
from dlisio import dlis
with dlis.load('myfile.dlis') as files:
for f in files:
for frame in f.frames:
curves = frame.curves()
# Do something with the curves
```
and from a LIS-file:
```python
from dlisio import lis
with lis.load('myfile.lis') as files:
for f in files:
for format_spec in f.data_format_specs():
curves = lis.curves(f, format_spec)
# Do something with the curves
```
In both cases the curves are returned as [structured
numpy.ndarray](https://numpy.org/doc/stable/user/basics.rec.html) with the
curve mnemonics as field names (column names).
## Build dlisio ##
To develop dlisio, or to build a particular revision from source, you need:
* A C++11 compatible compiler (tested on gcc, clang, and msvc 2019)
* [CMake](https://cmake.org/) version 3.5 or greater
* [Python](https://python.org) version 3.7 or greater
* [fmtlib](http://fmtlib.net/) tested mainly with 7.1.3
* [mpark_variant](https://github.com/mpark/variant)
* [pybind11](https://github.com/pybind/pybind11) version 2.6 or greater
* [setuptools](https://pypi.python.org/pypi/setuptools) version 28 or greater
* [layered-file-protocols](https://github.com/equinor/layered-file-protocols)
* python packages pytest, pytest-runner, and numpy
If you do not have pybind11 installed on your system, the easiest way to get a
working copy is to `pip3 install pybind11` (NP! pybind11, not pybind)
layered-file-protocols has to be installed from source if you don't already
have it on your system:
```bash
git clone https://github.com/equinor/layered-file-protocols.git
mkdir layered-file-protocols/build
cd layered-file-protocols/build
cmake .. -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=ON
-DLFP_FMT_HEADER_ONLY=ON
make
make install
```
To then build and install dlisio:
```bash
mkdir dlisio/build
cd dlisio/build
cmake .. -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=ON
make
```
dlisio follows common cmake rules and conventions, e.g. to set install prefix
use `-DCMAKE_INSTALL_PREFIX`. To build the python library it is usually a good
idea to build shared libraries. To disable python, pass `-DBUILD_PYTHON=OFF`.
By default, the python library is built.
## Contributing ##
We welcome all kinds of contributions, including bug reports, issues, feature
requests and documentation. The preferred way of submitting a contribution is to
make an [issue](https://github.com/equinor/dlisio/issues) on github.