For qPCR core facilities: hand over the run file, free up the analysis PC

A core runs several instruments from different vendors, and every user wants to come back and look at their data. The analysis PCs become a second queue behind the instruments.

Cores can end the analysis queue by giving users the original run file and a tool that opens it anywhere. CycleView opens QuantStudio .eds, LightCycler .ixo and .lc96p, Rotor-Gene .rex and RDML on Mac and Windows, so one app covers a mixed instrument park. Users open and inspect runs with the free viewer; those who analyse need Pro, and a Lab plan gives five seats with shared analysis templates. Files are processed on the user's own computer, so the core does not host or transmit anyone's data.

The second queue in every core

Instrument time is booked and managed. Analysis time usually is not. Users come back to the instrument PC to re-export, to look at a curve, or to reanalyse with a different threshold, and each visit blocks the next run's setup. Staff field the same question repeatedly: how do I open this file on my laptop?

One handover, any instrument

A workflow that scales:

  1. After the run, staff copy the original run file to the user's project folder, alongside any CSV the user asked for.
  2. Users open it in CycleView on their own computer, Mac or Windows, whatever the instrument brand.
  3. Users who need analysis get Pro, or join their group's Lab plan.

Because the same app reads QuantStudio, LightCycler and Rotor-Gene files, users who move between instruments learn one interface, and staff write one help page instead of three.

Bio-Rad and other formats

Bio-Rad .pcrd files are encrypted, so CycleView does not open them. For CFX instruments, export RDML from CFX Maestro as part of the handover. RDML is the open qPCR data format, and CycleView reads and writes it. Any instrument whose software exports RDML can be handled the same way.

Nothing passes through the core's servers

CycleView is a desktop app. It does not upload files, so the core is not running a data service, storing users' results, or answering questions about where data goes. The file goes from the instrument folder to the user, and analysis happens on the user's machine.

Consistent analysis across users

On the Lab plan, a group can share analysis templates per assay: reference genes, calibrator, threshold approach. A core that supports a standard assay can suggest settings, and users apply them the same way each time instead of improvising per run.

One app for every user's run files

QuantStudio, LightCycler, Rotor-Gene and RDML on Mac and Windows. Free to open, processed locally.

FAQ

Does the core need to install anything on the instrument PCs?

No. CycleView runs on users' own computers and reads the files the instrument software already writes.

Can users open runs without paying?

Yes. The free viewer opens every supported file with curves, plate map and the instrument's Cq values. Analysis and export are in Pro.

Which instruments are covered?

QuantStudio (.eds), LightCycler 480 (.ixo), LightCycler 96 (.lc96p), Rotor-Gene Q (.rex), and any instrument that exports RDML.

Is it suitable for a clinical core?

No. CycleView is for research use, not for diagnosis, and is not a medical device.

qPCR guides