Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How segio working in open process? #551

Open
bohan12 opened this issue Mar 21, 2023 · 1 comment
Open

How segio working in open process? #551

bohan12 opened this issue Mar 21, 2023 · 1 comment

Comments

@bohan12
Copy link

bohan12 commented Mar 21, 2023

Hi I am a beginner of earth science researcher, first thanks for your amazing open source packages, it really helpful in my research process. And tow of questions I want to ask.

First question, I got a problem of segio.open(), what segio doing in open step, it scan part of segy data?

Second question, I use the data in Cloud service and the normal download speed is around 70m/s(by monitor system report), but when I use segyio to open the data only have 20m/s. This cause the bytes read each time?

Thanks for your reply.

@ErlendHaa
Copy link
Contributor

Hi! Sorry for the late answer.

In the simplest case, where segyio ignores geometry segyio.open("file.segy", ignore_geometry=True) all it does it to parse the binary header to get the trace count and trace lengths and verify that it matches up with file size.

If geometry is infered, which is the default behavior, segyio will scan trace headers of a full line (inline if inline sorted, crossline if crossline sorted) to establish the inline/crossline/offset counts.

I'm unsure what's going on there. Segyio lazily reads traces when you access them. There might be some overhead if yuo have a slow network disk and do a lot of small reads, but it's hard to jugde

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

No branches or pull requests

2 participants