Mapping of 'resolution' fields

[rhfogh]

The various synchrotron upload formats have many kinds of 'resolution', but how do they map?

MXLIMS has MxExperiment.expectedResolution, MxExperiment.requiredResolution, and CollectionSweep.resolution, the latter is an input parameter that serves to determine the detector distance used during a sweep. The mapping to aimedResolution, 'Target resolution' and requiredResolution is obvious. But there are also parameters called 'neededResolution', 'preObsResolution', 'observed resolution', and DLS even has both 'neededResolution' and 'requiredResolution' in the documents we have seen.

Which of these 'resolutions' are active, which are obsoloete, and what do the different tags mean?

[epanepucci]

at maxiv the aimed resolution is used to calculate the detector distance that provides the given resolution on all sides of the detector.
required resolution could be used by unattended pipelines to decide if a certain sample should be collected or not or maybe in serial crystallography experiments to indicate that a certain goal has been attained for the given session/protein. i.e., let's change the injector cartridge and move on to the next project/time point.
some of these may also be notes to the person doing the data collection (in case of samples being collected by a third party).

[rhfogh]

@epanepucci Thanks. Yes, your aimed resolution and required resolution match the MXLIMS expectedResolution and requiredResolution. The trouble is with all the other resolutions that some people have.