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 ==
-*Finish AWP PP run to get comparison hazard curves, emailed out
+*Modify CyberShake to work on RSQSim ruptures
-*Updated Pegasus to get exitcode fix
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Tested script to update DB entries and RLS
+*CyberShake training
-*Tested auto-submit of sites
+*Update CyberShake study wiki pages to point to SQLite files
-*Caught and fixed requested memory bug in refactored code
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-*CyberShake calls
-*Outlined fields needed in seismogram header
-== Today ==
+== Project Backlog ==
-*Respond to Efecan's question about CyberShake workflow jobs
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Monitor execution of s022 to verify memory bug fix
+*Produce candidate site list for Bay Area CyberShake
-*Run hazard curves for additional verification sites
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Travel arrangements for SC12
+*Experiment with OMP parallelization for post-processing
-== Blocked ==
-*No
-== Follow-ups ==
-*Phil - next steps for production run?
-*Run test of I/O forwarding on Kraken
-*Continue testing compiler optimizations
-*Run some I/O tests to get reference values
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration