Submit a Story  :  IRAF Links  :  Past Polls  :  Calendar  :  Advanced Search  
     iraf.net
FAQ
 Forum FAQForum FAQ   Forum SearchForum Search   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Unable to open parameter file

 
Post new topic   Reply to topic    iraf.net Forum Index -> General IRAF
View previous topic :: View next topic  
Author Message
mattia



Joined: 10 Feb 2009
Posts: 2

PostPosted: Tue Feb 10, 2009 7:29 pm    Post subject: Unable to open parameter file Reply with quote

Hi all, I'm an IRAF newbie.

With every task I try to launch modifying parameters with epar, i got the error
Unable to open parameter file `uparm$***.par'
where *** is the chosen task

For instance

Code:
ecl> display filename.fits 1


works properly

while
Code:
ecl> epar display


after having set the various parameters gives me back message

Code:
Unable to open parameter file `uparm$tvdisply.par'.


does someone know what's wrong around?
thanks
Back to top
View user's profile Send private message
fitz
Site Admin


Joined: 30 Sep 2005
Posts: 3255
Location: Tucson

PostPosted: Tue Feb 10, 2009 7:34 pm    Post subject: Reply with quote

These are usually either permissions or path problems, and usually occur when copying/using an existing login.cl file. For example, if the IRAF tree is owned by the 'iraf' user you cannot used the login.cl in the iraf$local directory while logged in as yourself because you do not have permission to write to the iraf$local/uparm/ directory. Likewise, copying an existing login.cl to a new directory would fail because the path given for the uparm directory would be wrong.

In general, a new MKIRAF to create a login.cl and uparm directory will fix your problem. Otherwise, look in the login.cl to see what path is being used (specifically the 'home' value), and then whether you can write there. This isn't fatal, it just won't remember the params you set.

-Mike
Back to top
View user's profile Send private message
mattia



Joined: 10 Feb 2009
Posts: 2

PostPosted: Wed Feb 11, 2009 12:07 pm    Post subject: Reply with quote

thanks for your reply Mike, a new mkiraf solved the problem
Back to top
View user's profile Send private message
vmpas



Joined: 20 Apr 2011
Posts: 5

PostPosted: Wed Apr 20, 2011 8:41 am    Post subject: Reply with quote

Hi, I got the same problem. If I use imarith it gives me back the message
Unable to open parameter file `uparm$imlimarih.par'

Making a new mkiraf does'nt fix the problem.
Can anyone help me?

Thanks
Back to top
View user's profile Send private message
fitz
Site Admin


Joined: 30 Sep 2005
Posts: 3255
Location: Tucson

PostPosted: Wed Apr 20, 2011 5:14 pm    Post subject: Reply with quote

Use the command

Code:
cl> =osfn ("uparm$")


to print out the full host path to the uparm directory to be sure it exists and that you can write to it. If the directory does exist, be sure it isn't owned by anyone else.
Back to top
View user's profile Send private message
vmpas



Joined: 20 Apr 2011
Posts: 5

PostPosted: Thu Apr 21, 2011 8:30 am    Post subject: Reply with quote

The uparm directory exists, I'm the owner and I'm allowed to write to it.
But the uparm directory remains emty when I use imarith or imcombine, but it should create a .par file.
Last week it worked perfectly, now it doesn't. I did nothing to cause this....
Back to top
View user's profile Send private message
fitz
Site Admin


Joined: 30 Sep 2005
Posts: 3255
Location: Tucson

PostPosted: Thu Apr 21, 2011 8:41 am    Post subject: Reply with quote

Quote:
Last week it worked perfectly, now it doesn't. I did nothing to cause this....


Unless you upgraded IRAF, the OS, or users during this last week, then *something* (non-IRAF) has certainly changed ......

Can you do a "touch foo" in the uparm directory at the host level to confirm you can write to it? Is this a remote disk that might now be mounted read-only? If you do a MKIRAF in e.g. /tmp and login through there are the parameters saved (meaning you other uparm$ dir has a problm but IRAF is okay)? Has the machine been rebooted in the last week?
Back to top
View user's profile Send private message
vmpas



Joined: 20 Apr 2011
Posts: 5

PostPosted: Fri Apr 22, 2011 7:39 am    Post subject: Reply with quote

I didn't upgrade anything in the last week.
I can write to the uparm directory. The program and all other files I want to use are on the harddisk, so I'm allowed to write to it.
My computer was not rebooted in the last week, too.
Back to top
View user's profile Send private message
fitz
Site Admin


Joined: 30 Sep 2005
Posts: 3255
Location: Tucson

PostPosted: Mon Apr 25, 2011 4:44 am    Post subject: Reply with quote

Did you try doing a MKIRAF in /tmp and logging in from there (this gives you a fresh uparm directory)? Otherwise, if you do

Code:
cl> reset uparm = /tmp/     # trailing '/' required
cl> flpr 0                     # zero, not oh


are you able to save parameters?
Back to top
View user's profile Send private message
vmpas



Joined: 20 Apr 2011
Posts: 5

PostPosted: Mon Apr 25, 2011 12:48 pm    Post subject: Reply with quote

I installed the new Ubuntu 10.10 and reinstalled Iraf again. I also installed all my previously installed programs and tested Iraf. Again I got the same error as before.

Then I copied .fits files into /tmp directory and did mkiraf. I got a uparm directory, and was able to start iraf. I tested imarith and everything worked fine. But when I test imarith with .fits files on my desktop it doesn't work. Any ideas what could cause this?
Back to top
View user's profile Send private message
fitz
Site Admin


Joined: 30 Sep 2005
Posts: 3255
Location: Tucson

PostPosted: Thu Apr 28, 2011 6:10 am    Post subject: Reply with quote

Is there any chance there's a space in a directory name being used, e.g. /Users/vmpas/My Desktop/iraf ? If so, that's the problem, spaces are not allowed in pathnames.
Back to top
View user's profile Send private message
vmpas



Joined: 20 Apr 2011
Posts: 5

PostPosted: Thu Apr 28, 2011 1:01 pm    Post subject: Reply with quote

Yes, thanks, that was the problem. I changed the name of my directory and there was a space in it. Now everything works perfectly again.
Thanks
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    iraf.net Forum Index -> General IRAF All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2009 phpBB Group
 Copyright © 2005-2011 iraf.net
 All trademarks and copyrights on this page are owned by their respective owners.
Powered By Geeklog 
Created this page in 0.94 seconds