MSCIMAGE issue
Mike Fitzpatrick wrote on Jun 17, 2015
[Moderator's Note: Forwarded from story submission]
I've been trying to run MSCIMAGE on an image file and keep getting an segmentation violation.
ERROR: segmentation violation\r\n "sigscale=0.1, pclip=-0.5, grow=0., > "dev$null")"
line 280: mscsrc$mscimage.cl
called as: `mscimage ()\'
Looked at like 280 in the code and the problem seems to happen when the code is combining the different extension's BPMs into one final BPM image file.
The data is from CTIO Mosaic 2B. I did modify the BPMs so I tried both the modified and the original BPMs from the telescope but had no luck getting MSCIMAGE to run. I did use the fix shown in
http://iraf.net/forum/viewtopic.php?showtopic=1468738
IRAF v.: 2.16.1\r\nOS: OSX 10.10.3
I can transfer files and dpar from mscimage.
Thanks for the help
Jean Walker
kurtisw wrote on Jul 21, 2015
I've just started having this exact same issue also on Mac OSX 10.10. This error does not appear on my various linux boxes.
~Kurtis
prasadh wrote on Aug 06, 2015
Hi
Did any one find a solution for this . I have the same error massage .
ERROR: floating point invalid operation
"sigscale=0.1, pclip=-0.5, grow=0., > "dev$null")"
line 309: mscsrc$mscimage.cl
called as: `mscimage (mode=h)'
I tried the exact same thing in another iMac and got the same problem . But it works fine with linux mint .
Mike Fitzpatrick wrote on Aug 11, 2015
A different, but similar, problem was recently reported and fixed in MSCIMAGE that may also fix this bug. I've updated the MSCRED package with a new set of linux64/macintel binaries that includes the fix. To install on a v2.16 system, all you should need to do is:
% cd $iraf/extern
% make mscred
This will force an update of the package. The problem wasn't seen on 32-bit systems so those binaries we not updated this time, however if the problem continues please post back. It would help to have some sample data (e.g. upload to the anonftp at ftp://iraf.noao.edu/pub) and parameters we could use to reproduce the problem.
jpwalker wrote on Aug 11, 2015
Well I installed and tried the updated mscred package and have ran into a new problem. Now I get a new error message ERROR: Abnormal termination of child process '??'. The error message was also returned by mscdisplay which I didn't have a problem with before. I was able to open the image with display. I did do a full reinstall of IRAF (just in case). Here are the commands that I tried:
mscred> mscimage
List of input mosaic exposures (Cobj3034.fits):
List of output images (Oobj3034.fits):
ERROR: Abnormal termination of child process '??'
"type="image")"
line 28: mscsrc$mscimage.cl
called as: `mscimage ()'
mscred> mscdisp Cobj3034.fits
ERROR: Abnormal termination of child process '??'
mscred> mscdisp 1256_BVR_noback.fits
ERROR: Abnormal termination of child process '??'
mscred> display Cobj3034.fits[1]
frame to be written into (1:16) (1):
z1=40.82813 z2=116.966
mscred>
I'm running Mac OS X 10.10.4 and IRAF 2.16.1
Hope this helps.
Mike Fitzpatrick wrote on Aug 11, 2015
My apologies, I found a symlink in the package tree that caused linux binaries to be installed in the macintel directory, which is why the binaries don't run. I've updated the distribution so a new "make mscred" to reinstall the package should fix it. Sorry for the inconvenience, let me know if you still have problems.
prasadh wrote on Aug 16, 2015
HI
Thanks for updating it . I had a new mac pro machine and with the new installation it runs well . SO I think problem is fixed now .
Also I tried Ureka package (http://ssb.stsci.edu/ureka/) that contained iraf and it worked well too. Only concern with UREKA is it gave me black and white graphics when I run some tasks in interactive mode . ( e.g. . msccmatch , imexam ,mscexam etc . )
Mike Fitzpatrick wrote on Aug 16, 2015
Ureka is a 32-bit-only system and this problem only affected 64-bit binaries. The B&W graphics are probably due to having the terminal set as 'xterm' instead of 'xgterm' (do a "cl> stty xgterm" to reset it, or do a new MKIRAF).
Last post on Aug 16, 2015