-
-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
read mixed XDMF 2 #600
Comments
Ah. This example is XDMF 2.2, generated by ParaView 5.6.0; the examples in #553 were XDMF 3.0, generated by meshio. |
ParaView 5.7.0 (Microsoft Windows 10) optionally saves XDMF 3.0 (mixed3.tar.gz) and that is correctly read by meshio. Thus it looks like this issue only concerns |
I made a start on this (4e478eb) but it looks to me as though, in the example XDMF 2.2 generated above by ParaView 5.6.0, the
in which the last four are correctly the vertices but the first is the code for a Polygon. It should be 5 for a Quadrilateral. If it were a Polygon, it should be immediately followed by the number of vertices. There is an example of encoding a four-sided polygon as
in the Xdmf2 Modal and Format Archive. As this is a legacy version of a format, and this latest bug concerns ParaView rather than meshio, I might deprioritize this in favour of #599. |
Indeed, ParaView 5.6.0 fails to reread the quadrilateral. It doesn't raise an error and does count it as a cell but presumably as a Polygon with 0 vertices. On the other hand, if the 3 is manually emended to 5, meshio on branch 600-read-mixed-xdmf2 at |
Fixed by #601. |
In #599, distinguishing between how Polylines are written in XDMF depending on whether they're in
TopologyType
Polyline
orMixed
, a simple test XDMF file generated by ParaView could not be read by meshio.To reproduce: first generate the VTK
then open and
Save Data
in ParaView (here 5.6.0). This gives:Attempting to read this XDMF in meshio raises a
KeyError
.The text was updated successfully, but these errors were encountered: