stdimage options for large (14K) image?
Adrienne Cool wrote on Jul 21, 2006
Hello,
Does anyone know how to set stdimage to allow
a very large image to be displayed? I am using
imt8192 at the moment,
set stdimage = imt8192
but now have a 14,000x14,000 pixel mosaic to display,
and don't know how to find out what other bigger buffer
options are (if any).
Thanks...!
Adrienne
Does anyone know how to set stdimage to allow
a very large image to be displayed? I am using
imt8192 at the moment,
set stdimage = imt8192
but now have a 14,000x14,000 pixel mosaic to display,
and don't know how to find out what other bigger buffer
options are (if any).
Thanks...!
Adrienne
Emilliano Gregori wrote on Jul 21, 2006
Hello Adrienne,
I'm not sure, but the definition of stdimage modes is contained in file imtoolrc, which should be located in /usr/local/lib/
Here is an excerpt of mine:
maybe you can just add a new configuration, and call it, say, imt14000,
then, probably, you should tell to IRAF to use it.
In my login.cl I have a line:
maybe just uncomment it and set to imt14000.
Cheers,
Emiliano
P.S.: maybe, as the imtoolrc file says, you need to edit the graphcap file...?
I'm not sure, but the definition of stdimage modes is contained in file imtoolrc, which should be located in /usr/local/lib/
Here is an excerpt of mine:
# IMTOOLRC -- Predefined frame buffer configurations. The value of nframes
# given is the initial number of frame buffers allocated; more frames can be
# added at runtime. The configuration numbers may be given in any order but
# must be unique and in the range 1-128. NOTE - corresponding entries must be
# present in the dev$graphcap file, for use with IRAF. This file is used by
# both the IMTOOL and SAOIMAGE display servers.
#
# Format: configno nframes width height
1 2 512 512 # imt1|imt512
2 2 800 800 # imt2|imt800
3 2 1024 1024 # imt3|imt1024
4 1 1600 1600 # imt4|imt1600
5 1 2048 2048 # imt5|imt2048
6 1 4096 4096 # imt6|imt4096
7 1 8192 8192 # imt7|imt8192
maybe you can just add a new configuration, and call it, say, imt14000,
then, probably, you should tell to IRAF to use it.
In my login.cl I have a line:
#set stdimage = imt800
maybe just uncomment it and set to imt14000.
Cheers,
Emiliano
P.S.: maybe, as the imtoolrc file says, you need to edit the graphcap file...?
Mike Fitzpatrick wrote on Jul 21, 2006
Emiliano almost has the complete answer: Frame buffers are configured by editing both the imtoolrc file and the dev$graphcap file. From the FAQ:
The GDEVICES command will print a listing of the currently available buffers.
Cheers,
-Mike
What do I change to add a custom frame buffer size?
There are two files that need to be modified to create your own frame
buffer size, imtoolrc and graphcap. You will need to restart the display
window to activate these changes.
o First you need to copy over the system imtoolrc file into your home
directory, and then modify the file so it reflects your new frame
buffer size. Note the name change during the copy.
% cd
% cp /iraf_path/dev/imtoolrc .imtoolrc
% vi .imtoolrc
Go to the end of the file and add an entry for your particular frame
buffer following the examples in the file (contrary to what is in the
file, keep you frame numbers less than 64).
o Next, copy over the system graphcap file and edit it in a similar fashion
following the examples under the "STDIMAGES devices" section. Now when
you log into IRAF point to this new graphcap file, and then reset the
value for stdimage.
% cp /iraf_path/dev/graphcap mygraphcap
% vi mygraphcap
[restart the display window and log into the CL]
cl> reset graphcap = /home_path/mygraphcap
cl> gflush
cl> reset stdimage = my_new_frame_buffer
When editing the graphcap entry be sure to modify the ":cn" (configuration
number) field as well as the buffer sizes (the :xr and :yr fields as well
as the DD string). After resetting the graphcap environment variable be
sure to type a 'gflush' to reinitialize the graphics system.
The GDEVICES command will print a listing of the currently available buffers.
Cheers,
-Mike
Emilliano Gregori wrote on Jul 21, 2006
Hello Mike,
many thanks... I edited the message while you were posting your :D :D
many thanks... I edited the message while you were posting your :D :D
Last post on Jul 21, 2006