Tomography sinograms
BACKGROUND
A dummy script that illustrates all tomo scans we are aware of (ID19, ID15, ID16a, ID16b): https://gitlab.esrf.fr/snippets/209
If there are some sequence types missing (I'm sure there are), please add to the code or descibe in words in the comments.
- for absorption or transmission tomo (ID19)
- acquisition of images: 1 image (called "projection") for each rotation angle
- the sinogram is an image X axis => projection image line, Y axis => projection angle
- relies on Roi2Spectrum Lima feature
- acquisition of images: 1 image (called "projection") for each rotation angle
- for diffraction tomo (ID15)
- 1 image for each rotation angle and for each translation axis position
- the sinogram is an image X axis => translation position, Y axis => projection angle
- relies on ArcRois Lima feature
- 1 image for each rotation angle and for each translation axis position
- for fluo tomo (ID16a, ID16b)
- 1 mesh (or cont. equivalent) of the sample for each rotation angle
- the sinogram is an image X axis => mesh line, Y axis => rotation angle
- relies to MCA rois (already exist)
- 1 mesh (or cont. equivalent) of the sample for each rotation angle
- for xrf/xrd tomo (ID16b)
- 1 ascan (or cont. equivalent) of the rotation angle for each sample positions
- the sinogram is an image X axis => sample position, Y axis => rotation angle
- relies to MCA rois (already exist) and ArcRois Lima feature
- 1 ascan (or cont. equivalent) of the sample position for each rotation angle
- the sinogram is an image X axis => sample position, Y axis => rotation angle
- relies to MCA rois (already exist) and ArcRois Lima feature
- 1 ascan (or cont. equivalent) of the rotation angle for each sample positions
Scans where the rotation angle is not the inner-loop of the scan: angle order is not necessarily incremental.
FEATURE REQUESTS
- people want to be able to follow acquisition in live (don't confuse with the discussion on "live channels" #1032)
- at the end the resulting image has to be saved
- intermediate results must be ignored
How it was done before with spec: specific Lima plugin, that did all the work ; people were looking at intermediate results via shared memory + Oxidis.
TODO
-
Support ArcRois as counters in Bliss (under the same counter controller) !2671 (merged) -
Roi2Spectrum -
Support in Flint #1858 (closed) !2784 (merged) -
Re-emit data to the group, but this needs to be done in the tomo scan implementation (add helper functions in Bliss inspired by demo/userscript/tomo.py ?)
RELATED ISSUES
-
#1685 (closed), #1604: general question on managing lima sub-devices
-
#1032: "live channels", but sinograms are conceptually different from lets say a growing MCA spectrum. It is not "live" in that sense.
Edited by Wout De Nolf