Skip to content
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

RSDK-9587 generate series of waypoints to cover surface given a pcd mesh #4719

Conversation

biotinker
Copy link
Member

Add assorted public methods associated with Triangles and Meshes.

Also adds several helpful debug statements.

@viambot viambot added the safe to test This pull request is marked safe to test from a trusted zone label Jan 15, 2025
Copy link
Member

@raybjork raybjork left a comment

Choose a reason for hiding this comment

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

I'm not a fan of merging meshes and triangles as public structures considering this just makes them difficult to change in the future. We should just move this to our private sanding package until its more developed

motionplan/cBiRRT.go Outdated Show resolved Hide resolved
motionplan/motionPlanner.go Show resolved Hide resolved
motionplan/planManager.go Outdated Show resolved Hide resolved
services/motion/builtin/builtin.go Outdated Show resolved Hide resolved
spatialmath/box.go Outdated Show resolved Hide resolved
spatialmath/mesh.go Show resolved Hide resolved
@biotinker biotinker requested a review from raybjork January 27, 2025 18:09
@viambot viambot added safe to test This pull request is marked safe to test from a trusted zone and removed safe to test This pull request is marked safe to test from a trusted zone labels Jan 27, 2025
@viambot viambot added safe to test This pull request is marked safe to test from a trusted zone and removed safe to test This pull request is marked safe to test from a trusted zone labels Jan 27, 2025
@viambot viambot added safe to test This pull request is marked safe to test from a trusted zone and removed safe to test This pull request is marked safe to test from a trusted zone labels Jan 27, 2025
Copy link
Member

@raybjork raybjork left a comment

Choose a reason for hiding this comment

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

It looks like the triangle functions are unused here. If possible would like to keep them with the rest of the coverage code so everything is in the same place


// ClosestPointTriangleCoplanarPoint takes a point, and returns the closest point on the triangle to the given point
// The given point *MUST* be coplanar with the triangle. If it is known ahead of time that the point is coplanar, this is faster.
func ClosestPointTriangleCoplanarPoint(t *Triangle, pt r3.Vector) r3.Vector {
Copy link
Member

Choose a reason for hiding this comment

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

I didn't realize these triangle functions were currently unused (or at least I cant see any other references to them in this PR). Can we just move them to the rest of coverage code?

@viambot viambot added safe to test This pull request is marked safe to test from a trusted zone and removed safe to test This pull request is marked safe to test from a trusted zone labels Jan 27, 2025
@biotinker biotinker merged commit be31cfa into viamrobotics:main Jan 28, 2025
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
safe to test This pull request is marked safe to test from a trusted zone
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants