LPD's 512 memory cells are not necessarily filled in order - e.g. if the veto pattern is set to capture every eighth possible pulse, it might start with memory cells 8,16,24... and then loop around when it reaches the end. This filling order affects the detector's behaviour, so we want to correct the data using darks taken with the same veto pattern.
More precisely, it's OK for the cell order in the constants to be an extension of the cell order used for the data, so we're doing prefix matching. The idea is that constants will always be taken with 512 memory cells, varying only the order.
In practice, the way the veto pattern is usually set should mean the memory cell order is a function of only the first cell used and the step size, but we don't want to hardcode so many assumptions about the way the detector is configured and the way its firmware works.
How Has This Been Tested?
@manettim has added support for string conditions to CalCat (ITDM/calibration_catalog!107), and this is running on the test instance
I added basic support in iCalibrationDB (detectors/cal_db_interactive!86) - this pycalibration MR depends on that one.
For correction, I needed to get a token from test_calibration and configure ~/.config/pycalibration/cal_tools/restful_config.yaml to make it talk to that instance instead of the production one. Then:
