Well... not going so well.
If I run a small simulation with massif and the Release build of paraview, I
don't see any growing memory in time. I also get my VTK files and images.
If I run the same simulation linked against a Debug build with VTK_DEBUG_LEAKS
on, there is a segfault inside one o
Thanks for the advice Burlen -- I haven't used Massif before, so this is a good
opportunity to give it a try.
The initialize/finalize each time approach doesn't work either. I am calling
the Finalize() routine on the vtkCPProcessor class but then when it tries to
initialize again, it throws:
VTK_DEBUG_LEAKS, although will catch some serious errors, will not catch
all kinds of leaks. For example you can have leaks where data
erroneously accumulates with each time step, but is deleted at program
termination. VTK_DEBUG_LEAKS will not catch that kind of error. It's
probably better to u
Hi Andy,
Thanks for the tips. I will get working on the VTK_DEBUG_LEAKS now and see what
it turns up.
The initialize/finalize every time is definitely a hack and not for long-term
use. But, sponsors want a report on Monday and we need to be able to visualize
things for that -- the simulation
Hi Tim,
If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good at
finding VTK objects that aren't deleted properly. You should be able to run
this with a small amount of calls to Catalyst as well. If you try this and
want help understanding the output (if an object like a vtkUnstruct
Paraview is awesome for lots of functionalities, however I find it extremely
slow in processing data with any filter type, or in changing timestep as soon
as the model size is around one million cells or above. I have experience with
a commercial tool which on the same model and pc is 100x faste
Hi,
One of our users is running a very big simulation and writing out images of two
slices (two different views) every 1000 iterations and writing out the data for
the two slices (two different data writers) as VTK files every 5000 iterations.
It is using Paraview 4.4.
After 21000 iterations
Hi Sven,
I am not aware on any specific developer documentation for Catalyst on the
ParaView side (but I haven't worked on that subject for years), although
Utkarsh or Andy might know.
Usually looking at the code and redoing it in the Python world is what is
required, but as I said, I'm not sure
Hello Seb,
glad to read your answer. So the problem is not only that I was unable to
find the relevant information.
You say, you have not (yet) written the required code. Does "not (yet)"
mean that it is on the agenda maybe within the next half year? Then I could
find a workaround and look forward
It may be possible to do this with Catalyst. I would guess that nearly all
of the complex work would need to be done in the adaptor to integrate this
properly though.
On Wed, May 18, 2016 at 11:17 AM, wrote:
> Yes, you are right. In this case, there will be two separate
> MPI_COMM_WORLD. Plus, o
Lukasz,
> The volume rendering algorithms in Paraview are ultrafast with VTK image
> files but painfully slow with unstructured grids. I constantly have an idea
> in mind to map unstructured meshes to image files and then do the volume
> rendering.
That's indeed the reason by the "Resample to
On Fri, May 20, 2016 at 10:19 AM, Ramiro James Rebolledo Cormack <
ramre...@gmail.com> wrote:
>
> I compile paraview in my laptop (ubuntu 16.04) and my desktop (ubuntu
> 14.04) with exactly the same options in ccmake, in particular: OpenGL.
> In my laptop 'Export to pdf' works perfect.
> Is this re
Hi Utkarsh,
I am always building Paraview from source on Linux with all the features I
need, but there is no rush, I can wait for the next release or if I badly need
this functionality I will pull it from the “master”.
A little background:
I was actually playing around when I came across the is
On Thu, May 19, 2016 at 10:16 PM, Utkarsh Ayachit <
utkarsh.ayac...@kitware.com> wrote:
> + Not sure what's the deal with 4.0.1, but it's too old at this point
> so let's ignore that.
> + When you downloaded ParaView 5.0.1 from paraview.org, starting with
> 5.0.1, we are using a new implementation
Thanks Utkarsh.
2016-05-19 22:16 GMT-04:00 Utkarsh Ayachit :
> Ramiro,
>
> A few things to note:
>
> + Not sure what's the deal with 4.0.1, but it's too old at this point
> so let's ignore that.
>
I'm agree. I was just testing to understand what is happening.
> + When you downloaded ParaView
CLASSIFICATION: UNCLASSIFIED
Stephane,
I am not sure about the superbuild process. But if your goal is to just build a
ParaView for windows platform and not make a ParaView windows build using
Superbuild, I can get you with all the dependencies library compiled with
VS2013 express (which shoul
Hi Sven,
Live catalyst connection require a specific socket connection to the
in-situ process with some special handling.
We did not (yet) wrote the Python code to perform that specific action for
ParaViewWeb so it could be triggered by the web client or configured via an
argument at launch time.
Lukasz,
I'd suggest not to use 'ImageResampling' filter, it was a temporary fix and
clearly is buggy. A new filter has been added to ParaView "master", name
"Resample To Image". That would do what you want to do more reliably. What
platform are you running on? I can send you links to the nightly b
Hello All,
Is the Image Resampling filter applicable to all datasets or only VTK Images?
Each time I try to use this filter on any other dataset than a uniform image
file, Paraview crashes. In Paraview Help it is written: "Accepts input of
following types: vtkDataSet vtkCompositeDataSet". I am
19 matches
Mail list logo