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

Trace Selection on Read using headers? #24

Open
scott314159 opened this issue May 22, 2024 · 2 comments
Open

Trace Selection on Read using headers? #24

scott314159 opened this issue May 22, 2024 · 2 comments

Comments

@scott314159
Copy link

I am trying to read in a segy data set where dead traces have been inserted into the dataset. Dead traces have source and receiver coordinates set as zero as well as the mute being set at the end of the trace. Is there a way to ignore traces based on a header word value or range (e.g. don't read if SourceX is zero)? I imagine(?) that having zeros in my geometry and dead traces will hurt when I try FWI.

By the way, the "how to" video is very good. In it there is mention of the readme file that goes along with the video but I don't see that file in the distribution or github page. I did not see what I wanted to do in the video but it would be handy to have the readme as a reference if it is available.

Thanks.

@mloubout
Copy link
Member

it would be handy to have the readme as a reference

We do have a Wiki that go over the basics of reading/writing/scanning but might wanna put a link in the Readme as well

https://github.com/slimgroup/SegyIO.jl/wiki

Is there a way to ignore traces based on a header word value or range

Not "easily". The backend is written in a fairly efficient way that reads the file by chunck as it is faster rather than by trace. It would also be tricky because some datasets have valid src/rec at zero position. So the simplest way would be to use get_headers on your data then filter out the trace you don't want with filter/find, see for example in the scanning wiki
https://github.com/slimgroup/SegyIO.jl/wiki/Scanning

@scott314159
Copy link
Author

Thanks for the help. I'll check out the Wiki a bit more (I was myopic in my approach because I was focused on the reading of the file not scanning).

A link to the readme would be helpful as a reference. There are a few spots where some of the text is cut off so I can' read the whole line of code.

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