Staff Priorities - Scott: Difference between revisions

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
-**Looks like occasional I/O ops are very slow in seis_psa
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Ran curve sensitivity code
+*CyberShake training
-*Continued scec-02 -> scec-04 data copy
+*Update CyberShake study wiki pages to point to SQLite files
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-== Today ==
+== Project Backlog ==
-*Blue Waters:
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-**Get metrics from production SGTs
+*Produce candidate site list for Bay Area CyberShake
-*Stampede:
+*Investigate improved load-balancing for DirectSynth SGT handlers
-**Submit failed PP runs
+*Experiment with OMP parallelization for post-processing
-*Check in on Broadband runs on epicenter
-*Continue scec-02 -> scec-04 data copy
-*Analyze curve sensitivity results
-== Blocked ==
-*No
-== Follow-ups ==
-*Blue Waters call at 1
-Finish wiki entries for Stampede and Blue Waters validation
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration