kicked out of ds9
wfenton wrote on Jul 06, 2009
When I try to rimcurs or imexam on a list of images (or even a single image) the image is displayed in ds9 and then i am immediately kicked out back to the cl, rather than having the opportunity to, for example, use the 'a' key to get info. I've tried this on my os x system as well as the labs ubuntu system. Same result. I must have changed something but 'unlearning' the tasks doesn't seem to help.
Anyone have any ideas?
Anyone have any ideas?
Francisco Valdes wrote on Jul 06, 2009
Occasionally there can be a problem where the communication between an IRAF task and the cursor read with the display get out of sync. Then you can get this type of behavior where you want to read the cursor but instead a quit or EOF is returned. So try quitting IRAF and the display server and starting again.
Frank Valdes
Frank Valdes
wfenton wrote on Jul 06, 2009
thanks, have tried that. i wonder if a preference file got corrupted or if i could map the keys differently...
Francisco Valdes wrote on Jul 06, 2009
If restarting both IRAF and ds9 does not solve the problem then there must be something else wrong but I can't think of what that would be. To be clear, after you start ds9 and then IRAF and you type "=imcur" you don't get a cursor to type (possibly after having to click on ds9 to focur the window which is usually an X11 setting)?
Actually, do "lpar cl" and make sure that the "imcur" parameter is set to a null string (i.e. imcur = ""). Otherwise, when you read the cursor it is trying to read the contents of the specified file which may not actually exist or be at the end of the file. In this case you will indeed find that any cursor read gets an EOF which is what returns the cursor read query back to the CL.
Frank Valdes
Actually, do "lpar cl" and make sure that the "imcur" parameter is set to a null string (i.e. imcur = ""). Otherwise, when you read the cursor it is trying to read the contents of the specified file which may not actually exist or be at the end of the file. In this case you will indeed find that any cursor read gets an EOF which is what returns the cursor read query back to the CL.
Frank Valdes
Last post on Jul 06, 2009