Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(232 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== Yesterday ==
+
== Current Items ==
−
*Tested fix to BW job submission issues, seems to be working
+
*Modify CyberShake to work on RSQSim ruptures
−
*Reply to Nenad
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
−
*Started reviewing proposals for NSF panel
+
*CyberShake training
−
*Created volume for CyberShake UCERF3 test
+
*Update CyberShake study wiki pages to point to SQLite files
−
*CyberShake database discussion
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
−
*CyberShake science review
 
  
−
== Today ==
+
== Project Backlog ==
−
*Resume Study 15.12 using h2ologin4
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
−
*Submit end-to-end test workflow on Titan
+
*Produce candidate site list for Bay Area CyberShake
−
*Start work on model smoothing code
+
*Investigate improved load-balancing for DirectSynth SGT handlers
−
*Continue reviewing proposals for NSF panel
+
*Experiment with OMP parallelization for post-processing
−
*When John props up new DB, test insertion
 
−
 
 
−
== 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