Creo Simulate > Creo Simulate > Additional Information > The Database > Files Created by Creo Simulate
  
Files Created by Creo Simulate
This document lists files created by Creo Simulate and explains their purpose. Each of the following topics covers a different type of file:
Engine Files
Library Files
Results Files
AutoGEM Files
FEM Mode Files
Miscellaneous Files
Engine Files
Refer to the following topics for information on different categories of engine files:
mecbatch
Engine Input Files
Temporary Engine Files
Engine Output Files
mecbatch
The mecbatch command executes from your operating system the run of one or more design studies you previously included in a batch file. When you create a batch file, you can specify a name for the batch file or use the default name mecbatch (mecbatch.bat on Windows). Creo Simulate places the file in the directory from which you started Creo Simulate.
Engine Input Files
Creo Simulate creates the following engine input files when you start a run of an analysis or design study (study represents the name of the design study you are running):
study.mdb
Contains a snapshot of the model database for your part at the time you start the analysis or design study.
study.mda
Contains a snapshot of the model database for your assembly at the time you start the analysis or design study.
study.mds
Contains all the data needed to run a Creo Simulate study as a distributed batch process. It is generated when you click Run > Distributed batch on the Analyses and Design Studies dialog box. It is an engine input file that is the input to an engine job run remotely by Creo Distributed Batch.
study.mcd
Contains data used to formulate results windows, including layer information.
meshed_sdymdl.mdb
A transient file that enables Creo Simulate to reuse a mesh from an analysis or design study you had run previously. If you run the analysis or study as part of the Creo Simulate session, this file exists as a temporary conduit for the mesh and is deleted as soon as the analysis or study is underway. However, for batch runs, Creo Simulate does not delete this file.
study.lok
An empty file that locks the directory for results viewing when analysis or design study is running. The file is automatically deleted as soon as results are available.
current_session.pro
For an engine run or batch, Creo Simulate creates this text file in the study directory. It contain all the configuration options that have non default values.
Creo Simulate places the files in a directory called study, and places study in the directory for output files you specify through the Run > Settings command on the Analyses and Design Studies dialog box.
Temporary Engine Files
During a design study run, Creo Simulate creates a series of temporary files with .tmp and .bas extensions. These files are placed in a directory called study.tmp (study represents the name of the design study you are running). The software places study.tmp in the directory for temporary files you specify through the Run > Settings command on the Analyses and Design Studies dialog box.
Creo Simulate deletes the study.tmp directory when the run finishes successfully.
If you stop a run in progress or if a run terminates because of an error, these files are saved automatically. You are prompted to delete any temporary files left over from a previous run when you start a new run of the same design study.
Engine Output Files
The Structure engine creates the following engine output files when you run a design study. These files are placed in one of three directories:
• the study directory created during a run (where study is the name of the design study you run)
• the analysis subdirectory of the study directory (where analysis is the name of the analysis in that study)
• the step#### subdirectory of the study directory (where the four pound signs (####) represent the number of the master interval defined for the dynamic structural or transient thermal analysis in four-digit format)
The Structure engine creates the following files:
dpiupdt1.mdb
Contains a snapshot of the model database if the engine replaced elements that became invalid during a global sensitivity study. If this happens, Creo Simulate uses the dpiupdt1.mdb file (rather than the study.mdb file) when you review results.
study.cnv
Contains multi-pass and single-pass convergence information.
For multi-pass adaptive, this file contains the final p-order of each edge and a list of edges and elements for which convergence was not achieved. Creo Simulate also lists the errors in edge displacements and strain energies, or temperatures and energy norms, depending on the type of analysis.
For single-pass adaptive, this file contains the final p-order of each edge.
For transient thermal analyses, there are multiple .cnv files displaying p-orders at every master interval where results are saved. These are stored in the step#### directory.
study.dia
Communicates an error code to the user interface in the event of a non-recoverable condition during the engine run.
study.d##
Contains displacements or temperatures, depending on the analysis type. The two pound signs (##) represent the load set or mode number in two-digit format.
study.err
Contains the engine input echo along with non-recoverable conditions encountered during run time.
study.g##
Contains plotting data for global sensitivity. Creo Simulate reports values of measures at each design variable step. The two pound signs (##) represent the design variables number in two-digit format.
study.hst
Contains information about model updates during an optimization or a sensitivity design study.
study.l##
Contains plotting data for local sensitivity. Two points give a linear sensitivity plot for each measure versus the selected design variables. The two pound signs (##) represent the design variables number in two-digit format.
study.neu
Contains the connectivity of the grid.
study.opt
Contains plotting data for optimization. Creo Simulate reports values of measures at every step of the optimization.
study.pas
Contains information similar to the study.stt file but is more detailed.
study.pnu
Contains the connectivity information of the geometric element model.
study.res
Contains values of measures for each analysis pass.
study.rpt
Contains information about a run, including values of measures, warning messages, and, for optimization design studies, information about parameters and goal and limit quantities at each step of the optimization.
You can access this file through the Info > Status command on the Analyses and Design Studies dialog box, or print out the file through your operating system.
study.rst
Contains the state of the last pass for a multi-pass adaptive analysis. Creo Simulate uses this file if you decide to restart an analysis that you had previously stopped.
study.solution
Contains information on solutions generated during an analysis. The study solution file is in binary and is intended for internal engine use only.
Creo Simulate refers to this file when performing analyses that rely on the solution of a previously run analysis. For example, to perform a buckling analysis, you must specify a previously run static analysis that the Structure engine uses to determine the BLF. During the buckling analysis run, the Structure engine locates and refers to the study.solution file generated by the static analysis you specified when you defined the buckling analysis.
study.stt
Contains the start and completion times of major steps in the engine run. You can access this file through detailed summary you can review using the Info > Status command on the Analyses and Design Studies dialog box.
study.s##
This file contains the stress/strain distribution or the fluxes and temperature gradients, depending on the analysis type.
The two pound signs (##) represent in two-digit format the load set or mode number.
study.sp##
This file contains all the phases of stress or strain distribution in a dynamic frequency analysis reported with respect to the global rectangular coordinate system.
Shell membranes and bending stresses are reported with respect to the local material coordinate system. Forces and moments for beams are also reported with respect to the local coordinate system.
The two pound signs (##) in two-digit format represent the load set or mode number.
The file is placed in the directory STEP ####, where the four pound signs represent the frequency step.
study.ter
Contains a summary of your model as it is seen during the engine run expressed in ASCII. The summary includes such items as loads, constraints, materials, and so forth.
study.t##
Contains plotting data for dynamic structural and transient thermal analyses. Measure values of response points are reported at successive time steps. The two pound signs (##) represent the load set or mode number in two-digit format.
Creo Simulate also creates the following engine output files for structural analyses only:
study.a##
Contains the rotations. The two pound signs (##) represent the load set or mode number, in two-digit format.
study.b##
Contains the laminate stress/strain distribution calculated for a static, modal, dynamic time, dynamic frequency, dynamic random, dynamic shock, or buckling analysis. Creo Simulate calculates all quantities at the h-node locations and reports values with respect to the global rectangular coordinate system. The two pound signs (##) represent the load set number in two-digit format.
study.f##
Contains plotting data for frequency response. Measure values are reported at successive frequency steps. The two pound signs (##) represent the load set number in two-digit format.
study.fatigue##
Contains the results for a fatigue analysis. Creo Simulate calculates all quantities at the h-node locations lying on the external surface of the model and reports values with respect to the global rectangular coordinate system. The two pound signs (##) represent the load set number in two-digit format.
study.h##
Contains the displacement phases from a dynamic frequency analysis. The two pound signs (##) represent the load set number in two-digit format.
study.i##
Contains the velocity phases from a dynamic frequency analysis. The two pound signs (##) represent the load set number in two-digit format.
study.j##
Contains the acceleration phases from a dynamic frequency analysis. The two pound signs (##) represent the load set number in two-digit format.
study.k##
Contains the rotation phases from a dynamic frequency analysis. The two pound signs (##) represent the load set number in two-digit format.
study.m##
Contains the rotational velocity phases from a dynamic frequency analysis. The two pound signs (##) represent the load set number in two-digit format.
study.q##
Contains the rotational acceleration phases from a dynamic frequency analysis. The two pound signs (##) represent the load set number in two-digit format.
study.r##
Contains reactions on constrained points and edges for static deformation or mode of vibration. The two pound signs (##) represent the load set or mode number in two-digit format.
study.ss##
Contains the stress components distribution from a fatigue analysis expressed in ASCII. The two pound signs (##) represent the load set number in two-digit format.
study.coe
Contains information that the engine uses if you run a dynamic analysis using the Use modes from previous design study option.
study.v##
Contains the velocity in a dynamic time or dynamic frequency analysis. The two pound signs (##) represent the load set or mode number in two-digit format.
study.w##
Contains the acceleration in a dynamic time or dynamic frequency analysis. The two pound signs (##) represent the load set or mode number in two-digit format.
study.x##
Contains the angular velocity in a dynamic time or dynamic frequency analysis. The two pound signs (##) represent the load set or mode number in two-digit format.
study.y##
Contains the angular acceleration in a dynamic time or dynamic frequency analysis. The two pound signs (##) represent the load set or mode number in two-digit format.
study.p##
Contains maximum/minimum principal stress directions in static, modal, dynamic time, dynamic frequency, shock or buckling analysis. The two pound signs (##) represent the load set or mode number in two-digit format.
study.n##
Contains shell stress/strain results in static, modal, dynamic time, dynamic frequency, shock, or buckling analysis. The two pound signs (##) represent the load set or mode number in two-digit format.
study.buc
Contains static analysis solution information needed to reconstruct element stress during buckling analysis.
study.mor
Contains the material orientation information.
study.c##
Contains plotting data for contact analysis. Creo Simulate reports values of measures at each load increment. The two pound signs (##) represent the load set or mode number in two-digit format.
Creo Simulate also creates the following engine output file for thermal analyses only:
study.tld
Contains information that the engine uses for structural analyses containing a thermal temperature load or temperature-dependent material properties.
Library Files
Creo Simulate creates and adds to the following library files when you place a material set, beam section set, shell property sets, or spring stiffness set in the library with the Add To Library button on the appropriate dialog box:
beam_section.bsf
Contains the definition of a beam section you create (where beam_section is the name of the beam section). The beam library contains one .bsf file for each beam you create.
mshlprp.lib
Contains shell property sets.
mspstf.lib
Contains spring stiffness sets.
When you start a Creo Simulate product, Creo Simulate searches for library files in the following directories, in this order:
• the lib subdirectory in the Creo Simulate home directory
• the working directory
• your home directory
Creo Simulate uses the first copy of the appropriate configuration or library file it finds.
If you choose to add a beam section, spring stiffness, or shell property to the library, Creo Simulate creates a new version of the appropriate library file as follows:
• If Creo Simulate finds the file in the current directory or your home directory, Creo Simulate replaces the existing file with the new version.
• If Creo Simulate finds the file in the lib subdirectory or does not find the file, Creo Simulate places the new file in your home directory.
Results Files
Results files that belong to the following file formats are created when you save results:
file.rwd
Contains the result window definitions that you create and save.
file.grt
Contains in tabular form the XY values for a results graph that you create for all Creo Simulate products. You create this file when you generate a graph report.
file.pvs
Contains the fringe or contour plots that you create and save in a format that can be read in Creo View.
A .pvs file is created when you save a copy of a part file to Creo View format. However, when saving a copy of the assembly file to Creo View format, you create a .pvs file for the assembly file and .ol files for the components and sub-assembly files.
file.rwt
Contains the result window definitions and some of the result window attributes that you create and save.
file.html
Contains the graphic results for web viewing.
file.wrl
Contains the non-animated discretely colored fringe plot. The p-level plots are excluded.
file.nas
Contains the undeformed or deformed surface results of the NASTRAN mesh file that you define and save. You can control what goes into the contents of the .nas file through a NASTRAN template that you specify in the NASTRAN Analysis Template area of the Run FEM Analysis dialog box.
file.xls
Contains a pictorial rendering of the graph as well as a numeric table of the graph results at given intervals.
file.mpg
Contains the animated movie of a result window that you create and save. You can create this file to produce animated reproductions of your results. This feature helps create presentations.
file.avi
Contains the animated movie of a result window that you create and save. You can create this file to produce animated reproductions of your results. This feature helps create presentations.
file.mrs
This is a compressed file that contains the results directory and the associated result window definitions. This file format is used to save results to the Windchill workspace.
file.mrp
Compressed file that contains the results directory in a web page or HTML format. This file format is used to save results to the Windchill workspace.
AutoGEM Files
Creo Simulate creates the following files when you use AutoGEM:
model.agm
Contains information about the most recent AutoGEM operation you executed for the current model. You can access the AutoGEM log file regardless of whether AutoGEM completed successfully or unsuccessfully, or you interrupted it.
Creo Simulate saves the AutoGEM log file as model.agm (where model is the name of your model). Creo Simulate overwrites these files with each successive AutoGEM session. If you want to save a particular AutoGEM session, you can rename it through the operating system.
untitled.agm
Creo Simulate saves the AutoGEM log file as untitled.agm if you have not named your model. Creo Simulate overwrites these files with each successive AutoGEM session. If you want to save a particular AutoGEM session, you can rename it through the operating system.
model.mmp
Mesh file created by AutoGEM for a part model. Creo Simulate prompts you to save the mesh file. model.mmp is saved to the working directory if you select Yes.
model.mma
Mesh file created by AutoGEM for an assembly model. Creo Simulate prompts you to save the mesh file. model.mma is saved to the working directory if you select Yes.
FEM Mode Files
FEM mode creates the following output files that you can export to an FEA program to perform a finite element analysis:
model.ans
Contains your model's mesh data in ASCII format. Use this output file with the ANSYS solver.
model.nas
Contains your model's mesh data in ASCII format. Use this output file with the MSC/NASTRAN solver.
model.fnf
Contains information about an entire finite element model. Use the FEM Neutral output file to exchange data between Creo Parametric and FEA programs.
In addition, FEM mode creates the following files during the finite element modeling process.
model.bde
Lists problem mesh elements that fail a requested quality check.
model.fmp
Contains mesh data of a part. Creo Simulate creates this file in the current directory while generating the finite element mesh of your model.
model.fma
Contains mesh data of an assembly. Creo Simulate creates this file in the current directory while generating the finite element mesh of your model.
model.frd
Contains model's mesh and results data. Creo Simulate creates this file while performing a finite element analysis of your model.
model.inf
Lists a definition of your model and finite element results statistics.
model.plt
Contains plot file output from postprocessing.
Miscellaneous Files
Creo Simulate creates the following files when you start the product:
mech_trl.txt.X (where X is an integer)
Contains playback information of your actions in Creo Simulate. This file is automatically created in the current directory when you start the program. The software starts a new mech_trl.txt.X file whenever you begin a new Creo Simulate session.
Customer support can use this file to diagnose any problems you might have while running Creo Simulate.