Search found 13 matches
- Tue Feb 18, 2020 6:30 pm
- Forum: OpenSees.exe Users
- Topic: For 3D SSI problem in Opensees giving eqdof or rigidlink b/n structure base & proximity stdbrick element node didnt work
- Replies: 0
- Views: 2321
For 3D SSI problem in Opensees giving eqdof or rigidlink b/n structure base & proximity stdbrick element node didnt work
I defined my structure with a model builder of -ndm 3 -ndf 6 and my soil as -ndm 3 -ndf 3 with a stdbrick element. I connected the base of the structure with the brick elements with eqdof in dof1 and dof2. my analysis failed even for gravity load. what kind of constraints did you use to connect the base of the structure to the soil. I aslo tried to use rigid link, but it gave me an error because we cannot connect two nodes which have different dof. Michael midezutd@gmail.com
- Mon Feb 17, 2020 3:53 am
- Forum: OpenSees.exe Users
- Topic: 3d modeling of surface foundation on soil
- Replies: 4
- Views: 3970
Re: 3d modeling of surface foundation on soil
I defined my structure with a model builder of -ndm 3 -ndf 6 and my soil as -ndm 3 -ndf 3 with a stdbrick element. I connected the base of the structure with the brick elements with eqdof in dof1 and dof2. my analysis failed even for gravity load. what kind of constraints did you use to connect the base of the structure to the soil. Michael midezutd@gmail.com
- Thu Feb 13, 2020 6:21 am
- Forum: OpenSees.exe Users
- Topic: Error using Brick Element
- Replies: 4
- Views: 4191
Re: Error using Brick Element
I defined my structure with model builder of -ndm 3 -ndf6 and my soil as -ndm 3 -ndf 3 with brick element. I connected the base of the structure with the brick elements with eqdof in dof1 and dof2. my analysis failed even for gravity load. Michael midezutd@gmail.com
- Mon Feb 10, 2020 1:19 am
- Forum: OpenSees.exe Users
- Topic: can't use non-numeric floating-point value as operand of "/"
- Replies: 0
- Views: 2316
can't use non-numeric floating-point value as operand of "/"
I'm trying to do an analysis considering soil. I used Gid+Opensees to visualize my model and then get the tcl code. I get the following error.
#==================================================
can't use non-numeric floating-point value as operand of "/"
while executing
"expr 6.283185/sqrt($lam)"
("foreach" body line 2)
invoked from within
"foreach lam $lambda {
lappend T [expr 6.283185/sqrt($lam)]
}"
#==================================================
#==================================================
can't use non-numeric floating-point value as operand of "/"
while executing
"expr 6.283185/sqrt($lam)"
("foreach" body line 2)
invoked from within
"foreach lam $lambda {
lappend T [expr 6.283185/sqrt($lam)]
}"
#==================================================
- Mon Feb 10, 2020 1:03 am
- Forum: OpenSees.exe Users
- Topic: Solid+Beam Model Fails Eigenvalue Analysis
- Replies: 1
- Views: 2419
Re: Solid+Beam Model Fails Eigenvalue Analysis
I am having the same problem, how did you solve it?
- Sun Dec 15, 2019 4:52 pm
- Forum: OpenSees.exe Users
- Topic: BandSPDLinLapackSolver
- Replies: 2
- Views: 3110
Re: BandSPDLinLapackSolver
Is there any way I can model Shearwalls other than THUShell elements? Can I model elastic shear wall elements or by using fiber elements? I changed the column and beams to elastic elements but still, I got convergence errors when doing Pushover analysis or couldn't do Gravity analysis.
- Fri Dec 13, 2019 12:51 am
- Forum: OpenSees.exe Users
- Topic: ForceBeamColumn3d::update() -- could not invert flexibility
- Replies: 1
- Views: 3059
ForceBeamColumn3d::update() -- could not invert flexibility
I modeled a 4 story 2 way assymetric reinfoced concrete model in Opensees and when analyzing for gravity load I get the above error. I modeled the shearwall using multi-layer shell element THUShell. I was using "forceBeamColumn" element for the beam and column elements with Lobatto integrator. I also tried a "nonlinearBeamColumn" element. what is your recommendation to solve this error?
- Thu Dec 12, 2019 9:25 pm
- Forum: OpenSees.exe Users
- Topic: when using CuSP solver i get "Function load error! The version of DLL maybe incorrect." error. how can i solve it?
- Replies: 0
- Views: 3120
when using CuSP solver i get "Function load error! The version of DLL maybe incorrect." error. how can i solve it?
when using CuSP solver I get "Function load error! The version of DLL may be incorrect." error. how can I solve it?
- Mon Nov 18, 2019 10:08 pm
- Forum: OpenSees.exe Users
- Topic: problem while creating steel02
- Replies: 6
- Views: 6469
Re: problem while creating steel02
I came across the same error. Did you find a way to solve it?
https://opensees.berkeley.edu/community ... ED#p114021
https://opensees.berkeley.edu/community ... ED#p114021
- Mon Nov 18, 2019 10:05 pm
- Forum: Framework
- Topic: Cannot use PlainStressUserMaterial, no definition of PSUMAT
- Replies: 6
- Views: 16318
Re: Cannot use PlainStressUserMaterial, no definition of PSUMAT
I also came across a similar problem. Did you find any solution?
https://opensees.berkeley.edu/community ... ED#p114021
https://opensees.berkeley.edu/community ... ED#p114021
- Mon Nov 18, 2019 10:03 pm
- Forum: OpenSees.exe Users
- Topic: opensees3.0.3 cannot work well with PlaneStressUserMaterial
- Replies: 3
- Views: 3398
Re: opensees3.0.3 cannot work well with PlaneStressUserMaterial
I also came across a similar problem. Did you find any solution? Does using Mac version solve the problem or you found any other way?
https://opensees.berkeley.edu/community ... 1b#p114021
https://opensees.berkeley.edu/community ... 1b#p114021
- Mon Nov 18, 2019 7:41 pm
- Forum: OpenSees.exe Users
- Topic: PSUMAT - NOT DEFINED IN THIS VERSION, SOURCE CODE RESTRICTED
- Replies: 1
- Views: 2699
PSUMAT - NOT DEFINED IN THIS VERSION, SOURCE CODE RESTRICTED
I am using OpenSees windows Current version 3.0.3
I modeled a 3d structure with a shear wall. I used a multi-layer shell element for the simulation of shear wall components. PSUMAT - NOT DEFINED IN THIS VERSION, SOURCE CODE RESTRICTED error is halting me . nDmaterial PlaneStressUserMaterial is used to create the multi-dimensional concrete material model.
1. Can this material or any material related to this error be used in this version or do I need to change to other versions?
2. How can I solve this error?
I modeled a 3d structure with a shear wall. I used a multi-layer shell element for the simulation of shear wall components. PSUMAT - NOT DEFINED IN THIS VERSION, SOURCE CODE RESTRICTED error is halting me . nDmaterial PlaneStressUserMaterial is used to create the multi-dimensional concrete material model.
1. Can this material or any material related to this error be used in this version or do I need to change to other versions?
2. How can I solve this error?
- Wed Nov 06, 2019 10:32 pm
- Forum: OpenSees.exe Users
- Topic: BandSPDLinLapackSolver
- Replies: 2
- Views: 3110
BandSPDLinLapackSolver
Hi
I'm having a problem when I run a 3-D model for gravity load. My model is a two way asymmetric 4 story structure with Shear wall modeled with ShellMITC4. It appears to give this warning when running for gravity analysis.
Start of gravity analysis generation
WARNING BandSPDLinLapackSolver::solve() - the LAPACK routines returned 2
WARNING NewtonRaphson::solveCurrentStep() -the LinearSysOfEqn failed in solve()
StaticAnalysis::analyze() - the Algorithm failed at iteration: 0 with domain at load factor 1
OpenSees > analyze failed, returned: -3 error flag
I defined the my gravity analysis as follows:
# =================================================================================================================
puts "Start of gravity analysis generation"
# ------------------------------
wipeAnalysis ;
recorder Node -file L3.out -time -node 24 -dof 1 2 3 4 5 6 disp
# Create the system of equation, a sparse solver with partial pivoting
system BandSPD ;
# Create the constraint handler, the transformation method
constraints Plain ;
# Create the DOF numberer, the reverse Cuthill-McKee algorithm
numberer RCM ;
# Create the convergence test, the norm of the residual with a tolerance of
# 1e-12 and a max number of iterations of 10
test NormDispIncr 1.0e-12 25 3 ;
# Create the solution algorithm, a Newton-Raphson algorithm
algorithm Newton ;
# Create the integration scheme, the LoadControl scheme using steps of 0.1
integrator LoadControl 1 ;
# Create the analysis object
analysis Static ;
analyze 1
puts "End of gravity analysis generation"
## ------------------------------
## End of analysis generation
# ------------------------------
# =================================================================================================================
Thank you in advance for any consideration you give to my question.
I'm having a problem when I run a 3-D model for gravity load. My model is a two way asymmetric 4 story structure with Shear wall modeled with ShellMITC4. It appears to give this warning when running for gravity analysis.
Start of gravity analysis generation
WARNING BandSPDLinLapackSolver::solve() - the LAPACK routines returned 2
WARNING NewtonRaphson::solveCurrentStep() -the LinearSysOfEqn failed in solve()
StaticAnalysis::analyze() - the Algorithm failed at iteration: 0 with domain at load factor 1
OpenSees > analyze failed, returned: -3 error flag
I defined the my gravity analysis as follows:
# =================================================================================================================
puts "Start of gravity analysis generation"
# ------------------------------
wipeAnalysis ;
recorder Node -file L3.out -time -node 24 -dof 1 2 3 4 5 6 disp
# Create the system of equation, a sparse solver with partial pivoting
system BandSPD ;
# Create the constraint handler, the transformation method
constraints Plain ;
# Create the DOF numberer, the reverse Cuthill-McKee algorithm
numberer RCM ;
# Create the convergence test, the norm of the residual with a tolerance of
# 1e-12 and a max number of iterations of 10
test NormDispIncr 1.0e-12 25 3 ;
# Create the solution algorithm, a Newton-Raphson algorithm
algorithm Newton ;
# Create the integration scheme, the LoadControl scheme using steps of 0.1
integrator LoadControl 1 ;
# Create the analysis object
analysis Static ;
analyze 1
puts "End of gravity analysis generation"
## ------------------------------
## End of analysis generation
# ------------------------------
# =================================================================================================================
Thank you in advance for any consideration you give to my question.