 |
 |
Just to clarify things, there are two issues being discussed here: 1) Whether fits2ndf should produce a History component in the output NDF that records the fact that fits2ndf has been run (and will also record all subsequent processing). 2) Whether, in addition to 1), fits2ndf should also read any history information from the input FITS file and add it into the History component of the output NDF. Item 1) is trivial, and I have already implemented it. Item 2) is much more work, and has not been implemented yet. David 2009/9/10 Jason Kirk <[log in to unmask]>: > tim.jenness wrote: >> >> On Sep 9, 2009, at 1:55 AM, Malcolm J. Currie wrote: >>> >>> The modification does seem different from normal behaviour. If I use >>> TRANDAT, ASCIN, CREFRAME, PSF, MAKESURFACE etc. where an NDF is created from >>> scratch, we don't enable history recording by default. There are all the >>> other x2NDF applications in CONVERT. It will only confuse or mislead users >>> if some tasks switch on history recording but others do not. We should be >>> consistent. > > As a user I assume that all NDFs have history records because I've been told > that NDF *can* have history records. It is rather "frustrating" to find the > HISTORY missing as the only time most people are going to notice it missing > is when they explicitly need it. It seem odd to me, again as a user, to have > a rather useful bit of functionality turned off by default. > >> A more middle ground fix requiring more work would be for HISTORY >> recording to be enabled if an incoming FITS file has any HISTORY headers at >> all. Else, since disable HISTORY if there is no previous history. > > How many fits files actually have HISTORY components? If its "not very many" > disabling history on the produced NDFs won't be any different than the > current status quo. > > -Jason >