Ticket #649 (closed enhancement: fixed)

Opened 10 years ago

Last modified 7 years ago

cleanup types for db columns representing uncertainty

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

not applicable


Currently *Err column are a mixture of FLOATs (120 columns) and DOUBLEs (50 columns). We will never need more than 32 bits per column to capture uncertainty, and the uncertainty numbers are "very uncertain", so FLOAT is always sufficient. We should switch all *Err columns to float. Discussed at DataAccWG telecon Feb 17, 2009

Change History

comment:1 Changed 10 years ago by jbecla

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

Done in [7488]

comment:2 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.