[Paraview] Parallel unfriendly filters?

[Moreland, Kenneth]

Have you tried doing the threshold last (after the contour) rather than first? Generally, ParaView relies on ghost zones (cells) to avoid artifacts across process boundaries.

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of David Ortley <djortley at gmail.com<mailto:djortley at gmail.com>>
Date: Monday, February 8, 2016 at 1:14 PM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Parallel unfriendly filters?

I'm running Paraview in client/server mode with the server running on an HPC platform across multiple nodes.

My input is a multi-block silo file that contains ghost zone information.  The way I do a seamless contour when visualizing on my workstation is to do the following:

Load the silo file
    -> Threshold out the ghost zones (threshold filter)
        -> Merge the blocks
            -> Cell data to point data
                -> Contour

This works well enough when on a single machine.  But when visualizing client/server with the server running across multiple nodes, there appear seams on the contours.

Is this an expected behavior given my setup?  Are any of the filters that I listed above (Threshold, Merge Blocks, Cell data to point data, and Contour) not fully implemented in parallel yet?

nb - I've not spent a lot of time trying to debug the problem, so I don't know if the problem exists when a server is running on a single node only.  It looks like something that is happening at node boundaries, but I could be wrong and it could be a per/processor thing.

Thanks.

-David Ortley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160208/7a7ef566/attachment.html>