Dear Dear All<br><br><br>There is an issue reading 9-node bi-quadratic quads from Exodus to vtk through vtk's exodus reader.<br>Currently, 9-node quads are loaded into vtk as 8-node quads.<br><br>I do not seem to be able to find/understand the particular part of the vtk code that translates the nodal information from Exodus to VTK.<br>
I will need more help to be able to fix the bug!<br><br>Can anybody help please?<br><br>Thankfully<br>Davood<br><br><div class="gmail_quote">On Tue, May 17, 2011 at 12:21 PM, David Thompson <span dir="ltr"><<a href="mailto:dcthomp@sandia.gov">dcthomp@sandia.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">On May 17, 2011, at 6:03 , Davood Ansari wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
...<div class="im"><br>
However, one question is how does vtkExodusIIReader<br>
differe from vtkExodusReader.<br>
If I open the file and use PrintSelf methods They produce slightly different information:<br></div>
...<div class="im"><br>
The output from ExodusIIReader clearly suggests that my elements are 9 node quads!<br>
</div></blockquote>
<br>
Hi Davood,<br>
<br>
The ExodusIIReader is a rewrite of the ExodusReader. It outputs multiblock datasets rather than a single unstructured grid, so there is less overhead involved in representing blocks with different variables defined on them.<br>
<br>
The output from vtkExodusIIReader that identifies the block as "QUAD9" is reflecting the contents of the Exodus file, not the output of the reader.<br><font color="#888888">
<br>
David<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br><br><div style="text-align: left;"> work as if you'd stay forever, <br>prepare as if you'd leave tomorrow<br></div><br>