<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Wolf Bergenheim wrote:
<blockquote cite="mid:48348D6A.6060302@bergenheim.net" type="cite">On
12.05.2008 11:56, Tomas Ukkonen wrote:
<br>
<blockquote type="cite">After studying GRASS implementation a bit it
seems
<br>
that I need only to create independent software modules
<br>
for each functionality (r.* module) where I define
<br>
interface for transferring parameters and data between
<br>
GRASS and our c++ code.
<br>
Is this correct?
<br>
</blockquote>
Yes. In grass each functionality is wrapped in a stand-alone module.
There are library functions that will allow you to set up a standard
GRASS command line interface. See [1] for the programmer's manual. Also
have a look at the example raster module to get an idea on how to set
up the module to be a GRASS module, and how to access the GRASS raster
files.
<br>
</blockquote>
Yes I have read GRASS documents and source code to see <br>
how code should be modularized. <br>
<blockquote cite="mid:48348D6A.6060302@bergenheim.net" type="cite">Looking
forward to it. In the meanwhile I'll be happy to help you in case you
have any more questions.
<br>
</blockquote>
Thanks. I'm currently in the process of GRASSificating our methods <br>
into GRASS modules. I also already contacted Hamish (see below) for <br>
getting access to GRASS-addons. This will take a while however, because
<br>
I have other more pressing duties (writing research papers etc.) to do <br>
before I have time to do some coding. But I will ask you if I need any
help. <br>
<br>
<pre class="moz-signature" cols="72">--
Tomas Ukkonen
Finnish Geodetic Institute
PL 15 (Geodeetinrinne 2)
02431 MASALA, FINLAND
</pre>
<div class="moz-text-plain" wrap="true" graphical-quote="true"
style="font-family: -moz-fixed; font-size: 12px;" lang="x-western">
<pre wrap="">Hi Tomas,
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">> </span>Sometime ago I send an email to the GRASS-dev list and
<span class="moz-txt-citetags">> </span>asked for instructions to contribute code to GRASS and was told
<span class="moz-txt-citetags">> </span>to get a mentor/sponsor who can grant access to GRASS-Addons
<span class="moz-txt-citetags">> </span>repository.
</pre>
</blockquote>
<pre wrap=""><!---->
Sure. please post a message to the grass-psc mailing list stating that you have read and agree to GRASS's RFC2 document regarding our software license terms (the GPL) and wish to have access to the grass-addons repo. Please also post the OSGeo user ID you would like to use. if you don't have an OSGeo login, you can create yourself one:
<a class="moz-txt-link-freetext"
href="http://www.osgeo.org/osgeo_userid">http://www.osgeo.org/osgeo_userid</a>
After that we can add you to the list!
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">> </span>I'm currently working in a project where we have
<span class="moz-txt-citetags">> </span>developed/programmed drainage basin delineation
<span class="moz-txt-citetags">> </span>(terrain analysis) methods(*) that work better/differently
<span class="moz-txt-citetags">> </span>than their GRASS counterparts. There have been decision to
<span class="moz-txt-citetags">> </span>contribute some of this code to GRASS.
</pre>
</blockquote>
<pre wrap=""><!---->
Yes I remember your post well and was meaning to respond to it. At the time you sent it I was 4 days into a r.watershed calculation.
[5000x5000 cell region (10m DEM, 1000 sq km in catchments of interest) r.watershed took about 4-5 days to run and used 1.0-1.5 gb RAM, and I had to run it a few times to get the threshold as I liked]
I would mention out of interest that the original author of r.watershed stops by the grass mailing list now and then, even though the code is very many years old now.
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">> </span>For that we need write access to GRASS-Addons
<span class="moz-txt-citetags">> </span>repository and sponsor/mentor. Based on the
<span class="moz-txt-citetags">> </span>postings you seem to be fairly active in the community.
<span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>Could you help us get the write access to the repository or
<span class="moz-txt-citetags">> </span>point someone else who can?
</pre>
</blockquote>
<pre wrap=""><!---->
RFC2: <a class="moz-txt-link-freetext"
href="http://download.osgeo.org/grass/grass6_progman/rfc/">http://download.osgeo.org/grass/grass6_progman/rfc/</a>
PSC mailing list: <a class="moz-txt-link-freetext"
href="http://lists.osgeo.org/mailman/listinfo/grass-psc">http://lists.osgeo.org/mailman/listinfo/grass-psc</a>
It is requested that code conforms to SUBMITTING standards,
<a class="moz-txt-link-freetext"
href="http://trac.osgeo.org/grass/browser/grass/trunk">http://trac.osgeo.org/grass/browser/grass/trunk</a>
For the grass-addons it is only suggested, for inclusion in main GRASS source code it is required.
I look forward to seeing your contributions!
thanks,
Hamish
</pre>
</div>
</body>
</html>