[fitsbits] start of Public Comment Period on the INHERIT convention

[Phil Hodge]

What I don't understand is why you need to "inherit" these keywords.  
For DECam you have a convention that some keywords are in the primary 
header and some are in an extension header.  Why not just read or update 
keywords in the headers that actually contain the keywords? That's what 
we at STScI do for HST data, in spite of the INHERIT keyword.  Explicit 
is good.

Phil

On 07/02/2015 12:08 PM, Frank Valdes wrote:
> I will respond with the DECam raw data from the telescope.  This is a good question for this discussion.  If this goes somewhere interesting I can look at the other NOAO mosaic cameras and the calibrated files.
>
> The keywords from the list at http://heasarc.gsfc.nasa.gov/docs/fcg/standard_dict.html that are inherited are:
>
> DATE-OBS, INSTRUME, OBJECT, OBSERVER, TELESCOP
>
> I might also mention a couple that are important but not on the list:
>
> EXPTIME, FILTER, RA, DEC
>
> There are no WCS keywords even from the advanced WCS papers or the TPV convention used by DECam.
>
> Frank
>
>
> On Jul 2, 2015, at 7:26 AM, Mark Calabretta wrote:
>
>> On Wed, 1 Jul 2015 11:30:12 -0700
>> Frank Valdes <valdes at noao.edu> wrote:
>>
>>> DECam is
>>> generating a huge amount of data (arguably the biggest optical data
>>> source in the world) on an almost daily basis.  The raw data is an
>>> MEF and uses INHERIT.  The calibrated data produces MEF with INHERIT.
>>> All mosaic data that NOAO has in its archive, -- >10 yrs of Mosaic, > 5
>>> yrs of NEWFIRM, DECAM -- is in this format.
>> Which keywords known to the FITS standards are these files inheriting?
>>
>>
>> Mark Calabretta
>
> _______________________________________________
> fitsbits mailing list
> fitsbits at listmgr.nrao.edu
> https://listmgr.nrao.edu/mailman/listinfo/fitsbits