You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Description
Pink IK uses DAQP through `qpsolvers`, but the install-time dependency
repair only
verified that Pinocchio could be imported. In environments where
`pin-pink` or
`qpsolvers` is present but DAQP is missing, unregistered, or too old for
`qpsolvers` warm-start arguments, `solve_ik(..., solver="daqp")` can
fail and
fall back to current joint targets. The controller then reports a
misleading
end-effector position error in `test_pink_ik.py`.
This change makes the installer probe the full Pink IK stack:
`pinocchio`, DAQP
registration in `qpsolvers`, and the `daqp.solve` API shape required by
current
`qpsolvers` (`primal_start`). It also aligns the IsaacLab dependency pin
with
the compatible DAQP release, `daqp==0.8.5`.
Runtime handling stays narrow: ordinary IK failures keep the existing
fallback,
while missing DAQP or the specific `primal_start` API mismatch is
surfaced with
an actionable install message instead of being swallowed as an IK
fallback.
The docs config also mocks `qpsolvers`, matching the existing docs
treatment for
optional Pink IK dependencies such as `pink` and `pinocchio`, so API
docs can be
built without the runtime solver stack installed.
## Type of change
- Bug fix (non-breaking change which fixes an issue)
## Test Plan
- `./isaaclab.sh -p -m py_compile
source/isaaclab/isaaclab/cli/commands/install.py
source/isaaclab/isaaclab/controllers/pink_ik/pink_ik.py
source/isaaclab/setup.py docs/conf.py`
- `./isaaclab.sh -p -c "import inspect, pinocchio, daqp, qpsolvers;
assert 'daqp' in qpsolvers.available_solvers; assert 'primal_start' in
inspect.signature(daqp.solve).parameters; print('pink ik dependency
probe passed')"`
- `./isaaclab.sh -p -c "..."` small monkeypatch check that
`TypeError("solve() got an unexpected keyword argument 'primal_start'")`
raises the new DAQP compatibility `RuntimeError`
- `./isaaclab.sh -p -m pytest
source/isaaclab/test/controllers/test_pink_ik.py::test_movement_types -k
"GR1T2-Abs-v0 and stay_still" -q --tb=short -s -x`
- `./isaaclab.sh -p -m pytest
source/isaaclab/test/controllers/test_pink_ik.py -q --tb=short -x` (`23
passed, 1 skipped`)
-
`VIRTUAL_ENV=/home/zhengyuz/Projects/IsaacLab.wt/feature-heterogeneous_dexsuite/env_isaaclab
PATH=/home/zhengyuz/Projects/IsaacLab.wt/feature-heterogeneous_dexsuite/env_isaaclab/bin:$PATH
make current-docs` from `docs/`
-
`VIRTUAL_ENV=/home/zhengyuz/Projects/IsaacLab.wt/feature-heterogeneous_dexsuite/env_isaaclab
./isaaclab.sh -f`
## Screenshots
N/A.
## Checklist
- [x] I have read and understood the [contribution
guidelines](https://isaac-sim.github.io/IsaacLab/main/source/refs/contributing.html)
- [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with
`./isaaclab.sh --format`
- [x] I have made corresponding changes to the documentation (N/A - docs
config only)
- [x] My changes generate no new warnings
- [x] I have added tests that prove my fix is effective or that my
feature works
- [x] I have added a changelog fragment under
`source/<pkg>/changelog.d/` for every touched package (do **not** edit
`CHANGELOG.rst` or bump `extension.toml` -- CI handles that)
- [x] I have added my name to the `CONTRIBUTORS.md` or my name already
exists there
0 commit comments