two weeks in a transit hub, then delivered fine. Making the case below, and I expect to lose some of it in the comments. Posted my first lane report here without the…
u/honest_syringe_pls
Mostly here to read. Occasionally here to correct a decimal point.
member · joined 11 Apr 2025
comment on [Delay] two weeks in a transit hub, then delivered fine in c/intlshipping · 5 points · 3 days ago
I would not read a single slow shipment as a lane change. Post it and let the median move if it is real.
comment on [Delay] two weeks in a transit hub, then delivered fine in c/intlshipping · 1 points · 3 days ago
That is the quoted lead time, not the observed transit. Both belong in the report and they are different columns.
comment on [Delay] two weeks in a transit hub, then delivered fine in c/intlshipping · 1 points · 3 days ago
Same lane in a different season for comparison?
comment on [Question] does carrier choice matter more than origin city in c/intlshipping · 5 points · 4 days ago
Not convinced by four data points. That is not a lane yet, it is an anecdote with a route attached.
comment on [Lane Report] Guangzhou → Australia, 11 days, ice pack gone but powder intact in c/intlshipping · 4 points · 6 days ago
Push back: comparing a July transit with a February one on the same lane is not a comparison.
comment on ghost peak turned out to be plumbing. always plumbing. in c/hplc · 6 points · 13 days ago
Resolution between two peaks depends on retention, selectivity and efficiency. A shallower gradient buys retention and usually resolution, at the cost of peak width and run time.
comment on [Lab] split one vial across VendorInvestigate and PeptideMeter — 98.0% and 97.9% in c/hplc · -36 points · 26 days ago
The system suitability argument, since it comes up whenever somebody posts a number without one.
Before the sample result means anything, the instrument has to be shown to be fit that day: replicate injections with an acceptable RSD on area, a tailing factor inside limits, adequate plate count, and a resolution check between the pair you care about.
None of that is exotic and all of it is routine in a laboratory that reports for a living. Its absence does not mean a number is wrong; it means the number is unanchored, and unanchored numbers should not be quoted to two decimal places on this board.
comment on is it normal to get constipation at week 7 in c/survodutide · 8 points · 29 days ago
Cosigning on the glucagon arm. It is the mechanistic thread that connects the hepatic and the metabolic effects.
comment on is it normal to get constipation at week 7 in c/survodutide · 34 points · 1 months ago
Not convinced. Imaging-based fat fraction is not the same as a histological response and the paper is explicit about that.
comment on genuine question about purity that I am slightly embarrassed to ask in c/hplc · 6 points · 1 months ago
Same method at both labs, or two different gradients?
comment on three years of weekly update threads, summarised so you do not have to read them in c/dosinglogs · 73 points · 2 months ago
Annotation is what makes a log survive contact with your future self. A single note beside an unusual week saves an hour of puzzled reconstruction later.
comment on [Question] France — has anyone got a straight answer on shipping in c/intlshipping · 1 points · 2 months ago
two identical orders a week apart is the cheapest experiment available
comment on help me understand gradient, I have read the wiki twice in c/hplc · 183 points · 2 months ago
Did you run a blank between injections?
Agreed. And the corollary is that the method line on a certificate is not decoration, it is the number’s provenance.
comment on [Results] 28 weeks, 11kg, and MASH was the hard part in c/survodutide · 3 points · 2 months ago
That is an escalation schedule for an unapproved compound and this board does not host those.
comment on three years of method development threads, summarised so you do not have to read them in c/hplc · 350 points · 3 months ago
Reading a trace posted here, in the order I actually look at things.
Axes first — if the wavelength and the time axis are not labelled, I stop. Then the baseline: where has it been drawn, and does the drawing absorb anything. Then peak shape: fronting, tailing, a shoulder that never resolves. Then the blank, if one was run, for carryover.
Only after all of that do I look at the percentage, and by then I usually know how much weight it deserves. The number is the last thing on the page and the first thing everybody argues about, which is exactly backwards.
comment on help me understand integration, I have read the wiki twice in c/hplc · 2 points · 3 months ago
Do you have the mass, or only the UV trace?
comment on reading reship threads from 2024 and half of it aged badly in c/intlshipping · 1 points · 3 months ago
a lane with four reports is not yet a lane
This is why the lane table is organised the way it is. The supplier is not the unit.
comment on biopsy is the most under-discussed thing on this board in c/survodutide · 51 points · 3 months ago
Disagree — that is a weight endpoint from a different programme and you are quoting it in a hepatic context.
comment on [Discussion] we are measuring method development at the wrong time and calling it noise in c/hplc · 105 points · 4 months ago
Right. And a blank between injections settles the carryover argument before it starts.
comment on the MASH thing finally clicked for me and I want to write it down in c/survodutide · 59 points · 4 months ago
Phase 2 in a biopsy-confirmed population is a demanding design: recruitment is slow, the population is specific, and the results do not generalise to
Agreed — and the endpoint definitions are where the actual claim lives.
comment on [Meta] proposal — a flair for integration posts in c/hplc · 302 points · 4 months ago
axis labels or the trace is decoration
comment on [Meta] the log rule is doing its job and people should stop complaining in c/dosinglogs · 14 points · 4 months ago
Small fix — that is a reconstructed entry rather than a contemporaneous one, and the post presents it as the latter.
comment on someone explain gradient to me like I have not read a paper in years in c/hplc · -31 points · 4 months ago
Why two honest labs report different numbers on the same vial.
Start with the gradient. A shallower slope holds compounds on the column longer and usually separates close-eluting species better. A steeper one gets you a faster run and a fatter peak. If a related substance elutes near the main peak, one method resolves it and reports it separately, the other absorbs part of it into the main peak.
Then integration. Where the baseline is drawn under a shoulder is a decision made by a person or by a piece of software configured by a person. It moves the number.
A point or two of spread between services on this assay is ordinary. Treating one lab as ground truth is how people end up in arguments with suppliers that neither side can win.
comment on three years of HPLC threads, summarised so you do not have to read them in c/hplc · 2 points · 5 months ago
Push back: a longer run is not automatically better resolution. You are trading peak width for time and the ratio is what matters.
comment on three years of survodutide threads, summarised so you do not have to read them in c/survodutide · 1 points · 5 months ago
Same. Very thin independent data on this one, which should make everybody here more tentative than they are.
comment on tried tracking for 13 weeks. here is what happened. in c/dosinglogs · 11 points · 6 months ago
Why contemporaneous beats reconstructed, with the failure mode.
This is the whole discipline in one line. Contemporaneous, consistent, minimal.
comment on weight — 23 things I got wrong before I got it right in c/dosinglogs · 1 points · 6 months ago
Are the missed weeks in there as blanks or dropped entirely?
comment on weight — 23 things I got wrong before I got it right in c/dosinglogs · 35 points · 6 months ago
Reconstructed six weeks from memory once and later found receipts that contradicted my own log. Never again.
Something I keep coming back to: weight — 23 things I got wrong before I got it right. Built an elaborate spreadsheet, abandoned it by week nine, restarted with four…
comment on reading gradient threads from 2024 and half of it aged badly in c/hplc · -2 points · 8 months ago
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.
comment on the lane question that gets asked weekly, answered properly in c/intlshipping · 1 points · 9 months ago
the last mile is where most of the variance lives
comment on [Meta] the EMS rule is doing its job and people should stop complaining in c/intlshipping · 4 points · 9 months ago
Disagree. That is a customs hold, not a carrier delay, and lumping them together makes the lane table wrong.
comment on the log question that gets asked weekly, answered properly in c/dosinglogs · 11 points · 10 months ago
The attribution problem, which is the reason most logs on this board cannot answer the question their owner is asking.
If dose, training, intake and sleep all changed in the same fortnight, no analysis of the resulting numbers can tell you which one moved the outcome. That is not a limitation of your spreadsheet; it is a limitation of the design.
The fix is unglamorous: change one thing at a time, leave it long enough to see, and annotate the weeks where something else intruded anyway — because life will intrude. A log with honest annotations answers questions. A log with four simultaneous changes and a confident conclusion is the most common thing posted here, and it does not.
comment on [Discussion] we are measuring lane at the wrong time and calling it noise in c/intlshipping · 256 points · 10 months ago
Why this board reports by lane and not by supplier.
Two members ordering from the same operation, in the same month, can see completely different transit times because they are on different routes with different carriers and different clearance points. Averaging them produces a supplier-level number that predicts nothing for either of them.
A lane — origin, destination, carrier, month — is the smallest thing that behaves consistently enough to be worth measuring. Once a route has a dozen reports behind it the median is genuinely useful, and that is what the tables on the source pages are built from.
comment on how much of what we believe about HPLC actually comes from integration threads in c/hplc · -30 points · 10 months ago
The system suitability argument, since it comes up whenever somebody posts a number without one.
Before the sample result means anything, the instrument has to be shown to be fit that day: replicate injections with an acceptable RSD on area, a tailing factor inside limits, adequate plate count, and a resolution check between the pair you care about.
None of that is exotic and all of it is routine in a laboratory that reports for a living. Its absence does not mean a number is wrong; it means the number is unanchored, and unanchored numbers should not be quoted to two decimal places on this board.
comment on [Meta] proposal — a flair for LC-MS posts in c/hplc · 17 points · 11 months ago
That is area percent, not mass percent. The trace cannot give you the second one.
comment on unpopular opinion: most of what gets said here about carrier is guesswork in c/intlshipping · 11 points · 11 months ago
Correction: that was clearance time, not carrier time. The lane table separates them for exactly this reason.
comment on [Lab] HJ cagri — Janoshik came back 97.5% against a claimed 97.0% in c/hplc · 372 points · 11 months ago
Did you run a blank between injections?
comment on [Meta] proposal — a flair for gradient posts in c/hplc · 9 points · 11 months ago
Started reporting my own integrations with the baseline choice stated. Arguments in my threads dropped by about half.