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

Interface with meshio #405

Open
anderson2981 opened this issue Apr 26, 2024 · 9 comments
Open

Interface with meshio #405

anderson2981 opened this issue Apr 26, 2024 · 9 comments

Comments

@anderson2981
Copy link

anderson2981 commented Apr 26, 2024

Coreform Cubit can write mesh files in NASTRAN format, I have created a simple translation tool to go from NASTRAN to GMSH, which meshmode can already read, but it would be better to directly read in NASTRAN.

Here is my script that converts a NASTRAN file into a gmsh format.
https://gist.github.com/anderson2981/a16c045288401a55d450e3a831896cd9

Here an example 2D NASTRAN example.
https://gist.github.com/anderson2981/97f9a16c3f2828cae9e0c1e039beedbc

@anderson2981
Copy link
Author

@inducer

@inducer
Copy link
Owner

inducer commented May 1, 2024

One problem I see here is that human-readable names (e.g. wall_block) occur only in lines that are technically comments. How important is it that these names are preserved?

https://victorsndvg.github.io/FEconv/formats/bdf/MD_Nastran_2006_Quick_Reference_Guide.pdf

@inducer
Copy link
Owner

inducer commented May 1, 2024

(Compared to just the property numbers, i.e. the things defined by PROD et al.)

@anderson2981
Copy link
Author

I use the names as tags to apply the boundaries in my driver, so while the actual name isn't important, I still need some way of telling the driver which boundary is which. Gmsh has an extra section that defines all the names and their assignments.

This is an updated version of what I sent last week. To get the names I just read all the comment lines in the property section to figure out what the names are.

https://gist.github.com/anderson2981/1fb6d9d7d79002e3b3430af9c55c3a20

@alexfikl
Copy link
Collaborator

alexfikl commented May 1, 2024

A bit unrelated, but is meshio still an option at all? It's not very maintained anymore, but I imagine the established formats work pretty well. Shouldn't be too hard to write a little meshio2meshmode wrapper and that will give access to a whole bunch of formats (including NASTRAN).

@anderson2981
Copy link
Author

as far as i can tell, meshio does not appear to be an export format supported by coreform. Which is driving this development.

@alexfikl
Copy link
Collaborator

alexfikl commented May 1, 2024

as far as i can tell, meshio does not appear to be an export format supported by coreform. Which is driving this development.

meshio is just a library that can read and write a bunch of formats (including NASTRAN). I was suggesting to use it so that we don't have to implement the parsing ourselves. (more of a question, than a suggestion though)

@inducer
Copy link
Owner

inducer commented May 1, 2024

@lukeolson and I discussed that a bit a few years ago, and at the time

which led us to dismiss the possibility. At the same time, 🤷 if it gets closed up, we can just continue life with a fork. (e.g. https://github.com/inducer/meshio) So... maybe this is less bad than hacking our own half-broken NASTRAN reader.

@inducer inducer changed the title Adding a reader for NASTRAN file format Interfacing with meshio May 1, 2024
@inducer inducer changed the title Interfacing with meshio Interface with meshio May 1, 2024
inducer added a commit that referenced this issue May 2, 2024
@inducer
Copy link
Owner

inducer commented May 2, 2024

Some progress on this is in #411.

inducer added a commit that referenced this issue May 2, 2024
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

No branches or pull requests

3 participants