Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[Remote rendering 5.1] pvserver connectivity spike

未關閉
#33 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@ansBAkula 已經在處理了。

開始於 2026年9月11日。

評估

這個 Issue 還沒有評估資料。

描述

research
📝 Description of the feature

pvserver is a separate rendering process you connect to as a client, replacing the in-render window the spike used. This story is a timeboxed investigation to find out what integrating it actually takes, before committing to the implementation in 5.2. Backend-only. Open questions to answer:

  • How does RemoteRenderer connect to a pvserver process, and does the existing trame-rca streaming path still work unchanged once it does?
  • What happens to the session lifecycle now that rendering is in another process?
  • Do the per-part mutation triggers and VtkNodePipeline still work when the VTK objects live in pvserver's process rather than ours, or do they need to be marshaled across the boundary?
  • Does interaction (the interactor path, including the 4.5 workaround) change with pvserver in the loop?
  • Does any state, camera, per-part, need to be serialized/synced across the boundary that was previously just set directly?
  • How is pvserver packaged into the deployment environment?
Acceptance Criteria

A findings doc answering the above, enough to scope 5.2, including any gaps we didn't account for in Phase 4

💵 Business Value

No response

🔗 Useful links and references

No response

主要語言
Python
星號
1
分支
0
平均合併
1 天 23 小時
30 天內合併 PR
40

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

ansys/Visual-Interactive-Simulation-Object-Renderer 的其他 Issue

查看 ansys/Visual-Interactive-Simulation-Object-Renderer 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。