Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(440 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*USC 200m run had issues with I/O; emailed Efecan for help
+
*Modify CyberShake to work on RSQSim ruptures
*Sent Efecan 1 Hz input files for testing
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Skyped with Ali the intern
+
*CyberShake training
*Queued post SGT job on Titan
+
*Update CyberShake study wiki pages to point to SQLite files
 +
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
== Today ==
+
== Project Backlog ==
*Email Ali some sample pseudocode
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*When post-SGT is finished, transfer Titan SGTs to Blue Waters and run post-processing
+
*Produce candidate site list for Bay Area CyberShake
*If Efecan replies, make appropriate changes
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Run BW tests of uniform/random hypo distributions on 1000m surfaces in meantime
+
*Experiment with OMP parallelization for post-processing
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*Call with Matt of ORNL
 
 
 
== Areas of Responsibilities ==
 
* CyberShake
 
* Broadband CyberShake
 
* Code migration
 

Latest revision as of 17:56, 1 February 2018

Current Items

  • 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

Project Backlog

  • Run CyberShake post-processing on RSQSim events, once DB is populated
  • Produce candidate site list for Bay Area CyberShake
  • Investigate improved load-balancing for DirectSynth SGT handlers
  • Experiment with OMP parallelization for post-processing