OpenMHS family: micromanager

Micro-Manager through pymmcore-plus (helper:pymmcore-plus, planned)

Generated by MHS/registry/build_registry.py on 2026-10-20T00:00:00Z from 47 registry records and their task cards. A plan, not a conformance claim.

• bridge_status: planned (blocked_on: helper:pymmcore-plus)
• helper: none
• exemplar: none

Launch

Every driver package starts the same way; per-repo configuration (environment id, model path, port, baud rate, VISA resource) lives in the package's driver.py, never in launch flags:

mhs serve <driver-dir>

A package is done when python3 -m mhs.driver check <driver-dir> --backend fake exits 0 (evidence contract_checked; a fake never yields an MHS-Device level).

Registry coverage

• Repos: 47
• Decisions: bridge-runtime 6, reference 18, skip 23
• Waves: 9: 47
• Dispatchable now: 0
• Modes: hardware 6, simulated 5

Applicability

snapImage maps to cap.imaging.capture.v1, the Z stage to cap.imaging.focus.v1, illumination to cap.imaging.illumination.v1, other properties to cap.device.configure.v1; the demo configuration is the fake.

Capability mapping

The mapping is fixed when the helper lands; the applicability section lists its rules.

Class ids come from python3 -m mhs.driver catalog search <words>. The deprecated classes cap.device.describe.v1, cap.world.state.v1, cap.world.snapshot.v1 and cap.world.restore.v1 are replaced by the protocol methods mhs.devices.get, mhs.resource.read, mhs.snapshot and mhs.restore.

Safety

The risk floor of a device is the highest catalogue risk_class of its classes (CAP-017); a driver may declare a higher risk, never a lower one. Hardware at R1 or above needs an @estop and a non-empty safe state. Stages can collide; lasers can be dangerous and photobleach samples.

Fidelity

Bridge only; the fidelity belongs to the service, simulator or hardware behind it.

Pitfalls

Properties are untyped strings; configurations are hardware-specific.

First task cards

• gh.micro-manager/pycro-manager: bridge-runtime, wave 9, rank 36, MHS/registry/tasks/labs/micro-manager__pycro-manager.json
• gh.pymmcore-plus/pymmcore-plus: bridge-runtime, wave 9, rank 48, MHS/registry/tasks/labs/pymmcore-plus__pymmcore-plus.json
• gh.micro-manager/pymmcore: bridge-runtime, wave 9, rank 54, MHS/registry/tasks/labs/micro-manager__pymmcore.json
• gh.pymmcore-plus/pymmcore-nano: bridge-runtime, wave 9, rank 73, MHS/registry/tasks/labs/pymmcore-plus__pymmcore-nano.json
• gh.pymmcore-plus/napari-micromanager: skip, wave 9, rank 407, MHS/registry/tasks/labs/pymmcore-plus__napari-micromanager.json

Sources

• Task cards: MHS/registry/tasks/<track>/<owner>__<repo>.json (schema/taskcard.schema.json).
• Triage rules and the helper table: MHS/registry/triage.py; curated decisions: MHS/registry/overrides/.
• Driver API and gate: MHS/sdk/docs/driver-authoring.md; exemplars: MHS/drivers/.