FormatCBFMiniPilatus agrees to process but fails on Stoe lab-based data

[jamesrhester]

FormatCBFMiniPilatus claims to understand data files from a Pilatus100K integrated into Stoe lab equipment but the frames are not able to be processed, because the miniCBFs do not have a Beam_xy entry, and even if they did, the detector is mounted on a 2 theta arm. A complete dataset is available here and a full imgCIF describing all scans and gonio/detector geometry is available here. A sample header from scan 2, frame 10:

###CBF: VERSION 1.5, XI2CBF v1.2 (25May2022) Stoe&Cie GmbH
_array_data.header_convention PILATUS_1.2
_array_data.header_contents
;
# Detector: Pilatus100K
# Pixel_size 1.720000e-04 m x 1.720000e-04 m
# Silicon sensor, thickness 1000.000000 m
# Exposure_time 60.000000 s
# Wavelength 0.560834 A
# Detector_distance 0.040000 m
# Start_angle 151.261000 deg.
# Angle_increment 1.000000 deg.
# Detector_2theta -23.400000 deg.
# Phi -5.000000 deg.
# Phi_increment 0.000000 deg.
# Chi -30.183000 deg.
# Omega 151.261000 deg.
# Omega_increment 1.000000 deg.
# Oscillation_axis OMEGA
;

I may find time to fix this, presumably by carving out an exception for the Stoe equipment and making a new class, but I'm raising it here so it is not forgotten.