Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: proposed new table structures

...

  • Split center_position and observing_band fields
  • Retaining image size data (the VO _xel fields)
  • Add fields for spectral resolution, physical data description, and spacial region information
  • Determination and acquisition of time-domain information.

Below is the proposed new table structure for Images and Image Products in the metadata database.  There are 3 classes of columns below:  initial columns, new columns, columns adapted from (previous_column).  Depending on the design decisions and the behavior or CASA, some of these fields could be removed (t_xel, em_xel, pol_xel) if they they will be invariant. 

Images Database Table:

Column NameVO EquivalentSourceComments
target_nametarget_nameOBJECT Keyword
center_ra (center_position)s_raCenter of Ra Axis
center_dec (center_position)s_decCenter of Dec Axis
field_of_views_fovAverage of NAXISn*CRDELn of the Spacial Axes
spacial_regions_regionDerived from Spacial DataSTC-S String Defined in the TAP (Dowler, et al 2010)
ra_element_counts_xel1Relevent NAXISn Keyword
dec_element_counts_xel2Relevent NAXISn Keyword
spacial_resolutions_resolutionAverage of CRDELn of the Spacial Axes
image_stop_timet_max

Temporal domain information for an image is dependent upon the observation(s) used in its generation.  Some controlling process (Like Vlass Manager, whatever imaging pipeline we create, and any image manipulation software we use) will need to supply it. 

Since we are intending to store cubes as a collection of images, t_xel will can be removed and automatically returned as 1 for any individual image.

image_start_timet_min
image_integration_timet_exptime
temporal_element_countt_xel
frequency_min(observing_band)em_minMinimum of Spectral Axis


The spectral information is recoverable from the FITS header, and will identify the observing receiver(s), and total bandwidth processed for the image. 

frequency_max (observing_band)em_maxMaximum of Spectral Axis
spectral_resolutionem_res_powerSpectral CRDELn Keyword
spectral_element_countem_xelSpectral NAXISn Keyword
image_units

o_ucd

BTYPE & BUNIT KeywordsDescription of the physical quantity measured in the image
polarization_idpol_statesDeduced from NAXISn Keyword

More clarity is required for polarization information, as the exemplar files (Vlass quicklook images) have limited information available.  Some method of conveying  information about images (in CTYPE/CUNIT keywords, or via outside information) is required to get anything other than an overly simplistic assumption (NAXISn = 1 means Stokes I and NAXISn = 4 means Full Stokes Parameters). 

polarization_element_countpol_xelRelevent NAXISn Keyword
telescopeinstrument_nameTELESCOP KeywordThe observing instrument(s)
image_idobs_idautomatically generatedUnique Identifier for the Image
file_id
automatically generatedlink to information about the physical file
max_intensity


These values are can be determined from the data portion of the image file in conjunction with the BSCALE & BZERO keywords.  The library which is used for FITS interaction for ingestion can perform these calculations, but no information about the speed of results is yet available.

min_intensity

rms_noise

thumbnail
weblog, a PNG with identical name

...

Column NameVO EquivalentSourceComment
image_set_idobs_idautomatically generatedUnique Identifier for the Image Set
project_code
Required to facilitate Ingestion
configuration

This will need to hold the entire list used for the imaging. 
collection_nameobs_collection


calib_levelcalib_level
As defined by the VO in their 0-4 system


VO ObsCore Remaining Fields:

...