Skip to content

Conversation

@efernandez
Copy link
Member

This should be reviewed after merging #33

This adds:

  • Use the control period in the odometry update methods
  • With this, we compute the (internal) incremental pose using the wheel joint velocities instead of the positions, so the user can compute the twist from velocities and the pose from positions
  • Factorizes the tests for covariance and other minor changes on the tests
  • Remove the sophus depend, no longer needed

@afakihcpr @servos

@efernandez efernandez force-pushed the use_control_period_on_twist branch from 8316b97 to 10086d1 Compare February 8, 2016 16:40
@servos
Copy link

servos commented Feb 8, 2016

After testing, this seems to fix the issues we were seeing in CISIM.

@servos
Copy link

servos commented Feb 8, 2016

LGTM

Enrique Fernandez added 4 commits February 8, 2016 14:03
This way we can have position increment (dp) and velocity (v) from the
actual position and velocity, or estimated from velocity and position,
respectively.
@efernandez efernandez force-pushed the use_control_period_on_twist branch from 10086d1 to c5e66a4 Compare February 8, 2016 19:03
@efernandez
Copy link
Member Author

I've simply rebased into indigo-devel (w/o any conflict) after merging #33
Merging this now...

efernandez pushed a commit that referenced this pull request Feb 8, 2016
@efernandez efernandez merged commit a1f3622 into indigo-devel Feb 8, 2016
@efernandez efernandez deleted the use_control_period_on_twist branch February 10, 2016 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants