Skip to content

feat(constitution): offset joint limits by initial distance/angle#411

Open
Ligo04 wants to merge 2 commits intospiriMirror:mainfrom
Ligo04:feat/joint-limit-init-offset
Open

feat(constitution): offset joint limits by initial distance/angle#411
Ligo04 wants to merge 2 commits intospiriMirror:mainfrom
Ligo04:feat/joint-limit-init-offset

Conversation

@Ligo04
Copy link
Copy Markdown
Contributor

@Ligo04 Ligo04 commented Mar 30, 2026

Summary

Joint limits (prismatic and revolute) now support an initial offset so that the limit range is expressed relative to an initial configuration rather than the reference pose.

  • Add init_distance edge attribute to AffineBodyPrismaticJointLimit — the effective bounds become lower + init_distance and upper + init_distance
  • Add init_angle edge attribute to AffineBodyRevoluteJointLimit — the effective bounds become lower + init_angle and upper + init_angle
  • Both attributes default to 0.0, preserving backward compatibility
  • Update specification documents for UID 669 and 670 with the new offset formulas and attribute descriptions

Ligo04 added 2 commits March 30, 2026 16:08
Prismatic and revolute joint limits now account for an initial
configuration offset. The `init_distance` and `init_angle` edge
attributes are added to the lower/upper bounds so that limits are
expressed relative to the rest pose rather than absolute values.

Made-with: Cursor
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces initial offsets for affine body joint limits, specifically adding init_distance for prismatic joints and init_angle for revolute joints. These offsets are incorporated into the calculation of effective lower and upper bounds for joint constraints. The changes span documentation, CUDA backend implementations, and core attribute management. I have no feedback to provide as there were no review comments to evaluate.

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.

1 participant