A user has three signals captured using a triaxial accelerometer and asked “What is the simplest way to get the XYZ resultant from run-up file?” He had tried forming a resultant of the raw time histories, but didn’t fully understand the resultant time history.
Of course, the correct way of processing the data is to calculate the individual waterfalls from the x, y & z data and then calculate a resultant waterfall. (more…)
This note is based on a real requirement presented to Prosig by a prospective user. It’s the sort of challenge that we relish. This case is a great example of a real-world signal processing requirement and also great test of some of the unique features of Prosig’s DATS software. It also shows the power and flexibility of the new DATS V7.0 worksheets.
When we have a very noisy signal with a large number of spikes and signal bursts then if all else fails try Median Filtering. This is a technique often used in cleaning up pictures. The operation is almost childishly simple in concept but we will save the details until we have examined an example.
In many real-world applications it is impossible to avoid “spikes” or “dropouts” in data that we record. Many people assume that these only cause problems with their data if they become obvious. This is not always the case. Consider the following two time histories.
