system Mumps in OpenSeesSP and push over

This forum is for issues related to parallel processing
and OpenSees using the new interpreters OpenSeesSP and OpenSeesMP

Moderator: selimgunay

Post Reply
alirezacivil
Posts: 23
Joined: Mon Feb 16, 2015 8:39 pm

system Mumps in OpenSeesSP and push over

Post by alirezacivil » Tue Feb 28, 2017 1:41 am

I am doing gravity analysis and push over analysis in succession using OpenSeesSP.
When I use system Mumps in OpenSeesSP just for the gravity analysis it works. But it does not work for the push over analysis after performing gravity analysis.
What is the problem?

fmk
Site Admin
Posts: 5883
Joined: Fri Jun 11, 2004 2:33 pm
Location: UC Berkeley
Contact:

Re: system Mumps in OpenSeesSP and push over

Post by fmk » Tue Feb 28, 2017 8:40 pm

can you send the script.

alirezacivil
Posts: 23
Joined: Mon Feb 16, 2015 8:39 pm

Re: system Mumps in OpenSeesSP and push over

Post by alirezacivil » Tue Feb 28, 2017 11:06 pm

Hi Frank,

Thanks for your response.

First I perform gravity analysis with these scripts:
constraints Penalty 1.e25 1.e25
numberer RCM;
system Mumps;
test NormDispIncr 1.0e-6 20;
algorithm KrylovNewton ;
integrator LoadControl 0.1;
analysis Static;
analyze 10;

Then I carry out push over analysis with this code:
constraints Transformation;
numberer RCM;
system Mumps;
algorithm KrylovNewton ;
integrator DisplacementControl $IDctrlNode $IDctrlDOF $Dincr ;
analysis Static ;

In general, I am modelling a 12 storey building in 3D. The beam/column elements are elastic elements with concentrated hinges using zero length elements and shear walls are modelled using displacement beam column elements.
Because the code is too long, I cannot send it here. But, I can email you if it helps.

Also, I have another question, I saw somewhere you where suggesting to use:
system Mumps -ICNTL14 80;
What is it exactly, what does each number means?

Kind Regards,
Alireza

fmk
Site Admin
Posts: 5883
Joined: Fri Jun 11, 2004 2:33 pm
Location: UC Berkeley
Contact:

Re: system Mumps in OpenSeesSP and push over

Post by fmk » Wed Mar 01, 2017 11:51 pm

for now try without issuing the second system, numberer, algorithm, analsysis command .. as going from one static to another you do not need to redo these commands.

alirezacivil
Posts: 23
Joined: Mon Feb 16, 2015 8:39 pm

Re: system Mumps in OpenSeesSP and push over

Post by alirezacivil » Thu Mar 02, 2017 6:39 pm

Thanks.
It is ok now.

Can you please explain the "system Mumps -ICNTL14 80"? what is 80 means? I did not find it in wiki.

fmk
Site Admin
Posts: 5883
Joined: Fri Jun 11, 2004 2:33 pm
Location: UC Berkeley
Contact:

Re: system Mumps in OpenSeesSP and push over

Post by fmk » Mon Mar 06, 2017 9:17 pm

Mumps assumes a default amount of fill in during factorization and sets aside memory for it .. in a structural analysis problem if you have a number of MP constraints say for the floors this greatly increases the amount of fill in and the default is not going to be enough .. the switch just allocates more memory, 80 says it expects 80% fill in in the factorization.

alirezacivil
Posts: 23
Joined: Mon Feb 16, 2015 8:39 pm

Re: system Mumps in OpenSeesSP and push over

Post by alirezacivil » Thu Mar 09, 2017 3:40 pm

Hi Frank,
Thanks for your response.

I used -ICNTL 90. I got this error:
Work array too small; use -ICNTL14 option, the default is -ICNTL 20 make 20 larger.

The memory you are talking about is RAM in computer?
Should I enhance the RAM or I should use better CPU.
My CPU has 8 cores and I am using 7 cores to run the model. I kept one of them for windows to work on it.
What is your recommendation?

Thanks

fmk
Site Admin
Posts: 5883
Joined: Fri Jun 11, 2004 2:33 pm
Location: UC Berkeley
Contact:

Re: system Mumps in OpenSeesSP and push over

Post by fmk » Fri Mar 17, 2017 5:39 am

the memory is not RAM, it is memory the solver puts aside for fill in during the matrix factorization phase, 90% says assume 90% fill in .. which is incredibly large for a sparse matrix, might as well make a full matrix.

Post Reply