'%20d='M364.9%20143.2v98.9l-1.4%201.2-165.6%20140.4%2035.7%2029.7v-34.2l1.4-1.2%20123.4-105.4%206.5-5.6v37l-1.3%201.2-99.7%2085.8v84.7l-6.6-5.7-97-83.1-3.6-3%203.5-3%20174.4-150.6v-25.1L153.7%20360.5l-6.6%205.7v-98.9l1.4-1.2%20161.6-138-35.7-29.7v34.4L273%20134%20153.7%20236.7l-6.6%205.7v-37l1.3-1.2%2097-83.2V36.3L252%2042l97.1%2083.1%203.6%203-3.6%203-171.7%20147.7V304l106.2-90.6%2056.4-48.8%2018.3-15.7z'%20/%3e%3c/svg%3e)
ParaView, wherethe results already are
A 200 GB result should not have to move to be seen.Render it on the machine that wrote it, and watch in a tab.
$ dxflow workflow create --identity paraview hub://paraview --start --link
Every filter,nothing to install
The MPI build with Python 3.10, and every filter that ships with it.
Chain a reader, a filter and a view. Point that chain at your next case and it all runs again.
Cut a plane through the volume, throw half of it away, and read the value at any single point.
Iso-surfaces, transfer functions and ray tracing over 3D fields, coloured however you want it.
Step through the timesteps, set a camera path, and write it out as frames or a finished movie.
Trace what you clicked, then replay that script headless with pvpython across a hundred cases.
Structured and unstructured meshes, point clouds, polygonal data and volumes, in one pipeline.
Every defaultis one override away
The session reads its settings from the environment, so you set them on the start line.
$ dxflow workflow start paraview --override env.app.VNC_PASSWORD=something-long
$ dxflow workflow start paraview --override env.app.TASKBAR=show --link
One tab, andthe app fills it
A Linux desktop streamed to your browser, with ParaView already maximized.
It renders on the CPUuntil you give it a card
Software OpenGL carries the view by default, which is enough right up until the dataset is not.
Volume rendering and ray tracing over a heavy mesh go from a wait to a drag. A card turns the view interactive again.
A large dataset is a memory problem first. Give the step room to hold the mesh before worrying about the frame rate.
Python 3.10 is in the build. Record what you clicked, then run it headless with pvpython over every case you have.
Pulled once,then it stays
ParaView arrives as one image. This is what comes down the first time, and what the disk should have free for it.
What it wants,and what it needs
The definition asks for 4 cores and 8 GB. The image comes up on less than that, and a start given --fit trims the ask to whatever the machine actually has.
Machines that fit it
ParaView asks for 4 cores and 8 GB. Cheapest first.