I'm back from vacation and want to catch up with updating the GUI. I have a couple of questions.
1. r.univar has gone away. Now there is a r.univar.sh script and a r.univar2 program module. I'm not sure what the difference is (I looked at the docs for each in the CVS and GRASS 5.7 manual on line. The manual only listed r.univar). Should I include one or the other or both?
2. All the g3d modules (r3.*) have now been updated to 5.7 is seems. I'll add those that are now lacking in the GUI. I plan to put r3.showdspf under the display menu as it is a display module. However, I have a question about this and NVIZ. I remember that some version (current or yet to come?) of NVIZ was supposed to have support for displaying g3d display files, and there is a mkdspf panel in NVIZ. So, is r3.showdspf obsolete or nearly so? The same for r3.mkdspf?
3. I'll add d.nviz to the display menu also.
4. I see that r.resamp.rst is new. I'll add this.
5. g.mapset was done before I left, but I still need to add it.
6. I see a v.mapcalc that is recently updated. Is this a normally compiling module? Is there a help page for this?
Hamish already added v.univar while I was away.
Any other modules that has been added that I need to put into the GUI?'
Thanks for the help.
Michael
______________________________
Michael Barton, Professor & Curator
School of Human Origins, Cultures, & Societies
Arizona State University
Tempe, AZ 85287-2402
USA
1. r.univar has gone away. Now there is a r.univar.sh script and a
r.univar2 program module. I'm not sure what the difference is (I
looked at the docs for each in the CVS and GRASS 5.7 manual on line.
The manual only listed r.univar). Should I include one or the other or
both?
It's still there, it works, no action required.
GRASS:~> r.univar
does the right thing.
The program directory for the source code is called r.univar2, but if
you look in raster/r.univar2/Makefile, it gets built as r.univar. It
does not include extended stats yet (mode, quartiles, etc) so the old
script (which has those) was not removed in case anyone depends on that.
Once the C version has those, the script is gone. I'd leave the script
off the menu.
The Makefile in the grass51/raster/ directory just tells it which
directories to build, not module names.
5. g.mapset was done before I left, but I still need to add it.
Thanks for the clarification on r.univar, r.univar2, and r.univar.sh.
Michael
From: Hamish <hamish_nospam@yahoo.com>
Date: Tue, 03 Aug 2004 12:38:40 +1200
To: Michael Barton <michael.barton@asu.edu>
Cc: <grass5@grass.itc.it>
Subject: Re: [GRASS5] questions for updating tcltkgrass for 5.7
1. r.univar has gone away. Now there is a r.univar.sh script and a
r.univar2 program module. I'm not sure what the difference is (I
looked at the docs for each in the CVS and GRASS 5.7 manual on line.
The manual only listed r.univar). Should I include one or the other or
both?
It's still there, it works, no action required.
GRASS:~> r.univar
does the right thing.
The program directory for the source code is called r.univar2, but if
you look in raster/r.univar2/Makefile, it gets built as r.univar. It
does not include extended stats yet (mode, quartiles, etc) so the old
script (which has those) was not removed in case anyone depends on that.
Once the C version has those, the script is gone. I'd leave the script
off the menu.
The Makefile in the grass51/raster/ directory just tells it which
directories to build, not module names.
5. g.mapset was done before I left, but I still need to add it.
On Tue, Aug 03, 2004 at 12:38:40PM +1200, Hamish wrote:
> 1. r.univar has gone away. Now there is a r.univar.sh script and a
> r.univar2 program module. I'm not sure what the difference is (I
> looked at the docs for each in the CVS and GRASS 5.7 manual on line.
> The manual only listed r.univar). Should I include one or the other or
> both?
It's still there, it works, no action required.
GRASS:~> r.univar
does the right thing.
The program directory for the source code is called r.univar2, but if
you look in raster/r.univar2/Makefile, it gets built as r.univar. It
does not include extended stats yet (mode, quartiles, etc) so the old
script (which has those) was not removed in case anyone depends on that.
Once the C version has those, the script is gone. I'd leave the script
off the menu.
The r.univar.sh script is definitely needed unless r.univar covers all
functionality. That's why I renamed it to r.univar.sh.
On Mon, Aug 02, 2004 at 01:44:49PM -0700, Michael Barton wrote:
2. All the g3d modules (r3.*) have now been updated to 5.7 is seems.
I'll add those that are now lacking in the GUI. I plan to put
r3.showdspf under the display menu as it is a display module. However,
I have a question about this and NVIZ. I remember that some version
(current or yet to come?) of NVIZ was supposed to have support for
displaying g3d display files, and there is a mkdspf panel in NVIZ. So,
is r3.showdspf obsolete or nearly so? The same for r3.mkdspf?
On 8/3/04 2:16 AM, "Markus Neteler" <neteler@itc.it> wrote:
On Mon, Aug 02, 2004 at 01:44:49PM -0700, Michael Barton wrote:
2. All the g3d modules (r3.*) have now been updated to 5.7 is seems.
I'll add those that are now lacking in the GUI. I plan to put
r3.showdspf under the display menu as it is a display module. However,
I have a question about this and NVIZ. I remember that some version
(current or yet to come?) of NVIZ was supposed to have support for
displaying g3d display files, and there is a mkdspf panel in NVIZ. So,
is r3.showdspf obsolete or nearly so? The same for r3.mkdspf?
It's not clear to me if the code is in sync with the current
nviz.
This what I remembered seeing.
To the list in general:
Has anyone out there tested this? Is the g3d-enabled NVIZ the one that is
now in the CVS? I now have a 22 July build of 5.7. If I get a chance today
or tomorrow, I will try to test this. However, I have to say that I never
got r3.mkdspf and r3.mkdspf to work correctly on my Mac in 5.3.
If r3.showdspf and r3.mkdspf functions are now included within NVIZ, I may
take them off the menu (though this doesn't remove these commands from GRASS
of course).
Michael
______________________________
Michael Barton, Professor & Curator
School of Human Origins, Cultures, & Societies
Arizona State University
Tempe, AZ 85287-2402
USA
On Tue, Aug 03, 2004 at 08:32:26AM -0700, Michael Barton wrote:
On 8/3/04 2:16 AM, "Markus Neteler" <neteler@itc.it> wrote:
> On Mon, Aug 02, 2004 at 01:44:49PM -0700, Michael Barton wrote:
>> 2. All the g3d modules (r3.*) have now been updated to 5.7 is seems.
>> I'll add those that are now lacking in the GUI. I plan to put
>> r3.showdspf under the display menu as it is a display module. However,
>> I have a question about this and NVIZ. I remember that some version
>> (current or yet to come?) of NVIZ was supposed to have support for
>> displaying g3d display files, and there is a mkdspf panel in NVIZ. So,
>> is r3.showdspf obsolete or nearly so? The same for r3.mkdspf?
>
>
> See
> http://grass.itc.it/pipermail/grass5/2004-June/014773.html
>
> It's not clear to me if the code is in sync with the current
> nviz.
This what I remembered seeing.
To the list in general:
Has anyone out there tested this? Is the g3d-enabled NVIZ the one that is
now in the CVS?
No, the NVIZ in the CVS is still without g3d support.
The longer we wait, the more work it will be to integrate this support.