Postprocessing the rezoning results occurs as it does for nonlinear mesh adaptivity results.
For rezoning, the POST1 postprocessor (/POST1) is the primary postprocessing tool and most of its capability is available. Animation is also available via the ANDATA macro.
Each time rezoning occurs, the mesh changes, so new .rdb files
are necessary. For example, if you have used rezoning twice during the same analysis,
the program writes the following database files: .rdb,
.rd01, and .rd02. (For more information,
see File Structures for Repeated Rezonings.) Most POST1 postprocessing operations proceed
seamlessly from one database file to the next automatically; therefore, do not delete
the .rst or .rdb file, nor any
.rdnn
files, until you have completed postprocessing.
Displacement output for the rezoned model reports values as of the most recent rezoning, so the displacement will not seem to be continuous over multiple rezonings.
Keep all .rdb and .rdnn
database files until all desired postprocessing work has been completed.
The POST1 postprocessor is dependent on the .rst results file,
and on the .rdb and
.rdnn
files. If all or some of the database files are lost, the program uses
the .rst file to recover as much data as possible. In such
cases, however, data that exists only in database files may no longer be available,
causing some postprocessing operations to behave unexpectedly. For example,
information about defined components (CM), body-force loads on
nodes (BFLIST), and surface loads (SFLIST) may
be missing.
If you exited the program after the solution phase of the analysis and now want to perform POST1 postprocessing on your rezoning results, issue the /FILNAME command to specify the appropriate jobname before entering the POST1 processor. This is the preferred method for postprocessing rezoning results.
After entering the POST1 processor, it is helpful to issue the SET,LIST command.
For rezoning, the output list generated by the command indicates when a mesh change (and corresponding database file change) occurs due to rezoning, as shown in this example:
***** INDEX OF DATA SETS ON RESULTS FILE *****
SET TIME/FREQ LOAD STEP SUBSTEP CUMULATIVE
1 0.1000000 1 1 2
2 0.2000000 1 2 4
3 0.3500000 1 3 6
4 0.5500000 1 4 8
5 0.7500000 1 5 10
6 0.7500010 1 6 13 mesh changed
7 0.8750000 1 7 15
8 1.000000 1 8 17
...The output from a SET,LIST command is also useful for simply determining what information is available. For non-rezoning runs, for example, you can select substeps for further study by load step and substep number, time, set number, and the set for which a different mesh is used.
Animation for rezoning is available via the ANDATA macro.
Assuming that the appropriate jobname is already specified, the program proceeds from one mesh to the next automatically, using the data in each to generate the animation.
During the macro's initial scan, the program stores the view location and size of every saved substep. The program then combines the information to provide one fixed view (by internally setting the /FOCUS and /DIST commands to fixed values).
When using the POST26 time-history postprocessor (/POST26) on a model that you have rezoned, all of the usual information is available. Access it as follows:
Reset (RESET) the postprocessor specifications to initial defaults, erase all defined variables, and clear the data storage space.
Resume (RESUME) the appropriate .rd
nndatabase file (generally the one corresponding to the most recently created mesh).Issue a FILE command to open the .rst results file.
Only the output information available is fetched from the results file, as elements and nodes that exist in one mesh do not always exist in another.