[Paraview] using paraview with large meshes

[Andrew Maclean]

OK I found your problem. I cut and copied your command and got the same
result as you. If you put spaces after the "]" everything works OK.

So: 

[[[$Application GetMainWindow] GetCurrentPVSource] GetDataInformation]
GetMemorySize

Works Ok but not:

[[[$Application
GetMainWindow]GetCurrentPVSource]GetDataInformation]GetMemorySize

 

I am sure the CVS build is OK.

 

For XP, I am using the CVS (last Friday's download).

Using the sphere as a source, the command below returns 4.

For Linux I am using today's CVS download, and the behavior is the same.

 

Andrew

 

 

 

  _____  

From: Stephen Wornom [mailto:Stephen.Wornom at inria.fr] 
Sent: Tuesday, 17 May 2005 16:37
To: Andrew Maclean
Cc: 'Berk Geveci'; 'pview'
Subject: Re: [Paraview] using paraview with large meshes

 

Andrew Maclean wrote: 

[[[$Application GetMainWindow] GetCurrentPVSource] GetDataInformation]
GetMemorySize

 

Works for me OK.

Let do a check list to find the problem:
1-I downloaded the latest binary, are you using the downloaded binary or the
source?

2-when I type this in the prompt window:
[[[$Application
GetMainWindow]GetCurrentPVSource]GetDataInformation]GetMemorySize
I get this
invalid command name "vtkTemp4GetCurrentPVSource"

What could be the difference? Any suggestions on what to try to find the
problem?
Stephen



 

Andrew

 

  _____  

From: Stephen Wornom [mailto:Stephen.Wornom at inria.fr] 
Sent: Monday, 16 May 2005 18:31
To: Berk Geveci; pview
Subject: Re: [Paraview] using paraview with large meshes

 

Berk Geveci wrote: 

Errrr... I am not sure. 1.6 is so old I can't remember what
functionality it had :-)
  

[[[$Application GetMainWindow] GetCurrentPVSource] GetDatainformation]
GetMemorySize
Object named: vtkTemp662, could not find requested method:
GetDatainformation
or the method was called with incorrect arguments.

I downloaded the latest binary [2.0.1]
get the above result.
Stephen






 
On 5/13/05, Stephen Wornom  <mailto:Stephen.Wornom at inria.fr>
<Stephen.Wornom at inria.fr> wrote:
  

Berk Geveci wrote:
 
    

Hi Stephen,
 
Try this:
 
Load the 2M solution file, bring up the command prompt (Window ->
Command Prompt), in the command prompt type the following:
 
[[[$Application GetMainWindow] GetCurrentPVSource] GetDataInformation]
GetMemorySize
 
This should give you the memory usage for the dataset in Kbytes. This
works in parallel also. I am guessing for datasets of that size, the
processing is going be very slow unless you start running on a small
cluster.
 
-Berk
 
      

[[[$Application GetMainWindow] GetCurrentPVSource] GetDataInformation]
GetMemorySize
Object named: vtkTemp994, could not find requested method:
GetDataInformation
or the method was called with incorrect arguments.
 
 
      

I use v1.6 would that be the problem?
Stephen
 
 
    

On 5/13/05, Stephen Wornom  <mailto:Stephen.Wornom at inria.fr>
<Stephen.Wornom at inria.fr> wrote:
 
 
      

I am working with 16M, 64M vertices meshes using an unstructured CFD code.
 
I can view the 2M solution on my workstation 3.0 Ghs with 2.5 Gb RAM. It
takes about 5 minutes to load the file.
 
My question: For those working with 2M > meshes, what RAMs do you use?
Stephen
 
p.s.
I use the non mpi version of ParaView.
_______________________________________________
ParaView mailing list
ParaView at paraview.org
http://www.paraview.org/mailman/listinfo/paraview
 
 
 
        

_______________________________________________
ParaView mailing list
ParaView at paraview.org
http://www.paraview.org/mailman/listinfo/paraview
 
 
 
      

 
    

_______________________________________________
ParaView mailing list
ParaView at paraview.org
http://www.paraview.org/mailman/listinfo/paraview
 
  

 

 





  _____  



 
_______________________________________________
ParaView mailing list
ParaView at paraview.org
http://www.paraview.org/mailman/listinfo/paraview
  

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/paraview/attachments/20050517/f81033f8/attachment.html