iraf.net

Issues:
1: IRAF imexam will not open images opened in DS9.Message from imexam:
Warning: Cannot open image (E:/images/afarrow/test009.fit)
Warning: Pixels out of boundsIs this because DS9 is storing the name as windows standard? if so can I mess with iraf or ds9 to convert it to the standard cygwin path (ie: /cygdrive/e/images/afarrow/)?

---

SDSU - Astronomy - Mount Laguna Observatory Superintendent

If you literally entered the image path using the Windows 'E:/path' notation then the problem is that IRAF doesn't understand windows drive specifications. You'll need to use the /cygdrive path in order to find the file. The windows version of DS9 may indeed be able to read from the windows drive specification, I haven't tried.-Mike

Yes, DS9 uses the windows path when running on windows.

---

SDSU - Astronomy - Mount Laguna Observatory Superintendent

[quote:0fa33b038d="afarrow"]Yes, DS9 uses the windows path when running on windows.[/quote:0fa33b038d] I'm wondering if this could be a fix for : t_imexam.x
[code:1:0fa33b038d]#fix for windows ds9 and cygwinponiter replacename call salloc (replacename, SZ_FNAME,TY_CHAR)#check the second character of the string for the : signifying a windows path
if(imname[2] = ':')
{# initialize replacename with /cydrive/[drive letter]
replacename = "/cygdrive/" + imname[1]# change imname to remove the drive letter and :
for a=0 to SZ_FNAME-3
{
imname[a] = imname[a+2]
}#concatinate the changed imname to replacename then pass it back to imname
replacename = replacename + imname
imname = replacname
}[/code:1:0fa33b038d]I know that I most likely have the syntax wrong for the for loop. The question is then proper syntax and then proper placement into t_imexam.x so that this catches the file name before it gets processed.

---

SDSU - Astronomy - Mount Laguna Observatory Superintendent

Hi, everyone.I'm sorry if this is not the best place to ask this but, I thought that de topic title was general and I also thought that creating another topic for such a small thing does not worth it.Very well, I have the fallowing issue: Every time i send an image to imexam or imedit, the arrow keys stop "obeying" and i can't move the cursor with them. However, on a normal display there is no such problem.Any ideas?Thanks and sorry for the inconvenience.

What do you mean by 'normal display', i.e. is it loading the image from the XImtoo/DS9 menu directly?This otherwise sounds like a classic case of the 'mouse-focus' problem where you need to click on a window boundary before it will accept input, i.e. if the focus is on the terminal window running IRAF then you need to click on the display window before it will accept input once IMEXAM is running. You didn't say which platform this was on, details of how to fix this will depend on that information. There have been recent reports of problems with Fedora but no definitive reports that setting a mouse-focus policy fixes it. Note that having the NumLock/CapsLock keys enabled will affect input on some platforms, so you might try turning those off as well.-Mike

Hi, Mike. Many thanks for your reply."Normal Display" = under cl, command "disp [image]" and the image appears on the ds9 with the mouse cursor on it. I can sure tell you it's not a mouse-focus policy issue because it's set to "Strictly under mouse" and the mouse cursor is under the DS9 image frame.To summarize:
"disp [image]" => arrow keys work fine.
"imexam [image]" or "imedit [image]" => arrow keys stop working (obs: *only* the arrow keys. "c", "l" and others works just fine).This is under Fedora 11, and both Caps Lock and Num Lock are, by default and checked, off.Thanks again and best regards

We've had other reports of Fedora 10/11 and DS9 not playing well together. The arrow keys and the keystrokes you mention are builtin keystrokes to DS9 which means it is no longer entering 'cursor read mode' correctly and recognizing other keystrokes.Unfortunately I don't have easy access to a FC11 system to test this out. If you want to simply try reading the cursor to see if the server if behaving correctly you can use the RIMCURSOR task. Despite the focus setting, does clicking on the window anyway change the behavior? You might also try getting an older version of DS9 to see if that works any better, we've also heard this problem shows up with Gnome but not with KDE. Lastly, you might also contact Bill Joye at SAO to see if he has any ideas.-Mike

Hi, Mike. Thanks again for your reply.I think I don't understand how de rimcursor task works (even after reading the help manual). But, from what I experienced:under cl -> rimcursor [image]Arrow keys -> no action and no output at all
Other keys -> normal action and output, like "s" = 226. 289. 100 sNo, clicking doesn't change the behaviour at all.The current DS9 version is the DS9 5.4.5.fc11 and I'm running under KDE 4.3.2I'll try a DS9 downgrade and give you the feedback.Thanks again.

Hi, Mike.Finally, the issue has been closed (for me, anyway) and the solution was a update from DS9 5.4 to DS9 5.7. Now the arrow keys do the navigation through imexam and/or imedit.Thanks to you, I can now peacefully do the imedit task and remove the cosmic rays without loosing 5min. to centring the cursor with the mouse for each cosmic ray. =)Thank you very much.