There is a new thread about Bldg 7 freefall at JREF (
http://forums.randi.org/showthread.php?t=123340). Inside, you'll find nonsense spoken with great authority. I'd respond over there, but I don't need the resulting fecal paintjob, so I'll do it here just to put the record straight.
rwguinn wrote:In answer to why you can't measure acceleration from the video:
No accurate time reference, (frame rate can vary) no accurate (I.e., undistorted (unless you have video from straight on, perpendicular-to-the wall-at-the-same-elevation)) distance reference. A mis-measurement of as little as .05 seconds or 1 foot is significant. The time reference is also very short. Accumulated error is huge.
and later:
rwguinn wrote:Lots of videos, access to the originals (uncompressed), from many angles--plus they had access to construction details, and a whole hell of a lot better analysts and equipment than the average troother...
Almost all of this is wrong. See below for the one exception.
>>No accurate time referenceI actually can't address this because I've no idea what he's talking about, unless (despite separation by comma) it's tied into the next parenthetical comment:
>>(frame rate can vary)Yes, from one video to another, but so what? As to variance within one video, it's insignificant and is not cumulative. An hour video encompasses an hour of real time to within a small fraction of a second. Variance of frame rate is a sharp distribution about a mean and, in digital cameras, is essentially identical to an accurate timestamping datalogger. I've lamented the poor quality of internet videos, especially frame rate conversions, but it has nothing to do with this.
>>no accurate (I.e., undistorted (unless you have video from straight on, perpendicular-to-the wall-at-the-same-elevation)) distance reference.I guess he's never heard of perspective correction. In some cases it's not even necessary to know the scene geometry to correct for perspective distortion, a (x,y) scaling map might be obtained from known lengths of objects at various locations in the scene. However crude, this sort of correction field can get you to within a few percent which is good enough for many purposes. He betrays his lack of understanding by claiming the ideal orthogonal shot does not need perspective correction. Oh yeah?

(By the way, the object in the image is a flat checkerboard viewed head-on) Generally, it does require correction, with the exception discussed next.
Despite the above, for judicious choice of video, it sometimes suffices to get one vertical measurement of a known distance (# of floors) and use this as a single scaling factor as has been done in this thread. Many 911 videos are shot at considerable distance with zoom, giving a small total view angle hence allowing for small angle approximations for all but the most exacting work. In other words, with the right video, distortion is not even an issue.
>>A mis-measurement of as little as .05 seconds or 1 foot is significant.I don't disagree with this on its face but it's pretty vague. Significant in what way? Enough to prevent meaningful measurements from being taken? Hardly. As with above, such errors are NOT cumulative but represent a(n essentially Gaussian) distribution which, with enough data points, can provide reasonably sharp discrimination. Again, just like any other data recorder.
>>The time reference is also very short.I have no idea what this means or how it pertains to the discussion.
>>Accumulated error is huge.As I pointed out above, the accumulated error is insignificant.
>>Lots of videosI've looked at countless videos.
>>access to the originals (uncompressed)I can buy DVDs, too, and I have.
>>from many anglesIbid I've looked at countless videos.
>>plus they had access to construction detailsWhat do you know, he's right about that.
>>and a whole hell of a lot better analysts and equipment than the average trootherAll that's needed is a computer and freeware. I can't speak for the 'average troother' (whatever that is), but I write my own software to extract data from frames.
There, I feel better. I hate misinformation. I've posted my own caveats concerning measurement to obtain 'actual instantaneous' acceleration, and these stand. The remarks by rwguinn, however, are worthless.
PS Another poster, technoextreme, had this comment about rwguinn's assessment:
technoextreme wrote:I completely agree with everything he said.
Normally, I wouldn't take a potshot at something like this, but considering this was the first reply in the thread:
technoextreme wrote:As an engineer I can say with a 100% certainty that you can't measure acceleration using the videos.
I was going to let this slide because technically the measurement is
position, but now I have to say I'd never want that engineer in my employ. It's OK to
not know, but it's not OK to pretend you do.
Sorry for the OT, Hambone and Dr. G.