Turing Sim: Turning a UI Refresh into a Shareable Milestone
Situation
Turing Sim is an experimental OpenUSD editor and robotics simulation workbench. Its interface needs to keep the 3D viewport central while giving scene editing, inspection, and simulation controls a coherent place to live. The project also has a strict rule for interactive USD edits: they must enter the document command history so users can undo and redo them.
The project owner reported a much better interface after work with Claude Code. On September 27, the immediate need was to capture that work in a reviewable Git commit and make it available on GitHub. The commit includes more than visual changes, so this is a record of the milestone rather than a claim that every feature was built that day.
Task
The goal was to preserve the current application work without sweeping generated output into source control, check what could be verified headlessly, and synchronize it with the published repository. A second challenge was communicating the limits of that verification: the local Python environment does not include every binding used by the full desktop editor.
Action
The recorded changes establish a shared Qt design system with appearance modes, reusable controls, icons, and glass surfaces. The accompanying screenshot shows the newer glass treatment across the window chrome, dock tabs, panels, and viewport tools. The UI work also spans dock tabs, workspace layout, editor chrome, viewport controls, and robot panels. Separately, the commit adds a common runtime contract for Genesis and MuJoCo, a MuJoCo conversion path, and physics authoring through the undoable document command flow. These are distinct areas of work collected in one milestone commit.
The full headless test command completed with 372 passing tests and 14 skips. It also reported 12 failures and 3 errors. Several editor tests could not import pxr.Usdviewq; native schema subprocess tests crashed in the local macOS/OpenUSD environment. Those outcomes prevent a clean-suite claim and call for validation in the intended runtime. The generated MuJoCo warning log was left out of the commit.
GitHub authentication was refreshed. The remote repository had separate commit history but the same pre-change file tree, so the new commit was replayed onto the remote main and pushed without replacing its existing history. The resulting commit is 5881d6f.
Before and after: the interface
Earlier interface: flat charcoal panels and underlined tabs.
Current interface: glass surfaces and grouped controls around the viewport.
The earliest UI capture available for this comparison shows a flatter, mostly charcoal workspace: underlined Objects/Layers tabs, a fixed Inspector, and a small floating tool strip. The current capture shows blue-tinted glass around the viewport, capsule-shaped dock tabs and toolbar groups, a searchable scene tree, and more prominent floating viewport controls. The 3D canvas remains the visual center in both.
These screenshots use different selection and camera states. They illustrate changes in layout and visual language, not a controlled rendering-quality or performance comparison.
Result
The UI and simulation work is now recorded and available for review on GitHub. The design system documentation gives future panels a consistent visual vocabulary, while the engine adapter documentation lays out a path for comparable runtime checks. It explicitly treats benchmark numbers as unmeasured until the benchmark scripts are run and recorded.
The next validation step is to run the editor and schema checks in the supported macOS launch environment, investigate the observed failures, and record measured engine results before drawing performance conclusions.
Turing Sim:将界面更新整理成可分享的里程碑
背景
Turing Sim 是一个实验性的 OpenUSD 编辑器和机器人仿真工作台。界面需要让三维视口保持中心地位,同时清晰地组织场景编辑、属性检查和仿真控制。项目还有一条重要约束:交互式 USD 修改必须进入文档命令历史,才能可靠地撤销和重做。
项目负责人反馈,经过与 Claude Code 协作,界面已有明显改善。9 月 27 日的直接目标是把当前工作保存为可审查的 Git 提交,并同步到 GitHub。本次提交不仅包含视觉更新;提交日期并不能证明每项功能都是当天实现的。
目标与难点
这次需要完整记录应用代码,避免把生成的运行日志混入版本库,完成可在无界面环境运行的验证,并与已发布的仓库同步。另一个难点是准确说明验证边界:本地 Python 环境缺少桌面编辑器所需的部分绑定。
解决思路与行动
提交中的界面工作建立了共享的 Qt 设计系统,包括外观模式、可复用控件、图标和玻璃质感表面。配图展示了新版玻璃效果在窗口工具栏、停靠标签、面板和视口工具上的应用;还覆盖了停靠标签、工作区布局、编辑器工具栏、视口控件和机器人面板。另一部分工作加入了 Genesis 与 MuJoCo 的统一运行接口、MuJoCo 转换路径,以及通过可撤销文档命令进行的物理属性编辑。这些不同方向的改动被整理进同一个里程碑提交。
完整的无界面测试运行结果为 372 项通过、14 项跳过,同时有 12 项失败和 3 项错误。部分编辑器测试无法导入 pxr.Usdviewq;原生 schema 子进程测试在本地 macOS/OpenUSD 环境中崩溃。因此目前不能声称整套测试通过,仍需在目标运行环境继续验证。生成的 MuJoCo 警告日志没有纳入提交。
刷新 GitHub 登录后,发现远端仓库具有独立的提交历史,但变更前的文件树与本地一致。于是将新提交接到远端 main 的历史之后再推送,保留了远端已有历史。最终提交为 5881d6f。
初版与现在:界面变化
早期界面:深灰色平面面板与下划线标签。
当前界面:视口周围采用玻璃质感与分组控件。
目前能找到的最早界面截图以较平面的深灰工作区为主:Objects/Layers 使用下划线标签,Inspector 固定在右侧,视口中只有较小的浮动工具条。新版截图则展示了视口周围的蓝色玻璃质感、胶囊形停靠标签与工具栏分组、可搜索的场景树,以及更醒目的浮动视口控件。两版都把三维画布放在视觉中心。
两张截图的选择状态和相机视角不同,因此这里只比较布局与视觉语言,不据此判断渲染质量或性能。
结果与下一步
这批界面与仿真工作现已记录在 GitHub,供团队审查。设计系统文档为后续面板提供统一的视觉语言;引擎适配文档则定义了比较不同运行后端的方式。文档明确指出,基准测试数值仍需实际运行并记录,当前不能据此得出性能结论。
下一步是在受支持的 macOS 启动环境中验证编辑器和 schema,调查已观察到的失败,并在比较引擎性能前取得真实测量结果。


Top comments (1)