opensees report error,but i think it should work

Forum for OpenSees users to post questions, comments, etc. on the use of the OpenSees interpreter, OpenSees.exe

Moderators: silvia, selimgunay, Moderators

Post Reply
idkopensees
Posts: 5
Joined: Mon Nov 01, 2021 12:17 am

opensees report error,but i think it should work

Post by idkopensees » Sun Feb 27, 2022 4:38 am

its a CFS frame in opensees 2.5.0
wipe
puts "System"
model basic -ndm 2 -ndf 3
puts "restraint"
node 1 0.000E+000 3.000E+003
node 2 0.000E+000 0.000E+000
node 3 3.000E+003 3.000E+003
node 4 3.000E+003 0.000E+000
node 5 0.000E+000 0.000E+000
node 6 0.000E+000 3.000E+003
node 7 0.000E+000 3.000E+003
node 8 3.000E+003 3.000E+003
node 9 3.000E+003 0.000E+000
node 10 3.000E+003 3.000E+003
node 11 0.000E+000 0.000E+000
node 12 3.000E+003 0.000E+000
puts "mass"
mass 1 5.054E-002 5.054E-002 0.000E+000
mass 2 5.054E-002 5.054E-002 0.000E+000
mass 3 5.054E-002 5.054E-002 0.000E+000
mass 4 5.054E-002 5.054E-002 0.000E+000
mass 7 6.199E-001 6.199E-001 0.000E+000
mass 8 6.199E-001 6.199E-001 0.000E+000
mass 11 6.199E-001 6.199E-001 0.000E+000
mass 12 6.199E-001 6.199E-001 0.000E+000
puts "node"
fix 2 1 1 1;
fix 4 1 1 1;
puts "Equal DOF"
equalDOF 2 5 1 2
equalDOF 1 6 1 2
equalDOF 1 7 1 2
equalDOF 3 8 1 2
equalDOF 4 9 1 2
equalDOF 3 10 1 2
equalDOF 2 11 1 2
equalDOF 4 12 1 2
puts "material"
uniaxialMaterial Elastic 1 1.999E+005
uniaxialMaterial Elastic 2 2.550E+004
uniaxialMaterial Elastic 3 3.000E+004
uniaxialMaterial Pinching4 4 28600 3.8 55800 13 71500 27.8 60700 44.4 0.1 0.25 0.05 0.5 0.5 1.1 1.1 0.65 0.45 0.45 1.5 1.5 0.15 0.4 0.4 1.5 1.5 0.2 10 energy
puts "transformation"
geomTransf Linear 2
geomTransf Linear 5
geomTransf Linear 8
geomTransf Linear 12
geomTransf Linear 15
geomTransf Linear 19
puts "element"
element zeroLength 1 2 5 -mat 4 -dir 3
element elasticBeamColumn 2 5 6 1.000E+004 3.000E+004 1.250E+004 2
element zeroLength 3 6 1 -mat 4 -dir 3
element zeroLength 4 1 7 -mat 4 -dir 3
element elasticBeamColumn 5 7 8 1.000E+004 3.000E+004 1.250E+004 5
element zeroLength 6 8 3 -mat 4 -dir 3
element zeroLength 7 4 9 -mat 4 -dir 3
element elasticBeamColumn 8 9 10 1.000E+004 3.000E+004 1.250E+004 8
element zeroLength 9 10 3 -mat 4 -dir 3
element twoNodeLink 12 2 3 -mat 4 -dir 3 -orient -0.707 0.000 0.707
element twoNodeLink 15 1 4 -mat 4 -dir 3 -orient 0.707 0.000 0.707
element zeroLength 18 2 11 -mat 4 -dir 3
element elasticBeamColumn 19 11 12 1.000E+004 3.000E+004 1.250E+004 19
element zeroLength 20 12 4 -mat 4 -dir 3
puts "recorder"
recorder Node -file eigen1_node0.out -time -nodeRange 1 17 -dof 1 2 3 "eigen 1"
set numModes 12
set lambda [eigen $numModes]
set period "Periods.txt"
set Periods [open $period "w"]
puts $Periods " $lambda"
close $Periods
record

and error code is
ArpackSolver::Error with _saupd info = -9999
Could not build an Arnoldi factorization.IPARAM(5) the size of the current Arnoldi factorization: is 3factorization. The user is advised to check thatenough workspace and array storage has been allocated.
warning directintergrationanalisis::eigen()-eigensoe failed in solve()
node::geteigenvectors()-eigenvectors have not been set

mhscott
Posts: 875
Joined: Tue Jul 06, 2004 3:38 pm
Location: Corvallis, Oregon USA
Contact:

Re: opensees report error,but i think it should work

Post by mhscott » Sun Feb 27, 2022 7:10 am

You are probably asking for as many eigenvalues as there are dynamic DOFs. The default eigenvalue solver does not work when that is the case, so try asking for fewer eigenvalues.
https://portwooddigital.com/2020/11/01/ ... n-factors/

Post Reply