Replies: 2 comments 1 reply
-
Hey @vkazei, It's good to hear from you. I hope its starting to cool off a bit in Houston. I agree with you. I am personally not a big fan of the format, and it does make me a little sad to think DASCore would be adding more SEGY files to world, but so many programs use SEGY as inputs that its utility is undeniable. ProdML output is also high on our priority list. @aaronjgirard added the SEGY read support, I wonder if he has any thoughts on a road map for adding SEGY write support? We current just use segyio under the hood so, at first glance, I think it would be relatively straight-forward to produce SEGY files but I do know there is a lot of nuance to the format so it might not be as easy as it appears. Would you be willing to help us test the outputs to make sure they play nicely with your processing workflows? |
Beta Was this translation helpful? Give feedback.
-
Hi Vladimir and Derrick,
I could put in the effort to generate SEGY outputs, but one of the biggest
issues was ensuring that all the header information is correct, since the
DAS files don't have all of the SEGY information. If you could give some
input on what the most important SEGY file headers you'd need would be, I
can look into that soon. SEGY output hasn't been a priority lately, but now
that you've brought it up it could be done. Thanks for the file and I will
look into this
Best,
*Aaron Girard*
…On Thu, Sep 5, 2024 at 10:12 AM Vladimir Kazei ***@***.***> wrote:
Hi @d-chambers <https://github.com/d-chambers>,
Sure, I'd be happy to provide some feedback on usage. Here is an open DAS
VSP dataset for example:
https://researchdata.edu.au/walk-away-vertical-experiment-geolab/1915113
maybe we could test some DASCore tools and save updated segys?
—
Reply to this email directly, view it on GitHub
<#428 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEX7T356J7CJTQD4NRMKUYDZVB7GPAVCNFSM6AAAAABNMS4OYGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANJVHE3TONY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Would greatly help standardize output between vendors for subsequent seismic processing. Few of us at the DFOS workshop hope to see a SEGY output option soon :)
Beta Was this translation helpful? Give feedback.
All reactions