Last updated: April 22, 2026

How to Read Oligo Pool QC Metrics

Use this page to interpret a vendor QC sheet or NGS validation report for an oligo pool. It explains what representation, dropout, CV, Gini, fold-range, and error rate mean, plus how threshold decisions shift across CRISPR, NGS panels, mutagenesis, MPRA, and gene assembly work. If you need the source-backed threshold bands behind those calls, start from the QC thresholds by application research page.

NGS flow cells under deep blue and purple lab lighting

Next-Generation Sequencing (NGS) flow cell verification.

How to Read Core QC Metrics

Use these rows as a fast interpretation layer when you open a vendor QC sheet or NGS readout. They are meant to help you triage what looks strong, borderline, or worth escalating, not to replace application-specific thresholds.

MetricWhat It MeasuresFormulaWhat Strong Looks LikeBorderline ReviewEscalate When
Representation% of designed oligos detectedDetected / Designed × 100Most designed oligos are still presentNoticeable attrition but the pool is still broadly recoverableDropout clusters or the application-specific floor is missed
Dropout Rate% of oligos completely absent(Designed - Detected) / DesignedMissing sequences stay rare and scatteredLoss is visible but not yet dominantWhole sequence classes disappear or library bottlenecks become obvious
Uniformity (CV)Read count variationStdDev / Mean of readsRead-count spread stays relatively tightA long tail is forming but does not dominate the poolSevere outliers or a broad tail are likely to distort downstream use
Gini CoefficientDistribution inequalityLorenz curve calculationCounts are fairly even across the poolMeaningful skew is emerging in the read distributionA small subset of oligos is dominating the library
Error RatePer-base synthesis accuracy1 - (Perfect reads / Total)Full-length reads still support the intended assayErrors may be workable only with filtering or clone screeningSequence burden is high enough to undermine the planned use case
Fold-RangeMax/min read count spreadMax reads / Min readsNo extreme max/min outliers are visibleOutliers exist but do not yet define the poolA few sequences swamp the library while others are barely detectable

How QC Priorities Change by Application

The same pooled readout should not be judged with one universal cutoff. This table shows which QC gate usually matters first in each workflow. For published threshold bands and source trails, open the QC thresholds by application research page.

ApplicationPrimary QC GateWhy It DominatesWhen to Escalate into Evidence
CRISPR KO ScreenCoverage and representation through selectionAbundance loss can look like biology when coverage is too thinWhen you need published pooled-screen coverage floors
CRISPRa/i ScreenCoverage plus uniformity across subtle phenotypesSmall effect sizes make bottlenecks harder to spot from summary averages aloneWhen the screen design needs stronger published coverage guidance
NGS Capture PanelPanel balance and on-target performanceUniform presence matters more than one generic pooled-library cutoffWhen assay validation needs to be separated from generic pool QC
DMS / MutagenesisVariant or barcode read depth plus uniformityUnder-sampled variants distort enrichment scores and frequency callsWhen you need published DMS or mutagenesis depth bands
Gene AssemblyPost-correction error burdenSequence accuracy dominates rework cost once constructs get longerWhen the pool is being evaluated for synthesis-error burden rather than screening balance
MPRABarcode complexity with matched DNA and RNA coverageBarcode loss destabilizes activity estimates even when total reads still look highWhen you need published barcode-support filters and QC workflow notes

How to Calculate These Metrics

1

Sequence Your Pool

Perform NGS at required depth. Map reads to designed sequences with bowtie2 or BWA. Count reads per oligo.

2

Calculate Representation

Count oligos with ≥1 read. Divide by total designed oligos. Flag missing sequences for redesign.

3

Calculate Uniformity

Compute CV (StdDev/Mean), Gini coefficient, and fold-range from read count distribution.

Use Uniformity Estimator
4

Assess Error Rate

Align reads to designed sequences. Calculate per-base mismatch, insertion, and deletion rates.

Use Error Rate Calculator

Frequently Asked Questions

What is the Gini coefficient for oligo pools?
The Gini coefficient (0-1) measures how evenly oligos are represented. Lower values mean the pool is more even, while higher values mean a smaller subset of sequences is dominating the reads. Use it as a distribution-shape signal, not a universal pass/fail cutoff that applies equally to vendor QC, CRISPR screens, MPRA, and gene assembly.
What NGS depth do I need to verify my pool?
There is no single universal depth for every oligo pool. Baseline verification often starts with enough reads to see representation and obvious dropout, but application workflows add their own floors for coverage, barcode support, or error burden. Use the QC thresholds by application research page when you need source-backed bands rather than a generic first-pass readout.
How do I calculate oligo pool uniformity?
CV (coefficient of variation) = standard deviation / mean of read counts. Fold-range = max reads / min reads. Gini coefficient measures cumulative distribution inequality. Use all three together — CV for overall spread, Gini for systematic bias, fold-range for outliers.
What error rate is acceptable for oligo pools?
It depends on the application and the construct length. Gene assembly and other sequence-faithful synthesis workflows usually need tighter error control than pooled screening workflows, while barcode-linked assays care about preserving barcode identity and representation. Treat error rate as an application-specific decision, not a single global threshold.

Next Pages to Open