-
Notifications
You must be signed in to change notification settings - Fork 62
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
Neumann_point BC type #128
Comments
Hi Andreas, |
The example that I am currently working on is this one: It's for a 3D uniaxial test:
It uses the following variables to set up the simulation:
A A There are a few routines that read user-defined meshes if requested, that you can comment out. Thanks for having a look! |
For this type of traction-BC the trick is to use Neumann_point on the traction surface (with input force values given in the current configuration) AND apply 0. Neumann_integrated_only conditions everywhere else. This way, integration happens only on the required Neumann surface, otherwise it occurs on ALL faces adjacent to every Neumann node. The way Neumann_point has been coded is meant to deal with forces applied in one point, but affecting the whole surface. In case of distributed forces you can either use this workaround or re-code the Neumann integration (I have a branch for that). |
The Neumann_point BC type gives unexpected results.
For a simple uniaxial extension test, the results look as if one does not apply consistent nodal forces, however, that's what this BC type is supposed to compute.
Needs debugging or proper documentation on how to use this BC type!
The text was updated successfully, but these errors were encountered: