Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(704 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Blue Waters:
+
*Modify CyberShake to work on RSQSim ruptures
**Tested workflow-generating scripts
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
**Tried out performance monitoring tools, useful
+
*CyberShake training
*Stampede:
+
*Update CyberShake study wiki pages to point to SQLite files
**Continued testing PP configurations
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Kraken:
 
**Investigated OOM failures with new workflows -- just needed MPI_Finalize(), return 0
 
**Error on PP with Blue Waters AWP WNGC SGTs; investigated, found bug in
 
*Updated Pegasus to get new output-dir
 
*Emailed cybershake list to notify about CS Study 2.3 site list
 
*Blue Waters workshop at NCSA
 
  
== Today ==
+
== Project Backlog ==
*Blue Waters:
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Modify workflow-generating scripts to generate all 4 SGT sets at once
+
*Produce candidate site list for Bay Area CyberShake
**Wait on post-processing results from WNGC
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Stampede
+
*Experiment with OMP parallelization for post-processing
**Set up with AWP
 
**Test with fewer #s of DAXes
 
*Kraken
 
**Run forward simulation
 
**Run post-processing for BW AWP WNGC SGTs
 
*Add AWP helper scripts to DAX generator
 
*Draft request for GRAM remote job submission to Blue Waters
 
*Put Blue Waters #s on wiki
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*Phil, potentially
 
*David, after call
 
 
 
== 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