The loop

Open, apply,colour, look

ParaView has one interaction and you will repeat it a few hundred times. Everything else is detail on top of it.

Open a file

VTK, EnSight, CGNS, OpenFOAM case directories, XDMF, plain CSV. The reader is chosen for you.

Press Apply

Nothing renders until you do. This catches everyone once, and then never again.

Colour by a field

Pick a scalar from the toolbar dropdown. This is usually the moment the data starts making sense.

The pipeline

Filters stack,and nothing is destroyed

Each filter takes a dataset and produces a new one. The original stays where it was, which is why you can try things.

The Pipeline Browser down the left is the whole mental model. Your file sits at the top; every filter you apply hangs beneath whatever was selected when you applied it. Select a different node and the next filter branches from there instead. Delete a branch and the ones above it are untouched.

Slice and ClipCut a plane through the volume, or throw away everything on one side of it. The first two filters anyone learns.
ContourExtract a surface at a constant value — an isosurface. Where a scalar field becomes a shape.
ThresholdKeep only the cells inside a value range, which is both an analysis tool and a way to shrink data.
Glyph and Stream TracerArrows on a vector field, and lines that follow it. How a velocity field stops being three scalars.
Scale

Built for datathat will not fit

ParaView is not a viewer that happens to handle big files. It was designed around them, and that shows in how it behaves.

Parallel by design

The rendering server runs under MPI, so it can spread one dataset across many processes.

Client and server split

The interface can run on your laptop while the data stays on the machine that produced it.

Time as a first-class thing

A time-series is one object with a timeline, not a hundred files you open one at a time.

The practical version of this: if a dataset is slow to interact with, apply Extract Subset or a Threshold first and build your pipeline against the smaller version. Swap the input back at the end once the pipeline is right. This is the single biggest speed-up available to a new user.

Repeating it

Every clickis a Python line

Tools · Start Trace records what you do as a script. This is how a one-off exploration becomes something you can run over a hundred timesteps.

TraceRecordclicks become a Python script
pvpythonReplayno window, on the machine
.pvsmOr savethe whole session, to reopen

Trace a session, save the script, then run it with pvpython on the machine holding the data. No window, no clicking, and it produces the same images every time. Save the session itself as a .pvsm state file if what you want back is the interactive setup rather than a batch job.

On a machine

ParaView isalready built

Nothing here needs compiling. Pick a machine, and these two commands put it on there.

hub://paraview

$ dxflow workflow create --identity paraview hub://paraview

$ dxflow workflow start paraview

Read it, then run itPrepaid and by the hour, on a machine that is yours about a minute after you ask.