The Leading Tool for FEA Visualization and Post-processing, no other tool spans its range.
EnSight is the one complete visualization solution for your biggest and most challenging FEA post-processing problems.
Type 1 — Included Readers
Type 2 — Not Included User-Defined Readers
Type 3 — Stand-Alone Translators
Type 4 — EnSight Format
|ABAQUS||1||Two direct readers. Use "ABAQUS" reader for binary or ascii .fil files and "ABAQUS_ODB" for .odb file, see Knowledge Base. Note that ABAQUS .odb reader is not available on EnSight for Mac OS X, due to lack of libraries from Simmulia for OS X platform.|
|ADAGIO||1||Use Exodus II reader|
|ADINA||4||Exports EnSight Case format|
|ALEGRA||1||Use Exodus II reader|
|ANSYS||1||Direct reader for binary .rst, .rth, .rmq, .rfl files|
|AUTODYN||1||Direct reader for adres files (Windows only)|
|I-DEAS||1,3||Translator for I-DEAS FEA neutral file|
|LS-Dyna||1||User-defined reader for d3plot files, see Knowledge Base|
|MADYMO||1||Use LS-DYNA reader|
|MSC Adams||4||ADAMS/View plug-in macro written by MSC Software exports EnSight Casefile format, to obtain this macro, go to this MSC Knowledge Base Article. Supports flexible and rigid bodies.|
|MSC Dytran||1||User-defined reader for MSC/Dytran archive (.arc) files, see Knowledge Base. EnSight Query/Plot also reads the .THS time-history files. Sample = "Read from an external file"|
|MSC Marc||1||User-defined reader for t16 and t19 files|
|NASTRAN Input File||1||Input file reader for .dat, .bdf files.|
|1||User-defined reader for binary OP2 files|
|MSC Patran||3||Contact CEI for PATRAN to EnSight PATRAN macro|
|PERMAS||1||Contact CEI for user-defined BIF/BOF reader|
|PRESTO||1||Use Exodus II reader|
|PRONTO||1||Use Exodus II reader|
|RADIOSS||1||See Knowledge Base|
|TAHOE||4||See Knowledge Base|
Explanation of the types of interfaces:
Type 1 — Included Readers — These are accessed by choosing the desired format in the Data Reader dialog. They include common data formats as well as a number of readers for commercial software. These can be internal EnSight Readers as well as User-Defined Readers that interface to EnSight’s User-Defined Reader API. If the included reader is a User-Defined Reader there may be more info in $CEI_HOME/ensight80/src/readers. Also see the EnSight Online User Manual for details on using the reader. If you wish to create a data reader this article can be helpful.
Type 2 — Not Included User-Defined Readers — These are readers written by customers or vendors using EnSight’s User-Defined Reader API. These have the advantage of not requiring a separate data translation step and thus reduce user effort and disk storage requirements. EnSight users can obtain these readers by following the contact information in the table. For writing your own User-Defined Reader, complete documentation and dummy routines may be found in the directory $CEI_HOME/ensight80/src/readers. If you wish to create a data reader this article can be helpful.
Type 3 — Stand-Alone Translators — These are written by customers or vendors to convert data into EnSight format files. Several translators are provided with EnSight. These are found in the directory $CEI_HOME/ensight80/translators. Translators must first be compiled before they can be used. Some require links to libraries provided by the vendor of the program in question. See the README files found in each translator’s directory. For writing your own translator, a complete description of EnSight formats can be found in Chapter 11 of the EnSight Online User Manual.
Type 4 — EnSight Format — These are software vendors that support the EnSight format directly, i.e. an option is provided in their products to output data in EnSight5 or EnSight Case format. If you wish to export EnSight format directly, a complete description of EnSight formats can be found in Chapter 11 of the EnSight Online User Manual.