Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(530 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Summer School call
+
*Modify CyberShake to work on RSQSim ruptures
*High F call
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*CyberShake calls
+
*CyberShake training
*Glanced at SCEC section to Pegasus paper
+
*Update CyberShake study wiki pages to point to SQLite files
*Started looking over readiness review items
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Took stab at formal definition of time-to-solution
 
*Heard from NCSA that 5x PP test run did not trigger events
 
*Modified logic for determining number PX and PY for GPU SGTs
 
*Queued test of GPU SGT fix
 
  
== Today ==
+
== Project Backlog ==
*Monitor test of GPU SGT fix
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Test runtimes of GPU code with default mesh and mesh modified to give each processor a cube
+
*Produce candidate site list for Bay Area CyberShake
*Try 7x PP test on BW
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Integrate code to check AWP SGTs for NaNs
+
*Experiment with OMP parallelization for post-processing
*Work on 1D, CVM-H no GTL curves
 
*Continue preparing readiness review
 
*Work on Pegasus paper
 
*Check on completeness of 4 sites x 4 config hazard curves for readiness review
 
*Start wiki entry for CyberShake Study 14.2
 
 
 
== 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