Hi Paraview list,
I use a finite element code that generates VTK output, but I'm having
trouble dealing with halo (ghost) nodes/elements correctly.
We currently partition meshes node-wise, and each process writes all its
owned nodes and one level of halo nodes to a chunk. Once all the chunks are
Hi again list,
Inspired by David Ortley's recent success (see "Smooth seams in SILO
files") I wonder if perhaps the way I'm doing it is correct, but Paraview
is incorrectly considering the values at hidden nodes when calculating data
ranges.
Essentially my "option 3" (writing a vtkGhostLevels arr
Hi Louie,
Ghost/halo nodes are considered valid (but duplicated) so they are taken
into account when calculating ranges, statistics etc. What you need is to
mark them as invalid, it sounds like? We are making slow progress towards
having an infrastructure that supports this but currently it is onl
Hi Berk,
Thanks for your reply. Yes that does sound like what I need to do.
Shouldn't the nodes of elements with vtkGhostLevels>0 already be ignored in
the range calculation though?
Is there no way to do this currently then? I tried marking them with
vtkGhostPoints but it didn't help last time I
The only way to do this currently is to use the threshold filter to remote
the halo nodes.
Best,
-berk
On Fri, Feb 27, 2015 at 6:32 AM, Louie Cardone-Noott <
louie.cardone-no...@linacre.ox.ac.uk> wrote:
> Hi Berk,
>
> Thanks for your reply. Yes that does sound like what I need to do.
> Shouldn't
