Ticket #289 (closed design issue: fixed)

Opened 11 years ago

Last modified 7 years ago

Persisting extended parameters

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

not applicable

Description

Here are columns that we should add to the Object table based on the LSST common queries: extinction_r, mE1_r, mE2_r, mRrCc_r, mCr4_r, isoAGrad_r, isoBGrad_r, isoPhi_r, deRed_r, deRed_ri, petroR50, petroR50_r, q_r, petrorad_u, petrorad_g, fwhmA, fwhmB, fwhmTheta. Likely this is not going to be good enough, so... what extended parameters should we really keep in the Object Catalog and in the Source Catalog?

Change History

comment:1 Changed 11 years ago by jbecla

  • Component changed from unknown to dbSchema

comment:2 Changed 11 years ago by rhl

  • Owner changed from Robert Lupton to rhl

comment:3 Changed 11 years ago by rhl

  • Status changed from new to assigned

comment:4 Changed 11 years ago by jbecla

  • Milestone changed from DC3 Design to DC3a Apps DB Schema

comment:5 Changed 10 years ago by rhl

  • Owner changed from rhl to jbecla

We should be able to define the DC3a schema after the 2009-02-09 Davis meeting, but I do not believe that this will be the same as the final LSST schema; I imagine that you don't either.

comment:6 Changed 10 years ago by jbecla

  • Milestone changed from DC3a Apps DB Schema to DC3b Apps DB Schema

The Source/DIASource schema was extensively revised, (big thanks to Martin), it seems we are ok for DC3a, changing the milestone to DC3b

comment:7 Changed 8 years ago by jbecla

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

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