Merged Discussion of femr's video data analysis

[qimg]http://conleys.com.au/smilies/scratch.gif[/qimg]
I didn't - it's not even in the subject of the post???
In that case, is it fair to say that the early motion, if present, might be either related or unrelated to the failure?

ETA: Or as you say in another thread,

"Leading" of necessity means "going before" BUT "going before" does not necessarily imply causality.
so early movement "going before" collapse does not necessarily imply early movement is caused by the deterioration of the structure that led to collapse?
 
Last edited:
In that case, is it fair to say that the early motion, if present, might be either related or unrelated to the failure?

Ye gads man.

Early motion is present.

From about 2 minutes prior to release (T0)

At that point (T~=60 on graph #2) there is an abrupt change in motion behaviour.

Prior to that (including the 4 minutes on graph #1) there is still motion but it is oscillation with very close correlation between horizontal and vertical trace axis motion.


Have you bothered to read Appendix C yet ?


Bored silly explaining the bleedin' obvious to numpties with inter-personal "issues".

NIST said:
Of primary interest in this analysis was any information that could shed light on the collapse sequence of WTC 7. The starting point of the final set of building vibrations at 6 s before the east penthouse began to fall indicated that an event had occurred within the building at that time. In addition, a comparison of the oscillatory period with a model of the building’s motion indicated the mode that had been excited by the event. Whether the building swayed in a single plane with a translational mode or twisted with a torsional mode, this information provided more insight for the structural engineer trying to piece together the sequence of events.

Cue...OH ! NIST said it, well that's okay then. Yeah, femr2, you're right, but what was the point ? We all knew NIST were right anyway :(

Note: "Final set of building vibrations"... NIST "threw away" their earlier trace data, suggesting it was "probably camera motion". I've subtracted camera motion from my data, and the result indicates further "building vibration" relating to "an event occurring within the building" starting around 2 minutes prior to release.

So, come on pgimeno, are you going to continue to be "confused" and "unsure" or are you going to throw out the results of the 13 page Appendix C of NCStar 1-9 vol 2 and start saying NIST got it wrong... ?

I've already posted information from Appendix C so will laugh myself silly if the response is as I suspect it will be.

I suspect it will lead me to write a critique of Appendix C, followed by "so what do YOU suggest happened ~2 minutes prior to release?" :mad: (and then we can all go round and round in circles on the 5 minute memory JREF hamster wheel)

Yawn.
 
I think the whole idea of "main release" is the origin of much of this confusion.
I don't see any complaint about NIST defining their "main release" time, T0.

Why not ?
 
Last edited:
I don't see any complaint about NIST defining their "main release" time, T0.

Why not ?
You might have noticed I didn't specify you when I made the comment. If you remember, I did say NIST shouldn't have gone down that road in the first place (in response to "truther" concerns). Wasn't that when this all started?
 
You might have noticed I didn't specify you when I made the comment.
And ?

If you remember, I did say NIST shouldn't have gone down that road in the first place (in response to "truther" concerns).
Appendix C - VIDEO ANALYSIS OF WTC 7 BUILDING VIBRATIONS BEFORE COLLAPSE is totally separate to section 12.5.3 (Timing of Collapse initiation and Progression). Only 12.5.3 was amended as a result of Chandler's intervention. Given that the NIST 5.4s metric did not change between 12.5.3 updates the NIST T0 (release) did not change as a result, and so was also unaffected by Chandler. The "start of main collapse/release" timing and verbage is part of Appendix C, not 12.5.3.

So when you say "I think the whole idea of "main release" is the origin of much of this confusion.", please be aware that such was in place within the NIST report long before intervention by Chandler, which did not affect such.
 
scratch.gif

I didn't - it's not even in the subject of the post???

In that case, is it fair to say that the early motion, if present, might be either related or unrelated to the failure?
No it is not "fair" for at least three reasons:
1) The issue arises from a simple but somewhat lengthy explanation which I posted in response to another members question. That member has not responded at this stage. You have ignored the two main thrusts of my explanation - viz a context setting explanation and a response to the specific question that the other member asked which response was legitimately set within the context which I had defined. Your focus being on a detail which in your first comment and now your second comment has no reference to the setting of my explanation. IF I was being pedantic I could call that "quote mining";
2) Your queries are devoid of any context. They are not in the context of my explanation nor have you explained the context in which you are putting them. IF I was being pedantic I could call that "pointless speculation" until you inform me of your context or "hypothesis"; AND
3) Specific to the question of "might be either related or unrelated to the failure?" That is conceivably a true option but "stand alone" it is worthless. I was explaining a couple of characteristic aspects of a "failure". That failure was "the building started to move and the movement got worse and the building fell down". I was explaining in an understood context - viz internet discussion of alternate reasons for collapse - where there are two main classes of explanations or counter claims. One of those classes would expect progressive build up of motion over and above normal building swaying. The other class would include 'an "event->immediate descent" scenario'.

So that is my framing of the hypothesis. If you wish to frame an alternate hypothesis you are free to do so. Such is the accepted practice of the so called scientific method. However it is logically conceivable that there could be two distinct and separate causes of gross movement. That inevitably leads to two further considerations:
1) How do two separate causes of gross movement arise; AND
2) If they do why does it make the slightest difference to me trying to explain to DGM that IMO "release point timing" is not critical?

So, overall, it is not "fair" to expect me to chase your queries about single issue anomalies when you ignore the main points of my posts and nit pick detailed anomalies. In fact that practice is the stock standard mainstream tactic of our truther and troll friends.
....ETA: Or as you say in another thread,

ozeco41 said:
"Leading" of necessity means "going before" BUT "going before" does not necessarily imply causality.
so early movement "going before" collapse does not necessarily imply early movement is caused by the deterioration of the structure that led to collapse?
That comment was made in a different setting where the alternate hypotheses under consideration were already stated. So it is not analogous to this thread discussion. Plus it was intended to prompt thought in the other thread so I prefer to not explain here - that would be "giving the game way" and detract from the "thought starter" purpose.
 
If you remember, I did say NIST shouldn't have gone down that road in the first place (in response to "truther" concerns). Wasn't that when this all started?
I was aware of that separate aspect when I posted my comments.
...So when you say "I think the whole idea of "main release" is the origin of much of this confusion.", please be aware that such was in place within the NIST report long before intervention by Chandler, which did not affect such.
My comments followed my SOP's by not relying on NIST findings. I think you are both aware of my long held practice. It arose in early days of my Internet forum activities. I saw repeated confusion of objectives switching from whatever the technical subject was to "NIST wuz right/wrong" apologetics. Easy way out for me - build arguments on independent evidential facts and don't rely on NIST findings. I may have occasionally faltered on that stance. :o

BTW a consequence of my NIST Neutrality is that I am free to disagree with NIST - lèse-majesté if you prefer the term. A somewhat risky practice in the face of a climate dominated by NISToPhillia ;)
 
I was aware of that separate aspect when I posted my comments.

My comments followed my SOP's by not relying on NIST findings. I think you are both aware of my long held practice. It arose in early days of my Internet forum activities. I saw repeated confusion of objectives switching from whatever the technical subject was to "NIST wuz right/wrong" apologetics. Easy way out for me - build arguments on independent evidential facts and don't rely on NIST findings. I may have occasionally faltered on that stance. :o

BTW a consequence of my NIST Neutrality is that I am free to disagree with NIST - lèse-majesté if you prefer the term. A somewhat risky practice in the face of a climate dominated by NISToPhillia ;)
Interesting thing is it is sort of the same for me. The collapse of the east penthouse told me more about what happened than much of the details in their report.

The time between to penthouse collapse and "release" combined with the length of time of "free-fall" tells us how many floors of exterior columns were left un-braced. Interesting but largely un-important (to me anyway). This is "one off" stuff. Make this building collapse a hundred times for the same reason these details would change everytime but, that east penthouse would likely still be the first thing you see come down.
;)
 
Interesting thing is it is sort of the same for me. The collapse of the east penthouse told me more about what happened than much of the details in their report.
Plus that Col 79 must have failed since it was under the EPH - thereby making most of the Coll 79 discussion pointless because there was no CD so Col 79 must have failed from fire.
...The time between to penthouse collapse and "release" combined with the length of time of "free-fall" tells us how many floors of exterior columns were left un-braced. Interesting but largely un-important (to me anyway).
not much interest to me either EXCEPT some people make a lot of fuss about it and I am "attracted" by some of the nonsense.

This is "one off" stuff. Make this building collapse a hundred times for the same reason these details would change everytime but, that east penthouse would likely still be the first thing you see come down.
;)
The other thing about "one-off" is that it is not a good topic for "scientific method". This is all one off engineering forensic analysis. NOT repeatable falsifiable multiple experiments aimed at turning an hypothesis into a theory. The difference often doesn't matter but sometimes it does and you see some funny claims based on shaky foundations.
 
The other thing about "one-off" is that it is not a good topic for "scientific method". This is all one off engineering forensic analysis. NOT repeatable falsifiable multiple experiments aimed at turning an hypothesis into a theory. The difference often doesn't matter but sometimes it does and you see some funny claims based on shaky foundations.

I know I must sound like a broken record but this is why I'd like femr2 to tell me (us) what his objectives are with pushing this data to the level he claims to need (mostly want). I have no problems with this data (something I've also said before) but, I'd like to know, "what the hell is he looking for?".

If it's just so he can have the most accurate data ever, fine. Leave NIST out of it. The level they used was what they needed for their use. For their objectives, they did not "blow it".

If the claim is they did not meet their objective. That would be a topic of another thread. ;)
 
I know I must sound like a broken record but this is why I'd like femr2 to tell me (us) what his objectives are with pushing this data to the level he claims to need (mostly want). I have no problems with this data (something I've also said before) but, I'd like to know, "what the hell is he looking for?".
I will also sound like a broken record because I have posted explanations several times and been ignored by folk who seem to be pushing other agendas.
1) I see nothing wrong with a person having a goal of making the best measurements he is able to achieve. That is a legitimate goal which femr has stated many times.
2) In femr's case it also carries a heuristic objective of "let's see where this leads" without the need for a predetermined outcome. [EDIT: Supplementary rant about types of objective removed - it will keep for another day :blush:]
....If it's just so he can have the most accurate data ever, fine. Leave NIST out of it. The level they used was what they needed for their use. For their objectives, they did not "blow it"...
That statement at best is "not proven" in this thread. I don't have the link/reference but IIRC femr has addressed it in detail elsewhere.
...If the claim is they did not meet their objective. That would be a topic of another thread. ;)
It is, I don't have the link. IIRC femr has done specifically that - a list of criticisms of NIST methods some if not all which show that they did not meet their own objectives.

Unstated but implied in your comments is that there are at least two "ranges" of possible concerns about NIST's accuracy viz:
A) Was NIST good enough to meet its own objective; CONTRAST WITH
B) Was NIST good enough to meet other peoples objectives.

And, back on my "broken record" that is the issue we see being evaded repeatedly. You cannot determine if NIST was good enough without answering the "good enough for what"? Just as the arguments in this thread which claim errors by femr are nonsense without support of "error big enough to matter" to "this person" who wants to use it for "this purpose".

1) There will always be errors in this form of measurement - a truism not worthy of argument; WHILST
2) The significant issue remains "are the errors big enough to matter" - which need answers to two subordinate questions:
...matter to who? AND
...for what purpose?

Hence my "broken record" comments about defining "purpose" and not changing the horse of purpose part way through the mid stream of argument.
[/END_BROKEN_RECORD] ;) :)
 
Last edited:
I will also sound like a broken record because I have posted explanations several times and been ignored by folk who seem to be pushing other agendas.
1) I see nothing wrong with a person having a goal of making the best measurements he is able to achieve. That is a legitimate goal which femr has stated many times.
2) In femr's case it also carries a heuristic objective of "let's see where this leads" without the need for a predetermined outcome.

I have no real problem with this. :)

I don't have the link/reference but IIRC femr has addressed it in detail elsewhere.
It is, I don't have the link. IIRC femr has done specifically that - a list of criticisms of NIST methods some if not all which show that they did not meet their own objectives.

Not so much. The NIST had a very simple set of guidelines and objectives (4 points actually). Not that I really care anymore but maybe if I get bored I'll re-review that thread, if I can find it. (with emphasis on the project objectives). ;)
 
Last edited:
I have no real problem with this. :)
thumbup.gif


...Not so much. The NIST had a very simple set of guidelines and objectives (4 points actually). Not that I really care anymore but maybe if I get bored I'll re-review that thread, if I can find it. (with emphasis on the project objectives). ;)
Sure - but the global or top level objectives are not the issue here. Rather the specific objectives for the measurement of this bit of WTC7 collapse.
 
Sure - but the global or top level objectives are not the issue here. Rather the specific objectives for the measurement of this bit of WTC7 collapse.
I think we're back to a subset outside of the original objectives. This subset for the most part was brought on by NIST playing "debunker". Something I believe they never should have bothered with. I also believe they felt this too and didn't give it a 100% effort.

Naturally this is only my opinion and not the topic of this thread ;)
 
Last edited:
I think we're back to a subset outside of the original objectives...
We always were for this discussion in this thread. He can correct me if I'm in error but I don't think anything femr has posted in this thread is directed at NIST's four global objectives.

The criticism currently under discussion are about femr's video data analysis and in recent pages here it has been based on the example of the NW corner of WTC7. NIST's global objectives are not the current topic.
....So This subset for the most part was brought on by NIST playing "debunker"....
Yes
Something I believe they never should have bothered with.
Agreed.
I also believe they felt this too and didn't give it a 100% effort.
Which though expressed differently is what femr2 keeps saying viz: "NIST didn't give it 100%" OR "NIST methods had shortcomings" (OR any other paraphrase you want....) - And that takes us back to two of the main themes that I have been playing "Broken Record" with. Viz:
A) There are demonstrated shortcomings in the NIST methods;
B) Which may be "big enough to matter" depending on the purpose to which a person wants to put the data.

And those two apply equally to femr's data which, prima facie, is based on procedures which are more accurate in multiple ways.

And a lot of folks posting here have made implicit statements about their own personal required level of accuracy (or freedom from error).

...and, believe it or not they are different standards

Meanwhile others have, in effect, said "there are errors and I'm not prepared to say what standard is required" - which makes their partial arguments pointless.

Naturally this is only my opinion and not the topic of this thread ;)
It is relevant because it is clarifying what the topic is.
 
We always were for this discussion in this thread. He can correct me if I'm in error but I don't think anything femr has posted in this thread is directed at NIST's four global objectives.

You could be right. Maybe I was not clear. I have always considered just the main objectives. After all. They are the ones I consider significant.

It is relevant because it is clarifying what the topic is.

I can go with that.
 
Ye gads man.

Early motion is present.
Haven't said the contrary.

But I have to keep those guards on until I examine the data in detail, which I haven't yet, or that will be turned into "So you finally admit that..." which isn't true.

And I haven't examined what NIST say in that respect in enough detail yet either.

As far as I know you have not yet given static point region information for cam #3. You gave it only for Dan Rather; not too satisfactory in my opinion but the video just can't give more.

I doubt I will be able to judge the early motion without information about static point region in cam #3.
 
1) The issue arises from a simple but somewhat lengthy explanation which I posted in response to another members question.
Which I didn't contend.


That member has not responded at this stage. You have ignored the two main thrusts of my explanation - viz a context setting explanation and a response to the specific question that the other member asked which response was legitimately set within the context which I had defined.
Yes, I didn't reply to that because there was no specific point of disagreement there or anything I had comments on.


Your focus being on a detail which in your first comment and now your second comment has no reference to the setting of my explanation.
Yes, a detail that you have brought up several times in past without going into any explanation as far as I know, and since this is the first time I see you give one, I focused on that detail which is what called my attention.


IF I was being pedantic I could call that "quote mining";
You can call it as you prefer.


2) Your queries are devoid of any context. They are not in the context of my explanation nor have you explained the context in which you are putting them. IF I was being pedantic I could call that "pointless speculation" until you inform me of your context or "hypothesis";
Context: While reading your message I saw a possible non sequitur in your logic and asked for a clarification.


3) Specific to the question of "might be either related or unrelated to the failure?" That is conceivably a true option but "stand alone" it is worthless.
It is not "stand alone". It is in the context of having perceived in your message a wrong assumption of causation that led you to make assertions while treating them as conclusions, not as a mere hypothesis.

If it was a mere hypothesis, I did not perceive it from your post.


So, overall, it is not "fair" to expect me to chase your queries about single issue anomalies when you ignore the main points of my posts and nit pick detailed anomalies. In fact that practice is the stock standard mainstream tactic of our truther and troll friends.
The difference being that I have nothing against the rest of your post, and I am NOT focusing on a detail in order to invalidate your whole argument, which would be standard truther tactic. My intention was to point out that one of the side facts you stated was not proved by your reasoning, in order to not mislead other readers into thinking it was a fact.


That comment was made in a different setting [...]
Totally irrelevant. It's an universal principle. I could similarly have quoted any of these:

http://en.wikipedia.org/wiki/Post_hoc_ergo_propter_hoc
http://skepdic.com/posthoc.html
http://www.fallacyfiles.org/posthocf.html
http://www.merriam-webster.com/dictionary/post hoc, ergo propter hoc

I chose to quote you because that showed clearly that you are aware of it.


Meanwhile others have, in effect, said "there are errors and I'm not prepared to say what standard is required" - which makes their partial arguments pointless.
I don't know who those others will be. In my case I have already stated in particular that femr2's claim of over g is not supported by the his analysis of his data, which turns it into a bare unsupported assertion. There's a clear universal standard required: if you make a claim, support it with a valid proof. That standard was not met.
 
Last edited:
femr2's claim of over g is not supported by the his analysis of his data
How about your acceleration plots ? Or W.D.Clinger's ? Or tfk's ?

...or NISTS ? (Remember, their linear regression is over-g, and their function for velocity, if derived to acceleration, also includes a long period over-g)

Perhaps you'd care to explain how the same general trend profile emerges from multiple SG plots by multiple persons, multiple poly fits, multiple symmetric difference plots, ... ?

Error and noise all biased in one direction to artificially increase acceleration with multiple methods ?

Your focus on "what femr2 has claimed" seems to shift with the breeze.

Since when has over-g been the bee in your bonnet ? :rolleyes:

Frankly I don't care whether you trust the data. I don't really care about absolute magnitude either. If you're more comfortable with the indicated over-g period being nearer to or even under g...go for it. Makes little difference to me. Quite funny to then look back through extensive discussion about the actual causes of over-g behaviour though (and how it is to be expected) :)

The "claims" I have made about acceleration behaviour are quite conservative and based upon trend and general magnitude.

You think their is an error, go prove it.

You have your own plots, your own methods (and similar results).

Quantify the propogated error in your own methods.

(There have already been discussions on the topic within this thread, but I'll be damned if I'm going to waste my time finding them for you)

Given the extra information available by inspection of the trend views, there's a really simple way to "test the hypothesis", since you know "when" to look ;)
 

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