iraf.net

When I edit the ccdproc pram file and save with ":q" and then look at the file (using lpar ccdproc or epar ccdproc) to make sure that the changes were saved, I get back the original file. Changes are not being saved. Any suggestions?

Do you see any messages such as "Unable to open parameter file" when saving the epar session? If so then your 'uparm' environment variable is pointing to a non-existant/non-writable directory. This is set in your login.cl file and is usually cleared up with a new MKIRAF.Otherwise, files are saved in the uparm directory in a name based on the package and task name, are you sure you're not somehow confusing the CCDPROC in IMRED with the same task in the e.g. QUADRED package? For example, a "which ccdproc" will tell you which is the 'active' package at the moment. Does doing an "unlearn ccdproc" and then resetting the parameters make any difference? Does quitting epar with ":wq" rather than just ":q" make a difference? Which version of IRAF and on what system is this happening?-Mike

MikeI am using PC-IRAF Revision 2.14 on a Mac (Tiger). The problem is occurring in mscred when saving ccdproc parameter files. Earlier in the week when I would try to save the edited parm file I would get the message ERROR Segmentation Violation. Doing an unlearn ccdproc solved this problem, but then the problem with saving changes occurred. Using your advice I tried ":w" which worked. However after doing the ":w" and then invoking ":q" I get the segmentation error again although it does not seem to have an impact. In other words it works with ":w" followed by ":q" although I get that segmentation violation error message. ccdproc does what I want it to do now!Thanks for your help,
David

David,Is the segfault happening when you execute the task (i.e. in the x_ccdred.e binary) or when you try to quit the epar (meaning it is in the CL itself)?? There are no known issues in either case, but this may be something Frank recognizes even if I don't. Also, did you get the IRAF and package from us or is this a SciSoft installation? Are you sure you're using the latest version of the mscred package or could this be an old installation?-Mike

Hi David and Mike,I don't recognize this problem. I suspect it is a problem with the CL. Since Mike didn't seem to mention this, try exiting eparm with your EOF key; e.g. ^D. I rarely use :w or :q. Instead I either save and exit with EOF or go directly to :go which does a save before executing. Any further clues would be helpful.Yours,
Frank Valdes