Project: datamanagement
Issue DM-1939: Define instrumental inputs to PSF estimation
Define inputs needed to build physically-motivated PSF models beyond what's contained in the image data and the current CameraGeom. This includes: - static engineering data from lab tests - slowly-varying engineering data (measured daily, weekly, etc.) - per-visit auxiliary data from telescope and camera (including, but not limited to wavefront sensor data). The focus here should be on APIs, not the technical details of the data; we want to define class hierarchies (perhaps some polymorphic ones) that can be used to pass this data around in the future. We also want to identify and characterize any preprocessing that needs to be done before they can be used for PSF estimation. Experts who should be consulted include [~gpdf] (who is in charge of making sure the camera and telescope interfaces to DM are well-defined), camera/telescope people he recommends, and people from the LSST DESC who have worked on physical PSF estimation and know something about the things they'll want (e.g. Michael Schneider, Aaron Roodman). This is essentially a requirements-gathering task, so the output should be a confluence page, not code.
Story points: 10