questions about OS
Moderators: silvia, selimgunay, Moderators
-
- Posts: 37
- Joined: Sun Apr 01, 2007 7:35 pm
- Location: China
questions about OS
When I use the Example7 of Examples manual to do the pushover analysis, and only change the controlled dispalcement to 0.2*LBuilding-86.4 inch, the convergence failed at displacement 58.428.
The monitoring displacement-base force curve is not consistent with the concrete02 stress-strain curve. Why is the poseyielding curve up? Is this right?
When I use the concrete02 material to do the pushover of continuous girder bridge, the postyielding curve falls too quick ,I think it is not normal. Is this curve right?
Another question is the nodal result for displacement, velocity and acceleration is relative to ground or absolute.
recorder EnvelopeNode -file $dataDir/Nenvy.out -time -node 6 -dof 1 2 3 disp
recorder EnvelopeElement -file $dataDir/FEnvy175.out -ele 175 localForce
When I use these commands, no file is got. Is there something wrong?
The monitoring displacement-base force curve is not consistent with the concrete02 stress-strain curve. Why is the poseyielding curve up? Is this right?
When I use the concrete02 material to do the pushover of continuous girder bridge, the postyielding curve falls too quick ,I think it is not normal. Is this curve right?
Another question is the nodal result for displacement, velocity and acceleration is relative to ground or absolute.
recorder EnvelopeNode -file $dataDir/Nenvy.out -time -node 6 -dof 1 2 3 disp
recorder EnvelopeElement -file $dataDir/FEnvy175.out -ele 175 localForce
When I use these commands, no file is got. Is there something wrong?
what is the resultant hinge length?
the post-yield curve for the force-displacement is affected by the steel model. -- are you having a compression failure or a tension failure?
do the nodes and elements specified exist?
you should put in -time in the element recorder too.
the results for the pushover are relative, I believe.
the post-yield curve for the force-displacement is affected by the steel model. -- are you having a compression failure or a tension failure?
do the nodes and elements specified exist?
you should put in -time in the element recorder too.
the results for the pushover are relative, I believe.
Silvia Mazzoni, PhD
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
-
- Posts: 37
- Joined: Sun Apr 01, 2007 7:35 pm
- Location: China
Nonlinear Beam Column Element is used for Example07 and continuous girder bridge.
When the pushover is analyzed the following warnings appear.
WARNING: CTestEngernyIncr::test<> -the failed to converge after: 6 iterations
NewtnRaphson::solveCurrentStep<> -the convergenceTest object failed in test<>
StaticAnalysis::analyze<> - the Algotithm failed at iteration: 135 with domain at load factor 1.5262
analyze failed, returned: -3 error flag
.......
NewtonLineSearch::solveCurrentStep<> -the convergenceTest object failed in test<>
StaticAnalysis::analyze<> - the Algorithm failed at iteration: 0 with domain at load factor 1.52492
analyze failed, returned: -3 error flag
PROBLEM Pushover analysis: CtrlNode 141, dof 1, Disp=58.428 inch
the above warnings mean the result before load factor 1.52492 is believable ?
You mean the up postyielding curve affected by steel model(I use steelo2 material)is probably right?
I am sure the nodes and elements specified exist because I have use the Node Recorder and Element Recorder to get the results.
The nodal results and element results for earthquake dynamic analysis are relative or absolute?
Thank you for attention and reply!
When the pushover is analyzed the following warnings appear.
WARNING: CTestEngernyIncr::test<> -the failed to converge after: 6 iterations
NewtnRaphson::solveCurrentStep<> -the convergenceTest object failed in test<>
StaticAnalysis::analyze<> - the Algotithm failed at iteration: 135 with domain at load factor 1.5262
analyze failed, returned: -3 error flag
.......
NewtonLineSearch::solveCurrentStep<> -the convergenceTest object failed in test<>
StaticAnalysis::analyze<> - the Algorithm failed at iteration: 0 with domain at load factor 1.52492
analyze failed, returned: -3 error flag
PROBLEM Pushover analysis: CtrlNode 141, dof 1, Disp=58.428 inch
the above warnings mean the result before load factor 1.52492 is believable ?
You mean the up postyielding curve affected by steel model(I use steelo2 material)is probably right?
I am sure the nodes and elements specified exist because I have use the Node Recorder and Element Recorder to get the results.
The nodal results and element results for earthquake dynamic analysis are relative or absolute?
Thank you for attention and reply!
the uniform excitation analysis results are relative.
there is a problem with your analysis, it seems. some section has reached its strain limits, likely. check the local response.
there is a problem with your analysis, it seems. some section has reached its strain limits, likely. check the local response.
Silvia Mazzoni, PhD
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
-
- Posts: 37
- Joined: Sun Apr 01, 2007 7:35 pm
- Location: China
The above analysis is for the Example07 of OS examples manual. I only change the controlled dispalcement to 0.2*LBuilding.
If the above warnings appear the results are unbelievable?
When some section has reached its strain limits how the OpenSees deal with this case? continue to analyze until more sections reach strain limits, the structure stiffness becomes singular? I think results is still believable, right?
From which waring can I see the strain limits problems?
I still get no file about the Node Recorder and Element Recorder.
Are The Multiple-support excitation analysis results absolute?
If the above warnings appear the results are unbelievable?
When some section has reached its strain limits how the OpenSees deal with this case? continue to analyze until more sections reach strain limits, the structure stiffness becomes singular? I think results is still believable, right?
From which waring can I see the strain limits problems?
I still get no file about the Node Recorder and Element Recorder.
Are The Multiple-support excitation analysis results absolute?
this is a big with opensees that we haven't been able to figure out. when you have very very high demands on a section/fiber, you have problems converging.
remember, even though you only have 20% drift for the entire building, likely you are at 100% drift on some story, which is way too unreasonable. Hence, not a well-designed building or demand.
in MS excitation, yes, the results are absolute since you are imposing displacements at the support.
about the recorders, try changing them to regular recorders, not envelope, and see what you get.
Likely, you are not getting anything because the program failed to converge. see if you get something if you stop the analysis earlier..
remember, even though you only have 20% drift for the entire building, likely you are at 100% drift on some story, which is way too unreasonable. Hence, not a well-designed building or demand.
in MS excitation, yes, the results are absolute since you are imposing displacements at the support.
about the recorders, try changing them to regular recorders, not envelope, and see what you get.
Likely, you are not getting anything because the program failed to converge. see if you get something if you stop the analysis earlier..
Silvia Mazzoni, PhD
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
-
- Posts: 37
- Joined: Sun Apr 01, 2007 7:35 pm
- Location: China
In MS excitaion, when I only use accelerations to impose, the results are believable? For this case how to get the displacements? Integrate? How to deal with the floating? Is it better to impose both accelerations and displacements?
About the recorders, results for node recorder and element recorder are right.
When the program failed to converge the results are still got, and the front result datas for controlled displacement 0.2*LBuilding is the same with displacements 0.1*LBuilding, the post-yield curves for the force-displacement of both cases is up. So I think the results before the converge failing are believable, is that right?
About the recorders, results for node recorder and element recorder are right.
When the program failed to converge the results are still got, and the front result datas for controlled displacement 0.2*LBuilding is the same with displacements 0.1*LBuilding, the post-yield curves for the force-displacement of both cases is up. So I think the results before the converge failing are believable, is that right?
with MS you can only input displacements. that is the way it was formulated.
typically, you should have displacement records as well as acceleration records, otherwise, integrate.
about the recorders, then opensees is not giving you output because of the failure to converge, so it does not get the max/min -- you can just do this in postprocessing.
yes, i think 0.2 is too high.
typically, you should have displacement records as well as acceleration records, otherwise, integrate.
about the recorders, then opensees is not giving you output because of the failure to converge, so it does not get the max/min -- you can just do this in postprocessing.
yes, i think 0.2 is too high.
Silvia Mazzoni, PhD
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
-
- Posts: 37
- Joined: Sun Apr 01, 2007 7:35 pm
- Location: China
-
- Posts: 37
- Joined: Sun Apr 01, 2007 7:35 pm
- Location: China
-
- Posts: 37
- Joined: Sun Apr 01, 2007 7:35 pm
- Location: China
-
- Posts: 37
- Joined: Sun Apr 01, 2007 7:35 pm
- Location: China