Details
-
Type:
Story
-
Status: Won't Fix
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: daf_persistence, obs_base
-
Labels:None
-
Story Points:8
-
Epic Link:
-
Team:Data Access and Database
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
| Field | Original Value | New Value |
|---|---|---|
| Epic Link |
|
| Rank | Ranked higher |
| Assignee | Nate Pease [ npease ] |
| 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 @rhl suggests that maybe we need to standardize the registries. | 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 [~rhl] suggests that maybe we need to standardize the registries. |
| 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 [~rhl] suggests that maybe we need to standardize the registries. | 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 [~rhl] suggests that maybe we need to standardize the registries. |
| Team | Data Access and Database [ 10204 ] |
| Epic Link |
|
| Rank | Ranked higher |
| Epic Link | DM-4341 [ 21422 ] |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Epic Link | DM-4341 [ 21422 ] |
|
| Rank | Ranked higher |
| Rank | Ranked higher |
| Assignee | Nate Pease [ npease ] |
| Component/s | daf_persistence [ 10713 ] | |
| Component/s | butler [ 12317 ] |
| Component/s | obs_base [ 10719 ] |
Gen2 is dead.
| Resolution | Done [ 10000 ] | |
| Status | To Do [ 10001 ] | Won't Fix [ 10405 ] |
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).