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 ==
-*Tried to run AWP-ODC-SGT post-processing workflow on Ranger, found weird Condor errors
+*Modify CyberShake to work on RSQSim ruptures
-*Ran AWP-ODC-SGT post-processing, much higher hazard curves
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Compare profile run results, don't match - error somewhere
+*CyberShake training
-*Ran AWP-ODC-SGT on Kraken with Shiyu's executable, got different results
+*Update CyberShake study wiki pages to point to SQLite files
-*Tried running AWP-ODC-SGT with user scottcal, got 3rd executable and 3rd set of results
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-*Asked Patrick to try, got 4th executable
-== Today ==
+== Project Backlog ==
-*Try running individual seismogram synthesis for values with big differences
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Debug weird Condor errors between shock and Ranger
+*Produce candidate site list for Bay Area CyberShake
-*Try multiple tests with AWP-ODC-SGT on Kraken to see if we can get any agreement
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Look for obvious errors in profile run
+*Experiment with OMP parallelization for post-processing
-== Blocked ==
-*No
-== Follow-ups ==
-*No
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration