-
Notifications
You must be signed in to change notification settings - Fork 126
cache transform when computing geometries, probably more low hanging … #5456
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
base: main
Are you sure you want to change the base?
Conversation
referenceframe/frame_system.go
Outdated
| return result, nil | ||
| } | ||
|
|
||
| // composeTransforms assumes there is one moveable frame and its DoF is equal to the `inputs` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Recommend the following comment:
// composeTransforms returns the pose for `frame` given the inputs that frame depends on. The cache
// maps frame names to output poses. The cache assumes the linear inputs are the same as prior calls
// to `composeTransforms`. When a caller changes its `linearInputs`, the caller must invalidate its
// `cache` object.
dgottlieb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't check the callsite updates to check for cache invalidation -- just looked at the composeTransforms bit. Let me know if you think there's value in me taking a closer look for bugs in the usage. I assumed that class of bugs wasn't particularly at risk here.
this had less impact than i expected. |
Availability
Quality
Performance
The above data was generated by running scenes defined in the
|
…fruit