[Paraview] Xdmf weirdness and question

[Paul Melis]

On 01/14/13 17:33, Paul Melis wrote:
> I use the following Xdmf file to read this set into PV 3.14.1:
>
> <?xml version="1.0" ?>
> <!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
> <Xdmf>
>    <Domain>
>      <Grid Name="TheGrid" GridType="Uniform">
>        <Topology TopologyType="3DRectMesh" Dimensions="4096 4096 160"/>
>
>        <Geometry GeometryType="VXVYVZ">
>          <DataItem Dimensions="4096" NumberType="Float" Precision="4"
> Format="HDF">ql200.hdf:/x</DataItem>
>          <DataItem Dimensions="4096" NumberType="Float" Precision="4"
> Format="HDF">ql200.hdf:/y</DataItem>
>          <DataItem Dimensions="160" NumberType="Float" Precision="4"
> Format="HDF">ql200.hdf:/zf</DataItem>
>        </Geometry>
>
>        <Attribute Name="ql" AttributeType="Scalar" Center="Node">
>          <DataItem DataType="Float" Precision="4" Dimensions="4096 4096
> 160" Format="HDF">ql200.hdf:/ql</DataItem>
>        </Attribute>
>      </Grid>
>    </Domain>
> </Xdmf>
>
> This doesn't work unfortunately, as PV turns it into a grid of
> 160x4096x4096 (and no data is visible at all, even though the number of
> cells and points seems to be correct). I don't see where the reordering
> of axes comes from. Looking at Utilities/Xdmf2/libsrc/XdmfGeometry.cxx I
> think I got the Geometry stuff correct. Does anybody see what is wrong?
Ouch, seems I missed the line

"Dimensions are specified with the slowest varying dimension first (i.e. 
KJI order)."

in the Xdmf spec...


Paul