display @ mac os x
Paula R. T. Coelho wrote on Mar 10, 2006
hello,
i'm working on photometry taken in gemini, which has a fits file organized in MEFs. in order to work easier with other packages i'm used to imcopy the gemini file to a "normal" fits file. something like :
imcopy halo_pos2_i[sci,1,inherit] foo
i realized that when i do this at mac os x, the image is displayed smaller than the original one.
fxhead shows me the size of the image is ok
gmos> fxhead halo_pos2_i.fits,foo.fits
EXT# EXTTYPE EXTNAME EXTVE DIMENS BITPI INH OBJECT
0 halo_pos2_i.fits 16 M32 Halo pos
1 IMAGE SCI 1 3108x2304 -32 F M32 Halo pos
0 foo.fits 3108x2304 -32 M32 Halo pos
but at ds9 the original image ranges in x 356 - 2730 while foo ranges 760 - 2340.
i understand is something about display task
gdisplay halo_pos2_i 1 -> works (gdisplay from gemini package)
display foo 1 -> don't
display halo_pos_2_i[sci,1] 1 -> don't either
but puzzles me that this happens only at my mac and not when i run iraf on a linux machine.
help??
thx
paula
i'm working on photometry taken in gemini, which has a fits file organized in MEFs. in order to work easier with other packages i'm used to imcopy the gemini file to a "normal" fits file. something like :
imcopy halo_pos2_i[sci,1,inherit] foo
i realized that when i do this at mac os x, the image is displayed smaller than the original one.
fxhead shows me the size of the image is ok
gmos> fxhead halo_pos2_i.fits,foo.fits
EXT# EXTTYPE EXTNAME EXTVE DIMENS BITPI INH OBJECT
0 halo_pos2_i.fits 16 M32 Halo pos
1 IMAGE SCI 1 3108x2304 -32 F M32 Halo pos
0 foo.fits 3108x2304 -32 M32 Halo pos
but at ds9 the original image ranges in x 356 - 2730 while foo ranges 760 - 2340.
i understand is something about display task
gdisplay halo_pos2_i 1 -> works (gdisplay from gemini package)
display foo 1 -> don't
display halo_pos_2_i[sci,1] 1 -> don't either
but puzzles me that this happens only at my mac and not when i run iraf on a linux machine.
help??
thx
paula
Mike Fitzpatrick wrote on Mar 10, 2006
As long as the IMSTAT output is the same I wouldn't worry. DS9 as a server can only display the pixel values approximated by the z1/z2 value. In the DISPLAY task these are done using a grid of about 1000 spread across the image. GDISPLAY on the other hand may do a different scaling because of image binning or magnification, and so arrive at different z1/z2 values.
See the recent post on 'xiraf and ds9' for more about the problem, but keep in mind the values displayed are only approximate. XImtool will display actual values and WCS, similarly commands in IMEXAM will print actuals pixels/wcs.
-Mike
See the recent post on 'xiraf and ds9' for more about the problem, but keep in mind the values displayed are only approximate. XImtool will display actual values and WCS, similarly commands in IMEXAM will print actuals pixels/wcs.
-Mike
Paula R. T. Coelho wrote on Mar 10, 2006
hello mike,
what i mean is that the physical size of the image displayed is smaller, not the scale. only the central part is shown with display, not the entire image.
i mean, using gdisplay (or opening directly from ds9) i see the center of my galaxy, which lays close to one of the corners of the image.
but if i use display, i don´t see it. because slices of the image at all borders are really cut off.
i realized i can workaround this simply opening the image directly in ds9 and then working on it normally.
but i think this is somehow curious anyway, also because it happens on my mac but not in my linux machine...
cheers,
paula
what i mean is that the physical size of the image displayed is smaller, not the scale. only the central part is shown with display, not the entire image.
i mean, using gdisplay (or opening directly from ds9) i see the center of my galaxy, which lays close to one of the corners of the image.
but if i use display, i don´t see it. because slices of the image at all borders are really cut off.
i realized i can workaround this simply opening the image directly in ds9 and then working on it normally.
but i think this is somehow curious anyway, also because it happens on my mac but not in my linux machine...
cheers,
paula
Paula R. T. Coelho wrote on Mar 10, 2006
ops! i just saw the other post you mentioned. i´ll check out about the /usr/local/lib/imtoolrc symlink. sorry...
paula
paula
Paula R. T. Coelho wrote on Mar 10, 2006
ok, here's how i solved: i have to set stdimage=imtgmos or imtgmos2, then display shows the full image. with the imtgmos4 (my default at other linux plataform) or imtgmos8, the image is not shown entirely.
Last post on Mar 10, 2006