Reliability Sensitivity and Optimization Modules: Difference between revisions

From OpenSeesWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 7: Line 7:


==== What are the short term goals ====
==== What are the short term goals ====
Immediate (end of summer 2010!) achievable goals that can be deliverd that are useful to PEER, NEES!, and industry users.


==== What are the long term goals ====
==== What are the long term goals ====


=== What are the Boundaries ===
=== What are the Limits ===
 
# Some elements and materials some of this just will not work for. need to be documented.


=== What is the Product ===
=== What is the Product ===

Latest revision as of 21:28, 5 March 2010


Roadmap

What is the Vision

What are the short term goals

Immediate (end of summer 2010!) achievable goals that can be deliverd that are useful to PEER, NEES!, and industry users.

What are the long term goals

What are the Limits

  1. Some elements and materials some of this just will not work for. need to be documented.

What is the Product

  1. Seperate Module with clear interface to any FE code!
  2. Working Interface to OpenSees


Documentation

Explanation/THEORY (Armen & Terje)

have a look:

Optimization

Portal on IT

Earthquake Engineering

Probabilistic Assessment of Structures!

how to explain what these modules will do to a structural engineer.

What does reliability, sensitivity and optimization mean in context of structural engineering

What is the process

List of References

Command Manual for use with OpenSees (Mike, Kevin, Quan, Michele)

Examples

References:

If you use this work, we would appreciate it if you would reference the papers below:

Haukaas, T., Der Kiureghian, A. “Methods and object-oriented software for FE reliability and sensitivity analysis with application to a bridge structure.” ASCE Journal of Computing in Civil Engineering, 21(3), pp. 151-163, 2007.


Design

Based on Terje's original work, Kevin & Michaels changes.

One new change all agree on is use of a new FunctionEvaluator class and introduction of some other class to store results in.

<uml> abstract class FunctionEvaluator FunctionEvaluator <|-- TclFunctionEvaluator FunctionEvaluator : double eval(const char * =0) </uml>

Class Diagrams for Reliability