Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interface for specifying meaning of generalized coordinates of BallJoint and FreeJoint #185

Open
jslee02 opened this issue Apr 29, 2014 · 1 comment

Comments

@jslee02
Copy link
Member

jslee02 commented Apr 29, 2014

The meaning of generalized coordinates of BallJoint and FreeJoint is not clear.

BallJoint has rotation matrix R as configuration. Possible coordinate charts are:

r1 = log(R)
r2 = inverseEuluerXYZ(R)

FreeJoint has transformation matrix T as configuration. Possible coordinate charts are:

(q1, q2) = log(T)
(q1, q2) = (log(R), p)
(q1, q2) = (inverseEulerXYZ(R), p)

So we need member functions for the coordinate charts of BallJoint and FreeJoint.

enum CoordinateChart
{
  CC_EXP,
  CC_EULER_XYZ,
  // ...
  CC_EULER_ZYX
}

BallJoint::setCoordinateChart(CoordinateChart _chart);
CoordinateChart BallJoint::getCoordinateChart() const;
@jslee02 jslee02 added the API label Apr 29, 2014
@jslee02 jslee02 added this to the Release DART 4.0 milestone Apr 29, 2014
@jslee02 jslee02 modified the milestones: Release DART 4.1, Release DART 4.0 May 28, 2014
@jslee02 jslee02 modified the milestones: Release DART 5.0, Release DART 4.0.1 Jul 2, 2014
@jslee02 jslee02 added priority: medium should be resolved before the next release tag: feature request Indicates new feature requests Kind: Task and removed tag: feature request Indicates new feature requests labels Sep 15, 2014
@jslee02 jslee02 modified the milestones: Release DART (15.06), Release DART 4.3 Jan 2, 2015
@jslee02 jslee02 removed the Kind: Task label May 1, 2015
@jslee02 jslee02 removed this from the Release DART 5.0 milestone Jun 11, 2015
@stale
Copy link

stale bot commented Feb 13, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Feb 13, 2018
@stale stale bot removed the stale label Feb 13, 2018
@jslee02 jslee02 removed the priority: medium should be resolved before the next release label Jan 7, 2023
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

No branches or pull requests

1 participant