'%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)
VisIt, for meshesthat outgrew the desk
Built for the largest simulations, and happy with small ones.Point it at the data where it landed, and explore it there.
$ dxflow workflow create --identity visit hub://visit --start --link
Every operator,nothing to build
The Ubuntu 22 build from the VisIt project, with every plot and operator in it.
Pick a plot, stack operators beneath it, and the pipeline rebuilds on every database you open.
Cut through the mesh, pull a subset out of it, and query the value at a point or along a line.
Iso-surfaces, transfer functions and ray casting over scalar fields, coloured how you like it.
Step through the cycles, keyframe the camera, and write the sequence out as frames or a movie.
Derive a new field from the ones you have, then drive the entire session from a Python script.
Structured, unstructured, AMR and point meshes, with material and species subsetting built in.
Every defaultis one override away
The session reads its settings from the environment, so you set them on the start line.
$ dxflow workflow start visit --override env.app.VNC_PASSWORD=something-long
$ dxflow workflow start visit --override env.app.PANEL=hide --link
Many windows,one browser tab
A Linux desktop in the tab, with the panel kept so windows can move.
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.
Ray casting over a large scalar field goes from a wait to a drag. A card turns the view interactive again.
The viewer, the GUI and the plot controls come up separately, which is why the panel is left on by default.
The whole session has a scripting interface. Derive an expression, set the camera, and run the same thing over every cycle.
Pulled once,then it stays
VisIt 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
VisIt asks for 4 cores and 8 GB. Cheapest first.