Is your feature request related to a problem? Please describe.
Not related to a problem, but the integration of f4e_cdgs_utils would expand F4Enix's capabilities.
Describe the solution you'd like
As the title says, integration of f4e_cdgs_utils capabilities into F4Enix and a review of the implementation.
Describe alternatives you've considered
There are no alternatives.
Additional context
In the current implementation of the f4e_cdgs_utils, there is a bug related to the ordering of mesh indexes. While the PR#31 solved the problem for generation of CDGS, it has broken the capability to write VTKs. My suspicion is that order="F" in fluent_to_reg_mesh.py is needed to write VTK, while order="A" works for CDGS. This would probably have to be solved in the implementation.
Is your feature request related to a problem? Please describe.
Not related to a problem, but the integration of f4e_cdgs_utils would expand F4Enix's capabilities.
Describe the solution you'd like
As the title says, integration of f4e_cdgs_utils capabilities into F4Enix and a review of the implementation.
Describe alternatives you've considered
There are no alternatives.
Additional context
In the current implementation of the f4e_cdgs_utils, there is a bug related to the ordering of mesh indexes. While the PR#31 solved the problem for generation of CDGS, it has broken the capability to write VTKs. My suspicion is that order="F" in fluent_to_reg_mesh.py is needed to write VTK, while order="A" works for CDGS. This would probably have to be solved in the implementation.