What makes you assume the graph label is wrong, rather than a simple brain-fart ? (my guess is you'd prefer the graph label to be wrong eh)
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.
And your response to the 2/3rd's of my post prior to that ? Ah, ignored. Convenient.
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...)
1) How big is "the error" ?
2) Who is claiming a specific acceleration ?
3) What makes you assume that acceleration is overestimated rather than underestimated ?
Not 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.
2)
You have claimed over-g. Several times during the last years. Like when discussing the number of times the corner went over g.
3) I assume nothing. Again, unsupported ≠ false. Tattoo that in your forehead so you see it in the mirror as a reminder.
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.
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.
*waves to your edit box* Hi, femr's edit box!
Without you providing answers to those questions your assertion is unsupported.
Done (even if the answers were already given in the context that you destroyed). My assertion is supported. It was from the beginning. Now what?
What is your problem with over-g behaviour ?
My only problem with it is that currently it has the status of
bare assertion unsupported by the evidence you've provided so far.
1) NIST data contains multiple over-g segments. (And the entirety of their 32.196 ft/s2 linear regression value is itself over-g, with their assertions stated with no error analysis at all)
They don't claim it's over g. They clearly assume that any over g behavior is due to measuring error. Like the one at the 4s mark.
3) At the start of the over-g period indicated by my data the NW corner had descend about 3ft.
4) At the end of the over-g period indicated by my data the NW corner had descend about 38ft.
Something along these lines
might succeed in supporting the claim. As stated, that alone doesn't. As it stands, the claim remains unsupported.
So ? You might want to ask yourself what information could be gleaned by tracing two static regions at different distances from the camera... ?
At the time I posted that, you hadn't provided the static point location information. I still haven't evaluated the consequences because you keep diverting my scarce time into defending myself from your strawman attacks. You
might have a valid point here,
now that you've provided that information. I'll examine that when I have time.
As has been discussed many times within this thread, to bizarrely general agreement, over-g behaviour such as is indicated by my data, is expected.
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.
I don't know why you say I'm shifting my standards.
See my previous post.
I did. Your complaints were based on points having a huge difference in distance to the camera. Let's go over this again: huge difference in distance = huge consequences; negligible difference in distance = negligible consequences. 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. 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.
I'm afraid perspective correction "depends upon" much more than that
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.
Perspective correction
methods use sophisticated techniques to find out the 3D location of the data, in order to determine its distance to the camera from a given viewpoint, 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. In the end it all boils down to that. The 3D to 2D transformation done by a camera (or our eye) is given by:
x' = k
1·x/z
y' = k
2·y/z
where x' and y' are the projected point's coordinates (the pixel coordinates of the image), k
1 and k
2 are constants that depend on the FOV and aspect ratio, x and y are the horizontal and vertical coordinates of the point to project, transformed to the camera's reference frame, and z is the depth, or in other words, distance from the camera. There's a slight difference between both concepts (distance and depth) in that the distance is sphere-shaped while the depth is plane-shaped, but at the usual distances, the radius of that sphere is so big and the region to consider so small in comparison, that the difference is negligible, therefore using the term "distance from the camera" as an approximation to refer to depth is valid.
If it were not by z, the relationship would be purely linear, as happens with orthographic projection, given by:
x' = k
1·x
y' = k
2·y
And at great distances (such as that in the Dan Rather viewpoint), a small relative difference in distance implies so little perspective distortion that it's negligible. For example, the result of dividing e.g. by 5002 meters is not significant with respect to dividing by 5005 meters. Photographs taken from a very far distance with big zoom look almost orthographically projected for that reason.
The buildings you chose as static points may well be about half the way towards WTC7; that makes a 2x difference in perspective correction. 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. 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.
Therefore, I have not switched my standards whatsoever, quod erat demostrandum.
You are basing your claim of over-g on your acceleration graph, for which you never provided error analysis
You quite sure about that ?
What? You posted some variance information, which is incomplete without the propagation of error in the measurements. And you said this yourself:
and how that error influences the velocity and acceleration plots
Haven't done such for derivative plots. Very unlikely to do so. You're welcome to do so yourself if you feel the need. I don't. Good luck quantifying error post SG derivative
So yes, I'm sure about that,
in context. NOW you have provided a bit of error information taken from the symmetric difference method, the consequences of which I still have to analyze together with all the pending stuff. For some reason I suspect it doesn't apply to any acceleration graph you've provided that you've used to claim over-g.
The actual focus of "
what you are saying" has (not so) subtly shifted as I've
corrected your false assertions along the way. You may not even realise you're doing it, which is funny as hell from my perspective.
What is the text for that irony box exploding ?
Indeed. I'll have to go with this one.
What you have done so far has been to take my quotations out of context and building strawmen out of the decontextualized version of them. I could only identify very few valid objections you've made, which I can't address because the amount of bullcrap, diversions, misinterpretations and strawmen in the rest takes all of my time.
I hope the more discerning readers of this "discussion" find that comment both "outrageous" and "funny" at the same time.
How dare
you accuse
me of... !
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.