-
Notifications
You must be signed in to change notification settings - Fork 217
Expose depth_publisher param #250
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
Expose depth_publisher param #250
Conversation
|
Thanks for this! I'll review the PR tomorrow. |
jonbinney
left a comment
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.
Everything looks good except for the name "depth_publisher" which sounds like the name of a publisher object instead of a number of scans of history to keep. Could you rename it to something more descriptive? The name of parameter to the create_publisher() function is "qos_history_depth" and the default scan topic is "scan_filtered", so how about "scan_filtered_history_depth"?
|
Updated ! |
|
@doisyg did you forget to push the new commit? |
|
oupsie, wrong branch, fixed |
jonbinney
left a comment
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.
Looks good now, thanks!
|
@Mergifyio backport rolling |
✅ Backports have been created
|
Expose depth_publisher param (backport #250)
|
@jonbinney any chance we could trigger a new release for with this ? |
|
Yes I can do a release - I'll try to get to it this Sunday. |
|
Didn't have time to do the release today - i'll do it tomorrow. |
|
Released version 2.2.3 on kilted and 2.3.1 on rolling. It'll take some time to work through the build farm, then probably 1-3 weeks before there's a sync to the main kilted apt repos. Should show up sooner in the rolling apt repos. |
|
Thank you! |
Adds param
depth_publisher, without changing the current default of 1000, to allow changing the depth of thescan_to_scan_filter_chainoutput topic.For #249