BTGenZ
BTGenZ Computational PCR Pipeline

Integrated computational PCR analysis, from assay design to experimental data

A single PCR project rarely stops at one question. It can need new primers, a check of primers already on the shelf, a SNP-specific assay, a multiplex panel and a qPCR assay, and then analysis of sequencing reads, Ct values, gel images, Sanger traces and digital PCR partitions. BTGenZ has built a coordinated computational environment that covers eleven analytical workflows, keeps each one scientifically separate and brings the results together in one project record.

Example output. Cross-dimer screening for a three-target multiplex panel.
11analytical workflows, from primer design to digital PCR
50 of 50input files validated in the acceptance run
11 of 11workflows executed to completion in one project
173recorded output artifacts, each with a SHA-256 checksum
900+development tests reported over about six months

Figures come from the BTGenZ acceptance project and from the project team's development reporting. The test total is a project-level figure and is not an independent experimental validation. See Development & Validation.

The problem this infrastructure addresses

PCR analysis is spread across tools that were never designed to work together. Primer design lives in one program, thermodynamic checks in another, sequencing and qPCR data in vendor exports, and results end up in separate files that someone must reconcile by hand. Each hand-off is a place where a coordinate convention changes, a parameter is retyped or a QC decision is forgotten.

Integrating these steps is valuable only if the scientific reasoning of each step survives. That is the difficult part: a primer design engine, a multiplex optimiser, an amplicon aligner and a digital PCR classifier each rest on different models and different failure modes. The work behind this project was to coordinate them without flattening them. The research challenges page describes how.

Workflows supported

The analytical scope follows the BTGenZ Master Blueprint. Six workflows cover assay design and five cover the analysis of experimental data.

Assay design and evaluation

Experimental-data analysis

How the modules work together

Every project begins with intake: files are identified by content, given a role and checked. A workflow assessment then decides which of the eleven workflows apply, which files each one needs, what depends on what and in what order to run them. Each module runs with its own scientific logic and reports its own scientific QC outcome. A consolidated project summary then brings everything into one report with a checksum manifest.

Individual modules stay usable on their own, so a laboratory can ask for a single analysis such as a Sanger review or a digital PCR quantification without running anything else. The architecture page shows the connections in a diagram.

Evidence you can examine

About the example outputs. Every example output on this site comes from a synthetic acceptance dataset made of software-test fixtures. It does not contain patient samples or experimental biological results, and the figures illustrate what the workflows produce, not biological findings.

Who this work is for

Next step

If you have a PCR design or data analysis requirement, the collaboration page explains what a first conversation covers and what to include.