I have not commented out both gvl_align_data lines (#684 and #1009) in
gvl_calc.c, but fixed variable initialization in trunk r54866. Please
test.
Markus M
On Fri, Jan 11, 2013 at 10:33 PM, Michael Barton michael.bar...@asu.edu wrote:
Perhaps Windows and Linux--and earlier versions of OS
Markus and others,
I just tested this with GRASS trunk r54874 and it is still broken.
Removing all reference to lines gvl_align_data (and the function as well)
works. AFAICT, this only is called for viewing volumes. Does removing this
function break volume viewing for any other platform?
Hi Michael,
On Mon, Jan 7, 2013 at 7:57 AM, Michael Barton michael.bar...@asu.edu wrote:
So I found a change that would make volumes visible again a week ago. Anyone
have any thoughts about this? Do we need the function/procedure that sets the
memory pointer for volume displays? Or can we
On Jan 11, 2013, at 2:48 PM, Anna Kratochvílová wrote:
Hi Michael,
On Mon, Jan 7, 2013 at 7:57 AM, Michael Barton michael.bar...@asu.edu wrote:
So I found a change that would make volumes visible again a week ago. Anyone
have any thoughts about this? Do we need the function/procedure that
Perhaps Windows and Linux--and earlier versions of OS X--ignore the code.
The header for gvl_calc.c says that the author is Tomas Paudits (February
2004). Does anyone know if he is still around to ask?
Michael
__
C. Michael Barton
Director, Center for Social
So I found a change that would make volumes visible again a week ago. Anyone
have any thoughts about this? Do we need the function/procedure that sets the
memory pointer for volume displays? Or can we simply get rid of it? Is it
needed for Linux? Windows? Any thoughts about what happens without
Testing with GRASS 6.4.3RC2
Rem-ing out line 684 in gvl_calc_c
/* gvl_align_data(dbuff[i].ndx_new, dbuff[i].new); */
prevents crashing. But I don't see an isosurface.
Helena,
I'm using your test data (jr_7408MR_2m_t70)
What is a good value to set for an isosurface to see anything?
Slices
When I put in values between 15 and 20 I can see the horizontal outline of a
rectangle but not the 3D shape of a box. No isosurfaces display. No crash
either.
I un-commented line 684 and commented line 1009 in gvl_calc_c to see what
happens to slices
/* gvl_align_data(pos, slice-data); */
A
Michael,
what you describe sounds as if you had only one depth layer so let us check
first that the 3D region is right.
If the 3d region is set to the provided 3d raster given here
http://skagit.meas.ncsu.edu/~helena/grasswork/JR_7408MR_2m_t70.asci
Aha. You were right. The tbres and top bound was set to 1. Odd since I use set
the region to match the 3d map.
So I'll try it again and with the command and report back.
Michael
C. Michael Barton
Director, Center for Social Dynamics Complexity
Professor of Anthropology,
GREAT NEWS!
Commenting out both gvl_align_data lines (#684 and #1009) in gvl_calc_c makes
this work. Both slices and isosurfaces display and do not crash. I don't know
if there would be a problem with larger files or not. But this is finally
functional again.
BUT the command you sent does NOT
11 matches
Mail list logo
