Closed jsouter closed 1 month ago
Should we make the enum use the string names for each value, instead of int? Like with https://github.com/bluesky/ophyd-async/blob/1559aa0e451ffc93da46f5a0fdc7cf282def7fab/src/ophyd_async/epics/adcore/_core_io.py#L71
Should we make the enum use the string names for each value, instead of int? Like with
Would require a small change to the IOC but that would probably be nicer
Should we make the enum use the string names for each value, instead of int? Like with https://github.com/bluesky/ophyd-async/blob/1559aa0e451ffc93da46f5a0fdc7cf282def7fab/src/ophyd_async/epics/adcore/_core_io.py#L71
Would require a small change to the IOC but that would probably be nicer
I think everything's already in place on the pandablocks-ioc and ophyd async epics backend for this.
Okay, just tested against the lab panda, running a camonitor on the CAPTURE_MODE PV shows it gets set to FOREVER when HDFPanda.writer.open() is awaited.
Addresses https://github.com/bluesky/ophyd-async/issues/471
Implemented CaptureMode as an int enum to match what's in PandABlocks-ioc