Component data differs between Python and GUI

[adkoessler]

Hello all (and hello @hugtalbot who asked me to tag him :)

I am encountering a problem when trying to read some data values of custom components. It looks to be the same problem as in this topic, but the original poster gave no answer if he found a fix or not.
Version of SOFA: v22.06.99
Version of SofaPython3: v20.12.00

In the script, I have a controller who just prints some values data: "objectiveValue" with type vector<d> and "invJacobian" with type vector<vector<d>>

def objectiveValue(self):
    print("\nObjective value information")
    vv = self.root.Objective0.PositionObjective.objectiveValue.value
    print(vv.shape)
    print(str(vv))
    return 0

def inverseJacobian(self):
    print("Inverse Jacobian information")
    if self.time>self.root.dt.value:
	vj = self.root.animation.invJacobian.value
	print(vj.shape)
	print(str(vj))
    return 0

I compared values outputted by python with values from the GUI. For "objectiveValue" there is no problem, but for "invJacobian" I have:

The shape of the array is fine, some of the terms are passed to python (for instance highlighted number in shell corresponds to last value in GUI). But the result is not ok. The obvious good result is the one of the GUI btw.

Any input on this problem is appreciated.

[hugtalbot]

hey @adkoessler

when are you accessing the data invJacobian?
I would guess that this data is clear at each time step but here, I have no idea what is the nature of your component "root.animation". Therefore it is hard to determine what occurs here.

[adkoessler]

Hi @hugtalbot

The component is a custom one from a library built by some colleagues.
The functions for displaying values are called in the onAnimateBeginEvent() method of the controller.

[hugtalbot]

indeed : onAnimateEndEvent()

[adkoessler]

@hugtalbot Thanks, I tried it but the problem is still there.
I think it's telling that some values with the array are correctly reported. My understanding is that an array that's not initialized would be filled with random values or zeros. This isn't the case here, since some of the values make sense.

[adkoessler]

I realize this can be unclear, so I called inkscape to the rescue :)

[adkoessler]

Hi!

An update regarding the remark "have you checked whether the invJacobian data is cleared anytime in the C++ code within the time step?"
I had the code shown to me and I can confirm that the data is never cleared in between time steps.

[hugtalbot]

Hi @adkoessler

I really can not solve the issue with so few information, I am sorry about this.
Did you discuss this with Paul? I could try to discuss with him.

[adkoessler]

Hi @hugtalbot

Right now I have found a way to circumvent the problem: data is switched to vector<d> and I perform the reshaping into a matrix on my own.
Indeed, I think you could assess the problem in a better way by discussing with Paul.

[hugtalbot]

thanks for the update @adkoessler
would you mind trying to reproduce the same bug with some usual SOFA code? we would take the problem from here and make sure that data vector<vector<d>> can be accessed in python

[github-actions[bot]]

⚠️ ⚠️ ⚠️
@adkoessler
We are setting a new forum management policy: topics like this one, in which the last reply is more than 4 months old, will automatically be closed. Without further news in the coming weeks, our bot will proceed to automatic closure, thus keeping this forum clean and fresh 🌱 Thank you for your understanding

[github-actions[bot]]

⚠️ ⚠️ ⚠️
@adkoessler
In accordance with our forum management policy, the last reply is more than 4 months old and is therefore closed. Our objective is to keep the forum up to date and offer the best support experience.

Please feel free to reopen it if the topic is still active by providing us with an update. Please feel free to open a new thread at any time - we'll be happy to help where and when we can.

[github-actions[bot]]

⚠️ ⚠️ ⚠️
@adkoessler
In accordance with our forum management policy, the last reply is more than 4 months old and is therefore closed. Our objective is to keep the forum up to date and offer the best support experience.

Please feel free to reopen it if the topic is still active by providing us with an update. Please feel free to open a new thread at any time - we'll be happy to help where and when we can.