search

bluesky / ophyd

hardware abstraction in Python with an emphasis on EPICS
https://blueskyproject.io/ophyd
BSD 3-Clause "New" or "Revised" License
51 stars 79 forks source link

Notice when signals enter alarm state #624

Open tacaswell opened 6 years ago

tacaswell commented 6 years ago

See https://github.com/NSLS-II/bluesky/issues/1100

danielballan commented 6 years ago

We don’t already do this? Oof.

I plan to look into this as part of leveraging caproto to produce better error messages.

tacaswell commented 6 years ago

Motors do it, but not generic signals.

tacaswell commented 6 years ago

we should also think about how to do alarm propagation in Devices in general. As we combine many records into a Device we will in general have inconsistent alarm states across it's children. In many cases if there is an alarm (of some degree) on any child we want to kill the status objects. This probably also means we need a coherent way to keep track of where we have stashed the status object.

teddyrendahl commented 6 years ago

I've thought about suggesting Kind.alarm. How many devices would just monitoring read_attrs for alarm states be wrong?

ambarb commented 5 years ago

@tacaswell this is the other issue that I just spoke with you about. You converted my Bluesky issue into an ophyd issue.