Flint: where do not display all the motors used by a scan
Feedback from ID26.
Depending on the scan, the where
function is not able to display the expected motor.
- Talking to @janousov and @pguillou
- It's probably because of
CalcMotor
. The real motors from theCalcMotor
controllers are maybe not iterated and then not processed by thiswhere
function. - This could also be because of a continuous scan and the way it was impemented at ID26. In this case it have to be checked on the beamline.
I can take a look at the CalcMotor
problem.