The vtkXdmf reader and writer were rewritten during ParaView 3.7. (So they appear first in release 3.8.)
Specifically they were rewritten so as to use the xdmf library to do the bulk of the xml file wrangling that the original vtk classes did on their own. This was possible because of the update of the xdmf library itself from xdmf1 to xdmf2 that came into ParaView first in version 3.3. The benefits of the newer reader were mostly structural, better composite data support, greater efficiency, somewhat better parallelism and greater maintainability. If you have to make 3.6.2 read that data, you will probably need this particular change, in which Kenneth Leiter fixed support for tensor6 data. I believe this also first appeared in ParaView 3.7. commit 9f8c35ddcb94bed2b5faf008503873ebb086a826 Author: Kenneth Leiter <[email protected]> Date: Tue Jul 21 16:06:37 2009 -0400 ENH: Read in Tensor6 to VTK David E DeMarle Kitware, Inc. R&D Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109 On Mon, Apr 18, 2011 at 8:40 AM, Utkarsh Ayachit <[email protected]> wrote: > ParaView's XDMF reader was significantly revamped in past possibly > 3.8, I can't remember.So it's possible that older versions don't > support all xdmf files. > > Utkarsh > > On Sun, Apr 17, 2011 at 4:38 PM, Pratik Mallya <[email protected]> > wrote: >> I am currently using 3.10...but since clusters in my office have 3.6.2 >> installed i tried to use that version. However, for this file: >> >> <?xml version="1.0" ?> >> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []> >> <Xdmf> >> <Domain Name="test.xdmf"> >> <Grid Name="TensGrid"> >> <Topology TopologyType="2DSMesh" Dimensions = "256 256 "> >> </Topology> >> <Geometry GeometryType="X_Y"> >> <DataItem Dimensions="256 256" NumberType="Float" >> Precision="8" Format="HDF"> >> Q.h5:/X >> </DataItem> >> <DataItem Dimensions="256 256 " NumberType="Float" >> Precision="8" Format="HDF"> >> Q.h5:/Y >> </DataItem> >> </Geometry> >> <Attribute Name="S" Center="Node" AttributeType="Scalar" >> Precision="8"> >> <DataItem Format="HDF" Center="Node" >> NumberType="Float" Dimensions="256 256" Precision="8"> >> Q.h5:/S >> </DataItem> >> </Attribute> >> <Attribute Name="sig" Center="Node" >> AttributeType="Tensor" Precision="8"> >> <DataItem Format="HDF" NumberType="Float" >> Dimensions="256 256 8" Precision="8"> >> Q.h5:/Q >> </DataItem> >> </Attribute> </Grid> >> </Domain> >> </Xdmf> >> ....a simple xdmf for reading data, paraview 3.6 gives an error: >> >> ERROR: In >> /home/pratik/Manually_Installed_Softwares/numerical/ParaView/ParaView-3.6.2/VTK/Filtering/vtkDataSet.cxx, >> line 406 >> >> vtkStructuredGrid (0xb091888): Point array sig with 9 components, only has >> 14563 tuples but there are 65536 points >> >> >> whereas 3.10 does not. >> Was there a different format for reading xdmf files in pv3.6? I did try >> playing around with the dimensions, but it still didn't work. >> _______________________________________________ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://www.paraview.org/mailman/listinfo/paraview >> > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
