View on GitHub

IRAF Community Distribution

IRAF maintained by the community

Home | Installation | Packages | X11IRAF | PyRAF | Forum

clobbering problem

Aniello Grado wrote on Aug 04, 2003

Hi all,

I have a problem with imcombine. I'm combining some 300 images 1kx1k, if I
don't ask to produce a pixel list output, it works fine, otherwise I got a
"Warning: Operation would overwrite existing image (pl_2.pl)" also if I set
clobber = yes and I remove the .pl file before to run imcombine. How can I
deal with this problem? I am using:

NOAO PC-IRAF Revision 2.11.3 EXPORT Mon Sep 11 10:30:26 MST 2000
    This is the EXPORT version of PC-IRAF V2.11 supporting most PC systems.

Thanks in advance for the answer

Aniello

>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<
 Dr. Grado Aniello

Osservatorio Astronomico di
Capodimonte
Via Moiariello, 16
80131 Napoli Italy
tel. +39 081 5575 547
fax. +39 081 456710
>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<

Frank Valdes wrote on Aug 11, 2003

Hello Aniello,

This is a bug in the V2.11.3 version of IRAF.  The buglog is given below.
The workaround you are looking for is "reset imclobber=yes".  This is
for images while "clobber" is for non-images.

Note that mail to iraf@noao.edu will insure a more timely response.

Yours,
Frank Valdes

NUMBER: 529
MODULE: imcombine
SYSTEM: V2.11-V2.11.3
DATE:   Mon Aug 11 12:13:29 MST 2003
FROM:   valdes

BUG:    When specifying a bad pixel mask output with the "plfile" parameter
        it is possible to get

            Warning: Operation would overwrite existing image (<name>.pl)

        This occurs when a problem is encountered and the task tries again
        with a different parameters to avoid the problem.  The bug is that
        the pl file is not deleted before tryng again.  This retry behavior
        occurs for several reasons, most commonly when the number of images
        being combined exceeds a limit of about 250 images.  The workaround
        is to "reset imclobber=yes".  Note that this resets the clobber
        policy for all IRAF tasks so one should probably reset it to "no"
        after working around this IMCOMBINE bug.

STATUS: This is fixed in V2.12.

Last post on Aug 11, 2003