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 ==
-*Calculated rupture-site distance, added new DB column
+*Modify CyberShake to work on RSQSim ruptures
-*Continued work on pegasus-statistics issues, got updated versions from ISI
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Error with PMC run, 10x480 w/hierarchy test; updated pegasus on Kraken
+*CyberShake training
-*Continued work on debugging weird AWP results, isolating problem change
+*Update CyberShake study wiki pages to point to SQLite files
-*Emailed Rob to check on correct version of emod3d-mpi for runs
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-== Today ==
+== Project Backlog ==
-*Populate DB with rupture-site info
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Retry PMC run, 10x480 w/hierarchy
+*Produce candidate site list for Bay Area CyberShake
-*Update Pegasus, try monitord again - Pegasus group would like results before 4.1 release
+*Investigate improved load-balancing for DirectSynth SGT handlers
+*Experiment with OMP parallelization for post-processing
-== Blocked ==
-*Hypocenter login issues, so can't post new results for Maren - ping John again
-== Follow-ups ==
-*CyberShake calls
-*Runs for Rob and Kim
-*Continue testing compiler optimizations
-*Run some I/O tests to get reference values
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration