This PR will mitigate the danger of issue #33
By calling checkValidity() after creating an handarm_paramter object it is ensured that an exception is thrown in case a copy() was forgotten.
This does not check for a copy paste error in the strategy section, like
If you think this might be useful as well, I can add it to this PR.
IMPORTANT: This PR should not be merged before #34
I based this branch on the wall_grasp_tuning_DEMO branch, which is not merged yet to prevent merge conflicts. Merging this will also merge all the other changes to master.
My suggestion is, to merge #34, tag the state, and then merge this PR into master.
This PR will mitigate the danger of issue #33 By calling
checkValidity()
after creating an handarm_paramter object it is ensured that an exception is thrown in case a copy() was forgotten. This does not check for a copy paste error in the strategy section, likeHowever, the call for
copy()
is checked A way to prevent this and the issue #33 would be to introduce a convenient function like this:which would be called like this
If you think this might be useful as well, I can add it to this PR.
IMPORTANT: This PR should not be merged before #34
I based this branch on the wall_grasp_tuning_DEMO branch, which is not merged yet to prevent merge conflicts. Merging this will also merge all the other changes to master. My suggestion is, to merge #34, tag the state, and then merge this PR into master.