Closed prjemian closed 2 years ago
Should hklpy ignore the .kind
? Or should the user suffer the consequences of this unplanned setting?
Might be trickier than it seems to ignore the .kind
setting. At this time, we put the orientation information in the primary
stream, in the configuration. https://github.com/bluesky/hklpy/blob/c99a17d9b9087752141fb5f2055e59d4c2040f0c/hkl/util.py#L300-L303
Maybe this means we should reconsider how to store the orientation so that the details are secure against this type of reconfiguration.
Should be considered with #189.
hkl.util.list_orientation_runs(cat)
can take a long time for large catalogs. Add a progress bar?
For now, raise an error when a key is missing.
@gfabbris reported was raised
KeyError: 'energy'
by this sequence:On inspection of the
orientation
object, theenergy
key is missing:The diffractometer was configured with
fourc.energy.kind = "omitted"
.