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

Ensure integer dimension IDs are instrument-unique for LSST data

    Details

    • Templates:
    • Team:
      Architecture

      Description

      My understanding is that some of the integer Registry ID fields populated by astro_metadata_translator for some kinds of LSST data are not guaranteed to be globally unique - I think that's about date + sequence number IDs not being a unique exposure_id unless the control system is specified as well, but I'm hoping Tim Jenness can correct me if I'm wrong about that (while guessing what I'm actually thinking of).

      We need to fix this somehow - the easiest solution seems to be adding a few bits to represent whatever variable(s) are missing.  I'm pretty sure we don't have any requirement that these IDs be ordered with time, so hopefully that will make this pretty easy (it may be convenient for users to be able to express ranges of visits in time as ranges of integers, but I bet we'll mostly get that anyway, as in operations we're not going to be switching control systems much).

      This ticket does not need to include generating integer IDs for visits; I'll raise that on a new ticket (and I don't think it will need to involve astro_metadata_translator).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tjenness Tim Jenness
                Reporter:
                jbosch Jim Bosch
                Watchers:
                Jim Bosch, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel