Wednesday, June 08 2011 @ 10:05 AM MDT Contributed by: fitz Views: 168
NUMBER: 581 MODULE: splot SYSTEM: V2.15- DATE: Mon Jun 6 17:21:27 MST 2011 FROM: valdes
BUG: When using the deblending options a memory free error occurs with
64-bit versions. This is caused by allocating an integer array and
freeing it as a real array.
NUMBER: 580 MODULE: imcombine and variants SYSTEM: -V2.15.1 DATE: Fri Apr 1 10:53:41 MST 2011 FROM: valdes
BUG:When the grow options is used with masks or partially overlapping data a segmentation could occur. This is because when data is absent (because of non-overlap) or excluded (because of mask) an identifier value was not initialized. The only workaround is to not use the grow options.
BUG: SPECPLOT can sometimes throw a segmentation violation or not
recognize valid input spectra due to an incorrect macro definition
on 64-bit platforms (linux64 and macintel only).
STATUS: This has been fixed for the next release. A patched x_onedspec.e
binaries can be installed from ftp://iraf.noao.edu/iraf/v215/support//x_onedspec.e where the is either 'linux64' or 'macintel'.
BUG: The 64-bit port changes to iraf$noao/lib/smw.h improperly added a P2R() macro to
the APLOW/APHIGH macro declarations. This was causing tasks with
2-D data to make an out-of-bounds request for data and leading to
and error message such as
ERROR: Pixel subscript out of bounds (spec.fits)
Normal onedspec data or use on 32-bit platforms is not affected.
STATUS: Fixed for the next release. A re-application of the v2.15.1a patch
file or new installations of v2.15.1a will replace the affected binaries on 'linux64' and 'macintel'
platforms.
Monday, February 21 2011 @ 10:24 AM MST Contributed by: fitz Views: 343
NUMBER: 577 MODULE: dohydra, dofibers, doargus, do3fiber SYSTEM: -V2.15.1 DATE: Fri Feb 11 12:30:46 MST 2011 FROM: valdes
BUG: The tasks will shorten root input image names to six characters by
using the first five and last characters. Depending on the style
of image names this can result in name conflicts. The reason for
this shortening is no longer known so it is now considered a bug.
Workarounds are to be aware of this and rename image names to avoid
conflicts.
STATUS: This is fixed in the next release. The fix is to modify the file
$iraf/noao/imred/src/fibers/proc.cl as shown (replace lines 125 to
129 with "extn = extn // ".ms"). If you don't have permission
to make this change then copy the file to your iraf "home$"
directory, edit it, load the desired package, and then override
the definition of the file with "redefine proc = home$proc.cl".
NUMBER: 576 MODULE: imcombine SYSTEM: V2.14 DATE: Wed Nov 17 15:20:16 MST 2010 FROM: valdes
BUG: The addition of the image names using imcmb="$I" does not work for input images with a square bracket; e.g. foo[1], foo[im1], foo[*,*]. The IMCMB value, in order to allow long filenames, is stripped of any path. For an obscure reason related to VMS directories this code failed to find a rootname.
Tuesday, June 29 2010 @ 10:56 AM MDT Contributed by: fitz Views: 594
NUMBER: 575 MODULE: all tasks using the icfit tools SYSTEM: - V2.14 DATE: Mon Jun 28 14:08:48 MST 2010 FROM: valdes
BUG: The icfit tools are used in many tasks involving 1D function fitting.
These include onedspec tasks like continuum and identify. The
tools provide for a grow radius where any sigma rejected points
have neighbors also rejected. The logic was wrong
in two ways; one where if a neighbor was also a rejected point
it did not also reject neighbors of that point, and another where
the grow radius units were used both as in pixels and in user
coordinates. In reality the grow is supposed to be in user
coordinate units. In addition some tasks, like continuum, incorrectly
described the units adding to the confusion.
BUG: The ":function" command was not properly saving the new function
when refitting is done with the 'f' keystroke. This is because the
fitting function reinitializes the parameters to the startup
values without first saving the modified function.
BUG: It is likely that the DO tasks (e.g. doslit) will not work correctly
if the input image names have a path. This is because
internal database filenames are derived from the image names.
The recommended action is to work in the data directory.
STATUS: Work on these and related tasks is currently frozen and since
there is a basic workaround (working in the data directory)
nothing may be done for some time.