pylabrobot

Write liquid handling protocols using a backend-agnostic API by creating a LiquidHandler instance with your chosen backend. This abstracts vendor-specific commands, allowing the same protocol code to run on Hamilton STAR, Opentrons OT-2, or simulation backends.

Yes, you can simulate lab automation protocols before hardware runs. The Skill provides visualization and simulation components that validate pipetting and incubation steps, which also supports education and CI testing.

Backend-agnostic lab automation uses a unified API to control multiple hardware backends. You need it to reduce integration complexity when developing cross-vendor research workflows or protocols that must execute on different robotic platforms.

Yes, this approach supports tracking deck layouts and resource states. It includes robust resource and deck management for tracking wells, tips, and layouts, plus state serialization to maintain accurate laboratory configurations.

A limitation of using a unified API for cross-backend laboratory automation is that it requires a backend-agnostic API and resource models. Complex or highly vendor-specific hardware features may not be fully abstracted across Hamilton STAR, OT-2, and simulation backends.

To start automating pipetting and incubation workflows, install the library and create a LiquidHandler configured with a STAR, OT-2, or simulation backend. You can then begin writing backend-agnostic protocol code immediately.