Error messages

Errors can occur in the gstat code or during the matrix operations in the meschach matrix library. The cause of and possible solutions to the latter are explained in the second part of this section. Following is a list of the gstat error messages (with exit values).

variable not set: ... (2)

the named variable should have been set in the command file.

variable outside valid range: ... (3)

the named variable is outside its valid range (e.g. negative, where it should be positive).

value not allowed for: ... (4)

the named variable got a value that was not allowed (e.g. outside the valid range, or in contradiction to other settings)

no file name set: ... (5)

a file name was not set where it should.

write failed on file `...' (6)

could not write the named file (e.g. no write permission, file system full,...).

read failed on file `...' (7)

could not read the named file (e.g. file does not exist, no read permission,...).

cannot read real value from `...' (8)

could not transform the named string into a real number.

cannot read integer from `...' (9)

could not transform the named string into an integer.

syntax error: ... (10)

a syntax error occured in the file, at the position pointed to.

argument option error on `...' (11)

the named command line argument is erroneous.

domain (math) error on `...' (12)

math domain error

out of dynamic memory (13)

Memory resources exhausted.
Try set percell=1; reduce problem size or increase computer resources (e.g. platform, memory, swap space).

i/o error: ... (14)

interactive mode cannot be combined with redirected input or output streams.

no command file (15)

no command file was specified.

no user interface available (16)

error while writing to a pipe (17)

error while reading to a pipe (18)

operation not allowed in secure mode (19)

error in meschach matrix libary (20)

followed by further notification on what happened and hints on how this can be resolved

general error: ... (-1)

and the next,

NULL argument in function `...' (1)

should not occur, please report this type of error the author (use command line option -d2).

Other possible errors are:

error during variogram fit (no exit from user interface)

If you specify for instance a variogram model:

variogram(a): 1sph(2) + 1sph(2);

then the two models are linearly dependent--fitting their sill will lead to a singularity. Also, if, at a nonlinear fit, the range of a model tends to infinity, the true model may have to be a linear model (having one parameter), but two parameters are being fit for it--they will then be linearly dependent and lead to a singularity during fit. Solution: simplify the variogram model.

Matrix not positive definite

or other error messages from the meschach matrix library Apart from out-of-memory errors (see above) the meschach may terminate program execution when it encounters a matrix singularity, e.g. with

matrix not positive definite in function CHfactor()

or

singular matrix in function LDLfactor()

These two error messages may occur (a) during simulation, when an observation falls almost exactly at a simulation location (b) when two observations occur at identical location occur and noaverage was defined in its data definition. Solution to (a): increase the value of zero, to (b): remove the noaverage. Read also the next section.