1.2. Turbomachinery

The Turbomachinery analysis tool is designed to provide you with a smooth experience in the turbomachinery space. This tool is capable of analyzing the large majority of the common models, but has a few limitations. See Turbomachinery for more details on limitations.

  • Turbomachinery

    • The Turbomachinery features that imply creation of new EnSight variables or parts (Initialization, turbosurfaces creation, meridional creation, vectors on a 2D spanwise part creation) are not available on the Mac platform.

    • The Turbomachinery tool will fail on datasets that represent an entire 360 degree model (no periodic conditions in the direction perpendicular to the axis of rotation) and for which the components complete a rotation of more than 180 degrees.

    • The Turbomachinery tool is not enabled for EnSight in parallel (SOS) by default. To access the Turbomachinery feature, you will need to turn on the beta flag by setting the environment variable ENSIGHT_ANSYS_BETA_FLAG to 1.


      Note:  Each server will contain one entire turbomachinery component. Using a number of servers larger than the number of components will result in some servers remaining empty.


      Once the beta flag has been set and the data has been loaded in SOS, the turbomachinery tool will be able to run in the same way as on a single EnSight server. However, the performance will not be satisfactory. The computation time will not decrease with the number of servers, and might even increase in some circumstances. More work is needed to improve the performance of the tool in SOS.

    • Turbomachinery does not optimally perform in SOS, but should still work. However, if a model contains a fluid domain that wraps around itself more than 10 times, the turbomachinery tool will not be able to run initialization when the model is loaded in SOS.

    • Case linking is not supported with Turbomachinery and will fail when loading a second model within the same EnSight session that had Turbomachinery analysis applied to it via Case Linking or the Apply context from Case 1 feature.