Добавил:
Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
ANSYS.pdf
Скачиваний:
875
Добавлен:
31.08.2019
Размер:
31.29 Mб
Скачать

vk.com/club152685050 | vk.com/id446425943

Postprocessing Rezoning Results

Although no theoretical limit on the number of allowable rezonings in the same domain exists, the program allows up to 99 rezonings in a single job. In practice, two or three rezonings in a given domain should be sufficient.

To perform another rezoning, simply repeat the rezoning process. No special command is necessary, and the rezoning process remains the same.

4.11.1. File Structures for Repeated Rezonings

When multiple rezonings occur in the same domain during the same analysis, each creates a different finite element model. To make restarting and rezoning from any substep possible, the program saves

the .rdb files for the initial model and for each rezoned model. Similarly, different .rst files are created for each model to postprocess the results.

Following is the file structure after more than one rezoning has occurred:

File type

Rezone 0

Rezone 1

Rezone 2

...

Rezone 11

...

Rezone nn

 

(standard

 

 

 

 

 

 

 

run)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

.rdb

.rdb

.rd01

.rd02

...

.rd11

...

.rdnn

.rxxx

.rxxx

.rxxx

.rxxx

...

.rxxx

...

.rxxx

.ldhi

 

 

.ldhi

 

 

 

 

.rst

.rst

.rs01

.rs02

...

.rs11

...

.rsnn

The maximum number of .rdb files and .rst files is 99. The .ldhi load history file contains information for all models created as a result of multiple rezonings.

4.12. Postprocessing Rezoning Results

For rezoning, the POST1 postprocessor is the primary postprocessing tool and most of its capability is available. Animation is also available via the ANDATA macro. Output from the POST26 time-history postprocessor (/POST26) is restricted to the data contained in any one results file.

Each time rezoning occurs, the mesh changes, so new .rdb and .rst files are necessary. For example, if you have employed rezoning twice during the same analysis, the program writes the following results files: .rst, .rs01, and .rs02, and the following database file: .rdb, .rd01, and .rd02. (For more information, see File Structures for Repeated Rezonings (p. 121).) Most POST1 postprocessing operations proceed seamlessly from one file to the next automatically. Therefore, do not delete the .rst or .rdb file, nor any .rsnn or .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.

4.12.1. The Database Postprocessor

Before accessing the POST1 database postprocessor (/POST1), consider how the program should handle postprocessing data files, as follows:

The program treats all postprocessing data files as a single file automatically (assuming that all necessary files are present). If you exited the program after the solution phase of the analysis and now want to perform postprocessing on your rezoning results, issue the /FILNAME command to specify the appropriate

Release 15.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information

 

of ANSYS, Inc. and its subsidiaries and affiliates.

121

vk.com/club152685050Rezoning | vk.com/id446425943

jobname before entering the POST1 processor. This is the preferred method for postprocessing rezoning results.

If you must examine only one postprocessing data file--because some files are very large or some are missing, for example--resume (RESUME) the appropriate database to obtain the correct plot, then issue the FILE command within POST1. (For example, to check the results in postprocessing data file .rs02, resume database file .rd02.)

4.12.1.1. Listing the Rezoning Results File Summary

After entering the POST1 processor, it is helpful to issue the SET,LIST command.

For rezoning, the output list generated by the command includes an additional column indicating which postprocessing data file contains each saved substep of each load step. The first use of the new file is flagged with the word “rezone” to emphasize the change of file.

Following is an example output list from a SET,LIST command:

*****INDEX OF DATA SETS ON RESULTS FILE *****

SET

TIME/FREQ

LOAD STEP

SUBSTEP

CUMULATIVE

FILE SUFFIX

1

0.1000000

1

1

2

rst

 

2

0.2000000

1

2

4

rst

 

3

0.3500000

1

3

6

rst

 

4

0.5500000

1

4

8

rst

 

5

0.7500000

1

5

10

rst

 

6

0.7500010

1

6

13

rs01

rezone

7

0.8750000

1

7

15

rs01

 

8

1.000000

1

8

17

rs01

 

...

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, or set number.

Although the program creates multiple postprocessing data files for rezoning, you can consider them

a single file for POST1 processing (assuming that the appropriate jobname is already specified) because there is no need to access individual files directly. The program automatically detects the specific file needed according to the SET command issued, after which most of the usual postprocessing command capability (PLESOL, PRNSOL, etc.) is available.

4.12.1.2. Animating the Rezoning Results

Animation for rezoning is available via the ANDATA macro.

Assuming that the appropriate jobname is already specified, the program proceeds from one postprocessing data file 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).

4.12.1.3. Using the Results Viewer for Rezoning

The Results Viewer does not support results viewing across all rezoning results files automatically.

 

Release 15.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information

122

of ANSYS, Inc. and its subsidiaries and affiliates.