15.11.2012 Views

Mechanical APDL Basic Analysis Guide - Ansys

Mechanical APDL Basic Analysis Guide - Ansys

Mechanical APDL Basic Analysis Guide - Ansys

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 21: Memory Management and Configuration<br />

halves until it can allocate additional memory. If not specified, MEM_GROW defaults to one-half the initial<br />

scratch space. To turn off dynamic memory allocation (use a fixed-memory model), set MEM_GROW=0.<br />

LOCALFIL is a key that determines when files are to be closed: 0 (globally closed) or 1 (locally closed). It defaults<br />

to 0 (globally closed) and can be changed at the Begin level with the /CONFIG,LOCFL command. This<br />

key is applicable only to the EROT, ESAV, EMAT, FULL, and TRI files. Locally closed files (LOCALFIL=1) may<br />

be deleted earlier during solution if requested with the /FDELE command. This may be helpful while running<br />

large problems. Globally closed files are closed at the end of the run and are not opened and closed each<br />

substep. This saves time in analyses with many substeps.<br />

CONTACTS is the number of contact elements that are expected to be in contact at any given time. It defaults<br />

to 1000 and can be changed at the Begin level with the /CONFIG,NCONT command. This is not the same as<br />

the total number of contact elements in the model.<br />

ORDERER_ is a key that determines the automatic element reordering scheme: 0 (WSORT,ALL), 1 (WAVES),<br />

or 2 (both). It defaults to 2 and can be changed at the Begin level with the /CONFIG,ORDER command.<br />

Any of the following nine keywords that you do not specify is set to 100 the first time ANSYS encounters it.<br />

Whenever the current maximum is exceeded, the keyword value automatically doubles. The maximum values<br />

are dynamically expanded, even at first encounter.<br />

• MX_NODES is the maximum number of nodes. You can change the value (on most systems) at the Begin<br />

level with the /CONFIG,MXND command.<br />

• MX_ELEMS is the maximum number of elements. You can change the value (on most systems) at the<br />

Begin level with the /CONFIG,MXEL command.<br />

• MX_KEYPT is the maximum number of keypoints. You can change the value (on most systems) at the<br />

Begin level with the /CONFIG,MXKP command.<br />

• MX_LINES is the maximum number of lines. You can change the value (on most systems) at the Begin<br />

level with the /CONFIG,MXLS command.<br />

• MX_AREAS is the maximum number of areas. You can change the value (on most systems) at the Begin<br />

level with the /CONFIG,MXAR command.<br />

• MX_VOLUS is the maximum number of volumes. You can change the value (on most systems) at the<br />

Begin level with the /CONFIG,MXVL command.<br />

• MX_REALS is the maximum number of sets of real constants (element attributes). You can change the<br />

value (on most systems) at the Begin level with the /CONFIG,MXRL command.<br />

• MX_COUPS is the maximum number of sets of coupled degrees of freedom. You can change the value<br />

(on most systems) at the Begin level with the /CONFIG,MXCP command.<br />

• MX_CEQNS is the maximum number of constraint equations. You can change the value (on most systems)<br />

at the Begin level with the /CONFIG,FMXCE command.<br />

FILESPLT is the integer value indicating the file split point in megawords. A megaword is 1024*1024 4-byte<br />

words, or 4 MB. All files that are eligible for splitting will be split into a new file every increment of xxxx<br />

megawords (where xxxx is the value specified with this keyword). You can change the value (on most<br />

systems) at the Begin level with the /CONFIG,FSPLIT command. See Splitting Files Across File Partitions in<br />

the Operations <strong>Guide</strong> for more information on splitting files.<br />

You can change many of the configuration settings at program start-up using ANSYS entry options, at the<br />

Begin level with the /CONFIG command, or with other ANSYS commands. In most cases, therefore, there is<br />

no need to create your own config130.ans file. Also, the default settings for each computer system have<br />

314<br />

Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information<br />

of ANSYS, Inc. and its subsidiaries and affiliates.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!