As an extreme example, does the acceleration pattern seen in the purple graph seem realistic to you?
[qimg]http://www.cesura17.net/~will/Ephemera/Sept11/Femr2/sg51.png[/qimg]
For an insect, maybe. For a large, heavy object, no.
Not all output can be considered to be representations of the actual acceleration. One has to experiment in order to move toward the most realistic solutions.
Yes.
Of course, I've worked with actual accelerometers and raw data recorded by accelerometers, which usually does look like the purple graph (because things that move also tend to shake and vibrate), so I don't have the benefit of vague intuition telling me what such data "should" look like.
I tend to agree with you: Yes, the actual acceleration profile of a precise point on the surface of the NW roof corner - say, a specific radioactively marked molecule - might be that wild, because the material it's sittiing on shakes and vibrates as the building rubles to a violent fall.
It is however, with utmost certainty, NOT the acceleration profile of the purple graph. That is because we can't measure that point with the sort of precision I indicated, and instead each individual measurement is fraught with several errors. The purple line probably is dominated by the random fraction of those errors, not the actual fine movement.
I'm going to pick up from here, if I may.
First of all, Oystein is correct in saying that the purple graph is not an accurate reconstruction of the actual acceleration. There is no way to reconstruct any actual high-frequency signal that was lost in between the video frames. (Fractal interpolation can generate a likeness of such a signal, if one knows or assumes it was there in the first place and makes certain assumptions about the underlying spectrum; thus, a fractally compressed photograph of a forest can be enlarged beyond the original size of the photograph, and will show interpolated detail that was not there in the original photograph, but that will not be the same detail that actually existed in the scene when the photograph was taken. It's quite likely that the purple trace is doing essentially that.)
But that wasn't the question I was answering, which was "does the purple trace seem realistic?" To which I answered in the affirmative.
The reason it seems realistic is the nature of short-timebase accelerations. Most people have reasonably correct intuitive understanding of sustained accelerations such as in vehicles or falling, and even an approximate recognition of their magnitudes (such as, half a g lateral acceleration is impressive performance for a road car, corresponding to a zero-sixty time of about five seconds). For faster events such as collisions, people's intuitive sense of the magnitude is poorer, which is why for instance public service messages have to remind people that a baby held in arms in a car cannot be held onto in a moderate-to-high-speed collision. And for very fast events, most people don't have the slightest clue.
For example, one accelerometer device I have used extensively is designed for recording human activity on the scale of hours to days. The accelerometer in it triggers whenever accelerations of 0.1g or greater occur. You can hold the device in your hand and move it around very smoothly and gently, and it will not trigger. But if you hold it in your hand while making normal gestures, or very gently shake it, it will trigger. That's all pretty intuitive so far.
Now suppose I rest the accelerometer on a desk or table -- such as a sturdy steel office desk with a heavy top, weighing a total of 200 pounds. Without touching the accelerometer device itself, what do you think I would have to do to the desk, to get the device to trigger? Perhaps, grabbing the edge and shaking with all my strength? Or lifting up one end a few inches and letting it slam back to the floor? Or hitting the desk with a sledge hammer?
Actually, all it takes to trigger the device is a gentle tap with one finger, with about the same force you'd use to type a character on a computer keyboard, anywhere on the desk top.
And that's not a flaw or failure or "measurement error" in the device. The finger tap does actually cause a >0.1g acceleration of the desk top to occur, so the device is correct to trigger as a result. The acceleration just occurs for a very short time, producing what we would feel as only a very slight (if perceptible at all) vibration. Our intuitive sense of the magnitude of that acceleration is way off, because the time and distance scales involved are so small.
And note that we're not talking about a molecule here as Oystein suggested, nor the insect posited by Major Tom. A big steel office desk.
Now suppose instead of a single desk, we use a heavy counter that's bolted to the wall and runs the entire length of the room. Does the finger tap still work? Yes it does, if it's within a few yards from the device -- because while the larger counter has more mass (and the counter + the wall it's bolted to + the rest of the building the counter is part of far more still), objects generally get less rigid as they get larger, so the finger tap can still vibrate the portion of the counter near the accelerometer, so as to cause >0.1g acceleration.
Now perhaps you can see why if you affix an accelerometer to, say, the dashboard of a car prototype performing a quarter mile acceleration test (aka a drag race), the data you get will not be a smooth trace of the car's acceleration from zero to eighty mph. It will be full of spikes and swings of a full g and more, much like Tom's purple trace, or likely far worse. And --
-- yes, here is where I get to the point --
that's not noise.
That's the actual acceleration of the dashboard.
(That's not to say that there might not be additional measurement error or instrument noise on top of that. Just that even without any such error or noise, you'll still get an incredibly messy-looking trace.)
You can only call some aspect of the data trace "noise" once you've defined what it is you intended to measure or evaluate.
For example, an engineer interested in the overall torque output of the prototype car's engine and drive train, who wants to know how well the car accelerated down the road, would use a low pass filter on the data, to filter out all the high-frequency signals, the clunks and rattles and vibrations that don't figure in "how fast this baby pulls out" and so are just noise for his purposes.
And in the adjacent office, another engineer interested in the performance of the vibration-damping engine mounts, would use a high pass filter on the same data, to measure how much high-frequency vibration from the engine was getting through to the dashboard at various speeds. She doesn't care about the down-the-road acceleration, or lower-frequency bumps in the road, so the part she filters out is just noise for her purposes.
And in other adjacent offices, there's an engineer studying the performance of the car's suspension, and another studying the smoothness of the clutch during gear shifts. They would use two different bandpass filters on the same data, to filter out the road acceleration and the engine vibration and everything else that's just noise for their purposes.
None of them, though, are getting the "true acceleration" out of the data. The closest thing they have, or could ever get, to the "true acceleration" is the raw data itself. (The only exception to that would be that if there were known sources of instrument noise, with known characteristics e.g. a known frequency and magnitude or a known DC offset, those could be compensated for or filtered out before the data is passed along to the four engineers.)
So, how does that relate to the measured movement of the top edge of the outer curtain wall of Building 7?
Barring any rocket engines (or helium balloons, winch cables, etc.) in operation at the time, the only known constant influence on the structure is gravity.
By using a very low-pass filter on the data (that is to say, smoothing), you can get a pretty curve showing the net result of the influence of gravity on the wall. But in that case what you're filtering out is "noise" only if you were trying to use the fall of the building to measure the acceleration of gravity. Which I think I can safely presume is not your objective here; there are many far better and easier methods for measuring g.
For every other purpose, what you're filtering out is part of the signal. Such factors as "resistance" of the lower structure, which would have to involve multiple separate instances of breaking and crushing of structural members; collisions and impacts in the course of collapse, including those that could transfer impulse from other hidden parts of the structure; and even the effects of explosives, if there were any; would all involve higher-frequency events that you're filtering out, and likely would involve magnitudes of acceleration both positive and negative of a significant fraction of a g and more.
Which leaves me, like others, at a loss for what purpose this can serve.
Respectfully,
Myriad

