Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(688 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Blue Waters:
+
*Modify CyberShake to work on RSQSim ruptures
**Continued working through workflow creator - integrating with RunManager
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Kraken:
+
*CyberShake training
**Moved seismogram extraction to shock
+
*Update CyberShake study wiki pages to point to SQLite files
*Extracted forward seismograms - after a few false starts, sent results to Rob for review
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Added support for multiple runs with same site in RunManager
 
*Started wiki entries for Blue Waters and Stampede validation
 
*Accepted request to review HPC Summer School applications
 
  
== Today ==
+
== Project Backlog ==
*Blue Waters:
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Add support for data movement when SGT jobs complete
+
*Produce candidate site list for Bay Area CyberShake
**Test RunManager integration and qsub dependencies
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Stampede:
+
*Experiment with OMP parallelization for post-processing
**Follow-up with GRAM group re: hanging Perl script
 
*Kraken:
 
**Post-process 4 sets of WNGC SGTs and test support for multiple runs with same site
 
*Email ISI to ask about gathering metrics from Study 2.2
 
*Complete wiki entries for Blue Waters and Stampede validation
 
*Email Phil forward seismogram overlays
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*No
 
 
 
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