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

Inverse kinematics not giving an accurate result at first after a tool is changed #385

Open
EmaKrakovska opened this issue Jun 21, 2023 · 0 comments

Comments

@EmaKrakovska
Copy link

Describe the bug
When a tool is removed and a new tool is added, the inverse kinematics component for the same given plane does not give an accurate result at first computing, but only after the inverse kinematics is computed for another plane at least once.

To Reproduce
Steps to reproduce the behavior:

  1. Context:
    compas_fab version 0.28.0 on Rhino 7, Grasshopper

  2. Sample script:

     tool_frame = Frame(plane.Origin, plane.XAxis, plane.YAxis)
     ik_configuration = robot.inverse_kinematics(tool_frame,
                                                   start_configuration,
                                                   group=group,
                                                   options={
                                                     'avoid_collisions':avoid_collisions,
                                                     'return_full_configuration':True,
                                                   })           
    

Expected behavior
After removing and adding a new tool, the inverse kinematics computation should give a new and accurate result for the same plane.

Screenshots
First computation of inverse kinematics after the tool was changed (probably using a transformation from the previous tool).
inverse_kinematics_1
Second computation of inverse kinematics after the plane was shifted to a new position.
inverse_kinematics_2

Desktop (please complete the following information):

  • Windows 11
  • Python version 3.9.13
  • Python package manager conda
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