I'm looking at FVC expnum 66575, and it has EXTNAME keys:
> listhead /tmp/fvc-00066575.fits | grep EXTNAME
EXTNAME = 'FVC '
EXTNAME = 'C0003 ' / name of this binary table extension
EXTNAME = 'F0004 '
EXTNAME = 'C0004 ' / name of this binary table extension
EXTNAME = 'F0005 '
EXTNAME = 'C0005 ' / name of this binary table extension
EXTNAME = 'F0006 '
EXTNAME = 'C0006 ' / name of this binary table extension
EXTNAME = 'F0007 '
EXTNAME = 'C0007 ' / name of this binary table extension
EXTNAME = 'F0008 '
EXTNAME = 'C0008 ' / name of this binary table extension
EXTNAME = 'F0009 '
EXTNAME = 'C0009 ' / name of this binary table extension
EXTNAME = 'F0010 '
EXTNAME = 'C0010 ' / name of this binary table extension
EXTNAME = 'F0011 '
EXTNAME = 'F0000 '
EXTNAME = 'C0000 ' / name of this binary table extension
EXTNAME = 'F0001 '
EXTNAME = 'C0001 ' / name of this binary table extension
EXTNAME = 'F0002 '
EXTNAME = 'C0002 ' / name of this binary table extension
EXTNAME = 'F0003 '
EXTNAME = 'C0037 ' / name of this binary table extension
EXTNAME = 'C0024 ' / name of this binary table extension
ie, all mixed up. It looks like desi_fvc_proc with the --sequence option, however, assumes they are in order, and writes out the first image into output file *-F0000.csv.
I'm looking at FVC expnum 66575, and it has EXTNAME keys:
ie, all mixed up. It looks like desi_fvc_proc with the --sequence option, however, assumes they are in order, and writes out the first image into output file
*-F0000.csv
.