Forum Replies Created
-
AuthorPosts
-
HugoKeymaster
Hi Camille
Thank you for posting this issue.
Your the second person today mentioning this issue of non-loaded plugin on Windows. We will investigate this asap. For sure what you can do temporarily is to add the associated lib (dll) in Edit->PluginManager->Add..Moreover, it would be great if you could share (pull-request) the update you did on the MeshSTEPLoader plugin with the latest version of OpenCascade !
I’ll get back to you as soon as possible, to follow the discussion on GitHub: https://github.com/sofa-framework/sofa/issues/558
Best,Hugo
HugoKeymasterHey Yannie
Any luck with this runtime data displayed ?
The OglLabel should work. In the example scene examples/Components/visualmodel/OglLabel.scn, I added this and it works fine (displays the positions of the MechanicalObject):<OglLabel label="@Particles.position" fontsize="20" color="black" prefix="My positions: " updateLabelEveryNbSteps="1" y="75"/>
Hugo
HugoKeymasterHi Sarath
This might be normal : you need to grab the sphere using the shift+left clic
BestHugo
9 January 2018 at 10:41 in reply to: [SOLVED] Translating mechanical objects (not working c++) #10291HugoKeymasterAnother way, would be to use Python for interacting during runtime. This is the most straightforward approach on my point of view.
HugoKeymasterDear all,
First of all, when compiling in debug make sure that you set the path libraries to the debug lib.
For instance @mermail , your CMakeCache shows that you don’t have the debug lib for libpng nor the debug lib for glew:PNG_LIBRARY_DEBUG:FILEPATH=PNG_LIBRARY_DEBUG-NOTFOUND GLEW_LIBRARY_DEBUG:FILEPATH=GLEW_LIBRARY_DEBUG-NOTFOUND
But I guess this is not what is making you real trouble.
Another point is that we fix an issue related to the library in debug in PR #511. This might solve your issue. To take this update with git, you can either cherry pick the commit 6eae64f or checkout master or wait few days for the upcoming release!
Best regards,
Hugo
HugoKeymasterHi @mermail
Did you check the reply from Garibalde just above ?
adding the zlibd should be specified in when compiling in debug. If it does not solve your problem do not hesitate to open a new thread specific to your problem and post the error message.
Cheers,Hugo
HugoKeymasterDear @sarath,
Sorry for not having been able to assist you earlier.
I would like to wish you and all SOFA users a happy new year 2018!From what I understood you aim at interacting with deformable object, right?
One solution is to use the mouse to move one object that collides with its environment. The scene below implements such a case:<Node name="root" dt="0.005" gravity="0 0 0"> <VisualStyle displayFlags="showCollisionModels hideVisualModels" /> <DefaultAnimationLoop /> <CollisionPipeline verbose="0" draw="0"/> <BruteForceDetection name="N2"/> <NewProximityIntersection name="Proximity" alarmDistance="1" contactDistance="0.4"/> <CollisionResponse name="Response" response="default"/> <MeshGmshLoader name="meshLoader" filename="mesh/liver.msh" /> <Node name="Liver"> <EulerImplicitSolver rayleighStiffness="0"/> <CGLinearSolver iterations="200" tolerance="1e-06" threshold="1e-06"/> <TetrahedronSetTopologyContainer name="topo" src="@../meshLoader" /> <TetrahedronSetGeometryAlgorithms template="Vec3d" name="GeomAlgo" /> <MechanicalObject template="Vec3d" name="myLiver" showObject="1"/> <TetrahedronFEMForceField name="FEM" youngModulus="40000" poissonRatio="0.4" method="large" /> <MeshMatrixMass massDensity="1" /> <FixedConstraint indices="1 3 50 20 25" /> <Node name="Collision"> <MeshGmshLoader name="meshLoader" filename="mesh/liver.msh" /> <Mesh src="@meshLoader"/> <MechanicalObject scale="1.0"/> <Triangle name="CollisionModel" contactStiffness="5"/> <BarycentricMapping name="CollisionMapping" /> </Node> </Node> <Node name="Sphere"> <EulerImplicitSolver rayleighStiffness="0"/> <CGLinearSolver iterations="200" tolerance="1e-06" threshold="1e-06"/> <MechanicalObject template="Rigid" name="myParticle" position="-2 10 0 0 0 0 1" showObject="1" /> <UniformMass totalmass="1" /> <Sphere name="Floor" listRadius="1" simulated="1" moving="1" contactStiffness="1000" /> </Node> </Node>
Or you can use an haptic interface. I would suggest for you to have a look at the Geomagic plugin, to the scene applications/plugins/Geomagic/scenes/Geomagic-FEMLiver.scn It’s a really good example of haptic interaction with an hardware interface.
Hope this helps.
Best,Hugo
HugoKeymasterDear Cesar,
Thank you for reaching us through the forum and sorry for the delay of this reply.
I never used BVH animation myself but the demo /examples/Components/controller/ArticulatedHierarchyBVHController.scn is working fine for me. Do you have the same format of file ? Maybe the .bvh format evolved recently ? I know this BVHContainer has recently been deprecated in SOFA because this code has not been used for some time. I would be happy to update it and make it work for you.Best,
Hugo
HugoKeymasterHi Benny,
You are making a good point.
No example of volumetric cutting is available in SOFA, but we are working on it.
You should be able to use it very soon.Best,
Hugo
HugoKeymasterHi @vincentg
Glad to see that you solved your issue.
In case you are facing any other trouble do not hesitate to post them again on the forum.
Cheers,Hugo
HugoKeymasterHey @benoit
Happy new year 2018 !
Did Vincent’s reply help?
If so, can we mark this topic as solved?The SOFA community stays at your disposal for any further question.
Best,Hugo
HugoKeymasterHi @rubab,
But from what you said the problem does not come from the GmshLoader but from the component of your plugin in which you override the positions.
Am I understand it right?
If yes, then the troubleshooting should focus on this class. Can we have access to it?Best,
Hugo
HugoKeymasterHugoKeymasterHi @mermail,
Are you sure to have all dependencies installed?
Because the errors you are having at the compilation are linking errors.Your CMakeCache.txt would help understanding your issue. Could you share it with us?
Best,Hugo
HugoKeymasterDear @rubab,
Welcome in the SOFA community !
Nice to hear that you are using SOFA for cell simulations! Love it!I don’t know the classes you are mentioning (HoldingPippet and injectingPipette), there are not in the public version of SOFA. So it’s hard to help.
Could you share some examples with us of your scene? or repository.
Best,Hugo
HugoKeymasterDear @eunkyungbae,
Simulation of suture or knot tying is currently a topic of research. Several groups are starting to focus on this topic. If you are interested, I could invite you to future discussions about it.
To answer your question: yes to have a realistic knot simulation, you need self-collision.
Could you share an example scene with us so that we can better understand and help you?Best
Hugo
HugoKeymasterDear Sarath,
Great news ! Thank you so much !
I am sure the whole community will be greatful for what you succeeded to do !Best,
Hugo
14 December 2017 at 15:56 in reply to: [SOLVED] How to begin to use sofa for medical simulations? #10228HugoKeymasterDear Luca,
Thank you very much for your interest in SOFA and in physics simulation for medicine.
This is not an easy topic, since simulation mixes numerical methods, math, computational mechanics and computer science. The SOFA consortium proposes SOFA training sessions as a service if you need it.The tutorials in SOFA are indeed basics and need to be (constantly) improved. However, as you can guess, with such a large open-source project, there is plenty of priorities and hot topics to work on. Do not hesitate to have a look at the online documentation. The Get Started should help with some basics.
Best,
Hugo
HugoKeymasterHi Sarah,
I don’t think they have to be built in the same directory. However, you will either need a FindVRPN.cmake file in the repository cmake/ at the root of SOFA (it does not exist, but you can find one here) or specify yourself in the CMake configuration the path to the VRPN libs.
Cheers,
Hugo
HugoKeymasterAgain, I did do it myself, but I am pretty sure you can follow the guidelines from vprn library : https://github.com/vrpn/vrpn/wiki
Cheers,
Hugo
HugoKeymasterHi @sarath,
This is a linking error. Only three possibilities:
– the library project does not exist
– the library is not built
– build configurations do not matchCould you check this (mainly two first points) ?
Hugo
HugoKeymasterHugoKeymasterhi @bgarcial,
Thank you for your interest in SOFA and starting coding to integrate your work!
I would advise to get inspiration from the LeapMotion plugin (instead of Sensable).
Moreover you can find some documentation online on how to create a plugin.
Let us know if it works or if you have some errors, we would help you.Cheers,
Hugo
HugoKeymaster -
AuthorPosts