Welcome to iraf.net Wednesday, May 01 2024 @ 09:50 PM GMT
Buglog #185
- Thursday, October 01 1992 @ 11:06 PM GMT
- Contributed by: admin
- Views: 1,151
MODULE: imcombine, ccdred.combine, onedspec.scombine
SYSTEM: V2.9
SYSTEM: V2.9
NUMBER: 185 MODULE: imcombine, ccdred.combine, onedspec.scombine SYSTEM: V2.9 DATE: Thu Oct 1 17:06:23 MST 1992 FROM: valdes BUG: When using the CCDCLIP or CRRJECT rejection option with mclip=yes (which is the default) a minimum of 3 images/spectra is required. This means that two image/spectrum cosmic ray rejection doesn't work as intended. The workaround is to use mclip=no. This is equivalent for two images/spectra since the median and average are the same in this case. STATUS: Fixed in V2.10.2. NUMBER: 214 MODULE: scopy, sarith SYSTEM: V2.10-V2.10.2 DATE: Thu May 20 17:07:53 MST 1993 FROM: valdes BUG: When using SCOPY or SARITH with a specified wavelength range, w1 and w2 not equal to INDEF, and rebin=yes the spectra are correctly resampled to the requested wavelength interval but the coordinate system in the header is updated incorrectly. The coordinates may be off by a fraction of a pixel. For example if w1=6400 and w2=6600 the output data will have the first pixel at 6400 but the coordinate reported by LISPIXEL or any other task might be 6400.25 (where the dispersion is, say, 3 Angstroms per pixel). This error is caused during the conversion from logical to physical pixel coordinates when the physical coordinates are treated as integer; i.e. a wavelength of 6400 for the first logical pixel might be physical pixel 185.325 but it is then truncated to 185 and the coordinate system is set so that physical pixel 185 is 6400 and pixel 185.325 is 6400.25. This is a subtle error which may be discovered by looking at the coordinate of the first pixel with LISTPIX and comparing it with the requested wavelength of the first pixel. STATUS: Fixed in V2.10.3.
The following comments are owned by whomever posted them. This site is not responsible for what they say.