method development — 10 things I got wrong before I got it right
method development — 10 things I got wrong before I got it right. Change my mind, genuinely — I have no stake in being right about this.
Bought a second-hand instrument and learned more in six months of fixing it than in three years of reading traces.
Sent the same vial to PeptideMeter and VendorInvestigate. 99.2% against a claimed 98.5%. The difference was the gradient, not the material.
Ran a blank after a high-concentration injection and found the carryover I had been calling an impurity.
Tell me where this is wrong. That is the useful part of posting it.
best — the order this archive was captured in
System suitability — repeat injections, tailing factor, plate count, RSD on area — is what tells you the instrument was fit for the measurement that day. Without it, the purity figure is unanchored.
Cosigning the wavelength point. Half the disagreements in this board are two people looking at different detectors.
system suitability before you believe any number on the run
Agreed. Two analysts, one trace, two integration choices, and a spread that has nothing to do with the vial.
a blank injection between samples costs four minutes and settles most arguments
That figure cannot be quoted to two decimals off that baseline. The precision is not in the data.
Yes. Retention time is a hypothesis about identity. Mass is the answer.
Agreed, and it is why HJ printing the column and gradient on the certificate is genuinely useful rather than decorative.
two labs, two gradients, two honest answers
What did system suitability look like on that sequence?
This. A shoulder that does not baseline-resolve is a question, not a quantity.
Gave the same trace to two people I trust and got two integrations about a point apart. That was the most educational afternoon I have had here.
report the method or do not report the number
Right. And a blank between injections settles the carryover argument before it starts.
Is that baseline drawn by the software or by hand?
A shoulder that does not baseline-resolve cannot be quantified honestly. You can report it as an unresolved shoulder, which is useful information, or you can develop the method until it resolves.
Chased a ghost peak for three weeks. It was the plumbing. It is always the plumbing.
Do you have the mass, or only the UV trace?
area percent is relative to what the detector saw and nothing else
a shoulder is not an impurity until you can resolve it
Started reporting my own integrations with the baseline choice stated. Arguments in my threads dropped by about half.
Correction: that is a tailing factor, not a plate count. Different diagnostics for different problems.
LC-MS for identity, UV for relative quantity
Carryover from a previous high-concentration injection looks exactly like a small impurity. The blank injection is four minutes and it removes the ambiguity entirely.
reproducibility beats resolution if you only get one of them
reproducibility beats resolution if you only get one of them
quiet_reader_99 is right — the integration choice is a decision and it should be stated alongside the result.
ghost peak, check the plumbing first, it is always the plumbing
Can you post the trace with the axes labelled?
- 1That figure cannot be quoted to two decimals off that baseline. The…9 comments in this branch · started by u/camila_lindqvist
- 2Right. And a blank between injections settles the carryover argument before…7 comments in this branch · started by u/kofi_ferreira