Ticket #299 (closed design issue: suspended)

Opened 11 years ago

Last modified 7 years ago

Quantities in Object Catalog to describe time behavior

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

not applicable

Description (last modified by ktl) (diff)

What quantities do we need in the Object table to describe time behavior? Time averages? Scalegrams? More?

Change History

comment:1 Changed 11 years ago by ktl

  • Description modified (diff)

comment:2 Changed 11 years ago by TimAxelrod

  • Status changed from new to assigned

comment:3 Changed 11 years ago by jbecla

  • Component changed from unknown to dbSchema

comment:4 Changed 11 years ago by ktl

Tim will discuss with the science collaborations. The fields required are likely to change (grow) as experience with the database develops, so schema flexibility is mandatory here.

comment:5 Changed 11 years ago by ktl

Time behavior summary statistics are necessary for all Objects, not just ones determined (by whatever means) to be varying. Quantities for periodic variables may be quite different from those for transients.

comment:6 Changed 11 years ago by robyn

  • Milestone set to Post DC3

comment:7 Changed 10 years ago by jbecla

  • Milestone changed from Post DC3 to DC3b Apps DB Schema

comment:8 Changed 9 years ago by robyn

  • Owner changed from TimAxelrod to Tim Axelrod

Changing owner from 'TimAxelrod' to 'Tim Axelrod'

comment:9 Changed 8 years ago by ktl

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

Suspending for now, unlikely to be looked at in Winter2012.

comment:10 Changed 7 years ago by robyn

  • Milestone DC3b Apps DB Schema deleted

Milestone DC3b Apps DB Schema deleted

Note: See TracTickets for help on using tickets.