GeoscienceAustralia / eqrm

Automatically exported from code.google.com/p/eqrm
Other
5 stars 4 forks source link

New feature - Add degrading building capacity curve #51

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Currently the building capacity curve is described by two points, the yield 
point and the ultimate point.  After the ultimate point the curve is a straight 
line.

This change will have the curve slope down after the ultimate point, to reflect 
degrading of the building capacity curve.  

Two points will be used to describe this downward slope, the high degrading 
point and the low degrading point.

More details of this description to come. 

Original issue reported on code.google.com by duncan.g...@gmail.com on 13 Jun 2012 at 7:09

GoogleCodeExporter commented 9 years ago
Attaching requirements for the degrading capacity curve. This is also checked 
into the branch capacity_curve_enhancements in Documentation/Risk/Degraded 
Pushover 14 6 2012.ppt

Original comment by b...@girorosso.com on 27 Jun 2012 at 12:09

Attachments:

GoogleCodeExporter commented 9 years ago
This change may require changes to the way that damping is performed. The 
inelastic region that is affected by hysteresis may need to be calculated 
differently as the point used to calculate the area may lie in a degrading 
region.

If the point lies in the degrading region the hysteresis area will be 
calculated as much larger than the acceleration value suggests as it currently 
assumes the original capacity curve. This is highlighted by scenario 
TS_risk62MR where the Harea calculation results in overflows for some 
displacement values.

There are a few options if the point lies in the degrading area

1. Calculate the hysteresis area as it currently does but set the point to (D = 
alpha*Du, A = Au_rev). This assumes that the degrading area is not subject to 
damping.
2. Calculate the hysteresis area by doing 1. above and adding the area 
underneath the degrading part of the curve. The formula for this will need to 
be provided as part of the requirements.
3. Leave as is (see the potential issue above).

Original comment by b...@girorosso.com on 27 Jun 2012 at 4:21

GoogleCodeExporter commented 9 years ago
Assigning to Duncan for further work.

Original comment by b...@girorosso.com on 29 Jun 2012 at 7:09

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Needs more science before implementation.

Original comment by duncan.g...@gmail.com on 20 Mar 2013 at 3:56