OpenSees Developer: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
OpenSees Developer pages are intended for application developers of OpenSees. | OpenSees Developer pages are intended for application developers of OpenSees. OpenSees is a software framework for developing sequential and parallel finite element applications applications for structural and geotechnical engineering. | ||
OpenSees | The OpenSees code is open-source and released under a modified GPL. The modification allows users to use the source code for their own use. It does not allow them to sell a product that includes OpenSees code. The interpreters are written in such a way that developers wishing to gain financial advantage could for example: | ||
# Create pre and post processors for the OpenSees interpreters. | # Create pre and post processors for the OpenSees interpreters. | ||
# Create new modules, i.e. elements, materials, solvers, integrators, ... for the OpenSees interpreters. | # Create new modules, i.e. elements, materials, solvers, integrators, ... for the OpenSees interpreters. | ||
The code is made open-source and free to use for a number of reasons: | The code is made open-source and free to use and expand upon for a number of reasons: | ||
* Linus's Law: Given enough eyeballs all bugs are shallow. | |||
*Free software attracts users. | |||
* New ideas can be explored and built upon if they are available to be scrutinized. | |||
* Too much software developed in Civil Engineering research institutions is lost when graduate students leave. | |||
* The software developed in Civil Engineering research requires greater testing. | |||
Revision as of 00:25, 24 October 2009
OpenSees Developer pages are intended for application developers of OpenSees. OpenSees is a software framework for developing sequential and parallel finite element applications applications for structural and geotechnical engineering.
The OpenSees code is open-source and released under a modified GPL. The modification allows users to use the source code for their own use. It does not allow them to sell a product that includes OpenSees code. The interpreters are written in such a way that developers wishing to gain financial advantage could for example:
- Create pre and post processors for the OpenSees interpreters.
- Create new modules, i.e. elements, materials, solvers, integrators, ... for the OpenSees interpreters.
The code is made open-source and free to use and expand upon for a number of reasons:
- Linus's Law: Given enough eyeballs all bugs are shallow.
- Free software attracts users.
- New ideas can be explored and built upon if they are available to be scrutinized.
- Too much software developed in Civil Engineering research institutions is lost when graduate students leave.
- The software developed in Civil Engineering research requires greater testing.
Design the Framework
The initial design of the framework is outlined 'Object-Oriented Finite Element Programming: Frameworks for Analysis, Algorithm and Parallel Computing (1997), F.McKenna' [1]. Some of the interfaces in the dissertation have been modified over time.