5.7.2. Input Files

A copy of the project file (.ftsim) is put in the Analysis directory when running the job using the Forte User Interface, but is not used. This serves as a reference if you later want to view the project settings as they existed when the runs were generated. A copy of the project file is also put into each Run directory. The project file in the Nominal directory will be the same as in the Analysis directory; but the project file in the parameter study Run directories will be modified differently in each Run directory to reflect the parameters to be used in each Run.

In addition to the project file, the chemistry mechanism files and fuel library file are extracted from the project and pre-processed so the Ansys Forte executable is completely ready to start. You will see chem.* (or the gas chemistry file you have named in your mechanism) and fuel_lib_* file and also xml.out and therm.dat (or the name of the thermodynamics file in the mechanism you are using).

If a restart file has been specified in the Forte User Interface, that file will have been copied to the Run directory and named selected.ftrst. If corresponding results files (.ftres files, .ftind index file) have also been specified, they are copied to the Run directory and also named selected.*. These files are copied to avoid any file contention issues if you are running parallel jobs. These copies are deleted from the Run directory once the job has completed.

Finally, you will see some job-control and status files. For a single run, you will see a file named PREPARED. For a parameter study, you will see PREPARED and SELECTED. These files are removed as the job runs and are replaced by other job-status files. The batch scripts look for these files to exist when determining whether to run Ansys Forte simulation in that Run directory. This allows multiple queues to work in parallel without re-running the same jobs.