[Remote rendering 5.1] pvserver connectivity spike
@ansBAkula is already working on this.
Since Sep 11, 2026.
Assessment
This issue has not been assessed yet.
Description
📝 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
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 47
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ansys/Visual-Interactive-Simulation-Object-Renderer
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
Library updates Opentechnical
ansys/Visual-Interactive-Simulation-Object-Renderer#136 · 1 assignee ·
-
maintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#131 · 1 assignee ·
-
Release 1.0.2 Openmaintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#130 · 1 assignee ·
-
enhancement
ansys/Visual-Interactive-Simulation-Object-Renderer#126 · 1 assignee ·
All issues in ansys/Visual-Interactive-Simulation-Object-Renderer
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
instance instance add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
searxng/searx-instances#939 · 1 comment ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100