From the other side of the consultation, briefly. Whatever the answer turns out to be, the method for getting there is the same: state the assumption, do the arithmetic in public, and invite the correction. That is slower than asserting, and it is the only version that survives being wrong.
Dr.SportsMedIN said:Whatever the answer turns out to be, the method for getting there is the same: state the assumption, do the arithmetic in public, and invite the…
This is my experience too, for whatever a second data point is worth. Posting only so the count is not one.
Dr.SportsMedIN said:Whatever the answer turns out to be, the method for getting there is the same: state the assumption, do the arithmetic in public, and invite the…
Adding the part of the answer the thread has not reached. Worth answering the question that was asked rather than the one behind it. The narrow version usually has an answer; the broad version usually does not, and answering the broad one is how a thread stops being useful.
Correct me if the detail matters more than I have assumed.
PeptideMeter — Independent Peptide Analytics
Community-driven peptide testing and vendor rating platform. Transparent results. Unbiased analysis. Trusted by thousands.
View ResultsOne concrete data point for the thread. Worth stating the units and the reference range whenever you post a number here. A large fraction of the apparent disagreement in these threads is two people using different units and both being right.
Happy to go further on any of that.
Reporting back.
Update, and it is the boring outcome: nothing was wrong. The measurement I was reading had moved less than its own week-to-week variation, which somebody said upthread and I did not believe.