cl> reset use_new_imt = no
cl> flpr 0 (zero, not oh)
to defeat the new image expansion code and get back the old behavior, but otherwise your last report is what I would expect from v215 as well. Note you can also change the default setting of 'use_vo' in the hlib$zzsetenv.def file
Last edited by fitz on Sat Mar 24, 2012 8:19 pm; edited 1 time in total
The bug has been fixed and the distribution files were updated with the patch. I was planning to wait a few days to see what else is reported before building a proper patch update, for now I hope you won't mind downloading the v216 installation file and unpacking it once more. Thanks for the report.
mscred> ccdlist b
mscred> ccdproc b
b[im1]: Mar 25 13:20 Trim is [9:1016,9:2024]
b[im1]: Mar 25 13:20 Overscan is [1020:1035,9:2024], mean 1798.776
b[im2]: Mar 25 13:20 Trim is [9:1016,9:2024]
b[im2]: Mar 25 13:20 Overscan is [1020:1035,9:2024], mean 1798.086
ERROR: Cannot open file (tmp$ccdproc4264eP)
"sigscale=0.1, pclip=-0.5, grow=0., verbose=no)"
line 417: mscsrc$ccdproc.cl
called as: `ccdproc (images=b)'
mscred> ccdlist tmp$ccdproc4264eP
So I make:
mscred> reset use_new_imt = no
mscred> ccdproc b
b[im1]: Mar 25 13:25 Trim is [9:1016,9:2024]
b[im1]: Mar 25 13:25 Overscan is [1020:1035,9:2024], mean 1798.776
b[im2]: Mar 25 13:25 Trim is [9:1016,9:2024]
b[im2]: Mar 25 13:25 Overscan is [1020:1035,9:2024], mean 1798.086
b: Merge amplifiers
I used some dual-amp Mosaic data and tried to reproduce a problem with the latest V2.16. So could you please put an problem image in the ftp pub area and let me know. Also the parameter listing from "lpar mscred ccdproc" and any thing else you think might be appropriate, such as if you have a personalized instrument file.
Thanks for the data and the detailed log, I was able to reproduce the problem and found that aside from the earlier problem in the template expansion, the MSCRED package was accidently relinked with a pre-release version of the system containing a second bug. These have both now been fixed and verified and I was able to run your data with no problem without having to use the workaround.
You'll need to re-install both IRAF and MSCRED. I've built the IRAF patch but not the update script yet so simply get the new distribution file once again (sorry for the repeat installs). To update MSCRED (and all other packages), just do
I dowloaded the file "iraf.lnux.x86.tar.gz" from a link of:
and it did not work - the situation was the same. So I opened:
and found there "iraf.lnux.x86.tar.gz" (191660 KB, 03/23/2012, 01:25:00 AM) and "iraf.lnux.x86.gz" (195880 KB, 03/28/2012, 08:04:00 PM). I dowloaded the second one, made the installation and I was able to get the correct result. Thank you.
The problem is with PyRAF:
PyRAF 1.11 Copyright (c) 2002 AURA
Python 2.6.6 Copyright (c) 2001-2010 Python Software Foundation.
Python/CL command line wrapper
.help describes executive commands
--> displ a 1
--> displ a 1
--> ccdlist a
--> ccdproc a
Instrument (? for a list) ('instrmsc'):
Warning: Cannot open file (instrmsc)
Killing IRAF task `imheader'
Traceback (innermost last):
File "<CL script CL1>", line 1, in <module>
File "<CL script mscred.ccdproc>", line 192, in ccdproc
if (iraf.imaccess(Vars.outname + '') == yes):
IrafError: Error running IRAF task imheader
IRAF task terminated abnormally
ERROR (741, "Cannot open file (tmp$ccdproc12836cN)")
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum