Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(179 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Monitor Study 15.12 - fixed issues, continuing to make progress
+
*Modify CyberShake to work on RSQSim ruptures
*Kevin produced 1km spaced source description
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Ran single-source AWP GPU sim
+
*CyberShake training
*Submitted AWP CPU sim with entire source
+
*Update CyberShake study wiki pages to point to SQLite files
*CyberShake call
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
== Today ==
+
== Project Backlog ==
*CyberShake run manager down, emailed John
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Check read-only DB account; if works OK, send info out to Nenad
+
*Produce candidate site list for Bay Area CyberShake
*Create SRF from 1 km source description
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Try creating visualization from single-point run
+
*Experiment with OMP parallelization for post-processing
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*High F call at 11
 
 
 
== 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