ISOCAM Interactive Analysis User's Manual Version 5.0 - ISO - ESA

12 CHAPTER 2. ABOUT CIA
LOG Log file reporting verbosity. Ranging from 1 to 3 for increasing verbosity.
SCREEN Screen reporting verbosity. Ranging from 1 to 3 for increasing verbosity.
XWARN CIA uses IDL’s keyword inheritance. Setting this flag will alert you if a supplied
keyword parameter is not known by the called routine. If a warning appears, you
have either deliberately specified a keyword used by a low level routine or mistyped
the keyword (in which case it will be ignored). For example:
CIA> !ciaerr.xwarn=1
CIA> corr_dark, pds, /goodbye, /hello
CORR_DARK: Undefined keywords: /GOODBYE/HELLO
Dark correction with model and no scaling
• inclusion of contributed routines to CIA’s path. (Only for VMS, under Unix these routines
are included by default).
• setting the level of the on-line help (see section 2.3.2). Either the complete help for all
routines (Programmer’s Help) or only the help for high-level routines (User’s Help) is
displayed.
• defining whether the alias file is run.
• inclusion of your routines in IDL’s search path.
• Some users have reported problems running CIA on 24 bit X-Windows displays. One
suggested solution is to force IDL to use an 8 bit PseudoColor. To do this, uncomment
the following line to your CIA startup file:
device, pseudo_color=8
or to force IDL to use true color (24 bit) visuals
device, true_color=24
device,decompose=0
.run $cia_vers/graphics/xloadct_5_4.pro
and comment the line
.run $cia_vers/graphics/xloadct_3_6.pro
For more on this topic look for information on the procedure DEVICE in the IDL online
help.
Other solutions to this problem, that does not involve the CIA startup file, is suggested
in Section 2.4.
As already stated, all of the above can be configured in a CIA user startup file. The
following sections describe how you can create your own CIA startup file on both the
UNIX and VMS platforms.