<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>David,</div>
<div><br>
</div>
<div>Yes, I figured that's what you meant by ghost zones. My point is that you can leave these in for the contour operation. Because you have overlapping cells, the processors on each side of the boundary will compute the same data at the boundary.</div>
<div><br>
</div>
<div>The trick is to carry avtGhostZones all the way through the calculations. If done correctly, then the surface computed by Contour will have avtGhostZones cell data, and you can strip out the ghost zones in the contour. The only caveat is to be careful
with the Cell Data to Point Data filter because the avtGhostZones array will be invalid if converted from cells to points. You can tell the Cell Data to Point Data filter to just pass the cell data.</div>
<div><br>
</div>
<div>-Ken</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>ParaView <<a href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a>> on behalf of David Ortley <<a href="mailto:djortley@gmail.com">djortley@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Monday, February 8, 2016 at 1:56 PM<br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:paraview@paraview.org">paraview@paraview.org</a>" <<a href="mailto:paraview@paraview.org">paraview@paraview.org</a>><br>
<span style="font-weight:bold">Subject: </span>[EXTERNAL] Re: [Paraview] Parallel unfriendly filters?<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">Kenneth:
<div><br>
</div>
<div>The ghost zones are the contents of the ghost zones stored from the calculation. They overlap into the hydro from neighboring processors (the silo library stores a block per processor the way we're using it in our code.) If I leave them in there, I get
artifacts. I'm actually thresholding out a variable called 'avtGhostZones', which the silo libraries call the stored ghost zone values.</div>
<div><br>
</div>
<div><br>
</div>
<div>Dan:<br>
</div>
<div><br>
</div>
<div>Cell Data to Point Data is the only way I know of to activate the contour filter for silo files. The results are stored in cell arrays, which apparently don't activate the contour filter. I stumbled upon using Cell Data to Point Data by accident, so
if there's a better way to do this, I'm open to it.</div>
<div><br>
</div>
<div><br>
</div>
<div>Thanks.</div>
<div><br>
</div>
<div>-David Ortley</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Feb 8, 2016 at 1:35 PM, Moreland, Kenneth <span dir="ltr">
<<a href="mailto:kmorel@sandia.gov" target="_blank">kmorel@sandia.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>
<div>
<div>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.</div>
<div><br>
</div>
<div>-Ken</div>
<div><br>
</div>
</div>
</div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>ParaView <<a href="mailto:paraview-bounces@paraview.org" target="_blank">paraview-bounces@paraview.org</a>> on behalf of David Ortley <<a href="mailto:djortley@gmail.com" target="_blank">djortley@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Monday, February 8, 2016 at 1:14 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a>" <<a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a>><br>
<span style="font-weight:bold">Subject: </span>[EXTERNAL] [Paraview] Parallel unfriendly filters?<br>
</div>
<span class="">
<div><br>
</div>
<div>
<div>
<div dir="ltr">I'm running Paraview in client/server mode with the server running on an HPC platform across multiple nodes.
<div><br>
</div>
<div>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:</div>
<div><br>
</div>
<div>Load the silo file</div>
<div> -> Threshold out the ghost zones (threshold filter)</div>
<div> -> Merge the blocks</div>
<div> -> Cell data to point data</div>
<div> -> Contour</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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?</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Thanks.</div>
<div><br>
</div>
<div>-David Ortley</div>
</div>
</div>
</div>
</span></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>