...
Most of this is laid out in detail in the Data Products Definition Document. As long as DiaSource measurement on the boundaries of an image area (e.g. CCD) are well-defined (TBD: how will edges be handled?), this process appears to be parallelizable.
- Insert DiaSources into the Level 1 Database.
- Associate the DiaSources with a (single) best-fit DiaObject or SSObject each. (TBD: exact association algorithm)
- For all associated DiaSources:
- Retrieve all past DiaSources.
- If associated with SSObject:
- Update SSObject with DiaSource properties. (TBD: not mentioned explicitly in LSE-163; can this wait for DayMOPS?)
- For all unassociated DiaSources:
- Do precovery forced measurement on 30-day difference image cache, creating DiaSources.
- TBD: Is this in real time or in 24 hours; LSE-163 is self-contradictory.
- TBD: Do we cache difference images or just calibrated images and parameters to recompute difference images?
- TBD: DiaSources include data from (differences of) snaps (diffFlux); those have to be cached as well
- Do precovery forced measurement on 30-day difference image cache, creating DiaSources.
- For all unassociated DiaObjects:
- Do forced measurement on difference image, calibrated image (for fpFlux), and difference of snaps (diffFlux), generating new DiaSource
- Update all DiaSources with their associated DiaObject identifier.
- Insert all normal and forced measurement DiaSources into Level 1 Database.
- For all DiaObjects:
- (Re)compute DiaObject measurements from DiaSources.
- Ingest DiaObjects into Level 1 Database: as one transaction, invalidate previous DiaObject row and insert new DiaObject row.
- Issue alert for each DiaSource with contents:
- Alert Identifier
- Level 1 Database Identifier
- DiaSource contents
- DiaObject or SSObject contents
- All previous DiaSources (including any new precovery forced measurements)
- Difference image cutout
- Template image cutout
- Image metadata
- Note that no calibrated image cutout is included.
- Package alerts into VOEvent or other relevant standard.
- Transmit VOEvents to public VOEvent brokers via pre-configured transport protocol and internal LSST filtering service.
- Internal LSST filtering service executes pre-configured per-user filters for each alert.
- If filter returns True, alert is forwarded to user via pre-configured transport protocol.