1. CMake is the first step before the compilation. I think you are confusing these two different steps: (i) configuration of the project with CMake and (ii) compilation
2. The CMakeLists.txt referred here corresponds to the CMakeLists located in the sources of SOFA
In the CMake configuration (I guess using the cmake-gui interface), you need to set the CMake variable for boost. As detailed here in the doc, you can create a new entry
BOOST_ROOTand specify the path to your boost directory.
If you struggle, please specify us your OS and all your versions (SOFA, boost, cmake)
Thank you for your question.
SOFA is mainly a framework for solid mechanics. Few codes are actually computing fluid dynamics.
You can find two classes available for this:
- examples/Components/behavior/Fluid3D.scn : implementing on an Eulerian grid the work from Dr. Carlson (see thesis…
I come back to your issue.
Apparently you want to mesh this yarn surface (stl) mesh, right ?
Since it is very thin, all meshers will struggle in the meshing process.
What do you want exactly to model from this mesh again ?
Where do you want to be accurate in simulation ?
1. Cool let us know about it
2. I guess you are using these components within a node (a Context) which uses the CUDA templates. No GPU version seems to exist in the open-source repository. Therefore, the instantiation using the template “CudaVecxd” will not work.
For your information, instead of GPU, we have an independent…[Read more]
I am sorry I sent you a reply that apparently never succeeded.
In the open-source core of SOFA, the only possibility to create curved shapes with beam elements is to load a mesh including a curved geometry made of edges.
1. Building sofaCUDA Plugin – using CudaVec3d
Major changes occured in the last months in SOFA, affecting SofaCUDA. Which version are you using? master branch? v17.06 branch (as specified)?
CUDA toolkit relies on floats, this explains I guess the issues you are facing.
With the latest version of SOFA, you might need to compile i…[Read more]
Thank you for your question and welcome to the SOFA forum!
It seems you compiled SOFA successfully. However, when you run runSofa, it runs a batch simulation, i.e. without GUI. Was Qt properly found in the configuration (CMake) phase?
When you run for the first time, it is possible that the .ini files (config file for view for…[Read more]
I tried last week to get back with the Geomagic.
I saw what you meant. I had less than a hour to build and test. From this, I would really go for a TransformEngine recovering as input the Geomagic position, and providing an output position for the right_tip MechanicalObject. Then, you could apply rotation, but a bit of code in needed…[Read more]
Thank you for your interest in SOFA and welcome in the SOFA forum!
You apparently did all good steps and I don’t see the issue:
– your device seems to be well setup
– the name is the same in the scene and in the configuration
Have you tried to re-setup and configure your Geomagic device?
I will try the plugin myself next week when I…[Read more]
I think I better understood, the question is how to correctly access the fields of a MechanicalObject in C++. Your approach using
Just a remark: this means that your exporter will implicitely browse its node and look for a MechanicalObject. In SOFA, we are now advising to rather use…[Read more]
Before anything, I apologize I am no expert from the Flexible plugin.
If I understand correctly you are using Flexible, in a scene written in python. Is that correct?
Is the gradient matrix directly computed from a Flexible component? or do you want to compute it yourself from the position, rest_position and topology information?
Ok, you then have a problem of dependency. Let me explain.
You are including classes contained in the SofaBaseTopology library. As shown in the CheatSheet (not perfectly up to date FYI), the SofaBaseTopology belongs the SofaBase package.
Here is the CMakeLists.txt you need to use:
- Load More