HOME › FORUM › User Discussions › How to check the boundary and conectivity?
- This topic has 9 replies, 3 voices, and was last updated 5 years, 8 months ago by
mohammadshah.
-
AuthorPosts
-
November 7, 2015 at 1:56 am #252
kengawk
ParticipantI conduct an eigen analysis via OSN and failed with the following message.
ProfileSPDLinDirectSolver::solve() – aii < 0 (i, aii): (0,0)
I think there is a problem about the connectivity or boundary condition. As a matter of fact,before importing s2k file into OSN,I had eigen analysis in SAP2000 to make sure the connectivity and boundary condition.
However, this time the problem came out again.I cannot find the reason from visualized model. How can I find the it out? Programming a checking procesure for s2k file or tcl files?
-
This topic was modified 7 years, 7 months ago by
kengawk.
November 7, 2015 at 5:31 am #254kengawk
Participant.
.
.
ProfileSPDLinDirectSolver::solve() – aii < 0 (i, aii): (0,0)
domain error:argument not in valid range
while executing
“expr sqrt($lambda)”
(“foreach” body line 2)
invoked from within
“foreach lambda $lambda (
set omega [expr sqrt($lambda)]
set period [expr 2.0*$pi/$omega]
set frequ [expr 1.0/$perild]
puts $eigFID…”
(file “jjmrr.tcl” line 75)It seems that an unnecessary node could make the errors above when it exists in s2k file. This times it is hard to find them all out even in visualized model. In this situation, dead load analysis is failed too with the following erros.
UMD2FA:matrix is singular. Only 5244 pivots found.
WARNING UmfpackGenLinSolver::solve(void)-4 returned in factorization UMD2FA()
WARNING NewtonRaphson::solveCrrentStep()-the LinearSysOfEqn failed in solve()
StaticAnalysis::analyze()-the Algorithm failed at iteration:0 with domain at
load factor 1November 8, 2015 at 6:12 pm #255kengawk
ParticipantFree nodes have to be pick out by programming a checking free nodes or joints procedure for tcl files or s2k file. I made it,and the the eigen analysis is conducted.
But new problem comes out. The mode shape is failed to be ploted with the error message as following:
Index exceeds matrix dimensions.
Erro in PlotModeShape (line 98)
Error while evaluating UIControl Callback
Index exceeds matrix dimensions.
Error in PlotModeShape (line 157)
Error while evalutating UIControl Callback
Index exceeds matrix dimensions.
Erro in PlotModeShape (line 98)
Error while evaluating UIControl Callback
.
.
.
This model contains 1138 nodes and 1144 elements.November 10, 2015 at 10:54 pm #260Andreas Schellenberg
KeymasterYes, that is often a problem with SAP2000, because it will automatically eliminate/ignore degrees of freedom that are not connected to anything. However, OpenSees will not do this, so if you import a SAP2000 model that has dangling nodes or DOFs that are not connected to anything, the analysis in OpenSees will fail. You did the correct thing, by carefully checking your model for these conditions.
November 10, 2015 at 10:56 pm #261Andreas Schellenberg
KeymasterIf you would like to send me your model, I can check why the mode shapes are not being plotted.
November 11, 2015 at 9:15 pm #263kengawk
ParticipantThank you for your supports,Dr.Schellenberg.
I will send this model to you as soon as possible.
Hope it would not take too much of your time.I really appreciate your help!
Best wishes,
Ken
December 2, 2015 at 9:09 pm #272kengawk
ParticipantBy now, my answer is to program a checking procedure for a complicated model based on checking through the codes with naked eyes.
September 13, 2017 at 4:45 am #26826mohammadshah
ParticipantDear Kengawk,
I have a problem like you in my model. Let me know how I can find the nodes that have problems and also tell me how could I solve it?
Best
M
September 13, 2017 at 4:45 am #26827mohammadshah
ParticipantDear Kengawk,
I have a problem like you in my model. Let me know how I can find the nodes that have problems and also tell me how could I solve it?
Best
M
September 13, 2017 at 4:47 am #26828mohammadshah
Participant -
This topic was modified 7 years, 7 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.