Welcome to iraf.net Saturday, April 20 2024 @ 04:41 PM GMT
Buglog #307
- Saturday, August 12 1995 @ 12:54 AM GMT
- Contributed by: admin
- Views: 921
MODULE: splot
SYSTEM: V2.10.3-V2.10.4
SYSTEM: V2.10.3-V2.10.4
NUMBER: 307 MODULE: splot SYSTEM: V2.10.3-V2.10.4 DATE: Fri Aug 11 18:54:55 MST 1995 FROM: valdes BUG: When writing out a spectrum with the 'i' key an error about the keyword WAT1_002 not being found or cannot be deleted may occur. Because this occurs in graphics mode the error may flash by too fast to see (with XGTERM) and you may be repeatedly prompted for an output image. This loop can only be killed by killing the CL. The cause of this is a bug in SPLOT which occurs if there are BANDIDn keywords as produced by extraction with the APEXTRACT package. This problem has been reported with DEC ALPHA but could potentially affect any V2.10.3-V2.10.4 system. The workaround is to delete the BANDID keywords, which are only used for documentation currently, using HEDIT. You can then use SPLOT and write out modified spectra with 'i'. STATUS: Fixed in future versions. 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.
The following comments are owned by whomever posted them. This site is not responsible for what they say.