2.12 Understanding the File Structure for FLUENT in Workbench

When you save a Workbench project (e.g., my-project), the project is saved with a .wbpj extension (e.g., my-project.wbpj). Other files associated with the project (through other Workbench applications such as ANSYS FLUENT or ANSYS CFX) are located in the dp0 folder within a _files folder (e.g., my-project_files).

Each system in the Project Schematic has its own directory under the dp0 directory. The directory is named using the corresponding system identifier (e.g., FFF represents a FLUENT-based analysis system; FLU represents a FLUENT-based component system; Post represents a Results component system, etc.). The directory name is appended with a number to distinguish it from the directories for other systems of the same type (with the exception of the directory name for the first system of a specific type which has no number appended to it).

Within each system directory is a folder for each application that is part of the system. This folder is used to store the files generated and used by the application.

In addition to the settings, case and data files, the following files are managed by FLUENT in Workbench:

• monitor files

• flamelet files

• view factor files

• non-premixed files ( .pdf)

• interpreted user-defined (UDF) files

• compiled UDF libraries

• Discrete Transfer Radiation (DTRM) .ray files

• mechanism files ( .che or .inp)

• property database files ( thermo.db and transport.db)

You may use other types of files with FLUENT in Workbench, however, you are responsible for making sure that they are located in the appropriate folder within the project file structure.

The following figure represents an example of the directory structure for Workbench project with two Fluid Flow (FLUENT) systems and one Results system:

Figure 2.12.1: Example of the Directory Structure for a FLUENT-Based Project in Workbench

You can view the files associated with your Workbench project by selecting the Files option under the View menu.

View $\rightarrow$ Files

Figure 2.12.2: The Files View for a Project in Workbench

If data is shared between two systems, then files are also shared between the two systems. The shared file will exist in either the directory of the first system that used it, or in a global directory in the design point directory (depending on the type of system that generated the file).

The _files folder also contains a user_files directory. This directory should be used for any files you create or reference that you would like to store with the project.

In general, you should not modify the structure of the project directories or delete or modify any of the files that Workbench applications have stored in the project directories. However, you may delete FLUENT case and data files that are stored with the project but are no longer needed. You should close FLUENT before deleting FLUENT case and data files from the project directories.

Monitor files are automatically written to the appropriate working directory within the Workbench project files directory. You will not be able to specify a different path for monitor files from within FLUENT. When reading older case files in which a different location is specified for monitor files, a warning message will inform you that the path will be modified.

If you intend to use a FLUENT journal file that reads or writes files while running under Workbench, the journal file and the files it references should be moved to the appropriate FLUENT folder in the appropriate system folder in the Workbench project working directory. File paths in the journal files should use relative paths to point to the new locations for the files.

If you use models that generate mesh-dependent information the first time they are set up (e.g., DTRM, S2S) and then you change the mesh used in your system, the mesh dependent information (e.g., .dtrm file, .s2s file) may be incompatible with the new mesh. To resolve this issue, you can: Open FLUENT from your system, compute/write the .dtrm or .s2s output files, and then update the system. Use a solution strategy and write the .s2s file as a pre-initialization method using the appropriate command (e.g., (write-sglobs "2d.s2s.gz")).

If your FLUENT setup involves compiling and loading a user-defined function (UDF), it is recommended that you copy the UDF source code files to the same location as your mesh and settings files before compiling the UDF libraries. This location is available in the Files view in Workbench. You may need to save the project first to create the appropriate files folder within the Workbench project (e.g. <project name> $\backslash$dp0 $\backslash$FFF $\backslash$Fluent $\backslash$). If you need to unload a UDF library for any reason during your simulation, it is recommended that you save the project soon after unloading the library. If you archive a project that includes compiled user defined functions, you will need to recompile the libraries after opening the archived project. To do so, you will need to open FLUENT from the Setup cell, go to the UDF Library Manager dialog ( Define $\rightarrow$ User Defined $\rightarrow$ Functions $\rightarrow$ Manage...) and unload the existing UDF library. Next, rebuild the UDF library locally by going to the Compiled UDFs dialog ( Define $\rightarrow$ User Defined $\rightarrow$ Functions $\rightarrow$ Compiled...), selecting the archived .c and .h files, compiling, and loading the new UDF library. Finally, save the project.