Benchmark test case: cantilever subjected to end shear force #4912
Unanswered
julien-siguenza
asked this question in
Shell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
I create this topic to implement a benchmark test case of cantilever subjected to end shear force, as presented in the section 3.1 of the publication of Sze et al. (2004):
I thus implemented the following python scene, which attempts to reproduce this test case:
I give the following mesh as input to the
MeshGmshLoader
, that defines a rectangular plate with the dimensions (L, b):I fix the left extremity of the plate using a
FixedConstraint
and load the right extremity using theConstantForceField
, which I first set with a tinytotalForce
of 0.04 (1% of the maximum force Pmax) in the direction tangential to the plate.I define a big amount of
rayleighMass
(5.0) when setting theEulerImplicitSolver
, in order to reach more quickly the steady deformation of the plate.The
TriangularBendingFEMForceField
is finally used to define the shell, setting the Young's modulus to 1.2e6, the Poisson ratio to 0.0 and the thickness (dimension h) to 0.1.For the considered force, I am thus expecting a moderate deformation of the plate.
Instead, I am ending up with a result that I did not expect at all:
I suspect that this unexpected behavior is due to the
FixedConstraint
which probably constrains only the translational DOFs of the shell, but not the rotational DOFs of the shell on the selected nodes.Could anyone please confirm this and tell me how I can constrain the rotational DOFs?
A dirty workaround I here found to constrain the rotational DOFs on the desired extremal nodes was to constrain also the neighboring nodes:
I finally end up with the following result:
The behavior of the shell is much softer than what I am expecting looking at the reference result of this test case.
Another worrying thing is that increasing either the Young's modulus or the thickness of the shell both lead to a very similar result...
Can anyone please help me see more clearly in all these inconsistencies?
I guess I defined something wrong in my scene, but cannot find out what.
If it can be of any help, here are the messages that are displayed in my terminal when I am running my scene:
Thanks for helping 🙏
FYI: @hugtalbot @bakpaul
Beta Was this translation helpful? Give feedback.
All reactions