Tuesday, November 18 2008 @ 03:07 AM MST Contributed by: fitz Views: 613
The X11IRAF v2.0 release featuring XImtool support for 24-bit displays is now available as a beta release for general use from the following distribution links:
Limited internal-testing has shown this package is stable enough for wider
testing within the user-community, however it should be remembered this is
a Beta-release and some problems and platform-specific issues might still
be found (but are expected to be easily solved). Known issues (and existing features for those not familiar with XImtool) are outlined in the release notes for
V2.0 or the original
V1.3 notes.
This release provides only the existing X11IRAF
applications with 24-bit X11 display support. Please reply with any comments, suggestions or bug-reports.
Update 11/18/08: Distribution updated to fix a BadAlloc error seen on some systems. Update 12/1/08: Distribution updated to fix a BadValue error seen on MacPro systems, misc other bugs. Update 12/10/08: Distribution updated to fix misc bugs. Update 02/23/09: Updated distribution to include Cygwin binaries. Update 04/07/09: Updated distribution to include Sun/Solaris binaries.
NFEXTERN is an external IRAF package designed specifically for the reduction of NEWFIRM (an IR mosaic camera) instrument data, but which is also useful for other IR and mosaic reductions. It includes updated tasks found in MSCRED as well as catalog tools found in the ACE package. The package is now available from the downloads area and the ftp archive at NOAO.
See below for more information, please report any problems or comments.
The Science Software Branch of the Space Telescope
Science Institute wishes to announce the availability of version
3.10 of the Space Telescope Science Data Analysis Software (STSDAS).
Concurrent with the STSDAS release, we have also released v3.10 of
the TABLES external package. .....
Changelog and download details in the body of the story.
BUG: It is likely that the DO tasks (e.g. doslit) will not work correctly
if the input image names have a path. This is because
internal database filenames are derived from the image names.
The recommended action is to work in the data directory.
STATUS: Work on these and related tasks is currently frozen and since
there is a basic workaround (working in the data directory)
nothing may be done for some time.
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.
Thursday, April 09 2009 @ 01:51 AM MDT Contributed by: fitz Views: 148
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....)
BUG: The use of a '$' in a field name was causing the 'missing' value
to always be printed even if the field exists in the image. This
was caused by a failure to check for the character and removing it
prior to getting the value from the header. There is no workaround,
the code change is trivial.
It was 3 years ago today that iraf.net officially took over user support for our users, and the site has grown considerably since then: In 2008, we had over 75,000 unique visitors, served more than a million pages from the site, served an avg of 157 iraf-help-pages/day from the banner bar, transferred enough bandwidth for hundreds of full IRAF systems, answered many hundreds of user questions, and we are approaching 1200 registered users. 2009 has the potential for significant (and 'official') IRAF development, let's all hope for better budgets in the coming year.
Thanks again to all of you who use this site, and especially to those who regularly contribute to truly make it a community forum.
Monday, November 24 2008 @ 09:51 AM MST Contributed by: fitz Views: 431
The Astronomy Tools and Applications Branch of the Space Telescope Science Institute wishes to announce the availability of version 3.9 of the Space Telescope Science Data Analysis Software (STSDAS). Concurrent with the STSDAS release, we have also released v3.9 of the TABLES external package.....
Changelog and download details in the body of the story. Comments should go to help@stsci.edu
Tuesday, November 04 2008 @ 06:40 AM MST Contributed by: fitz Views: 350
NUMBER: 570 MODULE: imexpr, mskexpr, or tasks other asks using the expression evaluator SYSTEM: -V2.14.1 DATE: Mon Nov 3 22:16:41 MST 2008 FROM: valdes
BUG: Use of the built-in functions mod, min, max, and median produce an
"incompatible types" error even though the types of the arguments are
correct. This is a due to a coding error. There is no workaround
other than using alternative ways to express the desired
expression.