Will,
This might save you a little time.
Here are my previously posted charts, after filtering, of femr's data, showing that proper filtering of the data does NOT produce such absurd distortions of the data.
Of course, one of the things that I did was to scan them for self-consistency before I posted them.
The first three are for the short periods just before release (t = 1.5 to 5 seconds}, when the roofline point was bouncing up & down due to vibrations within the collapsing building. It's useful to show the transformations from position to velocity to acceleration vs time with rapidly varying inputs. (i.e., to validate one's filters.)
Position vs. Time.
Velocity vs. Time
Acceleration vs. Time
Note the zero acceleration crossings at {2.18, 2.52, 3.12, 3.42, 3.80, 4.18} seconds.
Note concomitant inflection points in the velocity graph at {2.20, 2.55, 3.15, 3.46, 3.80, 4.20} seconds.
Pretty good agreement. Errors might be a slight time shift due to filters or just my eyeballing the inflection points, but the results are self consistent.
Similarly, there are zero velocity crossings at {2.22, 2.89, 4.00, 4.36} seconds.
The position graph shows inflection points at {2.38, 2.92, 4.00, 4.32} seconds.
Same. Seems to be a slight time shift due to the filters, but good consistency between the graphs.
___
Here is the same data, using the same filters, during the collapse, from t = 3.5 to 9.0 seconds
Position vs. Time.
Velocity vs. Time
Acceleration vs. Time
tom
PS. If femr wasn't in the midst of a snit, he'd likely tell you where the raw data was, so that you didn't have to digitize it.
If you decide that my graphs aren't enough to make your point, or if you just want to play with very, very, very used & tattered toys, I'll be happy to forward you the raw & filtered spreadsheet data that I've got.
I'm going to give femr2 about 10 days to figure out where he went wrong. If he hasn't figured it out by then, I'm going to digitize his velocity curves directly from his graphs, calculate the derivatives, and then compare those competently calculated acceleration curves to the ones he's been feeding us. At the very least, that will provide a dramatic visual demonstration of the true uncertainty in femr2's acceleration graphs.
Why am I giving femr2 10 days? Because the digitization, calculations, and construction of overlay graphs will take several hours of my time, and I'm too busy right now to waste that much time on femr2's obvious mistakes.
This might save you a little time.
Here are my previously posted charts, after filtering, of femr's data, showing that proper filtering of the data does NOT produce such absurd distortions of the data.
Of course, one of the things that I did was to scan them for self-consistency before I posted them.
The first three are for the short periods just before release (t = 1.5 to 5 seconds}, when the roofline point was bouncing up & down due to vibrations within the collapsing building. It's useful to show the transformations from position to velocity to acceleration vs time with rapidly varying inputs. (i.e., to validate one's filters.)
Position vs. Time.
Velocity vs. Time
Acceleration vs. Time
Note the zero acceleration crossings at {2.18, 2.52, 3.12, 3.42, 3.80, 4.18} seconds.
Note concomitant inflection points in the velocity graph at {2.20, 2.55, 3.15, 3.46, 3.80, 4.20} seconds.
Pretty good agreement. Errors might be a slight time shift due to filters or just my eyeballing the inflection points, but the results are self consistent.
Similarly, there are zero velocity crossings at {2.22, 2.89, 4.00, 4.36} seconds.
The position graph shows inflection points at {2.38, 2.92, 4.00, 4.32} seconds.
Same. Seems to be a slight time shift due to the filters, but good consistency between the graphs.
___
Here is the same data, using the same filters, during the collapse, from t = 3.5 to 9.0 seconds
Position vs. Time.
Velocity vs. Time
Acceleration vs. Time
tom
PS. If femr wasn't in the midst of a snit, he'd likely tell you where the raw data was, so that you didn't have to digitize it.
If you decide that my graphs aren't enough to make your point, or if you just want to play with very, very, very used & tattered toys, I'll be happy to forward you the raw & filtered spreadsheet data that I've got.
Last edited: