Welcome to iraf.net Friday, March 29 2024 @ 12:59 AM GMT

Buglog #237

  • Friday, January 21 1994 @ 10:55 PM GMT
  • Contributed by:
  • Views: 1,122
MODULE: IEEE NaN support
SYSTEM: Sun/IRAF V2.10, V2.10.1, V2.10.2
NUMBER:	237
MODULE:	IEEE NaN support
SYSTEM:	Sun/IRAF V2.10, V2.10.1, V2.10.2
DATE:	Fri Jan 21 15:55:46 MST 1994
FROM:	tody

BUG:    When converting native floating point to IEEE floating point (as
	when writing FITS files), V2.10 IRAF has a feature which allows
	pixels with a reserved floating point value to be replaced by IEEE
	NaN on output.  In V2.10 Sun/IRAF, the code which does this was
	correct, but the wrong version of the affected object module was
	present in the system library (libvops.a) and in the IRAF shared
	image (S6.e).  This would cause zero to be written as the output
	IEEE value instead of NaN.

STATUS:	Fixed in V2.10.3 or later.  So far as I know the core IRAF system
	does not use this feature but it is used by some layered packages,
	e.g., STWFITS.  The bug only comes into play when mapping of NaNs on
	output is enabled by the application being used.  This is probably
	not a serious bug in most cases, but if the zeros are a problem the
	bug can be fixed by rebuilding the IRAF shared library S6.e.  Contact
	the IRAF group for advice on how to do this.

Buglog #237 | 0 comments | Create New Account

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



Privacy Policy
Terms of Use

User Functions

Login