iraf.net

Hi IRAF People,

I am using msccmatch to match catalogue stars to mosaic camera data
and after I remove the offending outliers that were found during the
matching process it asks me:

Accept solution?

I say yes and it throws the error:

ERROR: floating point overflow
called as: `msccmatch (mode=h)'

I have Googled this and the problem apparently originates in ccmap which
is called by msccmatch. There was a bug that was patched for Mac in
June, 2013, see here:

https://iraf.net/forum/viewtopic.php?showtopic=1467697

However, I can't find anything about this issue with Linux, which is
what I am using (my machine is running 64-bit Ubuntu 12.04).

Note that I am using the latest version of Ureka IRAF and I have tried
the same thing using Ureka PyRAF and it throws exactly the same error.

Here are the final lines from the output to the xgterm:

Fit coordinates:
input number of coordinates = 1297
average shift = (1.46, 15.69) arcsec
tangent point shift = (2.92, 16.37) arcsec
fractional scale change = (1.000, 1.000)
axis rotation = (1.331, 1.349) degrees
rms = (1.821, 0.672) arcsec
Accept solution? (no): yes
ERROR: floating point overflow
called as: `msccmatch (mode=h)'

Here is the param file for msccmatch in case if is helpful:

I R A F
Image Reduction and Analysis Facility
PACKAGE = mscred
TASK = msccmatch

input = obj1066.fits List of input mosaic exposures
coords = sourcecat.asc Coordinate file (ra/dec)
(outcoor= ) List of updated coordinate files
(usebpm = no) Use bad pixel masks?
(verbose= yes) Verbose?

# Coarse Search
(nsearch= 60) Maximum number of positions to use in search
(search = 60.) Translation search radius (arcsec)
(rsearch= 2.) Rotation search radius (deg)

# Fine Centroiding
(cbox = 11) Centering box (pixels)
(maxshif= 5.) Maximum centering shift to accept (arcsec)
(csig = 0.1) Maximum centering uncertainty to accept
(arcsec)
(cfrac = 0.5) Minimum fraction of accepted centers
(listcoo= yes) List centered coordinates in verbose mode?

# WCS Fitting
(nfit = 50) Min for fit (\$this->_split2($m[0])0) or max not found (<=0)
(rms = 0.5) Maximum fit RMS to accept (arcsec)
(fitgeom= general) Fitting geometry
(reject = 3.) Fitting rejection limit (sigma)
(update = yes) Update coordinate systems?
(interac= yes) Interactive?
(fit = yes) Interactive fitting?
(graphic= stdgraph) Graphics device
(cursor = ) Graphics cursor

accept = no Accept solution?
(mode = ql)

I hope someone can help and please let me know if you need any more information.

Richard

Amongst other things, Ureka uses a custom version of the original v2.16 system that pre-dates this fix. You see the same from pyraf because pyraf is nothing more than an alternate command environment.

The fix would be to get the patched v2.16.1 binary from ftp://iraf.noao.edu/iraf/v216/support/linux/x_images.e -- download in binary mode, make sure the file is executable and install in your iraf$bin.linux directory.

Fantastic, thank you for the quick reply. I copied the downloaded file to the directory as you suggested and it works. Fixed!