pylabrobot

Lab automation protocols can be written using a vendor-agnostic Python interface that abstracts hardware backends, enabling the same code to control liquid handling, deck resources, and plate readers across different supported robots.

Yes, you can simulate multi-device workflows before hardware execution. The framework provides simulation and visualization backends to validate liquid handling steps, tip tracking, volume tracking, and deck state for reproducibility.

Deck resource and state management allows you to define plates, tips, troughs, and tubes on a hierarchical deck layout. You can serialize and restore deck state, tracking liquids and tips throughout the automated workflow for full reproducibility.

Multi-device workflow coordination is achieved through a unified Python interface that orchestrates liquid handlers with analytical equipment like plate readers, heater shakers, incubators, centrifuges, and pumps for end-to-end assay automation.

No, you do not need specific vendor SDKs. The framework provides a unified Python interface with backend abstraction, allowing you to perform serial dilution, plate replication, and volume tracking without rewriting separate control code for every instrument.

Code needs rewriting because instruments typically use proprietary vendor SDKs. This framework solves that problem by providing a single vendor-agnostic Python interface with backend abstraction, supporting tip and volume tracking across different hardware.