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

Improve test coverage #6

Conversation

christophfroehlich
Copy link

Improve test coverage and some error string formatting for ros-controls#1472

@saikishor
Copy link

@christophfroehlich Thank you for adding tests for this case :). Appreciate it

@saikishor saikishor merged commit 0784152 into pal-robotics-forks:parse_limits_from_urdf_to_hw_info Apr 22, 2024
@christophfroehlich christophfroehlich deleted the parse_limits_from_urdf_to_hw_info branch April 22, 2024 22:19
saikishor pushed a commit that referenced this pull request May 6, 2024
…r) (#6)

* Merge error handling possilibity on read and write.

* Ros2 control extensions rolling joint limits plugins (#5)

* Added initial structures for joint-limit plugins.

* Move Ruckig limiter to package joint_limits_enforcement_plugins and make it working.

Co-authored-by: AndyZe <zelenak@picknik.ai>

* Add option to automatically update parameters after getting them from parameter server.

* Modify simple joint limiting plugin (same as changes to moveit2 filter)

* Add backward_ros dependency for crash stack trace

* Check for required inputs in simple joint limiter

* Change services history QOS to 'keep all' so client req are not dropped

* Add missing on 'pluginlib' dependency explicitly.

* Update ControllerParameters structure to support custom prefix and use in filters.

* Update messge.

* Change controller param changed msg log level to info instead of error

---------

Co-authored-by: Denis Štogl <destogl@users.noreply.github.com>
Co-authored-by: AndyZe <zelenak@picknik.ai>
Co-authored-by: bijoua <bijou.abraham@technipfmc.com>
Co-authored-by: bijoua29 <73511637+bijoua29@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants