......
And I have already provided you with TWO credible (not only credible, but 100% correct) engineering sources that affirm, in the strongest terms possible, that scale is absolutely critical in planning, constructing, executing & analyzing experimental data.
I provided Harris’ textbook.
Structural Modeling and Experimental Techniques By Harry G. Harris http://tinyurl.com/gra8ejf
And I provided you with the chapters that discussed scaling of experiments.
Both of them state, with zero ambiguity, that "proper attention to scaling is absolutely crucial in performing experiments with scaled models.”
It seems that “providing you with scholarly and credible sources that clearly state what you don’t want to believe” is an exercise that falls on deaf ears.
Not quite. It is important to remember that there are undoubtedly lurkers here who are curious about the subject, maybe haven't thought about it too much or yet made up their minds, and whilst the FFs of this world are a lost cause, these other people aren't. That's why we have to keep on knocking this nonsense down flat. Rationalise FF to boredom, because others are watching.
I have no idea what the record rate was. I have no idea how many times it has been edited, compressed, uploaded, modified, or whatever. What I do know, from what I can see and have repeatedly posted, is that the software he uses places a reference point on each frame.
The original video was broadcast on US network TV. Dan Rather was speaking over it.
Therefore it was recorded using an ENG (Electronic News Gathering) camera, & broadcast using NTSC coding & compression algorithms that were available on that day. In other words, 29.97 frames / sec. (Round of to 30 frames / sec., or 60 fields/sec.)
Its resolution was 704 pixels wide (16 pixels of video blanking) x 240 lines / field and 2 fields (one upper, one lower) / frame.
Count the number ("N") of data points between any two time points (t1 & t2). The data frame rate is then (N-1)/(t2-t1).
__
Now, the frame rate in Chandler’s version of the video is different. It IS operating at 5 Frames Per Second. It says so right at the bottom of the first image, circled in red, next to FPS (“Frames Per Second”). Does that mean that Chandler used every frame? Nope.
What it means is that Chandler extracted every 6th frame from the video, BEFORE he loaded the Dan Rather video into Physics Toolkit.
Note that 5 frames/sec is 1/6th of 30 frames/sec.
Here's a screen shot from the video. Count the number of data points. The numbers should help.
Now, count the data points in his graph. The numbers should help.
Now, notice that number circled in red: "-9.885". What do you think that means?
Now, here's the really interesting part. Notice the number beside it:
"± 0.456" What do you think that means?
Now, show me your technical acumen. Do you think that Chandler's data really shows "Free fall acceleration"?
Or do you think that "9.885" number needs to be, uh, "embellished" or perhaps "clarified" a little bit?
Can't wait to hear your reply...
__
In case you need any more convincing, read the following. Note that this is from his analysis of the Tower 1 collapse, but he is using exactly the same technique there as he used in this early version for WTC7.
Destruction of the World Trade Center North
Tower and Fundamental Physics
By David Chandler http://tinyurl.com/ykundj3
page 6:
Chandler said:
One such program is Tracker,[9] which is part of the Open Source Physics project.[10] The frame rate of the Sauret video clip, which is the standard NTSC rate of 30,000 frames per 1001 s, or approximately 29.97 fps, serves as the time base. ... The vertical position of the roof line was marked every six frames (0.2 s intervals) and the data was exported to a spreadsheet for analysis.
The vertical component of velocity was computed using a symmetric difference numerical differentiation algorithm,
Get the picture yet?
Since ∆t = 0.2 seconds, each velocity point is the average over 0.4 seconds, (specifically: the position 0.2 seconds after - the position 0.2 seconds before, divided by 0.4 seconds).
__
Yes, in fact it DOES make sense to use every 6th data point instead of every one.
Remember that I told you that taking derivatives of discrete data was an “ill posed math problem”. This is EXACTLY WHY it is “ill posed”.
Do you see that “∆t” in the denominator of the “velocity calculation” just above.
Well, as ∆t gets shorter, then uncertainties in the velocity start to grow. The velocities start to jump greatly up & down due to small errors in the position.
Then uncertainties in the acceleration, from point to point, skyrocket out of control.
There are methods for taming this behavior, but a simple way to do so is to just use every nth point, which keeps ∆t reasonably large.
This is exactly why he uses every 6th point.
And then he runs up against one of the problems with translating discrete data into continuous data, the Nyquist Criteria. Which says that, at a sampling rate of 5 samples/second, the acceleration could be oscillating all over the place, and his analysis will never be able to see any oscillation with a frequency greater than about 5/6 = 0.8 Hz. So, the tower could be accelerating & decelerating at frequencies higher than this very slow oscillation (1.2 seconds / cycle), and Chandler’s technique will never see it.
This is something that Chandler, being a high school physics teacher, is clueless about.
Chandler also says he downloaded the video from the NIST website, so I have no idea what they did to it. I can't find the video on the internet, so I can't find out any information on my own.
Remember I told you about compression artifacts. Well, here they are:
Do you see the white lines outside the buildings' edges & the black lines inside the buildings' edges? Those are compression artifacts. Those lines are NOT REALLY there. They are false.
A Video camera is NOT an engineering tool. It's an entertainment tool. Those artifacts do not bother someone watching a video. But for someone trying to do videogrammetry, they produce errors. And in this case, significant errors.
Where is the TRUE edge of the building in these images?
When you zoom in on the images, this is what you see:
Now, you tell me exactly which pixel represents the top left corner of the building.
Something else to consider: these black & white compression artifacts do NOT stay constant as the building collapses. They get thinner & thicker. The gray scales vary, etc.
There are some that claim that they can resolve the true location of the corner of the roofline within 1/100th of a pixel.
Those people are clueless.
Within 1 pixel? Perhaps.
Within 1/2 pixel? I doubt it.
Within 1/100th of a pixel? They're smoking crack...
This video "CBS-Net Dub5 24.avi” is NOT the Dan Rather video, but instead a video from a different angle.
This can be seen by the fact that the top of WTC7 does NOT align with the horizon, meaning that this camera is higher than the Dan Rather camera.
The tilt that I showed is real, from that camera's viewpoint. Here is the image again, and it IS taken before the collapse began.
Sorry for the confusion about the videos.
FF, you'll have to look thru the CBS videos listed in the NIST site to find the Dan Rather video.
An approximately 2.5° ±0.5° Lean of the building, the error band being my estimate.
Note that this is likely a compound angle, with both NS & EW components. The only thing that one can say about the lean is that it is about 2.5° in the plane normal to the camera line of sight.
Note: the best vertical that I could find in this image is the right vertical edge of the light colored building in the lower right. The red line is parallel & slightly offset from this edge of the building.
That looks like about 14 seconds into the video below. East Penthouse has dropped into WTC 7 but the western rooftop structures are still there and the perimeter frame has yet to begin moving down. https://www.youtube.com/watch?v=OUkvnfV606w&feature=youtu.be
One notes that the eastern portion of WTC7 ended up falling to the NE and impacting the Fitterman bldg., very much as one would expect with the lean that is indicated in your still image above.
Its a professional, CBS TV network video from 2001. THEREFORE it IS 29.97 fps (30 fps is an old standard from B&W TV days). If its not 29.97 fps then its not the original video. That would mean that its even of lesser quality than CBS's original.
You said a position measurement was every frame. The graph shows 13 frames over that 2.25 second period. That corresponds to 5.78 frames per second. A 5.78 fps video would be extremely choppy. The video in question isn't choppy, therefore it isn't 5.78 fps.
So either the graph isn't plotting every velocity point, or velocity points were not taken at every frame. The acceleration slope is garnered from the graph which is then either not using every calculated average velocity, or only using those that were calculated, every 8th frame.
The original video was broadcast on US network TV. Dan Rather was speaking over it.
Therefore it was recorded using an ENG (Electronic News Gathering) camera, & broadcast using NTSC coding & compression algorithms that were available on that day. In other words, 29.97 frames / sec. (Round of to 30 frames / sec., or 60 fields/sec.)
Its resolution was 704 pixels wide (16 pixels of video blanking) x 240 lines / field and 2 fields (one upper, one lower) / frame.
Count the number ("N") of data points between any two time points (t1 & t2). The data frame rate is then (N-1)/(t2-t1).
__
Now, the frame rate in Chandler’s version of the video is different. It IS operating at 5 Frames Per Second. It says so right at the bottom of the first image, circled in red, next to FPS (“Frames Per Second”). Does that mean that Chandler used every frame? Nope.
What it means is that Chandler extracted every 6th frame from the video, BEFORE he loaded the Dan Rather video into Physics Toolkit.
I would have thought that a clue as to how to find the original video that Chandler used, would his stating that he downloaded it from NIST. Thus ANYONE who truly wanted to know would start their search there. Its a bit of a chore to navigate but I can find everything I want to find anytime the notion hits me. I guess some people aren't really looking for facts and truth.
Since you're not going to get the correct answer to the question that I asked about Chandler's actual results, let me give it to you.
The ±0.456 is the Standard Deviation of the calculated acceleration.
So, THIS is the correct interpretation of Chandler's results:
There is a 68% probability that the average acceleration over that interval was between 9.43 & 10.34 m/sec2.
There is a 95% probability that the average acceleration over that interval was between 8.97 & 10.80 m/sec2.
There is a 99.7% probability that the average acceleration over that interval was between 8.52 & 11.25 m/sec2.
Now, tell me again. Do you really think that Chandler, with this analysis, proved that WTC 7 came down "at free fall acceleration"?
Now, Chandler got his degree in physics. Like every physics major, he was required to execute, write up & turn in many physics labs. He knows all about error analysis & statistical variation. He knows all about standard deviations.
He 100% KNOWS that, based on the analysis that he did, he can claim nothing other than the probabilities and error ranges that I quoted above.
Please tell me why he has been lying to Truther & everyone else, in all of his presentations, and claiming that this measurement shows that the building collapsed "at free fall"?
Yeah, you're right. I pulled the comment.
You'll notice from the location of the roof line, that it is well into the collapse. When the building was standing, the roofline was level with the horizon line in the distance.
On the "leaning WTC7" video frame grab, it was well below that horizon line. That is, well into its collapse.
No excuse for me being that sloppy...
But, as a small consolation, it DOES show that, even early in its collapse, WTC7 did not come "straight down".
We've all seen that it tilted towards the south late in its collapse (in the video from the NW corner). This view shows that, relatively early in its collapse, the upper block had some component of tilt towards the west.
Please tell me why he has been lying to Truther & everyone else, in all of his presentations, and claiming that this measurement shows that the building collapsed "at free fall"?
That's all very well and mathy, but it makes some very glaring omissions. Primarily the trigonometry of the situation. If you are going to have pieces toppling, then you are going to need pivot points, and enough geometry for your javelin.
So I asked:
Can you quantify this "very large" energy required?
There are basically two theories on the table that would explain the source of that energy:
Gravity (GPE - Gravitational Potential Energy)
Explosives (ChE - Chemical Energy)
I quantified the requirement for the first theory - that GPE is the energy source: Drop height of 10 to 40 floors - easily available for collapses starting 78+ floors above ground.
Remember: You made a claim about the quantity of energy.
Now you: How much explosives (equivalent to chemical energy, ChE) does it take, per mass unit of steel to propel a steel section to 60 mph?
That calculation is much less straightforward.
I have done it.
Have you?
Can you guess?
I'm pretty sure anyone who has been posting in this sub forum for any length of time is well aware of this, what does that have to do with Chandler lying to people???
So I asked:
Can you quantify this "very large" energy required?
There are basically two theories on the table that would explain the source of that energy:
Gravity (GPE - Gravitational Potential Energy)
Explosives (ChE - Chemical Energy)
I quantified the requirement for the first theory - that GPE is the energy source: Drop height of 10 to 40 floors - easily available for collapses starting 78+ floors above ground.
Remember: You made a claim about the quantity of energy.
Now you: How much explosives (equivalent to chemical energy, ChE) does it take, per mass unit of steel to propel a steel section to 60 mph?
That calculation is much less straightforward.
I have done it.
Have you?
Can you guess?
We need a "smilie" for "jerking their chains" because we have two examples of trolling Poes. Both effective - they are reeling in the bites
-- but of low efficiency - making a lot of posts to get the results.
In an analogy to fishing using more for "bait" than the net catch of fish.
No match for ergo at his best - on one occasion I counted 27 "bites" - troll feeding responses - to a single ergo post.
And both of them display a level of intelligence used for avoidance/evasion which is good enough to understand the topic. AKA give themselves away. "Yes, I'm the Great Pretender" - could probably make a song about it.
OK, I have 3 steel spheres, one is a steel micro sphere, one is a one inch Diameter. steel sphere, One is a ten foot diameter wreaking ball, I drop each from ten feet, onto a standard
4 inch concrete slab, what would I observe in the experiment?
We need to examine the exact videos NIST and Chandler used. You have posted a link that documents the event, but it's not the same video. The video you posted is taken from "Channel 5". The video in question has no such logo.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.