What you get
A table with one row per sample and one column per marker, a genotype in every cell. Read the calls as alleles (G/C), as A/B, as WT/HET/MUT where all markers have a wild type, or as 0/1/2. Each sample row carries its QC, each marker its control QC, and a quality card sums up the experiment.
A cell without a genotype says why: no call, inconclusive, no amplification, not measured or over range, each with its own shape as well as its color. Behind every column sits the plot the calls came from, with the cut-offs drawn on it, so you can show a reviewer where each boundary lies.
Your cluster plot, with the cut-offs on it
Clarida does not autocall by clustering. Each marker is called against cut-offs you set once and keep in your library, because cut-offs belong to the assay, not to the plate. The price, said plainly: you set them once per marker.
| KASP, TaqMan end point | Both dyes in one well, on the cluster plot: an RFU threshold per allele, or an angle window and a minimum signal |
|---|---|
| TaqMan real time, DMAS | The separation plot of ΔCq: a window between the homozygote bands |
| Melt | The melt peaks: a Tm range per allele, in °C |
| A marker without cut-offs | Plotted, not called, so you can read the boundaries off the plate first |
How it works in Clarida
01In the app: Design › Marker Setup
Each marker says which target reads which allele
A marker is the design of one polymorphic site: its alleles, the target and dye that read each one, and the calling method. Take it from your library, or let Clarida propose markers from the assays you added for you to confirm. Record the genotype each positive control should give.
- Add by: from the library by default; derive from the assays, by hand, or assign targets still waiting for a marker
- Calling method: ΔCq, end point, melting temperature (Tm)
Read the method: Genotyping by allelic discrimination
02In the app: Analyze › Raw data
Cq, end point and melt peaks from the file
When the run file brings its curves, Raw data gives the three readings genotyping uses, plotted from the run’s own data.
- End point: the last cycle by default, one you choose, or the mean over a range
- Melt: Savitzky–Golay smoothing, a cubic spline
In full on the Analyze page
03In the app: Analyze › Genotype calling
Every marker on its plot, the cut-offs you can drag
Clarida calls each marker on its own, and again whenever the data, its setup or a cut-off changes. Step through the markers to see each plot. On the ΔCq and end-point plots you can drag the cut-offs; a marker without any is plotted but not called.
- ΔCq: a window between the homozygote bands, with the allele order you choose
- Tm: a range per allele, in °C
Read the method: Genotyping by allelic discrimination
04In the app: Analyze › Genotyping report
The table, with a quality level per call
The calls come together in one table, with a quality level for each call, sample, marker and the experiment. Save the analysis to keep a read-only record of the calls as they were.
- Show genotypes as: alleles, A/B, WT/HET/MUT, 0/1/2
Read the method: How each quality check works
Why it is done this way
Instrument software usually reports calls by channel: the first allele, the second, heterozygote. If the two dyes were swapped in the setup, every homozygote comes out mirrored and nothing looks wrong. A marker states which target reads which allele, so a positive control with a known genotype can check it. When every such control returns its mirror image, Clarida reports the marker as inverted and leaves the calls for you to fix.
The calling method follows the chemistry. A ΔCq between two allele-specific reactions cancels whatever shifts both equally, input amount included: double-mismatch qPCR (DMAS) relies on it (Lefever et al., 2019). Probe and KASP assays are read at the end point, from the two dyes in one well (Livak, 1999). A melt peak’s temperature depends on the product’s sequence, not its amount.
Clustering finds groups in whatever you ran: on a plate where every sample shares one genotype, it still draws boundaries, and cuts that one population in two. Quality never changes a call either. A flagged call is still a call, and a failing control leaves the genotypes in place and withdraws the evidence for them.
What it doesn’t do
| Calling by clustering | Cut-offs per marker, set once, kept in your library |
|---|---|
| Genotypes in the PDF or HTML report | Not yet |
| Genotype calls in the Excel notebook or RDML | Not yet |
| High-resolution melting (HRM) | Melt peaks in Tm ranges only |
Frequently asked questions
Can you analyze a run already done on your instrument?
Yes. Start from the analysis-only Genotyping preset, import the run file, and set up the markers from its assays.
What if the dyes were swapped?
Clarida reports the marker as inverted when every control with a known genotype comes back mirrored, and leaves the calls for you to fix with one flip of its orientation.
What if you don’t know the cut-offs yet?
Run the plate anyway. Clarida plots every sample for a marker without cut-offs and calls nothing for it, so you can read the boundaries off the plot and enter them.
Can you reuse your markers on the next plate?
Yes. Add a marker to your library with its cut-offs, and take it from there next time.
Can a kit bring its control genotypes?
Yes. A kit can bring its markers with the expected genotype of each control, which Clarida then checks like your own.