Open rowlesmr opened 1 year ago
ooooor, we can just explicitly put in the angle offset due to any kind offset with PD_XCOORD
.
PD_SPEC
is good. I don't think a specimen would be per-detector._pd_instr.geometry
would be the right place to describe the geometry, but this is currently a free-text entry. We should make a new one with recognised values, e.g. _pd_instr.standard_geometry
an offshoot of #53
Sort of related to angle calibrations is how to record specimen displacements.
_pd_instr.detector_circle_radius
_pd_instr.dist_spec_anal
_pd_instr.dist_spec_detc
_pd_instr.dist_spec_vdetc
PD_SPEC
is the best place. I don't think thePD_INSTR
is appropriate.PD_PROC_LS
doesn't seem right, as although it is often a refined parameter, it does refer to a "real" thing.PD_SPEC
is aSet
category; do we need to be able to provide displacements per detector_id? if so, then we'd need to make something likePD_SPEC_DISPLACEMENT
orPD_CALIB_DISPLACEMENT
._pd_spec.displacement_geometry
to allow for the automated calculation of corrected 2theta values ? With an enumerated choice: "bragg-brentano", "debye-scherrer", "seeman-bohlin", ... , "other". Other would require_pd_calibration.conversion_eqn
to be defined.(I promise to stop thinking of things now... :))