[dilthoms]

I have modified your example scene file to reproduce it – http://pastebin.com/v9pphzWN With FreeMotionAnimationLoop added and the solvers moved to the root, the moving object does not move anymore. If I move the solvers to each Node, it works fine. Any pointers will be a great help. Thanks.

[dilthoms]

Hi Romain,

I tested the solution and it works well for scenes where I do not use FreeMotionAnimationLoop. Thanks a lot for the solution.

However, when I place the solvers at the root for a scene with FreeMotionAnimationLoop, the solvers do not seem to work – for example, the objects in the scene do not respond to keyboard movements. (They work when each subgraph contain its own solver.) Do you know how to handle this issue for scenes with FreeMotionAnimationLoop? Thanks.

[dilthoms]

Hi Romain,

Thanks a ton for suggesting a solution. I will try it out.

The reason I was using LocalMinDistance was because of the suggestions in
http://lists.gforge.inria.fr/pipermail/sofa-users/2014-February/002051.html
http://lists.gforge.inria.fr/pipermail/sofa-users/2013-March/001598.html

I found LocalMinDistance to be more stable than MinProximityIntersection. Is this true in general?

Thanks once again.

[dilthoms]

Hi Romain,

Thanks a lot for looking into the issue. All the scene files I have results in memory leak when the collision models are in continuous contact (the system memory steadily decreases). I use Point Line and Triangle collision models for both objects. An example scene file is at http://pastebin.com/XsTqqaR4

I would be happy to hear any other comments you might have about my scene file since I am fairly new to SOFA.

[dilthoms]

Hi Hugo,

No, I have not been able to identify the cause of the memory leak.

[dilthoms]

Yes, you have described the problem correctly and thanks for the updates.

[dilthoms]

Hi Hugo,
Thanks a lot for your reply.

The simulation that I want to do is to cut a triangular surface mesh, say the torus in the example, using a pair of scissors. For this, I plan to remove triangles using topologymodifier. I tried to use the TriangleFEMForceField and its variants but they were unstable with collisions. HexahedronFEMForceField with a grid topology worked perfectly and took care of the stability issues. Since I want to cut the torus based on collision with the pair of scissors, I would like to use the actual topology of the mesh and remove those triangles with which the scissors collide. I know it does not make much sense to have two topologies for the same object but I was wondering if there was some way to achieve what I wanted using SOFA.

[dilthoms]

From my understanding the time interval DT only specifies the resolution at which simulation is done. The time taken for your loop is not directly affected by DT. Someone from SOFA team can confirm this.

To reduce delay what you could try is slowing down the rate at which data is sent from arduino side so that it does not get buffered up on the receiving side.

[dilthoms]

One possibility is that your simulation is not running fast enough. Therefore the data from the COM port gets buffered up and positions do not get updated as fast as you want.

[Author]

Posts