Domain Decomposition Method ERROR # 3413

Hello to all,

I have a little problem with the Domain Decomposition Method and calculating on the cluster. I get the ERROR # 3413 which says, that non-static analysis is not supported. But I am calculating nonlinear quasi static and the documentation says that this case is supported by optistruct.

My approaches for the fault are:

- Wrong DOF of some parts and the parts are flying away but this should not bother the solver

-The documentation says: 'DDM allows you to run a single subcase of static analysis and/or optimization with multiple processors in either Shared Memory Processing (SMP) or Distributed Memory Processing (DMP) cluster computers.' I have more than one subcase

Has anyone an Idea what optisatruct is saying to me with non-static analysis?

Find more posts tagged with

English

OptiStruct

Accepted answers

All comments

Altair Forum User

Hi @DerPusher

Can you please share the entire out file?

Altair Forum User

I can give you first of all a picture of the solver output from yesterday. But i think it says the same thing as i explained.

out file will take a little time as i have to log-on into the cluster. But as i remember from yesterday, there is not really much more information as i mentioned.

Any Idea what 'non-static' could be?

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

Altair Forum User

@DerPusher

OK, I see that Non linear analysis is supported for DDM. I will check what is happening and will get back to you soon.

Altair Forum User

Another thing that could be the fault.

Preloading is not supported: I have modeled a press fit.

I have pretension of bolts in my simulation: To realize that the nodes of the Prentension surface are moved --> perhaps this is non-static?

Altair Forum User

Maybe,

can you remove pretension and check if that is working?

Altair Forum User

I will check it on the Weekend.

So if its helpful i have attached the stat and out file. Use Notepad++ cause with the standard editor from Windows the line breaks are not shown correctly

Unable to find an attachment - read this blog