System overview

Scenaven splits the work in two. The server keeps your simulation, converts it, and runs filters and Python. The browser shows an interactive 3D view of the surfaces the server sends back.

VTK VTK
OpenUSD OpenUSD
Three.js Three.js 
┌─────────────────────────────────────────────────────────────┐
│  Browser                                                     │
│  3D view · scene tree · rendering · time controls            │
└───────────────────────────┬─────────────────────────────────┘
                            │ upload, filters, geometry
┌───────────────────────────▼─────────────────────────────────┐
│  Server                                                      │
│  Convert · filter · time · Python                            │
└───────────────────────────┬─────────────────────────────────┘
                            │
              ┌─────────────┴─────────────┐
              ▼                           ▼
        Cloud storage              On-prem storage

Why the work is split

Work Where it runs Why
Reading VTK files, clip, warp, extract Server The full simulation is often too large for a browser tab
Building the scene the viewer can load Server One description of the session, shared by the view and by Python
Camera, colors, probes, and the scene tree Browser These stay responsive because they do not recompute the simulation
Keeping the converted scene Cloud or on-prem storage The same viewer, with storage that matches where you run Scenaven

For what VTK, OpenUSD, and Three.js each contribute, see VTK, OpenUSD & Three.js. For why the view is drawn with Three.js rather than by running VTK inside the browser, see Why Three.js?.

What you work with

The viewer is the full-screen 3D view and the controls around it: the scene tree, rendering, filters, viewport settings, time controls, and dataset info. After you sign in, amAIra and the Python session sit on the right.

The server accepts VTK files (.vtk, .vtkhdf, .vtp, .vtu), turns them into a scene, applies clip, warp, and extract, and runs Python against the simulation you loaded.

The home page signs you in and opens that viewer with your session.

Cloud and on-prem

The same viewer and the same conversion run in both places. What changes is where the files live and which features your connection allows.

Mode Storage Typical use
Cloud Hosted storage A preview on Examples, so always-on compute stays limited. Uploads, filters, Python, and amAIra run on-prem; hosted cloud with those tools follows feedback from that use
On-prem Disk on the machine running Scenaven Your own files, inside your network
Cloud Cloud
On-prem On-prem

Related topics