The XID DB Top level Science Requirements of the XID Imaging Program.

Version 0.2 Richard McMahon 2001-Nov-11
Added that the XIDDB needs to include a Log of all XMM observations
Added a requirement to store a unique identifier for all optical
imaging systems e.g. the observatory filter code

Version 0.1 Richard McMahon 2001-Sep-13


The XIDDB is intended to:

(i)   enable planning and execution of the XID imaging follow-up program

(ii)  it should contain information about X-ray data that relates to the
      XID imaging program

REQUIREMENT:
      o it must contain a catalogue of all executed and planned XMM 
        observations

      o it may contain relevant XMM PPS data products or links to what 
        is at LUX

      o maybe this part of the DB is at LUX unless it can be updated
        daily from a master at LUX

(iii) it should contain copies of the ACDS data products 

(iv)  it should contain information about the instruments being used for
       the XID imaging program

(v) it should contain a record of what ground based observations are
       scheduled for the XID program and what instruments are to be
       used.

(vi)   it should contain information about what XID fup data products 
      exist, where they are and who is person responsible for distribution 
      of this data.    (see note 1 below)

(vii) it should contain information about the quality and status of XID
     fup data products (see note 1 below)

(viii) it should permit access to XID fup data products or specify the
      location of the data if it is stored elsewhere.

(ix) it should contain catalogues of magnitudes based on the 
     XID fup dataproducts



-------------------------------------------------------------------------------

Note 1:

Draft minimal log of observations 

# from raw headers
run number
telescope
instrument
fieldname
waveband
exposure time
filter
filter system
filter identifier [unique observatory specific code]
date of observation
cat-ra
cat-dec
equinox
airmass

#from CASU pipeline
extinction
seeing
aperture corrections
zeropoint
relative_chip_zeropoint [I think there are zeropoint offsets per chip]
rms of astrometric fit
number of star used in fit






 it should contain a record of what XID observations have been executed:
    o this may just be basic information from obsering logs
    o there should be some qaulity control information assocaited with all
      data
    o e.g. seeing, cloud cover this can be a range of values and should
      support undefined