Merged Discussion of femr's video data analysis

You can't be trusted. Swamp the trivial point with waffle.
*shrug* You keep missing the word "segment" which was there since the beginning and validates my reference. Any graph with a straight horizontal line at about 32.2 ft/s² would have served the exact same purpose; even tfk's graph. Your strange way of understanding things is not my problem. Also, unlike you, I do concede when I think you're right, which in this case I don't. Your misrepresentation of the facts in order to attack me is what concerns me here. And your ad hom "you can't be trusted" is a low blow. There are many more issues of trust with you and your blunders, misinterpretations and nonstandard use of terms.


I'm "soooo" not interested in your wandering definition of "wrong".
My definition has been steady all this time. Your interpretation is what has been wandering (read: wrong most of the times) and I have had to correct numerous times and to use big red letters and to suggest you to tattoo it in your forehead. And for the looks of it, I'm not yet done. :rolleyes:


If you don't think there is a period of over-g, prove it ;) (And good luck with that)
Again, I don't know if there's a period of over-g because you haven't proved there is. I don't care enough as to put the effort of proving it either way. I do care that you make a categorical assertion without proving it.


I haven't dismissed "depth" in the slightest.
Maybe. I got that idea from here:
I've always said that perspective correction depends on the variation of distance to the camera.
I'm afraid perspective correction "depends upon" much more than that :rolleyes:
Which as it stands, is a false statement. Mine wasn't 100% accurate, because of my usage of distance instead of depth, but it's the only factor variable needed for perspective correction. By the way, the difference between distance and depth is < 0.6% based on the ~12° angle of view that I estimated (focal length in 35 mm film equivalent is about 160 to 200 mm).


Are you quite sure about that ? :) Perhaps you'd care to highlight why a point TL of frame and a point BR of frame are not affected by lens field of view effects. Perhaps you'd care to highlight why narrow field of view lenses and wide field of view lenses are identical in terms of perspective correction. Etc.
:rolleyes: Again, lens distortion is not perspective distortion. Maybe your software corrects for both at the same time, but they are entirely different types of distortion with entirely different causes. I have not been talking about lens distortion. You keep talking about lens distortion as if it was part of perspective distortion. It is not. Your nonstandard use of terms is your blunder. Deal with it. Perspective distortion is influenced ONLY by depth.


Who are you trying to "educate" ?

It's clear you are googling as you go.
:rolleyes: I explained the influence of FOV and orientation several messages ago, when you introduced them as factors for the first time. No, I merely thought about it. No need to google concepts I'm already very familiar with.


What "SG data" have I refused to provide ?
Parameters.


ROFL. If I provide you with such data you'll simply spend another year whingeing about how it was calculated. Do it yourself.
If you claimed inch precision, maybe I'd question that. I plan to give error bands for a range of credible camera positions.


What "other data" have I refused to provide you with ?
Static point location information for cam #3 was provided only several messages after I asked. There have been quite some other similar instances in which you haven't provided the data. We'll see if you provide the pixel aspect ratio information I request below.

Yes, I know, it is my problem to go over each of your 3400+ messages here and your who-knows-how-many messages in every other forum you've participated, as well as over each of your web pages. As everyone knows, the customary thing when writing a report or reply to a discussion is not to add references. When, for example, Bazant and Le wrote this in their reply to Gourley (BL 2008):

This energy has been calculated as 0.35ms(v1² + vcu²) by using the theory of comminution (Bažant et al. 2007).​

they were being just extremely magnanimous, as they could have just said:

This energy has been calculated as 0.35ms(v12 + vcu2) by using the theory of comminution (it's your problem to find the reasoning, it's already published in my works).​

as is customary in discussions. :rolleyes:


Splendid. Now, how are you going to go about synchronising multiple videos, managing differing scaling metric, feature resolution, differing noise levels, differing camera position accuracy, ... ? :rolleyes:
I have ideas for all of these. In the end it all translates to an error band. Any other variable you want controlled?


That would be a wonderful "clarification", except the pixel aspect ratio isn't 1:1.
Then?

See my previous post :)
I see nothing about pixel aspect ratio. Anyway I planned to add some checks.


Also, a quick points from my earlier post you decided to ignore...
The useful output from all the various trend views is simply trend shape and magnitude. All methods presented show similar trend shape and similar magnitude. Peak acceleration between both poly and both SG plots are within a few ft/s^2.
Doesn't mean either is correct. That doesn't prove over-g. No reason to comment on a non-proof.


(How long does it take you to write a post ?! Approaching 2 hours...)
:rolleyes: It can even take days. It depends on how much time I have and what other things I do meanwhile. Why your obsession about my posting timing? You've focused on that three times in three different posts within 24 hours.
 
Last edited:
LOL. No misrepresentation in the slightest. Perhaps a difference in interpretation, however, it's not me going to laborious and pedantic levels to try and make some kind of point out of a most trivial "difference of opinion". When people do that it speaks volumes.
I'm not the only one doing it, not even the one who initiated the silly criticism on the choice of example. :rolleyes:


ROFL. Get a grip man. By all means list these "corrections".
Do you really want me to list all the times where you've interpreted that I said there was no period of over-g (or acted as if you interpreted that), when I've said no such thing? :rolleyes:

I don't feel like listing all of my repeated corrections to your misunderstanding once again just to prove a point. One will suffice:
How many times do you fall in the same mistake?

Unsupported ≠ false



That's not the most simplistic, at least not in the sense that it treats the raw data directly without further processing that can introduce error. I've done a quadratic fit over the raw data in that interval instead, and got this out of QtiPlot:

Code:
Polynomial Fit of dataset: RawPositionData_2, using function: a0+a1*x+a2*x^2
Weighting Method: No weighting
From x = 1.251251251251000e+01 to x = 1.449783116450000e+01
a0 = -2.638454150958290e+03 +/- 1.791304696042726e+01
a1 = 4.283697269612591e+02 +/- 2.656166316734676e+00
a2 = -1.738928555529672e+01 +/- 9.832085836278116e-02
--------------------------------------------------------------------------------------
Chi^2/doF = 1.034921189393713e-01
R^2 = 0.999831069675003
Adjusted R^2 = 0.999826700787287
RMSE (Root Mean Squared Error) = 0.321701910064848
RSS (Residual Sum of Squares) = 12.1085779159065
---------------------------------------------------------------------------------------
The acceleration is twice a2, 34.8. Closer to a proof but still not there.


I've proved such to my satisfaction.
You've proved such to your satisfaction AND stated it publicly as a fact, not as your opinion.


My statement...
"I'm afraid perspective correction "depends upon" much more than [variation of distance to the camera]"
...is quite true, standing, sitting or doing cart-wheels.
Let's define concepts before we get lost in semantics.

Perspective correction: The process of undoing perspective distortion.
Perspective distortion: The distortion of a perspective projection with respect to an orthographic projection.
Perspective projection: The projection of a 3D image into a 2D plane, derived from the perspective projection formulas I posted in post #2819.
Orthographic projection: The projection of a 3D image into a 2D plane, derived from the orthographic projection formulas I posted in post #2819.
Lens correction: The process of undoing lens distortion.
Lens distortion: Distortion caused by optical side effects derived from the geometry of the lenses, such as barrel/pincushion/complex distortion and chromatic aberration.

Do you have other definitions? State yours. With my definitions:

- In a camera obscura, only perspective correction is needed, and not lens correction, because it doesn't have any lenses. The projection performed by a normal camera is the same as that performed by a camera obscura, but the lenses also introduce lens distortion. Yes, hole size in a camera obscura introduces some blurring, but it can be in theory reduced to under grain size.
- Lens correction must be applied before perspective correction, in order to obtain a "pure" perspective projection to correct.
- There is one single variable to consider for perspective correction: depth. Finding depth is a laborious work in which many other variables come into play; once you have it, it's all you need.
- In an orthographic projection, distance between two points can be determined solely by projected position, angle with the camera plane and pixel metric information. The latter can be derived from reference points at a known angle with the camera plane and a known distance between them.
- In a perspective projection, distance between two points can be determined solely by depth of each point, projected position, angle with the camera plane and pixel metric information. The latter can be derived from reference points at a known depth, angle, and distance between them.
- In a perspective projection, if you have a set of points all at the same depth, and you have metric information for two pairs of points that aren't aligned in the projection, you can derive metrics for any two points in the set, because they all are affected by perspective distortion in the exact same amount. That's the effect you exploited in the case of Dan Rather, ignoring angle with the camera plane and lens distortion. Which I'm not objecting to.
- Technically there's another factor to consider besides lens and perspective distortion, namely atmospheric distortion (refraction due to air density variation, e.g. hot air causing turbulent images), but we're all dismissing that effect as insignificant in this case, aren't we? It's already kind of minimized in the traces thanks to static point extraction. There isn't much that can be done to correct it anyway.


Lens distortion affects perspective correction, which is what you are proposing to do.
By the definitions above, lens distortion doesn't affect perspective correction. Maybe you're using a different definition of perspective correction. State yours.


If I didn't claim inch precision, you'd complain ad infinatum about placement accuracy.
Not if you did the corresponding error analysis.


Er, riiiight. Hmmm. Haven't read ahead...
You miss context very often for that reason.


Thanks.


Anyway I planned to add some checks.
About what ?
Aspect ratio.
 
Code:
Polynomial Fit of dataset: RawPositionData_2, using function: a0+a1*x+a2*x^2
Weighting Method: No weighting
From x = 1.251251251251000e+01 to x = 1.449783116450000e+01
a0 = -2.638454150958290e+03 +/- 1.791304696042726e+01
a1 = 4.283697269612591e+02 +/- 2.656166316734676e+00
a2 = -1.738928555529672e+01 +/- 9.832085836278116e-02 ...

The acceleration is twice a2, 34.8. Closer to a proof but still not there.

The inference depends on the data. However, given the tightness of the fit, it seems that random (iid) measurement error couldn't account for the apparent >g acceleration. The error would have to be substantially correlated with time -- which certainly is logically possible. Do you agree, more or less?
 
I don't feel like listing all of my repeated corrections...
Yawn. Only "corrections" in your own head I'm afraid ;)

That's not the most simplistic, at least not in the sense that it treats the raw data directly without further processing that can introduce error.
Simply replication of NIST's methods ;)

The acceleration is ... 34.8
Interesting to compare the 35.0 from symmetric difference (13) to the 34.8 from a second order polynomial.

Might be worth thinking about how well each polynomial fit produced during savitzky-golay derivative generation would behave ;)

Closer to a proof but still not there.
Then carry on with your analysis until you are satisfied.

You've proved such to your satisfaction
Correct.

AND stated it publicly as a fact, not as your opinion.
Where ?

Let's define concepts before we get lost in semantics.
No, let's start by not forgetting that the point of my response is to correct your clearly false assertion.

You're supposed to acknowledge your error :rolleyes:;)

Perspective correction...
Yawn. Have you just discovered "google" ?

The process of undoing perspective distortion.
You're looking to perform perspective correction on real-world footage of WTC7, for "whatever" reason.

That real-world footage is affected by all manner of "stuff", including various kinds of distortion, perspective effects, optical effects, ....

Lens distortion: Distortion caused by optical side effects derived from the geometry of the lenses, such as barrel/pincushion/complex distortion and chromatic aberration.
Which, bearing in mind video cameras have lenses... ;)

Do you have other definitions?
Undoubtedly, however they are far from the point, and leading away from your repeated buffoonery...

State yours.
Who are you talking to ? [points, laughs]

pgimeno said:
femr2 said:
pgimeno said:
I've always said that perspective correction depends on the variation of distance to the camera.
I'm afraid perspective correction "depends upon" much more than that
Which as it stands, is a false statement.

I am quite correct, and your banal and anal googling changes nothing.

In a camera obscura
Irrelevant.

the lenses also introduce lens distortion
Correct.

Lens correction must be applied before perspective correction
How do you separate the two when you have no information about the lens ? :rolleyes:

There is one single variable to consider for perspective correction: depth.
ROFL.

Finding depth is a laborious work in which many other variables come into play; once you have it, it's all you need.
LOL. What happened to your one variable ? :rolleyes:

In an orthographic projection
Irrelevant.

In a perspective projection, distance between two points can be determined solely by depth of each point, projected position, angle with the camera plane and pixel metric information. The latter can be derived from reference points at a known depth, angle, and distance between them.
LOL. Good luck determining any of those values with any accuracy. Jeebus.

Technically there's another factor to consider besides lens and perspective distortion, namely atmospheric distortion
And all sorts of other sources an'all.

By the definitions above, lens distortion doesn't affect perspective correction. Maybe you're using a different definition of perspective correction. State yours.
State yours ? Again, who do you think you're talking to ? LOL.

It's good to see that you're pulling your foot back out or your mouth "a teeny bit".

Mine ?

You're going nowhere with an attempt to perform accurate perspective correction without dealing with lens distortion.

Lens distortion affects perspective correction, which is what you are proposing to do.

Do you see how this works ?

You'll get there...if you stop assuming you know what I'm talking about, when you don't...and stop assuming I don't know what I'm talking about, when I do. Seemples.

pgimeno said:
femr2 said:
Haven't read ahead...
You miss context very often for that reason.
You are suggesting missing context by not reading ahead ?

Priceless.

You're welcome, however, making incorrect assertions, requoting them with corrections, without even BOTHERING to look up the PAR of 4:3 standard NTSC is pretty pathetic. I shouldn't have to give you these details, and you shouldn't be making such primitive mistakes. The problem is that you are clearly very inexperienced in the video arena, both in terms of video data and treatment.

So pull your horns in.
 
The inference depends on the data. However, given the tightness of the fit, it seems that random (iid) measurement error couldn't account for the apparent >g acceleration. The error would have to be substantially correlated with time -- which certainly is logically possible. Do you agree, more or less?
femr2 has said that error is bigger in the pre-release stage. Some correlation with time is possible. Video compression algorithms can do that. Probably not significant enough in this case.

Here's the plot of the fit for reference:

http://www.formauri.es/personal/pgimeno/xfiles/11-s/DanRatherQuadraticFit.png

I still have to examine the conversion from pixels to feet in more detail, but that can take long.
 
How do you separate the two when you have no information about the lens ? :rolleyes:
How do you correct perspective distortion with lens correction formulas? :rolleyes:


You're going nowhere with an attempt to perform accurate perspective correction without dealing with lens distortion.
Who said accurate? You're Mr. 571.1364±8.2345, not me.


Lens distortion affects perspective correction, which is what you are proposing to do.
The problem here is obviously semantics. I asked you to define your terms for that reason, even if you've refused.

"Lens distortion affects perspective correction".

You parse that as: "Lens distortion affects the image that you need to apply perspective correction to".

I parse that as "Lens distortion is a variable that intervenes in the process of perspective correction".

The former is true. The latter is false. Both of us were right.


You'll get there...if you stop assuming you know what I'm talking about, when you don't...and stop assuming I don't know what I'm talking about, when I do. Seemples.
And what about you stop assuming I don't know what I'm talking about, when I do? The only thing I googled is pixel aspect ratios, to know whether that was common. I haven't yet checked the resolution of the video.


You are suggesting missing context by not reading ahead ?
Yes. Sometimes you even split sentences in the middle and your reply doesn't make sense given the context of the whole sentence.


You're welcome, however, making incorrect assertions, requoting them with corrections, without even BOTHERING to look up the PAR of 4:3 standard NTSC is pretty pathetic.
Straw man. I have not made any incorrect assertion regarding aspect ratio. Inventing mistakes is pathetic.
 
Last edited:
How do you correct perspective distortion with lens correction formulas? :rolleyes:
How do you apply a lens correction formula without information about the lens ? :rolleyes:

Who said accurate? You're Mr. 571.1364±8.2345, not me.
LOL. Your purpose is to improve the cam#3 data. That data is already sub-pixel accurate in nature (ring any bells ?)

Without exceedingly high accuracy you're simply going to add noise to your target data.

The problem here is obviously semantics.
I disagree.

Your problem is that I am speaking from the perspective (pardon the pun) of "what you are intending to do to real-world WTC7 footage, and the obstacles which such presents", and you are getting yourself all tied up in googling "camera obscura" in a vain attempt to "prove femr2 wrong version the umpteenth".

It's rather obvious that you are gathering information about your proposed task in hand as you go along, and getting yourself lost in details as you simply don't understand very simple assertions from me.

Consider...8th February 2013...
Incorrect.

As I said...

The kind of motion already extracted from videos is well sub-pixel in nature, and contains some noise.

The result of determining full three dimensional position (in other words correcting for perspective) for the trace data in question would be very minor, and an almost linear deskew. As the fidelity of the data is already sub-pixel, and the Dan Rather viewpoint is almost orthogonal, the resultant change to derived acceleration trend plots would also be minor. Perhaps a slight change in magnitude, and that's about it.

If you don't understand, take offers to explain to you in more detail.

Calling my statement "Meaningless technobabble" does you no favours.

Tagging onto tfk's nonsense is also a bad idea.

As I aslo told you a couple of weeks ago...
Hey, if you want to look at perspective correction for the cam#3 viewpoint, great. I didn't go there as it is a whole can of worms, and imho is likely to add noise to existing data rather than reduce it. Good luck.

You can't determine depth during descent with one camera view. You'd be better off determining camera-object (wtc7) orientation during static motion period and performing a simple geometric correction.

Good luck with that. Remember to include all the other inherent noise sources on top.

You really should have done your "perspective" investigoogle in private.

"Lens distortion affects perspective correction".

You parse that as: "Lens distortion affects the image that you need to apply perspective correction to".

I parse that as "Lens distortion is a variable that intervenes in the process of perspective correction".

The former is true. The latter is false. Both of us were right.
Say wha' :jaw-dropp In what way can you specifically identify your own error and then declare you're right ?

Never mind eh.

And what about you stop assuming I don't know what I'm talking about
I don't assume it. I respond to it when you prove it to be the case.

Straw man. I have not made any incorrect assertion regarding aspect ratio.
a) Picture Aspect Ratio is not 1:1.
b) Pixel Aspect Ratio is not 1:1.

If you had any experience of video formats you would know that PAR of 1:1 is particularly rare. Sure, you clearly indicated doubt, but the value is still incorrect, and looking it up if you don't already know it takes about 30s.
 
femr2 has said that error is bigger in the pre-release stage.
No ! There is an increase in noise around the release point. I already told you to have a look at the actual Dan Rather data to see it for yourself.

I still have to examine the conversion from pixels to feet in more detail, but that can take long.
Do you mean will take a long time ?

-or-

Do you mean won't take a long time ?


One gets the impression you don't want to give Mark a straight answer.

What makes me chuckle is that I used the same derivative generation methods as NIST, got results over-g and you still question such.

Does that mean that you also question the NIST results to the same extent ? ;)

Again...(as you chose to ignore it in your prior response)...

Might be worth thinking about how well each polynomial fit produced during savitzky-golay derivative generation would behave.
 
LOL. Your purpose is to improve the cam#3 data. That data is already sub-pixel accurate in nature (ring any bells ?)
Wrong. My purpose is to make it usable. There's little point in having it there if it can't be used.


Without exceedingly high accuracy you're simply going to add noise to your target data.
Same with exceedingly high accuracy.


Your problem is that I am speaking from the perspective (pardon the pun) of "what you are intending to do to real-world WTC7 footage, and the obstacles which such presents", and you are getting yourself all tied up in googling "camera obscura" in a vain attempt to "prove femr2 wrong version the umpteenth".
My father was a photographer. I learnt a lot from him. Again, no need to google concepts I'm very familiar with. Also, I'm quite familiar with 3D graphics.


Say wha' :jaw-dropp In what way can you specifically identify your own error and then declare you're right ?
It's not my own error. My interpretation of your words was valid. Within that interpretation I was right. Within your interpretation you were right. I've done the effort to identify the issue and concede. You keep throwing **** at me without conceding anything.


Straw man. I have not made any incorrect assertion regarding aspect ratio.

a) Picture Aspect Ratio is not 1:1.
b) Pixel Aspect Ratio is not 1:1.
Which I didn't assert it was, thus putting in black and white that you were strawmanning... again. And again, you don't concede; you never do. :rolleyes: My exact words:
ETA: Also, it assumes 1:1 aspect ratio, which may or may not be correct.
- A reference point at a known height, in order to match both videos. Possibly two, depending on whether the aspect ratio is not 1:1
(Clarification: 1:1 alludes to the pixel aspect ratio, not to the image aspect ratio.)
See any incorrect assertion there?
 
@femr2: Isn't it time to cut your losses with this rolling "Gish Gallop"?
...Your problem is that I am speaking from the perspective (pardon the pun) of "what you are intending to do to real-world WTC7 footage, and the obstacles which such presents",...
Which is the position I have stated several times to the consternation of those who don't want to address the topic. Viz "purpose" and "scale of the obstacles" AKA errors.

...One gets the impression you don't want to give Mark a straight answer...
apparently - here IMO is a reason why.

The two ongoing discussions in this thread are:
1) the main topic question which can be simply stated as "Do femr's video analyses produce data which is accurate enough to be useful?"
The claims that femr's data is not accurate enough have degenerated into a pair of strawman arguments buried in a fog of personal attacks and a couple of Gish Gallops of untruths.

However if that discussion is to progress legitimately it demands quantification of the errors inherent in the analysis methods. And Mark's question starts to head in the direction of "quantification" which doesn't suit the tactics of "prove femr2 wrong version the umpteenth". (Neat phrase that one. ;))

Meanwhile the second discussion is:
2) pgimeno's tactic of limiting his acceptance of femr's analytical data to the requirement that femr must explain it to pgimeno's satisfaction. Plus a rolling "Gish Gallop" to make sure we all forget what the real issues are.

Well whoopee. Two different issues:
1) The accuracy is inherent in the methods and is available for objective measurement; and
2) Accuracy does not depend on femr's skill at explaining. Whether femr is the best explainer or the worst has no effect on the accuracy of the data.
 
...and yes, even thoug I've clearly marked them as sample, draft fits, and not perfect yet...at that time...the sample femr2 fit is still much better than NIST's.


Think ? I know it has little effect. Comes with having the models available and the facilities to move things around at will, including lens parameters. A distinct advantage.

As I said, I suggest you continue your, no doubt never-ending, "critique" in a more appropriate thread.

While I had a few minutes spare today I thought I'd have a quick look at Femr's aircraft impact angle. Using the camera and building position information Femr has provided we can draw lines back to the camera position and see the relationship between the sizes of various objects in the frame. By adding a line representing the fuselage length of the boeing 767 you can easily compare the visual length at the differnt impact angles, 3.5° from perpendicular to the face of the building for Femr and 12° for the NIST baseline. Since the downward angle of the aircraft only changes the length of the fuselage in the horizontal plane by about 6" I ignored that parameter for this quick check.

So here's the NIST baseline angle,
WTC2impactNist_zps9e46a14c.jpg


And Femr2's,

WTCimpactfemr_zpscefdd7c9.jpg


A quick and dirty check but I know which one looks closer to my eye.
 
Good work. femr2's estimation of Hezarkhani's camera position is definitely wrong. Carmen Taylor's photograph has about the same width for the east wall as Hezarkhani's video, both notably different to ferm2's, proving that it's not a lens effect as femr2 said, but a perspective effect due to a different position of the camera:

UA175-CarmenTaylorVsHezarkhani.gif
 
Last edited:
@femr2: Isn't it time to cut your losses with this rolling "Gish Gallop"? [...]

The two ongoing discussions in this thread are:
1) the main topic question which can be simply stated as "Do femr's video analyses produce data which is accurate enough to be useful?"
The claims that femr's data is not accurate enough have degenerated into a pair of strawman arguments buried in a fog of personal attacks and a couple of Gish Gallops of untruths.

However if that discussion is to progress legitimately it demands quantification of the errors inherent in the analysis methods. And Mark's question starts to head in the direction of "quantification" which doesn't suit the tactics of "prove femr2 wrong version the umpteenth". (Neat phrase that one. ;))

Meanwhile the second discussion is:
2) pgimeno's tactic of limiting his acceptance of femr's analytical data to the requirement that femr must explain it to pgimeno's satisfaction. Plus a rolling "Gish Gallop" to make sure we all forget what the real issues are....

I don't think that pgimeno is attempting to execute a Gish Gallop. I think a lot of the discussion has been chippy and off-point in a way that even professional discussions too often become, and that internet discussions may be especially prone to. Every imprecision or ambiguity in language can become an ongoing point of contention. Asking detailed questions about other researchers' methods isn't inherently a "tactic," but it can be -- and even with the best of intentions all around, the discussion can easily veer off point. This one is pretty far gone. So, yes, it would be great to focus on quantifiable issues.

My impression -- it can only be that, because I really don't have time to replicate analyses, nor do I have specific competence in this area -- is that in the specific question of average acceleration of the reference point over approximately a 2-second period, the results do not fundamentally depend on analytical method (how S-G is applied) or random "noise" in measurement. It could be sensitive to systematic measurement error.

Perhaps the best course is for pgimeno to see if he can replicate the basic result without using femr2's data. The difference between average acceleration of about 32 f/s2 and about 34.8 f/s2, over 2 seconds, is about 5-6 feet of displacement, yes? It would be easy to get wrong, but the inference doesn't necessarily depend on sub-pixel accuracy or fitting techniques.

I'm not sure how much the answer to this question matters, but as long as we're supposedly discussing empirical questions, it sure would be nice to do that.
 
I don't think that pgimeno is attempting to execute a Gish Gallop...
I don't think it is intentional but I prefer to stay away from considerations of personal motivation for reasons which apply generally to all threads and are specifically obvious in this thread. Viz where does personal antagonism take over from reasoned rational discussion.
...I think a lot of the discussion has been chippy and off-point in a way that even professional discussions too often become, and that internet discussions may be especially prone to. Every imprecision or ambiguity in language can become an ongoing point of contention....
Undoubtedly true but my preference is to clarify the way through the fog rather accept that is often happens and condone the fogginess.
Asking detailed questions about other researchers' methods isn't inherently a "tactic,"
Slightly disagree there...."isn't inherently an intended tactic" Lack of intent does not preclude tactical effect as you rightly observe:
...but it can be -- and even with the best of intentions all around,...
I've been monitoring this thread to see if it returns to reasoned discussion of what I see as the primary issues viz "Do femr's video analyses produce data which is accurate enough to be useful?" I am satisfied that femr has made a prima facie case and that no one has so far addressed or rebutted the key issue of "...accurate enough to be useful". My identification of that concern has led to several outbursts of personal attack directed at me - not just the ones directed at femr. Whilst it is easy to make the "it isn't intended - it often happens" assessment that you make - and I comprehend the perspective - such is not the innocent history of this thread.
the discussion can easily veer off point. This one is pretty far gone. So, yes, it would be great to focus on quantifiable issues...
There were two objectives being discussed over recent weeks as I identified in my post. We now have a third one which is a distraction from the real issues of differing perspective.

My impression -- it can only be that, because I really don't have time to replicate analyses, nor do I have specific competence in this area -- is that in the specific question of average acceleration of the reference point over approximately a 2-second period, the results do not fundamentally depend on analytical method (how S-G is applied) or random "noise" in measurement. It could be sensitive to systematic measurement error.
The first step should be to decide what the aim of the discussion is. It seems to be wandering all over the place with the only constant theme being "prove femr wrong". pgimeno some time back clarified his own objective as (words to the effect of) "Get femr to explain his methods to my satisfaction". That aim specifically precludes pgimeno addressing the actual measurements - which is why I have commented on it a couple of times - and withdrawn from discussion. That aim is of no interest to me.

I am interested in the main theme of "Do femr's video analyses produce data which is accurate enough to be useful?" and that theme unavoidably has two "legs" - viz 1, "are there errors of noise and procedural artefacts?" AND 2 "are these errors big enough to matter for whatever purpose?" The issue of existence of errors is not in question - femr has spent many hours over many months explaining how his methods seek to minimise errors to the best of his abilty. However some parties opposing femr have made a strawman argument out of the issue of errors - and "conveniently" - AKA deliberate choice of tactics - ignored the real issue of quantification of errors related to a range of specific purposes. A distinction I have elaborated on with IMO precision and in some detail. :o No one has picked up the gauntlet - my comments either ignored or countered with false personal attacks.

So:
...Perhaps the best course is for pgimeno to see if he can replicate the basic result without using femr2's data....
Whilst I comprehend your suggestion it involves:
a) A fundamental change of objective from the one pgimeno stated some days back. It is not clear at this stage whether he has changed his aim.
b) Also a shift to foggy ambiguous goals whilst I prefer clarity of both aims and reasoning. If the preference is to continue in fog I don't object - I simply withdraw from discussion until (and if) discussion reaches a point where I judge it is worthwhile to comment. :rolleyes:

...I'm not sure how much the answer to this question matters,...
You are not alone - it is the fundamental problem with this thread and many more. "What the **** are we talking about?" - illustrated I think by "When up to your arse in alligators it is easy to forget that the objective was 'drain the swamp'." Also references to "forests and trees" come to mind. :rolleyes:

My interest remains in draining the swamp. I'm not the least bit interested in the missing toe on Alligator 97's left front foot OR the broken teeth of Alligator 59. (Until someone shows relevance -- but I'll resist the temptation to extend the metaphor... :o)
... but as long as we're supposedly discussing empirical questions, it sure would be nice to do that.
Yes. Be clear where we are trying to head and clear as to the route we are attempting to traverse.

Although it is legitimately within the overall topic the last few posts of "moving the goal posts" don't help to clear up the actual areas of fog and apparent disagreement. Rather than converge on focussed discussion the new set of goalposts is merely a divergence into other matters at this stage.

(BTW There is a fundamental difference in the contextual setting of the arguments for femr's measurements of WTC7 collapse and those for aircraft impact direction but I will heed my own advice and not derail into explanations at this stage. ;))
 
Last edited:
How do you apply a lens correction formula without information about the lens ? :rolleyes:
I have done it. Method and results will be published soon.

I'm working on the plane issue as a warm-up for the more complex WTC7 analysis that is still not done, but I've already performed a lens correction analysis for Cam#3.




I don't think that pgimeno is attempting to execute a Gish Gallop.
Indeed not, thanks. And I think your diagnosis of the issues is pretty accurate.


Perhaps the best course is for pgimeno to see if he can replicate the basic result without using femr2's data.
I might end up doing that, but currently my focus is on entirely different matters, namely perspective issues for both the plane and WTC7. My remaining point of contention is pixels-to-feet conversion, something I still need to look at.
 
I might end up doing that, but currently my focus is on entirely different matters, namely perspective issues for both the plane and WTC7. My remaining point of contention is pixels-to-feet conversion, something I still need to look at.

I'm definitely not invested in any particular vision of the sequence in which you should work. I will comment that it isn't obvious to me whether and how this particular focus relates to the discussion of acceleration, or just where you think that discussion stands.

Here's another half-baked thought, for what it's worth: A cynic might construe that you are changing the subject because you think you can more easily criticize femr2 on some other subject. If you were to summarize some points of agreement between you and femr2 on the acceleration topic -- as well as unsettled questions on that topic -- that might contribute to recentering the discussion on empirical inquiry.
 
While I appreciate the thoughts above, they are in and of themselves evidence for why these topics should be in the Science and Math sub-forum.

I'm basically a n00b (and probably will be for life). Is there a clear statement of policy on this issue?

To me, it seems desirable that a (sub-)forum on 9/11 CT should also include some rational discussion*, much as a forum on creationism might. I see no better way to distinguish reasonable skepticism from selective gullibility than to let them coexist. But I see that there is more than one side to the question, and at any rate, it should be a policy decision.

*ETA: I'm too distracted to settle on the right words here, but roughly what I mean is empirical research that isn't focused on rebutting (or supporting) any CT.
 
Last edited:
I'm definitely not invested in any particular vision of the sequence in which you should work. I will comment that it isn't obvious to me whether and how this particular focus relates to the discussion of acceleration, or just where you think that discussion stands.

Here's another half-baked thought, for what it's worth: A cynic might construe that you are changing the subject because you think you can more easily criticize femr2 on some other subject. If you were to summarize some points of agreement between you and femr2 on the acceleration topic -- as well as unsettled questions on that topic -- that might contribute to recentering the discussion on empirical inquiry.
Good idea. I think my previous fit shows almost conclusively that the issue is not the noise; the only thing I still need to do to be sure is a least squares fit that fixes the second degree term of the polynomial to -16.1, and plot it to see how plausible it is compared to the -17.4 one. I suspect it won't cut it and that will definitely prove that the problem is not the noise. I already implied earlier that something along the lines of a fit that doesn't depend on error propagation might be successful, namely:
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.
(There were still quantification issues on that claim. "About" isn't very explicit, and I was not for checking the accuracy at the time. The linear fit was closer to a proof; it gave me a better idea and since now I have some more free time, I went ahead and tested it.)

So, there are many hurdles cleared, but there are some pending. Thing is, I don't think I should be the one doing this, because I haven't made the claim. My view on that is similar to how proving works in mathematics: if I find a mistake in a theorem, a step that doesn't follow from the previous step, the theorem is not proved, and it doesn't correspond to me to correct the proof. Ozeco seems to think that "the error is small and the theorem is roughly proved". There is no such thing as a "roughly proved" theorem. It is proved or it isn't, yet he tries to throw the burden of proof on me to provide a proof showing that the magnitude of some error matters. femr2, on the other hand, has repeatedly asked me to show my proof that the theorem is false, when I haven't claimed it's false (if I did, I would indeed have the burden to present a proof). Now, is there a series of steps that can fix the broken link in the deduction chain and complete the proof? That's what we're working on.

There are other points of contention. This exchange sums it up:

Exactly what is it that you are trying to prove ?

Exactly what purpose do you have for the data ?

What exactly are you trying to achieve ?
1) I'm now more convinced about early motion. The trace data was not enough for that; movement seen in the video was clearer.

2) You have claimed that the acceleration went over g. I don't think you have proved that.

3) I am defending a claim I made and you have attacked, namely that the issue with perspective is distance from the camera (depth).

4) I think I am in a position to undo perspective effects from Cam #3. That would enable usage of that data which currently can't be taken enough advantage of.
(1) is out of the way now. At this point, and without proof to the contrary, I regard it as a solved issue. If others have problems with it, they can question it and I will be watching.

(2) is the point that we're dealing with, and my position is summarized above. There are two things remaining to do: a comparison of fits with the one expected by gravity to definitely exclude noise as a source of bias, and an evaluation of the precision of the metrics. The latter will take time as I gather information on metrics from diverse sources. Unlike what femr2 seems to think, I don't regard NIST data as perfect and I prefer to check with other sources.

(3) wasn't a point I brought up. If what I'm doing is qualified as gish-galloping, I am by no means the only one doing it. I hope (3) is clear by now.

(4) is a point of interest for me and discussion on the subject can help, though femr2 is obviously in a quite defensive posture and unwilling to help.

There is a fifth point that is kind of coming up, namely the analysis performed by femr2 on the UA175 orientation and brought up in another thread. I have issues with it and he invited people to discuss it in this thread; however I'm afraid that when I bring it up in full, it will be also qualified as gish-gallop. *shrugs*
 

ISF - Join now!

Every member here is approved by hand. No bots, no spam, just people who care about evidence and honest debate.

Membership is free!

Create your free account

Back
Top Bottom