Skip to main content
Operate covers running the physical lab — the equipment your data comes from, what is on it right now, and what you want run next. It sits upstream of Data: Operate is where a test is requested and executed, and Data is where the resulting measurement is uploaded, read, and analysed.

Equipment

Model your lab as sites, cyclers, and channels, and link each measurement to the channel it ran on.

Lab view

A project-scoped dashboard of channel occupancy — what is running, and when a channel frees up.

Channel service

Take a channel out of service with a reason and read its incident history.

Planned measurements

Request a test, schedule it onto a channel, and link the real run back to the plan.

AI protocol authoring

Describe a test in plain English on the request form and get back a validated UCP protocol.

​
Where to start

If you are setting the lab up for the first time, build the equipment tree first — everything else keys off channels. Once channels exist, the Lab view becomes useful, and the test scheduler can place requests onto real hardware. Recording equipment is optional. Measurements work fine without a channel_id, so if you have a single cycler you can skip Operate entirely and use the free-text test_setup fields instead.