I join Thabita clarifying the current state of configuring Sofa since that we are trying it together.
As @taro has already mentioned, the compilation is fine right now. However, a run time error happens when executing runSofa.exe, and which is probably related to the
qwindows.dllwhich can not be located! I include the complete error…[Read more]
It is always an interesting topic.
In a simple simulation scenario, I applied a linear tensile force on a deformable object in the direction of its main axis. Using a Neo-Hookean behavior model, I noticed that the deformation is influenced by the number and size of elements (tetrahedrons).
However, it is possible to control the…[Read more]
I see. Thanks!
This means that I have to set youngModulus in MPa. and the force in Newton.
You also mentioned:
If the file mesh you load has values between 0 and 40
Non, they are not! The shape is not necessarily translated to the origin (0,0,0). The bounding box of the cuboid could be for instance [200 100 50 , 240 130 55]. Still,…[Read more]
my question is, as other people asked before, about units in SOFA. I read the discussion on a previous topic, but I’m still not sure that I did it the correct way after getting some confusing results in my simulation.
Let’s assume that my scene contains a soft-body cuboid with dimensions of 40mm*30mm*5mm, and and Young’s modulus of 1.5…[Read more]
Noura replied to the topic Compilation error while setValue to d_force in linearFF in the forum Programming with SOFA 4 months ago
Actually It should be simply :
Noura started the topic Compilation error while setValue to d_force in linearFF in the forum Programming with SOFA 4 months ago
I’m creating a linear force field and facing some difficulties in setting values to its member data (for example in the
Firstly, I declare a parameter “initForce” in my component header file:
typedef typename DataTypes::Coord::value_type Real;
In the constructor of the component, I…[Read more]
You can apply a constant force field to a certain node in your mesh (let say on the node with index 5), you supply the force direction and value (for instance 7 N. in the positive direction of Y axis), I included the “arrowSizeCoef” parameter which is optional just to help visualizing the force direction.
Noura replied to the topic Using "FreeMotionAnimationLoop" is stopping "TetrahedronFEMForceField" in the forum Using SOFA 10 months ago
Yes, that’s true. I forgot to include a ConstraintCorrection in the deformed object node. Now it works fine.
Thanks for the quick hint!
Noura started the topic Using "FreeMotionAnimationLoop" is stopping "TetrahedronFEMForceField" in the forum Using SOFA 10 months ago
I noticed that using the
FreeMotionAnimationLoopwill stop the ‘TetrahedronFEMForceField’ component from working.
A quick example to illustrate this is the famous tutorial scene “TutorialForceFieldLiverFEM.scn” in (/src/examples/Tutorials/ForceFields)
It is sufficient to include
<FreeMotionAnimationLoop/>in the main scene node to notice…[Read more]
I faced the same issue before with CGAL. Fortunately, I noticed that I could compile SOFA with CGAL successfully using
I know that this doesn’t solve the problem, but it could be a temporary solution until the issue is fixed.
Ubuntu 18.04.1 LTS
clang version 6.0.0-1ubuntu2
In order to compile using clang:…[Read more]
Noura replied to the topic How to exclude certain mesh elements from the collision test? in the forum Using SOFA 10 months, 3 weeks ago
Thanks for the clear detailed reply. Yes, it helps!
For the moment, the collision models are static along the simulation, and splitting the mesh into 2 parts sounds a good approach.
The hint concerning “doCollisionDetection” method is also handy, I may need to implement a specific collision pipeline with an adapted narrow phase…[Read more]
Noura started the topic How to exclude certain mesh elements from the collision test? in the forum Using SOFA 10 months, 3 weeks ago
I’m wondering if there is a way to exclude certain elements (nodes, edges, faces, etc.) in a mesh object from collision tests without deactivating the collision on the entire object?
Or should this be managed once the collision is detected, by inducing a certain response for example? Any hint?
Great effort. Thanks!
The constraints page in particular is very helpful. In case of related suggestions or minor remarks, should we post them on this thread or on sofa doc github?
BTW, I noticed that the link of “Mapping” page doesn’t exist.
Did you defined the “constraintFactor” in the AttachConstraint component?
If not, please try something like this:
<AttachConstraint object1="@obj1" object2="@obj2" indices1="0 1 2 3" indices2="0 1 2 3" constraintFactor="1 1 1 1" />
Yes, it is working as desired right now! Thanks a lot.
Besides the sensitivity to the dt, mass and force values, I realized that the main issue was due to the absence of the “compliance” parameter in the “UncoupledConstraintCorrection”!.
I also noticed that by removing the mass and constraint correction from the “object1_surf” node,…[Read more]
Thanks for looking into the scene. Yes, I see your notice about the usage of different templates in a projective constraint is very relevant and now, at least, I understand why the behaviour is not as expected.
Concerning your question about the need of
I use it is because the cube should be a rigid object and not a…[Read more]
I the following simulation, object1 and object2 are assembled using the
I noticed that when applying a constant force field to object1 (remove comment from tag1 in the scene), the simulation works as expected meaning that object1 is pulling object2.
Whereas when applying a constant force field to object2 (see…[Read more]
- Load More