imred.ccdred.flatcombine problem
Mike Reed wrote on May 26, 2010
When I try to run flatcombine, I get the following error:
ccdred> flatcomb flatsA00*.imh
ERROR: Cannot open image (flatsA0021.imh)
"ccdproc (ims, output="", ccdtype=ccdtype, noproc=no)"
line 38: ccdred$flatcombine.cl
called as: `flatcombine (input=flatsA00*.imh)'
and then what's really weird is the flat image is deleted. I can display the images, prior to running the command, and so I know the pix files are okay and images are valid. I have ccdproc set to use an overscan, and so NOT do bias or dark correction. flatcombine is set to process the images before combining. Each image is 2-d in the header.
epar flatcombine looks like this:
input = fl*.imh List of flat field images to combine
(output = Flat) Output flat field root name
(combine= average) Type of combine operation
(reject = avsigclip) Type of rejection
(ccdtype= flat) CCD image type to combine
(process= yes) Process images before combining?
(subsets= no) Combine images by subset parameter?
(delete = no) Delete input images after combining?
(clobber= no) Clobber existing output image?
(scale = mode) Image scaling
......
and epar ccdproc looks like this:
images = List of CCD images to correct
(output = ) List of output CCD images
(ccdtype= object) CCD image type to correct
(max_cac= 0) Maximum image caching memory (in Mbytes)
(noproc = no) List processing steps only?
(fixpix = yes) Fix bad CCD lines and columns?
(oversca= yes) Apply overscan strip correction?
(trim = yes) Trim the image?
(zerocor= no) Apply zero level correction?
(darkcor= no) Apply dark count correction?
(flatcor= yes) Apply flat field correction?
(illumco= no) Apply illumination correction?
(fringec= no) Apply fringe correction?
......
......
(readaxi= line) Read out axis (column|line)
(fixfile= fixpix.txt) File describing the bad lines and columns
(biassec= [3075:3104,2:31]) Overscan strip image section
(trimsec= [110:2757,1:31]) Trim data section
(zero = ) Zero level calibration image
(dark = ) Dark count calibration image
(flat = ) Flat field images
........
Any ideas? Thanks for the help.
Mike
ccdred> flatcomb flatsA00*.imh
ERROR: Cannot open image (flatsA0021.imh)
"ccdproc (ims, output="", ccdtype=ccdtype, noproc=no)"
line 38: ccdred$flatcombine.cl
called as: `flatcombine (input=flatsA00*.imh)'
and then what's really weird is the flat image is deleted. I can display the images, prior to running the command, and so I know the pix files are okay and images are valid. I have ccdproc set to use an overscan, and so NOT do bias or dark correction. flatcombine is set to process the images before combining. Each image is 2-d in the header.
epar flatcombine looks like this:
input = fl*.imh List of flat field images to combine
(output = Flat) Output flat field root name
(combine= average) Type of combine operation
(reject = avsigclip) Type of rejection
(ccdtype= flat) CCD image type to combine
(process= yes) Process images before combining?
(subsets= no) Combine images by subset parameter?
(delete = no) Delete input images after combining?
(clobber= no) Clobber existing output image?
(scale = mode) Image scaling
......
and epar ccdproc looks like this:
images = List of CCD images to correct
(output = ) List of output CCD images
(ccdtype= object) CCD image type to correct
(max_cac= 0) Maximum image caching memory (in Mbytes)
(noproc = no) List processing steps only?
(fixpix = yes) Fix bad CCD lines and columns?
(oversca= yes) Apply overscan strip correction?
(trim = yes) Trim the image?
(zerocor= no) Apply zero level correction?
(darkcor= no) Apply dark count correction?
(flatcor= yes) Apply flat field correction?
(illumco= no) Apply illumination correction?
(fringec= no) Apply fringe correction?
......
......
(readaxi= line) Read out axis (column|line)
(fixfile= fixpix.txt) File describing the bad lines and columns
(biassec= [3075:3104,2:31]) Overscan strip image section
(trimsec= [110:2757,1:31]) Trim data section
(zero = ) Zero level calibration image
(dark = ) Dark count calibration image
(flat = ) Flat field images
........
Any ideas? Thanks for the help.
Mike
Mike Reed wrote on May 26, 2010
oops, I figured that out. In my login.cl imtype=imh was commented out. Once I uncommented, it worked fine. Bizarre.
Mike
Mike
Mike Fitzpatrick wrote on May 26, 2010
By way of explanation:
There was a change starting with V2.11 in how the output type is created with respect to the input. In V2.10 and before, the behavior was that the output of a task was of the same image type as the input. In V2.11 the output type is set by the "imtype" variable and starting with v2.13 the default imtype was changed from 'imh' to 'fits'. In the past the problem was that people had imtype=imh and were trying to use FITS files, in your case it is the opposite situation but the same problem.
Some tasks still get confused if the image type changes during processing.
There was a change starting with V2.11 in how the output type is created with respect to the input. In V2.10 and before, the behavior was that the output of a task was of the same image type as the input. In V2.11 the output type is set by the "imtype" variable and starting with v2.13 the default imtype was changed from 'imh' to 'fits'. In the past the problem was that people had imtype=imh and were trying to use FITS files, in your case it is the opposite situation but the same problem.
Some tasks still get confused if the image type changes during processing.
Last post on May 26, 2010