# Genotyping by allelic discrimination

> How to turn an allelic-discrimination run into a sample-by-marker genotype table, and how Clarida makes each call: method, cut-offs and controls.

Source: https://clarida.bio/methods/genotyping-allelic-discrimination
Updated: 2026-10-30

[Methods](https://clarida.bio/methods)

How to turn an allelic-discrimination run into a sample-by-marker genotype table, and how Clarida makes each call: method, cut-offs and controls.

By [Jan Hellemans](https://clarida.bio/methods/genotyping-allelic-discrimination#about-the-authors)

September 19, 2026 Updated October 30, 2026 20 min read

A genotyping run looks, to an instrument, like any other qPCR run. Wells amplify, dyes fluoresce, Cq values come out. What turns those numbers into genotypes is the assay design: which dye, in which well, reports which allele. Clarida asks you to declare that design once, as a **marker**, and calls the genotypes from it. It calls per marker, never per dye or channel: without a marker, there is nothing to call.

**How to** covers the way from plate to genotype table, step by step; **How it works** explains the reasoning behind each step, for when a step raises a question. Both follow one example: *HBB* rs16911905, a diploid SNP with two alleles, `G` and `C`, typed on a 96-well plate.

## How to

### 1. Start from the Genotyping preset

On the qPCR page, start the experiment from the **Genotyping** preset. Its layout shows the sections genotyping needs and leaves out Cq processing, Exploration and Statistics. If the plate has already run and you start from the run file, choose **Genotyping – analysis only** instead: it skips Design and Execute.

### 2. Add your markers

Clarida only calls genotypes for markers; there is no generic calling by dye. Markers are built from the assays' targets and dyes, so add the assays in **Assay Prep** first. Then open **Marker Setup** and pick an **Input method**:

- **Derive from assays** turns the assays you select into markers. Choose the **Method** (a wand marks the one Clarida suggests) and, where there is a choice, **How targets become markers**. Clarida shows the proposed markers for confirmation before it adds anything.
- **From library** adds markers you saved earlier, or that came with a kit.
- **Manual** builds one marker at a time: name, method, and an allele row per allele with its target.
- **Assign pending targets** lists the targets no marker binds yet, with their count, so each can join one.

Then check the **Marker list**. Every allele needs a real name: a **Name alleles** badge marks positional names such as "Allele 1". The **Alleles** view shows which target reads which allele; for the example marker, `G` is read by one target and `C` by the other.

![The Marker setup section. An Input method card offers From library, Manual, Derive from assays and Assign pending targets. Below it, the Marker list shows three ΔCq markers, HBB rs16911905, HBB rs11036364 and OCA2 rs4778241, each with its rsID, ploidy 2, its two alleles with their dyes, and a ΔCq window in the Calling column. An Expected control genotypes block says there are no positive controls on this plate yet](https://clarida.bio/images/methods/genotyping-marker-setup.png)

Figure 1: Marker Setup with three markers derived from the assays. The Calling column shows each marker's ΔCq window.

For a ΔCq marker, the ⇄ arrow in the **Calling** cell sets which allele sits at the low end of the axis. For an end-point marker, the same cell sets whether it is **Called in** X–Y or polar space.

See [Why Clarida needs a marker](https://clarida.bio/methods/genotyping-allelic-discrimination#why-clarida-needs-a-marker), [The marker](https://clarida.bio/methods/genotyping-allelic-discrimination#the-marker) and [Choosing a calling method](https://clarida.bio/methods/genotyping-allelic-discrimination#choosing-a-calling-method).

### 3. Enter the cut-offs

A marker is only called once it has cut-offs. Enter them in the **Calling** cell of the Marker list: a ΔCq window on the marker row, and a Tm range or an RFU threshold per allele in the **Alleles** view. End-point markers have optional quality values in the **QC** cell.

Cut-offs you don't know yet can wait. Clarida does not call a marker without one, but still plots its data, so you can read the cut-off off the plate in step 5.

See [Where cut-offs come from](https://clarida.bio/methods/genotyping-allelic-discrimination#where-cut-offs-come-from) and [Why a marker needs a cut-off](https://clarida.bio/methods/genotyping-allelic-discrimination#why-a-marker-without-a-cut-off-is-not-called).

### 4. Set your controls' expected genotypes

Under **Expected control genotypes** in Marker Setup, pick the expected genotype of each positive control for each marker. A control with a known genotype is what catches a plate where the alleles were swapped. A positive control saved in the Library can carry its expected genotypes, so you set them once.

See [Detecting a mirrored plate](https://clarida.bio/methods/genotyping-allelic-discrimination#detecting-a-mirrored-plate).

### 5. Check the calls

Import the run under **Import & annotate**. **Genotype calling** then calls every marker on its own, and calls again whenever the data, a marker or a cut-off changes. Step through the markers with ‹ › and check, for each one:

- **Quality control** reads **Pass**, **Attention** or **Fail**. Its **Controls** line says whether the marker's controls passed, and its **Calls** line counts clean and flagged calls. Click a count, such as "flagged", to filter the table to those samples; the **Call QC** column marks each one.
- **The plot** (Separation for ΔCq, Melt peaks for Tm, Clusters for end point) shows whether the genotypes separate cleanly within the cut-offs.
- **Not called: missing cut-off** at the top means the marker has no cut-off yet. Read the cut-off off the plot and enter it in the **Settings** card.
- **This marker's alleles look inverted** means every known-genotype control came back as its mirror image. In Marker Setup, check the allele order (ΔCq), the ranges (Tm) or the target bindings (end point).

![The Genotype calling section for marker HBB rs16911905, the first of three. The Marker card reads ΔCq, 2 alleles, ΔCq = Cq(G) − Cq(C), no normalizer. The Settings card holds the cut-offs −1.50 and 2.00 between the GG, GC and CC bands. The Quality control card reads Attention: controls incomplete, 4 clean calls, 3 flagged, 13 not measured. Below, a separation plot shows three G/C samples near zero, one G/G sample at −4.2 and three one-sided samples in lanes at the edges, beside a table of each sample's ΔCq, call and call QC](https://clarida.bio/images/methods/genotyping-genotype-calling.png)

Figure 2: Genotype calling, one marker at a time. Quality control sits top right; the plot and the table show the same calls.

A value typed in the Settings card is saved on the experiment's marker. On a marker from the Library or a kit, whose design is locked, it applies to this analysis only.

See [Calling by ΔCq](https://clarida.bio/methods/genotyping-allelic-discrimination#calling-by-%CE%B4cq), [Calling by melting temperature](https://clarida.bio/methods/genotyping-allelic-discrimination#calling-by-melting-temperature), [Calling by end-point fluorescence](https://clarida.bio/methods/genotyping-allelic-discrimination#calling-by-end-point-fluorescence) and [Quality sits beside the call](https://clarida.bio/methods/genotyping-allelic-discrimination#quality-sits-beside-the-call).

### 6. Read the genotype table

**Genotyping report** shows the samples × markers table, with each sample's **Sample QC** and each marker's **Control QC**. Its **Quality control** card sums them up for the whole experiment. **Show genotypes as** switches between alleles (`G/C`), A/B and numeric (0/1/2), and offers WT/HET/MUT once every marker declares a wild type. A column badge marks a marker that was **Not called**, one where **All no call** came back, and one whose controls failed (**QC**). **Save analysis** keeps a read-only record of the calls.

![The Genotyping report section. Under an empty list of saved analyses, three cards read 60 cells called (20 samples × 3 markers, 40 not measured), Quality control Attention, and 20 of 20 genotyped. Below, the samples × markers table lists each sample with its sample QC, how many of its markers were genotyped, and a genotype per marker column, with each marker's control QC in a second header row](https://clarida.bio/images/methods/genotyping-report.png)

Figure 3: The genotype table: one row per sample, one column per marker.

See [Cells without a genotype](https://clarida.bio/methods/genotyping-allelic-discrimination#cells-without-a-genotype).

### 7. Keep your markers for next time

Use **Add to library** in the Marker list to save a marker, with its cut-offs, to your Library. The next experiment adds it with **From library**.

### Setting up TaqMan, KASP, melt and DMAS

- **TaqMan biallelic SNP:** two allele components in two dyes on one assay, method **ΔCq**. The running example.
- **KASP or TaqMan end-point read:** the same two components, method **End point**. Start in X–Y with a threshold per allele; switch to polar when low-input heterozygotes fall below one allele's threshold, and set the θ window from where the clusters sit.
- **Melt-based SNP assay:** two allele components, possibly on one target, method **Tm**, with a Tm range per allele. A heterozygote shows two peaks.
- **DMAS-qPCR:** two allele-specific primer sets in the same dye, in two wells. Method **ΔCq**; the marker spans both assays, and a **2 assays** badge marks it.
- **Detection panel:** four targets for four organisms are not alleles. Four allele-specific targets at one locus are one marker with four alleles; Clarida cannot tell the two apart, so derivation shows every proposed grouping for you to confirm.

## How it works

### Why Clarida needs a marker

Instrument software genotypes by channel. It reads the two dyes in each well and reports the call by position: `Allele 1`, `Allele 2` or `Heterozygote` on a Bio-Rad CFX, `Allele 1/Allele 2` in Thermo's software, `Allele X` or `Both Alleles` on a Roche LightCycler. The label names a position, not an allele.

Clarida calls per marker, for three reasons:

- **The dye does not always identify the allele.** In a DMAS or ARMS assay both alleles are read in the same dye, in different wells. Channel order carries no information there.
- **A stated binding can be checked.** A swap of allele 1 and allele 2 leaves every well amplifying and reports every homozygote as the other one. A control with a known genotype catches it against the marker (see [Detecting a mirrored plate](https://clarida.bio/methods/genotyping-allelic-discrimination#detecting-a-mirrored-plate)).
- **A call should mean the same thing everywhere.** A result in allele terms (`G/C`) can be compared across runs and plates, reported, and checked against expected genotypes. `Allele 1/Allele 2` means something only next to the plate it came from.

A marker is that stated binding. The minimum is small: which target reads which allele, and the calling method. Locus, rsID and wild type are optional, and **Derive from assays** proposes markers from the assays in one step. Where a target name does not say which allele it reads, the alleles arrive as "Allele 1" and "Allele 2" and a **Name alleles** badge asks you to name them.

### The marker

A marker is the genotyping design for one polymorphic site. It carries three things:

- **Alleles** are the reportable outcomes. The example marker has two, `G` and `C`. A deletion marker has two named `+` and `−`; a star-allele marker may have several. A genotype is a multiset of alleles, so a heterozygote is `G/C` and a homozygote `G/G`.
- **Components** are what gets measured. Each component binds to one target on one assay and reads one allele.
- **Method and cut-offs** are how the reading is taken (ΔCq, end point or melting temperature) and the thresholds that turn it into a genotype.

A marker refers to targets; it does not own them, and deleting a marker leaves its targets in place.

### The locus

A marker's **locus** says where on the genome it sits. Clarida stores it as four fields that compose into one coordinate, here rs16911905's on GRCh38:

```
locus_reference   type   position   ref_allele
NC_000011.10   :   g.   5228060       G
```

- **Reference sequence:** an accession with its version, since positions and reference bases move between assembly versions.
- **Sequence type:** the HGVS prefix saying how to read the position (`g.` genomic, `c.` coding DNA). A RefSeq accession gives it away: `NC_` is genomic, `NM_` coding DNA.
- **Position** on that sequence.
- **Reference allele** at that position. Each allele's variant detail supplies the change, so the locus plus `>C` is the variant (`NC_000011.10:g.5228060G>C`).

Strand follows from the reference sequence, so two independent designs for the same rsID compare as plain strings. Allele nucleotides are stored in reference orientation.

A partial locus is a complete answer. A gene symbol, an in-house build id or `chr7` on its own is a locus, and a copy-number or presence/absence marker has a locus and no position: `CYP2D6*5` is a whole-gene deletion, and its locus is the gene.

Where a reference allele is recorded, the **wild-type allele follows from it**: it is the allele whose variant detail matches the reference base, and Clarida offers it for confirmation. Star alleles, allele groups and presence/absence markers declare their wild type directly.

### Grouped and star alleles

An allele can be a single nucleotide change. Two shapes carry more:

- A **grouped allele** is one the assay reports as a unit. An allele named `LoF` stands for several loss-of-function variants that the chemistry reads together.
- A **star allele** is a haplotype. `NAT2*5B` is defined by `c.341T>C` + `c.481C>T` + `c.803A>G` in combination.

For both, `covers` lists the variants the group stands for, as rs IDs or HGVS descriptions. The call reports the group itself: `*1/LoF` states what the assay measured. Resolving `LoF` into one of its members would claim more than the measurement supports.

### Choosing a calling method

The method is a property of the marker and names the physical readout the genotype is taken from:

| Method | What is measured | Typical chemistry | Calling cut-off |
| --- | --- | --- | --- |
| **ΔCq** | The Cq difference between two allele-specific components | Allele-specific real-time PCR in one well (two dyes) or two (DMAS, ARMS) | A ΔCq window per allele pair |
| **Tm** | The melting temperature of each melt peak | Assays whose allele products melt at different temperatures | A Tm range per allele |
| **End point** | End-point fluorescence of each allele's dye, read in one well | A FAM/HEX duplex such as KASP or TaqMan allelic discrimination | An RFU threshold per allele, or a θ window and a minimum R |

Choose the method from the assay, not from the data. A ΔCq cancels anything that shifts both components equally, input amount included. A melt peak's temperature depends on the product's sequence, not on how much of it formed. End-point fluorescence needs no Cq, which is how KASP and TaqMan genotyping assays are designed to be read.

### Calling by ΔCq

For the ΔCq method, described in [Lefever et al. 2019](https://pubmed.ncbi.nlm.nih.gov/30770838/), a genotype is read from the difference between the two allele components. For the example marker it reads:

$$
\Delta Cq = Cq_{G} - Cq_{C}
$$

A `G/G` sample amplifies early on the `G` component and late, or not at all, on `C`, giving a large ΔCq of one sign. A `C/C` sample gives a large ΔCq of the other sign. A `G/C` heterozygote amplifies on both at roughly equal efficiency, giving a ΔCq near zero. The three genotypes occupy three separable regions of one axis, and the cut-offs decide where the boundaries lie.

Because it is a difference, the ΔCq needs no standard curve: anything that shifts both components equally, such as input amount, pipetting volume or plate position, cancels.

![The separation plot for HBB rs16911905. The ΔCq axis is divided by the cut-offs at −1.5 and 2 into a GG band below, a GC band between and a CC band above. Three heterozygotes sit near zero in the GC band, one G/G sample at −4.2 in the GG band, and three samples with one silent allele sit in lanes at the edges: one below the axis, marked −∞, and two above it, marked +∞](https://clarida.bio/images/methods/genotyping-dcq-plot.png)

Figure 4: ΔCq calling for rs16911905. Each band is labeled with the genotype it calls; samples with one silent allele sit in lanes at the edges.

**Orientation.** The order of subtraction decides the sign. Clarida stores it as a property of the marker. A new marker puts the **wild-type allele first** where one is declared, and otherwise keeps the order its alleles were declared in; the ⇄ arrow flips it. Flipping the orientation turns the axis over without changing any genotype. The cut-off window turns over with it: `−1.50 < ΔCq < 2.00` becomes `−2.00 < ΔCq < 1.50`, the same window seen from the other side, and a value set for one analysis turns over too. Calls already made are recalculated by themselves: each ΔCq changes sign, and every sample keeps its genotype.

**The bands carry the allele they call.** Two designs of the same variant can produce mirrored axes carrying identical information, so Clarida labels each band with the allele it calls. Reading the label gives the genotype on any design; reading the sign gives it on one.

**A one-sided ΔCq is a bound.** When one component stayed silent, the difference is only known to be at least, or at most, some value. A bound settles a homozygote: a sample that amplified strongly on `G` and not at all on `C` is the cleanest `G/G` there is. A heterozygote needs both sides. Clarida calls on a bound where the bound decides the genotype and shows these samples in their own lanes beside the axis, since they have no finite value to plot.

### Calling by melting temperature

A Tm marker carries one **acceptance range per allele**, in °C, and the ranges may not overlap. An allele is present in a well when one of the well's melt peaks falls inside its range, and the genotype is the set of alleles present: one allele gives a homozygote, both a heterozygote. This is peak matching; it does not model curve shape, which is the domain of high-resolution melting.

![Genotype calling for a HybProbe Tm marker with alleles G and A. The Settings card holds a range per allele: G 61.0 to 66.5 °C, expected 64.0, and A 51.0 to 56.0 °C, expected 53.5. The melt peak plot shows each sample's peaks as points, with the G range shaded at the top and the A range at the bottom; heterozygotes have a peak in both, joined by a line. The table lists each sample's peaks in °C and its call](https://clarida.bio/images/methods/genotyping-tm.png)

Figure 5: Tm calling: an allele is present when a melt peak falls inside its range. Heterozygotes show a peak in both.

Replicates combine per allele. When the wells disagree on which alleles are present, the cell is **inconclusive**, since the disagreement changes the genotype.

Three cases have their own outcome:

- **A peak outside every range** leaves the genotype as the in-range peaks define it, and flags the call: a primer dimer, an unexpected variant under the probe, or a range drawn too narrowly all look like this.
- **Amplification without a melt peak** is a **no call**. The sample is not silent, but the melt gives nothing to call from.
- **No amplification and no peak** is **no amplification**.

### Calling by end-point fluorescence

Suppose rs16911905 is typed as a single-well end-point duplex instead, FAM reporting `G` and HEX reporting `C`. Each well yields two numbers, one per allele, read after the final cycle. Clarida uses the experiment's end-point values, whether imported from the instrument or calculated from the amplification curves, and calls in one of two spaces:

- **X–Y space (the default): a threshold per allele.** An allele is present when its end-point fluorescence reaches its RFU threshold. The two thresholds divide the plot into four quadrants: `G/G` (FAM only), `C/C` (HEX only), `G/C` (both) and no amplification (neither).
- **Polar space: a θ window and a minimum R.** The two numbers, `x` for the first allele and `y` for the second, become an angle and a total. A well whose R is below the **minimum R** is reported as no amplification. Otherwise θ below the **θ window** calls the first allele's homozygote, θ inside it (edges included) the heterozygote, and θ above it the second allele's homozygote.

$$
\theta = \frac{2}{\pi}\arctan\left(\frac{y}{x}\right), \qquad R = x + y
$$

θ runs from 0 (the first allele only) to 1 (the second allele only); R is the total end-point signal. Replicate wells that call different genotypes make the cell inconclusive. `R = x + y` is a fair measure of total signal in a competitive single-well duplex, where both allele-specific probes share one template, so the total stays roughly the same whichever genotype the sample carries.

![Genotype calling for HBB rs16911905 as an end-point marker, called in X–Y space. The Settings card sets an RFU threshold per allele: G 700 and C 500. The cluster plot shows G fluorescence against C fluorescence, divided by the two thresholds into quadrants: C/C samples top left, G/C heterozygotes on a diagonal in the middle, G/G samples bottom right, and no amplification near the origin. The table lists each sample's G and C RFU, θ, R and call](https://clarida.bio/images/methods/genotyping-endpoint-xy.png)

Figure 6: End point in X–Y space: one RFU threshold per allele, and the two thresholds divide the plot into four quadrants.

**Why polar calling exists.** θ is a ratio, so it does not move with the amount of template. A low-input heterozygote slides toward the origin along its own ray. Per-allele RFU thresholds can let the weaker of its two signals drop below threshold and read it as a homozygote; a θ window keeps it a heterozygote, and the minimum R decides separately whether there was enough signal to call at all. That is why end-point genotyping software can call by angle, as LGC's Kraken does when it links points by [Nearest Angle](https://results.lgcgenomics.com/software/kraken_manual/frames/f=scoring_calls.htm). X–Y thresholds remain the default because they are easier to set and explain on a panel of many markers and few samples.

![Genotype calling for HBB rs11036364 as an end-point marker, called in polar space. The Settings card sets a θ window from 0.20 to 0.60 and a minimum R of 2000 RFU. The plot shows θ against R: G/G samples at θ near 0.05, G/A heterozygotes near 0.37 and A/A samples near 0.84, all above the minimum R line at 2000, with the no-template control below it. The table lists each sample's RFU per allele, θ, R and call](https://clarida.bio/images/methods/genotyping-endpoint-polar.png)

Figure 7: End point in polar space: a θ window separates the three genotypes, and a minimum R decides whether there was enough signal to call.

**Set the θ window from the data.** θ is not corrected for dye balance: when FAM runs brighter than HEX, the heterozygote cluster sits below 0.5, and a window centered on 0.5 would measure dye balance rather than genotype. An end-point marker that is not called yet still plots every sample's θ and R, so you can read the window off the plate before you set it.

**The view is not the rule.** The cluster plot switches freely between X–Y and polar, and switching never changes a call. The plot opens in the space that calls, and the calling rule is drawn in both views.

End-point calling reads both alleles in the same well and calls with the cut-offs or windows you set: Clarida does not call designs that read the alleles in separate wells, does not call by clustering, and does not normalize θ per channel.

### Where cut-offs come from

A reading becomes a genotype once you say which ranges mean which genotype. Those ranges are the marker's **cut-offs**, and they describe the assay design: a well-designed allelic-discrimination assay gives the same separation on every plate it runs on.

A cut-off comes from one of two places:

1. **A value set for this analysis**, which overrides the marker's own value. The marker itself is untouched, and resetting brings its value back.
2. **The marker's own value**, whether the marker belongs to this experiment or comes from the Library. A kit's markers are copied into the experiment, carrying the kit's values.

The Settings card in Genotype calling shows which of the two supplied the cut-off in force.

### Why a marker needs a cut-off

When no cut-off resolves for a marker, Clarida does not call it: the marker produces no calls, and the screen gives the reason. The Genotyping report marks its column **Not called**.

The alternative would be to derive boundaries from the plate by clustering the samples. But clustering describes the sample set: on a plate where every sample shares one genotype, it finds boundaries anyway and splits one real group in two. The result would read as an ordinary genotype table while its boundaries belonged to the plate, not the assay. A marker that is not called states the gap instead, and fixing it takes one step.

Genotype calling gives one of two reasons, with different remedies:

- **Not called: missing cut-off:** supply a cut-off and the marker is called.
- **Not called: marker shape not supported:** the marker's shape is outside what the engine handles, such as three alleles against a two-allele method.

This applies to one marker. Its neighbors on the same plate are called normally.

### Detecting a mirrored plate

A failed reaction gives no signal, a contaminated no-template control amplifies, inhibition shifts Cq values: these show in the data.

A **swapped allele-to-target binding** is silent. If the example marker's `G` component is bound to the `C` target and vice versa, every well amplifies normally, every quality metric passes, and every homozygote in the table is mirrored: `G/G` samples report as `C/C`. Heterozygotes are their own mirror image, so they report correctly.

**A sample whose genotype you already know detects it.** Record an expected genotype for a reference material, per marker, and Clarida compares. The failure is systematic, so the signature is unambiguous: *every* known-genotype control returns its own mirror image. Clarida reports that as one finding and leaves the calls as they are; correcting the marker is your decision.

Two other controls answer different questions:

- **A no-template control** that stays silent shows the reaction is clean. It carries no genotype, so it says nothing about orientation.
- **A heterozygote-only control set** verifies that both components work. Heterozygotes mirror onto themselves, so orientation stays unverified, and Clarida passes the marker and says so.

### Quality sits beside the call

Clarida answers two questions separately:

1. **What genotype does the data support?** The call.
2. **How far should you trust it?** The quality verdict.

Quality never changes a call. A flagged call **has been called**, and the flag says how heavily to lean on it. A failing control leaves the genotypes in place and withdraws the evidence for them.

The second question is answered at two separate levels, because a weak call and a failed control are different problems:

- **Call QC** judges one call: one sample at one marker. It is **Clean**, **Flagged** or **n/a**. A call is flagged when its replicates disagree, or when one of its call-level checks failed: a signal below the detection cut-off, an end-point signal below the signal floor or radial floor, or a melt peak outside every Tm range. A cell without a genotype (no call, no amplification, not measured) is n/a: it is counted on its own, never as a QC failure.
- **Control QC** judges one marker's controls. It is **Pass**, **Incomplete** or **Fail**. It fails when a known-genotype control disagrees with its expected genotype, a no-template control amplifies, or, for end point, a genotype cluster is wider than the angular cluster width. It is incomplete when there is no genotype control or no-template control to evaluate, an expected genotype is unresolved, or an allele was not exercised by any control. A marker that is not called is incomplete, never failed: a missing cut-off is not a control disagreement.

These two combine into a verdict for the marker, and the report rolls them up further. Each level takes the worst of what it is built from, by fixed rules:

- **Marker QC**, the headline of the Quality control card in Genotype calling: **Fail** when Control QC fails, **Attention** when Control QC is incomplete or any call is flagged, **Pass** otherwise. The card's Controls line shows Control QC; its Calls line counts the marker's calls, such as `18 clean · 2 flagged · 1 no call`.
- **Sample QC**, a column in the Genotyping report: **Flagged** when any of that sample's calls is flagged.
- **Control QC** again, in the report's marker header row. The report shows Control QC there rather than Marker QC, so a flagged call is counted once, in its sample's row.
- **Experiment QC**, the report's Quality control card: **Fail** when any marker's Control QC fails, **Attention** when any Control QC is incomplete or any sample is flagged, **Pass** otherwise.

A control's own result, agreeing with its expected genotype or not, shows on the control sample's icon. A failing control affects its own marker's Control QC and no other sample's Sample QC.

**A check you have not switched on is not part of QC.** Several checks only run once you set their threshold: the detection cut-off, and the end-point values below. Until then the check is **off**: it is listed under **Checks** with the setting that would switch it on, and it never makes a call flagged or a marker incomplete. A check that is switched on but could not run is listed as **not assessed**, with its reason.

**End point has its own quality values.** It has no Cq, so four values judge how far to trust an end-point call. None of them changes a call:

| Value | Unit | What it does |
| --- | --- | --- |
| **Radial floor** | Fraction of the full radius | A call below it is flagged (Call QC). |
| **Signal floor** | RFU, per allele | A call is flagged (Call QC) when its signal stays below the floor: the marker's control component where it has one, else its strongest allele. |
| **NTC radial ceiling** | Fraction of the full radius | A no-template control above it fails Control QC. |
| **Angular cluster width** | Degrees | A genotype cluster spread wider than this fails Control QC. Only clusters of 3 or more samples are judged. |

The **full radius** is the largest R among the marker's unknown samples, so the data define it, not the plot; no-template controls never set it. A value left empty switches its check off. These values live on the marker, apart from its cut-offs, can be overridden for one analysis, and apply in both calling spaces.

### Cells without a genotype

The finished table is samples × markers, one genotype per cell. Four outcomes describe a cell without a genotype, and each points somewhere different:

| Outcome | Meaning | Where to look |
| --- | --- | --- |
| **No call** | Called, and the value landed in no band | The marker: its cut-offs, its separation |
| **Inconclusive** | Replicates disagree, and the readings imply different genotypes | The wells, and the NTC |
| **No amplification** | Measured, and affirmatively nothing | The sample |
| **Not measured** | Nothing to call from: the well was never measured, or every replicate was excluded | The plate layout |

Each outcome has its own shape as well as its own color, so the table reads in grayscale and for color-blind readers.

A **Not called** column and an **All no call** column look alike and have different remedies. In the first, the marker was never called, and hovering its badge says why: a missing cut-off, which you supply, or a marker shape the engine does not support. In the second, it was called normally and separated nothing: look at the assay.

## About the author

- Jan Hellemans

  Co-founder, Clarida

  Leads the science and the methods at Clarida. Published the qBase method in 2007 and co-authored the MIQE guidelines.

  [Google Scholar](https://scholar.google.com/citations?user=L8EeDgwAAAAJ)

## Your last allelic-discrimination plate, called one marker at a time.

A plate that has already run starts from the analysis-only Genotyping preset.

[Start free](https://app.clarida.bio/login) · [Talk to a founder](https://clarida.bio/talk-to-us?topic=demo)
