VialSeq

About

Some context on what this is and isn't, so expectations are set honestly from the start.

Who's behind this

This tool is built and maintained by one person — a QC/QA lab technician, not a software company, not a professional development team. It's a spare-time project, worked on around an actual day job, not as anyone's main occupation.

The person behind it stays anonymous here on purpose. What's not anonymous is the authorship of the work itself — see the note at the bottom of this page.

Why it exists

It started as a personal tool to speed up building bracketed injection sequences for Agilent OpenLab CDS by hand, and grew from there into something worth sharing. It isn't affiliated with, endorsed by, or validated by Agilent — see the disclaimer in the tool's own footer for what that means in practice.

Built around one lab's way of working

This isn't a generic tool designed to fit every OpenLab CDS lab out there — it reflects how one specific lab runs its bracketed sequences: its own preparation types, its own batch-number format, its own step-by-step workflow. That's a deliberate trade-off, not an oversight: a tool built for one real way of working tends to actually fit that work well, instead of being a vague compromise that fits nobody precisely.

Some of that is already configurable — preparation types (like TEST/SR/AB) and the batch-number pattern can both be changed inside the tool, in "Preparation types & naming pattern," because not every lab names things the same way. What isn't configurable is the overall shape of the workflow itself (multi-batch bracketing, tray positions, the step-by-step structure) — that part reflects one specific lab's process.

If your lab works differently and this doesn't fit, that doesn't mean something's wrong with it — it means it wasn't built with your case in mind yet. Suggestions for making it fit more workflows are genuinely welcome — see the feedback link below.

What to expect

None of that changes how seriously bugs are taken when they're found — see the tool's own footer for how to review output before relying on it, and the feedback link below for where to send it.