Difference between revisions of "Visualizing AWP-ODC Output"
| Line 26: | Line 26: | ||
== Create traces == | == Create traces == | ||
| + | Often, other visual references are needed to make the visualization meaningful. The approach outlined uses a Cartesian grid projection to display the velocity results. This means that to display other data, we have to convert the data from (lat, lon) into (X index, Y index). | ||
| + | |||
| + | To do this, use the code get_grid_values.c . | ||
| + | |||
| + | <pre> | ||
| + | |||
| + | </pre> | ||
== Use local Paraview to connect to remote nodes == | == Use local Paraview to connect to remote nodes == | ||
Revision as of 18:32, 23 April 2018
This page documents a procedure to visualize AWP-ODC velocity output, using remote Paraview. So far, this procedure has only been tested on Titan using Paraview 4.4.0.
Contents
Configure the simulation
When running the AWP-ODC simulation, make sure it is configured to produce velocity output.
Take note of the following parameters:
- NX, NY, NZ (and NBGX, NEDX, NGBY, NEDY, NGBZ, NEDZ if specified)
- WRITE_STEP
- NSKPX, NSKPY, NSKPZ
- NTISKP
They'll be needed when producing the output.
Create a Paraview XDMF file
Once the simulation is complete, we must create a configuration file which tells Paraview how the velocity data is laid out in memory.
For this, run the script create_timeseries_file.py.
Usage: ./create_timeseries_file.py <X dim in output> <Y dim in output> <grid decimation> <NT in sim> <DT of sim> <NTISKP> <timesteps output per file> <prefix> <output file>
Based on this, a XDMF (XML) file is produced which can serve as input to Paraview.
Create traces
Often, other visual references are needed to make the visualization meaningful. The approach outlined uses a Cartesian grid projection to display the velocity results. This means that to display other data, we have to convert the data from (lat, lon) into (X index, Y index).
To do this, use the code get_grid_values.c .
