Welcome to iraf.net Thursday, April 25 2024 @ 10:02 AM GMT

Buglog #403

  • Friday, June 05 1998 @ 03:45 PM GMT
  • Contributed by:
  • Views: 1,061
MODULE: fixpix, ccdproc, display
SYSTEM: V2.11-V2.11.1
NUMBER:	403
MODULE:	fixpix, ccdproc, display
SYSTEM:	V2.11-V2.11.1
DATE:	Fri Jun  5 09:45:47 MST 1998
FROM:	valdes

BUG:	When fixing regions by interpolation along columns/across lines,
	which may be set by the user or automatically by finding the
	narrowest direction across a region of bad pixels, it is possible
	to get a segmentation error or error related to referencing invalid
	memory.  Whether this error occurs depends on the contents
	of memory.  If no error occurs the result is correct.

	One workaround is to use only interpolation across columns/along
	lines if this makes sense.  Another workaround is to add a dummy
	region with interpolation along columns covering all the columns.
	For example the first or last line as in '1 3072 1 1' for an image
	with 3072 columns.  It is also possible to break up the operation
	in FIXPIX using multiple passes.  For example if a bad pixel region
	is described by the rectangle '2000 3024 510 512' then two passes
	using '2000 2500 510 512' and '2500 3024 510 512' may work.

STATUS:	Fixed in the next release.

NUMBER:	410
MODULE:	crutil.crmedian
SYSTEM:	V1.1: May 1998
DATE:	Fri Sep  4 09:59:20 MST 1998
FROM:	valdes

BUG:	On images with more than about 500K pixels the median operation is
	done in overlapping blocks of lines.  The amount of overlap is
	half of the line median size 'lmed'.  The bug is that on output
	the overlap regions end up being zero.  There is no workaround
	except to reinstall the new version of the package.

STATUS:	Fixed in V1.2: Sep 4, 1998.

NUMBER:	500
MODULE:	apphot package
SYSTEM:	V2.12 and earlier
DATE:	Fri Jun 21 09:21:08 MST 2002
FROM:	davis

BUG:	In interactive mode the v keystroke will not update the aperture
	size or algorithm parameters correctly for the next measurement if
	the cursor position does not change significantly.

STATUS:	Fixed for the next patch / release of IRAF. The work around is to
	use the equivalent colon commands or move the cursor significantly
	after the last measurement.

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