TileDB-Segy
TileDB-Segy is a small MIT licensed Python library for easy interaction with seismic data, powered by TileDB. It combines an intuitive, segyio-like API with a powerful storage engine.
Feature summary
Available features
- Converting from SEG-Y and Seismic Unix formatted seismic data to TileDB arrays.
- Simple and powerful read-only API, closely modeled after
segyio. - 100% unit test coverage.
- Fully type-annotated.
Currently missing features
- API for write operations.
- Converting back to SEG-Y.
- TileDB configuration and performance tuning.
- Comprehensive documentation.
- Real-world usage.
Installation
TileDB-Segy can be installed:
-
from PyPI by
pip:pip install tiledb-segy -
from source by cloning the Git repository:
git clone https://github.com/TileDB-Inc/TileDB-Segy.git cd TileDB-Segy pip install .You may run the test suite with:
python setup.py test
Converting from SEG-Y
TileDB-Segy comes with a commandline interface (CLI) called segy2tiledb for converting
SEG-Y and Seismic Unix formatted files to TileDB formatted arrays. At minimum it takes
an input file and generates a directory at the same parent directory with the input and
extension .tsgy:
$ segy2tiledb a123.segy
$ du -sh a123.*
73M a123.sgy
55M a123.tsgy
To see the full list of options run:
$ segy2tiledb -h
usage: segy2tiledb [-h] [-o] [-g {auto,structured,unstructured}] [--su]
[--iline ILINE] [--xline XLINE]
[--endian {big,msb,little,lsb}] [-s TILE_SIZE]
input [output]
Convert a SEG-Y file to tiledb-segy format
positional arguments:
input Input SEG-Y file path
output Output directory path (default: None)
optional arguments:
-h, --help show this help message and exit
-o, --overwrite Overwrite the output directory if it already exists (default: False)
-g {auto,structured,unstructured}, --geometry {auto,structured,unstructured}
Output geometry:
- auto: same as the input SEG-Y.
- structured: same as `auto` but abort if a geometry cannot be inferred.
- unstructured: opt out on building geometry information.
(default: auto)
segyio options:
--su Open a seismic unix file instead of SEG-Y (default: False)
--iline ILINE Inline number field in the trace headers (default: 189)
--xline XLINE Crossline number field in the trace headers (default: 193)
--endian {big,msb,little,lsb}
File endianness, big/msb (default) or little/lsb (default: big)
tiledb options:
-s TILE_SIZE, --tile-size TILE_SIZE
Tile size in bytes.
Larger tile size improves disk access time at the cost of higher memory (default: 4000000)
API
TileDB-Segy generally follows the segyio API; you may consult its
documentation to learn about
the public attributes (ilines, xlines, offsets, samples) and addressing modes
(trace, header, attributes', iline, xline, fast, slow, depth_slice,
gather, text, bin).
You can find usage examples in the following Jupyter notebooks:
Differences from segyio
-
Addressing modes that return a generator of numpy arrays in
segyio, intiledb-segythey return a single numpy array of higher dimension. For example, in a SEG-Y with 50 ilines, 20 xlines, 100 samples, and 3 offsets:f.iline[0:5]:segyioreturns a generator that yields 5 2D numpy arrays of (20, 100) shapetiledb-segyreturns a 3D numpy array of (5, 20, 100) shape
f.iline[0:5, :]:segyioreturns a generator that yields 15 2D numpy arrays of (20, 100) shapetiledb-segyreturns a 4D numpy array of (5, 3, 20, 100) shape
-
The mappings returned by
bin,headerandattributes(name)have string keys instead ofsegyio.TraceFieldenums or integers. -
tiledb.segy.open(dir_path), thesegyio.open(file_path)equivalent, does not take any optional parameters (e.g.strictorignore_geometry). -
Unstructured and structured SEG-Y are represented as instances of two different classes,
tiledb.segy.Segyandtiledb.segy.StructuredSegyrespectively.StructuredSegyextendsSegy, so the whole unstructured API is inherited by the structured.- All attributes and addressing modes specific to structured files (e.g.
ilinesorgather) are available only toStructuredSegy. In contrastsegyioreturnsNoneor raises an exception if these properties are accessed on unstructured files. segyio.tools.dtis exposed asSegy.dt(fallback=4000.0)method.segyio.tools.cubeis exposed asStructuredSegy.cube()method.- There is no
unstructuredattribute; usenot isinstance(f, StructuredSegy)instead.
-
There is no
tracecountattribute; uselen(trace)instead. -
There is no
ext_headersattribute; uselen(text[1:])instead.
Metadata
Release files for tiledb-segy 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| tiledb-segy-0.3.1.tar.gz | 16.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tiledb_segy-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.4 kB
Release files / tiledb-segy-0.3.1.tar.gz
| Download URL | tiledb-segy-0.3.1.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86849802df0ff42a9645d9ef93f4302908bdcd47cd0810f3c0173c9ed40ef2dd
|
|
BLAKE2b-256 checksum How to use checksums |
160d1810929fd91f350c1ff0dd3bbbdfcfe76ab6554916a784b5164742cf3ad0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.2
|
Release files / tiledb_segy-0.3.1-py3-none-any.whl
| Download URL | tiledb_segy-0.3.1-py3-none-any.whl |
|---|---|
| Size | 16.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
446bca2fecde820277d1559588c409985b4ee493c1844c31997ee788105d03e2
|
|
BLAKE2b-256 checksum How to use checksums |
c95314fb84803586ad1d776aae6182341ad2f9b92bd9bb6b3e3a6df915f3b4e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.2
|
Security for tiledb-segy 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.