question on performing modal analysis in OptiStruct

Altair Forum User
Altair Forum User
Altair Employee
edited October 2020 in Community Q&A

Dear all:

 

I have  a model with plenty of elements (4,383,225) in OptiStruct for modal analysis. And I got the following error, would you please help on how to solve this problem?

Thank you for your help.


 
 *** ERROR # 2005 ***
 WIN_IO: WriteFile failed. (112).
 
 ****************
 Too many error messages. Aborting run.
 Current limit is 10000. Use 'MSGLMT' control card to change this value.
  

Answers

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited April 2018

    Hi @baozaizhang

     

    Looks like there isn't enough disk space.

     

    Could you please check the .out file for information about available and estimated disk space?

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2018

    I am having this same issue when running a frequency response analysis as well. How do I allocate more disk space or reduce the amount of disc space needed?

     

    I am using a tet 10 mesh element size 4 I believe

     

    Unable to find an attachment - read this blog

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2018

    Hi @Ryan JAntsch

     

    WARNING # 1971
     Current run is likely to fail due to insufficient disk space.
     Estimated disk space requirement = 754746 MB
     Estimated disk space available = 98047 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.

     

     

    You can redirect the scratch file writing directory to another temporary folder.  

     

    Please refer to the post:

    https://forum.altairhyperworks.com/index.php?/topic/18600-frf-analysis-error-151/&tab=comments#comment-37700