iraf.net

Hello,I am using a new iraf version that was recently installed on my system.
(I used to run the 2.11 version before.) I am trying to run several
different packages that I used to run routinely before, but I keep
getting the same error message. For example, if I try to run the
tasks "ccdproc" or "ccdlist" or "ccdhedit" etc. in the package
noao.imred.ccdred, I get the message
"Cannot open connected subprocess (ccdred$x_ccdred.e)". If I try to run the task "apsum" in
noao.twodspec.apextract, then I get the Error message
ERROR: Cannot open connected subprocess (apextract$x_apextract.e), etc.The IRAF on-line FAQ page (http://iraf.noao.edu/faq/FAQsec09.html#9008)
says the following about such errors:
***************************************************************************
What does "ERROR: Cannot open connected subprocess (pkg$x_pkg.e) mean? In general, the message indicates the named executable can't be found
or executed for some reason. It could be a problem with permissions (no read
or execute permission) or, more likely, the executable can't be found. The
named executable (x_pkg.e) is first looked for in the package bin directory,
e.g., bin$ or noaobin$. [The last placed searched is the package root
directory as reported in the error message.] You can cd to the package bin
directory and look around:
cl> cd noaobin
cl> path
tucana!/usr/iraf/noao/bin.sparc/
cl> dir long+
If all non-script tasks in the NOAO package can't be executed, an
installation error may have occurred. Check that the noao bin executables
were placed in the directory pointed to by the noao$bin.`mach' symbolic link.
It may be that they weren't installed at all or that they were placed in the
wrong directory.
Often, when tasks in an external package can't be executed, it is be-
cause mkpkg failed and the executables weren't created. Check the spool file
for errors. Another possibility with external packages is that the "-p pkg"
flag was omitted on the mkpkg command line, in which case the executables end
up in the pkg root directory with names like "pkgbinx_pkg.e". In this case,
you can simply move them to the the appropriate bin directory, the architecture
correct subdirectory of the package root directory. A trivial reason for
this error with external packages is that the package root is incorrectly
defined (maybe a missing trailing slash (UNIX) or unescaped $ (VMS)).
***************************************************************************So it seems that there is some error in the installation of IRAF which
is affecting most of the important packages. But as far as I could see, the
executables x_ccdred.e etc. do exist in /usr/local/iraf/bin.ssun on
my computer, (iraf was installed in /usr/local/iraf), so I am
not sure what the problem is. Could you please let me know what the
problem may be? What kind of installation error might there be and how does
one correct it?
(These packages used to run fine in my old iraf, which however had to be
upgraded because of Y2K bugs.)
Thank you very much.
--Sincerely,
Varsha Kulkarni
******************************************************
Varsha P. Kulkarni
University of South Carolina
Department of Physics and Astronomy
Columbia, SC 29208
Phone: 803-777-6293
FAX: 803-777-3065
E-mail: varsha@mail.psc.sc.edu
******************************************************

Hi Varsha,> executables x_ccdred.e etc. do exist in /usr/local/iraf/bin.ssun .... This probably means that the core iraf binaries and NOAO package
binaries we unpacked in the same place, you get the error because the
binaries aren't being found in the /usr/local/iraf/noao/bin.ssun directory
as expected. To make sure that you've unpacked everything else correctly,
your IRAF directory tree should look something like: /usr/local/iraf
/ \
(AS) /iraf /irafbin
/ \
(I bin.ssun noao.bin.ssun (NThe "iraf root" in this case is /usr/local/iraf/iraf and not just
/usr/local/iraf, if this system will be exported to other machines on the
local network you may want to make a /iraf link on all systems (pointing
to /usr/local/iraf) so the iraf root is /iraf/iraf for all machines.
I can't say specifically how your system needs to be repaired, but
at the least you should reinstall both the IB and NB distribution binaries
in the correct place. It's possible but more trouble and less reliable to
move them by hand. You can also download ftp://iraf.noao.edu/pub/sysinfo
to verify your installation. This is a csh script so just make it executable
and run it, the output will warn of possible problems or outright errors
and suggest fixes where needed.
Hope this helps, let us know if you still have problems or questions.Regards,
Mike Fitzpatrick