[Hugo]

Hey @toriwalnuss

we always focus on the first error namely:

 CMake Error: File /home/tori/sofa_21/src/applications/plugins/SofaPython3/ExternalProjectConfig.cmake.in does not exist.

Can you explain it?
Best

Hugo

[Hugo]

Ok then you could write something like:

sofa::component::constraintset::GenericConstraintSolver* solver;
type::vector< double > constraintForces = solver->d_constraintForces.getValue();

if (condition)
msg_info("Constraint Forces") << constraintForces;

Keep us posted if this helps.
How do you get the pointer to the GenericConstraintSolver?

Best,

Hugo

[Hugo]

Hi @serkan-ergun,

The console is clearly telling (auf Deutsch though) that you do not have access granted to this file. It really sounds more like a right issue on your machine, doesn’t it?

Did you compile both SOFA and SofaPython3 together? On the same Windows account?

Best

Hugo

[Hugo]

Hey @ewpostek

Definitely, here CMake tells you that you need to install pybind on your machine.
If it is already done, you need to pass its installation path in the variable: CMAKE_PREFIX_PATH as CMake explains it.

Does it help?

Best

Hugo

[Hugo]

Hey @akthetimes

From what I see you are attempting to do this in C++. Correct?

The GenericConstraintSolver has two dedicated options to compute the constraint forces:
– computeConstraintForces: boolean enablin the storage of the constraintForces
– constraintForces: vector containing the constraint forces

The type of constraintForces is type::vector< double >, make sure you are accessing it properly (WriteAccessor) and that you use the proper data type.

Since both are SOFA data, you can access them from outside the GenericConstraintSover.
Do you see my point?
Do you have a code snippet on your end that we could edit?

Best

Hugo

[Hugo]

Hey @dlouis & @akruszew

@psomers is right! Another thumb up for him!
Best,

Hugo

[Hugo]

Hey @serkan-ergun

As we discussed a bit earlier, I do not know anyone who have tested it so far.
The permission problem sounds more related to the rights on your machine than to a real install issue. Have you made progress on this?

Best wishes,

Hugo

[Hugo]

Dear @ericcui

Welcome on the SOFA forum!
In fact, c++ writing of a scene is less and less used among the community. People rather go for python scripting. Is there a reason why to choose c++ on your end?

Cutting is quite a piece of work. Only few examples are available in SOFA such as the TopologyModifiers in the examples. Anyway, we would be glad to assist.

Best wishes,

Hugo

[Hugo]

Hi @eaparra

Taking the values and dimension of your beam what should be this natural frequency?
And what is the one given by SOFA?

Best,

Hugo

[Hugo]

Keep us posted @qdyuan4619 😉

[Hugo]

Ola @ninaten !!

StackOverflow tells me : floating Point Exception happens because of an unexpected infinity or NaN. Could you share the scene and mesh with which you are having this error ? It is a runtime error from what I understand from your message. Correct? Which loader are you using?

Best wishes,

Hugo

[Hugo]

hey @shaswat2001

What do you mean by “behaving as a rigid body”?
Could you share your scene and explain the expected behavior?

Best wishes,

Hugo

[Hugo]

hey @zhangshuyong

If you are using the source code, could you try changing in SofaPhysicsSimulation.cpp line 287: AddAlias by addAlias ?
Let me poke anyway the SofaPhysicsAPI expert @epernod on this 😉
Best wishes,

Hugo

[Hugo]

You’re most welcome @agustinsantana!

[Hugo]

Hey @agustinsantana

Which SOFA version are you using?
If you are using the sources (SofaPardiso does not come with the binary version), you need to activate the CMake option PLUGIN_SOFAPARDISOSOLVER and also follow the README.md before configuring and compiling again.

Best wishes,

Hugo

[Hugo]

Hi @agustinsantana

Your question does not seem related to this post.
Could you create a dedicated post please? Could you also in this new post specify the issue that you are facing (config, SOFA version, SofaPython3 version, error log etc)

Thanks a lot in advance

Hugo

[Hugo]

Hi @eaparra

Great to read, thanks for your feedback.

Hugo

[Hugo]

Hey @shaswat2001

The question is rather which body is actually actuated by your cable?
Could you share the scene you are starting from?

Best wishes,

Hugo

[Hugo]

Hi @eaparra

The problems comes from the tolerance set to the ConstraintSolver. It is way to high. You need to request the CSolver to be more accurate. It must somehow related to the square of the expected error: if the expected error is about 1e-3m then tolerance should be 1e-6.

With :

<GenericConstraintSolver tolerance="1e-8" maxIterations="1000"/>

are completely disappearing in Example_2 for me./
Note that we provide training for having the theoretical background on Lagrange based constraint. There is also a whole doc online here.

Best wishes,

Hugo

[Hugo]

Hey @shaswat2001

The error given by the SubsetMapping is explicit: points from one mesh (probably the submesh) is not considered as inside the input mesh.

But in fact, from what I see from your files, you are aiming at extracting the surface of your *.msh mesh. To do so, you should rather use a TopologicalMapping. See for instance the Tetra2TriangleTopologicalMapping example. Let me know whether this is what you are looking for.

Best wishes,

Hugo

[Hugo]

Hey @pasquale94

You should compile the v21.06 branch of the SoftRobots plugin with the v21.06 release of SOFA.
Let me know if this solves the issue.
Best wishes,

Hugo

[Hugo]

hey @vanisri

You are right, this is missing. But this is on the roadmap of one of our engineers since we are updating the core of SOFA and its content in the SOFA NG project.
Further to this work, early 2022, we should see this package description incoming!

You can also refer to these examples. And never hesitate to get back to us when you face a problem.

Best wishes,

Hugo

[Hugo]

Hey @qdyuan4619

Thanks a lot for this detailed reply. Having all info will definitely help helping!
But I must say that I do not get the problem.
Maybe @guillaumeparan may help

Best,

Hugo

[Hugo]

Hey @agustinsantana

the dt of my previous post indeed refers to the global time step of the simulation : the one defined in your root node and visible in the mainscreen.
Regarding the pressure (sorry for my inaccuracy I am no user of the SoftRobots plugin myself), I meant that in the SurfacePressureConstraint you should specify the data field value where the value defined must be equal to the pressure you want to apply divided by the global time step mentioned above.

Let’s say that you want to apply 20 Pa (if your scene uses SI units) and that your time step is dt=0.5, you should then set value=10.

Is this clearer?
Best wishes,

Hugo

[Hugo]

Ola @eaparra

Apologies for the delay.
The LinearMovementConstraint and its associated (missing) doc are hard to get indeed. The keyTimes are times between which the movement will be interpolated: between keyTimes[0] and keyTimes[1], a linear interpolation is computed between the movements[0] and movements[1] (keyTimes and movements being input vector data). This motion can be applied on specific indices.

You therefore cannot make a movement without specifying the keyTimes.
Let me know if this helps.
Best,

Hugo

[Author]

Posts