Please reply to this post with a list of what you, as an OpenSees DEVELOPER, require of OpenSees.
The OpenSees Development Team
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
In my opinion the most required feature is to have a pre-processor and a post-processor. In order to integrate the OPS framework with geometric packages in an easier way, I think that some features are needed:
Possibility of obtaining Rigid body shapes in eigen analysis. Now it is quite difficult to check models with joints (zerolengths elements) when they are created with manual routines and checking these shapes would be helpfull to see which elements are not connected.
Add some additional examples for developers as the example1 of the EXAMPLES folder. Perhaps the typical TCL examples could be translated. I think they are very usefull for non C++ skilled users.
Add some solutions and projects. I would suggest solutions for Windows 64 and a project similar to quickmain in order to create a DLL that could be called from the pre-processor.
I think that these features would help to new users to understand the source code of OPS.
I think that would be useful to stop an analysis of a fiber model, save the state of the model (stress,..), change the fiber sections to simulate the rupture of some elements, redistribute the stresses in the structural model (given the new sections) and continue the analysis on the structure.
1. OpenSees on Ruby.
2. A configure executable to compile the source code easily.
3. Implementation of inclined supports.
The last one might be solved if an orientation option is added to the equalDOF command in the same way as was done with zero-length elements.
Why not consider CMake or EclipseIDE as a building utility for OpenSees to save us all the pain of building OpenSees on different platform .... Both can provide cross platform builds .... I think CMake is a better choice. Gmsh is an example of an application built by CMake ..... it is soooooo mobile.
I have been suffering for 2 weeks now to build OpenSees on Ubuntu 10.10 ..... so frustrated!
There are many posts mentioned how to spit mass,stiffness and damping Matrix out. At present neither mass or modal participation factors can not be recorded with OpenSees. Although We can go to the source code, find it and spit it out, it is very difficult for us.
Would you please do something about this. So that we can record mass,stiffness and damping Matrix buy Tcl scripts.
Thanks a lot!
I think this is right time to switch over from the Makefile.def system to something like automake and cmake. The painful make process for the usershould be converted to packaging everything (libs, binaries) in an archive. The same is done by Scilab (http://www.scilab.org) which also includes the thirdparty softwares like jvm.
The user can simply extract the archve in a directory of his /her choice and start using. This will ease the portability for different OSs (Win, Linux, Mac).
I hope OpenSees theam will look into the matter seriously.
Can you help me with this ?? I really want this program to work ..
But, please, clean spam from this forum, it's unreadable.
It would be very useful to be able to define boundary conditions not along the global coordinate system. The ability to define fixity for along an incline or at an angle to the GCS would be very beneficial.
based on my experiences with opensees in my few projects, i think it would be a good idea to include a capabality for coupling of methods/equations/domains. I mean in case a solution is made for a domain using e.g. boundary element the effects of which is going to be made on another adjacent domain in opensees, there are some methods, but there could be one especially developed for this coupling purpose which lets the user choose what method he/she wishes to apply for the other domain; i.e. other methods beside FEM could be included for coupled/parallel platform programming.
I hope I am clear enough.
Thanks for all your efforts,
Shiraz University of Technology