Welcome to iraf.net Monday, September 01 2014 @ 02:57 PM MDT

IRAF Development Roadmap Available

  • Sunday, September 29 2013 @ 10:51 PM MDT
  • Contributed by:
  • Views: 1,838
IRAFNET

NOAO is taking the opportunity to begin substantial development of IRAF before evolving priorities shift both focus and resources to new challenges starting in 2016. To this end, we have developed a roadmap of projects wewill complete over the next two years, after which time IRAF support will be limited to maintenance, user support, and development of science applications. These enhancements may be categorized in the following areas:

  • CL Language Enhancements
  • In-Memory CL Image Operators
  • Spectral Package Enhancements
  • Parallel Execution
  • Python Task Interface

We very much would appreciate your feedback on our plans for IRAF. Please feel free to comment below, or contact fitz@iraf.net if you don't wish to comment publically.

IRAF Development Roadmap Available | 1 comments | Create New Account

The following comments are owned by whomever posted them. This site is not responsible for what they say.

  • IRAF Development Roadmap Available
  • Authored by: olebole on Thursday, May 01 2014 @ 09:11 AM MDT
Hi Mike,

I am writing you on behalf of the Debian Astronomy working group.

One topic that isn't covered by your plan yet is a better support of (Linux) distributions yet. Currently, it is very difficult for us packagers to create an IRAF package that can be delivered as part of a distribution. From a Debian point of view, this has the following reasons:

* IRAF contains a number of convienience copies of other packages (like cfitsio, curl, readline, f2c, xmlrpc) which needs to be sorted out. It would be nice to support system-installed packages here as well (maybe as a configuration option).

* newer file system standards distinguish between system-dependent files (which go into /usr/lib, or /usr/lib/<arch> on Debian) and system independent files (which are in /usr/share). I have some patches which put everything on the right place; however it would be nice if IRAF could do this from scratch.

* There are a number of compiled files that have no source; mainly in the VO package. I am not sure whether they are all GPL; otherwise they can't be linked to IRAF (because of IRAFs license)

* it would be nice to have an automated unit test than can be used to check if everything works.

(and I probably forgot a number of things here...)

Many of these problems do not only concern Debian, but Fedora Linux seems to have similar problems as well (as stated on their mailing list).

Having IRAF packaged for the system has a number of advantages for the users; the main is that he automatically gets updates over the same channel as for the rest of his system.

If you like, we can discuss every of these items in more detail, and I can explain the motivation behind them. I know that it is not so visible, but it would help many people in installing and using IRAF.

Best regards

Ole


Privacy Policy
Terms of Use

User Functions

Login