[Hugo]

Any progress here @daserk ?

Best

Hugo

[Hugo]

Hi @NerioDev and @marco-ferro ,

Sorry for the very late reply.
Have the solution proposed by @akthetimes worked for you?

If it did not, I am sure @guillaumeparan could help on this.
If it did, I would be pleased to have some insights of your achievements. Anyway it could be nice to highlight them at the SOFA Week 2021 Symposium!

Best wishes,

Hugo

[Hugo]

Hey @benjamin

You seem to be using the BeamAdapter which is a private plugin for now.
It is therefore that we do not know very well yet.

I shortly looked into the code no VonMises stress is implemented. It could be interesting to implement it.
Are you using binary version of BeamAdapter or source one?

Best,

Hugo

[Hugo]

Thanks @jonny for letting me know.
Let me introduce you to @froy! Fred, we have an issue here between OglModel/MeshObjLoader to get a proper texture applied. Does it remind you something?

Best,

Hugo

[Hugo]

Hi @eaparra

From what I can run on my machine your scene is working.
Are the results still far from the one you are looking for?

If it is, could you please give me all the physical units and dimension of your object?
e.g. E = 7e10 Pa etc etc.

And sorry for keeping you waiting so long.
Best,

Hugo

[Hugo]

Hey @yupeng,

Any update on your research topic? Have the scene from Cosserat plugin proved useful?

Anyway, do not hesitate to join the SOFA Week 2021 and event present your ongoing work with the entire community!

Best wishes

Hugo

[Hugo]

Sorry wrong nickname, @mdubied

[Hugo]

Dear @dubied

Thanks for your message and sorry for our latency.
All components *SetTopologyAlgorithms have indeed been removed, or it should be rather said that they are no longer needed in the scene graph.

You can just remove them, the scene behavior won’t be affected.
Best wishes,

Hugo

[Hugo]

Hi @jonny

Since OglModel and MeshObjLoader are two different components, I am not estonished to read that there is some differences (even if there should not!).

In this PR #1096, the data field handleSeams was instroduced. It allows the MeshObjLoader to make sure he handles both position and vertices (uv). Have you tried to set it to true ?

Does it solve your problem?
If not, I would add other engineers in the loop more knowledgeable about these components.

Note that loading directly the mesh from OglModel will no longer be possible after v21.06.

Best wishes,

Hugo

[Hugo]

hey @bmanz

I must apologize for the delay of my reply.
Thanks for your question, Brandon.

First could you share the full scene with the meshes so that we can give it a try?

When solving constraints, you only need one ConstraintCorrection. Here you seem to have two for one single object: UncoupledConstraintCorrection and LinearSolverConstraintCorrection. Moreover, the latter needs to be connected to the solver, actually solving the system. In your case, it is the ShewchukPCGLinearSolver on top of the simulation while the SparseLDLSolver is only used for computing a preconditonner of the system matrix.

In a first step, you could try:
– to remove the ShewchukPCGLinearSolver and set the SparseLDLSolver instead (below the Euler integration scheme)
– to remove the UncoupledConstraintCorrection
– and keep only the LinearSolverConstraintCorrection

Again, having the full scene and meshes would help.
Best wishes,

Hugo

[Hugo]

Hi @eaparra

I am so sorry for the delay of our reply.
I just tested your scene (without the Communication plugin), I do not have any instabilities/abnormal vibrations. Have you updated your scene?

Best wishes,

Hugo

[Hugo]

Hi @ruffy369

Sorry for the late reply, we had a very busy September month keeping us away from the forum.

Thanks a lot for your enthusiastic feedback, it’s really good to read.

Regarding the coupling SOFA-ROS, as you noted, a plugin was designed for this purpose by an independent developer. However, this was not really further maintained.

However, we recently introduced an advanced integration of SOFA within a Python3.+ environment. Since ROS does have a python interface, you can simply make SOFA and ROS communicate through python.

Note, that I recently heard about a private C++ plugin interface SOFA and ROS (2). I will investigate whether this code could be made open.

Best wishes,

Hugo

[Hugo]

Hi @benjamin

Firstly, sorry for the late reply.
Regarding your SOFA version, v19.06 starts being really old. You might want to update sometimes soon (using SofaPython3!).

Second, thanks a lot for specifying your first post it helps.

Regarding the AttachConstraint approach, could you share with us all the options (data fields) you gave to the AttachConstraint please?

Regarding the BilateralIC, is the error on the determinant occurring also without the constraint ?

NB : your link on BeamMultiCompMoving.py is not properly set

Best,

Hugo

[Hugo]

Hi @daserk

Sorry that you struggled on this point.
Which version of SOFA and SofaPython3 are you using?

The recent PR #171 fixed the node iterator in python3, preventing from doing the getObject as you are trying to do – if I am correct. This was recently merged within the master branch of SofaPython3, and available in the v21.06.01. You should be able to write:

mytoto = root.getObject("Toto")
if mytoto != None:
    copymydata = mytoto.dataname

Could you try with the latest v21.06.01 please?

I hope this helps.
Best wishes,

Hugo

[Hugo]

Hi @agustinsantana

Sorry for the lack of context, I meant an environment variable SOFA_ROOT on Linux:

export SOFA_ROOT=/path/to/your/SOFA/install/

I hope this is clearer now.
Best

Hugo

[Hugo]

Hi @vanisri

You confirm that you are using v21.06 with VS19 and Win10, correct ?
Are you using the sources or the binaries?

Could you please detail the full command line ?

Did you make sure that:
– you specified the write path to the libSofaPython3 like:
./bin/runSofa plugins/SofaPython3/lib/libSofaPython3.so (for Linux)
– you defined both SOFA_ROOT and added the SOFA python bindings in PYTHONPATH as specified here.

Best

Hugo

[Hugo]

Hi @agustinsantana

I do not know the ModelOrderReduction plugin myself, but have you tried to set the path to your build/install of SOFA in the variable SOFA_ROOT ?
If this does not work, we will contact the plugin’s author.

Best

Hugo

[Hugo]

Hi @jonny

Interesting work and thank you for reporting this issue to us.
The OglModel does have a data field for texture : texturename did you try to use it?

If you have no topological changes in your scene, all you need is to recompute the obj file without the material information. Is this correct? Then a simple obj export should work.

Regarding your second question, my answer is I do not think so.
Let me also poke @froy on this topic to get his eye covering it.

Hope this helps
Best,

Hugo

[Hugo]

Let’s poke @jnbrunet but @sidaty as well on this Caribou topic 😉

Best

Hugo

[Hugo]

Ciao @chiarasapo

How did you define the physics of the “skin” object? It seems to have a very high stiffness and mass compared to the instrument. Therefore, the force feedback resulting is high. You could try to increase the mass of your instrument. A last parameter to adapt could be the stiffness of the RestShapeSpringsForceField.

Looking forward to hearing from you.
Best wishes,

Hugo

[Hugo]

hi @chiarasapo

have you done a PR? I was a bit busy these days and I might have missed it.
Best,

Hugo

[Hugo]

Hey @juan

1. As explained in my previous message, this error comes from the fact that the applyConstraint() function is not implemented. But it is only called for direct solvers. Therefore, using an iterative (=indirect) linear solver like the CGLinearSolver makes the warning disappear.

2. Changing the mass (m), changes the ratio k/m (where k is the stiffness of your system) related to the resonance frequency of your object. Therefore, the time step will have to be adapted for the simulation to remain stable:

decrease the mass –> higher frequency –> smaller time step is required

If you object mass is 0.1796kg then use this value in total mass but you have to choose an appropriate time step.

3. Advice : do not use this real-time option. It affects the time step. Dangerous.

Best wishes,

Hugo

PS: for me none of 13_8 or 13_9 is crashing

[Hugo]

Hey @zaread

I would suggest you take a look at our SOFA online tutorial or you register to one of our training sessions.
We know the first steps for non-simulation profile can be tough and we intend to work on it. Let me know whether you want to chat this further together.

Best wishes,

Hugo

[Hugo]

Hey @kaziabduljamil

On both question, both @jducrocq007 and @amazier were right:
– Ubuntu 18.04 (even better: 20.04)
– for your Qt issue, comes from the fact that during the install of Qt you forgot to select the Qt5 option or you did not add Qt in your CMAKE_PREFIX_PATH. See here for the option selection.

Best,

Hugo

[Hugo]

Hey @sergiopm23

Did @juan ‘s reply help you?
Else, I think your proposed code line Sergio could work under one condition: the box_roi1.indices must correspond exactly – in the same order – to the box_roi2.indices

Is it the case?
Have you solved your issue since then?

Best,

Hugo

[Author]

Posts