Ticket #297 (closed design issue: fixed)

Opened 12 years ago

Last modified 7 years ago

precision required by MOPS

Reported by: jbecla Owned by: TimAxelrod
Priority: normal Milestone:
Component: dbSchema Keywords:
Cc: Blocked By:
Blocking: Project: LSST
Version Number:
How to repeat:

not applicable


According to past discussions MOPS needs to know the precise time when an exposure was taken (with high precision). Revisit if such precision is really necessary given that each exposure is taken for 15 sec, and we will be cross-correlating MOPSPred catalog with new detections coming from a pair of exposures. If such precision would not be necessary, we could take advantage of pre-process phase and reduce mops-related computing during time critical step. If we do need such precision, we need to look into DATETIME types in various places in the precursor schema.

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 dbSchema

comment:3 Changed 11 years ago by ktl

After discussion with Tim, it appears that sub-second resolution will be required, since MOPS uses the location of the centroid of the Source, which is independent of exposure time. Second-resolution DATETIME fields in Object and/or Source may be sufficient if the sub-second resolution times are available through a join with Exposure.

comment:4 Changed 11 years ago by robyn

  • Milestone set to DC3 Apps Nightly Processing

comment:5 Changed 11 years ago by jbecla

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

We are going to support micro-sec precision in database, see ticket $405. This will be sufficient for MOPS.

comment:6 Changed 7 years ago by robyn

  • Milestone DC3a Apps Nightly Processing deleted

Milestone DC3a Apps Nightly Processing deleted

Note: See TracTickets for help on using tickets.