Welcome to iraf.net Monday, May 13 2024 @ 04:10 PM GMT
nicand |
08/10/2007 09:04PM (Read 5787 times)
|
|
|
Status: offline
Registered: 08/10/2007
Posts: 5
|
Hello everyone,I just finished installing IRAF onto Fedora Core 7 and I am getting the error below every time I try to run a command.cl> imhead Hreg13.fits PANIC in `/iraf/iraf/bin.linux/x_images.e': Memory has been corrupted
Unable to open parameter file `uparm$imlimhear.par'.Any advice on what I can do to fix this? Thank you
nicand
|
|
|
|
fitz |
08/10/2007 09:04PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
The linux v2.6 kernels changed the way memory is allocated and so it is necessary to remove a stacksize limit. In v2.12.2 and later this should be done automatically by the hlib$cl.csh script, please check that file for a line such as[code:1:5ee932143c]limit stacksize unlimited[/code:1:5ee932143c]If it is missing you can add it at the top of the script so it will be executed automatically. You can put this is your .cshrc or on the commandline before logging into IRAF, if you use the Bash shell the command is "ulimit -s unlimited".This assumes you get the same error using e.g. the dev$pix test image, if it happens only with this image it may be data-related and indicate a corrupted FITS file. Cheers,
-Mike
|
|
|
|
nicand |
08/10/2007 09:04PM
|
|
|
Status: offline
Registered: 08/10/2007
Posts: 5
|
Thank you, that worked GREAT for the memory corruption error. However, I am still getting the below error. Is it possible I am missing some parameter files? cl> imhead Hreg13.fits
Hreg13.fits[512,1024][real]:
Unable to open parameter file `uparm$imlimhear.par'.nicand
|
|
|
|
fitz |
08/10/2007 09:04PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
That basically means that either you don't have a uparm directory (e.g. didn't do a MKIRAF), the 'uparm' variable points to the wrong one (e.g. you copied a login.cl from someplace else), or you don't have permission to write to it (e.g. you logged into the CL through the 'iraf' account directory and can't write to the uparm dir there). A MKIRAF or checking your login permissions usually fixes it.-Mike
|
|
|
|
nicand |
08/10/2007 09:04PM
|
|
|
Status: offline
Registered: 08/10/2007
Posts: 5
|
GREAT! Thank you, it is working beautifully.
|
|
|
|
| |
|
Content generated in: 0.18 seconds |
|