I am exporting my data from Fluent in Ensight Case Gold binary format using location: Node. The data for multiple cluster runs is stored sequentially. However, the data from the first 1 s (i.e., the first run) visualizes correctly and smoothly, while the data from subsequent runs (at 2s) appears distorted or pixelated, as shown in the attached file.
first job data
data from subsequent jobs
Please share your data
Shared
Somehow downloading it as a .zip file results in a corrupted zip file, and I will not download each file individually.
Sorry about that, not sure why this happened, I uploaded a zip file at this link hopefuly it’ll work. Thanks!
drive-link-data
Timestep 3:
Timestep 4:
But this is coming from your data, ParaView is displaying it fine, its just how the data is.
I do not konw why your data is like this, what if you save it in other formats ?
The .cas and .dat files saved by Fluent after a run are all correctly visualizing. However, the problem, as far as I understand, is that the underlying mesh indexing or how the data is stored in the subsequent cluster runs is not consistent with the initial run’s geometry (the original .geo file). As you can see, timestep 3 marks the end of the first/initial run, and from 4 onward, there’s the subsequent cluster run.
So is this an issue in your data or how VTK/ParaView reads it ?
I think it’s how the data is being written/ being stitched order.
