Non-existent axes are included

[jamesrhester]

miniCBF headers like giving values of -9999 for axes that are not present. So, for example, SBGRID 952 has the following miniCBF header:

# Detector: PILATUS3 2M, S/N 24-0124
# 2020/Mar/19 17:43:25
# Pixel_size 172e-6 m x 172e-6 m
# Silicon sensor, thickness 0.001 m
# Oscillation_axis omega
# Excluded_pixels:  badpix_mask.tif
# Chi 0.0000 deg.
# Angle_increment 0.1000 deg.
# Polarization None
# file_comments 
# N_oscillations 1800
# Beam_xy (747.00, 828.00) pixels
# Exposure_time 0.150000 s
# Phi -9999.0000 deg.
# Energy_range (0, 0) eV
# Start_angle -118.8000 deg.
# Detector_distance 0.324127 m
# Detector_Voffset 0.0000 m
# Alpha 0.0000 deg.
# Flat_field: (nil)
# Threshold_setting 6750 eV
# Exposure_period 0.153000 s
# N_excluded_pixels: = 321
# Kappa -9999.0000 deg.
# Tau = 0 s
# Transmission 100.0
# Detector_2theta 0.0000 deg.
# Flux 1e+11
# Count_cutoff 1048500
# Trim_directory: (nil)
# Wavelength 0.918400 A

from which it is clear that there are no phi or kappa axes, but that there is a chi axis. However, creator includes phi and kappa axis definitions.