Search — hardware-integration

Request to support block_dim > 1 on CPU with CUDA-like block semantics, including shared tile state and barriers. Proposal suggests implementing cooperative fibers per block to preserve correctness while improving efficiency.

The kamino_mujoco_admm_solver example consistently warns about truncated contacts. The log indicates this happens in a typical setup (Warp 1.15.0 on A40), suggesting defaults or limits are easy to exceed.

ModelBuilder.add_particles() allows inconsistent array lengths across positions/velocities/masses/etc., producing an invalid model that still finalizes. This can yield non-finite state on CPU and potential out-of-bounds reads on CUDA; inputs should be validated before mutation and at finalize().

Examples that adjust ViewerGL camera speed fail because _cam_speed moved from ViewerGL to ViewerGUI in Newton v1.3.0. The example uses hasattr checks that no longer find the attribute, making small-scale scenes hard to view.

wp.quat_twist_angle() uses acos on the twist scalar component, which rounds to 1.0 in float32 near zero, producing a dead zone and discontinuity. Request is to stabilize behavior near zero and add a signed variant.

APIC capture of a padded bsr_set_transpose intermittently triggers heap corruption in CI (glibc free invalid next size) and AddressSanitizer reports a heap-buffer-overflow. The crash breaks the process pool and fails the job.

Isaac Lab flags an mgpu root-cause issue tied to the setting --/physics/fabricUseGPUInterop. The report is sparse, but it implies a problematic interaction between fabric GPU interop and multi-GPU usage.

Request to allow analytic ground planes to participate in hydroelastic (SDF) contacts so robots can rest on add_ground_plane without meshing the ground. The issue notes planes previously had HYDROELASTIC silently cleared and proposes threading plane support through broadphase and contact kernels.

Warp exports wp.bool arrays to DLPack using kDLBool (8-bit), but wp.from_dlpack() rejects the same dtype so boolean tensors cannot round-trip through DLPack on CPU or CUDA. This breaks expected interop patterns for masks/flags moving between frameworks.

A CUDA multiphysics example test intermittently fails a tight center-drift tolerance (0.06), passing on one CI run and failing on another with the same SHA. This points to nondeterminism or overly strict thresholds in a newly added example rather than a code regression.

Forum post reports Thor PCIe endpoint (EP) and EP XDMA communication failure. No details are provided, suggesting the user is blocked at bring-up/validation.

Forum post reports an Orin Nano HDMI problem. No body details are provided.

Forum post flags issues with Orin Nano PCIe and HDMI. No additional context is provided.

Forum post says changing the default UARTi baud rate fails on AGX Orin with JetPack 6.2. No details are provided.

Request to document how Warp behaves with non-blocking CUDA streams such as those borrowed from PyTorch. The goal is to avoid unexpected synchronization behavior when integrating Warp with external stream management.

Forum post mentions HSB FPGA IP for camera over Ethernet. With no body details, it reads as an inquiry about available IP/support for this pipeline.

Forum post asks about Jetson Thor camera over Ethernet and GPU Direct zero-copy DMA. No additional details are provided.

Bug report says RTL8168 Ethernet on Jetson Orin Nano Super intermittently negotiates at 100 Mbps instead of 1 Gbps on JetPack 7 (L4T R39.2.0). No further details are provided.

Forum post asks whether specific SODIMM pins can be configured as GPIO inputs/outputs. No additional context is provided.

Forum post asks if a 10G Holoscan Sensor Bridge can simplify high-bandwidth vision pipelines on Jetson. No details are provided beyond the exploratory question.

User wants to reuse a PWM controller currently used for pwm-fan for a custom application, indicating device-tree/service ownership friction.

Warp Adam/SGD can reuse optimizer state buffers from the wrong device when parameters are replaced with same shape/dtype on another device, potentially causing illegal memory access on CUDA.

Forum post titled “USB3.0 cable manual update voltage swing” provides no body details in the corpus. It likely concerns USB3 signal integrity/voltage swing settings and update procedures.

Forum post asks about HDMI support on the Jetson Orin Nano SOM, with no additional context provided. This indicates ongoing uncertainty about display-interface support at the module level.

Forum post titled “System throttled due to Over-current” has no body content in the corpus. It suggests the device is throttling due to over-current protection events.