Merge branch 'feature/getCovariance' into 'devel'
Removing getCovariance returning MatrixXs In wolf, by default the solver is not computing the whole covariance matrix of the estimation. It has to be called explicitly to the solver defining which blocks are desired to be computed. Then, they are stored in `Problem` in `std::map<std::pair<StateBlockPtr, StateBlockPtr>, Eigen::MatrixXs> covariances_`; Then, eventually when asking for a specific covariance block, this information is not stored. In `Problem`, `LandmarkBase` and `FrameBase`, there are 2 kind of covariance getters: * `MatrixXs getXXXCovariance(const XXXPtr& xxx_ptr)` * `bool getXXXCovariance(const XXXPtr& xxx_ptr, MatrixXs& cov)` The first one, if the covariance block hasn't been computed returns an uninitialized matrix without returning any information about what happened. According to #145, we agreed on removing this first getters for covariance blocks implemented in the current MR. See merge request !263
No related branches found
No related tags found
Showing
- hello_wolf/hello_wolf.cpp 10 additions, 2 deletionshello_wolf/hello_wolf.cpp
- include/base/frame_base.h 0 additions, 1 deletioninclude/base/frame_base.h
- include/base/landmark/landmark_base.h 0 additions, 1 deletioninclude/base/landmark/landmark_base.h
- include/base/problem.h 1 addition, 3 deletionsinclude/base/problem.h
- src/frame_base.cpp 0 additions, 5 deletionssrc/frame_base.cpp
- src/landmark/landmark_base.cpp 0 additions, 5 deletionssrc/landmark/landmark_base.cpp
- src/problem.cpp 23 additions, 28 deletionssrc/problem.cpp
- src/processor/processor_frame_nearest_neighbor_filter.cpp 22 additions, 8 deletionssrc/processor/processor_frame_nearest_neighbor_filter.cpp
- test/gtest_odom_2D.cpp 26 additions, 10 deletionstest/gtest_odom_2D.cpp
- test/gtest_problem.cpp 10 additions, 1 deletiontest/gtest_problem.cpp
Loading
Please register or sign in to comment