Forum Replies Created
-
Posts
-
Hi Malli,
Thank you for posting the output.
Could you also tell us what options (CMake config) did you activate?Dear Bushra,
I think the compilation worked fine, but the problem must be due to the Modeler. As mentioned in many thread, the Modeler is an old application and it includes several bugs. I would therefore advise to build your XML scene and test it with runSofa.
Let us know if your scene is working in runSofa.About the Modeler, we are currently putting a lot of effort in improving SOFA itself. In the future, we will take time to improve the Modeler. I will look at this issue of loading a plugin in the Modeler.
If, you need any further help in building your scene, do not hesitate to ask, we are here to help.
Cheers,
Hugo
Please, can you post the next answers/questions on this thread instead ?
Thanks in advance.
Dear Malli,
As Alex diagnosed in the previous post, you did not successfully build SOFA since the make process failed. We can help you in this, but you need to give us the entire output of the failure. All what we can notice from what you wrote is that there is an issue with MeshMinProximityIntersection.
Can you send us the whole output ?
Cheers,Hugo
Dear Raja,
I guess, you are trying to compile the MeshSTEPLoader plugin. This plugin is not compiled by default in SOFA since it has a dependency to OpenCascade library. This is the error given to you by CMake.
To solve it, you have to install OpenCascade on your system.
Next time, do not hesitate to create a new forum thread for a new question, if it is not related to the current topic.
Cheers,
Hugo
Hi Raja,
Your problem is caused by qwt : it has a dependency to Qt5Quick.
Either you de-acticate qwt in SOFA or you install Qt5Quick on your linux.Cheers,
Hugo
Hi Minmin,
To learn about SOFA, I would advise you to read over the documentation. It is unfortunately still not complete, but we are currently working on it.
You can also refer to the book chapter about SOFA.
Finally, about the files you want to generate:
- for .msh files, Gmsh or Tetgen allow to generate this format
- for .sph, this is a format to define spheres. It can be generated manually or maybe (not sure) this page may help you.
Do not hesitate to carry on using the forum if you have any further questions.
Cheers,Hugo
Hm, I see. At my best knowledge, a subset included inside the loaded mesh is not supported.. What kind of file does support such a subset of the topology?
To dump the position in a file, you can use an exporter (e.g. VTKExporter or ObjExporter).
You can find out more about the engines and loaders on the online documentation:
https://www.sofa-framework.org/community/doc/using-sofa/basic-components/engines/
On this page, you will find information about what you intend to do: a subset topology (from what I understand). Is that what you need?
Dear Ben,
When loading a mesh with a loader:
<MeshGmshLoader name="loader" src="myMesh.msh" />
You can access the position of your points using the data"@loader.position".
Is that what you want to do?To get the indices of the nodes within a cylinder there is no component already publicly available in SOFA, but it is rather easy to write it. You could get inspired from this : http://www.flipcode.com/archives/Fast_Point-In-Cylinder_Test.shtml. If you need more help on this, let us know.
Hope this helps.
Hugo
Hi Michel,
I know @alexbilger already did something very similar to what you mention.
Maybe could he have some suggestions!Cheers,
Hugo
And about the video of introduction to SOFA.
Here they are: https://www.sofa-framework.org/community/doc/getting-started/video-introduction-to-sofa/Cheers,
Hugo
Dear Ceci,
Indeed, it seems there is several issues with the Tutorials in the Modeler, especially with the Pendulum. I would advise to look at the StepByStep instead of the Pendulum.
I will (very soon) take care of fixing the whole Tutorial.
Thank you, for your feedback.
I will let you know as soon as it is fixed.Cheers,
Hugo
Dear @cecigatti,
We are very sorry, the Modeler is not meeting the quality we would expect it to have. We are going to work on this, but this is a significant amount of work.
What do you mean exactly by not able to see the examples?
Small trick: if you have problems launching a scene, you can still start yourself the scene using runSofa ../src/examples/Tutorials/StepByStep/_the_scene_you_want_to_test.scnAbout the falling particle, could you tell me which scene of the tutorial exactly ?
Finally, another advice, you can have a look at the presentations recorded on YouTube. These presentations may help you in 1) understanding SOFA and 2) building your own simulation.
Cheers,
Hugo
PS: I created a new topic in the “Using SOFA” forum, since it is another question.
Dear Ceci,
If you have a structure as follows:
sofa/v15.12/- src/
- build/
The make command has to be done in the sofa/v15.12/build/ directory and after configuring the project with cmake (cmake ../src from the build directory). If the compilation with make completed, you can already run the runSofa executable and play with SOFA!
QtCreator is not compulsory. It is an IDE (integrated development environment) to edit the code, but it isn’t compulsory. If you want to use QtCreator, open project CMakeLists.txt. Choose the sofa/v15.12/build/ as build directory, then click on Finish. The whole SOFA project should appear. QtCreator is ready to compile, and the build configuration is named “all”, though it corresponds to a Release.
The case with two build directories corresponds to the case you want to have a release and a debug build. It might not be useful for you.
Let me know if you need further assistance.
Cheers,Hugo
Alright,
If you change your mind do no hesitate to let us know so that we can help.
And, if you need any assistance in the linking process, keep us informed (in a new topic), we would be happy to help on this as well.Cheers,
Hugo
Hi Zahra,
No minimal configuration for SOFA. However, obviously, the stronger your configuration is, the faster your simulation will run!
About GPU, SOFA does not activate the GPU versions of SOFA by default. Therefore, no need of a GPU card. Nevertheless, if you want to run GPU codes, all you have to do is activate the SofaCUDA plugin.
Does this answer your question?Cheers,
Hugo
Hi all,
Just to add a small detail, you need to set the variable “f_listening” to true. This variable is common to all BaseObject. If true, this variable will allow the call of the handleEvent function in your component.
- either in your code: set “f_listening->setValue(true);” (hard-coded, then your component is always listening)
- or in the scene where your component is loaded : “< mycomponent listening="1" / >”
Hope this helps.
Hugo
Hi Juan Jo,
Are you then implementing the potential energy for the elastic forces in SOFA (based on Vega)? That would be very nice to share!
I know this is already implemented in TetrahedronFEMForceField::getPotentialEnergy()If you need help on this, I can put you in contact with researchers in the field.
Cheers,
Hugo
Dear Thomas,
I am no real expert in memory leak investigation, however, Valgrind seems to be definitely to be the best option.
I shortly looked into the code of “LocalMinDistance” but I couldn’t find an obvious problem (like a pointer which is not properly released, or missing delete on an instance). I’ll let you know if I can find it and I’ll also let other dev know about your issue.
Cheers,
Hugo
Hi Thomas,
There is a sense sometimes to use two topologies. But here the problem is the following.
You use a hexahedron-based topology for the collision since it appears to be more robust.
Did I understand the problem correctly?
But, you want a nice visualization and do the cutting on the triangular mesh.
Using hexa-topology implies that the cutting will be done on the hexa-collision mesh.What you want is :
scissors –> hexa collision –> cutting the triangular meshAt my best knowledge, this does not exist in SOFA. Therefore, you will have to implement a specific engine triggering the cut (on triangles) by listening to the contacts between scissors and hexa.
Hugo
