nxtomomill.converter.hdf5.acquisition.zseriesacquisition.ZSeriesBaseAcquisition#
- class nxtomomill.converter.hdf5.acquisition.zseriesacquisition.ZSeriesBaseAcquisition(*args, **kwargs)[source]#
Bases:
BaseAcquisition
A ‘z serie acquisition’ is considered as a serie of _StandardAcquisition. Registered scan can be split according to z_translation value.
Methods
__init__
(*args, **kwargs)Return axis display for the detector data to be used by silx view
Return the expected number of nxtomo created for this acquisition.
Return the tuple of all
StandardAcquisition
composing _acquisitionsget_z
(entry)get_z_translation_frm
(root_node, n_frame, ...)is_different_sequence
(entry)Can we have several entries 1.1, 1.2, 1.3.
read_entry
()register_step
(url, entry_type[, copy_frames])Add a bliss entry to the acquisition :type url:
DataUrl
:param url: :param entry_type:to_NXtomos
(request_input, input_callback[, ...])- rtype
tuple
write_as_nxtomo
(shift_entry, ...[, ...])- rtype
tuple
Attributes
configuration
is the acquisition expect to have a diode (instead of an energy field)
Is this an XRD-CT acquisition
Should we raise an error if we encounter or an issue or should we just log an error message
is x_translation expected
is z_translation expected
root_url
start_index
- rtype
int
- get_axis_scale_types()#
Return axis display for the detector data to be used by silx view
- get_expected_nx_tomo()[source]#
Return the expected number of nxtomo created for this acquisition. This is required to get consistent entry and file name. At lest for automation
- get_standard_sub_acquisitions()[source]#
Return the tuple of all
StandardAcquisition
composing _acquisitions- Return type
tuple
- property has_diode#
is the acquisition expect to have a diode (instead of an energy field)
- is_different_sequence(entry)[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 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, copy_frames=False)[source]#
Add a bliss entry to the acquisition :type url:
DataUrl
:param url: :param entry_type:- Return type
None
- property require_x_translation#
is x_translation expected
- property require_z_translation#
is z_translation expected