Skip to content

Feature/gradient occupancy#66

Draft
MultyXu wants to merge 8 commits into
developfrom
feature/gradient_occupancy
Draft

Feature/gradient occupancy#66
MultyXu wants to merge 8 commits into
developfrom
feature/gradient_occupancy

Conversation

@MultyXu

@MultyXu MultyXu commented Apr 15, 2026

Copy link
Copy Markdown

Add a gradient-based map publisher for the mid-level planner and other functionalities.

@MultyXu MultyXu marked this pull request as draft April 15, 2026 11:37
@MultyXu MultyXu requested a review from nathanhhughes April 15, 2026 11:51
@MultyXu

MultyXu commented Apr 15, 2026

Copy link
Copy Markdown
Author

@nathanhhughes The old tsdf occupancy publisher broke when there were ramps and hills, causing some issues with the mid-level planner. I'm not sure if these changes are ready to be merged and how we should try that in the DCSIT system. So I thought it was best to pin you to get an idea.

@nathanhhughes

Copy link
Copy Markdown
Collaborator

@MultyXu yeah, this will need some work on the Hydra side to actually merge in (it doesn't make sense to duplicate the code and work of the gradient-based traversability estimator), but easy to keep rebasing on top of develop if we have to make other changes to Hydra-Ros

@MultyXu MultyXu force-pushed the feature/gradient_occupancy branch from e237833 to 5092844 Compare June 24, 2026 00:17

@nathanhhughes nathanhhughes left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there's still too much duplication with the code and computation in Hydra and we should fix that before merging this

float confidence = 0.0f; // num_neighbors / 8.0
};

class TsdfGradientOccupancyPublisher : public ReconstructionModule::Sink {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should just add this as a sink to the traversability estimator instead of the reconstruction module (which would help drop the requirement for most of the code duplication), but we can also talk about what kind of architecture makes sense (we can also think about publishing this as a cost map instead of a occupancy grid and refining the mid-level planner to be able to take that as well)

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