Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(681 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Blue Waters:
+
*Modify CyberShake to work on RSQSim ruptures
**Monitored run, bugs in the AWP job specification, fixed
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Stampede:
+
*CyberShake training
**Found issue with the JM killer
+
*Update CyberShake study wiki pages to point to SQLite files
 +
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
== Today ==
+
== Project Backlog ==
*Blue Waters
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Test data movement
+
*Produce candidate site list for Bay Area CyberShake
**Sort out some issues with the Run Manager changing job status to Error prematurely
+
*Investigate improved load-balancing for DirectSynth SGT handlers
**Set up SSH keys to add jobs to pending.txt on shock when SGT run finishes
+
*Experiment with OMP parallelization for post-processing
*Stampede
 
**Post-process 3 sets of WNGC SGTs
 
*Start monitord DB population
 
*Create wiki entry for Study 2.2 data products (with links to maps, curves, Feng's analysis, seismograms)
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*No
 
 
 
Finish wiki entries for Stampede and Blue Waters validation
 
Think about readiness review
 
Think about access to CyberShake data
 
 
 
== 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