3.16.2. Creating Automatic Export Definitions for Transient Particle History Data

To create an automatic export definition for particle history data, begin by making sure that Unsteady Particle Tracking is selected in the Discrete Phase Model dialog box. Next, click the Create button under the Automatic Export selection list in the Calculation Activities task page (a drop-down list will appear). Select Particle History Data Export... from the drop-down list to open the Automatic Particle History Data Export dialog box (Figure 3.10: The Automatic Particle History Data Export Dialog Box).

Figure 3.10:  The Automatic Particle History Data Export Dialog Box

The Automatic Particle History Data Export Dialog Box

Then perform the following steps:

  1. Enter a name for the automatic export definition in the Name text box. This is the name that will be displayed in the Automatic Export selection list in the Calculation Activities task page. Make sure that the chosen name is not already used for another Automatic Export.

  2. Choose the File Type you want to export by selecting one of the following:

    • CFD-Post for the CFD-Post compatible format

    • FieldView for the FIELDVIEW format

    • EnSight for the EnSight format


    Important:  If you plan to export particle data to EnSight, you should first set up an automatic export definition so that solution data is also exported to EnSight during this calculation (see Creating Automatic Export Definitions for Solution Data). As described in the steps that follow, some of the settings must correspond between the two automatic export definitions.


  3. Select the predefined injections that are the source of the particles from the Injections selection list. See Creating and Modifying Injections for details about creating injections.

  4. Select the particle variables contained in the export file by clicking the Exported Particle Variables... button and selecting the variables appearing in the Reporting Variables dialog box (Figure 23.46: The Reporting Variables Dialog Box), as described in Reporting of Current Positions for Unsteady Tracking.

  5. If you have added the Color by variable in the Reporting Variables dialog box, select an appropriate category and variable under Quantity for the particle data to be exported.

  6. Set the Frequency at which the particle history data will be exported during the calculation. If you enter 10 in the Frequency text box, for example, a file will be written after every 10 time steps for transient flow cases or 10 DPM Iterations for steady flow cases.

  7. If your exported particle history file is too large to postprocess because there are too many tracks or particles written to the file, you can reduce the number of particle tracks by increasing the Skip value.

  8. If you selected EnSight Case Gold for the File Type, the Separate Files for Each Time Step option allows you to specify that separate files are written at the prescribed time steps. This option is enabled by default and is the recommended practice, as it ensures that all of the data is not lost if there is a disruption to the calculation (for example, from a network failure) before it is complete. If you choose to disable this option, all of the data for the .mscl and .mpg files will be combined into a single file for each.


    Important:  The setting for the Separate Files for Each Time Step option should be the same (that is, enabled or disabled) as that of the automatic export definition you set up to export solution data to EnSight during this calculation. For details, see Creating Automatic Export Definitions for Solution Data.


  9. Enter the name (and folder path, if you do not want it to be written in the current folder) for the exported particle data file in the Particle File Name text box. Alternatively, you can specify it through the Select File dialog box, which is opened by clicking the Browse... button. Make sure the file name is different from other existing Automatic Export definitions to avoid overwriting data.

    If you selected FieldView under File Type, you can write particle history data for each time step to separate files by including the character string %t in the particle file name. At the time of export, Fluent will substitute %t with the current time step. The saved files can be processed by FieldView 14 or newer.

  10. If you selected EnSight under File Type, you should specify the EnSight Encas File Name. Enter the same name (and folder path, if necessary) that you entered in the File Name text box when you set up the automatic export definition for exporting solution data to EnSight during this calculation. (For details, see Creating Automatic Export Definitions for Solution Data). The .encas file created during the solution data export will be modified and renamed as a new file that contains information about all of the related particle files that are generated after every time step during the export process (including geometry, velocity, scalars, particle and particle scalar files). The name of the new file will be the root of the original .encas file with .new appended to it (for example, if the solution data export creates test.encas, a file named test.new.encas will be written for the particle data export). It is this new file that should be read into EnSight.


    Important:  If you do not specify an EnSight Encas File Name, you will have to manually create an appropriate .encas file.


  11. Click OK to save the settings for the automatic export definition.

The particle data will be exported as it is generated during the transient calculation. If you selected EnSight under File Type, data files will be written in both .mpg and .mscl formats.


Release 18.2 - © ANSYS, Inc. All rights reserved.