15.4.1. File Naming Conventions

During the run, the flow solver writes the mesh and the solution data to the temporary run directory using the following naming conventions:

<prefix>_mesh.cgns mesh file

<prefix>_<timestep>.cgns solution file

where:

  • <prefix> is the filename prefix. By default, this is set to the export results object name. The default can be overridden by you during preprocessing.

  • <timestep> is the timestep number. This is a six-character string containing the timestep number. The string is formatted and right justified. For example, 000010, 000020, 000030, ... This enables files to show up in order when displayed using a directory listing. It also makes batch postprocessing the files easier.

At the end of the run, the files are stored in a saved version of the temporary directory called:

<filename>_<run number>

where <filename> is the basename of the CFX-Solver input file or results file from which the run was started and <run number> is the three character string indicating how many runs have been performed for this case. The run number is accumulated across restarts so that directories over a sequence of two or more runs might be labeled:

lescylinder_001/, lescylinder_002/, lescylinder_003/, ...

where the flow solver, in this case, was originally started using a CFX-Solver input file named lescylinder.def. For each run, an independent set of CGNS files will be stored separately in each directory.

15.4.1.1. Important Notes

  • The flow solver makes no attempt to keep track of previously written source files across restarts. Files are simply written out during each run and it is up to you to keep track of the sequence.

  • The mesh data is written only once at the beginning of the run to minimizes the data output. For rotating dipole results, the normal area vectors are also stored in the initial mesh file.