On branch dev_ntmdt_stage, each time move it called it will check the move against the stage constraints. Subsequently, each time get constraints is called it fetches this from the machine.
When does this occur?
Each time the stage is asked to move.
Where on the platform does it happen?
In the function get_constraints the function _get_scanner_range is called.
What is affected by this bug?
On branch
dev_ntmdt_stage
, each time move it called it will check the move against the stage constraints. Subsequently, each time get constraints is called it fetches this from the machine.When does this occur?
Each time the stage is asked to move.
Where on the platform does it happen?
In the function
get_constraints
the function_get_scanner_range
is called.Expected behavior (i.e. solution)
Run
_get_scanner_range
only on start-up.