You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Remote rendering 5.2a]: Plan paraview mode implementation #217
Pulled the spike branch on the feat/bas-pvserver-trials branch of the Theia repo. Configured local environment (Windows) to run the POC and confirmed ParaView runs in Theia as expected.
Generated plan for Phase 5 of the remote rendering epic using copilot (Opus).
Task breakdown:
1. A developer, running the session standalone in pvpython, sees a single-part dataset rendered by pvserver in the browser and drives camera, diffuse colour and tree selection
increment 0. refactor: move streamed-render protocols out of server_renderer (S)
increment 1. feat: add the PARAVIEW mode, pvserver address and settings (M)
increment 2: feat: stream the PARAVIEW mode in the client (S)
increment 3: feat: render through a pvserver session and document the environment setup (L)
increment 4: add the PARAVIEW scene and session-side Visor (M)
2. Multi-part datasets render with per-part control; duplicate-named sibling blocks are refused with a clear error
increment 1: feat: map Visor parts to pvserver blocks
3. A user starts a PARAVIEW session through Visor's API or CLI against a configured pvserver, and gets a clear error naming host:port when it is unreachable
increment 1: feat: run the PARAVIEW session in a pvpython process
increment 2: feat: start PARAVIEW sessions from the API
4. PARAVIEW sessions save and load; unsupported operations are reported; the setup is documented
increment 1: feat: save and load PARAVIEW sessions and document their usage
5. (no user-visible change) The two streamed scenes (from SERVER mode and PARAVIEW mode) share one base
increment 1: refactor: share a streamed-scene base
Activity
LKasianAnsys commentedon Nov 10, 2026
Pulled the spike branch on the feat/bas-pvserver-trials branch of the Theia repo. Configured local environment (Windows) to run the POC and confirmed ParaView runs in Theia as expected.
Generated plan for Phase 5 of the remote rendering epic using copilot (Opus).
Task breakdown:
1. A developer, running the session standalone in pvpython, sees a single-part dataset rendered by pvserver in the browser and drives camera, diffuse colour and tree selection
2. Multi-part datasets render with per-part control; duplicate-named sibling blocks are refused with a clear error
3. A user starts a PARAVIEW session through Visor's API or CLI against a configured pvserver, and gets a clear error naming host:port when it is unreachable
4. PARAVIEW sessions save and load; unsupported operations are reported; the setup is documented
5. (no user-visible change) The two streamed scenes (from SERVER mode and PARAVIEW mode) share one base