2009/9/8 tim.jenness <[log in to unmask]>:
> Provenance tracking can be enabled automatically using an environment
> variable (AUTOPROV). No reason why HISTORY propagation can't have a AUTOHIST
> environment variable.
>
> For CONVERT I would be in favour of simply enabling HISTORY when the file is
> imported to NDF.
OK. I'll add this issue to my do list. Not sure when it will make its
way to the top though.
David
> Tim
>
> On Sep 8, 2009, at 6:32 AM, Malcolm J. Currie wrote:
>
>>> Thanks Dave. The reason I asked is that can be (very) frustrating to have
>>> created an NDF and later find that its history component is missing.
>>
>> At the time the NDF library was made, the available storage was orders of
>> magnitude less than now, so it was decided not to default to create the
>> HISTORY component. For spectra, HISTORY could dominate the file size.
>> These days some extra cruft or valuable processing history (depending on
>> your view) wouldn't be noticed.
>>
>>>> It may be possible to modify the NDF library so that it reads an
>>>> environment variable whenever a new NDF is created, saying whether
>>>> default History recording should be enabled in the new NDF or not.
>>
>> That's preferable to extra parameters. It would maintain the current
>> approach of placing the onus on the user. If you always want history
>> information recorded, just add the definition when setting up your
>> data-processing environment.
>>
>> I too have been frustrated wanting to check the processing history of
>> random NDFs only to find none. For serious processing I always
>> enable history recording, as does ORAC-DR.
>>
>> Malcolm
>
> --
> Tim Jenness
>
|