I finally got it to work, at least for Scalar values. The Dimensions in the
topology section need to be 1 more than in the DataItem section because the
Xdmf reader is creating a Rectilinear Grid and not ImageData. So once I
finally figured that out then I could load up some of my scalar values.
On 05.02.2013 13:27, Michael Jackson wrote:
I finally got it to work, at least for Scalar values. The Dimensions in the
topology section need to be 1 more than in the DataItem section because the
Xdmf reader is creating a Rectilinear Grid and not ImageData. So once I
finally figured that
On Feb 5, 2013, at 10:23 AM, Jens Kleimann wrote:
On 05.02.2013 13:27, Michael Jackson wrote:
I finally got it to work, at least for Scalar values. The Dimensions in the
topology section need to be 1 more than in the DataItem section because the
Xdmf reader is creating a Rectilinear Grid
I have this:
?xml version=1.0 ?
!DOCTYPE Xdmf SYSTEM Xdmf.dtd []
Xdmf xmlns:xi=http://www.w3.org/2003/XInclude; Version=2.2
Information Name=DREAM3D Data File for Small IN100 Value=0/
Domain
Grid Name=Structured Grid GridType=Uniform
Topology TopologyType=3DCoRectMesh Dimensions=117 201 189/
Hello Mike
I'm not sure what the issue is ... I'm assuming the hdf5 file containing
the attribute data is in the same dir and the internal path is correct
etc ... it all depends on how picky the XDMF reader is ... for example
the number type for your Xdmf Attribute is Int but the Precision
I was wondering that myself as the data inside the HDf5 file is actually
encoded as a 1D array of 32 bit integers but in the xdmc file I am telling the
XDMF reader that the data is 3D. Wonder if that matters? I have tried both ways
and either get a read error or a ParaView crash.
--
Mike
