[AdamAL]

Twice now, I have experienced ParaView not reading Fluent's Ensight Case Gold exports properly.

Simply no (cell) data is read. The table headers are read, and displayed in the Properties pane, but the Multiblock-block inspector only shows the file name (whereas for comparison other, working, exports show all the named zones). The information pane shows "NA" for all statistics (Type, Cells, Points, Mem), but the (unnamed) table at the bottom does show a table of [index, flowtime].

The first time this happened I thought it was because Fluent was terminated prematurely by the queue system, maybe leaving the last file in a garbled state. However, today, one prematurely terminated case, read just fine, while another that excited properly again showed the same behavior.

Any suggestions for the cause of this?

Any suggestions for how to save the data (GB's worth)?

[AdamAL]

Well, what do you know. I proceeded to try and make minimum (not) working example. And I discovered the .geo file was empty. 0B. So I copied the .geo from another (working) case, using the same mesh. This solved the issue. I still don't know what caused it.

Edit This is not a surefire solution, though. It just happened again, but this time, the new replacement .geo was either not adequately similar, or other data was corrupted too.

[wyldckat]

Greetings Adam,

This seems to be more of a problem with Fluent, than with ParaView.

I don't use (and never used) Fluent, so I have no clue on what can/should be done. The only things that come to mind is one of the following possible problems:

1. There might not be enough system memory (RAM) to perform both the simulation, save a backup of the results and export to another non-Fluent format.
2. There might be a connection issue (Ethernet, Infiniband or NFS) in the machine/cluster being used.
3. If it's a cluster or shared workstation, there might be a problem with user quota, where you're allowed only to write a limited number of files, size per file or of total disk space occupied.
4. There might be a time limit in using the cluster or shared workstation, e.g. 24h to run the simulations.

In the end, I suggest that you either check in the Fluent forum or with your system's administrator

Best regards,
Bruno

[AdamAL]

I investigated a bit further. It seems it was an issue with the Fluent case file. The second failure was from a slightly modified copy of the first. This case-file consistently output zero-size .geo files for the Ensight export. Removing the auto export, and adding a new one, rectified the problem.