During the solution, several files are created. Some of these can be deleted after the solution but some need to be retained for postprocessing or for feeding other subsequent analyses. Since you can perform several different analyses on a single model or even have several models in the same Mechanical application project, you must manage the solution files in a consistent and predictable manner.
ANSYS Workbench's file management system keeps multiple databases under a single project. See Project File Management for a description of the file management system.
Note: The Analysis Settings Details view has an Analysis Data Management grouping that shows the solution directory location for each analysis.
Default behavior: By default an analysis in the Mechanical application saves only the minimal files required for postprocessing. Typically these include results files (file.rst, file.rth, file.rmg, file.psd, file.mcom), input file (ds.dat), output file (solve.out), and some other files that have valuable information about the solution ( file.BCS, file.nlh, file.gst). Of these only the results file is generally of significant size.
For Windows users, the solution files folder can be displayed using the feature.
Future Analysis: If the results of this analysis are to be used as a load or an initial condition in a subsequent analysis then additional files may need to be saved. Declaring your intent to use this in the future will automatically save the required files and reuse them in the subsequent analysis. Refer to Define Initial Conditions for details of these analyses.
Delete Unneeded Files: The solution process creates other files that are typically not needed for postprocessing or are not used in subsequent analyses. By default, the Mechanical application deletes these files at the end of solution. However, if for any reason, you want to keep all the files you could choose to do so.
You can use the Output Controls on the analysis settings page to write only the desired result types to the .rst file (for example, if strains are not needed, you can turn them off which would create a smaller result file). In addition, for advanced Mechanical APDL application users, Command objects can be used to further limit output via the OUTRES command.
An external result file is needed to post results. The following behavior will occur:
If you save a simulation, any simulation files (result and other required files) will be saved to the new location.
If you use the option (Environment and Model objects only), all subordinate objects are reproduced with the exception of the data for all result objects. This is based on the intention that loading changes are performed and the solution process is repeated.
If you attempt to resolve a previously solved and saved database, the corresponding saved result files are backed up automatically in case the current solve is not saved.
The /post1 XML transfer of result files used in previous releases is no longer used so any existing solution Command objects which were modifying the Mechanical APDL application results to be brought back into the Mechanical application no longer function.