search

krober10nd / SeismicMesh

2D/3D serial and parallel triangular mesh generation tool for finite element methods.
https://seismicmesh.readthedocs.io/
GNU General Public License v3.0
127 stars 33 forks source link

bounding box from files? #50

Closed nschloe closed 4 years ago

nschloe commented 4 years ago

In the README examples, the bounding boxes are specified explicitly. Can those not be read from the segy files?

krober10nd commented 4 years ago

I'll look into this but my initial guess is no this information isn't always standardized in the segy format. The segy format is quite dated and is used for a variety of purposes in seismology now. It has a fixed length header with user written notes typically.

nschloe commented 4 years ago

I think if it contains velocity data, then there must be an indication of where the data lives, too, right?

krober10nd commented 4 years ago

Yea, I had thought the same but had originally given up. I'll try again.

I started an issue with segyio to see if they have any insight.

https://github.com/equinor/segyio/issues/472

The segy format is essentially overloaded to support seismic velocity models. Normally it stores these things called shot records which are essentially collections of time series at microphones along the surface of the Earth.

nschloe commented 4 years ago

I see: The segy format by default only contains nx, ny[, nz]. Let's wait for the segyio issue to resolve, but probably the bbox has to be specified explicitly.