*** ERROR # 3405 ***

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

A fatal error has been detected during input processing:

 

  *** ERROR # 3405 ***

  Internal overflow happened due to the large size of model.

  This version of OptiStruct can not solve it.

 

Could somebody help me to solve this problem

Tagged:

Answers

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited August 2017

    Hi Mithun,

     

    This error is due to huge model size

     

    Does it happen in 2017.2 HyperWorks?

     

     

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited August 2017

    yeah its the same in that as well. btw did you get a chance to look at the model.  In the model  I sent you, what do you think is the best constraint for the send part of optimization

  • AxxAxx
    AxxAxx New Altair Community Member
    edited November 2017

    So I'm Also having this problem on 2017.2.

     

    Model summary:

    FINITE ELEMENT MODEL DATA INFORMATION :
    ---------------------------------------

      Total # of Grids (Structural)        :    510577
      Total # of Elements Excluding Contact:   2829184
      Total # of S2S Contact Elements      :     16189 (no internally created CGAPG)
      Total # of Degrees of Freedom        :   1513786
      (Structural)
      Total # of Non-zero Stiffness Terms  :  36782845

     

    Hardware:

     ************************************************************************
      **                Linux  3.0.101-63-default                 
     **         48 CPU:  Intel(R) Xeon(R) CPU E7-8857 v2 @ 3.00GHz         
     **                        CPU speed  3000 MHz                         
     **                   1033916 MB RAM,  65473 MB swap                  

     

    Anyone know if there is a solution? 

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited November 2017

    Hi,

     

    Let me guess, you have lot of elements and many load cases.  Try unchecking a few load cases for the analysis

  • AxxAxx
    AxxAxx New Altair Community Member
    edited November 2017

    Hi, with help of the Altair Support I found the solution. 

     

    Solution for me was to put the '-i64' flag as a run option.

    '-i64'             Use executable compiled with 64-bit integer, same as -altver i64

     

    You can see my model size above and I had two loadcases.

     

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited November 2017

    Hi,

     

    Using 64 bit solver should solve with 2017.2.

     

    You can add this using ControlCards>>PARAM>>I64SLV

Categories