nxtomomill.converter.hdf5.acquisition.blisstomoconfig.TomoConfig#

class nxtomomill.converter.hdf5.acquisition.blisstomoconfig.TomoConfig[source]#

Bases: object

hold motor used for tomography acquisition according to https://tomo.gitlab-pages.esrf.fr/ebs-tomo/master/modelization.html convension

__init__()[source]#

Methods

`__init__`()
`from_technique_group`(technique_group)	get rotation motor and thinks like this from the 'tomoconfig'.

Attributes

`rotation`	rtype `Optional`[`str`]
`sample_u`	rtype `Optional`[`str`]
`sample_v`	rtype `Optional`[`str`]
`sample_x`	rtype `Optional`[`str`]
`sample_y`	rtype `Optional`[`str`]
`tomo_detector`	rtype `Optional`[`str`]
`translation_x`	rtype `Optional`[`str`]
`translation_y`	rtype `Optional`[`str`]
`translation_z`	rtype `Optional`[`str`]

static from_technique_group(technique_group)[source]#

get rotation motor and thinks like this from the ‘tomoconfig’. This can retrieve one or several dataset name or a single one. In the case of several dataset name we get (real_motor_name, bliss_alias)

If the motor moves then this is pretty simple the real motor_name dataset exists. But if the motors does not move during the bliss scan (scalar value) then the real_motor_name dataset doesn’t exists and the bliss alias does. This is why we need to keep both and check both during the ‘standard process’…