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

[Remote rendering 4.2] Mode selection and remote entrypoint

Offen
#27 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
technical
Vorherrschende Sprache
Python
Sterne
0
Forks
0
Ø Merge
1 T. 10 Std.
Gemergte PRs (30 T.)
37

Beschreibung

### 📝 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_

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
python, wasm
Bereich
backend, frontend
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Aktiv
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
58/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.