Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(635 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Blue Waters:
+
*Modify CyberShake to work on RSQSim ruptures
**Continued monitoring production runs
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
**Ran tests with Efecan's suggested striping - faster for extraction, not for seis
+
*CyberShake training
**Submitted test with memcached back on
+
*Update CyberShake study wiki pages to point to SQLite files
*Automated movement of scec-02 files to scec-04
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Modified curve calculation to ignore certain ruptures
 
  
== Today ==
+
== Project Backlog ==
*Blue Waters:
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Continue monitoring production runs
+
*Produce candidate site list for Bay Area CyberShake
**Look at seis_psa results with memcached - if still slow, add timings
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Monitor data movement from scec-02 to scec-04
+
*Experiment with OMP parallelization for post-processing
*Monitor monitord DB insertion
 
*Northridge down
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*CyberShake calls
 
 
 
 
 
Finish wiki entries for Stampede and Blue Waters validation
 
 
 
== Areas of Responsibilities ==
 
* CyberShake 1.4
 
* 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