Justin,
I believe you have SGI - have you ever tried NVIZ?
Do you get the same problem, which I now believe is
a bug that for certain combination of viewing position,
zscale and resolution parts of the surface are masked out?
it gets worse when you zoom out and when the file is big -
(say 1000x1000). Bill was supposed to look at it but
he still seems to have troubles with his computer.
It worked Ok with the GL version, but OPEN GL
calls are different - do we have an OPEN GL expert who could
look at it? Bob (Covill) do you have anything new about
this bug?
If this cannot be fixed, it needs to be put in the manual
that there is this bug - people may really struggle with it.
Markus, maybe you should put a link to my message about
what works and what does not in NVIZ in the manual page
(I have seen that message somewhere on your GRASS site)
Don't wait with the release because of this bug - but it
would be nice to have it fixed (I can provide the data and
example images if somebody wants to look at it).
I too think that beta11 should be released ASAP and that
the LZW should be removed now - it will be too late to
do it after beta11, I am worried about it because i have
about million FP raster files, but it really needs to be done and
tested.
Helena
P.S. markus, thanks for the ITR letter.
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
Hi Helena
Helena Mitasova - staff wrote:
I believe you have SGI - have you ever tried NVIZ?
Do you get the same problem, which I now believe is
a bug that for certain combination of viewing position,
zscale and resolution parts of the surface are masked out?
it gets worse when you zoom out and when the file is big -
(say 1000x1000). Bill was supposed to look at it but
he still seems to have troubles with his computer.
It worked Ok with the GL version, but OPEN GL
calls are different - do we have an OPEN GL expert who could
look at it? Bob (Covill) do you have anything new about
this bug?
Yes, we are using an SGI here. I'm not sure if I replicated "the bug" or
not. After loading in a large surface (2300x2500) I increased the z
exaggeration to about 35 and most of the map was dark. It appeared to be
only a small portion of pixels were being rendered with bright colors
but the rest were all dark. Then I played with the lighting and found
that clicking "Follow ViewPoint" and then clicking the surface button,
rendered the surface properly. However, clicking "Follow ViewPoint"
(disabling it) and rendering again had no effect. Decreasing the z
exaggeration had no effect but increasing it again caused the same
problem. So, it appears that this problem is a lighting problem. Is this
the type of behavior you are experiencing?
BTW, I wouldn't call myself an OpenGL expert, but I am quite familiar
with it.
One thing I noticed is that we may want to change the lighting controls,
they do not seem very intuitive to me, but that's just my opinion. Also,
it seems that interrupting the render process is not truly interruptive.
While playing around with the lighting I interrupted the render many
times, yet when I stopped and let the render finish it flashed between
wire frame and rendered surface several times. This seems to indicate
that the commands were being queued somehow.
Anyway, I don't have a lot of time right now to look into this, I might
be able to take 1/2 a day or so.
--
Sincerely,
Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
People who think they know everything are very irritating to those
of us who do. ---Anonymous
Jazz and Trek Rule!!!
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Wed, Jan 17, 2001 at 10:40:38PM -0600, Helena Mitasova - staff wrote:
[snip]
I too think that beta11 should be released ASAP and that
the LZW should be removed now - it will be too late to
do it after beta11, I am worried about it because i have
about million FP raster files, but it really needs to be done and
tested.
Helena, I have a GRASS module that will perform the translation from LZW
to LIBZ compression for floating point rasters an entire mapset at a
time. It tries to be paranoid about making sure it can read what it
writes; so, the data is read/decoded/recoded to a temp file, then reread
and if successful transferred back to the original. It seems to work
okay (but has had little testing) -- http://www.jps.net/egm2/r.lzw2z.tgz
It's meant entirely for those situations where a copy of an earlier
version of GRASS is not readily available. Haven't worked out how to
distribute it, since it contains the offending LZW code.
(A shell script to run "r.compress -u" using earlier version of GRASS
before upgrading might be a little safer).
--
Eric G. Miller <egm2@jps.net>
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
Helena,
I have not had time lately to re-visit the NVIZ problems. If you could make some
data, and images available that demonstrate the problem, that would be helpful. A
good description of the current bugs would be a good idea to include with the
viewer.
Helena Mitasova - staff wrote:
Justin,
I believe you have SGI - have you ever tried NVIZ?
Do you get the same problem, which I now believe is
a bug that for certain combination of viewing position,
zscale and resolution parts of the surface are masked out?
it gets worse when you zoom out and when the file is big -
(say 1000x1000). Bill was supposed to look at it but
he still seems to have troubles with his computer.
It worked Ok with the GL version, but OPEN GL
calls are different - do we have an OPEN GL expert who could
look at it? Bob (Covill) do you have anything new about
this bug?
If this cannot be fixed, it needs to be put in the manual
that there is this bug - people may really struggle with it.
Markus, maybe you should put a link to my message about
what works and what does not in NVIZ in the manual page
(I have seen that message somewhere on your GRASS site)
Don't wait with the release because of this bug - but it
would be nice to have it fixed (I can provide the data and
example images if somebody wants to look at it).
I too think that beta11 should be released ASAP and that
the LZW should be removed now - it will be too late to
do it after beta11, I am worried about it because i have
about million FP raster files, but it really needs to be done and
tested.
Helena
--
Bob Covill
Tekmap Consulting
P.O. Box 2016
Fall River, N.S.
B2T 1K6
Canada
E-Mail: bcovill@tekmap.ns.ca
Phone: 902-860-1496
Fax: 902-860-1498
Justin,
You are right, NVZI does stack the draw commands. That was one of my concerns
when I added the auto-draw features. The Nset_cancel command will cancel a draw
in progress, but it will only cancel one draw request at a time. With the
auto-draw features, I bound this command to the canvas widgets (position and
light position). If you change position during the middle of a re-draw it is
cancelled. This could also be bound to the scale and entry widgets as well. The
only problem is, if more than one item is being drawn it will only cancel the
first re-draw.
Maybe a better solution, that I have not looked at yet is to have the cancel
routine built right in to the actual draw commands. In other words calling the
draw command (surface, vector, etc) will cancel an existing draw cammand.
Justin Hickey wrote:
Hi Helena
....
One thing I noticed is that we may want to change the lighting controls,
they do not seem very intuitive to me, but that's just my opinion. Also,
it seems that interrupting the render process is not truly interruptive.
While playing around with the lighting I interrupted the render many
times, yet when I stopped and let the render finish it flashed between
wire frame and rendered surface several times. This seems to indicate
that the commands were being queued somehow.
Anyway, I don't have a lot of time right now to look into this, I might
be able to take 1/2 a day or so.
--
Sincerely,
Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
People who think they know everything are very irritating to those
of us who do. ---Anonymous
Jazz and Trek Rule!!!
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
--
Bob Covill
Tekmap Consulting
P.O. Box 2016
Fall River, N.S.
B2T 1K6
Canada
E-Mail: bcovill@tekmap.ns.ca
Phone: 902-860-1496
Fax: 902-860-1498
Hi there,
On Wed, Jan 17, 2001 at 10:59:50PM -0800, Eric G . Miller wrote:
On Wed, Jan 17, 2001 at 10:40:38PM -0600, Helena Mitasova - staff wrote:
[snip]
> I too think that beta11 should be released ASAP and that
> the LZW should be removed now - it will be too late to
> do it after beta11, I am worried about it because i have
> about million FP raster files, but it really needs to be done and
> tested.
I fully agree to switch off LZW NOW!
If o.k., I'll do it in one hour.
Helena, I have a GRASS module that will perform the translation from LZW
to LIBZ compression for floating point rasters an entire mapset at a
time. It tries to be paranoid about making sure it can read what it
writes; so, the data is read/decoded/recoded to a temp file, then reread
and if successful transferred back to the original. It seems to work
okay (but has had little testing) -- http://www.jps.net/egm2/r.lzw2z.tgz
Helena, I have tested it, it is o.k.
It's meant entirely for those situations where a copy of an earlier
version of GRASS is not readily available. Haven't worked out how to
distribute it, since it contains the offending LZW code.
Question is if we shall integrate it into GRASS or not for the users.
(A shell script to run "r.compress -u" using earlier version of GRASS
before upgrading might be a little safer).
I have already written such script and the announcement:
http://www.geog.uni-hannover.de/grass/announces/announce_lzw_removal.html
-> fp_uncompress.sh: uncompress all raster maps. Save and run within your
old GRASS 5
-> fp_recompress.sh: recompress all raster maps with DEFLATE. Save and run
within new GRASS 5
It runs r.compress.
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Thu, Jan 18, 2001 at 09:04:54AM -0400, Bob Covill wrote:
Helena,
I have not had time lately to re-visit the NVIZ problems. If you could
make some data, and images available that demonstrate the problem, that
would be helpful. A good description of the current bugs would be a good
idea to include with the viewer.
If possible, please use (additionally) the GRASS bug tracking system:
http://www.geog.uni-hannover.de/grass/index2.html
-> Bug reports (GRASS 5) - see right column
Everyone in the world has write access, every developer management
capabilities.
Thanks!
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
Helena,
On Wed, Jan 17, 2001 at 10:40:38PM -0600, Helena Mitasova - staff wrote:
Justin,
I believe you have SGI - have you ever tried NVIZ?
Do you get the same problem, which I now believe is
a bug that for certain combination of viewing position,
zscale and resolution parts of the surface are masked out?
it gets worse when you zoom out and when the file is big -
(say 1000x1000). Bill was supposed to look at it but
he still seems to have troubles with his computer.
It worked Ok with the GL version, but OPEN GL
calls are different - do we have an OPEN GL expert who could
look at it? Bob (Covill) do you have anything new about
this bug?
If this cannot be fixed, it needs to be put in the manual
that there is this bug - people may really struggle with it.
Markus, maybe you should put a link to my message about
what works and what does not in NVIZ in the manual page
(I have seen that message somewhere on your GRASS site)
good idea, I have added the link into the CVS file here:
http://www.geog.uni-hannover.de/grass/gdp/html_grass5/nviz/index.html
(NVIZ tutorial, to be accessed from GRASS 5 manual pages)
Don't wait with the release because of this bug - but it
would be nice to have it fixed (I can provide the data and
example images if somebody wants to look at it).
Yes, please put on your server.
I too think that beta11 should be released ASAP and that
the LZW should be removed now - it will be too late to
do it after beta11, I am worried about it because i have
about million FP raster files, but it really needs to be done and
tested.
Yes! See my other mail.
Regards
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'