[GRASS5] R.flow again

[Michael Barton]

Good idea. I'll try it today.

MIchael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton



> From: Moritz Lennert <mlennert at club.worldonline.be>
> Date: Tue, 06 Dec 2005 11:55:37 +0100
> To: Michael Barton <michael.barton at asu.edu>
> Cc: grass5 <grass5 at grass.itc.it>
> Subject: Re: [GRASS5] R.flow again
> 
> Michael Barton wrote:
>> OK, now something even stranger is happening with r.flow.
>> 
>> I just did a script to create a net erosion/deposition map using USPED.
>> I¹ve tested it on the Spearfish data set. It includes r.flow, running
>> from the CLI of course.
>> 
>> If I zoom into to a very small area (205x172), it works like a charm.
>> But if I zoom out a little bit, r.flow bombs with the error below.
>> 
>> If I try the same zoom levels with the CLI for r.flow, it works fine.
>> Both are actually running r.flow via the CLI. However, the script is
>> started from a tcltk dialog. Does anyone have any idea what is going on
>> here? This script is nice to automate a tedious set of calculations.
>> 
> 
> [...]
> 
>> ------------------------------------------------------------------------
>> Run from script at 479x472 (as above) and r.flow bombs with the
>> following message
>> 
>> ------------------------------------------------------------------------
>> Opening output files...done.
>> Allocating memory: elevation, aspect, density, e/w distances,
>> quantization tolerances.
>> Reading input files: elevation...
>> .
>> Precomputing: tangents, e/w distances, quantization tolerances,
>> interpolated border elevatio
>> ns, aspects.
>> Working...done.
>> Writing density file...WARNING: 'cell/test' was found in more mapsets
>> (also found in user1).
>> done.
>> Closing files...done.
>> De-allocating memory...done.
>> GRASS 6.1.cvs (spearfish60_valencia):~ > r.usped &
> 
> Have you tried running the _script_ from the CLI, i.e. by giving it its
> parameters directly, and not via the tcltk interface ?
> 
> Moritz