[GRASS-dev] Parallelization of GRASS modules for GSOC 2009

I am a Masters student from International Institute of Information Technology-Hyderabad India, looking to participate in google summer of code under the OSGeo umbrella. More specifically, I want to work in the parallelizing GRASS modules using openMP (MPI is also fine).

Slightly confused where to start poking in the code.
Any suggestions on possible modules that have a good scope of coarse grained parallelization in it is welcome.

Please note: I am assuming that all the developers I have talked to earlier are already in this mail. If I missed anybody, please do inform me.

Have been slightly busy yesterday, so didnt put up a full effort in going through the code, forgive me for that.


JYOTHISH SOMAN


The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore, all progress depends on the unreasonable man.
George Bernard Shaw

On Thu, Mar 19, 2009 at 8:27 AM, Jyothish Soman
<jyothish.soman@gmail.com> wrote:

I am a Masters student from International Institute of Information
Technology-Hyderabad India, looking to participate in google summer of code
under the OSGeo umbrella. More specifically, I want to work in the
parallelizing GRASS modules using openMP (MPI is also fine).

That is a great idea - I am sure that many users would benefit from that.

Slightly confused where to start poking in the code.
Any suggestions on possible modules that have a good scope of coarse grained
parallelization in it is welcome.

I guess that some kind of profiling is needed to see where time is
wasted. The "problem" is that much of GRASS' intelligence stays
in the modules. So heavy interpolation modules are certainly
candidates.
Also the vector library (topology building?) might be a candidate.

We could make a quick survey in grass-user to ask people where
they find GRASS slow.

Please note: I am assuming that all the developers I have talked to earlier
are already in this mail. If I missed anybody, please do inform me.

(all are in the list)

Have been slightly busy yesterday, so didnt put up a full effort in going
through the code, forgive me for that.

No problem at all! Here is also the (navigable) manual:
http://download.osgeo.org/grass/grass6_progman/

Please ask if you need specific answers.

Markus

I went through the functions list and my first point of understanding was that the following functions will be nice to be worked into:

in raster functions:
r.terraflow, r.walk,r.watershed,r.water.outlet.

in image functions:
The most obvious one I saw was i.fft and i.ifft. An extension of which would be i.zc.
I went through Yann’s recommendation on i.atcorr, and went through the research paper corresponding to it, Since the concept is new to me, it is possible that I might end up picking the brains of the mentor.

Also beyond parallel, I will be fine with network tool kit also. Is it an active project?.

Whatever happens to my GSOC application, I will be more than happy to work with the developer team at GRASS.

On Thu, Mar 19, 2009 at 10:43 PM, Markus Neteler <neteler@osgeo.org> wrote:

On Thu, Mar 19, 2009 at 8:27 AM, Jyothish Soman
<jyothish.soman@gmail.com> wrote:

I am a Masters student from International Institute of Information
Technology-Hyderabad India, looking to participate in google summer of code
under the OSGeo umbrella. More specifically, I want to work in the
parallelizing GRASS modules using openMP (MPI is also fine).

That is a great idea - I am sure that many users would benefit from that.

Slightly confused where to start poking in the code.
Any suggestions on possible modules that have a good scope of coarse grained
parallelization in it is welcome.

I guess that some kind of profiling is needed to see where time is
wasted. The “problem” is that much of GRASS’ intelligence stays
in the modules. So heavy interpolation modules are certainly
candidates.
Also the vector library (topology building?) might be a candidate.

We could make a quick survey in grass-user to ask people where
they find GRASS slow.

Please note: I am assuming that all the developers I have talked to earlier
are already in this mail. If I missed anybody, please do inform me.

(all are in the list)

Have been slightly busy yesterday, so didnt put up a full effort in going
through the code, forgive me for that.

No problem at all! Here is also the (navigable) manual:
http://download.osgeo.org/grass/grass6_progman/

Please ask if you need specific answers.

Markus


JYOTHISH SOMAN
MS-2008-CS
Center for Security, Theory And Algorithm Research
International Institute of Information Technology
Hyderabad
India
Phone:+91-9966222626
http://www.iiit.ac.in/

The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore, all progress depends on the unreasonable man.
George Bernard Shaw