Fluent variable nodal and elemental data

When reading in Fluent data into EnSight it is important to take note of where the variables are located.

Fluent data can be read in directly to EnSight from the .cas and .dat files.  The .dat file contains variable data as element (cell-based) data.  Fluent data can also be exported from Fluent into EnSight's .encas format with either nodal or elemental (cell-based) variable data.

In EnSight you can open the calculator and look at the variable names. Those with an (E) are located at the elements (cells) and those with an (N) are located at the nodes.

Nodal data
If you want nodal data, use Fluent to export nodal variable data to an .encas file.
This is because when Fluent exports the data to the nodes, it uses all of the information available to it, including boundary conditions and/or any internal constraints or additional interpolation information related to the solution data. If any of your filenames or paths contain a space " " then edit the .encas file and put quotes around the full path and filename in the .encas file.

EnSight can move variable data from the elements to the nodes, but do not do this.
When EnSight interpolates the element data to the nodes, it does a straight interpolation, thus losing the wall zero velocity boundary condition or any other internal constraint or additional interpolation information.

Element data
If a user wants element (cell-based) data, then exporting variables from Fluent as element (cell-based) or reading the CAS/DAT directly yields the same results.  Just do not move the variables from the elements to the nodes in EnSight!

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request