IronyJuly, 2012 quote by Oystein belongs in this thread:
IronyJuly, 2012 quote by Oystein belongs in this thread:
Yes. From at least four different perspectives.Irony
I'm sure you do reallyI don't know what you mean.
I'm not...and what a strange aspect of my post to focus on...If you are referring to my three editions

So, you have actually been saying that my assertion of over-g IS supported by my analysis ?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 NOT supported by my analysis ?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, 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."Once again, I don't say your claim is erroneous. I am saying it's unsupported.
ROFL. 32.196 > 32.159. Done.Your burden of proof. You've failed.
Where ?There's a difference with your claim, though: he qualifies that as likely, not as a fact.
No, I'm not.Which means that you are in agreement with my assessment that cam #3 data is only good for looking at the shape.
Clearly.I don't see the problem nor do I know what hole you mean.
Did you miss where I provided you with an error band ?That's all the utility I see in your acceleration graph without an adequate quantification of error.
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 stand by my words
No, you just don't realise why I'm making the point.Silly pickiness.
To ensure the magnitude of traced camera motion is as near to that which affects WTC7.Why? To amplify the error in compensating for camera shake (in the form of displacement)?
I said such a long, long time ago.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".
You're missing the point.Can you show the symmetric difference acceleration graph you're talking about?
I wouldn't ask if I did.I'm sure you do really![]()
Should prove that I didn't know what you mean.I'm not...and what a strange aspect of my post to focus on...![]()
*sigh*So, you have actually been saying that my assertion of over-g IS supported by my analysis ?![]()
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 ?
No, I have NOT made that assertion [Your claim of over-g is not supported by your analysis] many times.
Yes.So, you have actually been saying that my assertion of over-g is NOT supported by my analysis ?![]()
See above. I have NOT made many times an assertion that includes that the error is too big.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."
S'funny![]()
Do you base your assertion of over g on NIST's data?ROFL. 32.196 > 32.159. Done.
Where ?There's a difference with your claim, though: he qualifies that as likely, not as a fact.
On the basis of my own analysis, I think a half-second of over-g acceleration was more likely than "about one second."
Embedded in a graph? Yes, I've missed it.Did you miss where I provided you with an error band ?
This graph? http://femr2.ucoz.com/_ph/7/513801604.png Yes, I know it. Your point?Did you notice the green line on the graph you linked ?
I see you skipped my question about orthographic projection. Interesting.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.
the skewing caused by perspective effects becomes particularly significant
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...Let's walk you through context again.
No-one said you did, you blithering...I have NOT made many times an assertion that includes that the error is too big.
No...Do you base your assertion of over g on NIST's data?![]()
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 ?![]()
Your burden of proof. You've failed.
ROFL. 32.196 > 32.159. Done.
ROFL. Lame.Embedded in a graph? Yes, I've missed it.
Good. There ya go. What's left for you to complain about ?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.
Jeez...This graph? http://femr2.ucoz.com/_ph/7/513801604.png Yes, I know it. Your point?
Boring. Have you managed to work out why tracing two static regions at differing distance from the camera is useful yet ?I see you skipped my question about orthographic projection. Interesting.
No need. I wrote it.Let me remind you what you said about the cam #3 view
Irrelevant.Would an orthographic projection make that problem disappear?
... (watches you quietly taking the goalposts as the ball gets closer)...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...
"Ta-da! You didn't score! Try again.""So, you have actually been saying that my assertion of over-g is NOT supported by my analysis ?"![]()
So, you have actually been saying that my assertion of over-g IS supported by my analysis ?![]()
Fair enough. I misunderstood your "It is" as "The acceleration is over g", not as "NIST's acceleration is over g".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.
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.Good. There ya go. What's left for you to complain about ?
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.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![]()
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.Boring. Have you managed to work out why tracing two static regions at differing distance from the camera is useful yet ?
Not in the least.Irrelevant.Would an orthographic projection make that problem disappear?
the skewing caused by perspective effects becomes particularly significant
ROFL. Your inept, repeated and verbose misinterpretation really is not my problem.... (watches you quietly taking the goalposts as the ball gets closer)...
You really need to work on your "quips". Yawn."Ta-da! You didn't score! Try again."
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"Fair enough. I misunderstood your "It is" as "The acceleration is over g", not as "NIST's acceleration is over g".
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 ?What graph of those you have posted does that apply to?
So ? Even you are capable of connecting the dots here. The old poly fits are not part of this particular discussion.In your graph below, the difference between Poly(10)/Poly(50) and SG at the 12.5s mark is about 10 ft/s².
Interesting. Didn't you claim that your SD derivative plot matched my old plot ?I don't see a graph obtained by symmetric difference.
You said..."NIST basically say that the acceleration roughly corresponds with the blue line in this graph for a certain segment."Yes, I agree that the shape is somewhat different to NIST's in that case too.
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.That's about the utility of your graphs, to compare shapes.
Were you now ? Interesting.I was referring to this one:![]()
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.
I suspect you're simply trying to cover yet another gaffe.I suspect you knew that and wanted to prove pgimeno wrong version the umpteenth.
It is indeed. Would have made more sense if you'd actually referred to that image at some point, you think ?After all, the graph is labeled "FEMR2 vs. NIST Linear Fit"
...which is simply "freefall".the blue line in this graph
So you don't know.It might have to do with discarding perspective effects
Other ? The reason is, as I ALREADY told you (though you didn't understand)...Any other reason?
Understando ?(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]
Of course it is. All footage of WTC7 is real-world, fully affected by all perspective effects...and not a bleedin' orthographic projection.Not in the least.
Have you managed to absorb NIST's views on the matter from 5 years ago yet ?I think there's consensus that there was movement a few seconds prior to the collapse.
It doesn't appear so from this comment.I personally have no doubt about the one a few seconds before because its magnitude is very clearly above the noise level.
The one what ?I only have problems about the one minutes before
Yet again, exactly what issue(s) do you still have with the proofs for early motion I have provided you with ?
Is that your estimate for you, JREF too, summarizing your book's conclusion? CD or no CD? Inside job, no inside job? 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.
Based on history... 2019 is optimistic. good luck... the supposed "gravity-driven collapse" is a mere illusion ...
It is probably the fact that it is you providing them.
At this pace I am looking for a JREF breakthrough somewhere around 2019.
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.
We can agree on that. Sunny day and blue sky here as I post.It is probably the fact that it is you providing them.
your usual fog here M_T.....At this pace I am looking for a JREF breakthrough somewhere around 2019.
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.it is rather a funny objective or limitation on discussion
Another point which makes the decisions to completely ignore the acceleration curve that they have full details to replicate themselves even "stranger".Be clear it is NOT "Are femr's methods acceptably good?" It is "do I (pgimeno) believe femrs explanations?"
...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 .....![]()
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;
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.
Getting cooler here as summer passes. But still clear blue sky.
Archaeological quote mining has rules of its own....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....
How did you guess?Don't go there. That would breach the subject of purpose.
Again, You're getting dangerously close to "what's close enough".![]()
Apart from getting seasons backwards you probably have some funny ideas about world geography and "up"....With the exception of the sky, I'm going the other way, odd.![]()
There's also the not-oft-discussed oddity that all you folks down/up there all iz from da future !Apart from getting seasons backwards you probably have some funny ideas about world geography and "up"
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.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"![]()
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: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.
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.Interesting. Didn't you claim that your SD derivative plot matched my old plot ?
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?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 ?![]()
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: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...
LOL.
I suspect you're simply trying to cover yet another gaffe.

You're supposed to be able to distinguish between blue and green.Am I supposed to be a mind-reader or something ?![]()
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.So you don't know.
Why don't you simply ask, rather than making a series of guesses.
OK. I'm still uncertain about how that was applied.Other ? The reason is, as I ALREADY told you (though you didn't understand)...
Understando ?
No I haven't, and I don't.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.
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?Of course it is. All footage of WTC7 is real-world, fully affected by all perspective effects...and not a bleedin' orthographic projection.
With "pointless waffle" defined as "you cut too close to the bone", I guess.The rest of your post is unsurprisingly pointless waffle.
LOL. You don't need someone from NIST to be here to make assertions about their methods or results.You're probably aware that I'm not discussing with NIST, because they are not in this forum.
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... ?So I doubt that the base point can be some double standards that I can't have. No wonder I misunderstand it.
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.Being bothered by me bringing up the poly fit?
During the earliest near-release moments, indeed.This other graph also exhibits >10 ft/s² differences between the 1 pass and 2 pass plots, and both use SG
Data around the release point is affected by significant noise (more than at other times) for the Dan Rather viewpoint data.Can you explain a 10 ft/s² difference between two plots purported to have an error band of less than ±3 ft/s²?
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 ?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.
Not being dumb in the slightest. I suggest you cut back on the rudeness. Tsk tsk.Are you being dumb on purpose?
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 areOr are you color blind to the point that you even confuse the written word as opposed to the actual color?
I'm more than aware of 12.5.4, as well you know. They only did one acceleration "fit" btwOr are you unaware that NIST did two fits
So ? You don't get to dictate the limits of discussion here paland I was referring to only one of them?
Yawn.Clarification
So ? All after the fact dear boy.I referenced it in a subsequent post, in an attempt to clarify what segment/fit I was talking about
Shifting focus ? Nope. Again, you don't get to dictate discussion scope.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.
ROFL.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.
What do you mean "applied" ?OK. I'm still uncertain about how that was applied.
Riiiight.No I haven't, and I don't.
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.So is Dan Rather, which is equally fully affected by all perspective effects
No I don't. Dan Rather data is not perspective corrected, which has been stated many times.yet you treat it as if it were an orthographic projection
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 lensWhy do you have problems now with me asking what would be your problem if the projection in Cam #3 was orthographic?
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.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.
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.I told you that having depth data for the affected points
For what purpose ?and it doesn't need to be extremely accurate, as small variations in depth make a very small difference
How did you remove lens distortion ?would be enough to transform the perspective projection that the camera did into an orthographic projection
I do indeed. See above.You keep dismissing that point
It doesn't.even if it renders yours moot
You can't ignore other perspective effects and call the result an orthographic projection.if, given the depth, I can transform the camera view into an orthographic projection
No, it's the point. You don't have "the depth", you don't have information to be able to generate "the depth".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
We don't got us no such thang.Actually, I already knew the answer to my question: an orthographic projection...
You clearly don't even understand what I'm saying to you. Shock.and that has nothing to do with any skew due to perspective effects,
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.not a problem of perspective effects or distortion as you have said several times
If that's what you actually believe...ROFL.With "pointless waffle" defined as "you cut too close to the bone", I guess.