Improve workspace batching and analytic IK buffer reuse - #606
Open
yuecideng wants to merge 4 commits into
Open
Conversation
|
6 tasks
Co-authored-by: matafela <chenjian@dexforce.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Reduce workspace-analysis overhead by replacing 1,000 individual FK calls for dynamic bounds with one batch and reusing analytic IK candidate storage. Robot batch methods now broadcast base transforms, preserve leading batch axes through solver adapters, and avoid redundant target allocations and single-seed reductions.
UR retains all 512 candidates, validity thresholds, and nearest-seed selection. Candidate-enumeration/kernel changes are outside this PR.
On RTX PRO 5000, warm dynamic-bounds estimation improves from 879.6 to 1.47 ms for UR5 and 143.5 to 0.83 ms for CobotMagic. Fixed-domain analysis gains vary, with some UR multi-seed cases around 1.3x and several cases near parity. CPU and CUDA each have 22 comparison cases with identical reported success rates and FK residuals. These are renderer-free measurements, not complete simulation startup timings; Torch memory counters do not include baseline Warp allocations.
See the benchmark methodology, results and reproduction commands.
Dependencies: no new dependencies.
Type of change
Validation
black .),git diff --check, context validation and API documentation coverage (1,853/1,853 exports) passed.Screenshots
Not applicable; numerical comparisons are in the benchmark report.
Checklist
black .command to format the code base.