Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: obs_lsst
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Team:Data Facility
Description
As is in obs_lsstCam, the raw_visit table in registry.sqlite3 has the same per-file informarion as the raw table. But it should be just the visit information for optimization in obs_base.
I think this is to fix config.register.visit in obs_lsstCam config/ingest.py
Attachments
Issue Links
- is triggering
-
- Done
Activity
I tried ingesting some imsim data with the ticket branch and it looks fine to me. Instead of having one row for each file, this fix means one row for each visit in the raw_visit table in registry.sqlite3.
Are there other tests I should do?
Hsin-Fang Chiang
added a comment - I tried ingesting some imsim data with the ticket branch and it looks fine to me. Instead of having one row for each file, this fix means one row for each visit in the raw_visit table in registry.sqlite3.
Are there other tests I should do? Looks great
Thanks! Merged to master.
Hsin-Fang Chiang
added a comment - Thanks! Merged to master. 
Kian-Tat Lim pointed out that the four columns that should be in `raw_visit` are 'visit', 'filter', 'expTime', 'taiObs', as specified in https://github.com/lsst/obs_base/blob/master/python/lsst/obs/base/mapping.py#L243-L247
Currently obs_lsstCam has dateObs but not taiObs, so I'm using dateObs for now.