Welcome to iraf.net Friday, March 29 2024 @ 10:04 AM GMT
jmccormac001 |
07/25/2014 06:47PM (Read 1185 times)
|
|
|
Status: offline
Registered: 07/25/2014
Posts: 7
|
Hi Guys,
I am running IRAF 2.16 on OS X Mavericks as part of scisoft and get an error from ccdproc when trying to reduce some science images.
PANIC in `/usr/local/scisoft//packages/iraf/iraf/noao/bin.macintel/x_ccdred.e': Memory fwa has been corrupted
I used ccdproc to process the darks and flats with no issues. I can make a subset of the data available if that would help. The full set is quite big (~1700 images). Below is an lpar of ccdproc. Any ideas would be great.
Cheers
James
ccdred\$this->_split2($m[0]) show version
NOAO/IRAF V2.16
ccdred\$this->_split2($m[0]) lpar ccdproc
images = "HAT*" List of CCD images to correct
(output = "") List of output CCD images
(ccdtype = "") CCD image type to correct
(max_cache = 0) Maximum image caching memory (in Mbytes)
(noproc = no) List processing steps only?\n
(fixpix = no) Fix bad CCD lines and columns?
(overscan = no) Apply overscan strip correction?
(trim = no) Trim the image?
(zerocor = yes) Apply zero level correction?
(darkcor = yes) Apply dark count correction?
(flatcor = yes) Apply flat field correction?
(illumcor = no) Apply illumination correction?
(fringecor = no) Apply fringe correction?
(readcor = no) Convert zero level image to readout correction?
(scancor = no) Convert flat field image to scan correction?\n
(readaxis = "line") Read out axis (column|line)
(fixfile = "") File describing the bad lines and columns
(biassec = "") Overscan strip image section
(trimsec = "") Trim data section
(zero = "Zero.fits") Zero level calibration image
(dark = "Dark.fits") Dark count calibration image
(flat = "Flat.fits") Flat field images
(illum = "") Illumination correction images
(fringe = "") Fringe correction images
(minreplace = 1.) Minimum flat field value
(scantype = "shortscan") Scan type (shortscan|longscan)
(nscan = 1) Number of short scan lines\n
(interactive = no) Fit overscan interactively?
(function = "legendre") Fitting function
(order = 1) Number of polynomial terms or spline pieces
(sample = "*") Sample points to fit
(naverage = 1) Number of sample points to combine
(niterate = 1) Number of rejection iterations
(low_reject = 3.) Low sigma rejection factor
(high_reject = 3.) High sigma rejection factor
(grow = 0.) Rejection growing radius
(mode = "ql")
|
|
|
|
fitz |
07/25/2014 07:58PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
If you're trying to process the full list of 1700 images, then this may be related to the new filename template code. You can workaround it and go back to using the old code by doing
cl\$this->_split2($m[0]) reset use_new_imt = no
cl\$this->_split2($m[0]) flpr 0 # zero, not oh
If that doesn't fix the problem please post an image header.
|
|
|
|
jmccormac001 |
07/25/2014 08:36PM
|
|
|
Status: offline
Registered: 07/25/2014
Posts: 7
|
thanks very much for the pointers. I have changed the settings you suggested and everything works well now.
thanks again
|
|
|
|
jmccormac001 |
07/28/2014 03:33PM
|
|
|
Status: offline
Registered: 07/25/2014
Posts: 7
|
Hi again,
I've just realised that the command you suggested is not maintained after closing IRAF. I've added this to my login.cl file. Is that fine or is there a better way to keep the desired behaviour each time IRAF is started?
Cheers
James
|
|
|
|
fitz |
07/28/2014 03:45PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
The default value is set in the iraf$unix/hlib/zzsetenv.def file, you can edit it there to make the change permanent. Adding it to your login.cl (before the final 'keep' statement) is also fine but you need to remember to do this for every login.cl you might use.
|
|
|
|
jmccormac001 |
07/31/2014 11:03AM
|
|
|
Status: offline
Registered: 07/25/2014
Posts: 7
|
Hi,
Thanks for the information, I have set the value to 'no' in the .def file, thanks.
One final question I have another version of IRAF on a different machine (v2.15a). I looked for the use_new_imt keyword in the same file but it is not present. Is this something new in v2.16? Am I OK to process large numbers of images in 2.15a?
I'm developing a pipeline to run on the machine with v2.15a on my laptop which is running v2.16. Sorry for the confusion.
Cheers
James
|
|
|
|
fitz |
08/01/2014 04:58AM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
The new image template code was introduced in v2.16, using the use_new_imt=no trick means that v2.15 and v2.16 will process long image lists using the same (old version of the) code.
|
|
|
|
| |
|
Content generated in: 0.23 seconds |
|