Below is a snippet of Python code that uses the ObsPy library to access, low-pass filter, and display three hours of data from one of my R-Shake devices. The lowpass filter is needed to reduce the traffic noise, but some spike-glitches which happen at irregular times are relatively huge. Ideas?
There are also some gaps with just plain missing data, I assume due to my internet dropping out, but I think that is a separate issue.
I’ve been looking at how to eliminate the spikes.
The trouble is that they are persist over several seconds and their energy is spread over a wide frequency band. Also, they are not too dissimilar from EQ waves, though the human eye (a superb instrument) can distinguish them quite easily.
The shape of the spikes is quite similar to Daubechies-type mother wavelets and I’ve been trying to use OWT (orthogonal wavelet transformation) to isolate them, so far without success.
In the meantime, I’ve found that eye-ometer followed by excision is the best method.
Kernel modules loaded : NO
Enablement : OFF
Thanks Branden. Both my R-Shake units use wired ethernet. Above text appears in both “myshake.out” files from the two devices, so I assume this means there is no wifi active. One is in the woods out back, and the other is in the front yard but underground, so I’m hoping there isn’t much RF immediately nearby.
default setting is that WiFi should be OFF, unless explicitly requested to be ON. not sure if it was ever on in the past and then didn’t get turned off? in any case, there are a couple of ways to turn it off:
via the front-end, proceed to SETTINGS::NETWORK::WIFI SETTINGS. if WiFi is ON, the checkbox should be checked “Connect to WiFi”. Turn this off and click the button.
if #1 is not true (“Connect to WiFi” is not checked), then log in to the unit and navigate to the directory /opt/settings/user and edit the file enable-wifi.conf. change the last line / setting to OFF from ON and reboot the unit
WiFi will then be turned off and your spikes will be forever in the past.
I see the glitches on both my systems. Here is the one that’s underground:
The lead-in cable is a CAT6 direct-burial type. Inside the wood box under the brick weight is just the geophone sensor, the Shake board mounted on a Pi-Zero, USB cable, and 5V power wires that are soldered to to the Shake board. The geophone is clamped to the plywood case using 0.041 stainless steel wire, twisted tight. The case sits on three leveling screws, which rest on the concrete pad.
The other night we were watching TV and a 3.2 hit us, but it only seemed to rattle the rafters. Then 2 minutes later we got another one. And again 10 min later. The epicentres were a few hundred m from the RS. They need to be >4.5 to worry us.