Data flow

These are the paths behind the main actions: opening a file, filtering, extracting, reading dataset info, opening an example, and playing time. For what VTK, OpenUSD, and Three.js each do along the way, see VTK, OpenUSD & Three.js.

Opening a file

You click Open and choose a file
    → the browser uploads it to the server
    → the server converts it and stores the scene
    → the browser fetches the surface for this session
    → the mesh appears, and the scene tree shows the source
Upload Upload
Scene Scene
View View

What you see

  1. The sidebar footer may show Cloud conversion or Local conversion with a progress bar.
  2. When that finishes, the view draws the surface and the Scene card lists the source.
  3. Scalar fields show up in the Rendering card once their names and ranges arrive.

.vtp and .vtu files follow the same path. You upload VTK. The server writes the scene the view loads.

Applying a filter

You edit warp or clip in the sidebar
    → the viewer sends the settings to the server
    → VTK runs on the simulation you loaded
    → the new surface is added to the scene
    → the scene tree gains a child (Clip, Warp, …)
    → the view refreshes

What you see

  • A message such as *Applying clip filter* or *Applying warp filter* may cover the view while the server works.
  • The new row appears under the source in the scene tree.
  • Select the child to look at that result, or use the eye icon to compare it with the source.

With Show clip plane in viewport on, you can drag the plane in the view. The server applies the new position when you release the drag.

Extracting cells or points

You drag a region and choose Extract cells or Extract points
    → the viewer sends the selection to the server
    → the server runs the extract
    → a new row appears in the scene tree

Extract needs a connected server and a volume you have loaded. The tools stay off until a mesh is ready.

Dataset info

You select a scene-tree row and click VTK dataset info (ℹ️)
    → the viewer asks the server about that object
    → the panel shows point and cell counts, fields, cell types, bounds, and time

Dataset info is available with uploads and filters: on-prem today, and on hosted cloud after that feedback. The cloud preview does not include it. See Cloud connection.

Opening an example

You pick an example in the gallery
    → the server opens a prepared dataset (nothing is uploaded)
    → the view loads it the same way as a file you opened
    → the scene tree shows that example as the source

Examples are datasets Scenaven already has on the server, for cloud and for a new on-prem install.

Playing time

The dataset has more than one time step
    → the viewer reads the list of steps
    → time controls appear at the top of the view
    → step or play asks the server for each frame
    → an active clip or warp is applied again for that step

If clip or warp covers the whole series, the first Play can show Building animation… while the server prepares the frames. See Time animation for playback and that wait.

What stays quick

Action Where it runs
Orbit, pan, zoom Browser
Colormap, opacity, display style Browser
Point and cell probe readouts Browser, from field values already loaded
Upload, convert, clip, warp, extract, Python Server

Moving the camera and changing color are immediate. Uploads and filters show progress because the server is doing the work.

Related