Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-8170

Catalogs should have a version number

    Details

    • Type: Story
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: afw
    • Templates:
    • Team:
      Data Release Production

      Description

      At present when a catalog is persisted that persistence does not seem to include a version number. It would be really nice to have that stored in such a way that the version could be determined before reading in the data (thus giving the reading code a chance to adapt to the version of the catalog being read).

      In some cases we have code that saves version information as a FITS header key, but that technique doesn't always work. This came up in the context of saving VisitInfo and offering backwards compatibility for ExposureInfo tables, and again recently in DM-8147, reading old PSF models.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                rowen Russell Owen
                Watchers:
                Jim Bosch, Russell Owen
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Summary Panel