INTERNAL ERROR in ESLM when buckling (LAMA) constraint included

Altair Forum User
Altair Forum User
Altair Employee
edited October 2020 in Community Q&A
The following internal error occurs only when I include linear buckling constraint in ESLM.  Does it mean linear buckling responses are not allowed inside ESLM nonlinear response optimization?

When considering traditional linear responses e.g. stress, displacement from linear subcases together with nonlinear responses, ESLM works fine for my application,

 

 

*** ERROR # 266 ***

 Specified matrix number 1 out of allowed range (1-0).

  

 

 *** INTERNAL PROGRAMMING ERROR ***

   in file 'fiospa_new.F', at location # 1362.

  

       ioerr(1) =         13

       ioerr(2) =          1

 ****  ABORTING RUN DUE TO AN INTERNAL ERROR  ****

  

 

 

Solver FAILED

 

input (*.fem), output (*.out) and *.stat files are located at:


 

Regards,

Tanut

 

P.S. HW Solvers 13.0.210 version was utilized.

Tagged:

Answers

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited February 2015

    Hi,

     

    I am checking with the developers on this. I will get back to you ASAP!

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited February 2015

    Many thanks Prakash!

     

    In case an older version works well with this type of application, please recommend it (plus a way to download it) to me.

     

    Regards,

    Tanut

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited February 2015

    P.S. Optistruct 13.0.210 complains an internal error when running ESLM optimizaiton with several loadcases. I have to get back to 13.0.0.98 to avoid this.

     


    ************************************************************************

      

     ANALYSIS COMPLETED.

      

      

     

     *** INTERNAL PROGRAMMING ERROR ***

       Access DSET 'B2Bigridexp' for wrong record 3 (only 2 exist)

      

      

     Error message 2 from operating system:

    No such file or directory

     

    ************************************************************************

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited February 2015

    Dear Prakash,

     

    May I ask if there is any update on this matter?

     

    Regards,

    Tanut

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited February 2015

    Hi Tanut,

     

    Our developers are looking into this issue.

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2015

    Thanks Prakash, please let us know whenever this problem is fixed.

     

    Tanut

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2015

    Hi,

     

    For now there is a workaround to get rid of the error.

     

    Include PARAM,ALTBUCK,0  in the deck. Edit the solver deck with notepad and supply the  PARAM,ALTBUCK,0 as shown in the attached image.

     

    Note: The ALTBUCK card cannot be accessed through GUI. It should be manually supplied in the deck.

    <?xml version="1.0" encoding="UTF-8"?>post-7616-0-00089300-1431508460_thumb.jp

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2015

    Thank you Prakash!

     

    It works but not completely.

     

    When I have other constraint e.g. displacement limit for nonlinear loadcase in addition to buckling constraint (LAMA), I get this programming error:

     

    START RUNNING MODULE :  NLGSLV ...

     

     

     *** INTERNAL PROGRAMMING ERROR ***

       in file 'xresults.F', at location # 1058.

      

     ****  ABORTING RUN DUE TO AN INTERNAL ERROR  ****

     

    Please see my input file in your Dropbox: V512_RF_COMP_M_11.fem
  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2015

    Hi,

     

    I shared a file with you. Please use that and check if you still get the same error.

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2015

    I still get the same error, so I should check your Optistruct verison.

    Mine is

     

     OptiStruct  Version 13.0.210.001

     Time of build : 23:21:01

     Date of build : Jan 12 2015

     Build tag     : 0751393_5533130_Ce64RBW8UH12M:96526

     Supported H3D : v12.0

     Radflex name  : radflex_13_win64.exe

     Use version : 130131112 or higher

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2015

    Hi,

     

    I have the same version

     

    OptiStruct  Version 13.0.210.001

     Time of build : 23:21:01

     Date of build : Jan 12 2015

     Build tag     : 0751393_5533130_Ce64RBW8UH12M:96526

     Supported H3D : v12.0

     Radflex name  : radflex_13_win64.exe

       Use version : 130131112 or higher

     

    Can you try the same model on another machine?
  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2015

    FYI,

     

    attaching the .out file

     

    Unable to find an attachment - read this blog

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2015

    Many thanks Prakash for your great support but I think we are mixing up TWO models here...

     

    The test.txt file you just sent above does not reflect my problematic model. So, I attach the file I am struggling with here again:

     

    https://www.dropbox.com/sh/0nqezeb8q95cbf1/AACjXJYzpkCudD8KOG0Sz2Gva?dl=0

     

    If you can run the attached file, please let me know.

     

    Many thanks,

    Tanut

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2015

    Hi Tanut,

     

    I think yes, sorry about that. 

     

    I checked with experts and suggested to remove the CSTRESS= ALL output from implicit dynamic subcase (make sure PARAM, ALTBUCK, 0 is still available).

     

    I ran withtout CSTESS and the analysis is through the error.

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2015

    Thank you so much Prakash!

    It went well.

     

    Tanut

Categories