Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(316 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*CyberShake calls
+
*Modify CyberShake to work on RSQSim ruptures
*Worked on CAAR proposal, sent edits to Phil
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Found memory issue with DirectSynth, debugging
+
*CyberShake training
*Replaced DirectSynth linear lookup with binary lookup
+
*Update CyberShake study wiki pages to point to SQLite files
 +
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
== Today ==
+
== Project Backlog ==
*Start 1 Hz sim, 2 Hz filter post-processing on BW
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Debug DirectSynth memory issue
+
*Produce candidate site list for Bay Area CyberShake
*Replace binary lookup with hashtable
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Support CAAR proposal effort
+
*Experiment with OMP parallelization for post-processing
*Work on interface between Titan and Blue Waters workflows
 
*Add cleanup to workflows
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*No
 
 
 
== 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