iraf.net

Hello; We have an update to IRAF FITS kernel that might take care of
this problem. We are short of manpower at this time and an IRAF patch
release timescale has not been decided yet.
If you need to have this problem resolve soon, please send a working
example using IRAF tasks only.Cheers,
Nelson ZarateOn 8/5/05, iraf <noaoiraf@gmail.com> wrote:
> ---------- Forwarded message ----------
> From: Help@stsci.edu <Help@stsci.edu>
> Date: Aug 3, 2005 10:00 AM
> Subject: CNSHD539006 Re: Problem with the task 'blot'
> To: iraf@noao.edu
>
>
> If you need to respond to this message please do so by replying to
> this message or create a new message with call number CNSHD539006
> included in the subject line.
>
> Current Call log entry :
>
> Martin,
>
> I was able to successfully reproduce your problem with your
> dataset. This revealed that the problem lies with the image header;
> more specifically, when I removed 106 out of the 108 sets of drizzle
> keywords from the header, everything worked fine. This not only
> indicates the problem, but demonstrates at least one workaround. The
> error actually occurs in the code when the header tries to get copied
> from the input image to the output image using the IRAF77 routine
> 'UHDCPY'. This header copy, as called by the IRAF version of 'blot'
> that you are using, relies on the IRAF FITS kernel for its basic
> functionality. We have seen other cases where there were limits in
> the FITS kernel which were exceeded, and perhaps this example
> demonstrates another such case. At any rate, there is nothing in
> 'blot' or any of the IRAF 'drizzle' code which could be modified to
> correct the problem; rather, it appears to lie in the underlying FITS
> image kernel.
>
> One workaround would be to edit the header down to remove most, or
> all?, of the sets of output drizzle keywords from the input image
> header prior to running 'blot', or creating a copy of the image which
> does not have the same full header. This would then successfully
> process through the IRAF version of 'blot'. MultiDrizzle/PyDrizzle
> does not suffer from this problem since it uses the callable interface
> to 'blot' and relies on PyFITS to manage all the image I/O. This may
> also be another option for your task development.
>
> At any rate, I am copying the IRAF team on this call, so they can
> review it for any potential FITS kernel bug fixes. Otherwise, if
> there is anything else I can do to help you work around this problem,
> just let me know.
>
> Cheers,
> Warren J. Hack
> SAA Project Lead
> Space Telescope Science Institute
> 3700 San Martin Drive
> Baltimore MD, 21218
> (410) 338-4943
>