Dear SEISAN community,

I have been trying to run the CORR routine to identify
unknown/uncatalogued events with similar waveforms in a continuous
database, where the master event waveforms are already sliced, so only
the scanned continuous waveforms are whole.
My problem, so far, is that I am constantly getting segmentation
faults, even when MULPLT is able to deal with the waveforms (I got
segmentation faults while using SEISAN 9.1 MULPLT on the same
waveforms, by the way). Could this be a limitation of the CORR
routine? What can the maximum length (in samples) be? Is the data
format much relevant in this case?
I must say I sliced one of the continuous waveforms in a 6 hours
segment and I was able to run the program. So I suppose I could do the
same for all the months of data I have, but before doing that, I would
prefer to have some expert opinion on what is the maximum length
allowed. However, I couldn't split the file using WAVETOOL
(Segmentation Fault)  ou rdseed_many, nor SEISEI, I had to resort to
ObsPy to slice/split the waveform. Is there a way to do it in SEISAN?
There must be, if MULPLT can read the long SEED files, there must be a
way for other programs to read them...

I am currently using SEISAN 10.3, and my waveforms are in miniseed.
All advice is very welcome.
Thank you all in advance,

Best regards,


PS : Dear developers, there is a typo in the version tag : " SEISAN
10.3 ,  Janauary 2015 "

--
Emanuel Antunes

Seismology Laboratory
Instituto Superior Técnico (IST)
Universidade de Lisboa (UL)

_______________________________________________
seisan mailing list
[email protected]
http://mailman.uib.no/listinfo/seisan

Reply via email to