Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • N ndcurves
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • loco-3d
  • ndcurves
  • Issues
  • #3

Closed
Open
Created Aug 29, 2019 by Pierre Fernbach@pfernbacOwner

Require SO3 curve

In multicontact-api and MLP we use SO3 (and SE3) curves.

SO3 should be initialized with 2 quaternion and a duration and output a quaternion which is the result of the slerp method. Main issue here is that the return dimension is 4 but the return size of the derivative is 3.

SE3 is not really required but would be easier for the user. It is basically the composition of a SO3 and any kind of curve of dimension 3.

I can implement them but I am not sure about the best way to do it (ie what should be their parent class) ? Ideally we should be able to make piecewise SO3/SE3 without changing the code of the piecewise templated class.

Assignee
Assign to
Time tracking