 |
 |
On Sep 11, 2009, at 7:12 AM, David Berry wrote: > 2009/9/11 Tim Jenness <[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 doesn't seem like it would be a lot of work but I >> don't know >> much about the NDF library and it's not an immediate priority for >> David to >> implement this. It could do with some testing to make sure weird >> things >> don't start turning up in the history. >> >> I haven't been advocating trying to parse FITS HISTORY blocks. > > Sorry. When you said "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" I took this as meaning you wanted the FITS > history records to be propagated into the NDF history component. > No. I meant that the presence of HISTORY headers indicates that HISTORY is being recorded for the file already so disabling it would be odd. Anyhow, fits2ndf always turning on history is fine for the minute. -- Tim Jenness