Skip to content
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.

SEGY write and report #17

Open
fintis opened this issue May 5, 2018 · 2 comments
Open

SEGY write and report #17

fintis opened this issue May 5, 2018 · 2 comments

Comments

@fintis
Copy link

fintis commented May 5, 2018

Hi,

Great work!

I was wondering if there is a base capability to write out SEGY. Is this possible with some implementation of the Reporting? Would it possible to share an example or perhaps give some pointers how one could implement writing out to SEGY? I would also like some explanation on how you intended the reporting package to be used in general.

Cheers

@thecoldwine
Copy link
Owner

thecoldwine commented May 5, 2018

Hello,

At the moment there is no way to use sigrun as writer although I'm considering such capability as a feature for release 1.0. I need to finish implement SEGY standard (extended headers are not supported at the moment, and there are no support for two's complementary numbers in traces).

Initially I used sigrun just as the navigation extraction tool without any traces parsing. Basically you need to implement some strategy which will be executed over all trace headers and produce report based on header information. As you can see this library is not under active development (i'm working on complete LAS file serializer/deserializer at the moment), but I have plans to provide detailed guide and serialization toolkit in couple of months (since I'm returning to seismic data processing in my daily routines). Stay tuned :)

If you want to implement serialization by yourself I would start with my parsing code. It is rare to see completely compliant structure in practice so writing segy will look like: 3200 EBCDIC-encoded bytes to the beginning -> 400 bytes of binary header (you need to provide custom structure logic here) -> [optional extended headers as stated in binary header] -> trace header (custom structure logic as well) -> trace data.

In my practice IEEE754 or IBM360 are covering 99% of SEGY files, so you don't need to reinvent the wheel and use existing code (not sure if I wroteIEEE754->IBM360 converter, but I can if needed).

@fintis
Copy link
Author

fintis commented May 5, 2018

@thecoldwine many thanks for your response. My daily routine happens to be seismic data processing as well. I will give it a go and keep you posted.

Many thanks once again

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants