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 ==
-*Extracted v3 vs v3.0.3 seismograms at 218/267/11 rupture, sent to Rob
+*Modify CyberShake to work on RSQSim ruptures
-*Responded to Manuela (post-doc with Norm) about right Run IDs to use with CyberShake data
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Compared v3.0.3 TEST runs from HPC and Kraken, good match
+*CyberShake training
-*Continued tracking down SGTs for production run
+*Update CyberShake study wiki pages to point to SQLite files
-*Finished USC hazard curves with AWP
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-== Today ==
+== Project Backlog ==
-*Check UCVM AWP results - start with projection
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Finish finding SGTs for production run
+*Produce candidate site list for Bay Area CyberShake
-*RWG USC curves almost done, do comparison when complete
+*Investigate improved load-balancing for DirectSynth SGT handlers
+*Experiment with OMP parallelization for post-processing
-== Blocked ==
-*No
-== Follow-ups ==
-*No
-*Run test of I/O forwarding on Kraken
-*Email CyberShake papers to Liwen
-*Continue testing compiler optimizations
-*Run some I/O tests to get reference values
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration