On Thu, 18 Oct 2007, Mark Thompson wrote:
> Thanks for that - I'd forgotten the old trick of getting rid of the adam
> parameter files! As Joao says it is puana, but it could be that the parameter
> file has got corrupted, maybe when we switched from hokulei to puana. We'll
> check it out and let you know.
Hi Mark,
from the current stage of the investigation it would be handy to know if
Joao ran FITS2NDF using the Hokulei release as that may be when the
corruption was introduced. I'm guessing this would have gone unnoticed if
Joao didn't use the in= out= command-line parameters method until after
Puana was installed. In that case the bug fix in Puana wouldn't make any
difference.
Thanks,
Peter.
> On 18 Oct 2007, at 00:25, Malcolm J. Currie wrote:
>
>> This used to occur when an HDS V4 parameter file or GLOBAL file had
>> subsequently been written to by a HDS V3 task, and then you tried to
>> access it with an HDS V4 application. This bug was fixed in the puana
>> release (right Tim?). I believe a quick solution is move the parameter
>> file ~/adam/fits2ndf.sdf, or run HDSTOOLS hcopy command on that
>> parameter file if you don't want to lose its parameter values.
>>
>> If you are already using puana we'd be concerned that the bug was still
>> present, hence one reason for Tim's question. If you're running
>> the hokulei release, then perhaps you/Mark should consider installing
>> puana. The puana release has many new features.
>> http://starlink.jach.hawaii.edu/release/
>>
>> Malcolm Currie
>
>
> _______________________________________________
> Stardev mailing list
> [log in to unmask]
> http://mailman.jach.hawaii.edu/mailman/listinfo/stardev
>
--
Peter W. Draper, http://star-www.dur.ac.uk/~pdraper
|