help!! The example of MVLEM do not run
Moderators: silvia, selimgunay, Moderators
-
- Posts: 2
- Joined: Wed Aug 05, 2015 6:11 pm
- Location: Xi`an University of Architecture and Technology
help!! The example of MVLEM do not run
I down load the example from "http://opensees.berkeley.edu/wiki/index ... _Walls",bu when i run it ,my opensees do not make it.
it occur"WARNING BandgenLinLapackSolver:solve<>-LAPACK routine returned 2"
"WARNING Newtonraphson:solvecurrentstep<>-the LinearSysofEqn failded in solve<>"
"StaticAnaysis:analyze<>-the Algorithm failed at iteration:0 with domain at load factor 0.1"
I just want to get some helps from here.Many thanks.my opensees revision number is 2.4.6<rev6062>
it occur"WARNING BandgenLinLapackSolver:solve<>-LAPACK routine returned 2"
"WARNING Newtonraphson:solvecurrentstep<>-the LinearSysofEqn failded in solve<>"
"StaticAnaysis:analyze<>-the Algorithm failed at iteration:0 with domain at load factor 0.1"
I just want to get some helps from here.Many thanks.my opensees revision number is 2.4.6<rev6062>
Re: help!! The example of MVLEM do not run
yes we know .. the developer is working on it.
-
- Posts: 2
- Joined: Wed Aug 05, 2015 6:11 pm
- Location: Xi`an University of Architecture and Technology
Re: help!! The example of MVLEM do not run
fmk wrote:
> yes we know .. the developer is working on it.
thank you for fmk,I think you will be restored
> yes we know .. the developer is working on it.
thank you for fmk,I think you will be restored
Re: help!! The example of MVLEM do not run
not sure about me! the code maybe.
Re: help!! The example of MVLEM do not run
Hi Frank,
I am also interested in using this element in my modeling and I am getting yet a different message: "ERROR -- element of type MVLEM not known"
It's suggested (by recent forum postings) that the element simply has a problem with running, but this seems more specific than that. There is no indication in the wiki that it needs to be installed, but it's also not in the latest source code (referring to: (root)/trunk/SRC/element/ - Rev 6024)
Can the status of this element be updated? Has it been temporarily removed from the source code?
I will also e-mail the developer at Fullerton, as listed on the Wiki, to see what that status is, but I'm happy with either source for an answer
Cheers,
Mike
EDIT: I downloaded to OpenSees 2.4.6 and ran my file again. It's passed the original error message (so it recognizes MVLEM now), albeit I have a few new error messages to correct on my own, related to the arguments I am passing it. I can solve those on my own I believe.
The developer of the code gave me extraordinarily quick responses, which I highly appreciated. I had never really dug into the source code before, and I still don't quite understand why I don't see MVLEM in the "(root)/trunk/SRC/element/" directory, but I can accept that my OpenSees version is recognizing it now.
Thanks anyways
I am also interested in using this element in my modeling and I am getting yet a different message: "ERROR -- element of type MVLEM not known"
It's suggested (by recent forum postings) that the element simply has a problem with running, but this seems more specific than that. There is no indication in the wiki that it needs to be installed, but it's also not in the latest source code (referring to: (root)/trunk/SRC/element/ - Rev 6024)
Can the status of this element be updated? Has it been temporarily removed from the source code?
I will also e-mail the developer at Fullerton, as listed on the Wiki, to see what that status is, but I'm happy with either source for an answer
Cheers,
Mike
EDIT: I downloaded to OpenSees 2.4.6 and ran my file again. It's passed the original error message (so it recognizes MVLEM now), albeit I have a few new error messages to correct on my own, related to the arguments I am passing it. I can solve those on my own I believe.
The developer of the code gave me extraordinarily quick responses, which I highly appreciated. I had never really dug into the source code before, and I still don't quite understand why I don't see MVLEM in the "(root)/trunk/SRC/element/" directory, but I can accept that my OpenSees version is recognizing it now.
Thanks anyways
Re: help!! The example of MVLEM do not run
are you looking at the code through the browser or have you downloaded it from the svn server .. at the moment te 2 are seperate and the source code browser will not be showing any of the latest changes
Re: help!! The example of MVLEM do not run
Thanks Frank -- I managed to get OpenSees to recognize the MVLEM element, but for the past couple weeks, my issue has been with implementing the element and having the code run. I have troubleshooted to exhaustion, and have brought my system down to 2 nodes, with an MVLEM element between the two nodes, and a simple vertical force applied at the top; the base node is fixed. No matter how simple or complex (I also tried the example from the Wiki), OpenSees is returning a stability error (the wiki example returns "LAPACK routine returned 2", and my simple lollipop example: "UmfpackGenLinSolver::solve(void)- 4 returned in factorization UMD2FA()")
I have varied the Analysis options, varied the material properties to carefully consider numerical problems (I was careful not to use too high or too low a value for the materials), and finally I simply replaced the element with an elasticBeamColumn and that worked --- hence, I am confident the issue lies in the element.
Since my OpenSees file is split into 15 different TCL's, I won't be able to copy-paste into this forum, but I'm glad to send it in case there is any interest to inspect.
I suspect this issue is related to the original poster's problem.
Thanks
I have varied the Analysis options, varied the material properties to carefully consider numerical problems (I was careful not to use too high or too low a value for the materials), and finally I simply replaced the element with an elasticBeamColumn and that worked --- hence, I am confident the issue lies in the element.
Since my OpenSees file is split into 15 different TCL's, I won't be able to copy-paste into this forum, but I'm glad to send it in case there is any interest to inspect.
I suspect this issue is related to the original poster's problem.
Thanks