Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Design Documents, Requirements Documents
-
Labels:
-
Team:Architecture
Description
In discussion with Kian-Tat Lim, it's clear that he regards it as a requirement that there be an association between Objects from different data releases (and this seems entirely reasonable to me, for what that's worth). However, this requirement is not documented anywhere. Please add it to the DPDD.
Attachments
Issue Links
- is triggering
-
DM-10554 Calculate impact of proposed DMS-REQ-0350
- Done
My main goal in trying to include L1 DiaObjects is to handle the case where an alert goes out in year N and someone wants to find out what the updated light curve is in DRX some years later. I don't really have a feel for how we map from a VOEvent alert containing a DiaSource ID and a DiaObject ID to a DiaObject ID from a later data release.
An Alert packet has a L1 DiaSource ID, DiaObject ID and (if you are lucky) and up to 6 Object IDs from the previous data release. The DiaObject has attached to it a light curve that is hopefully due to one of those 6 Object IDs but might be a light curve from multiple objects that are close to each other or none of them (a supernova from an object that was too faint before). So how do I go about finding the light curve from the current release? Do I just do a spatial search in the DiaObject table for the current release? Is the assumption that L1 cross-matching is a moving target and we should stay away from it? Is it possible that the L1 DiaObject no longer exists (say we decided that it was a composite and there were two distinct objects with different light curves)?
If we are ignoring L1 cross-matching, is my draft requirement text okay?