HUGE Amplitudes!

[ProfHuster]

We installed the RShake, and it seems to look good. But our amplitudes are many orders of magnitude too large (Displacements of 400 m!)

Is there something we missed in the set up?

[ProfHuster]

BTW, we are using a RPi 3 B+ over WiFi. Should we use a USB WiFi?

[ProfHuster]

Also, it is not installed in the ground, so it is on a tabletop in a room where there is a road with heavy traffic about 10 m away. Even with this, 400m displacement?

[TideMan]

The RShake measures velocities and reports these as counts.

How have you converted counts to displacement?   By integration?

Before integrating, you must high-pass filter to remove low-frequency noise which can cause large displacements, which are spurious.

[JerryP]

Where are you seeing these high amplitudes?  If on you Helicorder display, it can be changed under the DATA in the Web Front End access.

[ProfHuster]

I haven't dug into the software. A student just set up and ran the default RPi image. The large displacements, velocities and amplitudes are showing up on the raspberryshake.net station. We have the RShake 1D system.

[JerryP]

What is your system's ID and where are you on the map.please?

Sorry, I cannot answer your WiFi question as I am not using a WiFi connection.  I "believe" most users are directly connected.  Perhaps, others can advise!

Also, not sure what the "default RPI Image" is that you refer to. 

I'm sure HELP is on the way.  There are many users, worldwide, eager to help!

[Michael Huster]

The station is net AM, station R3D34.

By default image I mean the SD card that came with the R Shake kit.

--
Some useful links:
 
Manual: http://manual.raspberryshake.org/
Do It YourSelf Page: http://raspberryshake.org/do-it-yourself
Shop: https://shop.raspberryshake.org/
Website: http://raspberryshake.org/
 
Instagram: https://www.instagram.com/raspishake/
Facebook: https://www.facebook.com/raspishake/
Twitter: https://twitter.com/raspishake/
Hashtag: #rasperryshake, @raspishake
DOI: https://doi.org/10.7914/SN/AM
---
You received this message because you are subscribed to the Google Groups "RaspberryShake" group.
To unsubscribe from this group and stop receiving emails from it, send an email to raspberryshak...@googlegroups.com.
To post to this group, send email to raspber...@googlegroups.com.
Visit this group at https://groups.google.com/group/raspberryshake.
To view this discussion on the web visit https://groups.google.com/d/msgid/raspberryshake/6a093e16-634a-4e6f-acbd-e9820da88e56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Michael Huster
Pittsburgh, PA
mhus...@gmail.com

[Michael Huster]

Location is in Pittsburgh PA, the approx lat, lon is 

40.4345, -79.9909

On Fri, Apr 19, 2019 at 10:35 AM JerryP <aytonge...@gmail.com> wrote:

--

Some useful links:
 
Manual: http://manual.raspberryshake.org/
Do It YourSelf Page: http://raspberryshake.org/do-it-yourself
Shop: https://shop.raspberryshake.org/
Website: http://raspberryshake.org/
 
Instagram: https://www.instagram.com/raspishake/
Facebook: https://www.facebook.com/raspishake/
Twitter: https://twitter.com/raspishake/
Hashtag: #rasperryshake, @raspishake
DOI: https://doi.org/10.7914/SN/AM
---
You received this message because you are subscribed to the Google Groups "RaspberryShake" group.
To unsubscribe from this group and stop receiving emails from it, send an email to raspberryshak...@googlegroups.com.
To post to this group, send email to raspber...@googlegroups.com.
Visit this group at https://groups.google.com/group/raspberryshake.
To view this discussion on the web visit https://groups.google.com/d/msgid/raspberryshake/6a093e16-634a-4e6f-acbd-e9820da88e56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JerryP]

I am sorry, but I cannot get STATIONVIEW to come up today.  The station triangles appear, but no map.  The site just keeps tying to load.

 

[Ian Nesbitt]

Hi Michael,

Perhaps your units are not displaying correctly? I'm seeing displacements in the micrometer range for your station.

___________

Ian Nesbitt

Raspberry Shake Technical Support Specialist

ian.n...@raspberryshake.org

www.raspberryshake.org

On Fri, Apr 19, 2019 at 9:51 PM JerryP <aytonge...@gmail.com> wrote:

I am sorry, but I cannot get STATIONVIEW to come up today.  The station triangles appear, but no map.  The site just keeps tying to load.

 

--

Some useful links:
 
Manual: http://manual.raspberryshake.org/
Do It YourSelf Page: http://raspberryshake.org/do-it-yourself
Shop: https://shop.raspberryshake.org/
Website: http://raspberryshake.org/
 
Instagram: https://www.instagram.com/raspishake/
Facebook: https://www.facebook.com/raspishake/
Twitter: https://twitter.com/raspishake/
Hashtag: #rasperryshake, @raspishake
DOI: https://doi.org/10.7914/SN/AM
---
You received this message because you are subscribed to the Google Groups "RaspberryShake" group.
To unsubscribe from this group and stop receiving emails from it, send an email to raspberryshak...@googlegroups.com.
To post to this group, send email to raspber...@googlegroups.com.
Visit this group at https://groups.google.com/group/raspberryshake.

To view this discussion on the web visit https://groups.google.com/d/msgid/raspberryshake/49315a02-6caa-46a2-899d-80bf691c97e1%40googlegroups.com.

[Hans Rolvers]

Same here whole day, maps is gone. If displacements at 0.1 / 01 are not good, whell that’s the best I can get.

 

 

Sent from Mail for Windows 10

To view this discussion on the web visit https://groups.google.com/d/msgid/raspberryshake/CAJEanXh92pC5eU4i33hPO9%3DO0_fmzMW9qMZBRk1rF-wT%3DKdYPA%40mail.gmail.com.

[JerryP]

The stationview is back up & I agree with Ian's report.  If you are referring to large amplitudes when looking at SWARM, that can be adjusted by the SLIDER on the upper right of the display.  I have attached a copy of your station after slider adjustment.

Regards,

Jerry

[Ian Nesbitt]

Displacements of 0.1 are okay! I think the amplitudes here look normal.

___________

Ian Nesbitt

Raspberry Shake Technical Support Specialist

ian.n...@raspberryshake.org

www.raspberryshake.org

--

Some useful links:
 
Manual: http://manual.raspberryshake.org/
Do It YourSelf Page: http://raspberryshake.org/do-it-yourself
Shop: https://shop.raspberryshake.org/
Website: http://raspberryshake.org/
 
Instagram: https://www.instagram.com/raspishake/
Facebook: https://www.facebook.com/raspishake/
Twitter: https://twitter.com/raspishake/
Hashtag: #rasperryshake, @raspishake
DOI: https://doi.org/10.7914/SN/AM
---
You received this message because you are subscribed to the Google Groups "RaspberryShake" group.
To unsubscribe from this group and stop receiving emails from it, send an email to raspberryshak...@googlegroups.com.
To post to this group, send email to raspber...@googlegroups.com.
Visit this group at https://groups.google.com/group/raspberryshake.

To view this discussion on the web visit https://groups.google.com/d/msgid/raspberryshake/0f6bd455-6bb8-446b-8531-59ae9620d022%40googlegroups.com.

[Beasley Badger]

we installed ours last week and are having the same difficulty as you. Ours is in Hamilton, Ontario Canada. I see that your numbers are huge and I don't understand why the other person in this thread see the numbers that I expect to see. I wonder if my own settings in Raspberryshake can be adjusted, because I think that the unit is working fine, but the numbers, as you say, are many orders of magnitude off. This unit was fine until I unplugged it to put a longer network cable on it and move it to a spot that I could screw it in place. Once it booted back up, everything was in the billions and trillions, after it have been in the thousands and tens of thousands (like yours, a few metres from the lanes of a busy street.)

[richard boaz]

hi guys,

we really need station names to be able to follow up on any post.  without it, we really can't even start analyzing what could be going wrong.

thanks,

richard

--

Some useful links:
 
Manual: http://manual.raspberryshake.org/
Do It YourSelf Page: http://raspberryshake.org/do-it-yourself
Shop: https://shop.raspberryshake.org/
Website: http://raspberryshake.org/
 
Instagram: https://www.instagram.com/raspishake/
Facebook: https://www.facebook.com/raspishake/
Twitter: https://twitter.com/raspishake/
Hashtag: #rasperryshake, @raspishake
DOI: https://doi.org/10.7914/SN/AM
---
You received this message because you are subscribed to the Google Groups "RaspberryShake" group.
To unsubscribe from this group and stop receiving emails from it, send an email to raspberryshak...@googlegroups.com.
To post to this group, send email to raspber...@googlegroups.com.
Visit this group at https://groups.google.com/group/raspberryshake.

To view this discussion on the web visit https://groups.google.com/d/msgid/raspberryshake/7f03541a-edea-4ead-9e9c-818e93aed1e0%40googlegroups.com.

[Beasley Badger]

Thanks for the reminder for station names. Ours is AM.R3F9B

On Thursday, 18 April 2019 20:02:12 UTC-4, ProfHuster wrote:

[Beasley Badger]

I am truly just a noob here, so I might be on the wrong track, but I've done a bit of investigating to see if there is a pattern of struggles among other units. I cross checked the Raspberry Shake twitter feed to see if any other new stations announced this past week have similarly exaggerated results. I've found 4 that seem similarly affected... 

1. Announced on twitter, 16 April, 2019: AM.R4C1A located in Oklahoma

2. Announced on twitter, 19 April, 2019: AM.R0F23 located in Nepal

3. Announced on twitter, 22 April, 2019: AM.R5DAA located in Alaska

4. Announced on twitter, 22 April, 2019: AM.S8618 located in Nepal

Unfortunately, I have no idea what to do with this.

On Thursday, 18 April 2019 20:02:12 UTC-4, ProfHuster wrote:

[richard boaz]

hello,

this has been identified as a server-side issue and is in the process of being handled.  everything will be returned to normal today, sooner than later is the intent.

i will also report back when it has been fixed in real.

apologies for any inconvenience caused.

richard

--

Some useful links:
 
Manual: http://manual.raspberryshake.org/
Do It YourSelf Page: http://raspberryshake.org/do-it-yourself
Shop: https://shop.raspberryshake.org/
Website: http://raspberryshake.org/
 
Instagram: https://www.instagram.com/raspishake/
Facebook: https://www.facebook.com/raspishake/
Twitter: https://twitter.com/raspishake/
Hashtag: #rasperryshake, @raspishake
DOI: https://doi.org/10.7914/SN/AM
---
You received this message because you are subscribed to the Google Groups "RaspberryShake" group.
To unsubscribe from this group and stop receiving emails from it, send an email to raspberryshak...@googlegroups.com.
To post to this group, send email to raspber...@googlegroups.com.
Visit this group at https://groups.google.com/group/raspberryshake.

To view this discussion on the web visit https://groups.google.com/d/msgid/raspberryshake/cb619ec6-6f49-4d9f-a122-299db0ed0d6b%40googlegroups.com.

[Michael Huster]

How do I set the units? Right now when I start Swam locally, the units are counts, not m/s or a velocity units. This is how it appears in Swarm. Yes, the slider can scale the amplitudes in the helicorder view, but the real problem is that my geophone is not calibrated, I think.

To view this discussion on the web visit https://groups.google.com/d/msgid/raspberryshake/CABs%3Dv9ABqfBq-Ba14DBMFTBSLRxTBRtZc9aTo6mz_NpH7Mzemw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Michael Huster]

Is the this the server-side issue ivor.boaz referred to?

[richard boaz]

hi michael,

if you mean "why does swarm display counts instead of "real" units?", then no...

this is not a problem, per se.  this relates to the fact that you need to know the overall sensitivity of the specific instrument in order to do the conversion, where this sensitivity value differs for each combination of instrument type (and instrument hardware version), geophone type, and channel type.  this is the meta-data for the recorded seismic data.

swarm is a seismic data display program that is maintained by the USGS.  its abilities (or lack, depending) are defined by them.  typically, data display programs do not access the meta-data necessary to make this conversion.  (unlike back-end data processing programs which *must* access and read this data in order to do their calculations, e.g., PSD calculations, magnitude estimates, or any other type of processing which requires the time-domain data be deconvolved back to true ground motion.)

i am no swarm expert, but i will doubt it knows how to read this type of meta-data, ingest its contents, and then apply the various values where it needs to.  (and, needless to say, this entire concept is a huge can of worms.)

on the other hand, perhaps swarm allows for a simple input of the overall sensitivity that it could use to do the counts to m/s (and m/s^2) conversion you would like to see.  if not, this sounds like a reasonable enhancement request, which should be directed to them over at the USGS; see here.

sorry if this probably isn't the answer you were wanting to read...

cheers,

richard

To view this discussion on the web visit https://groups.google.com/d/msgid/raspberryshake/CAOY_DckWCfKVhygRxXgap_zoGiY1tXqvTpk3b1Og4CGBao5trw%40mail.gmail.com.

[Michael Huster]

My station is R10A9. The thread keeps diverting off of my station. My station shows HUGE velocities, displacements, etc. The main problem is that on shakenet, https://www.raspberryshake.net/stationview/#?net=AM&sta=R10A9 my R Shake shows up with 59 billion um/s or 50,000 m/s! 

I mentioned swarm only because Ian mentioned it above. 

So, going back to TideMan 4 days ago, how are counts converted to real units? Like I said, we burned a new SD card and it started up and ran giving these huge displacements and velocities.

Ian's response 3 days ago was not to my post but to a different station.

[Michael Huster]

OK. I just saw this might be a server problem. I'll wait until that gets settled.

[richard boaz]

hi,

the large amplitudes issue is a server-side problem that will be fixed today.  in fact, it is directly related to wrong values of overall sensitivity being used by the back-end system i mentioned in my previous post.

the conversion from counts to real units of velocity or acceleration is a completely different matter that has nothing to do with the large amplitudes problem.

have a search in the forum for other discussions that have come up in the last couple of years on this subject.  if i remember correctly, there is an answer there somehwere.  perhaps ian can help out in this regard better than i.

cheers,

richard

--
Some useful links:
 
Manual: http://manual.raspberryshake.org/
Do It YourSelf Page: http://raspberryshake.org/do-it-yourself
Shop: https://shop.raspberryshake.org/
Website: http://raspberryshake.org/
 
Instagram: https://www.instagram.com/raspishake/
Facebook: https://www.facebook.com/raspishake/
Twitter: https://twitter.com/raspishake/
Hashtag: #rasperryshake, @raspishake
DOI: https://doi.org/10.7914/SN/AM
---
You received this message because you are subscribed to the Google Groups "RaspberryShake" group.
To unsubscribe from this group and stop receiving emails from it, send an email to raspberryshak...@googlegroups.com.
To post to this group, send email to raspber...@googlegroups.com.
Visit this group at https://groups.google.com/group/raspberryshake.

To view this discussion on the web visit https://groups.google.com/d/msgid/raspberryshake/CAOY_DckawLJgToxckGEJLTN5j0pELfGHj1vNe38y46dZNhh5%2BA%40mail.gmail.com.

[TideMan]

On Wednesday, April 24, 2019 at 5:47:34 AM UTC+12, ProfHuster wrote:

How do I set the units? Right now when I start Swam locally, the units are counts, not m/s or a velocity units. This is how it appears in Swarm. Yes, the slider can scale the amplitudes in the helicorder view, but the real problem is that my geophone is not calibrated, I think.

In Swarm, hit the Helicorder View Settings button (2nd from left), then hit Wave Settings, then tick Use calibrations.  Data will be m/s instead of counts.

[Beasley Badger]

Thank you so much. The readings on our unit are looking great. L.

[richard boaz]

problem has been resolved, amplitudes should all be back to normal.

apologies for any inconvenience caused,

richard