Tom C (DLS)
Tom C (DLS)
@tacaswell I can see this being used in `bps.rd` and `bps.movr`, but is a user ever likely to use this? If so then I think dataclass is preferable, but if...
I'm erring on the side of 2 then. @tacaswell how strong is your preference for 3?
Also, what does "YOLO" mean?
I'm guessing https://github.com/bluesky/ophyd/pull/1036 might have something to do with it? @callumforrester do you recognise the error?
4th point of https://github.com/bluesky/bluesky/issues/1517 suggests we talked about `setpoint` (where we asked it to go) and `position` (where it actually is). I can't remember whether that was settled though...
Although I also found https://github.com/bluesky/bluesky/pull/1502#issuecomment-1111175618 which suggests `setpoint` and `readback`
I've made a new issue #1535 to track the creation of a protocol that would support this. Please put comments for the name of the protocol and its methods there
@ksunden @untzag @tacaswell
> Protocols cannot be instantiated, and I'm not sure how that works for their children Immediate subclasses of `Protocol` cannot be instantiated, but their subclasses can. So we can't `Readable()`...
> In my mind this the right way to check: https://github.com/bluesky/yaqc-bluesky/blob/master/bluesky_protocols.py https://github.com/bluesky/ophyd/blob/master/ophyd/tests/test_bluesky_protocols.py This gets messier when you implement multiple protocols: ```python class Implicit: def describe(self): return {} def set(self) ->...