Skip to content
Prev 10386 / 29559 Next

assertion failure on call to r.cost & v.what.rast

On Wed, 15 Dec 2010, Colin Bleay wrote:

            
Colin,

Please repost this on grass-stats:

http://grass.osgeo.org/statsgrass/index.php

as it is only marginally an R question. You may be able to put your 
execGRASS() calls in a try(), but I suspect that because it is running 
through system(), the answer is perhaps on the GRASS side, and may not be 
practical or easy. It may well be that the GRASS program is trying to use 
resources on your computer that Kerberos has locked - the g_mechListLock 
variable does not seem to be used in GRASS, and the g_initialize.c file 
seems to be part of Kerberos, not GRASS. How this works on Windows is not 
for regular humans to know about, I'm afraid.

Is your machine running under a tight security regime, perhaps? Can you 
try out your script on a different computer not using networked disk 
drives? It could also be a function of the environment in which the GRASS 
Windows binaries were built. Can you try having the repeated calls to 
execGRASS() separated by pauses, or have it do something else to let 
Kerberos recover its posture?

Roger