[Hugo]

Eligiusz,

This is strange. I just did it, and I just have the usual output:

Cloning into 'sofa/v16.08/src'...
remote: Counting objects: 245926, done.
remote: Compressing objects: 100% (3799/3799), done.
remote: Total 245926 (delta 2234), reused 0 (delta 0), pack-reused 242114
Receiving objects: 100% (245926/245926), 284.13 MiB | 32.06 MiB/s, done.
Resolving deltas: 100% (193139/193139), done.
Checking connectivity... done.
Checking out files: 100% (11997/11997), done.

Did you do anything special?
Is this a brand new download?

Hugo

[Hugo]

Hi Eligiusz,

No worries !
This is just due to tags which were removed in the github interface, and it appears that a reference is still present in the .git/ repo. But this won’t affect your download.

Cheers,

Hugo

[Hugo]

Dear Karthik,

To answer you point by point:

1. There is nothing wrong in the configuration. CMake just tells you that you do not have Python and metis installed.
2. The compilation crashes when it comes to the Sensable plugin. I am no expert of this plugin, but it should work for windows. We are currently working on it to release a new version of the plugin soon. I will ask other devs to look at it.
3. Indeed, nothing changes about Sensable between the v15.12 and the v16.08.

Sorry not to be able to help more.
I’ll come back with more info.
Cheers,

Hugo

[Hugo]

Hi Naman,

Could you tell me where in the tutorials you noticed this, please ?
About SOFA, only Qt5 is officially supported (Qt4 should compile), thus allowing you to proceed without worries !

Cheers,

Hugo

[Hugo]

Hi @fgafarov,

If no further help is needed, I will close the topic.
May I?
Cheers,

Hugo

[Hugo]

Cool ! thank you Binesh for sharing your issue and solution !
Best wishes,

Hugo

[Hugo]

Hi @jjcasmar,

Did the previous answers help you in solving your issue ?
If yes, I would then close the topic.

Best wishes,

Hugo

[Hugo]

Hi @fabienpean,

Did Thomas’ answers help you in running your examples and simulations ?
Best wishes from Stras,

Hugo

[Hugo]

Hi @mtcooper115,

How is it going?
Could you let us know whether the topic is solved.

FYI a new release of SOFA (v16.08) is now available.
Cheers,

Hugo

[Hugo]

Hi Weng,

Without any answer from you and due to the answer provided by Guillaume, we’ll set the topic as solved.

Best wishes,

Hugo

[Hugo]

Hi Binesh,

Could you share a (simplified if necessary) version of your scene?
This would greatly help us in assisting you.

Cheers,

Hugo

[Hugo]

Hi Alex,

Was my answer helpful for you?
Cheers,

Hugo

[Hugo]

Hi Alex,

All you need is love, and activate the flag SOFA_ENABLE_QWT.

Afterwards, during the CMake configuration, if you face the error mentioned previously in this thread:

Could not find a package configuration file provided by “Qt5Quick” with any
of the following names:

Qt5QuickConfig.cmake
qt5quick-config.cmake

You need to install Qt5Quick
sudo apt-get install libqt5quick5 qtdeclarative5-dev

Cheers from Stras,

Hugo

[Hugo]

Dear Wong,

y is the solution (x_sol) of the linear system Ax=b, without constraints
H is the (holonomic) constraint matrix
λ are your Lagrange multipliers
and d is the constraint violation.
Correct me if I am wrong Max.

You can find information in the paper about SOFA, from page 21.

There is only few expert in constraint solvers, we do have some of them in Strasbourg.
The Consortium may provide you training if needed, if you become a Consortium member.

Best regards,

Hugo

[Hugo]

Hi Wong,

Do you need any further assistance?
Best wishes,

Hugo

[Hugo]

Just to understand,

You got a tool with a jaw, right ? articulated.
But, why should the torus exactly be constrained?

I got the same behavior as yours.
But would the unstability of the jaw be due to the fact that the torus becomes both:

• in contact the upper jaw
• and constrained with the lower jaw ?

Then, the system becomes unstable.
Would that be possible (and therefore not directly due to BilateralInteractionConstraint) ?
Thanks.

Hugo

[Hugo]

Hi Irvin,

Could you tell me exactly which scene you are trying to reproduce? 6_FEM1 ?

Note that it always takes few seconds at the scene loading to pre-compute the compliance matrix with the PrecomputedConstraintCorrection (saved in the .comp file).

However, I remember I fixed something since the v15.12 : you can have a look at this commit.

Let me know if this solves your issue.

Best,

Hugo

[Hugo]

Dear Elek,

I guess you are referring to the article “Volume Contact Constraints at Arbitrary Resolution”. For more information about the paper itself, you can find it here and if you have any question about it, do not hesitate to contact directly the authors.

If your question is : is it possible in SOFA to work with volumetric independent shapes and computing their stress, the answer is yes. But, then you need to be more specific about what you want for material laws, for collision detection and response algorithms.

Best,

Hugo

[Hugo]

Dear Wong,

Could you please tell me what is your configuration so that I can try to reproduce your issue ?
OS: Windows, Linux, MacOS ?
version of SOFA : v15.12 ?

For me the simulation seems to run properly and the torus is well constrained with the lower part of the tool.
If you have also a video of your problem, do not hesitate to share it.

Cheers,

Hugo

[Hugo]

Dear Ben,

Indeed the most straightforward way is to directly display the mechanical object and not the visual. However, as you notice, this will imply strong performance constraints (fine mesh –> poor performances).

I will discuss this with researchers working on the topological changes in SOFA and maybe put them in contact with you. I come back to you as soon as possible.

Best,

Hugo

[Hugo]

Thank you very much Max for sharing this !!
Very nice work. Cheers,

Hugo

[Hugo]

Hi Wong,

To obtain such a behavior, the best would be to write your own constraint which would be activated depending on an event.

You can look at the code of FixedConstraint.inl or others.
Then your code should involve/listens to events (mouseclick, or any other) and activate the constraint regarding this event.

You can already find documentation about events here.

Would you like us to keep this thread open?
Cheers,

Hugo

[Hugo]

Hi Jean-Nicolas,

As I already said, this is some kind of a hook. The fact is that the constraint solver seems not to handle projective constraints properly.

I did not succeed to reproduce your error when applying the trick/patch written above.
But I am using a newer version of the Omni driver (not yet released but soon!).

As I said, you can use the RestShapeSpringForceField instead of fixed constraint, but this is no real solution.

Cheers,

Hugo

PS: in the Sensable plugin, a EnslavementForceFeedback is always added for the collision model associated to the Omni.
I dont’ see it in your scene, but I am no expert in collision detection and do not know the role of this component.

[Hugo]

Hi Thomas,

Sorry to hear that.
I created an issue on GitHub to make sure to remember of the problem and maybe someone already solved it.

Cheers,

Hugo

[Hugo]

Nice, good luck!

If you need further help, do not hesitate to create a new thread! We would be glad to assist you again!
Cheers,

Hugo

[Author]

Posts