-
Notifications
You must be signed in to change notification settings - Fork 16
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
multi subdomains merge issue #26
Comments
Hey Daniel, don't worry about asking questions - I am happy to hear that you might find this little project useful! The behavior you see is as I would expect it - the quad refinement operation is applied to each mesh separately before the next mesh in your parameter file will be constructed. In order to obtain a uniform refinement you need to set the number of quad refinements only for the last mesh to a value larger than zero:
However, when load the resulting mesh into Paraview, I need to disable the "max_angle" cell array, because it seems that some NaN values are written to it. That's probably related to the really high aspect ratios - but I should definitely fix this bug soon. I hope this helps you out. If not - feel free to ask any further questions! :-) Thanks again for your interest. Regards |
Hi @FloSewn, thanks for your support. Much appreciated. |
Hey Daniel, thanks for that hint and your idea! I will try to implement this for the next release. Best regards |
Hello Daniel, The parameter Greetings |
Hi @FloSewn,
Sorry for bothering you again. I have questions regarding multi subdomains meshing. It looks to me some of the parameters are shared from former subdomain to the latter subdomains. For example, if I have two subdomains, each with same number of quad refinements, but the former one will be refined twice and the mesh is merged to the latter one, though different output file prefixes are provided.
Attached is the detail job scripts I have used for four subdomains (with subdomain 3 and 4 commented for test purpose)
When I separated subdomains from each other, the mesh looks good. The discretization at the shared internal boundary are a bit different, which is probably due to the difference in cell size calculation for the local subdomain. This is not a problem as the it can be fixed by explicitly specified coordinates. However, the refinement for subdomain 1 has been done twice, if I mesh subdomain 1 and subdomain 2 together, and the output in frac2d-quad-multi-zone-2 contains both subdomain 1 and 2.
Would you please let me know if this is a bug or if I didn't use it properly?
Figure Left: mesh each subdomain separately, Figure Right: mesh subdomain 1 and 2 together
Thanks,
Daniel
The text was updated successfully, but these errors were encountered: