-
Notifications
You must be signed in to change notification settings - Fork 75
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
Error in traction calculation for simplicial elements #334
Comments
More importantly, it looks like something similar happens with tractions and tetrahedral elements. I recreated the analogous problem in 3D. And, again, applying the tractions to the "slanted" face of a reference tetrahedral element (the analogy of the hypotenuse for a reference triangular element) causes some unwanted scaling of the resultant nodal forces. Here's the script I wrote.
And here are the results.
Again, the net force is higher than it ought to be. |
I was trying solve the simple 2D problem (see diagram) of a bar in pure extension when I encountered a problem with how the tractions are calculated.
The problem can be reproduced with the following script.
The script assumes that the right-hand side has a height of
1
and the distributed load has value0.1
. Thus, the nodal forces on the right-hand side should sum up to a net force of1 * 0.1 = 0.1
. These are the results for the two different (but valid) connectivities defined in the script.In the second case, the net force is larger than
0.1
. The forces appear to have been scaled bysqrt(2)
, the length of the hypotenuse of the reference triangle. The upshot is that, unless the mesh is prepared so that the tractions are only applied to the legs of the reference triangle element, TACS cannot correctly solve the simple problem 2D problem I illustrated above.The text was updated successfully, but these errors were encountered: