Validation
For each omics pipeline we run a published reference dataset end-to-end and report what was recovered versus what was expected. This is the technical evidence behind the case studies — same code paths, public data, verifiable results.
For real client deliverables in plain English, see /case-studies.
GSE308859 — 4 timepoints (Sham, TAC 2w/4w/6w), ~27,200 cells, 10x Chromium
Public RNA-seq dataset, dexamethasone vs DMSO in A549 cells (canonical glucocorticoid response benchmark)
ATAC-seq across melanoma cell lines, ~20 samples
LFQ-Analyst tumour-vs-benign liver-tissue example, 10 patient-paired Benign/Malignant samples, LFQ-DDA MaxQuant
PXD010697 — Brüning 2019, sleep-deprivation synaptosomes, 48 LFQ-DDA samples across 6 timepoints
Genome-in-a-Bottle (GIAB) v4.2.1 NA12878 truth set, chromosome 22 (49,964 PASS variants)
Each validation run takes a publicly-available dataset where the expected biological signal is already published, processes it through the production OmicsDesk pipeline unmodified, and reports what was recovered. A pipeline that can recover canonical signals on public data is the same pipeline that will be run on your data — the code path is identical.