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 on coscheduling - restructured input file creation, ran out of file descriptors
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-**Tried to create 1 Hz mesh for AWP-SGT CPU - issues, asked David for help
+*CyberShake training
-*Replied to Xin, Rob explained
+*Update CyberShake study wiki pages to point to SQLite files
-*Talked with Karan re: monitord population issues, killed aftershock
+*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
-**Retry coscheduling when fewer SGT jobs are running
+*Produce candidate site list for Bay Area CyberShake
-**Profile Rupgen-api with eye to parallelism
+*Investigate improved load-balancing for DirectSynth SGT handlers
-**Continue with 1 Hz run
+*Experiment with OMP parallelization for post-processing
-*Stampede GRAM seems down, file ticket
-*Retry monitord population
-== Blocked ==
-*No
-== Follow-ups ==
-*CyberShake calls
-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