Closed silkenelson closed 4 years ago
umvr
already exists. Which devices are missing it?
Ah: I'll look and update the confluence documentation and resolve this request afterr that.
It is completely possible that the function didn't get put on every single device, so I'm happy to bring it over to anything we missed.
It is also possible that it does not work the way you expect or has other issues, so feel free to ask for revisions.
Did some investigation into which devices have/do not have the move interface:
Anything suspicious in either group?
pcdsdevices.attenuator.AttenuatorCalculatorBase pcdsdevices.epics_motor.SmarActOpenLoop pcdsdevices.lens.LensStack
All stand out as candidates
Also, I noticed while looking at our pseudopositioners: some may inherit directly from ophyd.PseudoSingle instead of the MvInterface-mixin version.
Diling just tried on gon_h in xpp3: it existed, but it says 'progress bar not available'.
That's frustrating... I prefer things we work on to stay working.
I was getting that progress bar message locally and thought it was just me... 🙍♂️
Feature Request Move a motor and print the current position until move is completed.
Existing Alternatives use old python.
Context This can give a lot of comfort when you don't trust a stage and/or just want to see how long the move will take.