Custom Query (454 matches)

Review the apps here:

• Site Data App (for viewing values for a single location): trunk/src/org/opensha/commons/data/siteData/gui/SiteDataApplet.java

• Site Data Map App (for creating maps of site data, including mosaics of multiple providers): trunk/src/org/opensha/commons/data/siteData/gui/SiteDataMapApplet.java

Then add them to the web site as regular apps.

Clarify how the tectonic region parameter is being used in the Hazard Curve Apps. For example, what happens when the user selects a value for the TRT param...does it get overridden by the calculator? Where does this get set?

We might want to hide this parameter from the user, depending on if it's actually used.

E-Mail from Ned, 9/1/2010:

The "Faults for Simulators" option in SCEC-VDO now uses the utility class:

org.opensha.sha.simulators.eqsim_v04.General_EQSIM_Tools

to get an ArrayList<RectangularElement> from the method getElementsList().

That utility classe (General_EQSIM_Tools) also has a method for getting events (getEventsList(), which returns ArrayList<EQSIM_Event>). Each EQSIM_Event object has the following methods for getting the element IDs and amounts of slip in the event:

ArrayList<Integer> getAllElementIDs() ArrayList<Integer> getAllElementSlips()

What I'd like SCEC VDO to be able to do is plot the slip in any one of the events.

For example, the faults could all be gray, and then the element for a given event could be plotted in color that's proportional to the amount of slip.

The user could either choose a specific ith event, or it could loop over them one by one (either by even temporal increments, or proportional to the actual time delay between events; the event time for each event is given by EQSIM_Event.getTimeInYears()). In fact, it would be cool to have some kind of slider bar so you could scroll through events.

Lets try to talk about this today also.

Thanks,

Ned

PS One thing to watch out for is that the ID in the various element and event objects is one plus the index in the arrays that hold those objects (the simulator group adopted the convention that their indices start from 1, not zero; I refer to their indices as "IDs" to avoid confusion). Again, I can explain more if this is not clear.