Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: afw
-
Labels:
-
Story Points:4
-
Epic Link:
-
Sprint:AP F21-1 (June)
-
Team:Alert Production
-
Urgent?:No
Description
VisitInfo needs to contain a visit-level identifier: visitId. This might be easiest to set after the gen3 butler is out (which will better codify the definition of visit).
Note: per the discussion below, the end result was an id field on VisitInfo, which could hold either the full focal plane exposure or visit identifier (depending on whether we have a snap, or combined visit).
Attachments
Issue Links
- blocks
-
DM-31773 Ensure visitInfo.id matches the butler visit key
- To Do
-
DM-29955 Add ExposureInfo id getter (replacement for VisitInfo.getExposureId())
- Done
-
DM-13943 Deprecate VisitInfo.getExposureId()
- Done
- duplicates
-
DM-13942 Remove exposureId and from VisitInfo and add visitId
- Invalid
-
DM-29097 Make visitInfo a property on exposure, not exposure.getInfo()
- Invalid
- is triggered by
-
RFC-459 Remove exposureId from VisitInfo and add visitId
- Implemented
- relates to
-
RFC-785 Move data ID -> integer packing state and logic out of butler
- Implemented
-
DM-13738 Remove exposureId from visitInfo
- Invalid
It would be very great if cameras that don't have an exposure/visit distinction (e.g. all of them, right now) had the same id for the raw and butler exposure and visit fields. I don't know how that all happens. We'll need a ticket to describe how that all should play out.