<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>RL on rocPAI-Forge</title><link>https://rocpai-forge.github.io/en/tags/rl/</link><description>Recent content in RL on rocPAI-Forge</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 06 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rocpai-forge.github.io/en/tags/rl/index.xml" rel="self" type="application/rss+xml"/><item><title>When a Robot Arm Invents Its Own Grip: An RL Practice with OpenArm</title><link>https://rocpai-forge.github.io/en/posts/openarm-rl-grasp/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://rocpai-forge.github.io/en/posts/openarm-rl-grasp/</guid><description>&lt;p>&lt;video src="https://rocpai-forge.github.io/media/openarm-rl-grasp/play_overview_web.mp4" poster="/media/openarm-rl-grasp/play_overview.jpg" autoplay loop muted playsinline style="width:100%;border-radius:.6rem;">&lt;/video>&lt;/p>
&lt;p style="text-align:center;color:#888;font-size:.8rem;">总览回放 / Overview replay&lt;/p>
&lt;blockquote>
&lt;p>📖 This is the &lt;strong>concise version&lt;/strong> (~3 min). For the full engineering details (design decisions, algorithm / reward, diagnostics, reproduce commands), read the &lt;a href="https://github.com/rocPAI-Forge/tech-blog-pub/blob/main/PhysicalAI/openarm-rl-grasp/README-details.md">&lt;strong>deep-dive →&lt;/strong>&lt;/a>&lt;/p>&lt;/blockquote>
&lt;h2 id="unilab--joint-release">UniLab &amp;amp; Joint Release&lt;/h2>
&lt;p>&lt;a href="https://github.com/unilabsim/UniLab">UniLab&lt;/a> is a &lt;strong>heterogeneous robot-RL training
infrastructure&lt;/strong>: &lt;strong>CPU-parallel physics simulation&lt;/strong> (MuJoCo / Motrix) and &lt;strong>GPU policy
learning&lt;/strong> are coupled through a unified runtime and shared memory — instead of pinning
physics, rollout collection, and learning on a single GPU-resident simulation path. Tasks,
rewards, and backend selection are expressed as Hydra owner YAMLs; training goes through a
unified &lt;code>uv run train&lt;/code> / &lt;code>uv run eval&lt;/code> CLI covering PPO, SAC, TD3, APPO, and more.&lt;/p></description></item></channel></rss>