Merged Discussion of femr's video data analysis

...
Here's something for you to play with...

  • The NIST Flight 175 Impact Orientation and Trajectory is...WRONG.
  • Therefore the NIST impact damage assessment is...WRONG.
  • Therefore the subsequent simulations in response to that incorrect damage assessment are...WRONG.
  • The NIST Inward Bowing mechanism is...WRONG.
  • The NIST Initiation Sequence is...WRONG.
...

Does anyone agree or disagree with these claims?
 
Does anyone agree or disagree with these claims?

I don't have enough knowledge to come to any conclusion, although I do note that NO respected engineering or scientific organization I have seen agrees with those claims.
 
(Addressing the arguer deleted)
..................
Here's something for you to play with...

  • The NIST Flight 175 Impact Orientation and Trajectory is...WRONG.
  • Therefore the NIST impact damage assessment is...WRONG.
  • Therefore the subsequent simulations in response to that incorrect damage assessment are...WRONG.
  • The NIST Inward Bowing mechanism is...WRONG.
  • The NIST Initiation Sequence is...WRONG.
..................

What's left ? :)

100% of NIST's report minus one sub-pixel.:)


  • The NIST Flight 175 Impact Orientation and Trajectory is...WRONG. (Haven't researched, don't know)
  • Therefore the NIST impact damage assessment is...WRONG.(Haven't researched, don't know)
  • Therefore the subsequent simulations in response to that incorrect damage assessment are...WRONG.(Haven't researched, don't know)
  • The NIST Inward Bowing mechanism is...WRONG. (femr is wrong)
  • The NIST Initiation Sequence is...WRONG.(femr is wrong)
 
I don't have enough knowledge to come to any conclusion, although I do note that NO respected engineering or scientific organization I have seen agrees with those claims.

Now that is silly. Since femr2 hasn't published his data and analysis yet in any professional media, you can't expect any such organization to even be aware of his work. So lack of agreement cannot possibly be construed as disagreement.

This here is, after all, still a rather obscure corner of teh interwebz.
 
Doh

I'll look at the NIST report again when I get home from work. Any idea in the document where I'd find the trajectory?

No. I was hoping to get replies from people better informed about both NIST's and femr's work.
 
...
  • The NIST Flight 175 Impact Orientation and Trajectory is...WRONG. (Haven't researched, don't know)
  • Therefore the NIST impact damage assessment is...WRONG.(Haven't researched, don't know)
  • Therefore the subsequent simulations in response to that incorrect damage assessment are...WRONG.(Haven't researched, don't know)


  • Are you interested to find out if femr is right? It looks like these are interesting points.
    Maybe depends a bit on how wrong NIST is - are we talking about miniscule deviations, or something serious that will change the main conclusions?


    [*]The NIST Inward Bowing mechanism is...WRONG. (femr is wrong)
    [*]The NIST Initiation Sequence is...WRONG.(femr is wrong)

Hm okay. I know discussion of this has taken place, but it mostly was lost pretty much in noise :(
 
Now that is silly. Since femr2 hasn't published his data and analysis yet in any professional media, you can't expect any such organization to even be aware of his work. So lack of agreement cannot possibly be construed as disagreement.

This here is, after all, still a rather obscure corner of teh interwebz.

Well, what is he waiting for then?
 
Are you interested to find out if femr is right? It looks like these are interesting points.
Maybe depends a bit on how wrong NIST is - are we talking about miniscule deviations, or something serious that will change the main conclusions?
How do you judge whether error is serious enough to fundamentally affect simulation outcome ? Run the simulation again I suppose, but that's not likely to happen.

The errors are significant.

Here's an old draft (which has been discussed in this sub-forum in stupidly boring detail with the likes of tfk in the past)...
http://femr2.ucoz.com/draft175.htm
http://femr2.ucoz.com/draft175-part2.htm

I suggest digging out the old thread (though I warn you it is full of irrelevant whining from tfk). I'll see if I can find it.
 
But - what about femr's video data analysis? Do you, at this point in time, see it reaching a state where any conclusions either by NIST or by this or that CT needs to be changed because of femr's video data analysis? On the level of detail and what not that you, ozeco, are interested in? Or has femr's video data analysis so far helped you to come to new or revised conclusions of your own?

Or is it too early for that? Should we maybe suggest to femr to stop debating his video data analysis for now, and come back when he is done?
There is a lot of common ground between our understandings Oystein but we differ on the element that is central to my position.

There is a "big picture" and there are details within that picture. You do not distinguish the two and many of your posts or questions are ambiguous as a result. Take the questions W.D.Clinger responded to:
  • Are the differences to NIST's analysis relevant? No.
  • In particular, in what way does his data analysis warrant a change in NIST's conclusions? In no way.
  • And finally: does this change go in the direction of making any conspiracy theory, such as explosive demolition, a more likely, or even the most likely explanation of ALL of the available observation? No.
1 "relevant" to who? and in what context? I cannot respond meaningfully to that question unless you specify the target of the "relevance". Unlike W>D>Clinger who is either saying "relevant to him" OR has some implied context for relevancy - whether hios own or NIST or....whoever.
2 Why has warrant a change in NIST become a measure? We are involved in an Internet discussion about details within the "big picture"*. Even if changing NIST conclusions was a valid goal - and it isn't in this thread at this time - does the need to change NIST apply to every detail? I doubt it. The NIST big picture is "impact plus fire damage and no MIHOP". So the only legitimate change to NIST is if it hits the NIST big picture. And that requires either proof that there was MIHOP OR (must include the logical possibilities) proof that aircraft impact or fire damage were not factors in some way.
3 Conspiracy theory etc is outside the scope of the topic. It is a possible matter in the scope of future considerations BUT femr2 has been explicit in stating his process and, despite the wish of yourself and numerous other members that femr2 adopt a different process, his chosen process is legitimate. See my previous brief post.

Let me now turn to your specific points:
Do you, at this point in time, see it reaching a state where any conclusions either by NIST or by this or that CT needs to be changed because of femr's video data analysis?
My interest is in understanding the collapse mechanisms and testing my long held view that there was no CD. I see the possibility that femr2's work could support core led collapse initiation for WTC1 or WTC2 contrast with NIST's perimeter led explanation. I see the possibility of such a finding opening a new round of "truther led claims" IMNSHO those claims would run directly into the great big wall of logistic and security impossibility. End of story at that point. I cannot see that something of the scale of core led v perimeter led would be grounds for altering NIST's work - whether it was acknowledged or not by NIST.
On the level of detail and what not that you, ozeco, are interested in? Or has femr's video data analysis so far helped you to come to new or revised conclusions of your own?
Both questions go to my personal interest - as I said earlier those interests are "understanding the collapse mechanisms and testing my long held view that there was no CD" nothing femr2 is doing is likely to change my mind on "No CD" - the big arguments are simply not in the technical domain but in the domains of security and logistics. However every bit of technical evidence that femr2 or Major_Tom reveal adds to my understanding of mechanism details. Unlike other members I do not limit my interest to the big picture. I am interested in details that others legitimately provide. I don't undertake the research myself - so my level of interest is moderate. And I can with reasonable accuracy position each bit of new technical information on the overall picture of what happened. So some bits are more important than others.


* Even that statement stretches the scope of topic. We are supposed to be discussing techniques for measuring details. The actual details should only enter discussion as evidence for "Discussion of femr's video data analysis"
 
How do you judge whether error is serious enough to fundamentally affect simulation outcome ? Run the simulation again I suppose, but that's not likely to happen.

The errors are significant.

Here's an old draft (which has been discussed in this sub-forum in stupidly boring detail with the likes of tfk in the past)...
http://femr2.ucoz.com/draft175.htm
http://femr2.ucoz.com/draft175-part2.htm

I suggest digging out the old thread (though I warn you it is full of irrelevant whining from tfk). I'll see if I can find it.

Has this been within the scope of this current thread?

But thanks anyway for posting the link. I read, although briefly (it's past midnight here) with interest.
 
How do you judge whether error is serious enough to fundamentally affect simulation outcome ? Run the simulation again I suppose, but that's not likely to happen.

The errors are significant.

To parrot ozeco: Significant for what, and to whom?
I was asking Basque Arch, so the questions I posted would have to get answered within his frame of reference.
Of course you, femr, are invited and welcome to add and explain your perspective within your frame of reference. But you already declared that you won't do that - go for conclusions. So you might as well not reply to questions I ask of other members.
 
To parrot ozeco: Significant for what, and to whom?
Significant in answer to your question..."are we talking about miniscule deviations, or something serious"

Significant error.

An example...


NIST suggest Lateral Approach Angle - 15 degrees +/- 2 degrees.

If camera placement is determined within a 100ft error of margin, the NIST angle is out by over 7 degrees.

If camera placement is determined within a 10ft error of margin, the NIST angle is out by over 9 degrees.

I'm confident in the latter.

NIST out by ~9 degrees.

Significant.

Ten Foot (10ft) Lateral Change in the Camera Position:
image005.gif


Hundred Foot (100ft) Lateral Change in the Camera Position:
image006.gif


NIST in red btw.

Oh, and the above over actual footage...
938786605.gif
 
Last edited:
There is a lot of common ground between our understandings Oystein but we differ on the element that is central to my position.

There is a "big picture" and there are details within that picture. You do not distinguish the two and many of your posts or questions are ambiguous as a result.

Hm actually, part of my interest today is to fathom that ambiguity.

Take the questions W.D.Clinger responded to:

1 "relevant" to who? and in what context? I cannot respond meaningfully to that question unless you specify the target of the "relevance". Unlike W>D>Clinger who is either saying "relevant to him" OR has some implied context for relevancy - whether hios own or NIST or....whoever.

I have no fixed target. I am happy if you respond within your frame of reference (and you do; thanks).

2 Why has warrant a change in NIST become a measure? We are involved in an Internet discussion about details within the "big picture"*. Even if changing NIST conclusions was a valid goal - and it isn't in this thread at this time -



* Even that statement stretches the scope of topic. We are supposed to be discussing techniques for measuring details. The actual details should only enter discussion as evidence for "Discussion of femr's video data analysis"

Oh, I disagree: It became a valid goal in this thread the moment my separate thread to discuss any conclusions to be drawn from the analysis was merged with this thread upon the request of the OP of this thread, femr, by a moderator.

does the need to change NIST apply to every detail? I doubt it. The NIST big picture is "impact plus fire damage and no MIHOP". So the only legitimate change to NIST is if it hits the NIST big picture. And that requires either proof that there was MIHOP OR (must include the logical possibilities) proof that aircraft impact or fire damage were not factors in some way.

So we (you and I) agree that such proof is unlikely to be forthcoming?

3 Conspiracy theory etc is outside the scope of the topic.

No. It became a topic when my thread was merged with this here...

It is a possible matter in the scope of future considerations BUT femr2 has been explicit in stating his process and, despite the wish of yourself and numerous other members that femr2 adopt a different process, his chosen process is legitimate. See my previous brief post.

Femr2 doesn't have to participate explicitly, but it was upon his request that discussion of consequences be merged into this thread, so I take it that femr2 is cool with debating that topic here. This needs not alter his stated process.

Let me now turn to your specific points:

Great, thanks. I read and duly noted. You had written about this before, and I am with you or understand your point of view mostly. I'll therefore not quote and respond to all of your post from here on, just a few minor remarks:

I cannot see that something of the scale of core led v perimeter led would be grounds for altering NIST's work - whether it was acknowledged or not by NIST.

Huh? :confused: Did you miss a negation here? This would appear like a major modification, even if it does not address foul play.

...Unlike other members I do not limit my interest to the big picture. I am interested in details that others legitimately provide. I don't undertake the research myself - so my level of interest is moderate. And I can with reasonable accuracy position each bit of new technical information on the overall picture of what happened. So some bits are more important than others.

As an interested non-engineer, I am frankly quite overwhelmed by all the details of both NIST's reports and femr2's analysises (is there a plural to analysis? ^^), so I am happy and thankful for all guidance and elucidation. To me, lots of what is debated here looks like pieces in a large puzzle: Some are already connected and definitely placed, some are connected to some others but not yet in their final position, some are well placed but not yet connected, and some are neither connected nor placed. In some regions of this puzzle, I am picking up pieces at random and see if I can place them or not, with the help of the big picture printed on the box, in other regions, I am already proceding quite systematically on my own.
Occasionally, someone tries to help me, but I can see that he is wrong, even though I don't yet know what is right.
 
...
And let's not lose sight of the OP of this thread - it was set up by another member, not femr2, to allow "Discussion of femr's video data analysis" :rolleyes:

Oops, I made that mistake a few times tonight to say this is femr's thread. :o
 
...
NIST out by ~9 degrees.

Significant.
...

And that is significant ... for what and to whom? For example, does that alter the basic finding that plane impact damaged a number of load bearing columns, blew of fireproofing, and started fires on several floors at once; and that plane impacts and fires caused WTC2 to collapse? Yes, no, or don't know?
(I am acting more obtuse than I actually am. I hope you get my point. Oh, and as I said a few times already, it is okay and accepted if you don't tell me why (towards what end goal) this is significant to you)
 

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