Welcome to iraf.net Monday, May 20 2024 @ 12:01 AM GMT


 Forum Index > Archives > Sitemail Archives
 "cannot open image (r092730)"
   
Anonymous: Guest
 01/01/1970 12:00AM (Read 471 times)  



I am having a weird problem. First let me explain that I have IRAF
running on a local machine (venus) in a "normal" fashion; that is, I
access the cl from venus and all my files are on venus and venus does
all the processing. The machine, venus, however, is not part of the
MIT public workstation environment. To use IRAF from any workstation
on campus, a "locker" must be attached and the cl is run using nfs.
Thus, the actual files that compose iraf are in some remote location
while the cpu you are using is at your present workstation, and your
files are in yet another location.On venus, I am able to attach lockers and other file systems and I
made an iraf image from a fits file and put the pixels in a public
place. Of course, permissions were such that anyone could read either
file. Then one of my students tried to read the file and received the
above error message. I went to venus and was able to read it fine. I
then went to a workstation and I was NOT able to access the image. It
is not some sort of nfs error or the fact that I did not attach the
correct file system.I notice the local host name gets put in the header. I would think
this could be a problem, but iraf seems to be able to deal with that.
I determined this from going to another image I made on venus and
checking that I could indeed access it from a workstation. There are
two odd things about this image which may be of relevance: 1. These
images we are having problems with are the 9 Mbyte strip scans. I
don't see how a large image size all by itself could cause these
problems, but maybe? And 2. The pathname is very large. Is there an
upper limit to the number of characters allowed? The path in this
case is
/earth/u1/data12.118/mko/mko_8804/md_to_sl.red/880505/092730/pix/
for the pixel file. The reason I think there may be some path limit
is because when I look in that directory, I find the file "r092730."
instead of the expected "r092730.pix". Is this a known bug? I will
do some experiments here with shorter filenames, but I hope you will
also be able to help.jjk

 
   

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