vialroom

#test-results 2025-07-26

Saturday15 messages4 participantstimes are UTC
Highlights from this day
  • pbs_pip — sample handling on your end absolutely affects it. draw cleanly, ship fast, do not let it sit warm what interests me is when the gap goes the same direction every… 11:44
  • pbs_pip — i told WXT about a result they would not have liked and they did not argue. credit where it is due 11:57
  • secretagogue_sy — weigh the vial before you reconstitute. it costs nothing and catches the common failure 13:09
PP

sample handling on your end absolutely affects it. draw cleanly, ship fast, do not let it sit warm
what interests me is when the gap goes the same direction every time. once is noise, three times is a pattern

PP

i told WXT about a result they would not have liked and they did not argue. credit where it is due

SS

right so if you are testing to settle an argument you will not settle it with n of 1
my read after three years of this: purity is mostly fine across the market and fill consistency is where suppliers differ

SS

weigh the vial before you reconstitute. it costs nothing and catches the common failure

lot        bought    purity   assay/label
A-2418     2025-03   99.1%    9.6 / 10mg
A-2601     2025-08   98.7%    9.8 / 10mg
B-0114     2026-01   99.3%    9.4 / 10mg
B-0329     2026-04   98.9%    9.9 / 10mg
SS

my read after three years of this: purity is mostly fine across the market and fill consistency is where suppliers differ

PP

98.1 against a certificate of 98.6 is fine. the same supplier landing low four times in a row is a question

SS

a single sample tells you about a single vial. that is genuinely all it tells you

the widest spread in my data is about 2.6 percentage points across five lots from one supplier

RR

underfill is more common than impurity. if you only test purity you are testing the less likely failure

selection bias

the results in this channel skew because people test when they are suspicious. that is selection bias and it is real

RR

i had a result i am fairly sure was a handling error on my side and i logged it as such

thats within range