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 ==
-*Tested buffering code, got better performance:
+*Modify CyberShake to work on RSQSim ruptures
-**read_sgt decreased from 21.1 avg to 15.8;  max from 5322 to 1404
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-**sgt_subset improved but could still be better:  avg from 1327 to 664, max from 6773 to 5443
+*CyberShake training
-**overall down to 5400 SUs/run
+*Update CyberShake study wiki pages to point to SQLite files
-*Corresponded with Maren and David about generating seismogram data products for EEW
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-== Today ==
+== Project Backlog ==
-*Testing 2 simultaneous workflows for SU burn
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Email Lonnie Crosby about Kraken I/O
+*Produce candidate site list for Bay Area CyberShake
-*Investigate changing order of points in SGT
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Work on new PGI seg fault
+*Experiment with OMP parallelization for post-processing
-*ucvm2query
-== Blocked ==
-*No
-== Follow-ups ==
-*No
-*Run test of I/O forwarding on Kraken
-*Continue testing compiler optimizations
-*Run some I/O tests to get reference values
-== Areas of Responsibilities ==
-* CyberShake 1.4
-* Broadband CyberShake
-* Code migration