[Paraview] Fwd: Odd behavior of XDMF files with 3DCORECTMesh

[David E DeMarle]

Just noticed I failed to reply-ALL.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

---------- Forwarded message ----------
From: David E DeMarle <dave.demarle at kitware.com>
Date: Wed, Sep 24, 2014 at 6:00 PM
Subject: Re: [Paraview] Odd behavior of XDMF files with 3DCORECTMesh
To: Armin Wehrfritz <dkxls23 at gmail.com>


I think this is a very very old bug.

For some reason, *RECTMesh (vtkRectilinearGrid) has been ijk instead of kji
for as long as I can remember.

*SMesh (vtkStructuredGrid) and *CoRectMesh (vtkImageData) are normal on the
other hand.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Sat, Sep 20, 2014 at 7:38 AM, Armin Wehrfritz <dkxls23 at gmail.com> wrote:

> Hi,
>
> I lately started to write my data in HDF5/XDMF files. This works so far
> very well for unstructured data using TopologyType="Mixed" and Polygon
> cells, but I have some trouble with structured grids.
>
> I attached a very simple VTK file, which is correctly visualized in
> ParaView. More precisely, the DIMENSIONS keyword specifies the
> dimensions in X Y Z direction and the SPACING and POINT_DATA keywords
> are specified accordingly.
>
> Opening the VTK file in ParaView and exporting the data as XDMF leads to
> an XDMF file with dimensions and the spacing is in reverse order (Z Y
> X), where seemingly the data is written in the same order as in the VTK
> file.
> Is this intended or a bug?
> Just to note, the data from the ParaView-created XDMF and the original
> VTK file are displayed consistently.
>
> When I however manually converter the VTK to a XDMF file with
> dimensions, spacing and data specified as in the VTK file, I get a
> completely wrong representation in ParaView.
> Seemingly, in the "Topology" element the "Dimensions" keyword specifies
> the dimensions in Z Y X direction, which I thing is rather odd.
> The whole thing gets then completely messed up when specifying the data.
>
> Am I doing something wrong when manually creating the XDMF file or is
> this a bug?
>
> Best regards,
> Armin
>
>
>
> --
> Armin Wehrfritz, Dipl.-Ing. (M.Sc.)
> Aalto University, School of Engineering
> Department of Energy Technology
> PO Box 14300
> FI-00076 Aalto, Finland
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140929/e566aafb/attachment.html>