2009-11-24 23:12:59 +08:00
|
|
|
/*
|
2010-01-16 09:16:59 +08:00
|
|
|
* @file testConfig.cpp
|
2009-11-24 23:12:59 +08:00
|
|
|
* @brief Tests for the Visual SLAM configuration class
|
|
|
|
|
* @author Alex Cunningham
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include <CppUnitLite/TestHarness.h>
|
2010-01-18 03:34:57 +08:00
|
|
|
|
|
|
|
|
#define GTSAM_MAGIC_KEY
|
|
|
|
|
|
Large gtsam refactoring
To support faster development *and* better performance Richard and I pushed through a large refactoring of NonlinearFactors.
The following are the biggest changes:
1) NonLinearFactor1 and NonLinearFactor2 are now templated on Config, Key type, and X type, where X is the argument to the measurement function.
2) The measurement itself is no longer kept in the nonlinear factor. Instead, a derived class (see testVSLAMFactor, testNonlinearEquality, testPose3Factor etc...) has to implement a function to compute the errors, "evaluateErrors". Instead of (h(x)-z), it needs to return (z-h(x)), so Ax-b is an approximation of the error. IMPORTANT: evaluateErrors needs - if asked - *combine* the calculation of the function value h(x) and the derivatives dh(x)/dx. This was a major performance issue. To do this, boost::optional<Matrix&> arguments are provided, and tin EvaluateErrors you just says something like
if (H) *H = Matrix_(3,6,....);
3) We are no longer using int or strings for nonlinear factors. Instead, the preferred key type is now Symbol, defined in Key.h. This is both fast and cool: you can construct it from an int, and cast it to a strong. It also does type checking: a Symbol<Pose3,'x'> will not match a Symbol<Pose2,'x'>
4) minor: take a look at LieConfig.h: it help you avoid writing a lot of code bu automatically creating configs for a certain type. See e.g. Pose3Config.h. A "double" LieConfig is on the way - Thanks Richard and Manohar !
2010-01-14 06:25:03 +08:00
|
|
|
#include "VectorConfig.h"
|
2010-01-16 09:16:59 +08:00
|
|
|
#include "visualSLAM.h"
|
2009-11-24 23:12:59 +08:00
|
|
|
|
|
|
|
|
using namespace std;
|
|
|
|
|
using namespace gtsam;
|
2010-01-16 09:16:59 +08:00
|
|
|
using namespace gtsam::visualSLAM;
|
2009-11-24 23:12:59 +08:00
|
|
|
|
|
|
|
|
/* ************************************************************************* */
|
2010-01-16 09:16:59 +08:00
|
|
|
TEST( Config, update_with_large_delta) {
|
2009-11-24 23:12:59 +08:00
|
|
|
// this test ensures that if the update for delta is larger than
|
|
|
|
|
// the size of the config, it only updates existing variables
|
2010-01-16 09:16:59 +08:00
|
|
|
Config init;
|
2010-01-14 10:58:29 +08:00
|
|
|
init.insert(1, Pose3());
|
|
|
|
|
init.insert(1, Point3(1.0, 2.0, 3.0));
|
2009-11-24 23:12:59 +08:00
|
|
|
|
2010-01-16 09:16:59 +08:00
|
|
|
Config expected;
|
2010-01-14 10:58:29 +08:00
|
|
|
expected.insert(1, Pose3(Rot3(), Point3(0.1, 0.1, 0.1)));
|
|
|
|
|
expected.insert(1, Point3(1.1, 2.1, 3.1));
|
Large gtsam refactoring
To support faster development *and* better performance Richard and I pushed through a large refactoring of NonlinearFactors.
The following are the biggest changes:
1) NonLinearFactor1 and NonLinearFactor2 are now templated on Config, Key type, and X type, where X is the argument to the measurement function.
2) The measurement itself is no longer kept in the nonlinear factor. Instead, a derived class (see testVSLAMFactor, testNonlinearEquality, testPose3Factor etc...) has to implement a function to compute the errors, "evaluateErrors". Instead of (h(x)-z), it needs to return (z-h(x)), so Ax-b is an approximation of the error. IMPORTANT: evaluateErrors needs - if asked - *combine* the calculation of the function value h(x) and the derivatives dh(x)/dx. This was a major performance issue. To do this, boost::optional<Matrix&> arguments are provided, and tin EvaluateErrors you just says something like
if (H) *H = Matrix_(3,6,....);
3) We are no longer using int or strings for nonlinear factors. Instead, the preferred key type is now Symbol, defined in Key.h. This is both fast and cool: you can construct it from an int, and cast it to a strong. It also does type checking: a Symbol<Pose3,'x'> will not match a Symbol<Pose2,'x'>
4) minor: take a look at LieConfig.h: it help you avoid writing a lot of code bu automatically creating configs for a certain type. See e.g. Pose3Config.h. A "double" LieConfig is on the way - Thanks Richard and Manohar !
2010-01-14 06:25:03 +08:00
|
|
|
|
2009-11-24 23:12:59 +08:00
|
|
|
VectorConfig delta;
|
|
|
|
|
delta.insert("x1", Vector_(6, 0.0, 0.0, 0.0, 0.1, 0.1, 0.1));
|
|
|
|
|
delta.insert("l1", Vector_(3, 0.1, 0.1, 0.1));
|
|
|
|
|
delta.insert("x2", Vector_(6, 0.0, 0.0, 0.0, 100.1, 4.1, 9.1));
|
2010-01-16 09:16:59 +08:00
|
|
|
Config actual = expmap(init, delta);
|
2009-11-24 23:12:59 +08:00
|
|
|
|
Large gtsam refactoring
To support faster development *and* better performance Richard and I pushed through a large refactoring of NonlinearFactors.
The following are the biggest changes:
1) NonLinearFactor1 and NonLinearFactor2 are now templated on Config, Key type, and X type, where X is the argument to the measurement function.
2) The measurement itself is no longer kept in the nonlinear factor. Instead, a derived class (see testVSLAMFactor, testNonlinearEquality, testPose3Factor etc...) has to implement a function to compute the errors, "evaluateErrors". Instead of (h(x)-z), it needs to return (z-h(x)), so Ax-b is an approximation of the error. IMPORTANT: evaluateErrors needs - if asked - *combine* the calculation of the function value h(x) and the derivatives dh(x)/dx. This was a major performance issue. To do this, boost::optional<Matrix&> arguments are provided, and tin EvaluateErrors you just says something like
if (H) *H = Matrix_(3,6,....);
3) We are no longer using int or strings for nonlinear factors. Instead, the preferred key type is now Symbol, defined in Key.h. This is both fast and cool: you can construct it from an int, and cast it to a strong. It also does type checking: a Symbol<Pose3,'x'> will not match a Symbol<Pose2,'x'>
4) minor: take a look at LieConfig.h: it help you avoid writing a lot of code bu automatically creating configs for a certain type. See e.g. Pose3Config.h. A "double" LieConfig is on the way - Thanks Richard and Manohar !
2010-01-14 06:25:03 +08:00
|
|
|
CHECK(assert_equal(expected,actual));
|
2009-11-24 23:12:59 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* ************************************************************************* */
|
|
|
|
|
int main() { TestResult tr; return TestRegistry::runAllTests(tr); }
|
|
|
|
|
/* ************************************************************************* */
|
