Welcome to iraf.net Friday, April 19 2024 @ 02:52 PM GMT


 Forum Index > Help Desk > General IRAF New Topic Post Reply
 Overwriting issue
   
Jean-Gab
 05/03/2016 05:35PM (Read 1379 times)  
+----
Newbie

Status: offline


Registered: 05/03/2016
Posts: 2
Hi,

I'm using IRAF 2.16 on OS X Yosemite, and I've got an issue when I try to overwrite on fits already existing. (ERROR: Cannot open file (/tmp///.IMT504)). I've checked on the forum and haven't found any solution yet (which was working).

My problem occurs when I use "imarith" or "doslit" task and don't specify an output (or if output = input).
I'm currently trying to complete the doslit tutorial (I'm kind of new to IRAF), so apparently everything should work quite smoothly, I guess. Here is my complete error message :

Change wavelength coordinate assignments? (yes|no|NO): no
ERROR: Cannot open file (/tmp///.IMT504)
"logfile=logfile)"
line 97: doslit$sarcrefs.cl (hidden task)
called as: `sarcrefs (arcref1=fdemoarc1, crval=INDEF, cdelt=INDEF, done=tmp$iraf1574ba, log1=logfile, log2=STDOUT)'
"sarcrefs (arcref1, crval, cdelt, done, log1, log2)"
line 189: doslit$sproc.cl (hidden task)
called as: `sproc (objects=tmp$iraf1574w, arcs1=tmp$iraf1574x, arctable=, standards=tmp$iraf1574y, crval=INDEF, cdelt=INDEF, dispcor=yes, extcor=yes, fluxcal=yes, resize=yes, clean=yes, splot=yes, redo=no, update=no, quicklook=no, batch=no, listonly=no)'
"resize, clean, splot, redo, update, quicklook, batch, listonly)"
line 54: doslit$doslit.cl
called as: `doslit ()'

I already have checked access permissions to /tmp and files in it, and " cl\$this->_split2($m[0]) show tmp " gives me "/tmp/".

If anyone has any clue about it, feel free to share ! Wink Thanks in advance for any enlightenment.

Cheers,
Jean-Gabriel

 
Profile Email
 Quote
fitz
 05/08/2016 08:22PM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
This was reported once or twice before but never actually resolved. It is almost certain that the error about the /tmp/.IMTnnn file is bogus, i.e. it's not something a task like IMARITH/DOSLIT would open (it is the unix socket for image display) but in the various layers of the IRAF kernel it is possible this error message percolated up from some lower-level system call

A task like IMARITH has the prospect of overwriting the input image by writing a temp image of the result and then moving it image back to the input file so an error in writing to /tmp (is the partition full? are there other temp files) may be the real problem and the error message is just getting unwrapped incorrectly. You can explicitly remove the /tmp/.IMT* files to see whether a more informative error appears.

 
Profile Email
 Quote
Jean-Gab
 05/09/2016 07:42AM  
+----
Newbie

Status: offline


Registered: 05/03/2016
Posts: 2
Thank you for your answer !

The solution to my problem seemed to be hidden here : https://iraf.net/forum/viewtopic.php?showtopic=1468688

I added this line "export IMTDEV=inet:5137" to my .bashrc and my error message vanished. I don't know if it is linked, or if I rebooted enough my computer to make it work Wink

Thank you again for your help !

Jean-Gab

 
Profile Email
 Quote
   
Content generated in: 0.12 seconds
New Topic Post Reply

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login