[Hugo]

Hi @secretdevil,

I repost your screenshot (it isn’t appearing properly)

If nothing appears in the new Window (you have the SOFA backgrounds, meaning you call DrawLogo()), it means the call of the function draw(), drawScene(), DisplayOBJs() is not done. Make sure you are calling it within your new OpenGL draw loop. Finally, everything is done properly, this could also be an issue of camera.

Cheers,

Hugo

[Hugo]

Hi Cece and Michel,

Since you succeeded in compiling SOFA on Windows, let us know if you still have this toolbar issue.

Cheers,

Hugo

[Hugo]

Hi Cece and Michel,

Since you succeeded in compiling SOFA on Windows, do not hesitate to let us know about your question concerning CarvingManager & OmniSOFA.

Cheers,

Hugo

[Hugo]

Dear Zahra,

At my best knowledge, such a component is not existing in SOFA. But there is an explanation. The notion of steady state can vary from a simulation to another: in some cases the velocity of the DOFs is the criterion, but in some other cases, another field might be more meaningful (evolution of volume, error estimation, etc.). Some people wrote their own components or use Python to script this.

Let us know if you need help in developing it.

Cheers,

Hugo

[Hugo]

Dear @zahra,

It’s now working for me. I had to activate the XML format to make it work. Here is how it looks like:

<VTKExporter name="vTKExporter" pointsDataFields="MechObj.force" filename="test" XMLformat="1" edges="0" triangles="0" exportEveryNumberOfSteps="0" exportAtBegin="1" exportAtEnd="1" />

Let me know if this works for you too.

Cheers,

Hugo

[Hugo]

Dear Michel,

As we mentioned in your other thread, the Online Documentation regarding the compilation has been updated, and its structure has been homogenized.

Cheers,

Hugo

[Hugo]

Hi Zahra,

You can send me your scene if you want me to test it.
(if it doesn’t require a specific plugin)

Cheers,

Hugo

[Hugo]

Hi Weng,

Perfect, let us know about your achievements in SOFA!
Cheers,

Hugo

[Hugo]

Ok, one more thing: you’re saying “my windows will be show but no context sharing with mainwindow of sofa”. Did you already implement it and test it? do you have any screenshot? If nothing is appearing you might need to call the draw function in your widget.

Cheers,

Hugo

[Hugo]

Dear Juan Jo,

You understood perfectly the way the addForce and addDForce are working. By default, SOFA indeed proposes only the Rayleigh model (\alpha*M + \beta*K). However, you can implement a custom damping using the addForce and addDForce as it is done in DiagonalVelocityDampingForceField.inl.

The addDForce is used to the implicit term (which accumulates in the Left Hand Side) related to the force derivative. The addDForce is only called if the matrix A (of the linear system Ax=b) is not assembled, i.e. addDForce is only called for iterative linear solvers (e.g. CGLinearSolver). If you use a direct solver (e.g. LU, LDL etc.), the function addKToMatrix will be used instead. Therefore, this does not depend on the integration scheme (Euler or other).

In the integration, as you mentioned, the MechanicalMatrix appears. This is an implicit way of describing how the matrix A of the linear system (Ax=b) will be computed. Behind this, visitors are sent to go through the right functions. If the solver is iterative: addDForce, addMBKv functions are called. If the solver is direct: addKtoMatrix, addBToMatrix are called.

The matrix B is added into the one matrix A (of the linear system Ax=b). Either B is not assembled (iterative solver) and a visitor launches the addMBKv function or B is assembled (direct solver) and a visitor launches the addBToMatrix function.

About the constraints, I am no expert. In SOFA you can use either an approach based on Lagrange multipliers or on penalty. Those are two different approaches:

• Lagrange: this is splitting the computation into several steps: solve the free motion, compute the constraints only on the considered DOFs (not the entire system) and then applying the constraint. This constraint uses a FreeAnimationLoop, a ConstraintSolver and your Constraint. This is suitable if you have few constraints compared to the number of DOFs of your objects. One example is the examples/Components/constraint/BilateralInteractionConstraint.scn
• Penalty method: this constraints couples the objects. If you define this constraint between two objects, the system solved includes the two objects and the constraints. This is therefore suitable if you have objects with few DOFs (i.e. the constrained system remains reasonably small). You can find a simple example : examples/Tutorials/Collision/MultipleObjectsTwoCubes.scn.

In your case, I would maybe use the Lagrange approach (Bileteral between my objects) and add a PlaneForceField “simulating” a floor (examples/Components/forcefield/PlaneForceField.scn).

Last, yes the Modeler still includes some bugs that have been reported. The improvement of this Modeler is one of the tasks to do in the future in order to make the introduction to SOFA easier.

Hope this helps. Next time, do not hesitate to open one thread per “topic”. But this is really nice to see people with a high-level of understanding in SOFA as you have.

Best regards,

Hugo

[Hugo]

Dear @bushra,

I asked the developers of SOFA about this plugin. It seems it hasn’t been used for some time. In our team, no one is using Xitact anymore. Could you tell us more about the error message you have (at crash), so that we can try to help?

Best regards,

Hugo

[Hugo]

Dear Binesh,

It is really unclear what you expect to do. Could you please reformulate your problem/question (and if necessary create a separate topic) and give us some context?

Best,

Hugo

[Hugo]

Dear Michel,

First, it’s hard to debug it without the full tracing of the error (from where the error is exactly generated: which line of which file).

Moreover, this is a quite astonishing error, especially since it’s related on Eigen. Did you follow step by step the documentation ? (we updated two days ago, after your report)

Best regards,

Hugo

[Hugo]

Perfect, you are very welcome Weng.

Best,

Hugo

[Hugo]

Dear Weng,

Did you check the following topic ? I think this was very close to your question. Does this help?

Best regards,

Hugo

[Hugo]

Dear Michel,

As mentioned by Guillaume in your other topic, improving the documentation is one of the wide tasks of the Consortium. However, any help and support of the community (feedback) is always appreciated.

About Qt, you can use both Qt4 or Qt5. Both are currently supported.

The Consortium just started two months ago, and we do our best to bring a cross-platform support. Unfortunately, only few developers in the SOFA community are working with Windows, which explains this “incomplete support for the MS Windows community”. In case you need a specific support for Windows, do not hesitate to subscribe a support service to the Consortium. We would be delighted to assist you closely.

Best regards,

Hugo

[Hugo]

Dear Zahra,

The data “PointsDataFields” is a string. Therefore, the “@” should not be used. Try without the “@” before the data: use only PointsDataFields=”MechObj.force”, this should work.

Cheers,

Hugo

[Hugo]

Dear Ash,

First, thank you for your interest in SOFA. However, please, do not multi-post a same topic (here about Sensable plugin). In case you need a quick reply, do not hesitate to subscribe to a membership with support. You can read more about the Consortium and its offer here.

About your compilation issue with the Sensable plugin, we are currently looking at it. We’ll let you know ASAP.

Unfortunately, we are not providing a separate binary version of SOFA for each plugin, this would require a huge amount of work. Again, the Consortium could provide such a service. Let us know if you need more information.

Best regards,

Hugo

[Hugo]

Dear Ash,

We close this discussion since another of your threads covers this topic.

Cheers,

Hugo

[Hugo]

Dear @binweng and dear @kipp,

A plugin LeapMotion has just been added in the SOFA project (in the v15.12 and the master branches)! You can find it in applications/plugins/LeapMotion. A README should help you in building this plugin. Please, let us know if you face any complications in compiling or using it.

Kipp, I am going to submit an article on the Leap Motion website as you suggested.

Best regards,

Hugo

[Hugo]

Yes of course Kip.

We’ll keep your upated. We are currently recompiling the LeapMotion plugin, so it shouldn’t take too long.

Cheers,

[Hugo]

Hi Weng,

You can indeed use the keyboard/mouse to interact with your simulation. Two possibilities:

• either you implement everything in C++. Based on the events in SOFA, you can detect when you press or release a key, press or release the mouse. To know hot to do it, please refer to the documentation.
• or you can use python. This way, you can interactively add new nodes, new components on events.

Let mw know if this isn’t clear or if you need some examples of these.
Cheers,

Hugo

[Hugo]

Dear Weng,

About a year ago, some people in our team in Strasbourg worked using the Leap. We therefore have a code for this. I will contact the researchers and see how to make it available.

Cheers,

Hugo

[Hugo]

Dear Ash,

By default in SOFA-v15.12, miniboost currently prevents from installing boost. However, if you activated a specific plugin requiring boost_thread, miniboost is not sufficient anymore. You will have to install boost on your system.

Did you activate any other plugin?

Cheers,

Hugo

[Hugo]

Dear Michel,

This is really a Qt issue.
How did you get Qt5 ? did you download the Qt binaries or did you compile Qt5 yourself ?
Something might have gone wrong in the process.

Cheers,

Hugo

[Author]

Posts