[obspy-users] GSE2 - Mismatching checksums
barsch at egu.eu
Thu Mar 16 11:16:11 CET 2017
currently no idea - please open a bug report at
https://github.com/obspy/obspy/issues - attach a sample file and a small
script showing the issue. Leave also a note about the used ObsPy &
Python version. Otherwise we can't reproduce this problem.
Thanks + Cheers,
Am 15.03.2017 um 17:06 schrieb Reiter, Franz:
> Dear Robert!
> Thank you for your kind help. Sorry that I did not check in the help before writing to the list!
> You are right. The files are about 10 years old and probably contain checksum errors.
> I could solve all cases with checksum error now.
> In the meantime another error came up on reading some of those gse2 files. The error is raised on executing the stream read function:
> Traceback (most recent call last):
> File "C:\Anaconda3\envs\obspy\lib\site-packages\obspy\io\gse2\libgse2.py", line 173, in read_header
> header['starttime'] = UTCDateTime(**date)
> File "C:\Anaconda3\envs\obspy\lib\site-packages\obspy\core\utcdatetime.py", line 330, in __init__
> dt = datetime.datetime(*args, **kwargs)
> ValueError: second must be in 0..59
> Does anyone have an idea how to solve this or where it could come from?
> Thank you all
> Message: 2
> Date: Tue, 14 Mar 2017 08:43:39 +0000
> From: "Reiter, Franz" <Franz.Reiter at uibk.ac.at>
> To: "obspy-users at lists.swapbytes.de" <obspy-users at lists.swapbytes.de>
> Subject: [obspy-users] GSE2 - Mismatching checksums
> <B43E97EB84E76A4D939F6831FCA826AD8BCAAE83 at XMBX2.uibk.ac.at>
> Content-Type: text/plain; charset="us-ascii"
> Dear collegues!
> I received a bunch of GSE2 files, each of them for one earthquake event, containing several traces.
> I wrote an obspy script to convert each trace to mseed format (read gse2 into a stream and write each trace to mseed).
> The following warning appears when reading the files:
> "Checksum differs only in absolute value. If this file " + \
> "was written with ObsPy GSE2, this is due to a bug in " + \
> "the obspy.io.gse2.write routine (resolved with ), " + \
> "and thus this message can be safely ignored."
> But reading works fine in this case.
> Some of the GSE2 files cannot be read by Obspy at all. I receive the following error (example):
> ChksumError: Mismatching checksums, CHK -7224649 != CHK 231752008
> Does anyone know more about this error and if there is a way to force Obspy to read those files into a a stream object?
> Thank you and best regards
> Franz Reiter
> PhD student
> University of Innsbruck
> Institute for Geology
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.swapbytes.de/pipermail/obspy-users/attachments/20170314/b241c5b1/attachment-0001.html>
> Message: 3
> Date: Tue, 14 Mar 2017 11:33:05 +0100
> From: Robert Barsch <barsch at egu.eu>
> To: users at obspy.org
> Subject: Re: [obspy-users] GSE2 - Mismatching checksums
> Message-ID: <50bc24d1-980e-8a00-1e47-1826f725163f at egu.eu>
> Content-Type: text/plain; charset="windows-1252"
> Dear Franz,
> you can ignore the warning if your GSE2 files were written with a very old ObsPy version. The files with checksum mismatches seem to be broken.
> However the GSE2 checksum is known to have issues - some GSE exporting programs wrote for years wrong checksum values. That is the reason ObsPy also offers a very handy verify_chksum parameter for the read function, see link below for more information.
> obspy-users mailing list
> obspy-users at lists.swapbytes.de
Dr. Robert Barsch
EGU Office Munich
eMail: barsch at egu.eu
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 181 bytes
Desc: OpenPGP digital signature
More information about the obspy-users