iraf.net

NUMBER: 572
MODULE: dotasks
SYSTEM: -V2.14
DATE: Tue Apr 28 11:19:41 MST 2009
FROM: valdes

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.

NUMBER: 571
MODULE: IMAGES.IMUTIL.HSELECT
SYSTEM: V2.14
DATE: Fri Jan 2 21:41:53 MST 2009
FROM: fitz

BUG: The use of a '$' in a field name was causing the 'missing' value to always be printed even if the field exists in the image. This was caused by a failure to check for the character and removing it prior to getting the value from the header. There is no workaround, the code change is trivial.

STATUS: Fixed for the next release.

NUMBER: 570
MODULE: imexpr, mskexpr, or tasks other asks using the expression evaluator
SYSTEM: -V2.14.1
DATE: Mon Nov 3 22:16:41 MST 2008
FROM: valdes

BUG: Use of the built-in functions mod, min, max, and median produce an "incompatible types" error even though the types of the arguments are correct. This is a due to a coding error. There is no workaround other than using alternative ways to express the desired expression.

STATUS: Fixed for the next release.

NUMBER: 569
MODULE: cosmicrays
SYSTEM: -V2.14.1
DATE: Mon Oct 13 10:33:15 MST 2008
FROM: valdes

BUG: The message

• ERROR: PLIO: reference out of bounds on mask

occurs when the image is not 2D. This can be a conceptual problem for data which define a higher dimensionality but with length of 1; e.g. [2048,2048,1]. This is effectively a 2D image but some IRAF tasks designed for 2D images can have problems with this.
The workaround is simply to use a 2D image section:

• cosmicrays image[*,*,1]

Of course one can also convert the image to 2D with imcopy or imslice.

STATUS: No updates are currently planned and users should use the workarounds noted above.

NUMBER: 568
MODULE: imcombine
SYSTEM: -V2.14.1
DATE: Tue Oct 7 12:52:35 MST 2008
FROM: valdes

BUG: When using avsigclip, ccdclip, or sigclip rejection around the median (mclip=yes) the resulting final median may be incorrect. This will generally only occur if unusually small low sigma values, such as lsigma=1, are used. This was due to using a wrong variable.

STATUS: Fixed for the next release.

NUMBER: 567
MODULE: apall, apedit
SYSTEM: V2.11-V2.14.1
DATE: Tue Oct 7 10:53:14 MST 2008
FROM: valdes

BUG: The :parameters and :apertures commands cause the task to exit with an error that parameter "apertures" isn't found. This problem has existed for a long time due to a missing parameter in the hidden parameter sets.

STATUS: Fixed for the next release.

NUMBER: 566
MODULE: display
SYSTEM: V2.12.4-V2.14
DATE: Tue Aug 26 17:10:07 MST 2008
FROM: valdes

BUG: The "ocolors" parameter was being used in place of the "bpcolors" parameter. There is no workaround.
STATUS: Fixed for the next release.

NUMBER: 565
MODULE: imextensions
SYSTEM: V2.13-V2.14
DATE: Mon Aug 25 16:24:33 MST 2008
FROM: valdes

BUG: Specifying an extension version or range of versions results in an integer divide by zero. This is a bug for which there is no around.
STATUS: Fixed for the next release.

NUMBER: 564
MODULE: ccdmask
SYSTEM: -V2.14.1
DATE: Fri Aug 22 09:27:06 MST 2008
FROM: valdes

BUG: The output mask from ccdmask is incorrect if the task has been run previously without starting the executable fresh. The workaround is to type "flpr ccdmask" before executing this task to force a fresh executable.

STATUS: Undiagnosed at present. Only the workaround has been defined.

NUMBER: 563
MODULE: imexpr
SYSTEM: -V2.14
DATE: Tue Aug 12 15:12:04 MST 2008
FROM: valdes

BUG: Literal (quoted) strings cannot be used in expressions stored in the expression database. The quotes are stripped and then the error is that an operand by that name is not found. As a warning, single quotes in the database are not interchangable with double quotes as they are on the command line. They are interpreted as character constants and something like 'abc' will be expanded to 'a bc'.

STATUS: Double quoted strings allowed in next release.