search

bluesky / ophyd-async

Hardware abstraction for bluesky written using asyncio
https://blueskyproject.io/ophyd-async
BSD 3-Clause "New" or "Revised" License
11 stars 25 forks source link

Eiger FastCS: Use PVI information to fill in PVs #551

Open coretl opened 2 months ago

coretl commented 2 months ago 
          As soon as PVI datastructures are published over PVA then this file will drastically change to something like:
class EigerDriverIO(Device):
    bit_depth: SignalR[int]
    stale_parameters: SignalR[bool]
    ...

It will also only need to include the signals that are needed at static analysis time, at runtime then all the extras (like beam_centre_x, etc) will be filled in automatically.

This will also mean that the class structure and ophyd attribute names will have to exactly match those in PVI.

For this reason I suggest we do this soon, and @GDYendell is going to start looking at this now

_Originally posted by @coretl in https://github.com/bluesky/ophyd-async/pull/528#discussion_r1723187325_

DominicOram commented 1 month ago

Following https://github.com/bluesky/ophyd-async/issues/557#issuecomment-2357802049 I think we can now do this.