The OpenSees Community

Deal all,

I was wondering if there is any future plan for updatingMakefile.def for macOS.

For example, Makefile.def for Ubuntu is quite well instructed.
I can easily compile OpenSees 3.1.0 in Ubuntu by simply following the instructions written in "MAKES/Makefile.def.EC2-UBUNTU".

However, for macOS, the update for Makefile.def is stuck at macOS 10.8 ("Makefile.def.MacOS10.8" is the latest) and I face countless errors when I try to compile OpenSees 3.1.0 in macOS. (most of the errors are related to fortran, openssl)
It would be greatly appreciated if Makefile.def for macOS Catalina is updated soon.

best regards.

Hello,

I'm experiencing a problem while using Joint2D in macOS Catalina.

Joint2D element requires input parameters as shown below:
"element Joint2D $eleTag $Nd1 $Nd2 $Nd3 $Nd4 $NdC <$Mat1 $Mat2 $Mat3 $Mat4> $MatC $LrgDspTag"

If I set "$Mat1 $Mat2 $Mat3 $Mat4" to zero, OpenSees returns "segmentation fault: 11" in macOS Catalina.

an example line is shown below:
"element Joint2D 10100 10101 10102 10103 10104 10100 10101 10102 0 10104 10100 0;"

The exact same code works fine in Windows 10 (version 1903).

If I don't use zeros in "<$Mat1 $Mat2 $Mat3 $Mat4>", "segmentation fault: 11" does not happen.

example code is provided below::

########## ########## ########## ##########
# Define dimensions #
########## ########## ##########
model BasicBuilder -ndm 2 -ndf 3;
########## ########## ##########
# joint nodes #
########## ########## ##########
puts "node"
node 10101 10.000000 100.000000;
node 10102 0.000000 110.000000;
node 10103 -10.000000 100.000000;
node 10104 0.000000 90.0000000;
node 10201 310.000000 100.000000;
node 10202 300.000000 110.000000;
node 10203 290.000000 100.000000;
node 10204 300.000000 90.0000000;
########## ########## ##########
# support node
########## ########## ##########
node 102 0.00000000 0.00000000;
node 202 300.00000007 0.00000000;
########## ########## ##########
# Fix nodes #
########## ########## ##########
puts "fix"
fix 102 1 1 1;
fix 202 1 1 1;
########## ########## ########## ##########
# geomtransf
########## ########## ########## ##########
puts "geomTransf"
geomTransf PDelta 1;
geomTransf Linear 2;
########## ########## ##########
# column mat
########## ########## ##########
puts "col mat"
uniaxialMaterial Elastic 10000 2000000.;
########## ########## ##########
# column ele
########## ########## ##########
puts "col ele"
element elasticBeamColumn 1010100 102 10104 99999. 99999. 99999. 1; # NS=1, NB=1
element elasticBeamColumn 1010200 202 10204 99999. 99999. 99999. 1; # NS=1, NB=2
########## ########## ##########
# beam ele
########## ########## ##########
puts "beam ele"
element elasticBeamColumn 2010100 10101 10203 99999. 99999. 99999. 2; # NS=1, NB=1
########## ########## ##########
# jnt ele
########## ########## ##########
puts "jnt ele"
element Joint2D 10100 10101 10102 10103 10104 10100 10000 0 0 10000 10000 0; # this prompts "Segmentation fault: 11"
element Joint2D 10200 10201 10202 10203 10204 10200 0 0 10000 10000 10000 0; # this prompts "Segmentation fault: 11"

# element Joint2D 10100 10101 10102 10103 10104 10100 10000 10000 10000 10000 10000 0; # this one works fine"
# element Joint2D 10200 10201 10202 10203 10204 10200 10000 10000 10000 10000 10000 0; # this one works fine"
########## ########## ########## ##########
# analysis
########## ########## ########## ##########
puts "analysis"
set Tol 1.0e-8;
constraints Transformation;
numberer RCM;
system BandGeneral;
test EnergyIncr $Tol 3000 0;
algorithm Newton -initial;
integrator LoadControl 0.1;
analysis Static;
analyze 10;
loadConst -time 0.0
########## ########## ########## ##########

Thank you for your help!

deal all.

I have been trying to make a slight modification to Fatigue material.
But I'm facing some difficulties...

1. OPS_GetNumRemainingInputArgs()
this command is originally included in Fatigue material. but this command does not seem to work properly in custom model (*.DLL).
Compiling is successful even if i don't remove this line.
However, opensees fails to run (terminates with pop-up "Opensees.exe has stopped working").
I also added these codes below to see what happens :
int numdata = OPS_GetNumRemainingInputArgs();
opserr << "num Input : " << numdata << endln;

the printed value was "0", regardless of the length of input.

2. OPS_getUniaxialMaterial() does not seem to work either..
In Fatigue material, this command is necessary...
I tried these codes to see what happens:
UniaxialMaterial* mat = OPS_getUniaxialMaterial(idata[1]);
opserr << "mat : " << mat << endln;

the printed value was "empty".

If anyone knows how to solve this issue, please help me.

my system is:
Windows 10 64-bit
tcl 8.5 32-bit
OpenSees 2.5.0 32-bit
Visual Studio 2015

regards.

Dear fmk,
thank you very much for your detailed reply.

I'm so sorry but I can't understand answer 3.
I feel so shame on my ignorance, but I don't see the difference between command prompt (cmd.exe) and terminal application/Dos prompt.
(mpiexec and opensees are included in the PATH environment)

and your suggestion about multiple sequential jobs are quite amazing idea.
I should consider modifying my code to run opensees in multiple.
(currently, the analysis should be done one after another. because the following analysis is based on the previous one.)

Dear fmk,
thank you very much for your reply!

I re-run the analysis to see the differences as you suggested.

OpenSees (1 node) + "system BandGeneral" : 8857 milliseconds
OpenSees (1 node) + "system Mumps" : 12644 milliseconds
OpenSeesSP (4 nodes) + "system BandGeneral" : 4968 milliseconds
OpenSeesSP (4 nodes) + "system Mumps" : 12338 milliseconds

If slow analysis of Mumps is due to the stiffness matrix, I would try other examples.
and I would like to ask you some questions.
1. what are "page faults"?

2. for the case of using OpenSeesMP, what is the best way to assign elements to cores? (substructuring?)
assume a building with 8 floors and 4 spans
method 1 - assign elements horizontally
floor 1 to 4 : assign to core 0
floor 5 to 8 : assign to core 1

method 2 - assign elements vertically
column span 1 to 2 : assign to core 0
column span 3 to 4 : assign to core 1

3. Is there any way for mpiexec.exe to stay in memory?
every time I type "mpiexec -n 4 ~~~" in command prompt (or MATLAB), it launches mpiexec and exits when OpenSees terminates.
this launching and exiting process takes approximately 5 to 10 seconds.
It is so time wasting when performing repeated batch analysis.

the problem is resolved.
it looks like "system Mumps" command and "analysis Static" command shouldn't be declared more than once...

and after this problem is resolved, another problem took place.

I have no idea why, but "system Mumps" command increases analysis time...
below are cyclic analysis comparisons. [example 5] is modified to repeat 10 times per cycle.

OpenSees (1 node) + "system BandGeneral" : 9252 milliseconds
OpenSeesSP (4 nodes) + "system BandGeneral" : 5185 milliseconds
OpenSeesSP (4 nodes) + "system Mumps" : 13072 milliseconds

question 1. why is "system Mumps" slows down OpenSeesSP?
question 2. how come "system BandGeneral" can solve equations in parallel? it is not written in the manual...

any help would be grateful.

dear all,

I have problem running scripts with OpenSeesSP.
I tried with "OpenSees Example 5. 2D Frame, 3-story 3-bay" example.
link : http://opensees.berkeley.edu/wiki/index ... _W-Section

here are some modifications I've made. it was necessary to run this script with OpenSeesSP.

1. changed "system BandGeneral" to "system Mumps" in "Ex5.Frame2D.build.InelasticFiberWSection.tcl".
2. also removed system declaration term in "LibAnalysisStaticParameters.tcl".
(it seems like duplicated declaration of "system Mumps" results in freezing issue.)
3. removed OpenSeesSP incompatible recorders (e.g., drift recorder )
4. modified 6-dof lateral loads to 3-dof. (Ex5.Frame2D.analyze.Static.Push.tcl)
5. modified "source GeneratePeaks.tcl" to "source LibGeneratePeaks.tcl" in "Ex5.Frame2D.analyze.Static.Cycle.tcl"

execution command : mpiexec -n 4 OpenSeesSP runCyclic.tcl

in the "runCyclic.tcl" :
source Ex5.Frame2D.build.InelasticFiberWSection.tcl
source Ex5.Frame2D.analyze.Static.Cycle.tcl

these errors when I use Mumps :
WARNING MumpsParallelSolver::setSize(void)- Error -3 returned in substitution dmumps()
WARNING:MumpsParallelSOE::setSize : solver failed setSize()
StaticAnalysis::handle() - LinearSOE::setSize() failedStaticAnalysis::analyze() - domainChanged failed at step 0 of 1
OpenSees > analyze failed, returned: -1 error flag
Trying Newton with Initial Tangent ..

although four OpenSeesSP process was running, the analysis won't progress...
after several minutes, MPIEXEC times out.

and these are part of error messages when I use SparseGEN instead of Mumps :
DistributedSuperLU::DistributedSuperLU()
DistributedSuperLU::recvSelf(int cTag, Channel &theChannel) - START
DistributedSuperLU::recvSelf(int cTag, Channel &theChannel) - END
DistributedSuperLU::sendSelf(int cTag, Channel &theChannel) - 5
DistributedSuperLU::sendSelf(int cTag, Channel &theChannel) - 5
Fatal error in PMPI_Comm_create: Other MPI error, error stack:
PMPI_Comm_create(609).........: MPI_Comm_create(comm=0xc40300f8, group=0xc80100f8, new_comm=0202E3CC) failed
PMPI_Comm_create(590).........:
MPIR_Comm_create_intra(250)...:
MPIR_Get_contextid(521).......:
MPIR_Get_contextid_sparse(752): Too many communicators

my system : Windows 10 Pro with intel Skylake CPU. (with OpenSeesSP 2.5.0)
any help would be grateful.
regards.

Dear fmk,

thank you for your kind reply.
now i see the clear difference between betaKCurrent and betaKComm.

thank you very much.

No, unfortunately, it is not solved.

instead, I compiled *.dylib as a temporal solution.

I'm going to re-try to resolve this error (or at least, find out causes of the errors) about a couple of weeks later.

Dear fmk,
thank you for your kind reply!

I'll try using modalDamping command, and I will notice you if something is amiss.

and I would like to ask you one more question.
if 'betaKcomm' is stiffness matrix of the last committed time step, what is the difference between betaKCurrent and betaKcomm?
this is really confusing to me..
because, I thought 'current stiffness matrix' was the stiffness matrix of the last committed time step..
is betaKCurrent has something to do with stiffness matrix of the trial time step?

Dear fmk,
sorry for my late respond...

I understand that 'betaKinit' is recommended when no proper reason is provided.
but what i would like to ask you is how '$betaKcomm' is measured in OpenSEES.

the followings are my presumptions about "$betaK"s.
$betaKinit seems to be related to elastic stiffness when very small displacement is applied on the structure (or element, etc).
$betaK seems to be tangent stiffness of the structure behaving inelastically.
but I have no idea how $betaKcomm is measured...

I would like to ask another question.
I have read some papers about rayleigh damping, and I found this:
http://onlinelibrary.wiley.com/doi/10.1 ... 2/abstract

this paper recommends using "modal superposition method" implemented in OpenSEES.
Is this method still in development? or already implemented?

deal all,

I would like to ask a question about rayleigh command.

the usage of rayleigh command :
rayleigh $alphaM $betaK $betaKinit $betaKcomm

I can see that $alphaM is same as 'a0' term explained in a text book 'Dynamics of structures' written by prof chopra.
and $betaKinit has something to do with 'a1' term in dynamics of structures.

$betaK seems to be related with tangent stiffness as the element goes inelastic range.

the problem is, I have no idea what $betaKcomm does..

in the command manual, it says "factor applied to elements committed stiffness matrix."
I have no idea what 'committed' means..

any help, suggestions, or reference recommendation would be appreciated.

regards

Dear Sanjeema,

The first time i successfully compiled ElasticPP.dll was about an year ago. at that time, win32functions.cpp had no problem.

but when I tried compiling same example with the newest svn, it gave me same error as yours. (related with 'win32functions.cpp')

I think there are some problems with the newest "win32functions"...

I remember that i had problem compiling example material(elasticPPcpp) with core directory alone.
but searching missing files and then pasting into my additional library (or core folder) solved the issue.

first of all, I downloaded whole files from OpenSees svn. (http://opensees.berkeley.edu/OpenSees/developer/svn.php)

while building custom materials, whenever error messages('missing files') pop up, i searched the whole svn directory and copied necessary files into my library.


i believe 'EigneSOE.h.' is located in /SRC/system_of_eqn

for more details about missing files :
Visual studio : I drag & dropped missing files in the 'Source Files' folder located in the solution explorer.

OS X :
method one - simply copy missing files in the same folder where "makefile" exists.
or method two - add more file path to the variable "INCLUDE" in the makefile.def.



and here's some questions i would like to ask.
1) is 64-bit OpenSees any better than 32-bit one? if not, it'd be better to use 32-bit OpenSees
2) how did you successfully created dll, while some files are missing?