[GRASS-dev] Re: [GRASS-user] problems using r.proj with large data set

[William Kyngesburye]

On Feb 8, 2007, at 9:11 AM, William Kyngesburye wrote:

>> The only thing that differs between the two is the memory= option.  
>> I'm
>> not sure what needs to be said about that option beyond what's  
>> already
>> in its description string.
>>
> maybe mention it in the description?  Other than the memory option  
> and name

Oops, forgot to finish my thoughts.

Other than the memory option and module name, it doesn't really say  
how it operates differently from r.proj.  Some hint about situations  
one might want to use it would be good.  Maybe mention that there  
will be more disk activity.

Add cross-references in each to the other.  Both see-also links, and  
in r.proj, a hint about using r.proj.seg for large rasters and where  
memory is limited.

> I'll give this a try, it'll help project the second have of this  
> project today if it works.  Since you didn't get any response  
> before, I'll try some timing tests to compare r.proj and  
> r.proj.seg, and compare the data generated, some time in the next  
> week or so.
>
Works great.  Now I can do something else while this is crunching.   
Dual cores is not much help for multitasking when all of memory is  
tied up, causing lots of swapping ^_^

My first impression is that speed (perceived, since I'm not twiddling  
my thumbs) is comparable.  Though there is a lot of disk thrashing  
(good thing the data is on an external drive).


-----
William Kyngesburye <kyngchaos at kyngchaos.com>
http://www.kyngchaos.com/

First Pogril: Why is life like sticking your head in a bucket filled  
with hyena offal?
Second Pogril: I don't know.  Why IS life like sticking your head in  
a bucket filled with hyena offal?
First Pogril: I don't know either.  Wretched, isn't it?

-HitchHiker's Guide to the Galaxy