August 28

Developer Meetings
3

meeting notes:

  • V1 Architecture V1b1 branch merged
    • device specific classes, using shared code behind the device-specific interface
  • introduced device managers: people responsible for maintaining specific device drivers. hopefully vendors in the future.
  • Chory Lab cookbook highlight: The PyLabRobot Cookbook

@CamilloMoschner: slides

  • is refactoring the Hamilton Star driver to handle advanced tracking and low-level commands.
  • developed a 3D visualization engine using three.js with glb model support. it looks sick
  • proposed standardizing device coordinate frames to the front-left bottom (fixing origin. PLR already fixed the axes / unit vectors.)

@claudio:

  • recent contributions including high-res centrifuges, the Agilent Echo, and the Agilent BenchCel.
  • Test new drivers: Claudio to test the incoming PF 3400 and refrigerated Hettich SBS centrifuge.

@j0nch: slides

  • Event Bus and Manual Operator: Introduced a resource-aware event bus for semantic tracking and a manual operator feature to handle human or custom non-PLR actions as structured protocol steps.

@kelsorjsf

The discussion regarding MHS (Model Hardware Standard):

  • Context: the standard was announced recently, and participants identified it as an “exciting hardware scenario” similar to MCP, aimed at making it easier to connect various instruments to agents, particularly for high-mix, low-volume execution.
  • Rick emphasized that MHS is not competing with PyLabRobot. Instead, MHS serves as a connector between agents and instruments, while PyLabRobot acts as the implementation framework that allows code to actually run on those instruments. MHS actually uses PyLabRobot already for various integrations. It might compete with SILA.
  • Camos noted that the MHS announcement video featured a “suspiciously high” number of PyLabRobot-supported devices, which Rick attributed to the fact that PyLabRobot provides accessible APIs that allow for development and hacking on these systems.
5 Likes