A Lima ROI outside of the image fail the scan without a clear message
If you create a ROI outside of the LIMA image, you can't ct
or scan the ROIs.
On BLISS side:
DEMO_SESSION [9]: loopscan(1, 1, beamviewer.roi_counters)
WARNING 2020-06-18 19:39:45,800 flint: Flint starting...
!!! === RuntimeError: Device LimaCCDs(id00/limaccds/slits_simulator) (beamviewer) is in Fault state === !!! ( for more details type cmd '
last_error' )
!!! === RuntimeError: Device LimaCCDs(id00/limaccds/slits_simulator) (beamviewer) is in Fault state === !!! ( for more details type cmd '
last_error' )
!!! === RuntimeError: Device LimaCCDs(id00/limaccds/slits_simulator) (beamviewer) is in Fault state === !!! ( for more details type cmd '
last_error' )
!!! === RuntimeError: Nexus writer is in FAULT state ('/5.1/instrument/beamviewer_roi1/data': shape = (), dtype=float incomplete) === !!!
( for more details type cmd 'last_error' )
!!! === RuntimeError: Device LimaCCDs(id00/limaccds/slits_simulator) (beamviewer) is in Fault state === !!! ( for more details type cmd '
last_error' )
On LIMA side:
src/CtEvent.cpp:133)-Error: *event=<Event [1.07322]: Severity=Error, Domain=Processing, Code=Default: RoiCounter : roi <82,846>-<302x179> is not contained into data <1024x1024>>
If you try to edit the ROIs back (you can't):
DEMO_SESSION [11]: edit_roi_counters(beamviewer, 1)
WARNING 2020-06-18 19:40:36,907 flint: Flint starting...
!!! === RuntimeError: Device LimaCCDs(id00/limaccds/slits_simulator) (beamviewer) is in Fault state === !!! ( for more details type cmd '
last_error' )
!!! === RuntimeError: Device LimaCCDs(id00/limaccds/slits_simulator) (beamviewer) is in Fault state === !!! ( for more details type cmd '
last_error' )
!!! === RuntimeError: Device LimaCCDs(id00/limaccds/slits_simulator) (beamviewer) is in Fault state === !!! ( for more details type cmd '
last_error' )
Took 0:00:02.319874[s]
!!! === RuntimeError: Device LimaCCDs(id00/limaccds/slits_simulator) (beamviewer) is in Fault state === !!! ( for more details type cmd '
last_error' )
It would be good to have a better user feed back.
- As it is easy to create ROI outside of the image with Flint:
- The ROI could be clamped before saved in LIMA
- The ROI could be constrained on GUI side (not for this release)
- Call a kind of sanity check in LIMA after updating the ROIs
- Stronger scan sequencer?
What do you think?