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

recommendations for input mesh #25

Open
otaolafranc opened this issue Jan 2, 2025 · 0 comments
Open

recommendations for input mesh #25

otaolafranc opened this issue Jan 2, 2025 · 0 comments

Comments

@otaolafranc
Copy link

Hello,
I would like to use my own tet meshes created in salome for algoHex, from my small experience, the best for this kind of meshers (where it uses as input a mesh itself) was use homogeneous size meshes. I have read a little bit about the hex-me-if-you-can workflow, but would like to get some feedback from experiecied user/developper in 'what to feed' to algoHex. for example I have runned a test with a T pipe with hologeneous size tetra mesh (generated using NETGEN) and algoHex is struggling a lot (it has been more than one and a half hour that it has been running without an output).
the mesh looks like this (it is in vtk format and it has all its features tagged correctly):
image
here is the mesh if necessary:
g.tar.gz
i would love to get some feed back, such as it is better to have even finer mesh or would be better for a best resolution on the edges and the remaining volumetric mesh it is not important that the size is larger....if you use finer mesh it will be more robust but it will take longer or the contrary, etc. this kind of things....
thanks in advance!

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

1 participant