iraf.net

NUMBER:	260
MODULE:	digiphot.daophot.seepsf
SYSTEM:	V2.10
DATE:	Mon Oct  3 13:08:46 MST 1994
FROM:	davis

BUG:	The seepsf task was forcing the output psf image to be less than or
	equal 23 pixels square, corresponding to a psfrad less than or equal
	to 11 pixels, no matter what the actual psfrad in the input image
	psf was. The computed portion of the output psf image was correct.
	The problem was that seepsf was using the wrong quantity to compute
	the default size of the output psf image.

STATUS:	Fixed in 2.10.3. There is no workaround.

NUMBER:	299
MODULE:	daophot.seepsf
SYSTEM:	V2.10
DATE:	Mon Jul  3 17:24:04 MST 1995
FROM:	davis

BUG:	Seepsf was crashing with a floating operand error if the input psf
	image was a purely analytic function, keyword varorder=-1. This
	error was accidentally introduced when the previous seepsf error
	(bug log # 260) was fixed.

STATUS:	Fixed in 2.11 and in the external addon package digiphotx. One
	possible workaround is make the psf image with varorder=0, then
	make a copy of it setting all the pixel values to 0.0 with
	imarith, and inputing the new image to seepsf.