You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Beam damage may be a big problem for operando experiments. One easy solution is a fast shutter that stays closed and only open briefly when actually triggering a detector. Bluesky makes this easy, since we can intercept and inspect messages as they go by. For example, this plan produces the following messages:
check the return value to see if the shutter is closed
If it was yield Msg("set", shutter, 0)
Yield the original trigger
Watch for the subsequent wait message
Afterwards, yield Msg("set, shutter, 1) if the shutter was originally closed
One tricky bit, not all plans and not all devices need this behavior. We can make it a plan decorator, but then we need to know which devices have this requirement.
The text was updated successfully, but these errors were encountered:
Beam damage may be a big problem for operando experiments. One easy solution is a fast shutter that stays closed and only open briefly when actually triggering a detector. Bluesky makes this easy, since we can intercept and inspect messages as they go by. For example, this plan produces the following messages:
bp.count([ic], num=2)
(assumingic
is a device)The strategy can be:
"trigger"
Msg("read", shutter)
yield Msg("set", shutter, 0)
wait
messageMsg("set, shutter, 1)
if the shutter was originally closedOne tricky bit, not all plans and not all devices need this behavior. We can make it a plan decorator, but then we need to know which devices have this requirement.
The text was updated successfully, but these errors were encountered: