You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Context:
compas_fab version 0.28.0 on Rhino 7, Grasshopper
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).
Second computation of inverse kinematics after the plane was shifted to a new position.
Desktop (please complete the following information):
Windows 11
Python version 3.9.13
Python package manager conda
The text was updated successfully, but these errors were encountered:
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:
Context:
compas_fab version 0.28.0 on Rhino 7, Grasshopper
Sample script:
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).
Second computation of inverse kinematics after the plane was shifted to a new position.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: