Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(947 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Looked at Shiyu's volume results, 1D results - emailed out to group
+
*Modify CyberShake to work on RSQSim ruptures
*Submitted TAU profiling run on Kraken
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Submitted 27x weak scaling run on Kraken
+
*CyberShake training
*Identified 3.5 TB of SGTs to move to Ranch, started transfer
+
*Update CyberShake study wiki pages to point to SQLite files
*Continued work on RupGen-api memcached support
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
== Today ==
+
== Project Backlog ==
*Ask Shiyu to generate SGTs for volume
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Monitor Ranch transfer and md5sums (very slow!)
+
*Produce candidate site list for Bay Area CyberShake
*Test SGT Merge on Kraken
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Continue work on RupGen-api memcached support
+
*Experiment with OMP parallelization for post-processing
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*No
 
 
 
== 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