Page 1 of 1

Seismosignal can not read long-term measurement data.

Posted: 09 Jan 2019, 05:59
by llem0
Dear Seismosignal team.
I would like to ask you for a recommendation for some software that can analyze long-term measurement data. For example at a sampling rate of 512Hz for 8 hours.

Kind regards

Re: Seismosignal can not read long-term measurement data.

Posted: 09 Jan 2019, 15:46
by Fanis_Moschas
Dear llem0,
It would help if you could provide us with more information.

Concerning the length of your time series, what is the length (in time series points) of the maximum time series you are interested in analyzing? Are you interested in analyzing the full 8 hours recording (some millions of points) or is it possible to break it into smaller ones? For Example SeismoSignal is capable of handling time series of a maximum length close to 260000 points.

Also in what type of analysis are you interested in? Time Series analysis (Fourier analysis, filtering etc.) or something different than that?

Thank you in advance for your feedback

Re: Seismosignal can not read long-term measurement data.

Posted: 21 Jan 2019, 05:35
by cibyjac
I am using Seismosignal version 2018, Release 2, Build 10, academic license. "For records larger than 32768 lines, the Fourier and Power spectra as well as the mean period Tm, cannot be calculated" error is being shown. Since this limitation is there, for long duration earthquake data, the Fourier analysis is not possible.

Re: Seismosignal can not read long-term measurement data.

Posted: 21 Jan 2019, 14:01
by huffte
Accelerograms, from real earthquakes, having fewer than 32,000 time acceleration pairs are abundant. There are, however, records having more than 32,000 points. In such a case it may be possible to load the data and use the 'frequency' value when the record is loaded into SeismoSignal.

For example, if I have a PEER-formatted record (5 acceleration values per line starting with line 5) with 60,000 acceleration values and a time step of 0.005 seconds, I could specify a frequency value equal to 2 (read only every other data point) and a time step equal to 0.010 (2 times 0.005). This would result in a 30,000 data point record. Similarly, I could specify a frequency value equal to 4, a time step equal to 0.020, and end up with a record having 15,000 data points.

Note that this does not alter the data read. It only skips a certain number of points. So, if the integrated velocity and displacement records are still accurate, the effect of skipping data points may be minimal, depending on the desired intensity measures to be studied. When using this approach, care should be taken in using extremely long period intensity measures.