How to READ and UNDERSTAND ABAQUS Files

Short Summary:
This video explains how to understand the numerous files generated when running an Abaqus simulation. The speaker introduces a "usefulness index" (1-3) to categorize these files based on their importance for understanding the simulation results. Highly useful files (index 3) include the .cae (Abaqus CAE file), .inp (input file), .odb (output database file), .dat (data file), and .msg (message file). Moderately useful files (index 2) are the .jnl (journal file) and .stf (status file). Less useful files (index 1) include the .lck (lock file), .cmf (command file), .ipm (interprocess message file), .plt (part file), and .dor (replay file). The video demonstrates how to access and interpret information within these files, using a unidirectional composite simulation as an example. Understanding these files is crucial for debugging, analyzing results, and sharing simulation data effectively.
Detailed Summary:
The video begins by addressing the confusion surrounding the numerous files generated by Abaqus simulations. The speaker aims to clarify the purpose and importance of each file type. A key concept introduced is the "usefulness index," a rating system (1-3) to categorize files based on their utility in understanding the simulation.
Section 1: Introduction and Problem Setup
The video introduces the problem: many users are confused by the multitude of files created after running an Abaqus model. The speaker sets the stage by showing a simple unidirectional composite model ready to run, highlighting the single .cae file before the simulation.
Section 2: Running the Simulation and Observing the Results
The simulation is run, and the results (plastic strain and shear bands) are briefly visualized. The focus then shifts to the newly generated files in the working directory.
Section 3: Categorizing Files by Usefulness
The core of the video is the classification of files based on the usefulness index:
-
Usefulness Index 3 (Highly Useful): These files are essential for understanding and analyzing the simulation. The speaker details each file:
.cae
(Abaqus CAE file): Contains the entire model definition..inp
(input file): The pre-processor instructions sent to the Abaqus solver. The speaker opens this file in Notepad to show its contents and explains how modifications can be made here..odb
(output database file): Stores all simulation results (stress, strain, etc.). The speaker mentions using Python to extract data from this file..dat
(data file): Contains all data associated with the simulation, including node information, element definitions, and any error messages..msg
(message file): Provides step-by-step updates and warnings during the simulation, crucial for debugging. The speaker points out a warning message within the file as an example.
-
Usefulness Index 2 (Moderately Useful): These files provide supplementary information.
.jnl
(journal file): A Python script recording all actions performed during the simulation, useful for recreating the model..stf
(status file): Shows the status of the simulation (e.g., aborted, completed).
-
Usefulness Index 1 (Less Useful): These files offer less critical information.
.lck
(lock file): Logs the start and finish times of the simulation..cmf
(command file): A set of commands driving the simulation, more relevant for programmatic control..ipm
(interprocess message file): Shows communication between the Abaqus CAE and the solver..plt
(part file): Contains information about the parts in the model..dor
(replay file): Similar to the journal file, recording actions within Abaqus.
Section 4: Conclusion
The video concludes by summarizing the importance of understanding these various files for effective Abaqus usage and mentions a related video on unit systems in Abaqus simulations. The speaker emphasizes that Abaqus generates extensive file information to aid users in understanding the simulation process.