Translating ODB Output Database Files to SIM Format

The translator converts an output database (.odb) file containing model and results information to a SIM database (.sim) file, allowing you to use the Physics Results Explorer app on the 3DEXPERIENCE platform for high-performance postprocessing of analysis results.

Errors are issued when specific data in the output database cannot be converted to the SIM database file. For example, if the output database does not have sufficient information to translate the data properly, or if support is not yet implemented for particular output in the SIM format. The translator will not stop if these types of errors are issued; however, it will stop (without saving the SIM database file) if a fatal error occurs.

This page discusses:

Limitations

The translator is subject to the following limitations:

  • All data in the output database file that are needed by the Physics Results Explorer app are copied to the SIM database file. Other data may not be copied to the SIM file.

  • Field and history results for the following output variables are not converted:

    • MMIXDME

    • MMIXDMI

    • NFORC

    • SSPEEQ

    • SSSPRD

    • SSTORQ

    • SSFORC

    • TIME

  • Data for the following elements are not converted:

    • ELBOW31C

    • Dashpot elements

    • Spring elements

    • Substructure elements

    • User elements

  • Coupling constraints are not converted.

Command Summary

abaqus odb2simodbodb-file-namesimSIM-database-file-nameloglog-file-nameo2sdebug

Command Line Options

odb

This option is used to specify the name of the output database file to be converted.

sim

This option is used to specify the name of the SIM database file to be output by the translator.

log

This option is used to specify the name of the log file generated during the translation. If this option is omitted, the information is written to the screen.

o2sdebug

This option specifies the level of detail for the messages that Abaqus writes to the log file. Valid settings are as follows:

  • 0 - errors only (default)

  • 1 - warnings and work-in-progress milestones (e.g., convert sections)

  • 2 - more debug information (e.g., field data)