ximtool error: no frame buffer config file found
Robert Blum wrote on Aug 14, 2009
Is this important?
blum@deckard_at_12:36>Warning: No frame buffer configuration file found.
os.zgtenv: cannot open `/usr/include/iraf.h'
os.zgtenv: cannot open `/usr/include/iraf.h'
os.zgtenv: cannot open `/usr/include/iraf.h'
blum@deckard_at_12:36>Warning: No frame buffer configuration file found.
os.zgtenv: cannot open `/usr/include/iraf.h'
os.zgtenv: cannot open `/usr/include/iraf.h'
os.zgtenv: cannot open `/usr/include/iraf.h'
Mike Fitzpatrick wrote on Aug 14, 2009
Two errors here: A missing /usr/include/iraf.h means that the iraf install script wasn't run on the machine, and so handly things like the 'mkiraf' and 'cl' commands may not be found. Some of this can be worked around with environment variables and aliases.
The other error is a missing frame buffer config file, i.e. what is normally /usr/local/lib/imtoolrc. This is also created as a symlink to $iraf/dev/imtoolrc when the install script is run, but you can also copy $iraf/dev/imtoolrc to $HOME/.imtoolrc to use it that way. BTW, this is the file that tells ximtool/ds9 what 'imt34' as a stdimage means.
Both problems can be fixed by running the install script.
-Mike
The other error is a missing frame buffer config file, i.e. what is normally /usr/local/lib/imtoolrc. This is also created as a symlink to $iraf/dev/imtoolrc when the install script is run, but you can also copy $iraf/dev/imtoolrc to $HOME/.imtoolrc to use it that way. BTW, this is the file that tells ximtool/ds9 what 'imt34' as a stdimage means.
Both problems can be fixed by running the install script.
-Mike
Robert Blum wrote on Aug 14, 2009
Thanks Mike!
I ran the install script and it has fixed everything as advertised.
-bob
I ran the install script and it has fixed everything as advertised.
-bob
Last post on Aug 14, 2009