ansys / ansys/Visual-Interactive-Simulation-Object-Renderer

[Remote rendering 4.2] Mode selection and remote entrypoint

Open
#27 0 comments 0 reactions 0 assignees View on GitHub
technical
Dominant language
Python
Stars
0
Forks
0
Avg merge
1d 10h
Merged PRs (30d)
37

Description

### 📝 Description of the feature

Allow VISOR to start in either LOCAL (default) or REMOTE mode.

Backend entrypoint allowing selection of RenderingMode is already in place from 1.3 (wired to a remote stub). This builds the frontend equivalent for the first time.

On mount, the app opens a probe connection to the Trame server, reads which mode it's in and branches: for remote it keeps that connection open and hands it to the remote path rather than reopening one, for local it closes the probe and lets the local path take over. Remote mode must not initialize or download the wasm binary. Both modes serve from the same bundle.

### Acceptance Criteria

Remote mode downloads no wasm binary (no .wasm request in the network tab).
Tests pass

### 💵 Business Value

_No response_

### 🔗 Useful links and references

_No response_

Contributor guide

Open the contributing guide

Research direction

Start at the app mount and the existing backend entrypoint for RenderingMode, then trace the Trame probe connection, remote handoff, and local wasm initialization. Run the project tests and verify that remote mode keeps the probe connection, while local mode closes it and remote mode makes no .wasm request.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, wasm
Domain
backend, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.