Fluent Transient Particle Data (DPM) Post Processing on Paraview (5.10.1)

Hi,

I have run a transient Ansys Fluent simulation involving a Discrete Phase Model - particles injected into the system. This case was set up in Ansys Fluent and (under the heading of calculation activities) have exported both Solution Data Export and Particle History Data Export in Ensight Case Gold and Ensight format respectively. This case was run on a HPC.

The simulation then as a result produces two .encas files namely a result.encase and a result.new.encase file along with case and data files,.mscl, .mpg, .scl, .vel and a .geo file.

When I read either .encase file into paraview, an initial error appeared where it could not read the file. I researched and found that this is due to the “” around the strings in the .encas model and then also deleting the last two lines in the .encase file. I’m at the stage where the .encas file will load into paraview but the .new.encase won’t load into paraview and leaves the following errors:

ERROR: In vtkEnSightGoldBinaryReader.cxx, line 1274
vtkEnSightGoldBinaryReader (000001962FA44890): This is not a binary data set. Try vtkEnSightGoldReader.

ERROR: In vtkEnSightReader.cxx, line 374
vtkEnSightGoldBinaryReader (000001962FA44890): error reading measured geometry file

ERROR: In vtkExecutive.cxx, line 730
vtkCompositeDataPipeline (000001962DB55050): Algorithm vtkEnSightGoldBinaryReader (000001962FA44890) returned failure for request: vtkInformation (000001962ED9EE80)
  Debug: Off
  Modified Time: 110211729
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA
  FORWARD_DIRECTION: 0
  ALGORITHM_AFTER_FORWARD: 1
  FROM_OUTPUT_PORT: 0

I have used the Ensight Case Reader.

Any help, advice or feedback would be greatly appreciated. I have scoured the internet trying to find a solution.

Many thanks in advance,

Emma

Please share your data.

Hi Mathieu,

Thank you so much for getting in touch!

I have close to 100 gb of data across all the formats above, which would be a huge file to upload here! Which files are the ones of interest?

Many thanks

Emma

Please share a smaller file that have the same issue.

Without data, the issue cannot be reproduced and that makes it very hard to help you I’m afraid.

With your data I get:

 vtkPGenericEnSightReader (0x5fcb4fd2c870): Unable to open file: /home/glow/data/tmp/paraview.geo

Are you missing a file ?

Hi Mathieu,

Yes, apologies, I have provided that .geo file to you now. You should now see the same errors that I get when opening the case in Paraview.

Kind regards

Emma

I’m able to open your dataset without issues using ParaView 5.13

Which version of ParaView are you using ?

Hi Mathieu,

I can open the .encas file on my version of Paraview 5.13.1. However, it is the file called “.new.paraview” that is not able to be opened. It is this file that contains my particle data.

Many thanks

Emma

I’m able to open the .new.encas but a file seems to be missing:

Unable to open file: /home/glow/data/tmp/Post Processing/default.mpg0001

Then there is no data to show. Did you forget to provide this file ?

Hi Mathieu,

That file is in the folder I made available to you. I double checked just there.

Emma

It was incorrectly named, but it was there, I fixed that.

Then I get the same error as you:

This is not a binary data set. Try vtkEnSightGoldReader.

It looks like you are mixing binary and ascii ensight data.

The .geo file is binary and the .mpg0001 file is ascii.
This is not supported by ParaView and I’m not sure this is valid for EnSight.

Can you export the .mpg0001 file to binary instead ?

Hi Mathieu,

I had set up the file export with the name and it automatically appends the time step to the name for each file; it might have been that the file was in a different directory when you downloaded the data.

I exported that particle data as a ‘Particle History Data Export’ which is available under the Calculation Activities. I selected EnSight as the file type. There was no option available before the export in this setting to change it to a binary format. The other fluid data, exported under the same medium of Calculation Activities in Fluent but under Solution Data Export allowed the selection of EnSight Case Gold format and subsequently then binary format. The latter opens without an issue on Paraview, whilst the first produces the binary error I described and as you saw. Is it possible to convert the file format after producing the file as I have not figured out how to impose a binary file format on the Particle History Data Export.

Many thanks

Emma

I’m afraid I have no idea as I’m not an EnSight user.

Hi Mathieu

Many thanks for your support. I will look into that now.

Kind regards

Emma