This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Bounce Characterization (Count, Time)
(01-24-2020, 06:22 PM)Sebastian Staacks Wrote: This might be possible, but this highly depends on what the recorded signal looks like and if we can come up with a way to detect these "bounces" in a reliable way with the means provided by phyphox. The magnetic ruler expriment does something similar by detecting peaks in the magnetometer data and plotting their times. Do you have example data? Is it just a short acceleration peak that occurs at a rate of about 4-6 Hz or did I misunderstand you there? If so, does the "acceleration stopwatch" work for you (check the "many" tab)? If so, is it only the count you are missing?

So the purpose of this is to identify what is causing my desk to bounce up and down at work.  I am on the second floor of a building, and there are various pieces of equipment on the floor below me that run at different times.  I measured the bounce using phyphox Acceleration Spectrum, and the peak frequency during the bounce is either 4.72Hz or 5.12Hz.  What I'm looking for is to be able to record data for some time period (ideally a full day) and characterize during which times there is a significant spike at that frequency.  Then I can work with my facilities group, for example, to find out which machines were running during that time.

Acceleration stopwatch just tells me when the acceleration is above a certain threshold, but not the frequency.  So as far as I can tell, it would be difficult to isolate the regular bouncing from (for example) typing on my keyboard, or setting my phone on my desk.  Either of those events generates acceleration spikes larger than 0.17m/s2, which is the threshold necessary for the bouncing to trigger a result in Motion Stopwatch.

Messages In This Thread
RE: Bounce Characterization (Count, Time) - by Charles Haase - 01-24-2020, 10:23 PM

Forum Jump: