You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I built GTSAM-develop with Matlab toolbox in windows (it required applying some patches from feedstock, but the same errors appears when I use their GTSAM 4.2 which they officially support)
when trying to insert a Vector to Values an error will appear when calling the solver (I tried ISAM2).
Exception from gtsam:
Attempting to retrieve value with key "v3", type stored in Values is class gtsam::GenericValue<class
Eigen::Matrix<double,-1,1,0,-1,1> > but requested type was class Eigen::Matrix<double,3,1,0,3,1>
For some reason there is a discrepancy between ValueType and the value type saved.
I found a workaround (suggested in other issues -using inserPoint3 and atPoint3) for both Point3 and Velocities values. But a robust solution would help, at least to know there is no hidden bug in out faulty compilation.
I found similar problems in the past, ie, 1, 2
I saw that a possible reason was the order of overloaded functions, but I couldn't find why it happens here.
Also, I know you don't fix windows issues anymore,
I would appreciate a general direction how to debug it myself.
This bug doesn't appear in Linux
Steps to reproduce
download gtsam-develop
from gtsam feedstock apply those patches: (1)fix-gtsam-export-4.2.0.patch (2)python-win (3) fix-gtsam-unstable-export-4.2.0 (4)fix-python-build-win (required to build 'release' version)
maybe not required, but - manually add to root CMakeList.txt file the equivalent of:
compile with msvp19 with ninja and CMake commands: -DGTSAM_INSTALL_MATLAB_TOOLBOX=ON -DGTSAM_BUILD_PYTHON=ON -DGTSAM_PYTHON_VERSION=3.11.1 -DGTSAM_WITH_TBB=OFF
add install directory to the path
run IMUKITTY example
to get it running properly - when inserting velocity values - replace "insert" with "insertPoint3", when reading velocity values replace "result.atVector" with "atVector.atPoint3"
Expected behavior
Environment
windows 10
matlab 23a
python 3.11.1
Additional information
The text was updated successfully, but these errors were encountered:
Exception from gtsam:
Attempting to retrieve value with key "v3", type stored in Values is class gtsam::GenericValue<class
Eigen::Matrix<double,-1,1,0,-1,1> > but requested type was class Eigen::Matrix<double,3,1,0,3,1>
I have the exact problem when I compile the tests on windows, and fix it on my PR. @etamarlu Can you try my PR if it work for you?
Description
I built GTSAM-develop with Matlab toolbox in windows (it required applying some patches from feedstock, but the same errors appears when I use their GTSAM 4.2 which they officially support)
when trying to insert a Vector to Values an error will appear when calling the solver (I tried ISAM2).
I tracked it down to NonlinearFactor.h.h at lines 707 or 710, when calling
For some reason there is a discrepancy between ValueType and the value type saved.
I found a workaround (suggested in other issues -using inserPoint3 and atPoint3) for both Point3 and Velocities values. But a robust solution would help, at least to know there is no hidden bug in out faulty compilation.
I found similar problems in the past, ie, 1, 2
I saw that a possible reason was the order of overloaded functions, but I couldn't find why it happens here.
Also, I know you don't fix windows issues anymore,
I would appreciate a general direction how to debug it myself.
This bug doesn't appear in Linux
Steps to reproduce
-DGTSAM_INSTALL_MATLAB_TOOLBOX=ON -DGTSAM_BUILD_PYTHON=ON -DGTSAM_PYTHON_VERSION=3.11.1 -DGTSAM_WITH_TBB=OFF
to get it running properly - when inserting velocity values - replace "insert" with "insertPoint3", when reading velocity values replace "result.atVector" with "atVector.atPoint3"
Expected behavior
Environment
Additional information
The text was updated successfully, but these errors were encountered: