Can't open large Ensight file on Windows 10

Hi,
I’ve a 89 gb ensight gold data (5 files; encas, scl1, scl2, scl3, vel, xml, geo) which I generated on ansys fluent. The data is transient (includes time steps). When I try to load it, it can see the point data in it but as soon as I click apply, it freezes presumably forever. After reading some of the discussions here I decided to try it on Ubuntu (WSL) and it loaded pretty quick.

Seems to be releated to the XML parsing error but it should’ve been patched on 5.12 and I am using 5.13.1.

What do you suggest? Does the XML fix also applies for ensight gold files?

Edit: I am testing a single variable ~15 gb (+ 500 mb .geo)

Can you share a data that reproduce the issue ? Even a smaller one that takes long on windows and not long on Linux ?

Does the XML fix also applies for ensight gold files?

It does not

Sorry for late reply, I was doing some test myself and found some interesting points. I opened the very same file in Ensight and exported it as ensight again. The converted file can be opened by ParaView without any issue.

Then I put the exported .case (it’s saved as instead .encas by Ensight) file among to the original files that I have issues with. I’ve just changed the file names of the rest as same as the ones saved by Ensight and voilà! It worked!

I’ve attached the case and xml files. Let me know if you still need all of the files, tho I don’t know if I can upload even a single variable (15gb) here.

“LesTransient.case” : Saved by Ensight and works on Paraview
LesTransient.case (10.2 KB)

“lestransient.encas”: Saved by Fluent and doesn’t work on Paraview
lestransient.encas (7.9 KB)

Well fluent and ensight are two different file format that do not use the same code path at all, but Im glad you found a work around.

Let me know if you still need all of the files, tho I don’t know if I can upload even a single variable (15gb) here.

If we want to ever fix the issue you potentially found in the fluent reader, then yes. You would need an external service to share big files indeed.

Although the software programs are different, they both export to the same ‘Ensight Gold’ format, which is what I used. Despite differences in file naming conventions between the programs for the Ensight Gold format, the files appear to be interchangeable.

So I used ensight reader on both as I suppose to. I will see if I can upload the files.

Thank you for your interest and quick replies.

Ha! I missed that!

Interesting indeed then! That is defintely an interesting point and may help for understanding the issue.

This is how the files look like. Since replacing “.encas” with the “.case” file I got from the Ensigh program makes the issue gone, I thought you may not need the whole data.

Note to others trying to read transient Fluent results in Paraview; I suggest everyone to set Fluent to export cgns at calculation runtime. Paraview seems to read cgns wayyy faster. I haven’t used it so I had I convert the results to ensight after the simulation run, converted those to cgns with Paraview (Ubuntu). Or you have to use ensight to fix your files so Paraview (windows) can read it if the issue haven’t been fixed yet.

Edit: I was refering to replacing .encas and .case files, not just the name

1 Like