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 ==
-*Checked on Rupture Variation inserts for ERF 36 - continuing, slowly
+*Modify CyberShake to work on RSQSim ruptures
-*Tried to run pegasus-statistics on Study 2.2 results, asked John to upgrade Python on aftershock
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Tested 1 Hz CyberShake velocity modifications - small test passed
+*CyberShake training
-*Added job id update job to Integrated workflow and test
+*Update CyberShake study wiki pages to point to SQLite files
-*Tried to test of integrated workflow on Blue Waters with scottcal proxy - asked John to upgrade to unlimited strength jars
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-== Today ==
+== Project Backlog ==
-*Try medium and large CyberShake velocity tests
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Test proxy when jars are upgraded
+*Produce candidate site list for Bay Area CyberShake
-*Run pegasus-statistics when upgraded
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Look over Maren's CyberShake paper
+*Experiment with OMP parallelization for post-processing
-*Monitor Rupture Variation inserts
-*Continue with 1 Hz modifications to SGT workflow
-== Blocked ==
-*No
-== Follow-ups ==
-*CyberShake calls
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration