Opened 14 years ago

Last modified 13 years ago

#78 closed defect

Add ability to compute Dip Direction — at Version 2

Reported by: Kevin Milner Owned by: Kevin Milner
Priority: minor Milestone:
Component: fault DB Version:
Keywords: Cc: Ned Field

Description (last modified by Kevin Milner)

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 (2)

comment:1 Changed 14 years ago by Kevin Milner

Description: modified (diff)

comment:2 Changed 14 years ago by Kevin Milner

Cc: Ned Field added
Description: modified (diff)
Status: new → assigned
Summary: rename "Dip LocationVector", add info text → Add ability to compute Dip Direction

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:

firstLoc = faultTrace.get(0);

lastLoc = faultTrace.get(faultTrace.getNumLocations() - 1);;
LocationVector? aveDir = LocationUtils?.vector(firstLoc, lastLoc);
aveDipDirection = ( aveDir.getAzimuth() + 90 );

in both StirlingGriddedSurface? & SimpleListricGriddedSurface?.

We should document this implementation carefully.

Cheers,

Ned

Note: See TracTickets for help on using tickets.