Skip to content

GitLab

bliss
bliss
Closed
Opened by Valentin Valls@valentin.valls
Report abuse New issue

watch_session_scans emit an unexpected new-data-event at the prepare stage of a Lima detector

Here is a problem occurred time to time for the very first acquisition of a scan using a Lima detector.

  • watch_session_scans inform Flint that a new data for the image is available
  • Flint reach data.get(-1).get_image(-1)
  • And receive this exception No image has been taken yet

It could be normal in case of a long time scan, cause we do not expect the very last image, but just something to display. But in case of a ct only one image is acquired and can be lost (on the flint side).

Any idea if it is normal? Or if it can be fixed?

If not, i still can mitigate that and retry to read the image at the end of the scan, or with a kind of sleep time. But it is not really convenient.

Problem noticed by @pithan.

ERROR:bliss.flint.helper.scan_manager:Error while reaching data ]   0 eta [None]
Traceback (most recent call last):
  File "/users/pithan/dev/bliss_jul25/bliss/flint/helper/scan_manager.py", line 86, in __refresh
    self.__new_scan_data(data_type, master_name, data)
  File "/users/pithan/dev/bliss_jul25/bliss/flint/helper/scan_manager.py", line 109, in __new_scan_data
    raw_data = image_view.get_image(-1)
  File "/users/pithan/dev/bliss_jul25/bliss/data/lima.py", line 126, in get_image
    data = self._get_from_server_memory(proxy, image_nb)
  File "/users/pithan/dev/bliss_jul25/bliss/data/lima.py", line 183, in _get_from_server_memory
    raise IndexError("No image has been taken yet")
Edited by Valentin Valls