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

Check JointAxis expressed-in values during Load #1195

Merged
merged 4 commits into from
Nov 16, 2022

Conversation

scpeters
Copy link
Member

@scpeters scpeters commented Nov 5, 2022

🎉 New feature

Related to #1166

Summary

In axis and axis2 elements, if the //xyz/@expressed_in attribute is not empty, then it must contain the name of a frame in the current scope. The parser does not currently check the validity of //xyz/@expressed_in values, as evidenced by the test failure added in 078b042. A checking function checkJointAxisExpressedInValues is added to the parser in 6ee6413, along with a new error type JOINT_AXIS_EXPRESSED_IN_INVALID.

Test it

Run the INTEGRATION_joint_axis_dom test with each commit from this branch.

Checklist

  • Signed all commits for DCO
  • Added tests
  • Added example and/or tutorial
  • Updated documentation (as needed)
  • Updated migration guide (as needed)
  • Consider updating Python bindings (if the library has them)
  • codecheck passed (See contributing)
  • All tests passed (See test coverage)
  • While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Signed-off-by: Steve Peters <scpeters@openrobotics.org>
Currently the //axis*/xyz/@expressed_in values are
not checked that they refer to valid frames. This
adds a check in Root::Load just after checking
that the Joint parent and child names are valid.
The JOINT_AXIS_EXPRESSED_IN_INVALID Error type is
added and used when checking //xyz/@expressed_in.

Signed-off-by: Steve Peters <scpeters@openrobotics.org>
@scpeters scpeters requested a review from azeey as a code owner November 5, 2022 06:20
@github-actions github-actions bot added the 🌱 garden Ignition Garden label Nov 5, 2022
@codecov
Copy link

codecov bot commented Nov 5, 2022

Codecov Report

Merging #1195 (6ee6413) into sdf13 (74fe572) will decrease coverage by 0.22%.
The diff coverage is 100.00%.

❗ Current head 6ee6413 differs from pull request most recent head 5e709ff. Consider uploading reports for the commit 5e709ff to get more accurate results

@@            Coverage Diff             @@
##            sdf13    #1195      +/-   ##
==========================================
- Coverage   87.50%   87.28%   -0.23%     
==========================================
  Files         124      125       +1     
  Lines       16096    16150      +54     
==========================================
+ Hits        14085    14096      +11     
- Misses       2011     2054      +43     
Impacted Files Coverage Δ
src/Root.cc 95.21% <100.00%> (+0.02%) ⬆️
src/parser.cc 87.44% <100.00%> (+0.29%) ⬆️
src/SDFExtension.cc 49.43% <0.00%> (-50.57%) ⬇️
src/Camera.cc 89.03% <0.00%> (-0.26%) ⬇️
src/parser_urdf.cc 87.79% <0.00%> (-0.02%) ⬇️
src/SDFExtension.hh 100.00% <0.00%> (ø)
python/src/sdf/pyCamera.cc 57.01% <0.00%> (+0.12%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

test/sdf/joint_axis_invalid_expressed_in.sdf Outdated Show resolved Hide resolved
@scpeters scpeters merged commit 438e05b into sdf13 Nov 16, 2022
@scpeters scpeters deleted the scpeters/check_axis_expressed_in branch November 16, 2022 23:55
@ahcorde ahcorde mentioned this pull request May 12, 2023
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌱 garden Ignition Garden
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants