updating build docs and comments
parent
1ea890f4e5
commit
4d4ea69919
|
@ -22,7 +22,7 @@ endif()
|
||||||
# Default to Debug mode
|
# Default to Debug mode
|
||||||
if(NOT FIRST_PASS_DONE)
|
if(NOT FIRST_PASS_DONE)
|
||||||
set(CMAKE_BUILD_TYPE "Debug" CACHE STRING
|
set(CMAKE_BUILD_TYPE "Debug" CACHE STRING
|
||||||
"Choose the type of build, options are: None Debug Release RelWithDebInfo MinSizeRel."
|
"Choose the type of build, options are: Debug Release Timing Profiling RelWithDebInfo."
|
||||||
FORCE)
|
FORCE)
|
||||||
endif()
|
endif()
|
||||||
|
|
||||||
|
|
6
README
6
README
|
@ -158,6 +158,12 @@ $] cmake -DGTSAM_BUILD_CONVENIENCE_LIBRARIES:OPTION=ON ..
|
||||||
link all of the tests at once. This option is best for users of GTSAM,
|
link all of the tests at once. This option is best for users of GTSAM,
|
||||||
as it avoids rebuilding the entirety of gtsam an extra time.
|
as it avoids rebuilding the entirety of gtsam an extra time.
|
||||||
|
|
||||||
|
CMAKE_BUILD_TYPE: We support several build configurations for GTSAM (case insensitive)
|
||||||
|
Debug (default) All error checking options on, no optimization. Use for development.
|
||||||
|
Release Optimizations turned on, no debug symbols.
|
||||||
|
Timing Adds ENABLE_TIMING flag to provide statistics on operation
|
||||||
|
Profiling Standard configuration for use during profiling
|
||||||
|
RelWithDebInfo Same as Release, but with the -g flag for debug symbols
|
||||||
|
|
||||||
|
|
||||||
Build and Install
|
Build and Install
|
||||||
|
|
20
USAGE
20
USAGE
|
@ -21,13 +21,16 @@ Compiling/Linking with gtsam:
|
||||||
the Boost.serialization library, which requires the the Boost.serialization
|
the Boost.serialization library, which requires the the Boost.serialization
|
||||||
headers and binaries to be linked.
|
headers and binaries to be linked.
|
||||||
|
|
||||||
|
If you use CMake for your project, you can use the CMake scripts in the
|
||||||
|
cmake folder for finding GTSAM, CppUnitLite, and Wrap.
|
||||||
|
|
||||||
Examples:
|
Examples:
|
||||||
To see how the library works, examine the unit tests provided.
|
To see how the library works, examine the unit tests provided.
|
||||||
|
|
||||||
|
|
||||||
Overview
|
Overview
|
||||||
---------------------------------------------------
|
---------------------------------------------------
|
||||||
The gtsam library has three primary components necessary for the construction
|
The GTSAM library has three primary components necessary for the construction
|
||||||
of factor graph representation and optimization which users will need to
|
of factor graph representation and optimization which users will need to
|
||||||
adapt to their particular problem.
|
adapt to their particular problem.
|
||||||
|
|
||||||
|
@ -48,19 +51,20 @@ Factors:
|
||||||
VSLAM Example
|
VSLAM Example
|
||||||
---------------------------------------------------
|
---------------------------------------------------
|
||||||
The visual slam example shows a full implementation of a slam system. The example contains
|
The visual slam example shows a full implementation of a slam system. The example contains
|
||||||
derived versions of NonlinearFactor, NonlinearFactorGraph, and a Config, in classes
|
derived versions of NonlinearFactor, NonlinearFactorGraph, in classes visualSLAM::ProjectionFactor,
|
||||||
VSLAMFactor, VSLAMGraph, and VSLAMConfig, respectively.
|
visualSLAM::Graph, respectively. The values for the system are stored in the generic
|
||||||
|
Values structure. For definitions and interface, see gtsam/slam/visualSLAM.h.
|
||||||
|
|
||||||
The clearest example of the use of the graph to find a solution is in
|
The clearest example of the use of the graph to find a solution is in
|
||||||
testVSLAMGraph. The basic process for using graphs is as follows (and can be seen in
|
testVSLAM. The basic process for using graphs is as follows (and can be seen in
|
||||||
the test):
|
the test):
|
||||||
- Create a NonlinearFactorGraph object (VSLAMGraph)
|
- Create a NonlinearFactorGraph object (visualSLAM::Graph)
|
||||||
- Add factors to the graph (note the use of Boost.shared_ptr here) (VSLAMFactor)
|
- Add factors to the graph (note the use of Boost.shared_ptr here) (visualSLAM::ProjectionFactor)
|
||||||
- Create an initial configuration (VSLAMConfig)
|
- Create an initial configuration (Values)
|
||||||
- Create an elimination ordering of variables (this must include all variables)
|
- Create an elimination ordering of variables (this must include all variables)
|
||||||
- Create and initialize a NonlinearOptimizer object (Note that this is a generic
|
- Create and initialize a NonlinearOptimizer object (Note that this is a generic
|
||||||
algorithm that does not need to be derived for a particular problem)
|
algorithm that does not need to be derived for a particular problem)
|
||||||
- Call optimization functions with the optimizer to optimize the graph
|
- Call optimization functions with the optimizer to optimize the graph
|
||||||
- Extract an updated configuration from the optimizer
|
- Extract an updated values from the optimizer
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue