Debug information

Although the gstat error messages are intended to clarify what went wrong, sometimes more information is needed to solve the problem. Extra information on various subjects can be printed during program execution, by setting the debug level to a specific value, e.g. to 9 by the command

set debug = 9;

or by setting the equivalent command line option -d 9 (section 5.2). All debug information (``help information'') is written to the screen (stdout) but can be redirected to a log file by the command

set logfile = 'gstat.log';

or by the command line option -l gstat.log. Allowed values for the debug level, and their effect are listed in table C.4.

Table C.1: values for debug and their output

debug	output
0	suppres any output except warning and error messages
1	normal output (default): short data report, program action and mode, program progress in %, total execution time
2	print the value of all global variables, all files read and written, and include source file name and line number in error messages
4	print OLS and WLS fit diagnostics
8	print all data after reading them
16	print the neighbourhood selection for each prediction location
32	print (generalised) covariance matrices, design matrices, solutions, kriging weights, etc.
64	print variogram fit diagnostics (number of iterations and variogram model in each iteration step) and order relation violations (indicator kriging values before and after order relation correction)
128	print warning on forced neighbourhoods (see force)
256	print, instead of program progress in %, for gridded prediction or simulation the current row and column number, or else the current record number
512	print block (or area) discretization data for each prediction location

To combine options, their values are summed. For instance, setting the debug level to 3 invokes both levels 1 and 2; setting it to 1023 would invoke them all. (Note that in certain circumstances, the log file size can become huge.)

Plotting kriging weights

When gstat is used for kriging prediction and the plot file name is defined, with for instance the command:

set plotfile='plot.gp';

then kriging weights are printed to the plot file is such a way that they can, for each prediction location, be plotted with gnuplot, using

gnuplot plot.gp