BTGenZ
Technical showcase

Computational PCR research infrastructure: the platform dashboard

The research workspace is where projects are created, assessed, executed and reviewed. The screenshot below is the dashboard of the platform as it stands, captured from the working system.

Select the image to enlarge it. The dashboard is shown for viewing only.

What the dashboard shows

A workspace organised by analysis

The left menu mirrors the architecture: dashboard and project creation, workflow execution and analysis results, then a dedicated page for each experimental-data module (amplicon sequencing, qPCR, gel, Sanger and digital PCR).

Project records at scale

The summary tiles show 896 project records and 890 completed assays at the time of capture. The recent-projects table lists project ID, name, target gene, organism, assay type and status, with direct links to results and workflow views. Many project names are test runs.

One record per project

Each row is a project that can hold several workflows. Multiplex, conventional PCR and targeted amplicon projects appear side by side with a common status.

Resource awareness

The workspace reports the processor cores available, the worker limit and the current load, so concurrent analyses are managed rather than started blindly.

Selected analytical outputs

Four outputs from the acceptance project show what the modules behind the dashboard produce.

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.
Design. Ranked primer pairs on a synthetic template.
Gel analysis. Ladder calibration used to size every band.
Digital PCR. Four partition clusters separated by thresholds.
Sanger. Trace with base calls and quality.

Why this matters for a client

A computational service is only as dependable as the system behind it. The dashboard, the module structure and the recorded outputs show an infrastructure that handles many projects, keeps each analysis separate and keeps a record of what was run. The architecture page explains how the parts connect and the validation page explains how the system was tested.

Next step

If you would like to discuss a PCR design or data analysis requirement, the collaboration page explains how to start.