Mechanical APDL Basic Analysis Guide - Ansys
Mechanical APDL Basic Analysis Guide - Ansys Mechanical APDL Basic Analysis Guide - Ansys
Chapter 21: Memory Management and Configuration halves until it can allocate additional memory. If not specified, MEM_GROW defaults to one-half the initial scratch space. To turn off dynamic memory allocation (use a fixed-memory model), set MEM_GROW=0. LOCALFIL is a key that determines when files are to be closed: 0 (globally closed) or 1 (locally closed). It defaults to 0 (globally closed) and can be changed at the Begin level with the /CONFIG,LOCFL command. This key is applicable only to the EROT, ESAV, EMAT, FULL, and TRI files. Locally closed files (LOCALFIL=1) may be deleted earlier during solution if requested with the /FDELE command. This may be helpful while running large problems. Globally closed files are closed at the end of the run and are not opened and closed each substep. This saves time in analyses with many substeps. CONTACTS is the number of contact elements that are expected to be in contact at any given time. It defaults to 1000 and can be changed at the Begin level with the /CONFIG,NCONT command. This is not the same as the total number of contact elements in the model. ORDERER_ is a key that determines the automatic element reordering scheme: 0 (WSORT,ALL), 1 (WAVES), or 2 (both). It defaults to 2 and can be changed at the Begin level with the /CONFIG,ORDER command. Any of the following nine keywords that you do not specify is set to 100 the first time ANSYS encounters it. Whenever the current maximum is exceeded, the keyword value automatically doubles. The maximum values are dynamically expanded, even at first encounter. • MX_NODES is the maximum number of nodes. You can change the value (on most systems) at the Begin level with the /CONFIG,MXND command. • MX_ELEMS is the maximum number of elements. You can change the value (on most systems) at the Begin level with the /CONFIG,MXEL command. • MX_KEYPT is the maximum number of keypoints. You can change the value (on most systems) at the Begin level with the /CONFIG,MXKP command. • MX_LINES is the maximum number of lines. You can change the value (on most systems) at the Begin level with the /CONFIG,MXLS command. • MX_AREAS is the maximum number of areas. You can change the value (on most systems) at the Begin level with the /CONFIG,MXAR command. • MX_VOLUS is the maximum number of volumes. You can change the value (on most systems) at the Begin level with the /CONFIG,MXVL command. • MX_REALS is the maximum number of sets of real constants (element attributes). You can change the value (on most systems) at the Begin level with the /CONFIG,MXRL command. • MX_COUPS is the maximum number of sets of coupled degrees of freedom. You can change the value (on most systems) at the Begin level with the /CONFIG,MXCP command. • MX_CEQNS is the maximum number of constraint equations. You can change the value (on most systems) at the Begin level with the /CONFIG,FMXCE command. FILESPLT is the integer value indicating the file split point in megawords. A megaword is 1024*1024 4-byte words, or 4 MB. All files that are eligible for splitting will be split into a new file every increment of xxxx megawords (where xxxx is the value specified with this keyword). You can change the value (on most systems) at the Begin level with the /CONFIG,FSPLIT command. See Splitting Files Across File Partitions in the Operations Guide for more information on splitting files. You can change many of the configuration settings at program start-up using ANSYS entry options, at the Begin level with the /CONFIG command, or with other ANSYS commands. In most cases, therefore, there is no need to create your own config130.ans file. Also, the default settings for each computer system have 314 Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
een chosen for efficient running of typical models on typical system configurations. Change them only for atypical models or atypical systems. Note for Distributed ANSYS Distributed ANSYS sets NO_ELDBW = 1 and NO_RSTGM = 1 and uses the default FSPLIT value. The NO_ELDBW, NO_RSTGM, and FSPLIT options cannot be changed when using Distributed ANSYS. 21.5. Understanding ANSYS Memory Error Messages This model requires more scratch space than available. ANSYS has currently allocated YY MB and was not able to allocate enough additional memory in order to proceed. Please increase the virtual memory on your system, and/or increase the work space memory and rerun ANSYS. Problem terminated. (Sparse or Block Lanczos solvers only): There is not enough memory for the solver to proceed. Please increase the virtual memory on your system and/or increase the work space memory and re-run ANSYS. Memory currently allocated for the solver = YY MB. (Sparse or Block Lanczos solvers only): There is not enough memory for the solver to proceed. Please increase the virtual memory on your system and/or increase the work space memory and re-run ANSYS. Memory currently allocated for the solver = YY MB. Memory currently required for the solver to continue = YYY MB. (Distributed Sparse solver only): There is not enough memory for the Distributed Sparse solver to proceed. Please increase the virtual memory on your system and/or increase the work space memory and re-run ANSYS. Memory currently allocated by ANSYS = YY MB. Memory allocation attempted = YYY MB. Largest block of ANSYS memory available for the Distributed Sparse solver = YYYY MB. The messages listed above may occur while you are running ANSYS. This type of message appears when you are running ANSYS in dynamic memory mode and ANSYS has attempted to allocate additional memory, but it failed because it could not find a large enough contiguous block of memory to proceed. On either 32-bit or 64-bit systems, specifying a higher -m value on the ANSYS execution command and executing ANSYS again may help. However, if a large enough block of memory is still unavailable, changing the -m value will not help. You can also try decreasing the database size to help free up more workspace, allowing you to continue with the analysis. On 64-bit systems, increasing the system virtual memory may help. Try increasing the system virtual memory so that the physical memory (i.e., RAM) plus the virtual memory comfortably exceeds the memory available at the failure point (shown in the error message). For more information, see Memory Management and Configuration in the Basic Analysis Guide. The memory (-m) size requested is not currently available. Reenter ANSYS command line with less memory requested. The database (-db) space requested is not currently available. Reenter ANSYS command line with less database space requested. Either of these messages may occur at ANSYS startup. 21.5. Understanding ANSYS Memory Error Messages Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates. 315
- Page 279 and 280: Chapter 16: Annotation A common ste
- Page 281 and 282: 16.3. 3-D Annotation 3-D text and g
- Page 283 and 284: Chapter 17: Animation Animation is
- Page 285 and 286: • ANMODE (Utility Menu> PlotCtrls
- Page 287 and 288: Figure 17.2 The Animation Controlle
- Page 289 and 290: Note If you are doing animation fro
- Page 291 and 292: Chapter 18: External Graphics Besid
- Page 293 and 294: 18.1.4. Exporting Graphics in UNIX
- Page 295 and 296: Note The commands discussed in this
- Page 297 and 298: 18.3.6. Editing the Neutral Graphic
- Page 299 and 300: Chapter 19: The Report Generator Th
- Page 301 and 302: 2. Specify a caption for the captur
- Page 303 and 304: 19.4.1.1. Creating a Custom Table I
- Page 305 and 306: Table ID 46 47 48 Description Compo
- Page 307 and 308: Button or Field DYNAMIC DATA REPORT
- Page 309 and 310: The HTML tag to begin JavaScript co
- Page 311 and 312: listingName A unique listing name a
- Page 313 and 314: Chapter 20: File Management and Fil
- Page 315 and 316: 20.4. Text Versus Binary Files Depe
- Page 317 and 318: Identifier ELEM EMAT ERR ESAV FATG
- Page 319 and 320: 20.4.3. File Compression Many file
- Page 321 and 322: You can also redirect graphics outp
- Page 323 and 324: Chapter 21: Memory Management and C
- Page 325 and 326: 21.3.3. Changing Database Space Fro
- Page 327 and 328: Figure 21.4 Dividing Work Space ANS
- Page 329: NUM_BUFR is the number of buffers p
- Page 333 and 334: Index Symbols 3-D graphics devices,
- Page 335 and 336: path plots, 142 POST26 graphs, 200
- Page 337 and 338: fatigue graphs, 257 files, 277 focu
- Page 339 and 340: material model interface, 8 materia
- Page 341 and 342: multiframe, 117 restarting an analy
- Page 343 and 344: WINDOW command, 227 Windows graphic
een chosen for efficient running of typical models on typical system configurations. Change them only for<br />
atypical models or atypical systems.<br />
Note for Distributed ANSYS Distributed ANSYS sets NO_ELDBW = 1 and NO_RSTGM = 1 and uses the<br />
default FSPLIT value. The NO_ELDBW, NO_RSTGM, and FSPLIT options cannot be changed when using Distributed<br />
ANSYS.<br />
21.5. Understanding ANSYS Memory Error Messages<br />
This model requires more scratch space than available. ANSYS has currently allocated YY MB and was<br />
not able to allocate enough additional memory in order to proceed. Please increase the virtual memory<br />
on your system, and/or increase the work space memory and rerun ANSYS. Problem terminated.<br />
(Sparse or Block Lanczos solvers only): There is not enough memory for the solver to proceed. Please increase the virtual memory on your system and/or increase the<br />
work space memory and re-run ANSYS. Memory currently allocated for the solver = YY MB.<br />
(Sparse or Block Lanczos solvers only): There is not enough memory for the solver to proceed. Please increase the virtual memory on your system and/or increase the<br />
work space memory and re-run ANSYS. Memory currently allocated for the solver = YY MB. Memory currently required for the <br />
solver to continue = YYY MB.<br />
(Distributed Sparse solver only): There is not enough memory for the Distributed Sparse solver to<br />
proceed. Please increase the virtual memory on your system and/or increase the work space memory<br />
and re-run ANSYS. Memory currently allocated by ANSYS = YY MB. Memory allocation attempted =<br />
YYY MB. Largest block of ANSYS memory available for the Distributed Sparse solver = YYYY MB.<br />
The messages listed above may occur while you are running ANSYS.<br />
This type of message appears when you are running ANSYS in dynamic memory mode and ANSYS has<br />
attempted to allocate additional memory, but it failed because it could not find a large enough contiguous<br />
block of memory to proceed.<br />
On either 32-bit or 64-bit systems, specifying a higher -m value on the ANSYS execution command and<br />
executing ANSYS again may help. However, if a large enough block of memory is still unavailable,<br />
changing the -m value will not help. You can also try decreasing the database size to help free up more<br />
workspace, allowing you to continue with the analysis. On 64-bit systems, increasing the system virtual<br />
memory may help. Try increasing the system virtual memory so that the physical memory (i.e., RAM)<br />
plus the virtual memory comfortably exceeds the memory available at the failure point (shown in the<br />
error message).<br />
For more information, see Memory Management and Configuration in the <strong>Basic</strong> <strong>Analysis</strong> <strong>Guide</strong>.<br />
The memory (-m) size requested is not currently available. Reenter ANSYS command line with less<br />
memory requested.<br />
The database (-db) space requested is not currently available. Reenter ANSYS command line with<br />
less database space requested.<br />
Either of these messages may occur at ANSYS startup.<br />
21.5. Understanding ANSYS Memory Error Messages<br />
Release 13.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information<br />
of ANSYS, Inc. and its subsidiaries and affiliates.<br />
315
Change language