Parallel GRASS

[James A. Farley]

> 
> 
> ----- Begin Included Message -----
> 
> >From grass-lists-owner at max.cecer.army.mil Wed Oct 13 10:59:53 1993
> Return-Path: <grass-lists-owner at max.cecer.army.mil>
> From: svdhara at npac.syr.edu (Sastry V. Dhara)
> Precedence: Bulk
> Subject: Parallel GRASS
> Content-Length: 550
> X-Lines: 29
> 
> 
> We are trying to rewirite parts of GRASS code to be run
> on Parallel Machines.
> 
> We are trying to identify those functions that are 
> compuatationally intensive.
> 
> The functions we identified so far are:
> 
> r.mapcalc and r.buffer
> 
> Can you suggest any other functions that take a lot of
> CPU time ?
> 
> Also, I request those who are already doing this kind of
> work to share their experiences here.
> 
> Or, you can send me mail directly.
> 
> Thanks.
> 
> Sastry Dhara
> Northeast Parallel Architectures Center
> Syracuse University
> Syracuse, NY 13244
> 
> 
You might add r.los and the surface generation modules to the list.


-- 
James A. Farley 		Technical Director, CAST/NCRI-SW
						12 Ozark Hall, Univ. of Arkansas
jim at cast.uark.edu		Fayetteville, AR  72701
Voice: (501) 575-6159	FAX  : (501) 575-3846