I've forwarded your model to our development team,
I'll keep you posted when we know the root cause and when it can be fixed
Regards
Daniel
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Thanks again for reporting the issue, the problem has been reproduced in our latest release (5.2), it comes from an incorrect padding management in case of 1D tensors.
It will be fixed in X-Cube-AI 6.0 early next year.
Regards
Daniel
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Your model is correctly supported now with X-CUBE-AI 7.3
Regards
Daniel
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
There is actually a bug in our code, normally fixed in the upcoming X-Cube-AI 7.1.0 early next year
Regards
Daniel
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
This model is supported starting X-CUBE-AI version 7.2
Regards
Daniel
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
I've opened a new bug with your model so we can fix the import asap.
Thanks for reporting the issue
Regards
Daniel
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Sorry for the late answer, this Robot model is correctly supported with X-CUBE-AI 7.3 already out
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
After analysis the problem is likely to come from the usage of nested models.
Maybe you can try to rewrite the same topology with no or less nested levels
Regards
Daniel
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
I finally got back to this. You were right. Once I removed the model nesting, the analysis worked correctly. I am glad I can even use multi-input Keras models.
I checked my model and everything seems okey. My model has 3 inputs (X, Y, Z) and 6 output labels. I had constructed bunch of segments according to dataset. With this error text, which things should I control or change?