Nico Schlömer

> Turns out the cell_sets are wrong: that is another problem with meshio. I am looking into it. If I understand correctly, fixing this will fix your problem.

That's right. I have no idea how cell data works in Abaqus inp files. If you find a format specification, let me know.

I'd love to reader _and_ writer for this. I think there is some motivation of handling structured meshes properly, see #404. Perhaps this is a good time to start things...

The names are cool. I'd vote for attributes `type` and `structure_shape` or `shape`. All downstream conversion functions can go into the mesh object itself. Do you want to start something?...

> because cells are usually not defined for structured grids I'd be fine with a Mesh that doesn't have `cells` or `points` at all, just the info provided from the...

@Zevrap-81 Instead of attaching your code as a zip, better just copy-paste it with triple backticks.

If I understand you correctly, this issue is about how to handle node sets and side sets, and how to incorporate them in meshio. That is indeed something to consider....

Alright, I've just now released meshio 2.0.0 with a `Mesh` container class. You can simply add node/side sets to that class and add i/o for Abaqus/Exodus.

It should work either way. Reopening.

@keileg Do you have an idea how to fix this? I'm getting ``` AssertionError: Incompatible cell data. 157 cell blocks, but 'gmsh:physical' has 16 blocks. ``` trying to read OP's...