bluesky.suspenders.SuspendWhenChanged

class bluesky.suspenders.SuspendWhenChanged(signal, *, expected_value=None, allow_resume=False, sleep=0, pre_plan=None, post_plan=None, tripped_message='', **kwargs)[source]

Suspend when the monitored value deviates from the expected.

Only resume if allowed AND when monitored equals expected.

Parameters
signalophyd.Signal

The signal to watch for changes to determine if the scan should be suspended

expected_valuestr, float, or int

RunEngine operations will be suspended when signal deviates from this value. If None (default), set to value of signal when object is created.

allow_resumebool

Should RunEngine be allowed to resume once signal.value == expected again? Default value of False is expected for intended use case.

sleepfloat, optional

How long to wait in seconds after the resume condition is met before marking the event as done. Defaults to 0.

pre_planiterable or callable, optional

Plan to execute just before suspending. If callable, must take no arguments.

post_planiterable or callable, optional

Plan to execute just before resuming. If callable, must take no arguments.

tripped_messagestr, optional

Message to include in the trip notification

Notes

This suspender is designed to require bluesky restart if value changes.

USE CASE:

SuspendWhenChanged() is useful when signal is an EPICS enumeration (“mbbo”) used with a multi-instrument facility. Choices predefined in the mbbo record are the names of instruments allowed to control any shared hardware.

  • The signal, set by instrument staff outside of bluesky, names which instrument is allowed to control the hardware.

  • Other instruments not matching signal are expected not to control the hardware (they could use simulators instead or not operate the shared hardware).

Since a decision of hardware vs. simulators is made at the time a bluesky session starts and ophyd objects are first created, the session needs to be aware immediately if the signal is changed. The default value of allow_resume=False defends this decision. If there is a mechanism engineered to toggle ophyd signals between hardware and simulators, one might consider allow_resume=True.

Examples

# pause if this value changes in our session
# note: this suspender is designed to require Bluesky restart if value changes
suspend_instrument_in_use = SuspendWhenChanged(instrument_in_use)
RE.install_suspender(suspend_instrument_in_use)

Example EPICS database for APS 2-BM-A and 2-BM-B:

record(mbbo, "2bm:instrument_in_use") {
    # instrument team sets this
    # For additional field names, see
    # https://epics.anl.gov/EpicsDocumentation/AppDevManuals/RecordRef/Recordref-25.html#HEADING25-15
    field(DESC, "instrument using beam now")
    field(ZRST, "none")
    field(ONST, "2-BM-A")
    field(TWST, "2-BM-B")
    # THST
    # FRST
    # FVST
    # ...
}

NOTE: Always make the zero choice (ZRST) in the mbbo record to be ‘none’. This allows the instrument staff to designate that no instrument is allowed to control the shared hardware. Start the names of the allowed instruments with ONST.

It is convenient for the multi-instrument facility to make this definition in EPICS rather than in a specific bluesky session. The EPICS value could be useful in other contexts of instrument control beyond the realm of bluesky.

__init__(signal, *, expected_value=None, allow_resume=False, sleep=0, pre_plan=None, post_plan=None, tripped_message='', **kwargs)[source]

Methods

__init__(signal, *[, expected_value, ...])

get_futures()

Return a list of futures to wait on.

install(RE, *[, event_type])

Install callback on signal

remove()

Disable the suspender

Attributes

tripped