mapping-attributes

Map ovrtx attributes into user memory for zero-copy updates.

201|25|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/NVIDIA-Omniverse/ovrtx --skill mapping-attributes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mapping-attributes
Source: https://github.com/NVIDIA-Omniverse/ovrtx/tree/main/.agents/skills/mapping-attributes
Command: npx skills add https://github.com/NVIDIA-Omniverse/ovrtx --skill mapping-attributes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Zero-copy updates to ovrtx internal buffers by mapping attributes into user memory, eliminating unnecessary copies.

Core Features & Use Cases

  • Direct memory access for attributes to CPU or GPU memory.
  • Efficient per-frame updates in real-time simulations (e.g., transforms, sensor states).
  • Use Case: Update a mapped attribute every frame with minimal latency.

Quick Start

Map a target attribute into memory, write updates to the mapped tensor, and unmap to apply changes.

Frequently Asked Questions about mapping-attributes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable zero-copy memory mapping for ovrtx attribute updates?

Zero-copy memory mapping for ovrtx attributes is enabled by mapping target attributes directly into user memory, allowing you to write updates to the mapped tensor and unmap to apply changes without intermediate copies.

What is zero-copy attribute mapping and when should I use it?

Zero-copy attribute mapping provides direct memory access to CPU or GPU buffers. Use this technique for per-frame updates in real-time simulations where latency and bandwidth are critical, such as updating transforms or sensor data.

Do I need to know attribute properties before mapping ovrtx attributes into memory?

Yes, mapping ovrtx attributes requires knowledge of attribute properties including dtype, shape, and semantics. You also need a supported mapping target and must ensure proper synchronization during map and unmap cycles.

What's the best way to update simulation transforms every frame with minimal latency?

The best way to update simulation transforms with minimal latency is using zero-copy attribute mapping. Map the target attribute into memory, write transform updates directly to the mapped tensor, and unmap to apply changes per frame.

What synchronization limitations apply when mapping attributes to user memory?

The main limitation during attribute mapping is the requirement for proper synchronization during map and unmap cycles. Failing to synchronize memory access correctly can lead to data corruption or inconsistent simulation states.