Rob,
Thanks for the reply.
I have been iterating through the debugger to try spot where goofy
numbers are being extracted. The dream is to identify a blindspot in the
code that I can fix and make it all work as expected :)
I am trying to design a workflow which uses dd to extract SEGD off tape,
tee the result to a disc file and feed stdout into segdread to
ultimately produce SEGY for production of near trace gathers for QC
image preparation. This is for the government of a developing nation and
there are over 15000 tapes.
Part of the job is to demonstrate the resulting SEGD disc files are
usable. SegDSeeMp can deal with these files fine. I have the source code
for SegDSeeMp, but its SEGD code is couched within their Qt framework.
Both SegDSeeMp and segdread are somewhat dense, which is to be expected
with a standard like SEGD.
regards
Graeme
On 8/12/22 20:38, rob(a)xsgeo.com wrote:
Hi Graham,
Last time I had SEGDREAD problems , I managed to read the data straight off
using openseaseis so that might be the quickest route.
Prior to that I think I had to hack the code to bypass whatever issue it was
having. Pretty sure I have read 8015 format previously without issues
though.
Regards
Rob
-----Original Message-----
From: Graeme Murray <murray(a)geocom.com.au>
Sent: Thursday, 8 December, 2022 12:22 PM
To: seisunix(a)mailman.seismic-unix.org
Subject: [Seisunix] segdread and 8015
I have been failing to get segdread to handle 8015 and 8036 SEGD files.
It handles 8058 without problem. I may end up seeing other formats, all
demultiplexed.
My example files can be viewed and headers examined in SegDSeeMp. The header
listings agree with what I can make out in a binary editor.
I've run segdread in a debugger to examine where things go wrong. It looks
as though it begins misinterpreting headers at some point. The general
header states there is one scan type, and 10 channel sets.
During the read it may encounter scan type 63 and channel set 46, which are
outside the bounds of an array. From there we segfault.
Before I go further, I thought I'd ask whether anyone else has had similar
issues.
regards
Graeme Murray
_______________________________________________
Seisunix mailing list -- seisunix(a)mailman.seismic-unix.org To unsubscribe
send an email to seisunix-leave(a)mailman.seismic-unix.org