-
Notifications
You must be signed in to change notification settings - Fork 237
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
Deformed cell for 3D mesh deformation in release mode #5980
Comments
Per our discussion yesterday in the biweekly user meeting, here more info on the compiler and optimization settings: ASPECT:
dealII:
|
I also tried, but couldn't, reproduce the issue on my Mac. My Mac installation has the following details:
dealII
|
I'll try to tease out for what coordinates and what cell the error is triggered on the cluster. |
The debugger does not allow to set breakpoints or look into the code, I guess because dealii was not built in dev mode (and I have no permissions to do so). A more recent installation of dealii using a newer gcc alleviates the problem though:
|
@Kaili270 and I ran into a curious error that only occurs in Release mode, only in 3D, and only for certain combinations of X mesh extent and X mesh repetitions.
dealii version: 9.5.2
ASPECT commit (May 29 2024): 249618d
Error message:
The error can be reproduced by taking the cookbook crustal_deformation/crustal_model_3D.prm and changing the Geometry model settings from
to
To get rid of the error, one only has to change the X extent to 128e3. It seems like a very specific edge case where the normal vector to the surface cannot be computed. For example,
does work, even though it also has repetitions that lead to square surface elements.
The error occurs for any mesh deformation plugin (as it occurs in make_initial_constraints in the mesh_deformation interface) and we also tried several different setups. For a more complex one, the same error occurs but during
make_constraints
instead ofmake_initial_constraints
in the mesh deformation interface.The text was updated successfully, but these errors were encountered: