mbfits headers are missing some after the software update for VLBI user parameters
From Teams chat @ford_prachayapan
v0.5.0`
it has frequency axis information
Filename: 20240502_035748.mbfits
----------------------------------------------------------
hdul['PRIMARY'].header
SIMPLE = T / conforms to FITS standard
BITPIX = 8 / array data type
NAXIS = 0 / number of array dimensions
EXTEND = T
TELESCOP= 'TNRO ' / Telescope Name [20A]
ORIGIN = 'NARIT ' / Organisation or Institution [20A]
CREATOR = 'v0.5.0 ' / Software (including version) [20A]
MBFTSVER= '1.67 ' / MBFITS version [10A]
COMMENT astropy.io.fits
-----------------------------------------------------------
hdul['ARRAYDATA-MBFITS'].header
1CTYP2F = / Frequency axis for col.2 [8A]. value="FREQ"
1CRPX2F = 0.0 / Ref. channel
1CRVL2F = 1000000000.0 / Frequency at ref. channel in rest frame [Hz]
1CDLT2F = 1907.3486328125 / Channel separation [Hz]
1CUNI2F = 'Hz ' / Unit [8A] value="Hz"
v0.6.1-3-g5bf99cc
Missing some frequency axis information
Filename: 20240523_062532.mbfits
----------------------------------------------------------------
hdul['PRIMARY'].header
SIMPLE = T / conforms to FITS standard
BITPIX = 8 / array data type
NAXIS = 0 / number of array dimensions
EXTEND = T
TELESCOP= 'TNRO ' / Telescope Name [20A]
ORIGIN = 'NARIT ' / Organisation or Institution [20A]
CREATOR = 'v0.6.1-3-g5bf99cc' / Software (including version) [20A]
MBFTSVER= '1.67 ' / MBFITS version [10A]
COMMENT astropy.io.fits
-----------------------------------------------------------------
hdul['ARRAYDATA-MBFITS'].header
1CTYP2F = / Frequency axis for col.2 [8A]. value="FREQ"
1CRPX2F = / Ref. channel
1CRVL2F = / Frequency at ref. channel in rest frame [Hz]
1CDLT2F = / Channel separation [Hz]
1CUNI2F = 'Hz ' / Unit [8A] value="Hz"
Something happened that frequency axis data is not filled in the newer file. We don't know yet if this is from a regression in software upgrade or a different observation config where TCS does not fill the header for some other reason.
Download the 2 files and check other SCAN-MBFITS values to compare the SCANTYPE, FEBE, etc ... to see how the observations are different, then we will understand why the header is incomplete.