1. FYI you can also install Pyraf directly from Debian, with “apt install python3-pyraf”. This will work directly – just start “pyraf”. It is however Python 3 only.
    BTW, the reason that we can’t deliver “cl” or “ecl” directly is that these name conflict with other packages in Debian.
    In case of problems, please open a bug report on Debian, or contact me 😉

  2. On the newest version of Debian, nothing happens. After fiddling with the variables in mkiraf.sh script, I got it to run successfully, created a new login.cl file, and set the variables in it to my taste. Then, running irafcl produces…nothing. Hangs without any information, does not launch xterm, does not do anything at all. Sad. I’ll mess with it again tomorrow, but everything worked until the latest debian upgrade.

  3. Jorg: On Debian, there is a global /etc/iraf/login.cl which can either be modified in-place (to have the settings changed for all users), copied to $(HOME)/.iraf/login.cl (to change the settings only for you), or to the working directory (to have local settings). mkiraf is really no longer needed.

    Invoking “irafcl” without arguments starts ecl on the current window, while “irafcl -x” starts a new xterm (or xgterm if installed) with the ecl. If it does not work, check that you don’t have remnants of old IRAF installation variables ($iraf, $host or so).

    If you experience problems with a Debian package, the best is to create a bug report in Debian (command “reportbug”), or start a discussion on https://github.com/iraf-community/iraf/discussions . These places are monitored, and the chances to get a response is higher than here.

Leave a Reply

Your email address will not be published. Required fields are marked *