-
Notifications
You must be signed in to change notification settings - Fork 115
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
Drop 3d connectivity broken ? #319
Comments
Is it possible (somehow) that, after the refined step, the octree is "too" off-balanced that |
Good find. The drop connectivity is indeed unusual. We had previously determined that every connectivity always needs full edge and corner information to support balance, even if balance is not extended across edges and/or faces. So we'd have to determine first whether the drop connectivity is complete. Any volunteers @pkestene @tim-griesbach ? |
Is it possible (somehow) that, after the refined step, the octree is "too" off-balanced that `p4est_balance` is unable to fix it ?
Thanks for the report! Generally, balance is designed such that absolutely
any mesh is legal as input. We'll have to double-check the drop
connectivity, and if the error persists look deeper into balance. Which is
on our list already, but we tend to get distracted since it usually works.
|
I checked the drop connectivity definition and did not find any problem with it. @hannesbrandt and I investigated the reported assertion crash in the past in the issue #238 and ended up investigating the balance algorithm (#238 (comment)). I think as @cburstedde mentioned this issue may require to continue the deeper look into balance. |
Thanks! Yes, we'll get back to the balance algorithm in depth early next year. |
Description
When running
./p8est_simple drop 5
(from example/simple sub-directory), one obtains the following logTo Reproduce
p4est configured with
./configure --enable-mpi --enable-debug CFLAGS=-O0 CC=mpicxx
Additional information
I checked current HEAD (develop) and v2.8.6 and v2.8.5 with the same results.
The text was updated successfully, but these errors were encountered: