Merge roi counters and roi profiles
Here is a proposal to rework the ROIs.
I think it would be good to merge ROIs together in order to provide consistent names.
This should bring few other helps:
- A single place to look at ROIs
- The same way to handle them
- This should provide an easier way to play with this concepts in user side
Here i think we only have to see a ROI as a unique geometry from a detector. So we have to decorrelate the ROI (a geometry) from the processing based on it (anyway it is a profile or a sum/mean/min/max).
This will became useful on GUI side, cause we can handle this point of view, but it's much better to provide the same concepts in BLISS, for consistency for users.
Current state
- limacam
- roi_counters
- roi2_sum
- roi3_min
- roi_profiles
- roi1
- roi_counters
We can see that the roi1
is not named the same as the others, and we can't really sort them together.
Here ROI ids can't overlap between roi_counters
and roi_profiles
, which is nice, but which is not obvious (that's an implicit constraint).
Proposal
- limacam
- rois
- roi1_vprofile
- roi2_sum
- roi3_min
- rois
This way we provide the same way to handles the ROIs: {roi_name}_{processing}
.
- limacam
- rois
- roi3_vprofile
- roi3_sum
- rois
Which could easily allow to reuse a ROI for many processing
Ideally
Ideally it would be even better to split ROI and processing, in order to have a real ROI object in BLISS. In which we can enable or disable processing.
- limacam
- rois
- roi1
- vprofile
- roi2
- sum
- roi3
- sum
- vprofile
- roi1
- rois