Skip to content

Conversation

@doisyg
Copy link

@doisyg doisyg commented Oct 26, 2025

Adds param depth_publisher, without changing the current default of 1000, to allow changing the depth of the scan_to_scan_filter_chain output topic.
For #249

@jonbinney
Copy link
Contributor

Thanks for this! I'll review the PR tomorrow.

Copy link
Contributor

@jonbinney jonbinney left a 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"?

@doisyg
Copy link
Author

doisyg commented Oct 29, 2025

Updated !

@jonbinney
Copy link
Contributor

@doisyg did you forget to push the new commit?

@doisyg
Copy link
Author

doisyg commented Oct 29, 2025

oupsie, wrong branch, fixed

Copy link
Contributor

@jonbinney jonbinney left a 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!

@jonbinney jonbinney merged commit 8f28c0c into ros-perception:kilted Oct 29, 2025
2 checks passed
@jonbinney
Copy link
Contributor

@Mergifyio backport rolling

@mergify
Copy link

mergify bot commented Oct 29, 2025

backport rolling

✅ Backports have been created

jonbinney added a commit that referenced this pull request Oct 29, 2025
@doisyg
Copy link
Author

doisyg commented Nov 14, 2025

@jonbinney any chance we could trigger a new release for with this ?

@jonbinney
Copy link
Contributor

Yes I can do a release - I'll try to get to it this Sunday.

@jonbinney
Copy link
Contributor

Didn't have time to do the release today - i'll do it tomorrow.

@jonbinney
Copy link
Contributor

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.

@doisyg
Copy link
Author

doisyg commented Nov 17, 2025

Thank you!

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.

2 participants