DNS 1-2 Storage Format: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
= Storage Format = | = Storage Format = | ||
The mesh is stored in <code>.pyfrm</code> format and the snapshots | The mesh is stored in <code>.pyfrm</code> format and the snapshots in <code>.pyfrs</code> format. | ||
A given solution snapshot | A given solution snapshot can be combined with the mesh file to create an associated <code>.vtu</code> or <code>.pvtu</code> file using the <code>pyfr export</code> command as detailed in the PyFR [http://pyfr.readthedocs.io documentation]. The converted files can be interrogated using the [https://vtk.org VTK library] or [https://www.paraview.org Paraview]. | ||
The profiles of different statistics and Reynolds stress budgets for the channel flow case are available in <code>.h5</code> format which can be accessed using [https://hdfgroup.org/solutions/hdf5 HDF5 library]. | |||
Revision as of 09:37, 30 August 2022
Storage Format
The mesh is stored in .pyfrm format and the snapshots in .pyfrs format.
A given solution snapshot can be combined with the mesh file to create an associated .vtu or .pvtu file using the pyfr export command as detailed in the PyFR documentation. The converted files can be interrogated using the VTK library or Paraview.
The profiles of different statistics and Reynolds stress budgets for the channel flow case are available in .h5 format which can be accessed using HDF5 library.
Contributed by: Arun Soman Pillai — Imperial College London
© copyright ERCOFTAC 2024