Working with Converge Data

Notes on using EnSight with ConvergeCFD solutions

Basic Usage Notes:
Basic users of ConvergeCFD and EnSight should follow these steps to analyze their data in EnSight:
1. Users should utilize the "post_convert" utility provided from Convergent Science to convert the Converge Log files (post*.out) into EnSight format.
Users should then execute the "post_convert" command in the terminal window. Users can follow the instructions provided and indicate which timesteps are to exported, as well as which variables are to be exported.
Both volumetric data as well as discrete data (spray particles) can be exported to EnSight format along with the associated variables.
2. Users can then load the resulting EnSight Case Gold Format data directly into EnSight and proceed with normal transient post processing of their results.
Advanced Users Notes:
For the more complex user, there are couple of caveats to the above steps, which depending upon how/what he wants to look at, he may have to do.

1. If the user is attempting to do Pathlines, he will need to adjust the "time values" export from Converge from crank angle to "time" in seconds. (At the time of writing, the "post_convert" utiliity writes "Crank Angle" into the time slot for EnSight). As this has units of "angle", yet the velocity has units of "m/s", these are not consistent, and EnSight cannot correctly integrate with time if there is not consistent units. To modify the Time values from Crank Angle to "time in seconds", we have a UserDefinedTool to do this conversion. This tool takes 1 second to run, and can be found here on our Python Exchange Site:
This issue really only effects Pathlines 

2. Depending upon if the user wants to look at the internal grid, and what program he is using, he may need to specify some settings. There are some flags that need to be set (depending upon version and which package) to get different "interpretation" of the internal grid. Again, this really only effects if he wants to see the grid on the internal mesh, or he gets holes in the clip planes. There is a separate Knowledge Base article on the settings for the different versions of EnSight, and the desired speed/memory/accuracy desired:

Updated 08-Mar-2013:

If you are using Converge datasets with the "Centroid" N-faced decomposition method, please see this additional FAQ regarding this N-faced decomposition method and EnSight versions 10.0.1 through 10.0.2 

FAQ here ---

Should you have further questions regarding using ConvergeCFD with EnSight, please do not hesitate to contact us.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request