#1449: R.SUN posible implementation
-------------------------+--------------------------------------------------
Reporter: Levid | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.2
Component: Default | Version: unspecified
Keywords: r.sun | Platform: MSWindows 7
Cpu: Unspecified |
-------------------------+--------------------------------------------------
I wrote a new algorithm for r.sun
it was wrote in C and the same estructure for future implementation in
GRASS.
attach 2 source code, one is the algorithm executable in console
and another is source code for GRASS, have descriptive names.
---------- Forwarded message ----------
From: GRASS GIS <trac@osgeo.org>
Date: 2011/9/14
Subject: [GRASS GIS] #1449: R.SUN posible implementation
To:
#1449: R.SUN posible implementation
-------------------------±-------------------------------------------------
Reporter: Levid | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.2
Component: Default | Version: unspecified
Keywords: r.sun | Platform: MSWindows 7
Cpu: Unspecified |
-------------------------±-------------------------------------------------
I wrote a new algorithm for r.sun
it was wrote in C and the same estructure for future implementation in
GRASS.
attach 2 source code, one is the algorithm executable in console
and another is source code for GRASS, have descriptive names.
Replying to [ticket:1449 Levid]:
> I wrote a new algorithm for r.sun
> it was wrote in C and the same estructure for future implementation in
GRASS.
> attach 2 source code, one is the algorithm executable in console
> and another is source code for GRASS, have descriptive names.
What is wrong with source:grass/trunk/raster/r.sun in the first place? I
can now see #498, #1446 and #2014 by a quick search. Or, is it about this
REST2 model?
I haven't looked into this patch to see what it does, but it is worth
noting that different researchers will like to use different algorithms
that make different compromises in order to achieve different goals. It
may be a good thing to have REST2, SOLPOS, and r.sun's algorithm as
options.