TABLE  EpochFrameStatus

Contains details of which image(s) are used in epochs in mergelogs

This tracks which frames are assigned - necessary for the automated curation
and doesn't cause conflicts between productIDs from RequiredStack and
RequiredMergeLogMultiEpoch, which both may apply to a single frame, and
therefore


Required constraints:
  • Primary key is (programmeID,multiframeID,extNum)
  • (programmeID) references Programme(programmeID)
  • (multiframeID,extNum) references MultiframeDetector(multiframeID,extNum)

NameTypeLengthUnitDescriptionDefault ValueUnified Content Descriptor
programmeIDint4 WSA assigned programme UID {image primary HDU keyword: HIERARCH ESO OBS PROG ID}-99999999meta.id
multiframeIDbigint8 the UID of the relevant multiframe obs.field
cuEventIDint4 UID of curation event giving rise to this record meta.bib
productIDbigint8 Product ID of deep stack frame (or intermediate stack if used as a deep stack). {image primary HDU keyword: PRODID}-99999999 
releaseNumsmallint2 Release number of deep stack frame (or intermediate stack if used as a deep stack). {image primary HDU keyword: RELNUM}-9999 
productTypevarchar16 Product type (stack,tile,mosaic)NONE 
extNumtinyint1 the extension number of this frame meta.number
Total length43