-
Notifications
You must be signed in to change notification settings - Fork 3
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
[humble] Get user specified parameters at startup #45
Conversation
CI will fail until this gets merged: ros-perception/point_cloud_transport#79 |
quantization_POSITION_paramDescriptor.name, config_.quantization_NORMAL, | ||
quantization_POSITION_paramDescriptor.name, config_.quantization_POSITION, |
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.
spotted some typos as well, so fixing those in this pass
@@ -85,6 +85,7 @@ void DracoPublisher::declareParameters(const std::string & base_topic) | |||
declareParam<int>( | |||
encode_speed_paramDescriptor.name, config_.encode_speed, | |||
encode_speed_paramDescriptor); | |||
getParam<int>(encode_speed_paramDescriptor.name, config_.encode_speed); |
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.
primary change is to add these so that if a user has configured parameter values at startup, we get them
appears to be working properly now. I first tested this by just logging to verify that the parameters were getting set at startup now. I also played back this rosbag with force_quantization on and off (set via average size of raw messages force_quantization off force_quantization on |
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.
Same comment here ros-perception/point_cloud_transport#79 (review)
Same here: #46 |
closing this one in favour of this other one #50 |
Currently, no plugins that
declare
parametersget
the values at startup. This means that even if a user were to specify a parameter via ros2 launch or ros2 run, it would not get loaded. The only way to load a non-default parameter atm is to dynamically configure it after startup.This PR fixes this by
get
ting the parameter values at startup. For users who are currently using the default values, this PR does nothing. For users who want to be able to specify the parameters at startup, this will allow them to do that.Relates to this issue: ros-perception/point_cloud_transport#66