Home › Forum › SOFA › Using SOFA › [SOLVED] How to model a deformable object with a deep crevice?
Tagged: 64_bits, collision model, crevice, deformable, SOFA_1712, Tetrahedron, Windows_7
- This topic has 5 replies, 2 voices, and was last updated 7 years ago by
Wong.
-
AuthorPosts
-
24 October 2018 at 07:47 #12260
Wong
BlockedHello everyone,
I tried to use the TetrahedronFEMForceField to model a deformable cylinder with a deep crevice (as the figure shown below).
But since the crevice is too narrow, the collision model vertices of the crevice would map to the same tetrahedron, then the crevice would not be able to be opened.Are there any simple ways to solve this problem?
29 October 2018 at 13:37 #12289Hugo
KeymasterDear @outtt ,
If I understand correctly, you want to simulate:
– a deformable object with an initial cut/crevice
– an auto-collision modelIs this correct?
Can you give us a bit of context: what kind of object is this suppose to be?For collision, any simulation should start without a collision as initial condition. Therefore your collision parameters must be well chosen. I need to find some info regarding the auto-collision since I never did it myself.
Best,
Hugo
29 October 2018 at 16:22 #12293Wong
BlockedHello @hugo,
It is indeed a deformable object with an initial cut/crevice, but not an auto-collision model.
I mean the problem is not the collision. You can even use the visual model instead.The problem is the BarycentricMapping. The mapping would be not correct if such mesh is used to map to the tetrahedral mesh. The vertices of the crevice would map to the same tetrahedron.
Now can you understand it?
Wong
2 November 2018 at 15:32 #123192 November 2018 at 16:47 #123223 November 2018 at 07:25 #12331Wong
BlockedHello @hugo,
I think my solution is not the best one because it is fairly complex and use many components. In fact, my mesh object is in fact not a cylinder as the picture you can see. It is a more complex mesh which does not have a smooth flat cut. So I use the SubsetTopologicalMapping component.
But I do not think it is an elegant method. Because it would be troublesome if it is used in real time cutting. One cut has resulted in so much code, let alone the situation when many cuts occur, although I am not sure if the smooth flat one would have the similar problem.
So I still want a more elegant method.
By the way, can you answer my new question at this link?
-
AuthorPosts
- You must be logged in to reply to this topic.
