<HTML>
<HEAD>
<TITLE>Re: [Paraview] Rendering bug?</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>I do not think that this is a rendering problem. I think you have just fooled the filter that extracts the external faces of the blocks (which is what is actually rendered). Notice that when you arrange the overlapping meshes exactly as you are doing, that some of the faces are coincident. In particular, the face that is missing is coincident. Up to the point before you run clean to grid, these faces are topologically distinct because they use an independent (although coincident) set of points. When you run clean to grid, these coincident points are merged. When the points are merged, the cells from the two meshes now share the same indexed points. At this point, these faces are no longer topologically distinct. The external faces filter notices that these two faces use the same points and marks it as a neighbor face (this is the definition of a neighbor face) and “correctly” removes it.<BR>
<BR>
The problem is basically that when you append the data sets you are creating a non-manifold mesh. To correct the problem, you need some sort of filter that identifies coincident cells and removes duplicates. I know of no such filter, so you will probably have to write your own.<BR>
<BR>
-Ken<BR>
<BR>
<BR>
On 11/11/09 7:33 AM, "Sven Buijssen" <<a href="sven.buijssen@tu-dortmund.de">sven.buijssen@tu-dortmund.de</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi,<BR>
<BR>
I've come across something that I consider a rendering bug, but before filing a<BR>
bug report I'd like to discuss it first. Maybe it sounds familiar. (I'm guess<BR>
it's not related to the z-fighting issue discussed last week.)<BR>
<BR>
I have two volume grids consisting of hexaeder which partially overlap (wavelet<BR>
sources for demonstration purposes in the attached *.pvsm file). After applying<BR>
AppendDataSets and CleantoGrid filter it looks like the resulting grid contains<BR>
all points and cells except the cell at the intersection of the two grids. See<BR>
attached image.<BR>
But the "missing" cell is actually there. Twice. It can be confirmed by applying<BR>
a ProgrammableFilter to add a cell array with cell numbers and applying a<BR>
Threshold filter. Set both lower and upper threshold to either 0 or 30 to verify<BR>
that the "missing" cell is still there. It simply not rendered any more.<BR>
<BR>
It happens with PV 3.6.1 binary release and PV compiled from CVS HEAD. (The<BR>
state file has been created with PV from CVS HEAD.)<BR>
<BR>
Any thoughts?<BR>
<BR>
Thanks<BR>
Sven<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'><BR>
**** Kenneth Moreland<BR>
*** Sandia National Laboratories<BR>
*********** <BR>
*** *** *** email: <a href="kmorel@sandia.gov">kmorel@sandia.gov</a><BR>
** *** ** phone: (505) 844-8919<BR>
*** web: <a href="http://www.cs.unm.edu/~kmorel">http://www.cs.unm.edu/~kmorel</a><BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT>
</BODY>
</HTML>