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 medium scale velocity test - looks good
+*Modify CyberShake to work on RSQSim ruptures
-*Switched to using regex RLS to start workflow testing on Blue Waters
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Monitored Rupture Variation inserts
+*CyberShake training
-*Heard from Yaakoub regarding tera3d access on Stampede
+*Update CyberShake study wiki pages to point to SQLite files
-*Modified PreSGT for 1 Hz
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-*Modified RWG SGT generator for 1 Hz
-== Today ==
+== Project Backlog ==
-*Try AWP format velocity test
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*John upgraded jars, retry - however, I think we may need to update openssl when he gets back
+*Produce candidate site list for Bay Area CyberShake
-*Continue workflow testing on BW
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Run pegasus-statistics when upgraded
+*Experiment with OMP parallelization for post-processing
-*Look over Maren's CyberShake paper
-*Continue monitoring RV inserts
-*Monitor and resubmit Stampede scratch deletes
-*Test RWG SGT generator at 1 Hz
-*Ask CyberShake group about velocity cutoffs
-== Blocked ==
-*No
-== Follow-ups ==
-*No
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration