nxtomomill merge requestshttps://gitlab.esrf.fr/tomotools/nxtomomill/-/merge_requests2023-09-26T10:59:14+02:00https://gitlab.esrf.fr/tomotools/nxtomomill/-/merge_requests/148Draft: add source - sample distance2023-09-26T10:59:14+02:00paynoDraft: add source - sample distancerelated to https://gitlab.esrf.fr/tomotools/tomoscan/-/merge_requests/122
for HDF5: for now we need to see how to retrieve the focal plan, we did not see this use cases from other beamlines yet.related to https://gitlab.esrf.fr/tomotools/tomoscan/-/merge_requests/122
for HDF5: for now we need to see how to retrieve the focal plan, we did not see this use cases from other beamlines yet.https://gitlab.esrf.fr/tomotools/nxtomomill/-/merge_requests/99Draft: EDF: improve flexibility of the bliss / HDF5 collect part (description...2023-09-26T10:59:08+02:00paynoDraft: EDF: improve flexibility of the bliss / HDF5 collect part (description of what needs to be done)If at one point we intend to create other classes than NXtomo it would be wise to add some meta handling of a structure defined in settings.py like:
```python
MAPPING = {
# could be used to provide more generic code a...If at one point we intend to create other classes than NXtomo it would be wise to add some meta handling of a structure defined in settings.py like:
```python
MAPPING = {
# could be used to provide more generic code and improve flexibility.
# at least for HDF5
# root attributes
"start_time": None, # TODO for now the user cannot provide them...
"end_time": None, # TODO for now the user cannot provide them...
"title": None, # TODO for now the user cannot provide them...
# sample attributes
"sample.rotation_angle": ROT_ANGLE_KEYS,
"sample.x_translation": X_TRANS_KEYS,
"sample.y_translation": Y_TRANS_KEYS,
"sample.z_translation": Z_TRANS_KEYS,
# instrument attributes
"instrument.detector.data": VALID_CAMERA_NAMES, # fit also automatically the frame type
"instrument.detector.estimated_cor_from_motor": Y_ROT_KEY,
"instrument.detector.count_time": ACQ_EXPO_TIME_KEYS,
"instrument.detector.x_pixel_size": X_PIXEL_SIZE,
"instrument.detector.y_pixel_size": Y_PIXEL_SIZE,
"instrument.detector.distance": DISTANCE_KEYS,
"instrument.detector.field_of_view": None, # TODO for now the user cannot provide them...
"instrument.detector.tomo_n": None, # TODO for now the user cannot provide them...
"instrument.diode.data": DIODE_KEYS,
"instrument.source.name": None, # TODO for now the user cannot provide them...
"instrument.source.type": None, # TODO for now the user cannot provide them...
"instrument.beam.incident_energy": None, # TODO for now the user cannot provide them...
}
```
which would define all the mapping to be done from the bliss file (the value is the name of the dataset in the file) to nexus file (key is the property to set)https://gitlab.esrf.fr/tomotools/nxtomomill/-/merge_requests/223Draft: h52nx: pass detector `roi` to the NXtomo2024-03-06T14:31:29+01:00paynoDraft: h52nx: pass detector `roi` to the NXtomoclose #172
Related to https://gitlab.esrf.fr/tomotools/nxtomo/-/merge_requests/32close #172
Related to https://gitlab.esrf.fr/tomotools/nxtomo/-/merge_requests/321.1https://gitlab.esrf.fr/tomotools/nxtomomill/-/merge_requests/200Flat reducer with angular dependency2024-01-15T13:13:32+01:00myronFlat reducer with angular dependencyFlat reducer with angular dependency and attaching them to scans, also helical ones and z-stages
------------------------------------------------------------------------------------------------
TODO list
---------
- [x] Obtain the prop...Flat reducer with angular dependency and attaching them to scans, also helical ones and z-stages
------------------------------------------------------------------------------------------------
TODO list
---------
- [x] Obtain the proper flats at the requested angles
- [x] Create adapted flats to match helical scansmyronmyron