iraf.net

In PSF in the daophot package, there's a field called mkstars. The help file says it is supposed to "Mark the selected or deleted psf stars on the image display ?". Enabling it does absolutely nothing, which is a shame, because it sounds like it would improve my work. What else do I need to enable to get this to run while interactively selecting PSF stars?
I'm running a Scisoft IRAF on 10.6.8 through an xgterm in the vanilla x11 which comes with my Mac, my version of DAOPHOT says May00 at the top whenever I open a help file. IRAF seems to be otherwise capable of scribbling on my ds9-- running tvmark interactively adds a mark when I hit the "a" button (as it should).

Sorry, this was overlooked. Please post back if you're still having problems.

Yes, this still doesn't work (I just got a new set of data-- 80 new images. yay!).I'm running ``released version 2.14'' on a macbook pro.

The 'mkstars' parameter is available in the PSF and PSTSELECT tasks only, all you should need to do is turn it on. It also appears to only work when an image display is available, is this running before you start the task? Are you able to run Example 1 of the PSF help page (which uses the parameter)?

I ran example 1 for the first time and it seems to work in the sense that I can create a model psf using dev$ypix and the three stars that the help file recommends. But there's nothing that makes the psf stars I select get marked on the image.What do you mean by "when an image display is available, is this running before you start the task?" How would I check this?

If I run the example I see the stars marked in a (very small) red cross, as expected, using either XImtool or DS9 as the display server.In the past there have been issues with DS9 releases not properly handling IRAF image displays so you might try getting the latest version to rule this out (although, it generally breaks everything). You might also try a "gflush" command after you exit the task to flush the graphics streams. Otherwise, if this is a very large image and you are zoomed out, do you see the marker when you zoom all the way into the star (i.e. the marker is drawn in pixel units, not screen units)??

Got it! I have more questions.First, what I had to fix to get it to work: The help file example psf statement has display=imdr, which is something I did not have set (or know what it did) when I was psfing images in the past. So I can set it at the bottom of this file or in the daophot master menu. It seems setting display=imdr* also makes the ubiquitous and ignorable "Graphics overlay not available for display device" warning go away when I do this too. Go figure. But I still get something that shows up now, even in MY images (okay in the magnifier box in ds9). But it works! Thanks!Here's what I want to know:Originally, the display variable in psf is set to read form the daophot master file. In the master package for daophot, display is set to stdimage. What does that do? Is it something I want to change for the whole package. In my login.cl I have a command that sets stdimage to imt2048 so I can see my entire big images. Is that the same thing?Thanks!*I did more searches for imdr and there's an imdb, imdg, and imdy which promise different colored crosses, but I still get red if I try the others. Since red is a color that shows up well against black, white and in between, I don't actually care about this bug.

[quote:d0b7345c1e]Originally, the display variable in psf is set to read form the daophot master file. In the master package for daophot, display is set to stdimage. What does that do? Is it something I want to change for the whole package. In my login.cl I have a command that sets stdimage to imt2048 so I can see my entire big images. Is that the same thing? [/quote:d0b7345c1e]The DAOPHOT package parameters (what you call the 'master file') are a means of setting common values for the package rather than repeating them for each task. In the case of display, the 'stdimage' value refers to the environment variable 'stdimage' which is used to set the frame buffer size. You can use the command GDEVICES to get a listing of the available sizes and then set stdimage appropriately (or the daophot..display param to the haardwired value). In the case of the 'imd' overlay names, these refer to dev$graphcap device entries that specify an overlay device color, this probably isn't appropriate for a general setting since you would want the image display size to be the same as that used when reading the cursor (the IMD device is mapped at 8192x8192 by default).
[quote:d0b7345c1e]I did more searches for imdr and there's an imdb, imdg, and imdy which promise different colored crosses, but I still get red if I try the others. Since red is a color that shows up well against black, white and in between, I don't actually care about this bug.[/quote:d0b7345c1e]I verified that DS9 (at least the version I'm using) draws in multiple colors and that DAOPHOT doesn't hardwire the value, but it's always possible this is a DS9 bug. Do you get colors doing:[code:1:d0b7345c1e]
cl> display dev$pix 1 fill+
cl> contour dev$pix dev=imdg fill+ label-
[/code:1:d0b7345c1e]