Skip to content
Prev 3637 / 29559 Next

error message when running errorsarlm

On Fri, 23 May 2008, Roger Bivand wrote:

            
Sorry, to put the record straight, finally, I hope - I can provoke similar 
error messages under Windows when either spam or Matrix methods are unable 
to allocate memory - usually the error messages returned from inside spam 
and Matrix are not informative, as the ones initially seen (things like 
"no function to return from, jumping to top level"). I just managed to 
reproduce this with spam on the 1GB Windows machine.

This is happening when the sparse package functions bail out because of 
difficulties allocating memory, but instead of terminating the line 
search, it continues to batter its head on one end of the interval. I'll 
try to make the functions behave more sensitively - which is not easy, 
because the sparse package functions can fail for a number of reasons, 
like lambda leaving its range, that are acceptable, or running out of 
memory on Windows, which isn't. On Linux 1GB, the underlying better memory 
management systems seem to protect us from this infelicity.

The base conclusion remain the same - weights should really be sparse, so 
do look at the output of the print method for neighbour objects! Neither 
method has any trouble with really sparse weights for this size of data 
set.

Roger