nxtomomill.converter.hdf5.acquisition.xrdctacquisition.XRDCTAcquisition#
- class nxtomomill.converter.hdf5.acquisition.xrdctacquisition.XRDCTAcquisition(root_url, configuration, detector_sel_callback, start_index, copy_frames=False)[source]#
Bases:
StandardAcquisition
- __init__(root_url, configuration, detector_sel_callback, start_index, copy_frames=False)[source]#
Note: for now we are force to provide entry and entry path as both can be different. For example when we are browsing the sample file entry == entry_path == 1.1 for example. Bit for the sample file file entry == 1.1 != entry_path == acquisssXXX_1.1
- Parameters
entry –
file_keys –
scan_titles –
param_already_defined –
raise_error_if_issue –
detector_sel_callback –
Methods
__init__
(root_url, configuration, ...[, ...])Note: for now we are force to provide entry and entry path as both can be different.
camera_is_valid
(det_name)check_tomo_n
()get_already_defined_params
(key)Return axis display for the detector data to be used by silx view
Return the expected number of nxtomo created for this acquisition.
get_z_translation_frm
(root_node, n_frame, ...)Can we have several entries 1.1, 1.2, 1.3.
parent_root_url
()- rtype
Optional
[DataUrl
]
read_entry
()register_step
(url[, entry_type, copy_frames])- param DataUrl url
entry to be registered and contained in the
to_NXtomos
(request_input, input_callback[, ...])- rtype
tuple
write_as_nxtomo
(shift_entry, ...[, ...])- rtype
tuple
Attributes
configuration
data_type
dim_1
dim_2
expo_time
is the acquisition expect to have a diode (instead of an energy field)
image_key_control
Is this an XRD-CT acquisition
Return the dict of all know machine electric current.
n_frames
n_frames_actual_bliss_scan
Should we raise an error if we encounter or an issue or should we just log an error message
is x_translation expected
require_y_translation
is z_translation expected
root_url
rotation_angle
start_index
- rtype
int
x_flipped
x_translation
y_flipped
y_translation
z_translation
- get_expected_nx_tomo()#
Return the expected number of nxtomo created for this acquisition. This is required to get consistent entry and file name. At lest for automation
- property has_diode#
is the acquisition expect to have a diode (instead of an energy field)
- is_different_sequence(url)[source]#
Can we have several entries 1.1, 1.2, 1.3… to consider. This is the case for XRD-CT where 1.1, 1.2, 1.3 should be consider as being part of the same sequence. Not for ‘standard tomography’
- property is_xrd_ct#
Is this an XRD-CT acquisition
- property known_machine_electric_current: Optional[dict]#
Return the dict of all know machine electric current. Key is the time stamp, value is the electric current
- Return type
Optional
[dict
]
- property raise_error_if_issue#
Should we raise an error if we encounter or an issue or should we just log an error message
- register_step(url, entry_type=None, copy_frames=False)#
- Parameters
url (DataUrl) – entry to be registered and contained in the acquisition
entry_type (
Optional
[AcquisitionStep
]) – type of the entry if know. Overwise will be ‘evaluated’
- Return type
None
- property require_x_translation#
is x_translation expected
- property require_z_translation#
is z_translation expected