iraf.net

I have moved this installation of IRAF to new systems several times, but it's getting really long in the tooth.
The thing is, it works, and I can't get newer installations to work the way we need them to in our environment.
I think I have most things working, except I'm getting the error Unable to open parameter file `uparm$imlimhear.par'
I have done a mkiraf, checked the permissions on the uparm directory, nothing seems to work. Any suggestions?
There is also an issue with tab autocomplete and 'dir' not working in some directories, but works in others with the same permissions and ownership. These 2 issues may not be related.

I'm beginning to think these 2 things are related.
ecl\$this-\$this->_split2($m[0])_split2($m[0]) show uparm
home$uparm/
ecl\$this-\$this->_split2($m[0])_split2($m[0]) cd uparm
ecl\$this-\$this->_split2($m[0])_split2($m[0]) dir
.
ecl\$this-\$this->_split2($m[0])_split2($m[0]) ls
imlimhear.par

I'm not sure how the dir command works in IRAF. I assume it's a different compiled command than the system?

You didn't say what platform this was, but my guess is that you may be seeing issues with a space in a directory path (e.g. "/Users/My Mac/iraf/...."). This sometimes works with quoting the directory but you can still run into problems if the $iraf (or in your case $home) path contains a space. Post back if you still have problems.

Thanks. This is a RHEL8 x86_64 machine. The user directories are mounted NFS, but there are no spaces in the directory or file names.

When a task looks for a parameter file it first looks in your uparm$ directory, and then in the task source directory. Your uparm$ depends on your home$ path, what does "cl\$this-\$this->_split2($m[0])_split2($m[0]) show home$" say the path is? The task directory is built off of the iraf$ root directory, so likewise what does "cl\$this-\$this->_split2($m[0])_split2($m[0]) show iraf" show is the path?

Parameter file issues are usually path problems, if not spaces or permissions in the path then either an incorrect path or sometimes a missing trailing '/' in the path definition. Using the osfn() function to get the OS filepath (e.g. "cl\$this-\$this->_split2($m[0])_split2($m[0]) =osfn("home$")") can expand the path. I'm assuming the prompts in your second post are an artifact of the posting.

Lastly, the v2.12.2a release is 32-bit only, if the filesystems you're using are very large they may be creating 64-bit inodes and so the system thinks it can't find the file because of this. In this case the only workaround is to use the 64-bit v2.16 system or else run a 32-bit OS in a VM.