Phil,
The same thing happens to me on my 32 bit windows system. It looks like
the glyph 3d class is being very liberal with memory allocation when
initializing arrays. It's using the number of points in the input
dataset rather than the number of points that will actually be glyphed
then after glyphing takes place the sizes are corrected. I'm going to
hazard a guess that it could be a whole lot smarter in this regard and
simply size the arrays based on the number of points that it will
actually glyph. The best thing to do is file a bug report so that it's
fixed in the coming release. I'll cc the list in case to see if anyone
can give you a better answer.
Burlen
On 10/16/2012 01:41 PM, Phil Amburn wrote:
Burlen,
Hadn't used dropbox before. Looks like a good solution. This may be
the second message with the dropbox link,
https://www.dropbox.com/s/v6b672rzs51uubw/3D_nam.20110525.t00z.12km_CONUS.f00.vtk
Phil
*From:*Burlen Loring [mailto:blor...@lbl.gov]
*Sent:* Tuesday, October 16, 2012 11:24 AM
*To:* Phil Amburn
*Subject:* Re: [Paraview] problem with data file when moving to
version 3.14
could you use drop box or something like that?
On 10/16/2012 11:02 AM, Phil Amburn wrote:
Burlen,
Yes, would be happy to share the dataset. It is ~34MB. Do you have
an ftp site where I can upload the dataset?
I can use over 5000 vectors with the 3.10 version. I get the memory
problem with 200 vectors with the 3.14 version.
Phil
*From:*Burlen Loring [mailto:blor...@lbl.gov]
*Sent:* Tuesday, October 16, 2012 9:10 AM
*To:* Phil Amburn
*Subject:* Re: [Paraview] problem with data file when moving to
version 3.14
Phil, I would have expected 1000 to be ok... Could you share the dataset?
Burlen
On 10/16/2012 08:33 AM, Phil Amburn wrote:
Hi Burlen,
Yes, I think you are right, that I am running out of memory. I've
attached a screen shot of the information tab, which has the same
values for both the 3.10 version and the 3.14 version.
I was surprised that the 3.10 version handles this data set with no
reported problems and 3.14 aborts with the memory problem.
I reduced the number of glyphs from the default 5000 to 1000 when
running the 3.14 version, but the problem persists.
Thanks,
Phil
*From:*Burlen Loring [mailto:blor...@lbl.gov]
*Sent:* Monday, October 15, 2012 5:12 PM
*To:* Phil Amburn
*Cc:* paraview@paraview.org <mailto:paraview@paraview.org>
*Subject:* Re: [Paraview] problem with data file when moving to
version 3.14
Hi Phil,
you're running out of memory, try reducing the number of glyphs. you
might also check the information tab to verify the contents of the
file are as expected.
Burlen
On 10/15/2012 03:56 PM, Phil Amburn wrote:
I've been using version 3.10 and have just started working with
version 3.14
During that transition I've encountered a problem with a data set.
The data is in the VTK legacy format and is ~34mb in size. I'll be
happy to provide a copy of this data set if that would help.
The simple process I use with this dataset is to read it and then use
the glyph filter with arrows. No problem with version 3.10. I
encounter a problem with version 3.14 with that process. I compiled
ParaView 3.14 to get some debug information. I'm working with Visual
Studio 2008 on MS Windows 7 -- 64 bit, but doing 32-bit compiles for
both 3.10 and 3.14
Attached are two screen shots of the results I get with my compiled
version of 3.14 running in the Visual Studio debugger.
I would appreciate any thoughts.
Phil
_______________________________________________
Powered bywww.kitware.com <http://www.kitware.com>
Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
