Hi,
I have a question concerning nviz_cmd. Martin supposed the module's
name to be just temporary. Do you feel that nviz_cmd name should be
replaced? Any suggestions?
Anna
Hi,
2011/8/20 Anna Kratochvílová <kratochanna@gmail.com>:
I have a question concerning nviz_cmd. Martin supposed the module's
name to be just temporary. Do you feel that nviz_cmd name should be
replaced? Any suggestions?
right see [1] for details.
`d.3d` sounds good for me, I would suggest `d.out.3d` because it
writes output directly to the file, or `d.out.nviz`...
Martin
[1] http://lists.osgeo.org/pipermail/grass-dev/2008-December/041160.html
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
Anna:
> I have a question concerning nviz_cmd. Martin supposed
> the module's name to be just temporary. Do you feel that
> nviz_cmd name should be replaced? Any suggestions?
Martin
right see [1] for details.
..
[1] http://lists.osgeo.org/pipermail/grass-dev/2008-December/041160.html
..
`d.3d` sounds good for me, I would suggest `d.out.3d`
because it writes output directly to the file, or
`d.out.nviz`...
Since this is also in grass 6.x, I worry a little that d.out.* is
too closely tied to the display monitor usage of the other d.*
modules and especially confusion with what d.out.file and
d.out.png do. i.e. nviz_cmd is more a generator than an exporter,
closer in a way to the old p.* paint commands.
also while we are here we should consider the future of d.nviz,
as it is a rather generic name once other options exist too.
I assume that d.nviz in grass 7 will one day be a front-end to
nviz_cmd, with the end-points, vector track, spline fitting, and
time step magic for individual frames performed in d.nviz, and
the actual rendering of each frame done by nviz_cmd in a series
of individual system calls (which could be done in parallel).
maybe d.nviz could call the encoder too? or maybe it would be
cleaner to have a d.3d.movie script around d.nviz and nviz_cmd
for that.
are thoughts about keyframe animation support for wxNVIZ?
perhaps
d.nviz -> d.nviz.script
nviz_cmd -> d.nviz.image
??,
Hamish
Hi,
2011/8/21 Hamish <hamish_b@yahoo.com>:
[...]
perhaps
d.nviz -> d.nviz.script
nviz_cmd -> d.nviz.image
you are probably right about `d.out.*`, it's historically to much
close to monitors usage and GRASS display architecture itself. The
proposal above makes sense to me.
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
I'd go with d.nviz.image because the result of the command is an image, not a script.
Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
On Aug 21, 2011, at 12:55 PM, Martin Landa wrote:
Hi,
2011/8/21 Hamish <hamish_b@yahoo.com>:
[...]
perhaps
d.nviz -> d.nviz.script
nviz_cmd -> d.nviz.imageyou are probably right about `d.out.*`, it's historically to much
close to monitors usage and GRASS display architecture itself. The
proposal above makes sense to me.Martin
--
Martin Landa <landa.martin gmail.com> * Studijní program Geodézie a kartografie – GeoWikiCZ
Hamish:
>> perhaps
>>
>> d.nviz -> d.nviz.script
>> nviz_cmd -> d.nviz.image
Michael wrote:
I'd go with d.nviz.image because the
result of the command is an image, not a script.
I meant d.nviz.script for a (wxPy) replacement of the existing
d.nviz module, which currently creates a tcl/tk script to run in
tcl/tk NVIZ to automatically set up the keyframe animation to
follow a certain camera track, from input coords (eg exported
vector map) or by interactively clicking the display monitor
(grass 6.x only).
a d.nviz.script could call d.nviz.image many times, once for
each timestep.
Hamish
---
GRASS6> d.nviz --help
[...]
Description:
Creates fly-through script to run in NVIZ.
Flags:
-i Interactively select route
-f Full render -- Save images
-c Fly at constant elevation (ht)
-k Include command in the script to output a KeyFrame file
-o Render images off-screen
-e Enable vector and sites drawing
Parameters:
input Name of input raster map
output Name of output script
name Prefix of output images (default = NVIZ)
route Route coordinates (east,north)
dist Camera layback distance (in map units)
ht Camera height above terrain
frames Number of frames
start Start frame number (default=0)
Hi all,
2011/8/21 Michael Barton <Michael.Barton@asu.edu>:
I'd go with d.nviz.image because the result of the command is an image, not a script.
if no objections I will rename `nviz_cmd` to `d.nviz.image`. I would
also vote for renaming in 6.x branches, `nviz_cmd` was just temp name,
unfortunately part of 6.4.0+.
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
Martin Landa wrote:
2011/8/21 Michael Barton <Michael.Barton@asu.edu>:
> I'd go with d.nviz.image because the result of the command is an image, not a script.if no objections I will rename `nviz_cmd` to `d.nviz.image`.
d.* should only be used for modules which use the display subsystem
(monitors, GRASS_PNGFILE, etc), which doesn't apply to nviz_cmd.
--
Glynn Clements <glynn@gclements.plus.com>
Martin wrote:
> if no objections I will rename `nviz_cmd` to `d.nviz.image`.
Glynn wrote:
d.* should only be used for modules which use the display
subsystem (monitors, GRASS_PNGFILE, etc), which doesn't apply
to nviz_cmd.
may I suggest to use m.* then. (keeping g.* for gis admin
functions)
also consider renaming g.transform to m.transform.
Hamish
Hi,
2011/8/28 Hamish <hamish_b@yahoo.com>:
d.* should only be used for modules which use the display
subsystem (monitors, GRASS_PNGFILE, etc), which doesn't apply
to nviz_cmd.may I suggest to use m.* then. (keeping g.* for gis admin
functions)
to summarize `nviz_cmd` could be renamed to `m.nviz.image`.
Objections, other suggestions?
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
Martin,
is nviz_cmd supposed to work in winGRASS6.4.2 (it works on mac and linux)
or is the Windows support planned only for winGRASS7 with m.nviz.image
thank you,
Helena
On Sep 28, 2011, at 6:59 AM, Martin Landa wrote:
Hi,
2011/8/28 Hamish <hamish_b@yahoo.com>:
d.* should only be used for modules which use the display
subsystem (monitors, GRASS_PNGFILE, etc), which doesn't apply
to nviz_cmd.may I suggest to use m.* then. (keeping g.* for gis admin
functions)to summarize `nviz_cmd` could be renamed to `m.nviz.image`.
Objections, other suggestions?
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Hi,
2011/9/29 Helena Mitasova <hmitaso@ncsu.edu>:
is nviz_cmd supposed to work in winGRASS6.4.2 (it works on mac and linux)
or is the Windows support planned only for winGRASS7 with m.nviz.image
it should work (not tested), I would prefer to rename nviz_cmd to
m.nviz.image also in GRASS6. It's quite new module which is not used
by normal users, so I think that we could rename it too (before
6.4.2).
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
Martin wrote:
I would prefer to rename nviz_cmd to m.nviz.image also in
GRASS6. It's quite new module which is not used by normal users,
who among us are normal users? 
(but seriously, I think one of the great draws of grass is that
it lets you do (or adapt the code to) odd-ball tasks which less
modifiable software lock you out of. it's a big reason why I first
started using it)
so I think that we could rename it too (before 6.4.2).
sounds good to me. see grass64/scripts/r.cats for a model of
leaving behind a link to the old name, if that's necessary.
(is the 6.x version scriptable?)
Hamish
I will have to update some assignments if the name is changed, but it should not be too much.
It will be better to rename it now rather than later, so +1 for the new name
Helena
On Sep 29, 2011, at 11:32 PM, Hamish wrote:
Martin wrote:
I would prefer to rename nviz_cmd to m.nviz.image also in
GRASS6. It's quite new module which is not used by normal users,who among us are normal users?
(but seriously, I think one of the great draws of grass is that
it lets you do (or adapt the code to) odd-ball tasks which less
modifiable software lock you out of. it's a big reason why I first
started using it)so I think that we could rename it too (before 6.4.2).
sounds good to me. see grass64/scripts/r.cats for a model of
leaving behind a link to the old name, if that's necessary.
(is the 6.x version scriptable?)Hamish
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
2011/9/30 Hamish <hamish_b@yahoo.com>:
sounds good to me. see grass64/scripts/r.cats for a model of
leaving behind a link to the old name, if that's necessary.
(is the 6.x version scriptable?)
done in r48567-r48571, candidate for backport to relbr64 - recorded as [1].
Martin
[1] http://trac.osgeo.org/grass/ticket/1456
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa