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
-**Continued working through workflow creator, added new capabilities
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Kraken:
+*CyberShake training
-**Forward simulation completed, started extracting seismograms, rotation issue, emailed with Rob
+*Update CyberShake study wiki pages to point to SQLite files
-*Finished putting Blue Waters information on internal wiki, emailed group
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-*Responded to Gideon with information to run CyberShake TEST case
-== Today ==
+== Project Backlog ==
-*Blue Waters:
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-**Continue working through workflow creator
+*Produce candidate site list for Bay Area CyberShake
-*Stampede:
+*Investigate improved load-balancing for DirectSynth SGT handlers
-**Support GRAM staff investigation of Perl script hanging
+*Experiment with OMP parallelization for post-processing
-*Kraken:
-**Add rotation to seismogram extraction, continue with comparison
-*Email ISI to ask about gathering metrics from Study 2.2
-*Email CyberShake list to announce Study 2.2 completion
-*Wiki entries for Blue Waters and Stampede validation
-== Blocked ==
-*No
-== Follow-ups ==
-*No
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration