Bruno Marques

Hi @AlbanOdot ,
*Here’s the short answer:*

how to use writeable():

with self.CFF.forces.writeable() as cff:
cff[:] = linear_forces_amplitude * layer

when should I use which:
in your case self.CFF.forces.value = linear_force_amplitude * Layer is as efficient as the writeable version

*The long answer now:*
Your first…[Read more]

Hi Zahra,

Sofa does not package numpy with its sources, so your problem, while indeed being an issue with concurrent versions of numpy on your system, is not linked to your install of SOFA. (as far as I know)

I’m no expert in this, but I’d guess that:
– you installed numpy either via your package manager (apt install python-numpy) or via pip…[Read more]

Hi and Welcome to Sofa!

Sadly, the runSofa GUI is not meant to allow stepping programmatically.
Luckily, there are some workarounds..:

1. SofaPython3 is a plugin in development. It’s purpose is to provide python packages for SOFA, that will let you define your own simulation loop in python by calling SOFA’s animate / step methods manually from…[Read more]

Hi @Angela_Fifi,

As-is in SOFA, there’s no way of changing the camera’s intrinsic parameters using exisiting components.
There is a plugin, called SofaCV (computer vision) that contains a component called CalibratedCamera, and that can take OpenCV-style camera calibration data in the form of:
– A 3×4 matrix encoding both extrinsic and intrinsic…[Read more]

Hi @Zahra

This is sadly a recurring issue with SOFA:
As of today, a simulation ran in the runSofa GUI can only be stopped or killed programatically (by using node.getRootContext().animate = False or by for instance calling quit() in the script to end the program.
There is no way to get from the “paused” state to the “animate” state of the…[Read more]

Bonjour Gaetan,

SOFA initialise ses composants en plusieurs étapes.
Tout d’abord, le constructeur de la classe est appelé. Les datafields sont initialisées à leurs valeurs par défaut.
Ensuite, la méthode parse() est appelée, et cette méthode va (justement) parser ton fichier de scène XML ou python, ou ton BaseObjectDescription, en fonction…[Read more]

SOFA is more a simulation *Framework* as it is a simulation *Software*.
It’s programming language is C++, but (long ago), to simplify scripting, a system has been set in place to describe scenes with XML, and it’s been the main way to create SOFA scenes for a long time.
It’s now much more recommended to create scenes in Python. A Python plugin,…[Read more]

Hi @huntsmanydw,
I personally never used the SOFA modeler so I’m probably not the best suited to answer your question.. But be aware that the modeler, while being present in SOFA’s repository, is not much maintained anymore. While we still apply bugfixes to it, we very rarely add new features to it.
I don’t believe any of the two features you are…[Read more]

Hi @Tim,
That’s a good question. To my knowledge there’s no such mechanism.
I looked it up a little bit and it seems that the way the animation works in runSofa is that clicking on the animate button:
– triggers the loop that will call the RealGUI::step() method.
– This method calls the Simulation::animate() method that triggers the execution of 1…[Read more]

Sorry, I replied a bit too fast the first time:
The results you’re getting means it works:

What your code is doing is catching every AnimateEndEvent signals, and stopping the simulation each time.
The AnimateEndEvent’s name is misleading, I admit: it should actually be called “SimulationStepEndEvent”. This signal is sent at the end of each time…[Read more]

Hi @himanshu,
I’m not a user of windows 10.. but it seems to me that you’re building SOFA without PLUGIN_SOFAPYTHON.

– Have you built SOFA by yourself (from sources) or did you download the binaries?
If you built it yourself, you need to enable the SofaPython plugin in your cmake configuration (PLUGIN_SOFAPYTHON=ON)

– Are you building the…[Read more]

@rubab123 Your mistake I suppose is that you declared an event pointer in your class declaration.
The prototype of the handleEvent function tells you that it takes a sofa::core::objectmodel::Event pointer as an argument, so that’s the one you have to work with. if you declare an Event* in your class, this one will of course be uninitialized hence…[Read more]

@rubab123, after reading your last post on the other topic you opened, I’m quite confident that my initial reply answers your problem:

What you want, if I understood correctly, is to wait for a user to execute a simulation in SOFA that would gather some data on the user’s inputs (accuracy, speed…), and, once the simulation is performed, stop…[Read more]

Hi @rubab123,

I’m not sure if I understood correctly, but if what you want is stop / pause the simulation from within a component, you can do this by calling setAnimate(false) on the root context:
this->getContext()->getRootContext()->setAnimate(false);

You can also do this from PythonScriptControllers, if that’s more convenient to…[Read more]

Hi @nicklj,

Could you tell us more about your build setting?

– Which OS are you on?
– Did you manually activate / deactivate any option in cmake besides PLUGIN_SOFAPYTHON, SOFA_BUILD_METIS?
– Could you dump the whole output of runSofa on the problematic scene?

Hi Zahra,

You might want to look at the “Tetra2TriangleTopologicalMapping” component.
You can find an example in the scene “examples/Components/topology/Tetra2TriangleTopologicalMapping.scn”

Alright!

We ended up finding what was missing.
Whiile my new class type was well declared, it wasn’t registered to the PythonFactory, which handles the lookup of typenames to find out if the BaseData* object provided could be downcasted.

In order to get the new type registered, a call to SP_ADD_CLASS_IN_FACTORY(cvMatData,…[Read more]

Hi Lionel,

Thanks for your input!
I did that too. There are bindings for AssembledSystem in the compliant plugin, that is slightly different (it has a constructor and destructor, which uses a different SP_* macro.
But fundamentally, the implementation is the same:

1. a SP_DECLARE_TYPE(MyPythonType)
2. multiple static methods for python with the…[Read more]