Currently, during fast energy scans, the id-energy readback remains static, displaying only the last energy setpoint (the midpoint of the scan). This creates a discrepancy between the reported value and the physical hardware state, leading users to believe the Insertion Device (ID) is not moving or tracking correctly.
Cause:
The id-energy signal is currently a soft-signal. It is only updated via a set method upon completion of a move. Because fast energy scans bypass standard set methods, the readback is never triggered to update.
Acceptance criteria :
Possible Solution:
- Implement an inverse converter for the energy readback. This will transform the raw motor position back into energy units in real-time, ensuring the readback is hardware-derived rather than setpoint-derived.
- An on the fly inverse function may be computational expansive, we may have to create inverse lookup table.
- Simply have the energy readback in mm of motor.
Tasks
base on the goals, deduce the tasks required. check them off once they're done
Related Resources
Currently, during fast energy scans, the id-energy readback remains static, displaying only the last energy setpoint (the midpoint of the scan). This creates a discrepancy between the reported value and the physical hardware state, leading users to believe the Insertion Device (ID) is not moving or tracking correctly.
Cause:
The id-energy signal is currently a soft-signal. It is only updated via a set method upon completion of a move. Because fast energy scans bypass standard set methods, the readback is never triggered to update.
Acceptance criteria :
Possible Solution:
Tasks
base on the goals, deduce the tasks required. check them off once they're done
Related Resources