Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(524 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Refactored and tested vmesh gen code
+
*Modify CyberShake to work on RSQSim ruptures
*Compared runtimes of GPU code with different size meshes - slower, more efficient on multiple-of-200 mesh
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Queued CVM-H no GTL with 4 sites
+
*CyberShake training
*Tried installing UCVM w/BBP 1D, tests failed
+
*Update CyberShake study wiki pages to point to SQLite files
*Tested performance of more CPUs for AWP - 50x50x50 is faster and more efficient
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Updated algorithm for synth runtimes
 
*Changed bookkeeping so that UCVM 1D model is tracked as "SCEC 1D", not HK
 
*Added BBP 1D to workflow and scripts
 
  
== Today ==
+
== Project Backlog ==
*Try 7x PP test on BW
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Check on curves with CVM-H, no GTL
+
*Produce candidate site list for Bay Area CyberShake
*Queue hazard curves with GPU, CPU code and CVM-S4.26
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Continue preparing readiness review
+
*Experiment with OMP parallelization for post-processing
*Generate BBP 1D curves
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*Summer School call
 
*High F call
 
*CyberShake calls
 
 
 
== 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