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 ==
-*Fixed error condition in workflow status
+*Modify CyberShake to work on RSQSim ruptures
-*Modified GPU meshes to be nz=200
+**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
-*Submitted GPU job for USC to test fix
+*CyberShake training
-*Technical readiness review
+*Update CyberShake study wiki pages to point to SQLite files
+*Create wiki page for CyberShake RSQSim, and upload sample seismograms
-== Today ==
+== Project Backlog ==
-*Look over TTS letter
+*Run CyberShake post-processing on RSQSim events, once DB is populated
-*Add ability to determine nodetype to Blue Waters cron job
+*Produce candidate site list for Bay Area CyberShake
-*If USC GPU curve looks good, queue other 7
+*Investigate improved load-balancing for DirectSynth SGT handlers
-*Tag code in SVN
+*Experiment with OMP parallelization for post-processing
-*Post versions on study page
-*Add ability to track runs as part of a study to run manager on northridge.usc.edu
-*Test data transfer speeds Blue Waters -> HPCC
-== Blocked ==
-*No
-== Follow-ups ==
-*High-F call
-*Blue Waters call
-== Areas of Responsibilities ==
-* CyberShake
-* Broadband CyberShake
-* Code migration