Ticket #291 (closed design issue: fixed)

Opened 11 years ago

Last modified 7 years ago

Tracking systematic errors in unreleased fits headers

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

not applicable

Description

How are we going to fix systematic errors in unreleased fits header? Will we update such fits headers? Create a new copy of a fits header? Track changes via database and don't touch the original fits header?

Change History

comment:1 Changed 11 years ago by TimAxelrod

  • Status changed from new to assigned

comment:2 Changed 11 years ago by jbecla

  • Component changed from unknown to database

comment:3 Changed 11 years ago by robyn

  • Milestone set to Post DC3

comment:4 Changed 11 years ago by jbecla

  • Summary changed from Tacking systematic errors in unreleased fits headers to Tracking systematic errors in unreleased fits headers

comment:5 Changed 11 years ago by TimAxelrod

I not sure I understand the scenario here. My guess: some time after operations begin, we discover a metadata item is systematically correct, eg the temperature sensor data associated with "Temp1" is actually coming from a different sensor "Temp17". If that's the issue, I'd say we should go into the database and correct all those metadata items, and I'm assuming that the provenance framework will give us some help in recording what we have done.

The Fits file issue is separate, I think. We are viewing this as an external format created by the formatters, and my assumption is that our internal storage of image pixels will be independent of Fits - but that still needs to be resolved.

comment:6 Changed 9 years ago by robyn

  • Owner changed from TimAxelrod to Tim Axelrod

Changing owner from 'TimAxelrod' to 'Tim Axelrod'

comment:7 Changed 8 years ago by ktl

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

I think Tim's answer is sufficient here. FITS delivered to the end user of course has the corrected metadata (derived from the database). If FITS is persisted to disk, that is an internal issue.

comment:8 Changed 7 years ago by robyn

  • Milestone Post DC3 deleted

Milestone Post DC3 deleted

Note: See TracTickets for help on using tickets.