Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
laser
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
mobile_robotics
wolf_projects
wolf_lib
plugins
laser
Commits
9478d9dd
Commit
9478d9dd
authored
9 years ago
by
Joan Solà Ortega
Browse files
Options
Downloads
Patches
Plain Diff
Documentation
parent
fd1b51f6
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/doxygen.conf
+1
-1
1 addition, 1 deletion
doc/doxygen.conf
src/processor_motion.h
+10
-8
10 additions, 8 deletions
src/processor_motion.h
with
11 additions
and
9 deletions
doc/doxygen.conf
+
1
−
1
View file @
9478d9dd
...
...
@@ -291,7 +291,7 @@ EXTENSION_MAPPING =
# case of backward compatibilities issues.
# The default value is: YES.
MARKDOWN_SUPPORT
=
NO
MARKDOWN_SUPPORT
=
YES
# When enabled doxygen tries to link words that correspond to documented
# classes, or namespaces to their corresponding documentation. Such a link can
...
...
This diff is collapsed.
Click to expand it.
src/processor_motion.h
+
10
−
8
View file @
9478d9dd
...
...
@@ -38,7 +38,6 @@ namespace wolf {
* delta_R = fromSensorFrame(delta_S) : this transforms delta_S from frame S to frame R.
* - The two operations are performed by the pure virtual method data2delta(). A possible implementation
* of data2delta() could be (we use the data member delta_ as the return value):
*
* \code
* void data2delta(const VectorXs _data)
* {
...
...
@@ -47,22 +46,25 @@ namespace wolf {
* delta_ = delta_R;
* }
* \endcode
*
* where format() is any code you need to format the data into a delta form,
* and fromSensorFrame() is explained below.
*
* Only when the motion delta is expressed in the robot frame R, we can integrate it
* on top of the current Robot frame: R <-- R (+) delta_R
*
* <code> xPlusDelta(R_old, delta_R, R_new) </code>
* \code xPlusDelta(R_old, delta_R, R_new) \endcode
*
*
* Defining (or not) fromSensorFrame():
*
* In most cases, one will be interested in avoiding the fromSensorFrame() issue.
* ### Defining (or not) the fromSensorFrame():
*
* In most cases, one will be interested in avoiding the \b fromSensorFrame() issue.
* This can be trivially done by defining the Robot frame precisely at the Sensor frame,
* so that S is the identity. In this case, fromSensorFrame() does nothing and delta_R = delta_S.
* This class does not declare any prototype for fromSensorFrame().
* In cases where this identification is not possible, or not desired,
* so that S is the identity. In this case, \b fromSensorFrame() does nothing and delta_R = delta_S.
*
* Notes:
* - This class does not declare any prototype for \b fromSensorFrame().
* - In cases where this identification is not possible, or not desired,
* classes deriving from this class will have to implement fromSensorFrame(),
* and call it within data2delta(), or write the frame transformation code directly in data2delta().
*/
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment