-
Notifications
You must be signed in to change notification settings - Fork 707
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
Shared Triangulation and Locally Owned Dofs issue #7531
Comments
I fail to reproduce your problem with the test case above (copying the |
Sorry, I didn't copy properly the whole code. Now I added the main function (which should be the same as the one you copied from step-60). |
Hmm... Is still can't reproduce the problem. For this to build I still need to replace Maybe, it is related to partitioning. Which partitioning are you using? Can you attach your |
I can reproduce the issue with 28fa42f. |
Ok thank you @masterleinad ! Anyway here is the detailed.log |
If you replace Triangulation with parallel::shared::Triangulation, you also have to replace compute_point_locations with distributed_compute_point_locations |
This seems to be fixed by #7527. At least, I don't see any problems anymore after applying the patch. |
Hi everyone!
I believe there is some problem at least one of "locally_owned_dofs" and "map_dofs_to_support_points" on shared triangulation. The following test is a modified half of step-60, where I do the following:
There might be something wrong in my lengthy procedure, but with 1 process everything is fine (also by printing and checking manually the points), while with multiple cores it sometimes works, sometimes doesn't (depending on the deformation function and number of cores used)...
I am sorry if for the 250 lines; I have been trying to reduce it, but I couldn't understand how to produce a
mesh_configuration_function
without the parameters...(and, being a part of step-60, on the first run will fail and generate a .prm file )P.S. So, @luca-heltai , turns out I really found a problem...
The text was updated successfully, but these errors were encountered: