[fitsbits] SDFITS file header vs extension header

[Bob Garwood]

On 5/14/2014 4:47 PM, Kuiper, Thomas (3266) wrote:
> Excellent!  Does that mean we can expect ASAP and GBTIDL to respect this convention, Bob?
I can't speak for ASAP and I'll add this to my GBTIDL todo list, but I 
wouldn't count on it any time soon.

Bob

>
> Tom
>
> Sent from my iPhone
>
>> On May 14, 2014, at 1:43 PM, "Rob Seaman" <seaman at noao.edu> wrote:
>>
>> The INHERIT convention addresses this:
>>
>>     http://fits.gsfc.nasa.gov/registry/inherit.html
>>
>> though not, I think, pertinent to SDFITS per se.
>>
>> Rob
>> —
>>
>>> On May 14, 2014, at 1:30 PM, Kuiper, Thomas (3266) <kuiper at jpl.nasa.gov> wrote:
>>>
>>> You're right. I was focused too narrowly on the data acquisition stage.  Thanks.
>>>
>>> Tom
>>>
>>> p.s. but should a reader not pick up relevant metadata wherever they live, and writers smart enough to avoid repetition?
>>>
>>> Sent from my iPhone
>>>
>>>> On May 14, 2014, at 1:24 PM, "Bob Garwood" <bgarwood at nrao.edu> wrote:
>>>>
>>>> Actually, combining data from different PROJIDs does happen.
>>>>
>>>>> On 5/14/2014 4:06 PM, Tom Kuiper wrote:
>>>>> What's the logic behind where to put metadata?  For example, why would
>>>>> these not go into the primary header:
>>>>> TELESCOP, site data, PROJID.  In fact, anything common to all extension
>>>>> in the file.
>>>>>
>>>>> Thanks
>>>>>
>>>>> Tom
>>>> _______________________________________________
>>>> fitsbits mailing list
>>>> fitsbits at listmgr.cv.nrao.edu
>>>> http://listmgr.cv.nrao.edu/mailman/listinfo/fitsbits
>>> _______________________________________________
>>> fitsbits mailing list
>>> fitsbits at listmgr.cv.nrao.edu
>>> http://listmgr.cv.nrao.edu/mailman/listinfo/fitsbits