[JTC] Add Parameter to Toggle State Setting on Activation #1231
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
requested review from
bijoua29,
bmagyar,
DasRoteSkelett,
destogl,
olivier-stasse,
peterdavidfagan and
VanshGehlot
|
Hi, I wanted to kindly ask if there’s a chance for this pull request to be reviewed. Any feedback would be greatly appreciated. Thank you! |
christophfroehlich
requested changes
Aug 29, 2024
There was a problem hiding this comment.
Makes sense. Please just add a tiny note in the https://github.com/ros-controls/ros2_controllers/blob/master/doc/release_notes.rst
|
Wait, I am not sure about this. Can you detail the scenario more. Are you using open loop? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1231 +/- ##
==========================================
+ Coverage 80.34% 80.36% +0.01%
==========================================
Files 105 105
Lines 9384 9388 +4
Branches 826 825 -1
==========================================
+ Hits 7540 7545 +5
Misses 1570 1570
+ Partials 274 273 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
@destogl We are not using open-loop control. We are creating a closed-loop controller called
Scenario:
|
…ctivation to release_notes. Updated the parameters.yaml description to match the same wording.
|
@christophfroehlich |
|
@christophfroehlich , are we good? |
|
@bmagyar @christophfroehlich |
christophfroehlich
merged commit f96d2fc
into
ros-controls:master
20 of 21 checks passed
|
@Mergifyio backport iron humble |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Oct 26, 2024
* [JTC] Add param to setting last command interface value as state on activation * [JTC] add a note about set_last_command_interface_value_as_state_on_activation to release_notes. Updated the parameters.yaml description to match the same wording. --------- Co-authored-by: Bence Magyar <[email protected]> Co-authored-by: Christoph Fröhlich <[email protected]> (cherry picked from commit f96d2fc)
mergify bot
pushed a commit
that referenced
this pull request
Oct 26, 2024
* [JTC] Add param to setting last command interface value as state on activation * [JTC] add a note about set_last_command_interface_value_as_state_on_activation to release_notes. Updated the parameters.yaml description to match the same wording. --------- Co-authored-by: Bence Magyar <[email protected]> Co-authored-by: Christoph Fröhlich <[email protected]> (cherry picked from commit f96d2fc) # Conflicts: # joint_trajectory_controller/src/joint_trajectory_controller_parameters.yaml
christophfroehlich
pushed a commit
that referenced
this pull request
Oct 26, 2024
) * [JTC] Add param to setting last command interface value as state on activation * [JTC] add a note about set_last_command_interface_value_as_state_on_activation to release_notes. Updated the parameters.yaml description to match the same wording. --------- Co-authored-by: Bence Magyar <[email protected]> Co-authored-by: Christoph Fröhlich <[email protected]> (cherry picked from commit f96d2fc) Co-authored-by: Kenta Kato <[email protected]>
bmagyar
pushed a commit
that referenced
this pull request
Oct 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new parameter in the JointTrajectoryController that enables toggling whether the last command interface value should be set as both the current_state and last_commanded_state upon activation.
Motivation
Consider a scenario where there is a transition from a JTC to another controller and back to a JTC. Due to the implementation specifics of the intermediary controller, it is possible that the command interface values from the first JTC remain. This can lead to dangerous situations where, upon reactivation, the second JTC inadvertently uses these stale command values to command the hardware.
To mitigate this risk, I have added an option within the JTC that ensures command values are reliably reset to reflect the current state upon activation, enhancing system safety.