peteroznewman
Subscriber

I tried solving on 18.2 your model on a computer with 192 GB of RAM, requested 15 cores. The only changes I made to your model is I set the Solver type to Iterative (PCG) instead of Direct (Sparse) and I removed the Command Object named shared out of core.  I let it run for 6 hours.


It has used 148 GB or 77% of the RAM and doesn't seem to be solving anymore.




The files on disk are < 9 GB.


The last few lines of solve.out are shown below:


ELEMENT TYPE  323 IS SHELL281. IT IS ASSOCIATED WITH ELASTOPLASTIC
MATERIALS ONLY. KEYOPT(8)=2 IS SUGGESTED AND HAS BEEN RESET.
KEYOPT(1-12)= 0 0 0 0 0 0 0 2 0 0 0 0

ELEMENT TYPE 324 IS SHELL281. IT IS ASSOCIATED WITH ELASTOPLASTIC
MATERIALS ONLY. KEYOPT(8)=2 IS SUGGESTED AND HAS BEEN RESET.
KEYOPT(1-12)= 0 0 0 0 0 0 0 2 0 0 0 0



*** NOTE *** CP = 4610.360 TIME= 00:489
This nonlinear analysis defaults to using the full Newton-Raphson
solution procedure. This can be modified using the NROPT command.

SOLUTION MONITORING INFO IS WRITTEN TO FILE= file.mntr

*** WARNING *** CP = 6576.456 TIME= 01:17:25
Material property EX of material 155 of element 259042 is evaluated at
a temperature of 22, which is below the supplied temperature range.
Temperature range checking terminates.
*WARNING*: Some MPC/Lagrange based elements (e.g.73784041) in real
constant set 726 overlap with other MPC/Lagrange based elements
(e.g.73786553) in real constant set 728 which can cause
overconstraint.

I think the solver is still running. It doesn't look like it, but it didn't run out of RAM or disk space.


When I issued the Stop command on the Solution control dialog, it stopped gracefully.