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
-**Got confirmation to use GO
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-**Added job to shock to process handoff there - idea from Karan
+*CyberShake training
-*Stampede:
+*Update CyberShake study wiki pages to point to SQLite files
-**Restarted failed WNGC jobs
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-**Fixed bug in job manager killer
-*Talked to David about generating list for monitord DB population
-*CyberShake calls
-== Today ==
+== Project Backlog ==
-*Blue Waters:
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-**Test handoff script
+*Produce candidate site list for Bay Area CyberShake
-*Stampede:
+*Investigate improved load-balancing for DirectSynth SGT handlers
-**Monitor WNGC jobs
+*Experiment with OMP parallelization for post-processing
-**Post-process 3 sets of WNGC SGTs
-*Finish wiki entry for Study 2.2 data products
-*Contact Andrew Hart for overview of OODT
-*Start forward simulations for a San Andreas and mountain events
-== Blocked ==
-*No
-== Follow-ups ==
-*No
-Finish wiki entries for Stampede and Blue Waters validation
-Think about readiness review
-Think about access to CyberShake data
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration