The Export Options tab allows you to specify the root directory, file names, and CAE formats to be used when exporting the high-order mesh.

Grid, Elevate, Export Options Tab
The Export Options tab provides controls for specifying the CAE formats and file locations to be used during high-order export.

All settings on the Export Options tab are contained in a single frame, the Formats frame. Root Directory specifies the root directory to be used for export. The text field is read-only and displays the full path to the Root Directory. Use the folder selector button to change the location of the Root Directory. The default location for the Root Directory can be one of three locations:

  1. The directory specified by the PWI_EXPORT_CAE_DIR environment variable.
  2. The directory in which the PW file is saved (if a PW file has been opened/saved)
  3. The most recently used export directory.

Note: Some CAE solvers have restrictions on the types of high-order meshes that are supported. For example, the Kestrel format only supports uniform Q2 high-order meshes and does not support Q3, Q4, or mixed order meshes. It is a good idea to check which types of high-order meshes your solver supports before exporting a high-order mesh from Fidelity Pointwise.

Below the Root Directory are checkboxes for each of the CAE formats that support high-order export (CGNS, Gmsh, and Kestrel). There is also an additional format, VTU, which can be used with ParaView to visualize high-order elements. Check the box next to a format to specify that the high-order mesh be exported to that format. Multiple formats may be selected, however, the CAE types specified in the CAE, Set Boundary Conditions panel will only be set for the format specified by the CAE Solver. All other formats will have their boundary condition CAE types set to Unspecified. By default, a format is selected if it matches the current selected CAE Solver (which can be viewed in the Status Bar).


Caution: When exporting to a CAE format that is not the format selected in CAE, Select Solver the boundary condition CAE types in the exported file are set to Unspecified. Depending on the CAE solver, you may need to manually edit the boundary conditions in your exported file before you are able to import the mesh into your solver.

The default root file name is either taken from the PW file name (left) or has a generic default value if no file has been opened (right).

To the right of each format name is an editable text field showing the file name to be used for exporting that format. By default, all formats use a common root name taken from the PW file name. Otherwise, if it is a new session of Fidelity Pointwise and no files have been opened or saved, it is set to a generic value HO_Export. You can also include a relative path from the Root Directory when specifying the file name for more organizational control over the exported files. Hovering over each text field displays a tooltip with the full path for the file.


Tip: If you want more control over the organization of your exported files, you can specify relative paths from the Root Directory in the file name text fields. For instance, you may want to specify separate sub-directories for each polynomial degree (Q2, Q3, and Q4). Just remember that these sub-directories must all exist before you export the mesh!

Hovering over the file name text field for a format displays the full path for the exported file.

The Restore Solver Defaults button can be used to restore the Root Directory, all format checkboxes, and all format file names to their default settings.


Tip: The settings on the Export Options tab persist after exiting the Elevate task. That is, if you export a high-order mesh then exit the Elevate task and change the CAE Solver, when you re-enter the task the CAE format selections and file names will still be set as they were the last time you were in the task. In this case, you can use the Restore Solver Defaults button to quickly pick up the change in CAE Solver. (Note that file operations, such as New, Save and Open, automatically trigger the defaults to be restored.)