Pete R Jemian

Labeled as bug but that's an opinion. Alternatively could be an enhancement. I picked bug since that is the way it works in the code now.

Possible duplicate of #1244 with addition of logging the intercepted lower-level exception.

This issue looks similar to https://github.com/APS-USAXS/ipython-usaxs/issues/255, which resets the instrument when a scan is ended abnormally. > When we decide to stop and abort a plan, the instrument is not...

@ambarb wrote: > IF the scan clean up returns motors to starting positions and user selects "STOP" on the CSS or PyDM or whatever equivalent screen, then the motor's read...

@kmpeters - The use case is described in this [particular comment above](https://github.com/bluesky/bluesky/issues/1296#issuecomment-590449228). > There are some motors that require a backlash regardless of encoder because of mechanical reasons. If the...

It is appropriate to note that this retry sequence concerns Signals which are *not* connected to the EPICS motor record movement. The motor record has its own move retry algorithm...

Is the *encouraged* pattern in the documents? It should be.

The discussion at the user meeting workshop and here is great. Panacea (use the same tools all the time) is what we rely on but the advice against a notebook...

I'm not persuaded that argument 1 only applies to notebooks. Our EPICS beam lines could change the state of the instrument at any time without knowledge of or control by...

Is this code executed? https://github.com/bluesky/bluesky/blob/566dce9e7ada95e2346c9aa61206c6a2f0a189bf/bluesky/utils/__init__.py#L1038-L1053