I've too often run into arguments that looked convincing and were dismounted later. I am careful with such things now.I "guess" you are not going to choose to justify why you consider mine only "probably" more accurate ?
You could have said "definitely" more accurate, whilst still complaining about error threshhold, yet you have chosen not to.
Recklessness doesn't gain respect, nor credibility. I am more careful and therefore I also consider the possibility that your analysis is wrong.It doesn't gain respect, nor credibility.
Why are you introducing the topic of implications in this thread? And I'm the one accused of gish-gallop?The fact is, that your assertion of "chaotic and unpredictable" has two primary implications. One you'll "like", the other you won't.
I'll commit the "gish-gallop" of answering, though.
The NIST simulations are not worthless, but they are chaotic. They offer a starting point. NIST had no data of core damage to work with; they couldn't do any analysis without it. They had two options: find a plausible starting point to see where it led, or not do the analysis. Along the way, they matched the data to the observables where possible. The final result matches their observations, so theirs was as good a starting point as many others.1) If even 0.00001 degree of error renders the subsequent simulation "chaotic and unpredictable", then the NIST simulations are completely worthless chaotic and random number generators, especially if you consider that the scale of error of one impact parameter (of several that are wrong) is around nine hundred thousand times larger than your offered "threshold".
But the errors in column location, non-uniformity of column density, weld resistance, and so many other factors, cause that performing a simulation to determine the damage to give results basically guaranteed to differ from real life results. Even two real life impacts with the very same conditions to within my example error above would produce different results.
By the way, the threshold you're confident with in your analysis is also a hundred thousand times bigger than my example error!!!1!11!eleventy!
Ah, switchback to a separate "argument". Canter![]()
What separate "argument"?I do hope you're not going to try and foist a manual by hand lens correction upon anyone.
Wait until I provide it and judge then. But out of curiosity, what would be wrong with that?I do hope you're not going to try and foist a manual by hand lens correction upon anyone.
I'll wait until you provide it and judge thenBut out of curiosity, what would be wrong with that?![]()
So you won't tell me what's wrong with that approach?I'll wait until you provide it and judge then![]()
Why would you ask ?So you won't tell me what's wrong with that approach?
Why don't you answer? That paper hints that it could be done:
When determining the lens parameters, all programs rely on the same paradigm: the ideal perspective mapping should map real world straight lines to straight lines in the image. So if a set of points P0, P1, ..., Pn is known to lie on a straight line, their images p0, p1, ..., pn should also fall onto a straight line [...]
But rectification of lines is not the method I've used, anyway.
I've provided you with a full paper about correcting lens distortion. What extra information do you need now ?!Why don't you answer?
My question was: "out of curiosity, what would be wrong with that [= a manual by hand lens correction]?"I've provided you with a full paper about correcting lens distortion. What extra information do you need now ?!
Ah, switchback to a separate "argument". CanterMy question was: "out of curiosity, what would be wrong with that [= a manual by hand lens correction]?"![]()

Compare the highlighted sentences.
Yes, I learned that there are better open source software packages for lens correction than the one I have been using, and I intend to repeat my adjustment with them.And did you learn nothing from the document supplied and my numerous other responses ?
Wrong. If I can determine the error, I can account for it in the final result. Introducing a known amount of error is much better than not knowing what error you have at all.Short answer...inaccurate. Lens parameters are given to 6dp for a reason. If you can't achieve accurate correction you might as well not bother.
Yes, and I'm sure you read this sentence?I'm sure you're aware that lens distortion varies between barrel, complex and pincushion types as zoom level is changed ?
- The final FOV is similar to the FOV in the collapse view, therefore the lens distortion is similar too.
Seems you haven't understood. I'm only using two frames, pre-zoom and post-zoom. I assume negligible lens distortion in the center of the image for the not zoomed view, and adjust the distortion of the zoomed view to match the magnified view. That will take me much closer to the actual lens distortion than without any correction at all. I can determine a plausible error from there, which will be substantially reduced with respect to not applying lens correction at all.How were you planning on separating change in perspective distortion during zooming at the same time ?
I plan to perform no lens correction, and instead determine an error band resulting of that omission. ETA: Unless I can find another zooming video similar to the one for Cam #3. But I suspect it won't be so close to the center if that's the case, which will ruin it.How are you planning on performing lens correction upon the Dan Rather footage, as you're planning on using both... ?
Last edited:
THAT statement will make MT's brain explode.
