Welcome to iraf.net Sunday, May 28 2017 @ 08:45 AM GMT

BUGLOG #562 -- MSCRED.CCDPROC

View Printable Version
  • Friday, August 22 2008 @ 11:02 PM GMT
  • Contributed by:
  • Views: 1,298
Bug Logs NUMBER: 562
MODULE: mscred.ccdproc
SYSTEM: V4.8
DATE: Tue Aug 12 12:19:30 MST 2008
FROM: valdes

BUG: The fix for bug number 546 was not fully correct. It works for binned data but results in an error for data which is flipped (e.g. when CCDSEC/DETSEC have a starting column greater than the ending column as in '[2048:1025,1:2048]'. The error is that the resulting CCDSEC in the processed image will be off by one. This can result is losing a column when merging multiple amps.

STATUS: Fixed for mscred V4.9.

BUGLOG #561 -- IMSTATISTICS, MIMSTAT

View Printable Version
  • Tuesday, July 15 2008 @ 06:11 PM GMT
  • Contributed by:
  • Views: 1,334
Bug Logs NUMBER: 561
MODULE: imstatistics, mimstat
SYSTEM: V2.14
DATE: Tue Jul 15 11:03:18 MST 2008
FROM: valdes

BUG: The user supplied upper and lower data limits may be exceeded if clipping is used. For instance, if the limits exclude all pixels the clipping with behave as if no pixels are excluded. If not all pixels are excluded and the clipping thresholds computed (number of sigma * standard deviation) exceed the limit then the clipping threshold is used. The only workaround is to not use clipping if the limit values are supplied or check first with no clipping to see if all pixels are excluded.

STATUS: Fixed for the next release.

BUGLOG #560 -- CCFIND

View Printable Version
  • Wednesday, January 23 2008 @ 11:00 PM GMT
  • Contributed by:
  • Views: 1,514
Bug Logs NUMBER: 560
MODULE: CCFIND
SYSTEM: V2.14
DATE: Wed Jan 23 15:56:04 MST 2008
FROM: fitz

BUG: For an image with a ZPN projection, the transform code in mwcs tries to reference the parent image to get the PV matrix keywords. This task called sk_decwcs() to open the WCS, but this routine then unmaps the image. When the task later uses the saved 'mw' pointer to transform coords the ZPN reference to the parent image is invalid and results in a segfault. Changed the code to call sk_decim() directly and operate on the currently open image instead.

There is no workaround other than to not set the 'usewcs' parameter and to set the WCS using the other parameters. Contact iraf.net for a new binary if needed.


STATUS: Fixed for the next release.

Buglog #559 -- TRANSFORM

View Printable Version
  • Tuesday, August 07 2007 @ 06:10 PM GMT
  • Contributed by:
  • Views: 1,829
Bug Logs NUMBER: 559
MODULE: longslit.transform
SYSTEM: -V2.12.3
DATE: Tue Aug 7 10:39:13 MST 2007
FROM: valdes

BUG: When using log resampling (xlog=yes or ylog=yes) it is possible to get a segmentation error. This is caused by taking the log and anti-log of coordinates and not getting back exactly the same value due to real precision problems. This process caused an attempt to go outside the valid range of the interpolator. This may be a rare problem but if it does happen one may be able to use the x1, x2, y1, y2 values to work around the problem. The workaround for a future release is to use double precision and to impose range limits on data passed to the interpolator.

STATUS: Fixed for the next release.

Buglog #558 -- MSCIMAGE

View Printable Version
  • Friday, March 30 2007 @ 06:10 PM GMT
  • Contributed by:
  • Views: 1,859
Bug Logs NUMBER: 558
MODULE: mscimage
SYSTEM: all release up to date
DATE: Fri Mar 30 11:04:18 MST 2007
FROM: valdes

BUG: MSCIMAGE defines the resampled output world coordinate system (WCS) using a reference image WCS. If this reference image has a ZPN projection an error will occur. This is because when the output WCS is set the ZPN projection is inherited from the reference image but MSCIMAGE does correctly setup the output ZPN projection from the reference image. So one must use a reference image with another projection such as TAN.

.....see story for remainder of buglog

Buglog #557 -- SPLOT

View Printable Version
  • Tuesday, December 05 2006 @ 12:54 AM GMT
  • Contributed by:
  • Views: 1,791
Bug Logs NUMBER: 557
MODULE: splot
SYSTEM: -V2.13beta
DATE: Mon Dec 4 15:29:44 MST 2006
FROM: valdes

BUG: When the dispersion function for a spectrum is log sampled, e.g. DC-FLAG=1, and there is also a logical/physical pixel offset, i.e. LTV1 is not zero, then writing out a new spectrum with the 'i' key the results in a wrong WCS. There is no workaround.
STATUS: Fixed for a future release.

Buglog #556 -- SPLOT, SARITH, SCOMBINE, STANDARD

View Printable Version
  • Sunday, October 29 2006 @ 08:37 PM GMT
  • Contributed by:
  • Views: 2,619
Bug Logs NUMBER: 556
MODULE: splot, sarith, scombine, standard
SYSTEM: -V2.13Beta
DATE: Fri Oct 27 09:33:16 MST 2006

BUG: When matching one spectrum to another, the reference spectrum, for some operation (e.g. arithmetic, combining, standard star calibration) the first spectrum is converted to its natural WCS units. If the reference spectrum is in different units the result will be wrong. This is rare but a particular case is when SPLOT displays a spectrum in some units, possibly set by the display units in the header or by the task parameter, and then a binary arithmetic operation is performed using a second spectrum. Even if the second spectrum has the same display units it may be resampled to match the reference spectrum in the wrong units. The code solution is to always resample in the current units of the reference spectrum.

The workaround for the SPLOT example is to use the ":units" command to put the initial spectrum into the natural units of the second spectrum. After the arithmetic you can changes the units back if desired.

STATUS: Fixed for a future release.

Buglog #555 -- FITCOORDS

View Printable Version
  • Wednesday, June 14 2006 @ 05:55 PM GMT
  • Contributed by:
  • Views: 2,274
Bug Logs NUMBER: 555
MODULE: longslit.fitcoords
SYSTEM: V2.13-Beta[12]
DATE: Wed Jun 14 10:41:50 MST 2006
FROM: valdes

BUG: If the fitting axis is 2 (the identify/reidentify features are defined by cuts along the second axis) the y coordinate for the 2D fitting will be wrong. You will notice this if data are plotted with one axis being the y coordinate. The other way you would notice this is that the transformation won't correctly remove the distortions and make a correct wavelength solution.

The only workaround is to transpose the data early before doing the feature identification and tracing. Note that you must then also reset the physical WCS after the transpose with the command "wcsreset wcs=physical".

STATUS: Fixed for the next IRAFNET V2.13 release.

Buglog #554 -- DOPCOR

View Printable Version
  • Tuesday, May 23 2006 @ 11:18 PM GMT
  • Contributed by:
  • Views: 1,861
Bug Logs NUMBER: 554
MODULE: dopcor
SYSTEM: V2.13
DATE: Tue May 23 16:11:05 MST 2006
FROM: valdes

BUG: The verbose output only prints information based for the last spectrum in a multispec file. When a single correction is being applied to all apertures this is correct but when different corrections are being generated for different apertures, say when adding a correction to apertures which had different initial corrections applied this can be concerning. The actual corrections are being applied correctly for each aperture but the verbose output may be misleading. There is no workaround though it is not a data calibration error just a logging error.

STATUS: To be fixed in a future release though no fix has yet been implemented.

Buglog #553 -- SPLOT

View Printable Version
  • Tuesday, May 16 2006 @ 11:04 PM GMT
  • Contributed by:
  • Views: 2,206
Bug Logs NUMBER: 553
MODULE: splot
SYSTEM: -V2.12.3
DATE: Tue May 16 11:08:14 MST 2006
FROM: valdes

BUG: If SPLOT is run more than once without flushing the process (flpr) then the default aperture will be that from the last execution. The consequence is that use of an image section to select an aperture in a multiaperture file may not display the intended spectrum. The workaround is to use the command "flpr" before using an image section.

STATUS: Fixed for the next release.

First | Previous | 1 2 3 4 5 6 7 | Next | Last


Privacy Policy
Terms of Use

User Functions

Login

Poll

IRAF Roadmap

Which Roadmap Feature Should Have Highest Priority?

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

Results
Other polls | 341 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

Stories

No new stories

Comments last 2 days

No new comments


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