Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Data Access
-
Labels:
-
Story Points:4
-
Epic Link:
-
Team:Alert Production
Description
Action item from the 2018-05-22/24 DMLT F2F
John Swinbank: Ensure pipelines code for regenerating images on demand is included in LDM-151, that an equivalent service is included in the appropriate DAX design documentation, and that both of them are included in the DM construction plan. 19 Jun 2018
(It's not clear from the above, but this is explicitly referring to the generation of PVIs)
Attachments
Issue Links
- is triggering
-
- In Progress
- links to
Activity
We discussed this at the DMLT call of 2019-12-02.
Main outcome of that is that Frossie Economou and Gregory Dubois-Felsmann are putting together a DMTN which will propose an architecture for generation of data products (not just PVIs) on demand. That will form the basis for further discussion at the DMLT, and subsequently for requesting inputs from T/CAMs.
In parallel, the new sizing model (DMTN-135) will have to make some assumptions about what is being stored and what is being computed. That will be clearly documented in the technote, and should ideally be parameterized so that it's easy to update the sizing model in response to architectural decisions.
This architectural question will be addressed in DMTN-139, an image service architecture note, being developed by me and Frossie under DM-22746.
Reassigning this to Wil O'Mullane, on the basis that it is primarily a managerial request (“ensure that it is included in the construction plan”), albeit one that has been blocked by the architectural issues on DM-22746 for a long time.
See DMTN-139 DM-22746
OOB, Tim Jenness points out that DMS-REQ-0069 “contains” some other requirements which specify that PVIs should contain a background model, a photometric zeropoint, a spatially-varying PSF, a WCS, the image data, a mask plane and a variance plane.