Welcome to iraf.net Saturday, April 20 2024 @ 04:29 PM GMT
buckleygeer |
12/16/2014 10:07PM (Read 1734 times)
|
|
|
Status: offline
Registered: 12/16/2014
Posts: 4
|
Hi, I have this bizarre problem that the interactive=yes option on reidentify has ceased to function. It was working fine and now it just ignores it and doesn't give me the option of examining the solution. I have the ureka 1.4.1 installed on a MacBookPro running 10.9.5. I have tried all the usual things like deleting the parameter file, doing unlearn etc., but nothing works. It is like it is stuck in interactive =NO. I have run out of ideas short of removing and reinstalling ureka.
Any suggestions?
Thanks
Liz Buckley-Geer
|
|
|
|
fitz |
12/16/2014 11:03PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
If doing a new MKIRAF in say /tmp and logging in through there fixes the problem (i.e. w/ a brand new uparm directory), then something may have reset which uparm directory you are using (e.g. did you login through another user's account and so an 'unlearn' doesn't have write permission to delete the file). Do a "show uparm" to see which directory is being used, or try "delete uparm$*" to delete everything. Does logging out and back in help? If you set a parameter, does an "lpar reidentify" show that setting was changed?
|
|
|
|
buckleygeer |
12/17/2014 05:44PM
|
|
|
Status: offline
Registered: 12/16/2014
Posts: 4
|
Hi Mike
Tried all the things you suggested but to no avail. My uparm directory is where it should be and I have write access to it. I see the changed settings if I do and epar and the lpar but it just ignores them. I tried mkiraf. In the absence of any other suggestions I think I will reinstall ureka.
Thanks Liz
|
|
|
|
buckleygeer |
12/19/2014 08:43PM
|
|
|
Status: offline
Registered: 12/16/2014
Posts: 4
|
Solved the problem. Don't ask!
Liz
|
|
|
|
fitz |
12/19/2014 08:57PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
64-bit filesystem?
|
|
|
|
buckleygeer |
12/19/2014 09:33PM
|
|
|
Status: offline
Registered: 12/16/2014
Posts: 4
|
More like pilot error. I had been using autoidentify but was having trouble getting a good line id so I switched to identify and forgot the crucial step of typing "f" to actually get a fit. Turns out if you don't do that then when you run reidentify it just calculates a shift and doesn't give you the interactive option as I suppose it thinks there is nothing to fit! I figured it out when I realized that one of my earlier files worked correctly so I compared the databases and realized what I had screwed up.
Thanks for the help.
Liz
|
|
|
|
| |
|
Content generated in: 0.22 seconds |
|