Skip to content

Migrate OVPhysX joint-wrench sensor onto OvPhysxView (view series, part 5)#6230

Open
AntoineRichard wants to merge 12 commits into
isaac-sim:developfrom
AntoineRichard:antoiner/feat/ovphysx_joint_wrench_view
Open

Migrate OVPhysX joint-wrench sensor onto OvPhysxView (view series, part 5)#6230
AntoineRichard wants to merge 12 commits into
isaac-sim:developfrom
AntoineRichard:antoiner/feat/ovphysx_joint_wrench_view

Conversation

@AntoineRichard

Copy link
Copy Markdown
Collaborator

🔗 Stacked on top of #6224 (Part 1 — OvPhysxView)

Branched off #6224 as a sibling of the asset migrations (#6225/#6226/#6227). Targets develop; until #6224 merges, the diff below includes the Part 1 OvPhysxView commits. Please review #6224 first.

Description

Part 5 of the OVPhysX view-migration series — route the joint-wrench sensor's tensor-binding management through OvPhysxView. Internal refactor; no public API change (sensors do not expose a root_view).

  • _initialize_impl builds one OvPhysxView instead of separate create_tensor_binding calls; binding handles come from binding_for.
  • Pose/state reads route through read_into (cached float32 reinterpret, typed off the binding shape), replacing the manual wp.array(ptr=...) reinterpret views.
  • All bindings are GPU-resident state (ARTICULATION_LINK_INCOMING_JOINT_FORCE); no CPU staging needed.
  • Numeric behavior unchanged.

Type of change

  • This change requires no public API change (internal refactor)

Checklist

  • I have run the pre-commit checks with ./isaaclab.sh --format
  • My changes generate no new warnings
  • I have added a changelog fragment (.skip — internal refactor, no user-facing change / no bump)

Testing

test_joint_wrench_sensor.py — cpu: 11 passed, cuda: 11 passed.

OVPhysX exposes physics attributes as a loose dict of TensorType ->
TensorBinding with no view object, unlike Newton's
selection.ArticulationView and PhysX's typed tensor views. OvPhysxView
wraps the bindings for one prim pattern behind a string-keyed
get_attribute / set_attribute surface, addressing attributes by the
lowercased TensorType enum name (e.g. "articulation_dof_stiffness").
It needs no Model/State/Control source object because the TensorType
already implies where the data lives.

Prototype per docs/superpowers/specs/2026-06-17-ovphysx-view-design.md.
Adds unit tests covering name<->enum resolution, the read-only guard,
discoverability, and get/set dispatch against a fake binding (no native
simulation required).
Reworks the view from a convenience wrapper into a layer that can back the
OVPhysX asset/data classes, per the PR review of isaac-sim#6224:

- read_into(name, dst): zero-copy fill of a caller-owned, possibly
  structured-dtype buffer (e.g. wp.transformf) via a float32 reinterpret
  view -- the mechanism the data containers use today.
- set_attribute: accepts structured-dtype sources via the same reinterpret;
  non-float32-width buffers are rejected rather than silently bit-cast.
- prim_paths + key_aliases: support the fused multi-prim binding form
  (create_tensor_binding(prim_paths=[...])) and storing a binding under a
  different TensorType key, as RigidObjectCollection needs.
- binding_for(): raw TensorBinding accessor for adoption.
- _CPU_ONLY_NAMES is now derived from tensor_types._CPU_ONLY_TYPES (no drift).
- Added joint/tendon/is_fixed_base metadata passthrough; eager construction
  raises if it creates zero bindings; get_attribute allocates a fresh buffer
  (no aliasing); nested error hierarchy; PhysX/binding Protocols.

Device policy: no implicit CPU<->GPU conversion. CPU-resident property types
are read/written on CPU; a buffer on the wrong device raises DeviceMismatch
instead of being staged. Device-less host data (numpy/list) is materialized
on the binding's native device.
The OvPhysxView addition is a significant new public surface for the OVPhysX
backend, so promote the changelog fragment from a minor to a major bump.
Reword the entry to describe the binding-manager surface (read_into, the
no-device-conversion policy) and drop the internal design-note path from the
user-facing changelog.
From the second PR review of isaac-sim#6224:

- Critical: _as_binding_view now requires a float32 scalar dtype before the
  zero-copy reinterpret. A same-byte-width wrong dtype (int32) previously passed
  the count-only guard and was bit-reinterpreted into garbage on the write path;
  sub-4-byte dtypes (float16) produced a misleading "0 elements" error. Both are
  now rejected with a clear message. Regression tests added (verified failing
  without the guard).
- _resolve enforces the str | TensorType union and raises UnknownAttribute on
  anything else, instead of letting a bogus key reach the wheel.
- _binding accesses binding.count directly (a malformed binding surfaces instead
  of being masked as a phantom no-match) and surfaces the underlying
  create_tensor_binding exception in the AttributeUnavailable message.
- Added docstrings to the six metadata properties; dropped the unused
  runtime_checkable decorator.
- Tests: same-byte/sub-4-byte dtype rejection, get_attribute(out=) wrong device,
  both indices+mask forwarded, read/write through a prim_paths+key_aliases view,
  non-str/non-TensorType key, and a read-only-names-are-valid-vocabulary check.
From the API-hardening review of isaac-sim#6224. Validate at the boundary and fail loud
instead of silently corrupting, mis-binding, or no-op'ing:

- Reject non-contiguous buffers in _as_binding_view (a strided/sliced source would
  be reinterpreted as contiguous and read/write the wrong memory).
- Canonicalize the device (wp.get_device) so a "cuda" view accepts a "cuda:0"
  buffer instead of raising a spurious, unsatisfiable DeviceMismatch; falls back
  to the raw string when the device can't be resolved locally.
- Reject TensorType.INVALID via the member path too (string path already did).
- Normalize key_aliases to TensorType members so string keys are honored rather
  than silently dropped, and reject aliases that cross the CPU/GPU residency or
  read-only boundary (the device/read-only guards key on the requested type).
- Reject empty pattern/prim_paths and tensor_types-without-eager at construction.
- Eager construction with an explicit tensor_types list now surfaces a failing
  type instead of swallowing it at debug level (default sweep still skips
  inapplicable types).
- Document binding_for as an unguarded escape hatch, get_attribute's native-device
  return, and the has_attribute name-validity-vs-availability split.

Adds regression tests for each (contiguity and INVALID verified failing without
the guard).
Surfaced by dogfooding the view in the articulation migration: the assets branch
on a "binding or None" pattern for optional/absent bindings (tendon types on a
tendon-less articulation, not-yet-created bindings), which the raising binding_for
can't express. try_binding_for returns None when the attribute is valid but not
available for the view's prims, while still raising UnknownAttribute for an invalid
name (a programming error, not an availability question).
…xView

read_into now reuses the float32 reinterpret of a destination buffer
across calls (keyed by buffer id, with a pointer-staleness guard), so the
wheel's object-identity read cache stays warm even when callers hand a
structured buffer each step -- they no longer need to maintain their own
reinterpret cache. get_attribute returns a typed array for attributes with
a known structured layout (transformf for poses, spatial_vectorf for
velocities, via a hand-maintained _ATTR_DTYPE map) and flat float32
otherwise.

This lets the asset data containers drop their bespoke _get_read_view
caching and read structured buffers straight through the view.
@github-actions github-actions Bot added the isaac-lab Related to Isaac Lab team label Jun 22, 2026
OvPhysxView (and OvPhysxFrameView) live in isaaclab_ovphysx.sim.views,
which had no API-docs page. Add the automodule stub and wire it into the
isaaclab_ovphysx autosummary so the new binding-manager view shows up in
the rendered API reference alongside assets / cloner / physics.
Three fixes from the Part 1 review:

- get_attribute (no out): route the freshly allocated buffer through
  _as_binding_view directly instead of the id()-keyed read cache. A fresh
  buffer can never hit the cache and would leak one entry (keeping the
  buffer alive) per call in a step loop; the cache only pays off for a
  reused out/dst buffer. Add a regression test asserting the no-out path
  leaves _read_views empty.

- Raise a dedicated DtypeMismatch instead of ShapeMismatch when a buffer's
  scalar element type is not float32, so a dtype error no longer reads as a
  dimensions error. Update the affected tests and the Raises docstrings.

- Make the view Warp-native: drop the fragile __module__ string-match that
  auto-converted Torch tensors on writes. Callers bridge a Torch tensor
  with wp.from_torch(t), keeping the device policy explicit and avoiding an
  optional Torch dependency.
Documentation/comment clarifications from the isaac-sim#6224 review (no behavior change):

- Narrow the documented contract to float32-only: attribute_names/has_attribute
  and the module docstring now state that a listed name is name-validity, not a
  dtype-support promise; non-float dtype handling awaits wheel dtype metadata.
- Mark _READ_ONLY_NAMES explicitly temporary; name the three access modes
  (read/write, read-only, write-only) and the wheel access_mode enum that should
  replace the table.
- Document key_aliases as an internal collection adapter, not general public API,
  pending descriptor metadata.
- Make the view test scope explicit: mock API mechanics here; live
  CPU-only-on-GPU / read-only+write-only / structured read_into coverage lives in
  the asset-integration tests.
…gh OvPhysxView

Replace the direct create_tensor_binding call and the manual float32
reinterpret alias in the OVPhysX joint-wrench sensor with an OvPhysxView.
The view owns the LINK_INCOMING_JOINT_FORCE binding and reads the GPU
spatial-vector tensor straight into the structured wrench buffer via
read_into, which caches the reinterpret per destination buffer.
@AntoineRichard AntoineRichard force-pushed the antoiner/feat/ovphysx_joint_wrench_view branch from d1a009c to f23d447 Compare June 23, 2026 10:01
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Jun 23, 2026
@AntoineRichard AntoineRichard marked this pull request as ready for review June 25, 2026 11:25
@greptile-apps

greptile-apps Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Routes the joint-wrench sensor's tensor-binding lifecycle through the new OvPhysxView class, replacing direct create_tensor_binding calls and a manually-managed float32 alias view with a string-keyed binding manager that caches structured-dtype reinterpret views internally. The public sensor API is unchanged.

  • ovphysx_view.py — new 705-line OvPhysxView class with lazy/eager binding creation, device-residency enforcement (no implicit CPU↔GPU staging), dtype reinterpret guards, and a _read_views cache that keeps the OVPhysX wheel's object-identity read-cache warm across steps.
  • joint_wrench_sensor.py_initialize_impl now creates one OvPhysxView and retrieves the binding from it; _update_buffers_impl calls read_into directly with the spatial_vectorf buffer; _invalidate_initialize_callback correctly nulls the view before the buffer to prevent Warp's deallocator from aborting on a freed-but-still-referenced allocation.
  • test_ovphysx_view.py — 587-line unit tests covering name resolution, structured-dtype reinterpret, device policy, key aliases, and the read-cache non-growth assertion for no-out get_attribute calls.

Confidence Score: 4/5

Safe to merge — this is a pure internal refactor with no public API changes, the sensor's numeric behavior is unchanged, and the teardown ordering is correct.

The _read_views cache in OvPhysxView accumulates entries without eviction. For the sensor's single reused buffer this is harmless, but as a general-purpose class it could quietly retain dead reinterpret-view objects for callers who cycle through many destination buffers. Everything else — device-residency enforcement, structured-dtype reinterpret, binding caching, invalidation ordering, and test coverage — looks solid.

The _read_view method in ovphysx_view.py (lines 802–818) warrants a second look on the cache eviction question before this class is used more broadly.

Important Files Changed

Filename Overview
source/isaaclab_ovphysx/isaaclab_ovphysx/sim/views/ovphysx_view.py New 705-line OvPhysxView class — string-keyed binding manager over OVPhysX TensorBinding. Well-structured with typed errors, device-residency policy, and a read-cache for structured-dtype reinterprets. The _read_views cache grows without eviction, which is benign for single-buffer callers but a latent memory concern for views used with many distinct destination buffers.
source/isaaclab_ovphysx/isaaclab_ovphysx/sensors/joint_wrench/joint_wrench_sensor.py Initialization now builds one OvPhysxView and retrieves the LINK_INCOMING_JOINT_FORCE binding from it; per-step reads route through read_into instead of a manual float32 alias view. Ordering in _invalidate_initialize_callback (view before buffer) is correct. _wrench_binding is still maintained as an instance attribute but no longer participates in the guard check.
source/isaaclab_ovphysx/test/sim/test_ovphysx_view.py 587-line unit test file covering pure helpers, construction (eager/lazy), get_attribute, read_into, set_attribute, device policy, dtype safety, key aliases, and adversarial cases via a fake PhysX+TensorBinding. Includes a dedicated test asserting that the read-cache is not populated on no-out get_attribute calls.
source/isaaclab_ovphysx/isaaclab_ovphysx/sim/views/init.pyi Adds OvPhysxView to all and the re-export list in the stub file. Clean, no issues.
docs/source/api/lab_ovphysx/isaaclab_ovphysx.sim.views.rst New RST page for isaaclab_ovphysx.sim.views using automodule. Correctly indexed in docs/source/api/index.rst.

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant S as JointWrenchSensor
    participant V as OvPhysxView
    participant PX as OVPhysX (PhysX)
    participant B as TensorBinding

    Note over S,B: _initialize_impl
    S->>V: OvPhysxView(physx, pattern, device)
    S->>V: binding_for(LINK_INCOMING_JOINT_FORCE)
    V->>PX: create_tensor_binding(tensor_type, pattern)
    PX-->>V: TensorBinding (cached in _bindings)
    V-->>S: _wrench_binding (raw handle)
    S->>S: validate body_count / count
    S->>S: allocate _wrench_buf (spatial_vectorf)

    Note over S,B: _update_buffers_impl (each step)
    S->>V: read_into(LINK_INCOMING_JOINT_FORCE, _wrench_buf)
    V->>V: "_resolve -> TensorType"
    V->>V: "_binding(tt) -> cached TensorBinding"
    V->>V: _check_device(_wrench_buf, device)
    V->>V: _read_view(_wrench_buf, binding)
    Note right of V: First call: build float32 reinterpret,<br/>cache in _read_views[id(buf)].<br/>Subsequent calls: reuse cached view.
    V->>B: binding.read(float32_reinterpret_view)
    B-->>V: fills buffer in-place

    Note over S,B: _invalidate_initialize_callback
    S->>S: "_root_view = None (releases _read_views)"
    S->>S: "_wrench_binding = None"
    S->>S: "_wrench_buf = None (safe: reinterpret already released)"
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant S as JointWrenchSensor
    participant V as OvPhysxView
    participant PX as OVPhysX (PhysX)
    participant B as TensorBinding

    Note over S,B: _initialize_impl
    S->>V: OvPhysxView(physx, pattern, device)
    S->>V: binding_for(LINK_INCOMING_JOINT_FORCE)
    V->>PX: create_tensor_binding(tensor_type, pattern)
    PX-->>V: TensorBinding (cached in _bindings)
    V-->>S: _wrench_binding (raw handle)
    S->>S: validate body_count / count
    S->>S: allocate _wrench_buf (spatial_vectorf)

    Note over S,B: _update_buffers_impl (each step)
    S->>V: read_into(LINK_INCOMING_JOINT_FORCE, _wrench_buf)
    V->>V: "_resolve -> TensorType"
    V->>V: "_binding(tt) -> cached TensorBinding"
    V->>V: _check_device(_wrench_buf, device)
    V->>V: _read_view(_wrench_buf, binding)
    Note right of V: First call: build float32 reinterpret,<br/>cache in _read_views[id(buf)].<br/>Subsequent calls: reuse cached view.
    V->>B: binding.read(float32_reinterpret_view)
    B-->>V: fills buffer in-place

    Note over S,B: _invalidate_initialize_callback
    S->>S: "_root_view = None (releases _read_views)"
    S->>S: "_wrench_binding = None"
    S->>S: "_wrench_buf = None (safe: reinterpret already released)"
Loading

Comments Outside Diff (2)

  1. source/isaaclab_ovphysx/isaaclab_ovphysx/sim/views/ovphysx_view.py, line 802-818 (link)

    P2 _read_views cache grows without eviction

    The cache maps id(dst) → reinterpret view and entries are never removed. For the current sensor usage (one reused _wrench_buf), this is a non-issue — the cache stays at size 1 for the view's lifetime. But OvPhysxView is a general-purpose class; a caller who passes a new structured dst on every call to read_into or get_attribute(out=...) will accumulate one dead entry per unique buffer object, keeping each float32 reinterpret (and by extension a raw pointer into the already-freed backing memory) alive in the dict indefinitely.

    A weakref-keyed eviction is the standard fix (weakref.WeakKeyDictionary doesn't work here because wp.array is likely not weak-referenceable, but a __del__-based sentinel or a size-bounded LRU would be sufficient). At minimum, a docstring note warning callers to reuse dst would make the expected usage pattern explicit.

  2. source/isaaclab_ovphysx/isaaclab_ovphysx/sensors/joint_wrench/joint_wrench_sensor.py, line 63-65 (link)

    P2 _wrench_binding is now only used inside _initialize_impl

    After this refactor, _wrench_binding is assigned from _root_view.binding_for(...), used only for the body_count/count guard, and then stored as an instance attribute that is cleared in _invalidate_initialize_callback — it no longer participates in the _update_buffers_impl guard (_root_view is None or _wrench_buf is None). Making it a local variable in _initialize_impl would remove the ambiguity about whether it signals initialization state. If it needs to stay on the instance for future callers or introspection, a comment explaining that intent would help.

    Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Reviews (1): Last reviewed commit: "Merge branch 'develop' into antoiner/fea..." | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation isaac-lab Related to Isaac Lab team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant