Streamlines
Use the Streamlines tool to generate streamlines using any available nodal or elemental vector field (typically a velocity field).
HyperView has a direct reader of EnSight files, thus allowing post-processing of typical CFD results from a large class of industry practices. The EnSight reader has been enhanced to support particle data (for example, modeling of dust particles in a flow) existent in a data set which can be animated; as well as transient data, including mesh deformation (for example, sliding mesh and ALE). The EnSight file type (*.encas, *.case) is available in the Files of type drop-down menu, located in the Load Model File or Load Results File selection dialog. In addition, Ensight files produced by SC/Tetra and other CFD solvers (for example, AcuSolve, Fluent, etc.) can also be loaded into HyperView by selecting the Auto option from the drop-down menu located in the Reader Options dialog. A separate SC/Tetra Ensight files option is also available for loading SC/Tetra files only (see the CFD Ensight Reader topic for additional information).
Saving EnSight files with Fluent
- With Fluent 6.*: select File/Export, select EnSight Case Gold as the File Type, then select the functions that you would like to export/post-process with HyperView (for example, Static Pressure and Total Pressure), leave the default options set at Node and Binary, and click Write to export the set of EnSight files.
- With Fluent 12.*: select File/Export/Solution Data…, select EnSight Case Gold as the
File Type, then select the Quantities that you would like to export/post-process with
HyperView (for example, Static Pressure and Total
Pressure), leave the default options as Node and Binary, and click Write to export the
set of EnSight files.Attention: By default Fluent will save the volume and boundary groups/components, therefore you do not need to select any Interior Zones. In Fluent, interior zones do not refer to the volume zones but instead refer to all of the faces (in 3D) between each pair of cells. It is very unlikely that you will ever need them, as they are used by Fluent for the solution process, and they are not needed for post-processing (as their numbers are so large that it will slow down your post-processing tasks considerably).