- 
                Notifications
    You must be signed in to change notification settings 
- Fork 115
Declare missing parameters for PID #443
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
Conversation
| Codecov Report❌ Patch coverage is  
 Additional details and impacted files@@               Coverage Diff               @@
##           ros2-master     #443      +/-   ##
===============================================
+ Coverage        77.75%   77.82%   +0.07%     
===============================================
  Files               30       30              
  Lines             2009     2020      +11     
  Branches           125      129       +4     
===============================================
+ Hits              1562     1572      +10     
  Misses             379      379              
- Partials            68       69       +1     
 Flags with carried forward coverage won't be shown. Click here to find out more. 
 🚀 New features to boost your workflow:
 | 
        
          
                control_toolbox/src/pid_ros.cpp
              
                Outdated
          
        
      | u_max = UMAX_INFINITY; | ||
| u_min = -UMAX_INFINITY; | ||
| bool antiwindup = false; | ||
| bool saturation = false; | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| bool saturation = false; | |
| bool saturation = true; | 
Shouldn't the default be true?
| declare_param(param_prefix_ + "saturation", rclcpp::ParameterValue(true)); | 
TO be coherent with the above one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd change it in initialize_from_args to be true only if u_min or u_max argument is finite.
for ROS parameters, idk if it should be default false or default true? or use the same logic, depending on u_clamp_max/min parameter?
(cherry picked from commit 4ea96f9)
Resolves #442
I fixed the tests, we haven't tested all the parameters with
initialize_from_ros_parameters