9 Sep
2021
9 Sep
'21
12:53 a.m.
Hi Cemal,
I recently had the same need but failed to compile the segdread program
in the current SU distribution (this issue was already mentioned a few
months ago by some SU users). Therefore, I have reverted to a previous
version of segdread, which I am attaching to this post. I also enclose
my SEGD2SU shell script that I wrote for the data I needed to convert.
Be aware that the segdread program will allow you to decode the seismic
traces, but not necessarily all the header parameters, for instance the
navigation parameters, because these parameters may be hidden in trace
header extensions (see the SEG-D Rev<x.y> specifications and the
description of the additional parameters that may have been encoded in
the trace header extensions by the data provider).
Good luck!
Michel
--
Michel DIETRICH
Director of Research at CNRS
ISTerre
Université Grenoble Alpes
CS 40700, 38058 Grenoble cedex 9, France
Michel.Dietrich(a)univ-grenoble-alpes.fr
<mailto:Michel.Dietrich@univ-grenoble-alpes.fr>
www.isterre.fr <www.isterre.fr>
Le 08/09/2021 à 23:30, Vincent Vandeweijer a écrit :
Hey Cemal,
You probably didn't build segdread.
You need to "make sfinstall"
Good luck!
Vincent
On Wed, Sep 8, 2021, 12:19 Cemal Erdemir <cerdemir(a)hotmail.com
<mailto:cerdemir@hotmail.com>> wrote:
Hi John, and the others
I have a segd files, and I need them read and converted to segy/su
urgently, is there such a tool within my reach?
Thanks much,
Cemal
sufind segd
gives me the below
information, but no segdread does not exist
---------------------
"
cemal01@cemal-LatE6530:PPT$ sufind segd
+
SEGBREAD - read an SEG-B tape
segbread > stdout tape=
+
SEGDREAD - read an SEG-D tape
segdread > stdout tape=
ingtpatternsssns
SUNAME listings containing the pattern: segd
$ segdread
segdread: command not found
"
---------------------
Cemal Erdemir
Email: cerdemir(a)hotmail.com <mailto:cerdemir@hotmail.com>
Cell: +1 832 668 6289
Office: +1 281 858 7653
------------------------------------------------------------------------
*From:* Seisunix <seisunix-bounces(a)mailman.seismic-unix.org
<mailto:seisunix-bounces@mailman.seismic-unix.org>> on behalf of
John Stockwell <john.19071969(a)gmail.com
<mailto:john.19071969@gmail.com>>
*Sent:* Wednesday, July 24, 2019 12:29 PM
*To:* petro(a)roxo.org <mailto:petro@roxo.org> <petro(a)roxo.org
<mailto:petro@roxo.org>>
*Cc:* seisunix(a)mailman.seismic-unix.org
<mailto:seisunix@mailman.seismic-unix.org>
<seisunix(a)mailman.seismic-unix.org
<mailto:seisunix@mailman.seismic-unix.org>>
*Subject:* Re: [Seisunix] Janitor project? (also a test of the new
list server)
People interested in editing the codes are encouraged to clone the
github version
at https://github.com/JohnWStockwellJr/SeisUnix
<https://github.com/JohnWStockwellJr/SeisUnix>
With git and to push your changes up to the github site.
Sent from my iPhone
On Jul 24, 2019, at 9:26 AM, Fernando M. Roxo da Motta
<petro(a)roxo.org <mailto:petro@roxo.org>> wrote:
Hi all,
I was just installing the 44R16 release and noticed a lot of
warnings
during compilation. As an example:
/usr/include/features.h:184:3: warning: #warning "_BSD_SOURCE and
_SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
Just changing the "_BSD_SOURCE" for "_DEFAULT_SOURCE" in
'Makefile.config' reduced a lot the number of warnings. Other
warnings
still are issued though.
Some of us are sort of development savvy and could (perhaps) use
some
time to try to fix those warnings. They are possibly harmless
most of
the time, but their meaning is that the software can have some
weakness.
Wouldn't be interesting to incentive whoever are interested to
try to
fix those?
By the way, GCC is becoming more and more picky about many things,
that is, it is evolving. Some things that were treated as a warning
or even accepted are being flagged as error these days. I got
some of
these in FreeUSP compiling recently and I am having an error in
compilation of sfio/segdread:
cc -c -I. -I.. -O -Dvt_threaded=0 stdfgetc.c
In file included from /usr/include/wchar.h:43:0,
from ../sfhdr.h:304,
from stdio_s.h:11,
from stdfgetc.c:1:
/usr/include/x86_64-linux-gnu/bits/types/__FILE.h:5:25: error:
conflicting types for ‘__FILE’ typedef struct _IO_FILE __FILE;
^~~~~~
In file included from stdfgetc.c:1:0:
stdio_s.h:8:25: note: previous declaration of ‘__FILE’ was here
typedef struct _sfio_s *__FILE;
^~~~~~
Makefile:25: recipe for target 'stdfgetc.o' failed
make[5]: *** [stdfgetc.o] Error 1
I will try to dig it.
Best regards.
Roxo
--
---------------- Non luctari, ludare -------------------+ WYSIWYG
Fernando M. Roxo da Motta <petro(a)roxo.org
<mailto:petro@roxo.org>> | Editor?
Except where explicitly stated I speak on my own behalf.| VI !!
PU5RXO | I see text,
------------ Quis custodiet ipsos custodes?-------------+ I get text!
_______________________________________________
Seisunix mailing list
Seisunix(a)mailman.seismic-unix.org
<mailto:Seisunix@mailman.seismic-unix.org>
https://mailman.seismic-unix.org/listinfo/seisunix
<https://mailman.seismic-unix.org/listinfo/seisunix>
_______________________________________________
Seisunix mailing list
Seisunix(a)mailman.seismic-unix.org
<mailto:Seisunix@mailman.seismic-unix.org>
https://mailman.seismic-unix.org/listinfo/seisunix
<https://mailman.seismic-unix.org/listinfo/seisunix>
_______________________________________________
Seisunix mailing list
Seisunix(a)mailman.seismic-unix.org
https://mailman.seismic-unix.org/listinfo/seisunix