The trace data really is as good as it's possible to extract from the video.
Which doesn't qualify it as "good enough".
Correction: I should have added "necessarily" to that sentence: 'which doesn't necessarily qualify it as "good enough"'.
Both WDC and pgimeno are complaining about your methods by alleging errors. With no indication of what range of errors are significant. Nor to whom they could be significant nor the purpose those persons would have for using the data...etc etc...
I am raising objections challenging his alleged results (his interpretation of the data). What I expect is for him to address the objections. He says there is early motion minutes before release but as far as my recollection goes (I admit to my bad memory), he has not presented his case of early motion convincingly yet. I just recall the bare assertions and the graphs.
...all the "is it good enough" questions without addressing "Good enough for Who?" and "For what purpose?"
In the sentence at the beginning of my post, good enough to give credibility to his claims.
For the sake of comparison, we're in a similar case to that of Jones et al. claiming the iron spheres are the result of a thermite reaction with the iron oxide particles, but having enough iron oxide visible in their micrograhps as to challenge that conclusion.
We even have claims that you, femr, are wrong on 'near "G" ' which do not even address the issue that NIST and Chandler were apparently correct with their claims for similar accelerations.
For the record, I have never said that femr is wrong on 'near "G"' [sic]. I really hope you don't mean that I implied this. In other occasions you have referred to distorted versions of what I said without naming me, and since it was not what I said, I didn't feel alluded. But if I am right and you imply here that I said that, I must say that those distortions are lawyer tricks that don't seek to find the truth but to win a case, which would destroy all your credibility here, at least for me.
It almost always has the form of you stating something that you say other posters have said, just like here, without naming anyone in particular, and it turns out that when you make such claims, I don't remember haven't seen that in the recent post history, even if I have said something that has some similarity. That would qualify as lying by innuendo, and it's devastating to credibility.
In this particular case, I don't remember anyone recently making the claim that femr2 is wrong on "near g acceleration". However I have said something similar recently, in post 2625, where you said:
c) That there was no period of "over 'G'"? and I replied:
a) and c) have a certain degree of support, in that the noise level may ruin that assessment. Which is not similar to "denying" "near g acceleration" on two acounts: first I am not denying, but implying it may be right or wrong and neither outcome can be reliably concluded, and second it doesn't apply to near g, but to over g.
I've seen a similar pattern of subtle distortions of words I've said or similar innuendo, for example, in threads related to Bazant, in which I didn't feel alluded, but now that I see a recurring pattern, I'm starting to think it's purposeful lawyertalk techniques.
And if you are resorting to such dishonest tactics in order to "win" your case, you're shredding your credibility, and even more on the account that you've criticized a similar attitude on other posters. Between straightening the record at every such innuendo and just not believing you, I'd opt for the latter, and probably other posters might do the same.
That said, your best defense would be to present an instance of a claim matching this assertion of yours:
We even have claims that you, femr, are wrong on 'near "G" ' at which point I will immediately apologize.
And back to the topic, as for NIST, I don't think their margin of error really proves their acceleration profile, but that doesn't matter, as their discussion focuses on splitting the fall into stages, one of which consists of the connections breaking and giving way, and that's enough to explain the visual record. Which serves as a definition of what is "good enough" when applied to NIST's analysis.
The "only read the last post" problem.
If you mean me, not nearly. I read each and every post of the threads I follow, and take good precautions to do so, including for example scrolling up right after posting to check if I missed something that was posted while I was writing. Right now I've noticed femr2 has posted while I was writing this and will read his posts later (I need to go now).
I've admitted that I seemed to remember that femr2 said the movement happed minutes before, but wasn't sure because of my memory. Which is not the same as not having read it as you imply.
BUT please resist the temptation to leave that key issue dragging whilst you go down side tracks...answer these?
...Good enough for who???
...Who are they???
...what is their need???
femr2 has shown results and I am claiming that these results don't necessarily follow from his data.
So:
... good enough to prove femr2's analysis,
... "they" is femr2,
... he needs more effort in presenting his case in a way that excludes the sources of error we have identified.