Ticket #295 (closed design issue: fixed)

Opened 12 years ago

Last modified 7 years ago

updating object if corresponding DIASource was deleted

Reported by: jbecla Owned by: Tim Axelrod
Priority: minor Milestone:
Component: database Keywords:
Cc: Blocked By:
Blocking: Project: LSST
Version Number:
How to repeat:

not applicable


What happens if MOPS decides that a DIASource, which we've already discarded at the Base Camp (because we keep only the last 10, and it is not part of these 10), was mis-associated to an object? How do we correct the values of the object without having the DIASource used to compute the original valuesd of the object?

Change History

comment:1 Changed 12 years ago by TimAxelrod

  • Status changed from new to assigned

comment:2 Changed 12 years ago by jbecla

  • Component changed from unknown to database

comment:3 Changed 12 years ago by ktl

After discussion with Tim, it seems likely that any updates to the Object will occur during DayMOPS processing at the Archive Center. Such updates will then have to be transmitted to the Base Camp before the next night.

comment:4 Changed 11 years ago by robyn

  • Milestone set to DC3 Apps Nightly Processing

comment:5 Changed 10 years ago by jbecla

  • Milestone changed from DC3a Apps Nightly Processing to Post DC3

comment:6 Changed 10 years ago by robyn

  • Owner changed from TimAxelrod to Tim Axelrod

Changing owner from 'TimAxelrod' to 'Tim Axelrod'

comment:7 Changed 8 years ago by ktl

  • Status changed from assigned to closed
  • Resolution set to fixed

Any updates to the Object will have to be incremental. A DIASource that is not in the Alert Production database can be retrieved from the up-to-date database.

comment:8 Changed 7 years ago by robyn

  • Milestone Post DC3 deleted

Milestone Post DC3 deleted

Note: See TracTickets for help on using tickets.