I can't compile the project Opensees. Code downloaded from Github 1st may 2019.
I'm using MS Visual Studio 2019, Intel Paralell Studio 2019 and ActiveTcl 8.6.9.
I've included the tcl folder with all projects (correctly, i hope).
The tcl project is returning error in line 1521 from src\tcl\command.cpp: "return isn't part of the tcl_interp".
Leonardo
Search found 5 matches
- Sun May 05, 2019 9:32 am
- Forum: Framework
- Topic: Hints for compiling OS on Windows
- Replies: 1
- Views: 9928
- Wed Mar 27, 2019 3:43 am
- Forum: OpenSees.exe Users
- Topic: Error of 'ForceBeamColumn' element
- Replies: 3
- Views: 3599
Re: Error of 'ForceBeamColumn' element
Then the problem could be a lot of things.
I would make make small models with each component isolated and test them.
If in your case the only problem is the line element, you could test it in a Moment-Curvature procedure and/or cantilever pushover simple model, just to see what you get.
I would make make small models with each component isolated and test them.
If in your case the only problem is the line element, you could test it in a Moment-Curvature procedure and/or cantilever pushover simple model, just to see what you get.
- Sat Mar 23, 2019 5:13 am
- Forum: OpenSees.exe Users
- Topic: Error of 'ForceBeamColumn' element
- Replies: 3
- Views: 3599
Re: Error of 'ForceBeamColumn' element
Hello,
The ForceBeamColumn is harder to obtain convergence in general. That happens because the analysis must correct the elements response at every step to assure compatibility. And if it fails to do so within the tolerance, then an error is returned.
You may:
a) Add more iterations and a more allowable tolerance, with these tags added at the end of the ForceBeamColumn: " -iter $MaxIters $Tolerance".
b) Change your elements to the DispBeamColumn, and improve your mesh where the nonlinearity is expected. If you mesh is refined enough, it will return you accurate results.
The ForceBeamColumn is harder to obtain convergence in general. That happens because the analysis must correct the elements response at every step to assure compatibility. And if it fails to do so within the tolerance, then an error is returned.
You may:
a) Add more iterations and a more allowable tolerance, with these tags added at the end of the ForceBeamColumn: " -iter $MaxIters $Tolerance".
b) Change your elements to the DispBeamColumn, and improve your mesh where the nonlinearity is expected. If you mesh is refined enough, it will return you accurate results.
- Fri Nov 02, 2018 6:26 am
- Forum: OpenSees.exe Users
- Topic: bug in LayeredShell
- Replies: 13
- Views: 12823
Re: bug in LayeredShell
fmk wrote:
> try this .. debug messages should be gone:
> http://opensees.berkeley.edu/OpenSees/c ... 64.exe.zip
Hello
I had the same problem, i.e., using layeredshell would flood the prompt, and using said link completely solved it.
Thank you very much.
Leonardo
> try this .. debug messages should be gone:
> http://opensees.berkeley.edu/OpenSees/c ... 64.exe.zip
Hello
I had the same problem, i.e., using layeredshell would flood the prompt, and using said link completely solved it.
Thank you very much.
Leonardo
- Fri Oct 05, 2018 5:17 am
- Forum: OpenSees.exe Users
- Topic: Help! the Opensees.exe has stopped working
- Replies: 2
- Views: 4424
Re: Help! the Opensees.exe has stopped working
Hello
I experienced a similar problem. Opensees suddenly closes when I run Example MVLEM1.
But if I run the same file under another version of Opensees, it works.
I suggest you download http://opensees.berkeley.edu/wiki/image ... _MVLEM.zip
The compacted files contains version 2.4.4 and it ran perfectly examples 1 and 2 of MVLEM.
Hope it helps
I experienced a similar problem. Opensees suddenly closes when I run Example MVLEM1.
But if I run the same file under another version of Opensees, it works.
I suggest you download http://opensees.berkeley.edu/wiki/image ... _MVLEM.zip
The compacted files contains version 2.4.4 and it ran perfectly examples 1 and 2 of MVLEM.
Hope it helps