CONVERGE and EnSight
New bundling of CONVERGE and EnSight
Convergent Science (Makers of CONVERGE) and Computational Engineering International (Makers of EnSight) have entered into an agreement to bundle EnSight for high quality postprocessing of CONVERGE results. As of CONVERGE 2.1, this agreement creates two new CONVERGE specific EnSight versions with examples and tools to help CONVERGE users. These versions, beginning with EnSight version 10.0.3(e), are:
1. EnSight Desktop for CONVERGE aka 'EDC'. Bundled with CONVERGE purchase from CSI. Requires the new "Customized EnSight for CONVERGE" formatted data. This data format is based on EnSight Case Gold format but is modified. EnSight "full" versions like Free, Desktop, Standard, and Gold can also read these files, but EDC can't read normal Case formatted files.
2. EnSight Standard for CONVERGE aka 'ESC'. Paid/licensed upgrade. Upgrade can be done either through CSI or CEI. Requires the new "Customized EnSight for CONVERGE" formatted data. Of course, users may upgrade directly to one of CEI's original aka "full" (ie. not CONVERGE specific but provides CONVERGE support) EnSight versions by contacting their CEI sales representative. These products read all supported EnSight data formats. The CONVERGE_Studio GUI installer allows the user to specify which installation of EnSight to use via the "Edit->Settings" of the "3D Post Processing" page. CONVERGE_Studio will place the CONVERGE specific settings and examples(ie. ConvergeExtension folder) into that EnSight installation location. The CONVERGE_Studio installer does not have a method to install ConvergeExtension alone. Users must reinstall the whole CONVERGE_Studio or copy over the ConvergeExtension manually. To download the appropriate packages, CONVERGE users must register an account at www.convergecfd.com/downloads first. After the registration is approved, they can login and traverse to -Root-/converge_releases/preprocessor_installation_package. There users will find a file called "0ReadMeFirst.txt" which describes the options. Contact CSI support regarding any further questions about this process. CONVERGE 2.1(and newer releases) into EnSight
Translator developed by CSI, "post_convert":
1. always used to transform CONVERGE data to Ensight readable format.
2. used to process CONVERGE v2.1, and newer releases, which continues to only write post*.out
3. now accessed more simply via CONVERGE_Studio which is the front-end GUI. Users no longer need to open a terminal and run the translator by hand.
4. transforms to: a) the new "Customized EnSight for CONVERGE" formatted data for EDC and ESC. b) any EnSight supported format(Normally EnSight Case Gold) for original EnSight versions.
5. latest CONVERGE_Studio installer dated after 10/04/2013 includes the appropriate post_convert. The post_convert with a post date of 10/7/2013 works with EnSight for CONVERGE. Available at the CSI website(www.convergecfd.com/news-item/convergestudioensight/)
6. processes both volumetric data as well as discrete data (spray particles) can be exported to EnSight format along with the associated variables.
7. if a user is using an old post_convert script to convert V2.1 files, an error message will be appear. CONVERGE releases prior to 2.1 into EnSight
Translator developed by CSI, "post_convert":
1. is always used to transform CONVERGE data to Ensight readable format.
2. outputs various formats including EnSight Case Gold.
3. processes CONVERGE post*.out files and is executed in a terminal window. Instructions from the software will walk you through the process of exporting time steps and variables.
4. processes both volumetric data as well as discrete data (spray particles) can be exported to EnSight format along with the associated variables.
5. does not have a version number so it could be difficult know if it is the latest translator
6. did have some bugs in the earlier versions, so it is important to have the latest. If a user is using an old post_convert script to convert V2.1 files, an error message will be displayed.
How do I get EnSight for CONVERGE? www.ceisoftware.com/ensight-for-converge/ -------
How do I get to the CSI CONVERGE information regarding EnSight? www.convergecfd.com/news-item/convergestudioensight/ -------
Does the installer for CONVERGE install EnSight? No, you will need to install EnSight unless you already have it. The CONVERGE Studio GUI will walk you through setting up references to the version of EnSight that you want to use. It will also install the ConvergeExtension package into the CEI_HOME folder to provide any special examples and tools. -------
If I have a version of EnSight 10.0.3(d) or older what happens when it reads a "Customized EnSight for CONVERGE" format dataset? EnSight versions prior to 10.0.3(e) will fail to read the "Customized EnSight for CONVERGE" format with a few possible generic error outcomes. This is due to the fact that those versions of EnSight do not understand this format but believe they are normal EnSight Case files. Possible outcomes include: 1) An empty graphics window without any error display. 2) A message in the terminal where EnSight was executed, indicating: "FYI: Parts[gui_epn=1,ipn=0]=NULL was not created/loaded." 3) An error message when manually trying to load a part indicating: "Error creating EnSight part(s)." -------
When an older version of ens_checker100 encounters a "Customized EnSight for CONVERGE" format dataset, what kind of behavior can I expect? The following error will most likely be displayed with slightly different values: Part 1: Description is: Computational mesh Unstructured Part Number of nodes is: 782175608 ===> Problem: ------------- Not successful reading the (782175608) X coordinates ... ... >-------------------------< > GEOMETRY section FAILED < >-------------------------< The rest of the information is most likely not useful. -------
Is ens_checker100 the only way to tell that a dataset is "Customized EnSight for CONVERGE" format? Yes, ens_checker100 versions newer that 10.0.3(e) will indicate in the output: "CONVERGE custom format" ens_checker 100 10.0.3(e) displays simply: "custom format" -------
What is the message that we would get from a newer version of ens_checker100 from 10.0.3(e) or later with a "Customized EnSight for CONVERGE" format? Versions newer that 10.0.3(e) will indicate in the output: "CONVERGE custom format" 10.0.3(e) only displays "custom format" -------
Costs? Users of CONVERGE, get "EnSight Desktop for CONVERGE" for free. More accurately, CSI has paid for their version of EDC as a group purchase. Users wishing to update to CEI's original(ie. not CONVERGE specific) EnSight versions, simply pay an upgrade fee. -------
Licenses? CEI is responsible for generating and distributing keys for EDC and ESC. -------
Who is responsible for supporting the EDC and ESC products? CSI is responsible for first line question. CEI after that. -------
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" utility 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: http://pythonexchange.com/2011/10/06/converting-crank-angle-to-time/ 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: http://www.ceisoftware.com/knowledge-base/?faq=499