Zahra

Dear Hugo,
Thank you for your kind explanation. I’m looking forward for the working flipNormals Gmsh loader. Meanwhile I will try to use Obj loader for the representation of Normals.

Best,
Zahra

Dear Hugo,

Setting the option “flipNormals” in MeshLoaders and TetrahedronSetGeometryAlgorithms and TriangleSetGeometryAlgorithms to 1 didn’t change the direction of normals. What do you mean that it depends on the code?

As an example, here is my code and mesh files:
https://gist.github.com/zbounik/c2c78c87de97d7ad0d7b1cc983d72f6d

Thank you for…[Read more]

Nice to hear that your problem is solved, and thanks for your explanation.

Hi @Simon,

Regarding the problem I encountered at that time, I solved it with so much trial and error. This is my final understanding of the process:
When I simply imported numpy in anaconda or in the Terminal without using SOFA, I had no problem. But when I imported SOFA and numpy, there was a conflict between different versions of numpy…[Read more]

Hi @Binesh,

Thank you for willing to help me, jnbrunet’s reply solved the issue.

For your information on what I was trying to do: I wanted to put a marker on a specific node, in order to make it more recognizable among other nodes in the mesh.

Best,
Zahra

Hi @jnbrunet,
Thank you very much for your suggestion, it works.

Best,
Zahra

Hi @bennetcole,

This is very interesting! Thank you.

Zahra

Dear Hugo,

Thank you for your kind invitation on joining SOFA Symposium. I really hope I have the opportunity to attend this professional event.

Regarding oneWay attachConstraint component, I think there is a problem with the definition as “the selected nodes (indices1) of object1 follow the associcated nodes (indices2) in object2.” (I also…[Read more]

Thank you 🙂

Hi @Binesh, Hi @Hugo,

Thank you very much for your explanation.

To make sure, based on what you mentioned if I want Obj2 to simulate independently, and Obj1 to follow it, then I think I should set twoWays=false. Is it true?

Best,
Zahra

Hi,
My problem with importing numpy has been solved. In my case, the problem was that the default python in my system wasn’t the one that SOFA is using. Changing the default python fixed the error.

Best,
Zahra

My problem with importing numpy has solved. In my case, the problem was that the default python in my system wasn’t the one that SOFA is using. Changing the default python removed the error.

Best,
Zahra

Dear @Damien,
Thank you for your explanations on SofaPython3. It looks great!

Best,
Zahra

Hi @Hugo,

I was considering it in Centimeters, thank you for correcting me.

Best,
Zahra

Dear @Hugo,

The object I’m currently working with is a liver. The range of the values of the current mesh file is 8.5*5.1*2.3

Best,
Zahra

Dear @Hugo.

I’m not sure if it is OK to ask my question here, but as it is directly related, I’am asking it here.

In reply to Noura, you have mentioned that “If the file mesh you load has values between 0 and 40, then your file is in mm.” This confused me. So why 40? What if the dimension of the loaded mesh be around 70?

I have another…[Read more]

Dear @Bruno Marques,

Thank you for your kind reply, and sorry for the late reply, my code were running so I couldn’t try your hint and give you the feedback sooner.

I tried your hints, I uninstalled everything, including Anaconda and numpy, until there was no numpy there. I then reinstalled Anaconda, and the problem persists. At least it’s…[Read more]