Welcome to iraf.net Wednesday, February 21 2018 @ 11:20 AM GMT

Buglog #587 -- MSCZERO

View Printable Version
  • Tuesday, June 24 2014 @ 01:41 AM GMT
  • Contributed by:
  • Views: 5,363
Bug Logs NUMBER: 587
MODULE: mscred.msczero, nfextern.msctools.msczero
SYSTEM: V2.14-
DATE: Mon Jun 23 16:10:59 MST 2014
FROM: valdes

BUG: When using msczero with DS9 a "coordinate not in an image" error may occur. This is due to DS9 returning a WCS identifier ending in 00 instead of 01 or higher. A way to check this is to display an image with mscdisplay or msczero, enter =imcur, hit any key in ds9 (all this from an IRAF session). If you see 100 in the string that gets printed then this is the problem.

The workarounds are

1. Update mscred to 5.06 or nfextern to 2.44.
2. Use ximtool instead of DS9
3. After displaying edit uparm$mscdispN (where N is the frame) to change the ?01 to ?00; i.e. 101 -> 100. Note that any redisplay will undo this change.

Note that there is a known problem with DS9 V7.2 that has more problems with cursor readback so also used an earlier version of DS9.

STATUS: A script fix was added to the latest mscred and nfextern and the repository versions updated.

Buglog #581 -- SPLOT

View Printable Version
  • Wednesday, June 08 2011 @ 04:05 PM GMT
  • Contributed by:
  • Views: 3,812
Bug Logs 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.

STATUS: Fixed in future patches and releases. [Note: Patched binaries for affected architectures can be found in ftp://iraf.noao.edu/iraf/v215/support/arch>/x_onedspec.e].

Buglog #580 -- imcombine and variants

View Printable Version
  • Friday, April 01 2011 @ 06:20 PM GMT
  • Contributed by:
  • Views: 2,712
Bug Logs 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.

STATUS: Fixed for future patches and releases.

Buglog #579 -- specplot

View Printable Version
  • Thursday, March 31 2011 @ 05:50 PM GMT
  • Contributed by:
  • Views: 1,874
Bug Logs NUMBER: 579
MODULE: onedspec.specplot
DATE: Thu Mar 31 10:41:56 MST 2011
FROM: fitz

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'.

Buglog #578 -- splot, scombine, fxcor, identify tasks, dispcor, disptrans

View Printable Version
  • Wednesday, March 09 2011 @ 07:49 AM GMT
  • Contributed by:
  • Views: 1,715
Bug Logs NUMBER: 578
MODULE: splot, scombine, fxcor, identify tasks, dispcor, disptrans
SYSTEM: v2.15-V2.15.1a (64-bit platforms only)
DATE: Tue Mar 8 21:57:38 MST 2011
FROM: fitz

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.

Buglog #577 -- dohydra, dofibers, doargus, do3fiber

View Printable Version
  • Monday, February 21 2011 @ 05:24 PM GMT
  • Contributed by:
  • Views: 1,183
Bug Logs 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".

Buglog #576 -- IMCOMBINE

View Printable Version
  • Wednesday, November 17 2010 @ 10:50 PM GMT
  • Contributed by:
  • Views: 1,215
Bug Logs NUMBER: 576
MODULE: imcombine
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.

STATUS: This has been fixed for the next release.

Buglog #575 -- All ICFIT tasks

View Printable Version
  • Tuesday, June 29 2010 @ 04:56 PM GMT
  • Contributed by:
  • Views: 1,266
Bug Logs 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.

STATUS: Fixed for the next (v2.15) IRAF release.

Buglog #574 -- DAOPHOT.PSF

View Printable Version
  • Wednesday, April 14 2010 @ 05:06 AM GMT
  • Contributed by:
  • Views: 1,350
Bug Logs NUMBER: 574
MODULE: daophot.psf
SYSTEM: -V2.14
DATE: Tue Apr 13 22:01:52 MST 2010
FROM: fitz

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.

STATUS: Fixed for the next release.

Buglog #573 -- MSCIMAGE

View Printable Version
  • Friday, September 18 2009 @ 04:44 PM GMT
  • Contributed by:
  • Views: 1,804
Bug Logs NUMBER: 573
MODULE: mscimage
SYSTEM: - V4.9 August, 2008
DATE: Fri Sep 18 08:36:30 MST 2009
FROM: valdes (discovered and diagosed by Thomas de Boer)

BUG: The task ignores the parameters "boundary" and "blank" which are fixed to be "constant" and "0." respectively.

STATUS: This is fixed for the next release.
First | Previous | 1 2 3 4 5 6 7 | Next | Last

Privacy Policy
Terms of Use

User Functions



IRAF Roadmap

Which Roadmap Feature Should Have Highest Priority?

  •  Performance Improvements
  •  CL Enhancements
  •  Spectroscopy Tools
  •  Python Interface
  •  Multi-lang Interface
  •  Other Suggestions?

Other polls | 361 voters | 3 comments

Visual Theme Switcher

Test out available themes by selecting from one of the 3 available themes or give the Visual Switcher a try:

What's New


No new stories

Comments last 2 days

Fatal error: Call to undefined function load_extra_modules() in /home3/irafnet/public_html-2.0.0/index.php on line 457