Previous: MIA and EWS differ   Up: Contents  

MIDI FITS binary table files

General structure

  1. Primary Header
    RA    =   245.8521    / coordinate in degrees
    HIERARCH ESO DET DIT       =  0.04 /int time in seconds
    HIERARCH ESO INS CAM NAME  = 'FIELD'
    HIERARCH ESO ISS CHOP FREQ = 1.0
    HIERARCH ESO DET NRTS MODE = 'OBS_FRINGE_TRACK_DISPERSED'
    etc.
  2. First Extension (Table) (INS_DESCRIPTION)
    Table Header
    Table Data
        
  3. 2nd Extension Table (INS_TRAIN)
  4. ARRAY_DESCRIPTION
  5. ARRAY_GEOMETRY
  6. OPTICAL_TRAIN
  7. IMAGING_DETECTOR
  8. IMAGING_DATA
  9. SCAN_SETUP
MIDI raw observations are broken up into multiple files of about 100 MB, each with its own Primary Header, IMAGING_DETECTOR, IMAGING_DATA... with file names:

MIDI.<date>T<START_UT>.fits

Inside of EWS most programs accept multiple files as a single blank separated character string:

midiPipe,'outtag',"file1.fits file2.fits file3.fits",mask=maskfile.fits

A handy way to read FITS headers on UNIX machines is:

fold filename | more

In EWS:

  header = oirGetPriHead(filename) & print,header
  camera = oirGetKey(filename,'CAM NAME') & print,camera

Please look in the EWS UserGuide for short descriptions of the various utilities.


IMAGING_DATA table


OIFITS format for visibility files


Previous: MIA and EWS differ   Up: Contents  
Rainer Köhler, 21-Mar-2005