Ticket #472 (closed new functionality: fixed)

Opened 11 years ago

Last modified 7 years ago

Persisting exposure and visit metadata

Reported by: jbecla Owned by: ktl
Priority: normal Milestone:
Component: daf_persistence Keywords:
Cc: smm Blocked By: #414
Blocking: Project: LSST
Version Number:
How to repeat:

not applicable

Description

Need transient visit class and a formatter, need to modify exposure formatter. Discussed at DataAccWG 11/19/08

Change History

comment:1 Changed 11 years ago by ktl

  • Status changed from new to assigned

Actually, a DataProperty (or, now, PropertySet) is probably good enough. This is what was used for visit metadata in DC2.

comment:2 Changed 11 years ago by ktl

  • Blocked By 414 added

comment:3 Changed 10 years ago by ktl

  • Status changed from assigned to inTicketWork

Visit metadata is handled by the VisitMetadataStage and an OutputStage. Amp exposure metadata needs to be extended to handle new fields in the DC3a schema ([8996] creates the ticket branch in afw). CCD exposure metadata is more tricky, as writing it at the per-amp level causes multiple writes of the same data but the CCD information is only indirectly known at the visit/FPA level.

comment:4 Changed 10 years ago by ktl

We will write amp, CCD, and FPA ids as ampExposure metadata in the database. Changes to the schema and the formatter were needed. A separate stage, running in preprocess() so only once per visit, will be required to generate the ccdExposure metadata from the ampExposure metadata using a SQL query.

comment:5 Changed 10 years ago by ktl

  • Status changed from inTicketWork to assigned

Merged to trunk in [9822] and [9824]. Released in afw 3.3.16, cat 3.3, and ctrl_dc3pipe 3.3.2.

comment:6 Changed 10 years ago by ktl

  • Status changed from assigned to closed
  • Resolution set to fixed

comment:7 Changed 7 years ago by robyn

  • Milestone DC3a MW DB deleted

Milestone DC3a MW DB deleted

Note: See TracTickets for help on using tickets.