This preview shows pages 1–3. Sign up to view the full content.
This preview has intentionally blurred sections. Sign up to view the full version.
View Full Document
Unformatted text preview: OVERVIEW OF ABAQUS/CAE GRAPHICS USER INTERFACE T11 TUTORIAL T1 OVERVIEW OF ABAQUS/CAE GRAPHICS USER INTERFACE Background . The finite element computer programs Abaqus/Standard and Abaqus/Explicit are rooted in the subject of continuum mechanics. The Course Reader does not address the latter program. Throughout the Course Reader most of the computer analysis experience offered with Abaqus/Standard is through the Abaqus/CAE program, which is a graphical user interface. Their relationship is shown in the data processing flow chart below. Following standard finite element terminology, the Abaqus/CAE program is termed the pre and postprocessor, and the Abaqus/Standard (or Abaqus/Explicit) program is the solver. CAE stands for C omplete A baqus E nvironment. Abaqus Data Processing Flow Chart Although Abaqus/CAE makes for a more visual or perhaps tactile approach, it obscures the fact that the formation and solution of the discrete algebraic finite element problem is actually performed by a separate program, namely Abaqus/Standard. For reasons that are partly historical and partly practical, the interfacing of model definition data between finiteelement preprocessor and solver programs is nearly always achieved through an ascii text input file (see Problems 19 and 110). Abaqus input files have a .inp file extension and are generated automatically by Abaqus/CAE when the user submits a job. They are then automatically loaded by Abaqus/Standard to begin the Input file job.inp Preprocessing Abaqus/CAE Solvers: Abaqus/Standard Abaqus/Explicit Postprocessing Abaqus/CAE Report file job.rpt Output files job.odb, job.dat job.res, job.fil Model database file job.cae Solution OVERVIEW OF ABAQUS/CAE GRAPHICS USER INTERFACE T12 analysis. 1 Embedded in Abaqus/CAE is a straightforward philosophy of problem solving. It presumes that the analyst has created an idealization of a structure or component that he or she can convey to the program in sufficient detail for a meaningful finite element analysis. The analyst prescribes the structural idealization using a logical sequence of input data modules. In this first phase of the analysis, called the Preprocessing Phase , the analyst is guided in providing a complete description of the structure's idealization (e.g., its geometry, material properties, loads and boundary conditions). This is accomplished without concern for how the structural idealization is to be discretized to produce a finite element model for solution , i.e., essentially without regard for the finite element method itself. This strategy fosters an accurate description of the problem and promotes a meaningful analysis by eliminating distractions due to concern for how the finite element model and solution are to be obtained....
View
Full
Document
This note was uploaded on 08/09/2011 for the course MAE 168 taught by Professor Klug during the Spring '11 term at UCLA.
 Spring '11
 Klug

Click to edit the document details