Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

ABORTING RUN DUE TO AN INTERNAL ERROR

*** INTERNAL PROGRAMMING ERROR ***
in file 'dppdrv1.F', at location # 1034.

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

************************************************************************
OptiStruct error termination report printed to file
'opti.stat'.

Someone please tell me what is the problem

Unable to find an attachment - read this blog

Find more posts tagged with

English

OptiStruct

Accepted answers

All comments

Altair Forum User

Hi Mithun,

Can you share the .out file please?

Altair Forum User

Unable to find an attachment - read this blog

Altair Forum User

Hi Mithun,

Can you try the same model with 2017 HyperWorks?

Looks like a programming error in 14.0 If you still face the error, please share the model file with us to investigate further.

Altair Forum User

Hi Prakash,

I tried it in HW2017 its the same, but its something else, because when i change from 'all' to 'displayed' it works and the wieder part is everything is displayed. Could you take a look at the model and also how can i upload the model so that it is only accessible to you.

Thanks in advance,

Mithun

Altair Forum User

Hi Mithun,

Thank you for sharing the model. I will get back to you soon.

Altair Forum User

Hi Mithun,

The error is because of huge number of design variables. We are checking with experts. I will share their suggestions and views ASAP!!!

Altair Forum User

hi, Prakash,

I have a doubt, as you know i am running a composite optimization and i am confused with the dconstraints. Currently i am using composite stresses 1, 2 and 12, but there are regions in the model ( at the joints) where the stresses are higher and this leads to constraint violation. Do you have any suggestions for the dconstraints?

Also did you have any success with the model?

cheers,

Mithun

Altair Forum User

Hi Mithun,

For internal programming error add I64 which uses 64bit solver with 2017

You can add this through PARAM>> I64SLV.

I need check the model further to understand the constraints and objectives. I will get back to you soon on this.