[GRASS-dev] wxNviz volumes

[Helena Mitasova]

On Jul 4, 2011, at 3:39 PM, Michael Barton wrote:

> Anna,
> 
> I did some further testing. SVN from the past hour.
> 
> 1) Volumes. These loaded OK. When I move them around in the view, I can see the bounding cube. But I can't see any isosurfaces

Mike, make sure that you set the value of your isosurface, then add it and set polygon resolution to 1 - I have the isosurfaces loading at 3 
and only very little shows up, but they pop-up at full resolution.
Also your isosurfaces may be under your surface (if you have any), you would have to change the surface position for now,
as the position is not implemented for volumes yet.
Finally, make sure you have the 3D region set up correctly - I find it rather tricky now when we have res3 for all
and you need to over ride it by tbres if you want different resolution vertically. 3D region setting may need some tune up.

> or "slides" (slices?).
this might not have been implemented yet.

> Maybe I'm doing something wrong, but nothing appears no matter how I set it.
> 
> 2) Fringe. I was able to get the height to update on my SRTM of the Jordan River valley, but cannot see any changes at all when I apply it to the Spearfish 10m DEM. Also, there are some places where the top does not match the topography. I'm attaching an image from the Spearfish elevation10m DEM to illustrate what I'm talking about. The top edge of the fringe follows the topography in some places, but cuts from a peak to a place in a valley (not the bottom) to the left of the peak. This may be an OpenGL issue, but should be looked into for this to be useful. 

the bad top edge of the fringe has been there from the very beginning - it may be computed based on coarse resolution -
it may be worth to check whether it is still a problem with a very small DEM when everything is loaded at resolution 1.
But it may be something entirely different and goes beyond wxnviz. Of course it would be great to find a fix.
> 
> 3) Graphic output (follow up on Hamish's post of earlier today). It works!! That is good. But it only seems to work for PPM. The Tif file that it creates will not open (tried in GIMP and Apple Preview).

I can open the saved tif with Preview

> As Hamish notes, other formats would be welcome--jpeg and png especially. 

yes, especially for MSWindows users without tiff support.

> 
> 4) Your point is well taken about adjusting one image versus adjusting all of them. But I'll make one more pitch for putting position onto the view page. It moves around images in the window to position them in different ways. This is what happens in the view window. Perhaps I'm unusual in this, but when I'm positioning the images (i.e., with the position tool), I also want to move them around with the view puck, adjust height, etc. When I'm changing image display properties (drape map, transparency, resolution, etc.), I'm less likely to be messing with positioning. But that's just me. How do others normally work with 3D images?

I haven't looked into this. I will try it next.
> 
> I'm not getting the terminal chatter that Markus reported. Maybe it's been fixed in the interim. The only thing I get is the following when I launch GRASS
> 
> Launching 'wxpython' GUI in the background, please wait...
> GRASS 7.0.svn (Spearfish60_test):~ > Mon Jul  4 12:14:16 cmb-MBP-3.local pythonw2.6[3540] <Error>: CGContextRestoreGState: invalid context 0x0
> Mon Jul  4 12:14:16 cmb-MBP-3.local pythonw2.6[3540] <Error>: CGContextRestoreGState: invalid context 0x0
> Mon Jul  4 12:14:16 cmb-MBP-3.local pythonw2.6[3540] <Error>: CGContextRestoreGState: invalid context 0x0
> Mon Jul  4 12:14:16 cmb-MBP-3.local pythonw2.6[3540] <Error>: CGContextRestoreGState: invalid context 0x0
> Mon Jul  4 12:14:16 cmb-MBP-3.local pythonw2.6[3540] <Error>: CGContextRestoreGState: invalid context 0x0
> 
> ...and the following when I quite the GUI after running wxNviz
> 
> pythonw2.6(3540,0xa070e540) malloc: *** error for object 0x21d0d980: pointer being freed was not allocated
> *** set a breakpoint in malloc_error_break to debug

that is what I am getting too but it is not causing any problems.

Helena
> 
> Thanks again. This is really looking good. Haw hard is a north arrow?
> 
> 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 Jul 3, 2011, at 5:10 AM, Anna Kratochvílová wrote:
> 
>> Hello,
>> 
>>> Martin's fix allowed me to get wxNviz going and try it out. Your summer work has
>>> make great improvements in getting this to the level of functionality of the old
>>> tcltk nviz. The view controls work very well and the map updates automatically.
>>> The data controls work well too and alter the image as indicated. The lighting
>>> works really well too and I'm glad to see the cutting plane and fringe
>>> functional. This is all very much appreciated. I have a few observations and
>>> suggestions from going through and testing. 
>>> 
>>> 1. Position controls. Works fine. But this seems to make more sense on the view
>>> page as it affects the orientation of the map display rather than the color or
>>> character of the image itself (other things on the data page). 
>> 
>> On data page there are things relating to one chosen map, so that's the reason why position is there.
>> But I agree it should be improved. I thought about some interactive positioning, I'm not sure how this could be done
>> but I'll try something.
>> 
>>> 2. Z-exag. Works fine. It would be nice if this could be a float with at least 1
>>> decimal so that z-exag. of 1.5 or 2.5 could be set. Not a high priority though.
>> 
>> This shouldn't be problem.
>> 
>>> 3. Cutting plane. Most works fine. But the x and y sliders seem to do the same
>>> thing. Height doesn't seem to have any affect. Tilt make visual cutting planes
>>> disappear (same thing with TclTk). 
>> 
>> x, y mean the rotation center, you can see it when you use rotation. Height 
>> has effect only when using tilt. I know about the disappearing of the shading with tilt
>> but I'm not sure if I can do anything about it.
>> 
>>> 4. Fringe. All works well except the 'elevation from bottom' command. It doesn't
>>> seem to do anything.
>> 
>> It works for me. Maybe it's another Mac problem.
>> 
>> Thanks for testing, it's welcomed.
>> 
>> Best regards
>> Anna
>