Issue with /INTER/TYPE2 and degenerated BRICK user elements #5000
Replies: 1 comment
-
|
Additional observations after further investigation: |
Beta Was this translation helpful? Give feedback.
-
|
Additional observations after further investigation: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am working on a composite laminate simulation in OpenRadioss.
Each ply is meshed with elements oriented along the fiber direction. To model a ply, I use two different types of user-defined elements through USER Property:
• "standard" custom elements representing the bulk of the ply,
• smaller custom damageable elements inserted between the standard elements to represent crack initiation and propagation.
As a consequence, the meshes are non-conforming between plies.
To connect the plies together, I currently use a /INTER/TYPE2 tied interface with SpotFlag = 0 (kinematic tie). However, the results show non-physical behavior, in particular abnormally high stress values in some elements.
At this stage, I strongly suspect that the issue may come from the combination of:
• the use of degenerated BRICK user elements (8-node elements where only 4 nodes are effectively used to represent shell-like behavior),
• and the use of the TYPE2 tied interface
In other words, although the elements behave as shells in the formulation, they are still interpreted by Radioss as BRICK elements, and I am not sure whether the TYPE2 interface handles this situation correctly. In particular, I don't know how the type 2 contact has access to the correct shape function if Radioss sees BRICK element.
I would appreciate any suggestions regarding:
Thank you for your help.
Beta Was this translation helpful? Give feedback.
All reactions