[Core][IO] Implement EnSight 6/Gold output for simulation results

[loumalouomega]

📝 Description

Introduction

After what was discussed in last Kratos workshop, this PR introduces EnSightOutput, a new class for exporting simulation results to the EnSight 6/Gold file format. This implementation allows users to generate a complete EnSight dataset, including case, geometry, and variable files, enabling advanced post-processing and visualization with the EnSight software or other compatible tools like ParaView or Hyperview (reason why this format was chosen).

Source: https://fr.scribd.com/document/156786965/Ensight-File-Format-Manual

The generated output files have been successfully loaded and visualized in ParaView and Hyperview to confirm the correctness of the mesh geometry and the plotted nodal/elemental data.

The EnSightOutput class provides a comprehensive solution for writing mesh geometry, along with both nodal and elemental results. It is designed to handle transient simulations by tracking and outputting data at different time steps. The input is very simiar and compatible with the one used in the VtkOutput.

Key features

• EnSight 6/Gold compatibility: Generates standard .case, .geo, and variable files (.scl, .vec, .ten, etc.).
• Nodal and elemental/conditional data: Supports the output of variables defined at nodes and elements. It includes functionality to extrapolate results from integration (Gauss) points to nodes before writing.
• Transient analysis: Correctly handles time-dependent data by managing time step information within the case file.
• Flexible configuration: Output behavior, including file format (ASCII/Binary) and variables to be printed, can be controlled via the Parameters object.
• Structured & modular: The implementation is encapsulated within the EnSightOutput class, providing a clean interface for integration into the simulation workflow. The core logic is initiated by calling the PrintOutput() method at each desired step.

This feature significantly enhances the post-processing capabilities of the application by interfacing with a powerful, industry-standard visualization tool.

TODO

• Binary output to be corrected (right now it is a corrupt output)
• EnSight Gold implementation is done, but requires to implement the proper check and testing (requires to rewrite output check).

🆕 Changelog

• Changes to [Core] Add SkippableEntity method to InputOutputUtilities for geometry type checks #13716
• Changes to [Doc] Update VTKOutputProcess documentation #13850
• Add EnSight output functionality to Kratos
• Unit tests have been added to verify the file writing logic for different data types (scalar, vector) and mesh configurations
• Update the kratos/python_scripts/compare_two_files_check_process.py to support EnSight 6 files.
• [Add documentation for EnSight Process and imporove VTK Output Process]7061549)

[loumalouomega]

NOTE: Deploy will never work because these chanegs come from my fork, and I am not going to cherry-pick to a branch in Kratos because is to many commits.

[RiccardoRossi]

this is cool ... is it fast?

[loumalouomega]

this is cool ... is it fast?

Well, it is more or less like legacy VTK, not particularly fast.

[RiccardoRossi]

@sunethwarna @matekelemen you have a lot of experience with vtk output, can you take a look here in particularly to see if there can be some reuse of the vtu stuff?

[sunethwarna]

Thanks for this nice feature @loumalouomega . I have the following concerns before doing a thorough review.

• I would not put the format examples on the cpp, I think it is sufficient to have example files (which you have for testing) to know what the format looks like.
• I would reformulate the code such that, most of the code duplications can be removed by using templating or creating methods.

The cpp itself is 3k+ lines, I would reduce the number of lines by doing the above mentioned things.

[sunethwarna]

Another small question, does this support mpi ?

[loumalouomega]

Another small question, does this support mpi ?

No, sorry

[loumalouomega]

Thanks for this nice feature @loumalouomega . I have the following concerns before doing a thorough review.

* I would not put the format examples on the cpp, I think it is sufficient to have example files (which you have for testing) to know what the format looks like.

The problem is that there are different formats in here, the gold (7) and classic (6), and to actually implement without become crazy I think is relevant to have it there.

* I would reformulate the code such that, most of the code duplications can be removed by using templating or creating methods.

Which code duplications? (the data is written in a different manner depending of the data type, I cannot reuse code there)

The cpp itself is 3k+ lines, I would reduce the number of lines by doing the above mentioned things.

[loumalouomega]

Any advance on this?

[loumalouomega]

What is the status of this?