Ticket #414 (closed enhancement: fixed)

Opened 11 years ago

Last modified 7 years ago

Unique id generation

Reported by: jbecla Owned by: jbecla
Priority: normal Milestone:
Component: daf_persistence Keywords:
Cc: smm, rhl Blocked By:
Blocking: #472 Project: LSST
Version Number:
How to repeat:

not applicable

Description

Need to determine how to generate unique ids, then implement

Change History

comment:1 Changed 11 years ago by ktl

  • Status changed from new to assigned

comment:2 Changed 11 years ago by ktl

  • Owner changed from ktl to Tim Axelrod
  • Status changed from assigned to needinfo

This ticket does not specify which unique ids are to be generated. These may include:

  • visit ids
  • exposure ids
  • object ids
  • DIASource ids, source ids

There are several issues here:

  1. Who is producing each of these ids and what information is available when they are produced?
  2. How do we use the bits in the 32 or 64 bit words assigned to each id?

Initial thoughts on these issues have been written up in UniqueIds.

Once decisions have been made, implementation will be in the various Formatters (in afw, ap, detection, and meas) and in the lsst.ip.diffim.VisitMetadataStage (which should probably move to a different location).

comment:3 Changed 11 years ago by ktl

  • Cc smm, rhl added

comment:4 Changed 11 years ago by ktl

  • Blocking 472 added

comment:5 Changed 11 years ago by Tim Axelrod

  • Owner changed from TimAxelrod to jbecla
  • Status changed from needinfo to assigned

Updated UniqueIds with my proposal.

comment:6 Changed 10 years ago by jbecla

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

Per discussion DataAccWG telecon Feb 24, 2009, current scheme is fine for DC3a, with the exception of sdqa keys. This has been fixed [7583].

comment:7 Changed 7 years ago by robyn

  • Milestone DC3a MW DB MWI Improvements deleted

Milestone DC3a MW DB MWI Improvements deleted

Note: See TracTickets for help on using tickets.