The CUTEr package is distributed with three default ``sizes'': large, medium, and small. In addition, there is a custom size, which, as the term indicates, may be suitable for situations demanding a specialized configuration. These sizes refer to the size of the memory available for problem decoding and solution, and hence are directly related to the size (the amount of data) of the problems that CUTEr can tackle. It may happen that the predetermined sizes do not fit your favorite problem or your machine, and that you wish to specify your own. Typically, when running too large a problem, CUTEr will complain that one of the size parameters is too small and stop. You then have to increase this parameter (if this is possible on your machine) in order to handle the problem. This modification of the CUTEr array sizes is explained below.
We first note that the dependency on problem size occurs in both the decoding of the problem SIF file into data structures and subroutines and in the computation of the required problem values by the provided evaluation tools. Indeed, the problem dependent data is fully specified by its associated SIF file and must be taken into account in all stages up to the numerical solution process. Therefore, the size of both the SIF decoder and the tools (and indeed, the interface optimizers) must be adequate for the problem.
The actual choice of one of the predetermined sizes is made when running the install_cuter command, which prompts the user for the desired size. In fact, install_cuter, or the Makefiles, depending on which CUTEr you are using, cast the source code against a ``size mask'' corresponding to the selected size, and thereby determines the dimensions of the various arrays used in the code. The assignment statements are differentiated by their first four characters:
| CBIG | specifies the large size |
| CMED | the medium size |
| CTOY | the small size |
| CCUS | the custom size |
Note that the custom size is first thought of as larger than the large size, but nothing prevents the user from building an intermediary size or a smaller size than the toy size.
Changing the size of the CUTEr distribution in the sense just described may call for a partial re-installation. If most (or all) parameters must be, say, increased, it might be worth considering simply re-installing CUTEr using a larger size (e.g. large if medium turns out to be insufficient for your purposes). To that end, execute install_cuter again and select the correct size. In case very few parameters need to be changed, the procedure described below might be considered. We now examine this procedure in more detail.