INTERNAL PROGRAMMING ERROR

narasimhamurthy
narasimhamurthy Altair Community Member
edited 2020 04 in Community Q&A

Hi,

 

i am performing buckling analysis but getting error as show in below.

 

*** INTERNAL PROGRAMMING ERROR ***

   in file 'xdsemx_i8.F', at location # 262.

 

       ioerr(1) =          1

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

 

i am using Optisrtuct 2018 version

 

how to solve this error?

 

 

Thanks and Regards,

Narasimhamurthy

 

Unable to find an attachment - read this blog

Answers

  • Rahul Rajan_21763
    Rahul Rajan_21763 New Altair Community Member
    edited 2019 16

    Could you just add PARAM,LGDISP,1 and run again.It seems this was fixed in the version(2018.0.1) which you are currently using.

    <?xml version="1.0" encoding="UTF-8"?>2018.0.1.JPG

  • narasimhamurthy
    narasimhamurthy Altair Community Member
    edited 2019 18

    Defined PARAM, LGDISP, 1

    but getting same error.

    Please find attached output file.

    Unable to find an attachment - read this blog

  • Rahul Rajan_21763
    Rahul Rajan_21763 New Altair Community Member
    edited 2019 20

    Could you also add PARAM, KGRGD, YES as per the warning mentioned in the .out file. If it gives an error, then please share .out and .stat file.

  • narasimhamurthy
    narasimhamurthy Altair Community Member
    edited 2019 22
  • Rahul Rajan_21763
    Rahul Rajan_21763 New Altair Community Member
    edited 2019 22

    Please remove special character (- _ . % etc)used in part name/file name/user name & also change the run folder.Run again and let us know the outcome.

  • narasimhamurthy
    narasimhamurthy Altair Community Member
    edited 2019 24

    not yet solved.

     

    Please find attached output file and stat file.

     

    Unable to find an attachment - read this blog

  • Rahul Rajan_21763
    Rahul Rajan_21763 New Altair Community Member
    edited 2019 25

    Can you give a final try by unchecking output request or param cards defined.In the past we have seen this programming error is mainly observed because of output request /param.

  • narasimhamurthy
    narasimhamurthy Altair Community Member
    edited 2019 31

    removed all PARAM and output request.

     

    but error not yet solved.

     

    Unable to find an attachment - read this blog

  • narasimhamurthy
    narasimhamurthy Altair Community Member
    edited 2019 04

    is there any solution to solve this error?

  • Rahul Rajan_21763
    Rahul Rajan_21763 New Altair Community Member
    edited 2019 05

    removed all PARAM and output request.

     

    but error not yet solved.

     

    Last shared files are based on 2017.2.So I am commenting based on the files shared in this quote using 2018.0.1

     

    This is related to some IO issue during a matrix vector multiplication in Lanczos. I am afraid I will need the model to see what could be the problem but as a workaround you could try using MUMPS as the lanczos solver via the solvtype card and see if it works out. Alternatively you could try ddm mode (even with 1 proc).

    Unable to find an attachment - read this blog