Problems reading Ensight Case Gold file exported from Ansys Fluent

Hi,

I am running fluid dynamics simulations with ANSYS Fluent. I usually export the results to Ensight Case Gold in ASCII format and post-process them successfully in Paraview 5.13. However, when I try to export the results in binary format (still in Ensight Case Gold) to reduce their size, I can’t open them in Paraview, and I get these errors:

I saw that this topic has already been discussed on this forum.

Can you tell me if a solution to this problem has been found or implemented, or if I can just export the results in ASCII format?

Thanks!

Same answer as the other thread:

This will requires some contribution, either from a dev spending some time or from a someone funding the issue.
Do not hesitate to reach out to Kitware if you are interested by that.

https://www.kitware.com/

https://discourse.paraview.org/t/how-are-features-and-bug-fixes-incorporated-into-paraview/4735/3

Hi @enrisang, could you try out ParaView 6.0.0-RC1 and load the new EnSightGoldCombined reader plugin (Tools menu → Manage Plugins…). This is a new reader, perhaps it supports this file properly.

Hi @cory.quammen, thank you for your tip! I tried with ParaView 6 and actually succeeded in opening the Ensight Case Gold file. However, it only allowed me to load the geometry of the CFD domain; all the point arrays and the measured particles part were not loaded. These are the warnings/errors that I got:

@enrisang Found the solution for this if the problem you have is same.

@Trupenparikh Thank you! I tried your solution and was able to read Ensight Case Gold files in binary format. However, I still have the same problem when I also export particle history data:

I tried to change the file reader, using EnSight Gold Combined Reader in Paraview 6.0, but it didn’t work:

@enrisang No idea on this one. Maybe Chatgpt could help.

Hello! Even if this is a 1 year old topic, i figured i could follow up on this issue since i got the same problem and managed to resolve it. Apparently, the binary parser struggles with thread IDs higher than 65000 and yields this error. Changing the export format to ASCII worked for me, even if it inherently slowed the reader. Another possible solution could be changing the thread IDs to be lower than 65000.