#78 closed defect (fixed)
Add ability to compute Dip Direction
Reported by: | Kevin Milner | Owned by: | Kevin Milner |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | fault DB | Version: | |
Keywords: | Cc: | Ned Field |
Description (last modified by )
Should be "Dip Direction" (done). Is it computed? How does that work? Should the user be able to override it? If the user edits the parameter, will it be recomputed at midnight? Maybe add button to recompute it.
Change History (5)
comment:1 Changed 13 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 13 years ago by
Cc: | Ned Field added |
---|---|
Description: | modified (diff) |
Status: | new → assigned |
Summary: | rename "Dip LocationVector", add info text → Add ability to compute Dip Direction |
comment:3 Changed 13 years ago by
The database manager should definitely be able to override the dip direction (if they have better knowledge). In fact, the database should be clear about whether dip direction was calculated or entered by hand.
If the value is not entered by hand, then I'm not event sure the database should contain any value (as opposed to computing a derived value when asked for)
comment:4 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Finished updates (and updated application). Here are the changes:
- renamed Dip LocationVector? to Dip Direction
- set all dip direction values to null in the database
- did a check for consistency with calculated values before deletion. All values but 2 matched, and those 2 were outdated values that never got updated.
- created getDipDirection() in FaultTrace?.
- This value simply returns getStrikeDirection() + 90.
- updated other classes that were calculating it manually to use this new method
like before, if the DB has a value then it will be used. if there is no value, it will be computed on the fly. this computation is still done in StirlingGriddedSurface? and SimpleListricGriddedSurface? (both call FaultTrace?.getDipDirection()), and not in the DB classes.
Method for computing it (e-mail from Ned, 11/30/10):
Kevin,
The Aki Richards convention is described at:
http://www.opensha.org/glossary-strikeDipRake
All data in the database should already conform to this.
As for implementation, I see aveDipDir computed as:
in both StirlingGriddedSurface? & SimpleListricGriddedSurface?.
We should document this implementation carefully.
Cheers,
Ned