Skip to content
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

Mesh.external vestigial? #268

Closed
gdmcbain opened this issue Dec 3, 2019 · 0 comments · Fixed by #269
Closed

Mesh.external vestigial? #268

gdmcbain opened this issue Dec 3, 2019 · 0 comments · Fixed by #269

Comments

@gdmcbain
Copy link
Contributor

gdmcbain commented Dec 3, 2019

Has the Mesh.external attribute become vestigial?

external: Any = None

The docstring says:

external
If Mesh is loaded from external format (object), the original
representation is kept here.

but I don't think it is set in skfem.importers.meshio.from_meshio.

In the motivating case, I did actually have an $ElementData block in a MSH 2 file which was parsed as .cell_data['quad'][my_data] by meshio.read but that's not read by skfem.importers.meshio.from_meshio.

Of course in my application I can just skip from_file and use meshio.read and from_meshio, that's not too much trouble.

Should the .external attribute just be deleted from skfem.Mesh?

Later on, if other similar applications arise, it might be worth thinking about how to generalize from_meshio to capture the cell_data beyond the 'gmsh:physical'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant