-
Notifications
You must be signed in to change notification settings - Fork 97
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
periodic boundary conditions for arbitrary mesh files? #412
Comments
@fverdugo, if you have a chance, it would be great to get a few hints from you on this. |
It should be possible. One has to understand how Gmsh encodes information about periodic boundaries and then use it in Gridap. Essentially, one needs to pair the vertices at the two ends of a periodic boundary from the info provided by gmsh. The rest should be easy. @jesusbonilla and @AndiMD have recently worked with GridapGmsh and perhaps they are also interested in this feature. |
@stevengj I started to work on this point in a fork of GridapGmsh (these are the main modifications). However, the approach that I have followed so far might be quite basic/preliminary. It is still not working properly. I am able to construct the |
Is this issue resolved by gridap/GridapGmsh.jl#35? |
Yes! 🎉 |
We saw in #266 and #318 that you support periodic boundary conditions for
CartesianDiscreteModel
. What would be needed to support them for arbitrary (periodic) meshes?In particular, we are looking at periodic triangular meshes in a rectangular domain, generated by Gmsh, and would like a way to tell Gridap's matrix assembly to treat one of the directions as periodic.
The text was updated successfully, but these errors were encountered: