I must have missed this thread at the time:
http://grass.itc.it/pipermail/grass-dev/2006-April/022612.html
I've just noticed that r.terraflow has its own licence which isn't
compatible with the GPL (advertising clause), so we shouldn't be
providing binaries.
Ideally, we should have an --enable-nongpl switch so that people don't
trip over this accidentally. Or, better still, just remove all non-GPL
code.
--
Glynn Clements <glynn@gclements.plus.com>
I will try to contact Laura and see whether she has any plans for maintaining it and
changing the license. If not, I suggest to remove it, although we will lose
the multiple flow direction flow routing (maybe it could be added to r.watershed?)
and the capability to process larger DEMs (not possible with r.watershed).
There is a new system available called terrastream with many new additional
options and Pfaffstetter-code based watershed hierarchy output, which is better and
faster and can be run as GRASS module, but users will have to download and compile
it by themselves - link can be provided on wiki add-on list.
The code is huge, C++ and would be hard to maintain within GRASS.
so give me few days to see whether I can get in touch with Laura and we can then
do what will be most appropriate,
Helena
Helena Mitasova
Dept. of Marine, Earth and Atm. Sciences
1125 Jordan Hall, NCSU Box 8208,
Raleigh NC 27695
http://skagit.meas.ncsu.edu/~helena/
On Oct 19, 2007, at 6:47 PM, Glynn Clements wrote:
I must have missed this thread at the time:
http://grass.itc.it/pipermail/grass-dev/2006-April/022612.html
I've just noticed that r.terraflow has its own licence which isn't
compatible with the GPL (advertising clause), so we shouldn't be
providing binaries.Ideally, we should have an --enable-nongpl switch so that people don't
trip over this accidentally. Or, better still, just remove all non-GPL
code.--
Glynn Clements <glynn@gclements.plus.com>_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev
Thanks for keeping track of this useful but sometimes troublesome
module. I am very interested in the potential for modern watershed
analysis via a 3-rd party package like terrastream.
Thanks!
Dylan
On 10/19/07, Helena Mitasova <hmitaso@unity.ncsu.edu> wrote:
I will try to contact Laura and see whether she has any plans for
maintaining it and
changing the license. If not, I suggest to remove it, although we
will lose
the multiple flow direction flow routing (maybe it could be added to
r.watershed?)
and the capability to process larger DEMs (not possible with
r.watershed).There is a new system available called terrastream with many new
additional
options and Pfaffstetter-code based watershed hierarchy output, which
is better and
faster and can be run as GRASS module, but users will have to
download and compile
it by themselves - link can be provided on wiki add-on list.
The code is huge, C++ and would be hard to maintain within GRASS.so give me few days to see whether I can get in touch with Laura and
we can then
do what will be most appropriate,Helena
Helena Mitasova
Dept. of Marine, Earth and Atm. Sciences
1125 Jordan Hall, NCSU Box 8208,
Raleigh NC 27695
http://skagit.meas.ncsu.edu/~helena/On Oct 19, 2007, at 6:47 PM, Glynn Clements wrote:
>
> I must have missed this thread at the time:
>
> http://grass.itc.it/pipermail/grass-dev/2006-April/022612.html
>
> I've just noticed that r.terraflow has its own licence which isn't
> compatible with the GPL (advertising clause), so we shouldn't be
> providing binaries.
>
> Ideally, we should have an --enable-nongpl switch so that people don't
> trip over this accidentally. Or, better still, just remove all non-GPL
> code.
>
> --
> Glynn Clements <glynn@gclements.plus.com>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev
r.terraflow is a critical piece of our r.landscape.evol script (GRASS
Addons/LandDyn) that models long-term surface process dynamics. I sincerely
hope that we can solve any licensing issues or have it replaced with a
better module. There is nothing else in the GRASS repertoire that actually
replaces it.
Michael
On 10/19/07 9:16 PM, "Dylan Beaudette" <dylan.beaudette@gmail.com> wrote:
Thanks for keeping track of this useful but sometimes troublesome
module. I am very interested in the potential for modern watershed
analysis via a 3-rd party package like terrastream.Thanks!
Dylan
On 10/19/07, Helena Mitasova <hmitaso@unity.ncsu.edu> wrote:
I will try to contact Laura and see whether she has any plans for
maintaining it and
changing the license. If not, I suggest to remove it, although we
will lose
the multiple flow direction flow routing (maybe it could be added to
r.watershed?)
and the capability to process larger DEMs (not possible with
r.watershed).There is a new system available called terrastream with many new
additional
options and Pfaffstetter-code based watershed hierarchy output, which
is better and
faster and can be run as GRASS module, but users will have to
download and compile
it by themselves - link can be provided on wiki add-on list.
The code is huge, C++ and would be hard to maintain within GRASS.so give me few days to see whether I can get in touch with Laura and
we can then
do what will be most appropriate,Helena
Helena Mitasova
Dept. of Marine, Earth and Atm. Sciences
1125 Jordan Hall, NCSU Box 8208,
Raleigh NC 27695
http://skagit.meas.ncsu.edu/~helena/On Oct 19, 2007, at 6:47 PM, Glynn Clements wrote:
I must have missed this thread at the time:
http://grass.itc.it/pipermail/grass-dev/2006-April/022612.html
I've just noticed that r.terraflow has its own licence which isn't
compatible with the GPL (advertising clause), so we shouldn't be
providing binaries.Ideally, we should have an --enable-nongpl switch so that people don't
trip over this accidentally. Or, better still, just remove all non-GPL
code.--
Glynn Clements <glynn@gclements.plus.com>_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev
__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
I just found that r.regression.linear has various terminology problems
that may cause confusion about what it actually computes. One can look at the script
to check the exact equations but how many users actually do that?
Do we have somebody who has a good knowledge of english stats terminology
to fix it (I don't trust mine very much)?
For example,
1. help says:
R: sumXY - sumX*sumY/tot
but the script computes "correlation coefficient" (e.g. J.H. Zar: Biostatistical analysis)
which does not imply dependence of Y on X and
it is rather a measure of intensity of association between X and Y
R= (sumXY - sumX*sumY/tot)/((sumsqX - sumX^2/tot)*(sumsqY - sumY^2/tot))^0.5;
so should the help say
R: correlation coefficient
rather then list initial part of the equation used?
(for linear regression it should be R^2)
2.
map1 should be map for x-variable (if we talk about linear regression - map for independent variable x)
map2 should be map for y-variable (if we talk about linear regression - map for dependent variable y)
instead of map for x coefficient and map for y coefficient
3. it says median but it actually computes mean?
4. what is this called F= R^2/(1-R^2/tot-2)
there may be more, so it would be great if somebody with stats expertise could look at it
- it is quite short and simple (but useful) script
Helena
Helena Mitasova
Dept. of Marine, Earth and Atm. Sciences
1125 Jordan Hall, NCSU Box 8208,
Raleigh NC 27695
http://skagit.meas.ncsu.edu/~helena/