Skip to content

[Remote rendering 5.2a]: Plan paraview mode implementation #217

Open

Description

@LKasianAnsys

User Story Description

Using the spike in 5.1 as input, plan the work for the ParaView mode in VISOR

Acceptance Criteria

Break down the work for Phase 5 into user stories.

Additional Links

No response

Requires new or update to third party ? If "yes" add the name(s) and the version(s) of the Third Party Software.

No

Name and Version for Third Parties

No response

Activity

  1. self-assigned this
    on Nov 9, 2026
  2. LKasianAnsys commented on Nov 10, 2026

    @LKasianAnsys
    CollaboratorAuthor

    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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions