Tue, Apr 5 2005
22:06:32
|
|
Request created by guest
|
|
Subject: NVIZ: limitation regarding volume data
Platform: GNU/Linux/i386
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: 6.1CVS
NVIZ currently features a limitation for the max number of volumes.
This limit is arbitrarily set to 100, there are apparently no such limitations
for surfaces, etc.
This causes strange effects and/or unexpected stops when scripting is used for
batch-processing of lots of data.
It is strongly suggested to increase the default value of the variable
MAX_VOL_FILES in /libogsf/gsds.c to a significantly higher value.
Thanks,
Peter |
|
Wed, Apr 6 2005
13:10:38
|
|
Mail sent by neteler@itc.it
|
|
Return-Path |
<neteler@itc.it>
|
Delivered-To |
grass-bugs@lists.intevation.de
|
Date |
Wed, 6 Apr 2005 13:10:35 +0200
|
From |
Markus Neteler <neteler@itc.it>
|
To |
Request Tracker <grass-bugs@intevation.de>
|
Cc |
grass5@grass.itc.it
|
Subject |
Re: [GRASS5] [bug #3146] (grass) NVIZ: limitation regarding volume data
|
Message-ID |
<20050406111035.GC13254@thuille.itc.it>
|
Mail-Followup-To |
Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
|
References |
<20050405200632.CE1901005AA@lists.intevation.de>
|
Mime-Version |
1.0
|
Content-Type |
text/plain; charset=us-ascii
|
Content-Disposition |
inline
|
In-Reply-To |
<20050405200632.CE1901005AA@lists.intevation.de>
|
User-Agent |
Mutt/1.4.1i
|
X-Spam-Status |
No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
|
X-Spam-Level |
|
On Tue, Apr 05, 2005 at 10:06:32PM +0200, Request Tracker wrote:
> this bug's URL: http://intevation.de/rt/webrt?serial_num=3146
> -------------------------------------------------------------------------
>
> Subject: NVIZ: limitation regarding volume data
>
> Platform: GNU/Linux/i386
> grass obtained from: CVS
> grass binary for platform: Compiled from Sources
> GRASS Version: 6.1CVS
>
> NVIZ currently features a limitation for the max number of volumes.
> This limit is arbitrarily set to 100, there are apparently no such limitations
for surfaces, etc.
>
> This causes strange effects and/or unexpected stops when scripting is used
for batch-processing of lots of data.
>
> It is strongly suggested to increase the default value of the variable
> MAX_VOL_FILES in /libogsf/gsds.c to a significantly higher value.
Looking at:
cd lib/ogsf
grep MAX_VO *
gsurf.h:#define MAX_VOLS 12
GVL2.c:static int Vol_ID[MAX_VOLS];
GVL2.c: if (Next_vol < MAX_VOLS) {
gvl_file.c:#define MAX_VOL_SLICES 4
gvl_file.c:#define MAX_VOL_FILES 100
I feel that MAX_VOL_SLICES and MAX_VOL_FILES should probably go into
gsurf.h and that MAX_VOLS should match MAX_VOL_FILES.
?
Markus
|
|
Tue, Jul 19 2005
23:22:18
|
|
Mail sent by mneteler
|
|
Hi,
I have moved MAX_VOL_SLICES and MAX_VOL_FILES to gsurf.h.
The numbers are still unchanged (Helena or Jaro may recommend).
Markus |
|
Wed, Aug 31 2005
22:11:05
|
|
Owner changed to hmitasova by mneteler
|
|
Mon, Oct 23 2006
04:19:58
|
|
Subject changed to NVIZ: volume limitation (max slices, max files) by hbowman
|
|