CFX-Solver runs that include remeshing will have a slightly non-standard directory structure during execution. For example, using a CFX-Solver input file named case.def, a directory structure similar to the following will exist just after solution execution is interrupted and the second instance of remeshing begins:

case.def 
case_001/ 
      1_full.trn 
      0_full.trn 
      2_full.trn 
      3_oldmesh.res 
      3_remesh.out 
 case_001.dir/ 
      3_full.trn 
      4_full.trn res mon

The first instance of remeshing occurred when the solver was interrupted after the third time step. Following this instance of remeshing, all CFX-Solver Results files (such as transient, backup, and remeshing) contained in the run directory, case_001.dir, were moved into the final solution directory, case_001. The results file written when the solver was interrupted before remeshing was renamed to 3_oldmesh.res. Any text output to the console window during remeshing was redirected to the file named 3_remesh.out, which is also placed in the final solution directory.

The second, and currently running, instance of remeshing began when the solver was interrupted after the fifth time step. The results file written by the solver still has the generic name, res, and monitor data (contained in the mon file) has not yet been inserted into the results file.

Just after inserting the new mesh(es) into the analysis definition, the files contained in the final solution and run directories change slightly. The CFX-Solver Results and CFX-Solver Output files are renamed (to 5_oldmesh.res and 5_remesh.out, respectively) and moved from the run directory into the final solution directory. An automatically generated session file, meshUpdate.pre, is used by CFX-Pre to generate the updated the solver input file, 5_newmesh.def, and each of these files are present in the run directory. These files are, however, replaced or removed during the next instance of remeshing or when the analysis ends and the run directory is deleted.