[GRASS-dev] Contributing code to GRASS?

Tomas Ukkonen tomas.ukkonen at fgi.fi
Fri May 23 05:34:55 EDT 2008


Wolf Bergenheim wrote:
> On 12.05.2008 11:56, Tomas Ukkonen wrote:
>> After studying GRASS implementation a bit it seems
>> that I need only to create independent software modules
>> for each functionality (r.* module) where I define
>> interface for transferring parameters and data between
>> GRASS and our c++ code.
>> Is this correct?
> 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.
Yes I have read GRASS documents and source code to see
how code  should be modularized.
> Looking forward to it. In the meanwhile I'll be happy to help you in
> case you have any more questions.
Thanks. I'm currently in the process of GRASSificating our methods
into GRASS modules. I also already contacted Hamish (see below) for
getting access to GRASS-addons. This will take a while however, because
I have other more pressing duties (writing research papers etc.) to do
before I have time to do some coding. But I will ask you if I need any
help.

-- 
Tomas Ukkonen
Finnish Geodetic Institute
PL 15 (Geodeetinrinne 2)
02431 MASALA, FINLAND




Hi Tomas, 


> > Sometime ago I send an email to the GRASS-dev list and
> > asked for instructions to contribute code to GRASS and was told
> > to get a mentor/sponsor who can grant access to GRASS-Addons
> > repository.
>   

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:
  http://www.osgeo.org/osgeo_userid


After that we can add you to the list!


> > I'm currently working in a project where we have
> > developed/programmed drainage basin delineation
> > (terrain analysis) methods(*) that work better/differently
> > than their GRASS counterparts.  There have been decision to
> > contribute some of this code to GRASS.
>   

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.



> > For that we need write access to GRASS-Addons
> > repository and sponsor/mentor. Based on the
> > postings you seem to be fairly active in the community.
> > 
> > Could you help us get the write access to the repository or
> > point someone else who can?
>   

RFC2:  http://download.osgeo.org/grass/grass6_progman/rfc/
PSC mailing list: http://lists.osgeo.org/mailman/listinfo/grass-psc

It is requested that code conforms to SUBMITTING standards,
  http://trac.osgeo.org/grass/browser/grass/trunk
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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-dev/attachments/20080523/9170a0cd/attachment.html


More information about the grass-dev mailing list