iraf.net

hi Guys,

I am sure this must be really stupid, I have been fighting this since yesterday though.

I cannot imdelete files in my system. I was just using !rm instead, but within mscred some of the scripts run imdelete then I cannot circumvent the problem.

I tried this under the cl and under pyraf. I downloaded pyraf again and tried it again, to no avail.

I am running on mac os x 10.9.5

My cl is: NOAO/IRAF PC-IRAF Revision 2.16 EXPORT Thu May 24 15:41:17 MST 2012

My pyraf / ureka :
PyRAF 2.1.5 Copyright (c) 2002 AURA
Python 2.7.5 Copyright (c) 2001-2013 Python Software Foundation.

[maca:~/iraf] kanaan% ur_version
1.0


Under the cl this is what happens:

ecl\$this->_split2($m[0]) ls -l
total 1040
dr-xr-xr-x 475 kanaan staff 16150 Feb 16 2007 A0298
-r--r--r-- 1 kanaan staff 529920 Jun 19 12:14 A0298.0001.fits
ecl\$this->_split2($m[0]) imdelete A0298.0001.fits
delete image `A0298.0001.fits' - WD1524-0030 ? (yes):
ERROR: bus error
ecl\$this->_split2($m[0]) !id
uid=503(kanaan) gid=20(staff) groups=20(staff),12(everyone),61(localaccounts),79(_appserverusr),80(admin),81(_appserveradm),98(_lpadmin),399(com.apple.access_ssh),33(_appstore),100(_lpoperator),204(_developer),398(com.apple.access_screensharing)

Under pyraf:

--\$this->_split2($m[0]) imdelete A0298.0001.fits
delete image `A0298.0001.fits' - WD1524-0030? (yes):
Killing IRAF task `imdelete'
Traceback (innermost last):
File "", line 1, in
iraf.imdelete('A0298.0001.fits', _save=1)
IrafError: Error running IRAF task imdelete
IRAF task terminated abnormally
ERROR (501, "bus error")

I can imcopy images in these directories:

--\$this->_split2($m[0]) imcopy A0298.0001.fits lixo
A0298.0001.fits -\$this->_split2($m[0]) lixo
--\$this->_split2($m[0]) ls -l
total 2088
dr-xr-xr-x 475 kanaan staff 16150 Feb 16 2007 A0298
-r--r--r-- 1 kanaan staff 529920 Jun 19 12:14 A0298.0001.fits
-rw-r--r-- 1 kanaan staff 532800 Jun 19 12:30 lixo.fits

Apparently I can do everything but imdelete!

I am going nuts with this :-)

thanks for your attention.
Antonio

Check the value of the 'cache' CL environment variable: If it is /tmp then you're seeing an old bug in the system that is likely still around because of the Ureka version you are using (which is additionally a not-quite v2.16 customized version of the system). Simply resetting this to some path like "home$cache/" (trailing '/' required should fix the probem). It's also possible installing a newer Ureka (now repackaged as something called Astroconda) would also fix the problem.

It worked.

thanks very much

Antonio