Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • N ndcurves
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • 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
  • #19
Closed
Open
Issue created Nov 06, 2019 by Guilhem Saurel@gsaurelOwner

Consistency in polynomial init / eval types

Hi,

If I create a polynomial, I have to give it an init point and an end point as pointX_ts: https://gepgitlab.laas.fr/loco-3d/curves/blob/devel/python/curves_python.cpp#L151

Then, if I evaluate it, I get a point_t: https://gepgitlab.laas.fr/loco-3d/curves/blob/devel/include/curves/polynomial.h#L242

So in this test, we are basically checking that a pointX_t object is equal to a point_t object: https://gepgitlab.laas.fr/loco-3d/curves/blob/devel/python/test/test.py#L248

This can work for X = 3, but shouldn't it always work ?

Assignee
Assign to
Time tracking