No more manual tcf-to-t0cf (and viceversa) conversions. Now if there's a tool attached in the planning group, it will use its frame for the planning request (IK, FK, cartesian and kinematic planning).
Although the change does not break the API itself, the default behavior is a breaking change, but one I would propose we just accept and mark it with semver.
[x] Breaking change: bug fix or new feature that involve incompatible API changes.
[ ] Other (e.g. doc update, configuration, etc)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
[x] I added a line to the CHANGELOG.rst file in the Unreleased section under the most fitting heading (e.g. Added, Changed, Removed).
[ ] I ran all tests on my computer and it's all green (i.e. invoke test).
[x] I ran lint on my computer and there are no errors (i.e. invoke lint).
[ ] I added new functions/classes and made them available on a second-level import, e.g. compas_fab.robots.CollisionMesh.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added necessary documentation (if appropriate)
No more manual tcf-to-t0cf (and viceversa) conversions. Now if there's a tool attached in the planning group, it will use its frame for the planning request (IK, FK, cartesian and kinematic planning).
Although the change does not break the API itself, the default behavior is a breaking change, but one I would propose we just accept and mark it with semver.
Re. https://forum.compas-framework.org/t/planning-with-tcf-after-attaching-a-tool-ros-backend/581
What type of change is this?
Checklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.CHANGELOG.rstfile in theUnreleasedsection under the most fitting heading (e.g.Added,Changed,Removed).invoke test).invoke lint).compas_fab.robots.CollisionMesh.