Difference between revisions of "Staff Priorities - Scott"

Latest revision as of 17:56, 1 February 2018

Modify CyberShake to work on RSQSim ruptures
- Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
CyberShake training
Update CyberShake study wiki pages to point to SQLite files
Create wiki page for CyberShake RSQSim, and upload sample seismograms

@@ Line 1: / Line 1: @@
-== Yesterday ==
+== Current Items ==
-*Blue Waters:
+*Modify CyberShake to work on RSQSim ruptures
-**Finished SGT production runs!
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-**Ran test with seis_psa - looks like execution is taking 2/3 of runtime
+*CyberShake training
-*Refactored curve sensitivity code to run much faster (fewer DB hits)
+*Update CyberShake study wiki pages to point to SQLite files
-*Broadband production walkthrough with Fabio
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-*Continued scec-02 -> scec-04 data copy
-== Today ==
+== Project Backlog ==
-*Blue Waters:
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-**Get profiling info for seis_psa
+*Produce candidate site list for Bay Area CyberShake
-**Get stats for SGT production runs
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Stampede:
+*Experiment with OMP parallelization for post-processing
-**Work on offloading
-*Run curve sensitivity, get values for a single site, create ranking
-*Redo curve diff calculation since more have completed
-*Continue scec-02 -> scec-04 data copy
-*Monitor monitord population
-== Blocked ==
-*No
-== Follow-ups ==
-*Call with David
-Finish wiki entries for Stampede and Blue Waters validation
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration