Welcome to iraf.net Saturday, February 25 2017 @ 09:03 AM GMT

How It Works -- Database / Archive Interactions

View Printable Version
  • Wednesday, August 12 2009 @ 05:57 AM GMT
  • Contributed by:
  • Views: 1,696
How It Works

A database interface has been part of the original IRAF design since 1984, but was never implemented. Originally, the idea was that the DBIO interface would be used to maintain all datafiles, keywords in image headers, data tables and so on. In the original design this was practically an implementation of an entire RDBMS system within IRAF, something not needed today where we have database systems that can be accessed via a daemon (e.g. mysql, postgres) or can be self-contained in text file (e.g. SQLite and accessed via an API.

See below for more comments ....

How It Works -- Thread/Multi-Core Support

View Printable Version
  • Saturday, July 25 2009 @ 07:11 PM GMT
  • Contributed by:
  • Views: 2,218
How It Works

[Note: I'd originally intended to be more prolific about these topics, sorry. Please comment on any suggestions you have for ideas, otherwise I may expand the topics to some non-IRAF projects that might be of interest]

IRAF is inherently a multi-process system (i.e. even a simple script requires binaries for the CL and perhaps several packages) and has always had the ability to run background jobs, but users sometime wonder whether tasks can be made multi-threaded as a means of improving performance for highly data-parallel operations (e.g. mosaic image processing). The short answer is that it is possible, but only with some restructuring of the core system, and of course needed changes to applications to enable the threading.

See below for more .....

How It Works -- Compiler Optimizations

View Printable Version
  • Saturday, April 18 2009 @ 05:42 AM GMT
  • Contributed by:
  • Views: 2,440
How It Works

A question that has often been asked over the years is whether IRAF would benefit from specialized hardware (e.g. the Altivec array processor on PPC systems) or high-performance compilers. The short answer is, it depends.

See below for further discussion .....

How It Works -- IRAF Memory Usage

View Printable Version
  • Thursday, April 09 2009 @ 07:51 AM GMT
  • Contributed by:
  • Views: 1,559
How It Works This is the inaugural message of a topic I hope to make a regular feature on this site. It is an excerpt from a paper recently written meant to inform the reader about various technical aspects of the IRAF system (we hope to also make this paper public in its entirety as well). Topics will cover a range of technical IRAF system matters with the hope of prompting discussion and questions. but will by no means be complete. Your comments and suggestions for future topics are encouraged.

IRAF Memory Usage

IRAF memory requirements are small by any measure; the system will happily process a Mosaic image on a machine with as little as 32MB of memory installed. This is due in large part to the fact that most tasks were written to process images in a line-by-line fashion rather than reading in an entire image, extensions of a mosaic MEF file are processed serially where possible. .....(read more below....)



Privacy Policy
Terms of Use

User Functions

Login

Poll

IRAF Roadmap

Which Roadmap Feature Should Have Highest Priority?

  •  Performance Improvements
  •  CL Enhancements
  •  Spectroscopy Tools
  •  Python Interface
  •  Multi-lang Interface
  •  Other Suggestions?

Results
Other polls | 329 voters | 2 comments

Visual Theme Switcher

Test out available themes by selecting from one of the 3 available themes or give the Visual Switcher a try:

What's New

Stories

No new stories

Comments last 2 days

No new comments