2009/9/11 David Berry <[log in to unmask]>:
> 2009/9/11 Malcolm J. Currie <[log in to unmask]>:
>>> I agree that NDF history should now be enabled by default for everyone but
>>> I'd like a way for people to get the old behaviour through an environment
>>> variable.
>>
>> That's my view too. Change the default but give global control to the user.
>>
>> At present FITS2NDF is anomalous in that it enables history without user
>> control. I wanted to know your view on the bigger picture.
>
> True, it is anomalous, and should be brought into line as soon as the
> NDF changes are made. But for the moment, it is probably more useful
> having history support hardwired "on" rather than hardwired "off".
I've added a new tuning parameter called "AUTO_HISTORY" to the NDF
library (it can also be accessed using the environment variable
"NDF_AUTO_HISTORY"). If it is set non-zero, then the NDF_CREAT and
NDF_NEW functions (as used by apps that create new NDFs from scratch
rather than by propagation from an existing NDF) will add a History
component automatically to the output NDF.
I've consequently removed the hard-wired history creation from fits2ndf.
Malcolm - maybe you should add a comment to this effect to SUN/95 and SUN/55 ?
David
|