...
- 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 DiaSource is associated with an SSObject:
- Update SSObject with DiaSource properties. (TBD: not mentioned explicitly in LSE-163; can this wait for DayMOPS?)
- If DiaSource is not associated:
- Create a new DiaObject
- 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 forced measurement on difference image, calibrated image (for fpFlux), and difference of snaps (diffFlux), generating new DiaSource
- Note that this is a normal DiaSource, not a ForcedDiaSource (which does not exist any more), but it may need to have a flag set to indicate that it was forced.
- (Re)compute DiaObject measurements from DiaSources.
- 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.
- If filter returns True, alert is forwarded to user via pre-configured transport protocol.
- Do precovery forced measurement on 30-day difference image cache, creating additional forced DiaSources.
- The note above about forced DiaSources applies here as well.
- 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