nxtomomill.converter.hdf5.acquisition.blisstomoconfig.TomoConfig

class nxtomomill.converter.hdf5.acquisition.blisstomoconfig.TomoConfig

Bases: object

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

__init__()

Methods

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

Attributes

rotation	rtype: str | None
sample_u	rtype: str | None
sample_v	rtype: str | None
sample_x	rtype: str | None
sample_y	rtype: str | None
tomo_detector	rtype: str | None
translation_x	rtype: str | None
translation_y	rtype: str | None
translation_z	rtype: str | None

static from_technique_group(technique_group)

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’…