Third time lucky eh

(How many times did you
actually abandon your original post ?

)
Frankly, I don't see why you say I'm switching datasets, especially given you've been doing what you criticize all the time, including the posting of Dan Rather static point location when the static points being discussed were from Cam #3. That's called double standards according to my dictionary.
LOL. You switch between complaining about early motion "claims" and acceleration "claims" so often, the occasional (admitted) brain fart is inevitable
I didn't have that much time. Had to cut somewhere. I'm forced to be selective. You have a tendency to post walls of text. (So does Ozeco, and amazingly he complains about other doing the same...)
How very convenient for you
Always paying attention.
1) The error I took for that statement was tfk's 80 ft/s², as would be obvious if you looked at it in context. I was not serious using it, as would be obvious if you looked at it in context. It was an example of why error analysis matters, as would be... you know the rest.
Oh, so you
don't have any issue with acceleration plot error bands ?
2) You have claimed over-g. Several times during the last years.
I have indeed.
Like when discussing the number of times the corner went over g.
ROFL. No that was tfk, with his ludicrous claims of passing over the "over-g" threshold a specific number of times, based upon his wildly (and clearly method based) smoothed curve oscillations
I beg to differ.
Again, unsupported ≠ false. Tattoo that in your forehead so you see it in the mirror as a reminder.
Read the thread(s). That I've posted information you haven't managed to spot yet is not my problem, it's yours.
I provided you with some information you claimed hadn't been posted "not long ago", yet you are still clinging to the notion that the details you "believe" have not been discussed (many times) are "absent". Get a grip man.
+/- 3 ft/s
2 ring any bells ?
All of these were responded in the post, if you looked at it in context instead of sentence by sentence. You cut the trees and then claim there's no forest.
Again... So you
don't have any issue with acceleration plot margins of error ?
I think you must be hitting reply before reading the post, and then reading and replying as you read each sentence, instead of reading, understanding, and then hitting reply. Which makes you miss the context completely. It's the best explanation for your MO.
ROFL. You can try and run away from your assertions but let me repeat your own words...
"Your claim of over-g is not supported by your analysis because the error is too big to claim a specific acceleration."
No "context" going on there. An assertion you've made many times for varying and shifting reasons....unless you're retracting it ?
Exactly where does "context" come in ?
*waves to your edit box* Hi, femr's edit box!
Hi pgimeno's third abandoned reply over the last six hours
Done (even if the answers were already given in the context that you destroyed). My assertion is supported. It was from the beginning.
No, it's not. So are you personally happy with acceleration plots as provided ?
My only problem with it is that currently it has the status of bare assertion unsupported by the evidence you've provided so far.
ROFL. What happened to your "context" based dismissals ?
(Managed to spot me hinting that error estimation on acceleration has already been provided yet ? (perhaps not, early in the post I guess)
They don't claim it's over g.
Quite correct. It is. WHY don't they say what it is ? Why do they arbitrarily say "AT" ? Why is it okay for NIST to perform zero error analysis, come out with results that indicate over-g then state "AT" g ?
They clearly assume that any over g behavior is due to measuring error. Like the one at the 4s mark.
Assumption is the mother of all...
Defending NIST ? Nice
Again, exactly why do you think over-g is an issue ?
Something along these lines might succeed in supporting the claim. As stated, that alone doesn't. As it stands, the claim remains unsupported.
No,
those claims are utterly specific. You can quibble about magnitude error in the data, but the claims you are claiming are unsupported are "just not".
At the time I posted that, you hadn't provided the static point location information.
ROFL. I provided that information in
2010
I still haven't evaluated the consequences because you keep diverting my scarce time into defending myself from your strawman attacks.
I'm not making strawman attacks. I'm showing your clear lack of understanding about the effect of perspective. I'm providing you with information you clearly don't understand. I suggested you should stop, but your ego has clearly kicked in. Bad idea. ROFL.
You might have a valid point here
No, I, unlike you, know what I'm talking about. You, unlike me, are talking utter faeces.
My "point" is absolute.
You can ask me what I'm talking about if you don't understand you know
now that you've provided that information
The image I provided you with included two static trace regions. I already provided you with the relevant information. That your knowledge is lacking is not my problem
I'll examine that when I have time.
If you don't have an instant understanding you REALLY shouldn't be making the inept assertions you have been diggin your own hole with.
Again, would you like me to explain ?
What good is you examining anything going to do ? You are showing repeatedly you "don't know your posterior from your elbow" in this arena
Yes, including me, which doesn't mean it occurred. And before you jump the gun again, see above about what you should be tattooing in your forehead.
See later in my post where I provide you with resultant error analysis estimation
I did. Your complaints were based on points having a huge difference in distance to the camera.
ROFL. No, they were not. They were based upon you dismissing perspective correction when tracing motion of the NW corner over a 200 pixel range, yet asserting that (hint) amplification of camera motion with differing camera-object distance, with a magnitude of 0.02 pixels was somehow more significant.
ROFL. "DL". "Irony explode", ...
Again ? When did you dig this hole before ?
huge difference in distance = huge consequences
Not necessarily. All manner of factors come in to play. Rewind to me informing you about the extra information you could obtain by tracing two static regions with differing distances from the camera ?
(A massive hint)
Exactly how large do you think the amplification of motion obtained from static region traces nearer to the camera is going to be further from the camera, in the specific case of the (surely) cam#3 footage ? [rolleyes]
(Another massive hint... if you trace two "distances" you can see the difference) [rolleyes]
negligible difference in distance = negligible consequences
Utterly viewpoint determined [rolleyes]
And if you had paid attention to the context of my post, you'd have seen that my suggestion regarding using Cam #3 acceleration plots included ignoring the vertical axis units and using the graph for what the Dan Rather based ones are good for: looking at the overall shape of the graph.
ROFL. Fill that massively deep hole in quick son. I've already expressed (years ago) that the general profile shape is similar between cam#3 and Dan Rather datasets, however,
YOUR "issue" is about magnitude...at which point the skewing caused by perspective effects becomes particularly significant [rolleyes]
Which, beyond the fact that it reveals a segment not as horizontal as it would be expected when comparing it with NIST's analysis, I don't see the point of.
Say wha' ?
Maybe I should have said perspective distortion (which needs a corresponding correction) depends on distance to the camera. You usually have no problems with using the terms the way you want them to mean. Now having problems if someone else does the same? Dude, you're full of double standards.
ROFL. You clealry have no understanding of the effect of perspective upon trace data extracted from video. Can't resist (as it's been necessary for pretty much every other para...) [rolleyes]
Perspective correction methods use sophisticated techniques to find out the 3D location of the data
Deary me. Perspective correction from a known camera location is pretty trivial, and certainly doesn;t resolve position in full three dimensions [rolleyes]
in order to determine its distance to the camera from a given viewpointp
Distance ? Distance ?

ROFL. Hows about "orientation" and "field of view" and ... [rolleyes]
and compensate for that by undoing the projection the camera has done in order to obtain a purely linear relationship, and undoing it depends exclusively on distance to the camera.
ROFL. Oh. My. Days. [rolleyes]
In the end it all boils down to that.
Just walk away [rolleyes]
The 3D to 2D transformation done by a camera (or our eye) is given by...

I'll wade through your "verbage" when I stop laughing. Can hardly see right now [rolleyes]
The buildings you chose as static points may well be about half the way towards WTC7
Building
S ?! ROFL. No. One set close, one set further away [rolleyes]
that makes a 2x difference in perspective correction
ROFL. You're not even talking about perspective correction, and you don't even realise it. LOL.
Big deal, compared to the difference between distance to the top and distance to the bottom of the NW corner, which for the purpose of watching the shape of the acceleration plot, is negligible.
ROFL. #must remind myself to repost information about inter-window spacing [rolleyes]
You implicitly acknowledged that importance when you pointed to the Dan Rather static point location, saying that the building chosen was at a similar distance to the camera as WTC7 was.
The closer the better, absolutely ! What is hilarious is your inept extrapolation [rolleyes]
Therefore, I have not switched my standards whatsoever, quod erat demostrandum.
How many [rolleyes]'s does it take to sink in [rolleyes]
What? You posted some variance information, which is incomplete without the propagation of error in the measurements. And you said this yourself

In the post you are responding to I provided you with error estimation for acceleration [rolleyes] (in other words propogation of error from displacement/time to acceleration/time [rolleyes])
You claimed that variance (and scaling metric) information didn't exist. Seems you were quite wrong. LOL. [rolleyes]
So yes, I'm sure about that, in context. NOW you have provided a bit of error information
ROFL. Information provided long, long ago son. [rolleyes]
taken from the symmetric difference method, the consequences of which I still have to analyze together with all the pending stuff.
Analyze ? [rolleyes] Given the "assuredness" of your "prose" you shouldn't have to blink twice [rolleyes]
For some reason I suspect it doesn't apply to any acceleration graph you've provided that you've used to claim over-g.
You can suspect what you please. You can flail about ALL OVER THE PLACE as much as you please. Given your recent "performance", forgive me if I point and laugh more than try and continue to help you [rolleyes]
What you have done so far has been to take my quotations out of context
Nope [rolleyes]
and building strawmen out of the decontextualized version of them.
Nope [rolleyes] Great nice longey wordy tha' [laughs big smiley]
I could only identify very few valid objections you've made
Would you like a list ? [rolleyes]
which I can't address because the amount of bullcrap, diversions, misinterpretations and strawmen in the rest takes all of my time.
What can I say, but...
Dear. Oh dear. Oh dear. Oh dear.
I'm afraid the more discerning readers will see your sentence splitting and decontextualization and see through the way you manipulate it in order to make it seem you're right.
You just believe whatever it is that you want to believe. Great job sir.
Never had to place so many

's in one post. [rolleyes]
(And had to change loads of them to text as the JREF forum doesn't allow 57 "images". LOL)