Skip to content

Conversation

@WeihangGuo
Copy link
Contributor

No description provided.

Copy link
Member

@claytonwramsey claytonwramsey left a comment

Choose a reason for hiding this comment

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

note my one comment but otherwise ok! good to submit when that is done.


const bool in_bounds_out = (copy_out <= 1.F).all() and (copy_out >= 0.F).all();

return (not check_bounds or in_bounds_in or in_bounds_out) and
Copy link
Member

Choose a reason for hiding this comment

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

should this be (not check_bounds or (in_bounds_in and in_bounds_out))? Since if we are checking the bounds, we want both ends of the transition to be valid.

Also, maybe we should move the calculation of in_bounds_in and in_bounds_out to be gated behind an if statement to save perf where check_bounds is false? It is not a big loss though, so this is probably fine as is.

@zkingston zkingston merged commit 397a839 into KavrakiLab:main Dec 12, 2025
7 checks passed
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.

3 participants