[Hugo]

Hi @eliekhairallah

I don’t see anything about Qt in CMake, it is a dependency though. Did you follow the Build instructions for Windows?

You are not supposed to move files during compilation.
What is the error when the compilation stops?

Best,

Hugo

[Hugo]

Hi @benjamin5523

There several way of doing this.
I recommend you to choose one and stick to it.

The one I prefer is: create a repository apart from SOFA, containing all external plugins you want (STLIB, SoftRobot etc). At the root of this repository, you can then create a text file: CMakeLists.txt with the following structure

find_package(SofaFramework)

sofa_add_plugin(SoftRobot/ SoftRobot)
sofa_add_plugin(STLIB/ STLIB)
...

Your repo should look like:
repo
|
— STLIB/
— SoftRobot/
— CMakeLists.txt

Final step, when compiling SOFA, you add to the SOFA_EXTERNAL_DIRECTORIES entry the path to your repository containing the above-described CMakeLists.

When configuring (SOFA), you will now see your plugin options appear.
Configure, generate and compile.

I hope this helps.

Hugo

[Hugo]

Hi @qwe12050

it took me some time to found because it’s very simple!
Check the case of your node “constraint” one is a “c” another is a “C”

Best

Hugo

[Hugo]

Hi @outtt

Your last statement is actually incorrect.
The “Rigid” type used in the Beam model is actually not rigid but it rather corresponds to a frame model (position + orientation). Between two frames, a deformable beam is defined. You can have a look to the example : examples/Components/forcefield/BeamFEMForceField.scn

Cheers,

Hugo

[Hugo]

Hi @eddhoare

For your information, the following work was performed with FEM:

Best

Hugo

[Hugo]

Hi @xavierleorio

I just answered a very similar question here.

Best,

Hugo

[Hugo]

Hi @rainvector (and @xavierleorio asking a similar question in another post)

Thanks for pointing out this work. It is indeed an work performed about 8-10 years ago. Currently, the InSimo company is working on this topic again. But at my best knowledge, it has not been widely refreshed in the open-source community.

Simulating suture is indeed more complex that only collision detection. You need to detect collision, then regarding a perforation threshold create a perforation constraint and then constraint your needle and your tissue. There is interesting research topics there. I would be happy to guide you (as much as I can) and connect your within the community. A joint project could also be promising! In this case, do not hesitate to contact me in PM.

Best wishes,

Hugo

[Hugo]

Hi @scharreyron

Sorry for the delay!
I know that you can still have some trace information in MacOS when a crash occurs: a “Report” will be proposed, if you agree to send the report a window opens with some additional bash information about the crash. It could help.
Could you try to copy this error report?

Best

Hugo

[Hugo]

Hi @sarah

It’s good to dare looking in the code.
Do never hesitate to propose also improvement to the doc yourself, the documentation is open for contribution as well.

I will try to work on it, since the topic is fresh.

Hugo

[Hugo]

Dear SOFA forum,

The SOFA Technical Committee of the first 2020 semester (STC#9) took place late April 2020 and 100% online due to the Covid-19 situation. Consortium members and core developers met to prepare the upcoming release (v20.06) and design the technical roadmap for the next release (v20.12). Your opinion matters, join us next time for STC#10!

The report of the committee as well as the roadmap are now available online.

The next large event gathering the SOFA community will be the SOFA Week 2020. The international community will meet on the 23-27th November 2020 in Paris to present scientific and industrial projects, while fostering the networking!

Looking forward to seeing you in Paris!

Hugo

[Hugo]

Hi @twxu

You are very welcome! (and thanks for closing the topic)
Best

Hugo

[Hugo]

Hi @twxu

Welcome to the SOFA forum then!
Do you have python installed on your machine? This is what seems to be missing.

Best

Hugo

[Hugo]

Hi @ruofeng,

The SofaPython plugin is based on the python2.7 library. However, this plugin does NOT allow to use SOFA in a python (2.7) environment but only allows for writing python scripts which are run by SOFA, thus having more interactivity.

Not only does the SofaPython3 plugin to link against the python3 library but it allows for the first time to run SOFA simulations from a native python environment. This was not possible with the previous SofaPython(2.7) plugin.

I hope this answers your point.
Best,

Hugo

[Hugo]

Hi @eliekhairallah

Are you sure the compilation succeeded (if no binary is generated)?
Did you specify the compilation CMAKE_BUILD_TYPE = Release ?

Could you please share all the output of the CMake configuration? the output of the compilation?

Best

Hugo

[Hugo]

Ouh yeah! Do not hesitate to send me videos so that I can highlight both of your work!
Congrats @pasquale94 and @NickHockings for helping so much!

Hugo

[Hugo]

Hi @eddhoare !

To model catheter or endoscope, why not choosing a approach based on the beam theory?
You can directly get inspired from the example scene : examples/Components/forcefield/BeamFEMForcefield.scn

Best,

Hugo

[Hugo]

I noticed Fred suggested to run a command, but I have sometime to run another one, could you test this:

$ open -F runSofa.app

Hugo

[Hugo]

I close the topic since the full doc is here for constraint correction.

Hugo

[Hugo]

With a bit of delay ^^ @luibass92

A doc page has been written on the ArticulatedSystemMapping here.

Hugo

[Hugo]

Hi @johnza

What effect of the fluid are you exactly looking at? Floating? Pressure? Flow?
As you know, SOFA is mainly focused on solid mechanics and only SPH fluid or Eulerian approach are available.

We had a code modeling buoyancy: BuoyantForceField but it was deprecated and removed since v18.12.

Best,

Hugo

[Hugo]

Hi @eddhoare !

This part of SOFA is a bit rusty indeed. JointSpringForcefield are a bit cumbersome to describe. You also have the AngularSpringForcefield.
But you are using the right components.

What are you modeling exactly?

Hugo

[Hugo]

Hi @outtt

Thanks for the drawing it helps a lot to understand!
I would then go as follows:
– for the surface mesh, use the FEM model of your choice using Vec3d (3 DOF per nodes)
– in a subnode create the BeamModel (which looks a bit like centerlines, see the recent plugin here) and set a RigidMapping between your Vec3d and your Rigid3d dofs.

Let me know if this works as expected.
Best wishes,

Hugo

[Hugo]

We will make sure about this.
Stay tuned in September 😉

[Hugo]

I close this topic since this one is duplicating.

Hugo

[Hugo]

Hi @jerry

We are working on this currently : easier and cleaner output from matrices (stiffness, mass etc). For now, I would say for your own use case, you can pick the value in the code when it is computed, create a dedicated data which would then be available for export.

Hugo

[Author]

Posts