Wrong. I believe the shape of your graphs is more accurate than NIST's linear and curve fits. I thought I had said so in the same message and some messages ago.In fact you DO make assertions about NIST details further down in THIS post, but appear unable to criticise it in the slightest.
With a basis on the above? Yah, sureDouble-standards son.
I don't see any point on commenting anything on that. I also don't comment on mistakes by Millette, for example, even if it seems clear he made at least a couple. I'm not discussing with Millette. I'm not discussing with NIST. This is a forum in which you made claims, and I'm discussing them with you.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... ?![]()
Not only.During the earliest near-release moments, indeed.
(cropped only so the width isn't so annoying)
Which is obviously not the case for the period you claim to be over g.There will certainly be a lower error band during periods of no/minimal motion, for numerous reasons.
I have not used my graphs to claim over g. You have.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 ?
ROFL. Not confused in the slightest son. You referred to one image whilst THINKING about a different one.

That's false as I already explained. I talked about a segment of the blue horizontal line in the graph as being the acceleration that NIST claimed, in the context of discussing the utility of your graph. My statement was correct.
Where do I say "acceleration" fit?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 ? All after the fact dear boy.
Because you can't resist answering a single sentence addressed to you, I guess. It's not that I'm putting a gun in your head for you to reply.Could you explain to me exactly why I should waste any of my time with you ?
1) I'm now more convinced about early motion. The trace data was not enough for that; movement seen in the video was clearer.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 ?
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.
When are you going to stop wandering around between early motion and acceleration derivative ?
Ditto.You don't get to dictate the limits of discussion here pal![]()
So, Dan Rather is also fully affected by all perspective effects, is it not?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
Equally is another word for also. Or it is in Spanish.
Prove pgimeno wrong version the umpteenth?
If you suspect perspective issues, evaluating the distance of the measured points to the camera will give you an idea of how important the perspective issues are.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
It wasn't. Pointless waste of time.
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.
In the case of Dan Rather, the distance is too big and the variation of distance too small for the effect of perspective to be of any significance. The movement is also predominantly vertical so the angle of the fall with the camera plane is also quite small to be significant. For Cam #3 the angle is probably even less than for Dan Rather.
I might give it a try. As a first step I need the Dan Rather and cam #3 location. What information do you have?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.
My best shot at cam #3 location was this: http://www.formauri.es/personal/pgimeno/xfiles/11-s/Cam3Location.png but it still has some issues, namely the wall of the building on the left is not well aligned with the picture, the windows don't match very well (though that might be normal), and the corners of old WTC7 and new WTC7 don't match perfectly. Not to mention that I've seen issues with the heights of the buildings given by Google Earth in past. ETA: Also, it assumes 1:1 aspect ratio, which may or may not be correct.
My aim is to calculate the 3D path to measure the depth and the angle with the camera plane for each data point. With that, I can give perspective-corrected data for the view in real world units. My idea is to apply minimum and maximum estimations of the error to the data, in order to produce two datasets that determine an error band.
For the purpose of removing the perspective effects from the data without adding much noise/error.For what purpose ?and it doesn't need to be extremely accurate, as small variations in depth make a very small difference
I won't, just as you didn't for Dan Rather. Lens distortion is not perspective distortion.How did you remove lens distortion ?![]()
I hope to be able to give an error band and prove the fidelity of the manipulation of the data.How did you negate adding noise to the sub-pixel fidelity data ?
Nor was I suggesting thatYou can't ignore other perspective effects and call the result an orthographic projection.
Moving your goalposts again? "The depth" was totally not the issue before. It was completely unrelated to the issue. I was so wrong about it being the issue. Now the issue is that I can't generate it.No, it's the point. You don't have "the depth", you don't have information to be able to generate "the depth".
I just need the camera positions to generate "the depth". That and:
- Position of the NW corner.
- Height of the building.
- 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
- The traces from both cameras.
Last edited:
x