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
-**Monitored production runs
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-**Continued work on parallelized rupture variation generator - decided to change strategies
+*CyberShake training
-*Stampede:
+*Update CyberShake study wiki pages to point to SQLite files
-**Check disk usage for SGTs on /scratch - 20 TB
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-**Emailed David for help with cleanup
-**Got simple offloading code working
-== Today ==
+== Project Backlog ==
-*Blue Waters:
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-**Monitor production runs
+*Produce candidate site list for Bay Area CyberShake
-**Work on revised approach to just read points from rupture geometry file
+*Investigate improved load-balancing for DirectSynth SGT handlers
+*Experiment with OMP parallelization for post-processing
-== Blocked ==
-*Stampede - down for maintenance
-== Follow-ups ==
-*No
-Check on SA forward sim
-Email Stampede staff, let them know about node crashing solution
-Finish wiki entries for Stampede and Blue Waters validation
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration