Handling of very large files
Altair EmployeeHi community,
I currently have a very large .hm/.fem file which I want to use in optistruct. The file has millions of elements (3D) due to a very complex shape. Although I do have a very powerful PC (190GB RAM, 2TB disk space etc.), I got the following error msg:
MEMORY ESTIMATION INFORMATION :
-------------------------------Solver Type is: Sparse-Matrix Solver
Direct Method
Current Memory (RAM) : 41148 MB
Estimated Minimum Memory (RAM) for Out of Core Solution : 41135 MB
Recommended Memory (RAM) for Out of Core Solution : 41148 MB
Recommended Memory (RAM) for In-Core Solution : 438587 MB
(Note: The Minimum Memory Requirement is limited by Output Module.)
DISK SPACE ESTIMATION INFORMATION :
-----------------------------------Estimated Disk Space for Output Data Files : 10808 MB
Estimated Scratch Disk Space for In-Core Solution : 23721 MB
Estimated Scratch Disk Space for Out of Core Solution : 546652 MB************************************************************************
BEGINNING ANALYSIS SOLUTION ....
************************************************************************ANALYSIS RESULTS :
------------------
*** WARNING # 1971
Current run is likely to fail due to insufficient disk space.
Estimated disk space requirement = 557460 MB
Estimated disk space available = 184013 MB
Suggestions to reduce disk space requirements:
For static analysis - reduce the number of loadcases.
For eigenvalue/buckling analysis - reduce frequency range in
EIGRL card or number of modes requested.
For FRF analysis - reduce the number of loading frequencies.
For transient analysis - reduce the number of output time steps.
ITERATION 0
*** ERROR # 2005 ***
WIN_IO: WriteFile failed. (112).
*** WARNING # 732
Nonzero iostat returned from access write.
File's unit number = 41
Record number = 167292
Buffer size = 131072
Access option = 2
Returned iostat = -3
*** ERROR # 2005 ***
WIN_IO: WriteFile failed. (112).
*** WARNING # 732
Nonzero iostat returned from access write.
File's unit number = 41
Record number = 167293
Buffer size = 131072
Access option = 2
Returned iostat = -3
*** ERROR # 2005 ***
WIN_IO: WriteFile failed. (112).
*** WARNING # 732
Nonzero iostat returned from access write.
File's unit number = 41
Record number = 167294
Buffer size = 131072
Access option = 2
Returned iostat = -3
*** ERROR # 2005 ***
WIN_IO: WriteFile failed. (112).
*** WARNING # 732
Nonzero iostat returned from access write.
File's unit number = 41
Record number = 167295
Buffer size = 131072
Access option = 2
Returned iostat = -3
*** ERROR # 2005 ***
WIN_IO: WriteFile failed. (112).
*** WARNING # 732
Nonzero iostat returned from access write.
File's unit number = 41
Record number = 167296
Buffer size = 131072
Access option = 2
Returned iostat = -3
*** ERROR # 2005 ***
WIN_IO: WriteFile failed. (112).
*** WARNING # 732
Nonzero iostat returned from access write.
File's unit number = 41
Record number = 167297
Buffer size = 131072
Access option = 2
Returned iostat = -3
*** ERROR # 2005 ***
WIN_IO: WriteFile failed. (112).
*** WARNING # 732
Nonzero iostat returned from access write.
File's unit number = 41
Record number = 167298
Buffer size = 131072
Access option = 2
Returned iostat = -3
*** ERROR # 2005 ***
WIN_IO: WriteFile failed. (112).
*** WARNING # 732
Nonzero iostat returned from access write.
File's unit number = 41
Record number = 167299
Buffer size = 131072
Access option = 2
Returned iostat = -3
*** ERROR # 2005 ***
WIN_IO: WriteFile failed. (112).
*** WARNING # 732
Nonzero iostat returned from access write.
File's unit number = 41
Record number = 167300
Buffer size = 131072
Access option = 2
Returned iostat = -3
*** ERROR # 2005 ***
WIN_IO: WriteFile failed. (112).
*** WARNING # 732
Nonzero iostat returned from access write.
File's unit number = 41
Record number = 167301
Buffer size = 131072
Access option = 2
Returned iostat = -3
*** More of ERROR messages # 2005 were suppressed...
****************
Too many error messages. Aborting run.
Current limit is 10000. Use 'MSGLMT' control card to change this value.
************************************************************************
Following warning messages appeared too many times
and were suppressed:
2005
Total of 9989 repeat error message(s) were suppressed.
To see more messages use 'MSGLMT' control card in the data or config file.
************************************************************************
There were 11 WARNING(s) reported during the run.
Since I wasn't sure if I hadn't enough RAM, I have started the analysis with the following options:
-core out -nproc 12 -optskip -checkel no
Unfortunately my run is active for more than 1 day and I have no idea, how to accelerate that analysis....
Do you have any inputs for accelerating simulations in optistruct? Thank you in advance.
BR
Answers
-
Please add the below param card to the deck
PARAM,HASHASSM,YES
And force the job to run with In-Core solution.Let us know if this helps
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
0 -
Hi @Musti
Clearly the error is due to insufficient disk space. Try to reduce the number of loading frequencies for FRF analysis.
If you are using Commercial HyperWorks suite, I would suggest to get in touch with your local support to get a quick solution.
0 -
Hi guys,
since I get these Informations quite late in the evening, I can't contact the hotline
/emoticons/default_sad.png' srcset='/emoticons/sad@2x.png 2x' title=':(' width='20' />
Today I've started the analysis with -core IN -nproc 12 -optskip -checkel no AND PARAM,HASHASSM,YES.
I have currently like 1,5TB space left but the following failure popped up... I will try to run the analysis on an external disk
*** ERROR # 7007 ***
The run failed because automatic memory expansion has failed.
Currently allocated working storage is 37224 MB.
Automatic expansion failed to expand to 441949 MB.
The failed amount is the minimum required memory to complete the run.
Please verify whether the system has enough memory and rerun the problem.
*** INFORMATION # 1991
Assembly module is not memory bottleneck - turning off hash assembly.0 -
Hi @Musti
You need to either expand the memory as @Q.Nguyen-Dai said or reduce the number of freq loading numbers and check if this goes through the memory error.
0
