Opened 14 years ago
Last modified 11 years ago
#93 assigned defect
Stochastic Event Set calculations should support IMR/TRT mapping
| Reported by: | Kevin Milner | Owned by: | Kevin Milner |
|---|---|---|---|
| Priority: | major | Milestone: | OpenSHA 1.4 |
| Component: | sha | Version: | |
| Keywords: | HazardCurveLocal | Cc: | Ned Field, Peter Powers |
Description
Currently the multiple IMR GUI gets disabled for stochastic event set calculations in the HazardCurveApp?, but this should be supported. The calculator will have to be updated to take the IMR map, and should use the same logic and calculation parameters as the regular probabilistic calculations.
Change History (8)
comment:1 Changed 14 years ago by
| Owner: | changed from Peter Powers to Kevin Milner |
|---|---|
| Status: | new → assigned |
comment:2 Changed 14 years ago by
comment:3 Changed 14 years ago by
We should do a test to see how much more memory is require for an earthquake rupture to contain the TRT, but I'm not sure we're going to be able to avoid doing this.
comment:4 Changed 14 years ago by
it shouldn't impact memory much...it'd just add an extra 32 bit pointer to each object, same as adding an integer field. So even for a large ERF with 400,000 ruptures, that's ~1.5 MB of memory.
comment:5 Changed 14 years ago by
| Milestone: | OpenSHA 1.1 → OpenSHA 1.2 |
|---|
Let's put this off for OpenSHA 1.2...it requires some decent refactoring, and I think we should rethink our EqkRupture? class a little bit.
comment:7 Changed 13 years ago by
| Milestone: | OpenSHA 1.2 → OpenSHA 1.3 |
|---|---|
| Version: | 1.0.x |
comment:8 Changed 11 years ago by
| Milestone: | OpenSHA 1.3 → OpenSHA 1.4 |
|---|
In order to do this, we'll have to make EqkRupture? objects know their tectonic region type (currently it's just in the source). Is that OK with everyone?