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 ==
-*AWP SGT jobs at USC finished
+*Modify CyberShake to work on RSQSim ruptures
-*Ran verification test with RWG v3.0.3, seeing ~10% differences
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Emailed Rob with test results and analysis of differences, Rob says expected
+*CyberShake training
-*Submitted TEST SGTs on hpc to verify that v3.0.3 results on Kraken are good
+*Update CyberShake study wiki pages to point to SQLite files
-*Submitted USC SGTs on kraken to get hazard curve
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-*Worked on direct calculation of UCVM in AWP format
-== Today ==
+== Project Backlog ==
-*Run PP with AWP SGTs at USC
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Monitor RWG TEST and USC SGT runs
+*Produce candidate site list for Bay Area CyberShake
-*Run tests of UCVM in AWP format
+*Investigate improved load-balancing for DirectSynth SGT handlers
+*Experiment with OMP parallelization for post-processing
-== Blocked ==
-*No
-== Follow-ups ==
-*Phil regarding CyberShake
-*CyberShake call
-*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