Welcome to iraf.net Friday, April 26 2024 @ 01:21 PM GMT

Buglog #421

  • Monday, April 12 1999 @ 07:43 PM GMT
  • Contributed by:
  • Views: 1,068
MODULE: daophot.peak, daophot.nstar, daophot.allstar
SYSTEM: V2.11
NUMBER:	421
MODULE:	daophot.peak, daophot.nstar, daophot.allstar
SYSTEM:	V2.11
DATE:	Mon Apr 12 13:43:18 MST 1999
FROM:	davis

BUG:	The daophot peak, nstar, and allstar tasks can crash with a floating
	divide by 0 (Solaris) or floating exception (Linux) if the predicted 
	error computation goes to 0.0. This can happen if the predicted
	model is 0.0 (most likely to occur at large radii from the object
	being fit) , the readout noise is 0.0, and the profile error is
	0.0.

STATUS:	Fixed for the next release of IRAF. The workaround is to make sure
	that the readout noise is set > 0.0.

Buglog #421 | 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