feature/BAD_ChartValue

View source
feature/BAD_ChartValue
  • Contributors
    1. Loading...
Author Commit Message Date Builds
250+ commits behind develop.
Michael Bosse
Merge remote-tracking branch 'origin/feature/BAD_forMike' into feature/BAD_ChartValue Conflicts: gtsam_unstable/nonlinear/tests/testExpression.cpp
Frank Dellaert
Mike, consider this renaming if you want to stress the value aspect. I'm still thinking Values should store naked types (double, Vector3, Pose3) and then algorithms iterate on Values and create whatever Charts are needed.
Michael Bosse
got Expression of chart_origin(ChartValue) working
Michael Bosse
testing expressions of ChartValues TEST(Expression, ChartValue_origin) segfaults :-( but not sure why, yet ...
Michael Bosse
Merge remote-tracking branch 'origin/feature/BAD' into feature/BAD_ChartValue
Michael Bosse
test ChartValue with Point3
Michael Bosse
Merge remote-tracking branch 'origin/feature/BAD' into feature/BAD_ChartValue
Michael Bosse
testing adding Chart to Values works (test fails as it is supposed to)
Michael Bosse
fixed stupid fix
Michael Bosse
Merge remote-tracking branch 'origin/feature/BAD' into feature/BAD_ChartValue Conflicts: gtsam/geometry/tests/testCal3Bundler.cpp
Michael Bosse
simple test of ChartValue
Michael Bosse
initial go at a templated value based on default charts