Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(762 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Successfully ran s351 workflow with I/O pipe forwarding
+
*Modify CyberShake to work on RSQSim ruptures
*Found new PGI seg fault - only when run multiple PP jobs in sequence
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Talked with Gideon
+
*CyberShake training
 +
*Update CyberShake study wiki pages to point to SQLite files
 +
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
== Today ==
+
== Project Backlog ==
*Run monitord on s351 job to get metrics
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Add timing calls to extract, seis code
+
*Produce candidate site list for Bay Area CyberShake
*Work on new PGI seg fault
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*ucvm2query
+
*Experiment with OMP parallelization for post-processing
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*No
 
 
 
 
 
*Run test of I/O forwarding on Kraken
 
*Continue testing compiler optimizations
 
*Run some I/O tests to get reference values
 
 
 
 
 
== 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