Merged Discussion of femr's video data analysis

I don't know what you mean.
I'm sure you do really ;)

If you are referring to my three editions
I'm not...and what a strange aspect of my post to focus on... :boggled:

No, I have NOT made that assertion [Your claim of over-g is not supported by your analysis] many times.
So, you have actually been saying that my assertion of over-g IS supported by my analysis ? :rolleyes:

I have claimed that you haven't provided an error analysis that allows to judge whether the error is too big or not, in order to support your own claim of over g.
So, you have actually been saying that my assertion of over-g is NOT supported by my analysis ? :rolleyes:

Once again, I don't say your claim is erroneous. I am saying it's unsupported.
So, when I say "An assertion you've made many times for varying and shifting reasons", you respond with "No, I have NOT made that assertion many times." :rolleyes:

S'funny :)

Your burden of proof. You've failed.
ROFL. 32.196 > 32.159. Done.

There's a difference with your claim, though: he qualifies that as likely, not as a fact.
Where ?

Which means that you are in agreement with my assessment that cam #3 data is only good for looking at the shape.
No, I'm not.

I don't see the problem nor do I know what hole you mean.
Clearly.

That's all the utility I see in your acceleration graph without an adequate quantification of error.
Did you miss where I provided you with an error band ?

Did you notice the green line on the graph you linked ?

I stand by my words
Not a good idea. It's clear you don't understand what I'm telling you. I'll explain to you again using very short words and point at pictures when I can be bothered.

Silly pickiness.
No, you just don't realise why I'm making the point.

Why? To amplify the error in compensating for camera shake (in the form of displacement)?
To ensure the magnitude of traced camera motion is as near to that which affects WTC7.

Now you say that "a conservative estimation based upon wide window symmetric difference (rather than wide window savitzky-golay) would tot up to something around the +/- 3 ft/s2".
I said such a long, long time ago.

Can you show the symmetric difference acceleration graph you're talking about?
You're missing the point.
 
I'm sure you do really ;)
I wouldn't ask if I did.


I'm not...and what a strange aspect of my post to focus on... :boggled:
Should prove that I didn't know what you mean.


So, you have actually been saying that my assertion of over-g IS supported by my analysis ? :rolleyes:
*sigh*

Let's walk you through context again.

You said:

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 ?
I've NOT made that specific claim with the highlighted assertion. The fact that you said I did many times opened the door to misinterpretations of my position.

That part of the claim was not serious. It's not part of what I have been claiming. I don't know if the error is too big or not. You haven't shown. It's what prevents me from accepting your claim of over-g.

You misrepresent my words once again in your quotation:
No, I have NOT made that assertion [Your claim of over-g is not supported by your analysis] many times.
A claim which INCLUDES that the error is too big, and not the one you put in [ ] alone, is the assertion I have only made once, and not seriously.


So, you have actually been saying that my assertion of over-g is NOT supported by my analysis ? :rolleyes:
Yes.


So, when I say "An assertion you've made many times for varying and shifting reasons", you respond with "No, I have NOT made that assertion many times." :rolleyes:

S'funny :)
See above. I have NOT made many times an assertion that includes that the error is too big.


ROFL. 32.196 > 32.159. Done.
Do you base your assertion of over g on NIST's data? :rolleyes:


There's a difference with your claim, though: he qualifies that as likely, not as a fact.
Where ?
On the basis of my own analysis, I think a half-second of over-g acceleration was more likely than "about one second."


Did you miss where I provided you with an error band ?
Embedded in a graph? Yes, I've missed it.

If you mean this: "a conservative estimation based upon wide window symmetric difference (rather than wide window savitzky-golay) would tot up to something around the +/- 3 ft/s2", no, I didn't miss it.


Did you notice the green line on the graph you linked ?
This graph? http://femr2.ucoz.com/_ph/7/513801604.png Yes, I know it. Your point?


Not a good idea. It's clear you don't understand what I'm telling you. I'll explain to you again using very short words and point at pictures when I can be bothered.
I see you skipped my question about orthographic projection. Interesting.

Let me remind you what you said about the cam #3 view:
the skewing caused by perspective effects becomes particularly significant
You were complaining about perspective effects. Would an orthographic projection make that problem disappear?
 
Let's walk you through context again.
Let's not. I'd draw your attention to the part of my comment... "for varying and shifting reasons". Your volumous and pedantic "context" crap really isn't the point. The point is...

"So, you have actually been saying that my assertion of over-g is NOT supported by my analysis ?" :rolleyes:

...which you have said for varying and shifting reasons.

I have NOT made many times an assertion that includes that the error is too big.
No-one said you did, you blithering... :rolleyes:

Do you base your assertion of over g on NIST's data? :rolleyes:
No...

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.
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 ? :rolleyes:
Your burden of proof. You've failed.
ROFL. 32.196 > 32.159. Done.

AGAIN...the NIST linear regression provides their stated 32.196 ft/s^2 value for acceleration, which they state to 3dp.

That is over-g.

Done.

Embedded in a graph? Yes, I've missed it.
ROFL. Lame.

If you mean this: "a conservative estimation based upon wide window symmetric difference (rather than wide window savitzky-golay) would tot up to something around the +/- 3 ft/s2", no, I didn't miss it.
Good. There ya go. What's left for you to complain about ?

This graph? http://femr2.ucoz.com/_ph/7/513801604.png Yes, I know it. Your point?
Jeez...

513801604.png

You said - NIST basically say that the acceleration roughly corresponds with the blue line in this graph for a certain segment.

I pointed you towards the green line, which is the NIST formula for velocity differentiated to acceleration.

The green line is somewhat a little differnet to the blue line.

Now what can you see out of the round window :rolleyes:

I see you skipped my question about orthographic projection. Interesting.
Boring. Have you managed to work out why tracing two static regions at differing distance from the camera is useful yet ?

You are in no position to make a point about "skipping" post elements. You conveniently ignore much of mine, especially those portions that are particularly critical.

Let me remind you what you said about the cam #3 view
No need. I wrote it.

Would an orthographic projection make that problem disappear?
Irrelevant.

I'll reiterate all the elements you've "skipped" in recent posts a little later, when I can be bothered.
 
Let's not. I'd draw your attention to the part of my comment... "for varying and shifting reasons". Your volumous and pedantic "context" crap really isn't the point. The point is...
... (watches you quietly taking the goalposts as the ball gets closer)...
"So, you have actually been saying that my assertion of over-g is NOT supported by my analysis ?" :rolleyes:
"Ta-da! You didn't score! Try again."

So the point is no longer...
So, you have actually been saying that my assertion of over-g IS supported by my analysis ? :rolleyes:
? OK, in that case I hope that the point is finally clear, and that you stop putting in my mouth what I have not been saying, once and for all.


No...


AGAIN...the NIST linear regression provides their stated 32.196 ft/s^2 value for acceleration, which they state to 3dp.

That is over-g.

Done.
Fair enough. I misunderstood your "It is" as "The acceleration is over g", not as "NIST's acceleration is over g".


Good. There ya go. What's left for you to complain about ?
What graph of those you have posted does that apply to? In your graph below, the difference between Poly(10)/Poly(50) and SG at the 12.5s mark is about 10 ft/s². I don't see a graph obtained by symmetric difference.


Jeez...

[qimg]http://femr2.ucoz.com/_ph/7/513801604.png[/qimg]
You said - NIST basically say that the acceleration roughly corresponds with the blue line in this graph for a certain segment.

I pointed you towards the green line, which is the NIST formula for velocity differentiated to acceleration.

The green line is somewhat a little differnet to the blue line.

Now what can you see out of the round window :rolleyes:
Yes, I agree that the shape is somewhat different to NIST's in that case too. That's about the utility of your graphs, to compare shapes.

I was referring to this one:

5930538.jpg


I suspect you knew that and wanted to prove pgimeno wrong version the umpteenth. After all, the graph is labeled "FEMR2 vs. NIST Linear Fit"


Boring. Have you managed to work out why tracing two static regions at differing distance from the camera is useful yet ?
It might have to do with discarding perspective effects, although without knowing the relative distance from the camera to each traced spot and WTC7, that's only moderately convincing. Also, the region on the left is wide enough to covers an ample range of distances.

Any other reason?


Would an orthographic projection make that problem disappear?
Irrelevant.
Not in the least.

With depth information for every point (pixel) in the image, it would be possible to transform the perspective projection into an orthographic (non-perspective) projection, which doesn't have the problem of perspective.

You know that, and know the answer. The problem would disappear, as the perspective is no longer an issue. Therefore your sentence:
the skewing caused by perspective effects becomes particularly significant
would become moot, proving that the issue with perspective is depth.

But since you want to prove pgimeno wrong version the umpteenth, you prefer to say "Irrelevant" rather than concede.
 
... (watches you quietly taking the goalposts as the ball gets closer)...
ROFL. Your inept, repeated and verbose misinterpretation really is not my problem.

"Ta-da! You didn't score! Try again."
You really need to work on your "quips". Yawn.

Fair enough. I misunderstood your "It is" as "The acceleration is over g", not as "NIST's acceleration is over g".
You misunderstand many things, including the base point, which is about your double-standards when it comes to "what NIST says" -vs- "what femr2 says" :rolleyes:

What graph of those you have posted does that apply to?
Stupid question you already know the specific answer to. Why haven't you asked yourself whether using SG based derivative generation process results in wider or narrow error band ? ;)

In your graph below, the difference between Poly(10)/Poly(50) and SG at the 12.5s mark is about 10 ft/s².
So ? Even you are capable of connecting the dots here. The old poly fits are not part of this particular discussion.

I don't see a graph obtained by symmetric difference.
Interesting. Didn't you claim that your SD derivative plot matched my old plot ?

Yes, I agree that the shape is somewhat different to NIST's in that case too.
You said..."NIST basically say that the acceleration roughly corresponds with the blue line in this graph for a certain segment."

Which part of the green NIST curve would you say fits your statement ? :)

That's about the utility of your graphs, to compare shapes.
If you mean trend and magnitude, sure. Who said otherwise ? tfk made some dub-ass assertions, sure, though I don't see you complaining. LOL.

I was referring to this one:
5930538.jpg
Were you now ? Interesting.

One must then wonder why you used this one in your posts then...
NIST basically say that the acceleration roughly corresponds with the blue line in this graph for a certain segment:

http://femr2.ucoz.com/_ph/7/513801604.png

The shape of your graph reveals the behavior is a bit different to an horizontal straight line.
:rolleyes: LOL.

I suspect you knew that and wanted to prove pgimeno wrong version the umpteenth.
I suspect you're simply trying to cover yet another gaffe.

Am I supposed to be a mind-reader or something ? :rolleyes:

You mean one image, but repeatedly refer to a different one. Good job ! :rolleyes:

After all, the graph is labeled "FEMR2 vs. NIST Linear Fit"
It is indeed. Would have made more sense if you'd actually referred to that image at some point, you think ? :rolleyes:

Then, you'd have trouble referring to...
the blue line in this graph
...which is simply "freefall".

Ah don't see me no blue line on tha' graph you jus'a switched to son.

Oh what a tangled web you weave :rolleyes:

It might have to do with discarding perspective effects
So you don't know.

Why don't you simply ask, rather than making a series of guesses.

All you do there is dig the hole deeper.

Any other reason?
Other ? The reason is, as I ALREADY told you (though you didn't understand)...
(hint) amplification of camera motion with differing camera-object distance
...
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]
Understando ?

I imagine you've lost track of the "context" of this element of discussion. Need a reminder ? :) Step #1...we were talking about removing camera motion.

Not in the least.
Of course it is. All footage of WTC7 is real-world, fully affected by all perspective effects...and not a bleedin' orthographic projection.

Yawn.

The rest of your post is unsurprisingly pointless waffle.
 
I think there's consensus that there was movement a few seconds prior to the collapse.
Have you managed to absorb NIST's views on the matter from 5 years ago yet ?

I personally have no doubt about the one a few seconds before because its magnitude is very clearly above the noise level.
It doesn't appear so from this comment.

I only have problems about the one minutes before
The one what ?

Yet again, exactly what issue(s) do you still have with the proofs for early motion I have provided you with ?
 
Yet again, exactly what issue(s) do you still have with the proofs for early motion I have provided you with ?

It is probably the fact that it is you providing them.

At this pace I am looking for a JREF breakthrough somewhere around 2019.
 
It is probably the fact that it is you providing them.

At this pace I am looking for a JREF breakthrough somewhere around 2019.
Is that your estimate for you, JREF too, summarizing your book's conclusion? CD or no CD? Inside job, no inside job? 2019?
... the supposed "gravity-driven collapse" is a mere illusion ...
Based on history... 2019 is optimistic. good luck


You are JREF. I think you are being optimistic on your estimate to figure out 911 and drop your failed CD, and the silly SG curve stuff.
 
It is probably the fact that it is you providing them.

At this pace I am looking for a JREF breakthrough somewhere around 2019.

From the book:

According to Kuhn, the ordinary process of science generates "puzzle solutions" from a set of assumptions, but does not attempt to question those assumptions. Extra-ordinary science takes place when those fundamental assumptions are challenged or in doubt.


So in order to understand the collapses we have to challenge the fundamental assumptions of science?
 
It is probably the fact that it is you providing them.
We can agree on that. Sunny day and blue sky here as I post.

I monitor this thread because I am interested in the question of magnitude of errors.

As I have several times challenged those opposing femr 2 - there are three questions current on the thread:

The first one is "Are there errors in femrs work?" This one has been pursued with some vigour as if it was relevant and significant. It isn't. It is a strawman argument based on a truism and a lie by innuendo - the truism being that all such measurement techniques have errors - due to "noise" and "perocedural artefacts" to put it simply. The false implication - strictly the as yet unproven implication - is that the errors are "big enough to matter". Which I doubt but I'm not the one making the claims and I try to avoid "reversed burden of proof" trickery.

The second is the question which no-one opposing femr wants to address. And it is the one that matters and the only one on this topic that is significant to numbers of members. "Are the errors big enough to matter?" Status - no one has shown that they are. (Therefore they aren't BTW)

The third question is of specific interest to pgimeno. At the risk of getting him wrong I understand it to be that he is not convinced that femrs explanations of his methods and data support the methods. If I have that bit correct pgimeno then limits his acceptance of femrs work to the single foundation of femrs own explanations. That limitation neatly prevents any of us proving femrs work acceptable because he only listens to femrs own explanations. Not fair you say? femr can look after himself but it is rather a funny objective or limitation on discussion.

Be clear it is NOT "Are femr's methods acceptably good?" It is "do I (pgimeno) believe femrs explanations?" So it locks out multiple other paths to address whether or not femr's work is accurate enough to be used for various purposes. And effectively drowning out discussion of what could well be the main topic of the thread.

I'm not interested in pgimeno's question whilst ever it remains artificially bounded to accept only femr's explanations. Obvious I (or you M_T) don't count if he will only listen to femr.

I am interested in question two - if ever we get to discuss it. :D

....At this pace I am looking for a JREF breakthrough somewhere around 2019.
your usual fog here M_T.

femr doesn't need a breakthrough on his general work.. There has been no legitimate rebuttal of anything other than details which don't matter.

Your own breakthrough could follow a lot earlier if you ever decide to post clear claims and follow acceptable processes of discussion.

The ball is with you on those ones. 2019 probaly optimistic.
 
it is rather a funny objective or limitation on discussion
One of the "funniest" recent "turns" (of which there are many as silly "angle" after silly "angle" is refuted) is the repeated decision from posters within the thread (primarily pgimeno and W.D.Clinger) to totally ignore the 1-pass Savitzky-Golay acceleration derivative curve provided over a month ago.

Given that their alleged "issues" with the older acceleration curve, provided about 2 YEARS ago, are based upon them not knowing exactly how it was produced, I find it very "interesting" that they continue to completely ignore the 1-pass SG curve for which they do have full details for complete replication.

Be clear it is NOT "Are femr's methods acceptably good?" It is "do I (pgimeno) believe femrs explanations?"
Another point which makes the decisions to completely ignore the acceleration curve that they have full details to replicate themselves even "stranger".

But then again, how could such continue to complain/reject/... when they have...

a) The raw numerical source data
b) The numerical data in real-world units and full details of how they were computed
c) Full disclosure of acceleration curve generation methodology
d) Ability to replicate acceleration curve themselves and perform any amount of "analysis" of both error propogation and derivative parameter variation.

621711303.png


It also appears that such members have been oblivious to NIST's "analysis" within Appendix C of NCStar 1-9 vol2 until very recently, yet have been "arguing against femr2" within this thread for ..... :rolleyes:
 
...It also appears that such members have been oblivious to NIST's "analysis" within Appendix C of NCStar 1-9 vol2 until very recently, yet have been "arguing against femr2" within this thread for ..... :rolleyes:

Any comparison with NIST (Even Chandler) has to be avoided because:
A) prima facie, as per your 16 points, your methods are multiple ways more accurate than NIST/Chandler et al. So the starting point for a legitimate rebuttal has to be from that end of the argument. With 16 barriers variously in the way; AND

B) The fact that all four of those lines in the multiple times reposted "NW Corner Dan Rather" graphs show the same trends of rapid acceleration followed by a period >G then reducing acceleration. And a finite difference of values between the four which does not alter the trends. But go back a few weeks and look at the verbal gymnastics of avoidance when I pressed that point.

Sure the "pre-release" section looks unreliable for reasons which differ between SG and poly methods. But that period of time has been highlighted many times as to significance. By my count the significant issue has only bee identified three times. And the displacement data of itself is sufficient - thereby bypassing all the nit picks as to various numeric methods and single or double stages of differentiation.

And those two - A and B above - are only the two most obvious. The technique of detailed nit picking is usually associated with the "other side" of the arguments.

Getting cooler here as summer passes. But still clear blue sky.

BTW I see that my "...version the umpteenth" phrase got purloined. I may have to review the "No royalties" policy. :D

Got it. I will not charge royalties if it is used validly. :rolleyes:
 
Last edited:
Any comparison with NIST (Even Chandler) has to be avoided because:
A) prima facie, as per your 16 points, your methods are multiple ways more accurate than NIST/Chandler et al. So the starting point for a legitimate rebuttal has to be from that end of the argument. With 16 barriers variously in the way;

Don't go there. That would breach the subject of purpose. ;)
B) The fact that all four of those lines in the multiple times reposted "NW Corner Dan Rather" graphs show the same trends of rapid acceleration followed by a period >G then reducing acceleration. And a finite difference of values between the four which does not alter the trends.

Again, You're getting dangerously close to "what's close enough". ;)


Getting cooler here as summer passes. But still clear blue sky.

With the exception of the sky, I'm going the other way, odd. :)
 
...Given that their alleged "issues" with the older acceleration curve, provided about 2 YEARS ago, are based upon them not knowing exactly how it was produced, I find it very "interesting" that they continue to completely ignore the 1-pass SG curve for which they do have full details for complete replication....
Archaeological quote mining has rules of its own.

They have to go back years to find "truth supporting" comments by some of our colleagues AND totally ignore what is actually being discussed at present. As if any current comment is invalidated by evidence of heresy from years back. There is fertile ground for ridicule/caricature in that bit of nonsense.

I think I actually said this recently BUT..

...I'll bet if I could quote mine into a few histories we could find evidence of belief in Santa Claus. And, by the prevailing logic, if they one stated belief in Santa, they must still hold to it.

Naturally I still do believe in Santa but that is a different issue. :D
 
Don't go there. That would breach the subject of purpose. ;)

Again, You're getting dangerously close to "what's close enough". ;)
How did you guess? ;)

I have a few funny ideas:
1) Makers of rulers and measuring devices are not the only users. And there are many more users of rulers than there are makers;
2) Some people specialise in using measuring devices as a service to other people. Probably because some things need professional measurer's to do the measuring. Land survey prior to change of title is one example. Surveyors are very often not the users of their measurement data;
3) Whether they measure for themselves or get other people to measure for them most users have their own "purpose" for needing the measurement.
5) And, strange tho it seems around here:
a) (Heaven forbid my heresy BUT) the level of accuracy required for a purpose depends on the "purpose" to which the measurements are to be put. And that requirement depends on the purpose of the user - not the taker of measurements OR the maker of the ruler.
b) THEREFORE is is as obvious as the genitals of a male canine that you cannot say whether measurements are "good enough" without knowing "what for?" (Note the popular Aussie expression - slightly moderated for more sensitive eyes. :o)

Bottom line is:
Arguing about whether or not there are errors in measured and numerically processed data is a strawman to avoid the real question. There is no doubt that measurement and processing involves errors. The real question here is "are the errors big enough to matter"? And the answer to that depends on the purpose. And I shouldn't have to point out that bleedingly obvious bit of reality.

...With the exception of the sky, I'm going the other way, odd. :)
Apart from getting seasons backwards you probably have some funny ideas about world geography and "up".
upover3.jpg
...I was born in "Yorksha" (that is how you pronounce it) - I'm 11/71 Pom and 60/71 Aussie.
 
Last edited:
You misunderstand many things, including the base point, which is about your double-standards when it comes to "what NIST says" -vs- "what femr2 says" :rolleyes:
You're probably aware that I'm not discussing with NIST, because they are not in this forum. So I doubt that the base point can be some double standards that I can't have. No wonder I misunderstand it.


Stupid question you already know the specific answer to. Why haven't you asked yourself whether using SG based derivative generation process results in wider or narrow error band ? ;)


So ? Even you are capable of connecting the dots here. The old poly fits are not part of this particular discussion.
Being bothered by me bringing up the poly fit? OK. This other graph also exhibits >10 ft/s² differences between the 1 pass and 2 pass plots, and both use SG:

621711303.jpg


Can you explain a 10 ft/s² difference between two plots purported to have an error band of less than ±3 ft/s²?


Interesting. Didn't you claim that your SD derivative plot matched my old plot ?
I claimed that my double-SG-plus-double-central-differencing plot was a fairly good match for your double-SG-plus-who-knows-what-else plot. Which I don't see the point of bringing to this discussion.


You said..."NIST basically say that the acceleration roughly corresponds with the blue line in this graph for a certain segment."

Which part of the green NIST curve would you say fits your statement ? :)
Are you being dumb on purpose? Or are you color blind to the point that you even confuse the written word as opposed to the actual color? Or are you unaware that NIST did two fits and I was referring to only one of them?


I was referring to this one:

[qimg]http://femr2.ucoz.com/_ph/7/2/5930538.jpg[/qimg]

Were you now ? Interesting.

One must then wonder why you used this one in your posts then...

:rolleyes: LOL.
Clarification: "this one" alluded to the FIT, not to the GRAPH. NIST did two fits, a curve fit and a linear fit. The linear fit corresponds to a segment of the blue line in the first plot I referenced, namely this plot and its blue line:

513801604.jpg


segment which you isolated in this other graph, which is why I referenced it in a subsequent post, in an attempt to clarify what segment/fit I was talking about:

5930538.jpg
.

And the curve fit corresponds to the green line, which you for some reason ("prove pgimeno wrong for the umpteenth time", perchance?) shifted to.

The first image I referred to had the advantage of showing not just one plot, as the one I referenced later, but several plots, which gave more opportunities to compare the shape. That's the reason I used it. And I compared the linear fit (blue line), not the curve fit (green line), even if both served my purpose equally well (as I commented afterwards). Why you shifted focus to the green line as if I was referring to it or as if I was not able to see it is still a mystery to me. :rolleyes:


I suspect you're simply trying to cover yet another gaffe.
:i:


Am I supposed to be a mind-reader or something ? :rolleyes:
You're supposed to be able to distinguish between blue and green.


So you don't know.

Why don't you simply ask, rather than making a series of guesses.
You have an history of not answering technical questions about data you've produced (think "what were your parameters for the SG plot?"). I deemed that approach unfruitful.


Other ? The reason is, as I ALREADY told you (though you didn't understand)...

Understando ?
OK. I'm still uncertain about how that was applied.


I imagine you've lost track of the "context" of this element of discussion. Need a reminder ? :) Step #1...we were talking about removing camera motion.
No I haven't, and I don't.


Of course it is. All footage of WTC7 is real-world, fully affected by all perspective effects...and not a bleedin' orthographic projection.
So is Dan Rather, which is equally fully affected by all perspective effects, yet you treat it as if it were an orthographic projection. Why do you have problems now with me asking what would be your problem if the projection in Cam #3 was orthographic?

The casual observer would say that the reason is to not concede that the issue with perspective is depth, because that would expose your blunder when you denied it and said I didn't know what I was talking about.

I told you that having depth data for the affected points (and it doesn't need to be extremely accurate, as small variations in depth make a very small difference) would be enough to transform the perspective projection that the camera did into an orthographic projection. You keep dismissing that point, even if it renders yours moot: if, given the depth, I can transform the camera view into an orthographic projection, then the fact that "[a]ll footage of WTC7 is real-world, fully affected by all perspective effects...and not a bleedin' orthographic projection" is the irrelevant point, not mine.

Actually, I already knew the answer to my question: an orthographic projection still has the problem of determining the angle of the trajectory of the studied point (NW corner in this case) with respect to the camera plane as it varies, and that has nothing to do with any skew due to perspective effects, which are absent in an orthographic projection. It's a mere consequence of the fact that the point's trajectory changes its angle with respect to the camera, not a problem of perspective effects or distortion as you have said several times.


The rest of your post is unsurprisingly pointless waffle.
With "pointless waffle" defined as "you cut too close to the bone", I guess.
 
Last edited:
You're probably aware that I'm not discussing with NIST, because they are not in this forum.
LOL. You don't need someone from NIST to be here to make assertions about their methods or results.

In fact you DO make assertions about NIST details further down in THIS post, but appear unable to criticise it in the slightest.

The NIST linear fit is crap. NIST performed no camera motion extraction, no perspective correction, no deinterlacing, threw away most of the available data, performed zero error analysis... yet you make assertions about their "analysis" with zero criticality.

Double-standards son.

So I doubt that the base point can be some double standards that I can't have. No wonder I misunderstand it.
So, where might I find your posts moaning and whining about lack of NIST error analysis, lack of perspective correction, lack of camera motion extraction, lack of... ? :)

Being bothered by me bringing up the poly fit?
Bothered ? Nah. If you choose to continue to focus on years old data when newer and higher quality data has been provided to you, that's entirely up to you...though it does highlight your purposes.

This other graph also exhibits >10 ft/s² differences between the 1 pass and 2 pass plots, and both use SG
During the earliest near-release moments, indeed.

Can you explain a 10 ft/s² difference between two plots purported to have an error band of less than ±3 ft/s²?
Data around the release point is affected by significant noise (more than at other times) for the Dan Rather viewpoint data.

The "old" SG plot was treated to minimise the effect of that increase in noise.

The "new" SG plot is more sensitive to it.

You could say the error around that region is higher.

Who "purported" the two plots to have the same error band ?

Who "purpoited" error bands for either plot ?

I've suggested a simple calc would result in around +/- 3 ft/s^2 error band for a different plot, and that you could assume similar for the SG plots...but if you disagree...do the math yourself.

Double it if you like. Who cares ?

Ever considered that full-timespan error band is impractical ?

There will certainly be a lower error band during periods of no/minimal motion, for numerous reasons.

There is absolutely more noise around the release point.

But then...you should already know this if you're looking at the data yourself... To be making assertions about segments of the data without even bothering to look at it is feeble.

I claimed that my double-SG-plus-double-central-differencing plot was a fairly good match for your double-SG-plus-who-knows-what-else plot. Which I don't see the point of bringing to this discussion.
ROFL. Why have you not produced an error analysis for your plots ? Why is the behaviour of your curve different to that of the 1-Pass SG plot around the release point ?

Are you being dumb on purpose?
Not being dumb in the slightest. I suggest you cut back on the rudeness. Tsk tsk.

Or are you color blind to the point that you even confuse the written word as opposed to the actual color?
ROFL. Not confused in the slightest son. You referred to one image whilst THINKING about a different one. Awesome. Mind-readers one and all we are :rolleyes:

Or are you unaware that NIST did two fits
I'm more than aware of 12.5.4, as well you know. They only did one acceleration "fit" btw :rolleyes:

and I was referring to only one of them?
So ? You don't get to dictate the limits of discussion here pal :)

You refer to NIST acceleration data...I'll point you to how crap their non-linear "model" is when the acceleration derivative is generated.

Clarification
Yawn.

I referenced it in a subsequent post, in an attempt to clarify what segment/fit I was talking about
So ? All after the fact dear boy.

Why you shifted focus to the green line as if I was referring to it or as if I was not able to see it is still a mystery to me.
Shifting focus ? Nope. Again, you don't get to dictate discussion scope.

You have an history of not answering technical questions about data you've produced (think "what were your parameters for the SG plot?"). I deemed that approach unfruitful.
ROFL.

Could you explain to me exactly why I should waste any of my time with you ?

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 ?

OK. I'm still uncertain about how that was applied.
What do you mean "applied" ?

When are you going to stop wandering around between early motion and acceleration derivative ?

No I haven't, and I don't.
Riiiight.

So is Dan Rather, which is equally fully affected by all perspective effects
Er, no. Whilst, of course, the same range of differing perspective distortions affect the Dan Rather footage, the magnitude of several of those effects are much smaller for such than for the cam#3 footage.

yet you treat it as if it were an orthographic projection
No I don't. Dan Rather data is not perspective corrected, which has been stated many times.

Why do you have problems now with me asking what would be your problem if the projection in Cam #3 was orthographic?
I don't have problems with such in the slightest...it simply isn't...so discussing it is a pointless waste of time. Might as well have a pointless discussion about what the situation would be if it was filmed with a fish-eye lens, or a telecentric lens :rolleyes:

It wasn't. Pointless waste of time.

The casual observer would say that the reason is to not concede that the issue with perspective is depth, because that would expose your blunder when you denied it and said I didn't know what I was talking about.
ROFL. The WTC7 footage suffers from numerous perspective distortions, in all three dimensions, non-linearly. Cam#3 especially so. Correct perspective correction goes far beyond your primitive and repeated assertions about "depth". "The isue is" ?! ROFL.

I told you that having depth data for the affected points
Depth "data". Per sample ? Ew. If you want to go generate that data, go ahead. Quite what you want to do with it is your own affair.

and it doesn't need to be extremely accurate, as small variations in depth make a very small difference
For what purpose ?

You don't remove other perspective effects by ignoring them you know.

would be enough to transform the perspective projection that the camera did into an orthographic projection
How did you remove lens distortion ? :rolleyes:

How did you negate adding noise to the sub-pixel fidelity data ?

You keep dismissing that point
I do indeed. See above.

even if it renders yours moot
It doesn't.

if, given the depth, I can transform the camera view into an orthographic projection
You can't ignore other perspective effects and call the result an orthographic projection.

then the fact that "[a]ll footage of WTC7 is real-world, fully affected by all perspective effects...and not a bleedin' orthographic projection" is the irrelevant point
No, it's the point. You don't have "the depth", you don't have information to be able to generate "the depth".

Tough.

IF there had been a series of cameras of identical specification set up around WTC7 at exact known locations with exact known orientation and frame-synced and... then ... :rolleyes:

You want to "prove my dismissal wrong". Go ahead. Generate your "depth data" and increase the accuracy of the derivative acceleration data (with proof of course that you have actually increased the accuracy). Enjoy.

Actually, I already knew the answer to my question: an orthographic projection...
We don't got us no such thang.

and that has nothing to do with any skew due to perspective effects,
You clearly don't even understand what I'm saying to you. Shock.

not a problem of perspective effects or distortion as you have said several times
Ye gads man. You don't have image data conforming to an orthographic projection, and you have no data available to be able to twist one out of what image data you do have. Get a grip man.

With "pointless waffle" defined as "you cut too close to the bone", I guess.
If that's what you actually believe...ROFL.

Yawn.
 

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