Welcome to iraf.net Wednesday, May 15 2024 @ 07:39 PM GMT


 Forum Index > Archives > Sitemail Archives
 ccdproc trouble under Linux
   
Anonymous: Guest
 08/16/2005 10:24PM (Read 2880 times)  



From: Jim Scotti <jscotti@pirl.lpl.Arizona.EDU>
Date: July 20, 2005 12:33:38 PM MST
To: iraf@noao.edu
Subject: ccdproc trouble under Linux
I'm running IRAF under Linux (Fedora Core 2) and ran into problems
while using ccdproc under the mosaic extension. I've created a dark
and a flat frame using darkcombine and flatcombine, both under the
msc package and need to process my science images. We are using a
Site 2K chip with 4 quad readout and stored using the mosaic
extensions. Here is the "epar ccdproc" output followed by the output
the task gives me after a moment or two. I'll also put the logfile
output at the end. I've checked the obvious, namely permissions on
the directory and files. I'm running in my own account on the
machine. I'm stumped at the moment and thinking about kludges (like
doing my own dark and flat correction with imarith....).======= epar ccdproc: I R A F
Image Reduction and Analysis Facility
PACKAGE = mscred
TASK = ccdprocimages = *.fits List of Mosaic CCD images to process
(output = ) List of output processed images
(bpmasks= ) List of output bad pixel masks
(ccdtype= ) CCD image type to process
(noproc = no) List processing steps only?(xtalkco= no) Apply crosstalk correction?
(fixpix = no) Apply bad pixel mask correction?
(oversca= no) Apply overscan strip correction?
(trim = no) Trim the image?
(zerocor= no) Apply zero level correction?
(darkcor= yes) Apply dark count correction?
(flatcor= yes) Apply flat field correction?
(sflatco= no) Apply sky flat field correction?
(split = no) Use split images during processing?
(merge = no) Merge amplifiers from same CCD?(xtalkfi= ) Crosstalk file
(fixfile= ) List of bad pixel masks
(saturat= INDEF) Saturated pixel threshold
(sgrow = 0) Saturated pixel grow radius
(bleed = INDEF) Bleed pixel threshold
(btrail = 20) Bleed trail minimum length
(bgrow = 0) Bleed pixel grow radius
(biassec= ) Overscan strip image section
(trimsec= ) Trim data section
(zero = ) List of zero level calibration images
(dark = /data/jscotti/calib/dark150.fits) List of dark count
calibration image
(flat = /data/jscotti/calib/Flat5.fits) List of flat field images
(sflat = ) List of secondary flat field images
(minrepl= 1.) Minimum flat field value(interac= no) Fit overscan interactively?
(functio= minmax) Fitting function
(order = 1) Number of polynomial terms or spline
pieces
(sample = *) Sample points to fit
(naverag= 1) Number of sample points to combine
(niterat= 1) Number of rejection iterations
(low_rej= 3.) Low sigma rejection factor
(high_re= 3.) High sigma rejection factor
(grow = 0.) Rejection growing radius
(fd = )
(fd2 = )
(mode = ql)
======= task output:List of Mosaic CCD images to process (*.fits):
Warning: Cannot access template file or cannot make copy file (Raw//
data/jscotti/calib/Flat5.fits)
Warning: cannot rename `tmp353mb.fits' -> `/data/jscotti/calib/
Flat5.fits'
ERROR: Error processing 07.01.fits======= logfile:/data/jscotti/calib/Flat.fits[amp0]: Jul 18 16:09 Dark is /data/
jscotti/calib/dark150.fits[amp0], scale 1.2
/data/jscotti/calib/Flat.fits[amp1]: Jul 18 16:09 Dark is /data/
jscotti/calib/dark150.fits[amp1], scale 1.2
/data/jscotti/calib/Flat.fits[amp2]: Jul 18 16:09 Dark is /data/
jscotti/calib/dark150.fits[amp2], scale 1.2
/data/jscotti/calib/Flat.fits[amp3]: Jul 18 16:09 Dark is /data/
jscotti/calib/dark150.fits[amp3], scale 1.2=======Thanks!Jim.Jim Scotti
Lunar & Planetary Laboratory
University of Arizona
Tucson, AZ 85721 USA http://www.lpl.arizona.edu/
~jscotti/From: Frank Valdes <valdes@noao.edu>
Date: July 27, 2005 12:08:58 PM MST
To: Jim Scotti <jscotti@pirl.lpl.Arizona.EDU>
Subject: Re: ccdproc trouble under Linux
Hi Jim,This is a highly unusual error message. I have never seen it before
though it was easy enough to find where it is being triggered. This
is happening at the lowest level of IRAF in Unix calls to determine
the status flags for the file being copied and to create a zero
length copy in preparation for doing the copy . Who is wanting to
make the copy I can't tell but I think it might be in the FITS
handling code.Anyway, about all I can think of, other than something weird with
Fedora Core 2, is that you have some kind of permissions problem with
the directory you are in. I would suggest you move to a new
directory, maybe on a different disk, and see if the problem goes
away. If it does not I think we would have to log into your machine
and reproduce this in-situ.I'm sorry for the problem and the delay in replying.Yours,
Frank
From: Jim Scotti <jscotti@pirl.lpl.Arizona.EDU>
Date: August 4, 2005 9:37:15 AM MST
To: Frank Valdes <valdes@noao.edu>
Subject: Re: ccdproc trouble under Linux
Hi Frank,
Sorry to be so slow in responding - we were out on vacation. The first thing I checked were permissions and everything seemed
fine - a+rwx and I was owner. Permissions on the Raw directory are
drwxrwxrwx and permissions on the tmp files are -rw-rw-r-- which
seems correct. I also copied the files over into my home directory
(I had them on a bigger data disk for processing) and got the exact
same error message. I haven't tried running the processing on our
Slowlaris machines yet. I bet we have a different version (not to
mention differences between the Solaris and Linux versions of IRAF).
I'd be happy to either come over and ssh into the machine so you can
see things first hand or if you'd like to come over here at your
convenience.Jim.[I went to see Jim. Before I went I looked at the report again and
noticed that
it was complaining about Raw//data/jscotti/calib/Flat5.fits. This
points to the
fact that the calibration specified has an absolute path. CCDPROC is
trying
to process the calibration (because it was created by hand) and when
it tries
to make the backup copy by prepending the backup directory it is a
bad path.
So this is a bug in the implementation of CCDPROC and the workaround is
to copy the calibrations to the working directory and not use an
absolute path.
In talking to Jim I also told him how to edit the header so CCDPROC
would not
process the hand-processed calibrations. FV 8/16/05]

 
   

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login