Merged Discussion of femr's video data analysis

Or a frame average (with DF removed and RGB range extension, of course) ;)

793931407.png



Now, given that the approach vector, determined from radar data, long before the last moment manouvers, is...

[drum roll]

... ~15 degrees clockwise from WTC orientation...

749689034.png


... can you think of any reason, other than the accurate rotoscoped evidence already presented, why the horizontal orientation angle at impact, after the last moment manouvers, is not going to be 15 degrees ? :D

BTW It's not 15 degrees, of course.

NIST got it wrong.

Eduardo Kausel got it wrong.

You, as you keep suggesting my "orientation is so far off everyone elses", got it wrong.

Anyone else want to retain suggestion of 15 degrees ?
 
Not me. But I've lost track of why it matters or what difference it makes. :o



Other than the spurious objective of:
[qimg]http://conleys.com.au/smilies/umpteenth.gif[/qimg]

Who cares if he's right or wrong. His work seems a lot like adding numbers to the value of Pi, interesting but of no practical value.
 
Who cares if he's right or wrong....
Taking only the OP and members showing "care":
- In the first two pages of the thread we have tfk (OP), DGM, beachnut, W. D. Clinger, carlitos, ozeco41, jaydeehess, pgimeno
- and last two pages of the thread we have MarkLindeman, Reactor drone, chrismohr plus some of the originals.

And, in those same "ends" of the thread we have T.A.M., Major_Tom, LSSBB, tsig showing "interest" in the thread discussion as distinct from the measurements per se. And those four coming from very different directions - whether or not you would count them as "caring if he's right or wrong".
...His work seems a lot like adding numbers to the value of Pi,...
There were some comments a few weeks back on the implicit "to whom" it "seems" - so it's not just you. But those to whom it seems "a lot like adding numbers to the value of P" don't have to comment if it is of no interest. The ones who are interested obviously don't regard it as of no interest.

However what you said:
...interesting but of no practical value.
...misses - or is ambiguous over - where the order of accuracy factors come into play.

If it was down at the red bit: 3.14159265358979323846264338327950288419716939937510582 ...the accuracy would be of no significance to WTC collapse discussion.

In fact anything after the first few decimals is also likely to be insignificant: 3.14159265358979323846264338327950288419716939937510582

For a lot of lay people the approximation 22/7 is near enough for pi - that is 3.14285... but most of us engineers would avoid that staying with the 3.14159.... (In the pre-calculator days we managed with 3.14 - if we could read the slide rule to that accuracy.) And even that approximation is closer by a couple of orders of magnitude than the level of imprecision being discussed here in the last few pages.

12o versus 3o and 5o versus 3o to quote just one of the recent aircraft movement counter claims. Those differences are in the first order of magnitude - certainly not down in the arena of microscopic detail.
 
Last edited:
Who needs to know what the angle is ? I don't.


Wonderful. Now, given that my models are oriented via satellite imagery, have a ******* guess what orientation a model fit exactly over an image of the thing will be...

Anyone building a model needs to know what the angle is. The MIT paper was out by 2° and I see no reason why yours couldn't be. You may get a perfect alignment to an aerial photograph on a map but who aligned the image on the map in the first place? When google stiches up a scene how concerned are they with the exact orientation of a building?




Excellent. Now, have you BOTHERED to research how they actually came up with the values ?

Yes I read the NIST report and the MIT paper. Neither of them use radar data to obtain impact orientation.

Have you bothered to cross-check with radar data to find early approach vector ?

Have you bothered to consider the effect of the last momemt manouvers ?

Perhaps you'd care to explain why you've chosen to completely ignore this rather unsubtle HINT that I provided you with a few days ago...

[qimg]http://femr2.ucoz.com/_ph/2/749689034.png[/qimg]

...and the angle a-curring.


You haven't bothered to fit any of these details into your thought process. Omitting such says much about competence and intent.

[qimg]http://femr2.ucoz.com/WCBS_Dub3_11d.gif[/qimg]

Lets consider last moment manouvres then. Given an aircraft speed of 540mph and I'll be generous and assume the entire 9 second clip was an even turn, in order to get from a 15° approach angle to a 3.5° approach angle the aircraft would have to be banked at about 29° for the entire duration of the clip. It clearly isn't. Looking at his bank angles and times he couldn't turn more than about 3° off course.
 
Anyone building a model needs to know what the angle is.
Yawn. Not necessary. Scene element placement all relative to each other. You want it, you've measured it. What good will it do you ? Bu**er all. You'd still use map imagery to place other features.

The MIT paper was out by 2° and I see no reason why yours couldn't be.
LOL. How many times do I need to repeat to you over and over again...tower models were placed using satellite and vector map data.

You may get a perfect alignment to an aerial photograph on a map but who aligned the image on the map in the first place? When google stiches up a scene how concerned are they with the exact orientation of a building?
ROFL. How far down the rabbit hole of attempt and fail to...
125144793.gif
...are you willing to go ?

:rolleyes:

Complete joke.

Specify the "stitching" error on this image...
http://femr2.ucoz.com/lineofsight1.jpg
...or be quiet.

Yes I read the NIST report and the MIT paper. Neither of them use radar data to obtain impact orientation.
I know. If they had included ovservations from it, they'd have known their numbers were crap.

Lets consider last moment manouvres then. Given an aircraft speed of 540mph and I'll be generous and assume the entire 9 second clip was an even turn, in order to get from a 15° approach angle to a 3.5° approach angle the aircraft would have to be banked at about 29° for the entire duration of the clip. It clearly isn't. Looking at his bank angles and times he couldn't turn more than about 3° off course.
ROFL. You can SEE the change in vector man ! Get a grip.

It's not a realtime GIF. It's not a "standard" turn, so whatever "formula" you think you're using, it's worthless.

You've completely failed to "prove femr2 wrong version the umpteenth".

You're utterly scraping the barrel.

Use a 3D modeler, recreate the scene, use hazarkhani footage to verify.

Anything other than that is simply substanceless handwaving.
 
Last edited:
Specify the "stitching" error on this image...
http://femr2.ucoz.com/lineofsight1.jpg
...or be quiet.

And what would be the point of doing that? You've already specified that that wasn't the map you used,

Before you ask, no, it doesn't affect my scene. That was done long before the pools were there.


ROFL. You can SEE the change in vector man ! Get a grip.

Since you're so good at seeing the changes in vectors how much do you think his dive angle changed based on that view?
 
ROFL. How far down the rabbit hole...
The all too often seen problem of losing the forest when:
- discussing a tree.
- Or the 3rd branch on that tree;
- or the 7th sub-branch of the 3rd branch on that tree;
-or the fourteenth twig on the 7th sub-branch of the 3rd branch on that tree;
-or the 57th leaf on the.....

So "forests v trees" for the US folk (I think) or "woods for trees" for us UK and AU folk.

...alternatively stated "when up to your arse in alligators it is easy to forget that the objective was 'drain the swamp'"

So the Op is "Discussion of femr's video data analysis" and I'm very unclear as to where a call for femr conjecture - viz:
...how much do you think his dive angle changed based on that view?
...is discussion of "analysis".

The status of discussion on the thread seems to be that there is a prima facie claim that femrs work is:
1) More accurate than some notable others; AND
2) Sufficiently accurate for many purposes - demonstrated by people who have asked for the data for use to support their purpose.

Asking femr to speculate doesn't progress the discussion - and I comprehend why femr is moved to say:
...How far down the rabbit hole of attempt and fail to...
125144793.gif
...are you willing to go ?

:rolleyes:
 
So the Op is "Discussion of femr's video data analysis" and I'm very unclear as to where a call for femr conjecture - viz:...is discussion of "analysis".

Asking femr to speculate doesn't progress the discussion - and I comprehend why femr is moved to say:

I assume, since femr brought up that visual that he'd done some kind of analysis on it. Asking what vertical angle change his analysis showed is on topic. If no analysis was done then pointing at a .Gif and saying, "just look at it" doesn't really help his case, if anything it points out his lack of understanding of 3d geometry.

Since the Op is "Discussion of femr's video data analysis" I'm very unclear as to what any of your recent posts have to do with the subject.
 
And what would be the point of doing that? You've already specified that that wasn't the map you used.
I have indeed. I used a previous set of satellite imagery in conjunction with vector maps, as I've told you many times. There's zero justification for your absurd stance.

Since you're so good at seeing the changes in vectors how much do you think his dive angle changed based on that view?
"Impertinent child" tone aside, I haven't specifically looked at late change in dive angle, though I have, of course, looked at impact vertical orientation...around the 3 degree mark.

I'd be looking at the altitude component of the radar data over time for that.

It seems the reason for posting that image has missed you completely. You can see a distinct change in horizontal vector.

Using that viewpoint to determine orientation and trajectory changes would require additional rotoscoping.

None of which is necessary, as I've already done it from the Hezarkhani viewpoint (amongst a couple of others).

Achimspok has iirc rotoscoped from that viewpoint, and his results tally with mine in terms of impact orientation.
 
I assume, since femr brought up that visual that he'd done some kind of analysis on it.
Assumption is the mother of all...

It's a convenient viewpoint to see late orientation changes.

Asking what vertical angle change his analysis showed is on topic.
I'm not interested in change of orientation over time. The analysis you're trying to "critique" is about orientation at impact, not orientation some time earlier.

The point of highlighting that the radar data indicates an approach vector 15 degrees clockwise from tower is to highlight the blatantly obvious fact that late manouvers change that.

If no analysis was done then pointing at a .Gif and saying, "just look at it" doesn't really help his case
I posted it to help you...a waste of time it seems. I have no "case" to make. You've not bothered to perform any rotoscoping. You've tried and failed, by many wandering and meandering routes, to find "issues" with my rotoscope results or cast "doubt" with your ultimately substanceless complaints.

My results stand. Would you Christmas-Eve it.

if anything it points out his lack of understanding of 3d geometry
ROFL. Surprisingly enough, I don't have a "lack of understanding of 3d geometry". What a stupid and underhand thing to say. LOL.

Given your previous "method" I find your absurd and baseless assertion rather funny. Highly ironic.
 
I'm very unclear as to what any of your recent posts have to do with the subject.
(Femr has already disposed of the comments in the earlier part of your post. I have no need to add further comments)

Your "very unclear" could be because my posts are actually "off-topic" or or simply a misfit between my writing clarity and your comprehension.

Lets eliminate the allegation of "Off Topic" first.

Are you asserting that my posts are "Off Topic"?

These are the ones I have made since you joined the discussions.

Can you identify (at least) one which you allege is "Off Topic" and explain why it is off topic?

(2956 Reactor drone - your post which changed the focus of discussion.)
2973 Brief comment response to femr.
2977 Brief reference to the previously identified key factors of the main discussion.
2982 Brief light hearted comment - spot on the faulty process
3011 Yet another brief light hearted comment - with a spot on technical point included.
3012 Comment to femr on directly relevant technical issues
3026 Comment on misunderstanding of both the thread topic and femrs goals.
3032 Agreed with MarkLindeman on need to avoid goalpost shifting.
3041 Response to MarkLindeman on relevance and accuracy.
3045 Further response to MarkLindeman on relevance.
3054 Response to ChrisMohr identifying a risk of misunderstanding.
3056 Consequential response to femr following 3054 above.
3059 Follow up response to ChrisMohr.
3062 Follow up clarification for femr2.
3074 Response to femr.
3078 Response to femr - alluding to an important aspect about WTC7 collapse.
3079 Response to a query by tsig.
3080 Describing a valid professional use for femr's analyses.
3084 Response to femr reaffirming the point identified in 3078.
3087 Response to pgimeno.
3089 Response to tsig acknowledging my apparent misreading of his earlier post.
3094 Response to twinstead - same query as tsig...except.
3102 Response to femr - (BTW it was showing my concern as to what you et al were trying to "prove").
3104 Direct and detailed on topic response to a query by tsig - spot on your topic focus BTW.
3108 The post you are querying.

Once we are clear that my posts are "On Topic" we can then resolve your lack of clarity....

....err... if any remaining lack of clarity is in fact "on topic" :D
 
It's a convenient viewpoint to see late orientation changes.

Given that the clip covers about 3.5km of travel and is seen from nearly end on it gives a highly exaggerated view of any orientation changes. From that angle, that's what a 3-4° turn looks like. With the radar tracking the aircraft at an initial 18° orientation relative to the towers the turn in at the second to last radar marker placed the aircraft at about 15°. A last minute turn isn't going to get him an extra 11.5°.

Since I had a 1/200th scale 767 in the kit pile and a couple of hours to spare I threw together a scale model of the scene. Locations and angles are as per the 2d maps used to draw the sightlines. WTC building stand ins are at 29° relative to a north south baseline and all scale distances are measured off that datum line. NIST model was at 12° yaw angle and 5° nose down pitch, Femr model was at 3.5° yaw and 3° nose down pitch. Both models had a 38° roll to the left. Once again it confirms a 10-12° impact orientation.

physicalmodelcompnist2_zpsf59b515a.jpg


physicalmodelcompfemr2_zps78d9b11a.jpg



Given your previous "method" I find your absurd and baseless assertion rather funny. Highly ironic.

Given that there's nothing wrong with my previous method I find your criticism of it absurd and baseless. Since I had the model there here's a visual for you,

2dvs3donview_zps81a45036.jpg


regardless of whether the aircraft is being viewed from ground level or from the impact level it has the same proportional nose to tail distance. The only thing that changes is the diagonal.
 
Last edited:
Given that the clip covers about 3.5km of travel
Just over 3.1. Why is every single value you state always wrong ?

and is seen from nearly end on it gives a highly exaggerated view of any orientation changes
Not exaggerated, but certainly blatant. You have to be careful to interpret correctly, sure. Exaggerate ? Nah.

From that angle, that's what a 3-4° turn looks like.
Angle ? Methinks you are forgetting a dimension or two. You don't appear to have even bothered to determine the camera location. I'm afraid you have to do more than assert, you have to show why ;)

With the radar tracking the aircraft at an initial 18° orientation relative to the towers the turn in at the second to last radar marker placed the aircraft at about 15°.
Radar tracked the aircraft at an initial location in a different city !!11!! :D

Assuming you mean the radar image provided, which covers significantly more than the last 3km of travel, why is it that you are incapable of sourcing any of your own data ?

Assuming you mean the angle change from a top-down viewpoint over the period of time of the provided animated GiF using only the available radar datapoints (which do NOT get you to the towers and do not include the last moment manouvers) then you're looking at about 1.5 degrees, not 3 degrees.

Why are all your values so shoddy ?

A last minute turn isn't going to get him an extra 11.5°.
A baseless assertion I'm afraid. You are also neglecting a number of dimensions.

Since I had a 1/200th scale 767 in the kit pile
I'm sure you did :rolleyes:

Did you bother to scale it correctly ?

image001.gif


Did you bother to apply appropriate dihedral wing angle ?

and a couple of hours to spare I threw together a scale model of the scene.
CLEARLY thrown together. Absolute joke given the kind of criticism you've aimed at my clearly far superior and proficient "efforts" :(

Locations and angles are as per the 2d maps used to draw the sightlines.
Sightlines ? Say what ?

Do you mean that you are using the high resolution satellite map, that I provided you with, as a plane within your renderering package, positioning scaled models of the WTC complex over such, setting up an appropriate camera placed correctly over the same image, determining focal point projection and aiming the camera as appropriate ?


Or do you mean you botched together a couple of measurements and placed objects with no ability to verify relative positioning or scale ?

I strongly suspect the latter, which would be attrocious.

WTC building stand ins are at 29° relative to a north south baseline and all scale distances are measured off that datum line.
Clearly you are not using the provided satellite imagery to define relative position between scene objects. Pfft.

NIST model was at 12° yaw angle and 5° nose down pitch
I strongly doubt your ability to remember to specify all aircraft orientation changes in aircraft axes, not world axes...

Your "renders" are an absolute joke.

It's not often I'm so blunt...

You haven't bothered to include secondary buildings, for a reason.

That reason is one of the following two options...

1) You are not competent to perform a simple rotoscope accurately.

2) You are fabricating results... aka lying.


Now, given that I performed my rotoscope with clearly far more care, and have absolutely zero reason to fabricate results...I'm afraid I suggest you are suffering from BOTH (1) AND (2) above.

That you get a result that NIST is "spot on" and femr2 is "wrong" I KNOW you've messed up.

Ending up with NIST "correct" is so blatantly dry-labbed it's hilarious.

Given that there's nothing wrong with my previous method I find your criticism of it absurd and baseless.
Of course there's something wrong with it, as I have explained to you several times.

It CANNOT capture off-plane angular changes. It cannot "work". It's fatally flawed for the purpose you are applying it to.

Since I had the model there here's a visual for you
An unreadable garbled image. Learn to use the tools first.

regardless of whether the aircraft is being viewed from ground level or from the impact level it has the same proportional nose to tail distance. The only thing that changes is the diagonal.
Oh dear.


This is getting ridiculous.

I'll get around to finding the box with the original scene files, or simply regenerate them.

Provide your scene files please :) I can then detail all of your failings in full.
 
I'm afraid you have to do more than assert, you have to show why ;)


Just taking a leaf out of your book.


Did you bother to scale it correctly ?


Did you bother to apply appropriate dihedral wing angle ?.


Scale models are already to scale and yes, I did apply the correct dihedral and flex of a wing in flight.


CLEARLY thrown together. Absolute joke given the kind of criticism you've aimed at my clearly far superior and proficient "efforts" :(.


Thrown together yes, it took longer to calculate the positions and set up models than it did to make them. You may think your efforts are far superior but they're not far superior if they consistently show the wrong angle.




Or do you mean you botched together a couple of measurements and placed objects with no ability to verify relative positioning or scale ?

I strongly suspect the latter, which would be attrocious.


If you wish to verify my angles all you have to do is create your own scale model. You have all the information you need to do so.


Clearly you are not using the provided satellite imagery to define relative position between scene objects. Pfft.


Oh, but I am.


I strongly doubt your ability to remember to specify all aircraft orientation changes in aircraft axes, not world axes....


There are only three to remember. With a tube passing through the length of the fuselage the model can be placed over a rod protruding from the scale building. That rod can be accurately positioned to achieve the specified pitch and yaw angles and the model can then be rotated on the rod to get the desired roll angle. Unlike your "superior model" mine is actually at 12° when I set it to 12°. If the plan views you provided are anything to go by your models are at least 2° over the specified values.

Your "renders" are an absolute joke..


They're not renders, they're real world models

It's not often I'm so blunt...

You haven't bothered to include secondary buildings, for a reason.

That reason is one of the following two options...

1) You are not competent to perform a simple rotoscope accurately.

2) You are fabricating results... aka lying.


Now, given that I performed my rotoscope with clearly far more care, and have absolutely zero reason to fabricate results...I'm afraid I suggest you are suffering from BOTH (1) AND (2) above.

That you get a result that NIST is "spot on" and femr2 is "wrong" I KNOW you've messed up..

Secondary buildings are only needed to accurately locate the camera position. Since we know that position it's not essential that they're there.

1) I haven't attempted rotoscoping yet. Figured I'd do a quick physical model to double check first.

2) I have no reason to fabricate results. I'm merely checking the alternative values against reality. It's not my fault that your values don't match.


Ending up with NIST "correct" is so blatantly dry-labbed it's hilarious.


Nothing has been adjusted to make NIST correct and you wrong. Positions are worked out, the camera is set and the chips fall where they may. As I said, if you want to check you're more than welcome to do your own model to verify.


Of course there's something wrong with it, as I have explained to you several times.


Actually you haven't explained it, merely asserted it.

It CANNOT capture off-plane angular changes. It cannot "work". It's fatally flawed for the purpose you are applying it to..

And there you go again.


An unreadable garbled image. Learn to use the tools first.


Seems fairly straightforward to me. Two images of the same aircraft in the same orientation, one with the camera at ground level, one with the camera at the same level as the aircraft. Building width is matched and the aircraft length matches. You can check this yourself by raising the camera and doing a render in your 3d environment if you want. Viewer elevation makes no difference, that's why the 2d check works.


Oh dear.


This is getting ridiculous.

I'll get around to finding the box with the original scene files, or simply regenerate them.

Provide your scene files please :) I can then detail all of your failings in full.

You first.
 
Last edited:
Have we figured out yet why this thread is in the 9-11 conspiracy subforum?

Most of us have - or rather didn't need to "figure it out" - there is no mystery.

1) The OP - tfk - started it here;
2) Forum policy - all 9/11 related discussions go in the 9/11 sub forum.

Why should it be anywhere else?

I imagine that if a Current Affairs discussion about "dangerous dogs" turned into a multi-page discussion on pet animal nutrition, with nothing whatsoever to do with dog behaviour, then it might be split off into Science.

It's a long time since 9/11 CT was addressed in this thread (was it ever?).

In fact the whole thread could be considered o/f ('off forum')
 
... I'm afraid you have to do more than assert, you have to show why ;). ...
Like you did for the SG filter? Never? Googled it up, and used it. For the aircraft you have left out a lot of stuff too. Lots of flying stuff. You need to get more dirty into the flying stuff; which you have not. Not surprising since you think failed 911 fringe nut papers are technical. You can't debunk the failed papers; what does this data debunk? Which failed 911 truth claim does this lay to rest? An attack on NIST, or what? Where did the engine land?

The hard part starts at impact. The scary dynamics start at impact, and what will be done past impact? Why are you obsessed with NIST? What angle would make a difference in the impact area; where is the plane going?
 
Last edited:
I imagine that if a Current Affairs discussion about "dangerous dogs" turned into a multi-page discussion on pet animal nutrition, with nothing whatsoever to do with dog behaviour, then it might be split off into Science.

It's a long time since 9/11 CT was addressed in this thread (was it ever?).

In fact the whole thread could be considered o/f ('off forum')

There are two relevant points which you are overlooking Glenn:
1) Policy - the 9/11 sub forum was established as a place for all 9/11 related discussion.
2) Consistency - if you and others want at this late stage to limit it to discussion of conspiracy then why is it that only the threads involving femr2 (and occasionally Major_Tom) are subject to these suggestions?

BTW your analogy is not accurate - try it on the premise that "All matters related to Dogs were to go in the Dog Forum"

The history of the sub forum would have been very different if technical discussion of 9/11 related matters had been banned.

The clearest current examples of pure science topics are the "ThermXte Dust" threads. Why is it that ChrisMohr, Oystein, Ivan K, Sunstealer are not subjected to this sort of policy change attack? Why the obvious desire to censor femr2?

Personally I wouldn't care if the forum history had been different - if it had been limited to the Socio-Political aspects of 9/11 and technical discussion sent elsewhere. But I doubt that the separation could have been maintained with any consistency.

Those who are suggesting such a change IMO either haven't thought it through OR are driven by pure personal animosity.

If we look at possible legitimate reasons for moving material out of this sub forum with the intent that the topics wither and die elsewhere why only pick on this thread? Surely the the most obvious time and bandwidth consuming nonsense we could target is in the threads which are dedicated to trolling and counter trolling? And there are many more of those. Some OPed with the obvious intention of trolling to attract counter trolling - just read the currently active threads in the subforum index page.
 
Last edited:

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