Where a run goes after the cycler
In a self-service core, your staff train the users, who then book the instrument and run their own plates, and the analysis happens back in the group: in the maker's software on the shared PC, or in someone's spreadsheet. The run file leaves on a stick or by email, because the workstation is not an archive: "Data could be deleted anytime (older first) without warning" (CEITEC Genomics Core Facility). It keeps a busy core lean, and for most bookings it is the right split.
What it costs shows up later, out of your sight. Of 253 European cores surveyed, 72% had no system to identify the raw data behind a published figure, and 10% of self-service facilities had a way to check how users analyzed their results (Kos-Braun et al., 2020). When a PI questions a number, the core still gets the email.
| Today | With Clarida |
|---|---|
| Users carry run files off the workstation on a stick, or by email | Pair the instrument PC once with Porta, and each group requests its runs from its own folder |
| A different maker’s analysis software for each cycler on the shared PC | One analysis in the browser, for files from CFX, LightCycler 480, QuantStudio, Rotor-Gene or RDML |
| A study booked over four plates and three weeks | Inter-run calibration ties the plates together, with QC of its own |
| A PI questions a number, and the analysis lives on a student’s laptop | The experiment sits in the group’s workspace: who saved each version, each exclusion and its note, and the settings set it began from |
Each instrument with its maker’s program? When is your cycler’s software enough?
The questions that end up at the core
Most of what reaches you is one of four questions. In Clarida each has an answer you can open, without becoming the analyst for every group.
- Where is my run? In the group’s experiment, once someone requested it from the shared folder. Its curves and Cq values were imported there, so clearing the workstation loses none of them (Import).
- Can another group see our data? No. A workspace opens to its members only, and on a shared instrument each group sees its own folders, never where they sit on the PC (how Porta keeps them apart).
- How was this number made? The History tab shows who saved each version and when. Every exclusion shows whether a person or a rule made it, with any note typed for it, and the experiment keeps the settings set it started from (Analyze).
- Who took which run? Your workspace keeps a record of every request to the instrument PC: which file, who asked and when, including those from the groups you share it with.
Start from the cyclers and groups you serve
- Every cycler’s run file. CFX, LightCycler 480, QuantStudio, Rotor-Gene or RDML, raw curves included, or a Cq table. The instrument’s Cq stays beside the one Clarida calls from the curves (importing instrument data).
- Groups already on Clarida. Each group keeps its own workspace, and you share its folder with it from your PC.
- New users every semester. Each new group workspace opens with demo experiments and Clarida’s starter presets, and its owners can pin the ones they recommend. Every section of the app carries its own help.
- qbase+ archives. A group’s old analyses come across free, read-only, and do not count as experiments.
For your director
What a director, the institute and purchasing ask for before a facility account is opened.
| What it costs | Per experiment, for the whole account, never per user. A facility account, with a workspace per group, is priced with you around your volume; the plans for a single lab are on pricing. |
|---|---|
| Cost recovery | An experiment is a unit you can pass on per booking. Clarida does not count experiments per group for you yet; each workspace lists its own. |
| Where the data lives | In the EU. The app runs in Amsterdam and the database in Stockholm, with all traffic over HTTPS. |
| Who sees a group’s data | The members of its workspace. The account holder joins each new workspace; that group’s owners can remove them, except from the last one. |
| Signing in | With Google, Microsoft or a link by email. Institutional single sign-on is not built in yet; it is set up on request for a facility account. |
| When someone leaves | Their experiments stay in the group’s workspace; only their access ends. |
| Getting data out | Any experiment as RDML, an Excel workbook or its report. |
| If the facility stops paying | Experiments stay viewable and exportable, but no new ones can be created. |
| Who built it | The people behind qbase+, which VIB licensed for over 1,000 of its researchers in 2013 (Technology Networks). Jan Hellemans led the qBase paper and Jo Vandesompele the geNorm one, and both co-authored the MIQE guidelines (meet them). |
| Not yet | A usage count per group, a read-only role, one settings set shared across all workspaces, and dPCR. |
Frequently asked questions
Do you end up analyzing every group’s data?
No. Each group analyzes in its own workspace. You join one when its owner or an admin invites you, to look at an analysis together.
Can each group keep its own reference genes and settings?
Yes. A settings set belongs to one workspace, so each group’s choices stay its own. A facility’s set cannot yet be handed to every group: each workspace starts from Clarida’s defaults and builds its own.
Can you try it before the director signs?
Yes. The free plan is for one person, so bring a run from one of your cyclers. Workspaces for your groups come with a facility account, which we set up with you.
What happens when the account’s experiments run out?
Every group can still open, analyze and export what it has. New experiments wait until the next period starts.
Does it handle dPCR?
Not yet. Clarida analyzes qPCR and RT-qPCR today.