[obspy-users] Checking readability of mseed files
megies at geophysik.uni-muenchen.de
Wed Jul 17 10:12:37 CEST 2019
please still open an issue if the program crashes (as opposed to an
exception being raised gracefully), and use your preferred file sharing
application to give us access to the file. Just let me know if you dont
use any file sharing you can upload this to I can set something up.
On 17/07/2019 02:31, Januka Attanayake wrote:
> Hi Tobias,
> Thanks. The file is 70+ MB after zipping. Thus, unless there's a
> convenient way to upload it, I'll have to slip this one through knowing
> that the file has a bad blockette. I received instructions for a
> workaround from Richard Sanderson at UCSB through the list.
> Januka Attanayake
> Research Fellow| Earthquake Seismology
> Homepage: https://sites.google.com/site/janukaattanayake
> School of Earth Sciences | McCoy Bldg. 200
> University of Melbourne | Parkville 3010 VIC
> On Tuesday, July 16, 2019, 08:15:07 PM GMT+10, Tobias Megies
> <megies at geophysik.uni-muenchen.de> wrote:
> Pleas open an issue on Github and attach one of the files that makes
> ObsPy crash on your computer. This should not happen. If anything else
> than a "read()" command is needed to reproduce the crash, please add a
> minimal code example.
> On 16/07/2019 08:01, Januka Attanayake wrote:
>> Hi All,
>> I am reading in a large number of mseed files for some analysis taking
>> several hours, and have trouble with bad mseed files that obspy can't
>> read. Every time obspy encounters an unreadable mseed file, my script
>> crashes, and I have to re-start the analysis from scratch after removing
>> them. This is very time consuming. I was wondering if anyone has figured
>> out a way to first figure out bad mseed files, i.e. the ones that obspy
>> can't read (or crashes on), and remove them in a pre-processing step?
>> Once I get rid of these files, I can directly run the anlysis without
>> any interruption.
>> I tried python -m obspy.io.mseed.scripts.recordanalyzer (Thanks Tobias!)
>> but this doesn't do the job I want. I also tried to figure this out with
>> get_flags(), but that too isn't helpful. All I want is to figure out
>> whether obspy can (or not) read an mseed file without crashing.
>> Thanks very much!
>> Januka Attanayake
>> Research Fellow| Earthquake Seismology
>> Homepage: https://sites.google.com/site/janukaattanayake
>> School of Earth Sciences | McCoy Bldg. 200
>> University of Melbourne | Parkville 3010 VIC
>> obspy-users mailing list
>> obspy-users at lists.swapbytes.de <mailto:obspy-users at lists.swapbytes.de>
> obspy-users mailing list
> obspy-users at lists.swapbytes.de <mailto:obspy-users at lists.swapbytes.de>
> obspy-users mailing list
> obspy-users at lists.swapbytes.de
EMail: tobias.megies at lmu.de
Tel: +49 (0) 89 2180-73981
Fax: +49 (0) 89 2180-73970
Department für Geo- und Umweltwissenschaften
Tel: +49 (0) 89 2180-4326
Fax: +49 (0) 89 2180-4205
More information about the obspy-users