The OpenSees Community

I am using OpenseesSP to push a huge 3D model to a certain point.

When I change the number of cores or I run it in different computer, it affects the point which the model is diverging.

I wanted to know what is happening and how I can improve the convergence?


It should be noted that results are identical just the point which is not converging changes.

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

Can you please explain how we can do it?
Thanks

I was wondering is it possible to continue an analysis which is failed or finished?

For instance, If one pushes building to 1%, is it possible to push it further to 1.5% after the previous analysis is done and saved.

Or we should redo from zero?

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.

Hi,
Thanks for your response.

When I record the nodes in separate files ( each node in separate node command) opensees freezes. Without progressing in the analysis, it starts writing in the results folder and if I do not stop it, the volume of this folder can reach to 10 GB.

But I found the solution. I should write all of the node tags in one command of recorder. Then it is fine.

Hi,
Thanks for your response.

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.
I wanted to record each node rotations. When I use the recorder commands for one node it works. But when it comes to recording all of the nodes, it has some errors.

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

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?

Is there any limitation on the numbers of recorders using OpenSeesSP?
The recorders work individually but not together!

Dear fmk,

Thanks for your response.

Can you please explain it more?
Because when I use nodes with 3 coordinates, I see this "MVLEM:: setDomain,.: 2 coords required at nodes, not enough provided for element"
It seems that when I use nodes with 3 coordinates, it does not recognize. I was wondering that can you please explain how I can use nodes in 3D environment with 2 coordinates?

Thanks and Kind Regards

I was wondering to know that whether "SFI MVLEM - Cyclic Shear-Flexure Interaction Model for RC Walls " element is working in 3D environment or not.

Hi Jayanthan,
I could not get rational results from this element. But about the definition of the inputs, you can look this manual:
http://opensees.berkeley.edu/wiki/image ... Manual.pdf
Kind Regards,
Alireza

I found the reason why the material was not running.

It was because the optional part (<$ndI $ndJ $dof $perpDirn $delta>) in the command is not optional:
limitCurve Shear $curveTag $eleTag $rho $fc $b $h $d $Fsw $Kdeg $Fres $defType $forType <$ndI $ndJ $dof $perpDirn $delta>
It should be written, then it runs.

I have another question regarding this material. Is it possible to use SI units or the input should be in inch and Psi?
Thanks

Thanks for your response.

I wanted to use Hysteretic Material for this purpose but apparently this material is not working in this version of opensees.
Do you have other suggestions for the alternative material?
If not can you please introduce some references for coding a new material?

Thanks a lot.