• Quick note - the problem with Youtube videos not embedding on the forum appears to have been fixed, thanks to ZiprHead. If you do still see problems let me know.

Merged Discussion of femr's video data analysis

So where is it from then? You haven't given a reference.
Are you for real ? It's a graph I made by recording the time between each of the datapoints in figure 12-76.

ETA, nevermind, why bother asking you for proper documentation? The graph doesn't provide any insight re: your earlier points anyway. It doesn't make any difference.
It provides exactly the insight required for me to say...
On their displacement data, there is a datapoint at T0, and the next one is nearly a second later...
[qimg]http://femr2.ucoz.com/_ph/7/2/415549729.jpg[/qimg]

They waited a bit (though not long enough) before extracting data for the trace above region B.

Sloppy. (And indication they may have manually traced. Yuk.)
:rolleyes:
 
See post below

Clarified that your graph labels the first data pair differently from NIST graph. Oh well.
 
Last edited:
Which leaves us once again with a void of data needed to support the claims made by both you and MT.

Nothing much has changed it seems. The new graph tracing the pixel brightness was a start though....

But I'm beginning to think that you haven't actually done the maths to back up the many assertions, otherwise methinks you would have posted the data already. In that case it really does make your claims seem quite poorly supported - I refer to the repeated assertions regarding horizontal/vertical motion components, and the complete invalidity of the NIST T=0 which is your central claim.
 
See above :rolleyes:
You really are making a bit of a fool of yourself you know. This is trivially simple stuff. Wasting my time because you can't eveb read a graph ? Jeebus.

not really exact, was it? Roughly, approximately
As accurate as possible from the image extracted from the PDF. Accurate enough.

Your *nearer to 0.5* made me laugh. Get some glasses eh.

And does absolutely nothing to prove your many assumptions, as I've complained to you about.
It proves no data between T0 and T=~0.86, supporting the suggestion that NIST started their positional trace later than T0 (which would be a good thing for them to do, as the roofline structures are in the way. They didn't leave it quite long enough, but hey)

Am I for real? Just asking questions, that's all. :)
Nah, you're making repeated incredibly inept assertions. Get some sleep.
 
:jaw-dropp

~0.86s

Can you not read a graph ? Measure it, rather than waving your arms around and guessing.

Uhm, using your own timescale (1second interval), unless you've graphed it incorrectly, datapoint 1 to datapoint 2 are about .6 seconds apart.

Where is the datatapoint at T=0? Oh, it's missing. I checked 12-76 I see it is there in that graph.

Wasn't clear on yours because of that.
 
I refer to the repeated assertions regarding horizontal/vertical motion components
I've already stated I haven't determined z-plane information...
There have been discussions aimed at determining specific N-S movement, but there are not really enough different video viewpoints to gain much accurate z-plane information. The better route is simply to recognise that the Cam#3 viewpoint suffers from the perspective problem and not use the region of flexure to define T0, better still don't use the cam#3 viewopint to define T0 at all. Use the Dan Rather viewpoint instead.


and the complete invalidity of the NIST T=0 which is your central claim.
Here's a graph you might like from Jul 2010... ;)


Take your time.

Oh, and...


Useful information that.
 
It proves no data between T0 and T=~0.86, supporting the suggestion that NIST started their positional trace later than T0 (which would be a good thing for them to do, as the roofline structures are in the way. They didn't leave it quite long enough, but hey)

Maybe. But you really don't know. I don't see any reason to trust your assumptions as facts.
 
I've already stated I haven't determined z-plane information...

-There have been discussions aimed at determining specific N-S movement, but there are not really enough different video viewpoints to gain much accurate z-plane information. The better route is simply to recognise that the Cam#3 viewpoint suffers from the perspective problem and not use the region of flexure to define T0, better still don't use the cam#3 viewopint to define T0 at all. Use the Dan Rather viewpoint instead.'

Yes, fine, so you have given up trying to determine it. Then it would be appropriate to stop bringing up the topic as if you had some conclusive evidence/ hard data, which you don't.

You decided to do it another way, again fine. That's your choice, doesn't mean it is the only valid choice.


Here's a graph you might like from Jul 2010... ;)
[qimg]http://femr2.ucoz.com/_ph/7/2/736613183.jpg[/qimg]

Take your time.

Oh, and...
[qimg]http://femr2.ucoz.com/_ph/7/2/558511393.jpg[/qimg]

Useful information that.

Without knowing what the 0 frame refers to these graphs are not useful. You might like to include that info in the graph.
 
Last edited:
Uhm, using your own timescale (1second interval), unless you've graphed it incorrectly, datapoint 1 to datapoint 2 are about .6 seconds apart.

Where is the datatapoint at T=0? Oh, it's missing. I checked 12-76 I see it is there in that graph.

Wasn't clear on yours because of that.
ROFL...
975319243.png


See that black circle where the two axes intersect ? T0, with a datapoint marker.

See the next one ? ~0.86s.

My graph shows the datapoint spacing, thus the title...
"NIST Figure 12-76 Datapoint Spacing"
...and the axis labels...
"Separation (s) / Datapoint Pair"

Get a grip man.
 
Last edited:
I'll put the matter another way - the exact N/S motions are unknown. Determinations are inconclusive contrary to the claims of some; added to this the limited resolution of the videos and therefore data derived can only be used as estimations for general purposes.

In my view so long as the measurements fall within a reasonable range of accuracy and are recognized to be inherently inexact, they are useful.
Approximate collapse times may vary by 1 second or more, depending on the method of measurement. This does not in itself invalidate the major engineering conclusions of the main investigation done by NIST.
 
ROFL...
[qimg]http://femr2.ucoz.com/_ph/7/975319243.png[/qimg]

See that black circle where the two axes intersect ? T0, with a datapoint marker.

See the next one ? ~0.86s.

My graph shows the datapoint spacing, thus the title...
"NIST Figure 12-76 Datapoint Spacing"
...and the axis labels...
"Separation (s) / Datapoint Pair"

Get a grip man.

You don't accept any responsibility for it, I get that. But the fact is you didn't plot the first datapoint at T=0. NIST does put their first point there in 12-76.

You see? I really do understand. The NIST graph does a better job of presenting the data. But unfortunately I wasn't looking at it, I was looking at your graph.
Oh well...
 
femr2 wants his graphs to remain a mystery. I have been suggesting proper titles and axis labels for a year now. Again, intentionally vagueness as control mechanism.
 
I'll put the matter another way
That's the spirit.

the exact N/S motions are unknown
Agreed.

Determinations are inconclusive contrary to the claims of some
No, I have plenty trace data from other regions. Now that I know the T0 position exactly, I can dig out the Dan Rather trace from that horizontal position and we can confirm the T0 in that location with the Dan Rather footage. I can also trace pixel column 304 on the Cam#3 data, which will also show, not useful as such, but interesting information ;)

added to this the limited resolution of the videos and therefore data derived can only be used as estimations for general purposes.
I think I've adequately shown the level of detail that can be extracted. It's surprisingly high ;)

In my view so long as the measurements fall within a reasonable range of accuracy and are recognized to be inherently inexact, they are useful.
You are entitled to your opinion of course.

Approximate collapse times may vary by 1 second or more, depending on the method of measurement.
They really shouldn't, but if you're happy with that level of accuracy that's your lookout. I prefer such metrics to be as accurate as possible.
 
You don't accept any responsibility for it, I get that. But the fact is you didn't plot the first datapoint at T=0. NIST does put their first point there in 12-76.

You see? I really do understand. The NIST graph does a better job of presenting the data. But unfortunately I wasn't looking at it, I was looking at your graph.
Oh well...
ROFL. You can't read the graph properly is the problem.

I CLEARLY state and label the x axis...Datapoint PAIR.

First point on my graph is for the time between the TWO datapoints, at T=0 and T=0.86

You really don't understand, and it's noones fault but your own.

You seem to think NIST plotted datapoint spacing somewhere. They didn't. "The NIST graph does a better job of presenting the data" ?? ROFL. Totally different graph content and purpose.

:D
 
Last edited:
femr2 wants his graphs to remain a mystery. I have been suggesting proper titles and axis labels for a year now. Again, intentionally vagueness as control mechanism.
:confused: All the graphs are titled and labelled clearly.
 
They really shouldn't, but if you're happy with that level of accuracy that's your lookout. I prefer such metrics to be as accurate as possible.

The level of accuracy is perfectly adequate for the purposes of an engineering report on structural failure.

For physics and video tool geeks, I would understand this would not be so.
 

Back
Top Bottom