Initialization File

The default initialization file icc.ini is shown in Example 2-1 .

Example 2-1 Initialization file icc.ini

[Verbose] [ProfilePath]
profiles/ [ImagePath] images/ [DataPath] data/ [NumberOfTests] 30 [Tests]

IC_lhints.scr IC_conerr.scr IC_lana.scr IC_eval.scr IC_lmany.scr

IC_optspeed.scr IC_connect.scr IC_evalmany.scr IC_attr1.scr IC_attr2.scr

IC_layouts.scr IC_conmany.scr IC_optsize.scr IC_evalerr.scr IC_update1.scr

IC_update2.scr IC_xprofile.scr IC_xprofilehost.scr IC_xprofilesav.scr

IC_xprofilesavremote.scr IC_xwindow.scr IC_xwindowerr.scr IC_xdisplay.scr

IC_evalplus.scr IC_pacbug.scr IC_loadsol.scr IC_sun_update.scr IC_gray.scr

IC_gamut.scr IC_lut.scr

The icc.ini file does not include the tests, IC_xprofilesavroot.scr and IC_updatewin.scr, which must be run as root. To run IC_xprofilesavremote.scr, you need to change the DISPLAY environment variable. See the comments in the automated test scripts (auto-kcmstest and auto-kcmstest-root) for details.

The icc.ini file contains the path to the profiles, images, and data required to run the test scripts. In addition, it lists the number of test scripts following the [NumberOfTests] field, and it lists the filename of each test script.

If your CMM requires a different set of test scripts, you can create an alternate initialization file. Say, for example, you edited several of the scripts to test special features of your CMM. In such a case you need to install the scripts you plan to test with in the script directory. To add to the existing initialization file, you also must create an alternate file that reflects test script changes. See "Creating An Alternate Initialization File" ," for details.