polyphot
Josh Tartar wrote on May 16, 2006
Hi all...
I'm having a bit of difficulty with polyphot.
I'm using it in such a way that I already have a polygon defined in a file, e.g. sourcename.pol and I have the center of the source defined as sourcename.coo, so that when I enter the polyphot command, I enter it as:
polyphot sourcename.fits polygon=sourcename.pol coo=sourcename.coo
I should be getting several prompts for additional information, but instead I'm getting the message:
Warning: Graphics overlay not available for display device.
any help on this matter would be greatly appreciated!
I'm having a bit of difficulty with polyphot.
I'm using it in such a way that I already have a polygon defined in a file, e.g. sourcename.pol and I have the center of the source defined as sourcename.coo, so that when I enter the polyphot command, I enter it as:
polyphot sourcename.fits polygon=sourcename.pol coo=sourcename.coo
I should be getting several prompts for additional information, but instead I'm getting the message:
Warning: Graphics overlay not available for display device.
any help on this matter would be greatly appreciated!
Mike Fitzpatrick wrote on May 16, 2006
The message is normal (if annoying), graphics overlays were never implemented in the system. Try to 'unlearn polyphot' in case some old parameter setting is changing the behavior (e.g. 'interactive' turned off).
-Mike
-Mike
Josh Tartar wrote on May 16, 2006
Ok, so do I then just type 'unlearn polyphot'? I tried that, and I got the same message:
Warning: Graphics overlay not available for display device.
I also got this message
Unable to open parameter file `uparm$aptpolypt.par'
Warning: Graphics overlay not available for display device.
I also got this message
Unable to open parameter file `uparm$aptpolypt.par'
Mike Fitzpatrick wrote on May 16, 2006
Ignore the overlay message.
The uparm message likely means that either your uparm dir isn't writable (e.g. you logged in from somebody else's login.cl), or isn't valid (e.g. you copied a login.cl from someplace else and the 'home$' path is no longer correct (uparm is defined as a subdir of home$)). Personal definitions should be in a loginuser.cl file in the same dir as the login.cl with 'keep' as the last statement. You can rebuild the login.cl with a 'mkiraf' at the unix prompt.
-Mike
The uparm message likely means that either your uparm dir isn't writable (e.g. you logged in from somebody else's login.cl), or isn't valid (e.g. you copied a login.cl from someplace else and the 'home$' path is no longer correct (uparm is defined as a subdir of home$)). Personal definitions should be in a loginuser.cl file in the same dir as the login.cl with 'keep' as the last statement. You can rebuild the login.cl with a 'mkiraf' at the unix prompt.
-Mike
Josh Tartar wrote on May 16, 2006
After I invoke polyphot and receive the overlay message, I still need to input additional data for which polyphot should be prompting me. However, after I receive the overlay message, I cannot input anything further.
Is there any way around this?
Is there any way around this?
Mike Fitzpatrick wrote on May 16, 2006
Do you mean you get the command prompt back, or the task appears to hang? Is DS9 already running and do you get the image cursor (blinking circle)? If so then your problem may simply be window focus, i.e. click on the border of the DS9 window to send input focus to that window.
Otherwise, what output/prompts are you expecting? Not all parameters are queried for, can you post your polygon file (e.g. is there a semicolon termiinator?) or some more details using a dev$pix example?
-Mike
Otherwise, what output/prompts are you expecting? Not all parameters are queried for, can you post your polygon file (e.g. is there a semicolon termiinator?) or some more details using a dev$pix example?
-Mike
Josh Tartar wrote on May 16, 2006
Mike
I do indeed get a blinking circle. I've tried clicking on the edge of the ds9 display window, but it doesn't do anything.
I am not sure exactly what prompts I should be expecting; I'm working from a procedure written up by someone else. The procedure does say to record a sky annulus inner radius and an annulus width, as well as a sky std deviation, so I assume I should expect those prompts.
thanks,
Josh
I do indeed get a blinking circle. I've tried clicking on the edge of the ds9 display window, but it doesn't do anything.
I am not sure exactly what prompts I should be expecting; I'm working from a procedure written up by someone else. The procedure does say to record a sky annulus inner radius and an annulus width, as well as a sky std deviation, so I assume I should expect those prompts.
thanks,
Josh
Mike Fitzpatrick wrote on May 16, 2006
Josh,
I think what you're referring to is the 'v' keystroke used to "verify critical parameters". Once you see the blinking circle, move the cursor to the image someplace and type 'v' and you should see the prompts. Clicking on the window border is only needed when your mouse-focus policy requires it. The 'v' should show you something like:
-Mike
I think what you're referring to is the 'v' keystroke used to "verify critical parameters". Once you see the blinking circle, move the cursor to the image someplace and type 'v' and you should see the prompts. Clicking on the window border is only needed when your mouse-focus policy requires it. The 'v' should show you something like:
Centering algorithm (centroid) (CR or value):
New centering algorithm: centroid
Centering box width in scale units (5.) (CR or value):
New centering box width: 5. scale units 5. pixels
Sky fitting algorithm (centroid) (CR or value):
Sky fitting algorithm: centroid
Inner radius of sky annulus in scale units (10.) (CR or value):
New inner radius of sky annulus: 10. scale units 10. pixels
Width of the sky annulus in scale units (10.) (CR or value):
New width of the sky annulus: 10. scale units 10. pixels
Standard deviation of background in counts (INDEF) (CR or value):
New standard deviation of background: INDEF counts
Minimum good data value (INDEF) (CR or value):
New minimum good data value: INDEF counts
Maximum good data value (INDEF) (CR or value):
New maximum good data value: INDEF counts
-Mike
Josh Tartar wrote on May 16, 2006
It did. Thank you very much.
Josh
Josh
Last post on May 16, 2006