Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(916 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Created velocity plots along N-I fault surface
+
*Modify CyberShake to work on RSQSim ruptures
*Make slides for EarthCube presentation tomorrow
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Extract seismograms from forward run at site location
+
*CyberShake training
*Compared RWG and AWP results from TEST with CVM-H - found Q issue, reran CVM-H job
+
*Update CyberShake study wiki pages to point to SQLite files
*Tested built find and zip, modified and changed workflow tools
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Submitted new TAU run on Kraken
 
  
== Today ==
+
== Project Backlog ==
*Email out velocity plots along N-I surface for CVM-H/CVM-S
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Add CyberShake section to pegasus-mpi-cluster XSEDE paper
+
*Produce candidate site list for Bay Area CyberShake
*Repeat RWG/AWP comparison with CVM-H
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Rerun AWP with CVM-S TEST site with modified Q
+
*Experiment with OMP parallelization for post-processing
*Look at plots from AWP forward run
 
*Add default striping change on Kraken dirs to workflow
 
*Check on new TAU run on Kraken
 
*Monitor workflow run
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*No
 
 
 
== 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