This repository contains the implementation from “HJCD-IK: GPU-Accelerated Inverse Kinematics through Batched Hybrid Jacobian Coordinate Descent”.
HJCD-IK is a GPU-accelerated, sampling-based hybrid inverse kinematics solver for generating one or more robot configurations for a target end-effector pose.
- Linux
- NVIDIA GPU
- CUDA Toolkit 12.x or 13.x
- Python 3.9 or newer
- CMake 3.24 or newer
- GCC or Clang
- nlohmann-json
Clone the repository:
git clone https://github.com/A2R-Lab/HJCD-IK.git
cd HJCD-IKRun the development setup:
chmod +x scripts/setup/setup_dev.sh
./scripts/setup/setup_dev.sh
source .venv/bin/activateThe script initializes the required submodules, creates a virtual environment, installs dependencies,
regenerates the collision-enabled Panda model, and builds hjcdik.
Development setup and signed GPU-proof tooling require Python 3.11 or newer; the base package
supports Python 3.9 or newer.
If needed, convert the shell scripts to Unix line endings:
dos2unix scripts/setup/*.sh scripts/bench/*.shVerify the installation:
python - <<'PY'
import hjcdik
print("hjcdik:", hjcdik.__file__)
print("build/model:", hjcdik.build_info())
PYInitialize the required submodules:
./scripts/setup/bootstrap.shCreate a virtual environment:
python3 -m venv .venv
source .venv/bin/activateInstall the build tools, then build the package and development dependencies against the committed,
collision-enabled grid.cuh:
python -m pip install --upgrade \
pip setuptools wheel cmake ninja scikit-build-core pybind11
python -m pip install -e ".[dev]" --no-build-isolationGRiD code generation is optional for the default Panda build. Install .[codegen] and use the
collision-enabled command below only when changing the URDF or end-effector target.
import hjcdik
target = hjcdik.sample_targets(num_targets=1, seed=0)[0]
result = hjcdik.generate_solutions(
target,
batch_size=2000,
num_solutions=1,
)
print("solutions:", result["count"])
print("joint configurations:", result["joint_config"])
print("position errors:", result["pos_errors"])
print("orientation errors:", result["ori_errors"])Each call solves one target. batch_size is the number of candidate configurations,
not the number of target poses. A wheel contains one compiled robot; use build_info()
to confirm its identity. See upgrading and verified scope
for changes to collision defaults, native ownership, and error handling.
Target poses use:
[x, y, z, qw, qx, qy, qz]
Target and returned pose positions are in meters; quaternions use wxyz order and are normalized on input.
Returned pos_errors are in millimeters and ori_errors are in radians. Check these errors against
your tolerances; the solver can return approximate candidates for unreachable targets. Collision filtering
can return fewer solutions, including zero. See the Python API.
In hard/both mode, collision-aware refinement may retain a free fallback within 5 mm / 0.05 rad
when this run finds no exactly converged free candidate. A nonempty result is not an accuracy
certificate: check both errors for the same candidate against your application's tolerances.
build_info()["ee_target"] identifies the compiled tool frame. MotionBenchMaker goals are
hand-frame poses, 105 mm from the default Panda TCP; the collision example converts them explicitly.
The benchmark's --target-mode goal requires a panda_hand_joint build, whereas --target-mode cylinder
uses the default panda_grasptarget_hand build. Do not pass hand poses directly to a TCP build.
Generate the Panda collision model:
python scripts/codegen/generate_grid.py \
csrc/urdf/panda.urdf \
-t panda_grasptarget_hand \
--collision \
--spherized-urdf \
external/foam/assets/panda/smaller_panda_spherized.urdfRebuild:
python -m pip install -e . --no-build-isolationAfter any code-generation change, rebuild with:
bash scripts/setup/rebuild.shNote: the tests and collision-free example require a collision-enabled build.
The default Panda model keeps fixed finger-joint origins at +/-40 mm in the hand frame.
Foam supplies sphere shapes, but their placement uses this kinematic URDF. The frozen paper
reference uses +/-65 mm finger origins and is deliberately retained for historical comparisons.
The benchmark's --collision-validation-model paper (default) selects that legacy reference;
--collision-validation-model hjcd selects an independent URDF-derived check of the current
geometry. This flag changes only post-hoc validation, never the solver's compiled robot.
Both checks are environment-only; the solver's hard/both modes additionally check self-collision.
CSV/YAML collision results have a .metadata.json sidecar identifying the selected model,
source hashes, finger origins, and compiled-header identity.
Benchmark summaries count attempted queries, including zero-output failures, rather than returned solutions. Configuration dumps retain the target/frame and empty records for independent FK scoring. See the current timing and evidence protocol.
Run the included examples:
python examples/01_open_world_solve.py
python examples/02_collision_free_solve.py
python examples/03_batch_sweep.pyFor the full test suite, use the collision-enabled Panda build above and install .[dev,codegen].
GPU-proof receipt generation and the one-shot development setup require Python 3.11 or newer.
Run:
python -m pytest tests/ -vWhen adding or renaming tests, regenerate and commit the proof manifest before recording a receipt:
python scripts/setup/update_gpu_proof_manifest.pyThe GPU-proof policy binds the full test list, solver sources, executable docs/examples, build/codegen scripts, and dependency
gitlinks. A scoped pytest -k ... run is useful for diagnosis but cannot certify the full suite.
Run one test file:
PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 \
python -m pytest tests/test_fk_equivalence.py -vThe benchmark harness (benchmark/hjcd_ik_bench.py), the optional competitor baselines and the paper
reproduction protocol are documented in
docs/source/user_guide/benchmarks/reproduction.md;
measured results and the fairness study are in
docs/source/user_guide/benchmarks/results.rst.
Timing numbers are only meaningful on an otherwise idle GPU.
Generate a robot-specific model:
python scripts/codegen/generate_grid.py \
<PATH_TO_URDF> \
-t <FIXED_TARGET_NAME>Example:
python scripts/codegen/generate_grid.py \
csrc/urdf/fetch.urdf \
-t ee_fixedThen rebuild:
python -m pip install -e . --no-build-isolationHJCD-IK supports fixed-base serial chains with 1–32 independent revolute or continuous joints rotating around local +Z; fixed joints may connect links and the tool frame. Prismatic, mimic, branched, floating-base, and other-axis models are rejected. GRiD supports more robot classes than this solver. See the custom-robot guide.
Generate collision spheres from the URDF:
python scripts/codegen/generate_grid.py \
path/to/robot.urdf \
-t end_effector_fixed_joint \
--collision \
--collision-res 0.02Or use a pre-spherized foam URDF:
python scripts/codegen/generate_grid.py \
path/to/robot.urdf \
-t end_effector_fixed_joint \
--collision \
--spherized-urdf path/to/robot_spherized.urdfCollision environments use a MotionBenchMaker-style JSON format.
Each problem may contain:
goal_pose
start
world_frame
obstacles
Examples are available in:
tests/mb_problems.json
Supported obstacle types are:
spherecuboidcylinder
"cuboid": {
"box": {
"dims": [0.30, 0.25, 0.80],
"pose": [-0.05, 0.00, -0.40, 1, 0, 0, 0]
}
}"cylinder": {
"post": {
"radius": 0.035,
"height": 0.24,
"pose": [0.35, 0.15, 0.12, 1, 0, 0, 0]
}
}"sphere": {
"ball": {
"radius": 0.05,
"pose": [0.40, 0.10, 0.30, 1, 0, 0, 0]
}
}All poses use:
[x, y, z, qw, qx, qy, qz]
@inproceedings{yasutake2026hjcdik,
title = {{HJCD-IK}: {GPU}-Accelerated Inverse Kinematics through Batched Hybrid Jacobian Coordinate Descent},
author = {Yasutake, Cael and Liu, Andrew H. and Kingston, Zachary and Plancher, Brian},
booktitle = {2026 IEEE/RSJ International Conference on Intelligent Robots and Systems (IROS)},
year = {2026},
note = {arXiv:2510.07514}
}HJCD-IK is released under the MIT License.
This material is based upon work supported by the National Science Foundation (under Award 2411369). Any opinions, findings, conclusions, or recommendations expressed in this material are those of the authors and do not necessarily reflect those of the funding organizations.