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

Port registryInfo.py from obs_subaru into Butler

    Details

    • Type: Story
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: daf_persistence, obs_base
    • Labels:
      None

      Description

      in butler (probably butlerUtils), users would like the ability to dump info from a repository's sqlite registry to text (console output). This is already implemented in obs_subaru/.../registryInfo.py, and basically just needs to be ported to butler in a sensible place. There are a few cases that assume certain columns are present and we need either to make the script more generic, or Robert Lupton suggests that maybe we need to standardize the registries.

        Attachments

          Activity

          Hide
          ktl Kian-Tat Lim added a comment -

          Standardizing registries could require limiting a lot of the flexibility that the Butler was intended to provide. It is not clear if that flexibility is still desirable, however.

          There are definitely some things in registryInfo.py that are very HSC-specific. A more generic version should probably dump all columns present in the "raw" table (or allow some means of specifying a list of columns to include or exclude), possibly with some summarization. I'm not sure that the max() functions are always appropriate.

          And we should likely use the lsst.db package and SQLalchemy for database portability, if that is necessary (otherwise just use sqlite as the CameraMapper's registries do internally).

          Show
          ktl Kian-Tat Lim added a comment - Standardizing registries could require limiting a lot of the flexibility that the Butler was intended to provide. It is not clear if that flexibility is still desirable, however. There are definitely some things in registryInfo.py that are very HSC-specific. A more generic version should probably dump all columns present in the "raw" table (or allow some means of specifying a list of columns to include or exclude), possibly with some summarization. I'm not sure that the max() functions are always appropriate. And we should likely use the lsst.db package and SQLalchemy for database portability, if that is necessary (otherwise just use sqlite as the CameraMapper's registries do internally).

            People

            • Assignee:
              Unassigned
              Reporter:
              npease Nate Pease
              Watchers:
              Hsin-Fang Chiang, Kian-Tat Lim, Nate Pease
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Summary Panel