Skip to content

[JTC] Rename open_loop_control parameter and slightly change its scope#1525

Merged
christophfroehlich merged 15 commits intoros-controls:masterfrom
Thieso:open_loop_control_param
Mar 7, 2025
Merged

[JTC] Rename open_loop_control parameter and slightly change its scope#1525
christophfroehlich merged 15 commits intoros-controls:masterfrom
Thieso:open_loop_control_param

Conversation

@Thieso
Copy link
Contributor

@Thieso Thieso commented Feb 4, 2025

Resolves #1505

@Thieso Thieso changed the title [JTC]#1505 [JTC] Rename open_loop_control parameter and slightly change its scope #1505 Feb 4, 2025
Copy link
Member

@christophfroehlich christophfroehlich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your PR. However, we must not change the default behavior of existing setups. Your change would go into the stable jazzy release as well.

  1. please keep the old open_loop parameter and add a deprecation warning if it is set to the non-default value (true)
  2. if open_loop is set to true, we still should deactivate the use_closed_loop_pid_adapter_ and override the setting of interpolate_from_desired_state
  3. Mark deprecated code clearly, so we can remove that in the release after next.
  4. Please add a migration note and release note here.

@christophfroehlich christophfroehlich changed the title [JTC] Rename open_loop_control parameter and slightly change its scope #1505 [JTC] Rename open_loop_control parameter and slightly change its scope Feb 4, 2025
Thieso and others added 3 commits February 7, 2025 23:03
…rameters.yaml

Co-authored-by: Christoph Fröhlich <christophfroehlich@users.noreply.github.com>
Co-authored-by: Christoph Fröhlich <christophfroehlich@users.noreply.github.com>
@Thieso
Copy link
Contributor Author

Thieso commented Feb 7, 2025

Thanks for the comments. This should be better now.

Copy link
Member

@christophfroehlich christophfroehlich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the follow-up, but please use pre-commit the next time (fixed that for you).

@codecov
Copy link

codecov bot commented Feb 11, 2025

Codecov Report

Attention: Patch coverage is 66.66667% with 3 lines in your changes missing coverage. Please review.

Project coverage is 84.72%. Comparing base (fc56126) to head (eac66d6).
Report is 9 commits behind head on master.

Files with missing lines Patch % Lines
...ory_controller/src/joint_trajectory_controller.cpp 0.00% 1 Missing and 2 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1525      +/-   ##
==========================================
- Coverage   84.78%   84.72%   -0.06%     
==========================================
  Files         124      124              
  Lines       11439    11442       +3     
  Branches      963      967       +4     
==========================================
- Hits         9698     9694       -4     
  Misses       1433     1433              
- Partials      308      315       +7     
Flag Coverage Δ
unittests 84.72% <66.66%> (-0.06%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...ory_controller/test/test_trajectory_controller.cpp 99.74% <100.00%> (-0.01%) ⬇️
...ntroller/test/test_trajectory_controller_utils.hpp 83.87% <ø> (-0.06%) ⬇️
...ory_controller/src/joint_trajectory_controller.cpp 84.72% <0.00%> (-0.39%) ⬇️

... and 6 files with indirect coverage changes

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@christophfroehlich
Copy link
Member

@Thieso as you are currently working on the open-loop mode, could you have a look on #780 please and approve it if it makes sense for you? Then, please change also all occurances of open-loop in the code comments in this PR here ;)

@Thieso
Copy link
Contributor Author

Thieso commented Feb 13, 2025

@Thieso as you are currently working on the open-loop mode, could you have a look on #780 please and approve it if it makes sense for you? Then, please change also all occurances of open-loop in the code comments in this PR here ;)

Hi, I took a look and tested it on my example and it actually fixes another bug which I was not yet able to find. So it looks good to me but what exactly do you mean by replacing open-loop occurances?

@christophfroehlich
Copy link
Member

can you leave a review in the other pr please?
i just mean that in the comments of some tests there is written open-loop, and after your changes this does not make sense any more

@mergify
Copy link
Contributor

mergify bot commented Feb 14, 2025

This pull request is in conflict. Could you fix it @Thieso?

Copy link
Member

@saikishor saikishor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@christophfroehlich christophfroehlich merged commit fcaa035 into ros-controls:master Mar 7, 2025
21 of 27 checks passed
@christophfroehlich
Copy link
Member

@Thieso as this is merged, could you please open the follow-up PR removing the deprecated code? We then can merge that as soon as we branch for jazzy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[JTC] Parameter open_loop_control should be the default

4 participants