Just notes to myself - JMB - Sep 2007

Archived data products....

  - VLA raw data files 

  - VLBA raw data files

  - VLBA partly-calibrated data files 

  - Lorant's image pipeline :

    - image files .fits, .jpg, .JPG

    - calibrated uvdata the produced the image

    - calibrated uvdata for a project on date at freq that contains 
      data that might produce images of several sources.

  - VLA observing control scripts : scheduled and dynamic

  - VLA operators log files


Data file ID tags ...

  - arch_file_id (number) relates archived VLA or VLA raw data files
    in 'archive' table to rows in observing scans table, and spectral 
    window descriptions table arch_file_id = 0 in archive file location 
    table. arch_file_id is generated when the raw data file is ingested
    and cataloged..

  - arch_file_id is used in the Image table to relate an image file
    to the calibrated uvdata file that created that image. This 
    arch_file_id is not the same as the value used to relate the raw
    data file to meta data in other db tables. The image table 
    arch_file_id is created when the image file and it's uvdata
    file are cataloged. This is only used for VLAPipeline images.
    The image arch_file_id is also loaded into the archive file location
    table.

  - common_file_id is used in the Image Table to relate image files
    with those calibrated uvdata files that contain data for several
    different images...



  I need to consider the most complicated situation :

   n raw VLA data files --> VLA Pipeline --> 1 or more calibrated VLA files,
   --> VLA Pipeline --> m calibrated VLA files (single source)
   --> one fits iamge file for each of the previous files

  How can I relates all of these files? What if the user starts with the
  raw data file, how can he find the calibrated data files and images??