gmos gdisplay
Elizabeth Wehner wrote on Jun 21, 2006
Hi,
I'm having trouble displaying gmos imaging fits files using gdisplay. When I set stdimage=imt4096 and use mscimage with fill+ it displays the same MEFs just fine, but when I set stdimage=imtgmos and use gdisplay, nothing shows up in ds9 and I get a lengthy (one error message per column, perhaps?) scroll of errors like this:
ximtool: attempted write out of bounds on framebuf
write 12800 bytes at [0,1174]
ximtool: attempted read out of bounds on framebuf
read 12800 bytes at [0,1172]
ximtool: attempted write out of bounds on framebuf
write 12800 bytes at [0,1172]
ximtool: attempted read out of bounds on framebuf
read 12800 bytes at [0,1170]
any advice?
thanks!
I'm having trouble displaying gmos imaging fits files using gdisplay. When I set stdimage=imt4096 and use mscimage with fill+ it displays the same MEFs just fine, but when I set stdimage=imtgmos and use gdisplay, nothing shows up in ds9 and I get a lengthy (one error message per column, perhaps?) scroll of errors like this:
ximtool: attempted write out of bounds on framebuf
write 12800 bytes at [0,1174]
ximtool: attempted read out of bounds on framebuf
read 12800 bytes at [0,1172]
ximtool: attempted write out of bounds on framebuf
write 12800 bytes at [0,1172]
ximtool: attempted read out of bounds on framebuf
read 12800 bytes at [0,1170]
any advice?
thanks!
Mike Fitzpatrick wrote on Jun 21, 2006
The 'imtgmos' frame buffer is 6400x4644, but from the error messages it looks like you're using the imtgmos4 buffer which is 1600x1161 and was set up for binned images. With the mscimage fill parameter the display will scale up or down to fit the frame buffer, however GDISPLAY looks for a binning parameter and adjusts the magnification itself.
Double check your stdimage setting (I think it is an output of the task anyway) as well as binning keywords in the header. Another possibility is that the frame buffer configuration file being used (/usr/local/lib/imtoolrc is a symlink to iraf$dev/imtoolrc) doesn't have this configuration. Have a look at the file and check that imtgmos is there and that you're using at least the V2.12.2a release.
Cheers,
-Mike
Double check your stdimage setting (I think it is an output of the task anyway) as well as binning keywords in the header. Another possibility is that the frame buffer configuration file being used (/usr/local/lib/imtoolrc is a symlink to iraf$dev/imtoolrc) doesn't have this configuration. Have a look at the file and check that imtgmos is there and that you're using at least the V2.12.2a release.
Cheers,
-Mike
Elizabeth Wehner wrote on Jun 21, 2006
fitz
Another possibility is that the frame buffer configuration file being used (/usr/local/lib/imtoolrc is a symlink to iraf$dev/imtoolrc) doesn't have this configuration. Have a look at the file and check that imtgmos is there and that you're using at least the V2.12.2a release.
This one did the trick. I'm using the scisoft version on my Mac, so there wasn't a symbolic link to imtoolrc in /usr/local/lib/. Once I added it, gdisplay worked.
Thanks!
Last post on Jun 21, 2006