If it doesn't agree with experiment, it's wrong.

Status
Not open for further replies.
Can you wife define "great speed"?

When do you think you can quantify ... Mass and gravity did the ejections at a speed you can't define.
Got the size of an explosive to do your ejection at great speed, a speed you have failed to define?

Good luck getting an answer, he's ignored several posts already in hopes we'd all forget after a few days. Now he's gish galloping into a section of the NIST report he doesn't seem to understand.

Typical twoofer behaviour.
 
FalseFlag,

The posters here have been thru all of this years ago. In excruciating, contentious detail. Many of the people in that discussion don’t post here anymore.
I’d stopped, until I saw your technically-challenged statements.

I am not making up my facts. I have made up nothing. I have cited NIST's own data when discussing constant acceleration.

Your technical ignorance prevents you from understanding - in detail - what NIST really said. You’re sloppy. You don’t pay close attention to the words.

And you don’t understand the physics or the engineering.

Average acceleration and constant acceleration are two entirely different things. Average acceleration is meaningless. The issue is constant acceleration.

And here is your colossal mistake.

Both Chandler (& then NIST) performed similar analyses of the velocity & acceleration of the fall of WTC7.
NIST did a better job in their analysis.
And a FAR better job in articulating their conclusions.

And, NO, NIST & Chandler do NOT say the same thing about the acceleration of WTC7. The difference is subtle, but it is there.

But, in both cases, they took position vs time data. NIST’s took a smarter point approximately above the CG of the building. Chandler took the westernmost point on the roof line.

The difference is that Chandler’s data will pick any rotational lurching of the building (CW or CCW about a N-S axis thru the CG) during collapse with a motion component in the vertical direction.
NIST’s data will pick up any similar rotational lurching as horizontal motion only, and it won’t add noise to the vertical analysis.

Both Chandler & NIST took the position vs. time data and calculated APPROXIMATE velocity versus time. NIST used a central difference approximation. (See NCSTAR1-9 v2, pg. 602). I’m not sure what Chandler used (back biased, central or forward biased). But in both cases, they took a data point approximately every 8th frame.

At 30 frames/sec, this means that, with a central difference approximation, the velocity is the AVERAGE over 0.53 seconds. (0.266 seconds prior & 0.266 seconds after the reported time value.)

So, you see, the velocity values themselves are, by themselves, average values over each interval.
They are NOT instantaneous values.

And then comes the GIANT error.

Both Chandler & NIST performed a “linear regression fit” (aka “a linear approximation”) of the velocity vs. time data, over a 2.25 second interval, in order to calculate an AVERAGE acceleration.

Two key points:
1. The slope is the “best fit linear approximation” … over the 2.25 second interval.! You’re correct that the accelerations reported by Chandler & NIST are not really “average”.

They are, really, “averages of averages”.

2. Any time, every time, anyone applies a LINEAR fit to any velocity vs. time data, in order to calculate acceleration, that technique (the “linear” part) forces the acceleration to be … a constant. No matter how scattered or non-linear the velocity data may be, a linear fit always produces a “constant” acceleration.

The constant acceleration is purely an artifact, an incorrect artifact, of Candler’s choice to perform a linear fit. The “constant acceleration” is NOT in the data. The data, when analyzed competently, shows without question, a NON-constant acceleration.

Chandler started out being somewhat truthful with his presentation, saying things like “the curve is nearly indistinguishable from free fall acceleration.” Notice that he initially said “the curve”, NOT “the building’s acceleration”.

But, pretty quickly, Chandler abandoned the truth, and lapsed into “Da Twoof”™. He started saying “the building fell "at G” for 2.25 seconds.” And all the clueless have been parroting him ever since.

I told you that NIST did a far better job with their terminology. They refer to the acceleration as approximate and as an average.

They say:
NIST said:
The slope of the velocity curve is approximately constant between about 1.75 s and 4.0 s. To estimate the downward acceleration during this stage, a straight line was fit to the open-circled velocity data points using linear regression (shown as a straight line in Figure 12–77). The slope of the straight line, which represents a constant acceleration, was found to be 32.2 ft/s2 (with a coefficient of regression R2 = 0.991), equivalent to the acceleration of gravity g. Note that this line closely matches the velocity curve between about 1.75 s and 4.0 s.

Note the bolded words.

You are correct that NIST then got sloppy, and stated on page 602:

NIST said:
In Stage 2, the north face descended at gravitational acceleration, as exterior column buckling progressed and the columns provided negligible support to the upper portion of the north face.

And again, on page 607
NIST said:
A more detailed analysis of the descent of the north face found three stages: (1) a slow descent with acceleration less than that of gravity that corresponded to the buckling of the exterior columns at the lower floors, (2) a freefall descent over approximately eight stories at gravitational acceleration for approximately 2.25 s, and ...

They should have said "at approximately gravitational acceleration" and "approximately freefall descent".
 
Extremely well put and explained tfk. I fear and expect that FF simply will be unable to comprehend it though. I sincerly hope I am wrong.

Its been pointed out to him before that the ONLY thing actually measured is the position of a location on the building and that then the average velocity is calculated between those points, and then an average acceleration is calculated.

That last bit is, as you say above, a bit mis-stated. A "best fit" straight line is a simplification that by definition creates a constant acceleration that is a type of average.
 
"Sloppy"
An overstatement, imho. Fact is this time period is at the end of a collapse sequence of between 17 and 20 seconds (depending largely on when the clock starts). By the time acceleration maxs , a great majority of structural integrity simply does not exist any longer.
I noted earlier that the first part of the facade itself , that began falling, was along the vertical kink on the north face. That movement was also seen on the rooftop , demonstrating that the entire central portion of the building was fully compromised at the time that truthers at best, start the collapse clock.

Focusing on the last 3 seconds of collapse made no sense at all to NIST. It cannot tell anyone anything about the cause of the collapse. Its hardly "sloppy" to spend little effort on a insignificant bit of minutia.

Only AE911T thinks it can and they cannot garner any widespread support for their odd position, from the professional community.
 
Last edited:
FalseFlag,
You’re sloppy.
I'm sloppy? Provide examples. Without examples your words are meaningless.

You don’t pay close attention to the words.
Provide examples. Without examples your words are meaningless.

And you don’t understand the physics or the engineering.
Please provide a specific example to prove I don't understand the physics or engineering using a source other than your own words, .

Both Chandler (& then NIST) performed similar analyses of the velocity & acceleration of the fall of WTC7.
NIST did a better job in their analysis.
And a FAR better job in articulating their conclusions.

Please provide concrete proof that NIST did a better job. Please provide a link to show the materials, data, and computer programs used in their analysis. Please explain, using sources other than your own opinion, why they did a better job in their analysis and they articulated their conclusions better.

And, NO, NIST & Chandler do NOT say the same thing about the acceleration of WTC7. The difference is subtle, but it is there.

Please transcribe exactly what David Chandler said about the acceleration of WTC7. Then, please let me know what NIST said. Also, please explain the subtle difference that you claim is there. Please make sure to explain why this subtle difference is relevant.

But, in both cases, they took position vs time data. NIST’s took a smarter point approximately above the CG of the building. Chandler took the westernmost point on the roof line.
Please explain, using a source other than your own opinion, why NIST's method is smarter. Also, please provide their exact method so I can see the exact pixel they used.

The difference is that Chandler’s data will pick any rotational lurching of the building (CW or CCW about a N-S axis thru the CG) during collapse with a motion component in the vertical direction.
NIST’s data will pick up any similar rotational lurching as horizontal motion only, and it won’t add noise to the vertical analysis.

Please provide proof that Chandler's video picks up this rotation, and please provide a source, other than your own opinion, why this matters.

Both Chandler & NIST took the position vs. time data and calculated APPROXIMATE velocity versus time. NIST used a central difference approximation. (See NCSTAR1-9 v2, pg. 602). I’m not sure what Chandler used (back biased, central or forward biased). But in both cases, they took a data point approximately every 8th frame.
Please explain why this matters.

At 30 frames/sec, this means that, with a central difference approximation, the velocity is the AVERAGE over 0.53 seconds. (0.266 seconds prior & 0.266 seconds after the reported time value.)

Please post where your data points are from and the formulas used to calculate the values you list. Also, please provide links to your sources.

So, you see, the velocity values themselves are, by themselves, average values over each interval.
They are NOT instantaneous values.
Please explain why this matters, using sources other than your own opinion.


Both Chandler & NIST performed a “linear regression fit” (aka “a linear approximation”) of the velocity vs. time data, over a 2.25 second interval, in order to calculate an AVERAGE acceleration.

Two key points:
1. The slope is the “best fit linear approximation” … over the 2.25 second interval.! You’re correct that the accelerations reported by Chandler & NIST are not really “average”.

They are, really, “averages of averages”.

2. Any time, every time, anyone applies a LINEAR fit to any velocity vs. time data, in order to calculate acceleration, that technique (the “linear” part) forces the acceleration to be … a constant. No matter how scattered or non-linear the velocity data may be, a linear fit always produces a “constant” acceleration.

In Chandler's video he clearly states that the computer program determines the best slope based on the data points. How do you know NIST's computer program is better, when they both arrived at the same results?

Finally, do you have a link to the video NIST uses for their measurements? I can't seem to find it anywhere. Is it the same one Chandler uses? I can't seem to find that, either.

Here's a few more questions. NIST doesn't mention freefall in their early drafts. Then, all of a sudden, they do. Who is the person who brought this to NIST's attention? If this was such a non-issue, why wouldn't NIST just ignore it? If this person wasn't right, wouldn't they say so? If the person who asked this question was wrong, then NIST would have simply dismissed it. They did not dismiss the issue. They addressed it, although they did come up with a lame explanation for it.
 
Last edited:
They should have said "at approximately gravitational acceleration" and "approximately freefall descent".
Then why didn't they? Why would they admit freefall, when they didn't need to? Are you really going to say they were "sloppy"? If so, I do agree with you, but for different reasons.

This also begs a major question. Why are you so critical, and I mean extremely critical, when it comes to how they measured acceleration during the collapse? If you are so critical of them here, then why do you accept their conclusions regarding progressive collapse, which is a laughable explanation? Why do you accept their computer model when it clearly doesn't match what can be observed - by anyone? Why are you not critical of them refusing to release the data they used to create their computer model? I really could go on at the glaring failures of NIST to do a proper investigation, but I will just stop here, for now.

I know the answer to all these questions, but will you admit it?

I don't mean this as a personal attack, but I really need to address this issue. Your assertions can only be interpreted that you claim to know physics and engineering better than anyone at NIST. The probability of this being true is extremely low. Even David Chandler admits the people at NIST are brilliant engineers. His conclusion is that they were tasked with covering up what really happened.
 
Last edited:
Its been pointed out to him before that the ONLY thing actually measured is the position of a location on the building and that then the average velocity is calculated between those points, and then an average acceleration is calculated.
No, the computer program David Chandler used tracks the vertical position of the reference point (the top corner of WTC7) over time. Each frame (not every 8 frames as was incorrectly claimed by another poster) generates a new reference point. The graph David Chandler shows in his video is not of average velocity. The graph is of actual velocity vs. time. The user can then enter a start and end time, and the computer will generate a straight line (slope) that is the best fit of all of the points in between the two times. This slope is the acceleration.

The graph shows an acceleration of (approximately) 9.8m/s/s for about 2.25 seconds. This value approximately matches NIST's experiments. Acceleration that has the same value over an interval can be said to have constant acceleration during that interval. Why? Simple. It's because the value of the acceleration does not change. Something that does not change is constant. The interval in this example is about 2.25 seconds. That means, without a doubt, anyone can correctly say there was constant acceleration during the collapse of WTC7 for about 2.25 seconds. The value of that acceleration was 9.8m/s/s, or freefall.

You keep saying I don't understand this. You are wrong, and your personal attacks are getting tiring. It is ludicrous to claim I'm wrong, when I'm the one who is correcting you, and providing clear proof that you are wrong.
 
Last edited:
I'm sloppy? Provide examples. Without examples your words are meaningless.


Provide examples. Without examples your words are meaningless.


Please provide a specific example to prove I don't understand the physics or engineering using a source other than your own words, .



Please provide concrete proof that NIST did a better job. Please provide a link to show the materials, data, and computer programs used in their analysis. Please explain, using sources other than your own opinion, why they did a better job in their analysis and they articulated their conclusions better.



Please transcribe exactly what David Chandler said about the acceleration of WTC7. Then, please let me know what NIST said. Also, please explain the subtle difference that you claim is there. Please make sure to explain why this subtle difference is relevant.


Please explain, using a source other than your own opinion, why NIST's method is smarter. Also, please provide their exact method so I can see the exact pixel they used.



Please provide proof that Chandler's video picks up this rotation, and please provide a source, other than your own opinion, why this matters.


Please explain why this matters.



Please post where your data points are from and the formulas used to calculate the values you list. Also, please provide links to your sources.


Please explain why this matters, using sources other than your own opinion.




In Chandler's video he clearly states that the computer program determines the best slope based on the data points. How do you know NIST's computer program is better, when they both arrived at the same results?

Finally, do you have a link to the video NIST uses for their measurements? I can't seem to find it anywhere. Is it the same one Chandler uses? I can't seem to find that, either.

Here's a few more questions. NIST doesn't mention freefall in their early drafts. Then, all of a sudden, they do. Who is the person who brought this to NIST's attention? If this was such a non-issue, why wouldn't NIST just ignore it? If this person wasn't right, wouldn't they say so? If the person who asked this question was wrong, then NIST would have simply dismissed it. They did not dismiss the issue. They addressed it, although they did come up with a lame explanation for it.

Crikey. I haven't seen such audacious argumentum ad lapidem since Danny Noel and his Global Platonic Theater.
 
Provide examples.

Please provide a specific example

Please provide concrete proof

Please transcribe exactly what

Please explain, using a source

Please provide proof

Please explain why this matters.

Please post where

Please explain why this matters

Demanding little thing aren't ya.

I only want one thing:

Please provide a real world example of movendi uniformiter in directum
 
Originally Posted by*FalseFlag*



Provide examples.*

Please provide a specific example

Please provide concrete proof*

Please transcribe exactly what*

Please explain, using a source*

Please provide proof*

Please explain why this matters.

Please post where*

Please explain why this matters

How about reading the NIST report in detail rather than just the cherries presented on Truther sites.
 
No, the computer program David Chandler used tracks the vertical position of the reference point (the top corner of WTC7) over time. Each frame (not every 8 frames as was incorrectly claimed by another poster) generates a new reference point. The graph David Chandler shows in his video is not of average velocity. The graph is of actual velocity vs. time. The user can then enter a start and end time, and the computer will generate a straight line (slope) that is the best fit of all of the points in between the two times. This slope is the acceleration.

The graph shows an acceleration of (approximately) 9.8m/s/s for about 2.25 seconds. This value approximately matches NIST's experiments. Acceleration that has the same value over an interval can be said to have constant acceleration during that interval. Why? Simple. It's because the value of the acceleration does not change. Something that does not change is constant. The interval in this example is about 2.25 seconds. That means, without a doubt, anyone can correctly say there was constant acceleration during the collapse of WTC7 for about 2.25 seconds. The value of that acceleration was 9.8m/s/s, or freefall.

You keep saying I don't understand this. You are wrong, and your personal attacks are getting tiring. It is ludicrous to claim I'm wrong, when I'm the one who is correcting you, and providing clear proof that you are wrong.

Could the 2.5 seconds be an artifact of the computer programs caculations?
 
No, the computer program David Chandler used tracks the vertical position of the reference point (the top corner of WTC7) over time. Each frame (not every 8 frames as was incorrectly claimed by another poster) generates a new reference point. The graph David Chandler shows in his video is not of average velocity. The graph is of actual velocity vs. time. The user can then enter a start and end time, and the computer will generate a straight line (slope) that is the best fit of all of the points in between the two times. This slope is the acceleration.

Thanks for making it clear you have no clue as to what velocity or acceleration is, or how they can be measured. Every point on Chandler's graph is a measurement of the average velocity in the time interval between two frames, and cannot possibly be anything else, and a "straight line that is the best fit of all the points between the two times" is by definition the average acceleration over that time interval. Your inability to grasp this is quite obvious to everyone here but you.

Dave
 
Here's a few more questions. NIST doesn't mention freefall in their early drafts. Then, all of a sudden, they do. Who is the person who brought this to NIST's attention?

David Chandler, IIRC.

If this was such a non-issue, why wouldn't NIST just ignore it?

NIST did just ignore it initially, because it is a non-issue.

If this person wasn't right, wouldn't they say so?

As we know, Chandler was right that WTC7 accelerated at close to 1G for about 2.25 seconds, so NIST had no reason to dispute this. You're confusing correctness with relevance; Chandler was correct that the collapse displayed this particular feature, but that doesn't make it important.

If the person who asked this question was wrong, then NIST would have simply dismissed it. They did not dismiss the issue. They addressed it, although they did come up with a lame explanation for it.

After being asked to address an irrelevant issue, NIST addressed it; what's your problem with that? Their response was based on the understanding that this particular feature of the collapse was unimportant in determining the cause of collapse and was not particularly anomalous. And, let's face it, you truthers would have whined just as loudly if they haven't addressed it as you're whining now about them not coming up with the conclusion that you want them to come up with.

Dave
 
I only want one thing:

Please provide a real world example of movendi uniformiter in directum

I was reading a webpage the other day that had two examples, the first will make you face palm, the second ironically they got right, except that they were using it as an example of an object in motion under pure Newtonian Physics, in which case they actually got it wrong....

Their examples...

(1) A bus traveling at a constant speed.
(2) A planet orbiting its sun.
 
Prove the following example is wrong.

Example: A object rests on the surface of the earth. The object is in a vacuum. Since the object is at rest, there is no motion. There is a downward force acting on the object, which is exerted by gravity. Since the object is at rest, there is an opposite force acting on the object in the opposite direction. This force is called the normal force. Since the object is in a vacuum, there is no force exerted by air. The only forces acting on the object are the force due to gravity and the normal force. The forces are balanced, so the net force is zero. As long as the net force is zero, the object will stay at rest.

Once again, prove any part of my example is wrong. Simply saying that I'm wrong doesn't count. You must clearly prove I'm wrong, with an example citing your sources and reasoning.

If your example was truly representative of newtons first law, I should be able to put on a spacesuit, climb inside your vacuum, and give your object a little kick. I'm going to give it an upwards kick like you would a soccer ball. If your example holds true to Newtons first law it should travel in a strait line at a constant speed (uniform motion) forever. Unfortunately you have Earths gravity field in your example, and as soon as I kick it it will start accelerating back towards the surface of the Earth at 9.8m/s/s where it will eventually come to rest.

If your example can't go from rest to uniform motion or vice versa then it is not representative of newtons first law and your application is flawed.

I have clearly proven that you are wrong and here is my source:

Lex I: Corpus omne perseverare in statu suo quiescendi vel movendi uniformiter in directum, nisi quatenus a viribus impressis cogitur statum illum mutare.
 
Status
Not open for further replies.

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