Wrong value displayed by bluesky in motor movement when close to end of motion

[cmazzoli]

In a macro, I asked for:

mov(gamma,160) coming from an higher gamma value. I got:

[end of previous scan..] +------------+--------------+

gamma
164.0811 deg

[beginning of following scan..] Transient Scan ID:

The motor is actually at the correct value but I wonder then why the position shown on the screen by bluesky is not the final position reached by the motor before starting the scan. This can be confusing for users, who may have doubts on how to check motor positions while a macro (or plan..) is keeping the control interface busy.

[tacaswell]

Is this reproducible?

[cmazzoli]

Happened twice, back and forth in the same macro.. On Mar 2, 2016 3:11 PM, "Thomas A Caswell" notifications@github.com wrote:

Is this reproducible?

— Reply to this email directly or view it on GitHub https://github.com/NSLS-II/wishlist/issues/107#issuecomment-191405814.

[tacaswell]

Is the source for your function someplace I can see?

[cmazzoli]

If I remember right, this is the code (as xf23id1, ~/Beamline/Macros/fCCD_Fe55.py):

#### Fe55 source through mica window

RE.md['group']='CSX';
RE.md['project']='fCCD single photon';
RE.md['sample']['type']='External source through mica window';
RE.md['sample']['composition']='Fe55'

fccd.acquire_time.put(5)

## Dark images
mov(gamma,160)
sleep(2)

fccd.plugin_num_images.put(120)

for kk in arange(0,1):
    ct()
    olog('Fe55 test. Dark image: #{}, {} images @ {:.1f}Hz'.format((db[-1].get('start').get('scan_id')), fccd.plugin_num_images.get(), 1./fccd.acquire_time.get()))

## Light images
mov(gamma,179)
sleep(2)

fccd.plugin_num_images.put(120)

for kk in arange(0,6):
    ct()
    olog('Fe55 test. Light image: #{}, {} images @ {:.1f}Hz'.format((db[-1].get('start').get('scan_id')), fccd.plugin_num_images.get(), 1./fccd.acquire_time.get()))

## Dark images
mov(gamma,160)
sleep(2)

fccd.plugin_num_images.put(120)

for kk in arange(0,2):
    ct()
    olog('Fe55 test. Dark image: #{}, {} images @ {:.1f}Hz'.format((db[-1].get('start').get('scan_id')), fccd.plugin_num_images.get(), 1./fccd.acquire_time.get()))

fccd.plugin_num_images.put(100)
sleep(2)

ct()
olog('Fe55 test - noise. Dark image: #{}, {} images @ {:.1f}Hz'.format((db[-1].get('start').get('scan_id')), fccd.plugin_num_images.get(), 1./fccd.acquire_time.get()))

fccd.plugin_num_images.put(2000)
sleep(2)

ct()

olog('Fe55 test - noise. Dark as Light image: #{}, {} images @ {:.1f}Hz'.format((db[-1].get('start').get('scan_id')), fccd.plugin_num_images.get(), 1./fccd.acquire_time.get()))

[tacaswell]

Can you reproduce this by doing

mov(gamma, 179)
mov(gamma, 160)

[tacaswell]

And this is that green constantly updating text in the screen that is wrong?

[cmazzoli]

I checked now with another collection profile (is the simulation mode available??) and apparently I don't see it anymore. I moved relative of few degrees (I am measuring, I cannot perturb it too much..). Yes it was related with the on screen green live update on the motor position. Should I do some other tests?

[tacaswell]

This should be reported as a bug against ophyd. Closing to move there.

What is the beamline phone number?