Short Description
The VLASS Products should form a collection in the archive with additional meta-data.
Current Status
<add link to JIRA Epic here>
Epic Ticket Status
<Add pie chart of tickets in epic here>
Project Charter
Long Description
- Quality Assurance flags should use the standard QA mechanism in the archive.
VLASS Specific Meta-Data
The following meta data shall be available for all VLASS Products:
Product Type: Quick Look or Single Epoch Calibration
| Meta-Data | Values | Comments | |
|---|---|---|---|
| Epoch | 1.1, 1.2, ... Cumulative | The epoch in which the data was taken, the underlying data should specify which half as well (e.g. Epoch 1.1 or Epoch 1.2) although this may not be presented to external users. | |
| Product Type | Calibration | Quick Look Single Epoch | |
| Image | Quick Look Single Epoch Cumulative Coarse Cube Fine Cube | Coarse Cubes are a special case and need additional consideration in their treatment. | |
| Tile | The tile identifier for the products | ||
Requirements
Must have
- Minimal image metadata consistent with IVOA Obscore 1.0
- Metadata describing links between EBs, the calibrations and images produced from them for provenance purposes. E.g. each image should have metadata naming the one or more EBs and calibrations that were used to make it.
- For "cubes" individual planes need metadata linking them to a single overall cube product.
Should have
- Standard image metadata consistent with IVOA Obscore 1.1
- Cumulative products should contain the dates of all observations that were included
Could have
- <Things that are nice to have but not strictly required>
Will not have
- <Things that explicitly will not be included>
Implementation Plan.
Milestones
- CoDR Passed: Project charter accepted
- PDR Passed: Requirements specified and accepted
- CDR Passed: Design specified and accepted
Release Plan:
Project Calendar
<Add calendar for epic here>