Welcome to iraf.net Friday, March 29 2024 @ 11:30 AM GMT
Buglog #178
- Tuesday, August 18 1992 @ 05:31 PM GMT
- Contributed by: admin
- Views: 1,115
MODULE: images.fmedian
SYSTEM: V2.9
SYSTEM: V2.9
NUMBER: 178 MODULE: images.fmedian SYSTEM: V2.9 DATE: Tue Aug 18 11:31:49 MST 1992 FROM: davis BUG: The fmedian task can crash with a segmentation violation or a floating operand error if image pixel to integer mapping is turned off (hmin = zmin and hmax = zmax) and the input image contains data outside the range defined by zmin and zmax. The bug is not seen often because for most ccd images the data is between -32768 and 32767. STATUS: The bug is fixed in 2.10.1. The work-around is to either let zmin and zmax default to the image minimum and maximum or set hmin and hmax to numbers that are slightly different from hmin and hmax. NUMBER: 327 MODULE: apphot interactive tasks SYSTEM: V2.10.3 and later DATE: Mon Feb 12 14:37:55 MST 1996 FROM: davis BUG: The m keystroke command was performing a 'measure next object' operation (the n keystroke command) instead of a 'move to next object operation' as intended. STATUS: Fixed for the next release of iraf. The work around is to use the :m keystroke command. NUMBER: 450 MODULE: imfilter.fmedian,imfilter.frmedian,imfilter.fmode,imfilter.frmode SYSTEM: V2.11 DATE: Fri Nov 19 14:20:16 MST 1999 FROM: davis BUG: The fast median / mode filtering tasks will overflow producing pathological pixel values if the size of the filtering kernel xfilter * yfilter > 32767 and the number of pixels in 1 histogram bin happens to be > 32767 as may happen in bad pixel regions. The problem was due to the fact that for historical reason the algorithm histogram was stored as a short instead of an int. STATUS: Fixed for 2.11.3. The workaround is to try and keep the filter size < 32767 pixels in size, or to use the much slower median task.
The following comments are owned by whomever posted them. This site is not responsible for what they say.