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 ==
-*Summer School call
+*Modify CyberShake to work on RSQSim ruptures
-*CyberShake calls
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Started migrating Titan codes to geo112
+*CyberShake training
-*Looked at Shashank's AWP-ODC-SGT GPU issues, think it's related to bad inputs
+*Update CyberShake study wiki pages to point to SQLite files
-*Monitored BW run, but OOM errors; scaled back from 10 rupture variations per batch to 5, tried again
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-*Queued SMCA 1Hz SGTs on Titan
-*Added option to skip md5sum step
-*Continue work on DirectSynth (~98%)
-== Today ==
+== Project Backlog ==
-*Configure better SGT inputs, test, send to Shashank
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Monitor BW run
+*Produce candidate site list for Bay Area CyberShake
-*Monitor Titan SGTs
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Continue work on DirectSynth
+*Experiment with OMP parallelization for post-processing
-*Respond to Glenn
-*Continue migrating Titan codes to geo112
-== Blocked ==
-*No
-== Follow-ups ==
-*No
-== Areas of Responsibilities ==
-* CyberShake
-* Broadband CyberShake
-* Code migration