[Hugo]

Hi Binesh,

I guess this component is stored in one of your plugins, right ?
You should set the right dependency to you plugin: you need to find the package SofaBase in which the lib SofaBaseTopology is located. With this lib, you can use the TopologyEngineImpl.

This might be a solution. Let me know if it helps,
Cheers,

Hugo

[Hugo]

Hi Alex,

We noticed both messages (forum and contact form).
Thank you very much for your interest in SOFA!
SOFA is a good solution for medical simulation, even if the start can be a bit tough, but we are here to help anytime!

In the binaries available on the download page, runSofa is available. With this binary, you should be able to run all examples (located in examples/Components and examples/Tutorials).

Otherwise, you can checkout the sources via GitHub and compile SOFA as detailed in the online documentation. You will then be able to run the Modeler. However, this Modeler is now deprecated and not supported anymore. Again, the examples stored in examples/Components and examples/Tutorials should really help starting with SOFA.

As you might have noticed, a Get Involved page summarize all existing media and resources around SOFA. Do not hesitate to have a look.

Could you also share with us what kind of application you are aiming at?
We would be pleased to assist you in your developments and help you promoting your results. Therefore, do not hesitate to keep us updated.

For any further issue, please do not hesitate to post the forum for technical issue or contact us for more general questions.
Best,

Hugo

[Hugo]

Hi nlete,

Can you read to which the final position the tool is jumping ?
This might come from the value you set in positionBase=”0 0 0″.
Can the Geomagic device be re-calibrated ?

Keep us updated,

Hugo

[Hugo]

Hi nlete,

Did you try with master branch?
I think this might be due to the FixedConstraint. FixedConstraint fixes the positions of some points. But during the collision, the velocity of the same points might be affected and increased. You could try replace the FixedConstraint with RestShapeSpringForceField, see if it works.

Let us know if it works

Hugo

[Hugo]

The easier, the better!
You’re welcome.

Cheers,

Hugo

[Hugo]

Hi Ruilang,

It means there is any issue with the handling of topological changes. It might come from the TriangleSetTopologyModifier. I am really not an expert in this area. I’ll try to investigate or find someone who can have a look. Let us know if you solve your issue!

Best,

Hugo

[Hugo]

Hi Sisi,

You should rather look at the MeshGmshLoader.
An example is available in examples/Components/loader/MeshGmshLoader.scn

Best,

Hugo

[Hugo]

Hi Cristóbal,

Alright, I set the topic as resolved then.

But you need to know that this uniform mass is not “physically” correct, since each node has the same mass, regardless from the topology. It corresponds to a mass matrix M diagonal with one single constant value on the diagonal components.

Do not hesitate to create a new topic for any further question.
Best wishes,

Hugo

[Hugo]

Hi Sen,

Indeed there is example of C++ scenes in applications/tutorials.

The source code of SOFA is hosted on GitHub : https://github.com/sofa-framework/sofa
You can clone it with git and browse it.

What do you mean learn the source code?

Hugo

[Hugo]

Dear all,

J-3 before the STC#3!!

Please do not hesitate to share with us your latest achievements in vidéo, contributions and expectations around SOFA! The consortium will make sure to show and share them with all our developers.

To attend the scientific and technical committee, please contact us.

Cheers,

Hugo

[Hugo]

Very nice to hear!
Do not hesitate to post further issues or help other users 😉

Best wishes from France,

Hugo

[Hugo]

Dear Cristóbal,

Welcome to the SOFA community!
The SparseGridTopology is an option to create a sparse grid (obviously). If all you want is (love) create a basic cube, you can also have a look at RegularGridTopology (see examples/Components/topology/RegularGridTopology.scn) or the CubeTopology (see examples/Components/topology/CubeTopology.scn).

As you noticed in the example SparseGridTopology.scn, the coarser the mesh, the stiffer the dragon. But this has nothing to do with the mesh or the mechanical constitutive law: the scene uses a UniformMass. This mass defines a mass per element. The more elements you have in the mesh, the higher the mass.

Is that clear?
You should instead use the MeshMatrixMass or the DiagonalMass (for lumped mass).

Best

Hugo.

[Hugo]

Hey Lujain,

I needed also to update my CGAL version.
I am using CGAL plugin in SOFA master branch on linux, boost_1.58, and CGAL4.9 (as you did). I am getting significant errors as well :

In file included from /data/Softwares/sofa/src/master/applications/plugins/CGALPlugin/MeshGenerationFromPolyhedron.inl:39:
In file included from /usr/local/include/CGAL/Mesh_criteria_3.h:31:
/usr/local/include/CGAL/Mesh_3/global_parameters.h:33:6: error: "BOOST_PARAMETER_MAX_ARITY must be at least 12 for CGAL::Mesh_3"
#    error "BOOST_PARAMETER_MAX_ARITY must be at least 12 for CGAL::Mesh_3"
     ^
In file included from /data/Softwares/sofa/src/master/applications/plugins/CGALPlugin/MeshGenerationFromPolyhedron.cpp:33:
In file included from /data/Softwares/sofa/src/master/applications/plugins/CGALPlugin/MeshGenerationFromPolyhedron.inl:39:
/usr/local/include/CGAL/Mesh_criteria_3.h:174:3: error: too many template arguments for class template 'parameters'
  BOOST_PARAMETER_CONSTRUCTOR(Mesh_criteria_3, (Base), parameters::tag,
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/boost/parameter/preprocessor.hpp:1136:5: note: expanded from macro 'BOOST_PARAMETER_CONSTRUCTOR'
    BOOST_PARAMETER_CONSTRUCTOR_AUX( \
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/boost/parameter/preprocessor.hpp:1126:5: note: expanded from macro 'BOOST_PARAMETER_CONSTRUCTOR_AUX'
    BOOST_PARAMETER_FUNCTION_PARAMETERS(tag_namespace, ctor, args)          \
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/boost/parameter/preprocessor.hpp:562:27: note: expanded from macro 'BOOST_PARAMETER_FUNCTION_PARAMETERS'
    ) : boost::parameter::parameters<                                               \
                          ^
/usr/include/boost/parameter/parameters.hpp:714:8: note: template is declared here
struct parameters
       ^
In file included from /data/Softwares/sofa/src/master/applications/plugins/CGALPlugin/MeshGenerationFromPolyhedron.cpp:33:
In file included from /data/Softwares/sofa/src/master/applications/plugins/CGALPlugin/MeshGenerationFromPolyhedron.inl:39:
/usr/local/include/CGAL/Mesh_criteria_3.h:174:3: error: too many template arguments for class template 'match'
  BOOST_PARAMETER_CONSTRUCTOR(Mesh_criteria_3, (Base), parameters::tag,
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/boost/parameter/preprocessor.hpp:1136:5: note: expanded from macro 'BOOST_PARAMETER_CONSTRUCTOR'
    BOOST_PARAMETER_CONSTRUCTOR_AUX( \
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/boost/parameter/preprocessor.hpp:1129:5: note: expanded from macro 'BOOST_PARAMETER_CONSTRUCTOR_AUX'
    BOOST_PARAMETER_FUNCTION_FWD_CONSTRUCTORS( \
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/boost/parameter/preprocessor.hpp:1120:5: note: expanded from macro 'BOOST_PARAMETER_FUNCTION_FWD_CONSTRUCTORS'
    BOOST_PARAMETER_FUNCTION_FWD_CONSTRUCTORS0( \
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
note: (skipping 30 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/usr/include/boost/preprocessor/control/iif.hpp:25:60: note: expanded from macro 'BOOST_PP_IIF_I'
#    define BOOST_PP_IIF_I(bit, t, f) BOOST_PP_IIF_ ## bit(t, f)
                                                           ^
/usr/include/boost/preprocessor/control/iif.hpp:32:31: note: expanded from macro 'BOOST_PP_IIF_1'
# define BOOST_PP_IIF_1(t, f) t
                              ^
/usr/include/boost/parameter/preprocessor.hpp:364:39: note: expanded from macro 'BOOST_PARAMETER_FUNCTION_FWD_MATCH_Z'
    , typename boost::parameter::aux::match< \
                                      ^
/usr/include/boost/parameter/preprocessor.hpp:98:8: note: template is declared here
struct match
       ^

We’ll see what we can do with some of the plugin developpers..
Keep you updated.

Cheers,

Hugo

[Hugo]

Hi Ruilang,

Indeed, something seems to move in your scene, thus affecting the bbox computation, i.e. visualization.

Could you share with us here your XML scene ?

If the value increases when you are moving the mouse, the problem might come from one of your draw() functions.

Best,

Hugo

[Hugo]

Hi Ruilang,

Thank you very much for this video that helps a lot!
It seems to be a problems related to the camera, and more especially to the params znear and zfar (actually znear mainly).

Both znear and zfar are computated from the bounding box (BBox) of the scene, itself computed from your MechanicalObject. In your video, the value of znear seems to change change, which means that the BBox changes due to a moving MechanicalObject.

A quick fix would be to set yourself a fix value of the parameter bbox of your MechanicalObject, e.g.:

<MechanicalObject name="myMO" bbox="0 0 0 10 10 10" />

Let me know if this helps.
Cheers,

Hugo

[Hugo]

Hi Dongun,

So I understand that you use the pre-compiled binaries. Right?

Could you please provide us:

• the complete console message when running buffoon.scn
• and the complete message in the library loading error” message Box ?

Thks.

[Hugo]

Dear Dongun,

What version of SOFA are you using ? v16.08 (see tag) ? v.16.12 ?

Did you run the SOFA binaries and compiled yourself the LeapMotion plugin separately ?
Did you compile the SOFA sources while activating the LeapMotion plugin ?

Did the compilation run properly ?
What is the error you have when loading the dll ?

Best

Hugo

[Hugo]

Hi Lujain,

Hard to help, we need more info.
Could you please share your mesh and your scene?
What is the error when SOFA crashes?

Best,

Hugo

[Hugo]

You’re welcome @wq57fan.
There is now a documentation page on it: Write a scene in Cpp

Do not hesitate to open new topics if you need it or assist user based on your own experience. Best,

Hugo

[Hugo]

You’re more than welcome nlete !!
Do not hesitate to post any new topic if necessary, and help other users as well 😉

Best,

Hugo

[Hugo]

Ok then I close the topic since it was not SOFA related.
Good luck with your research Lujain !

[Hugo]

Thank you for your feedback.
Here is the documentation page updated.

Do not hesitate to contribute to it.

Best,

Hugo

[Hugo]

Dear Zahra,

I looked at both fine and coarse simulations.
It obviously does not give the same results, due to the mesh resolutions.

However, in order to have the coarse simulation driving the fine mesh, I tried to put them in one single scene with a BarycentricMapping (input=coarseMesh output=fineMesh). But it won’t work well since, look, the meshes are not the same size:

Cheers,

Hugo

[Hugo]

Hi Sen,

Please, detail a bit more your posts, by providing scene files, and meshes so that anyone can really help you.
Yes, I guess changing the stiffness and contactstiffness would affect the physical behavior. Did you test it ?

Hugo

[Hugo]

Hi,

I am sorry Sen, I really don’t get what you want to achieve.
Could you reformulate it please ? or give an illustration.

Hugo

[Author]

Posts