Six things it doesthat people miss
Most users learn open, apply, colour, and stop. These are the features that change what ParaView is for.
Render, spreadsheet, chart and histogram side by side, all showing the same pipeline object.
Pick cells in the 3D view and carry them into a table, a chart, or a new filter branch.
A directory of timestep files opens as one source with a timeline, not a hundred separate loads.
A shell inside the app, a trace recorder, and pvbatch for running the result with no window.
A grid of the same visualisation across parameter values, for comparing cases at a glance.
Run the server next to the data and the interface where you are. Only rendered pixels travel.
The render viewis one of many
Splitting the layout is how ParaView stops being a picture viewer and starts being an analysis tool.
Click a cell,then keep it
Selection is the bridge between looking at something and doing arithmetic on it, and it is almost invisible in the interface.
Select points or cells in the render view with the toolbar tools, and the Spreadsheet View narrows to exactly those rows. Extract Selection then turns that into a new pipeline object you can filter, export or plot over time. Plot Selection Over Time takes a selection and produces a chart of how those specific cells evolved — which is the answer to a surprising share of real questions.
Everything hereis scriptable
The interface is a front end onto a Python API, and anything you can click you can write down.
$ pvbatch --force-offscreen-rendering render.py
$ ls frames/
This matters more on a rented machine than on a laptop. Get the pipeline right interactively, trace it, then run the trace over every case with pvbatch and stop the machine. You pay for the render, not for the hours you would have spent clicking through a hundred datasets.
ParaView isalready built
Nothing here needs compiling. Pick a machine, and these two commands put it on there.
$ dxflow workflow create --identity paraview hub://paraview
$ dxflow workflow start paraview