Skip to content

Compared with R and Python scripts

What a qPCR script of your own asks of the lab

A script wins for methods of your own and long pipelines. Clarida covers the published ones, with the plate and mixes, without code to maintain.

4 in your first month, then 2 a month. No card.

You keepNew methods, the wider pipeline
You addThe plan, the mixes, published methods
On this page

When is your own script the better choice?

Much of qPCR analysis was first published as R and Python code, and the packages are free.

You are developing a new methodNew methods reach R and Python first; qpcR fits and compares amplification curve models
You model many genes in a complex designMCMC.qpcr: Bayesian models over all genes at once, with the controls as priors
Reference genes are one step of your pipelineNormqPCR has geNorm, NormFinder and ΔΔCq; HTqPCR handles high-throughput plates
qPCR sits next to other dataA script runs it unattended beside sequencing, imaging or clinical data
A robot fills your platesA protocol for the Opentrons Python API says what goes into each well; designit and Omixer balance groups over plates
Someone in the lab maintains codeWith git and renv, a well-kept script is as reproducible as analysis gets

Has your script become a job of its own?

  • Only one person can run it. When they go, the analysis leaves with them: turnover was among the difficulties people who write research software named most (Carver 2022).
  • Last year’s script can stop running. Of over 9,000 R files shared with published studies, 74% stopped with an error on a fresh setup (Trisovic 2022).
  • An update moved the numbers. A new major release of one imaging package changed brain volumes by 8.8% on average (Gronenschild 2012), and Bioconductor releases every six months, each tied to one R version.
  • A package you rely on stops. The pcr package, checked against published results when it appeared, was archived on CRAN in November 2025 because reported issues went unfixed.
  • The plan lives somewhere else. The plate map sits in a spreadsheet and the mix recipe on paper, so the script learns the layout only when someone types it again.
  • QA asks which wells were excluded, and why. The answer is a line in someone’s code.

Side by side

What you needR or Python scriptsClarida
Define
Starting the next experiment
Details
Copy and editLast month’s script and sample sheet, changed for the new plateStronger: From a presetYour lab’s settings, steps, assays, mix and cycling protocol at once; the goal and papers noted with it
Design
Plate layout
Details
Randomizeddesignit and Omixer spread sample groups over plates against batch effectsPipetting orderLaid out by your grouping and fill rules in blocks for a multichannel pipette, each automatic rule explained
Execute
Mixes and volumes
Details
Your own codeA few lines per mix; a package for qPCR master mixes is not documented as of October 26, 2026Stronger: Worked outWhat to collect and each mix recipe with its surplus, again whenever the design changes, until the runs are ready
Filling the plate
Details
Robot or paperOpentrons’ Python API drives a pipetting robot; by hand, a printed plate mapGuidedStage by stage on the plate; a note on a well comes back next to its measurement
Import
Raw data in
Details
Parser neededRDML has readers in R and Python; ReadqPCR reads some instrument exports, your own code the restStronger: Run filesCFX, QuantStudio, LightCycler 480 and Rotor-Gene files, RDML, qbase+ and Cq tables, matched to the plate you planned; raw curves kept
Analyze
Published methods
Details
AssembledNormqPCR has geNorm, NormFinder and ΔΔCq; you supply the efficiencies, and its NRQ function is marked experimentalStronger: Built inEfficiency per target from your dilution series, several reference genes, geNorm and NormFinder, a curve fit per well for Cq, error carried to the result
Your own methods
Details
Stronger: AnythingNew methods reach R and Python first; any statistic, any plotSet methodsThe published methods with the settings you choose; no custom code
Part of a pipeline
Details
Stronger: NativeRuns unattended next to sequencing, imaging or clinical dataBy fileRDML and Excel exports, file imports; no public API
Report
A report to hand over
Details
Stronger: Any formatQuarto runs your code inside the document and renders HTML, PDF or WordReport, notebookA PDF or HTML report stamped with the Clarida release; the experiment in your Excel notebook; RDML 1.3 for the runs
Throughout
Who changed what
Details
Code editsGit keeps each change to the script and its author; choices made while running it are not keptDecisions storedSetting changes, automatic exclusions and accepted QC deviations, with who and when
One method for the whole lab
Details
Per copyEach person’s copy can drift, unless the lab keeps one repositoryStronger: SharedNamed settings sets that freeze once used; each experiment keeps its own copy; on a paid plan
The same numbers later
Details
If rebuiltrenv pins packages, not R or system libraries; 74% of shared R files failed to rerunStronger: FrozenA saved analysis never changes, even after an update
When its author leaves
Details
Needs a new ownerPackages too: pcr left CRAN in 2025 when reported issues went unfixedStronger: MaintainedUpdated and tested by Clarida; nobody in your lab has to keep it running

marks the stronger tool for that need.

In short

Stronger in a scriptYour own methods · Part of a pipeline · A report to hand over
Stronger in ClaridaStarting the next experiment · Mixes and volumes · Raw data in · Published methods · One method for the whole lab · The same numbers later · When its author leaves
A drawPlate layout · Filling the plate · Who changed what

How do you check it against your script?

  • Start from a plate your script has already analyzed. Import its run file, or the Cq table the script read.
  • Export RDML and read it back in R. The RDML package returns the Cq values and raw curves, well by well.
  • Compare per well, then per sample. Cq, then efficiency, then the normalized quantity: a difference shows at the earliest step where the methods part.

Can you keep your script beside it?

Plan in ClaridaThe run layout, the mixes and the bench notes, before your script takes over
Hand the run to your scriptRDML 1.3 with the Cq values and raw curves, for the RDML package in R or rdmlpython in Python, which Clarida’s per-well efficiencies are tested against
Read the Excel exportEach step in its own section with every intermediate value, ready for readxl or pandas (Excel notebook)
Bring your script’s Cq to ClaridaA Cq table as Excel, CSV or text, its columns mapped with you before anything is saved
What does not carry overRDML holds no analysis settings; the Excel export names what it started from

Frequently asked questions

Isn’t a script more reproducible than any app?

For the code, yes: git and renv record exactly what ran. They don’t pin R itself or the system libraries, as renv says, so rerunning years later can mean rebuilding an environment first. A saved analysis in Clarida keeps its data, settings and results together and never changes, even after an update. A saved report carries the Clarida release and a hash of its input data. An analysis kept without one does not name the version yet.

Can a script plan the plate as well?

Yes, and it can balance it. designit and Omixer spread treatment groups and other factors over plates, which matters in a large study where each one can act as a batch. Clarida does not randomize: it lays out the plate by grouping and fill rules for a multichannel pipette, then works out the mixes and guides you at the bench. Need both? Randomize in a script, then set Clarida’s run layout to manual and place the wells as the script assigned them.

Does a script you wrote need validating?

In regulated work, yes. OECD guidance for GLP counts statistical applications and data evaluation tools built for one facility as customized systems, which “bear the highest intrinsic risk”, and asks for a validation process and for the source code to be kept as long as the study records (OECD No. 17). Clarida needs validating as well, for the way your lab uses it, though nobody there maintains its code.

What happens to your data if you stop using Clarida?

It stays yours, in open formats. RDML holds the raw curves, the Cq values and the plate, and the Excel workbook every result, with the settings it started from, so a script can take over where Clarida stopped.

What does Clarida cost next to free packages?

Nothing, to start. The packages are free, and so is a first try. Clarida’s free plan: 4 experiments in your first month, then 2 a month. No card.

Sources

Each source with the day we last checked it. Something out of date? Tell us.

Checked

Leave whenever you like, with the raw curves.

Analyze a plate, then export it as RDML 1.3 with its Cq values and raw curves, ready for the RDML package in R. 4 experiments in your first month, then 2 a month. No card.

Other comparisons

All comparisons
  • Spreadsheets

    You keep
    Your own formulas, Prism for figures
    You add
    Plate, mixes and analysis, linked
  • Instrument software

    You keep
    The run, the protocol, signed records
    You add
    The plan, and runs from four makers
  • Dedicated qPCR software

    You keep
    GenEx for PCA and replicate planning
    You add
    Plate layout and mixes, from your lists
  • ELN or LIMS

    You keep
    Samples, signatures, the release
    You add
    qPCR methods your team doesn’t code
  • Benchling

    You keep
    The record, stock and sign-off
    You add
    The qPCR layout, mixes and method