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 <[email protected]<mailto:[email protected]>> on behalf of David Ortley <[email protected]<mailto:[email protected]>> Date: Monday, February 8, 2016 at 1:14 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> 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
_______________________________________________ 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
